ECSS Equipment Mission-Specific Tests (space-systems/ecss/e1003-eq-mission)
Use when the task is executing the mission-specific portion of the equipment
test campaign under ECSS-E-ST-10-03C §5.5.6 — running tests that are unique
to the equipment's actual mission environment and function (airborne sound
pressure, dynamic vibration, electromagnetic compatibility, thermal environment,
or functional performance in mission configuration) and verifying each result
against acceptance or qualification limits.
Domain quick reference
- §5.5.6 requires that equipment undergoing environmental testing address
any test whose pass/fail criterion is tied directly to the mission it will
perform, beyond the general environmental sequence. Each such test is tied
to a specific mission scenario or performance requirement.
- §5.5.6.1 covers airborne sound pressure measurement: the equipment is
exposed to an acoustic pressure field representative of its launch or
operational environment, and the overall sound pressure level (SPL)
measured on or near the equipment must remain at or below the limit defined
in the test specification.
- Every mission-specific test is categorized into exactly one type:
acoustic (SPL measurement), vibration (structural dynamic response),
emc (electromagnetic compatibility in mission configuration), thermal
(thermal environment representative of on-orbit or re-entry conditions),
or functional (performance verification under mission loads). An unrecognized
test type is rejected before it enters the evaluation.
- Test levels are either acceptance (lower stress, production flight hardware)
or qualification (higher stress, margin demonstration). The limit value
used in each evaluation must match the level specified in the test procedure.
- A margin is computed for every test: positive means the measurement sits
below the limit (pass), negative means an exceedance (fail). A zero margin
is a pass at the exact limit.
- Campaign completeness is verified separately: all test types required by
the equipment's test specification must appear in the submitted campaign
before the equipment can be declared mission-test complete.
Workflow
- Collect the list of mission-specific tests required for this equipment
from the test specification (derived from §5.5.6 and the equipment's
mission requirements document).
- For each test record, validate that the required fields are present
(test ID, test type, test level, measured value, limit value) and that
the test type is one of the recognized mission-specific types. Reject
any record with missing fields or an unrecognized type before processing.
- For acoustic tests (§5.5.6.1), compare the measured overall SPL (dB)
against the SPL limit from the test specification. Record the margin
(limit minus measured) and mark the test as pass (margin ≥ 0) or
fail (margin < 0).
- For all other mission-specific test types, apply the same margin logic:
compute margin = limit − measured (for tests where a higher value is
worse) or measured − limit (where a lower value is worse), then pass
or fail accordingly.
- Check campaign completeness: confirm that every test type required by
the specification appears at least once in the submitted records.
Record any missing types as a completeness gap.
- Compile a campaign summary: total records, passed, failed, records with
validation errors, overall campaign status (pass only when all records
pass and no errors exist), and the completeness gap list.
Pitfalls
- Mixing acceptance and qualification limits: each evaluation must use the
limit that matches the stated test level. Applying a qualification limit
to an acceptance-level test artificially tightens the criterion and may
cause spurious failures.
- Skipping the test-type validation step: an unrecognized test type silently
bypasses the evaluation unless it is explicitly rejected, creating a gap
in the campaign record.
- Reading a zero margin (measured equals limit exactly) as a borderline
concern: at the limit is a pass per ECSS convention; only a negative
margin is an exceedance.
- Declaring campaign completeness based on count alone: a campaign with the
right number of records but missing an entire test type (e.g., no acoustic
test at all) is incomplete regardless of record count.
- Conflating "no test record submitted" with "test not required": the
completeness check must be driven by the specification's required-type
list, not inferred from the submitted records.
Behavior contract (gate 3)
Mission-specific test categorization, limit comparison, margin computation,
campaign completeness, and sound pressure evaluation are exercised by the
gate 3 contract test: scripts/test_e1003_eq_mission.py against
scripts/e1003_eq_mission_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1003_eq_mission.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
- Anchor clause: ECSS-E-ST-10-03C §5.5.6 (equipment mission-specific tests),
§5.5.6.1 (airborne sound pressure measurement).
1---2name: e1003-eq-mission3description: "Use when execute equipment mission-specific test verification under4 ECSS-E-ST-10-03C §5.5.6: categorize each test by mission-environment type (acoustic5 sound pressure, dynamic vibration, electromagnetic compatibility, thermal environment,6 or functional performance), validate measured values against acceptance or qualification7 limits, compute test margins, verify all required mission-specific test types are8 present in the campaign, and confirm each result meets its pass criterion. Covers9 airborne sound pressure measurement per §5.5.6.1 and other mission-environment10 verification steps. Trigger: ecss, e-st-10-system-scope, e-st-10-03c,11 equipment-testing, mission-specific-tests, sound-pressure, vibration, emc."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-eq-mission23 domain: space-systems24 subdomain: ecss25 tags: [ecss, e-st-10-system-scope, e-st-10-03c, equipment-testing, mission-specific-tests, sound-pressure, vibration, emc]26 version: 0.1.027 author: Aero Agent Skills28---2930# ECSS Equipment Mission-Specific Tests (space-systems/ecss/e1003-eq-mission)3132Use when the task is executing the mission-specific portion of the equipment33test campaign under ECSS-E-ST-10-03C §5.5.6 — running tests that are unique34to the equipment's actual mission environment and function (airborne sound35pressure, dynamic vibration, electromagnetic compatibility, thermal environment,36or functional performance in mission configuration) and verifying each result37against acceptance or qualification limits.3839## Domain quick reference4041- §5.5.6 requires that equipment undergoing environmental testing address42 any test whose pass/fail criterion is tied directly to the mission it will43 perform, beyond the general environmental sequence. Each such test is tied44 to a specific mission scenario or performance requirement.45- §5.5.6.1 covers airborne sound pressure measurement: the equipment is46 exposed to an acoustic pressure field representative of its launch or47 operational environment, and the overall sound pressure level (SPL)48 measured on or near the equipment must remain at or below the limit defined49 in the test specification.50- Every mission-specific test is categorized into exactly one type:51 acoustic (SPL measurement), vibration (structural dynamic response),52 emc (electromagnetic compatibility in mission configuration), thermal53 (thermal environment representative of on-orbit or re-entry conditions),54 or functional (performance verification under mission loads). An unrecognized55 test type is rejected before it enters the evaluation.56- Test levels are either acceptance (lower stress, production flight hardware)57 or qualification (higher stress, margin demonstration). The limit value58 used in each evaluation must match the level specified in the test procedure.59- A margin is computed for every test: positive means the measurement sits60 below the limit (pass), negative means an exceedance (fail). A zero margin61 is a pass at the exact limit.62- Campaign completeness is verified separately: all test types required by63 the equipment's test specification must appear in the submitted campaign64 before the equipment can be declared mission-test complete.6566## Workflow67681. Collect the list of mission-specific tests required for this equipment69 from the test specification (derived from §5.5.6 and the equipment's70 mission requirements document).712. For each test record, validate that the required fields are present72 (test ID, test type, test level, measured value, limit value) and that73 the test type is one of the recognized mission-specific types. Reject74 any record with missing fields or an unrecognized type before processing.753. For acoustic tests (§5.5.6.1), compare the measured overall SPL (dB)76 against the SPL limit from the test specification. Record the margin77 (limit minus measured) and mark the test as pass (margin ≥ 0) or78 fail (margin < 0).794. For all other mission-specific test types, apply the same margin logic:80 compute margin = limit − measured (for tests where a higher value is81 worse) or measured − limit (where a lower value is worse), then pass82 or fail accordingly.835. Check campaign completeness: confirm that every test type required by84 the specification appears at least once in the submitted records.85 Record any missing types as a completeness gap.866. Compile a campaign summary: total records, passed, failed, records with87 validation errors, overall campaign status (pass only when all records88 pass and no errors exist), and the completeness gap list.8990## Pitfalls9192- Mixing acceptance and qualification limits: each evaluation must use the93 limit that matches the stated test level. Applying a qualification limit94 to an acceptance-level test artificially tightens the criterion and may95 cause spurious failures.96- Skipping the test-type validation step: an unrecognized test type silently97 bypasses the evaluation unless it is explicitly rejected, creating a gap98 in the campaign record.99- Reading a zero margin (measured equals limit exactly) as a borderline100 concern: at the limit is a pass per ECSS convention; only a negative101 margin is an exceedance.102- Declaring campaign completeness based on count alone: a campaign with the103 right number of records but missing an entire test type (e.g., no acoustic104 test at all) is incomplete regardless of record count.105- Conflating "no test record submitted" with "test not required": the106 completeness check must be driven by the specification's required-type107 list, not inferred from the submitted records.108109## Behavior contract (gate 3)110111Mission-specific test categorization, limit comparison, margin computation,112campaign completeness, and sound pressure evaluation are exercised by the113gate 3 contract test: scripts/test_e1003_eq_mission.py against114scripts/e1003_eq_mission_logic.py (stdlib unittest, offline). Run:115python3 scripts/test_e1003_eq_mission.py116117## Compliance118119- ECSS standards are freely downloadable (ESA); cite the source and120 paraphrase per standards-map.yaml.121- compliance: STANDARDS-REF, gated: false.122- Anchor clause: ECSS-E-ST-10-03C §5.5.6 (equipment mission-specific tests),123 §5.5.6.1 (airborne sound pressure measurement).