ashfordeOU
- 1.3k skills
- 0 followers
- 5 repo stars
- 3 days ago last updated
- ▌ Test Analysis Correlation · ashfordeou bundleUse when assess the correlation between measured structural dynamic properties from a modal survey test and finite-element model predictions, per ECSS-E-ST-32C and ECSS-E-ST-32-11: pair each measured natural frequency and mode shape to its analysis counterpart by Modal Assurance Criterion (MAC), check the paired frequency deviation against the accepted tolerance, verify the MAC value meets the acceptance threshold for mode-shape similarity, flag modes that remain unpaired or breach either criterion, and confirm no discrepancy is outstanding before the FE model is released for load analysis. Trigger: ecss, e-st-32-structures-scope, test-analysis-correlation, modal-survey, mac, frequency-deviation, mode-pairing, fem-updating, structural-dynamics.
- ▌ E2008 Diode Human Body Esd · ashfordeou bundleUse when a human body ESD step stress for protection diodes is planned or audited. Assess whether a protection diode survives an electrostatic discharge representative of a charged person reaching its terminals, under ECSS-E-ST-20-08C clause 9.6.16: hold the discharge network capacitance and series resistance inside their bands, derive the peak current, decay constant, transferred charge and stored energy the step voltage produces, walk the geometric step ladder with its pulse count and both polarities, take the reverse leakage and forward voltage drift across the series, and group the surviving level into a withstand band. Trigger: ecss, e-st-20-08c-clause-9-6-16, protection-diode-human-body-esd, diode-hbm-discharge-network, diode-hbm-peak-current, diode-hbm-stored-energy, diode-hbm-withstand-band, diode-esd-leakage-drift, diode-esd-step-stress-ladder.
- ▌ Q7026 Crimping Operation · ashfordeou bundlePerform and grade one crimp cycle on a high-reliability electrical connection. Use when a crimp is being made and the setup has to be defensible before the handles move: match the die and positioner to the contact part number, take the selector setting from the wire gauge inside that contact, refuse a tool whose calibration has lapsed on date or on cycle count, confirm the ratchet released only on a completed cycle and that the barrel took exactly one, then grade the resulting height against its two-sided band and split remake from reject on the wire left. Trigger: ecss, q-st-70-26-crimping, crimp-die-and-positioner-match, crimp-selector-setting-by-gauge, crimp-tool-calibration-currency, crimp-ratchet-full-cycle, crimp-over-and-under-compression.
- ▌ Q7026 Terminal Placement · ashfordeou bundleAssess where a contact or terminal sits on a prepared conductor before the die closes. Use when a wire has been inserted into a barrel and the seating has to be graded while it can still be changed for free: measure the insulation-to-barrel gap against the band for that contact, confirm the conductor bottomed in the bore, read the inspection window fill, count strands left outside the barrel, check that insulation and conductor are each under their own grip, and grade how square the contact sits in the nest. Trigger: ecss, q-st-70-26-crimping, crimp-insulation-gap-band, crimp-conductor-bottoming-check, crimp-inspection-window-fill, crimp-strands-outside-barrel, crimp-contact-die-nest-seating.
- ▌ Q7040 Defect Disposition · ashfordeou bundlePlan the disposition of a braze defect that has failed acceptance, choosing between re-braze, local repair, a use-as-is deviation and scrap. Use when an indication has already been graded against its class limit and somebody has to pick a route the assembly can survive and the rules permit. Scores how far past the limit the defect sits, refuses a further thermal cycle once the re-braze budget or the cumulative exposure allowance is spent, never re-brazes a crack that has run into the parent metal, routes eroded parent metal away from more heat, demands an approved deviation before any use-as-is, and attaches the re-inspection each route owes. Trigger: ecss, q-st-70-40-brazing-scope, braze-defect-disposition, braze-rebraze-budget, braze-local-repair-route, braze-use-as-is-deviation, braze-cumulative-thermal-exposure, braze-rework-reinspection.
- ▌ Q7046 Lot Identification · ashfordeou bundleDefine the identity a threaded fastener lot carries into stores: the composed lot identifier, the marking the part can physically hold, the traceability chain behind it and the package it ships in. Use when a lot is about to be marked, labelled and packed and someone must say whether it can be told apart later: compose the identifier from manufacturer, part, heat, charge and date code over a restricted character set, size the marking against the area a hexagon head actually offers, hold the stamp depth to a fraction of the head height, keep the mark off the run-out of a fatigue part, and refuse a package holding two production lots. Trigger: ecss, q-st-70-46-threaded-fasteners, fastener-lot-identifier-composition, fastener-head-marking-capacity, fastener-marking-depth-limit, fastener-traceability-chain-gap, fastener-mixed-lot-package.
- ▌ Q7050 Tape Lift Sampling · ashfordeou bundleAssess a tape-lift surface sample under ECSS-Q-ST-70-50C and grade the surface it came from: subtract a blank lift, correct the counted size bands for the tape recovery efficiency on that finish, accumulate the bands from the largest downwards, scale the lifted area onto the reference area a cleanliness level is stated over, then grade each band and report the governing one. Use when reading a tape-lift count sheet, defending a recovery correction, or checking whether a lifted patch was large enough to describe the surface. Trigger: ecss, q-st-70-50c, tape-lift-sampling, tape-lift-recovery-efficiency, surface-particle-cumulative-count, blank-lift-subtraction, surface-cleanliness-level-grading.
- ▌ Rigid Body Motion Checks · ashfordeou bundleUse when verify that a finite element model passes rigid-body checks under ECSS-E-ST-32C clause 5.4: confirm the assembled mass matrix yields a total mass matching the reference value within tolerance, confirm that applying each of the six rigid-body displacement modes (three translations, three rotations) produces near-zero strain energy, and confirm that residual forces arising from rigid-body displacements are below the acceptance threshold. Each check produces a pass or fail result with a numeric residual; all three must pass for the model to be accepted. Trigger: ecss, e-st-32-structures-scope, rigid-body-checks, mass-matrix, strain-energy, residual-forces, fem-verification, finite-element.
- ▌ Acceptance Test Programme · ashfordeou bundleUse when plan and execute acceptance proof and leak tests on flight hardware under ECSS-E-ST-32C clause 5.5: determine the required proof pressure for each pressurized assembly from its maximum design pressure and the applicable proof factor, confirm the applied test pressure meets or exceeds the requirement and that the hold duration satisfies the minimum dwell time, evaluate the measured leak rate against the allowable limit for each sealed assembly, and determine overall programme acceptance only when every test item passes. Trigger: ecss, e-st-32c, acceptance-test, proof-test, leak-test, flight-hardware, pressure-vessel, structural-acceptance.
- ▌ Alignment Geometry Checks · ashfordeou bundleUse when verifying that structural components meet alignment accuracy, dimensional stability, and geometrical form requirements per ECSS-E-ST-32C clauses 4.6.3.19–4.6.3.21. Check each component's measured alignment (angular and translational) against its specified tolerance; assess dimensional change from baseline against the stability budget across thermal, hygroscopic, creep, and other drivers; verify geometrical form deviations (flatness, straightness, circularity, parallelism, perpendicularity, angularity, runout) against interface control drawing allowables; and aggregate findings to determine overall compliance. Trigger: ecss, e-st-32-structures-scope, alignment-checks, dimensional-stability, geometrical-control, tolerance-verification, structural-geometry, interface-control.
- ▌ Drd Cad Model Description · ashfordeou bundleUse when validate a CAD model and drawing description document (CADMDD) for structural design delivery under ECSS-E-ST-32C Annex A: confirm the model format is an accepted exchange or native type, verify the coordinate system definition (origin, axes, handedness), check assembly tree completeness and component identification, validate drawing title block required fields, assess mass property completeness (mass, centre of gravity, inertia tensor), confirm interface definitions carry type and mating-component, and determine the overall delivery maturity and configuration status against release criteria. Trigger: ecss, e-st-32-structures-scope, cad-model, drawing-description, cadmdd, mass-properties, coordinate-system, model-delivery.
- ▌ Dynamic Response Analysis · ashfordeou bundleUse when compute the dynamic response of a spacecraft structure to sine, random, or shock loading per ECSS-E-ST-32C clause 4.6.2.5: apply the dynamic amplification factor to a swept-sine excitation, derive the RMS and 3-sigma acceleration response to a random-vibration input via Miles' equation, evaluate the shock response spectrum for a half-sine pulse, or identify which analysis type applies to a given load event. Categorize each load event as sine, random, shock, or transient before selecting the response model; flag any load event that does not map to a recognized category. Trigger: ecss, e-st-32-structures-scope, dynamic-response-analysis, random-vibration-analysis, shock-response-spectrum, sine-response, miles-equation, sdof-oscillator.
- ▌ E10 Analysis Report Guide · ashfordeou bundleUse when assemble an engineering analysis report to the ECSS-E-ST-10C Annex S content guideline so its result can be cited as verification evidence: confirm every required section carries content, confirm each input datum states where it came from, confirm the analysis tool is named with its qualification status, confirm every reported result carries an uncertainty, and confirm a compliance conclusion actually survives its own uncertainty against the limit. Trigger: ecss, e-st-10-system-scope, analysis-report, annex-s-guideline, input-provenance, tool-qualification, result-uncertainty, verification-evidence.
- ▌ E10 Analysis Tools Models · ashfordeou bundleUse when validate the analysis methods, tools and models behind a space system analysis before its results are used, under ECSS-E-ST-10C clause 5.3.4: decide whether a tool qualifies by heritage reuse or must be correlated, compute its correlation error against independently derived reference data, compare that error against the acceptance tolerance set by the analysis criticality, and aggregate every tool review into a single verdict on whether the analysis is valid. Trigger: ecss, e-st-10-system-scope, analysis-tools, model-qualification, tool-correlation, heritage-reuse, domain-of-applicability, analysis-criticality.
- ▌ E1002 Other Planning Docs · ashfordeou bundleUse when determine which other ECSS-E-ST-10-02C verification planning documents (the interface to the AIT plan, the analysis plans) are required for a set of requirements based on the verification method assigned to each one, check every required document against its minimum content fields and against full cross-reference coverage of the requirement identifiers assigned to its method, track each document's draft/in_review/approved status, and roll up an overall other-planning-documents readiness status and compliance flag for the verification programme. Trigger: ecss, e-st-10-02c, verification planning, AIT plan interface, analysis plan, other planning documents, verification method, document completeness, requirement linkage, planning document status roll-up.
- ▌ E1002 Verification Report · ashfordeou bundleUse when compile or audit the Verification Report against the ECSS-E-ST-10-02 clause 5.3.2.5 and Annex F Document Requirements Definition: confirm every verification event cites the underlying report holding its evidence, reconcile the executed methods against the methods the verification control document planned in both directions, detect an event whose claimed status contradicts the verdict of the report it cites, and roll the events up to a status for each requirement. Trigger: ecss, e-st-10-02c, verification-report, vrpt, annex-f-drd, method-agreement, evidence-linkage, status-rollup.
- ▌ E2007 Peak Detector Usage · ashfordeou bundleValidate that every frequency-domain emission or susceptibility measurement uses peak detection under ECSS-E-ST-20-07C clause 5.2.8.2: reject averaging, root-mean-square, sample and quasi-peak detectors that report below the true peak, derive the dwell each measured point receives from the sweep time and point count, compare it against the resolution-bandwidth response time and the pulse repetition interval, check the frequency step against the resolution bandwidth so a narrow signal cannot slip between bins, and return the governing run. Use when a receiver setup or a test report must be shown to record peaks rather than averages. Trigger: ecss, e-st-20-07c, frequency-domain-peak-detector, resolution-bandwidth-response-time, receiver-dwell-per-bin, pulse-repetition-interval-dwell, spectrum-bin-step-check.
- ▌ E2007 Tested Unit Bonding · ashfordeou bundleUse when verify that a tested unit is bonded to the test reference-plane only through the bonding provisions built into its own design, as ECSS-E-ST-20-07C clause 5.2.6.2 requires: categorize each bond path as design-provided or test-added, raise every test-added jumper as a setup non-conformance, compute the series strap-and-contact resistance of each design-provided path and the parallel effective bonding-resistance of the set, compare it with the declared bonding-resistance requirement, check each bond-strap length-to-width ratio against the low-inductance geometry rule, and reconcile the computed value with the bench reading. Trigger: ecss, e-st-20-electrical-scope, tested-unit-bonding, bonding-provisions, bonding-resistance, bond-strap-aspect-ratio, reference-plane-bonding, design-provided-bonding, test-added-jumper.
- ▌ E2008 Coverglass Delivery · ashfordeou bundleEvaluate whether an offered coverglass shipment may leave under ECSS-E-ST-20-08C clause 8.10. Use when a dispatch of ordered coverglasses is presented for release with the documentation set the order agreed: hold every batch whose agreed documents are absent, written to a superseded issue, unsigned or issued against another batch; fill each ordered line from its own coverglass type before any alternative the order named, and never from one it did not; reconcile every line short and every surplus piece; and apply the declared partial-delivery floor under a named tolerance. Trigger: ecss, e-st-20-08c-clause-8-10, coverglass-dispatch-release, coverglass-agreed-documentation-set, coverglass-batch-document-coverage, coverglass-type-substitution-permission, coverglass-partial-delivery-floor.
- ▌ Microvibration Analysis · ashfordeou bundleUse when determine the micro-vibration environment of a spacecraft structure under ECSS-E-ST-32C clause 4.6.2.21: categorize each disturbance source as rotating (reaction wheels, momentum wheels, cryocoolers, pumps), periodic-low-frequency (solar array drives), or impulsive (thruster valves), compute harmonic frequencies for each rotating source, apply the structural transmissibility from source mounting to sensitive equipment, check whether any harmonic falls within the instrument sensitive frequency band, compute the induced micro-vibration amplitude at equipment, and verify compliance against the instrument micro-vibration allowable. Trigger: ecss, e-st-32-structures-scope, microvibration, micro-vibration, reaction-wheel, disturbance-source, transmissibility, sensitive-instrument, jitter, harmonic.
- ▌ Q7005 Equipment Control · ashfordeou bundleAudit the spectrometer, the measurement cells and the sampling consumables an infrared contamination analysis rests on. Use when a run under ECSS-Q-ST-70-05C has to be cleared before a sample is taken: walk each calibration and each consumable shelf life forward by whole calendar months so a month end lands where the calendar puts it, report the days left on the analysis day rather than on today, weigh the wavenumber tolerance against the uncertainty that polices it, grade a cell pathlength as a fraction of nominal, and refuse a cell or wipe blank that sits too close to the quantitation limit beside it. Trigger: ecss, q-st-70-05-ir-contamination-scope, ir-spectrometer-calibration-currency, measurement-cell-pathlength-verification, sampling-consumable-shelf-life, precleaned-consumable-blank-level, wavenumber-tolerance-uncertainty-ratio.
- ▌ Q7022 Re Test Procedure · ashfordeou bundlePrepare the re-test a stored material owes before its shelf life is extended under ECSS-Q-ST-70-22, and grade what comes back: take the property set from the material family, take the specimen count from the lot size, derive each acceptance threshold from the as-manufactured value and a declared retention fraction in the direction that property may drift, compare with a relative tolerance so a result on the limit passes everywhere, and keep a failed re-test distinct from an incomplete one. Use when an extension request needs test evidence. Trigger: ecss, q-st-70-22, shelf-life-re-test-plan, re-test-acceptance-threshold, re-test-property-retention, re-test-specimen-count, re-test-incomplete-versus-failed.
- ▌ Q7026 Harness Interface · ashfordeou bundleCoordinate the crimping requirements of ECSS-Q-ST-70-26C with the harness manufacturing rules of ECSS-Q-ST-20-30C so the shop works to one instruction per topic. Use when both documents reach the same harness bench and somebody has to say which governs: allocate every shared topic to one owning document, take the stricter limit where both state one in the same direction, let a declared subordination outrank the arithmetic, keep a floor and a ceiling as a band unless that band is empty, escalate two differing rules instead of quietly picking one, and report the topics neither document owns. Trigger: ecss, q-st-70-26, q-st-20-30, crimp-harness-interface, crimp-harness-topic-allocation, crimp-harness-requirement-conflict, crimp-harness-stricter-limit.
- ▌ E10 Budget Margin Policy · ashfordeou bundleUse when consolidating technical budgets (mass, power, data rate, pointing, thermal, propellant, etc.) at system level under ECSS-E-ST-10C flow-down and applying the project margin policy: roll up contributor current-best-estimate plus maturity margin, add the system-level contingency margin, and check the result against the allocated value with a phase-appropriate minimum remaining margin. Trigger: ecss, e-st-10c, technical budget, budget consolidation, margin policy, mass budget, power budget, data rate budget, link budget, contingency margin, maturity margin, system margin.
- ▌ E10 Product Verification · ashfordeou bundleUse when verify a product against its Technical Specification and close the verification out under ECSS-E-ST-10C clause 5.5.2: confirm each requirement carries at least one recognized verification method, resolve each assigned method to a status from its recorded objective evidence, partition the product's requirements into verified, open, failed and no-method-assigned, and decide whether the verification file supports close-out. Trigger: ecss, e-st-10-system-scope, product-verification, verification-methods, objective-evidence, close-out, djf, verification-file, technical-specification.
- ▌ E1006 Char Justification · ashfordeou bundleUse when verify that every system requirement in the requirements database carries a recorded justification explaining why the requirement exists, per ECSS-E-ST-10C §8.2.2. For each requirement, determine whether the justification field is populated and whether the justification cites a traceable source — such as a stakeholder need, mission objective, standard clause, derived rationale, or safety argument. Flag any requirement whose justification text is absent or empty, and any requirement whose justification source reference is not recorded or belongs to an unrecognised source category. Produce a per-requirement verdict and a summary count of non-compliant items across the set. Trigger: ecss, e-st-10-system-scope, requirement-justification, rationale, char-justification, traceability, requirements-management, §8.2.2.
- ▌ E1011 Assessment Process · ashfordeou bundleUse when run the continuous assessment process for a space system project under ECSS-E-ST-10 clause 4.10.1: categorize each finding by type (observation, action item, non-conformance), evaluate technical performance measures against their thresholds to derive a nominal/marginal/exceeded status, determine closure validity for each finding, compute the overall compliance status across all open findings and measure outcomes, and generate the structured Annex C assessment-report fields. The process applies at every review event across all project phases; open non-conformances and exceeded thresholds both block a compliant outcome. Trigger: ecss, e-st-10-system-scope, continuous-assessment, technical-performance-measure, finding-categorization, review-event, annex-c-report, compliance-status.
- ▌ E2008 Bare Cell Delivery · ashfordeou bundleUse when a shipment is offered: hold every cell drawn from a lot whose data package is not released, disposition each cell as shippable, shippable on an accepted concession or held, fill each ordered grade line from that grade before any upgrade the order permits, reconcile every line short and over, and apply the declared partial-delivery floor. Evaluate whether a dispatch of ordered bare solar cells may leave under ECSS-E-ST-20-08C clause 7.8, where the hardware and its matching documentation set have to close together. Trigger: ecss, e-st-20-08c, clause-7-8, bare-cell-dispatch-release, bare-cell-lot-documentation-coverage, bare-cell-grade-line-allocation, bare-cell-upgrade-substitution-rule, bare-cell-partial-delivery-floor.
- ▌ E50 Bandwidth Allocation · ashfordeou bundleAllocate link bandwidth across the data flows a space communication system carries, under ECSS-E-ST-50C clause 5.3.1: each flow is sized from its own rate and the overhead its protocol stack adds, and the sum of the allocations plus the reserved margin stays inside the capacity of the link they share. Compute per-flow allocations, the aggregate, the margin actually achieved and the shortfall when there is one, separating a link that eats its margin from one that does not fit at all, and cut proportionally when it cannot. Use when sizing or reviewing a spacecraft communication link budget. Trigger: ecss, e-st-50-communications, communication-bandwidth-allocation, link-capacity-oversubscription, protocol-overhead-factor, per-flow-rate-sizing, link-bandwidth-margin-policy.
- ▌ E50 Data Unit Identifier · ashfordeou bundleVerify that every formatted data unit a space link carries holds an identifier naming its source, its destination or both, under ECSS-E-ST-50C clause 5.6.13.2, then size the counter field that carries that identifier so it still names one unit for as long as the design acts on it. Compute the modulus of the counter field, the period it takes to wrap, how many units are live inside the retention window, and the coverage of one against the other; separate a field that wraps inside the window from one that covers it with no margin; size the narrowest field that works by exact integer doubling; and read an observed run for gaps, wraps and repeats. Use when sizing or reviewing data unit counters. Trigger: ecss, e-st-50-communications, data-unit-identifier-field-width, data-unit-counter-wrap-ambiguity, data-unit-sequence-gap-detection, data-unit-retention-window-coverage.
- ▌ E50 Isochronous Services · ashfordeou bundleEvaluate whether a delivery stream meets the isochronous service obligation of ECSS-E-ST-50C clause 5.6.14.4, where a service promised at a fixed cadence has to arrive on that cadence and not merely at the right average rate. Compute every delivery's deviation from the ideal grid, the peak-to-peak jitter, the playout buffer that would re-time the stream, and the smallest tolerance the run would have passed under, then separate a rate error that walks the stream off the grid from bounded jitter that stays put. Use when accepting or reviewing an isochronous downlink, playback or synchronous bus service. Trigger: ecss, e-st-50-communications, isochronous-delivery-jitter, isochronous-grid-deviation, isochronous-playout-buffer-sizing, isochronous-rate-drift, isochronous-cadence-acceptance.
- ▌ E50 Time Synchronization · ashfordeou bundleDetermine whether two spacecraft sharing an inter-spacecraft network really hold their clocks together under ECSS-E-ST-50C clause 5.7.4.5. Recover the offset and the round trip from the four timestamps of one exchange, then budget what the exchange cannot cancel: static path asymmetry, the asymmetry relative motion opens while the responder holds the reply, timestamp resolution and jitter, plus the walk-apart at the relative drift rate before the next exchange. Use when sizing a synchronization interval, budgeting a coordination window, or reviewing a two-way transfer design on a formation, relay or rendezvous pair. Trigger: ecss, e-st-50c-clause-5-7-4-5, inter-spacecraft-time-synchronization, two-way-time-transfer-exchange, clock-offset-estimate-error, range-rate-reciprocity-error, synchronization-interval-sizing, relative-clock-drift-budget.
- ▌ Q6013 Class 2 Connectors · ashfordeou bundleUse when a harness connector has to become an application verdict. Assess whether a connector with removable contacts may be applied at the intermediate assurance class under ECSS-Q-ST-60-13C clause 5.6.6: refuse a connector naming no insert arrangement or removal tool, name every contact worked past the insertion limit, derate the rated contact current for the class and again for the share of positions energised at once, name every position over that allowance, take the planned matings as a share of the rated durability, check the spare provision, and score the build evidence, crediting a heritage claim below a direct record. Trigger: ecss, q-st-60-13c-clause-5-6-6, class-two-removable-contact-connector, removable-contact-insertion-limit, connector-contact-current-derating, connector-insert-loading-factor, connector-mating-cycle-durability, connector-spare-contact-provision.
- ▌ Q6013 Class 3 Connectors · ashfordeou bundleUse when a harness connector choice has to become a documented decision. Evaluate whether a connector family and the contacts going into it may be adopted at the lowest assurance class of ECSS-Q-ST-60-13C clause 6.6.6: derate each candidate's rated contact current for the class and again for the share of positions loaded, refuse a family short of current, short of spare positions or standing on no specification, rank the admissible families and pick one, then settle contact sourcing: refuse an unidentified lot outright, credit an alternative source below the connector manufacturer only where an interchangeability record exists, and score the selection evidence, crediting a supplier declaration below a project record. Trigger: ecss, q-st-60-13c-clause-6-6-6, class-three-connector-family-selection, connector-contact-sourcing-credit, contact-interchangeability-record, connector-contact-current-derating, connector-spare-position-share, class-three-connector-selection-verdict.
- ▌ Q7006 In Situ Vs Ex Situ · ashfordeou bundleDetermine whether each property of a particle or UV irradiation is read out without breaking vacuum or after transfer, under ECSS-Q-ST-70-06C. Use when a bleaching or air-sensitive property must be measured and the handling between chamber and instrument can undo what the beam did. Converts the transfer time and the recovery half-time into the fraction that has already come back, forces an in-situ read-out once that fraction passes its ceiling or the surface meets air, humidity or repeated openings, derives the transfer-time ceiling, and mandates the sealed, dry, light-tight handling an ex-situ read-out has to carry. Trigger: ecss, q-st-70-06, in-situ-versus-ex-situ-read-out, radiation-induced-darkening-recovery, transfer-time-ceiling, specimen-handling-controls, air-sensitive-specimen-transfer, chamber-opening-count.
- ▌ Q7026 Crimp Tool Control · ashfordeou bundleVerify that a crimp tool, die and positioner set is certified for the contact in front of it and that its calibration is still live under ECSS-Q-ST-70-26C. Use when a tool is drawn from the pool for a flight harness and both the calendar interval and the crimp count since last calibration have to be honoured. Matches die and positioner to the contact part number and conductor range, consumes the allowance on whichever of elapsed days or accumulated cycles runs out first, honours a withdrawal in the register, and returns released, book-for-calibration, overdue or not-certified. Trigger: ecss, q-st-70-26, crimp-tool-certification, crimp-die-positioner-match, crimp-tool-calibration-interval, crimp-cycle-count-allowance, crimp-tool-withdrawal.
- ▌ Riveted Joint Analysis · ashfordeou bundleUse when verify a riveted structural joint per ECSS-E-ST-32C clause 4.6.2.15: distribute applied shear and in-plane moment to individual rivets using the centroid method, compute rivet shear force and sheet bearing stress for each fastener, determine the inter-rivet buckling critical stress for the skin panel between fasteners, and evaluate crippling stress for each thin-walled outstanding flange element. Flag any rivet or panel element with a negative margin of safety before issuing a stress report. Covers single-shear and double-shear rivet patterns, inter-rivet skin buckling under compressive running load, and outstanding-flange crippling. Trigger: ecss, e-st-32-structures-scope, riveted-joint, shear-transfer, inter-rivet-buckling, crippling-analysis, rivet-pattern, fastener-margin, bearing-stress.
- ▌ Strength Functionality · ashfordeou bundleUse when verify strength functionality requirements per ECSS-E-ST-32C clause 4.3.2 across all levels of assembly: confirm no yielding occurs at the Design Yield Load (DYL) and no failure at the Design Ultimate Load (DUL). Scale limit loads by yield and ultimate factors of safety, evaluate multiaxial stress states with the von Mises criterion, and compute margins of safety for yield and ultimate thresholds at each assembly level (component, subsystem, system). Flag any level where a margin falls below zero. Applicable to linear and nonlinear finite element analyses. Trigger: ecss, e-st-32-structures-scope, strength-functionality, margin-of-safety, design-yield-load, design-ultimate-load, von-mises, factors-of-safety.
- ▌ Adaptive Backstepping · ashfordeou bundleUse when you must design and simulate the tuning-functions adaptive backstepping control law for a second-order strict-feedback plant x1_dot = x2 + theta f1(x1), x2_dot = u + f2(x1, x2) with the unknown constant plant parameter theta inside the recursion: update the single parameter estimate theta_hat with the second tuning function carried through the z1 z2 error recursion, assemble the adaptive virtual control and the final control, and audit the augmented Lyapunov function with the parameter-error term. Produces the error-variable and parameter-estimate histories, the tuning-function updates, the closed-loop command, and the parameter-error convergence verdict that gate an adaptive backstepping control assessment. Trigger: adaptive-backstepping, tuning-function, parameter-estimate, strict-feedback, adaptive-virtual-control, augmented-lyapunov-function, parameter-error-convergence, no-over-parameterization.
- ▌ Cospe Nonmetallic Liner · ashfordeou bundleUse when assess the structural integrity of a composite overwrapped pressure vessel with a homogeneous non-metallic liner per ECSS-E-ST-32C clause 4.6.3: categorize the liner material family, verify the proof pressure and burst pressure factors against the maximum allowable working pressure, check liner strain at proof pressure against the liner allowable strain, validate the overwrap fiber volume fraction, and apply environmental degradation to the effective burst margin. A vessel assessment is not compliant until all margin checks pass. Trigger: ecss, e-st-32-structures-scope, cospe, composite-overwrapped-pressure-vessel, nonmetallic-liner, burst-factor, proof-factor, strain-compatibility.
- ▌ E10 Delivery Per Review · ashfordeou bundleUse when planning or checking which systems-engineering documents a space project must deliver or re-baseline at each review milestone per ECSS-E-ST-10C Annex A (informative): build the document-by-review delivery schedule, verify a given review's deliveries against it (missing and unplanned deliveries), and roll up readiness across the whole review sequence. Trigger: delivery schedule, document delivery per review, Annex A, review deliverables, MDR PRR SRR PDR CDR QR AR FRR CRR ER documents, ECSS-E-ST-10C Annex A.
- ▌ E10 Phase Task Overview · ashfordeou bundleUse when checking per-phase system engineering task lists and outputs under ECSS-E-ST-10C: confirm the project's tasks for lifecycle phases 0 through F (mission analysis through disposal) are identified and tracked against the System Engineering Plan (SEP) deliverables. ECSS-E-ST-10C clause 4.3.3-4.3.9 gives the informative per-phase task overview. Trigger: ecss, e-st-10c, phase task, lifecycle phase, phase 0, phase A, phase B, phase C, phase D, phase E, phase F, systems engineering, 4.3.3, space systems engineering.
- ▌ E10 Systems Engineering · ashfordeou bundleUse when scoping or gating European space systems engineering per ECSS-E-ST-10C: determine the lifecycle phase (0 through F), map each phase to its review gate (MDR, PRR, SRR, PDR, CDR, QR, AR, FRR, CRR, ER), and validate that a phase is ready to exit when its required review records are complete. The phase-gate sequence drives program planning and procurement milestones for space systems, from mission analysis through disposal. Trigger: ecss, e-st-10c, lifecycle phases, phase gate, mdr, prr, srr, pdr, cdr, qr, ar, frr, space systems engineering.
- ▌ E1002 Inspection Report · ashfordeou bundleUse when produce or audit an inspection report against the ECSS-E-ST-10-02 clause 5.3.2.4 and Annex E Document Requirements Definition: judge each variable characteristic against its own tolerance band with the limits included, take an attribute characteristic's recorded result, confirm the measuring equipment held a calibration valid on the day the measurement was taken, confirm the inspector appears on the qualified roster, and separate characteristics never inspected from those inspected and found out of tolerance. Trigger: ecss, e-st-10-02c, inspection-report, annex-e-drd, tolerance-band, calibration-validity, inspector-qualification, conformity.
- ▌ E1002 Method Inspection · ashfordeou bundleUse when applying the inspection verification method under ECSS-E-ST-10-02C clause 5.2.2.5: categorize each checklist item as a visual or measurement inspection technique, decide whether inspection may be used for a given requirement, evaluate a visual item outcome and a measurement item outcome against their criteria, check the inspection programme's completeness in the verification plan, and roll the item statuses up to an overall inspection verdict. Trigger: ecss, e-st-10-02c, inspection method, visual inspection, measurement check, checklist, verification plan, item outcome, roll-up.
- ▌ E1004 Trapped Proton Wc · ashfordeou bundleUse when computing worst-case trapped proton radiation flux spectra for a space mission per ECSS-E-ST-10-04C: apply AP-8/AP-9-class models over solar maximum and solar minimum epochs, build the point-wise maximum envelope across source models and epochs, and categorize which source dominates at each energy to support radiation design margin analysis. Trigger: trapped protons, AP-8, AP-9, solar maximum, solar minimum, worst-case spectrum, point-wise envelope, radiation design margin, e-st-10-04, ecss.
- ▌ E1006 Char Completeness · ashfordeou bundleUse when assess requirement-set completeness against a mission or function decomposition tree per ECSS-E-ST-10C §8.2.8: verify every leaf node in the tree has at least one covering requirement, every requirement traces to a known tree node, and no invalid trace references exist. Flag uncovered leaf nodes as completeness gaps. Flag requirements with no valid tree trace as uncategorized. Flag trace references to nonexistent nodes as data-entry errors, distinct from structural gaps. Returns a structured result: uncovered leaves, orphan requirements, and invalid trace pairs; is_complete is True only when all three lists are empty. Trigger: ecss, e-st-10-system-scope, e-st-10c, requirement-completeness, function-tree, mission-tree, traceability, gap-analysis, requirement-coverage.
- ▌ E1011 Training Approach · ashfordeou bundleUse when defining the training approach for human operators as required by ECSS-E-ST-10-11C §4.3.5: categorize each operator task by criticality and worst-case error consequence, determine the minimum required training level (awareness, procedural, or expert), select admissible training means (simulation, CBT, classroom, on-the-job, handbook, or briefing), assign a training strategy (initial, recurrent, refresher, or qualification), set the recurrent interval for strategies that repeat, and verify every identified task has a training approach record so no task enters operation without a traceable HFE training provision. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, training-approach, human-factors-engineering, hfe, operator-training, training-level, training-strategy, training-means.
- ▌ E2008 Bare Cell Marking · ashfordeou bundleUse when a bare cell delivery register, cell marking scheme or wafer-lot traceability claim has to be reviewed. Audit the permanent traceability code marked on delivered bare solar cells under ECSS-E-ST-20-08C clause 7.1.3: decide whether the marking method and the place it is put are admissible on a brittle cell at all, whether the mark stays readable through the welding, bonding, cure and cycling the cell will see, how much illuminated area the mark costs against the policy cap, what depth the coded fields and the delivery register actually reach against the depth the process document sets, and whether a code repeats across the delivered set. Trigger: ecss, e-st-20-08c, bare-cell-permanent-marking, bare-cell-traceability-depth, bare-cell-mark-placement-admissibility, bare-cell-active-area-mark-loss, bare-cell-code-uniqueness-register, wafer-lot-traceability-claim.
- ▌ E50 Guaranteed Delivery · ashfordeou bundleVerify the guaranteed delivery service of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.14.2, whose single normative item obliges the space link to carry every data unit handed to the service through to the far end and to keep the sending order, with no allowance for one that does not arrive. Replay a delivery trace and separate the losses from the duplicates from the reorderings, compound the per-attempt loss over the retransmissions to get the residual, derive the attempts a residual target needs, and report a service that drops units at all — silently or otherwise. Use when specifying or auditing an acknowledged transfer service. Trigger: ecss, e-st-50-communications, guaranteed-delivery-service, exactly-once-data-unit-delivery, in-order-delivery-verification, residual-loss-after-retransmission, delivery-failure-notification-to-sender.
- ▌ E50 Sequence Identifier · ashfordeou bundleSize the sequence identifier of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.13.3, which asks that each transferred data unit carry an identifier the receiver can use to tell loss, duplication and reordering apart. Compute the identifier space a field width gives, the largest outstanding window that space keeps unambiguous under go-back-N or selective repeat, the field width a required window actually needs, and how long the mission runs before the space wraps. Replay a received identifier trace and name the gaps, repeats and reorderings it contains. Use when sizing a sequence number field or reviewing a retransmission window on a space link. Trigger: ecss, e-st-50-communications, space-link-sequence-identifier, sequence-identifier-field-width, sequence-number-wraparound-ambiguity, sliding-window-sequence-space, selective-repeat-sequence-modulus, out-of-order-data-unit-detection.
- ▌ E7041 Action Initiation · ashfordeou bundleDetermine whether a detected on-board event actually releases its bound request, under ECSS-E-ST-70-41C clause 6.19.5.2. Use when an event was reported and the expected command never went out, or when one noisy sensor turned a single binding into a command storm: reading the function-level switch before the per-definition one so the answer names the switch that stopped it, separating an event no definition covers from one whose definition is disarmed, releasing the request the definition already holds, treating every occurrence as its own release rather than coalescing repeats, and computing the peak release rate against a stated limit. Trigger: ecss, e-st-70-41c, event-action-initiation, event-action-release-decision, event-action-two-level-arming, event-action-release-storm, event-action-uncovered-event-detected, event-action-peak-release-rate.
- ▌ In Service Surveillance · ashfordeou bundleUse when evaluate the in-service surveillance programme for a spacecraft or launcher structural assembly under ECSS-E-ST-32C section 4.8: identify items requiring periodic inspection, assign inspection type (visual, NDT, dimensional) and interval based on structural criticality and consumed fatigue fraction, assess detected damage against allowable damage limits, determine residual strength when damage exceeds the allowable, and decide whether to accept, accept under continued-flight rationale, repair, or replace the affected component. Flag items with missing residual strength analysis before continued operation. Trigger: ecss, e-st-32-structures-scope, in-service-surveillance, inspection, damage-evaluation, maintenance, repair, structural-health, fatigue-fraction, continued-flight.
- ▌ E3301 Flushing Purging · ashfordeou bundleDetermine whether a mechanism needs an inert dry-gas blanket under ECSS-E-ST-33-01C clause 4.2.6, then size the one it needs. Use when operation or storage in ambient air would degrade the mechanism through lubricant oxidation, moisture uptake, corrosion or a friction rise, and the blanket has to be engineered rather than assumed: choosing a gas that is actually inert against the declared driver, computing the enclosure volume exchanges and flush duration that reach a residual target, working out the pump-and-backfill cycles a vacuum route needs instead, grading dew point and purity, and checking the blanket is unbroken across every ground phase. Trigger: ecss, e-st-33-01-mechanisms-scope, mechanism-inert-gas-purge, dry-gas-flushing-plan, purge-volume-exchange, purge-dew-point-limit, pump-and-backfill-cycles, ground-phase-purge-continuity.
- ▌ E4008 Validation Rules · ashfordeou bundleValidate the body of a simulator exchange file against the rules of ECSS-E-ST-40-08C clause 5.7.2.2. Use when the task is running the structural pass over each entry for required fields, declared types and smuggled-in extra fields, then the referential pass over the whole file for identifier uniqueness, references that resolve to an entry of the kind the field expects, and cycles in the parent, base and link graph, keeping a structurally broken entry out of the reference graph and saying so rather than dropping it. Grades a file against the two normative items. Trigger: ecss, e-st-40-08c, exchange-file-validation-pass, exchange-file-structural-validation, exchange-file-referential-integrity, duplicate-exchange-identifier, unresolved-entry-reference, exchange-reference-cycle.
- ▌ E50 Expedited Delivery · ashfordeou bundleAnalyze the expedited delivery service of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.14.3, whose single normative item asks that urgent data reach the far end ahead of the traffic already queued for the link. Compute the latency an urgent unit sees under no expedited class, a non-preemptive class that waits for the unit in service, and a preemptive class that interrupts it, compare each against the deadline, report the service rate or the policy change that would meet it, and check that the expedited load still leaves the normal traffic a share of the link. Use when specifying urgent data handling or reviewing link priority. Trigger: ecss, e-st-50-communications, expedited-data-delivery-service, expedited-queue-bypass-latency, preemptive-expedited-transmission, expedited-traffic-starvation-of-normal-traffic, urgent-data-unit-deadline.
- ▌ E7041 Request Sequence · ashfordeou bundleModel the on-board request sequence of ECSS-E-ST-70-41C clause 6.21.4 and decide whether one is well formed, holdable and runnable. Use when reasoning about a named block of requests the ground fires with a single command: keeping the identifier unique in the sequence store, insisting on at least one request and treating the held order as part of the sequence, checking each request would stand alone, refusing a sequence that loads or runs itself, fitting the loaded size to the declared store capacity, policing the absent to loaded to executing lifecycle, and stopping a run at the first failing request. Trigger: ecss, e-st-70-41-packet-utilization-scope, on-board-request-sequence, request-sequencing-service, request-sequence-store-capacity, request-sequence-lifecycle, request-sequence-self-reference.
- ▌ Fos Tables Application · ashfordeou bundleUse when determine the required factor of safety (FOS) for a structural component under ECSS-E-ST-32C clause 4.2.5: select the applicable yield, ultimate, or proof FOS from the tabulated values based on mission type (unmanned or human spaceflight), apply that factor to limit loads to obtain design loads, and compute the resulting margin of safety for each load case. Trigger: ecss, e-st-32-structures-scope, factor-of-safety, yield-factor, ultimate-factor, proof-factor, unmanned-spaceflight, human-spaceflight, margin-of-safety, structural-sizing.
- ▌ Fracture Material Data · ashfordeou bundleUse when derive fracture material properties for a space structure component: establish valid plane-strain fracture toughness KIC from test specimens, fit Paris-law da/dN crack growth curves from coupon data, determine the fatigue crack growth threshold ΔKth for each applicable load ratio, and apply conservative knockdown factors when data originate from a handbook or a limited-data campaign. Covers KIC specimen validity checks per the plane-strain size criterion, R-ratio adjustment of thresholds, three-region crack growth characterisation (threshold, Paris, near-KIC), minimum data requirements for Paris-curve fitting, and assembling a fully adjusted material data record. Trigger: ecss, e-st-32-structures-scope, fracture-toughness, crack-growth, paris-law, kic-validity, delta-kth, limited-data, material-data, da-dn.
- ▌ Q1009 Customer Meeting · ashfordeou bundleCoordinate the customer review board sitting on a submitted major nonconformance under ECSS-Q-ST-10-09 clauses 5.2.3.1 to 5.2.3.3. Use when a supplier's package has reached the customer and the board has to establish whether it can take a disposition at all. Separates the two ways a sitting fails: the customer functions that constitute the board, and the supplier representative without whom nothing can be confirmed. Assesses the impacts the supplier cannot see from inside its own scope, meaning system budget share, every interface parameter against its agreed range and slip against the activity float, then holds each submitted cause and consequence to a confirmed, disputed or open state. Trigger: ecss, q-st-10-09, customer-review-board-sitting, higher-level-impact-assessment, interface-parameter-range-breach, activity-float-consumption, supplier-confirmation-of-causes, disposition-deferral.
- ▌ Q1009 Internal Meeting · ashfordeou bundleRun the internal nonconformance review board sitting of ECSS-Q-ST-10-09 clause 5.2.2.1. Use when a supplier convenes its own board on internally raised nonconformances and the sitting, its agenda and its minutes all have to stand up to later scrutiny. Judges the roster against the mandatory board functions and against the voting quorum separately, because one shortfall is repaired by a delegate and the other by a reconvene; admits an agenda item only once its review package is complete, deferring the rest rather than deciding on evidence that is not there; and holds every item heard to a decision record naming disposition, rationale, owner and due day. Trigger: ecss, q-st-10-09, internal-nonconformance-review-board, nrb-voting-quorum, ncr-review-package, nrb-agenda-admissibility, nrb-minutes-completeness, internal-disposition-decision-record.
- ▌ Q20 Eidp Example Cover · ashfordeou bundlePrepare and assess the end item data package cover page of ECSS-Q-ST-20C Annex F, used as the house header format for the Annex B package: hold the field order the worked example fixes, refuse a blank mandatory field or a non-positive issue and document count, rebuild the package number from the contract and serial number, check the three-signature approval block for one person holding two roles or signatures taken out of order or after the cover issue, and reconcile the declared document count with the index. Use when a package cover is raised, reissued or checked on receipt. Trigger: ecss, q-st-20c-annex-f, eidp-cover-page, eidp-header-format, eidp-number-pattern, eidp-approval-block, eidp-document-count.
- ▌ Q40 Operational Safety · ashfordeou bundleEvaluate the operational safety provisions of an ECSS-Q-ST-40C clause 6.6 programme: rank every declared control against the design-elimination to procedure-and-training precedence, refuse a catastrophic ground hazard resting on procedure alone, require a verification behind each control, compare the reaction time a mission-control constraint needs with the time the operator has, and report the hazardous phases - transport, handling, integration, launch-site work - left with no operation. Use when ground-operations hazards are controlled, a flight-operations constraint is written, or an operations readiness review asks whether the set is covered. Trigger: ecss, q-st-40c, ecss-operational-safety-constraint, ecss-ground-operations-hazard-control, mission-control-reaction-margin, hazard-control-precedence-rank, launch-site-handling-hazard.
- ▌ Q6005 Pre Seal Burn In · ashfordeou bundleCompute what a biased thermal soak run on an open hybrid microcircuit package actually delivered, and decide whether the unit survived it, under ECSS-Q-ST-60-05 clause 10.3.3. Use when a burn-in log has to be graded rather than counted: convert the chamber hours to equivalent hours at the reference condition through the Arrhenius relation, test every segment against the permitted band, discard the hours before a break long enough to cool the unit, weigh each monitored parameter's drift against its allowance, and return one verdict. Trigger: ecss, q-st-60-05, pre-seal-burn-in, open-package-thermal-soak, burn-in-arrhenius-equivalent-hours, burn-in-interruption-restart, pre-and-post-soak-parameter-drift, pre-seal-burn-in-verdict.
- ▌ Q6013 Class 2 Relifing · ashfordeou bundleUse when an expired storage period has to become a disposition. Determine whether a stored lot of commercial EEE parts may have its usable life extended at the intermediate assurance class under ECSS-Q-ST-60-13C clause 5.3.10: grade the store the parts actually sat in, scale the package family baseline period by it, test the elapsed storage against that period, check the relifing cycle ceiling before any test is considered, assemble the test set the lot owes, apply the single re-tinning allowance this class grants a lone solderability failure, and compute the decaying extension each further cycle earns. Trigger: ecss, q-st-60-13c-clause-5-3-10, class-two-relifing, stored-part-storage-period-grading, relifing-cycle-ceiling, solderability-retinning-allowance, decaying-storage-extension, stored-lot-re-screening-referral.
- ▌ Q6013 Class 3 Relifing · ashfordeou bundleUse when an expired storage period has to become a disposition at the lightest class. Determine whether a stored lot of commercial EEE parts may have its usable life renewed at the lowest assurance class under ECSS-Q-ST-60-13C clause 6.3.10: grade the store the parts actually sat in, scale the package family baseline by it, test elapsed storage against the earned period, size the attribute sample this class inspects in place of every unit, assemble the fuller test set an uncontrolled store reopens, apply the repeatable re-tinning allowance up to its ceiling, and end the sequence on a cumulative life cap rather than a cycle count. Trigger: ecss, q-st-60-13c-clause-6-3-10, class-three-relifing, earned-storage-period-grading, relife-attribute-sample-plan, cumulative-storage-life-cap, repeatable-retinning-allowance, stored-lot-re-screening-referral.
- ▌ Q7026 Crimp Inspection · ashfordeou bundleEvaluate a finished crimp against its dimensional and visual acceptance limits. Use when completed crimps have to be dispositioned and a characteristic may simply not have been read: grade height and width against their own two-sided bands, size the flash extruded at the die parting line, confirm a bell mouth is formed and inside its length band where the contact calls for one, count the strands that can be seen, check the insulation grip closed on the jacket, and hold an unread characteristic at review rather than letting it pass. Trigger: ecss, q-st-70-26-crimping, crimp-height-and-width-band, crimp-die-flash-limit, crimp-bell-mouth-length-band, crimp-strand-visibility-count, crimp-unread-characteristic-review.
- ▌ Q7028 Conductor Repair · ashfordeou bundleDesign the repair of a broken, cut or lifted conductor on a printed-circuit-board assembly. Use when a track is open and the method, the wire and the bonding still have to be worked out: it chooses between a lap-soldered replacement segment and an insulated jumper from the gap length and the track width, refuses a break past the reach of either, computes the overlap each lap end needs, sizes the jumper from the circuit current and a current-density derating, spaces the bonds along the unsupported run, and compares the replacement cross-section against the copper it replaces. Trigger: ecss, q-st-70-28c-board-repair, pcb-conductor-repair, pcb-track-lap-solder-splice, pcb-jumper-wire-sizing, pcb-jumper-bond-spacing, pcb-conductor-cross-section.
- ▌ Q7029 Odour Assessment · ashfordeou bundleEvaluate the acceptability of the odour an offgassing sample presents to a trained sensory panel under ECSS-Q-ST-70-29: keep only the scores of judges currently qualified on the reference set, check the panel is still large enough once they are dropped, average the intensity ratings, test the spread for a panel that did not agree, and grade the result against the acceptance rating. Use when an offgassing test has produced panel scores and they must become a defensible odour verdict rather than an average. Trigger: ecss, q-st-70-29, offgassing-odour-assessment, offgassing-sensory-panel, offgassing-odour-rating-scale, offgassing-panel-qualification, offgassing-panel-dispersion, crew-compartment-offgassing.
- ▌ Q7045 Hardness Testing · ashfordeou bundleEvaluate a hardness indentation and, where the table allows it, carry the reading onto another scale. Use when the methods clause of ECSS-Q-ST-70-45 calls for Brinell, Vickers or Rockwell hardness: reduce the impression to its number, test the Brinell impression-to-ball ratio against the band the scale is defined over, reconcile force and indenter through the load index, report an impression pressed too near a neighbour or an edge, and interpolate a conversion inside the table while refusing one beyond it. Trigger: ecss, q-st-70-45, brinell-impression-ball-ratio, brinell-load-index-pairing, vickers-diagonal-asymmetry, rockwell-c-permanent-depth, hardness-scale-conversion-table.
- ▌ Q7002 Tml Measurement · ashfordeou bundleDetermine the total mass loss of specimens taken through an outgassing screening. Use when the three weighings of a run under ECSS-Q-ST-70-02C have to become a screening result: refer the loss to the initial mass so light and heavy coupons are comparable, refuse a specimen heavier after the exposure as a weighing error, subtract the water taken back on to leave the recovered mass loss, report a loss smaller than the balance division as unresolvable rather than small, and grade the replicate spread against its scatter allowance. Trigger: ecss, q-st-70-02c, outgassing-total-mass-loss, outgassing-recovered-mass-loss, outgassing-water-vapour-regained, outgassing-balance-resolution-floor, outgassing-replicate-scatter, outgassing-screening-limit.
- ▌ Q7040 Brazing Records · ashfordeou bundleAudit the record a brazement owes and decide whether it closes on its own evidence. Use when a brazed joint has been made and the traveller has to prove how, because the joint cannot be re-opened to find out: build the required field set from the process and whether flux was used, name the gaps in the order the set requires them, test the operator against both the certificate expiry and the continuity interval that disuse runs out, read the furnace run for its ramp, soak, cooling and atmosphere channels and for enough load thermocouples to see a cold corner, and close only when nothing is outstanding. Trigger: ecss, q-st-70-40-brazing, brazement-record-set, braze-operator-continuity-interval, braze-furnace-thermal-profile-trace, braze-procedure-qualification-record, braze-load-thermocouple-coverage.
- ▌ Q7045 Fatigue Testing · ashfordeou bundleDerive a stress-life curve from an S-N set and report what its points are entitled to claim. Use when the methods clause of ECSS-Q-ST-70-45 calls for fatigue data: censor the run-outs out of the log-log least-squares fit instead of letting them pull the curve towards a life nobody observed, reconcile every point against the declared run-out threshold, report a run-out that stopped before the fitted curve predicts failure as constraining nothing, and carry the cycling frequency and the specimen form with the curve. Trigger: ecss, q-st-70-45, sn-curve-basquin-loglog-fit, fatigue-runout-censoring, fatigue-runout-threshold-contradiction, fatigue-cycling-frequency-band, fatigue-notched-specimen-kt.
- ▌ Q7045 Tensile Testing · ashfordeou bundleCompute the tensile properties of a metallic specimen from its stress-strain record. Use when a tension test has been run under ECSS-Q-ST-70-45 and the properties have to be reported: fit the modulus by least squares over a declared elastic window and report the quality of that fit, locate the offset proof strength where the shifted line crosses the record, take the ultimate strength from the peak of the curve rather than its last point, derive elongation and reduction of area from the broken halves, and refuse a record whose strain does not increase. Trigger: ecss, q-st-70-45, metallic-tensile-offset-proof-strength, tensile-ultimate-strength-peak, tensile-elongation-after-fracture, tensile-modulus-least-squares-window, tensile-reduction-of-area.
- ▌ Q7080 Ndt Of Am Parts · ashfordeou bundleDetermine the non-destructive inspection suite an additively manufactured part needs, and whether the declared setup can actually find the flaw that matters. Use when a build is released against ECSS-Q-ST-70-80C inspection and the ECSS-Q-ST-70-15C method set: size the tomography voxel from the cone-beam geometry, take the ultrasonic resolution from the wavelength, grow the radiographic limit with the flaw tilt, strike out methods a rough as-built surface or an enclosed channel defeats, then compare the smallest detectable flaw against the fracture-control critical flaw on the coverage the criticality category demands. Trigger: ecss, q-st-70-80-additive-manufacturing-scope, am-part-ndt-suite, ct-voxel-detectability, ultrasonic-lack-of-fusion-detection, radiographic-flaw-tilt, am-enclosed-channel-inspectability, am-volumetric-coverage-category.
- ▌ Q7080 Part Acceptance · ashfordeou bundleDerive the acceptance case for a lot of additively manufactured parts, class by class. Use when a build lot is presented for acceptance under ECSS-Q-ST-70-80C: read the density, porosity and surface limits the part class sets, confirm the mandatory screens that class owes were actually performed, size the sampling plan from the protection demanded rather than a rule of thumb -- the smallest sample whose exact hypergeometric chance of accepting a lot at the limiting quality stays under the tolerated consumer risk -- then rule on the lot against the findings observed. Trigger: ecss, q-st-70-80-additive-manufacturing-scope, am-part-acceptance, part-class-acceptance-limits, am-lot-sampling-plan, hypergeometric-consumer-risk, limiting-quality-level, mandatory-am-screening.
- ▌ Q80 Compliance Matrix · ashfordeou bundleBuild a clause-by-clause compliance matrix against ECSS-Q-ST-80C Rev.2 as a draft for human sign-off: join the clause list to an evidence index of document, section, status and justification, set each clause to compliant, partially compliant, not compliant or not applicable, pre-fill clauses tailored out for the software category, raise gaps such as missing evidence, compliance claimed without a reference and not-applicable claims that contradict the tailoring, summarise coverage, and render Markdown or CSV ending at the stop line. Use when a supplier answers the Q-80 compliance matrix or a customer audits one. Trigger: q80-compliance-matrix, software-product-assurance-compliance, clause-by-clause-compliance, evidence-index, compliance-gap-list, statement-of-compliance.
- ▌ Weld Fracture Control · ashfordeou bundleUse when assess weld fracture-control compliance for space structural hardware under ECSS-E-ST-32C clause 8.3: categorize each weld by quality level (class A, B, or C according to its stress state, service loading, and criticality), screen weld imperfections against ISO 6520-1 acceptance limits for the assigned class, compute the safe-life fatigue margin by comparing the applied stress-cycle spectrum to the S-N allowable for the weld category, and verify that the NDT method and coverage are sufficient to guarantee detection of the assumed initial flaw size. Trigger: ecss, e-st-32-structures-scope, weld, fracture-control, safe-life, fatigue, ndt, iso-6520-1, weld-imperfection, weld-quality.
- ▌ Welded Joint Analysis · ashfordeou bundleUse when assess welded joints under ECSS-E-ST-32C clause 4.6.2.14: categorize each weld by quality class (WQ1, WQ2, WQ3) to derive the joint efficiency factor, compute the allowable normal and shear stresses from the parent material ultimate strength reduced by that efficiency and the applicable safety factor, calculate the effective weld throat area from the joint geometry (butt or fillet weld), determine the applied normal and shear stress components from the design load case, evaluate the margin of safety for the normal mode, shear mode, and combined von Mises criterion, and flag any negative margin as a finding requiring redesign or re-categorization at a higher quality class. Trigger: ecss, e-st-32-structures-scope, welded-joint, weld-quality-class, joint-efficiency, allowable-stress, margin-of-safety, fillet-weld, butt-weld.
- ▌ Copc Nonmetallic Liner · ashfordeou bundleUse when verify structural compliance of a Composite Overwrapped Pressure Container (COPC) fitted with a homogeneous non-metallic liner per ECSS-E-ST-32 clause 4.5.3: categorize the liner material as thermoplastic, thermoset, or elastomer; check proof and burst pressure factors against MEOP minimums; assess liner gas permeation rate against the project allowable limit; compute the load-sharing ratio between liner and composite overwrap; confirm liner-fluid chemical compatibility; and validate demonstrated cyclic fatigue life against mission cycle requirements with the applicable safety factor. Flag any factor shortfall, permeation exceedance, compatibility gap, or fatigue deficit before design acceptance. Trigger: ecss, e-st-32-structures-scope, copc, nonmetallic-liner, pressure-vessel, proof-pressure, burst-pressure, permeation, load-sharing, fatigue-life.
- ▌ E10 Env Design Factors · ashfordeou bundleUse when you define the natural and induced environments a product is exposed to across its mission phases under ECSS-E-ST-10C clause 5.3.2: determine the set of applicable environment types from the product's declared mission phases, identify the engineering domain each environment type belongs to, derive the design-and-test factor for that domain from the product's verification approach (qualification test, protoflight test, acceptance test, analysis, or similarity), compute the resulting test level from a captured limit level, and flag any applicable environment for which no limit level has been captured. Trigger: ecss, e-st-10c, environment definition, design and test factors, mission phase environment, qualification test, protoflight test, acceptance test, verification approach, limit level.
- ▌ E1002 Control Closeout · ashfordeou bundleUse when control and close out product verification under ECSS-E-ST-10-02 clause 5.4.1: confirm every verification control document row reached a closed status with evidence cited, confirm each closure taken against a waiver names a waiver the authority actually approved, confirm no nonconformance is still open, and confirm the verification database was delivered machine-readable in the agreed format covering every row the control document holds. Trigger: ecss, e-st-10-02c, verification-closeout, verification-control-document, waiver-approval, nonconformance, verification-database, electronic-delivery.
- ▌ E1003 Eq General Tests · ashfordeou bundleUse when running the general equipment test requirements of ECSS-E-ST-10-03C 5.5.1 within a qualification, acceptance, or protoflight test sequence: run the functional/performance test at each sequence position (baseline and final comprehensive, interim abbreviated unless an anomaly is suspected), evaluate current measurements against the baseline to flag degraded parameters, verify physical configuration (mass properties and visual inspection) at each test point, and confirm the launch configuration for any test representative of the launch environment, closing out the sequence only when every mandatory position is present and clear. Anchor: E-ST-10-03C clause 5.5.1. Trigger: equipment general tests, functional test, performance test, physical configuration check, launch configuration check, baseline functional test, protoflight test sequence, e-st-10-03, ecss.
- ▌ E1006 Char Performance · ashfordeou bundleUse when verify each requirement in a system specification for performance content under ECSS-E-ST-10C §8.2.1: confirm each performance requirement carries quantified parameters — numeric value, engineering unit, and comparison operator — flag requirements with missing or unquantified performance data, and confirm that performance requirement types are recognized before assessment. Trigger: ecss, e-st-10-system-scope, performance-requirements, quantification, parameter-values, requirements-review, verification, system-specification.
- ▌ E1009 Transform Decomp · ashfordeou bundleUse when decompose a spacecraft coordinate transformation chain per ECSS-E-ST-10-09C §5.4.8: validate each rotation matrix for orthogonality and proper orientation (determinant +1), determine the ordering of translation and rotation primitives in the chain, resolve a composed rotation into its Euler angle sequence, compose a series of elementary transforms into a single homogeneous matrix, and verify roundtrip consistency. Apply at any stage of mission reference frame analysis where transformation chains must be broken into auditable primitive steps. Trigger: ecss, e-st-10-09c, e-st-10-system-scope, reference-frames, transformation-chain, rotation-matrix, euler-angles, homogeneous-transform.
- ▌ E1011 Ops Nomenclature · ashfordeou bundleUse when validate operations nomenclature consistency across a mission operations document or interface control document per ECSS-E-ST-10-11C §4.3.3: confirm each crew role label belongs to the canonical set (Commander, Pilot, Mission Specialist, Payload Specialist, Flight Engineer, Ground Controller, Flight Director), confirm each mission phase term matches the standard vocabulary (launch, ascent, orbit insertion, on-orbit operations, rendezvous, docking, de-orbit, reentry, landing, recovery), confirm command type labels match the authorized taxonomy, and detect synonym conflicts where a single operational concept is referred to by multiple non-equivalent terms within the same document. Flag abbreviations, non-standard synonyms, and unrecognized terms for correction to canonical form before baselining. Trigger: ecss, e-st-10-system-scope, ops-nomenclature, crew-roles, mission-phases, command-types, operational-terminology, nomenclature-consistency.
- ▌ E1012 Shield Transport · ashfordeou bundleUse when run detailed 1-D, 2-D, or 3-D radiation transport calculations for spacecraft shielding analysis per ECSS-E-ST-10-12C clause 6.2.4: select a transport method (Monte Carlo or deterministic Sn/Pn code), specify geometry dimension and material composition, compute transmitted dose or fluence behind each shielding layer with buildup correction, and verify the result against the subsystem total-ionising-dose limit. For 1-D slab geometry, apply photon exponential attenuation and proton range-stopping to determine residual penetration or blocked contribution. Flag dimension mismatches, unsupported materials, invalid parameters, or dose-limit exceedances before accepting a shield design as adequate. Trigger: ecss, e-st-10c, e-st-10-12c, shield-transport, radiation-transport, monte-carlo, deterministic-sn, shielding, dose-limit, proton-range, fluence.
- ▌ E10 Req Consolidation · ashfordeou bundleUse when a requirement subject is common to several next-lower-level products in an ECSS-E-ST-10C specification tree and must be consolidated into a support specification instead of repeated per product, or when the same requirement flows down to two or more products with conflicting values and the conflict must be resolved before the requirement baseline is set. ECSS-E-ST-10C clause 5.2.3.2 governs requirement consolidation and flow-down conflict resolution. Trigger: ecss, e-st-10c, requirement consolidation, support specification, flow-down conflict, common requirements, specification tree, 5.2.3.2.
- ▌ E10 Req Risk Analysis · ashfordeou bundleUse when assessing the technical/requirement risk of a candidate or derived requirement during ECSS-E-ST-10C flow-down: determine likelihood x severity into a risk class, feed the project risk register, and gate baselining on a defined mitigation for medium-and-above risk consistent with M-ST-80. Trigger: ecss, e-st-10c, requirement risk, risk register, risk analysis, technical risk, mitigation, m-st-80, risk index, likelihood severity.
- ▌ E10 Req Verif Methods · ashfordeou bundleUse when every requirement in an ECSS-E-ST-10C requirements set needs a verification method (test, analysis, review-of-design, inspection) and a verification level (equipment, subsystem, element, segment, system) assigned before verification planning, consistent with E-ST-10-02 verification methods/levels and E-ST-10-03 testing. Trigger: verification method, review of design, ROD, verification level, test analysis inspection, verification matrix, E-ST-10-02, E-ST-10-03, requirement verification, ecss, e-st-10c.
- ▌ E1002 Analysis Report · ashfordeou bundleUse when determine whether an analysis report actually verifies its requirement under ECSS-E-ST-10-02 clause 5.3.2.2: confirm the analysis was run against the design baseline under verification rather than a superseded model, confirm every case the requirement's envelope demands was analysed and flag cases that drifted outside it, confirm each case carries a verdict and that a case not run states why, and roll the case results up to a requirement verdict. Trigger: ecss, e-st-10-02c, analysis-report, verification-by-analysis, case-coverage, model-baseline, envelope, verdict-rollup.
- ▌ E1002 Method Analysis · ashfordeou bundleUse when determine which ECSS-E-ST-10-02C clause 5.2.2.3 analysis technique (worst-case, statistical, qualitative, classical calculation, or similarity) applies to a requirement being verified by analysis, validate the heritage conditions that must all hold before a case can close by similarity to a previously verified reference item -- verified reference item, design/manufacturing equivalence, and an enveloped operating environment -- check an analysis plan for the fields a closure review requires, and roll a set of analysis cases up into open/closed status. Trigger: ecss, e-st-10-02c, verification by analysis, verification by similarity, heritage, analysis technique selection, similarity validation conditions, environment envelope, analysis plan completeness.
- ▌ E1003 Test Conditions · ashfordeou bundleUse when define test conditions for a space equipment or system verification campaign under ECSS-E-ST-10C §4.4.1: establish the required ambient environment parameter ranges (temperature, pressure, humidity, EMI environment), the cleanliness class for each test area, the ESD protection measures required for each test item, the unit-under-test configuration state and interface definitions, and the monitoring channel set with recording rates and acceptance limits. Each condition input is categorized as compliant or non-compliant; undefined mandatory conditions are flagged; and monitoring coverage is confirmed before test execution is permitted. Trigger: ecss, e-st-10-system-scope, test-conditions, ambient-environment, esd-protection, cleanliness, test-configuration, monitoring.
- ▌ E1006 Char Uniqueness · ashfordeou bundleUse when verify that every requirement in a spacecraft system specification is unique in wording and content — detecting exact duplicates (identical normalised text) and near-duplicates (high substantive-vocabulary overlap) across the requirement set, and reporting each offending pair with a finding that identifies which requirements must be reworded or consolidated. Applies the uniqueness characteristic of ECSS-E-ST-10C §8.2.5: a requirement whose meaning or wording already exists in another requirement in the same set adds no engineering value and creates traceability ambiguity. Trigger: ecss, e-st-10-system-scope, requirement-uniqueness, duplicate-detection, near-duplicate, requirement-quality, wording-overlap, consolidation.
- ▌ E1011 Crew Provisions · ashfordeou bundleUse when specifying crew station provisions under ECSS-E-ST-10C §4.7.5: identify each station by type (piloting, mission, payload, maintenance), verify seat dimensions against the crew anthropometric envelope, confirm restraint load capacities for shoulder harness, lap belt, and footrest, assess console reach and height against the seated crew envelope, and validate egress clearance against the minimum path width. Flag each station that fails a geometry, load, or clearance requirement before proceeding to detailed design. Trigger: ecss, e-st-10-system-scope, crew-stations, seat-restraints, console-layout, egress, anthropometry, crew-accommodation.
- ▌ E1011 Hfe Req Process · ashfordeou bundleUse when manage the HFE requirements process for a space system under ECSS-E-ST-10-11C §4.6.1–4.6.2: capture each human factors engineering requirement with a non-empty source identifier, categorize it by type (functional, performance, environmental, safety, anthropometric), allocate it to one or more system elements (hardware, software, procedure, training), and verify bidirectional traceability from source to requirement and from requirement to implementing element. Flag any requirement missing its upstream source trace, any requirement in an allocation-required lifecycle state with no assigned implementing element, and any element of an unrecognized type. Track lifecycle status through proposed, approved, allocated, implemented, verified, and closed. Trigger: ecss, e-st-10-11c, hfe, human-factors-engineering, hfe-requirements, requirements-process, traceability, allocation.
- ▌ E1012 Bg Experimental · ashfordeou bundleUse when assess background radiation using experimental irradiation data under ECSS-E-ST-10C §10.4.8: validate each experimental flux or dose-rate record for completeness and uncertainty bounds, compare measurements against the applicable reference environment model, determine whether experimental data supersede or supplement the standard model estimate, compute the combined background assessment value and its uncertainty envelope, and confirm that data provenance is recorded in the assessment record. Trigger: ecss, e-st-10-system-scope, experimental-irradiation, background-assessment, radiation-flux, dose-rate, environment-model, uncertainty-bounds.
- ▌ E1012 Shield Geometry · ashfordeou bundleUse when build the radiation shielding geometry model for a component or equipment item under ECSS-E-ST-10-12C §6.3: assemble the three-tier shielding hierarchy (parts packaging, equipment housing, spacecraft structure), compute the areal density contribution of each shielding layer, sum contributions across all tiers to derive the effective shielding seen by the sensitive part, and check interfaces (connectors, cutouts, feed-throughs) where the local effective shielding falls below a required minimum threshold. Trigger: ecss, e-st-10-12c, shield-geometry, areal-density, radiation-shielding, parts-packaging, equipment-shielding, spacecraft-structure.
- ▌ E50 Time Distribution · ashfordeou bundleCompute the accuracy a distributed time reference actually delivers to each of its users under ECSS-E-ST-50C clause 5.7.2.8, which asks that time reach the users that need it inside a stated accuracy. Build the budget at the consumer, not at the master: uncompensated transport delay, half the path asymmetry, half the timestamp step and the random jitter of every hop, systematic terms added and random terms root-sum-squared, plus the holdover a consumer accumulates on its own oscillator between distribution messages. Use when sizing a distribution period, grading a chain against a required accuracy, or finding which consumer sets the limit. Trigger: ecss, e-st-50c-clause-5-7-2-8, time-distribution-accuracy-budget, time-reference-distribution-chain, distribution-holdover-drift, timestamp-quantization-error, path-asymmetry-time-error, distribution-period-sizing.
- ▌ E7041 Obcp Definition · ashfordeou bundleValidate an on-board control procedure definition before it is ever loaded, under ECSS-E-ST-70-41C clause 6.18.4.1. Use when the task is deciding whether a procedure the ground wrote can actually run aboard: checking identity and version against the definition store, matching it to an engine that carries the right language and a large enough procedure limit, separating mandatory arguments from defaulted ones, refusing an activation value of the wrong type, digesting a definition so ground and spacecraft cannot disagree about which build is aboard, and sizing a whole definition set against the store. Trigger: ecss, e-st-70-41c, pus-packet-utilisation, obcp-definition, on-board-control-procedure-definition, obcp-engine-procedure-limit, obcp-argument-binding, obcp-definition-store-sizing.