Summary
An automotive team needed a flexible, vendor-neutral infrastructure to connect test vehicles, trackside sensors and supporting robotics, and to validate policies before spending track time.
WiseVision provided:
- WiseOS as a ROS 2-based operational layer for telemetry and orchestration
- MCP ROS2 for integrating operator tooling and AI-assisted workflows
- A high-fidelity Digital Twin environment for scenario replay and sim-before-test validation
Stack Used
- WiseOS
- MCP ROS2
- Digital Twins (O3DE / Isaac Sim / Genesis)
- ROS 2
- InfluxDB (Data Black Box)
Key Benefits
- Vendor-neutral test infrastructure
- More productive track time via scenario replay
- Safer automation via sim-before-test
- Full auditability and operator control
Challenges
Mixed vehicle platforms, sensor stacks and vendor tooling
Limited access to track time and the need to replay scenarios reliably
Need for auditability and control over what automation and AI agents can do
Desire to validate policies and workflows safely before real tests
Solution
1. WiseOS – Unified Test Track Fabric
WiseOS connected:
- Trackside sensors (cameras, GNSS/RTK, weather, V2X, etc.) into ROS 2
- Test vehicles and support platforms via ROS 2 nodes or bridges
- Telemetry and events into Data Black Box (InfluxDB)
- Status and timelines from all assets in one place
2. MCP ROS2 – Operator & AI Tools
MCP ROS2 exposed tools with role-based controls:
- List vehicles, sensors and test assets
- Start / stop test runs and collect artifacts
- Query recent events and telemetry windows
- Human-in-the-loop approvals for restricted actions
- All actions logged for review
3. Digital Twin – Scenario Replay & Validation
A Digital Twin of the track and operating zones with O3DE / Isaac Sim / Genesis:
- 3D representation of roads, intersections and infrastructure
- Simulated vehicles, robots and sensor coverage
- Same interfaces as real operations
- Scenario replay and policy testing before real tests
Architecture Overview
- Vehicles and sensors → ROS 2 → WiseOS connectivity & telemetry
- WiseOS → InfluxDB → event logs and analysis
- MCP ROS2 → operator tools and AI-assisted workflows
- Digital Twin → scenario replay, testing and visual context
Digital Twin Use Cases
🎓 Test & Operator Training
Train procedures and tooling workflows without consuming track time
🧪 Scenario Replay
Replay logged events and validate changes against consistent baselines
🤖 ADAS / Autonomy Validation
Test policies safely before running expensive real-world tests
Outcomes
This pattern typically provides:
✅ Vendor Independence
- A neutral infrastructure layer independent of specific vendors
- Freedom to iterate across vehicle and sensor stacks
✅ More Productive Testing
- Scenario replay to reduce repeated manual investigations
- Clear traceability from event → decision → action
✅ Safer Automation
- Sim-before-test workflows for policies and automation
- Risk-free experimentation in the Digital Twin
✅ Full Auditability
- Complete logging of all actions and automation decisions
- Role-based access controls
Next Steps
The same architecture can be extended to multiple tracks, larger fleets, or integrated with test management and reporting tools
Note: Automotive programs are typically evaluated individually with appropriate safety controls and NDAs.