ECSS Equipment Protoflight Test Baseline (space-systems/ecss/e1003-eq-protoflight)
Use when the task is defining the equipment protoflight test baseline
under ECSS-E-ST-10-03C: deciding which test approach an equipment item
follows, and deriving the protoflight test level and duration for each
applicable test type ahead of test specification and test procedure
drafting.
Domain quick reference
- ECSS-E-ST-10-03C clause 5.4 defines the protoflight test approach:
when a single equipment model must serve as both the design
qualification article and the flight article (no separate, dedicated
qualification model is built), that equipment follows a protoflight
test baseline instead of running a full qualification campaign on
one model and a separate acceptance campaign on another.
- Table 5-5 tabulates, per test type (for example mechanical vibration,
thermal vacuum, thermal cycling, EMC), the qualification-level and
acceptance-level test severities: the qualification level carries
more margin above the predicted flight environment than the
acceptance level.
- Table 5-6 tabulates, per test type, the associated qualification and
acceptance test durations or cycle counts: the qualification
duration is longer than the acceptance duration.
- The protoflight baseline rule combines the two tables: the
protoflight test level for a test type is set at the qualification
level, while the protoflight test duration is set at the (shorter)
acceptance duration. This demonstrates qualification-level design
margin without exposing the flight hardware to the full
qualification duration, which could induce excess wear-out or
fatigue on hardware that still has to fly.
- A protoflight baseline entry that departs from this level/duration
combination is a deviation and needs a documented engineering
rationale -- it cannot be substituted silently. Equipment with a
dedicated qualification model does not use the protoflight baseline
at all; it keeps separate qualification and acceptance campaigns.
Workflow
- For each equipment item, classify its test approach: protoflight
when no dedicated qualification model exists (the same hardware
demonstrates qualification and then flies), otherwise
qualification-and-acceptance (separate models, standard campaigns).
- For each applicable test type on a protoflight equipment item,
capture its Table 5-5 qualification level and acceptance level, and
its Table 5-6 qualification duration and acceptance duration.
Reject a spec where the qualification level is below the acceptance
level or the qualification duration is below the acceptance
duration -- qualification must carry more margin and more exposure
than acceptance, not less.
- Derive the protoflight baseline for the test type: level =
qualification level, duration = acceptance duration.
- Build the full baseline matrix across every required test type for
the equipment item; reject a duplicate test type entry and report
any required test type still missing from the matrix.
- When a proposed baseline entry is supplied from elsewhere (for
example a test specification already in draft), compare it against
the standard-rule baseline derived from the same spec; flag any
entry whose level or duration does not match unless the test type
already has a recorded, approved deviation.
- Before declaring equipment ready for protoflight testing, confirm
it is actually categorized as following the protoflight approach and
that its baseline matrix has no missing required test types.
Pitfalls
- Applying the protoflight baseline (qualification level, acceptance
duration) to equipment that actually has a dedicated qualification
model -- that equipment should run separate qualification and
acceptance campaigns, not a blended baseline.
- Accepting a test spec where the "qualification" severity or duration
is weaker than the "acceptance" one -- that inverts the margin
relationship the baseline rule depends on.
- Silently substituting a different level or duration than the
standard rule produces instead of flagging it as a deviation needing
documented justification.
- Declaring an equipment item ready for protoflight testing while a
required test type is still missing from its baseline matrix.
Behavior contract (gate 3)
The approach-classification, spec-validation, baseline-derivation,
matrix-completeness, and deviation-flagging logic is exercised by the
gate 3 contract test: scripts/test_e1003_eq_protoflight.py against
scripts/e1003_eq_protoflight_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1003_eq_protoflight.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-protoflight3description: "Use when you define the equipment protoflight test baseline under ECSS-E-ST-10-03C clause 5.4: decide whether an equipment item must follow the protoflight test approach (one hardware model demonstrating both design qualification and flight acceptance, with no separate dedicated qualification model), and derive, for each test type, the protoflight test level from the Table 5-5 qualification/acceptance severities and the protoflight test duration from the Table 5-6 qualification/acceptance durations. Also flag any protoflight baseline entry whose level or duration deviates from the standard qualification-level/acceptance-duration rule without a documented engineering deviation. Trigger: protoflight test baseline, protoflight approach, equipment test levels, test duration, Table 5-5, Table 5-6, E-ST-10-03, ecss, e-st-10c."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-protoflight15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-03c, protoflight, equipment-testing, test-levels, test-duration]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Equipment Protoflight Test Baseline (space-systems/ecss/e1003-eq-protoflight)2324Use when the task is defining the equipment protoflight test baseline25under ECSS-E-ST-10-03C: deciding which test approach an equipment item26follows, and deriving the protoflight test level and duration for each27applicable test type ahead of test specification and test procedure28drafting.2930## Domain quick reference3132- ECSS-E-ST-10-03C clause 5.4 defines the protoflight test approach:33 when a single equipment model must serve as both the design34 qualification article and the flight article (no separate, dedicated35 qualification model is built), that equipment follows a protoflight36 test baseline instead of running a full qualification campaign on37 one model and a separate acceptance campaign on another.38- Table 5-5 tabulates, per test type (for example mechanical vibration,39 thermal vacuum, thermal cycling, EMC), the qualification-level and40 acceptance-level test severities: the qualification level carries41 more margin above the predicted flight environment than the42 acceptance level.43- Table 5-6 tabulates, per test type, the associated qualification and44 acceptance test durations or cycle counts: the qualification45 duration is longer than the acceptance duration.46- The protoflight baseline rule combines the two tables: the47 protoflight test level for a test type is set at the qualification48 level, while the protoflight test duration is set at the (shorter)49 acceptance duration. This demonstrates qualification-level design50 margin without exposing the flight hardware to the full51 qualification duration, which could induce excess wear-out or52 fatigue on hardware that still has to fly.53- A protoflight baseline entry that departs from this level/duration54 combination is a deviation and needs a documented engineering55 rationale -- it cannot be substituted silently. Equipment with a56 dedicated qualification model does not use the protoflight baseline57 at all; it keeps separate qualification and acceptance campaigns.5859## Workflow60611. For each equipment item, classify its test approach: protoflight62 when no dedicated qualification model exists (the same hardware63 demonstrates qualification and then flies), otherwise64 qualification-and-acceptance (separate models, standard campaigns).652. For each applicable test type on a protoflight equipment item,66 capture its Table 5-5 qualification level and acceptance level, and67 its Table 5-6 qualification duration and acceptance duration.68 Reject a spec where the qualification level is below the acceptance69 level or the qualification duration is below the acceptance70 duration -- qualification must carry more margin and more exposure71 than acceptance, not less.723. Derive the protoflight baseline for the test type: level =73 qualification level, duration = acceptance duration.744. Build the full baseline matrix across every required test type for75 the equipment item; reject a duplicate test type entry and report76 any required test type still missing from the matrix.775. When a proposed baseline entry is supplied from elsewhere (for78 example a test specification already in draft), compare it against79 the standard-rule baseline derived from the same spec; flag any80 entry whose level or duration does not match unless the test type81 already has a recorded, approved deviation.826. Before declaring equipment ready for protoflight testing, confirm83 it is actually categorized as following the protoflight approach and84 that its baseline matrix has no missing required test types.8586## Pitfalls8788- Applying the protoflight baseline (qualification level, acceptance89 duration) to equipment that actually has a dedicated qualification90 model -- that equipment should run separate qualification and91 acceptance campaigns, not a blended baseline.92- Accepting a test spec where the "qualification" severity or duration93 is weaker than the "acceptance" one -- that inverts the margin94 relationship the baseline rule depends on.95- Silently substituting a different level or duration than the96 standard rule produces instead of flagging it as a deviation needing97 documented justification.98- Declaring an equipment item ready for protoflight testing while a99 required test type is still missing from its baseline matrix.100101## Behavior contract (gate 3)102103The approach-classification, spec-validation, baseline-derivation,104matrix-completeness, and deviation-flagging logic is exercised by the105gate 3 contract test: scripts/test_e1003_eq_protoflight.py against106scripts/e1003_eq_protoflight_logic.py (stdlib unittest, offline). Run:107python3 scripts/test_e1003_eq_protoflight.py108109## Compliance110111- ECSS standards are freely downloadable (ESA); cite the source and112 paraphrase per standards-map.yaml.113- compliance: STANDARDS-REF, gated: false.