ECSS Equipment Thermal Tests (space-systems/ecss/e1003-eq-thermal)
Use when the task is running equipment-level thermal testing under
ECSS-E-ST-10-03C clause 5.5.4: choosing between thermal vacuum and
thermal test at mission pressure, executing the qualification/
acceptance/protoflight thermal cycle plan, and verifying the test is
actually complete.
Domain quick reference
- ECSS-E-ST-10-03C clause 5.5.4 covers the two equipment-level thermal
test types: thermal vacuum (the unit is exposed to vacuum in its
operational environment) and thermal test at mission pressure (the
unit operates sealed or pressurized and is not vacuum-exposed).
- The temperature levels and the cycle-count/duration baselines for
each test campaign (qualification, acceptance, protoflight) are set
by the sibling baseline leaves (e1003-eq-qual Table 5-1/5-2,
e1003-eq-acceptance Table 5-3/5-4, e1003-eq-protoflight Table
5-5/5-6); this leaf consumes those levels and carries the per-test
rules: cycling execution, plateau stabilization tolerance, and
functional/performance success criteria.
- A thermal cycle has a cold plateau and a hot plateau. A plateau is
stable only once the temperature holds inside tolerance of its
target for the whole commanded dwell window, not merely at the
instant it first touches the target.
- Functional/performance verification is mandatory at the temperature
extremes of the first and last cycle at minimum, in addition to any
ambient checks before and after the test; a plateau without the
required functional/performance result cannot be certified even if
it stabilized thermally.
Workflow
- Determine whether the unit is vacuum-exposed in its operational
environment; select thermal_vacuum if so, otherwise
thermal_at_mission_pressure.
- Pull the hot/cold temperature targets, tolerance, dwell duration,
and required cycle count for the applicable campaign
(qualification/acceptance/protoflight) from the matching sibling
baseline leaf.
- Build the cycle plan from those levels: the required number of
cold/hot plateau pairs, each held for the commanded dwell.
- Record temperature readings through each plateau; a plateau counts
as stable only when a contiguous run covering the full dwell window
stays within tolerance of the target.
- At the first and last cycle's plateaus (minimum), execute and
record the functional/performance test; treat a required plateau
with no functional result as unresolved regardless of its thermal
stabilization.
- Declare the thermal test complete only when: the executed test type
matches the unit's vacuum exposure, the executed cycle count meets
the plan's required count, every plateau stabilized, and every
required functional/performance check passed.
Pitfalls
- Running a thermal test at mission pressure on a unit that is
actually vacuum-exposed in operation, or vice versa.
- Treating the first instant the target temperature is touched as the
plateau being achieved, instead of requiring stability through the
whole dwell window.
- Skipping the functional/performance test at the first or last
cycle's extremes and still certifying the cycle or the test.
- Declaring the test complete with fewer cycles than the campaign's
baseline plan requires.
Behavior contract (gate 3)
The test-type selection, cycle-plan construction, plateau-stabilization,
and completion logic is exercised by the gate 3 contract test:
scripts/test_e1003_eq_thermal.py against
scripts/e1003_eq_thermal_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1003_eq_thermal.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-eq-thermal3description: "Use when running equipment-level thermal tests under ECSS-E-ST-10-03C clause 5.5.4: select thermal vacuum vs thermal test at mission pressure for a unit based on its vacuum exposure, execute the qualification/acceptance/protoflight thermal cycle plan (cold/hot plateaus, dwell stabilization, functional/performance checks at the extremes), and verify the test as complete only when every required cycle stabilizes and passes. Trigger: thermal vacuum, TVAC, thermal cycling, thermal test at mission pressure, equipment thermal test, dwell stabilization, hot plateau, cold plateau, e-st-10-03, ecss."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-eq-thermal15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-03c, thermal-vacuum, thermal-cycling, equipment-test, tvac]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Equipment Thermal Tests (space-systems/ecss/e1003-eq-thermal)2324Use when the task is running equipment-level thermal testing under25ECSS-E-ST-10-03C clause 5.5.4: choosing between thermal vacuum and26thermal test at mission pressure, executing the qualification/27acceptance/protoflight thermal cycle plan, and verifying the test is28actually complete.2930## Domain quick reference3132- ECSS-E-ST-10-03C clause 5.5.4 covers the two equipment-level thermal33 test types: thermal vacuum (the unit is exposed to vacuum in its34 operational environment) and thermal test at mission pressure (the35 unit operates sealed or pressurized and is not vacuum-exposed).36- The temperature levels and the cycle-count/duration baselines for37 each test campaign (qualification, acceptance, protoflight) are set38 by the sibling baseline leaves (e1003-eq-qual Table 5-1/5-2,39 e1003-eq-acceptance Table 5-3/5-4, e1003-eq-protoflight Table40 5-5/5-6); this leaf consumes those levels and carries the per-test41 rules: cycling execution, plateau stabilization tolerance, and42 functional/performance success criteria.43- A thermal cycle has a cold plateau and a hot plateau. A plateau is44 stable only once the temperature holds inside tolerance of its45 target for the whole commanded dwell window, not merely at the46 instant it first touches the target.47- Functional/performance verification is mandatory at the temperature48 extremes of the first and last cycle at minimum, in addition to any49 ambient checks before and after the test; a plateau without the50 required functional/performance result cannot be certified even if51 it stabilized thermally.5253## Workflow54551. Determine whether the unit is vacuum-exposed in its operational56 environment; select thermal_vacuum if so, otherwise57 thermal_at_mission_pressure.582. Pull the hot/cold temperature targets, tolerance, dwell duration,59 and required cycle count for the applicable campaign60 (qualification/acceptance/protoflight) from the matching sibling61 baseline leaf.623. Build the cycle plan from those levels: the required number of63 cold/hot plateau pairs, each held for the commanded dwell.644. Record temperature readings through each plateau; a plateau counts65 as stable only when a contiguous run covering the full dwell window66 stays within tolerance of the target.675. At the first and last cycle's plateaus (minimum), execute and68 record the functional/performance test; treat a required plateau69 with no functional result as unresolved regardless of its thermal70 stabilization.716. Declare the thermal test complete only when: the executed test type72 matches the unit's vacuum exposure, the executed cycle count meets73 the plan's required count, every plateau stabilized, and every74 required functional/performance check passed.7576## Pitfalls7778- Running a thermal test at mission pressure on a unit that is79 actually vacuum-exposed in operation, or vice versa.80- Treating the first instant the target temperature is touched as the81 plateau being achieved, instead of requiring stability through the82 whole dwell window.83- Skipping the functional/performance test at the first or last84 cycle's extremes and still certifying the cycle or the test.85- Declaring the test complete with fewer cycles than the campaign's86 baseline plan requires.8788## Behavior contract (gate 3)8990The test-type selection, cycle-plan construction, plateau-stabilization,91and completion logic is exercised by the gate 3 contract test:92scripts/test_e1003_eq_thermal.py against93scripts/e1003_eq_thermal_logic.py (stdlib unittest, offline). Run:94python3 scripts/test_e1003_eq_thermal.py9596## Compliance9798- ECSS standards are freely downloadable (ESA); cite the source and99 paraphrase per standards-map.yaml.100- compliance: STANDARDS-REF, gated: false.