ISO 8373:2021: Why a Robot's Classification Determines Its Certification Fate

A robot is defined by its mission, not its form. This founding principle of ISO 8373:2021 has concrete implications for every engineering team aiming to ship a certified system. It is the reality around which Koddex was designed.

In today's robotics landscape, teams deploy entire fleets across industrial, medical and consumer environments — contexts where regulatory compliance is not optional, but a market access condition. Yet most organizations treat certification as a final phase, an anxiety-laden closing audit prepared in a rush.

ISO 8373:2021 is not just another glossary to file away. It is the master key that determines which requirements apply to your system, from the very first specification line. Misclassifying your robot means risking the wrong safety reference framework — and a full restart six months before production.

1. The three robot families under ISO 8373:2021

The standard structures the robotics world into three functional categories. Each carries its own galaxy of safety standards, European directives and certification processes. Understanding these — often porous — boundaries is the absolute prerequisite to any serious engineering strategy.

Service Robotics

Operates autonomously to perform useful tasks for humans or other equipment, outside structured industrial environments. This category covers domestic uses (vacuum cleaners, autonomous mowers), professional uses (logistics AMRs, service robots in human contact) and exploration or intervention (drones, AUVs, ground inspection robots).

Applicable references: ISO 13482, ISO 3691-4, EU Machinery Directive.

Industrial Robotics

Reprogrammable manipulators for industrial use — fixed or mobile. The category includes multi-axis articulated arms, SCARA robots, Delta robots, and collaborative systems (cobots) that share workspace with human operators.

Applicable references: ISO 10218-1/2, ISO/TS 15066, ISO 13849, IEC 62061, IEC 61508.

Medical Robotics

Distinct electromedical equipment, subject to medical device regulation. Two main subfamilies: robot-assisted surgery and rehabilitation or physical assistance (therapeutic exoskeletons, motor rehabilitation robots).

Applicable references: IEC 60601-1, MDR 2017/745, ISO 14971, IEC 62304.

2. The certification map by family

Each classification opens a specific normative tree. Confusion between families — voluntary or by lack of rigor — is one of the most frequent causes of certification delays.

2026 watchpoint. The Machinery Regulation 2023/1230/EU enters into force on January 14, 2027. It explicitly integrates high-risk AI systems into machinery safety requirements, including autonomous robots. Teams starting today have a 12-month window to adapt their documentary architecture.

3. The systemic problem: certification thought of too late

Engineering teams arriving six months from production with an inconsistent file almost always share the same history. Safety requirements were managed in a Word document. Validation tests linger in unversioned Excel sheets. Design decisions are scattered across email threads, closed Jira tickets and meetings without minutes.

At audit time, traceability that no one maintained in real time must be reconstituted after the fact. This pattern has a name in audits: the design justification gap. Teams know what they built. They cannot demonstrate why they built it that way, nor how each design decision connects to a specific normative requirement.

"When the fleet goes from 1 to 10,000 deployed robots, certification not anticipated from the design stage can block the entire production launch. Documentary rigor is not a cost — it is what protects speed."

— Romain Moulin, Co-founder & CEO · Exotec — 12,000+ robots deployed worldwide

The direct consequence is systematic: several months of delay, unbudgeted costs, and in medical or aerospace sectors, market refusal.

4. The Koddex approach: certification as a byproduct of engineering

If every engineering decision is traced the moment it is made, certification is no longer a project — it is an extraction. Koddex has been structured around this conviction, with six core capabilities for robotics teams.

Visual Metamodeling

Each robotic subsystem (motorization group, navigation module, safety controller) is defined as a typed archetype with its own attributes. Product variants share the same source model. Zero duplication, guaranteed consistency at fleet scale, whether 100 or 12,000 deployed units.

Requirements → Tests Traceability

Each normative requirement — for example REQ: ISO 10218-1 §5.10 — is directly linked to the components it covers and to the associated validation tests. An auditor instantly accesses the complete chain of evidence without manual reconstruction. Traceability is not produced for the audit, it is maintained continuously.

Lock & Revision Management

Production baselines are locked as immutable snapshots. Koddex simultaneously manages the maintenance of a certified version, the development of an evolutive version, and the design of a next generation, without contamination risk between branches or accidental overwriting of a certified configuration.

Impact Analysis Graph

When a supplier modifies a component specification, Koddex instantly identifies all affected dependencies across the model: assemblies, firmware calibrations, functional safety requirements, and concerned product variants. The impact perimeter is known before the decision is made, not after.

Library of Certifiable Templates

Koddex ships with reusable templates covering requirement trees, ISO 12100 risk matrices (5×5 severity × probability), test plans and documentary structures for ISO 10218, ISO 3691-4, IEC 61508 SIL 2, and the Machinery Directive. Migration of existing data (BOMs, requirements, design history) is performed in days, supported by the Koddex team.

AI Agents via MCP

Koddex exposes an MCP (Model Context Protocol) protocol that allows AI agents to read, write and automate inside the engineering model. Assisted generation of compliance documentation, normative inconsistency detection, requirements coverage analysis — directly inside engineering workflows, not in a chat interface disconnected from the rest of the system.

5. The certification workflow on Koddex: from classification to audit

Step 1 — Classify the system per ISO 8373:2021 (Day 1)
Define in Koddex the robot type, the intended application and the operating environment. This classification determines the applicable normative references and loads the corresponding templates.

Step 2 — Build the system architecture with normative attributes (Sprints 1–2)
Model each subsystem with its technical attributes and inherited normative requirements. The Safety Controller SC-100, for example, carries the requirement REQ: IEC 61508 SIL 2 directly in the component, not in a separate document.

Step 3 — Manage risk analysis in real time (Continuous)
The ISO 12100 or ISO 14971 risk matrix is maintained in Koddex, linked to the affected components and subsystems. Each design change triggers an alert if functional safety requirements are potentially impacted.

Step 4 — Lock validation baselines (Milestones)
At each milestone (PDR, CDR, qualification, certification), an immutable baseline is created. The auditor accesses a frozen project snapshot at any time, without subsequent modifications disturbing the reading of the certified state.

Step 5 — Generate the technical file (Audit)
Since traceability is maintained continuously, extracting the technical file (requirements → design decisions → validation tests → results) is a few-clicks operation. Not several weeks of manual reconstitution.

6. The edge cases that trap teams

AMR in human coactivity zones

A mobile autonomous robot used in logistics is initially classified under ISO 3691-4. As soon as it operates in a zone shared with human operators within one meter, ISO/TS 15066 (cobotics) and ISO 13849 (SRP/CS, Performance Level) requirements add to the initial reference. This perimeter extension must be detected and documented immediately, at the precise location where the architectural decision was made — exactly the type of cascade the Koddex Impact Analysis Graph captures automatically.

Exoskeletons and assistance robots

Wearable physical assistance devices navigate the border between service robotics (ISO 13482) and medical devices (MDR, IEC 60601-1). The intended use — industrial or therapeutic — determines the dominant reference. In Koddex, this duality is managed by defining intended use as a top-level system attribute, linked to distinct normative branches in the model.

Systems embedding autonomous AI functions

With the European AI Act and Machinery Regulation 2023/1230/EU coming into force, robots integrating high-risk AI systems must demonstrate the traceability of their algorithmic decisions. Koddex develops technical documentation templates compliant with AI Act requirements for robotic systems — an advantage for teams that anticipate this transition from the design phase.

7. Why documentary rigor is a competitive advantage

Certification is not just a regulatory constraint. In today's robotics ecosystem, demonstrating certification mastery has become a top-tier commercial argument.

Public tenders and large industrial accounts. Tenders systematically require proof of ISO, CE or IEC compliance before qualification. A structured technical file, extractable in a few days rather than several weeks, measurably changes the commercial dynamic.

Fundraising and due diligence. Industrial investors and specialized hardware funds scrutinize the maturity of engineering processes. An architecture with full traceability signals a professional, scalable team, capable of managing growth without re-architecting its processes.

International expansion. Going from CE certification to FDA 21 CFR Part 11, or from European ISO 10218 to American ANSI/RIA R15.06 requirements, requires adapting templates — not rebuilding the whole reference framework. Koddex is designed for this geographical and normative extensibility.

Fleet maintenance and evolution. On tens of thousands of deployed units, every component change must go through a rigorous change control process. The traceability maintained in Koddex guarantees that certified configurations remain auditable throughout the product lifetime — including years after initial market launch.

Conclusion

ISO 8373:2021 is the keystone that determines the entire certification strategy of a robotics project. Correctly classifying your robot from the design stage — service, industrial or medical — conditions every functional safety requirement, every validation test and every piece of the file presented to the notified body or auditor.

Certification is not an end-of-project effort. It is a natural byproduct of well-tooled engineering, where every decision is traced the moment it is made.

Your engineering rigor is your competitive advantage. Build it on Koddex.