Industrial Robot — ISO 10218-1:2025
This pattern is for robot manufacturers — organisations that build the industrial robot arm, its controller, and the firmware that ships with it. The conformance target is ISO 10218-1:2025 and the harmonised standards stack that supports presumption of conformity to EU MR 2023/1230. The integrator side (the cell-building side) follows the parallel pattern under ISO 10218-2:2025, which shares most of the workflow.Scenario
You manufacture an industrial robot arm. Customers will integrate it into their cells. Your obligations:- Produce a robot that satisfies ISO 10218-1:2025.
- Provide instructions for use that let an integrator build an ISO 10218-2:2025-conformant cell.
- Document risk-reduction measures, safety-rated software, safety functions, performance levels.
- Maintain a technical file that supports EU-type examination (Annex IX of EU MR 2023/1230).
- Re-conformance on standard amendments and on substantial modifications to the product.
Prerequisites
Project setup
1
Create the project
From the dashboard or
rbtk project create. One project per robot product family.2
Pin the standards stack
3
Link your repositories
Install the GitHub App and link the firmware, messages, and any subordinate repos.
4
Ingest your risk assessment
Export hazards to
roboticks/hazards.yaml. See ISO 12100.5
Declare your safety architecture
Write
roboticks/architecture.yaml per IEC 62061. Lists safety functions, subsystems, and their SIL CL or PL.Derivation
Author requirements covering, at minimum, every clause of ISO 10218-1:2025 that the risk assessment identifies as applicable. The platform’s LLM-assisted derivation (Team and Enterprise) suggests requirement text from clauses; you ratify. A typical industrial-robot project ends up with 150–400 requirements across:
Every requirement has
derives_from pointing at the exact clause and edition, asil_pl (or category), mitigates_hazards linking to the risk assessment, and acceptance listing the confirming tests.
Test patterns
The dominant patterns for an ISO 10218-1:2025 project:
See the SDK examples for code-level recipes.
Release
1
Cut a release for every shipped firmware version
rbtk release cut --tag v3.1.0 (or via dashboard).2
Verify
Every required test runs on the pinned commit set. The release auto-promotes to
verified on full pass. Gaps surface for triage.3
Generate the evidence pack
4
Mark shipped
On actual shipment to customers,
rbtk release ship v3.1.0. The 10-year retention clock starts.Handoff
Hand the pack to your notified body per the customer-handoff procedure. For ISO 10218-1:2025 specifically, expect the assessor to:- Sample-verify the hash chain (
rbtk evidence verify-chain). - Drill into the safety-rated software section — coverage thresholds, SARIF findings.
- Spot-check requirements derived from §5.4 (stop functions) — the most-scrutinised clause area.
- Request MCAP restores from Glacier for specific collaborative-operation scenarios (if PFL).
- Request a re-verification on a chosen subset of tests, to confirm reproducibility.
Maintenance
What this pattern does not cover
- Integrator-side (cell) conformity — see ISO 10218-2:2025; the pattern is mirror-image.
- Component supplier certification — your safety-rated drives, controllers, sensors come with their own certifications. Reference them in
architecture.yaml; do not re-certify in Roboticks. - Annex IV technical-file assembly beyond verification evidence — see EU MR 2023/1230 conformity for the full technical-file pattern.
Next steps
ISO 10218 standard page
The standard reference.
EU MR conformity pattern
Technical-file assembly around the evidence pack.
Cobot variant
If you are PFL.
Change-impact workflow
Per-PR triage.