EN ISO 13482: Safety Standard for Autonomous Robots in Industrial Environments

Plant managers procuring patrol robots regularly encounter two standards in tender documents: EN ISO 10218 for industrial robots and EN ISO 13482 for service robots. Confusing the two is the most common cause of failed procurement. This text separates both standards cleanly, sets out the requirements for mobile service robots in outdoor use, and names the duties that arrive in January 2027 with the EU Machinery Regulation 2023/1230.

EN ISO 13482: Scope and Demarcation

EN ISO 13482 specifies safety requirements for three categories of robots: mobile service robots, physical assistant robots, and person carrier robots (ISO 13482:2014). Industrial robots with fixed mounting and safety fencing are explicitly outside the scope. EN ISO 10218 applies to those.

This demarcation is regularly confused in procurement procedures. Anyone tendering an autonomous patrol robot and demanding conformity to EN ISO 10218 is requiring the wrong standard. Patrol robots for perimeter use are mobile service robots without active personal contact. They fall under Section 5 of EN ISO 13482.

The standard was published in 2014 and harmonised in the DACH region as DIN EN ISO 13482. It supplements the EU Machinery Regulation 2023/1230 (EUR-Lex) but does not replace it. The regulation remains the higher-level legal document for CE marking. EN ISO 13482 is the technical means for the presumption of conformity.

Anyone applying industrial robot standards to patrol robots demands protective devices that are neither sensible nor feasible in outdoor use. The safety fence that defines EN ISO 10218 does not exist here.

Hazards the Standard Addresses

EN ISO 13482 lists the specific hazards of mobile service robots in Section 5. Collision with persons during autonomous navigation is addressed in Section 5.7. Detection range, reaction time, and safety distances are prescribed.

Section 5.8 addresses instability: ramps, sills, wet surfaces. For outdoor use this adds the issue of power supply at temperatures below -10 °C. Lithium-ion batteries lose up to 40 percent of capacity at -15 °C. Anyone relying on data sheet figures alone is planning for the failure.

Electromagnetic interference from industrial radio, crane systems, or welding robots are standard risks in plant environments. The standard refers to EMC testing per EN 61000-6-2 for industrial environments. Misinterpretation of sensor signals in fog, rain, and direct sunlight affects RGB cameras and LiDAR equally. The consequence: sensor redundancy is not a comfort feature, it is a standard requirement.

Cyber manipulation of the control system is named as a risk in EN ISO 13482, with reference to IEC 62443. For KRITIS operators this reference is binding, because the NIS-2 Directive obliges essential entities to secure cyber-physical systems as well (NIS-2).

Risk Assessment Per EN ISO 12100

EN ISO 13482 requires a risk assessment following the methodology of EN ISO 12100. This is not a formality. The documentation must cover all foreseeable misuses, such as an employee deliberately blocking the robot, or a forklift driver crossing the patrol path.

Residual risks must be communicated to the operator in writing. A manufacturer who supplies the risk assessment as an annex to the data sheet does not fulfil the standard. A project-specific assessment per site of use is required. A production hall with mixed traffic has different risks than a secured perimeter with fencing.

For safety-related controls the Performance Level per EN ISO 13849-1 must be defined. Person detection generally requires Performance Level d. Stability monitoring can be Performance Level c, provided the risk assessment supports this.

Quarero supplies the risk assessment as part of RaaS commissioning. It is not invoiced separately and not outsourced to subcontractors. Contract model details are in the Robotics-as-a-Service model.

Protective Functions: What Must Sit Inside the Robot

The standard requires a mechanically accessible emergency stop. At least one physical button must be present. A purely software-based emergency shutdown via app is not sufficient.

Speed limitation in personal zones is set at ≤ 0.3 m/s. This is the value treated in collision studies as the threshold for negligible injury energy. In an open perimeter the robot may move faster as soon as no persons are detected.

Redundant sensors for person detection are mandatory. The QR-2 uses thermal imaging plus RGB. In fog or darkness the thermal camera takes over, in direct sunlight the RGB sensor does. A single LiDAR without redundancy does not fulfil the standard for personal zones.

Safe Torque Off (STO) must trigger within the safety distance when an obstacle is detected. Acoustic and visual warning signals before motion start are prescribed. Logging of all safety-relevant events must remain available for at least 90 days. For KRITIS deployments, longer retention periods are advisable.

The technical implementation is documented in the Quarero QR-2 specification.

Relationship to the EU Machinery Regulation 2023/1230

The EU Machinery Regulation 2023/1230 enters into force as binding law in January 2027 and replaces Machinery Directive 2006/42/EC. Autonomous mobile robots are classified as high-risk machinery when they use safety-relevant AI. This applies to every patrol robot with learning-based obstacle detection.

CE marking for high-risk machinery requires a conformity assessment by a notified body. A manufacturer declaration alone is not sufficient. Anyone procuring robots in 2026 should secure contractually that the manufacturer carries the transition to the new regulation. An exit clause for standard changes belongs in the contract.

EN ISO 13482 remains an applicable means for the presumption of conformity once listed under the new regulation. The technical documentation must remain available for ten years. With a RaaS contract over five years this means: the provider is liable for document availability even after the contract ends.

The organisational duties that arise in parallel from NIS-2 are set out in NIS-2 board liability.

Operator Duties After Commissioning

Handover ends the manufacturer's duty and starts the operator's duty. Under ArbSchG §5 a risk assessment at the deployment site must be prepared that supplements the manufacturer documentation. Anyone deploying the robot in a warehouse and later moving it to the outdoor car park must adjust the assessment.

Instruction of the workforce is carried out at least once per year and must be documented. Contents: behaviour on encounter, emergency stop operation, reporting channels for incidents. A ten-minute introduction during onboarding is not sufficient.

Maintenance intervals must follow the manufacturer's specifications. Deviations must be justified and documented. Incidents with property damage or personal contact must be reported to the Berufsgenossenschaft. For KRITIS deployments there is an additional reporting duty under BSI-Gesetz §8b (BSI-KritisV).

For camera systems a data protection impact assessment per Art. 35 GDPR must be documented. This applies even when the cameras are not primarily intended for person capture but could capture persons. In practice: every RGB camera with an outdoor view.

Conformity at Quarero QR-2 and QR-3

Both Quarero models fulfil EN ISO 13482 for mobile service robots without active personal contact. Conformity is not model-based but project-based. A separate risk assessment is prepared per deployment site and attached to the declaration of conformity.

Performance Level d applies to person detection. Performance Level c applies to stability monitoring. These values are stored in the technical documentation and named explicitly in the declaration of conformity. Procurers who require this information in tender documents filter out providers without clean documentation reliably.

The QR-3 is additionally tested per IEC 62443-3-3 for KRITIS deployment. This testing addresses the cybersecurity requirement only hinted at in EN ISO 13482. For operators under BSI-KRITIS Regulation it is de facto mandatory. Details are in QR-3 for KRITIS deployment.

The declaration of conformity is part of the RaaS contract, not an additional document on request. This distinction matters: anyone who has to request the declaration only after contract signature has not secured it contractually.

Procurement Checklist for Plant Managers

Before contract signature, request the manufacturer's declaration of conformity. A marketing statement on standard conformity without a signed document is not robust. The Performance Levels of the individual safety functions must be confirmed in writing, not derived from data sheets.

Logfile access for own audits must be secured contractually. Anyone dependent on the manufacturer's logs in the event of an incident loses negotiating room with insurers and supervisory authorities. An API with documented endpoints is the minimum solution.

Liability arrangements for personal injury must be clarified between manufacturer, operator, and insurer. Usual allocations provide that the manufacturer is liable for design faults, the operator for deployment faults. The boundary between the two is defined in the contract, not in the BGB.

Software update duties must be defined for the remaining contract term. A robot whose safety software receives no more patches after three years drops out of conformity automatically. The exit clause for standard changes is the final point: if EN ISO 13482 or the Machinery Regulation changes, it must be defined who carries the adjustment.

Anyone reviewing the cost frame for a fully conformant robotics solution against traditional guard service will find the breakdown in the TCO comparison guard service. The practical deployment case is described in Perimeter protection in industrial parks.

EN ISO 13482 is not an obstacle, it is the basis for a robust procurement decision. Anyone citing the standard cleanly in tender documents filters non-conformant providers out automatically. To arrange a pilot meeting in which conformity documents can be reviewed before contract signature, please book a slot at Request pilot meeting.