ECSS Engineering Changes & Nonconformances (space-systems/ecss/e10-changes-nc)
Use when the task is controlling an engineering change or a nonconformance under ECSS-E-ST-10C clause 5.6.9: determine whether it affects the requirements or design baseline, route it to the right approval authority, and gate implementation on an approved disposition with the baseline updated, consistent with M-ST-40 and Q-ST-10-09.
Domain quick reference
- ECSS-E-ST-10C clause 5.6.9 requires engineering changes and nonconformances that affect requirements or design to be controlled before they are implemented: assess baseline impact, obtain an approved disposition, and update the baseline before proceeding.
- Two item types:
change(engineering change request) andnonconformance(departure from an approved requirement/design found in a product or process). - An item "requires a baseline change" when it affects requirements, design, or both. Baseline-impacting changes route to the CCB (M-ST-40 configuration change control); baseline-impacting nonconformances route to the NRB (Q-ST-10-09 disposition). Items that do not touch the baseline may be handled and closed locally.
- An item may only be implemented/closed as approved once its
disposition is
approvedand, for baseline-impacting items, the baseline has been updated to reflect it. - This leaf scopes the systems-engineering control point (impact
assessment, authority routing, implementation gate) only. The full
nonconformance lifecycle (detection, containment, major/minor
classification, root-cause analysis, CAPA, NCR database, trend
analysis) is owned by the Q-ST-10-09
q1009-*leaves; baseline establishment mechanics are owned by the siblinge10-config-baselinesleaf (10C clause 5.4.2.2).
Workflow
- Raise the item (
changeornonconformance) with a description and flag whether it affects requirements, design, or both. - Compute whether it requires a baseline change (affects requirements or design) and determine the approval authority: CCB for baseline-impacting changes, NRB for baseline-impacting nonconformances, local authority otherwise.
- Record the disposition (
approvedorrejected) from the authority, with a rationale. - If approved and the item requires a baseline change, update the baseline before closing it. If approved and no baseline change is required, or if rejected, close it directly.
- Check the register: no item may be treated as implementable until it is closed (and, if baseline-impacting and approved, the baseline update is recorded).
Pitfalls
- Implementing a baseline-impacting change or nonconformance before its disposition is approved and the baseline has been updated (the gate is skipped).
- Closing an approved baseline-impacting item without going through the baseline update step, leaving the configuration baseline out of sync with what was approved.
- Re-dispositioning an item that has already been dispositioned instead of raising a new item or reopening it explicitly.
- Confusing this leaf's control-point scope (impact assessment,
authority routing, implementation gate) with the full Q-ST-10-09
nonconformance lifecycle (detection, classification, CAPA,
closeout, database/trend analysis) — see the sibling
q1009-*leaves — or with baseline-establishment mechanics — see the siblinge10-config-baselinesleaf (10C clause 5.4.2.2).
Behavior contract (gate 3)
The impact-assessment, authority-routing, disposition, and implementation-gate logic is exercised by the gate 3 contract test: scripts/test_e10_changes_nc.py against scripts/e10_changes_nc_logic.py (stdlib unittest, offline). Run: python3 scripts/test_e10_changes_nc.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
