Hai Robotics technology notes
A layered technical reference on Hai Robotics' ASRS platform, built from their
public material. Source corpus: 147 pages of hairobotics.com (data/pages.jsonl),
technology map in data/technologies.json.
The one rule these notes follow
Two kinds of statement live in here, and they are never blended:
- "How Hai applies it" sections contain only claims that appear verbatim on a
Hai Robotics page, each with its source URL. Every quote in these notes is
machine-checked against the corpus by
scraper/verify_knowledge.py. - Everything else is general domain knowledge — the fundamentals needed in order to reason about their design. It is not attributable to Hai. Nothing here licenses a claim like "Hai uses contract-net task allocation"; they have never said that.
Seven things a solutions architect would normally want to know are not published
anywhere on the site — wire protocols, consistency model, algorithm families,
deadlock handling, deployment stack, sizing methodology, and the term "digital
twin". They are listed in technologies.json under inferred; each is an open
question rather than a documented answer.
Template
Each technology section carries the same six headings:
| Heading | Contains |
|---|---|
| What it is | Plain definition, provider-neutral |
| Why it matters here | Why it exists in a warehouse robotics system |
| Fundamentals | Concepts, math, algorithm families — general knowledge |
| How Hai applies it | Cited claims only, with URLs |
| Tradeoffs and pitfalls | Where designs go wrong |
| Key terms | Vocabulary to use fluently |
Layers
| # | File | Technologies | Weight |
|---|---|---|---|
| 1 | platform-architecture | WES, ESS, Algorithm Platform, Data Platform, Simulation Platform, SOA | core |
| 2 | algorithms | order allocation, task allocation, path planning, charging, order shaping, slotting | core |
| 3 | integration | ERP/WMS/MES, RCS↔WCS split, equipment/PLC, mixed fleet | core |
| 4 | non-functional | availability, request throughput, fleet scale, comms security | core |
| 5 | navigation | DM code + inertial + SLAM, LiDAR, 3D vision, calibration, mechanical constraint | supporting |
| 6 | handling | ACR variants, multi-tote, storage depth, spacing, envelope, agnosticism | core |
| 7 | energy | battery chemistry, autonomous charging | supporting |
| 8 | safety | on-robot safety, human-robot zones, CE/NRTL/ISO | core |
| 9 | solution-design | layout & material flow, deployment sizing, GTP workstations, simulation verification | core |
The 60-second version
Hai Robotics sells ACR (Automated Case-handling Robot) goods-to-person systems.
Robots climb standard racking, pull totes or cartons, carry up to 9 at once, and
deliver them to workstations where a human picks without walking. HaiQ is the
software: WES (orders and inventory, talks to the customer's ERP/WMS) → ESS
(fleet and equipment scheduling, also called RCS in at least one deployment) →
robots, with an Algorithm Platform for the optimisation decisions, a Data Platform for telemetry, and a Simulation Platform that validates a design 1:1
before anyone commits.
The architectural crux of the role — and the thing to be able to draw on a whiteboard — is where Hai's stack stops and the customer's begins. See integration.