ECSS Element Pressure Tests — Proof, Cycling, Burst, Leak (space-systems/ecss/e1003-el-pressure)
Use when the task is running the element-level pressure test sequence required
by ECSS-E-ST-10C §6.5.3 -- proof, pressure cycling, design burst, and leak --
for a pressurized hardware item, verifying that each test result meets its
acceptance criterion before the element advances to integration.
Domain quick reference
- Proof test: Apply a proof pressure derived from the maximum expected
operating pressure (MEOP) multiplied by a proof factor (default 1.5×) and
hold it for the required duration. The item must sustain the proof pressure
without permanent deformation or detectable leakage.
- Pressure cycling test: Cycle the internal pressure between a lower bound
and an upper bound for at least the required number of cycles, simulating
the fatigue loads accumulated over the operational life. The item must remain
leak-free and dimensionally stable after the full cycle count.
- Design burst test: Apply the design burst pressure (MEOP × burst factor,
default 2.0×) to verify that the item retains structural integrity up to its
ultimate pressure limit. The item must not rupture at or below the design
burst pressure; rupture above it confirms the margin is genuine.
- Leak test: Measure the leak rate and compare it against the allowable
leak rate for the application (e.g. Pa·m³/s). The measured rate must not
exceed the allowable; a margin is computed as allowable minus measured.
- Each test type returns a
passed flag and a findings list; an empty
findings list means the criterion is met. The full sequence is summarised by
an overall_passed flag.
Workflow
- Confirm the MEOP of the element and select the proof factor and burst
factor from the applicable requirements document. Verify the allowable
leak rate is on record before starting.
- Proof test: compute the required proof pressure (
MEOP × proof_factor)
and verify that the test facility can reach and hold it. Apply the proof
pressure and maintain it for at least the required hold duration. Record
whether deformation or leakage was observed; either observation is a
finding.
- Pressure cycling test: set the cycling bounds (min pressure ≥ 0,
max pressure > min) and the required cycle count. Run the cycles and
record any leakage or deformation observed during or after. Confirm that
the completed cycle count meets or exceeds the requirement.
- Design burst test: compute the required burst pressure (
MEOP × burst_factor).
Apply pressure up to the design burst pressure and record whether rupture
occurred. A result is a finding if the applied pressure was below the
required burst pressure or if the item ruptured.
- Leak test: with the element pressurized, measure the leak rate using
the agreed test method. Compare against the allowable rate. Record the
margin; a negative margin is a finding.
- Aggregate all findings across the four tests. Issue the element for
integration only when every findings list is empty and
overall_passed
is true.
Pitfalls
- Applying the proof pressure and immediately releasing it without holding it
for the required duration -- a short hold does not adequately stress
manufacturing defects into detectable leakage or deformation and the test
criterion is not met.
- Treating a design burst test where the applied pressure was below the design
burst pressure as a pass because the item did not rupture -- the test is
only valid when the required pressure was actually reached; an under-pressure
run is inconclusive, not a pass.
- Running a leak test at ambient pressure rather than at the operational
pressure -- leakage at zero differential is always zero and gives no
information about the in-service condition.
- Omitting the pressure cycling test on the grounds that the proof test was
already run -- cycling accumulates fatigue in a way a single proof hold
cannot reveal; the two tests are not substitutes for each other.
- Setting the allowable leak rate to zero or leaving it unset and then
reading "no violation found" as compliance -- an unset allowable means the
system-level leakage budget was never allocated to this element, which is
itself a finding.
Behavior contract (gate 3)
The proof, cycling, burst, and leak evaluation logic is exercised by the
gate 3 contract test: scripts/test_e1003_el_pressure.py against
scripts/e1003_el_pressure_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1003_el_pressure.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1003-el-pressure3description: "Use when run element-level pressure tests for pressurized space hardware under ECSS-E-ST-10C §6.5.3: determine proof pressure from the maximum expected operating pressure and verify the hold duration, cycle pressure between bounds for the required number of fatigue cycles, apply design burst pressure to confirm ultimate structural integrity, and measure leakage against the allowable leak rate. Each test produces a pass/fail verdict with explicit findings. Trigger: ecss, e-st-10-system-scope, pressure-test, proof-pressure, burst-pressure, pressure-cycling, leak-test, meop."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/e1003-el-pressure15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, pressure-test, proof-pressure, burst-pressure, pressure-cycling, leak-test, meop]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Element Pressure Tests — Proof, Cycling, Burst, Leak (space-systems/ecss/e1003-el-pressure)2324Use when the task is running the element-level pressure test sequence required25by ECSS-E-ST-10C §6.5.3 -- proof, pressure cycling, design burst, and leak --26for a pressurized hardware item, verifying that each test result meets its27acceptance criterion before the element advances to integration.2829## Domain quick reference3031- **Proof test**: Apply a proof pressure derived from the maximum expected32 operating pressure (MEOP) multiplied by a proof factor (default 1.5×) and33 hold it for the required duration. The item must sustain the proof pressure34 without permanent deformation or detectable leakage.35- **Pressure cycling test**: Cycle the internal pressure between a lower bound36 and an upper bound for at least the required number of cycles, simulating37 the fatigue loads accumulated over the operational life. The item must remain38 leak-free and dimensionally stable after the full cycle count.39- **Design burst test**: Apply the design burst pressure (MEOP × burst factor,40 default 2.0×) to verify that the item retains structural integrity up to its41 ultimate pressure limit. The item must not rupture at or below the design42 burst pressure; rupture above it confirms the margin is genuine.43- **Leak test**: Measure the leak rate and compare it against the allowable44 leak rate for the application (e.g. Pa·m³/s). The measured rate must not45 exceed the allowable; a margin is computed as allowable minus measured.46- Each test type returns a `passed` flag and a `findings` list; an empty47 findings list means the criterion is met. The full sequence is summarised by48 an `overall_passed` flag.4950## Workflow51521. Confirm the MEOP of the element and select the proof factor and burst53 factor from the applicable requirements document. Verify the allowable54 leak rate is on record before starting.552. **Proof test**: compute the required proof pressure (`MEOP × proof_factor`)56 and verify that the test facility can reach and hold it. Apply the proof57 pressure and maintain it for at least the required hold duration. Record58 whether deformation or leakage was observed; either observation is a59 finding.603. **Pressure cycling test**: set the cycling bounds (min pressure ≥ 0,61 max pressure > min) and the required cycle count. Run the cycles and62 record any leakage or deformation observed during or after. Confirm that63 the completed cycle count meets or exceeds the requirement.644. **Design burst test**: compute the required burst pressure (`MEOP × burst_factor`).65 Apply pressure up to the design burst pressure and record whether rupture66 occurred. A result is a finding if the applied pressure was below the67 required burst pressure or if the item ruptured.685. **Leak test**: with the element pressurized, measure the leak rate using69 the agreed test method. Compare against the allowable rate. Record the70 margin; a negative margin is a finding.716. Aggregate all findings across the four tests. Issue the element for72 integration only when every findings list is empty and `overall_passed`73 is true.7475## Pitfalls7677- Applying the proof pressure and immediately releasing it without holding it78 for the required duration -- a short hold does not adequately stress79 manufacturing defects into detectable leakage or deformation and the test80 criterion is not met.81- Treating a design burst test where the applied pressure was below the design82 burst pressure as a pass because the item did not rupture -- the test is83 only valid when the required pressure was actually reached; an under-pressure84 run is inconclusive, not a pass.85- Running a leak test at ambient pressure rather than at the operational86 pressure -- leakage at zero differential is always zero and gives no87 information about the in-service condition.88- Omitting the pressure cycling test on the grounds that the proof test was89 already run -- cycling accumulates fatigue in a way a single proof hold90 cannot reveal; the two tests are not substitutes for each other.91- Setting the allowable leak rate to zero or leaving it unset and then92 reading "no violation found" as compliance -- an unset allowable means the93 system-level leakage budget was never allocated to this element, which is94 itself a finding.9596## Behavior contract (gate 3)9798The proof, cycling, burst, and leak evaluation logic is exercised by the99gate 3 contract test: scripts/test_e1003_el_pressure.py against100scripts/e1003_el_pressure_logic.py (stdlib unittest, offline). Run:101102 python3 scripts/test_e1003_el_pressure.py103104## Compliance105106- ECSS standards are freely downloadable (ESA); cite the source and107 paraphrase per standards-map.yaml.108- compliance: STANDARDS-REF, gated: false.