ashfordeOU
- 1.3k skills
- 0 followers
- 5 repo stars
- 3 days ago last updated
- ▌ Q20 Gse Delivery · ashfordeou bundleCoordinate the delivery review and the handover of ground support equipment under ECSS-Q-ST-20C clauses 5.8.4.3 and 5.8.4.4: check that the board had the functions it needed and a chair independent of the work under review, confirm the agenda covered every subject it owes, let the open action list decide hold, reserve or deliver, derive the conformity certificates the item's own states demand, test each one against the delivery day so an expired or not-yet-issued certificate is caught, and reconcile the documentation that travels with the equipment. Use when GSE is about to be handed to its user. Trigger: ecss, q-st-20c-clause-5-8-4-3, gse-delivery-review-board, gse-board-quorum, gse-conformity-certificate-validity, gse-delivery-documentation, gse-delivery-authorisation.
- ▌ Q20 Pretailoring · ashfordeou bundleDerive the tailored clause 5 requirement set from the ECSS-Q-ST-20C clause 6 pre-tailoring matrix for one space product type: refuse a matrix row that says nothing about a product type or calls a requirement modified without stating the modification, keep each surviving requirement with its disposition, name every requirement the matrix does not cover, reconcile the project's own proposal against the baseline so a relaxation needs an approved justification while a tightening does not, and report the share of the set that still applies. Use when a project has to justify which quality requirements it works to. Trigger: ecss, q-st-20c-clause-6, pre-tailoring-matrix, space-product-type-applicability, tailored-requirement-set, requirement-relaxation-justification, applicable-requirement-fraction.
- ▌ Q20 Test Reports · ashfordeou bundleEvaluate a test report against the quality-assurance content and approval rules of ECSS-Q-ST-20C clause 5.6.3.2: check the mandatory sections are present, that every parameter the procedure demanded carries a finite measured value in the demanded unit or a justified not-measured declaration, grade each value against its limits with a value sitting on a limit counted inside, confirm every anomaly seen during the run was written up with a nonconformance reference and a disposition, and refuse a pass conclusion contradicted by the data. Use when a test report is submitted for approval or returned for correction. Trigger: ecss, q-st-20c-clause-5-6-3-2, qa-test-report-content-check, test-data-completeness-ratio, test-discrepancy-recording, test-report-approval-signature, measured-value-limit-grading.
- ▌ Q20 Test Reviews · ashfordeou bundlePerform the readiness and post-test reviews of ECSS-Q-ST-20C clause 5.6.5 as graded decisions rather than meetings: grade each review against the criterion list its own kind owns, refuse a waiver on a criterion that kind holds mandatory and demand a reference and an approver on the waivers it does allow, check the chair and product assurance were present with minutes referenced and no blocking action left open, and check a readiness review closed before the test started and a post-test review was held after it ended. Use when deciding go or no-go, or whether a finished test can be called closed. Trigger: ecss, q-st-20c-clause-5-6-5, test-readiness-review-criteria, post-test-review-closure, review-waiver-admissibility, review-blocking-action, trr-ptr-schedule-order.
- ▌ Q2007 Monitoring · ashfordeou bundleMonitor and measure the execution of a test campaign at a space test centre under ECSS-Q-ST-20-07C clause 5.8.1: rate every acquisition channel on its sample-rate ratio against the frequency of interest, its dropout fraction and its calibration validity; adjudicate each hold point on witness presence and named release authority; merge the logged surveillance intervals over the test window for the covered fraction and the unwatched gaps. Use when a test-centre monitoring plan, a surveillance log or an acquisition channel list has to be assessed before, during or after test execution. Trigger: ecss, q-st-20-07c, test-centre-monitoring, data-acquisition-channel-check, acquisition-nyquist-margin, test-hold-point-release, witness-point-adjudication, test-execution-surveillance, surveillance-coverage-gap.
- ▌ E1003 Eq General · ashfordeou bundleUse when verifying the general equipment-level test requirements under ECSS-E-ST-10-03C clause 5.1, ahead of picking the qualification, acceptance, or protoflight test baseline: confirm the test model carries the correct campaign (qualification/acceptance/protoflight), validate the test configuration is flight-representative or has documented deviations with every required interface simulated, check that mechanical/electrical interface checks bookend the test sequence, and run the functional-test-before/after and performance-test-bookend rules across the sequence. Trigger: ecss, e-st-10-03c, equipment test requirements, test configuration, interface check, functional test, performance test, test model applicability, general equipment tests.
- ▌ E1003 Eq Mission · ashfordeou bundleUse when execute equipment mission-specific test verification under ECSS-E-ST-10-03C §5.5.6: categorize each test by mission-environment type (acoustic sound pressure, dynamic vibration, electromagnetic compatibility, thermal environment, or functional performance), validate measured values against acceptance or qualification limits, compute test margins, verify all required mission-specific test types are present in the campaign, and confirm each result meets its pass criterion. Covers airborne sound pressure measurement per §5.5.6.1 and other mission-environment verification steps. Trigger: ecss, e-st-10-system-scope, e-st-10-03c, equipment-testing, mission-specific-tests, sound-pressure, vibration, emc.
- ▌ E1003 Eq Thermal · ashfordeou bundleUse 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.
- ▌ E1003 Management · ashfordeou bundleUse when manage a system-level test campaign under ECSS-E-ST-10C §4.3.1: assign customer and supplier responsibilities to each test event, verify that all mandatory readiness conditions (configuration baseline locked, procedure approved, support-equipment calibrated, personnel qualified, safety clearance granted) are satisfied before authorising a test, sequence campaign phases from planning through closeout, and flag any responsibility gap or unmet readiness prerequisite before the test-readiness review is held. Trigger: ecss, e-st-10-system-scope, test-management, test-campaign, readiness-review, customer-supplier, test-responsibility, test-readiness.
- ▌ E1003 Objectives · ashfordeou bundleUse when defining the test objectives for a qualification, acceptance or protoflight test campaign under ECSS-E-ST-10-03C clause 4.5: define the demonstrated-margin and workmanship-screen objectives assigned to each campaign type, derive the required test level (qualification level vs acceptance level) and duration class (full vs reduced) that those objectives imply, and validate a proposed test definition against the campaign's assigned objectives before test conditions, levels and durations are locked in downstream. Trigger: test objectives, qualification testing, acceptance testing, protoflight testing, demonstrated margin, workmanship screen, e-st-10-03, ecss, e-st-10c.
- ▌ E1003 Pre Launch · ashfordeou bundleUse when running pre-launch health checks, leak verification, functional tests, and campaign constraint checks at the launch site under ECSS-E-ST-10C §7: categorize each health check as structural, electrical, thermal, propulsion, software, or mechanical; compare measured leak rates against the allowable limit for each pressurized system; evaluate functional test outcomes for critical and non-critical subsystems; and verify every launch campaign environmental and temporal constraint is within its bounds before declaring launch readiness. Trigger: ecss, e-st-10-system-scope, pre-launch, launch-site, health-check, leak-verification, functional-test, launch-campaign, launch-readiness.
- ▌ E1004 Atmosphere · ashfordeou bundleUse when defining the neutral atmosphere environment for a mission under ECSS-E-ST-10-04C: select the applicable neutral-atmosphere density model (NRLMSISE-00 for general-purpose drag and lifetime work, JB-2006 for precision analyses) based on the case's precision need, verify the analysis altitude falls within the model's valid range, classify the solar activity level from the F10.7 solar flux index, apply solar/geomagnetic scaling to the reference density, select a wind model (HWM-type) when the case needs thermospheric wind data, and flag any non-Earth target body as needing a planet-specific atmosphere model instead of an Earth model. Trigger: neutral atmosphere, NRLMSISE-00, JB-2006, HWM, thermosphere, atmospheric density, drag, orbital lifetime, F10.7, solar flux index, geomagnetic index, wind model, e-st-10-04, ecss, space environment, planetary atmosphere.
- ▌ E1004 B2 Ige2006 · ashfordeou bundleUse when implementing the IGE-2006 geostationary trapped-electron flux model under ECSS-E-ST-10-04C Annex B.2: look up the differential electron flux at a requested energy and L-shell by log-linear interpolation between the model's tabulated energy and L-shell nodes, resolve the requested confidence level (mean or a worst-case percentile) to its flux scale factor, assemble a full energy-spectrum table for a request, and flag any energy or L-shell query that falls outside the tabulated node range as an extrapolation rather than silently returning a boundary value. Trigger: IGE-2006, geostationary electron model, GEO electron flux, trapped electron spectrum, L-shell interpolation, confidence level, worst-case percentile, Annex B.2, e-st-10-04, ecss, space environment.
- ▌ E1004 B8 Stormer · ashfordeou bundleUse when computing the Størmer vertical cutoff rigidity for a spacecraft location under ECSS-E-ST-10-04C Annex B.8: apply the dipole-field Størmer formula scaled by an epoch-dependent geomagnetic dipole moment coefficient to derive the cutoff rigidity at a geomagnetic latitude and radial distance, verify whether a given charged-particle rigidity penetrates the geomagnetic field at that location, and roll per-orbit-sample penetration results into a geomagnetic-shielding assessment for low-inclination low-Earth-orbit missions. Trigger: Stormer cutoff, Størmer cutoff, vertical cutoff rigidity, geomagnetic cutoff, dipole moment epoch, geomagnetic shielding, cosmic ray cutoff, rigidity spectrum, e-st-10-04, ecss, space environment, radiation environment.
- ▌ E1004 Mm Margins · ashfordeou bundleUse when applying margins to a debris/meteoroid flux prediction and its ballistic-limit damage prediction for an ECSS-E-ST-10-04C space environment specification: compute the margined expected-impact rate from a flux margin factor, compute the margined critical (ballistic-limit) diameter from a diameter margin factor, derive the margined probability of no penetration (PNP), and verify the margin factors used meet the project's minimum conservatism before the PNP is compared against its requirement. Trigger: debris margin, meteoroid margin, MMOD margin, flux margin factor, ballistic limit margin, critical diameter margin, damage prediction margin, probability of no penetration, PNP, margined flux, §10.2.6, E-ST-10-04, ecss, e-st-10c space environment.
- ▌ E1004 Ref Debris · ashfordeou bundleUse when selecting a meteoroid or orbital-debris flux model for a spacecraft environment analysis per ECSS-E-ST-10-04C Annex J: determine whether a candidate model (natural meteoroid or catalogued orbital debris) is applicable to a case's altitude, epoch, and particle-diameter range, compute the model's stated uncertainty band around a nominal flux value, and validate a reported flux/model pairing against the model's applicability envelope so an out-of-envelope claim is flagged rather than accepted at face value. Trigger: ecss, e-st-10-04c, meteoroid flux, orbital debris flux, flux model applicability, model uncertainty factor, ORDEM, MASTER, Annex J.
- ▌ E1004 Ref Geomag · ashfordeou bundleUse when selecting the geomagnetic field model reference data for a mission per ECSS-E-ST-10-04C Annex E: determine whether the internal field alone (IGRF) is sufficient for a given orbit altitude or an external/magnetospheric model must be added, validate an IGRF coefficient generation epoch as definitive, predictive, or stale, select the required spherical-harmonic degree/order truncation for the altitude, choose an external field model tier from the geomagnetic activity (Kp) index, and check a position against the solar-wind-pressure-dependent magnetopause standoff distance. Produces a structured field-model-source determination with explicit error paths for out-of-range inputs. Trigger: ecss, e-st-10-04c, geomagnetic field, igrf, external field model, magnetospheric model, magnetopause, kp index, space environment reference data.
- ▌ E1004 Ref Plasma · ashfordeou bundleUse when determine the ECSS-E-ST-10-04C Annex H plasma-environment reference region for a mission orbit regime (ionosphere, plasmasphere, auroral, outer magnetosphere, solar wind, magnetosheath, magnetotail/L2), validate a candidate density or temperature value against that region's reference order-of-magnitude range, derive a log-space representative value for margin analysis, and identify the hot, tenuous plasma condition associated with spacecraft surface-charging risk. Trigger: ecss, e-st-10-04c, annex h, plasma environment, plasma density, plasma temperature, ionosphere, plasmasphere, auroral, magnetosphere, solar wind, magnetosheath, magnetotail, spacecraft charging.
- ▌ E1011 Procedures · ashfordeou bundleUse when develop, validate, or review operational procedures for a space system under ECSS-E-ST-10-11C §4.9.1: structure each procedure with mandatory fields (procedure_id, title, purpose, procedure_type, preconditions, numbered steps, expected_outcome), verify the procedure_type is one of the accepted operational categories (nominal, contingency, maintenance, test, launch_countdown, on_orbit), confirm every step begins with an imperative verb and does not exceed the cognitive-load word limit, check that verification checkpoints are spaced within the allowed consecutive-step count, and flag compound actions that should be split into discrete steps. Trigger: ecss, e-st-10-system-scope, procedures, operational-procedures, hfe-review, procedure-validation, procedure-format, human-factors.
- ▌ E1011 Verif Test · ashfordeou bundleUse when verify human factors engineering (HFE) requirements for a space system by ground tests and demonstrations per ECSS-E-ST-10-11C §4.11.3 and Annex D: identify each HFE requirement needing ground verification, assign a verification method (test, demonstration, analysis, or inspection), map each test or demonstration method to its Annex D event category, check that all mandatory Annex D ground events are covered, evaluate pre-event readiness criteria, and aggregate pass, fail, and pending status across all requirements into an overall compliance determination. Trigger: ecss, e-st-10-system-scope, hfe, human-factors, ground-test, verification, annex-d, hfe-testing, ergonomics.
- ▌ E1012 Bg Nuclear · ashfordeou bundleUse when determine the background count rate produced by nuclear interactions in spacecraft shielding materials under ECSS-E-ST-10-12C §10.4.3: for each shielding layer, compute the nuclear interaction probability from material type and areal density using the nuclear interaction length, estimate the secondary particle yield per interaction as a function of incident particle energy, compute the interaction rate for a given incident flux and detector area, scale by the fraction of secondaries depositing energy in the sensitive detector volume, and compare the resulting background rate against the instrument background budget to verify compliance. Trigger: ecss, e-st-10-12c, nuclear-background, spallation, secondary-particles, nuclear-interaction-length, detector-background, background-budget, ionisation.
- ▌ E1012 Principles · ashfordeou bundleUse when assess radiation effects on space components or systems under ECSS-E-ST-10-12C §4 evaluation framework: identify which radiation effect types apply (total ionising dose, displacement damage, single-event effects, enhanced low dose rate sensitivity), determine the evaluation activities required for the current project phase from the stage-activity table, validate parameter-unit pairs against the §4 parameter table, and verify evaluation completeness before phase closure. The framework spans phase A concept screening through phase F end-of-life verification, with cross-references to ECSS-E-ST-10-04C for the radiation environment inputs. Trigger: ecss, e-st-10-12c, radiation-effects, total-ionising-dose, displacement-damage, single-event-effects, eldrs, radiation-hardness-assurance, evaluation-activities, project-phase.
- ▌ Drd Design Loads · ashfordeou bundleUse when determine design loads for a space structure under ECSS-E-ST-32C Annex B: enumerate all load cases by type (static, quasi-static, dynamic-sine, dynamic-random, dynamic-shock, thermal, acoustic, pressure, inertia, combined), assign a Limit Load to each, apply partial safety factors to derive Design Limit Loads (DLL), compute Design Yield Loads (DYL = DLL × yield factor), and compute Design Ultimate Loads (DUL = DLL × ultimate factor). Flag any load case with a missing limit load, a safety factor outside the accepted range, or a load type not in the ECSS load taxonomy. Trigger: ecss, e-st-32-structures-scope, design-loads, limit-load, dll, dyl, dul, load-cases, drd, safety-factor.
- ▌ Drd Mass Summary · ashfordeou bundleUse when produce a structure mass summary (SMS) document per ECSS-E-ST-32C Annex N: enumerate every structural component with its dry mass and design maturity code, apply the maturity-dependent margin to each entry to obtain the component mass-with-margin, sum the contributions to derive total dry mass and total mass-with-margin, compare the total against the allocated mass budget, and flag any component missing a recognized maturity code or a valid mass value. Trigger: ecss, e-st-32-structures-scope, mass-summary, sms, dry-mass, mass-margin, maturity-code, drd, mass-budget.
- ▌ E10 Pretailoring · ashfordeou bundleUse when applying the ECSS-E-ST-10C clause 7 pre-tailoring matrix to a space project: for the project's declared space product type (e.g. space segment, ground segment, launch service segment element), determine which clause-5 system-engineering requirements are applicable, optional, or not applicable, before project-specific tailoring per ECSS-S-ST-00-01. Checks the matrix itself is complete and well-formed, and checks the project's carried-forward requirement clauses against the resolved applicability (missing mandatory clauses, out-of-scope clauses kept without justification, unknown clause ids). Trigger: ecss, e-st-10c, pre-tailoring, pretailoring matrix, tailoring matrix, product type, applicability, clause 7.
- ▌ E10 Req Analysis · ashfordeou bundleUse when analysing customer or upper-level requirements to derive, generate, control and document the requirement set for a space system and for each lower level, per ECSS-E-ST-10C clause 5.2.1. Checks that every requirement traces to a customer requirement or an existing upper-level requirement (no orphans), carries identifying text and rationale (documented), and is under configuration control (released or baselined). Trigger: ecss, e-st-10c, requirement analysis, derive requirements, requirement derivation, requirement set, lower-level requirements, requirement control, 5.2.1.
- ▌ E10 Req Baseline · ashfordeou bundleUse when establishing or controlling the requirements baseline for a configuration item (CI) under ECSS-E-ST-10C clause 5.2.3.9: classify each requirement's approval status ahead of an agreed baseline milestone, verify it carries requirement text and a verification method, identify duplicate requirement identifiers within the set, define the baseline record once every requirement in the set is ready, and validate every subsequent addition, modification, or deletion of a baselined requirement against an approved change request. Trigger: ecss, e-st-10c, requirements baseline, baseline management, configuration item, milestone review, change control, requirement verification.
- ▌ E10 Tradeoff Drd · ashfordeou bundleUse when produce or review a trade-off report against the ECSS-E-ST-10C Annex L Document Requirements Definition: validate that the criterion weights form a normalized set, confirm every option carries a score against every criterion rather than defaulting a gap to zero, compute the weighted ranking and the margin to the runner-up, test whether shifting any single weight flips the winner, and decide whether the report reaches a defensible recommendation. Trigger: ecss, e-st-10-system-scope, trade-off-report, annex-l-drd, weighted-criteria, option-ranking, sensitivity-analysis, decision-margin.
- ▌ E10 Trs Flowdown · ashfordeou bundleUse when flowing customer technical requirements down to next-lower-level technical requirements specifications (TRS) per ECSS-E-ST-10C clause 5.2.3.1: check every customer TS requirement reaches at least one child TRS, that no child TRS value contradicts the parent TS or a sibling TRS, and that each TRS carries the document structure expected by E-ST-10-06. Trigger: ecss, e-st-10c, trs flowdown, technical requirements specification, requirement flow-down, customer TS, next-lower-level requirements, e-st-10-06.
- ▌ E1002 Acceptance · ashfordeou bundleUse when running the acceptance stage of ECSS-E-ST-10-02C verification for a flight (or protoflight) article: gate the article on flight-standard workmanship/configuration eligibility, apply the acceptance-article rules distinguishing a dedicated acceptance test (prototype philosophy) from protoflight credit, guard against an acceptance test overstepping its qualified margin, disposition the workmanship/performance outcome, and close out the stage across a product set. Anchor: E-ST-10-02C clause 5.2.4.3. Trigger: acceptance stage, acceptance test, acceptance article, flight-standard workmanship, protoflight credit, overtest, acceptance review, e-st-10-02, ecss.
- ▌ E1002 Facilities · ashfordeou bundleUse when qualifying an integration and test facility or a test tool before it is used on a flight article under ECSS-E-ST-10-02C clause 5.2.6.6: map the planned test method to the facility type it requires, verify the facility's operating envelope covers the test's required range, confirm the facility's quality accreditation is a live Q-ST-20-07 test-centre accreditation, confirm calibration currency for the facility and for any measurement instrument, confirm a test tool's interfaces fit the article, check a qualification-plan record for missing fields, and roll many facility/tool qualification results up into a single AIT readiness gate. Trigger: ecss, e-st-10-02c, facilities, test tools, facility qualification, q-st-20-07, test-centre quality, calibration, capability envelope, ait readiness.
- ▌ E1002 Method Rod · ashfordeou bundleUse when verify a requirement's compliance under the review-of-design method of ECSS-E-ST-10-02C clause 5.2.2.4: classify each design-evidence item (drawing, analysis report, design description, supplier certificate, heritage data, similarity data) as direct or heritage evidence, apply the admissibility rule for a safety-critical requirement backed only by heritage evidence, roll up each item's compliant, non_compliant, open, or not_applicable disposition into an overall requirement status, and assemble a review-of-design report entry per requirement while flagging any requirement absent from the report. Trigger: ecss, e-st-10-02c, review of design, rod, design evidence, heritage data, similarity data, verification report, requirement close-out.
- ▌ E1002 Pre Launch · ashfordeou bundleUse when a flight item needs a pre-launch readiness go/no-go before launch under ECSS-E-ST-10-02C: transport-induced damage check, storage/shelf-life and environmental-excursion check, launch-site health/functional checks, and as-built launch configuration vs qualified/accepted baseline. Trigger: pre-launch readiness, launch readiness review, LRR, transport check, shelf life, storage excursion, launch-site checkout, launch configuration, as-built vs baseline, verification stage, E-ST-10-02, ecss, e-st-10c.
- ▌ E1002 Rod Report · ashfordeou bundleUse when produce or audit a review-of-design report against the ECSS-E-ST-10-02 clause 5.3.2.3 and Annex D Document Requirements Definition: confirm the review panel exists and is independent of the design authors by identity rather than by declaration, confirm every reviewed document is pinned to a revision, confirm each checklist item carries a result with an adverse item dispositioned and a not-applicable item justified, and close the review only when nothing adverse remains open. Trigger: ecss, e-st-10-02c, review-of-design, annex-d-drd, reviewer-independence, checklist-disposition, document-revision, design-evidence.
- ▌ E1002 Simulators · ashfordeou bundleUse when a simulator (functional, real-time, or closed-loop / hardware-in-the-loop) is used to generate verification evidence under ECSS-E-ST-10-02C and its own qualification status needs to be established before that evidence can be credited: which fidelity evidence a simulator's role requires, whether it is currently qualified, and whether a design or interface change triggers re-qualification. Trigger: simulator qualification, functional simulator, real-time simulator, closed-loop simulator, hardware-in-the-loop, HIL simulator, verification tool qualification, e1002, e-st-10-02, ecss, e-st-10c.
- ▌ E1003 El General · ashfordeou bundleUse when verify general element test requirements under ECSS-E-ST-10C §6.1: order the test campaign by ascending scope (unit, integration, element), confirm that every declared interface is exercised by at least one passing test, check that all element-level functions are covered by the campaign, and flag missing required test levels before formal acceptance. Trace each test result to its driving requirement and control the test configuration throughout. Trigger: ecss, e-st-10-system-scope, element-testing, test-sequence, interface-verification, functional-check, test-campaign, test-compliance.
- ▌ E1003 El Mission · ashfordeou bundleUse when run element mission-specific tests under ECSS-E-ST-10C clause 6.5.6: determine the applicable test categories for a given element type and mission orbit, validate that the planned test programme covers every required category, evaluate individual test results against acceptance limits, and produce an aggregated per-element mission-test compliance verdict. Test categories are divided into functional, environmental, and performance-verification types. Category selection depends on both the mission orbit (LEO, GEO, MEO, HEO, interplanetary) and the element type (propulsion, structure, avionics, payload, power). Trigger: ecss, e-st-10-system-scope, mission-specific-tests, element-testing, test-programme, mission-profile, acceptance-criteria, test-compliance.
- ▌ E1003 El Thermal · ashfordeou bundleUse when run and validate element-level thermal tests per ECSS-E-ST-10C §6.5.4: thermal vacuum cycling, thermal balance correlation, mission-pressure thermal cases, and Space-Station-specific thermal conditions for a spacecraft element. Checks each test case for conformance with temperature setpoint, soak duration, cycle count, chamber pressure, and margin requirements. Verifies thermal model correlation against balance measurements and confirms the mandatory thermal test campaign is complete before closure. Trigger: ecss, e-st-10c, thermal-vacuum, thermal-balance, tvac, tbal, mission-pressure, iss-thermal, element-thermal-test.
- ▌ E1012 Rdm Basis · ashfordeou bundleUse when define the radiation design margin (RDM) requirement basis for a spacecraft component from the mission radiation environment specification (ECSS-E-ST-10-12C §5.1.1): take the total ionising dose, proton fluence, and electron fluence from the environment model, apply the minimum RDM factor to each parameter to derive the required component withstand level, verify the factor meets the ECSS minimum threshold, and flag any component whose radiation tolerance falls short of the required level. Trigger: ecss, e-st-10-system-scope, e-st-10-12c, radiation-design-margin, rdm, total-ionising-dose, proton-fluence, electron-fluence.
- ▌ E1012 Tid Basis · ashfordeou bundleUse when determine the TID assessment basis for a spacecraft electronics programme under ECSS-E-ST-10-12C §7.1–7.4: identify every orbit environment that contributes to total ionising dose (trapped protons, trapped electrons, solar energetic protons, galactic cosmic rays, bremsstrahlung), categorize each device technology against the TID sensitivity spectrum per Table 7-1 (high/moderate/low), flag bipolar linear technologies that require low dose-rate ELDRS testing, and derive the minimum TID qualification test level from the design dose and the required margin factor. Trigger: ecss, e-st-10-system-scope, total-ionising-dose, tid-assessment-basis, tid-environment, radiation-sensitive-technology, eldrs, dose-margin, table-7-1.
- ▌ E1024 Iid Guide · ashfordeou bundleUse when draft an Interface Identification Document (IID) for a space system or equipment item under ECSS-E-ST-10-24C Annex D: inventory every interface of the item, categorize each interface by type (physical, electrical, data, RF, thermal, optical, fluid), assign a maturity level (proposed, agreed, or baselined) to each interface, record the responsible party for each interface side, verify that every interface links to a controlling Interface Control Document, and aggregate completeness gaps before formal baseline. Trigger: ecss, e-st-10-system-scope, iid, interface-identification, interface-register, icd, interface-management, interface-type, maturity-level.
- ▌ E1024 Lifecycle · ashfordeou bundleUse when run the interface management life cycles for a space project under ECSS-E-ST-10C §4.3: determine required lifecycle activities per project phase for generic, space-element–launch-segment, space–ground-segment, and OTS-product interface types; check that phase-gate agreements are in place; and verify interface documentation has reached the expected maturity level. Covers all four lifecycle streams and OTS-product involvement agreements. Trigger: ecss, e-st-10-system-scope, interface-management, lifecycle, phase-gate, launch-segment, space-ground, ots-product, agreements.
- ▌ E3102 Leak Test · ashfordeou bundleDefine the leak test of a two-phase heat transport item under ECSS-E-ST-31-02C clause 5.6.8. Use when the task is deriving the acceptance leak rate from the fluid inventory the item may lose over its life rather than quoting one, picking a method whose sensitivity actually resolves that rate, converting a helium tracer reading to the working fluid through the inverse square root of molar mass, and grading the converted rate against the acceptance value while separating a real measurement from a reading below the instrument floor. Trigger: ecss, e-st-31-02c, derived-acceptance-leak-rate, helium-tracer-molar-mass-conversion, leak-test-method-sensitivity, two-phase-fluid-inventory-loss, instrument-floor-non-detection.
- ▌ E3311 Materials · ashfordeou bundleEvaluate a material list for an explosive device against ECSS-E-ST-33-11C clause 4.9. Use when the task is deciding which candidates may sit next to a charge and which are out: grading vacuum mass loss and condensable volatiles, grading gas evolution and decomposition-onset depression measured in contact with the explosive, holding stress-corrosion susceptibility to the allowed category unless a justification is on record, checking each temperature rating against the hot case plus margin, and computing the potential difference across every declared contact pair against the allowance its environment carries. Trigger: ecss, e-st-33-11-explosive-subsystem-scope, explosive-material-compatibility, explosive-gas-evolution-limit, explosive-outgassing-screening, explosive-galvanic-couple, stress-corrosion-susceptibility-explosive, decomposition-onset-depression.
- ▌ E50 Error Rates · ashfordeou bundleCompute the error-rate budget of a ground network data path against ECSS-E-ST-50C clause 5.8.4, which asks the ground figure to sit well under the rates carried by the space link and by the space network rather than under an absolute number of its own. Convert a bit error rate into a block or frame error rate, compose the segments of a path into one end-to-end figure, and invert that composition into the rate each hop has to hold. Report errored bits, errored blocks and errored seconds over a pass, and the headroom as a ratio and in decibels. Use when apportioning an error budget across ground segments, or grading a measured path against one. Trigger: ecss, e-st-50-ground-network, ground-network-error-rate, bit-error-rate-to-frame-error-rate, end-to-end-error-budget-apportionment, errored-seconds-per-pass, ground-segment-error-margin.
- ▌ E5053 Semantics · ashfordeou bundleValidate the semantics subclause of a SpaceWire service primitive against ECSS-E-ST-50-53 clause 5.2.2.2. Use when a protocol service definition declares its per-primitive parameter lists and they have to hold together before baseline: check every parameter for a name, a type and a presence category, refuse a conditional parameter with no stated condition, reject duplicate or unnamed entries, then align each request against its paired indication, response and confirm so no mandatory parameter is dropped across the pair and no parameter appears that the originator never supplied. Trigger: ecss, e-st-50-53, service-primitive-semantics-subclause, primitive-parameter-list, parameter-presence-category, conditional-parameter-condition, request-indication-pair-alignment, spacewire-service-definition.
- ▌ E7041 Parameter · ashfordeou bundleValidate the parameters an on-board control procedure is started with under ECSS-E-ST-70-41C clause 6.18.3.2, where every procedure declares its parameters and an argument list is usable only when it matches that declaration. Use when the task is binding supplied arguments positionally or by name, checking arity and order, refusing a type the declared parameter cannot hold, refusing a value outside its declared range or outside its enumerated set, applying declared defaults for omitted optional parameters, and computing the encoded octet size of the bound set the start request has to carry. Trigger: ecss, e-st-70-41c, obcp-parameter-declaration, obcp-argument-binding, obcp-parameter-range-check, obcp-parameter-enumeration-membership, obcp-parameter-default-value, obcp-parameter-encoded-size.
- ▌ E7041 Resources · ashfordeou bundleSize the on-board resources a large packet transfer downlink subservice reserves under ECSS-E-ST-70-41C clause 6.13.3.2: turn each queued large message into the whole parts it buffers, sweep the transaction timeline for the peak of simultaneous transactions and peak reserved octets, then admit or refuse each arrival against the declared transaction slots and buffer pool. Use when the number of simultaneous large message downlinks, the octets reserved per transaction or the buffer pool of a service 13 subservice has to be justified or reviewed. Refuses an unordered transaction interval and a zero slot count. Trigger: ecss, e-st-70-41c, pus-service-13, large-message-downlink-resources, concurrent-transaction-slots, downlink-buffer-pool, transaction-slot-admission, peak-reserved-octets.
- ▌ Insert Analysis · ashfordeou bundleUse when determine the structural adequacy of mechanical inserts embedded in metallic, honeycomb sandwich, or composite structures per ECSS-E-ST-32C clause 4.6.2.16: categorize each insert by substrate type (metal, honeycomb core, composite laminate), select the governing failure mode (pull-out for metal threads, core shear and potting failure for honeycomb potted inserts, bearing and pull-through for composites), compute the allowable strength for each mode, apply the quadratic interaction equation when axial and shear loads act simultaneously, and derive the margin of safety with the project factor of safety applied. Flag any insert with a negative margin or a missing strength allowable. Trigger: ecss, e-st-32-structures-scope, insert-analysis, honeycomb, potted-insert, composite-bearing, margin-of-safety, structural-fastener.
- ▌ Lbb By Analysis · ashfordeou bundleUse when determine whether a pressurized structure satisfies the leak-before-burst requirement by analysis per ECSS-E-ST-32C clause 5.3.2: compute the critical crack length at burst pressure using linear elastic fracture mechanics, verify that a through-wall leak crack remains stable below the residual-strength limit, integrate a Paris-law fatigue crack-growth model to confirm life from initial flaw to through-wall penetration exceeds mission life with margin, and assess residual strength with the largest stable leak crack. Trigger: ecss, e-st-32-structures-scope, leak-before-burst, lbb, fracture-mechanics, crack-growth, residual-strength, pressure-vessel.
- ▌ Q20 Coc Example · ashfordeou bundleDraft and grade a certificate of conformity against the worked example of ECSS-Q-ST-20C Annex H, taken as the standard sheet format: hold the printed block order, name every mandatory block left blank as one finding, parse each serial range into a prefix, a first and a last serial at one padded width, refuse a mixed prefix or a backwards range, report two ranges covering the same serial, reconcile the serials covered with the declared quantity, rebuild the certificate number from the contract reference and the sheet sequence, and refuse a sheet dated after the day it is presented. Use when a certificate is raised or checked on receipt. Trigger: ecss, q-st-20c-annex-h, certificate-of-conformity-format, coc-block-order, coc-serial-range-arithmetic, coc-number-pattern, coc-issue-date-check.
- ▌ Q20 Gse General · ashfordeou bundleAudit the general quality assurance requirements that follow ground support equipment under ECSS-Q-ST-20C clause 5.8.8: test each identification mark against the marking scheme, catch a mark repeated across the register and a mark on the item that disagrees with the register entry, derive the record set the item's category and states demand, size the record retention shortfall in years against service life plus margin, and name every handling provision a safety-critical item owes at its point of use. Use when a GSE register or a single item's file is being reviewed. Trigger: ecss, q-st-20c-clause-5-8-8, gse-identification-marking, gse-register-duplicate-mark, gse-record-retention-shortfall, gse-safety-critical-handling-provision, gse-file-completeness.
- ▌ Q20 Logbook Drd · ashfordeou bundleMaintain and assess the unit logbook of ECSS-Q-ST-20C Annex C against its document requirements description: validate each history, inspection, modification and environmental entry against the fields its type owes, check the numbering for a gap or a repeat, refuse a date that runs backwards down the sequence, trace the configuration through the modification chain so each one starts where the last left off, flag an environmental excursion or a failed inspection carrying no nonconformance reference, and accumulate the exposure hours recorded. Use when a logbook is opened, written up or reviewed at acceptance. Trigger: ecss, q-st-20c-annex-c, unit-logbook-drd, logbook-history-entries, logbook-inspection-entries, logbook-modification-chain, logbook-environmental-exposure.
- ▌ Q2007 Tf Config · ashfordeou bundleVerify that a test facility is under configuration control as ECSS-Q-ST-20-07 clause 5.6.2 asks, and say what the state of the baseline obliges the test centre to do. Use when a campaign is about to run in a facility whose hardware, software, fluid lines and fixed instrumentation have moved since the last baseline: refuse a facility never baselined, check that every configuration item carries an identification, replay the approved and applied change records from the baseline version forward, and report any item whose as-run configuration that chain does not reach. Trigger: ecss, q-st-20-07-test-facility-clause-5-6-2, test-facility-configuration-baseline, test-facility-as-run-configuration-drift, test-facility-unapproved-change-applied, test-facility-configuration-item-identification.
- ▌ Q2007 Tf Design · ashfordeou bundleDesign and clear a new or modified test facility for use under ECSS-Q-ST-20-07C clause 5.6.1. Use when a facility development has to prove it is finished rather than merely delivered: take the ordered review set from the change category, capture each requirement with a criticality, verification method, status and reference, refuse a safety-critical requirement closed by design review alone or waived at all, name a review closed before an earlier one, report verification coverage as a fraction, and hold the facility out of use while anything blocks. Trigger: ecss, q-st-20-07-test-centre, q2007-tf-design, test-facility-development-review-set, facility-requirement-verification-coverage, facility-modification-change-category, verification-before-facility-use, facility-acceptance-review-sequence.
- ▌ E1002 Execution · ashfordeou bundleUse when execute verification activities against the verification plan and control document under ECSS-E-ST-10-02 clause 5.3.1: confirm every readiness condition holds before an activity starts, suspend it while any nonconformance raised against it stays open, confirm each departure from the approved procedure was authorized before execution rather than after, reconcile the as-run steps against the as-planned steps, and derive the activity's true state from its own record. Trigger: ecss, e-st-10-02c, verification-execution, readiness-review, nonconformance, deviation-approval, as-run-record, activity-state.
- ▌ E1002 Gse Tools · ashfordeou bundleUse when ground support equipment (GSE) will interface with flight hardware during verification and needs to be qualified as verification tooling before use, consistent with ECSS-E-ST-10-02C clause 5.2.6.2 (GSE qualification) and the general tool-qualification regime of clause 5.2.6.1. Classifies GSE as mechanical (MGSE) or electrical (EGSE) and determines the required qualification actions (interface control document, proof test, periodic re-proof, interface safety verification, calibration with traceability). Trigger: GSE, ground support equipment, MGSE, EGSE, proof test, handling equipment, test stimulation equipment, tool qualification, E-ST-10-02, verification tooling, ecss, e-st-10c.
- ▌ E1003 Dev Tests · ashfordeou bundleUse when plan and execute development tests for a space system under ECSS-E-ST-10C §4.2: define each test objective with a traceable success criterion, specify the test conditions and their acceptable tolerance bands, record actual conditions during test execution, evaluate all measurements against minimum and maximum requirement bounds, and confirm the development test report contains every mandatory element (objective reference, actual conditions, measurements, outcome, and anomaly record). Development tests precede the qualification test programme and generate design margin data to reduce programme risk. Trigger: ecss, e-st-10-system-scope, development-testing, test-objectives, test-conditions, test-reporting, test-plan, qualification-precursor.
- ▌ E1003 El Crewed · ashfordeou bundleUse when run crewed-mission element tests under ECSS-E-ST-10C §6.5.7: vibroacoustic emission, human factors engineering (HFE), toxic offgassing, and audible noise. Categorize each test record into one of the four mandated test families, evaluate measured results against acceptance limits, and flag any missing test families or limit exceedances before crewed-mission qualification sign-off. Each family has distinct acceptance criteria: vibroacoustic levels in dB, HFE pass/fail judgments, offgassing concentration in mg/m³, and audible noise in dB(A). A crewed element is compliant only when all four families produce no findings. Trigger: ecss, e-st-10-system-scope, crewed-mission, vibroacoustic, hfe, toxic-offgassing, audible-noise, crewed-element-test.
- ▌ E1003 Retesting · ashfordeou bundleUse when applying ECSS-E-ST-10-03C clause 4.6 retesting rules to define whether an article must be retested: a design modification made after qualification, storage after a protoflight/acceptance test beyond the qualified shelf life, a previously flown article being prepared for reflight, or a qualification-model article proposed for flight use. Classify each case's required action (no retest, requalification, acceptance-level retest, or disallowed for flight) ahead of test-programme execution (sibling e1003-test-programme leaf), and verify no case in the retesting scope is left undetermined. Anchor: E-ST-10-03C clause 4.6. Trigger: retesting, retest, requalification, design modification after qualification, storage shelf life, reflown hardware, qualification model flight use, E-ST-10-03C, ecss.
- ▌ E1003 Tailoring · ashfordeou bundleUse when determine the tailoring profile of ECSS-E-ST-10-03C for a specific space project class (A–D) using the Annex D informative method: map each standard requirement to an applicability status (Applicable, Not Applicable, Tailored, or Conditional), assign verification methods, and produce a compliance matrix and a verification matrix. Apply when a project team must scope the system engineering requirements set to their mission category, justify deviations, and supply the matrices required by a review or product-assurance gate. Trigger: ecss, e-st-10-03c, tailoring, annex-d, compliance-matrix, verification-matrix, project-class, system-engineering, applicability.
- ▌ E1003 Test Data · ashfordeou bundleUse when record, reduce, and deliver test measurement data for a spacecraft test campaign under ECSS-E-ST-10C §4.3.5: determine the minimum sampling rate for each channel type (vibration, acoustic, thermal, pressure, electrical, strain), validate that raw data records carry complete metadata (channel ID, calibration coefficients, timestamp, format), compute storage requirements, apply linear calibration to convert raw counts to engineering units, categorize each data channel as primary, secondary, or housekeeping, and confirm that the delivery package bundles a calibration file, test report reference, and all required traceability fields before handover. Trigger: ecss, e-st-10-system-scope, test-data, sampling-rate, data-reduction, data-delivery, calibration, test-measurement, storage-requirement.
- ▌ E1003 Test Docs · ashfordeou bundleUse when producing the test documentation set required by ECSS-E-ST-10C §4.3.3: draft the Assembly, Integration and Test (AIT) plan, the Test Specification (TSPE), the Test Procedure (TPRO), and the Test Report; verify each document carries the mandatory control fields (type, issue number, date, approval status); confirm the TSPE and TPRO trace every item to a recorded test requirement; check that document sequencing is respected (AIT plan approved before TSPE is released, TSPE approved before TPRO is released, TPRO approved before the Test Report is issued); and flag any missing document, broken traceability link, or sequence violation before the test campaign proceeds. Trigger: ecss, e-st-10-system-scope, test-documentation, ait-plan, tspe, tpro, test-report, document-control, traceability.
- ▌ E1004 B4 Flumic · ashfordeou bundleUse when implementing the FLUMIC outer/inner radiation belt worst-case trapped electron model under ECSS-E-ST-10-04C Annex B.4: select the belt region (inner belt, outer belt, or both for a belt-crossing orbit), apply the confidence (percentile) level and the worst-case exposure-duration class the analysis purpose requires, evaluate the resulting electron energy spectrum, and integrate the flux above a shielding-relevant threshold energy for internal (deep-dielectric) charging design. Trigger: FLUMIC, worst-case electron spectrum, outer belt, inner belt, internal charging, deep dielectric charging, trapped electrons, Annex B.4, e-st-10-04, ecss, space environment, radiation belt model.
- ▌ E1004 B5 Geo Wc · ashfordeou bundleUse when implementing the NASA worst-case geosynchronous (GEO) electron environment spectrum per ECSS-E-ST-10-04C Annex B.5: select the applicable energy band of the two-population exponential spectral fit (a lower-energy population associated with spacecraft surface charging and a higher-energy, penetrating population associated with deep-dielectric/internal charging), compute the differential and integral electron flux at a given energy, derive the worst-case fluence for a stated exposure duration, and assess a case's worst-case fluence against its qualified fluence limit. Trigger: NASA worst-case GEO electron spectrum, geosynchronous electron environment, internal charging, deep dielectric charging, Annex B.5, e-st-10-04, ecss, space environment, electron fluence.
- ▌ E1004 Meo Meov2 · ashfordeou bundleUse when computing MEO trapped-radiation flux spectra and mission fluence for a medium-Earth-orbit spacecraft per ECSS-E-ST-10-04C Annex B.3: interpolate a MEOv2-style spectral model across the crossed L-shell range, apply orbit-averaging across the radiation belts, and produce differential and integral electron and proton fluence inputs for total-dose and charging analyses. Trigger: MEO trapped radiation, MEOv2 model, L-shell crossing, orbit-averaged spectrum, electron fluence, proton fluence, radiation belts, e-st-10-04, ecss.
- ▌ E1004 Meteoroid · ashfordeou bundleUse when computing the meteoroid flux environment for a mission profile under ECSS-E-ST-10-04C clause 10.2.2.2/10.2.4 and Annex C: determine which meteoroid model components apply (the Grun-type sporadic background model plus any meteoroid stream active on the mission epoch), compute the background cumulative mass flux, apply Earth-shielding geometry for Earth-orbiting cases, and combine them into the total incident flux consumed by the downstream impact-risk assessment. Trigger: ecss, e-st-10-04c, meteoroid environment, grun model, meteoroid streams, sporadic background flux, earth shielding, space environment, impact risk input.
- ▌ E1011 Cue Cards · ashfordeou bundleUse when develop cue cards for spacecraft emergency and contingency operations under ECSS-E-ST-10-11C §4.9.2: identify the scenario scope and crew task sequence, structure each card as a compact step-by-step action list within brevity and legibility limits, assign severity and scenario type, verify action steps carry imperative verbs and respect the maximum step count per card face, and confirm the complete card set covers all mandatory emergency and contingency scenarios. Trigger: ecss, e-st-10-system-scope, cue-cards, emergency-procedures, contingency-operations, crew-procedures, quick-reference, human-spaceflight.
- ▌ E1011 Iso Index · ashfordeou bundleUse when identify the applicable ISO and European standards that support an ECSS-E-ST-10-11C human factors engineering (HFE) requirement: map each HFE topic area to the relevant indexed standards (ISO 9241 series, ISO 10075, ISO 11064, ISO 14738, EN 614, EN 894), confirm every topic area in the HFE design plan has at least one indexed standard on record, and flag any topic area with no indexed standard so the coverage gap can be resolved before the HFE plan is accepted. Trigger: ecss, e-st-10-system-scope, hfe, iso-9241, iso-10075, iso-11064, human-factors, ergonomics, hfe-standards-index, annex-e.
- ▌ E1011 Mannequin · ashfordeou bundleUse when verify fit, reach, and visibility of crewed spacecraft workstations and habitable volumes using electronic mannequins and digital human models, per ECSS-E-ST-10-11C §4.5.2. Select the bounding anthropometric population percentiles (5th-female for minimum reach, 95th-male for maximum envelope), position the mannequin at each defined workstation, evaluate clearance against the required fit margin, check whether each control target lies within the functional reach envelope, and confirm each critical display falls within the accepted visibility cone without obstruction. Flag any station where fit margin, reach shortfall, or obstruction check fails. Trigger: ecss, e-st-10-11c, e-st-10-system-scope, mannequin, digital-human-model, fit-verification, reach-envelope, visibility-check, anthropometry, crewed-spacecraft.
- ▌ E1011 Verif Sim · ashfordeou bundleUse when verify human factors engineering requirements for a space system by running crew-in-the-loop simulations under ECSS-E-ST-10-11C §4.11.4: define simulation scope and acceptance criteria, recruit representative and qualified crew participants, execute integrated system simulations, measure task completion, error rate, and workload against thresholds, compare results to acceptance criteria, and produce a simulation-based HFE verification report. Trigger: ecss, e-st-10-system-scope, hfe-verification, crew-in-the-loop, simulation, task-performance, workload-assessment, human-factors.
- ▌ E1012 Bg Direct · ashfordeou bundleUse when predict the sensor background count rate produced by direct ionisation of the active detector volume by charged particles under ECSS-E-ST-10-12C §10.4.2: identify the charged particle populations (trapped protons, trapped electrons, galactic cosmic rays, solar energetic particles) at the target orbit, compute the energy deposited per crossing particle from its linear energy transfer (LET) and sensor geometry, retain only populations whose deposited energy meets or exceeds the detection threshold, accumulate the background event rate across all contributing populations using particle flux and sensor cross-section, and compare the aggregated rate against the sensor background allocation. Trigger: ecss, e-st-10-12c, sensor-background, direct-ionisation, charged-particle, let, deposited-energy, detection-threshold.
- ▌ E4008 Assembly · ashfordeou bundleValidate an SMP assembly artefact against the catalogues it instantiates, under ECSS-E-ST-40-08C clause 5.2.10 and the five normative items that clause places on the artefact. Use when an assembly has to be accepted or rejected while the simulator is still in its building state: resolving every instance to a type its declared catalogue actually supplies, keeping instance paths unique and every parent path resolvable, accepting a field value only where the type declares that field, the field is writable and the value fits the declared type and range, and counting the children of each container against its multiplicity bounds. Trigger: ecss, e-st-40-08-simulation-modelling-scope, e4008-assembly, smp-assembly-artefact, assembly-instance-resolution, assembly-field-configuration, assembly-container-multiplicity, assembly-build-verdict.
- ▌ E50 Activities · ashfordeou bundleAssess the activity set a communication system engineering step actually declares against ECSS-E-ST-50C clause 5.2.1.2, which fixes the activities of the step rather than leaving them to whatever the schedule allowed. Grade a plan on three properties at once: every required activity is declared by somebody, every declared activity both consumes an input and produces an output, and every input consumed is either available to the step or produced by a peer activity. Report coverage as a fraction with the orphans and the unsatisfiable inputs named. Use when planning or reviewing a communication system engineering process. Trigger: ecss, e-st-50-communications, communication-system-engineering-activities, communication-process-activity-coverage, activity-input-traceability, orphan-process-activity, communication-design-process-audit.
- ▌ E50 Congestion · ashfordeou bundleModel congestion on a space communication link under ECSS-E-ST-50C clause 5.3.2, which asks that offered load running above the service rate be held and drained rather than resolved by loss. Compute the backlog a burst leaves, whether the provided buffer contains it, how long an overload runs before that buffer fills, and how long the backlog takes to clear once the burst ends. Where it does not fit, report both ways out: the buffer this burst needs, and the service rate that would hold it inside the buffer already there. Use when sizing buffers or reviewing flow control on a spacecraft link. Trigger: ecss, e-st-50-communications, communication-link-congestion, link-buffer-overflow-time, offered-load-versus-service-rate, burst-backlog-sizing, link-flow-control-margin.
- ▌ E5053 Function · ashfordeou bundleAudit the function subclause of a SpaceWire service primitive against ECSS-E-ST-50-53 clause 5.2.2.1. Use when a protocol service definition needs its per-primitive purpose statements graded before baseline: confirm every declared primitive carries a function statement, measure the informative content it adds beyond the primitive name, catch a statement that only restates that name, detect parameter, generation-timing or receiver-side detail that belongs in the neighbouring subclauses, flag normative wording smuggled into an informative statement, and report two primitives sharing one statement. Trigger: ecss, e-st-50-53, service-primitive-function-subclause, primitive-purpose-statement, spacewire-service-definition, subclause-content-leakage, primitive-name-restatement, informative-statement-audit.
- ▌ Leak Tightness · ashfordeou bundleUse when determine maximum allowable leak rates for pressurized spacecraft structures and verify that the leak-tightness design meets ECSS-E-ST-32C clause 4.2.1 requirements: categorize each potential leak path by interface type (seal, penetration, weld, bond line, or fitting), apply the tightness class allowable with a design margin, check that every individual path rate and the total system rate stay within the effective limit, and document any exceedance or unrecognized path type as a finding. Trigger: ecss, e-st-32-structures-scope, leak-tightness, leak-rate, pressurized-structure, seal, pressure-vessel, leak-path.
- ▌ Pfci Screening · ashfordeou bundleUse when identify the Potentially Fracture Critical Items (PFCIs) within a structural assembly or ground support equipment (GSE) set under ECSS-E-ST-32C clause 6.1: screen each item through the Figure 6-1 decision tree by checking structural role, worst-case failure effect, tensile-load presence, material fracture susceptibility, and minimum dimension threshold; determine whether each item is a PFCI requiring fracture control or a non-PFCI; and record the first gate where non-PFCI items are screened out. GSE items engaged in critical operations are included in the screening scope. Trigger: ecss, e-st-32-structures-scope, pfci, fracture-control, structural-screening, gse, fracture-critical, pfci-list.
- ▌ Q1009 Closeout · ashfordeou bundleVerify that a nonconformance has met its close-out criteria under ECSS-Q-ST-10-09C clause 5.4.2 before the report is closed. Use when an NCR is proposed for closure, when the retained record set has to be checked against the route that was taken, or when closure signatures and retention are in question: confirm the granted disposition was carried out and checked, hold closure while a condition or an agreed action is unfinished, name the records a departure route additionally owes, and compute how long the closed report has to stay available. Trigger: ecss, q-st-10-09c, ncr-closure-criteria, disposition-verification, capa-completion-check, closure-signature-roles, retained-record-set, ncr-retention-period.
- ▌ Q1009 Database · ashfordeou bundleMaintain the nonconformance database ECSS-Q-ST-10-09 clause 5.5.2 makes a project keep, and decide whether it is doing its job. Use when nonconformances are being raised on a programme and the register behind them has to be graded before a progress review or an audit: refuse a database never opened, check each row carries its identifier, raising day, affected item, category and status, take registration coverage against the count raised rather than the rows held, catch a status that moved backwards or a closure with no disposition or evidence behind it, name the open rows past their review age, test the retrieval keys a report is built on, and say whether periodic reporting is current. Trigger: ecss, q-st-10-09-clause-5-5-2, nonconformance-database-registration-coverage, nonconformance-status-tracking-regression, nonconformance-record-retrieval-keys, nonconformance-periodic-reporting-currency.
- ▌ Q1009 Template · ashfordeou bundleEvaluate a candidate nonconformance report form against the informative template of ECSS-Q-ST-10-09 Annex C, whose headings and fields follow the normative Annex A data item. Use when a project is adopting or reviewing its default NCR form: refuse a form carrying no section for a content group the data item fixes, weigh field coverage as the mean over the groups rather than a count of fields found, measure a re-sequenced form as an inversion share against the annex order, record local additions as deviations rather than errors, and keep what the informative form permits apart from what the normative content still owes. Trigger: ecss, q-st-10-09-annex-c, ncr-report-form-heading-coverage, ncr-report-form-field-coverage, ncr-report-form-order-inversion-share, ncr-report-form-local-deviation.
- ▌ Q20 Gse Config · ashfordeou bundleMaintain configuration control over ground support equipment under ECSS-Q-ST-20C clause 5.8.2: assess whether each GSE item is identified well enough to be controlled as one unit, hold the set as a baseline, replay the change log against that baseline in order so an unapproved, out-of-sequence or version-jumping change is refused and named rather than silently absorbed, then compare the as-built result with the configuration the equipment is declared to be at. Use when GSE has drifted from its baseline and the real state has to be established. Trigger: ecss, q-st-20c-clause-5-8-2, gse-configuration-item-identification, gse-baseline, gse-change-control, gse-as-built-configuration, gse-version-sequence-break.
- ▌ Q20 Gse Design · ashfordeou bundleAudit the design, development and verification of ground support equipment under ECSS-Q-ST-20C clause 5.8.1: trace each GSE requirement up to a source requirement that actually exists and down to a verification record, compare the method a record used with the method the requirement planned, refuse a paper closure on a requirement that protects flight hardware or people, compute the closure coverage of the set, and return approved, approved-with-actions or not-approved. Use when a GSE design has to be reviewed before it goes near flight hardware. Trigger: ecss, q-st-20c-clause-5-8-1, gse-requirement-traceability, gse-verification-record, gse-verification-method-substitution, gse-closure-coverage, gse-design-review-verdict.
- ▌ Q2007 Planning · ashfordeou bundlePlan the quality and safety of a space test centre as ECSS-Q-ST-20-07 clause 5.3.2 asks, and say whether the plan in place can be run to. Use when a test centre's objectives, resourcing or management programmes are being set or audited: refuse a plan never established, name the objectives carrying no metric, no numeric target or no direction, name the ones nobody owns, take resource coverage against what the objectives require rather than against what the centre holds, find the objectives no approved programme carries, and read attainment in both directions with an exact equality settled by tolerance. Trigger: ecss, q-st-20-07-clause-5-3-2, test-centre-quality-objective-measurability, test-centre-objective-attainment-direction, test-centre-resource-planning-coverage, test-centre-management-programme-coverage.
- ▌ Q2007 Security · ashfordeou bundleAudit test-centre site security and access control under ECSS-Q-ST-20-07C clause 5.5.4. Use when a centre has to show who may enter which zone, who was inside it, and where the hardware and its data were left: decide each access request against zone tier, badge validity and authorised hours, treat the escort as the admitting party for a visitor, list every reason a request fails instead of the first, find visits signed in and never signed out, reconstruct zone occupancy, and flag items or data held below their sensitivity tier. Trigger: ecss, q-st-20-07-test-centre, q2007-security, test-centre-zone-access-tier, visitor-escort-admission-authority, test-centre-visit-signout-gap, test-item-storage-sensitivity-tier.
- ▌ Q2007 Specimen · ashfordeou bundleAssess the control a test centre keeps over a customer's test item under ECSS-Q-ST-20-07C clause 5.7.4.3: work the receipt inspection, confirm the item carries a marking unique inside the centre's register, compare the as-received build against the configuration the customer declared, weigh it against the declared mass within its allowance, list the accompanying documents that did not arrive, walk the custody chain for a handover whose receiving holder does not match the next holder, and return accept, accept against a nonconformance, or quarantine. Use when a customer item arrives at a test centre or its intake record is being audited. Trigger: ecss, q-st-20-07c-clause-5-7-4-3, test-specimen-receipt-inspection, test-specimen-unique-identification, as-received-configuration-recording, test-specimen-custody-chain, test-specimen-disposition.
- ▌ E10 Ddp Mapping · ashfordeou bundleUse when convert a heritage programme's legacy design data pack onto the ECSS document set following the ECSS-E-ST-10C Annex R mapping guidance: validate each legacy item's disposition, confirm a carried-forward item names at least one recognized ECSS target document, confirm a retired item states why and claims no target, and walk the mapping in the opposite direction to find any owed ECSS document that no legacy content feeds. Trigger: ecss, e-st-10-system-scope, legacy-data-pack, annex-r-mapping, heritage-conversion, document-set, content-retirement, coverage.
- ▌ E10 Se Planning · ashfordeou bundleUse when plan the systems engineering (SE) activities and milestones for an ECSS-E-ST-10C project: integrate each technical discipline's own plan (product assurance, verification, configuration management, software engineering, assembly/integration/verification) into the single project schedule, phase the SE activities against the canonical technical review sequence, and check that every discipline's input is delivered on or before the review milestone it feeds. Also determine when a required discipline plan is missing from the schedule and verify the review milestones themselves run in sequence. Trigger: ecss, e-st-10c, se planning, systems engineering plan, sep, milestone phasing, discipline integration, review sequence, 5.6.2.
- ▌ E1011 Hfe Role · ashfordeou bundleUse when define the Human Factors Engineering (HFE) role in a space-systems project under ECSS-E-ST-10-11C §4.3.1–4.3.2: identify required HFE task categories (requirements definition, task analysis, design support, human-machine interface definition, verification and validation, design-review participation), assign each task to a lifecycle phase, and verify that formal interfaces are established with Systems Engineering, Safety, Operations, Training, and Software Engineering. Flag any task category missing from the role definition, any mandatory interface discipline absent, and any lifecycle phase with no HFE task assigned. Trigger: ecss, e-st-10-11c, e-st-10-system-scope, hfe-role, human-factors-engineering, hfe-interface, hfe-tasks, lifecycle-phase.
- ▌ E1011 Ops Ergo · ashfordeou bundleUse when assess spacecraft operations design ergonomics under ECSS-E-ST-10C §4.6.7: evaluate each operational procedure for step-count limits, decision-branch density, and time-critical verification coverage; determine the automation level for each function given its response-time requirement and consequence severity; and verify that safety-critical commands carry sufficient independent inhibit actions. Each function is categorized into manual, supervised, or automated allocation and each finding is raised before operations documentation is finalised. Trigger: ecss, e-st-10-system-scope, operations-ergonomics, automation-allocation, error-tolerance, procedures, human-factors.
- ▌ E1011 Phys Env · ashfordeou bundleUse when assess the physical and psycho-physiological environments relevant to human performance under ECSS-E-ST-10-11C §4.2.1.6: categorize each environment parameter as physical (thermal, acoustic, vibration, lighting, or atmospheric composition) or psycho-physiological (workload, stress, sleep adequacy), verify that all required parameters have been assessed for the applicable mission phase, check each measured or predicted value against its human-performance acceptability bound, flag any parameter that falls outside the acceptable range, and confirm full coverage before closing the environment characterisation. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, physical-environment, psycho-physiological, human-performance, thermal, acoustic, vibration, illuminance, atmospheric-quality.
- ▌ E1011 Test Drd · ashfordeou bundleUse when generate and validate the Human Factors Engineering (HFE) test report against the ECSS-E-ST-10-11C Annex D Document Requirements Definition (DRD): confirm all mandatory sections are present and complete, verify participant counts meet the minimum for the test type (formative or summative), check that every finding is assigned a severity category (critical, major, or minor), confirm each finding has at least one linked recommendation, and verify that all planned test scenarios are represented in the execution record. Trigger: ecss, e-st-10-11c, hfe, human-factors, test-report, drd, findings, recommendations, usability-test.
- ▌ E1011 Timeline · ashfordeou bundleUse when build the operations timeline for a human-rated space system per ECSS-E-ST-10-11C §4.9.3: sequence each crew task in a phased timeline, compute the time-averaged workload index for each hourly assessment window, verify no window exceeds the maximum allowable workload level, confirm mandatory rest gaps are preserved between consecutive high-demand activity clusters, and check that concurrent task counts remain within the cognitive limit specified by the HFE requirement. Trigger: ecss, e-st-10-system-scope, operations-timeline, crew-workload, workload-index, human-factors, task-sequencing, rest-period, concurrent-tasks.
- ▌ E1011 User Pop · ashfordeou bundleUse when define user populations for a space system under ECSS-E-ST-10-11 §4.2.1.3: categorize each user group as crew, ground operator, or maintainer; establish capability ranges across physical, cognitive, sensory, and training dimensions for each population; verify that all design-relevant population types are covered; and flag populations with missing or internally inconsistent capability entries, or any design parameter that falls outside the target population's capability envelope. Trigger: ecss, e-st-10-system-scope, user-population, human-factors, crew, ground-operator, maintainer, capability-range, hfe.
- ▌ E1012 Bg Basis · ashfordeou bundleUse when define the sensor-background assessment basis for a space instrument under ECSS-E-ST-10-12C §10.1–10.3: identify the relevant natural radiation environments for the target orbit (trapped electrons and protons, galactic cosmic rays, solar energetic particles, albedo neutrons), map the instrument to a sensor-technology family from the standard's Table 10-1 taxonomy (silicon semiconductor, scintillator, proportional counter, solid-state germanium, CdTe/CdZnTe, neutron detector, microchannel plate), and confirm both inputs are on record before proceeding to quantitative background calculations. This leaf sets the mandatory prerequisite inputs for all downstream §10 background-flux and response calculations. Trigger: ecss, e-st-10-system-scope, background, sensor-background, radiation-environment, instrument-technology, space-instrument, background-basis.
- ▌ E1012 Bg Scint · ashfordeou bundleUse when estimate scintillation and Cerenkov background count rates in photomultiplier tubes (PMTs) and microchannel plates (MCPs) exposed to a space radiation environment under ECSS-E-ST-10-12C §10.4.6: identify the incident particle species, kinetic energy, and fluence rate; verify whether each particle exceeds the Cerenkov threshold in the detector window or substrate material; compute the Cerenkov photon yield per unit path length using the Frank-Tamm visible-band integral; add the ionisation-driven scintillation contribution; derive the total spurious background count rate; and compare the result against the detector dark-count budget to determine compliance. Trigger: ecss, e-st-10-system-scope, scintillation, cerenkov, pmt, mcp, background-rate, photon-detector, radiation-background.
- ▌ E1012 Bio Risk · ashfordeou bundleUse when run a radiobiological risk assessment for a crewed or uncrewed space mission under ECSS-E-ST-10C §11.5: estimate excess cancer risk from accumulated effective dose, categorize each uncertainty source (dosimetry, biological, model, epidemiological, transport) per the §11.5 uncertainty taxonomy, derive risk bounds using the compound uncertainty factor, and determine whether the risk estimate meets mission-acceptable limits. Trigger: ecss, e-st-10-system-scope, radiobiology, space-radiation-risk, effective-dose, cancer-risk, uncertainty-analysis, dose-response.
- ▌ E1012 See Data · ashfordeou bundleUse when compute in-orbit single-event-effect rates and degradation predictions from experimental cross-section measurements per ECSS-E-ST-10C §9.4.2: validate the four-parameter Weibull fit (saturation cross-section, threshold LET, width, shape exponent) against physical constraints, integrate the fitted cross-section curve against the mission differential LET spectrum using the trapezoidal rule to obtain the predicted in-orbit SEE rate, and compare the result against the component hardness limit to assess compliance. Reject an invalid Weibull parameter set or an unsorted LET spectrum before integration proceeds. Trigger: ecss, e-st-10-system-scope, see-data, weibull-fit, single-event-effects, cross-section, let-spectrum, see-rate-prediction, hardness-limit.
- ▌ E1012 Segr Seb · ashfordeou bundleUse when estimate destructive heavy-ion, proton, and neutron Single Event Gate Rupture (SEGR) and Single Event Burnout (SEB) rates for power devices in a space radiation environment per ECSS-E-ST-10-12C §9.4.1.6: categorize the component as power MOSFET (susceptible to both SEGR and SEB) or bipolar transistor (SEB only), fit a Weibull cross-section model to device heavy-ion test data, integrate the fitted cross-section against the orbit LET spectrum, apply the bias-derating condition appropriate to each effect, compute the predicted destructive event rate in events per device per day, and compare against the mission destructive-SEE rate requirement with a design margin. Trigger: ecss, e-st-10-system-scope, segr, seb, single-event-burnout, single-event-gate-rupture, destructive-see, weibull, power-mosfet, heavy-ion-rate.
- ▌ E1012 Tid Data · ashfordeou bundleUse when determine the total ionizing dose (TID) degradation of a component or material from experimental test records under ECSS-E-ST-10-12C §7.6–7.7: extract the dose-response curve from laboratory TID test measurements, interpolate the parameter value at the mission design dose, apply an enhanced low dose-rate sensitivity (ELDRS) correction factor when bipolar semiconductor devices are present to account for greater on-orbit degradation at lower dose rates, apply a lot-variability margin to bound the worst-case parameter value across production lots, and compare the result against the functional limit to assess TID compliance. Trigger: ecss, e-st-10-system-scope, tid, total-ionizing-dose, tid-testing, degradation-prediction, eldrs, dose-rate, lot-variability.