Metric contract
Define the event, unit, denominator, sampling period, exclusions and acceptance threshold before the run.
Reading method · 03
Turn robot claims into repeatable measurements that include failure, intervention, drift and recovery.
FUURAA thesis
Engineering map
Each layer states the boundary to establish and the evidence needed for the next decision.
Define the event, unit, denominator, sampling period, exclusions and acceptance threshold before the run.
Separate robot, tool, perception, material, upstream, downstream, safety and operator causes without double counting.
Link software, recipe, tool, calibration, product lot, operator and environmental state to every material result.
Verification questions
Each question needs an object, conditions, denominator, threshold and accountable decision owner.
Is the denominator cycles, attempted parts or accepted parts?
Are manual resets and discarded trials included?
Can another team reproduce the measurement procedure?
What changed between the best demonstration and the reported average?
Evidence to preserve
A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.
Versioned test protocol and raw event log
Failure taxonomy with time, cause, owner and disposition
Calibration, software and configuration evidence for every run
Scope boundary
A clean video, best-case cycle or unversioned spreadsheet cannot establish repeatable production performance.
This is an engineering reading and decision framework; it does not replace application-specific risk assessment, conformity work, procurement acceptance or professional advice.
Sources and evidence status
Source dates and review status remain visible; external sources open in a new tab.
Provides a common measurement frame for pose, path, velocity and related manipulator performance characteristics.
Demonstrates measurement of tool-centre position and orientation degradation to support condition assessment.