ECSS Systems Engineering — Continuous Assessment Process (space-systems/ecss/e1011-assessment-process)
Use when the task is to run the continuous assessment process defined in
ECSS-E-ST-10 clause 4.10.1 — categorizing findings from review events,
evaluating technical performance measures (TPMs) against their threshold
bands, tracking finding closure, and producing the structured Annex C
assessment-report fields.
Domain quick reference
- Clause 4.10.1 establishes assessment as an ongoing activity that runs at
every major review event across all project phases (Phase 0 through F).
At each event the responsible engineer gathers findings and TPM readings,
evaluates them against criteria, and records the outcome in the Annex C
report format.
- Findings are categorized into exactly one of three types before they
enter the tracking register:
- observation — a noted deviation or potential risk that does not
mandate a corrective action on its own but must be recorded and
monitored;
- action item — a directed task that must be completed and closed
before the project can advance past the associated milestone;
- non-conformance — a verified departure from a stated requirement;
a non-conformance that remains open drives the overall assessment
status to non-compliant.
- TPMs are the quantitative indicators chosen to track achievement of
critical technical requirements (e.g., total system mass, power margin,
link budget margin). Each TPM is evaluated against a threshold boundary
(maximum or minimum permitted value). A reading within 10 % of the
boundary is marginal; beyond it is exceeded. An exceeded TPM drives the
status to at-risk.
- The Annex C report is the normative output format; its required fields
are: record identifier, event name and date, project phase, scope
description, finding counts by status (open/closed/waived), the open
finding identifiers, the TPM status per measure, and the single overall
status derived from combining finding and measure outcomes.
Workflow
- At the start of each review event, assign a unique record identifier
and record the event name, date (YYYY-MM-DD), project phase, and scope
description. Reject any record with an empty identifier, name, or
scope, or with a date that does not conform to ISO 8601.
- Inventory every finding raised during or since the previous event.
For each finding, confirm its type is one of observation / action_item /
non_conformance (reject any unrecognised type before it enters the
register). Record the responsible party; a finding with no responsible
party cannot be tracked to closure.
- For each finding whose status is "closed" or "waived", verify closure
validity: the finding must have a non-empty identifier, a description,
and a responsible party; a waived finding additionally requires a
documented rationale. Flag any gap as a structural defect in the
record.
- Collect the current reading for every TPM in scope. For each TPM,
determine whether the reading is nominal (comfortably within the
threshold), marginal (within 10 % of the threshold boundary), or
exceeded (beyond the boundary), using the max/min threshold type
appropriate to that measure.
- Derive the overall assessment status by applying the priority rules:
- non_compliant if any non-conformance finding is open;
- at_risk if any TPM is exceeded, or if any action item is open
(and no open non-conformance exists);
- marginal if any TPM is marginal (and no higher-priority condition
applies);
- compliant if all findings are closed or waived and all TPMs are
nominal.
- Populate the Annex C report fields. Confirm that the count of
measure-status entries matches the count of measures in the record;
a mismatch is a structural error. Deliver the report dict for
archiving or onward review.
Pitfalls
- Treating a finding with no responsible party as "open but trackable" —
an unowned finding cannot be driven to closure and represents a gap in
the assessment governance, not a routine open item.
- Collapsing marginal and exceeded TPMs into a single "at-risk" label and
losing the distinction — marginal allows the project to proceed with
monitoring, whereas exceeded triggers active corrective measures; the
two must remain separate in the register.
- Leaving a waived finding's rationale blank and recording the status as
waived — a waiver without documented rationale has the same evidential
weight as no decision at all; the record must be rejected until the
rationale is supplied.
- Skipping the structural validation step and populating Annex C fields
directly — validation gates catch empty identifiers, malformed dates,
unrecognised types, and mismatched measure counts before they propagate
into the archived report.
- Treating "no findings" as automatically "compliant" — the overall status
is compliant only when both the finding register and the TPM set are
explicitly clear; a record with no measures defined cannot confirm TPM
health.
Behavior contract (gate 3)
The finding-categorization, TPM-evaluation, closure-validity, overall-
status, Annex-C generation, and record-validation logic is exercised by
the gate 3 contract test:
scripts/test_e1011_assessment_process.py against
scripts/e1011_assessment_process_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_assessment_process.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1011-assessment-process3description: "Use when run the continuous assessment process for a space system project under ECSS-E-ST-10 clause 4.10.1: categorize each finding by type (observation, action item, non-conformance), evaluate technical performance measures against their thresholds to derive a nominal/marginal/exceeded status, determine closure validity for each finding, compute the overall compliance status across all open findings and measure outcomes, and generate the structured Annex C assessment-report fields. The process applies at every review event across all project phases; open non-conformances and exceeded thresholds both block a compliant outcome. Trigger: ecss, e-st-10-system-scope, continuous-assessment, technical-performance-measure, finding-categorization, review-event, annex-c-report, compliance-status."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/e1011-assessment-process15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, continuous-assessment, technical-performance-measure, finding-categorization, review-event, annex-c-report, compliance-status]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Systems Engineering — Continuous Assessment Process (space-systems/ecss/e1011-assessment-process)2324Use when the task is to run the continuous assessment process defined in25ECSS-E-ST-10 clause 4.10.1 — categorizing findings from review events,26evaluating technical performance measures (TPMs) against their threshold27bands, tracking finding closure, and producing the structured Annex C28assessment-report fields.2930## Domain quick reference3132- Clause 4.10.1 establishes assessment as an ongoing activity that runs at33 every major review event across all project phases (Phase 0 through F).34 At each event the responsible engineer gathers findings and TPM readings,35 evaluates them against criteria, and records the outcome in the Annex C36 report format.37- Findings are categorized into exactly one of three types before they38 enter the tracking register:39 - **observation** — a noted deviation or potential risk that does not40 mandate a corrective action on its own but must be recorded and41 monitored;42 - **action item** — a directed task that must be completed and closed43 before the project can advance past the associated milestone;44 - **non-conformance** — a verified departure from a stated requirement;45 a non-conformance that remains open drives the overall assessment46 status to non-compliant.47- TPMs are the quantitative indicators chosen to track achievement of48 critical technical requirements (e.g., total system mass, power margin,49 link budget margin). Each TPM is evaluated against a threshold boundary50 (maximum or minimum permitted value). A reading within 10 % of the51 boundary is marginal; beyond it is exceeded. An exceeded TPM drives the52 status to at-risk.53- The Annex C report is the normative output format; its required fields54 are: record identifier, event name and date, project phase, scope55 description, finding counts by status (open/closed/waived), the open56 finding identifiers, the TPM status per measure, and the single overall57 status derived from combining finding and measure outcomes.5859## Workflow60611. At the start of each review event, assign a unique record identifier62 and record the event name, date (YYYY-MM-DD), project phase, and scope63 description. Reject any record with an empty identifier, name, or64 scope, or with a date that does not conform to ISO 8601.652. Inventory every finding raised during or since the previous event.66 For each finding, confirm its type is one of observation / action_item /67 non_conformance (reject any unrecognised type before it enters the68 register). Record the responsible party; a finding with no responsible69 party cannot be tracked to closure.703. For each finding whose status is "closed" or "waived", verify closure71 validity: the finding must have a non-empty identifier, a description,72 and a responsible party; a waived finding additionally requires a73 documented rationale. Flag any gap as a structural defect in the74 record.754. Collect the current reading for every TPM in scope. For each TPM,76 determine whether the reading is nominal (comfortably within the77 threshold), marginal (within 10 % of the threshold boundary), or78 exceeded (beyond the boundary), using the max/min threshold type79 appropriate to that measure.805. Derive the overall assessment status by applying the priority rules:81 - **non_compliant** if any non-conformance finding is open;82 - **at_risk** if any TPM is exceeded, or if any action item is open83 (and no open non-conformance exists);84 - **marginal** if any TPM is marginal (and no higher-priority condition85 applies);86 - **compliant** if all findings are closed or waived and all TPMs are87 nominal.886. Populate the Annex C report fields. Confirm that the count of89 measure-status entries matches the count of measures in the record;90 a mismatch is a structural error. Deliver the report dict for91 archiving or onward review.9293## Pitfalls9495- Treating a finding with no responsible party as "open but trackable" —96 an unowned finding cannot be driven to closure and represents a gap in97 the assessment governance, not a routine open item.98- Collapsing marginal and exceeded TPMs into a single "at-risk" label and99 losing the distinction — marginal allows the project to proceed with100 monitoring, whereas exceeded triggers active corrective measures; the101 two must remain separate in the register.102- Leaving a waived finding's rationale blank and recording the status as103 waived — a waiver without documented rationale has the same evidential104 weight as no decision at all; the record must be rejected until the105 rationale is supplied.106- Skipping the structural validation step and populating Annex C fields107 directly — validation gates catch empty identifiers, malformed dates,108 unrecognised types, and mismatched measure counts before they propagate109 into the archived report.110- Treating "no findings" as automatically "compliant" — the overall status111 is compliant only when both the finding register and the TPM set are112 explicitly clear; a record with no measures defined cannot confirm TPM113 health.114115## Behavior contract (gate 3)116117The finding-categorization, TPM-evaluation, closure-validity, overall-118status, Annex-C generation, and record-validation logic is exercised by119the gate 3 contract test:120scripts/test_e1011_assessment_process.py against121scripts/e1011_assessment_process_logic.py (stdlib unittest, offline). Run:122123```124python3 scripts/test_e1011_assessment_process.py125```126127## Compliance128129- ECSS standards are freely downloadable (ESA); cite the source and130 paraphrase per standards-map.yaml.131- compliance: STANDARDS-REF, gated: false.