ashfordeOU
- 1.3k skills
- 0 followers
- 5 repo stars
- 3 days ago last updated
- ▌ Fracture Control Plan · ashfordeou bundleUse when prepare or review a fracture control plan for a spacecraft or launch vehicle structure per ECSS-E-ST-32C DRD Annex F clause 5.2: inventory all structural items and categorize each as fracture-critical (FC) or non-fracture-critical (NFC) based on the failure consequence of fracture, verify the plan contains all required sections (part inventory, criticality rationale, NDE requirements, safe-life or fail-safe life approach, verification methods, approval authority, and update triggers), confirm that FC items carry complete NDE and verification records, determine whether a design or material change triggers a mandatory plan update, and verify that plan approval signatures are present at the required authority level. Aggregate all findings into an overall plan-completeness verdict. Trigger: ecss, e-st-32c, fracture-control-plan, fracture-critical, safe-life, fail-safe, nde-requirements, plan-approval, e-st-32-structures-scope.
- ▌ Modal Analysis Checks · ashfordeou bundleUse when verify modal analysis outputs from a spacecraft or launch-vehicle finite element model against ECSS-E-ST-32C §5.7 acceptance criteria: confirm the rigid-body mode count equals six for a free-free model, confirm each rigid-body mode has a near-zero frequency below the programme threshold, evaluate the cumulative effective mass fraction per translational axis and confirm it meets the required minimum (typically 90 %), and check that the first elastic mode in each axis satisfies the stated minimum frequency requirement. Modes are categorized as rigid-body or elastic before any acceptance criterion is applied. Trigger: ecss, e-st-32-structures-scope, modal-analysis, effective-mass, rigid-body-modes, natural-frequency, mode-shapes, finite-element-model.
- ▌ Model Geometry Checks · ashfordeou bundleUse when verify a finite element model geometry against ECSS-E-ST-32C §5.2 requirements: confirm all node IDs are unique, no two nodes share coordinates within the mesh tolerance, no unreferenced free nodes exist, every element references valid node IDs, interface node sets from adjacent substructures coincide within the specified interface tolerance, and surface element normals are consistently oriented. Apply before any FEM analysis (structural static, modal, or thermoelastic) to confirm the mesh is geometrically sound. Flag each finding as a geometry defect category—duplicate node ID, coincident nodes, free node, broken connectivity, interface mismatch, or reversed normal—and report pass or fail per category. Trigger: ecss, e-st-32-structures-scope, fem-geometry, node-uniqueness, interface-consistency, surface-normals, mesh-quality, free-nodes.
- ▌ Q7002 Test Conditions · ashfordeou bundleValidate the condition set written on an outgassing run sheet. Use when a screening run is being booked under ECSS-Q-ST-70-02C and the declared point has to be reconciled with the method: grade specimen temperature, collector temperature and soak duration against their own bands, treat chamber pressure as a ceiling that low vacuum satisfies, require a named rationale and approval reference for each parameter that departs rather than one blanket note, and add pump-down, stabilisation, soak and cool-down to see whether the booked chamber time can hold the run. Trigger: ecss, q-st-70-02c, outgassing-test-conditions, outgassing-specimen-temperature-setpoint, outgassing-collector-temperature-setpoint, outgassing-soak-duration, outgassing-chamber-pressure-ceiling, outgassing-condition-departure-justification.
- ▌ E50 Link Setup Times · ashfordeou bundleCompute the time a space communication link takes to come into service and assess it against the budget it is allowed, under ECSS-E-ST-50C clause 5.6.8: every stage that must complete before user data flows — carrier acquisition, symbol and frame synchronisation, each negotiation handshake and the round trips it costs — is summed, compared with the declared setup budget, and measured against the contact window that has to absorb it. Report the dominant stage, the margin, the share of the pass consumed and the seconds that must be shaved. Use when budgeting or reviewing acquisition time on a spacecraft link. Trigger: ecss, e-st-50-communications, link-setup-time-budget, carrier-acquisition-stage-timing, handshake-round-trip-delay, contact-window-setup-share, link-acquisition-margin.
- ▌ E50 Space Link Media · ashfordeou bundleAssess the transmission media carrying a mission's space links against what those links must deliver, under ECSS-E-ST-50C clause 5.6.12.1: every link names a medium the mission declared and agreed, and that medium supports the link's required rate, range and availability. Compute per-criterion utilisation, separate a medium with headroom from one that only just fits from one that cannot carry the link, rank the media a link could use, and flag a medium outside the interoperable set. Use when choosing or reviewing the RF or optical medium of a spacecraft space link. Trigger: ecss, e-st-50-communications, space-link-medium-selection, space-link-media-capability-envelope, rf-versus-optical-space-link-medium, space-link-medium-availability-margin, space-link-medium-interoperability.
- ▌ E50 Time Correlation · ashfordeou bundleDerive the correlation between onboard time and the reference time scale under ECSS-E-ST-50C clause 5.6.14.6, which asks that the two be correlated to a stated accuracy. Remove the one-way light time first, because it biases every pair alike and no fit can recover a common bias. Then fit offset and drift by least squares, take the residual spread and the standard error of the drift, and turn the stated accuracy into a validity horizon — the interval after which the correlation must be taken again. Use when sizing a time-correlation cadence or reviewing onboard clock accuracy. Trigger: ecss, e-st-50-communications, onboard-time-correlation, onboard-clock-drift-fit, time-correlation-validity-horizon, correlation-light-time-bias, recorrelation-interval-sizing.
- ▌ E5053 Reserved Field · ashfordeou bundleEvaluate the reserved octet that a packet transfer protocol data unit carries between its protocol identifier and its user application field. Use when an ECSS-E-ST-50-53C clause 5.3.4 link has to settle sender duty and receiver tolerance: write the held-back pattern on transmission, fix the octet offset from the path length, read it back from a received unit, and apply a stated receiver policy that either discards a deviant octet, accepts it and records the deviation, or accepts it silently, which is itself reported. Tally a run of received octets into accepted, discarded and deviation counts. Refuses an unknown role, an unknown policy and an empty log. Trigger: ecss, e-st-50-53c, spacewire-reserved-field, reserved-octet-pattern, receiver-tolerance-policy, reserved-field-offset, protocol-revision-boundary.
- ▌ Fail Safe Compliance · ashfordeou bundleUse when verify fail-safe structural compliance under ECSS-E-ST-32C clause 6.3.3: identify each fail-safe item in the structure, determine the governing damage scenario (element loss, through-crack, or partial-crack), compute residual strength after that damage and compare it against the required residual load capability, confirm the inspection method and interval provide at least two detection opportunities before catastrophic failure, and assess whether widespread fatigue damage conditions could cause simultaneous loss of multiple load-path elements before detection. Each item produces a compliance verdict with explicit findings. Trigger: ecss, e-st-32-structures-scope, fail-safe, residual-strength, widespread-fatigue-damage, inspection-interval, damage-scenario, structural-integrity, fail-safe-compliance.
- ▌ Q2030 Comp Branching · ashfordeou bundleAssess a breakout in a metallic braid-shielded bundle against the complementary branching rules of ECSS-Q-ST-20-30C clause 7.7. Use when the task is computing the braid angle, filling factor and optical coverage each branch braid achieves from its construction, holding every branch to the coverage the trunk already carried rather than only to a floor, adding the trunk, junction and branch segments into one shield-continuity resistance and grading it, refusing a takeoff whose junction is not bonded, and limiting the unshielded length a breakout leaves exposed. Trigger: ecss, q-st-20-30c, braid-shielded-bundle-branching, breakout-shielding-continuity, braid-optical-coverage, braid-filling-factor, shield-continuity-resistance-budget, unbonded-breakout-junction, unshielded-takeoff-length.
- ▌ Q2030 Comp Labelling · ashfordeou bundleAudit harness labelling and marking against the complementary content, format and durability requirements of ECSS-Q-ST-20-30C clause 7.6. Use when the task is decomposing a label token into the fields the project format prescribes, grading each field against the character set its position carries, scaling the minimum character height to the distance the marking is read from, placing the label inside its window from the termination, requiring both ends of a wire routed through a bundle to be marked, grading abrasion and solvent legibility evidence, and catching a token carried by two wires. Trigger: ecss, q-st-20-30c, complementary-harness-labelling, harness-label-token-format, marking-character-height-scaling, label-placement-window, label-durability-cycles, duplicate-harness-label-token, both-end-wire-marking.
- ▌ Q40 12 Fta Procedure · ashfordeou bundleExecute a fault tree analysis to the IEC 61025 procedure adopted by ECSS-Q-ST-40-12C: validate the tree for dangling references, cycles and malformed AND, OR and k-out-of-n gates, expand it to minimal cut sets, evaluate those cut sets qualitatively by order, quantify the top event exactly by inclusion-exclusion and against the rare-event and min-cut-upper-bound estimates, rank contributors by Birnbaum, Fussell-Vesely and criticality importance, sweep the sensitivity of any basic event, and assemble the reporting record. Use when a tree has been drawn and the cut sets, top-event probability, importance ranking or sensitivity numbers are owed. Trigger: ecss, q-st-40-12c, iec-61025-fta-procedure, minimal-cut-set-expansion, fault-tree-top-event-quantification, fault-tree-importance-ranking, fault-tree-sensitivity-sweep.
- ▌ Q7002 Test Execution · ashfordeou bundleAnalyze the run log of a thermal-vacuum outgassing exposure. Use when a soak has finished under ECSS-Q-ST-70-02C and the question is how much of it counts: check that pump-down, heating, stabilisation, soak and cool-down were stamped in the only order they can occur in, credit an interval only when the samples at both ends had specimen temperature, collector temperature and chamber pressure inside their limits together, gather the failing stretches into excursions with their causes, and report qualified soak time beside wall-clock elapsed time. Trigger: ecss, q-st-70-02c, outgassing-exposure-execution, outgassing-qualified-soak-time, outgassing-run-log-excursion, outgassing-exposure-phase-order, outgassing-collector-temperature-hold, outgassing-chamber-pressure-hold.
- ▌ Q7004 Test Reporting · ashfordeou bundleDocument an ECSS thermal test so the report carries its conditions, its results and its anomalies in the agreed format, and grade what it is missing. Use when an ECSS-Q-ST-70-04C reporting clause has to become a releasable document: check every field the format asks for, treat a blank field as an omission while a measured zero stays a result, validate the recorded conditions against each other, require a disposition on every anomaly, catch an anomaly logged outside the cycles that ran, and block release on a pass standing over an open anomaly. Trigger: ecss, q-st-70-04-thermal-testing-scope, thermal-test-report-completeness, test-condition-recording, test-anomaly-disposition, report-release-blocking, thermal-test-report-format.
- ▌ Q7022 Stock Rotation · ashfordeou bundleDetermine the issue order and lot separation a limited-shelf-life stock holding owes under ECSS-Q-ST-70-22: queue the issuable lots by receipt date with a deterministic tie-break, name where receipt order and expiry order disagree so a later lot expiring sooner is not stranded, raise a finding per bin holding mixed materials, commingled lot numbers without a divider, or quarantined stock beside issuable stock, and grade each actual pick against the queue. Use when stock is binned, a picker questions a lot, or a store is audited. Trigger: ecss, q-st-70-22, shelf-life-stock-rotation, first-in-first-out-issue-order, shelf-life-lot-separation, shelf-life-bin-commingling, out-of-rotation-pick.
- ▌ Q7028 Repair Records · ashfordeou bundleAudit the record a repair or modification of a printed circuit board assembly leaves behind under ECSS-Q-ST-70-28C: score the mandatory header fields, require a location that names a side and a reference designator or grid rather than prose, require an approved method with the revision of the procedure that was followed, require every material to carry a batch and a shelf life still valid on the day it was used, match the verification activities recorded against the set the method demands, read the authorization, repair and verification dates in order, and check the retention period. Use when auditing repair paperwork or closing a board out. Trigger: ecss, q-st-70-28c, board-repair-record-audit, repair-location-identification, repair-material-batch-traceability, repair-verification-record-set, repair-record-chronology.
- ▌ Q7045 Impact Testing · ashfordeou bundleAssess a set of Charpy V-notch specimens against its requirement and the conditions it was broken under. Use when the methods clause of ECSS-Q-ST-70-45 calls for impact toughness: scale the requirement to the width below the notch so a sub-size bar is not judged against a full-size figure, hold the set average and every individual bar to their own floors, confirm each bar was struck within tolerance of the stated temperature after a long enough soak and a quick enough transfer, and report readings outside the usable part of the pendulum. Trigger: ecss, q-st-70-45, charpy-subsize-width-scaling, charpy-set-average-and-individual-floor, charpy-strike-temperature-tolerance, charpy-transfer-time-limit, charpy-pendulum-capacity-band.
- ▌ Safe Life Compliance · ashfordeou bundleUse when verify safe-life fracture-control compliance for structural items per ECSS-E-ST-32C clause 6.3.2: categorize each structural item as safe-life or fail-safe, gather crack-growth analysis and test evidence for every safe-life item, confirm that crack-growth life meets or exceeds the design life multiplied by the applicable scatter factor, check that residual strength at end-of-life crack size meets the limit-load requirement, and flag items with missing analysis, test documentation, or margin shortfall. Trigger: ecss, e-st-32-structures-scope, safe-life, crack-growth, residual-strength, fracture-control, structural-margin, fatigue-crack.
- ▌ Bolted Joint Analysis · ashfordeou bundleUse when analyze load transfer, bearing stress, bypass ratio, preload, and failure modes in a bolted metallic or composite joint per ECSS-E-ST-32C clause 4.6.2.13: distribute applied load among fasteners by relative stiffness, compute bearing stress and bypass ratio at each fastener location, check the linear bearing-bypass interaction criterion against material allowables, derive bolt preload from installation torque, and identify governing failure modes including bearing, net-section tension, shear-out, pull-through, fastener shear, fastener tension, and fatigue. Trigger: ecss, e-st-32-structures-scope, bolted-joint, bearing-stress, bypass-ratio, preload, metallic-fastener-joints, composite-bolted-joints, lug-joint-analysis.
- ▌ E10 Function Tree Drd · ashfordeou bundleUse when generate or validate a system function tree against the ECSS-E-ST-10C Annex H Document Requirements Definition: confirm the functional breakdown resolves as a single-rooted, fully connected hierarchy with unique identifiers and resolvable parent links, confirm each function is named with a bare action verb plus an object, reject a level that splits into a single pass-through child, and confirm every elementary function traces to a requirement and is allocated to exactly one system element. Trigger: ecss, e-st-10-system-scope, function-tree, annex-h-drd, functional-breakdown, elementary-function, function-allocation, requirement-trace.
- ▌ E10 Interface Control · ashfordeou bundleUse when you identify and control system-level interfaces under ECSS-E-ST-10C clause 5.6.4: catalog each interface between two interfacing elements, classify its physical domain (mechanical, electrical, thermal, data, fluid) and reject an unrecognized domain, determine whether it crosses an internal or external responsibility boundary and which control document ECSS-E-ST-10-24 requires as a result, draft the interface requirement document (IRD) before the interface matures, define the interface control document (ICD) baseline once it does, verify that both sides declare matching interface parameters, and manage the interface through its control status lifecycle from identified to verified without skipping a step. Trigger: ecss, e-st-10-system-scope, interface management, interface control document, interface requirement document, icd, ird, e-st-10-24.
- ▌ E1011 Cognitive Ergo · ashfordeou bundleUse when assess cognitive ergonomics for a human-operated space system interface under ECSS-E-ST-10-11C §4.6.6: evaluate information presentation density and coding-dimension count per display element, determine workload band from a composite operator workload index, check simultaneous-task count against the cognitive capacity threshold, and verify that situation-awareness indicators at all three levels — perception, comprehension, and projection — are present. Trigger: ecss, e-st-10-system-scope, cognitive-ergonomics, information-presentation, workload-management, situation-awareness, hfe.
- ▌ E1011 Cognitive Perf · ashfordeou bundleUse when apply cognitive performance and fatigue reference data under ECSS-E-ST-10-11 §4.5.4 to assess crew task feasibility: categorize each fatigue source as task-induced, sleep-deprivation, or circadian; determine the fatigue-adjusted sustained-attention duration available; evaluate working memory loading against fatigue-reduced capacity; and verify that decision time available is sufficient for the option count at the crew member's fatigue level. Compute a per-domain risk rating (acceptable, marginal, unacceptable) and derive an aggregate crew cognitive risk. Flag any domain that breaches its threshold as a finding before task or crew assignment proceeds. Trigger: ecss, e-st-10-system-scope, cognitive-performance, fatigue, attention, working-memory, decision-making, crew-performance.
- ▌ E1011 Context Of Use · ashfordeou bundleUse when define the context-of-use description for a product or system as the foundational human-centred design (HCD) input under ECSS-E-ST-10-11C §4.2.2: identify the intended user population, the tasks they must perform, the physical and organisational environment, any relevant constraints, and the mission phases in which users interact with the system, then structure these elements into a reviewable context-of-use record that feeds subsequent HCD planning and human factors evaluation. Trigger: ecss, e-st-10-system-scope, context-of-use, human-centred-design, hcd, user-population, task-analysis, operational-environment, human-factors.
- ▌ E1011 Env Ergonomics · ashfordeou bundleUse when assess environmental ergonomics for a crewed space habitat or EVA station under ECSS-E-ST-10-11 §4.6.5: evaluate noise sound-pressure levels against habitable-area and sleep-quarter limits, verify whole-body vibration doses against daily exposure thresholds, confirm illuminance levels suit each operational area type, check atmospheric pressure, oxygen and carbon-dioxide partial pressures, and humidity against habitable limits, verify operative temperature and radiant-asymmetry boundaries, and audit EVA suit internal atmosphere for pressure, oxygen fraction, and CO₂ concentration. Trigger: ecss, e-st-10-system-scope, human-factors, environmental-ergonomics, noise, vibration, lighting, atmosphere, eva.
- ▌ E1011 Hcd Activities · ashfordeou bundleUse when run HCD activities for a crewed or human-tended space system per ECSS-E-ST-10-11C §4.4.3: decompose human tasks into steps with performer roles and criticality levels via task analysis; capture user and organisational requirements with priority and category; produce design solution elements traceable to each requirement; evaluate each design element against structured criteria to reach a pass, conditional, or fail outcome. Apply to crew interfaces, ground control workstations, maintenance operations, and any human-in-the-loop function requiring structured design justification. Trigger: ecss, e-st-10-11c, hcd, human-centred-design, task-analysis, user-requirements, design-evaluation, crew-interface.
- ▌ E1011 Maint Stations · ashfordeou bundleUse when design physical maintenance stations for a crewed spacecraft per ECSS-E-ST-10-11C §4.7.8: verify that each station's access zone meets minimum reach depth, lateral clearance, and vertical clearance thresholds for intravehicular, extravehicular, or hybrid zone types; confirm that registered tools are compatible with the station zone type and that large-envelope single-hand tools are flagged for operating-arc review; validate that lighting levels meet the minimum lux requirement for the zone; and categorize all maintenance tasks by frequency and zone type while flagging tasks that reference tools not on record at the station. Trigger: ecss, e-st-10-system-scope, maintenance-stations, access-zone, workspace, tooling, lighting, human-factors.
- ▌ E1011 Mission Phases · ashfordeou bundleUse when map mission phases and identify human-in-the-loop activities for HFE requirements capture under ECSS-E-ST-10-11C §4.3.6: inventory each canonical phase (ground operations, launch, ascent, deployment, on-orbit checkout, nominal operations, contingency, disposal), categorize every operator or crew activity within each phase, flag phases with no human-in-the-loop coverage, flag critical activities lacking human oversight in safety-critical phases, and derive one HFE requirement per human-assigned activity to populate the requirements register. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, human-factors, mission-phases, human-in-the-loop, hfe-requirements, operator-activities.
- ▌ E1011 Verif Analysis · ashfordeou bundleUse when verify Human Factors Engineering (HFE) requirements by analysis or similarity under ECSS-E-ST-10-11 §4.11.2: select the applicable analysis method (task analysis, cognitive workload, workspace envelope, anthropometric analysis, or digital human model simulation), score heritage similarity against the target design to determine whether prior evidence transfers, run DHM simulations and compare joint angles, reach zones, crew forces, and visual fields against acceptance thresholds, and compile the mandatory analysis/simulation report per Annex B. Trigger: ecss, e-st-10-11, hfe, human-factors, verif-analysis, dhm, digital-human-model, similarity, annex-b, ergonomics.
- ▌ E1012 Bio Env Limits · ashfordeou bundleUse when defining the space radiation environments applicable to a crewed mission and verifying crew dose compliance with ECSS-E-ST-10C §11.3–11.4: identify which environments (galactic cosmic rays, solar energetic particles, trapped protons, trapped electrons, secondary neutrons) apply to the orbit profile, determine dose contributions to the blood-forming organ, eye lens, and skin, compare accumulated doses against the short-term (30-day and annual) and career limits for each crew member, and flag any exceedance or missing limit record as a protection finding requiring resolution before crew-hours approval. Trigger: ecss, e-st-10-system-scope, crew-dose, radiation-protection-limits, space-radiation-environment, GCR, SPE, trapped-radiation, BFO-dose, career-limit.
- ▌ E1012 Bio Quantities · ashfordeou bundleUse when determine dosimetric quantities for a space radiation environment analysis per ECSS-E-ST-10C §11.2: select a radiation weighting factor (wR) for each particle type from the §11.2 Table 11-1 categories (photons, electrons, protons, alphas, heavy ions, energy-dependent neutrons), select a tissue weighting factor (wT) for each organ from §11.2 Table 11-2, compute equivalent dose per tissue as absorbed dose multiplied by wR, compute effective dose as the sum of wT × HT across all tissues, and derive dose equivalent from absorbed dose and the LET-dependent quality factor Q(L) defined in §11.2. Trigger: ecss, e-st-10-system-scope, dosimetry, radiation-weighting-factor, tissue-weighting-factor, equivalent-dose, effective-dose, quality-factor, dose-equivalent.
- ▌ E1012 Dd Degradation · ashfordeou bundleUse when determine the end-of-life parametric degradation of a component exposed to displacement damage dose under ECSS-E-ST-10-12C §8.6: select the degradation curve model (power-law, exponential, or tabular) for the part, compute the normalized EOL parameter value from the displacement damage dose and curve coefficients, apply the design margin, and verify the margin-adjusted EOL value meets the circuit minimum requirement. Flag any component whose degradation curve is not on record or whose dose falls outside the characterized range. Trigger: ecss, e-st-10-12c, displacement-damage, dd-degradation, parametric-degradation, non-ionizing, eol-parameter, ddd-curve, bipolar-degradation.
- ▌ E1012 Shield Process · ashfordeou bundleUse when execute the spacecraft shielding calculation process under ECSS-E-ST-10-12C §6.2.1: identify the radiation effects that require quantification (TID, DD, SEE proton, SEE heavy-ion), select the appropriate calculation method for each effect from the geometry- and effect-dependent method table (slab approximation, sector analysis, or Monte Carlo for primary shielding; NIEL-weighted fluence for DD; LET-spectrum assessment for heavy-ion SEE), compute the predicted dose or fluence behind the combined primary and secondary shielding, and compare each result against the component's dose or fluence limit including the radiation design margin. Trigger: ecss, e-st-10-system-scope, shielding, radiation shielding, TID, displacement damage, SEE, sector analysis, Monte Carlo, radiation design margin, primary shielding, secondary shielding.
- ▌ E1012 Tid Assessment · ashfordeou bundleUse when calculate total ionising dose (TID) damage for spacecraft electronic components under ECSS-E-ST-10-12C §7.5: derive the applicable radiation damage parameters for each component category (§7.5.1), compute the accumulated ionising dose from orbit-specific dose rates and mission duration using an aluminium shielding model (§7.5.2), apply the required design margin, and compare each component's dose requirement against its TID limit to produce a compliant or non-compliant finding. Trigger: ecss, e-st-10-12c, e-st-10-system-scope, tid, total-ionising-dose, radiation-damage, dose-calculation, shielding, rha, component-assessment.
- ▌ E1024 Eicd Subsystem · ashfordeou bundleUse when produce EICDs at the space segment subsystem level per ECSS-E-ST-10-24C §5.8.2: identify all inter-subsystem interfaces by type (mechanical, electrical, thermal, data, RF, fluid, optical, pyrotechnic), verify each interface record carries every required field, confirm that requirement references trace to the system-level requirement registry, flag records where subsystem identifiers are not distinct, and detect duplicate or contradictory interface definitions for the same subsystem pair. Aggregate document-level, per-interface, traceability, and consistency findings to determine whether the EICD achieves compliance. Trigger: ecss, e-st-10-system-scope, eicd, interface-control-document, subsystem-interface, traceability, verification, consistency-check.
- ▌ E1024 Identification · ashfordeou bundleUse when identify interfaces for a space system under ECSS-E-ST-10-24C §5.2: build the interface tree or list, assign each interface to a category (mechanical, electrical, data, thermal, fluid, RF, or optical), and generate unique interface identifiers following the standard naming convention. Apply to any system or subsystem boundary where the interface type, connecting entities, and sequence position must be captured before interface control documentation proceeds. Trigger: ecss, e-st-10-system-scope, interface-identification, interface-tree, interface-category, interface-identifier, icd, interface-control.
- ▌ E4008 Model Instance · ashfordeou bundleValidate a model Instance against the seven normative items of ECSS-E-ST-40-08C clause 4.2.2.2. Use when a simulation assembly is reviewed instance by instance: confirming the name is a legal identifier that no sibling already uses, requiring a description, resolving the model definition against the catalogue, confirming every declared field is bound by a supplied value or a declared default, range- and type-checking each bound value, resolving every mandatory reference onto a path that exists in the assembly, and confirming the resulting hierarchy path is occupied once. Reports the seven items separately so a partial review is auditable. Trigger: ecss, e-st-40-08c, simulation-model-instance, model-instance-field-binding, model-instance-path-uniqueness, model-definition-catalogue-resolution, model-instance-reference-resolution, simulation-assembly-instance-review.
- ▌ E50 Interoperability · ashfordeou bundleEvaluate whether a space link can actually work with the external assets its mission claims cross-support from, per ECSS-E-ST-50C Rev.2 clause 5.6.4. Use when an interoperability requirement has to be stated and then shown: compare the link profile against each partner on frequency band, modulation, channel coding and frame format, separate a partner that shares no option from one that simply never declared an attribute, pick a deterministic operating option where both sides overlap, and name the options the link would have to add to recover a partner it cannot reach today. Trigger: ecss, e-st-50c-clause-5-6-4, space-link-interoperability, ground-station-cross-support, link-profile-compatibility, cross-support-option-negotiation, undeclared-partner-attribute.
- ▌ Drd Alignment Budget · ashfordeou bundleUse when determine the structural alignment budget for a spacecraft or instrument mounting interface under ECSS-E-ST-32C Annex L: identify every contributor to alignment error — manufacturing tolerances, thermoelastic distortion, gravity-release deformation, load-induced deflection, and measurement uncertainty — assign sensitivity coefficients, combine contributions by root-sum-square or worst-case arithmetic, and verify the resulting total against the pointing or interface alignment requirement. The budget must cover both on-ground and on-orbit alignment states and record each contributor's type, magnitude, and sensitivity coefficient. Flag any exceedance or missing allowable before closing the budget. Trigger: ecss, e-st-32c, e-st-32-structures-scope, alignment-budget, structural-alignment, thermoelastic, gravity-release, pointing-budget, interface-alignment.
- ▌ Drd Dimstab Analysis · ashfordeou bundleUse when prepare a dimensional stability analysis (DSA) report for a spacecraft structure per ECSS-E-ST-32C Annex C: verify the report contains every mandatory DRD section, validate material CTE and hygrothermal coefficients, compute linear thermal and hygrothermal displacements for each structural member, combine contributions to derive total dimensional change, compute stability margins against requirements, assess CTE mismatch between dissimilar joined materials, and confirm every structural member's dimensional change is within the applicable stability requirement. Trigger: ecss, e-st-32-structures-scope, dimensional-stability, cte, hygrothermal, thermal-distortion, displacement, stability-margin, drd.
- ▌ Drd Fatigue Analysis · ashfordeou bundleUse when determine the content and completeness of a fatigue analysis report deliverable under ECSS-E-ST-32C Annex D (DRD-FA): verify the report defines all required load spectra, applies Miner's rule damage summation over rainflow-counted cycle blocks, adjusts predicted fatigue life by the required scatter factor, and confirms a positive life margin at each fatigue-critical location. Categorize each load event by spectrum type, sum fractional damage across stress amplitudes, and flag any location where the scatter-factor-adjusted life falls below the required design life. Trigger: ecss, e-st-32-structures-scope, fatigue-analysis, load-spectra, miner-rule, scatter-factor, s-n-curve, fatigue-life, damage-summation.
- ▌ E10 Config Baselines · ashfordeou bundleUse when establishing the functional, allocated, or product configuration baseline for a space system under ECSS-E-ST-10C clause 5.4.2.2: classify the baseline type, confirm every earlier baseline in the functional-then-allocated-then-product sequence is already established, verify the gating milestone review (SRR for functional, PDR for allocated, CDR for product) has passed, check that the baseline's required configuration-management artifacts are on record, and aggregate the findings per baseline type so a program-level compliance status can be derived. Trigger: ecss, e-st-10-system-scope, configuration baseline, functional baseline, allocated baseline, product baseline, m-st-40, srr, pdr, cdr, configuration management milestones.
- ▌ E10 Req Traceability · ashfordeou bundleUse when maintaining bidirectional requirement traceability under ECSS-E-ST-10C: keep the requirements traceability matrix (RTM) aligned across customer requirements, derived requirements, allocated products and verification records, and detect broken, missing or dangling trace links before review gates. ECSS-E-ST-10C clause 5.2.2 governs requirement traceability as part of system engineering requirement flow-down. Trigger: ecss, e-st-10c, requirement traceability, RTM, trace matrix, bidirectional trace, 5.2.2, space systems engineering.
- ▌ E1002 Method General · ashfordeou bundleUse when you need to determine which verification method or combination of methods -- test, analysis, review-of-design, inspection -- satisfies a requirement under ECSS-E-ST-10-02C clause 5.2.2.1: categorize the requirement, filter to the methods eligible for that category, enforce that a safety-critical requirement always carries test, apply the test-over-analysis-over-review-of-design-over-inspection precedence rule with a stated rationale whenever a more rigorous eligible method is skipped, and roll up a verification plan's per-method counts and its non-compliant requirement ids. Trigger: ecss, e-st-10-02c, verification method selection, test analysis review-of-design inspection, method precedence, verification plan completeness, safety-critical verification, method applicability rules.
- ▌ E1002 Reverification · ashfordeou bundleUse when determine whether a previously verified hardware item or software configuration requires re-verification following a design change, extended storage period, re-flight of previously flown hardware, or an observed anomaly. Apply ECSS-E-ST-10C §5.4.3 to categorize the triggering event, derive the minimum re-verification scope, enumerate the required activities (inspection, functional test, delta qualification, similarity assessment, structural and thermal analysis, anomaly investigation, documentation review), check which activities are documented, and confirm the item re-enters the verified database only after all required activities are closed or formally waived. Trigger: ecss, e-st-10-system-scope, re-verification, design-change, anomaly, re-flight, storage, verification-scope, delta-qualification.
- ▌ E1003 El Protoflight · ashfordeou bundleUse when define the element protoflight test baseline under ECSS-E-ST-10-03C §6.4: decide whether a space element must follow the protoflight test approach (one hardware model demonstrating both design qualification and flight acceptance, with no separate dedicated qualification model), and derive, for each required test type, the protoflight test level from the Table 6-5 qualification severities and the protoflight test duration from the Table 6-6 acceptance durations. Also flag any protoflight baseline entry whose level or duration deviates from the standard qualification-level/acceptance-duration rule without a documented engineering deviation. Trigger: ecss, e-st-10-system-scope, protoflight, element-testing, test-levels, test-durations, Table-6-5, Table-6-6, qualification-baseline, acceptance-baseline.
- ▌ E1003 Eq Protoflight · ashfordeou bundleUse when you define the equipment protoflight test baseline under ECSS-E-ST-10-03C clause 5.4: decide whether an equipment item must follow the protoflight test approach (one hardware model demonstrating both design qualification and flight acceptance, with no separate dedicated qualification model), and derive, for each test type, the protoflight test level from the Table 5-5 qualification/acceptance severities and the protoflight test duration from the Table 5-6 qualification/acceptance durations. Also flag any protoflight baseline entry whose level or duration deviates from the standard qualification-level/acceptance-duration rule without a documented engineering deviation. Trigger: protoflight test baseline, protoflight approach, equipment test levels, test duration, Table 5-5, Table 5-6, E-ST-10-03, ecss, e-st-10c.
- ▌ E1003 Test Programme · ashfordeou bundleUse when define the overall test programme for a space system or subsystem under ECSS-E-ST-10C §4.1: identify each hardware model entering the programme (BB, EM, QM, EQM, PFM, FM), derive its corresponding test level (development, qualification, proto-flight, or acceptance), build and validate the ordered test sequence for each model ensuring positions are unique and consecutive, verify that functional tests bookend the sequence at position 1 and the final position, confirm all required programme-level documents are on record before scheduling begins, and validate that the required verification inputs for each test activity are supplied. Trigger: ecss, e-st-10-system-scope, test-programme, models-under-test, test-sequence, verification-inputs, programme-documentation, qualification, acceptance.
- ▌ E1004 Ref Atmosphere · ashfordeou bundleUse when determining which reference atmosphere model and inputs apply to a mission atmosphere lookup under ECSS-E-ST-10-04C Annex G: map the target body and altitude to the cataloged reference models (NRLMSISE-00, JB-2006, and GRAM-class planetary models), select the model that matches the analysis purpose (drag prediction, density reference, or full-profile engineering) while validating the altitude against that model's supported range, and verify every input the selected model needs (solar/geomagnetic activity or trajectory fields) is present before the model is run; also classifies an Earth altitude into its atmospheric regime for scoping. Trigger: ecss, e-st-10-04c, annex g, atmosphere model, nrlmsise-00, jb-2006, gram, planetary atmosphere, reference atmosphere, drag prediction.
- ▌ E1006 Char Ambiguity · ashfordeou bundleUse when determine whether requirements are unambiguous under ECSS-E-ST-10C §8.2.4: identify vague qualitative terms (adequate, sufficient, appropriate, optimal), weasel qualifiers (TBD, TBC, as required, where possible), compound connective ambiguity (and/or without explicit resolution), and implicit subjects with no stated system element; flag each finding with its category and severity; confirm every requirement admits exactly one interpretation before passing the ambiguity gate. Trigger: ecss, e-st-10-system-scope, requirement-ambiguity, vague-terms, single-interpretation, requirement-quality, e1006, e-st-10c.
- ▌ E1006 Char Tolerance · ashfordeou bundleUse when verify that each quantitative performance characteristic in a system requirement set carries an explicit tolerance alongside its nominal value, per ECSS-E-ST-10C §8.2.10: for each quantitative requirement, confirm a nominal value is present, a plus-tolerance and minus-tolerance are both stated (symmetric or asymmetric), and tolerance magnitudes are non-negative. Qualitative requirements are out of scope. Trigger: ecss, e-st-10c, e-st-10-system-scope, characteristic-tolerance, quantitative-requirements, tolerance-verification, requirements-completeness.
- ▌ E1009 Chain Analysis · ashfordeou bundleUse when verify end-to-end coordinate system transformation chains across all frame users in a spacecraft project, following ECSS-E-ST-10C §5.2.3. Inventory every coordinate system in the project, register each inter-frame transformation link, and trace the chain from each user frame back to a common root frame. Flag any user frame that cannot reach the root, detect circular dependencies in the directed transformation graph, and check handedness consistency along each resolved chain. A project is chain-compliant only when all users are reachable, no cycles exist, and all frames in every chain share the same handedness convention. Trigger: ecss, e-st-10-system-scope, coordinate-systems, transformation-chain, reference-frames, chain-analysis, frame-consistency, handedness, e-st-10c.
- ▌ E1009 Responsibility · ashfordeou bundleUse when verify responsibility assignments for each coordinate system definition and transformation entry in a Coordinate System Document, ensuring every entry carries exactly one identified owner before the document is baselined. The procedure checks no CSD entry is unassigned (orphaned) and no entry carries ambiguous dual ownership, producing a compliant responsibility matrix per ECSS-E-ST-10C §5.2.1. Trigger: ecss, e-st-10-system-scope, coordinate-system, transformation, responsibility, ownership, csd, single-owner, assignment.
- ▌ E1011 Assessment Drd · ashfordeou bundleUse when generate or validate the HFE continuous assessment process report per ECSS-E-ST-10-11C Annex C (normative DRD): confirm the report identifies assessment scope (system under review, mission phase, review gate or milestone), the assessment method applied (inspection, walkthrough, simulation, or user trial), a finding register where each entry carries an HFE criterion label, a severity level (critical, major, minor, or observation), and a recommendation, and a corrective-action register that links each finding to an owner and status. Derive the overall result: fail when any critical finding remains unresolved, conditional when a critical or major finding is in progress, pass otherwise. Flag any mandatory DRD section that is absent. Trigger: ecss, e-st-10-system-scope, hfe-assessment, drd, continuous-assessment, finding-register, corrective-action, assessment-report, hfe-drd.
- ▌ E5053 Eop Character · ashfordeou bundleEvaluate the end-of-packet marker that terminates a SpaceWire transfer carrying a CCSDS packet under ECSS-E-ST-50-53C clause 5.4.1.8: separate a normal terminator from an error terminator and from no terminator at all, decide deliver or discard from that marker before any payload is parsed, and grade a received sequence against a discard-ratio budget so a link that is up but shredding packets is visible. Use when receiving, discarding or fault-finding CCSDS transfers on a SpaceWire link. Trigger: ecss, e-st-50-53c, spacewire-eop-character, spacewire-eep-error-terminator, ccsds-transfer-discard-rule, spacewire-packet-truncation, link-discard-ratio, terminator-disposition.
- ▌ E7041 Absolute Time · ashfordeou bundleConvert an on-board moment to and from the absolute-time parameter a packet definition declares, under ECSS-E-ST-70-41C clause 7.3.10. Use when a generation time, a time-tagged release or a collection-interval start reads plausibly wrong on the ground: fixing the time code, the coarse and fine field widths and the epoch in the definition rather than on the wire, truncating downwards so an encoded time never names a later moment, and refusing a time past the coarse span instead of wrapping it into the wrong era. Trigger: ecss, e-st-70-41c, pus-absolute-time-parameter, cuc-coarse-fine-time-code, cds-day-segmented-time-code, on-board-time-epoch-agreement, absolute-time-span-overflow, time-code-resolution-budget.
- ▌ E7041 Relative Time · ashfordeou bundleCompute and encode the relative-time parameters a packet definition declares, under ECSS-E-ST-70-41C clause 7.3.11. Use when a collection interval, an offset from a reference or a gap between two events is being carried in a packet: keeping a duration epoch-free so nobody reads it as a date, holding it as a signed two's-complement coarse count whose negative reach is one step longer than its positive one, flooring towards minus infinity so the fine count stays non-negative, and refusing a difference of moments the field cannot hold. Trigger: ecss, e-st-70-41c, pus-relative-time-parameter, signed-duration-two-s-complement, epoch-free-duration, coarse-fine-duration-encoding, absolute-minus-absolute-interval, duration-range-overflow.
- ▌ Microvibration Test · ashfordeou bundleUse when evaluate micro-vibration, microgravity, or noise disturbance test compliance for spacecraft equipment under ECSS-E-ST-32C clause 4.6.3.12: categorize each disturbance source as tonal, broadband, or transient, verify that the test measurement frequency band fully covers the required range, compute force and torque disturbance amplitudes using a force-measuring platform or equivalent fixture, compare each measured amplitude against the allocated disturbance budget, and flag any source whose amplitude exceeds the budget or whose frequency coverage is insufficient. Apply this skill when establishing or reviewing the test configuration, measurement chain, and pass/fail criteria for micro-vibration qualification or acceptance testing of rotating or oscillating equipment. Trigger: ecss, e-st-32-structures-scope, microvibration, micro-vibration, noise-disturbance, disturbance-budget, tonal-disturbance, broadband-disturbance, force-platform.
- ▌ Overwrap Inspection · ashfordeou bundleUse when assess composite overwrap integrity per ECSS-E-ST-32C clause 5.7: select the non-destructive testing method appropriate to the detected anomaly type and overwrap material (CFRP, GFRP, aramid), evaluate inspection coverage against the required threshold, categorize each defect as acceptable, monitor, or rejectable using established size criteria, and determine the overall inspection outcome (pass, conditional-pass, fail, or incomplete). Apply visual damage tolerance evaluation to surface anomalies before committing to invasive NDT. Trigger: ecss, e-st-32-structures-scope, overwrap-inspection, composite-overwrap, ndt, vdt, delamination, void.
- ▌ Pfci Fci Flli Lists · ashfordeou bundleUse when document, compile, and verify the ECSS-E-ST-32C clause 6.4.2 fracture control item lists (PFCIL, FCIL, FLLIL): categorize each structural item as Potentially Fracture Critical (PFCI), Fracture Critical (FCI), or Flight Limited Life (FLLI) based on fracture sensitivity and demonstrated compliance, confirm required documentation is present for each item category, and verify that each list carries an issue number, approval date, and authorised signatory before submission to configuration control. Trigger: ecss, e-st-32-structures-scope, fracture-control, pfcil, fcil, fllil, flight-limited-life, configuration-control, fracture-critical-items.
- ▌ Q20 Gse Maintenance · ashfordeou bundleMaintain ground support equipment under ECSS-Q-ST-20C clause 5.8.9: measure each planned task against its own clock, calendar days or operating hours, report how much of every interval has been consumed and by how much a task has run past it, treat a task landing exactly on its interval as due rather than late, derive the reverification an intervention owes from the part it touched, name every recalibration or inspection still outstanding before the equipment goes back to work, and return the continued-readiness verdict. Use when GSE is due for maintenance or is coming out of it. Trigger: ecss, q-st-20c-clause-5-8-9, gse-maintenance-interval, gse-overdue-maintenance-task, gse-post-maintenance-recalibration, gse-continued-readiness-record, gse-return-to-service.
- ▌ Q20 Logbook Example · ashfordeou bundlePrepare and assess the logbook cover page of ECSS-Q-ST-20C Annex E, used as the house record header for the Annex C content: hold the field order the worked example fixes, refuse a blank mandatory field, a non-positive issue, a period running backwards or a sheet numbered past its own total, render the header with labels aligned to one column, compute the sheets the entry count needs at the book's ruling, and cross-check the cover serial, period and sheet total against the entries it heads. Use when a logbook is opened, reissued or checked at handover. Trigger: ecss, q-st-20c-annex-e, logbook-cover-page, logbook-record-header, logbook-cover-field-order, logbook-cover-period, logbook-sheet-count.
- ▌ Q20 QA Deliverables · ashfordeou bundlePlan and audit the quality assurance documents a project owes at each review from the mapping table of ECSS-Q-ST-20C Annex I: resolve the rows the declared scope actually turns on, separate a document reissued at every review in its window from one delivered twice, hold the maturity each review owes on the draft, issued and approved ladder, measure a submission against its lead time in days before the review date, score the review as the satisfied fraction of what it owed, and walk the sequence to the first review that does not clear the threshold. Use when a delivery schedule is built or a review data pack is audited. Trigger: ecss, q-st-20c-annex-i, qa-deliverables-per-review, qa-document-review-matrix, qa-document-maturity-ladder, qa-submission-lead-time, review-readiness-rollup.
- ▌ Q2007 Test Sequence · ashfordeou bundleStructure a test campaign plan against the typical test process sequence offered by ECSS-Q-ST-20-07C Annex B: lay the planned phases on the reference flow, report a mandatory phase that is neither planned nor omitted against a recorded tailoring rationale, name every adjacent pair that runs the flow backwards, flag a rationale left behind for a phase that is planned anyway, and lay the durations into contiguous day windows so the plan carries a schedule. Use when a campaign plan is being drafted or an offered sequence is being compared with the reference. Trigger: ecss, q-st-20-07c, typical-test-process-sequence, test-campaign-phase-ordering, test-phase-precedence-conformance, test-sequence-tailoring-rationale, campaign-phase-day-windows.
- ▌ Q2030 Comp Crimping · ashfordeou bundleVerify a crimp-termination lot against the complementary crimping requirements of ECSS-Q-ST-20-30C clause 7.4, which take precedence over the delegated workmanship criteria wherever both speak. Use when the task is resolving which limit governs a crimp characteristic, grading a measured crimp height against the window the contact and wire gauge carry, sizing the tensile sample a lot owes and grading every pull against the minimum force its gauge carries, refusing a barrel holding an unqualified second wire or any solder, and confirming the crimping tool's calibration is still current. Trigger: ecss, q-st-20-30c, complementary-crimping-requirements, crimp-height-window, crimp-pull-test-sampling, crimp-barrel-wire-count, complementary-over-delegated-precedence, crimp-tool-calibration-currency, solder-in-crimp-barrel.
- ▌ Q2030 Comp Emc Foil · ashfordeou bundleValidate a conductive metal foil EMC shield against the complementary application and termination criteria of ECSS-Q-ST-20-30C clause 7.8. Use when the task is sizing the foil thickness against the skin depth of its metal at the lowest frequency the shield must work from, turning a helical wrap overlap into a pitch, a layer count over every point and the tape length the run consumes, confirming the conductive face is applied inward against the drain wire, and costing the drain-wire pigtail in decibels against a full circumferential termination. Trigger: ecss, q-st-20-30c, conductive-foil-emc-shield, foil-skin-depth-sizing, helical-foil-wrap-overlap, foil-drain-wire-termination, shield-pigtail-penalty-db, conductive-face-orientation, foil-tape-length-estimate.
- ▌ Q2030 Comp Sleeving · ashfordeou bundleEvaluate the insulation sleeving applied over terminated contacts against the complementary requirements of ECSS-Q-ST-20-30C clause 7.5. Use when the task is choosing a sleeve size that will pass over the largest diameter on its assembly path and still close onto the diameter it must grip, sizing the cut length from the covered span, the overlap owed at each end and the longitudinal shrinkage, confirming the installed sleeve clears the contact retention and mating features, and deciding whether an opaque sleeve has left a joint without an inspection record. Trigger: ecss, q-st-20-30c, complementary-insulation-sleeving, sleeve-recovery-ratio, sleeve-cut-length-sizing, sleeve-end-overlap, contact-retention-feature-clearance, opaque-sleeve-inspectability, longitudinal-sleeve-shrinkage.
- ▌ Q40 Hazard Closeout · ashfordeou bundlePerform hazard reporting, review and close-out under ECSS-Q-ST-40C: hold every hazard control on its own row of the safety verification tracking log, discharge a control only when its row is closed, cites evidence and has that evidence accepted, add the safety review board behind a catastrophic or critical hazard and an acceptance reference behind any declared residual risk, then emit the hazard close-out statement and the log rollup. Use when hazards are taken to a safety review for closure. Trigger: ecss, q-st-40c, ecss-hazard-close-out, safety-verification-tracking-log, svtl-annex-c, hazard-close-out-statement, residual-risk-acceptance-reference.
- ▌ Q7026 Crimp Records · ashfordeou bundleAudit a set of crimping records for the completeness and traceability the records clause of ECSS-Q-ST-70-26C asks of them. Use when a harness dossier is assembled and every termination has to be answerable: check the mandatory fields are carried, resolve the tool identifier into the calibration register, resolve the operator against the certification window covering the date of the crimp rather than today, resolve both wire and contact lots into accepted receiving records, grade the periodic pull-test cadence across the set in date order, and grade the retention period. Trigger: ecss, q-st-70-26, crimp-record-completeness, crimp-lot-traceability-chain, crimp-tool-identifier-resolution, crimp-operator-date-validity, crimp-record-retention-period.
- ▌ Q7028 Repair Limits · ashfordeou bundleDetermine whether a printed circuit board assembly stays inside the repair ceilings of ECSS-Q-ST-70-28C once a further repair is added. Read the count and density allowance the assurance level carries, combine the repairs already on the board with the ones proposed, refuse a reused site identity, measure the in-plane separation of every pair against the minimum that pair takes — longer on one face, shorter across the laminate — count repairs per conductor, and return the disposition with the closest pair, the governing limit and whether the proposal is what broke it. Use when authorising another repair or auditing a heavily reworked board. Trigger: ecss, q-st-70-28c, repairs-per-board-allowance, board-repair-proximity-rule, board-repair-density-limit, repairs-per-conductor-limit, repair-site-separation.
- ▌ Aeroelastic Analysis · ashfordeou bundleUse when determine aeroelastic stability margins for aerodynamic surfaces on a launch vehicle or atmospheric segment under ECSS-E-ST-32C clause 4.6.2.17: categorize each surface as flutter-critical or divergence-critical, compute the flutter speed margin and divergence speed margin against the design envelope, verify each margin exceeds the 15 % required clearance, evaluate frequency separation between structural eigenfrequencies and aerodynamic forcing, and flag any surface where flutter speed, divergence speed, or frequency separation falls short of the required threshold. Trigger: ecss, e-st-32c, aeroelastic, flutter, divergence, dynamic-response, frequency-separation, launch-vehicle-structures.
- ▌ E1004 Contamination · ashfordeou bundleUse when assessing on-orbit contamination of a spacecraft external surface under ECSS-E-ST-10-04C clause 11.2: classify each contamination source as molecular (outgassing, venting, propulsion effluent, leak) or particulate (debris, MLI fragment, handling residue, paint flake), determine the molecular transport path (direct line-of-sight vs. LEO ram/wake return flux), compute the deposited molecular mass and compare it against the surface's allowable budget, and verify every particulate-generating surface carries a cleanliness level per the ECSS-Q-ST-70-01 contamination control linkage. Trigger: ecss, e-st-10-04c, contamination, molecular contamination, particulate contamination, outgassing, deposition, cleanliness level, q-st-70-01, on-orbit contamination assessment.
- ▌ E1004 Ref Particles · ashfordeou bundleUse when selecting particle-radiation reference models for a space-environment case under ECSS-E-ST-10-04C Annex I (informative): categorize the particle population (trapped proton, trapped electron, solar energetic particle, galactic cosmic ray, albedo neutron) and the orbit regime, check a proposed energy against the population's cataloged model energy range and a proposed altitude against its altitude range, determine whether a low-Earth orbit is geomagnetically shielded for a given inclination, determine whether the South Atlantic Anomaly enhancement applies to a low-Earth orbit's altitude and inclination, and select the cataloged model identifier a radiation case must cite. Trigger: ecss, e-st-10-04c, annex i, particle radiation, trapped proton, trapped electron, solar energetic particle, galactic cosmic ray, albedo neutron, model selection, south atlantic anomaly, geomagnetic shielding.
- ▌ E1004 Sep Direction · ashfordeou bundleUse when characterizing the directional solar particle flux for a mission under ECSS-E-ST-10-04C 9.2.2.5: compute the interplanetary magnetic field connection geometry (Parker spiral angle) to categorize a solar particle event's magnetic connection, classify the event's arrival phase (anisotropic onset versus later quasi-isotropic diffusion), compute the cone angle between a look/arrival direction and the field-aligned streaming direction, apply the anisotropy scaling to an omnidirectional-equivalent flux, and verify that a case's magnetospheric entry channel has its required cutoff-rigidity check before closing the directional assessment. Trigger: solar particle event, SEP, SPE, anisotropy, cone angle, pitch angle, Parker spiral, magnetic connection, well-connected, directional flux, magnetospheric entry, polar cusp, E-ST-10-04C 9.2.2.5, ecss, space environment, radiation environment.
- ▌ E1004 Trapped Other · ashfordeou bundleUse when determining how the trapped-radiation environment applies to a non-LEO/GEO/MEO orbit (HEO, GTO, interplanetary transfer) under ECSS-E-ST-10-04C: determine the orbit regime from perigee/apogee altitude, split the trajectory into segments inside versus beyond the geomagnetically trapped domain using the magnetopause standoff distance, verify both trapped species (proton and electron) are covered wherever trapped-domain dwell exists, and hand off out-of-domain segments to the interplanetary radiation leaves rather than silently dropping them. Trigger: HEO, GTO, geostationary transfer orbit, highly elliptical orbit, interplanetary trajectory, escape trajectory, trapped radiation, magnetopause standoff, Van Allen belt crossing, e-st-10-04, ecss, space environment, radiation environment.
- ▌ E1006 Char Cm Trace · ashfordeou bundleUse when auditing configuration management traceability of requirements under ECSS-E-ST-10C §8.2.3: verify each requirement carries a unique identifier, a documented source trace linking it to an originating parent requirement, standard clause, or customer specification, and an assignment to a configuration baseline. Flag requirements with missing identifiers, empty source traces, unrecognized source types, or unassigned baselines. Identify duplicate requirement identifiers across the set. A requirement achieves CM-trace compliance only when its identity, source trace, and baseline assignment are all present and valid. Trigger: ecss, e-st-10c, e-st-10-system-scope, configuration-management, cm-trace, traceability, requirements-identity, cm-baseline.
- ▌ E1009 Documentation · ashfordeou bundleUse when maintain the Coordinate Systems Document (CSD) across the spacecraft project life cycle under ECSS-E-ST-10C §5.2.2: define each coordinate system with a unique identifier, origin, axis triad, and reference frame; validate entry completeness; enforce permissible lifecycle state transitions (draft -> review -> approved -> superseded); verify that required project phases each carry at least one applicable coordinate system; and compute a CSD readiness score to track documentation maturity. Trigger: ecss, e-st-10-system-scope, coordinate-systems-document, csd, reference-frame, axis-definition, lifecycle, project-phases, documentation-maturity.
- ▌ E1009 Transform Def · ashfordeou bundleUse when define each coordinate transformation in a spacecraft or system model under ECSS-E-ST-10-09C §5.4.9: specify every transform with a verbal statement, a rotation-matrix equation, and a figure reference; express each matrix relative to its parent frame using a declared row-column convention; and verify that numerical precision is consistent across all entries in the model. Check orthogonality (R^T R = I, determinant +1) for each rotation matrix, confirm the parent frame is in the defined frame set, and flag any transform missing its verbal description, figure reference, or declared convention. Trigger: ecss, e-st-10-system-scope, coordinate-transformation, rotation-matrix, parent-frame, row-column-convention, precision-consistency, frame-definition.
- ▌ E1009 Tree Analysis · ashfordeou bundleUse when map product-tree frame relationships and derive transformation chains per ECSS-E-ST-10C Annex B: register each assembly element as a body-frame node in a directed tree, verify the tree has a single root and no cycles, find the transformation chain between any two frames through the lowest common ancestor, compose the chain of 4x4 homogeneous matrices into one frame-to-frame transform, and export the Franck diagram edge list showing every parent-to-child frame link. Trigger: ecss, e-st-10-system-scope, transformation-tree, Franck-diagram, frame-relationships, product-tree, coordinate-chain, homogeneous-transform.
- ▌ E1011 Anthropometry · ashfordeou bundleUse when apply anthropometric and biomechanical reference data to spacecraft or habitat design under ECSS-E-ST-10-11C §4.5.1: determine the percentile range the design must accommodate (typically 5th–95th), interpolate body dimensions at the required percentile, check that every clearance and reach envelope covers the full target population, verify that required operator forces stay within the 5th-percentile strength limit, and apply microgravity spinal-unloading corrections to stature and seated-height before comparing with design envelopes. Trigger: ecss, e-st-10-system-scope, anthropometry, biomechanics, percentile, reach-envelope, strength-limit, microgravity-correction, human-factors, crew-provisions.
- ▌ E1011 Habitable Env · ashfordeou bundleUse when evaluate crew habitable environments under ECSS-E-ST-10-11C §4.7.1–4.7.2: verify net habitable volume per crew member against the minimum per-person threshold, assess atmospheric parameters (oxygen partial pressure, carbon dioxide partial pressure, total cabin pressure, temperature, relative humidity) against allowable bands, check layout provisions for emergency egress paths and workstation accessibility, and confirm hygiene-system allocations are on record for each compartment. The skill aggregates findings per compartment and flags every non-compliant or unrecorded item before the design review. Trigger: ecss, e-st-10-11c, habitable-environment, crew-provisions, atmospheric-habitability, volume-allocation, layout-design, hygiene.
- ▌ E1011 Physical Perf · ashfordeou bundleUse when evaluate crew physical performance and fatigue limits under ECSS-E-ST-10-11C §4.5.3: categorize each crew task by metabolic rate band (rest, light, moderate, heavy, or very heavy), check the continuous-work duration against the per-category allowable limit, compute the minimum required recovery period, flag any work bout that exceeds the sustained-performance threshold, and validate a full work-rest schedule against the daily workload accumulation limit for each category. Applicable to IVA and EVA crew scheduling, ergonomic compliance review, and mission-phase workload analysis. Trigger: ecss, e-st-10-system-scope, physical-performance, crew-workload, fatigue, metabolic-rate, work-rest-schedule, human-factors, ergonomics.
- ▌ E1012 Dd Assessment · ashfordeou bundleUse when assess displacement damage (DD) parameters for a spacecraft device under ECSS-E-ST-10-12C §8.5: determine the total non-ionizing dose (TNID) by summing NIEL-weighted fluence contributions across all particle species and energy bins for the mission environment, convert TNID to the displacement damage equivalent fluence (DDEF) referenced to a standard particle, apply the project radiation design margin (RDM) factor to the DDEF, and compare the margin-adjusted DDEF against the device displacement damage limit to determine compliance. Trigger: ecss, e-st-10-system-scope, displacement-damage, dd-assessment, tnid, ddef, niel, rdm, radiation-design-margin.
- ▌ E1012 Dd Expression · ashfordeou bundleUse when compute the displacement damage (DD) dose for a spacecraft device under ECSS-E-ST-10-12C §8.2: identify all contributing particle types and energy bins from the mission radiation environment, retrieve the Non-Ionizing Energy Loss (NIEL) value for each bin, multiply each bin fluence by its NIEL to obtain the partial DD contribution, sum all partial contributions to obtain the total DD dose in MeV/g, convert to a reference-particle equivalent fluence using the DD equivalence relation (NIEL ratio to the chosen reference), and compare the resulting equivalent fluence against the device displacement damage requirement. Trigger: ecss, e-st-10-system-scope, displacement-damage, niel, damage-factor, equivalent-fluence, radiation-effects, dd-dose, proton-damage.
- ▌ E1012 Phase Margins · ashfordeou bundleUse when establish project-phase radiation hardness margins for a space mission under ECSS-E-ST-10-12C §5.6: determine the required radiation design margin (RDM) at each review milestone (pre-PDR, PDR-to-CDR, post-CDR), verify that the RDM for total ionising dose and displacement damage meets or exceeds 2.0 relative to the predicted mission environment, confirm phase-appropriate hardness assurance activities are scoped, and validate that post-CDR test methods (cobalt-60, proton, heavy-ion, or verified heritage similarity) are appropriate for each radiation type. Apply at every phase gate where a component radiation tolerance is compared against the mission environment budget. Trigger: ecss, e-st-10-12c, e-st-10-system-scope, radiation-hardness-assurance, phase-margins, rdm, tid-margin, dd-margin, see-qualification, test-methods.
- ▌ E1012 Shield Sector · ashfordeou bundleUse when run detailed sector shielding calculations for a spacecraft component under ECSS-E-ST-10-12C §6.2.3: discretize the surrounding 4π steradians into directional sectors, ray-trace each direction through the spacecraft mass model to accumulate areal shielding density (g/cm²), apply dose-depth attenuation curves to derive the ionising dose contribution from each sector, and aggregate across all sectors to obtain total TID at the point of interest. Apply a radiation design margin (RDM) to the aggregated dose and compare against the part's qualified dose level to determine compliance. Suitable for shielding trade studies, shielding mass optimisation, and unit-level radiation hardness assurance verification. Trigger: ecss, e-st-10-12c, sector-shielding, ray-tracing, dose-depth, TID, radiation-design-margin, RDM, mass-model, radiation-hardness-assurance.
- ▌ E1012 Shield Simple · ashfordeou bundleUse when run the simplified shielding analysis for a sensitive component under ECSS-E-ST-10-12C §6.2.2: model the shield as a planar slab, a spherical shell, or a set of solid-angle sectors, compute the areal density of each layer as thickness × density, invert that relation to derive the thickness needed for an areal-density budget, flux-weight the mean areal density across sectors, verify the sector set covers the full 4π sphere within tolerance, and report the minimum and maximum shielded ray directions as the worst- and best-case exposure paths. Trigger: ecss, e-st-10-12c, simplified-shielding, planar-slab, spherical-shell, solid-angle-sectoring, areal-density, shielding-summary.
- ▌ E4008 Mission Start · ashfordeou bundleDerive the mission time scale from a declared mission start under ECSS-E-ST-40-08C clause 5.4.2, the single normative item that clause places on the instant mission time is measured from. Use when a schedule is written on the operational timeline rather than on run time: mapping mission time onto simulation time through mission start and the epoch at simulation zero, keeping a negative mission time legal so pre-separation activities survive, holding both scales in exact integer nanoseconds, and deciding whether a second declaration is unchanged, a restatement whose shift moves every entry, or refused because the simulator is already executing. Trigger: ecss, e-st-40-08-simulation-modelling-scope, e4008-mission-start, mission-time-scale, mission-start-declaration, negative-mission-time, mission-start-restatement-shift.
- ▌ E50 Error Detection · ashfordeou bundleCompute the error detection a space data transfer protocol owes under ECSS-E-ST-50C clause 5.6.13.4, whose three normative items ask that the link protocol detect errors at all, that the project set its own figure for the units the code lets through undetected, and — a recommendation, not a requirement — that the detection chosen suit the telemetry and telecommand performance of clause 5.6.11. Header coverage is not among the three and is graded here as this leaf's own discipline. Derive the corruption rate a channel bit error rate produces over a unit, the fraction that escapes a checksum or a CRC, the undetected units expected across a pass, and the weakest catalogue code that still meets the bound. Use when choosing a transfer-layer code or reviewing a data integrity budget. Trigger: ecss, e-st-50-communications, data-unit-error-detection, undetected-error-probability-budget, crc-coverage-of-header-and-payload, residual-error-rate-after-crc, transfer-layer-detection-code-selection.
- ▌ Drd Test Prediction · ashfordeou bundleUse when prepare a structural test prediction report per ECSS-E-ST-32C Annex Q: determine predicted response quantities (displacement, load, stress, natural frequency) at each monitoring point for every test load case, derive safety-abort thresholds from scaled finite-element analysis outputs, verify that predicted peak responses fall within instrument measurement ranges, and establish the analysis-to-test correlation acceptance band for each monitored quantity. Trigger: ecss, e-st-32-structures-scope, test-prediction, drd, structural-test, monitoring-point, abort-threshold, test-correlation, calculix-linear, annex-q.
- ▌ E10 Config Assembly · ashfordeou bundleUse when determining the physical and functional grouping rules that govern how configuration items are assembled for integration under ECSS-E-ST-10C clause 5.4.2.3: check every pair of configuration items proposed for one physical assembly for mounting-zone match, hazard separation between energetic and non-energetic items, and EMI role conflict between a sensitive and an emitting item; flag a functional grouping conflict when items sharing a function group are physically incompatible; account each assembly's total mass against its allocable mass budget; and derive a dependency-ordered integration sequence across assemblies. Trigger: ecss, e-st-10c, configuration assembly, configuration item grouping, physical grouping rules, functional grouping rules, integration sequence, mass budget, hazard separation, emi conflict.
- ▌ E10 Req Consistency · ashfordeou bundleUse when identify and resolve internal inconsistencies inside a requirement baseline under ECSS-E-ST-10C clause 5.2.3.6: reduce each requirement that bounds a shared parameter to the feasible interval its constraint implies, intersect the intervals of a group to find a parameter no value can satisfy, and compare every requirement binding on a shared interface attribute to find the same attribute given two different values. Trigger: ecss, e-st-10-system-scope, requirement-consistency, conflicting-requirements, constraint-interval, feasible-range, interface-attribute, requirement-baseline.
- ▌ E10 Req Maintenance · ashfordeou bundleUse when maintaining ECSS-E-ST-10C requirements under configuration control (clause 5.2.3.8): determine whether a requirement's lifecycle state transition (draft, proposed, baselined, obsolete) is allowed, verify that a change to a baselined requirement carries an approved change request before it is applied, assess the change's impact on derived requirements found via the parent-child traceability link and on verification items linked to the requirement, and confirm the impact assessment and a maintenance record are captured before the change is closed. Trigger: ecss, e-st-10c, requirement maintenance, configuration control, change impact assessment, derived requirements, verification impact, baseline change request.
- ▌ E10 System Analysis · ashfordeou bundleUse when scoping and scheduling ECSS-E-ST-10C system analyses for a space project: classify a required system analysis as mission, functional, interface, environmental, or operational, determine which analysis types a given project phase requires, verify each analysis definition carries a non-empty objective and defined outputs, and check whether an analysis is scheduled early enough to feed the phase that first requires it. Trigger: ecss, e-st-10-system-scope, system-analysis, mission-analysis, functional-analysis, interface-analysis, environmental-analysis, operational-analysis, analysis-scheduling.
- ▌ E10 Tech Matrix Drd · ashfordeou bundleUse when generating or validating the Technology Matrix deliverable per ECSS-E-ST-10C Annex F: check the document carries the required DRD sections, each listed technology carries the required matrix fields (name, current TRL, target TRL, mission applicability), TRL values are valid (integer 1-9) and non-regressing (target TRL at or above current TRL), and mission applicability is resolved rather than left blank or TBD. Trigger: ecss, e-st-10c, technology matrix, trl, technology readiness level, annex f, mission applicability, technology plan.
- ▌ E1002 Closeout Docs · ashfordeou bundleUse when consolidate verification close-out documentation under ECSS-E-ST-10C §5.4.4.2: gather all verification reports at the applicable review milestone, merge per-requirement verification statuses into a consolidated register, identify requirements that failed or were not verified and determine whether each needs a waiver or a deviation, draft register entries with technical justification and risk-level tag, and confirm every requirement carries a final disposition (Pass, Fail, Waived, or Deferred) before the review board gate. Trigger: ecss, e-st-10-system-scope, closeout-documents, verification-consolidation, waiver-register, deviation-register, review-gate, close-out.
- ▌ E1002 Other Reports · ashfordeou bundleUse when decide whether a verification activity needs documentation beyond the four report DRDs under ECSS-E-ST-10-02 clause 5.3.2.6, and check what is produced: derive the need from the activity's own trigger conditions rather than preference, confirm any additional report carries the minimum identification that makes it citable, confirm its author did not also approve it, and flag a report that restates the scope of a DRD report already produced for the same activity. Trigger: ecss, e-st-10-02c, additional-documentation, verification-reporting, trigger-conditions, report-duplication, self-approval, citability.
- ▌ E1002 Qualification · ashfordeou bundleUse when running the qualification stage of an ECSS-E-ST-10-02C verification programme: closing design qualification against requirements before acceptance/QR, tailoring the qualification scope by product heritage category (Table 5-1: new design, unmodified heritage within envelope, modified or envelope-exceeding heritage), and confirming every product in scope is closed with matching evidence. Trigger: qualification stage, design qualification, heritage product category, Table 5-1, qualification by similarity, delta qualification, qualification review, QR, e-st-10-02, ecss, e-st-10c.
- ▌ E1002 Tools General · ashfordeou bundleUse when a verification tool (test equipment, GSE, simulator, software tool, or facility) needs to be categorized and given a qualification-status category (A/B/C/D) before it is used to generate verification evidence, consistent with ECSS-E-ST-10-02C verification tools clause 5.2.6.1. Trigger: verification tool, tool classification, tool qualification status, category A B C D, GSE, EGSE, MGSE, simulator qualification, software tool validation, test facility, E-ST-10-02, ecss, e-st-10c.
- ▌ E1003 El Acceptance · ashfordeou bundleUse when determine the acceptance test baseline for a space hardware element under ECSS-E-ST-10C §6.3 and Tables 6-3/6-4: identify which test types are mandatory for the element category, derive acceptance levels from qualification levels by applying the prescribed margin factors (vibration random −3 dB, thermal range narrowed by the acceptance margin), confirm each test duration meets the category minimum, and verify the complete proposed test plan contains no missing required tests before acceptance test review is convened. Trigger: ecss, e-st-10c, element-acceptance, acceptance-test, test-baseline, acceptance-levels, test-duration, vibration-acceptance, thermal-acceptance, acceptance-margin.