ECSS Test Centres — Test Facility Risk Assessment (space-systems/ecss/q2007-tf-risk)
Use when the task is clause 5.6.5 of ECSS-Q-ST-20-07: a test facility
is to carry a campaign, its hazards have to be identified and assessed,
and the question is what risk is left after the mitigations that are
actually in place and who has to accept it.
Domain quick reference
- Identification comes before assessment. A facility owes a declared
set of hazard categories — pressure, energised systems, lifting,
hazardous fluids, thermal, noise and the rest it operates — and an
assessment that covers fewer of them is short, however careful the
hazards it did assess are.
- Risk is a pair, not a number. A severity index and a likelihood index
place the hazard in a band of the matrix; two hazards with the same
index product can land in different bands when the matrix is not
symmetric, and the band is what the decision uses.
- Only implemented mitigations may be credited. A planned interlock
reduces nothing on the day of the run, so the residual band is
recomputed from the implemented mitigations alone and the planned ones
are reported as work outstanding.
- A mitigation moves likelihood or severity by a declared number of
matrix steps, and it cannot move an index below the floor of its
scale. Crediting an unbounded reduction turns a severe hazard into an
acceptable one on paper.
- Above the acceptance line, a residual risk needs a named authority.
An unacceptable residual is not made acceptable by the naming, but an
undesirable one is carried only when somebody is recorded as carrying
it.
- A safety case has a shelf life. A facility reassessed before its last
modification describes a facility that no longer exists, so the
assessment date is checked against the last modification and against
the review interval.
Workflow
- Validate the risk policy first: the severity and likelihood scale
bounds, the band thresholds over the index product, the acceptance
line and the review interval. A band table whose thresholds are not
ascending is refused.
- Refuse an assessment with no hazards at all; that closes on hazards
not identified rather than on an empty clean sheet.
- Validate each hazard: a label, a category, a severity and a
likelihood index inside the scale, and a list of mitigations. Refuse
the same hazard label twice.
- Measure category coverage against the categories the facility
declares it operates, naming the uncovered ones.
- Compute the initial index and band for every hazard from the
unmitigated indices.
- Credit the implemented mitigations only, clamping each reduced index
at the floor of its scale, and recompute the residual index and band.
- Check the acceptance records: every residual above the acceptance
line needs a named authority, and a residual in the unacceptable band
cannot be accepted at all.
- Close on one verdict in order: hazards not identified, the safety
case stale against the last modification or the review interval, an
unacceptable residual risk, a residual above the line with no named
authority, category coverage short, risk reduction outstanding on
planned mitigations, or the residual risk accepted.
Pitfalls
- Crediting a planned mitigation. The barrier that will be fitted next
month does not lower the risk of a run next week, and a residual band
computed from planned work is a statement about the future.
- Reading the index product instead of the band. The band table is what
encodes the test centre's tolerance; two hazards at the same product
can sit either side of the acceptance line.
- Letting a mitigation drive an index below its scale. A three step
reduction on a likelihood of two cannot reach minus one, and an
unclamped credit makes a severe hazard vanish arithmetically.
- Accepting an unacceptable band because an authority signed. Naming an
authority records who carries an undesirable risk; it does not move
the band, and a signature on an unacceptable residual is a finding.
- Reporting coverage from the hazards assessed. Coverage is against the
categories the facility operates, so an uncovered category has to stay
in the denominator.
Behavior contract (gate 3)
The policy validation, hazard validation, band lookup, category
coverage, the implemented-only mitigation credit with its scale
clamping, the residual band recomputation, the acceptance authority
check, the safety case currency check and the verdict ordering are
exercised by the gate 3 contract test: scripts/test_q2007_tf_risk.py
against scripts/q2007_tf_risk_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q2007_tf_risk.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q2007-tf-risk3description: "Assess the hazards of a test facility and the residual risk left after mitigation, as ECSS-Q-ST-20-07 clause 5.6.5 asks. Use when a safety case for a facility has to be argued before a campaign rather than asserted: refuse an assessment covering fewer hazard categories than the facility owes, take a severity and a likelihood index per hazard into a risk band, credit only the mitigations actually implemented, recompute the residual band, and require a named acceptance authority for every residual risk above the acceptance line. Trigger: ecss, q-st-20-07-test-facility-clause-5-6-5, test-facility-hazard-category-coverage, test-facility-residual-risk-band, test-facility-risk-acceptance-authority, test-facility-mitigation-credit."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/q2007-tf-risk15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20-07-test-centre-scope, q2007-tf-risk, q-st-20-07-test-facility-clause-5-6-5, test-facility-hazard-category-coverage, test-facility-residual-risk-band, test-facility-risk-acceptance-authority, test-facility-mitigation-credit, test-facility-safety-case-currency]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Test Centres — Test Facility Risk Assessment (space-systems/ecss/q2007-tf-risk)2324Use when the task is clause 5.6.5 of ECSS-Q-ST-20-07: a test facility25is to carry a campaign, its hazards have to be identified and assessed,26and the question is what risk is left after the mitigations that are27actually in place and who has to accept it.2829## Domain quick reference3031- Identification comes before assessment. A facility owes a declared32 set of hazard categories — pressure, energised systems, lifting,33 hazardous fluids, thermal, noise and the rest it operates — and an34 assessment that covers fewer of them is short, however careful the35 hazards it did assess are.36- Risk is a pair, not a number. A severity index and a likelihood index37 place the hazard in a band of the matrix; two hazards with the same38 index product can land in different bands when the matrix is not39 symmetric, and the band is what the decision uses.40- Only implemented mitigations may be credited. A planned interlock41 reduces nothing on the day of the run, so the residual band is42 recomputed from the implemented mitigations alone and the planned ones43 are reported as work outstanding.44- A mitigation moves likelihood or severity by a declared number of45 matrix steps, and it cannot move an index below the floor of its46 scale. Crediting an unbounded reduction turns a severe hazard into an47 acceptable one on paper.48- Above the acceptance line, a residual risk needs a named authority.49 An unacceptable residual is not made acceptable by the naming, but an50 undesirable one is carried only when somebody is recorded as carrying51 it.52- A safety case has a shelf life. A facility reassessed before its last53 modification describes a facility that no longer exists, so the54 assessment date is checked against the last modification and against55 the review interval.5657## Workflow58591. Validate the risk policy first: the severity and likelihood scale60 bounds, the band thresholds over the index product, the acceptance61 line and the review interval. A band table whose thresholds are not62 ascending is refused.632. Refuse an assessment with no hazards at all; that closes on hazards64 not identified rather than on an empty clean sheet.653. Validate each hazard: a label, a category, a severity and a66 likelihood index inside the scale, and a list of mitigations. Refuse67 the same hazard label twice.684. Measure category coverage against the categories the facility69 declares it operates, naming the uncovered ones.705. Compute the initial index and band for every hazard from the71 unmitigated indices.726. Credit the implemented mitigations only, clamping each reduced index73 at the floor of its scale, and recompute the residual index and band.747. Check the acceptance records: every residual above the acceptance75 line needs a named authority, and a residual in the unacceptable band76 cannot be accepted at all.778. Close on one verdict in order: hazards not identified, the safety78 case stale against the last modification or the review interval, an79 unacceptable residual risk, a residual above the line with no named80 authority, category coverage short, risk reduction outstanding on81 planned mitigations, or the residual risk accepted.8283## Pitfalls8485- Crediting a planned mitigation. The barrier that will be fitted next86 month does not lower the risk of a run next week, and a residual band87 computed from planned work is a statement about the future.88- Reading the index product instead of the band. The band table is what89 encodes the test centre's tolerance; two hazards at the same product90 can sit either side of the acceptance line.91- Letting a mitigation drive an index below its scale. A three step92 reduction on a likelihood of two cannot reach minus one, and an93 unclamped credit makes a severe hazard vanish arithmetically.94- Accepting an unacceptable band because an authority signed. Naming an95 authority records who carries an undesirable risk; it does not move96 the band, and a signature on an unacceptable residual is a finding.97- Reporting coverage from the hazards assessed. Coverage is against the98 categories the facility operates, so an uncovered category has to stay99 in the denominator.100101## Behavior contract (gate 3)102103The policy validation, hazard validation, band lookup, category104coverage, the implemented-only mitigation credit with its scale105clamping, the residual band recomputation, the acceptance authority106check, the safety case currency check and the verdict ordering are107exercised by the gate 3 contract test: scripts/test_q2007_tf_risk.py108against scripts/q2007_tf_risk_logic.py (stdlib unittest, offline). Run:109python3 scripts/test_q2007_tf_risk.py110111## Compliance112113- ECSS standards are freely downloadable (ESA); cite the source and114 paraphrase per standards-map.yaml.115- compliance: STANDARDS-REF, gated: false.