ashfordeOU
- 1.3k skills
- 0 followers
- 5 repo stars
- 3 days ago last updated
- ▌ E1003 El Mechanical · ashfordeou bundleUse when run element-level mechanical tests for a space hardware item under ECSS-E-ST-10C §6.5.2: categorize each test type (physical properties, modal survey, static load, spin, transient/sine-burst, acoustic, random vibration, sinusoidal vibration) into its structural or dynamic family, confirm test levels and durations are within their qualification, protoflight, or acceptance specification, enforce the required test sequence (physical-properties and modal-survey before dynamic tests), and flag any non-compliant result or missing test item. Trigger: ecss, e-st-10c, element-mechanical, modal-survey, random-vibration, sinusoidal-vibration, acoustic, physical-properties, static-load, mechanical-testing.
- ▌ E1003 Eq Acceptance · ashfordeou bundleUse when defining the acceptance test baseline for a piece of equipment under ECSS-E-ST-10-03C: derive per-test-type acceptance levels and durations from the equipment's qualification baseline and its margin/duration reduction rules, guard against an acceptance level or duration that fails to sit below its qualification counterpart, and check the baseline for coverage gaps before it is released to the test programme. Anchor: E-ST-10-03C clause 5.3 + Tables 5-3/5-4. Trigger: equipment acceptance test, acceptance test baseline, acceptance level, acceptance duration, Table 5-3, Table 5-4, e-st-10-03, ecss testing.
- ▌ E1003 Eq Electrical · ashfordeou bundleUse when scoping and running the ECSS-E-ST-10-03C equipment electrical/RF test set for one equipment item: verify test applicability (EMC, magnetic, ESD, passive intermodulation, multipactor, corona/arc discharge) from equipment risk flags, define each test's status (not applicable, missing, passed, failed), and roll up the campaign disposition (complete, incomplete, failed) before equipment qualification/acceptance sign-off. Anchor: E-ST-10-03C clause 5.5.5. Trigger: equipment electrical test, EMC test, magnetic test, ESD test, passive intermodulation, PIM test, multipactor test, corona test, arc discharge test, e-st-10-03, ecss.
- ▌ E1003 Uncertainties · ashfordeou bundleUse when verifying that a demonstrated test margin under ECSS-E-ST-10-03C still holds once measurement uncertainty is taken into account: compute the effective margin by subtracting the applicable measurement/instrumentation uncertainty (Table 4-2 typical values, overridable by project-specific characterization) from the demonstrated margin, assess whether the result is still positive, and flag any project-specific uncertainty that exceeds its Table 4-2 typical value for justification. Trigger: measurement uncertainty, instrumentation uncertainty, Table 4-2, test margin, demonstrated margin, effective margin, e-st-10-03, ecss, e-st-10c, test accuracy.
- ▌ E1004 B7 Solar Ions · ashfordeou bundleUse when deriving solar energetic particle (SEP) heavy-ion energy spectra with Z-dependent elemental abundances for single-event-effects (SEE) analysis under ECSS-E-ST-10-04C Annex B.7: derive each species' differential flux spectrum from a reference element (oxygen) spectrum, classify the SEP event type (gradual/shock-associated vs impulsive/flare-associated) from its iron-to-oxygen abundance ratio, apply the event type's elemental abundance table to scale species spectra, verify heavy-ion species coverage extends through the iron group, and identify whether the worst-case impulsive-enhanced abundance table is selected for SEE. Trigger: solar energetic particle, SEP heavy ion, Annex B.7, Z-dependent abundance, iron-rich event, Fe/O ratio, heavy ion spectrum, SEE analysis, e-st-10-04, ecss, space environment, radiation environment.
- ▌ E4008 Link General · ashfordeou bundleVerify the general rules every link in an SMP Level-2 assembly artefact obeys before its kind-specific typing is reached, per ECSS-E-ST-40-08C clause 5.2.7.1: each link name is a valid identifier and unique in the assembly, the declared kind is interface, event or field, both endpoints resolve onto a declared instance by longest-path match with an element left over, no endpoint dangles or reaches outside the assembly scope, the same kind-source-target triple is not declared twice, and an instance is not joined to itself. Use when an assembly fails to connect, a link silently does nothing, or a whole link set needs grading. Trigger: ecss, e-st-40-08c, smp-level-2, assembly-link-set, link-endpoint-resolution, duplicate-link-detection, dangling-link-endpoint, assembly-link-naming.
- ▌ E50 Data Labelling · ashfordeou bundleValidate the label a space communication system puts on the data it carries, per ECSS-E-ST-50C clause 5.8.2, which asks that data be labelled well enough for a receiver to recover its identity from the unit alone. Compare the declared fields against source, destination, data type, sequence and generation time; size each identifier field in whole bits against the things it has to name; find whether the sequence counter wraps inside the window where two units must stay distinguishable; and price the label against the payload. Use when sizing a header or reviewing a data unit format. Trigger: ecss, e-st-50c-clause-5-8-2, space-data-unit-labelling, label-field-width-sizing, sequence-counter-wrap-ambiguity, label-overhead-fraction, source-and-destination-identifier-capacity.
- ▌ E50 Directionality · ashfordeou bundleVerify the declared directionality of a space link under ECSS-E-ST-50C Rev.2 clause 5.6.2. Use when the task is deciding whether a link declared forward-only, return-only or bidirectional carries every direction its allocated services need, whether a bidirectional link has stated simultaneous or alternating operation, whether a two-way service that needs both directions open at once has been placed on an alternating link, and whether the turnaround and propagation terms leave the two-way response time inside its allowance. Trigger: ecss, e-st-50c, space-link-directionality, forward-link-direction, return-link-direction, bidirectional-space-link, alternating-link-turnaround, two-way-response-time, service-direction-allocation.
- ▌ E5053 Ccsds Packet · ashfordeou bundleValidate the CCSDS packet a SpaceWire transfer protocol carries and size the frame around it. Use when an ECSS-E-ST-50-53C clause 5.1.1 packet is built or read back: normalise the six primary-header fields, pack them into header bytes and unpack a capture back into the same record, turn the data-field size into the length field and back, size the packet and the frame that adds routing and the protocol byte, split a user datum too large for one data field into a grouped sequence, and check the counter advanced. Flags fill traffic carrying a grouped sequence or a secondary header, and a frame over the profile maximum. Trigger: ecss, e-st-50-53c, ccsds-space-packet-header, ccsds-packet-length-field, ccsds-grouping-flags, ccsds-sequence-counter-continuity, spacewire-protocol-identifier-byte, ccsds-idle-application-identifier.
- ▌ E5053 Packet Field · ashfordeou bundleValidate the packet field that closes a packet transfer protocol data unit. Use when an ECSS-E-ST-50-53C clause 5.3.6 unit has to be checked against the packet it claims to carry: fix the field offset from the path length, read the six-octet primary header, take the declared total length from the header's own length count rather than from the transfer protocol, and compare it with the octets actually present. Report a complete packet, a truncation with its shortfall, an overrun with the trailing octets that belong to no packet, or a field beyond the link limit, then separate the single packet from anything following it. Trigger: ecss, e-st-50-53c, spacewire-packet-field, space-packet-primary-header, packet-field-truncation, packet-field-overrun, self-delimiting-packet-length.
- ▌ E5053 Send Request · ashfordeou bundleValidate a send request handed to the SpaceWire CCSDS packet transfer entity under ECSS-E-ST-50-53C clause 5.5.2, against its three obligations at once: the destination resolves to a usable logical address or a path of output ports, the request carries exactly one complete CCSDS packet whose declared length matches the octets supplied, and the encoded transfer with its address, protocol identifier and reserved octet fits the transmit limit so an over-long request is refused rather than truncated on the link. Use when issuing or reviewing CCSDS send requests over SpaceWire. Trigger: ecss, e-st-50-53c, spacewire-send-request, spacewire-logical-address, spacewire-path-address, ccsds-transfer-encoding, max-transfer-unit-refusal, send-primitive-parameters.
- ▌ E7041 File Systems · ashfordeou bundleDefine and audit the on-board file system model every other file management request is addressed against, under ECSS-E-ST-70-41C clause 6.23.5.1. Use when ground paths will not resolve against a spacecraft and the declaration itself is suspect: deciding flat against hierarchical, resolving an object only as a repository path plus a name within it, enforcing the declared separator, name charset, octet caps and depth at the identifier, and catching declarations that contradict themselves — flat with a depth above one, a separator inside the permitted charset, a depth unreachable within the path cap, or case-folded names that alias two ground objects onto one. Trigger: ecss, e-st-70-41c, pus-file-management, on-board-file-system-model, flat-versus-hierarchical-repository, repository-path-plus-file-name, file-name-octet-cap, case-insensitive-name-aliasing.
- ▌ E7041 Packet Store · ashfordeou bundleModel what an on-board packet store does with each telemetry packet offered to it under ECSS-E-ST-70-41C clause 6.15.3.1. Use when the task is choosing between a bounded and a circular packet store, or explaining which packets a full one lost: tracking occupancy against capacity in octets, discarding while storage is switched off, holding the oldest record in a bounded store and overwriting it in a circular one, refusing an overwrite that would tear a hole in a retrieval the ground is still reading out, and reporting fill, losses and the oldest and newest packet held. Trigger: ecss, e-st-70-41c, pus-packet-utilisation, on-board-packet-store, circular-packet-store-overwrite, bounded-packet-store-full, packet-store-storage-state, open-retrieval-overwrite-protection.
- ▌ Fci Classification · ashfordeou bundleUse when determine whether a structural item qualifies as a fracture-critical item (FCI) under ECSS-E-ST-32-01C clause 6.2.2: evaluate each candidate item against the pressurized-system criterion, the fracture-limited life item (FLLI) criterion, the NDT-limited criterion, and the composite primary-structure criterion; assign the applicable FCI category or none; and produce a determination with rationale traceable to the failure-consequence level (catastrophic, critical, or non-critical). Trigger: ecss, e-st-32-structures-scope, fracture-critical-item, fci, flli, pressure-vessel, composites, ndt-limited, fracture-control.
- ▌ Q20 Gse Acceptance · ashfordeou bundleEvaluate the acceptance of ground support equipment under ECSS-Q-ST-20C clause 5.8.4.2: grade each acceptance result against the agreed GSE requirement it answers, keep the measured margin rather than only the verdict, refuse a reported pass whose own measurement misses the bound, insist that a safety-critical requirement be shown by test or inspection instead of argued on paper, compute acceptance coverage over the requirement set, and separate a failure carried on an approved waiver from one that stops the equipment. Use when GSE has finished its acceptance campaign and someone has to say whether it may be used. Trigger: ecss, q-st-20c-clause-5-8-4-2, gse-acceptance-test-grading, gse-acceptance-margin, gse-acceptance-coverage, gse-waivered-limitation, gse-release-for-use.
- ▌ Q20 Gse Production · ashfordeou bundleEvaluate the production of a ground support equipment item under ECSS-Q-ST-20C clause 5.8.3: grade each bought-in lot on supplier approval state, incoming inspection, conformity evidence and lot traceability, apply the surveillance a conditionally approved supplier owes, replay the manufacturing, assembly and integration operations in sequence against process qualification and operator certification validity, check every mandatory inspection point for completion and the right witness, and return released, released-with-actions or held. Use when a GSE build is up for release. Trigger: ecss, q-st-20c-clause-5-8-3, gse-procurement-assurance, gse-supplier-surveillance, gse-mandatory-inspection-point, gse-process-qualification-validity, gse-build-release-verdict.
- ▌ Q20 Test Equipment · ashfordeou bundleVerify that the equipment a test is about to be run with satisfies the quality assurance control ECSS-Q-ST-20 clause 5.6.2 places on it, electrical ground support equipment included. Use when a test readiness review or a set-up check falls due: judge calibration at the day of use rather than the day of the audit, refuse a due day contradicting the calibration interval, weigh the uncertainty carried against the tolerance being judged as an accuracy ratio, keep a guard band at each end of the instrument span, refuse an unapproved change to the build standard, and hold equipment whose self-test or functional check has gone stale. Trigger: ecss, q-st-20-clause-5-6-2, test-equipment-calibration-validity-at-use, test-equipment-accuracy-ratio, egse-configuration-control, test-equipment-readiness-window.
- ▌ Copc Metallic Liner · ashfordeou bundleUse when verify a composite overwrapped pressure container (COPC) with metallic liner per ECSS-E-ST-32 clause 4.5.2: confirm the liner remains elastic at proof pressure, compute the margin-of-safety on liner hoop stress at maximum expected operating pressure, validate proof and burst pressure factors against required minimums, demonstrate leak-before-burst by confirming the fracture-mechanics critical flaw depth exceeds the liner wall thickness, and check the fatigue-cycle budget against a cycle-life scatter factor of at least four before pressurised qualification is declared. Trigger: ecss, e-st-32-structures-scope, copc, metallic-liner, pressure-vessel, leak-before-burst, fatigue-cycle-budget, fracture-mechanics, proof-pressure, burst-factor.
- ▌ Cops Metallic Liner · ashfordeou bundleUse when assess the structural response of a COPS (Composite Overwrapped Pressure Structure) with metallic liner under ECSS-E-ST-32C §4.4.3: compute the hoop strain shared between the liner and composite overwrap via the compatibility condition, determine the stress state in each component at design pressure, check the liner against yielding, verify the composite against its hoop allowable, account for ring stiffener contributions to shell stiffness, and confirm the burst pressure margin satisfies the required factor of safety. Trigger: ecss, e-st-32-structures-scope, cops, composite-overwrapped-pressure-structure, metallic-liner, stiffened-shell, liner-interaction, burst-pressure, load-sharing.
- ▌ Copv Metallic Liner · ashfordeou bundleUse when verify a Composite Overwrapped Pressure Vessel (COPV) with metallic liner under ECSS-E-ST-32-02C §4.3.3: determine liner hoop stress at MEOP, confirm proof and burst pressure factors meet minimum requirements, evaluate fatigue-life of the metallic liner against scatter-factored design cycle count, assess composite overwrap fiber stress at burst via netting theory, and check liner yield limits at proof. Covers titanium, aluminium, and Inconel liners, autofrettage detection, margin-of-safety computation, and consolidated compliance reporting. Trigger: ecss, e-st-32-structures-scope, copv, metallic-liner, composite-overwrap, pressure-cycle-fatigue, proof-pressure, burst-pressure, pressure-vessel.
- ▌ Drd Stress Strength · ashfordeou bundleUse when produce a structural stress and strength analysis report under ECSS-E-ST-32C Annex K: identify each structural element and its applicable load cases (limit, yield, ultimate), apply the required factors of safety, compute the margin of safety for every load-case/element pair, flag any negative margin, and verify the analysis document package contains all DRD-mandated content items. Trigger: ecss, e-st-32-structures-scope, stress-analysis, strength-analysis, margin-of-safety, factors-of-safety, structural-elements, drd-stress-strength, load-cases, material-allowables.
- ▌ Drd Test Evaluation · ashfordeou bundleUse when evaluate test results against predictions for a structural test campaign under ECSS-E-ST-32C Annex P: verify each test objective is met, compare measured responses to predicted values within the approved tolerance, assess all anomalies encountered and confirm their disposition, check post-test article condition, and produce the pass/reject conclusion for the test evaluation report. The procedure covers static, dynamic, acoustic, and thermal test types. Trigger: ecss, e-st-32-structures-scope, test-evaluation, test-prediction, test-objectives, anomaly-disposition, test-article-condition, structural-test-campaign.
- ▌ E1002 Pretailoring · ashfordeou bundleUse when apply the ECSS-E-ST-10-02C §6 pre-tailoring matrix to a space product type: determine the applicability level (applicable, recommended, optional, or not applicable) for each clause-5 verification requirement for the product category under assessment, identify every applicable requirement that must be covered, flag any applicable verification requirement absent from the project's captured requirement set, and produce the per-requirement applicability record for engineering review. Product categories cover space system, segment, equipment, and payload. Trigger: ecss, e-st-10-02c, pretailoring, verification-matrix, product-type, verification-requirements, clause-5, requirements-applicability.
- ▌ E1002 Vcd Closeout · ashfordeou bundleUse when closing out the Verification Control Document (VCD) per ECSS-E-ST-10C §5.4.4.1: determine the compliance status of each verifiable requirement as compliant, not compliant, or waived; collect every linked verification record (test report, analysis report, inspection record, review-of-design output); assign compliant when all records are passed or not applicable, not compliant when any record is open or failed and no approved waiver is on file, and waived when a formal approved waiver document reference is recorded against the requirement. Flag rows with no verification evidence, open records blocking closeout, and failed records without an approved waiver reference. Produce a VCD closeout summary with counts by status and a list of all blocking findings. Trigger: ecss, e-st-10-system-scope, vcd-closeout, verification-control-document, compliance-status, waiver, verification-records, requirement-closeout.
- ▌ E1003 Test Reviews · ashfordeou bundleUse when perform test readiness reviews and close-out reviews for a spacecraft test campaign under ECSS-E-ST-10C §4.3.2: verify each review has defined entry criteria grouped as mandatory or advisory, determine the outcome (pass, conditional pass, or fail) from which criteria are met, confirm all test anomalies carry a disposition before close-out, and ensure every review produces a complete record capturing review type, chair, attendees, criteria verdicts, outcome, and open action items. Apply the Test Readiness Review to gate entry to testing and the close-out review to gate release of results. Trigger: ecss, e-st-10-system-scope, test-readiness-review, close-out-review, review-criteria, anomaly-disposition, test-records, review-outcome.
- ▌ E1004 Annex A Data · ashfordeou bundleUse when assembling the natural electromagnetic radiation and solar/geomagnetic index reference dataset from ECSS-E-ST-10-04C Annex A for a mission design case: determine which quantities (TSI, EUV/XUV band irradiance, Earth albedo, Earth IR emission, F10.7, F10.7A, geomagnetic index) apply, verify each quantity's solar-cycle phase tagging and that phase-dependent values ordered minimum/mean/maximum, and flag missing quantities, missing phases, or phase-tagging errors before the dataset feeds e1004-em-radiation or e1004-indices. Trigger: Annex A, natural EM radiation data, solar/geomagnetic indices, F10.7, F10.7A, Ap, Kp, TSI, solar constant, solar-cycle reference values, Earth albedo, Earth IR emission, e-st-10-04, ecss.
- ▌ E1004 Annex C Flux · ashfordeou bundleUse when computing meteoroid background flux and meteor-shower stream enhancement for a space mission per ECSS-E-ST-10-04C Annex C: apply the Grün interplanetary flux model, add meteor-stream enhancement tables for known shower epochs, and apply Earth shielding and gravitational focusing corrections for near-Earth orbits to produce the meteoroid environment input for impact risk assessment. Trigger: meteoroid flux, Grün model, meteor stream, shower enhancement, Earth shielding, gravitational focusing, impact risk, e-st-10-04, ecss.
- ▌ E1004 Em Radiation · ashfordeou bundleUse when you must define a mission's natural electromagnetic radiation environment per ECSS-E-ST-10-04C clause 6.2: assemble the solar spectrum bands (XUV through IR and solar radio), scale total solar irradiance (TSI) to the mission's heliocentric distance, and combine planetary albedo and infrared emission into the incident EM flux a spacecraft must design against. Trigger: electromagnetic radiation environment, solar spectrum, TSI, total solar irradiance, solar radio, planetary albedo, planetary IR, earth albedo, e-st-10-04c 6.2.
- ▌ E1004 Rad Env Spec · ashfordeou bundleUse when producing the radiation environment specification (RES) required by ECSS-E-ST-10-04C clause 9.3 for a space mission: determine which radiation environment components (trapped radiation, solar energetic particles, galactic cosmic rays, internal-charging worst-case spectra, trapped-proton worst-case spectra, atmospheric albedo neutrons) apply to each orbit segment, verify that the RES states the model choice, basis (long-term-average vs. worst-case), and uncertainty for every applicable component, and flag missing sections or missing uncertainty statements before the RES is closed out. Trigger: radiation environment specification, RES, e-st-10-04, ecss, per-orbit radiation data, model choice, worst-case spectrum, radiation uncertainty.
- ▌ E1004 Sep Peakflux · ashfordeou bundleUse when you must compute solar energetic particle (SEP) peak proton fluxes with JPL-type worst-case models for single event effect (SEE) worst-case analyses per ECSS-E-ST-10-04C: confirm the analysis purpose actually needs a peak-flux (not fluence) model, pick the standard proton energy channel that covers the device's SEE sensitivity threshold, compute the worst-case integral peak flux at the chosen confidence level, and check the worst-case window is a short high-intensity period rather than a mission-duration integration. Produces the peak-flux applicability verdict, the selected energy channel, the computed peak flux, and the worst-case window classification. Trigger: sep peak flux, solar particle peak flux, jpl model, see worst case, single event effect worst case, proton peak flux, e-st-10-04c 9.2.2.3.
- ▌ E1011 Hcd Planning · ashfordeou bundleUse when plan the human-centred design (HCD) process for a space system or product under ECSS-E-ST-10-11C §4.4.1–4.4.2: identify every HCD activity required by Annex A (context-of-use analysis, user requirements specification, design solution, evaluation, implementation verification), assign each activity to an ECSS project phase (0 through F), allocate at minimum one HF specialist as the responsible party per activity, and confirm the resulting HCD plan covers all mandatory activities with no phase-order violations. Trigger: ecss, e-st-10-system-scope, hcd-planning, human-centred-design, hfe, hcd-plan, annex-a, project-phases, responsibilities.
- ▌ E1011 Training Req · ashfordeou bundleUse when define training requirements and materials for operator tasks derived from operational products under ECSS-E-ST-10-11C §4.9.5: determine the training need tier for each task from task complexity, procedural novelty, and safety criticality (routine / standard / enhanced / specialized); verify that the minimum required training materials exist for the assigned tier; confirm that every personnel role performing the task holds a training assignment before first operational use; and assess whether available training time and scheduling window meet the tier minimum. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, training-requirements, training-need-assessment, training-materials, personnel-roles, human-factors-engineering, hfe.
- ▌ E1011 Users Manual · ashfordeou bundleUse when define the users manual for a human-rated space system under ECSS-E-ST-10-11C §4.3.4: verify that all required HFE input sections are present (user population, task procedures, interface description, error recovery, mission-phase applicability, training requirements), validate each task procedure's steps against applicable mission phases, confirm that safety-critical steps carry a warning note, verify that every task procedure with safety-critical steps has a linked error-recovery entry, and check that user-population entries carry skill level, physical constraints, cognitive load limits, and operating language. Trigger: ecss, e-st-10-11c, e-st-10-system-scope, users-manual, hfe-inputs, task-procedures, error-recovery, human-factors-engineering.
- ▌ E1011 Workstations · ashfordeou bundleUse when assess workstation layout and human-factors design for a crewed spacecraft under ECSS-E-ST-10-11C §4.7.6: verify display placement within acceptable viewing angles from the crew Eye Reference Point, verify controls fall within the reach envelope for their access-frequency zone (primary, secondary, or tertiary), and verify ingress/egress clearance dimensions meet minimum crew-access requirements. Categorize each workstation element by access-frequency zone, flag any element outside its zone's viewing or reach limits, and confirm every access path meets clearance minimums. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, workstation, human-factors, viewing-angle, reach-envelope, ingress-egress, layout.
- ▌ E1012 Dose Effects · ashfordeou bundleUse when assessing radiation dose-effects margin compliance for electronic components under ECSS-E-ST-10 §5.5.2: apply the radiation design margin factor to the predicted component dose, compare the result against each component's specified tolerance, check parametric degradation limits (gain, leakage current, threshold voltage) against allowable change fractions, verify functional continuity at the margin-multiplied dose, and flag every component that fails a dose, parametric, or functional limit. Trigger: ecss, e-st-10-system-scope, dose-effects, radiation-design-margin, total-ionizing-dose, parametric-degradation, functional-degradation, component-tolerance.
- ▌ E1012 See Env Tech · ashfordeou bundleUse when define SEE-relevant mission orbit environments and electronic technology susceptibility profiles under ECSS-E-ST-10-12C §9.2–9.3: categorize the mission orbit as LEO, MEO, GEO, HEO, interplanetary, or lunar to determine the dominant particle population (trapped protons, heavy ions, galactic cosmic rays, solar particle events), map each candidate technology (CMOS, BiCMOS, SRAM, DRAM, Flash, FPGA, power MOSFET, linear bipolar) to its applicable SEE types (SEU, SET, SEFI, SEL, SEB, SEGR), and flag technologies with destructive SEE risk requiring protective controls. Trigger: ecss, e-st-10-system-scope, see, single-event-effects, orbital-environment, technology-susceptibility, sel, seb, segr, seu, table-9-1.
- ▌ E1012 See Hardness · ashfordeou bundleUse when run SEE hardness assurance for a space electronic device under ECSS-E-ST-10-12C §9.5: determine the device's susceptibility to ion-induced and proton/neutron-induced single-event effects, predict the on-orbit SEE rate using device cross-section parameters and the mission particle spectrum, compare the predicted rate against the allowed-error-rate requirement, and assign the hardness assurance category that sets acceptance testing and lot-screening obligations. Trigger: ecss, e-st-10-system-scope, see, single-event-effect, seu, sel, seb, see-rate, hardness-assurance, ion-environment, proton-neutron.
- ▌ E1024 Eicd Element · ashfordeou bundleUse when produce EICDs for space segment elements under ECSS-E-ST-10-24C §5.8.3: categorize each interface by type (element-to-element or element-to-launcher), verify that all required identification fields are populated, confirm characteristic coverage across the applicable physical media families (mechanical, electrical, thermal, data, RF), and cross-check that every interface characteristic entry carries at least one linked verification provision. Flag EICDs with missing fields, unrecognized interface types, uncovered characteristic families, or characteristics lacking verification linkage. Use across all space segment element boundary interfaces throughout the EICD preparation and review lifecycle. Trigger: ecss, e-st-10-system-scope, eicd, element-interface, element-to-launcher, interface-control-document, interface-identification, verification-linkage.
- ▌ E1024 Requirements · ashfordeou bundleUse when structure interface requirements for an Interface Requirements Document (IRD) per ECSS-E-ST-10-24C §5.3: categorize each requirement as functional, physical, environmental, or data-characteristic, verify that every requirement carries a unique identifier, text, rationale, and verification method, check that each interface is covered across all four mandatory requirement categories, and flag incomplete or missing coverage. Applicable at any level where two items exchange signals, mechanical loads, thermal energy, or data streams. Trigger: ecss, e-st-10-system-scope, ird, interface-requirements, functional-requirements, physical-requirements, environmental-requirements, data-characteristics.
- ▌ E5053 Status Code · ashfordeou bundleEvaluate the status code a sending node writes into a CCSDS packet transfer protocol data unit on SpaceWire under ECSS-E-ST-50-53C clause 5.1.3: check the encoding fits the one octet field, group it against the deployment code assignment as success, a defined error, user-defined, unassigned or reserved, decide whether the receiving node accepts, reports or rejects the transfer, and summarise a run of received codes. Use when a receiver meets a status encoding it did not expect. Trigger: ecss, e-st-50-53-spacewire-ccsds-scope, ccsds-transfer-status-code, reserved-status-encoding, unassigned-status-encoding, transfer-error-reporting, status-code-registry.
- ▌ E7041 Obcp Engine · ashfordeou bundleEvaluate whether an on-board control procedure engine can take another procedure under ECSS-E-ST-70-41C clause 6.18.2.3, where the engine is a bounded execution environment and not an unlimited interpreter. Use when the task is validating an engine capability declaration and then admitting or refusing a load or a start against the supported procedure language and version, the code and data footprint versus the engine store, the concurrently loaded and concurrently running limits, and the per-cycle step budget the already running set consumes, then reporting engine utilisation with a named reason for every refusal. Trigger: ecss, e-st-70-41c, obcp-engine-capability, obcp-load-admission, obcp-concurrency-limit, obcp-step-budget-per-cycle, obcp-engine-store-footprint, obcp-engine-utilisation.
- ▌ Modal Survey Test · ashfordeou bundleUse when execute a modal survey test on a spacecraft structural assembly to identify natural frequencies, damping ratios, and mode shapes; validate the finite element model by computing the Modal Assurance Criterion for each test-prediction mode pair and flagging pairs below the acceptance threshold; verify each identified frequency falls within the allowable tolerance of its predicted counterpart; confirm the measurement point configuration covers all target modes; and flag any damping estimate outside the physically plausible structural range or any target mode without a measured counterpart. Trigger: ecss, e-st-32-structures-scope, modal-survey-test, natural-frequency, mode-shape, mac, damping-ratio, frequency-response-function, fem-validation, model-correlation.
- ▌ Ph Classification · ashfordeou bundleUse when determine the pressure hardware category of a spacecraft or launch vehicle hardware item per ECSS-E-ST-32 clause 4.1: assign each item as a Pressure Vessel (PV), Pressure System (PS), Pressure Container (PC), or Simple Pressure Equipment (SPE) using the figure 4-1 through 4-3 decision criteria; apply SPE simplicity thresholds for pressure level, internal volume, geometry, material, and heat source; resolve multi-component assemblies as pressure systems with individually categorized sub-items; flag items that carry primary structural loads concurrently with pressure retention. Trigger: ecss, e-st-32-structures-scope, pressure-hardware, pressure-vessel, pressure-system, pressure-container, spe, ph-classification.
- ▌ Q2007 Environment · ashfordeou bundleEvaluate test-centre infrastructure suitability and work-environment control, ECSS-Q-ST-20-07C clauses 5.5.1-5.5.2. Use when a facility has to show it can hold the environment a test asks for and then that it did: check the declared capability band contains the required band for temperature, humidity, supply voltage and frequency, purge media and coolant, report the containment margin at each end, derive power-quality bands from nominal plus percentage tolerance, count monitored excursions with side and magnitude, time the longest unbroken one, and flag sampling too slow to see it. Trigger: ecss, q-st-20-07-test-centre, q2007-environment, test-facility-capability-band-containment, test-centre-environmental-excursion, power-quality-tolerance-band, environmental-monitoring-interval-adequacy, test-centre-media-purity-control.
- ▌ Q40 Analyses Mgmt · ashfordeou bundleDetermine the safety analysis suite an ECSS-Q-ST-40C clause 7.2 to 7.4 programme owes at a given lifecycle phase, reading the Annex A applicability matrix: resolve which analyses are mandatory and which only recommended, degrade an analysis to recommended where the worst severity carried sits below its floor, compare the resolution with the declared plan to expose missing analyses, analyses the phase has no use for and analyses due after the phase review, and report the coverage achieved. Use when an analysis plan is drafted, tailored for a phase, or audited before a project review. Trigger: ecss, q-st-40c, annex-a-analyses-applicability-matrix, safety-analysis-suite-selection, lifecycle-phase-analysis-set, safety-analysis-plan-gap, mandatory-safety-analysis.
- ▌ Q7002 Test Report · ashfordeou bundleDocument the conditions, results and uncertainties of a thermal-vacuum outgassing screening run in the reporting format of ECSS-Q-ST-70-02C, or grade a report already issued. Use when a run is finished and the record must state the material tested, the conditions achieved, the values obtained and their uncertainty. Checks identification to batch and processing state, grades every recorded condition against its window, pairs an out-of-window condition with a recorded deviation, combines the uncertainty components in quadrature, expands them by the declared coverage factor, and matches value resolution to uncertainty. Trigger: ecss, q-st-70-02, outgassing-test-report, outgassing-test-conditions-window, outgassing-uncertainty-budget, expanded-uncertainty-coverage-factor, out-of-window-test-deviation, outgassing-reporting-resolution.
- ▌ Q7006 Test Report · ashfordeou bundleDocument the environment, exposure, results and uncertainties of a particle or UV radiation test under ECSS-Q-ST-70-06C, or grade a report already issued. Use when a run is finished and the record has to state what the specimen was in, how much it received, what the properties did and how well any of it is known. Checks identification and dosimetry traceability, requires every exposure as planned and achieved, grades the relative deviation and pairs an out-of-tolerance value with a note, reports the dose-rate acceleration against the mission, holds ultraviolet irradiance and chamber pressure to their ceilings, and combines uncertainty components in quadrature. Trigger: ecss, q-st-70-06, radiation-test-report, dosimetry-traceability, planned-versus-achieved-exposure, dose-rate-acceleration-factor, uv-equivalent-sun-hours, radiation-uncertainty-budget.
- ▌ Q7029 Test Report · ashfordeou bundleDocument an offgassing test under ECSS-Q-ST-70-29 by assembling the report and checking it holds together: the article and run identification, the product inventory, the concentration table, the toxicity and odour assessments and the stated conclusion, with every product cross-checked across the three tables and every stated total recomputed from the rows it claims to summarise. Use when a completed offgassing campaign must become a traceable report and a conclusion that contradicts its own tables has to be caught before issue. Trigger: ecss, q-st-70-29, offgassing-test-report, offgassing-report-traceability, offgassing-table-cross-check, offgassing-total-recomputation, offgassing-conclusion-consistency, crew-compartment-offgassing.
- ▌ Q7053 Test Report · ashfordeou bundleDocument the cycles, degradation data and conclusion of an ECSS-Q-ST-70-53C sterilization-compatibility test, or grade a report already issued. Use when an exposure campaign is finished and the record has to stand on its own for a reviewer who was not there. Checks identification down to batch and process, matches the logged cycles against the planned count, catches a gap or a repeat in the cycle numbering, grades each achieved parameter against its window, pairs an out-of-window value with a recorded deviation, flags a deviation recorded against nothing, requires a pre and a post value for every declared property, and tests the stated conclusion against the data behind it. Trigger: ecss, q-st-70-53-sterilization-compatibility-scope, sterilization-compatibility-test-report, exposure-cycle-log-completeness, achieved-cycle-parameter-window, out-of-window-cycle-deviation, report-conclusion-consistency.
- ▌ E10 Coordsys Units · ashfordeou bundleUse when engineering data across an ECSS-E-ST-10C programme (system level) needs to be checked for consistent use of reference coordinate systems per E-ST-10-09 and SI units, before it is exchanged between disciplines, suppliers, or verification/operations teams. Trigger: coordinate system, reference frame, SI units, unit consistency, coordinate systems document, CSD, E-ST-10-09, frame consistency, ecss, e-st-10c.
- ▌ E10 Design Budgets · ashfordeou bundleUse when allocate technical budgets (mass, power, data rate, link, pointing, thermal, or any other quantifiable design resource) for a space system under ECSS-E-ST-10C clause 5.4.1.2 and Annex I: determine the minimum required margin for the project's current life-cycle phase, track each item's current best estimate against its allocation and the phase's required margin, verify that sub-item allocations sum within the parent system-level allocation, and check the system-level margin on the summed current best estimates. Trigger: ecss, e-st-10c, technical budget, margin philosophy, budget allocation, current best estimate, mass budget, power budget, margin management, maturity margin.
- ▌ E10 Design General · ashfordeou bundleUse when conduct and document a product's design against its allocated Technical Requirements Specification under ECSS-E-ST-10C clause 5.4.1.1: confirm every allocated requirement is covered by at least one design definition item, confirm every design item traces back to a known requirement, and confirm every design decision records the alternatives considered, the option selected and the rationale for selecting it, then decide whether the product's design is complete for the assessment. Trigger: ecss, e-st-10-system-scope, design-definition, design-decision, technical-requirements-specification, requirement-coverage, design-traceability, design-rationale.
- ▌ E10 Design Methods · ashfordeou bundleUse when select and validate the design methods, tools and models behind a design output under ECSS-E-ST-10C clause 5.4.1.3: separate model-based methods from rule-based ones, establish each model's validation status against the domain of applicability of the present design case, weight the confirmation each model contributes and compare the total against the threshold in the method selection plan, and confirm a recorded rationale exists wherever a design rule is applied outside its documented precedent. Trigger: ecss, e-st-10-system-scope, design-methods, model-validation, domain-of-applicability, design-rules, heritage-precedent, confirmation-weight.
- ▌ E10 Req Allocation · ashfordeou bundleUse when allocating requirements to functions and to product-tree elements (configuration items) under ECSS-E-ST-10C: run functional analysis to establish the function tree, allocate each requirement to the function(s) it drives, allocate each requirement to the configuration item(s) that implement it, and check allocation completeness (no unallocated requirement, no orphan function or element) before the requirement baseline is frozen. ECSS-E-ST-10C clause 5.2.3.5 governs requirement allocation as part of system engineering requirement flow-down. Trigger: ecss, e-st-10c, requirement allocation, functional analysis, product tree, configuration item, function tree, 5.2.3.5, space systems engineering.
- ▌ E1002 Post Landing · ashfordeou bundleUse when an element's mission profile includes physical return of hardware to Earth (descent capsule, sample-return canister, recoverable payload, splashdown-recovered stage) and the post-landing verification stage of ECSS-E-ST-10-02C must be run: confirm applicability, assess each recovered item's condition against its pre-flight baseline, flag safety-critical findings, and track items that could not be recovered for alternate evidence. Trigger: post-landing verification, recovery, returned hardware, descent capsule, sample return, splashdown, recovered payload, E-ST-10-02, ecss, e-st-10c.
- ▌ E1004 Ref Gravity · ashfordeou bundleUse when defining Earth and third-body gravitational reference constants (GM, J2 oblateness coefficient) per ECSS-E-ST-10-04C Annex A for a space mission: compute point-mass, J2 zonal-harmonic, and third-body tidal perturbation accelerations at a given orbit radius, and determine which gravity-model terms the mission's environment specification must carry for the orbit regime and mission duration. Trigger: gravity constants, GM, J2 oblateness, zonal harmonic, third-body tidal acceleration, gravity environment specification, e-st-10-04, ecss.
- ▌ E1004 Ref Indices · ashfordeou bundleUse when selecting solar-activity and albedo/IR reference data for a space-environment case under ECSS-E-ST-10-04C Annex F (informative): determine the solar-cycle activity level (minimum/mean/maximum) that a case should assume from its F10.7 solar-flux value, look up the reference index set (F10.7 flux, sunspot number) and the Earth albedo/IR flux references for that level, validate a proposed index value against the dataset's valid range, interpolate an index across the solar-cycle phase when a cycle-phase fraction is given, and produce the combined solar-index plus albedo/IR reference record that a thermal or radiation case must cite. Trigger: ecss, e-st-10-04c, annex f, solar index, f10.7, sunspot number, solar cycle, albedo, earth ir, reference data, activity level, thermal case.
- ▌ E1004 Sep Fluence · ashfordeou bundleUse when you must compute solar proton fluences for a mission's radiation environment using the ESP model per ECSS-E-ST-10-04C clause 9.2.2.2 and Annex B.6: select the confidence level and mission duration, compute the cumulative fluence spectrum across energy thresholds, and verify the fluence is monotonically consistent with duration, confidence level and energy threshold before it feeds the radiation environment specification. Trigger: solar proton fluence, ESP model, solar particle event fluence, confidence level, mission duration, sep fluence, e-st-10-04c 9.2.2.2, annex b.6.
- ▌ E1004 Trapped Leo · ashfordeou bundleUse when computing the trapped radiation electron environment for a LEO spacecraft per ECSS-E-ST-10-04C 9.2.1.2: apply AE-8/AE-9-class flux tables indexed by McIlwain L-shell and B-L (B/B0) coordinates, include the South Atlantic Anomaly dose contribution, and produce the differential and integral electron flux inputs for total-dose and internal-charging assessments of the spacecraft. Trigger: trapped electrons, LEO radiation environment, AE-8, AE-9, McIlwain L-shell, B-L coordinates, South Atlantic Anomaly, electron flux, e-st-10-04, ecss.
- ▌ E1009 Authorities · ashfordeou bundleUse when identify the appropriate international standards authority for a space mission's time scale, reference frame, ephemeris, geodesy, or data-format requirement; map each required data product to its originating body (IERS, IAU, USNO, BIPM, IMCCE/JPL, CCSDS, NIMA, WGCCRE); verify that citations are correctly attributed to the producing authority; and audit a product list for coverage gaps against the Annex C authority registry. Trigger: ecss, e-st-10-system-scope, authorities, reference-frames, time-scales, ephemerides, geodesy, iers, iau, bipm, ccsds.
- ▌ E1009 Mech Frames · ashfordeou bundleUse when define mechanical body frames for a spacecraft under ECSS-E-ST-10-09C §5.4.5: determine each frame's type (spacecraft body, equipment, or sensor mounting), verify the direction cosine matrix (DCM) satisfies orthogonality and proper-rotation constraints, confirm every equipment and sensor frame names a valid parent frame traceable to the spacecraft body frame, and validate that each equipment and sensor frame carries a tied alignment data record with a declared measurement status (measured, nominal, or estimated). Trigger: ecss, e-st-10-system-scope, mechanical-frames, body-frame, alignment-data, dcm, coordinate-frame, spacecraft-frame, sensor-mounting-frame.
- ▌ E1011 Informatics · ashfordeou bundleUse when evaluate on-board informatics support for a crewed space system under ECSS-E-ST-10-11C §4.8: categorize each display element as numerical, graphical, status_text, alert, or control; determine alert urgency level from hazard severity and time criticality; check display format compliance against minimum contrast ratio and character height thresholds; and assess automation authority to confirm crew override is available for supervisory and autonomous operating modes. Flag every display format shortfall, alert level mismatch, and missing crew override before the workstation is accepted. Trigger: ecss, e-st-10-11c, informatics, hfe, display-design, alerts, automation-authority, crew-interface, workstation-review.
- ▌ E1011 Labels Cues · ashfordeou bundleUse when verify labels, colour codings, and warning cues for a crewed spacecraft interface under ECSS-E-ST-10-11C §4.7.3: categorize each marking as a label (text identifying a control, display, or panel) or a cue (colour-coded indicator or alert signal), confirm every label is non-empty and within the character-length limit, check each colour-coded indicator against the HFE colour-status convention (red for danger, amber for caution, green for nominal, white or grey for information), and confirm every warning cue is detectable and that items with criticality 'warning' or 'emergency' carry at least two redundant cueing modalities (visual, auditory, or tactile). Flag every label, colour, or cue that fails its check; a panel is not compliant until all findings are resolved. Trigger: ecss, e-st-10-11c, e-st-10-system-scope, labels-cues, colour-coding, warning-cues, hfe, human-factors-engineering.
- ▌ E1012 Bio Margins · ashfordeou bundleUse when calculate biological effects margins for a crewed mission under ECSS-E-ST-10C §5.5.5: categorize each biological stressor as radiation (ionizing), physiological (microgravity effects), atmospheric (gas composition, pressure), thermal, or acoustic; determine the design-point exposure for each stressor; apply the margin factor appropriate to that stressor category (radiation uses 1.5×; all other biological stressors use 1.25×); compare the margined exposure against the crew health allowable limit; and flag every stressor whose margined exposure exceeds its limit or whose allowable limit is not on record. Trigger: ecss, e-st-10-system-scope, biological-effects, bio-margins, crewed-missions, radiation, margin-philosophy, crew-health, physiological.
- ▌ E1012 Dd Env Tech · ashfordeou bundleUse when identify displacement-damage-relevant particle environments and susceptible component technologies for a space mission under ECSS-E-ST-10-12C §8.3–8.4: categorize the orbital environment by DD relevance (trapped protons, solar proton events, galactic cosmic rays), map each candidate technology (solar cells, bipolar devices, CCDs, optocouplers, photonic components) to its DD susceptibility tier, and confirm every DD-susceptible item has an assigned NIEL-based analysis path. Trigger: ecss, e-st-10-system-scope, displacement-damage, dd, niel, trapped-protons, solar-cells, bipolar-devices, ccd, optocoupler.
- ▌ E1012 Env Margins · ashfordeou bundleUse when apply environment-driven margins for a spacecraft radiation assessment under ECSS-E-ST-10C §5.3: determine whether the AE-8 worst-case GEO trapped-electron exemption applies for a given mission orbit, compute the design dose by multiplying the predicted total ionising dose by the required radiation design margin factor for deterministic models, verify that a probabilistic-model confidence level meets the level agreed with the customer or authority, confirm that model-uncertainty evidence is documented, and record the §5.3a–e obligation status before the environment input is released to the radiation-effects analysis. Trigger: ecss, e-st-10-system-scope, radiation-margins, ae-8, geo-environment, model-uncertainty, rdm, probabilistic-model, confidence-level, environment-driven-margins.
- ▌ E1012 See Margins · ashfordeou bundleUse when evaluate single event effects (SEE) margin compliance for space electronics under ECSS-E-ST-10C §5.5.3: categorize each event type as soft (SEU, SET, SEFI) or potentially destructive (SEL, SEB, SEGR), compute the predicted event count over the mission duration, apply the required margin factor, compare the margined total against the mission allowable, and flag any device that exceeds the allowable or lacks current-limiting protection for a destructive-category event. Trigger: ecss, e-st-10-system-scope, see-margins, seu, sel, single-event-effects, radiation-margins, space-electronics, latch-up.
- ▌ E1024 Icd Generic · ashfordeou bundleUse when apply generic Interface Control Document (ICD) structure and content rules under ECSS-E-ST-10-24C §5.7 for any ICD variant — EICD, MICD, or TICD: verify each ICD carries a unique interface identifier, an identification block (document number, revision, date, project, interface name, provider, requester), an applicable-documents list, an interface-description section, a numbered requirements section with bilateral allocation and parent-system traceability, a verification-method entry for every requirement, a named configuration-control authority, and a revision history. Flag missing sections, incomplete identification blocks, untraceable requirements, and absent configuration-control records. Trigger: ecss, e-st-10-system-scope, icd, eicd, micd, ticd, interface-control-document, icd-structure, interface-requirements, configuration-control.
- ▌ E3301 Gear Design · ashfordeou bundleDesign a mechanism gear mesh against ECSS-E-ST-33-01C clause 4.7.5.4.7. Use when a spur or helical stage must be shown good for tooth strength, flank wear, backlash and life together: forming the tangential tooth force from module and torque, computing the Lewis bending stress and the Hertzian flank contact stress, derating both material allowables for the required tooth load cycles, sweeping backlash across the thermal range for the gear-to-housing expansion mismatch, and checking the lubricant against that range, the flank stress and the gear material. Trigger: ecss, e-st-33-01-mechanisms-scope, gear-tooth-bending-stress, gear-flank-contact-stress, gear-backlash-thermal-range, gear-lubricant-compatibility, gear-tooth-load-cycles, lewis-form-factor.
- ▌ E50 Failure Modes · ashfordeou bundleEvaluate whether a communications link still meets its performance requirement in every failure mode the mission declares, per ECSS-E-ST-50C clause 5.6.11.4: sum each mode's concurrent decibel contributors, subtract them from the nominal margin, grade every mode against the required margin, name the mode that governs, and return any required mode the budget never covered as unassessed rather than as passing. Use when a link budget shows a healthy nominal column and the failure-mode columns are empty, optimistic, or graded one contributor at a time. Trigger: ecss, e-st-50c-communications-scope, link-performance-failure-modes, degraded-link-margin, governing-worst-case-link-mode, redundancy-recovered-link-failure, uncovered-failure-mode, concurrent-degradation-stack-up.
- ▌ E50 Noise Sources · ashfordeou bundleAssess whether the noise sources acting on a receiving chain have been identified, then add them at one reference plane, per ECSS-E-ST-50C Rev.2 clause 5.6.6. Use when a link budget needs a system noise temperature that can be defended: check that sky, atmosphere, ground spillover, feed loss and front end are each named, refer every source through the loss between its own plane and the reference plane, credit a lossy run with the noise it generates as well as the noise it attenuates, and report the group that dominates the total so a reduction is spent where it pays. Trigger: ecss, e-st-50c-clause-5-6-6, link-noise-source-identification, system-noise-temperature-budget, feed-loss-noise-contribution, antenna-figure-of-merit-g-over-t, noise-reference-plane-referral.
- ▌ E5052 Error Codes · ashfordeou bundleDetermine which status a SpaceWire RMAP target reports and whether the reply agrees with it. Use when an ECSS-E-ST-50-52C clause 5.6 error-code question arises: look a status value up in the registry for its slug and fault family, walk the detection precedence so a command that trips several conditions is answered with the one a target settles on, decide whether a reply leaves the target at all when the header cannot be trusted, check that a failure status carries no returned data and that no value kept aside is reported, then summarise a run of transactions by family. Trigger: ecss, e-st-50-52c, rmap-status-code-registry, rmap-error-detection-precedence, rmap-silently-dropped-command, rmap-reserved-status-value, rmap-reply-status-consistency, rmap-fault-family-summary.
- ▌ Q2007 Nc Control · ashfordeou bundleManage a nonconformance raised at a space test centre under ECSS-Q-ST-20-07C clause 5.8.2, inside the ECSS-Q-ST-10-09 nonconformance system: categorize the anomaly major or minor from safety effect, exceeded article limit, violated requirement or invalidated conditions; derive its reporting deadline and disposition authority; decide whether the run owes a partial or a full retest; and test the proposed disposition against the customer agreement it needs. Use when a test-centre anomaly, an anomaly report log or a disposition proposal has to be adjudicated before campaign close-out. Trigger: ecss, q-st-20-07c, q-st-10-09, test-centre-nonconformance, test-anomaly-report, nonconformance-disposition-authority, test-retest-scope-decision, article-overstress-ratio, nonconformance-close-out.
- ▌ Q2007 Principles · ashfordeou bundleScope the quality and safety management of a space test centre on the principles of ECSS-Q-ST-20-07C clause 4, where assurance reaches the whole centre organization and every test service rather than the test run alone: take each centre function against both disciplines, refuse an exclusion on a core function whatever its rationale, demand a rationale and an accountable owner where an exclusion is admissible, keep subcontracted test services inside the centre's own scope, refuse an assurance line reporting into the operations it grades, and score the uncovered cells. Use when a test centre scope statement is written or audited. Trigger: ecss, q-st-20-07c, test-centre-assurance-scope, quality-and-safety-assurance-principles, test-service-scope-exclusion, subcontracted-test-service-scope, assurance-organizational-independence.
- ▌ Q40 12 Fta Tools · ashfordeou bundleEvaluate a software tool offered to support fault tree analysis under ECSS-Q-ST-40-12C: match what the tool computes against what the analysis actually needs, grade its results against reference cases inside a declared tolerance, compare two runs of one model for repeatability, verify that the model survives an export and re-import in the required exchange formats, derive the qualification effort the result consequence demands, and close with an acceptance verdict plus the restrictions that ride with it. Use when a tool is being chosen, requalified after a version change, or challenged in review. Trigger: ecss, q-st-40-12c, fta-tool-qualification, fta-tool-benchmark-grading, fta-tool-repeatability-check, fault-tree-model-exchange-round-trip, fta-tool-capability-gap.
- ▌ Q40 12 Fta Usage · ashfordeou bundleScope fault tree analysis inside an ECSS project under the ECSS-Q-ST-40-12C adoption of IEC 61025: categorize the need as top-down consequence reasoning or bottom-up failure-mode enumeration, decide whether a tree, an FMECA or both carry the work, name the analyses the tree feeds — hazard analysis under ECSS-Q-ST-40-02 or the dependability analyses of ECSS-Q-ST-30C — set the depth as qualitative or quantitative, and compute how far the basic events trace back to declared failure modes. Use when a project has to justify that a fault tree is the right technique, or to divide work between a tree and an FMECA. Trigger: ecss, q-st-40-12c, fta-usage-scoping, fta-versus-fmeca-division, iec-61025-adoption, fault-tree-basic-event-traceability, fta-analysis-depth-selection.
- ▌ Q7080 Am Records · ashfordeou bundleAudit a build record for the evidence an additively manufactured part has to carry years after the machine was re-tooled. Use when a build is closed out under ECSS-Q-ST-70-80C records: check every field the part class owes, separate a field nobody filled in from one filled in with nothing, work the powder blend into a virgin mass share and a reuse generation and hold both against the class limits, resolve each inspection, coupon and post-process reference against a retrievable document, and report retention alongside the verdict. Trigger: ecss, q-st-70-80-additive-manufacturing-scope, am-build-record, powder-lot-traceability, powder-reuse-generation, virgin-powder-fraction, build-parameter-record, am-record-retention.
- ▌ Hardware Verification · ashfordeou bundleUse when verifying DO-254 airborne electronic hardware: determine the verification methods that apply to a simple or complex AEH item, check whether independent verification is expected at the hardware design assurance level, validate requirements-based test coverage against the A/B and C/D ratios, review hardware/software integration evidence, and confirm the verification effort is complete against the required method set. Methods scale from reduced verification for simple AEH to test, analysis, and review for complex AEH. Trigger: do-254, verification, airborne electronic hardware, aehl, hardware design assurance, requirements-based test, hardware/software integration, review, analysis.
- ▌ Acoustic Analysis · ashfordeou bundleUse when analyze acoustic loading response of spacecraft structural panels under a diffuse acoustic field per ECSS-E-ST-32C clause 4.6.2.6: convert broadband sound pressure levels to acoustic pressure, compute overall sound pressure level from spectral bands, categorize the excitation as low-frequency or high-frequency coupling, compute acoustic force on each panel, verify structural response margins against allowables, confirm the diffuse-field assumption above the Schroeder frequency, assess acoustic fatigue risk for sustained high-level exposures, and aggregate compliance findings per surface. Trigger: ecss, e-st-32-structures-scope, acoustic-analysis, diffuse-acoustic-field, sound-pressure-level, acoustic-loading, low-frequency-response, structural-acoustic, acoustic-fatigue.
- ▌ E10 Req Agreement · ashfordeou bundleUse when drive the customer and supplier sign-off loop on a technical requirements specification under ECSS-E-ST-10C clause 5.2.3.7: determine who must sign, check each party's recorded review against the specification's current baseline revision, separate a stale agreement from an open comment and from a party that has not responded, flag a review left open beyond the agreed review period, and decide whether the specification is agreed. Trigger: ecss, e-st-10-system-scope, requirements-agreement, sign-off, customer-approval, supplier-approval, baseline-revision, stale-agreement, overdue-review.
- ▌ E10 Spec Tree Drd · ashfordeou bundleUse when generate or validate a project specification tree against the ECSS-E-ST-10C Annex J Document Requirements Definition: confirm the tree is singly rooted, fully connected and free of duplicate identifiers, confirm each specification sits exactly one level below its parent, confirm every product-tree node carries exactly one specification, and confirm every non-root specification declares the parent it flows its requirements down from. Trigger: ecss, e-st-10-system-scope, specification-tree, annex-j-drd, requirement-flowdown, product-tree-coverage, specification-levels.
- ▌ E10 Verif General · ashfordeou bundleUse when plan and manage system-level product verification under ECSS-E-ST-10C clause 5.5.1, consistently with the verification process of E-ST-10-02 and the testing scope of E-ST-10-03: assign recognized verification methods to a system requirement, link its approach back to the verification policy in the System Engineering Plan, track each method to a status, require an evidence reference before any method counts as closed, and aggregate the methods into the requirement's verification status. Trigger: ecss, e-st-10-system-scope, verification-planning, verification-policy, sep, verification-methods, method-status, closure-evidence, deviation.
- ▌ E1002 Method Test · ashfordeou bundleUse when determine whether the test method can serve as the formal verification method for a requirement under ECSS-E-ST-10-02C clause 5.2.2.2: check that the requirement's outcome is physically measurable, a representative test article is available, the operational environment is reproducible in a facility, and pass/fail criteria are defined; validate that a test-method record delegates detailed procedure, configuration, and criteria-level detail to an E-ST-10-03 test specification rather than embedding it; and roll up a requirement set's test-readiness and delegation-compliance status. Trigger: ecss, e-st-10-02c, test method, formal verification, verification conditions, test applicability, e-st-10-03, test specification delegation, pass/fail criteria, test readiness roll-up.
- ▌ E1002 Test Report · ashfordeou bundleUse when produce or review a verification test report against the ECSS-E-ST-10-02 clause 5.3.2.1 and Annex C Document Requirements Definition: confirm the report identifies the article, its configuration, the facility and the test procedure by revision, confirm the cited revision is the one actually run, confirm every test objective carries its own verdict, confirm each observed discrepancy is linked to a raised nonconformance, and aggregate the objective verdicts under a severity ordering. Trigger: ecss, e-st-10-02c, test-report, annex-c-drd, test-objectives, procedure-revision, discrepancy, nonconformance-link, measured-data.
- ▌ E1003 El Pressure · ashfordeou bundleUse when run element-level pressure tests for pressurized space hardware under ECSS-E-ST-10C §6.5.3: determine proof pressure from the maximum expected operating pressure and verify the hold duration, cycle pressure between bounds for the required number of fatigue cycles, apply design burst pressure to confirm ultimate structural integrity, and measure leakage against the allowable leak rate. Each test produces a pass/fail verdict with explicit findings. Trigger: ecss, e-st-10-system-scope, pressure-test, proof-pressure, burst-pressure, pressure-cycling, leak-test, meop.
- ▌ E1003 Eq Pressure · ashfordeou bundleUse when running equipment structural-integrity-under-pressure tests under ECSS-E-ST-10-03C: run the leak, proof pressure, pressure cycling, design burst and burst tests on pressurized space segment equipment, derive which of these tests apply from the test campaign and the item's service profile, select whether burst margin is demonstrated by a physical burst test or a design burst analysis depending on whether the article can be sacrificed, sequence a destructive burst test last, and evaluate each test's pass/fail criteria before declaring the item's pressure-test set complete. Trigger: pressure test, leak test, proof pressure, proof pressure test, pressure cycling, design burst, burst test, MEOP, burst factor, structural integrity under pressure, e-st-10-03, ecss, e-st-10c.
- ▌ E1004 B9 Mobe Dic · ashfordeou bundleUse when characterizing the directional transmission of galactic cosmic ray (GCR) and solar energetic particle (SEP) flux through the geomagnetic field under ECSS-E-ST-10-04C Annex B.9: compute the local vertical Stormer-type geomagnetic cutoff rigidity from geomagnetic latitude, apply the Mobius-class Directional Intensity Change (DIC) correction for a given arrival zenith angle and azimuth to obtain the directional cutoff rigidity (capturing the east-west asymmetry between eastward- and westward-arriving primaries), classify a candidate particle rigidity as forbidden, penumbra, or allowed transmission across that directional cutoff's penumbra band, and select the worst-case (lowest-cutoff) arrival direction to verify that a direction-resolved radiation environment case bounds the true geomagnetic shielding. Trigger: geomagnetic cutoff, Stormer cutoff, Directional Intensity Change, DIC, Mobius model, east-west effect, penumbra, geomagnetic transmission, rigidity, asymptotic direction, e-st-10-04, ecss.
- ▌ E1004 Impact Risk · ashfordeou bundleUse when running a meteoroid/space-debris impact risk assessment for a space element under ECSS-E-ST-10-04C clause 10.2.5: combine the cumulative damaging flux from each contributing particle population at the ballistic-limit critical diameter, turn it into an expected impact count over the exposed area and mission duration, and compute the probability of no penetration (PNP) and probability of damage via the Annex J Poisson method, checking the result against the mission's PNP acceptance requirement. Distinct from the sibling e1004-debris and e1004-meteoroid leaves, which select and evaluate the flux models this leaf consumes, and from the sibling e1004-mm-margins leaf, which applies design margins to flux or damage predictions rather than running the probability calculation itself. Trigger: ecss, e-st-10-04c, impact risk, damage probability, probability of no penetration, pnp, annex j, meteoroid debris risk, ballistic limit, space environment.
- ▌ E1012 Seu Proton · ashfordeou bundleUse when predict proton- and neutron-induced single-event upset (SEU) and multiple-cell upset (MCU) rates for space electronic devices under ECSS-E-ST-10C §9.4.1.3: identify the direct-ionization and nuclear-reaction transport paths, apply the Weibull cross-section model over the trapped-proton and free-proton/neutron flux spectra for each path, sum the path contributions to derive the total SEU rate, compute expected upsets over mission duration, compute MCU rate from the MCU fraction, and compare predicted rates against the device SEU budget. Trigger: ecss, e-st-10-system-scope, seu, mcu, proton-induced-seu, neutron-induced-seu, single-event-upset, weibull-cross-section, nuclear-reaction, radiation-hardness.
- ▌ E1012 Shield Unc · ashfordeou bundleUse when determine shielding calculation uncertainties for a spacecraft radiation analysis under ECSS-E-ST-10C §6.4: identify each uncertainty contributor as model (transport-code assumptions and dose-conversion factors), geometry (simplified mesh versus as-built structural detail), or cross-section (nuclear reaction data spread), assign a fractional uncertainty to each contributor, combine them by RSS or linear worst-case summation, apply a k-sigma margin to the nominal computed dose or fluence, and verify the margined result remains within the allowable shielding requirement. Trigger: ecss, e-st-10-system-scope, shielding-uncertainty, model-uncertainty, geometry-uncertainty, cross-section-uncertainty, radiation-margin, dose-budget.
- ▌ E1024 Definition · ashfordeou bundleUse when define interfaces for a space system element by establishing the geometry, signals, protocols, and allocated budgets at each interface end in the IDD or single-end ICD, following ECSS-E-ST-10-24C §5.4: identify every interface end, assign the required geometric envelope and mounting constraints, document signal types and electrical characteristics or communication protocols, allocate per-end resource budgets and verify margin against capacity, and confirm the interface-definition record is complete before it is submitted to the interface control baseline. Trigger: ecss, e-st-10-system-scope, interface-definition, idd, icd, geometry, signals, protocols, budget, interface-end.
- ▌ E4008 Epoch Time · ashfordeou bundleConvert an epoch-scale schedule entry onto simulation time under ECSS-E-ST-40-08C clause 5.4.1, the single normative item that clause places on an entry written at an absolute instant. Use when a schedule mixes epoch instants with simulation-time offsets and the simulator has to decide when each entry actually fires: subtracting the declared epoch at simulation time zero, refusing a float nanosecond count and an undeclared epoch reference, keeping the conversion exactly reversible, reporting an instant the run has already passed instead of dropping it, and stepping a repeating entry to its first occurrence at or after the resolution instant. Trigger: ecss, e-st-40-08-simulation-modelling-scope, e4008-epoch-time, schedule-epoch-time-entry, epoch-to-simulation-time-conversion, epoch-reference-declaration, epoch-entry-already-past, epoch-entry-repeat-period.
- ▌ E4008 Event Link · ashfordeou bundleAssess the event links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.3: resolve each endpoint onto a declared event element with the right role, refusing a sink used as an emitter or a source used as a receiver, then compare the argument the source carries with the argument the sink expects, treating the void argument as a type of its own rather than an absent one. Fan-out from one source is admitted, fan-in into one sink raises an invocation-order advisory, and an identical link declared twice is refused. Use when an event never reaches its handler or an assembly rejects a wiring. Trigger: ecss, e-st-40-08c, smp-level-2, assembly-event-link, event-source-sink-role, event-argument-compatibility, event-fan-out-ordering, void-event-argument.
- ▌ E4008 Field Link · ashfordeou bundleEvaluate the field links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.4: resolve the source onto a readable output or state field and the target onto a writeable input or state field, require identical primitive datatypes because a link copies rather than converts, require identical array shape, refuse a second writer into one target field, and refuse a field linked to itself. The driven-field set the configuration check needs is returned, and a dataflow cycle is raised as an ordering advisory. Use when a value never propagates or two writers fight over one field. Trigger: ecss, e-st-40-08c, smp-level-2, assembly-field-link, field-direction-rule, field-datatype-match, single-writer-field-target, field-link-dataflow-cycle.
- ▌ E50 Arq Settings · ashfordeou bundleConfigure the automatic repeat request parameters of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.13.5, whose single normative item asks that the retransmission settings be adjustable in flight and consistent with the link they run over. Derive the retransmission timeout floor from the round trip, the acknowledgement delay and the jitter, the transmit window the bandwidth-delay product needs, the worst case delivery time a retry limit allows, and the residual loss it leaves. Report every setting that is fixed in the build rather than commandable. Use when tuning retransmission timers or reviewing an ARQ configuration. Trigger: ecss, e-st-50-communications, arq-retransmission-timeout, arq-transmit-window-sizing, arq-retry-limit-budget, ground-settable-arq-parameters, automatic-repeat-request-configuration.
- ▌ E7041 Bit String · ashfordeou bundleValidate a bit-string parameter field against ECSS-E-ST-70-41C clause 7.3.7, where an ordered run of bits with no numeric meaning is carried either at a length the format code fixes or behind a count field. Use when a status word comes back one bit adrift, or when a variable pattern is outgrowing its count field: holding a fixed field to exactly its declared length rather than padding or truncating it, appending pad bits only at the trailing end and keeping them out of the value, bounding a variable pattern by what its count field can announce, and treating a zero-length pattern as legitimate only where the length travels with it. Trigger: ecss, e-st-70-41-packet-utilisation-scope, pus-bit-string-parameter-type, bit-string-octet-padding, bit-string-count-field-width, fixed-length-bit-field, variable-length-bit-field, bit-string-declaration-order.
- ▌ E7041 Enumerated · ashfordeou bundleDerive the enumerated parameter encoding of ECSS-E-ST-70-41C clause 7.3.3, where a symbol travels as an unsigned binary code in a field whose width the format code fixes. Use when a report decodes to a state nobody declared, or a new mode has to be added to a live enumeration: sizing the field from the largest declared code by exact bit length, refusing a table that reaches past its width, counting the spare codes a future state could take, and reporting an undefined code as undefined rather than resolving it to a default symbol. Trigger: ecss, e-st-70-41-packet-utilisation-scope, pus-enumerated-parameter-type, enumerated-code-field-width, undefined-enumeration-code, enumeration-spare-code-headroom, symbol-to-code-mapping, enumeration-widening-decision.
- ▌ E7041 Find Files · ashfordeou bundleExecute a wildcard file search across an on-board repository and judge whether its bounded report can be trusted, under ECSS-E-ST-70-41C clause 6.23.4.4. Use when a search came back with a list and the question is what it left out: matching the any-run and single-character wildcards within a name only, keeping recursion into sub-repositories an explicit flag rather than something a pattern can trigger, returning repository path with every name because one name exists in several repositories, and separating a complete report from one truncated against the report capacity with the omitted count stated. Trigger: ecss, e-st-70-41c, pus-file-management, find-files-request, on-board-file-search-wildcard, recursive-repository-search, truncated-search-report, search-report-capacity.
- ▌ Ndt Verification · ashfordeou bundleUse when verify NDT/NDI method applicability, inspection coverage adequacy, and indication acceptance for structural elements under ECSS-E-ST-32C clause 4.6.3.13: determine the applicable inspection methods for a given material family (metallic, composite, bond, weld) and defect family (surface, subsurface, volumetric, delamination), confirm the inspected fraction meets the criticality-based coverage minimum (100% primary, 50% secondary, 20% tertiary), evaluate each recorded NDT indication against its acceptance limit, and confirm no rejectable or marginal indications remain. Applies to primary, secondary, and tertiary load-carrying structures where NDT evidence is required in the structural verification matrix. Trigger: ecss, e-st-32-structures-scope, ndt, ndi, non-destructive-testing, structural-verification, coverage, acceptance-criteria, indication-evaluation.
- ▌ Q20 Eidp Content · ashfordeou bundleBuild and grade the end item data package of ECSS-Q-ST-20C clause 5.7.2 and its Annex B document requirements description: resolve the record list the product type actually owes rather than reusing a neighbouring delivery's index, mark each required record present and approved at a stated revision, validly declared not applicable with a justification and an approver, or missing, refuse a not-applicable declaration on a core conformity record, and confirm the certificate of conformity points at the as-built configuration list revision the package carries. Use when a delivery package is compiled or reviewed before handover. Trigger: ecss, q-st-20c-clause-5-7-2, end-item-data-package-content, annex-b-drd-document-list, certificate-of-conformity-reference, as-built-configuration-list-revision, eidp-not-applicable-justification.