Repository navigation
Glossary
github-actions[bot] edited this page Oct 23, 2026
·
1 revision
The codes that appear in file names, commit messages, the records and the maps, decoded in one place.
Each work product is named WP, a letter for its area, and a number, for example WP-C-04 is the safety function
specification. The work product register lists every
one with its clauses, gate and status.
| Prefix | Area | Folder |
|---|---|---|
WP-M |
Management: strategy, plans, confirmation measures, regulatory strategy, impact analysis | 01-management/ |
WP-C |
Concept: machine limits, operating envelopes, risk assessment, safety functions and PLr, risk reduction, cybersecurity and ML concepts | 02-concept/ |
WP-S |
System: safety requirements, SRP/CS architecture, stopping and separation budget, I/O, cybersecurity architecture | 03-system/ |
WP-H |
Hardware: safety chain, electrical safety, failure analysis, PL calculation, component qualification, mechanical analysis | 04-hardware/ |
WP-W |
Software: the controller safety layer and the hardened host stack: requirements, architecture, verification, parameters, ML engineering | 05-software/ |
WP-V |
Validation: stopping and holding, collaborative operation, E-stop, fault injection, cybersecurity, test operations, field trials | 06-validation/ |
WP-P |
Supporting processes: configuration, change, problem resolution, documentation, review, tools, release, the process model |
07-supporting/, process/
|
WP-A |
Analyses: FMEA, FTA, CCF, STPA, independence of the chain | 08-analyses/ |
WP-O |
Operation: assembly, operation, information for use, field monitoring, incident response | 09-production-operation/ |
WP-K |
Safety case, technical documentation, cybersecurity case, assessments, release record, AI Act record | 10-safety-case/ |
WP-T |
Traceability data | trace/ |
| Code | Reads as | Where it lives |
|---|---|---|
HZ-M, HZ-E, HZ-T, HZ-P, HZ-C, HZ-D and the rest |
Hazard, by category (mechanical, electrical, thermal, collaborative contact, control and cyber, data), the identifiers of the concept-phase package kept | Risk assessment, WP-C-03 |
SF- |
Safety function of the control system, with its required Performance Level PLr; SF-32 is the hardwired emergency stop |
WP-C-04 |
DM-, IFU-
|
Design measure (inherently safe design or guarding) and information for use: the package's non-control "safety functions", reclassified; their SF numbers are reserved and never reused | WP-C-05, WP-O-03 |
SR- |
Safety requirement of the SRP/CS | WP-S-02 |
HWSR-, SWSR-
|
Hardware and software safety requirement | WP-H-01, WP-W-02 |
CSR-, TS-
|
Cybersecurity requirement, threat scenario | WP-C-08, WP-C-07 |
AIR-, ML-
|
Requirement on a learned component; a learned component | WP-C-09 |
FI-, TC-
|
Functional insufficiency, triggering condition | WP-C-10 |
PAR- |
Safety-related parameter: joint limits, torque and speed caps, watchdog timings | WP-W-09 |
AOU- |
Assumption of use: what the analysis assumes about the operator, the supply, the build, the bench; AOU-01 to AOU-08 are the package's assumptions in order |
Machine definition and safety case |
OE- |
Operating envelope: OE-1 supervised lab bench, OE-2 classroom, OE-3 industrial collaborative cell, OE-4 public demo |
WP-C-02 |
M- |
Operating mode: M-01 OFF, M-02 IDLE, M-03 TEACH, M-04 RUN, M-05 ESTOP |
WP-C-01 |
CFG- |
Configuration: CFG-001 the B601-DM v1.1 reference arm, CFG-002 the B601-RS variant, tracked and unverified |
case/configurations/ |
BL- |
Baseline: a named state of the record; BL-001 is the inherited state |
case/baselines/ |
DF- |
Defeater: known counter-evidence against a claim | Safety case, WP-K-01 |
GAP- |
A finding of the baseline gap assessment; never reused | Gap assessment |
OI- |
Open item of a work product, due at a gate | The last section of every work product |
IX-, FB-
|
Cross-domain interface, feedback route | Process model |
GOV-, CON-, DES-, DEV-, INT-, REL-, OPS-
|
Activities of the process model, by phase | Process maps |
CR-, FSA-, AUD-, CS-, ML-R, NB-
|
Confirmation reviews, functional safety assessments, audits, cybersecurity review and assessment, ML reviews, notified body | WP-M-06 |
DQ- |
Decision question for the project lead | Decision register |
T-, D-
|
Tailoring decision, strategic decision | WP-M-01 §5, §8 |
G0 to G6
|
Lifecycle gates | WP-M-00 §2 |
FM-, SYRS-, SRS-, HWRS-, TC-U/I/S-
|
Failure modes, requirements and test cases of the concept-phase package; cited as sources, not record identifiers | The reBot_DevArm_*.xlsx workbooks at the repository root |
| Term | Meaning |
|---|---|
| Performance Level (PL) | ISO 13849-1's measure of a safety function's ability to perform under foreseeable conditions, PL a (lowest) to PL e. The required PL, PLr, comes from the risk graph on the hazard; the achieved PL from the control system's category, MTTFD, DCavg and CCF. |
| Category | The designated architecture of a safety-related part: B, 1, 2, 3 or 4. Category 3 and 4 have two channels so that a single fault does not lose the function. |
| MTTFD, DCavg, CCF | Mean time to dangerous failure per channel; average diagnostic coverage; the common cause failure score. The three numbers the PL calculation needs, and the ones no actuator supplier has published. |
| SRP/CS | Safety-related part of a control system: everything from the button or the monitor through the logic to the contactor that implements a safety function. |
| Safety function | A function of the machine whose failure can immediately increase risk: emergency stop, safe stop on watchdog, joint torque and speed limiting, and so on. |
| Emergency stop, protective stop | A stop a person triggers (ISO 13850) versus a stop the control system triggers on a monitored condition: a lost heartbeat, a joint limit, a detected contact. |
| Stop category 0 / 1 | EN 60204-1: immediate removal of power (0; the arm's joints coast and the gripper may release) or a controlled stop followed by removal of power (1). |
| Safety-rated monitored stop | The collaborative mode in which the arm is held stopped by a monitored function while a person is in reach; motion resumes only when the person has left. |
| Hand guiding | The collaborative mode in which an operator moves the arm by hand (the arm's TEACH mode) under an enabling device and a safely limited speed. |
| Speed and separation monitoring (SSM) | The collaborative mode in which the arm slows or stops as a person approaches, keeping the separation distance of ISO 13855. |
| Power and force limiting (PFL) | The collaborative mode in which contact is permitted because the force and pressure the arm can exert stay below the body-region thresholds of ISO/TS 15066 Annex A. Not claimed in the first safety case (DQ-005). |
| Separation distance, minimum gap | How far a person must be from the arm during motion (ISO 13855, ISO 13857) and how small a joint gap must be so a finger cannot be crushed in it (ISO 13854). |
| SELV | Safety extra-low voltage: the 24 V motor supply, isolated from mains by the supply, on which the shock argument rests. |
| Three-step method | ISO 12100's order of risk reduction: inherently safe design first, then safeguarding, then information for use. |
| Technical documentation | The file Regulation (EU) 2023/1230 Annex IV requires a manufacturer to hold; WP-K-02 indexes it. |
| Security level target (SL-T) | IEC 62443's target per foundational requirement, SL 1 to SL 4. |
| Doer, checker, checker of last resort | The host stack proposes; the controller safety layer checks; the hardwired chain acts regardless of software. |
| Reference arm | The B601-DM v1.1 on a fixtured bench: the configuration the claims apply to. See Reference arm. |
| Hold point | A condition no test proceeds past: WP-V-07 before any powered test with a person in reach, and WP-V-03 before anyone is in reach during motion. |
| Term | Meaning |
|---|---|
| Claim | A statement the safety case argues is true. |
| Evidence item | A test result, analysis or review that supports a claim. Each carries a review state; it is accepted only after confirmation review. |
| Defeater | Known counter-evidence, or a reason the argument might not hold. Open defeaters are published, not hidden. GAP-01…GAP-36 are the first. |
| Confirmation review | An independent check that a work product does what its standard asks. Nothing leaves draft without a verification review; nothing is accepted without a confirmation measure. |
| Baseline | A frozen, named state of the whole record. |
| Independence I0 to I3 | Who may review: the author, another person, someone outside the team, someone outside the organisation. |
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