Rate
Normalise events by missions, lines, distance or operating hour.
Deployment evaluation · 14
Use stable categories and denominators for blocked paths, bad scans, failed transfers, failed picks and manual resets.
FUURAA thesis
Engineering map
Each layer states the boundary to establish and the evidence needed for the next decision.
Normalise events by missions, lines, distance or operating hour.
Measure detection, response, recovery and verification time.
Track recurrence after software, layout or process changes.
Verification questions
Each question needs an object, conditions, denominator, threshold and accountable decision owner.
Are categories mutually understandable?
Which events require physical intervention?
How much work is shifted to support teams?
Does the same fault recur?
Evidence to preserve
A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.
Versioned exception taxonomy
Event-level burden and recovery log
Corrective-action and recurrence record
Scope boundary
Vendor-defined intervention metrics may use different denominators and cannot be compared without reconstruction.
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.
Develops repeatable measures for mobility, manipulation, sensing, endurance, communications, operator proficiency, logistics and safety.
Studies injury trends, risk profiles and worker safety around traditional, collaborative, mobile and AI-enabled robots.