ECSS HFE — On-Board Informatics Support (space-systems/ecss/e1011-informatics)
Use when the task is evaluation of informatics support for a crewed space
workstation per ECSS-E-ST-10-11C §4.8 — checking display element types,
alert urgency tiers, display legibility, and automation authority against
the HFE requirements for on-board data systems, software interfaces, and
crew-automation interaction.
Domain quick reference
- §4.8 groups display elements into five functional types: numerical
readouts (measured or computed values), graphical trend and map
displays, status_text indicators (mode, state, label), alert
indicators (crew-attention demands), and control elements (input
widgets). An element must be placed in exactly one type before its
legibility is assessed.
- Alert urgency is tiered into three levels. A warning demands
immediate crew action and applies when hazard severity is high and
corrective action must begin within seconds. A caution requires
timely action (minutes available) and covers high-to-medium severity
situations not demanding split-second response. An advisory covers
all remaining combinations where crew awareness is needed but no
time-critical action is required. The declared tier on any alert
indicator must match the outcome of this hazard-severity ×
time-criticality mapping.
- Display legibility is governed by two minimum thresholds: luminance
contrast ratio (text or symbol against background, minimum 4.5) and
character height (minimum 3.5 mm at design viewing distance up to
700 mm). Both must be satisfied; failing either is a format violation.
- Automation authority is assigned one of four levels: advisory
(system informs, crew decides and acts), shared_control (crew and
system jointly execute), supervisory (crew sets goals, system
executes steps), autonomous (system acts without crew input). At
supervisory and autonomous levels the crew must retain a documented
override capability; its absence is an authority violation.
Workflow
- Inventory every display element on the workstation and categorize each
one into numerical, graphical, status_text, alert, or control. Reject
any element whose type is not in the recognized set before assessment
continues.
- For each alert element, determine the required urgency tier by mapping
the associated hazard severity (low / medium / high) against the
time criticality for corrective action (seconds / minutes / hours /
none). Compare the required tier against the declared tier; flag a
mismatch if they differ.
- Check every display element for legibility: compute or obtain the
luminance contrast ratio and the character height at design viewing
distance. Flag the element when either falls below its minimum
threshold (contrast ratio < 4.5, character height < 3.5 mm).
- For each automation function on the workstation, record its authority
level. Confirm that supervisory and autonomous functions carry a
documented crew override capability; flag each that does not.
- Aggregate the format violations, alert tier mismatches, and automation
violations per workstation. The workstation is not informatics-compliant
under §4.8 until all three lists are empty.
Pitfalls
- Assigning a caution tier to a high-severity situation that demands
action within seconds — the warning tier exists precisely for this
case and its omission leaves the crew with insufficient urgency cuing.
- Treating contrast ratio and character height as alternatives: both
thresholds are independent minima and a display that passes one can
still fail the other.
- Allowing advisory or shared_control automation functions to inherit the
crew-override requirement from higher authority levels — override is
mandatory only at supervisory and autonomous levels; adding it elsewhere
creates unnecessary interface complexity without safety benefit.
- Proceeding with the alert tier check before confirming that the element
type is recognized — an alert indicator on an unknown element type means
the hazard mapping has not been scoped to a defined function and the
tier assignment is unvalidated.
Behavior contract (gate 3)
The display element type check, alert urgency determination, display
format compliance, automation authority assessment, and workstation
aggregation logic is exercised by the gate 3 contract test:
scripts/test_e1011_informatics.py against
scripts/e1011_informatics_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_informatics.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-informatics3description: "Use when evaluate on-board informatics support for a crewed space system under ECSS-E-ST-10-11C §4.8: categorize each display element as numerical, graphical, status_text, alert, or control; determine alert urgency level from hazard severity and time criticality; check display format compliance against minimum contrast ratio and character height thresholds; and assess automation authority to confirm crew override is available for supervisory and autonomous operating modes. Flag every display format shortfall, alert level mismatch, and missing crew override before the workstation is accepted. Trigger: ecss, e-st-10-11c, informatics, hfe, display-design, alerts, automation-authority, crew-interface, workstation-review."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-informatics15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-11c, informatics, hfe, display-design, alerts, automation-authority, crew-interface]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS HFE — On-Board Informatics Support (space-systems/ecss/e1011-informatics)2324Use when the task is evaluation of informatics support for a crewed space25workstation per ECSS-E-ST-10-11C §4.8 — checking display element types,26alert urgency tiers, display legibility, and automation authority against27the HFE requirements for on-board data systems, software interfaces, and28crew-automation interaction.2930## Domain quick reference3132- §4.8 groups display elements into five functional types: **numerical**33 readouts (measured or computed values), **graphical** trend and map34 displays, **status_text** indicators (mode, state, label), **alert**35 indicators (crew-attention demands), and **control** elements (input36 widgets). An element must be placed in exactly one type before its37 legibility is assessed.38- Alert urgency is tiered into three levels. A **warning** demands39 immediate crew action and applies when hazard severity is high and40 corrective action must begin within seconds. A **caution** requires41 timely action (minutes available) and covers high-to-medium severity42 situations not demanding split-second response. An **advisory** covers43 all remaining combinations where crew awareness is needed but no44 time-critical action is required. The declared tier on any alert45 indicator must match the outcome of this hazard-severity ×46 time-criticality mapping.47- Display legibility is governed by two minimum thresholds: luminance48 contrast ratio (text or symbol against background, minimum 4.5) and49 character height (minimum 3.5 mm at design viewing distance up to50 700 mm). Both must be satisfied; failing either is a format violation.51- Automation authority is assigned one of four levels: **advisory**52 (system informs, crew decides and acts), **shared_control** (crew and53 system jointly execute), **supervisory** (crew sets goals, system54 executes steps), **autonomous** (system acts without crew input). At55 supervisory and autonomous levels the crew must retain a documented56 override capability; its absence is an authority violation.5758## Workflow59601. Inventory every display element on the workstation and categorize each61 one into numerical, graphical, status_text, alert, or control. Reject62 any element whose type is not in the recognized set before assessment63 continues.642. For each alert element, determine the required urgency tier by mapping65 the associated hazard severity (low / medium / high) against the66 time criticality for corrective action (seconds / minutes / hours /67 none). Compare the required tier against the declared tier; flag a68 mismatch if they differ.693. Check every display element for legibility: compute or obtain the70 luminance contrast ratio and the character height at design viewing71 distance. Flag the element when either falls below its minimum72 threshold (contrast ratio < 4.5, character height < 3.5 mm).734. For each automation function on the workstation, record its authority74 level. Confirm that supervisory and autonomous functions carry a75 documented crew override capability; flag each that does not.765. Aggregate the format violations, alert tier mismatches, and automation77 violations per workstation. The workstation is not informatics-compliant78 under §4.8 until all three lists are empty.7980## Pitfalls8182- Assigning a caution tier to a high-severity situation that demands83 action within seconds — the warning tier exists precisely for this84 case and its omission leaves the crew with insufficient urgency cuing.85- Treating contrast ratio and character height as alternatives: both86 thresholds are independent minima and a display that passes one can87 still fail the other.88- Allowing advisory or shared_control automation functions to inherit the89 crew-override requirement from higher authority levels — override is90 mandatory only at supervisory and autonomous levels; adding it elsewhere91 creates unnecessary interface complexity without safety benefit.92- Proceeding with the alert tier check before confirming that the element93 type is recognized — an alert indicator on an unknown element type means94 the hazard mapping has not been scoped to a defined function and the95 tier assignment is unvalidated.9697## Behavior contract (gate 3)9899The display element type check, alert urgency determination, display100format compliance, automation authority assessment, and workstation101aggregation logic is exercised by the gate 3 contract test:102scripts/test_e1011_informatics.py against103scripts/e1011_informatics_logic.py (stdlib unittest, offline). Run:104python3 scripts/test_e1011_informatics.py105106## Compliance107108- ECSS standards are freely downloadable (ESA); cite the source and109 paraphrase per standards-map.yaml.110- compliance: STANDARDS-REF, gated: false.