What we said
In physical AI, the ability to measure task success, degradation and real-world robustness is often as important as the model itself. If a company cannot measure the failures that occur in real environments, or detect whether changes improve those failures over time, it will struggle to show genuine learning. If that is right, measurement capability should be one of the things separating companies in production from companies stuck in pilots.
How we tested it
We looked at three measures:
- How well buyers say they can actually measure four different things about the systems they are closest to: whether a deployment is succeeding or failing, whether performance is degrading over time, whether a change actually improved real-world performance, and how the system handles edge cases it wasn’t built for.
- Which operating metrics they track consistently today.
- How often evaluation comes up when buyers are asked what the hardest part of making physical AI work is.
What we found
Few buyers can reliably tell whether their systems are getting better. Only 20% of buyers say they can reliably measure whether a change they made improved real-world performance. 19% say the same about how their system handles conditions it was not built for. The metrics buyers do track lean toward keeping the plant running: 69% track uptime and 65% track safety incidents, while intervention rate is tracked by 42% and recovery success by 26%.
Directional
20%
of robotics buyers say they can reliably measure whether a change they made actually improved real-world performance — which, in our view, a learning loop depends on
All qualified buyers, n=85 · Segment bases are small (sizes shown in each column header); read differences across segments as directional, not precise
| Category | Scaled (n=32) | Limited production (n=29) | Piloting (n=24) |
|---|---|---|---|
| Whether a deployment is succeeding or failing at its task in the real world | 56% | 24% | 13% |
| Whether performance is degrading over time | 44% | 28% | 4% |
| Whether a change to the system actually improved real-world performance | 38% | 10% | 8% |
| How the system handles edge cases and conditions it wasn't built for | 41% | 10% | 0% |
All qualified buyers, n=85 · Segment bases are small (sizes shown in each column header); read differences across segments as directional, not precise
See the full benchmark69%
of robotics buyers track uptime and availability consistently, the most-tracked of the eleven metrics we asked about
All qualified buyers, n=85 · Select all that apply, so the shares add to more than 100% · Buyers track 5.4 of these metrics each on average
| Category | % of buyers |
|---|---|
| Uptime / availability | 69% |
| Safety incidents | 65% |
| Cost per unit of work | 61% |
| Throughput | 58% |
| Deployment time | 53% |
| Autonomous completion rate | 51% |
| Payback period | 45% |
| Intervention rate | 42% |
| Mean time to resolution | 41% |
| Support hours per unit / site | 31% |
| Recovery success rate | 26% |
| None of the above | 2% |
All qualified buyers, n=85 · Select all that apply, so the shares add to more than 100% · Buyers track 5.4 of these metrics each on average
See the full benchmark