ECSS EEE Components — Class 3 Alert and Advisory Handling (space-systems/ecss/q60-class-3-alert-handling)
Use when the task is the clause 6.5.3 step of ECSS-Q-ST-60C: an alert, an
errata sheet or a manufacturer advisory has landed on a part the programme
already selected at the lowest assurance class, and the question is which of
the parts on the declared list it actually reaches, what that earns, and by
when. The hard part at this class is not the action. It is that the records
frequently cannot say whether the advisory reaches a given entry at all.
Domain quick reference
- Applicability is three valued here, not two. The part number decides first
and a different one excludes the entry outright. After that a named
manufacturer or a named date-code range can exclude an entry only when the
entry records that same field. Where it records nothing, the answer is
indeterminate, because the records cannot rule the entry out.
- An indeterminate entry is worked as if it applied. That is the safe default
and, at this class, the common one. What the assessment owes alongside it is
the specific evidence that would decide it: a goods-in record naming the
actual manufacturer, or a label record carrying the delivered date code.
- Indeterminate is not the same as urgent. It is worked, but it sits just
under a confirmed match at the same severity and stage, so a queue never
puts an unproven entry ahead of a proven one.
- The action comes from severity and procurement stage together. The same
alert reselects a part still only on paper, holds an order, quarantines
stock, recalls a kit, or reaches the customer, depending on how far the
entry had travelled when the advisory arrived.
- Availability decides where the response can be built at all. A part still
on the market with an approved equivalent is answered from stock; without
one it earns a last-time buy with added screening; and a part that can no
longer be bought cannot be answered by procurement, so anything above an
information notice moves the response into the design.
- One advisory rarely touches one programme. The same commercial part number
usually sits on several declared lists, and the advisory is fanned out to
every programme holding it.
- The acknowledgement clock runs in working days from issue and runs shortest
for a safety alert. An unacknowledged advisory is still accruing.
Workflow
- Validate the advisory: an identifier, a part number, a known severity, an
issue date, and a date-code range given as both ends or neither.
- Resolve applicability for every declared-list entry on part number,
manufacturer and date-code range together.
- Drop the excluded entries. For every remaining entry record whether it is
confirmed or indeterminate and, if indeterminate, what would close it.
- Derive the action each entry earns from severity and stage jointly.
- Choose the supply route from whether the part is still procurable and
whether an approved equivalent already exists.
- Score and order the queue so confirmed matches lead, and band the scores.
- Count the applicability states across the whole list and report the worked
share as an exact pair as well as a fraction.
- Count acknowledgement working days against the severity deadline, build the
dissemination list, and report every finding. The advisory closes only when
nothing is outstanding and an acknowledgement date exists.
Pitfalls
- Reading a missing field as an exclusion. An entry that records no
manufacturer has not been shown to be a second source; it has been shown to
be untraceable, and it is worked as affected until that changes.
- Recording an entry as indeterminate and stopping there. The assessment owes
the evidence that would decide it, or nothing ever closes.
- Letting indeterminate entries flood the top of the queue. They are worked,
but a confirmed match at the same severity and stage is worked first.
- Deriving the action from the stage alone. An alert and a safety alert part
company exactly at installed hardware, where one assesses the application
and the other removes the part.
- Purging stock on an obsolete part. Where the part can no longer be bought
there is no stock to purge into, and the response that actually exists is a
design change.
- Comparing date codes as strings. A four-digit code is a year and a week, and
it is compared as that ordered pair against both ends of the window.
- Accepting a date-code range with only one end given. A half-specified window
silently matches everything or nothing.
- Answering the advisory on the programme that received it and leaving the
sister programmes holding the same selection unwarned.
Behavior contract (gate 3)
The advisory validation, date-code parsing and range comparison, three-valued
applicability resolution, closing-evidence derivation, severity-and-stage
action lookup, supply-route selection, queue scoring and banding, exposure
counting and acknowledgement working-day comparison are exercised by the gate
3 contract test: scripts/test_q60_class_3_alert_handling.py against
scripts/q60_class_3_alert_handling_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q60_class_3_alert_handling.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q60-class-3-alert-handling3description: "Assess an alert, errata sheet or manufacturer advisory against the class 3 EEE parts a programme has already selected, under ECSS-Q-ST-60C clause 6.5.3: resolve each declared-list entry on part number, manufacturer and date-code range together and let the answer stay three valued, work an entry the records cannot rule out as affected while naming the evidence that would close it, derive the action from severity and procurement stage jointly, move the response into the design where the part can no longer be bought, rank the queue, and count acknowledgement working days. Use when an advisory lands on a selected class 3 part. Trigger: ecss, q-st-60c-clause-6-5-3, class-3-eee-advisory, class-3-indeterminate-applicability, class-3-obsolescence-response-route, class-3-advisory-queue-ranking, class-3-advisory-acknowledgement-deadline."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/q60-class-3-alert-handling15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-60-eee-scope, q60-class-3-alert-handling, class-3-eee-advisory, class-3-indeterminate-applicability, class-3-obsolescence-response-route, class-3-advisory-queue-ranking, class-3-advisory-acknowledgement-deadline]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS EEE Components — Class 3 Alert and Advisory Handling (space-systems/ecss/q60-class-3-alert-handling)2324Use when the task is the clause 6.5.3 step of ECSS-Q-ST-60C: an alert, an25errata sheet or a manufacturer advisory has landed on a part the programme26already selected at the lowest assurance class, and the question is which of27the parts on the declared list it actually reaches, what that earns, and by28when. The hard part at this class is not the action. It is that the records29frequently cannot say whether the advisory reaches a given entry at all.3031## Domain quick reference3233- Applicability is three valued here, not two. The part number decides first34 and a different one excludes the entry outright. After that a named35 manufacturer or a named date-code range can exclude an entry only when the36 entry records that same field. Where it records nothing, the answer is37 indeterminate, because the records cannot rule the entry out.38- An indeterminate entry is worked as if it applied. That is the safe default39 and, at this class, the common one. What the assessment owes alongside it is40 the specific evidence that would decide it: a goods-in record naming the41 actual manufacturer, or a label record carrying the delivered date code.42- Indeterminate is not the same as urgent. It is worked, but it sits just43 under a confirmed match at the same severity and stage, so a queue never44 puts an unproven entry ahead of a proven one.45- The action comes from severity and procurement stage together. The same46 alert reselects a part still only on paper, holds an order, quarantines47 stock, recalls a kit, or reaches the customer, depending on how far the48 entry had travelled when the advisory arrived.49- Availability decides where the response can be built at all. A part still50 on the market with an approved equivalent is answered from stock; without51 one it earns a last-time buy with added screening; and a part that can no52 longer be bought cannot be answered by procurement, so anything above an53 information notice moves the response into the design.54- One advisory rarely touches one programme. The same commercial part number55 usually sits on several declared lists, and the advisory is fanned out to56 every programme holding it.57- The acknowledgement clock runs in working days from issue and runs shortest58 for a safety alert. An unacknowledged advisory is still accruing.5960## Workflow61621. Validate the advisory: an identifier, a part number, a known severity, an63 issue date, and a date-code range given as both ends or neither.642. Resolve applicability for every declared-list entry on part number,65 manufacturer and date-code range together.663. Drop the excluded entries. For every remaining entry record whether it is67 confirmed or indeterminate and, if indeterminate, what would close it.684. Derive the action each entry earns from severity and stage jointly.695. Choose the supply route from whether the part is still procurable and70 whether an approved equivalent already exists.716. Score and order the queue so confirmed matches lead, and band the scores.727. Count the applicability states across the whole list and report the worked73 share as an exact pair as well as a fraction.748. Count acknowledgement working days against the severity deadline, build the75 dissemination list, and report every finding. The advisory closes only when76 nothing is outstanding and an acknowledgement date exists.7778## Pitfalls7980- Reading a missing field as an exclusion. An entry that records no81 manufacturer has not been shown to be a second source; it has been shown to82 be untraceable, and it is worked as affected until that changes.83- Recording an entry as indeterminate and stopping there. The assessment owes84 the evidence that would decide it, or nothing ever closes.85- Letting indeterminate entries flood the top of the queue. They are worked,86 but a confirmed match at the same severity and stage is worked first.87- Deriving the action from the stage alone. An alert and a safety alert part88 company exactly at installed hardware, where one assesses the application89 and the other removes the part.90- Purging stock on an obsolete part. Where the part can no longer be bought91 there is no stock to purge into, and the response that actually exists is a92 design change.93- Comparing date codes as strings. A four-digit code is a year and a week, and94 it is compared as that ordered pair against both ends of the window.95- Accepting a date-code range with only one end given. A half-specified window96 silently matches everything or nothing.97- Answering the advisory on the programme that received it and leaving the98 sister programmes holding the same selection unwarned.99100## Behavior contract (gate 3)101102The advisory validation, date-code parsing and range comparison, three-valued103applicability resolution, closing-evidence derivation, severity-and-stage104action lookup, supply-route selection, queue scoring and banding, exposure105counting and acknowledgement working-day comparison are exercised by the gate1063 contract test: scripts/test_q60_class_3_alert_handling.py against107scripts/q60_class_3_alert_handling_logic.py (stdlib unittest, offline). Run:108python3 scripts/test_q60_class_3_alert_handling.py109110## Compliance111112- ECSS standards are freely downloadable (ESA); cite the source and113 paraphrase per standards-map.yaml.114- compliance: STANDARDS-REF, gated: false.