ECSS Test-Centre Quality and Safety — Planning (space-systems/ecss/q2007-planning)
Use when the task is clause 5.3.2 of ECSS-Q-ST-20-07: the test centre
plans its quality and safety — the objectives it sets, the resources it
puts behind them, and the management programmes that carry them — and
the question is whether that plan is one the centre can actually be held
to.
Domain quick reference
- An objective nobody can measure is an intention. A metric name, a
finite numeric target and a direction saying which way is better are
what make it checkable, and an objective missing any of the three is
counted as unmeasurable rather than as merely unmet. The distinction
matters because an unmet objective is a performance question and an
unmeasurable one is a planning defect.
- Attainment depends on the direction. Two escapes against a target of
five is attained; two on-time deliveries against a target of five is
not. The comparison lives in one place so the direction cannot be
applied inconsistently across a register.
- The equality case is the one that moves between hosts. An achieved
value computed as a ratio can land a few units in the last place off
its target, so the comparison carries a tolerance rather than a bare
inequality on either side.
- Resource coverage is taken against what the objectives require, and
over-planning one line does not pay for under-planning another. Each
line is capped at its own requirement before the ratio is formed,
otherwise a surplus of conductor hours hides a safety-officer gap.
- A programme is the vehicle an objective travels in. Only an approved
programme carries anything, and by default a programme with no
milestone is a title rather than a plan. An objective no programme
carries has nobody driving it.
- A programme pointing at an objective that does not exist is a wrong
entry, not a missing one. It is carried as an advisory so it cannot be
confused with the objectives that genuinely have no vehicle.
Workflow
- Validate the planning policy first: the resource coverage and
objective attainment the centre set itself, whether an owner is
demanded per objective, and whether a programme needs milestones to
count. An unrecognised key is refused rather than ignored.
- Validate the plan: finite numeric targets where present, recognised
directions and programme states, a positive requirement on every
resource line, non-negative planned quantities, and nothing
registered twice.
- Name the unmeasurable objectives, and stop there if any exist —
attainment across a register containing one of them is not a number
worth reporting.
- Name the objectives nobody owns, when the policy demands an owner.
- Take resource coverage with each line capped at its own requirement,
and name each under-planned line with the size of its shortfall.
- Take the objectives no approved programme carries, and separately the
programme references pointing at no objective.
- Take attainment across the measurable objectives in each objective's
own direction, comparing against the target with a tolerance.
- Close on one verdict in order: plan absent, objectives unmeasurable,
objectives unowned, resources under-planned, objectives uncovered, or
plan established. Carry the dangling references and the attainment
shortfall as advisories.
Pitfalls
- Reading an unmet objective as an unmeasurable one, or the reverse.
One needs management attention on the result, the other needs the
objective rewritten before any result means anything.
- Applying one direction to a whole register. Defect counts and
availability fractions sit in the same table and move opposite ways;
a single comparison across both silently inverts half the verdicts.
- Summing planned units against summed requirements without capping. A
surplus on the cheapest line pays for a gap on the one that actually
binds, and the coverage ratio reports a plan that cannot be run.
- Counting a draft or milestone-free programme as coverage. Nothing is
scheduled, so the objective has no vehicle whatever the register says.
- Treating a dangling programme reference as an uncovered objective.
The objective does not exist; what needs correcting is the programme,
and merging the two invents work nobody has to do.
Behavior contract (gate 3)
The policy validation, objective, resource and programme validation, the
measurability and ownership gaps, attainment in both directions
including the exact-equality case, resource coverage with per-line
capping, the programme coverage and dangling references, and the ordered
verdict are exercised by the gate 3 contract test:
scripts/test_q2007_planning.py against scripts/q2007_planning_logic.py
(stdlib unittest, offline). Run: python3 scripts/test_q2007_planning.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-planning3description: "Plan the quality and safety of a space test centre as ECSS-Q-ST-20-07 clause 5.3.2 asks, and say whether the plan in place can be run to. Use when a test centre's objectives, resourcing or management programmes are being set or audited: refuse a plan never established, name the objectives carrying no metric, no numeric target or no direction, name the ones nobody owns, take resource coverage against what the objectives require rather than against what the centre holds, find the objectives no approved programme carries, and read attainment in both directions with an exact equality settled by tolerance. Trigger: ecss, q-st-20-07-clause-5-3-2, test-centre-quality-objective-measurability, test-centre-objective-attainment-direction, test-centre-resource-planning-coverage, test-centre-management-programme-coverage."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-planning15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20-07-test-centre-quality-and-safety-scope, q2007-planning, q-st-20-07-clause-5-3-2, test-centre-quality-objective-measurability, test-centre-objective-attainment-direction, test-centre-resource-planning-coverage, test-centre-management-programme-coverage, test-centre-objective-ownership]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Test-Centre Quality and Safety — Planning (space-systems/ecss/q2007-planning)2324Use when the task is clause 5.3.2 of ECSS-Q-ST-20-07: the test centre25plans its quality and safety — the objectives it sets, the resources it26puts behind them, and the management programmes that carry them — and27the question is whether that plan is one the centre can actually be held28to.2930## Domain quick reference3132- An objective nobody can measure is an intention. A metric name, a33 finite numeric target and a direction saying which way is better are34 what make it checkable, and an objective missing any of the three is35 counted as unmeasurable rather than as merely unmet. The distinction36 matters because an unmet objective is a performance question and an37 unmeasurable one is a planning defect.38- Attainment depends on the direction. Two escapes against a target of39 five is attained; two on-time deliveries against a target of five is40 not. The comparison lives in one place so the direction cannot be41 applied inconsistently across a register.42- The equality case is the one that moves between hosts. An achieved43 value computed as a ratio can land a few units in the last place off44 its target, so the comparison carries a tolerance rather than a bare45 inequality on either side.46- Resource coverage is taken against what the objectives require, and47 over-planning one line does not pay for under-planning another. Each48 line is capped at its own requirement before the ratio is formed,49 otherwise a surplus of conductor hours hides a safety-officer gap.50- A programme is the vehicle an objective travels in. Only an approved51 programme carries anything, and by default a programme with no52 milestone is a title rather than a plan. An objective no programme53 carries has nobody driving it.54- A programme pointing at an objective that does not exist is a wrong55 entry, not a missing one. It is carried as an advisory so it cannot be56 confused with the objectives that genuinely have no vehicle.5758## Workflow59601. Validate the planning policy first: the resource coverage and61 objective attainment the centre set itself, whether an owner is62 demanded per objective, and whether a programme needs milestones to63 count. An unrecognised key is refused rather than ignored.642. Validate the plan: finite numeric targets where present, recognised65 directions and programme states, a positive requirement on every66 resource line, non-negative planned quantities, and nothing67 registered twice.683. Name the unmeasurable objectives, and stop there if any exist —69 attainment across a register containing one of them is not a number70 worth reporting.714. Name the objectives nobody owns, when the policy demands an owner.725. Take resource coverage with each line capped at its own requirement,73 and name each under-planned line with the size of its shortfall.746. Take the objectives no approved programme carries, and separately the75 programme references pointing at no objective.767. Take attainment across the measurable objectives in each objective's77 own direction, comparing against the target with a tolerance.788. Close on one verdict in order: plan absent, objectives unmeasurable,79 objectives unowned, resources under-planned, objectives uncovered, or80 plan established. Carry the dangling references and the attainment81 shortfall as advisories.8283## Pitfalls8485- Reading an unmet objective as an unmeasurable one, or the reverse.86 One needs management attention on the result, the other needs the87 objective rewritten before any result means anything.88- Applying one direction to a whole register. Defect counts and89 availability fractions sit in the same table and move opposite ways;90 a single comparison across both silently inverts half the verdicts.91- Summing planned units against summed requirements without capping. A92 surplus on the cheapest line pays for a gap on the one that actually93 binds, and the coverage ratio reports a plan that cannot be run.94- Counting a draft or milestone-free programme as coverage. Nothing is95 scheduled, so the objective has no vehicle whatever the register says.96- Treating a dangling programme reference as an uncovered objective.97 The objective does not exist; what needs correcting is the programme,98 and merging the two invents work nobody has to do.99100## Behavior contract (gate 3)101102The policy validation, objective, resource and programme validation, the103measurability and ownership gaps, attainment in both directions104including the exact-equality case, resource coverage with per-line105capping, the programme coverage and dangling references, and the ordered106verdict are exercised by the gate 3 contract test:107scripts/test_q2007_planning.py against scripts/q2007_planning_logic.py108(stdlib unittest, offline). Run: python3 scripts/test_q2007_planning.py109110## Compliance111112- ECSS standards are freely downloadable (ESA); cite the source and113 paraphrase per standards-map.yaml.114- compliance: STANDARDS-REF, gated: false.