ECSS Test Centre — Control of Nonconformances (space-systems/ecss/q2007-nc-control)
Use when the task is the nonconformance-control step of ECSS-Q-ST-20-07C
clause 5.8.2 — deciding what an anomaly discovered at the test centre makes
the centre owe: how fast it must be reported, who owns its disposition, and
how much of the run has to be done again.
Domain quick reference
- A test-centre anomaly has two distinguishable subjects and the control
path differs: the test article, and the test itself. A facility fault that
left the article untouched still invalidates the conditions and still
forces a retest; an article defect found during test is dispositioned
through the customer's nonconformance system whatever the facility did.
- Severity is derived, not declared. Personnel or facility safety, a level
taken past the article's stated limit, a violated specified requirement or
invalidated test conditions each make the anomaly major on their own. The
derivation matters because the deadline and the authority both hang off it.
- The reporting clock starts at detection, not at the end of the run or at
the shift handover. A major anomaly reaching the customer after the run is
finished has already cost the customer the decision it was owed.
- Disposition authority follows severity: a minor anomaly is dispositioned by
the centre's quality function, a major one by the customer's review board.
Use-as-is and repair leave the article different from its specification, so
on a major anomaly both need the customer's recorded agreement.
- Retest scope is a separate decision from disposition and is often forgotten.
A level past the article's limit puts the whole article's state in question
and forces the run again; invalidated conditions force the affected phases
again, and force the whole run only when every phase is affected.
- A record marked closed while a finding is still open is itself a finding.
Close-out of the campaign is a statement that no anomaly is unresolved, so
it is graded on the set, not on each record in isolation.
Workflow
- Validate the anomaly record: identifier, detection hour, reporting hour
and proposed disposition are all required; a report timed before its
detection is an input error.
- Categorize severity from the effect flags, deriving overstress from the
applied level against the article limit when both are given rather than
trusting a declared flag.
- Derive the reporting deadline and the disposition authority from that
severity, and grade the elapsed hours against the deadline with a named
tolerance at the boundary.
- Decide the retest scope: full for an overstressed article, full when every
phase was invalidated, partial for the named affected phases, none when
neither applies. Refuse to guess when conditions were invalidated but no
phase is named.
- Check the disposition against the permitted set and against the customer
agreement a major use-as-is or repair requires.
- Confirm an owed retest is either the disposition itself or recorded as
performed; an owed retest that is neither is a finding.
- Aggregate the campaign: count major, minor, open, late and retest-owed
records, and permit close-out only when the finding list is empty.
Pitfalls
- Trusting a declared overstress flag when the applied and limit levels are
both in the record. Derive it, and treat a level exactly on the limit as
within the limit rather than past it.
- Letting the reporting clock start at the end of the run. The deadline is
measured from detection, so an anomaly detected early in a long campaign
can be late before the run is over.
- Dispositioning a major anomaly use-as-is on the centre's own authority.
The centre can propose it; only the customer's review board can agree it.
- Closing a record because the disposition was agreed while the retest it
forced has not been performed. Disposition and retest scope are separate
decisions and both have to be discharged.
- Repeating only the phase where the anomaly was noticed when the article
itself was taken past a limit. The article's state, not the phase boundary,
is what governs the scope in that case.
- Widening a reporting deadline to make an exact-equality case pass. An
equality at the limit is a representation question, handled by the
tolerance inside the comparison; the deadline stays as specified.
Behavior contract (gate 3)
The severity derivation, deadline and authority mapping, timeliness grading,
retest-scope decision, disposition validation and campaign aggregation are
exercised by the gate 3 contract test:
scripts/test_q2007_nc_control.py against
scripts/q2007_nc_control_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q2007_nc_control.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-nc-control3description: "Manage a nonconformance raised at a space test centre under ECSS-Q-ST-20-07C clause 5.8.2, inside the ECSS-Q-ST-10-09 nonconformance system: categorize the anomaly major or minor from safety effect, exceeded article limit, violated requirement or invalidated conditions; derive its reporting deadline and disposition authority; decide whether the run owes a partial or a full retest; and test the proposed disposition against the customer agreement it needs. Use when a test-centre anomaly, an anomaly report log or a disposition proposal has to be adjudicated before campaign close-out. Trigger: ecss, q-st-20-07c, q-st-10-09, test-centre-nonconformance, test-anomaly-report, nonconformance-disposition-authority, test-retest-scope-decision, article-overstress-ratio, nonconformance-close-out."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-nc-control15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20-test-centre-scope, q2007-nc-control, test-centre-nonconformance, test-anomaly-report, nonconformance-disposition-authority, test-retest-scope-decision, nonconformance-close-out]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Test Centre — Control of Nonconformances (space-systems/ecss/q2007-nc-control)2324Use when the task is the nonconformance-control step of ECSS-Q-ST-20-07C25clause 5.8.2 — deciding what an anomaly discovered at the test centre makes26the centre owe: how fast it must be reported, who owns its disposition, and27how much of the run has to be done again.2829## Domain quick reference3031- A test-centre anomaly has two distinguishable subjects and the control32 path differs: the test article, and the test itself. A facility fault that33 left the article untouched still invalidates the conditions and still34 forces a retest; an article defect found during test is dispositioned35 through the customer's nonconformance system whatever the facility did.36- Severity is derived, not declared. Personnel or facility safety, a level37 taken past the article's stated limit, a violated specified requirement or38 invalidated test conditions each make the anomaly major on their own. The39 derivation matters because the deadline and the authority both hang off it.40- The reporting clock starts at detection, not at the end of the run or at41 the shift handover. A major anomaly reaching the customer after the run is42 finished has already cost the customer the decision it was owed.43- Disposition authority follows severity: a minor anomaly is dispositioned by44 the centre's quality function, a major one by the customer's review board.45 Use-as-is and repair leave the article different from its specification, so46 on a major anomaly both need the customer's recorded agreement.47- Retest scope is a separate decision from disposition and is often forgotten.48 A level past the article's limit puts the whole article's state in question49 and forces the run again; invalidated conditions force the affected phases50 again, and force the whole run only when every phase is affected.51- A record marked closed while a finding is still open is itself a finding.52 Close-out of the campaign is a statement that no anomaly is unresolved, so53 it is graded on the set, not on each record in isolation.5455## Workflow56571. Validate the anomaly record: identifier, detection hour, reporting hour58 and proposed disposition are all required; a report timed before its59 detection is an input error.602. Categorize severity from the effect flags, deriving overstress from the61 applied level against the article limit when both are given rather than62 trusting a declared flag.633. Derive the reporting deadline and the disposition authority from that64 severity, and grade the elapsed hours against the deadline with a named65 tolerance at the boundary.664. Decide the retest scope: full for an overstressed article, full when every67 phase was invalidated, partial for the named affected phases, none when68 neither applies. Refuse to guess when conditions were invalidated but no69 phase is named.705. Check the disposition against the permitted set and against the customer71 agreement a major use-as-is or repair requires.726. Confirm an owed retest is either the disposition itself or recorded as73 performed; an owed retest that is neither is a finding.747. Aggregate the campaign: count major, minor, open, late and retest-owed75 records, and permit close-out only when the finding list is empty.7677## Pitfalls7879- Trusting a declared overstress flag when the applied and limit levels are80 both in the record. Derive it, and treat a level exactly on the limit as81 within the limit rather than past it.82- Letting the reporting clock start at the end of the run. The deadline is83 measured from detection, so an anomaly detected early in a long campaign84 can be late before the run is over.85- Dispositioning a major anomaly use-as-is on the centre's own authority.86 The centre can propose it; only the customer's review board can agree it.87- Closing a record because the disposition was agreed while the retest it88 forced has not been performed. Disposition and retest scope are separate89 decisions and both have to be discharged.90- Repeating only the phase where the anomaly was noticed when the article91 itself was taken past a limit. The article's state, not the phase boundary,92 is what governs the scope in that case.93- Widening a reporting deadline to make an exact-equality case pass. An94 equality at the limit is a representation question, handled by the95 tolerance inside the comparison; the deadline stays as specified.9697## Behavior contract (gate 3)9899The severity derivation, deadline and authority mapping, timeliness grading,100retest-scope decision, disposition validation and campaign aggregation are101exercised by the gate 3 contract test:102scripts/test_q2007_nc_control.py against103scripts/q2007_nc_control_logic.py (stdlib unittest, offline). Run:104python3 scripts/test_q2007_nc_control.py105106## Compliance107108- ECSS standards are freely downloadable (ESA); cite the source and109 paraphrase per standards-map.yaml.110- compliance: STANDARDS-REF, gated: false.