Many AGV buyers focus on the robots themselves and underestimate the importance of the server architecture. In reality, a poorly designed RCS server can create more downtime than the AGVs.

For a typical 20-AGV deployment, the recommended architecture is:

Warehouse LAN      │      ├── RCS Server      │      ├── SQL Database      │      ├── WMS / ERP Interface      │      ├── Wi-Fi Controller      │      └── Engineering Workstation

Best practice is to place the AGV system on a dedicated VLAN rather than mixing it with office traffic.

What Server Specifications Are Needed for 20 AGVs?

The exact requirements depend on fleet size, traffic density, mission volume, integration complexity, and database size.

Minimum Specification

Preferred Specification

This provides capacity for future AGVs, WMS integration, reporting databases, and simulation modules.

Can I Run the RCS in VMware or Hyper-V?

In most cases, yes.

Many modern Chinese AGV RCS platforms support:

• VMware – Widely used in industrial environments

• Hyper-V – Common in Microsoft-based IT infrastructures

Virtualization Benefits

• ✔ Easier Backup Management

• ✔ Faster Disaster Recovery

• ✔ Hardware Independence

• ✔ Snapshot Capability

• ✔ Reduced Maintenance Downtime

Before purchasing, request written confirmation regarding supported hypervisor versions, minimum VM resources, and licensing restrictions.

Does the RCS Need Permanent Internet Access?

A mature AGV system should not require internet access for daily operation.

AGVs   ↓ RCS Server   ↓ Local Database

Core fleet management functions should continue operating even if the facility loses internet connectivity.

Important Procurement Question:
Can the RCS operate indefinitely in a fully isolated or air-gapped network environment?

Licensing Considerations

Online Licensing

Internet Failure      ↓ License Check Failure      ↓ Potential Software Restriction

Online licensing may require periodic verification and can create operational risks.

Offline Licensing

Preferred for industrial AGV deployments.

• Hardware Key

• License File

• Server MAC Address

• USB Dongle

For mission-critical facilities, offline licensing is generally safer.

How Should I Back Up the Layout Database?

Your AGV map is often one of the most valuable project assets.

It typically contains:

• Navigation Maps

• Traffic Rules

• Safety Zones

• Charging Locations

• Elevator Interfaces

• Door Interfaces

Recreating these assets can require days or even weeks.

Recommended Backup Strategy

RCS Server     ↓ Local Backup NAS     ↓ Offsite Backup

This architecture protects against server failures, SSD failures, ransomware incidents, and accidental deletion.

Should You Use Database Replication?

Primary RCS      ↓ Real-Time Replication      ↓ Secondary RCS

Failover times can often be measured in minutes instead of hours.

Network Security Recommendations

Local Deployment

• ✔ Local Database

• ✔ Local User Authentication

• ✔ Local Backups

Remote Support Controls

• ✔ VPN-Only Access

• ✔ Approval-Based Sessions

• ✔ Session Logging

• ✔ Read-Only Diagnostics Option

Firewall Segmentation

• ✔ AGV Traffic

• ✔ Office Traffic

• ✔ Guest Wi-Fi

• ✔ Remote Support Traffic

Questions to Include in Your AGV RFQ

• ✔ What are the official CPU and RAM requirements for 20 AGVs?

• ✔ Is VMware officially supported?

• ✔ Is Hyper-V officially supported?

• ✔ Can the system operate permanently without internet access?

• ✔ How is offline licensing managed?

• ✔ What database engine is used?

• ✔ How are backups performed?

• ✔ Is database replication supported?

• ✔ Can the RCS run in an air-gapped network?

• ✔ What is the recovery process after a server failure?

Procurement Recommendation

For a typical 20-AGV warehouse deployment, the safest architecture is:

• ✔ Dedicated Virtualized RCS Server

• ✔ 32 GB RAM

• ✔ RAID SSD Storage

• ✔ UPS Protection

• ✔ Daily Automated Database Backups

• ✔ Weekly Map Backups

• ✔ Offline Software Licensing

• ✔ Dedicated AGV VLAN

• ✔ VPN-Controlled Remote Support

This architecture delivers enterprise-level reliability while remaining independent from external internet services and minimizing downtime risks caused by server failures.