When importing automated forklifts from China, warehouse automation is not only a mechanical project. It is also an IT infrastructure project.
The fleet management software must communicate with AGVs, process task requests, manage traffic, store operational data and exchange information with other warehouse systems.

For companies with strict IT policies, one of the first questions is whether the Chinese fleet supervisor software can run inside the company's existing server environment.
This includes operating system compatibility, database architecture, virtualization, Docker deployment, network segmentation and offline operation.
Many enterprise environments use Windows Server for business applications, but the compatibility of a Chinese AGV fleet management platform depends entirely on the software architecture supplied by the manufacturer.
Before purchasing, ask the supplier to identify the supported operating systems and the exact software components required by the fleet management system.
The deployment documentation should specify:
Supported operating system versions
CPU requirements
Memory requirements
Storage requirements
Required network ports
Required runtime frameworks
Database requirements
Virtualization compatibility
Backup requirements
Antivirus and security requirements
Do not assume that software that runs on a Chinese manufacturer's engineering computer will automatically run on the customer's corporate Windows Server. The production environment should be validated before deployment.
Docker can make enterprise software deployment easier to standardize, but not every AGV fleet management platform is designed for containerized deployment.
Some systems may consist of several independent services, while others may rely on a traditional Windows application, dedicated database server or proprietary middleware.
If your IT department uses Docker, ask the Chinese supplier whether the fleet management platform supports:
Docker deployment
Docker Compose
Containerized databases
Private container registries
Persistent storage volumes
Container restart policies
Health monitoring
High-availability deployment
The supplier should also explain which services need direct access to the AGV network and which services can remain inside the corporate server environment.
Virtual machine deployment can be attractive for companies that operate VMware, Hyper-V or other enterprise virtualization platforms.
However, the AGV supplier should confirm that virtualization is officially supported rather than simply assuming that the software will work because the operating system can be virtualized.
The engineering review should cover:
Supported hypervisors
Virtual CPU requirements
Memory allocation
Disk performance
Network latency
Time synchronization
USB or hardware dependencies
License activation
Backup and restore procedures
Real-time communication requirements should receive particular attention. A fleet server may tolerate normal enterprise application latency, but communication between the fleet manager, AGVs and safety systems must follow the manufacturer's specified architecture.
The database architecture varies by supplier. A fleet management system may use a commercial relational database, an open-source database, an embedded database or a combination of databases and local data stores.
The important issue for the customer is not simply the database brand. IT teams should understand what information is stored and how that information can be backed up and recovered.
Typical data categories may include:
AGV status
Task history
Alarm records
Battery information
Position information
Mission statistics
Traffic events
Configuration parameters
Map data
User accounts
Ask the supplier whether these databases can be backed up using the company's standard enterprise backup platform.
Direct database access should not automatically be granted simply because the customer owns the server. Some fleet management systems depend on proprietary database structures or application-level logic.
A safer approach is to ask the supplier for documented interfaces for accessing operational data.
These may include:
REST APIs
Web APIs
Database views
Scheduled data exports
CSV exports
Message queues
Reporting interfaces
This allows the corporate IT team to retrieve information without directly modifying production database tables.
An air-gapped or highly isolated network may be possible, but this depends on the software architecture and the customer's operational requirements.
A fully isolated AGV environment must still provide communication between the components required for automation. For example, the fleet server may need to communicate with AGVs, charging stations, warehouse systems and local operator interfaces.
The key question is therefore not simply whether the system has internet access. The customer should determine which connections are actually required.
Ask the supplier to provide a complete communication matrix showing:
Source system
Destination system
IP address or hostname requirement
Protocol
Port
Direction
Purpose
Encryption method
Internet dependency
This document allows the corporate IT department to build firewall rules without relying on assumptions.
Some automation platforms may use cloud services for remote diagnostics, fleet monitoring, software updates or analytics. Other systems can be deployed entirely on local infrastructure.
For an enterprise customer, this distinction should be clarified before signing the purchase contract.
Ask whether the following functions require an external connection:
Initial software activation
License verification
Remote technical support
Software updates
Remote diagnostics
Telemetry transmission
Cloud monitoring
Backup services
If internet connectivity is optional, the customer should document the offline operating procedure before deployment.
Internet connectivity and AGV fleet communication are two different issues. A fleet may operate entirely on a local network while having no connection to the public internet.
However, if the supplier's architecture depends on cloud services, internet loss could affect specific functions.
Before deployment, test:
AGV-to-server communication
Task dispatch
Traffic management
Map access
Operator dashboard
Alarm monitoring
Data storage
Remote support
Software license validation
The acceptance test should clearly distinguish between a local network failure and an internet connection failure.
The fleet management server should normally be treated as an enterprise application rather than an isolated piece of warehouse equipment.
A typical architecture may contain several network zones:
Corporate IT network
Warehouse management network
AGV fleet network
Industrial control network
Guest or maintenance network
Network segmentation can reduce the impact of a problem in one area. The exact architecture should be designed jointly by the customer's IT team and the AGV supplier.
The required protocols depend on the integration architecture. The fleet system may need to communicate with AGVs, WMS, ERP, PLCs, automatic doors, elevators, charging equipment and other warehouse systems.
Depending on the project, technologies may include:
TCP/IP
HTTP or HTTPS
REST API
WebSocket
MQTT
OPC UA
Modbus TCP
Profinet
VDA 5050
The supplier should not simply provide a list of supported protocols. The customer should determine which protocol is used for each specific interface.
Linux compatibility depends on the software architecture. A supplier may provide a Linux-native application, a containerized application, or software that requires Windows-specific components.
If the customer standardizes on Linux, request:
Supported Linux distributions
Supported versions
Required packages
Container requirements
Database requirements
Kernel dependencies
Installation instructions
Upgrade procedure
The customer should complete a proof-of-concept installation before the production fleet is delivered.
A technical IT review should be completed before the AGV contract is finalized.
A useful checklist includes:
| IT Requirement | What to Verify |
|---|---|
| Operating System | Supported Windows or Linux versions |
| Server | CPU, RAM, storage and performance requirements |
| Virtualization | VMware, Hyper-V or other supported platforms |
| Containers | Docker or other container deployment options |
| Database | Database engine, backup and recovery requirements |
| Network | Required ports, protocols and network topology |
| Security | Authentication, encryption and access controls |
| Offline Operation | Functions available without internet access |
| Backup | Complete recovery procedure for server failure |
The most useful document is a complete system architecture and deployment package. It should allow the customer's IT team to understand the system without relying entirely on the supplier's engineers.
Request:
System architecture diagram
Server installation guide
Operating system requirements
Hardware specifications
Database architecture
Network topology
Communication matrix
API documentation
Backup and recovery guide
Software upgrade procedure
License documentation
Cybersecurity documentation
Offline deployment procedure
Ideally, the customer should be able to perform routine server administration without requiring the Chinese manufacturer for every basic IT task.
The customer's IT team should be able to manage:
Server backups
Operating system monitoring
Storage capacity
Network connectivity
User access
Firewall rules
System health monitoring
Virtual machine snapshots where supported
Disaster recovery procedures
The AGV manufacturer should remain responsible for application-level troubleshooting, fleet algorithms, AGV communication and proprietary configuration.
This separation of responsibilities makes long-term support much easier.
Server failure should be included in the system design rather than treated as an unexpected event. The customer should understand how the AGVs behave when the fleet management server becomes unavailable.
The project should define:
AGV behavior during server loss
Current-task behavior
Controlled-stop behavior
Database recovery process
Map recovery procedure
Configuration backup
Server replacement procedure
Maximum acceptable recovery time
For critical warehouses, redundant server architecture may be appropriate depending on the fleet software's capabilities.
The IT portion of AGV acceptance testing should verify more than whether the dashboard opens successfully.
A practical test should include:
Server installation
Database initialization
AGV connectivity
Task dispatch
Network interruption
Server restart
Database backup
Database restoration
User authentication
API communication
Firewall configuration
Offline operation
Alarm logging
Data export
These tests should be documented before the final site acceptance test so that both the customer and supplier understand the expected system behavior.
| Question | Why It Matters |
|---|---|
| Which operating systems are officially supported? | Determines server compatibility |
| Can the software run in a virtual machine? | Supports enterprise infrastructure |
| Is Docker officially supported? | Determines container deployment options |
| Which database engine is required? | Determines backup and maintenance requirements |
| Does the system require internet access? | Important for isolated environments |
| Can the system operate on an air-gapped network? | Determines cybersecurity architecture |
| What ports and protocols are required? | Allows firewall configuration |
| How is the database backed up? | Protects operational data |
| How long does complete system recovery take? | Supports disaster recovery planning |
The best approach is to involve the corporate IT team before the AGV order is finalized. Do not wait until the vehicles arrive to discover that the fleet server requires an unsupported operating system or an internet connection that the company's security policy prohibits.
First, obtain the complete software architecture from the Chinese manufacturer. Then compare the requirements against the company's approved server, virtualization, database, network and cybersecurity standards.
For larger projects, perform a controlled proof-of-concept installation before deploying the production fleet.
The final deployment should have clearly documented operating system requirements, server specifications, database architecture, communication ports, backup procedures, recovery procedures and internet dependencies.
This allows the Chinese AGV system to become part of the company's existing IT infrastructure instead of creating a separate unmanaged technology environment inside the warehouse.
FREE ENGINEERING SUPPORT Stop Gambling on Generic Platforms. Get an AGV/AMR Tailored to Your Warehouse.Buying automated guided vehicles involves complex safety standards (CE/ANSI), navigation setups (Laser SLAM), and ERP system integration. Don't risk your factory safety with middle-men. ✓ 100% Direct Factory: Customized payload up to 5 Tons. ✓ Free CAD Simulation: Send us your layout, and our engineers will simulate the optimal AGV routes. ✓ Global Support: Overseas installation guidance & local maintenance partners. |