ECSS Space Environment — Component Dose-Effects Margin Factors (space-systems/ecss/e1012-dose-effects)
Use when the task is applying component dose-effects margin factors per
ECSS-E-ST-10 §5.5.2 — determining whether each electronic component's
radiation tolerance, after multiplication by the radiation design margin
(RDM), is met, and whether its parametric and functional degradation limits
remain within specification.
Domain quick reference
- §5.5.2 requires that the predicted component dose (from the mission
radiation environment analysis) be multiplied by a margin factor —
the radiation design margin — before comparing to the component's
specified tolerance. The standard RDM is 2.0 unless a project-specific
value is justified and formally agreed.
- Two degradation checks supplement the tolerance comparison:
(a) parametric degradation — each performance parameter (gain,
leakage current, threshold voltage, etc.) has an allowable change
fraction relative to its pre-irradiation nominal; exceeding that fraction
is a finding even if the gross tolerance is met;
(b) functional degradation — the component must still satisfy its
functional specification at the required (margin-multiplied) dose.
- A component is dose-effects compliant only when all three checks pass:
the tolerance check, every parametric limit, and the functional test.
A marginal pass on one check does not compensate a failure on another.
- Radiation-hardness-assurance (RHA) grades and lot acceptance test
results are the primary evidence for component tolerance values; generic
data-sheet minimums without RHA evidence are flagged as insufficient.
Workflow
- Obtain the predicted dose for every component location from the
environment analysis. Reject any component with no dose record before
proceeding — an absent predicted dose is itself a finding.
- Multiply each predicted dose by the RDM (default 2.0) to get the
required tolerance. Flag any component whose documented tolerance is
below that required value; do not waive without a formal deviation.
- For each component, retrieve the parametric degradation specification:
the allowable change fraction for each tracked parameter. For each
parameter compute the fractional change between the pre-irradiation
nominal and the post-irradiation degraded value. Flag any parameter
whose change fraction exceeds its allowable limit.
- Confirm that the component passes its functional test at the required
(margin-multiplied) dose. A component that nominally meets the gross
tolerance but fails a functional test at that dose is non-compliant.
- Aggregate findings per component: a component with any dose, parametric,
or functional finding is non-compliant. Record which check failed and by
how much (the margin shortfall or the exceeded change fraction).
- Produce a component disposition table: compliant / non-compliant, with
the specific finding for each flagged component. This table feeds the
radiation-effects section of the design review package.
Pitfalls
- Comparing predicted dose directly to component tolerance without
applying the RDM — the factor of two (or project value) is mandatory;
skipping it understates the design requirement.
- Treating a gross tolerance pass as sufficient when parametric limits
have not been individually verified — a component that survives the
total dose but degrades a critical parameter beyond its allowed fraction
is non-compliant regardless of the tolerance margin.
- Using minimum data-sheet values instead of RHA-graded or lot-verified
tolerance data — data-sheet minimums are often not characterised for
the relevant radiation type or dose rate, and must not substitute for
RHA evidence without formal justification.
- Applying the same RDM to every location without considering shielding
heterogeneity — components behind thick shielding accumulate less dose;
each location needs its own predicted-dose input before the RDM is applied.
- Conflating total ionizing dose (TID) effects with displacement damage
(NIEL) effects — §5.5.2 addresses TID parametric and functional
degradation; displacement damage is a separate mechanism requiring its
own limit check and is not covered by this leaf.
Behavior contract (gate 3)
The dose-margin, parametric-degradation, and functional-degradation logic
is exercised by the gate-3 contract test:
scripts/test_e1012_dose_effects.py against
scripts/e1012_dose_effects_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1012_dose_effects.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1012-dose-effects3description: "Use when assessing radiation dose-effects margin compliance for electronic4 components under ECSS-E-ST-10 §5.5.2: apply the radiation design margin factor to5 the predicted component dose, compare the result against each component's specified6 tolerance, check parametric degradation limits (gain, leakage current, threshold7 voltage) against allowable change fractions, verify functional continuity at the8 margin-multiplied dose, and flag every component that fails a dose, parametric, or9 functional limit. Trigger: ecss, e-st-10-system-scope, dose-effects,10 radiation-design-margin, total-ionizing-dose, parametric-degradation,11 functional-degradation, component-tolerance."12license: Apache-2.013compliance: STANDARDS-REF14standards:15 - id: ecss16 reference-only: true17gated: false18domain: space-systems19pack: space-systems20compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"21metadata:22 source: https://skillmd.com/skills/ashfordeou/e1012-dose-effects23 domain: space-systems24 subdomain: ecss25 tags: [ecss, e-st-10-system-scope, dose-effects, radiation-design-margin, total-ionizing-dose, parametric-degradation, functional-degradation, component-tolerance]26 version: 0.1.027 author: Aero Agent Skills28---2930# ECSS Space Environment — Component Dose-Effects Margin Factors (space-systems/ecss/e1012-dose-effects)3132Use when the task is applying component dose-effects margin factors per33ECSS-E-ST-10 §5.5.2 — determining whether each electronic component's34radiation tolerance, after multiplication by the radiation design margin35(RDM), is met, and whether its parametric and functional degradation limits36remain within specification.3738## Domain quick reference3940- §5.5.2 requires that the predicted component dose (from the mission41 radiation environment analysis) be multiplied by a margin factor —42 the radiation design margin — before comparing to the component's43 specified tolerance. The standard RDM is 2.0 unless a project-specific44 value is justified and formally agreed.45- Two degradation checks supplement the tolerance comparison:46 (a) **parametric degradation** — each performance parameter (gain,47 leakage current, threshold voltage, etc.) has an allowable change48 fraction relative to its pre-irradiation nominal; exceeding that fraction49 is a finding even if the gross tolerance is met;50 (b) **functional degradation** — the component must still satisfy its51 functional specification at the required (margin-multiplied) dose.52- A component is dose-effects compliant only when all three checks pass:53 the tolerance check, every parametric limit, and the functional test.54 A marginal pass on one check does not compensate a failure on another.55- Radiation-hardness-assurance (RHA) grades and lot acceptance test56 results are the primary evidence for component tolerance values; generic57 data-sheet minimums without RHA evidence are flagged as insufficient.5859## Workflow60611. Obtain the predicted dose for every component location from the62 environment analysis. Reject any component with no dose record before63 proceeding — an absent predicted dose is itself a finding.642. Multiply each predicted dose by the RDM (default 2.0) to get the65 required tolerance. Flag any component whose documented tolerance is66 below that required value; do not waive without a formal deviation.673. For each component, retrieve the parametric degradation specification:68 the allowable change fraction for each tracked parameter. For each69 parameter compute the fractional change between the pre-irradiation70 nominal and the post-irradiation degraded value. Flag any parameter71 whose change fraction exceeds its allowable limit.724. Confirm that the component passes its functional test at the required73 (margin-multiplied) dose. A component that nominally meets the gross74 tolerance but fails a functional test at that dose is non-compliant.755. Aggregate findings per component: a component with any dose, parametric,76 or functional finding is non-compliant. Record which check failed and by77 how much (the margin shortfall or the exceeded change fraction).786. Produce a component disposition table: compliant / non-compliant, with79 the specific finding for each flagged component. This table feeds the80 radiation-effects section of the design review package.8182## Pitfalls8384- Comparing predicted dose directly to component tolerance without85 applying the RDM — the factor of two (or project value) is mandatory;86 skipping it understates the design requirement.87- Treating a gross tolerance pass as sufficient when parametric limits88 have not been individually verified — a component that survives the89 total dose but degrades a critical parameter beyond its allowed fraction90 is non-compliant regardless of the tolerance margin.91- Using minimum data-sheet values instead of RHA-graded or lot-verified92 tolerance data — data-sheet minimums are often not characterised for93 the relevant radiation type or dose rate, and must not substitute for94 RHA evidence without formal justification.95- Applying the same RDM to every location without considering shielding96 heterogeneity — components behind thick shielding accumulate less dose;97 each location needs its own predicted-dose input before the RDM is applied.98- Conflating total ionizing dose (TID) effects with displacement damage99 (NIEL) effects — §5.5.2 addresses TID parametric and functional100 degradation; displacement damage is a separate mechanism requiring its101 own limit check and is not covered by this leaf.102103## Behavior contract (gate 3)104105The dose-margin, parametric-degradation, and functional-degradation logic106is exercised by the gate-3 contract test:107scripts/test_e1012_dose_effects.py against108scripts/e1012_dose_effects_logic.py (stdlib unittest, offline). Run:109110```111python3 scripts/test_e1012_dose_effects.py112```113114## Compliance115116- ECSS standards are freely downloadable (ESA); cite the source and117 paraphrase per standards-map.yaml.118- compliance: STANDARDS-REF, gated: false.