Introduction
A robot can complete a task once and still be unusable in production. Factories need the distribution of cycle times, uptime, intervention rate, failures and recovery duration across shifts, not the fastest edited clip. Cycle time is the elapsed time for one complete work cycle. Reliability describes the probability that the robot completes required work without failure over a defined interval. Takt time is the production pace demanded by customer demand. These metrics are related but not interchangeable.
Key findings
- Figure's BMW record separates process requirements from observed cumulative output: 84 seconds for the full cycle and 37 seconds for loading were requirements, while 90,000+ parts and 1,250+ hours are reported outcomes.
- Cycle time needs explicit start and end conditions and should include reset or recovery rules.
- Average cycle time can hide long-tail failures, interventions and slow recoveries that determine line impact.
- Uptime, intervention rate and mean time to repair need a defined denominator and observation window.
- Manufacturers rarely publish raw shift-level failure and intervention logs.
Humanoid Robot Cycle Time and Reliability Explained - evidence comparison
The table records what each source establishes and keeps missing data visible.
| System or method | What the evidence establishes | Evidence class | Main unresolved point |
|---|---|---|---|
| Figure at BMW | Figure states an 84-second cycle requirement with a 37-second loading phase; separately it reports 90,000+ parts loaded and 1,250+ operating hours. | Company-reported production metrics | Manufacturers rarely publish raw failure logs. |
| Public humanoid demos | Most provide no trial count, failure distribution or uptime denominator. | Insufficient reliability evidence | Metrics from different tasks are not directly comparable. |
| Industrial robot baseline | Conventional automation is evaluated with established uptime and maintenance metrics, creating a higher evidence bar for humanoids. | Operational benchmark context | Independent multi-month reliability studies remain scarce. |
Evidence classification
- Officially documented specifications, standards or project status stated by the responsible organization.
- Real-system evidence demonstrations or deployments performed on physical hardware under described conditions.
- Company claim a numerical or operational statement reported by the company and not independently audited.
- Simulation or research evidence useful for mechanisms, but not proof of field deployment.
- Insufficient public evidence control mode, trial count, version or operating conditions are missing.
Definition and deployment boundary
Cycle time is the elapsed time for one complete work cycle. Reliability describes the probability that the robot completes required work without failure over a defined interval. Takt time is the production pace demanded by customer demand. These metrics are related but not interchangeable.
How a factory workflow is engineered
Define task start and end conditions before timing. Separate walking, manipulation, waiting, charging, reset and recovery. Record success rate and intervention count over many trials. Track mean time between failures and mean time to repair where data exist. Measure thermal limits, battery degradation and calibration drift across shifts.
How to classify pilots and deployments
The review method for humanoid robot cycle time follows the hardware, software and deployment evidence published by Figure AI, IFR, Apptronik. It checks site, task, robot version, run hours, interventions, throughput and whether the activity was a test or production operation and refuses to infer fleet scale, autonomy or reliability from a single edited demonstration.
Operational failure modes
Average cycle time hides long-tail recovery events. A reset by a technician can be omitted from task timing. Battery or actuator temperature can reduce performance later in a shift. Software updates can regress a previously stable task. A robot that does not fall may still fail through grasp, navigation or network errors.
Tasks with credible industrial value
Credible applications include Pilot acceptance testing, Task selection and line balancing, Maintenance planning and spare-parts strategy and Comparison of humanoids against human work and existing automation.
Limitations and missing information
- Manufacturers rarely publish raw failure logs.
- Metrics from different tasks are not directly comparable.
- Independent multi-month reliability studies remain scarce.
- Specifications, prices, repositories and deployment status can change after publication.
- Benchmarks from different robots or environments are not directly comparable.
Conclusion
Cycle-time requirements, achieved throughput and reliability should be reported as separate fields. Figure's BMW record provides useful production exposure and process requirements, but public sources still omit the shift-level intervention and failure distribution needed to calculate uptime or MTBF.
Sources and methodology
Sources for humanoid robot cycle time were rechecked on September 26, 2026, with Figure's BMW production record treated carefully so process requirements are not presented as achieved performance distributions. Missing intervention, reset and failure logs remain undisclosed.
Related TechniaHQRobot guides
Source review notes
Review date recorded September 26, 2026
Supported by the cited sources
- Figure states an 84-second full-cycle requirement and a 37-second loading phase for the BMW task, and separately reports more than 90,000 parts loaded and more than 1,250 operating hours.
- Public humanoid demos: Most provide no trial count, failure distribution or uptime denominator.
Not confirmed or incomplete
- Manufacturers rarely publish raw failure logs.
- Metrics from different tasks are not directly comparable.
- Independent multi-month reliability studies remain scarce.
Likely to change quickly
- Commercial availability, prices, model versions and software access.
- Deployment counts, company partnerships and repository maintenance status.
Share this article
Share the current TechniaHQRobot article page.
Continue reading
Open the latest robotics reporting, Physical AI analysis and hardware notes.