Summary
A distribution warehouse operated multiple AMR fleets from different vendors, each with its own tools and monitoring.
WiseVision helped them create a unified operational layer that:
- Connected AMRs and sensors under WiseOS
- Used MCP ROS2 to provide a common control and debugging interface
- Introduced a Digital Twin of the warehouse to test route changes and layouts
Stack Used
- WiseOS
- MCP ROS2
- Digital Twins (warehouse)
- ROS 2
Key Benefits
- Single view of AMR fleet
- Lower risk when changing routing logic
- Less time switching between tools
- Easier AI-based orchestration
Challenges
Fragmented monitoring – each AMR vendor had its own UI and API
Difficult to coordinate routes across fleets and reduce congestion
Limited visibility into historical telemetry and bottlenecks
High risk when rolling out new routing policies directly on production floor
Solution
1. WiseOS – Fleet Connectivity
WiseOS as the central ROS 2-based operating layer:
- AMRs connected via ROS 2 bridges into a shared ROS 2 graph
- Telemetry stored in Data Black Box (InfluxDB)
- Fixed sensors integrated into same telemetry layer
- One place to observe fleet health
2. MCP ROS2 – Shared Interface
MCP ROS2 exposed the ROS 2 environment as MCP tools:
- List robots and their key metrics
- Subscribe to navigation topics and logs
- Trigger or simulate route changes
- Prototype orchestration logic
3. Digital Twin – Warehouse Flows
A Digital Twin of the warehouse:
- 3D environment with racks and workstations
- Simulated AMRs following route plans
- Integration with WiseOS / MCP ROS2
- What-if scenario testing
Architecture Overview
- Multiple AMR fleets → ROS 2 → WiseOS connectivity & telemetry
- WiseOS → InfluxDB Data Black Box → dashboards & analysis tools
- MCP ROS2 → MCP clients (AI assistants, custom tools)
- Digital Twin → ROS 2 integration for simulation & validation
Outcomes
Typical benefits for this pattern:
✅ Unified Visibility
- A single view of the AMR fleet, regardless of vendor
- One monitoring interface for operations teams
✅ Lower Risk
- Test routing logic changes in twin first
- Safer deployment of new policies
✅ Time Savings
- Less time switching between proprietary tools
- Faster troubleshooting and debugging
✅ Future-Ready
- Easier path to AI-based orchestration using MCP ROS2
- Foundation for advanced analytics
Next Steps
The same approach can be extended to additional warehouses, factory lines, or integrated with WMS/ERP for end-to-end visibility