Hai Wiki
home / knowledge / 08-safety.md

Layer 8 — Safety engineering and compliance

Do not treat this as a footnote. Two of Hai's engineering job descriptions name safety explicitly, and the Netherlands R&D role demands CE harmonised standards knowledge as a headline requirement. Safety is where software intuitions most often mislead, because it obeys different rules from application software: it is certified, it is hard-wired, and it cannot be iterated on in production.


On-robot safety systems

What it is. The protective functions built into each robot.

Why it matters here. These are the last line of defence, and their behaviour constrains throughput — every protective stop costs cycle time.

Fundamentals.

  • Layered defence: detect (sensors) → warn (audio/visual) → slowstopfail safe. Each layer has a different response time and a different cost to throughput.
  • Emergency stop is a category of its own. An e-stop is a hard-wired, safety-rated circuit that must work when the software has crashed. It is not an application feature.
  • Energy containment matters in vertical systems: a robot holding a 30 kg tote 12 m up stores real potential energy. Anti-fall mechanisms are the mitigation, and they must be passive — engaging on power loss, not on command.
  • Fail-safe vs. fail-operational. Warehouse robots are fail-safe: on fault they stop. Safe stopping is straightforward when nothing is overhead — which is exactly why anti-fall gets separate treatment.

How Hai applies it.

"The HaiPick system has several safety functions, including obstacle detection, anti-collision features, audio-visual and voice alerts, an emergency stop button, lifting anti-falling mechanisms, and motor protection." — /robots/haipick-a3

"Obstacle detection, active obstacle avoidance, anti-collision alarm, and emergency stop" — /robots/haipick-a42

"Audible and visual alarms and voice alerts for real-time robot status." — /robots/fast-transit-amr-k50

Six named functions, and note that lifting anti-falling and motor protection are called out separately from collision safety — evidence they take the vertical-energy problem seriously.

Tradeoffs and pitfalls. Over-sensitive protective fields produce nuisance stops that erode real throughput below simulated throughput. This is a commissioning tuning problem with a genuine safety floor beneath it.

Key terms. e-stop · protective stop · anti-fall · fail-safe · layered defence · nuisance stop · safety-rated circuit.


Human-robot shared-zone safety

What it is. Keeping people safe in a space where robots move — including during maintenance, when someone must physically enter the automation zone.

Why it matters here. This decides the layout. Fenced zones, door positions and maintenance access are floor-plan decisions made early and expensively changed later. It also decides whether maintenance requires shutting the system down — which is an availability question, and therefore an architecture question.

Fundamentals.

  • Three broad strategies, in ascending sophistication:
    1. Separation — fence the robots away from people entirely. Simple, certain, costs floor space and makes maintenance disruptive.
    2. Interlocked access — guard doors that stop the zone when opened. Standard practice; the interlock must be in the control model, not an alarm.
    3. Detection and speed adaptation — sense people and slow or stop only what is near them. Keeps the rest of the system running.
  • The relevant standards vocabulary: ISO 3691-4 (driverless industrial trucks), ISO 10218 / ISO TS 15066 (industrial and collaborative robots), ISO 13849 (performance levels for safety control systems), and the Machinery Directive behind CE marking. (General knowledge — Hai names none of these specifically.)
  • Speed and separation monitoring is the formal name for the "slow down when a person is near" approach.
  • Maintenance is the hard case: someone must enter the zone while the business wants the rest running. Zone-level rather than system-level shutdown is the design answer.

How Hai applies it.

"Smart safety vests (HaiVest) detect personnel and adjust robot speed or stop robots automatically, allowing safe maintenance without downtime." — /solutions/haipick-system-3

"Standard safety fences around automation zones." — /solutions/haipick-system-3

"Workstation protections like safety doors placed in the workstations to prevent arm injuries." — /solutions/haipick-system-3

"Safety Protections for Human-robot Cooperation" — /products

HaiVest is the interesting one. A wearable that makes the person detectable, rather than relying on the robot to recognise a human, is a pragmatic inversion — detecting a beacon is far more reliable than detecting a person, and it directly buys maintenance-without-downtime. It is a genuine engineering choice with a clear rationale, and it sits well past the front page of their material.

Tradeoffs and pitfalls.

  • A wearable only protects people who wear it. The design assumes a controlled workforce with enforced procedure — fine for maintenance staff, weaker for visitors and contractors.
  • Fenced zones consume floor area and complicate emergency egress routes.

Key terms. ISO 3691-4 · ISO 13849 · performance level · Machinery Directive · guard door interlock · speed and separation monitoring · zone shutdown · HaiVest.


CE, NRTL and ISO certification

What it is. Third-party attestation that products meet regional safety and quality standards.

Why it matters here. Certification is a market-access gate, not a quality badge. Uncertified equipment cannot legally be placed into service in the EU. For a solutions architect this shows up as schedule risk and as a constraint on what can be customised.

Fundamentals.

  • CE marking is the manufacturer's declaration of conformity with applicable EU directives (Machinery Directive foremost), demonstrated against harmonised standards. Self-declared for most machinery, but the technical file must exist and stand up.
  • NRTL (Nationally Recognized Testing Laboratory — UL, ETL, CSA) is the North American equivalent, and unlike CE it requires third-party testing. This is why CE+NRTL is stated as a pair: it means the product can be sold on both sides of the Atlantic.
  • ISO 9001 certifies the quality management system — how the company controls its processes. It says nothing about product safety, and conflating the two is a common error.
  • The customisation trap. Modifying a certified machine can invalidate its certification. Every "can you just change…" request has a compliance cost, and knowing that is a mark of industrial experience.

How Hai applies it.

"Product Safety: CE+NRTL certified." — /robots/haipick-a3

"CE/NRTL certified." — /robots/fast-transit-amr-k50

"Safety CE and NRTL certified." — /solutions/system-features

"Hai Robotics is ISO 9001 certified" — /company

"Excellent knowledge regarding CE safety standards and their implementation in the material handling industry." — /join-us/recruitment/senior-system-designer-workstations

"Secure Safety (CE Harmonized Standards) and Ergonomics are part of the System Design." — /join-us/recruitment/senior-system-designer-workstations

That last quote is the important one: Hai treats CE harmonised standards as an input to system design, not a box ticked at the end. Compliance and ergonomics belong at the front of a design rather than in a downstream review — which is how Hai describe their own process.

Tradeoffs and pitfalls.

  • Regional variation is real: one robot page notes the A3 models are not available in Japan. Certification and market availability are not global.
  • Certification timelines are long. A customisation requested late in a project can push a go-live by months.

Key terms. CE marking · Machinery Directive · harmonised standard · declaration of conformity · technical file · NRTL (UL/ETL/CSA) · ISO 9001 · market access.