Edge-AI Based Distributed Fleet Coordination for Autonomous Mobile Robots (AMRs) in Smart Warehouses
“We are building a smart traffic control system for warehouse robots so they can talk to each other and navigate without crashing. Instead of relying on a central computer that might fail, each robot makes its own decisions to avoid jams and finish tasks faster.”
Deconstructed Problem Blueprint
WHAT TO BUILD?
A decentralized multi-agent coordination software framework designed to run on edge hardware (Jetson/Raspberry Pi) for autonomous mobile robots.
WHO IS IT FOR?
Bharat Electronics Limited (BEL) and large-scale warehouse operators, logistics managers, and automated manufacturing facilities.
WHY DOES IT EXIST?
Centralized systems create single points of failure and latency issues. In a warehouse, if the Wi-Fi drops or the server lags, the entire fleet stops, leading to massive productivity losses.
INPUT → PROCESS → OUTPUT ARCHITECTURE PIPELINE
Lidar/Depth camera point clouds, IMU sensor data, peer-to-peer Wi-Fi/Bluetooth signals, and task priority queues.
Distributed consensus algorithms (e.g., Raft or Paxos-lite), Collision Avoidance (ORCA or Velocity Obstacles), and decentralized task allocation (Market-based bidding).
Real-time velocity commands for robot motors, collision-free path trajectories, and a lightweight dashboard visualizing fleet health and status.
CONSTRAINTS
- Must run on edge hardware (limited CPU/RAM)
- Zero reliance on a central server for pathfinding
- Must handle dynamic obstacles (human workers/other robots)
- Low-latency communication requirement
JURY METRICS
- Zero inter-robot collisions
- 20% reduction in task completion time vs. stop-and-wait
- Communication overhead per robot
- System recovery time after node failure
CORE BOTTLENECK
Achieving stable 'Distributed Consensus'—ensuring all robots agree on who moves first at a narrow intersection without a central 'traffic light' controller.
Why You Should Choose This PS (Pros)
- High industrial relevance for BEL
- Clear, measurable success criteria
- Strong potential for hardware-software integration demos
- Highly scalable concept
Challenges & Risks to Watch (Cons)
- Requires strong grasp of robotics middleware (ROS 2)
- Simulation environment setup can be time-consuming
- Debugging distributed systems is notoriously difficult

