ECSS Operations Design Ergonomics — §4.6.7 (space-systems/ecss/e1011-ops-ergo)
Use when the task is the operations design ergonomics assessment required
by ECSS-E-ST-10C §4.6.7 -- evaluating operational procedures for
cognitive complexity, allocating functions to the correct automation
level based on response-time and consequence constraints, and verifying
that safety-critical commands are protected by an adequate number of
independent inhibit actions before the operations documentation is
finalised.
Domain quick reference
- §4.6.7 addresses three interlocking design concerns: procedure
structure, automation allocation, and error tolerance. All three must
be assessed before an operations design is considered ergonomically
adequate.
- A procedure is compliant when its total step count does not exceed the
recommended limit (15 steps), no single step carries more than three
decision branches, and every time-critical step has an associated
verification action confirming the step was effective. Procedures
exceeding 15 steps are split into sub-procedures; steps with more than
three decision branches are restructured or delegated to a decision
table. The step-count and branch-density limits reflect the cognitive
load threshold above which operator error rates increase materially.
- Each operational function is categorized into one of three automation
levels: manual (operator initiates and monitors without automated
support), supervised (automation executes under operator oversight with
the ability to intervene), or automated (the system acts without
operator input in the execution loop). The minimum acceptable level is
determined by the function's required response time and the severity of
the consequence if it is executed incorrectly. Functions with a
required response time below 2 s cannot be reliably performed by an
operator and must be automated; functions requiring response within 10 s
must be at least supervised; functions with catastrophic-severity
consequences must be at minimum supervised regardless of response time.
- Error tolerance requires that a safety-critical command not be
executable by a single inadvertent operator action. A minimum of two
independent inhibit actions must be present; each inhibit is a
separately intentional step (e.g. mode select, interlock release, arm)
that cannot be triggered by a single slip. The inhibit count is checked
per command before the command interface design is frozen.
Workflow
- Collect all operational procedures and, for each, list the steps with
their decision-branch count, time-criticality flag, and verification
action status. Reject procedures where step or branch data is missing
before assessing them.
- Evaluate each procedure: flag a step count above 15, flag any step
with more than three decision branches, and flag every time-critical
step that lacks a verification action. Record each finding against the
procedure and step identifier.
- Collect every operational function and its automation allocation
proposal. For each function, record the required response time and the
worst-case consequence category (low, medium, high, catastrophic).
Derive the minimum acceptable automation level from the response-time
and consequence rules. Flag any proposed level that is below the
minimum and record the gap.
- Collect every safety-critical command and its inhibit count (number of
independent inhibit actions). Flag any command whose inhibit count is
below two. Raise an error if a negative inhibit count is recorded --
that is a data entry error, not a design choice.
- Aggregate the procedure, automation, and error-tolerance findings into
the review. The operations design is ergonomically adequate only when
all three finding lists are empty.
Pitfalls
- Splitting a long procedure only in documentation without verifying the
sub-procedures individually: each sub-procedure must independently
satisfy the 15-step limit and the branch-density constraint.
- Treating supervised automation as equivalent to manual with a confirm
button: supervised level requires that the automation execute the
action and the operator have genuine authority to halt or override, not
merely that a dialog box appear.
- Setting the consequence category to the nominal outcome rather than the
worst-case failure outcome: the allocation rule applies to the worst
plausible outcome of incorrect execution, not the intended outcome of
correct execution.
- Counting all inhibits as independent when some share the same physical
path or mode: two inhibits on the same relay or within the same command
string count as one for the purpose of the error-tolerance check.
- Reading a missing verification action as implicitly present: if no
explicit verification step is listed for a time-critical procedure
step, it is flagged as absent.
Behavior contract (gate 3)
The procedure assessment, automation allocation, and error-tolerance
inhibit logic is exercised by the gate 3 contract test:
scripts/test_e1011_ops_ergo.py against
scripts/e1011_ops_ergo_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_ops_ergo.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-ops-ergo3description: "Use when assess spacecraft operations design ergonomics under ECSS-E-ST-10C §4.6.7: evaluate each operational procedure for step-count limits, decision-branch density, and time-critical verification coverage; determine the automation level for each function given its response-time requirement and consequence severity; and verify that safety-critical commands carry sufficient independent inhibit actions. Each function is categorized into manual, supervised, or automated allocation and each finding is raised before operations documentation is finalised. Trigger: ecss, e-st-10-system-scope, operations-ergonomics, automation-allocation, error-tolerance, procedures, human-factors."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-ops-ergo15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, operations-ergonomics, automation-allocation, error-tolerance, procedures, human-factors]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Operations Design Ergonomics — §4.6.7 (space-systems/ecss/e1011-ops-ergo)2324Use when the task is the operations design ergonomics assessment required25by ECSS-E-ST-10C §4.6.7 -- evaluating operational procedures for26cognitive complexity, allocating functions to the correct automation27level based on response-time and consequence constraints, and verifying28that safety-critical commands are protected by an adequate number of29independent inhibit actions before the operations documentation is30finalised.3132## Domain quick reference3334- §4.6.7 addresses three interlocking design concerns: procedure35 structure, automation allocation, and error tolerance. All three must36 be assessed before an operations design is considered ergonomically37 adequate.38- A procedure is compliant when its total step count does not exceed the39 recommended limit (15 steps), no single step carries more than three40 decision branches, and every time-critical step has an associated41 verification action confirming the step was effective. Procedures42 exceeding 15 steps are split into sub-procedures; steps with more than43 three decision branches are restructured or delegated to a decision44 table. The step-count and branch-density limits reflect the cognitive45 load threshold above which operator error rates increase materially.46- Each operational function is categorized into one of three automation47 levels: manual (operator initiates and monitors without automated48 support), supervised (automation executes under operator oversight with49 the ability to intervene), or automated (the system acts without50 operator input in the execution loop). The minimum acceptable level is51 determined by the function's required response time and the severity of52 the consequence if it is executed incorrectly. Functions with a53 required response time below 2 s cannot be reliably performed by an54 operator and must be automated; functions requiring response within 10 s55 must be at least supervised; functions with catastrophic-severity56 consequences must be at minimum supervised regardless of response time.57- Error tolerance requires that a safety-critical command not be58 executable by a single inadvertent operator action. A minimum of two59 independent inhibit actions must be present; each inhibit is a60 separately intentional step (e.g. mode select, interlock release, arm)61 that cannot be triggered by a single slip. The inhibit count is checked62 per command before the command interface design is frozen.6364## Workflow65661. Collect all operational procedures and, for each, list the steps with67 their decision-branch count, time-criticality flag, and verification68 action status. Reject procedures where step or branch data is missing69 before assessing them.702. Evaluate each procedure: flag a step count above 15, flag any step71 with more than three decision branches, and flag every time-critical72 step that lacks a verification action. Record each finding against the73 procedure and step identifier.743. Collect every operational function and its automation allocation75 proposal. For each function, record the required response time and the76 worst-case consequence category (low, medium, high, catastrophic).77 Derive the minimum acceptable automation level from the response-time78 and consequence rules. Flag any proposed level that is below the79 minimum and record the gap.804. Collect every safety-critical command and its inhibit count (number of81 independent inhibit actions). Flag any command whose inhibit count is82 below two. Raise an error if a negative inhibit count is recorded --83 that is a data entry error, not a design choice.845. Aggregate the procedure, automation, and error-tolerance findings into85 the review. The operations design is ergonomically adequate only when86 all three finding lists are empty.8788## Pitfalls8990- Splitting a long procedure only in documentation without verifying the91 sub-procedures individually: each sub-procedure must independently92 satisfy the 15-step limit and the branch-density constraint.93- Treating supervised automation as equivalent to manual with a confirm94 button: supervised level requires that the automation execute the95 action and the operator have genuine authority to halt or override, not96 merely that a dialog box appear.97- Setting the consequence category to the nominal outcome rather than the98 worst-case failure outcome: the allocation rule applies to the worst99 plausible outcome of incorrect execution, not the intended outcome of100 correct execution.101- Counting all inhibits as independent when some share the same physical102 path or mode: two inhibits on the same relay or within the same command103 string count as one for the purpose of the error-tolerance check.104- Reading a missing verification action as implicitly present: if no105 explicit verification step is listed for a time-critical procedure106 step, it is flagged as absent.107108## Behavior contract (gate 3)109110The procedure assessment, automation allocation, and error-tolerance111inhibit logic is exercised by the gate 3 contract test:112scripts/test_e1011_ops_ergo.py against113scripts/e1011_ops_ergo_logic.py (stdlib unittest, offline). Run:114python3 scripts/test_e1011_ops_ergo.py115116## Compliance117118- ECSS standards are freely downloadable (ESA); cite the source and119 paraphrase per standards-map.yaml.120- compliance: STANDARDS-REF, gated: false.