all publishers

ashfordeOU

@ashfordeou source repo

1,298 published skills · page 6 of 13

  1. ▌
    E1024 Planning · ashfordeou bundle
    Use when define the Interface Management Plan (IMP) for a space project under ECSS-E-ST-10C §5.1: establish IMP scope and purpose, assign team responsibilities for interface identification, documentation, review, approval, baseline, and change control, specify the IM process steps from identification through verification, schedule IM milestones against project lifecycle phases (phases 0 through F), and integrate the IMP with the System Engineering Plan (SEP) by linking the SEP IM section and confirming the IMP is listed as a required project deliverable. Apply also to audit an existing IMP for §5.1 completeness. Trigger: ecss, e-st-10-system-scope, interface-management, imp, sep, lifecycle-phases, responsibilities, process-definition, milestones, im-plan.
    5 repo stars
  2. ▌
    E1024 Ref Data · ashfordeou bundle
    Use when define the interface reference data list for a space system development project under ECSS-E-ST-10-24C Annex E: identify each interface type (electrical, mechanical, thermal, data, RF, optical, fluid, pyrotechnic), specify typical parameters with measurement units and value ranges, assign a format token per parameter entry, verify that every record contains all required fields, and group entries by interface type to produce a structured reference table. Apply during ICD development, interface requirement capture, or compliance review of interface documentation. Trigger: ecss, e-st-10-system-scope, e-st-10-24c, interface-management, icd, interface-reference-data, parameter-list, units, formats, interface-types.
    5 repo stars
  3. ▌
    E1024 Tmtc Icd · ashfordeou bundle
    Use when produce TM/TC interface control documents (ICDs) for a spacecraft following ECSS-E-ST-10-24C §5.9: register CCSDS application process identifiers (APIDs), define PUS-based telemetry and telecommand packet structures with service and subservice assignments, validate packet field ranges against CCSDS and PUS-C conventions, check APID registration completeness, and verify the ICD includes at least one TM downlink and one TC uplink definition. Trigger: ecss, e-st-10-system-scope, tmtc-icd, telemetry, telecommand, ccsds, pus, apid, packet-definition, icd.
    5 repo stars
  4. ▌
    E4008 Activity · ashfordeou bundle
    Audit the activities inside an SMP schedule task against ECSS-E-ST-40-08C clause 5.4.5 and the fourteen normative items that clause places on them. Use when a schedule has to be resolved against the assembled model rather than read on its own: giving each activity one declared kind carrying only its own payload and a name unique in its task, resolving the instance path, checking an entry point exists and takes no arguments, checking a field exists, is writable and receives a value of the declared type inside its range, checking an emitted event exists, and reporting activities that advance simulated time or write one field twice. Trigger: ecss, e-st-40-08-simulation-modelling-scope, e4008-activity, schedule-activity-kinds, activity-entry-point-invocation, activity-field-assignment, activity-event-emission, activity-write-order-hazard.
    5 repo stars
  5. ▌
    Q2010 Dossier · ashfordeou bundle
    Maintain the off-the-shelf item evaluation dossier that ECSS-Q-ST-20-10C clause 5.1.3 and its Annex B data-requirement description ask for, as an append-only record of every evaluation performed on every candidate. Use when evidence is arriving from several evaluations and somebody has to say which Annex B sections a candidate still owes and whether any finding is unresolved. Adds entries without overwriting history, supersedes only by a higher revision, refuses a conclusion with no source reference or date behind it, reports coverage per candidate, and grades evidence older than its validity window as stale rather than counting it. Trigger: ecss, q-st-20-10, ots-evaluation-dossier, annex-b-drd-coverage, append-only-evaluation-record, entry-supersession-revision, stale-evaluation-evidence, unresolved-evaluation-finding.
    5 repo stars
  6. ▌
    Q2010 Process · ashfordeou bundle
    Scope the off-the-shelf item utilisation process of ECSS-Q-ST-20-10C clause 4 against the project product tree: decide the stage each candidate has actually reached across market investigation, characterization and selection, and procurement and qualification, refusing to count a later stage while an earlier one is still open, add the delta qualification plan an item not already qualified for this application owes, and reconcile candidates with the tree so a candidate on a make node, a candidate on a node the tree lacks, and an off-the-shelf node with no candidate all surface. Use when an item reuse strategy is being scoped or audited. Trigger: ecss, q-st-20-10c, ots-item-selection-process, ots-market-investigation, ots-characterization-and-selection, ots-delta-qualification-plan, ots-product-tree-integration.
    5 repo stars
  7. ▌
    Q2030 Testing · ashfordeou bundle
    Audit the test programme of a manufactured electrical harness under ECSS-Q-ST-20-30C section 6.19 and its IPC section 19 acceptance basis. Use when the task is deciding which tests a harness owes and whether the recorded results support acceptance: nondestructive examination, continuity graded against a loop resistance computed from conductor length, cross-section and mated contact count, insulation resistance at its electrification time, a dielectric withstanding voltage derived from the working voltage, pull strength scaled to conductor size, and the reduced-level retest a reworked harness owes. Trigger: ecss, q-st-20-30c, harness-continuity-test, harness-insulation-resistance, harness-dielectric-withstanding-test, harness-pull-test, harness-test-after-rework, ipc-whma-a-620-harness-testing.
    5 repo stars
  8. ▌
    Drd Allowables · ashfordeou bundle
    Use when prepare the material and mechanical-part allowables document required by ECSS-E-ST-32C Annex H (MMPA DRD): identify every structural material and fastener in scope, assign each an allowable basis (A-, B-, S-, or typical), retrieve governing allowable values from MMPDS or CMH-17 for composites, apply environmental and statistical knockdown factors, verify that all required mechanical properties are present for the applicable temperature range, and confirm full source traceability before the allowables package is released for structural analysis use. Trigger: ecss, e-st-32-structures-scope, drd-allowables, mmpsd, cmh17, material-allowables, mechanical-part-allowables, allowable-basis, knockdown-factors, structural-properties.
    5 repo stars
  9. ▌
    Drd Math Model · ashfordeou bundle
    Use when draft the Mathematical Model Description Document (MMDD) for a structural mathematical model under ECSS-E-ST-32C Annex I and clause 32-03: categorize the model as finite-element, analytical, or hybrid, verify all required MMDD documentation fields are present and non-empty, check eigenfrequency correlation against the ±5 % tolerance and modal assurance criterion (MAC) values against the minimum threshold, assess delivery-package completeness against the MMDD checklist, and flag any missing or non-conforming items before the model is released for use. Trigger: ecss, e-st-32-structures-scope, mathematical-model, mmdd, finite-element, fem, model-correlation, mac, eigenfrequency, model-delivery.
    5 repo stars
  10. ▌
    E10 Budget Drd · ashfordeou bundle
    Use when produce or review a project technical budget report against the ECSS-E-ST-10C Annex I Document Requirements Definition: place every budget item in a recognized category, inflate its basic value into a current best estimate using the margin its design maturity earns, check each estimate against its allocated maximum, roll the estimates up per category and system-wide, apply the system margin, and decide whether the report satisfies the DRD. Trigger: ecss, e-st-10-system-scope, technical-budget, annex-i-drd, mass-budget, power-budget, margin-philosophy, design-maturity, budget-allocation.
    5 repo stars
  11. ▌
    E10 Changes Nc · ashfordeou bundle
    Use when controlling an engineering change or nonconformance that may affect requirements or design under ECSS-E-ST-10C: assess whether it impacts the approved baseline, route it to the right approval authority, and gate implementation on an approved disposition with the baseline updated, consistent with M-ST-40 (configuration management) and Q-ST-10-09 (nonconformance control). Trigger: ecss, e-st-10c, engineering change, change request, nonconformance, ncr, m-st-40, q-st-10-09, baseline impact, ccb, nrb, disposition.
    5 repo stars
  12. ▌
    E10 Technology · ashfordeou bundle
    Use when identifying critical technologies for a space project under ECSS-E-ST-10C clause 5.6.7, assessing their Technology Readiness Level (TRL) per E-AS-11 (ISO 16290), building the technology matrix, and defining the development plan that closes the gap to the TRL required for the project. Trigger: ecss, e-st-10c, technology plan, technology matrix, trl, technology readiness level, iso 16290, e-as-11, technology risk, critical technology, annex e, annex f.
    5 repo stars
  13. ▌
    E1002 Approach · ashfordeou bundle
    Use when defining the verification approach under ECSS-E-ST-10-02C clause 5.2.1: decide which requirements enter verification, check whether a chosen method is applicable at a given life-cycle stage, assess the risks for requirements that cannot be verified by test and the mitigations for them, validate a per-requirement strategy, roll closure status up by verification level, and confirm the plan is complete. Trigger: ecss, e-st-10-02c, verification approach, verification strategy, method applicability, stage, risk assessment, mitigation, plan completeness, closure roll-up.
    5 repo stars
  14. ▌
    E1002 In Orbit · ashfordeou bundle
    Use when a flight item has requirements that cannot be fully closed on the ground and must be verified once on orbit under ECSS-E-ST-10-02C clause 5.2.4.5: identify which requirements need the in-orbit stage, close them out against commissioning evidence, and reopen a previously closed requirement for re-verification when an in-orbit anomaly affects it. Trigger: in-orbit verification, commissioning, on-orbit performance, anomaly re-verification, post-launch checkout, e-st-10-02, verification stage, ecss, e-st-10c.
    5 repo stars
  15. ▌
    E1002 Sw Tools · ashfordeou bundle
    Use when a software tool (simulation code, FEM solver, thermal/analysis package) is being used to generate verification-by-analysis evidence under ECSS-E-ST-10-02C and needs a qualification check before its output is accepted: was the tool validated, is it under configuration control, are the analysis conditions inside its validated domain, and does a safety-critical use have an independent cross-check, consistent with the tool/model validation principle of E-ST-10 §5.3.4. Trigger: software tool qualification, verification by analysis, analysis tool validation, tool configuration control, validated domain, independent check, e1002, e-st-10-02, ecss.
    5 repo stars
  16. ▌
    E1003 Tpro Drd · ashfordeou bundle
    Use when validate a Test Procedure (TPRO) document against ECSS-E-ST-10C Annex C DRD requirements: confirm the header carries all required identification fields (document ID, title, revision, objective, test level, applicable standard, safety requirements), verify each procedure step is numbered sequentially with an explicit action, expected result, and data-recording entries specifying parameter, unit, and acceptance range, check that pass/fail criteria cover all measured parameters, and surface any structural gap before the procedure enters formal review. Trigger: ecss, e-st-10-system-scope, e-st-10c, tpro, test-procedure, drd, data-recording, pass-fail-criteria, procedure-validation, annex-c.
    5 repo stars
  17. ▌
    E1003 Tspe Drd · ashfordeou bundle
    Use when validate or generate a Test Specification (TSPE) document against the ECSS-E-ST-10C Annex B Data Requirement Document: verify the document carries a test identification block (ID, name, and test-type category), a substantive description of the test objective, a conditions block covering environment, configuration, and stimuli, an ordered procedure list with step numbers and actions, and at least one measurable success criterion with parameter, limit, and measurement unit. Flag each absent or incomplete section as a compliance finding before the review board accepts the document. Trigger: ecss, e-st-10c, tspe, test-specification, drd, test-conditions, success-criteria, annex-b.
    5 repo stars
  18. ▌
    E1004 B3 Meov2 · ashfordeou bundle
    Use when implementing the ONERA MEOv2 trapped-electron flux model for GNSS/navigation-orbit (MEO) radiation analyses under ECSS-E-ST-10-04C Annex B.3: represent the model's flux-versus-energy spectral form as a function of McIlwain L-shell, interpolate the model's L-shell reference grid to an arbitrary L-shell (including along a full mission orbit's L-shell trace), and compute per-energy, orbit-averaged, and worst-case-L-shell flux outputs for the orbit. Trigger: MEOv2, ONERA, GNSS orbit radiation, MEO electron flux, McIlwain L-shell, spectral flux model, orbit interpolation, e-st-10-04c annex b.3, ecss, space environment, trapped radiation.
    5 repo stars
  19. ▌
    E1004 Neutrons · ashfordeou bundle
    Use when you must define the atmospheric albedo neutron environment for a LEO mission and include it in the radiation environment specification (RES) per ECSS-E-ST-10-04C: decide whether the environment applies to the orbit regime, classify the neutron energy spectrum into bands, assess the geomagnetic-latitude exposure that drives the flux, and verify the RES entry carries every required field before the RES is closed out. Trigger: ecss atmospheric albedo neutrons, albedo neutron environment, leo neutron flux, radiation environment specification neutrons, e-st-10-04c 9.2.5.
    5 repo stars
  20. ▌
    E1009 Notation · ashfordeou bundle
    Use when verify that all frames, coordinate systems, and transformation data in exchanged engineering products comply with the ECSS-E-ST-10C §5.3.2 standard notation: confirm each frame identifier is an uppercase alphanumeric label, confirm each rotation matrix is orthogonal with determinant +1, confirm each quaternion carries unit norm, confirm each Euler-angle representation declares an explicit 3-digit axis-sequence code with no two adjacent axes identical, confirm every annotated vector carries a frame label, confirm transformation chains are gap-free between consecutive steps, and flag any exchange record that omits a mandatory notation field. Trigger: ecss, e-st-10-system-scope, notation, coordinate-frame, rotation-matrix, quaternion, euler-angles, frame-annotation, transformation, interface-data.
    5 repo stars
  21. ▌
    E1011 Displays · ashfordeou bundle
    Use when design displays for a crewed spacecraft interface under ECSS-E-ST-10-11C §4.9.4: verify each display's format properties (layout type, font size, contrast ratio) against HFE minimum thresholds, check the information-density budget (parameter count and visible alarm count per display) against project limits, and assess each alarm entry for valid priority, consistent state, visual and auditory distinctiveness for high-priority active alarms, and correct suppression-indicator visibility. Flag every format, density, or alarm finding; a display is not compliant until all findings are resolved. Trigger: ecss, e-st-10-11c, e-st-10-system-scope, displays, display-format, information-density, alarm-presentation, hfe, human-factors-engineering.
    5 repo stars
  22. ▌
    E1012 Bg Calc · ashfordeou bundle
    Use when run radiation background calculations for a spacecraft instrument or detector under ECSS-E-ST-10C §10.4.9: compute the energy-deposition spectrum by applying linear energy transfer to the ambient particle flux in each energy bin, determine the absorbed dose for each particle species, derive nuclear interaction rates from the particle flux, nuclear cross-section, and target areal density, apply Beer-Lambert attenuation to propagate the radiation environment through shielding material, and compare the integrated dose against the mission allowable budget, flagging any exceedance. Trigger: ecss, e-st-10-system-scope, radiation-background, energy-deposition-spectrum, nuclear-interaction-rate, linear-energy-transfer, shielding-attenuation, dose-budget.
    5 repo stars
  23. ▌
    E1012 Bg Xray · ashfordeou bundle
    Use when compute the fluorescent X-ray interaction background for a space detector or instrument per ECSS-E-ST-10-12C §10.4.5: enumerate structural and shielding materials in the detector field of view, check whether each material's K-shell absorption edge is below the primary radiation energy, compute the K-shell photoelectric cross-section and fluorescent photon yield per emission line (K-alpha and K-beta) from incident fluence, element areal density, fluorescence yield, and detector solid angle, then sum all material contributions to form the predicted background spectrum and flag any line whose count exceeds the instrument background tolerance. Trigger: ecss, e-st-10-system-scope, x-ray-fluorescence, xrf, fluorescence-yield, characteristic-x-rays, detector-background, photoelectric-cross-section, radiation-background.
    5 repo stars
  24. ▌
    E1012 Bio Unc · ashfordeou bundle
    Use when evaluate uncertainties in a space-radiation biological-effects assessment under ECSS-E-ST-10-12C §11.6: identify each required uncertainty source (radiation quality factor, dose-and-dose-rate effectiveness factor, cancer-risk coefficient from epidemiology, inter-population transfer model, and dosimetry and transport), combine the independent log-space components in quadrature to obtain a geometric standard deviation, derive the 95% confidence interval around the point-estimate risk value, assign a qualitative uncertainty level, and flag any required source type absent from the budget. Trigger: ecss, e-st-10-system-scope, biological-effects-uncertainty, quality-factor, ddref, cancer-risk, confidence-interval, dose-equivalent-uncertainty.
    5 repo stars
  25. ▌
    E1012 Rdm See · ashfordeou bundle
    Use when determine the radiation design margin for single-event effects (SEE) on spacecraft EEE parts under ECSS-E-ST-10-12C §5.1.3: categorize each SEE-sensitive device as subject to destructive effects (latchup, burnout, gate rupture) or non-destructive effects (upset, functional interrupt, transient), compute the LET-threshold margin for destructive parts and the upset rate margin for non-destructive parts, verify each margin meets the required RDM factor, and flag any part with insufficient margin before design acceptance. Trigger: ecss, e-st-10-system-scope, e-st-10-12c, radiation-design-margin, single-event-effects, see, let-threshold, upset-rate, see-hardness-assurance.
    5 repo stars
  26. ▌
    E1012 Seu Ion · ashfordeou bundle
    Use when calculating heavy-ion-induced single-event upset (SEU), multiple-cell upset (MCU), and single-word multiple-bit upset (SMU) rates for a space-qualified device under ECSS-E-ST-10-12C §9.4.1.2: fit the device cross-section versus LET curve with a Weibull model (LETth, W, s, σsat), integrate over the mission LET spectrum using the rectangular parallelepiped (RPP) method, optionally apply the integral RPP (IRPP) chord-length correction for sensitive-volume geometry, derive MCU and SMU rates from upset multiplicity and same-word fractions, and verify the predicted rate meets the system requirement with a 10× design margin. Trigger: ecss, e-st-10-12c, e-st-10-system-scope, seu, mcu, smu, heavy-ion, let-spectrum, rpp, irpp, weibull.
    5 repo stars
  27. ▌
    E1012 Tid Unc · ashfordeou bundle
    Use when evaluate TID assessment uncertainties for space electronic components under ECSS-E-ST-10-12C §7.8: identify every uncertainty source (radiation environment model, shielding geometry, dose-rate and temperature effects during test, part-to-part variability), assign a multiplicative uncertainty factor to each source, compute the combined factor as the product of all individual factors, derive the design TID as the product of the mean environment TID and the combined uncertainty factor, and verify that the component's minimum lot tolerance divided by the design TID meets the required Radiation Design Margin. Trigger: ecss, e-st-10-12c, tid, total-ionizing-dose, uncertainty, radiation-design-margin, dose-rate, shielding, part-variability, rdm.
    5 repo stars
  28. ▌
    E1024 Control · ashfordeou bundle
    Use when assess interface baseline control and change approval under ECSS-E-ST-10C §5.5: establish an approved baseline from candidate interface documents, categorize each change request as minor (no functional impact) or major (affecting interface definition, timing, or physical properties), verify Interface Change Board quorum before voting, evaluate vote outcome by simple majority, confirm all required stakeholders have formally agreed to the interface document, and maintain an auditable change log for every state transition. Trigger: ecss, e-st-10-system-scope, interface-control, interface-baseline, change-control, interface-change-board, icb, agreement-process.
    5 repo stars
  29. ▌
    E1024 Icd Drd · ashfordeou bundle
    Use when generate and validate an Interface Control Document (ICD) against ECSS-E-ST-10-24C Annex B DRD criteria: identify both sides of each interface pair, assign each interface to a recognized type (mechanical, electrical, thermal, data, RF, optical, fluid), confirm all mandatory DRD sections are present (scope, reference documents, interface description, verification requirements), trace every interface requirement to a parent IRD or system-level requirement, and verify that each interface requirement carries an assigned verification method. Flag incomplete identification, unrecognized interface types, missing sections, untraced requirements, and requirements lacking verification coverage. Trigger: ecss, e-st-10-system-scope, interface-control, icd, drd, interface-management, requirements-traceability, verification-coverage.
    5 repo stars
  30. ▌
    E1024 Idd Drd · ashfordeou bundle
    Use when generate or validate an Interface Definition Document (IDD) or single-end ICD under ECSS-E-ST-10-24C Annex C: confirm each interface record carries a recognized type and status, verify that every record names its mating item and supplies non-empty interface characteristics, flag any agreed interface that lacks a bilateral ICD reference, surface superseded entries without a successor reference, tally interfaces by status, and decide whether the IDD is complete. Trigger: ecss, e-st-10-system-scope, idd, interface-definition-document, single-end-icd, interface-type, icd-reference, mating-item, interface-status.
    5 repo stars
  31. ▌
    E1024 Ird Drd · ashfordeou bundle
    Use when generate or validate an Interface Requirements Document (IRD) for a space system element pair under ECSS-E-ST-10-24C Annex A: identify both interface parties, categorize each interface requirement by type (mechanical, electrical, thermal, data, rf, environmental, human), assign a unique verifiable identifier to every requirement, confirm each requirement carries a verification method (T/A/I/R/D), check that no duplicate requirement IDs exist, and flag any missing mandatory document-level fields such as project name, issue date, or applicable documents list. Trigger: ecss, e-st-10-system-scope, ird, interface-requirements-document, drd, interface-parties, verification-method, requirement-traceability.
    5 repo stars
  32. ▌
    E7041 Boolean · ashfordeou bundle
    Validate and encode a boolean parameter field under ECSS-E-ST-70-41C clause 7.3.2, where the boolean type admits exactly one format code and occupies exactly one bit. Use when the task is laying out on-board flags or reading them back off the wire: accepting only the one defined type pair, refusing the integers 0 and 1 and the string forms that a looser encoder would quietly accept as truth values, packing a run of flags most significant bit first so the first field of the definition is the first bit, and counting the pad bits a short run leaves carrying nothing. Trigger: ecss, e-st-70-41c, pus-packet-field-type, boolean-parameter-field, one-bit-boolean-field, boolean-field-truth-value, boolean-flag-bit-packing, boolean-field-padding-bits.
    5 repo stars
  33. ▌
    E7041 Deduced · ashfordeou bundle
    Determine the type a deduced parameter takes from an earlier field of the same packet, under ECSS-E-ST-70-41C clause 7.3.12. Use when a packet definition leaves a parameter untyped until run time: checking that the deducing field precedes the field it settles, that every value the selector admits maps to a type the reader knows, and that the mapping covers the selector value space, because one unmapped value does not spoil a single parameter, it moves every field after it and leaves the rest of the packet unreadable. Trigger: ecss, e-st-70-41c, pus-deduced-data-type, run-time-parameter-type-deduction, selector-field-precedence, deduced-type-mapping-coverage, unmapped-selector-value, variable-layout-packet-sizing.
    5 repo stars
  34. ▌
    E7041 Tracing · ashfordeou bundle
    Evaluate the trace an OBCP engine keeps of a procedure's execution, under ECSS-E-ST-70-41C clause 6.18.4.8. Use when a retrieved trace cannot account for what a procedure did, or when a long run comes back with only its last few records: applying the configured granularity as the filter that fixes which execution events are recordable at all, fitting the records into a bounded buffer under a drop-oldest or stop-at-the-brim policy, separating a trace switched on mid-run from one that covers the whole run, computing coverage against the events offered, and deciding whether what survived can be read as a contiguous sequence. Trigger: ecss, e-st-70-41c, obcp-execution-tracing, obcp-trace-granularity-filter, obcp-trace-buffer-overflow-policy, obcp-mid-run-trace-enable, obcp-trace-reconstructability, obcp-trace-coverage.
    5 repo stars
  35. ▌
    Q1009 Ncr Drd · ashfordeou bundle
    Generate or validate a nonconformance report against the normative data item of ECSS-Q-ST-10-09 Annex A. Use when a nonconformance has been raised on a deliverable item and the report has to be graded before it goes to a review board or is closed out: grade it at the stage it has actually reached rather than against the closure blocks, add the content the proposed disposition path carries, whether acceptance justification, repair requalification, reinspection, scrap authorisation or supplier return, derive from the report whether the internal board settles it or the customer board has to see it, and refuse a customer route closed with no customer approval recorded. Trigger: ecss, q-st-10-09-annex-a, nonconformance-report-drd-content-blocks, nonconformance-disposition-path-content, nonconformance-review-board-routing, customer-nonconformance-review-board-approval.
    5 repo stars
  36. ▌
    Q2007 Qs Reps · ashfordeou bundle
    Assess a test centre's quality and safety representative appointments under ECSS-Q-ST-20-07C clause 5.3.4. Use when the register has to show each representative really holds stop-test authority and direct access to management rather than a title: grade the appointment form, the authorities the role must carry, and independence from the test-execution reporting line, count the escalation hops to top management, refuse a verbal appointment as cover, and compute the authority-coverage ratio and the per-activity gaps where no sound quality or safety representative stands. Trigger: ecss, q-st-20-07-test-centre, q2007-qs-reps, quality-and-safety-representative-appointment, test-centre-stop-test-authority, direct-management-access-escalation, representative-independence-from-test-execution, test-activity-representative-coverage.
    5 repo stars
  37. ▌
    Q2007 Tf Risk · ashfordeou bundle
    Assess the hazards of a test facility and the residual risk left after mitigation, as ECSS-Q-ST-20-07 clause 5.6.5 asks. Use when a safety case for a facility has to be argued before a campaign rather than asserted: refuse an assessment covering fewer hazard categories than the facility owes, take a severity and a likelihood index per hazard into a risk band, credit only the mitigations actually implemented, recompute the residual band, and require a named acceptance authority for every residual risk above the acceptance line. Trigger: ecss, q-st-20-07-test-facility-clause-5-6-5, test-facility-hazard-category-coverage, test-facility-residual-risk-band, test-facility-risk-acceptance-authority, test-facility-mitigation-credit.
    5 repo stars
  38. ▌
    E1003 Anomaly · ashfordeou bundle
    Use when resolving anomalies or failures detected during spacecraft testing under ECSS-E-ST-10C §4.3.4: categorize each failure by domain (hardware, software, environmental, electrical, mechanical), determine containment actions scaled to the severity level (critical/major/minor), verify the anomaly record captures all required documentation fields, assign a disposition code (accept as-is, repair and retest, waiver required, reject, pending analysis), and identify which test cases must be repeated as a consequence of the anomaly or its corrective action. Trigger: ecss, e-st-10c, anomaly, test-anomaly, containment, disposition, retest-decision, anomaly-resolution, test-failure.
    5 repo stars
  39. ▌
    E1003 El Qual · ashfordeou bundle
    Use when define the element qualification test baseline for a space hardware item under ECSS-E-ST-10C §6.2: determine the qualification approach (full qualification versus protoflight) from the element category and prototype test history, map the mission environment drivers to the required test types, compute the qualification level by applying the standard margin over the acceptance level for each test type (vibration, acoustic, shock, thermal cycling, thermal vacuum, quasi-static), compute the qualification duration by applying the duration factor or soak extension over the acceptance duration, and verify that a proposed test plan meets every level and duration requirement against the computed baseline. Trigger: ecss, e-st-10c, element-qualification, qualification-level, qualification-duration, test-baseline, vibration-margin, thermal-margin, protoflight, acceptance-level.
    5 repo stars
  40. ▌
    E1003 Eq Qual · ashfordeou bundle
    Use when defining the equipment qualification test baseline of an ECSS-E-ST-10-03C testing programme: select which test families apply to a piece of equipment and in what sequence (Table 5-1), and derive each applicable test's qualification level and duration from its reference level/duration plus a margin and duration factor (Table 5-2). Trigger: equipment qualification test, qualification baseline, test sequence, Table 5-1, Table 5-2, qualification level, qualification duration, margin factor, E-ST-10-03, ecss, e-st-10c.
    5 repo stars
  41. ▌
    E1004 Geo Ige · ashfordeou bundle
    Use when computing GEO trapped energetic-electron flux and mission fluence for a geostationary spacecraft per ECSS-E-ST-10-04C Annex B.2: interpolate an IGE-2006-style local-time and energy spectral model at fixed L ~= 6.6, apply local-time sector weighting, and produce the differential and integral electron fluence inputs for internal charging and dose analysis. Trigger: GEO trapped electrons, IGE-2006, geostationary, L-shell 6.6, local-time spectrum, electron fluence, internal charging, e-st-10-04, ecss.
    5 repo stars
  42. ▌
    E1004 Gravity · ashfordeou bundle
    Use when you need to define the gravity environment (magnitude and gradient) for a mission orbit under ECSS-E-ST-10-04C: select and apply the Earth gravity model appropriate to the orbit regime (point-mass/low-degree geopotential vs. high-degree geopotential, plus third-body and solid-Earth-tide perturbation terms), compute the gravitational acceleration magnitude and radial gravity gradient at the mission orbit's altitude, verify the mission's stated altitude falls inside the selected model's validity range, and check that the perturbation terms included for the case cover what the orbit regime and mission duration require. Trigger: gravity model, geopotential, Earth gravity field, third-body perturbation, solid Earth tide, gravity gradient, gravitational acceleration, mission orbit, e-st-10-04, ecss, space environment.
    5 repo stars
  43. ▌
    E1004 Indices · ashfordeou bundle
    Use when you must determine which solar and geomagnetic activity indices (F10.7, Ap/Kp) apply to a space environment analysis epoch under ECSS-E-ST-10-04C clause 6.2.2 and Annex A: identify the index set an analysis purpose requires (atmospheric drag/lifetime, electromagnetic radiation reference, geomagnetic field epoch), classify the solar-cycle epoch from the F10.7 81-day-average index into solar minimum/mean/maximum, select the reference index values for that epoch, and verify a case's provided indices are complete and match the worst-case solar condition its purpose requires before the epoch is handed to the leaf that consumes it. Trigger: F10.7, solar radio flux, Ap index, Kp index, geomagnetic activity index, solar activity index, solar-cycle epoch, environment epoch selection, e-st-10-04c 6.2.2, annex a, ecss, space environment indices.
    5 repo stars
  44. ▌
    E1004 L2 Tail · ashfordeou bundle
    Use when defining the radiation environment for a Sun-Earth L2 or deep-magnetotail mission under ECSS-E-ST-10-04C clause 9.2.7: define which unshielded galactic-cosmic-ray and solar-energetic-particle components apply once the trapped-belt boundary is left behind, flag orbit segments that cross the magnetotail plasma sheet or lobes so a supplemental charging environment is added, and verify the resulting environment definition is complete before it feeds the radiation environment specification (RES). Trigger: L2, Lagrange point, deep magnetotail, magnetotail plasma sheet, magnetotail lobe, deep-space radiation environment, unshielded GCR, unshielded SEP, e-st-10-04, ecss.
    5 repo stars
  45. ▌
    E1004 Stormer · ashfordeou bundle
    Use when scoping geomagnetic shielding for LEO solar-energetic-particle (SEP) and galactic-cosmic-ray (GCR) environments under ECSS-E-ST-10-04C clause 9.2.4 and Annex B.8: compute the Stormer vertical cutoff rigidity at a point from its geomagnetic latitude and radial distance, determine whether a particle of given rigidity is geomagnetically excluded or allowed to reach that point, build the exposure-fraction profile across an LEO ground track, and verify the assessment before escalating to full trajectory tracing when the vertical-cutoff approximation cannot be trusted. Trigger: Stormer cutoff, vertical cutoff rigidity, geomagnetic shielding, geomagnetic cutoff, trajectory tracing, penumbra, LEO SEP shielding, GCR geomagnetic cutoff, rigidity cutoff, e-st-10-04, ecss.
    5 repo stars
  46. ▌
    E1006 Process · ashfordeou bundle
    Use when execute the Technical Specification establishment process under ECSS-E-ST-10C §5: advance through phase-0 preliminary TS tasks (F1.1–F1.4), verify that prerequisites are satisfied before starting each task, iterate requirements at each decomposition level until no open changes remain, then advance through phase-A TS tasks (F1.5–F1.10) and issue the phase-A Technical Specification. Trigger: ecss, e-st-10-system-scope, ts-establishment, technical-specification, phase-0, phase-a, requirements-iteration, decomposition, systems-engineering.
    5 repo stars
  47. ▌
    E1006 Purpose · ashfordeou bundle
    Use when assess the purpose, chain position, and content model of an ECSS Technical Specification (TS) per ECSS-E-ST-10C §4: determine whether each TS section belongs to the general part (scope, applicability, normative references, terms and definitions, product definition) or the requirements part (technical requirements, verification requirements, interface requirements, design requirements), identify the TS issuer and recipient roles in the customer–supplier chain, and verify that all mandatory sections are present before placing the TS under configuration control. Trigger: ecss, e-st-10-system-scope, technical-specification, ts-purpose, ts-content-model, customer-supplier-chain, general-part, requirements-part, ts-completeness.
    5 repo stars
  48. ▌
    E1006 Wording · ashfordeou bundle
    Use when verify requirement wording against ECSS-E-ST-10C §8.3 rules: confirm each statement uses shall (mandatory), should (recommendation), or may (permission); detect non-standard verbal forms (will, must); flag ambiguous or unverifiable terms (adequate, appropriate, user-friendly); enforce single obligation per statement; and reject embedded rationale text. Replace forbidden terms with measurable criteria and move justification to a NOTE. Trigger: ecss, e-st-10-system-scope, wording, verbal-form, shall, requirements-authoring, ambiguity, single-statement, verifiability.
    5 repo stars
  49. ▌
    E1009 Csd Drd · ashfordeou bundle
    Use when generate or validate a Coordinate Systems Document (CSD) for a spacecraft project under ECSS-E-ST-10-09C Annex A DRD requirements: define each coordinate frame with a unique identifier, origin, axis directions, frame type, and attachment body; record every frame-to-frame transformation with its rotation sequence and translation vector; populate the parameter tables with numeric values and units referencing the correct frame; and verify the document satisfies the DRD completeness checklist. Apply at any project phase that produces or updates a formal CSD deliverable. Trigger: ecss, e-st-10-system-scope, coordinate-systems, csd, frames, transformations, parameter-tables, drd, annex-a, rotation-sequence.
    5 repo stars
  50. ▌
    E1009 Figures · ashfordeou bundle
    Use when verify that coordinate-frame relationship diagrams conform to ECSS-E-ST-10-09C §5.3.3 figure conventions: confirm each diagram carries a complete annotation set (figure ID, title, origin description, all three axis labels, and frame name), validate the three axes form a right-handed orthogonal triad, check that any Euler-angle rotation sequence is a valid proper-Euler or Tait-Bryan form (three characters, no two consecutive identical axes), and confirm the frame type falls within the recognized ECSS categories (body, orbital, sensor, structural, inertial). Applies to coordinate-system diagrams entering a system data package or design review under ECSS-E-ST-10C. Trigger: ecss, e-st-10-system-scope, coordinate-frame, figure-convention, right-hand-rule, euler-sequence, axis-labeling, frame-diagram, coordinate-relationship.
    5 repo stars
  51. ▌
    E1011 Hcd Drd · ashfordeou bundle
    Use when validate the Human-Centred Design (HCD) process plan against the ECSS-E-ST-10-11C Annex A Document Requirements Definition (DRD): confirm every mandatory section is present (scope, context-of-use description, stakeholder inventory, HCD activity schedule, evaluation plan, HFE staffing, and requirements traceability), verify each HCD activity is linked to a project milestone and a responsible practitioner, confirm evaluation events are categorized as formative or summative with success criteria, and flag any missing HFE practitioner competency record or traceability gap before the plan is submitted for review. Trigger: ecss, e-st-10-11c, hcd, human-centred-design, hfe, human-factors, hcd-plan, drd, evaluation-plan.
    5 repo stars
  52. ▌
    E1011 Medical · ashfordeou bundle
    Use when assess medical facilities and provisions for a crewed spacecraft against ECSS-E-ST-10-11C §4.7.9 HFE requirements: categorize each provision item as emergency, diagnostic, routine, or preventive; determine the minimum required provision set for the mission duration category (short ≤30 days, medium 31–180 days, long >180 days); verify the on-board inventory covers every required item; compute consumable quantities against crew size and mission duration with a 10 percent margin; and flag any missing capability or consumable shortfall as a non-compliance finding. Trigger: ecss, e-st-10-system-scope, medical, crew-health, hfe, medical-provisions, consumables, mission-duration.
    5 repo stars
  53. ▌
    E1011 Offduty · ashfordeou bundle
    Use when design off-duty stations — sleep quarters, personal hygiene facilities, and recreation areas — aboard a crewed spacecraft per ECSS-E-ST-10-11C §4.7.7 HFE requirements: categorize each station as sleep, hygiene, or recreation, verify mandatory parameters (acoustic attenuation, lighting range, thermal envelope, volume, restraint, privacy) for sleep stations, verify containment and accessibility parameters for hygiene facilities, verify exercise volume and communication link availability for recreation areas, and aggregate findings per station to determine overall HFE compliance. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, off-duty-stations, sleep-station, hygiene-facility, recreation, human-factors.
    5 repo stars
  54. ▌
    E1011 Org Env · ashfordeou bundle
    Use when you document the organisational environment for a human spaceflight or ground-intensive mission under ECSS-E-ST-10-11C §4.2.1.5: identify crew roles and their authority levels, map ground support units and interface types, record procedure types with designated approval authorities, and verify that mandatory functions — flight control, systems monitoring, crew support — are covered by at least one ground unit. Flag gaps: missing commander role, uncovered mandatory ground function, or procedure without an approval authority. Produce a complete org-env record before the human factors context-of-use analysis proceeds. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, org-env, crew-organisation, ground-support, procedures, human-factors.
    5 repo stars
  55. ▌
    E1012 Dd Unc · ashfordeou bundle
    Use when determine displacement damage (DD) assessment uncertainty factors for a spacecraft radiation analysis under ECSS-E-ST-10-12C §8.7: identify each uncertainty source (environment model, NIEL scaling, shielding transport, and device response data), assign a numeric factor to each source, combine the factors into an overall uncertainty multiplier using either the multiplicative or root-sum-square method, apply the combined factor to the nominal proton-equivalent fluence to obtain the design fluence, and verify the result accommodates the required design margin. Trigger: ecss, e-st-10-12c, displacement-damage, dd-uncertainty, niel-scaling, radiation-hardness-assurance, proton-fluence, uncertainty-budget, design-margin.
    5 repo stars
  56. ▌
    E50 Security · ashfordeou bundle
    Audit the security a space communication system applies to the data it carries under ECSS-E-ST-50C clause 5.8.3, which asks that protection match how sensitive that data is. Compare each flow's declared services against what its sensitivity group needs — integrity, authentication, replay protection, confidentiality — because none of them substitutes for another; price the tag, initialisation vector and replay counter against every frame; and work out how long one key lasts before the counter space or the per-key frame limit runs out. Use when reviewing a link security design or sizing a rekey interval. Trigger: ecss, e-st-50c-clause-5-8-3, space-link-security-services, security-field-frame-overhead, replay-counter-width-sizing, rekey-interval-lifetime, data-sensitivity-service-mapping.
    5 repo stars
  57. ▌
    E5053 Fields · ashfordeou bundle
    Define the ordered field set a packet transfer protocol data unit is built from. Use when an ECSS-E-ST-50-53C clause 5.4.1.1 sender and receiver have to agree on where every boundary falls: lay out the target logical address, protocol identifier, reserved and user application octets in order after any path-address bytes, close with the self-delimiting packet, compute each field offset and the shortest unit that can carry them, split a received unit back into named fields, and audit a declared field sequence for a missing field, an invented one or a swapped pair. Refuses a repeated field name and a unit too short to hold the set. Trigger: ecss, e-st-50-53c, packet-transfer-unit-field-order, protocol-data-unit-field-offsets, positional-field-layout, minimum-unit-length, field-sequence-audit.
    5 repo stars
  58. ▌
    E7041 Packet · ashfordeou bundle
    Extract the whole space packet a packet-typed parameter carries, under ECSS-E-ST-70-41C clause 7.3.13. Use when a dump report, a forwarded telecommand or a rejection report carries another packet as its value: keeping the contained packet's own primary header rather than stripping it, deriving its size from the packet-length field inside it instead of from any length declared beside it, and splitting a container of back-to-back packets by walking those lengths, so one packet that misstates its own length is caught as a finding before it desynchronises every packet after it. Trigger: ecss, e-st-70-41c, pus-packet-typed-parameter, contained-space-packet-extraction, derived-packet-length-field, packet-store-dump-splitting, forwarded-telecommand-container, container-desynchronisation.
    5 repo stars
  59. ▌
    Fsi Analysis · ashfordeou bundle
    Use when analyze fluid-structure interaction effects in a spacecraft or launch vehicle structural assembly per ECSS-E-ST-32 clause 4.6.2.7: identify sloshing loads from propellant or fluid-filled tank motion, determine hydroelastic coupling between structural vibration modes and enclosed fluid volumes, evaluate aerodynamic buffet excitation during atmospheric flight, compute effective added mass and natural frequency shifts caused by fluid-structure coupling, and verify that combined dynamic responses remain within structural margins. Trigger: ecss, e-st-32-structures-scope, fluid-structure-interaction, sloshing, hydroelastic, buffet, propellant-slosh, fsi, dynamic-coupling, launch-loads.
    5 repo stars
  60. ▌
    Q20 Delivery · ashfordeou bundle
    Manage the delivery of a consignment under ECSS-Q-ST-20C clause 5.7.5: derive the shipping control documents the consignment owes from its own states rather than from a standing list, read the transport monitoring record for excursions outside each declared environmental limit, treat the unmonitored part of a journey as unknown instead of compliant, reconcile the identification on the certificate of conformity with the consignment it covers, and decide whether that certificate may be issued at all. Use when goods are about to move and the paperwork has to travel with them. Trigger: ecss, q-st-20c-clause-5-7-5, shipping-control-documentation, transport-environment-excursion, transport-monitor-coverage-gap, certificate-of-conformity-issue, consignment-identification-match.
    5 repo stars
  61. ▌
    Q20 Eidp Drd · ashfordeou bundle
    Structure and assess the end item data package of ECSS-Q-ST-20C Annex B against its document requirements description: emit the numbered table of contents the DRD fixes, group every submitted document under the design, manufacturing, test or acceptance data it belongs to, raise a document filed under the wrong category as its own finding, name what each category is short of, list an unrecognised document as an extra instead of failing on it, and return the per-category and whole-package completeness. Use when a data package is compiled, indexed or reviewed before handover. Trigger: ecss, q-st-20c-annex-b, eidp-drd, eidp-document-categories, eidp-table-of-contents, eidp-design-data, eidp-manufacturing-data, eidp-acceptance-data.
    5 repo stars
  62. ▌
    Q20 Gse Eidp · ashfordeou bundle
    Produce the end item data package a delivered piece of ground support equipment owes under ECSS-Q-ST-20C clause 5.8.4.1: derive the package sections from the item's own states instead of a standing table, refuse a section still in draft or marked approved with nobody behind it, force every open nonconformance into the package the receiving side accepts the item with, compute the approved fraction of the required set and decide whether the package may be released. Use when GSE is about to change hands and its data package has to be assembled or audited. Trigger: ecss, q-st-20c-clause-5-8-4-1, gse-end-item-data-package, gse-eidp-section-derivation, gse-eidp-approval-state, gse-open-nonconformance-carry-over, gse-data-package-release.
    5 repo stars
  63. ▌
    Acoustic Test · ashfordeou bundle
    Use when perform acoustic test verification of a spacecraft structure per ECSS-E-ST-32C clause 4.6.3.10: derive the 1/3-octave band test spectrum from the launch acoustic environment, apply the qualification margin to acceptance levels, compute the Overall Sound Pressure Level (OASPL), verify frequency range covers 31.5 Hz to 10 kHz, check test duration against the category minimum, and assess band-by-band spectrum compliance within tolerance. Categorize the test as qualification, acceptance, or protoflight; flag duration shortfalls, frequency coverage gaps, and spectrum underdrive or overdrive. Trigger: ecss, e-st-32-structures-scope, acoustic-test, acoustic-noise, oaspl, sound-pressure-level, vibro-acoustic, structural-test.
    5 repo stars
  64. ▌
    Drd Fci Lists · ashfordeou bundle
    Use when build the Annex G fracture-critical item register for a structure assessed under ECSS-E-ST-32C: screen each structural item against fracture-criticality criteria, assign each item to the Primary Fracture Critical Item List (PFCIL), Fracture Critical Item List (FCIL), or Fracture Limited Life Item List (FLLIL), validate entry fields and numeric bounds, compute the fracture life margin of safety, and verify that both the PFCIL and FLLIL are proper subsets of the FCIL. Trigger: ecss, e-st-32-structures-scope, fracture-control, fci-lists, pfcil, fcil, fllil, fracture-criticality, drd.
    5 repo stars
  65. ▌
    E10 Risk Mgmt · ashfordeou bundle
    Use when managing technical risk for a space project under ECSS-E-ST-10C clause 5.6.8: identify a risk, analyse it into a likelihood x severity risk class, plan and record mitigation actions for risks that require them, assess the residual risk left after mitigation, and escalate residual risk that remains above the acceptable band for formal acceptance, in coordination with the ECSS risk-management standard M-ST-80. Distinct from the sibling e10-req-risk-analysis leaf, which scores risk per individual requirement rather than tracking the project-wide risk register through mitigation, residual assessment, and acceptance. Trigger: ecss, e-st-10c, technical risk management, risk register, mitigation action, residual risk, risk acceptance, m-st-80, risk escalation.
    5 repo stars
  66. ▌
    E10 Spec Tree · ashfordeou bundle
    Use when establishing or maintaining the specification tree of a space product decomposition per ECSS-E-ST-10C clause 5.2.3.1c and Annex J: mirror the product tree with one technical specification per node (support specifications included), check the tree has no orphan or duplicate specs, and confirm every spec's parent link matches the product tree's parent-child structure. Trigger: specification tree, spec tree, product decomposition, support specification, ECSS-E-ST-10C 5.2.3.1c, Annex J.
    5 repo stars
  67. ▌
    E10 Tradeoffs · ashfordeou bundle
    Use when comparing candidate solutions to a system engineering decision under ECSS-E-ST-10C clause 5.3.3 and Annex L: define the evaluation criteria and their weights, score each candidate against every criterion on a common scale, gate any candidate that fails a mandatory pass/fail criterion, rank the remaining candidates by weighted score, and flag when the recommendation is a close call sensitive to the weighting assumptions rather than a clear-cut winner -- then record the result as a trade-off report. Trigger: ecss, e-st-10-system-scope, trade-off analysis, tradeoff, evaluation criteria, weighted scoring, candidate solution, annex l, trade-off report.
    5 repo stars
  68. ▌
    E1002 Phasing · ashfordeou bundle
    Use when phasing verification activities with the project life cycle under ECSS-E-ST-10-02C clause 5.2.7: locate a life-cycle phase in the project phase sequence, decide whether a phase carries a verification output requirement, list the outputs that phase owes and the gaps against them, check entry readiness for a target phase, rank per-requirement verification maturity, roll that up to a project-wide status, and run the full phasing review. Trigger: ecss, e-st-10-02c, verification phasing, life cycle, phase A, phase outputs, entry readiness, maturity rank, project verification status.
    5 repo stars
  69. ▌
    E1002 Process · ashfordeou bundle
    Use when running the verification process as a customer-supplier activity under ECSS-E-ST-10-02C clause 5.1: validate the product level, life-cycle phase, activity status and document type of each verification activity, assign the executor and the closure approver by role, determine which documents a phase still owes before it can close, roll individual activity statuses up to a single process status, and verify a closure sign-off against the activity's required evidence. Trigger: ecss, e-st-10-02c, verification process, customer supplier, product level, responsibility assignment, documentation completeness, closure sign-off, activity roll-up.
    5 repo stars
  70. ▌
    E1003 Ait Drd · ashfordeou bundle
    Use when validate an Assembly, Integration and Test (AIT) plan against the ECSS-E-ST-10C Annex A Document Requirements Definition: verify all required DRD sections are present (objectives, product tree, test campaign, schedule, facilities, responsibilities), confirm every test traces to at least one verifiable requirement, check that every product tree item carries at least one test assignment, and flag tests that need a special facility but carry no facility reference. Trigger: ecss, e-st-10c, e-st-10-system-scope, ait-plan, assembly-integration-test, drd, test-traceability, product-tree, facility-assignment.
    5 repo stars
  71. ▌
    Q20 Coc Drd · ashfordeou bundle
    Prepare and assess the certificate of conformity of ECSS-Q-ST-20C Annex D against its document requirements description: validate the identification and signature fields the DRD names, refuse a certificate asserting full conformity while enumerating deviations or qualifying its conformity with none listed, resolve every evidence reference against the delivered evidence register, report the coverage, and reject a signature held by a function inside the organisation that built the item or dated before the evidence it certifies. Use when a certificate is raised, countersigned or checked at incoming inspection. Trigger: ecss, q-st-20c-annex-d, certificate-of-conformity-drd, coc-conformity-statement, coc-evidence-references, coc-signature-authority, coc-deviation-list.
    5 repo stars
  72. ▌
    Q20 Qap Drd · ashfordeou bundle
    Generate and assess the quality assurance plan of ECSS-Q-ST-20C Annex A against its document requirements description: build the numbered DRD outline the contract level owes, decide whether each section carries the subjects the DRD names, confirm the organisation section states a quality function independent of the line that builds the product, reconcile the task provisions with the level's set, resolve every procedure the plan cites against its own reference list, and refuse a tailoring declaration on scope or organisation. Use when a quality plan is drafted, tailored or reviewed before submission. Trigger: ecss, q-st-20c-annex-a, quality-assurance-plan-drd, qa-plan-section-order, qa-plan-task-provisions, qa-plan-independence-statement, qa-plan-tailoring-justification.
    5 repo stars
  73. ▌
    Static Test · ashfordeou bundle
    Use when assess static structural test compliance for a spacecraft or launch vehicle structural assembly under ECSS-E-ST-32C clause 4.6.3.7: determine the required test load from the design limit load and the applicable load factor (qualification ultimate, qualification yield, or acceptance proof), generate the incremental load-application sequence with hold steps, compute margin of safety for each critical load case, and evaluate the success criteria covering no fracture at the test load level, residual deformation within the post-test allowable, and structural stiffness within the model-correlation tolerance band. Trigger: ecss, e-st-32-structures-scope, static-test, structural-test, load-factor, margin-of-safety, qualification, acceptance, load-application.
    5 repo stars
  74. ▌
    Drd Buckling · ashfordeou bundle
    Use when determine the structural buckling capacity of load-bearing members for an ECSS-E-ST-32C Annex M buckling report: categorize each member by geometry (column, flat plate, or shell), resolve the effective length factor from its boundary conditions, compute the critical buckling stress using the Euler formula for slender columns or the Johnson parabolic formula for intermediate columns, apply a knock-down factor for initial geometric imperfections, evaluate the margin of safety against the applied compressive stress, and confirm that every member achieves a non-negative margin of safety. Trigger: ecss, e-st-32c, buckling, column-buckling, plate-buckling, euler, johnson, knock-down, margin-of-safety, structural-report.
    5 repo stars
  75. ▌
    E1002 Levels · ashfordeou bundle
    Use when a product tree needs its verification levels defined and every requirement needs a verification level assigned before verification planning under ECSS-E-ST-10-02C: build the equipment/subsystem/element/segment/system hierarchy, assign each requirement to the level of the component(s) it is allocated to, and check whether a level is ready to close out. Trigger: verification level, verification levels, equipment subsystem element segment system, product tree, common ancestor, level closure, level close-out, E-ST-10-02, ecss, e-st-10c.
    5 repo stars
  76. ▌
    E1002 Models · ashfordeou bundle
    Use when a space project must define its verification model philosophy under ECSS-E-ST-10-02C: choosing prototype vs protoflight, listing the physical models (STM, EM, QM, PFM, FM, EQM) with purpose/configuration/stages for the Verification Plan, checking a model is representative of the item it stands in for, and flagging re-verification after a design change. Trigger: model philosophy, prototype model, protoflight, qualification model, flight model, engineering model, model list, verification plan, VP, model-based verification, E-ST-10-02, ecss, e-st-10c.
    5 repo stars
  77. ▌
    E1002 Stages · ashfordeou bundle
    Use when defining verification stages for a product under ECSS-E-ST-10-02C: qualify, accept, verify pre-launch, in-orbit (incl. commissioning) and post-landing each with its objective and applicability to the product's launched/recovered life profile, ahead of stage-specific planning (qualification, acceptance, pre-launch, in-orbit, post-landing leaves). Trigger: verification stages, qualification stage, acceptance stage, pre-launch verification, in-orbit verification, commissioning, post-landing verification, E-ST-10-02, ecss, e-st-10c.
    5 repo stars
  78. ▌
    E1003 El Emc · ashfordeou bundle
    Use when running element electromagnetic compatibility tests under ECSS-E-ST-10-03C §6.5.5: determine auto-compatibility by verifying that each internal emitter's frequency has sufficient isolation margin against every internal receive band, evaluate passive intermodulation (PIM) products for RF-bearing elements to confirm no odd-order products fall within the receive band, perform residual magnetic dipole moment checks against the element magnetic budget, and identify the correct test mode—stand-alone or embedded—per §6.5.5.2 for each applicable test category. Trigger: ecss, e-st-10-03c, emc, electromagnetic-compatibility, pim, passive-intermodulation, magnetic-field, auto-compatibility, stand-alone, embedded.
    5 repo stars
  79. ▌
    E1004 B6 Esp · ashfordeou bundle
    Use when generating the Annex B.6 Emission of Solar Protons (ESP) worst-case fluence spectra for a mission under ECSS-E-ST-10-04C: build the reference annual integral fluence spectrum, apply the confidence-level scale factor for the required design percentile, apply the mission-duration scale factor for the exposure period, assemble the resulting fluence-above-energy spectrum, and verify the selected confidence level meets the mission's worst-case design threshold. Trigger: ESP, emission of solar protons, solar proton fluence, solar particle event, worst-case fluence, confidence level, JPL model, Annex B.6, e-st-10-04, ecss, space environment, radiation environment.
    5 repo stars
  80. ▌
    E1004 Debris · ashfordeou bundle
    Use when a space project must define which space debris flux model (MASTER-class or ORDEM-class) to select and apply, under ECSS-E-ST-10-04C clause 10.2.2.1, for a mission's orbit and analysis epoch: validating that a candidate model's declared altitude/inclination/epoch/diameter envelope actually covers the mission envelope, building a complete model run request, and determining when a prior result needs re-assessment. Trigger: space debris flux, debris environment model, MASTER model, ORDEM model, orbital debris, debris flux envelope, debris risk input, E-ST-10-04, ecss, e-st-10c.
    5 repo stars
  81. ▌
    E1004 Geomag · ashfordeou bundle
    Use when defining the geomagnetic field environment model for a mission under ECSS-E-ST-10-04C: select the applicable geomagnetic field model (an IGRF-class internal field model alone at low/mid geocentric distance, or that model combined with an external/magnetospheric field model at high geocentric distance) from the mission orbit's geocentric distance, determine the correct IGRF epoch and apply secular variation to update the reference internal field for the mission's target date, verify the target date remains within the secular-variation extrapolation validity window, compute the dipole-approximation B,L equatorial field magnitude for radiation-belt characterization, and validate that the analysis case's declared model and epoch handling meet these requirements. Trigger: geomagnetic field, IGRF, secular variation, B L coordinates, magnetospheric field, external field model, Tsyganenko, dipole approximation, e-st-10-04, ecss, space environment.
    5 repo stars
  82. ▌
    E1004 Plasma · ashfordeou bundle
    Use when defining the plasma environment required by ECSS-E-ST-10-04C clause 8.2 for spacecraft charging analysis: determine which plasma regions (ionosphere, plasmasphere, auroral, outer magnetosphere, solar wind, magnetosheath, magnetotail/L2, planetary, induced) apply to each orbit segment, verify that a model and the electron density, electron temperature, ion density, and ion temperature are recorded for every applicable region, and identify missing regions or incomplete entries before the charging environment definition is closed out. Trigger: plasma environment, spacecraft charging, e-st-10-04, ecss, electron density, ion temperature, surface charging, auroral charging, outer magnetosphere plasma, plasmasphere, induced plasma.
    5 repo stars
  83. ▌
    E1006 TS Drd · ashfordeou bundle
    Use when validate a Technical requirements specification (TS) document against the ECSS-E-ST-10C Annex A DRD: confirm all mandatory sections are present (system identification, mission context, technical performance requirements, interface requirements, environmental conditions, and verification cross-reference table), verify each requirement carries a unique identifier and an assigned verification method (test, analysis, inspection, or review of design), check that interface requirements reference a registered ICD entry, and flag any absent mandatory section or any requirement lacking a verification method. Trigger: ecss, e-st-10-system-scope, technical-specification, ts-drd, requirements-document, verification-method, interface-requirement, drd-validation.
    5 repo stars
  84. ▌
    E1011 Params · ashfordeou bundle
    Use when identify and map the interrelated HFE parameters that characterise a human-machine system under ECSS-E-ST-10-11C §4.2.1.1–4.2.1.2: categorize each parameter into the standard parameter set (performance, workload, situation awareness, human error, training, environment, interface, communication), trace interrelationships among parameter categories, assess completeness of the parameter set against required categories, and verify that every defined system phase carries at least one parameter assignment. Trigger: ecss, e-st-10-system-scope, hfe-parameters, human-machine-system, workload, situation-awareness, human-error, parameter-completeness.
    5 repo stars
  85. ▌
    E1011 Req Id · ashfordeou bundle
    Use when identify HFE requirements from mission-phase and operator-role analysis and capture them into the Technical Specification (TS) under ECSS-E-ST-10-11C §4.3.7: enumerate every applicable mission phase, assign the operator roles active in each phase, map each phase-role pair to the relevant HFE driver categories (workload, habitability, anthropometry, visibility, reachability, cognitive, communication, safety), generate a structured requirement ID for each identified driver, verify that every phase carries at least the mandatory safety and workload requirements, and confirm that all generated IDs are unique and correctly formatted before the TS baseline is closed. Trigger: ecss, e-st-10-system-scope, hfe-requirements, mission-phase, operator-role, human-factors, requirement-identification, technical-specification.
    5 repo stars
  86. ▌
    E1011 Safety · ashfordeou bundle
    Use when assess HFE safety requirements for a spacecraft operations catalogue under ECSS-E-ST-10-11C §4.6.3: categorize each operation by hazard criticality (critical, high, medium, low), verify that human-error prevention measures — confirmation steps, interlocks, reversibility checks, crew notification, dual verification — are present at the level each criticality demands, check that irreversible high-consequence operations carry maximum protection, confirm safety-critical operator interfaces provide clear state cues and go/no-go criteria, and flag every operation whose protection set falls below the minimum for its level. Trigger: ecss, e-st-10-system-scope, hfe, human-factors, safety-critical-operations, human-error-prevention, interlock, crew-notification.
    5 repo stars
  87. ▌
    E1012 Bg Gwd · ashfordeou bundle
    Use when estimate radiation-induced noise contributions for a space-based gravity-wave detector test mass under ECSS-E-ST-10-12C §10.4.7: determine the particle-flux-driven charge deposition rate on the test mass, compute the stochastic force noise power spectral density from charge shot-noise coupling and from cosmic-ray momentum-transfer recoil, convert total force noise to displacement noise using the free test-mass transfer function, verify that accumulated charge stays within the charge-management design limit, and compare resulting displacement noise against the instrument radiation noise budget allocation. Trigger: ecss, e-st-10-system-scope, gravity-wave-detector, radiation-noise, charge-deposition, force-noise-psd, displacement-noise, cosmic-ray, test-mass, noise-budget.
    5 repo stars
  88. ▌
    E10 Djf Drd · ashfordeou bundle
    Use when assemble or review a product Design Justification File against the ECSS-E-ST-10C Annex K Document Requirements Definition: validate each justification record's method and review status, confirm every record cites the document its evidence lives in, resolve each requirement to justified, open, rejected-evidence or no-evidence under a severity ordering, surface a requirement whose accepted argument rests on similarity alone, and decide whether the file supports the design. Trigger: ecss, e-st-10-system-scope, design-justification-file, djf, annex-k-drd, justification-evidence, similarity-heritage, evidence-traceability.
    5 repo stars
  89. ▌
    E10 Mdd Drd · ashfordeou bundle
    Use when generating or validating a Mission Description Document (MDD) for a European space project per ECSS-E-ST-10C Annex B: check that the required sections (objectives, mission statement, mission scenario, constraints) are present, that the mission statement carries an objective/target/timeframe, that the mission scenario phases follow the launch-to-disposal order, and that every constraint is categorised (programmatic, technical, operational, environmental) before the MDD is handed off at MDR. Trigger: mdd, mission description document, annex b, e-st-10c annex b, mission statement, mission scenario, mission constraints, drd, mission definition review, mdr package.
    5 repo stars
  90. ▌
    E10 Pum Drd · ashfordeou bundle
    Use when produce or review a Product User Manual against the ECSS-E-ST-10C Annex P Document Requirements Definition: confirm the manual declares the product configuration it describes and that it matches what was delivered, confirm every required section is present and not empty, confirm procedure steps are numbered contiguously without repeats, confirm every hazardous step carries its warning ahead of the step, and confirm each maintenance task states its interval and required resources. Trigger: ecss, e-st-10-system-scope, product-user-manual, pum, annex-p-drd, operating-procedures, hazard-warnings, maintenance-interval, configuration-match.
    5 repo stars
  91. ▌
    E10 Rjf Drd · ashfordeou bundle
    Use when compile or audit a Requirements Justification File against the ECSS-E-ST-10C Annex O Document Requirements Definition: validate each requirement's derivation basis, confirm a parent-derived requirement names its parent and that a top-level requirement rests on a standard or mission need instead, detect a rationale that merely restates the requirement it is meant to justify, confirm each rationale is attributed, and decide whether every requirement is justified. Trigger: ecss, e-st-10-system-scope, requirements-justification-file, rjf, annex-o-drd, derivation-basis, requirement-rationale, attribution.
    5 repo stars
  92. ▌
    E10 Rtm Drd · ashfordeou bundle
    Use when build or audit a requirements traceability matrix against the ECSS-E-ST-10C Annex N Document Requirements Definition: confirm every row carries its DRD fields, trace each derived requirement upward to a parent that exists in the matrix, trace each requirement that must flow down to at least one child, detect parent-pointer cycles, and confirm each allocation names a real product-tree element and each verification method is one of the four recognized ones. Trigger: ecss, e-st-10-system-scope, traceability-matrix, annex-n-drd, upward-trace, downward-trace, requirement-allocation, trace-coverage.
    5 repo stars
  93. ▌
    E10 Scr Drd · ashfordeou bundle
    Use when preparing a System Concept Report (SCR) for a European space project per ECSS-E-ST-10C Annex C: validate that the required sections (candidate concepts, trade summary, feasibility assessment, recommended concept) are present, that every candidate concept carries a description, that the trade summary scores every candidate against all trade criteria (technical, programmatic, cost, risk), that every candidate carries a valid feasibility verdict, and that the recommended concept is a known candidate that is not itself flagged not_feasible before the SCR is handed off at the end of phase 0/A. Trigger: scr, system concept report, annex c, e-st-10c annex c, candidate concepts, trade summary, trade-off analysis, feasibility assessment, drd, concept selection, down-select.
    5 repo stars
  94. ▌
    E10 Se Mgmt · ashfordeou bundle
    Use when manage the system engineering activities, responsibilities and interfaces of the SE function as defined in the System Engineering Plan (SEP) under ECSS-E-ST-10C clause 5.6.1: categorize each SE activity by kind, determine its assigned responsible role against the SEP responsibility assignment, verify each activity's required interfaces to other project functions (project management, product assurance, engineering disciplines, customer) are on record, and track activity status so a blocked activity carries a reason and a completed activity has no open prerequisite. Trigger: ecss, e-st-10-system-scope, se management, sep, responsibility assignment, interface control, system engineering plan, e-st-10c 5.6.1.
    5 repo stars
  95. ▌
    E10 Sep Drd · ashfordeou bundle
    Use when you must generate or validate a System Engineering Plan (SEP) document against its document-requirements-definition (DRD) per ECSS-E-ST-10C Annex D: check the document carries every mandatory content block (introduction, applicable/reference documents, SE organisation, SE processes, SE tasks, DRD linkage), that every organisation interface (product assurance, AIV, risk management, configuration management, software engineering) is covered by an assigned role, that every task has a known owner, and that every document the SEP claims to plan or control exists in the project's master document list. This checks the SEP document's DRD content shape; see the sibling e10-sep leaf for SEP maintenance and baseline-consistency logic. Trigger: sep drd, system engineering plan drd, ecss annex d, sep content, sep document requirements, e-st-10c annex d.
    5 repo stars
  96. ▌
    E1006 Types · ashfordeou bundle
    Use when classify technical requirements for a space system under ECSS-E-ST-10C §6.2.1–6.2.13: assign each requirement to one of twelve requirement types (functional, mission, interface, environmental, operational, human factor, ILS, physical, PA-induced, configuration, design, verification), confirm every requirement belongs to exactly one type, and flag requirement statements that cannot be assigned without additional information. Trigger: ecss, e-st-10-system-scope, requirement-types, functional, mission, interface, environmental, operational, physical, PA-induced, configuration, design, verification.
    5 repo stars
  97. ▌
    E1009 Frame · ashfordeou bundle
    Use when define and validate a spacecraft reference frame under ECSS-E-ST-10C §5.4.1: establish the frame origin and three orthogonal right-handed axes, label each axis with a physical direction reference, determine whether the frame is inertial or time-varying (body-fixed, orbit-referenced, or planet-fixed), supply an epoch for inertial frames, confirm the name follows the ECSS uppercase-alphanumeric convention, and verify that any child frame traces an unbroken chain back to a root inertial frame. Trigger: ecss, e-st-10-system-scope, reference-frame, coordinate-frame, axes, right-handed, inertial, body-fixed, orbit-referenced, frame-naming.
    5 repo stars
  98. ▌
    E1009 Units · ashfordeou bundle
    Use when verify that every coordinate and derived quantity in a space-system interface document or software parameter list states its unit as the SI standard or an explicitly listed stated exception, per ECSS-E-ST-10-09C §5.4.3. For each parameter: determine the quantity type (distance, angle, time, angular rate, velocity, mass, force, pressure, temperature, frequency, acceleration), identify the prescribed SI unit, check whether the actual stated unit is SI or appears on the stated-exception list, and flag any parameter whose unit is neither. Output a per-parameter verdict (si, stated_exception, or non_compliant) and a summary of all findings. Trigger: ecss, e-st-10-system-scope, units, SI-units, coordinates, reference-frames, stated-exceptions, quantity-types, parameter-verification.
    5 repo stars
  99. ▌
    E1024 Verif · ashfordeou bundle
    Use when verify and validate interfaces under ECSS-E-ST-10-24C §5.6: check each ICD record for completeness (required fields, valid interface type, non-self-referential subsystems), confirm every VCD entry carries an approved verification method per E-ST-10-02 (test, analysis, inspection, review, or similarity) and a recognized status, trace each interface requirement to at least one VCD entry to identify coverage gaps, and flag interface items with no verification record. Trigger: ecss, e-st-10-system-scope, e-st-10-24c, interface-verification, icd, vcd, verification-control-document, interface-compliance, coverage-trace.
    5 repo stars
  100. ▌
    E4008 Event · ashfordeou bundle
    Validate the event publish-and-subscribe design of a space simulator against ECSS-E-ST-40-08C clause 5.4.6. Use when the task is declaring an event source with one typed argument, refusing a repeated subscription or an unsubscribe by a sink that never subscribed, holding notification in subscription order, checking an emitted argument against the declared type, keeping an emission out of a simulator state that cannot honour it, isolating one raising sink so the sinks behind it are still notified, and grading the design against the fourteen normative items the clause carries. Trigger: ecss, e-st-40-08c, simulator-event-source, simulator-event-sink, event-subscription-order, event-argument-type-check, duplicate-event-subscription, event-sink-failure-isolation, event-emission-state-guard.
    5 repo stars