Repository navigation
ISO 21448 performance limits
Standards tour · stop 14 of 20 · ← IEC 61025 · IEC 62443 →
Known or unknown, safe or unsafe. Exploring shrinks the unknown and unsafe area by turning it into known cases; measures and limits then shrink the known and unsafe area; what is left is argued as acceptable. Generated by tour_figures.py; it explains the standard's idea and claims nothing about the arm.
In one sentence. ISO 21448 deals with harm that happens when nothing has failed, because a function's design or sensing is not good enough for the situation; the record borrows its method, not its scope.
ISO 21448:2022, Road vehicles: safety of the intended functionality, known as SOTIF. It is an automotive standard. The record uses it as a method only, because no machinery standard covers hazards that arise without a fault: what a current-based torque estimate cannot sense, or what a learned policy does on a scene it was not trained on.
Every situation the function meets falls into one of four areas:
- Known and safe: handled by a measure or a limit.
- Known and unsafe: a triggering condition that leads to harm, identified but not yet handled.
- Unknown and unsafe: the situations nobody has thought of yet.
- Unknown and safe: harmless whether found or not.
Analysis, tests and field data move situations out of area 3 into area 2; measures, or limits on the operating envelope, move them from area 2 into area 1; what remains is argued as acceptable residual risk.
Two of the arm's safeguards are estimates, not sensors: contact is detected from motor currents, and learned policies propose motions from camera images. Both can fail to do their job with every part working.
| What the record takes | Where |
|---|---|
| The functional insufficiencies and triggering conditions of sensing and the learned policy | Insufficiency analysis, WP-C-10 |
| Unknown scenarios and field trials | WP-V-08 |
Every limit found is closed by a safety function or an operating-envelope limit, or stays open as a defeater in the safety case.
Any SOTIF conformance; the standard is written for road vehicles and is cited as informative.
- Functional insufficiency: a shortfall in the specification or the performance of a function.
- Triggering condition: a situation that, with an insufficiency, leads to a hazardous behaviour.
- Known and unknown scenarios: situations already identified, and those not yet.
No standard is held by the project, so every clause number on this page is to be checked against a licensed copy. The lead decided to buy them only when an assessor is engaged (DQ-011).
| Clause | What it covers |
|---|---|
| §6, §7 | Identifying hazards, functional insufficiencies and triggering conditions, as the record cites them |
Standards tour · stop 14 of 20 · ← IEC 61025 · IEC 62443 →
Mirrored from wiki/ on main at 832f97b, 2026-11-01. Pages are reviewed by pull request; the wiki is not edited in place. This wiki explains and links; safety claims and evidence live in the assurance record.
reBot-DevArm assurance wiki
- Home
- Processes
- Process maps
- Standards at a glance
- How we use each standard
- Standards tour
- Roadmap and status
- How the repository is organized
- How decisions are made
- Glossary
- Reading the safety case
- Hazard scenes
- For the assessor
- Reference arm
- Contributor guide
- Reporting a safety concern
- Session log
- FAQ
The standards tour
- Start here
- ISO 12100
- ISO 10218-1 and -2
- ISO 13849-1 and -2
- IEC 62061
- IEC 61508
- EN 60204-1
- ISO 13850
- ISO 13854
- ISO 13857
- ISO 13855
- ISO/TS 15066
- IEC 60812
- IEC 61025
- ISO 21448
- IEC 62443
- ISO/IEC TR 5469
- UL 4600
- Automotive SPICE
- Machinery Regulation
- AI Act
Repository