Executive signal. Humanoid robotics is crossing a hard boundary: the market is beginning to judge machines by productive minutes, successful cycles and avoided human intervention rather than by the quality of a stage demonstration. Beijing’s World Robot Conference and World Humanoid Robot Games are making that transition unusually visible. The programme now includes continuous tasks in factories, hotels, homes, retail and emergency settings, while Western industrial deployments are publishing the first operational evidence from automotive and logistics sites. The decisive contest is no longer who can build a robot that walks. It is who can operate a safe, supportable fleet that produces an economic return inside an existing workplace.
This is an important change of state for physical AI. A general-purpose model can fail, retry and conceal much of its operational friction behind a software interface. A humanoid cannot. Every uncertain grasp, thermal limit, network interruption and reset becomes visible on the factory floor. Physical AI therefore converts familiar model risks into measurable operational liabilities: downtime, damaged material, missed takt time and safety exposure. Enterprises evaluating the sector should now treat the robot as one component of a wider production system—not as an embodied chatbot, and not as a miraculous replacement for conventional automation.
1. Beijing moves the benchmark from spectacle to work
The latest signal comes from Beijing, where more than 300 companies are expected to show over 2,000 exhibits at the World Robot Conference, according to reporting by Reuters. The timing is commercially charged: the conference coincides with Unitree’s Shanghai market debut after intense retail demand for its offering. Yet the underlying story is less about capital-market theatre than about a change in the questions being asked. Customers increasingly want to know how much supervision a machine needs, how consistently it completes a useful task and whether its output can justify its total operating cost.
The official programme for the second World Humanoid Robot Games captures the shift. Alongside races, football and street dance, organisers have added housekeeping, firefighting and retail assistance. The scenario events are designed for authentic settings such as factories, hotels and model homes, with autonomous positioning, recognition and manipulation encouraged. Tasks include folding clothes, preparing food and extinguishing fires. Most significantly, robots are expected to execute continuous, long-duration work rather than a single rehearsed move.
That distinction matters. A backflip proves an impressive combination of dynamics, control and hardware. It says little about whether a machine can identify unfamiliar objects, complete hundreds of mundane cycles, recover from a misplaced item and safely resume after an exception. Commercial work is an adversarial benchmark made of dust, glare, variable packaging, obstructed routes and tired infrastructure. It is also relentlessly statistical. A robot can succeed in a promotional video while remaining economically unusable if its rare failures demand constant expert attention.
Reuters reports that an estimated 50% to 70% of humanoids produced in China this year may be used in “data factories” to gather training data rather than perform paid productive work. That estimate should temper simple unit-shipment narratives. Robots deployed to create demonstrations or collect trajectories are part of the development pipeline, not necessarily evidence of end-market adoption. The more revealing numbers will be paid operating hours, task throughput, intervention frequency, renewal rates and expansion from one workflow to several.
2. The real product is the operational envelope
The emerging evidence from automotive production is valuable because it exposes the narrowness—and seriousness—of current deployments. BMW says Figure 02 supported production of more than 30,000 X3 vehicles during a ten-month programme at its Spartanburg plant. The robot inserted sheet-metal parts for welding, a repeatable and physically demanding body-shop task. BMW is now moving to Figure 03 for a logistics sequencing application in which unsorted components are picked and placed into a trolley in assembly order.
Figure’s own deployment report gives the operational detail that the market needs more of. The company reports more than 90,000 parts loaded, over 1,250 runtime hours and ten-hour weekday shifts. It defined explicit targets for cycle time, placement accuracy and human interventions. The application required three sheet-metal parts to be positioned within a five-millimetre tolerance, with a target above 99% success per shift and zero interventions. Those are not general-intelligence benchmarks. They are production engineering constraints.
The account is also revealing because it names a hardware weakness. Figure identifies the forearm as the top failure point in that deployment and says the experience drove a redesign of wrist electronics and cabling in Figure 03. That is what genuine field learning looks like: not a larger benchmark score, but a failure mode eliminated from the next bill of materials. Every deployed hour generates both task data and reliability data. The company that closes this loop fastest can turn physical failures into design changes before competitors discover the same issues at scale.
For buyers, the lesson is to define the operational envelope before discussing generality. What objects must be handled? At what weight, tolerance and cycle time? How often does the environment change? Can the workcell be separated from people? Who clears faults? What happens when wireless connectivity disappears? A humanoid may eventually switch among many skills, but today’s strongest economic case remains a constrained workflow in a human-designed space where legs and arms avoid an expensive facility retrofit.
3. Integration, not intelligence, becomes the control plane
The deployment stack extends far beyond the robot and its policy model. Agility Robotics’ August account of its customer deployment process describes simulation, recreation of the customer workflow, physical data collection, on-site validation, mapping, Wi-Fi integration, fleet-management configuration, workforce communication and a 90-day operating-data phase. It also states an uncomfortable but useful truth: some candidate tasks are better served by an autonomous mobile robot or a fixed arm.
This is not a concession. It is a sign of an industry becoming more disciplined. Conventional automation wins when the task and environment can be standardised. A humanoid earns its premium only where human geometry, changing workflows or disconnected “islands of automation” make fixed systems impractical. The procurement decision should therefore begin with process decomposition, not with a preferred robot. Organisations need a ranked map of repetitive, ergonomically difficult and safety-sensitive work, together with the cost and variance of each workflow.
The integration burden also creates a new control plane. Fleet software must schedule work, enforce safety states, distribute approved models, monitor health and preserve event logs. Identity and access management must extend to robots that can press buttons, move goods and operate near valuable equipment. Network segmentation must assume that sensors may capture sensitive industrial layouts and production data. Software updates need staged roll-outs and rollback paths because an update that improves one behaviour could degrade another. The robot’s “brain” may attract attention, but the enterprise-grade product is the entire managed system.
Agility says its current generation remains inside sectioned-off workcells during commercial deployments and that it is targeting a cooperatively safe humanoid for 2027. That timeline is a reminder that capability and permission are separate. A machine may be technically able to navigate near people before a customer can demonstrate that the combined system, workflow and facility controls are acceptably safe. The winning vendors will make assurance evidence portable: documented hazard analyses, validated stop behaviour, traceable software versions and clear responsibility for remote support.
4. Unit economics will punish hidden human labour
Humanoid economics are often reduced to purchase price versus annual wages. That is dangerously incomplete. Reuters cites a Chinese brokerage estimate that an industrial humanoid would need an all-in cost of roughly 160,000 yuan to pay back within two years against a worker earning 80,000 yuan annually, while typical robot costs are reported at 300,000 to 500,000 yuan. Even that comparison omits integration, supervision, spares, charging, service, floor modifications, insurance and the cost of production interruptions.
The central metric should be cost per successful autonomous task, not cost per robot. Its denominator must exclude time spent waiting for a teleoperator, technician or deployment engineer. If one person quietly rescues several robots throughout a shift, that labour belongs in the automation budget. The same is true of remote human demonstrations used to produce training data. Human assistance can be a rational bridge to autonomy, but it must be measured rather than hidden behind the word “AI”.
Robots-as-a-Service can reduce initial capital risk and align supplier incentives with uptime. Agility’s commercial agreements provide an early template. Its GXO deployment put Digit into day-to-day logistics operations under a multi-year arrangement, while a 2026 agreement with Toyota Motor Manufacturing Canada followed a pilot and targets manufacturing, supply-chain and logistics work. These are vendor statements and should be assessed accordingly, but the contractual progression from pilot to service agreement is more meaningful than a laboratory demonstration.
Enterprise buyers should demand a clean economic ledger: productive hours; task success rate; mean time between interventions; recovery time; service response; energy use; human oversight minutes; damage and near-miss events; and the percentage of the shift in which the robot is available but not useful. A vendor that refuses these metrics is selling optionality, not production capacity.
5. Physical AI creates a cyber-physical attack surface
Once robots become networked workers, cybersecurity becomes part of functional safety. A compromised office application can leak information; a compromised robot can also move, obstruct, drop or strike. The risk model therefore needs both cyber controls and physical consequence analysis. Credentials for fleet orchestration, model registries and remote support are privileged production assets. Sensor streams can reveal factory layouts, inventory flows, employee behaviour and proprietary processes. Logs may become evidence after an incident and must be protected from tampering.
The highest-risk path is not necessarily a cinematic hostile takeover. More plausible failures include a stolen support account, an unsafe configuration pushed to the wrong fleet, poisoned training data, an unverified model update or a denial-of-service incident that stops a critical workflow. Enterprises should separate safety-certified control functions from higher-level learning components wherever feasible. Network loss should lead to a predictable safe state. Remote access should require strong authentication, short-lived credentials and complete audit trails. Model and firmware packages should be signed, versioned and reproducible.
Procurement teams should also ask where inference occurs, what telemetry leaves the site and whether vendor personnel can view camera data. Retention and jurisdiction matter, particularly when robots operate in sensitive manufacturing environments. A physical-AI contract needs breach-notification terms, support-access controls, vulnerability-handling commitments and an exit plan that preserves operational continuity if the vendor or cloud service becomes unavailable.
The security objective is not to eliminate autonomy. It is to constrain autonomy inside an observable, recoverable system. The mature deployment will know which robot executed which policy, on which software version, against which task instruction, with which sensor and intervention record. Without that chain of evidence, post-incident analysis becomes guesswork.
What to watch next
- Continuous-task results from Beijing. Completion time matters less than autonomous completion rate, intervention count and performance after environmental changes.
- Expansion beyond the first use case. The strongest signal will be customers reusing the same fleet across multiple workflows without a fresh engineering project each time.
- Published reliability data. Expect pressure for operating hours, mean time between failures, recovery time and safety-event reporting—not just unit shipments.
- Safety standardisation. Watch how dynamically stable mobile robots are covered and how vendors translate standards into deployable evidence for employers and insurers.
- Service-network depth. Hardware margins may matter less than field support, spare parts, fleet software and the ability to restore production quickly.
- The supervision ratio. A credible path to scale requires each human operator to support many robots, with intervention minutes falling over time.
Closing assessment. The humanoid market is not entering an era of effortless generality. It is entering the uptime economy. Beijing’s scenario contests, BMW’s production metrics and the emerging Robots-as-a-Service model all point in the same direction: physical AI will be valued as an operational system. The near-term winners will be vendors that choose narrow work intelligently, measure failure honestly and surround capable machines with industrial-grade safety, security and support. The robot that wins may not be the one with the most dramatic demonstration. It will be the one that turns up for the next shift.
Sources
- Reuters — Beyond marathons and backflips, China’s robots face a commercial test
- Beijing Municipal Government — 2nd World Humanoid Robot Games
- BMW Group — Figure 03 project at Plant Spartanburg
- Figure — Figure 02 production deployment report
- Agility Robotics — Humanoid deployment process
- Agility Robotics — Digit deployment at GXO
- Agility Robotics — Toyota Motor Manufacturing Canada agreement
Leave a Reply