ECSS Structural Mechanical Systems — Acceptance Test Programme (space-systems/ecss/acceptance-test-programme)
Use when the task is planning and executing the acceptance proof and leak
test programme for flight hardware per ECSS-E-ST-32C clause 5.5 --
determining proof pressure requirements, verifying test execution
conditions, evaluating leak rates, and recording the overall programme
outcome.
Domain quick reference
- Clause 5.5 defines two mandatory test families for flight hardware
acceptance: proof tests (applied to pressurized assemblies to
demonstrate structural integrity at the maximum design pressure with
a prescribed proof factor) and leak tests (applied to sealed
assemblies to confirm that the actual leak rate does not exceed the
allowable limit derived from the mission requirement). Both families
must be completed and passed before a hardware item is accepted.
- The required proof pressure for a pressurized assembly is its maximum
design pressure (MDP) multiplied by the proof factor. The proof
factor at acceptance level is 1.0 for flight hardware (as distinct
from the higher qualification proof factor used during development
testing). The hardware must sustain the proof pressure for a minimum
hold duration without leakage, collapse, or permanent deformation
beyond the permitted limit.
- A leak test records the measured leak rate under the prescribed
differential pressure condition and compares it against the allowable
leak rate. An assembly with zero allowable leak rate on record cannot
be evaluated and the missing requirement is itself a finding. The
acceptance test programme as a whole is satisfied only when every
individual test item in both families has a recorded pass.
Workflow
- Inventory every pressurized and sealed assembly on the flight
hardware and assign each one to the appropriate test family: proof,
leak, or both. Reject an assembly with an unrecognized test type
before it enters the programme.
- For each assembly requiring a proof test, compute the required proof
pressure from the MDP and the applicable proof factor. Confirm the
applied test pressure meets or exceeds this value, and that the
measured hold duration meets the minimum dwell time specified in the
test procedure. Flag any shortfall as a proof-test violation.
- For each assembly requiring a leak test, compare the measured leak
rate against the allowable leak rate from the contamination and
sealing requirement. Flag an exceedance as a leak-test violation.
Flag a missing allowable limit as an unrecorded requirement.
- Aggregate the violation lists per assembly; an assembly is accepted
only when its list is empty. The full acceptance test programme
passes only when every assembly in the programme is accepted.
- Record the test outcome for each assembly and the overall programme
verdict in the test report. A programme with any open violation must
not be closed out until all findings are resolved and the relevant
tests are re-run to a clean outcome.
Pitfalls
- Applying the qualification proof factor at acceptance level -- clause
5.5 uses the acceptance proof factor (1.0 × MDP for typical
pressurized structures), and overloading flight hardware with a
higher qualification factor risks damage and is a test configuration
error.
- Treating a hold duration that is marginally short as acceptable
without re-test -- the minimum dwell time is a hard limit; a short
hold makes the test inconclusive regardless of the pressure level
reached.
- Accepting a sealed assembly with no allowable leak rate on record as
compliant because no exceedance was computed -- an unrecorded
allowable means the sealing requirement was never captured, which is
itself a finding.
- Closing out the programme before all assemblies have a recorded pass
-- the programme verdict is the logical AND of all individual test
results; a single open finding blocks the programme.
Behavior contract (gate 3)
The proof-pressure computation, proof-test condition check, leak-test
evaluation, and programme aggregation logic is exercised by the gate 3
contract test: scripts/test_acceptance_test_programme.py against
scripts/acceptance_test_programme_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_acceptance_test_programme.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: acceptance-test-programme3description: "Use when plan and execute acceptance proof and leak tests on flight hardware under ECSS-E-ST-32C clause 5.5: determine the required proof pressure for each pressurized assembly from its maximum design pressure and the applicable proof factor, confirm the applied test pressure meets or exceeds the requirement and that the hold duration satisfies the minimum dwell time, evaluate the measured leak rate against the allowable limit for each sealed assembly, and determine overall programme acceptance only when every test item passes. Trigger: ecss, e-st-32c, acceptance-test, proof-test, leak-test, flight-hardware, pressure-vessel, structural-acceptance."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/acceptance-test-programme15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-32c, acceptance-test, proof-test, leak-test, flight-hardware, pressure-vessel, structural-acceptance]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Structural Mechanical Systems — Acceptance Test Programme (space-systems/ecss/acceptance-test-programme)2324Use when the task is planning and executing the acceptance proof and leak25test programme for flight hardware per ECSS-E-ST-32C clause 5.5 --26determining proof pressure requirements, verifying test execution27conditions, evaluating leak rates, and recording the overall programme28outcome.2930## Domain quick reference3132- Clause 5.5 defines two mandatory test families for flight hardware33 acceptance: proof tests (applied to pressurized assemblies to34 demonstrate structural integrity at the maximum design pressure with35 a prescribed proof factor) and leak tests (applied to sealed36 assemblies to confirm that the actual leak rate does not exceed the37 allowable limit derived from the mission requirement). Both families38 must be completed and passed before a hardware item is accepted.39- The required proof pressure for a pressurized assembly is its maximum40 design pressure (MDP) multiplied by the proof factor. The proof41 factor at acceptance level is 1.0 for flight hardware (as distinct42 from the higher qualification proof factor used during development43 testing). The hardware must sustain the proof pressure for a minimum44 hold duration without leakage, collapse, or permanent deformation45 beyond the permitted limit.46- A leak test records the measured leak rate under the prescribed47 differential pressure condition and compares it against the allowable48 leak rate. An assembly with zero allowable leak rate on record cannot49 be evaluated and the missing requirement is itself a finding. The50 acceptance test programme as a whole is satisfied only when every51 individual test item in both families has a recorded pass.5253## Workflow54551. Inventory every pressurized and sealed assembly on the flight56 hardware and assign each one to the appropriate test family: proof,57 leak, or both. Reject an assembly with an unrecognized test type58 before it enters the programme.592. For each assembly requiring a proof test, compute the required proof60 pressure from the MDP and the applicable proof factor. Confirm the61 applied test pressure meets or exceeds this value, and that the62 measured hold duration meets the minimum dwell time specified in the63 test procedure. Flag any shortfall as a proof-test violation.643. For each assembly requiring a leak test, compare the measured leak65 rate against the allowable leak rate from the contamination and66 sealing requirement. Flag an exceedance as a leak-test violation.67 Flag a missing allowable limit as an unrecorded requirement.684. Aggregate the violation lists per assembly; an assembly is accepted69 only when its list is empty. The full acceptance test programme70 passes only when every assembly in the programme is accepted.715. Record the test outcome for each assembly and the overall programme72 verdict in the test report. A programme with any open violation must73 not be closed out until all findings are resolved and the relevant74 tests are re-run to a clean outcome.7576## Pitfalls7778- Applying the qualification proof factor at acceptance level -- clause79 5.5 uses the acceptance proof factor (1.0 × MDP for typical80 pressurized structures), and overloading flight hardware with a81 higher qualification factor risks damage and is a test configuration82 error.83- Treating a hold duration that is marginally short as acceptable84 without re-test -- the minimum dwell time is a hard limit; a short85 hold makes the test inconclusive regardless of the pressure level86 reached.87- Accepting a sealed assembly with no allowable leak rate on record as88 compliant because no exceedance was computed -- an unrecorded89 allowable means the sealing requirement was never captured, which is90 itself a finding.91- Closing out the programme before all assemblies have a recorded pass92 -- the programme verdict is the logical AND of all individual test93 results; a single open finding blocks the programme.9495## Behavior contract (gate 3)9697The proof-pressure computation, proof-test condition check, leak-test98evaluation, and programme aggregation logic is exercised by the gate 399contract test: scripts/test_acceptance_test_programme.py against100scripts/acceptance_test_programme_logic.py (stdlib unittest, offline).101Run:102python3 scripts/test_acceptance_test_programme.py103104## Compliance105106- ECSS standards are freely downloadable (ESA); cite the source and107 paraphrase per standards-map.yaml.108- compliance: STANDARDS-REF, gated: false.