Telemetry & Insights Demo

Unified signals across robots, missions, facilities—plus explainability, impact, and recommended actions.

99.1%
Uptime (last 24h)
192
Throughput (picks/hr)
5
Alerts (last 24h)
142h
MTBF
$18.4k
Downtime $ avoided

Throughput & Alerts (simulated)

Throughput Alerts Hover for values
Open Ops Dashboard

AI Explainability — “Why did this alert trigger?”

Predicted Idle Storm
Confidence: 0.82  •  Impact: ~$3.1k if unmitigated.
Why: queue time ↑, mission retries ↑, corridor camera occlusions, dock queue > SLA.

AI Guidance

Based on last 24h telemetry, RobotOps suggests:

  • ⚙️ Reroute missions from Aisle 12 to restore baseline in ~2.4h.
  • 🔋 Stagger charge windows to reduce battery abuse by ~9%.
  • 🎯 Re-train “Dock 3 Queue” rule with new priority weights.

Economic Impact

Monthly ROI (proj)
+$384.0k
Cost / alert mitigated
$146
Downtime avoided (30d)
$540k
Throughput gain
+1.2%

Next 6h Forecast

Predicted congestion & alert risk (uncertainty band)
Low 0–2h Elevated 2–4h Watch 4–6h

What changed? (24h vs 7d baseline)

Queue time @ Dock 3
+18%
Battery abuse events
+7%
Mission success rate
+3%
Camera occlusions (Zone B)
+22%
View related alerts See Warehousing use case

Bottleneck heatmap

Aisle 12
High
Dock 3
Elevated
Zone B
Moderate
Packing
Low
Tip: reroute missions from Aisle 12, prioritize STAT missions at Dock 3, and schedule Zone-B camera sweep.

What-if simulator

Projected throughput
+1.2%
Expected downtime
-0.1%
Monthly ROI impact
+$384.0k
Confidence
0.78
Run full ROI calculator

Recommended actions (ranked)

Reroute missions away from Aisle 12 Priority 1
Impact: reduce congestion & retries in next 2h

Schedule staggered charge window Priority 2
Impact: battery abuse ↓, throughput stability ↑

Camera sweep in Zone B Priority 2
Impact: reduce occlusions & false stops

Triage Dock 3 queue rule Priority 3
Impact: stabilize queue & STAT mission latency

Alert triage

AlertLikely causeSuggested actionConfidenceEst. impactActions