⚠️ A working draft under continuous verification. Every case here is curl + WebFetch verified. Three caveats: (1) some news sites (FreightWaves / The Robot Report) return bare-curl 403 from bot protection but are 200 with a browser UA — links valid; (2) mainland gov sites returning curl 000 are geo-blocks, not dead links (e.g. the State Grid Hangzhou gov portal), so reachable first-hand/media sources are cited instead; (3) strictly separate four classes: real "mobile carrier ferries dog" / quadruped into a dispatch system / inter-model cooperation / standalone products — explicitly excluding "wheeled-legged single machine" and "quadruped returns to a fixed charging dock" from "car-dog cooperation."
🌐 What this answers
A very concrete question: which AMRs/AGVs have robot dogs actually been system-integrated / interface-bridged / partnered with? Are there named products and deployments? This article lays out every curl-verifiable case worldwide and honestly flags which are real integration vs misread.
Following: Marsupial research (academic + architecture), the Fusion article (three fusion forms), GO2 starter (GO2 has no ready AMR integration). This one is the "integration cases" list itself.
🧭 One-line overview
Real "mobile carrier ferries/releases a child dog" commercial integrations are very few worldwide — one in China, one overseas. Real "quadruped plugged into an AMR dispatch system" — one solid case in China (SEER). The rest is either inter-model cooperation, a wheeled-legged single machine, a "dog returns to a fixed dock" misread as carrier, or vendors with separate products and zero linkage.
✅ 2. Real car-dog integration cases (mobile carrier carries dog)
| Partners (dog × vehicle/AMR) | Region | Scenario | Source |
|---|---|---|---|
| robot dog × UISEE UiBox autonomous vehicle × State Grid Hangzhou | China | vehicle ferries the dog ~10 km cross-zone; dog dismounts for last-100-m inspection of tunnels/stairs; 15 km² coverage1 | UISEE first-hand |
| RIVR (ex-Swiss-Mile) wheeled-legged × Evri vans | UK | last-100-yard: driver pulls to the curb, the dog leaves the van to deliver to the door while the driver handles other parcels2 | RIVR official |
| RIVR wheeled-legged × Veho vans | US Austin | quote: the robot "navigates from the delivery vehicle all the way to the customer's doorstep," ~200/day alongside a human driver3 | FreightWaves (needs browser UA) |
RIVR's platform comes from the Swiss-Mile wheeled-legged lineage4. These three are the only curl-verifiable "vehicle→dog" cooperations worldwide — all inspection/delivery, outdoor; none is "in-plant multi-floor haulage," so for Otsuka they are architecturally analogous references, not a copy-paste in-plant solution.
🧩 3. Quadruped truly plugged into an AMR dispatcher (RCS) — closest to Otsuka's "software orchestration"
The most valuable finding this round, because it's the ready reference for "scheduling the dog" in the Otsuka plan:
- SEER (Standard Robots): robot dogs D1/D2 plugged into the M4 dispatcher, unified with the whole plant's heterogeneous robots56. This is the solid domestic "quadruped truly in RCS dispatch" — but it uses SEER's own dispatcher, NOT VDA5050.
- SEER SRC controllers: SRC-1100/5000 provide motion control + dev kits for third-party quad/hexapod dogs (two on show at WRC2025)87. An "enabling-controller layer."
For Otsuka: "quadruped into heterogeneous dispatch" already has a domestic implementation (SEER M4) — far more realistic than writing a VDA5050 bridge from scratch; referenceable or even a partnership.
🔗 4. Inter-model cooperation (not "car-dog," but related)
| Cooperation | Scenario | Note | Source |
|---|---|---|---|
| DeepRobotics Jueying X30 quadruped + Lynx M20 wheeled-legged | State Grid Linyi 220 kV substation: "wheeled-legged quick scan + quadruped fine inspection" loop | both are DeepRobotics' own, not an external AMR | 11(self-media, use with care); Lynx official |
| GuoZi/Leaderobot wheeled/rail/quadruped/drone | substations, multi-type into one inspection host across provinces | real multi-type unified dispatch, but no public proof the quadruped is in-house | 10 |
⚠️ 5. Common misreads to clear up (NOT car-dog cooperation)
WebFetch-verified one by one — the following are easily spun as "car-dog cooperation" but aren't:
- "Dog returns to a fixed charging dock" ≠ carrier cooperation: Boston Dynamics Spot Dock12, Asylon DroneDog + DogHouse fixed charging pod13, ANYbotics ANYmal + dock (even a movable dock is "dog walks to dock," not "dock carries dog")14— all quadrupeds walk back to a fixed/dynamic dock on their own, no mobile carrier.
- Wheeled-legged single machine ≠ vehicle+dog: Unitree B2-W and DeepRobotics Lynx M20 have their own leg-end wheels — one machine, not "AMR carrying a dog."
- Sensor-extension partnership ≠ carrier: Trimble × Boston Dynamics straps a laser scanner on Spot for site surveying15; Spot self-walks + returns to a fixed dock, nothing to do with AMR mounting.
❌ 6. Negative matrix (to prevent overstatement; all curl-verified)
| Claim | Reality |
|---|---|
| Unitree B2/B2-W/GO2 × third-party AMR integration | many standalone dog inspection deployments20, but no "Unitree + named third-party AMR integration / AGV dispatch" case |
| Hikrobot/Geek+/YOUIBOT/Standard/Forwardx/Siasun × quadruped | all 6 are "AMR base + arm," zero quadruped integration (Siasun only has a non-commercial in-house quadruped prototype) |
| DeepRobotics "fused with third-party heavy AMR" | public sources can't name any specific AMR vendor/model — don't write it as fact in the plan |
| GuoZi "quadruped+AGV base+arm" 3-in-1 | no evidence; only a standalone quadruped inspection product page19 |
| robot dog × VDA5050 | China's VDA5050 deployments are all wheeled AMRs (e.g. Yiwu × Geek+/GuoZi)18, no robot dog; overseas openTCS/OTTO fleet managers are protocol-neutral/extensible but have no public quadruped-in-dispatch case1617 |
Trend evidence: Pudu D5 ships in both legged and wheeled (D5-W) forms21, showing "wheeled-legged" becoming the logistics-quadruped mainstream — but still "one machine," not "AMR carrying a dog."
🎯 Implications for Otsuka
- "Robot dog × third-party AMR physical integration" has almost no off-the-shelf product — beyond RIVR (wheeled-legged delivery) and UISEE (outdoor inspection), there's no commercial package, and neither is in-plant haulage. Doing it means self-integration, consistent with the GO2 starter conclusion.
- But "quadruped into heterogeneous dispatch" already has a domestic path: SEER M4 / SRC controllers already bring robot dogs into unified dispatch — a more realistic starting point than writing a VDA5050 bridge from scratch; referenceable or even partnerable.
- Don't expect VDA5050 to wire quadrupeds off-the-shelf (the standard targets 2D wheeled only) — cross "dog+AGV" dispatch means self-written middleware, or a domestic dispatcher like SEER that already supports heterogeneity.
- The differentiation lies in this gap: nobody has productized "robustly scheduling a robot dog into AMR logistics dispatch + physical mother-child docking." If the Otsuka plan builds this integration middleware + docking + dispatch orchestration, that's the "software × hardware" moat in the business plan.
⚠️ To verify / to add
- Want me to dig deeper into SEER: M4's quadruped interface detail, whether it can take Otsuka's existing AGVs, and the partnership/procurement path (the most likely domestic ready route).
- First-hand technical detail of the UISEE × State Grid "car-dog integrated": in-plant transferability, contacting the integrator.
- DeepRobotics "car-dog cooperation": want me to email DeepRobotics sales to pin down who that "third-party heavy AMR" actually is?
- The gov first-hand source (State Grid Hangzhou) returns curl 000 from geo-blocking — if you can re-check on a mainland network, I'll add the first-hand gov link.