ECSS Space Systems — Element Acceptance Test Baseline (space-systems/ecss/e1003-el-acceptance)
Use when the task is to determine the acceptance test baseline for a flight
hardware element under ECSS-E-ST-10C §6.3, Tables 6-3/6-4 -- deriving
acceptance test levels from qualification levels, mapping mandatory test types
to the element category, and verifying that every proposed test duration meets
the specified minimum before the acceptance test review is convened.
Domain quick reference
- ECSS-E-ST-10C §6.3 distinguishes three element categories that govern which
tests are mandatory (Table 6-4, paraphrased): simple elements require
visual inspection and functional tests only; standard elements add random
vibration and thermal cycling; critical elements further add sine
vibration, thermal vacuum, and EMC. Each element is placed into exactly one
category before the mandatory test set is determined.
- Acceptance levels are derived from the corresponding qualification levels by
applying a fixed reduction margin. For random vibration the acceptance power
spectral density is 3 dB below the qualification PSD, which reduces the
overall grms level by a factor of approximately 0.707. For sine vibration the
acceptance amplitude (g) is likewise reduced by 3 dB in amplitude (factor
≈ 0.707). For thermal tests the acceptance temperature range is the
qualification range narrowed by the acceptance margin (nominally 5 °C) at
each extreme; a qualification range too narrow to accommodate the margin at
both ends is flagged as degenerate before any test planning proceeds.
- Minimum test durations are specified per test type in Table 6-3 (paraphrased):
vibration sine 4 min total, vibration random 2 min total, thermal cycling
480 min, thermal vacuum 1 440 min, EMC 60 min, functional 30 min, visual
inspection 15 min. A test whose actual duration falls short of the minimum is
a duration finding, independent of whether all test types are present.
- A proposed acceptance test plan must pass two independent checks before the
baseline is confirmed: (1) baseline completeness -- all mandatory test types
for the element category are present; (2) duration compliance -- every listed
test meets its minimum duration.
Workflow
- Assign the element to one of the three categories (simple, standard,
critical) based on its design complexity, functional criticality, and
mission class per the project's element-category rationale document. Reject
an unrecognised category before any further processing.
- Retrieve the mandatory test set for the assigned category from the Table 6-4
mapping. Any test type in the proposed plan that is not in the defined
vocabulary is rejected as an unrecognised entry before the baseline check
runs.
- For each test type in the mandatory set, derive the acceptance level from the
qualification baseline: apply the −3 dB grms factor for random vibration,
the −3 dB amplitude factor for sine vibration, and the ±5 °C thermal margin
for thermal tests. Verify that the qualification input values are positive
(vibration) or produce a non-degenerate acceptance range (thermal) before
any level is issued.
- Compare the proposed test plan against the mandatory set: record every
mandatory test type absent from the proposed plan as a missing-test finding.
Additional tests beyond the mandatory set are allowed and do not generate a
finding.
- For each test entry in the proposed plan, compare its declared duration
against the Table 6-3 minimum for that test type; record the shortfall in
minutes for every entry that falls short.
- Combine the findings: the acceptance test baseline is confirmed only when
both the missing-test list and the duration-failure list are empty. Any
remaining finding must be resolved and re-verified before the acceptance
test review board considers the plan closed.
Pitfalls
- Applying qualification levels directly as acceptance levels -- acceptance
tests run at reduced levels (−3 dB for vibration, narrowed thermal range);
using qualification levels over-stresses the flight article and voids the
acceptance rationale.
- Omitting the category assignment step and treating all elements as standard
-- a simple element tested at the standard mandatory set incurs unnecessary
risk of overstress; a critical element tested at the standard set leaves EMC,
sine vibration, and thermal vacuum uncovered.
- Reading a duration shortfall as a minor administrative issue -- a test that
runs below its minimum duration has not demonstrated the required exposure
and must be repeated; it is a test-validity finding, not a paperwork gap.
- Accepting a degenerate thermal range without flagging it -- when the
qualification temperature band is too narrow to accommodate the acceptance
margin at both extremes, the acceptance range is undefined and the thermal
test cannot be planned until the qualification range is reviewed.
- Treating extra tests in the proposed plan as evidence that the baseline is
complete -- baseline completeness is determined by the mandatory set; extra
tests do not compensate for missing mandatory ones.
Behavior contract (gate 3)
The category mapping, level derivation, duration check, baseline completeness,
and full plan validation logic is exercised by the gate 3 contract test:
scripts/test_e1003_el_acceptance.py against
scripts/e1003_el_acceptance_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1003_el_acceptance.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-acceptance3description: "Use when determine the acceptance test baseline for a space hardware4 element under ECSS-E-ST-10C §6.3 and Tables 6-3/6-4: identify which test types5 are mandatory for the element category, derive acceptance levels from qualification6 levels by applying the prescribed margin factors (vibration random −3 dB, thermal7 range narrowed by the acceptance margin), confirm each test duration meets the8 category minimum, and verify the complete proposed test plan contains no missing9 required tests before acceptance test review is convened. Trigger: ecss,10 e-st-10c, element-acceptance, acceptance-test, test-baseline, acceptance-levels,11 test-duration, vibration-acceptance, thermal-acceptance, acceptance-margin."12license: Apache-2.013compliance: STANDARDS-REF14standards:15 - id: ecss16 reference-only: true17gated: false18domain: space-systems19pack: space-systems20compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"21metadata:22 source: https://skillmd.com/skills/ashfordeou/e1003-el-acceptance23 domain: space-systems24 subdomain: ecss25 tags: [ecss, e-st-10-system-scope, element-acceptance, acceptance-test, test-baseline, acceptance-levels, test-duration, acceptance-margin]26 version: 0.1.027 author: Aero Agent Skills28---2930# ECSS Space Systems — Element Acceptance Test Baseline (space-systems/ecss/e1003-el-acceptance)3132Use when the task is to determine the acceptance test baseline for a flight33hardware element under ECSS-E-ST-10C §6.3, Tables 6-3/6-4 -- deriving34acceptance test levels from qualification levels, mapping mandatory test types35to the element category, and verifying that every proposed test duration meets36the specified minimum before the acceptance test review is convened.3738## Domain quick reference3940- ECSS-E-ST-10C §6.3 distinguishes three element categories that govern which41 tests are mandatory (Table 6-4, paraphrased): **simple** elements require42 visual inspection and functional tests only; **standard** elements add random43 vibration and thermal cycling; **critical** elements further add sine44 vibration, thermal vacuum, and EMC. Each element is placed into exactly one45 category before the mandatory test set is determined.46- Acceptance levels are derived from the corresponding qualification levels by47 applying a fixed reduction margin. For random vibration the acceptance power48 spectral density is 3 dB below the qualification PSD, which reduces the49 overall grms level by a factor of approximately 0.707. For sine vibration the50 acceptance amplitude (g) is likewise reduced by 3 dB in amplitude (factor51 ≈ 0.707). For thermal tests the acceptance temperature range is the52 qualification range narrowed by the acceptance margin (nominally 5 °C) at53 each extreme; a qualification range too narrow to accommodate the margin at54 both ends is flagged as degenerate before any test planning proceeds.55- Minimum test durations are specified per test type in Table 6-3 (paraphrased):56 vibration sine 4 min total, vibration random 2 min total, thermal cycling57 480 min, thermal vacuum 1 440 min, EMC 60 min, functional 30 min, visual58 inspection 15 min. A test whose actual duration falls short of the minimum is59 a duration finding, independent of whether all test types are present.60- A proposed acceptance test plan must pass two independent checks before the61 baseline is confirmed: (1) baseline completeness -- all mandatory test types62 for the element category are present; (2) duration compliance -- every listed63 test meets its minimum duration.6465## Workflow66671. Assign the element to one of the three categories (simple, standard,68 critical) based on its design complexity, functional criticality, and69 mission class per the project's element-category rationale document. Reject70 an unrecognised category before any further processing.712. Retrieve the mandatory test set for the assigned category from the Table 6-472 mapping. Any test type in the proposed plan that is not in the defined73 vocabulary is rejected as an unrecognised entry before the baseline check74 runs.753. For each test type in the mandatory set, derive the acceptance level from the76 qualification baseline: apply the −3 dB grms factor for random vibration,77 the −3 dB amplitude factor for sine vibration, and the ±5 °C thermal margin78 for thermal tests. Verify that the qualification input values are positive79 (vibration) or produce a non-degenerate acceptance range (thermal) before80 any level is issued.814. Compare the proposed test plan against the mandatory set: record every82 mandatory test type absent from the proposed plan as a missing-test finding.83 Additional tests beyond the mandatory set are allowed and do not generate a84 finding.855. For each test entry in the proposed plan, compare its declared duration86 against the Table 6-3 minimum for that test type; record the shortfall in87 minutes for every entry that falls short.886. Combine the findings: the acceptance test baseline is confirmed only when89 both the missing-test list and the duration-failure list are empty. Any90 remaining finding must be resolved and re-verified before the acceptance91 test review board considers the plan closed.9293## Pitfalls9495- Applying qualification levels directly as acceptance levels -- acceptance96 tests run at reduced levels (−3 dB for vibration, narrowed thermal range);97 using qualification levels over-stresses the flight article and voids the98 acceptance rationale.99- Omitting the category assignment step and treating all elements as standard100 -- a simple element tested at the standard mandatory set incurs unnecessary101 risk of overstress; a critical element tested at the standard set leaves EMC,102 sine vibration, and thermal vacuum uncovered.103- Reading a duration shortfall as a minor administrative issue -- a test that104 runs below its minimum duration has not demonstrated the required exposure105 and must be repeated; it is a test-validity finding, not a paperwork gap.106- Accepting a degenerate thermal range without flagging it -- when the107 qualification temperature band is too narrow to accommodate the acceptance108 margin at both extremes, the acceptance range is undefined and the thermal109 test cannot be planned until the qualification range is reviewed.110- Treating extra tests in the proposed plan as evidence that the baseline is111 complete -- baseline completeness is determined by the mandatory set; extra112 tests do not compensate for missing mandatory ones.113114## Behavior contract (gate 3)115116The category mapping, level derivation, duration check, baseline completeness,117and full plan validation logic is exercised by the gate 3 contract test:118scripts/test_e1003_el_acceptance.py against119scripts/e1003_el_acceptance_logic.py (stdlib unittest, offline). Run:120python3 scripts/test_e1003_el_acceptance.py121122## Compliance123124- ECSS standards are freely downloadable (ESA); cite the source and paraphrase125 per standards-map.yaml.126- compliance: STANDARDS-REF, gated: false.