Robotics Public Procurement as Demand-Spec Gate

Date: 2026-06-17 Owner: Finance / Charlie AGT-002 Status: RESEARCH_ONLY Visibility: PUBLIC Public-safety: source-backed industry/framework evidence only; no trade recommendation; no Hugo private portfolio data.

One-line answer

2026 年机器人知识库最值得补的新鲜信号之一，不是又一个 demo，而是中国人形机器人 / 具身智能开始出现可公开引用的政策场景清单、政府/高校/产业平台采购公告和中标规格；这把研究焦点从“机器人能不能表演”推进到“采购方到底要求什么、愿意为哪些能力付款、这些能力离 S5 经济性还差什么”。🟢/🟠

Core question

公开采购和招标是否已经能作为 humanoid robotics 从 S3/S4 走向 S5 的需求侧证据？

Current answer: yes for S4 demand-spec evidence, no for S5 economics. Procurement documents show budgets, delivery windows, product specs, development openness, training / installation / warranty requirements, and sometimes unit counts. They still do not disclose productive robot-hours, utilization, customer ROI/payback, renewal, vendor gross margin, intervention rate, maintenance burden, or repeat deployment economics. 🟢/🟠

Why this updates stale robotics knowledge

Prior artifacts already track demos, runtime, teleoperation, standards, RaaS, Amazon fleet benchmarks, and IFR denominator. The stale gap is customer-side procurement language: what buyers now put into budgets and specs.

Signal update:

• MIIT / SASAC 2026专项行动 asks selected provincial regions to choose at least 20 key scene units each, covering at least two of industrial / service / special domains; relevant central enterprises should choose at least 10 key scenes each. Work plans are due 2026-06-30, summaries due 2026-11-30. 🟢 MIIT/SASAC notice via Shenzhen Software Industry Association repost, 2026-06-10.
• Policy target: by end-2026, key products such as humanoids should complete application validation and routine deployment in representative scenarios, form 100+ high-value application scenarios, and drive “万台级” landing capability. 🟢
• Public tenders in May 2026 show buyers already specifying humanoid unit count, budget, delivery, sensors, compute, freedom degrees, payload, runtime, SDK/API/ROS-like openness, training, installation, warranty, and domestic-procurement constraints. 🟢/🟡

Noise boundary:

• A procurement notice is not proof of useful deployment.
• A budget is not proof of ROI.
• A technical spec is not proof the robot can work in the target process.
• An education/research procurement is not the same as industrial paid deployment.

Evidence table

Procurement-spec pattern: what buyers are actually asking for

Across the reviewed notices, procurement language clusters into six categories:

1. Body / mobility

• Height, weight, adult-like form, bipedal or wheel-legged movement, walking speed, slope / step / gap performance, DOF count.
• Example: Suzhou specifies 165 cm, 58 kg, 47 DOF, 5 km/h flat-ground humanoid walking. 🟢

2. Manipulation

• Arm payload, dexterous hand DOF, tactile sensing, repeat positioning, SDK control, grasp-load tests.
• Example: Unitree G1-EDU + Dex3-1 mirror page specifies Dex3-1 two hands, each 7 DOF, 33 tactile sensors, 500g max grasp of a 5cm hard object, ±2mm fingertip repeat positioning. 🟡

3. Perception / compute

• Depth cameras, LiDAR, RGBD, IMU, microphone array, AI compute, Jetson / TOPS-style edge compute.
• Example: Suzhou asks for 275 TOPS AI compute and multiple sensor types; Unitree mirror page references NVIDIA Jetson Orin. 🟢/🟡

4. Developer openness

• SDK/API, bottom-level control, high-level control docs, simulation model/robot description files, reinforcement-learning samples, OTA, ROS2-style development.
• This is a high-signal clue: many current buyers are not just buying labor substitution; they are buying data / development / education infrastructure. 🟢/🟠

5. Delivery / after-sales

• 30–90 day delivery windows, installation, training, warranty, maintenance, invoices, full-payment after acceptance.
• This converts demos into procurement operations, but still does not disclose field reliability. 🟢

6. Policy / domestic procurement

• Some notices specify domestic goods, SME-oriented procurement, no imported goods, no consortium, no subcontracting.
• This matters for China supply-chain localization but should not be overread as proof of superior technology. 🟢/🟠

Stage classification

Current classification: S4 demand-spec gate.

Why S4:

• Procurement budgets and award notices show real buyer processes, not only company claims. 🟢
• Specs reveal what the customer side thinks is purchasable and testable in 2026: full-body platform, sensors, compute, manipulation, SDK, simulation, training, warranty. 🟢
• The MIIT/SASAC action creates a tracked scene funnel with explicit deadlines and summary mechanisms. 🟢

Why not S5:

• Most reviewed procurement is education / research / demonstration / innovation-center infrastructure, not scaled production-work replacement.
• Public sources do not show accepted productive robot-hours, autonomous task-completion rate, intervention minutes per robot-hour, uptime distribution, maintenance cost, customer ROI/payback, renewal, vendor margin, or repeat orders.
• Unit counts are still small in visible procurement examples: 1 unit, 4 units, one batch, one training room. 🟢/🟠

Signal vs noise

Signal:

• More procurement docs with explicit operational KPIs: task success rate, daily useful hours, uptime, MTBF/MTTR, safety cases, acceptance criteria, intervention logs. 🟢/🟠
• Repeat purchases by the same buyer after initial acceptance. 🟢
• MIIT/SASAC 2026 summary publishing scenario-level performance and deployment counts by 2026-11/12. 🟢
• Shift from “education / display / development platform” toward “production workstation / maintenance / logistics / inspection” with quantified output requirements. 🟢/🟠

Noise:

• “具身智能” wording in procurement titles without task acceptance metrics.
• Feature specs that prioritize performance, gestures, exhibition, or drumming over productive workflows.
• Budget size without deployment outcome.
• One-off procurement by a school or exhibit hall treated as proof of market-wide demand.

What would change our mind

Upgrade toward stronger S4 / early S5 if:

1. A buyer publishes acceptance reports with robot-hours, task success rate, uptime, intervention and safety incidents. 🟢
2. A user unit makes a second purchase or expands from 1–4 robots to a named fleet after measured results. 🟢
3. Procurement specs shift from generic platform specs to process-specific ROI targets, e.g. parts moved per hour, inspection accuracy, maintenance turnaround, safety shutdown rate, or labor-hours replaced. 🟢/🟠
4. Vendors disclose robot revenue / gross margin / service burden tied to procurement deliveries. 🟢
5. MIIT/SASAC 2026 summary provides enough denominator data to estimate accepted units per scene and deployment conversion. 🟢/🟠

Downgrade if:

1. 2026采购 remains concentrated in display / education / lab platforms, with little evidence of production use. 🟢/🟠
2. Specs keep emphasizing DOF/TOPS/appearance while omitting uptime, safety, maintenance and ROI. 🟢
3. Public procurement repeatedly fails, cancels, or produces only one bidder / low competition. 🟢/🟡

Common misconceptions

1. “Government procurement = commercialization proven.” Correction: it proves budgeted demand and procurement process; commercialization requires accepted deployment and repeat economics. 🟢/🟠

2. “Specs like 275 TOPS or 47 DOF prove capability.” Correction: they prove buyer requirements and product configuration, not task performance or economics. 🟢

3. “Education procurement is irrelevant.” Correction: it is not direct labor substitution, but it can build data, talent, testing and developer infrastructure; this matters for a construction cycle. 🟢/🟠

4. “Domestic procurement constraints mean China wins.” Correction: they show localization policy and market access conditions, not automatic technical or economic leadership. 🟢/🟠

Public-safe draft paragraph

A useful 2026 robotics signal is hiding in procurement documents. China’s humanoid and embodied-AI push is no longer only a set of company demos: MIIT/SASAC’s 2026 action asks selected provinces and central enterprises to identify real scene units, build application consortia, validate deployment, and summarize results by late 2026. At the micro level, public tenders now specify budgets, unit counts, sensors, compute, DOF, runtime, SDK/API openness, training, warranty and delivery windows. That is a real S4 demand-spec signal. It is not S5 economics yet: the missing denominator is still productive robot-hours, intervention rate, uptime, ROI/payback, renewal, vendor margin and service burden.

Research implications

• Add procurement documents to the S4-to-S5 monitoring system as a demand-side evidence source, separate from OEM announcements.
• Track buyer type: education / lab / display / innovation center / industrial user / central enterprise / government scene unit.
• Track procurement purpose: platform research, data collection, training, demonstration, production task, inspection, logistics, maintenance, service.
• Track accepted deliverables: unit count, delivery time, warranty, training, SDK, safety requirements, task metrics, acceptance reports.
• Do not use procurement budgets as revenue-quality proof until award, delivery, acceptance, and repeat procurement are visible.

Source list

• MIIT / SASAC, “工业和信息化部办公厅 国务院国资委办公厅关于联合开展2026年度人形机器人与具身智能实景实训专项行动的通知,” 工信厅联科函〔2026〕256号, dated 2026-06-03; reposted by Shenzhen Software Industry Association 2026-06-10. 🟢 https://ssia.org.cn/page74?article_id=2726
• Suzhou Public Resources Trading Platform, “苏州市具身智能机器人综合创新中心人形机器人采购项目中标结果公告,” 2026-05-20, project SZQY2026-GQ-WZ-G-011. 🟢 https://ggzy.suzhou.gov.cn/jyxx/003034/003034003/20260520/987cb1ce-ab04-46d9-a445-3ff2df9d3bc5.html
• Beijing Public Resources Trading Service Platform, “（教育教学改善）具身智能数据采集与人形机器人装配技术实训中心建设公开招标公告,” 2026-05-14, project S110000C005106773001. 🟢 https://ggzyfw.beijing.gov.cn/jyxxcggg/20260514/5531110.html
• Far East Tender Procurement Trading Network, “具身智能（机器人、机器狗）采购项目招标公告,” 2026-05-06, project 0722-26FE6208SZF-0. 🟢 https://szyd11.com/tender/detail?TenderId=1010283
• Qianlima tender mirror, “具身智能人形机器人本体及灵巧手采购（JJ20260018）结果变更公告,” 2026-05-28. 🟡 https://www.qianlima.com/bid-600727860.html

Public-safety flag

PUBLIC-safe as an evidence-gate memo. Do not include Hugo portfolio weights, trade rationale, paid-report excerpts, rumors, or buy/sell/hold language. Do not claim any vendor is a winner from procurement unless award, delivery, acceptance, repeat orders and financial materiality are separately sourced.