ECSS Human Factors Engineering — Operations Timeline (space-systems/ecss/e1011-timeline)
Use when build the operations timeline for a human-rated space system per
ECSS-E-ST-10-11C §4.9.3 -- sequencing crew tasks in a phased timeline,
computing the hourly workload index for each assessment window, checking
every window against the maximum allowable workload level, verifying
mandatory rest gaps between high-demand clusters, and confirming concurrent
task counts remain within the HFE cognitive limit.
Domain quick reference
- Each crew activity in the mission phase is assigned a task ID, start
time (minutes from the phase epoch), duration, and one of three workload
levels: low (routine monitoring), medium (active procedure execution), or
high (emergency response or complex multi-step operations). Workload level
maps to a numeric value (low = 1, medium = 2, high = 3) used in index
computation. An unrecognized level is a structural error that must be
resolved before workload analysis proceeds.
- The time-averaged workload index for an assessment window is the sum of
(workload_value × fraction_of_window_occupied) for all tasks active within
that window. A window is typically one crew-hour. The index must not exceed
the maximum allowable value (equivalent to one sustained high-level task)
in any window; two concurrent high-level tasks push the index to 6, which
always violates the limit.
- The concurrent task count at any instant must not exceed the cognitive
limit drawn from the HFE requirement (typically three simultaneous tasks
per crew member). The check fires at every task start and end event, not
just at window boundaries; off-boundary violations are a common miss.
- After any cluster of consecutive high-demand assessment windows (index
exceeding the high-demand threshold), a minimum rest gap must separate
that cluster from the next. The gap is measured from the end of the last
high-demand window in the first cluster to the start of the first
high-demand window in the next cluster. A crew changeover or short
procedure break shorter than the minimum does not satisfy the rest
requirement.
Workflow
- Collect all crew tasks for the mission phase. For each task record: a
unique task ID, a short description, start time in minutes from the phase
epoch (non-negative integer), duration in minutes (positive integer),
workload level (low / medium / high), and required crew count (≥ 1).
Reject any task entry that fails these structural checks before proceeding
to workload analysis.
- Slide a one-hour assessment window across the full timeline span in
60-minute steps. For each window compute the time-averaged workload index
(sum of workload_value × overlap_minutes for all tasks in the window,
divided by window duration in minutes). Flag any window where the index
exceeds the maximum allowable workload level.
- Perform an event-sweep at every task start and end instant. Maintain an
active-task count: increment on task start, decrement on task end. When
a task starts, if the resulting count exceeds the cognitive limit, record
a concurrent-task violation. Tasks ending and tasks starting at the same
minute are ordered so ends are processed before starts, preventing a
spurious violation when one task replaces another exactly.
- Identify all high-demand windows (index exceeds the high-demand
threshold) and group consecutive windows into clusters. For each pair of
adjacent clusters measure the inter-cluster gap in minutes. Flag any gap
shorter than the minimum required rest duration.
- Aggregate all findings from steps 1 through 4. The timeline is
workload-compliant only when all three finding lists are empty:
structural errors, workload exceedances, concurrent-task violations, and
rest-gap shortfalls.
Pitfalls
- Applying task workload values as peak loads rather than time-weighted
contributions — a high-level task occupying only half a window contributes
index 1.5, not 3.0; sum the weighted products, do not take the window
maximum.
- Treating a gap between tasks as a rest period without verifying its
duration meets the minimum — procedure transitions and tool changeovers
are not rest periods and must not be counted toward the rest requirement.
- Omitting low-workload tasks from the timeline on the assumption they have
no effect — even low-level tasks accumulate when many are concurrent; a
cluster of three simultaneous low-level tasks produces an index of 3,
equal to one sustained high-level task, and all three count against the
concurrent-task limit.
- Checking concurrent-task count only at window boundaries and missing
intra-window spikes — the event-sweep must fire at each exact task
start/end minute to catch violations that open and close within a window.
Behavior contract (gate 3)
The task-entry validation, workload-index computation, concurrent-task
event-sweep, and rest-gap cluster check are exercised by the gate 3
contract test: scripts/test_e1011_timeline.py against
scripts/e1011_timeline_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_timeline.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-timeline3description: "Use when build the operations timeline for a human-rated space system per ECSS-E-ST-10-11C §4.9.3: sequence each crew task in a phased timeline, compute the time-averaged workload index for each hourly assessment window, verify no window exceeds the maximum allowable workload level, confirm mandatory rest gaps are preserved between consecutive high-demand activity clusters, and check that concurrent task counts remain within the cognitive limit specified by the HFE requirement. Trigger: ecss, e-st-10-system-scope, operations-timeline, crew-workload, workload-index, human-factors, task-sequencing, rest-period, concurrent-tasks."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-timeline15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, operations-timeline, crew-workload, workload-index, human-factors, task-sequencing, rest-period, concurrent-tasks]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Human Factors Engineering — Operations Timeline (space-systems/ecss/e1011-timeline)2324Use when build the operations timeline for a human-rated space system per25ECSS-E-ST-10-11C §4.9.3 -- sequencing crew tasks in a phased timeline,26computing the hourly workload index for each assessment window, checking27every window against the maximum allowable workload level, verifying28mandatory rest gaps between high-demand clusters, and confirming concurrent29task counts remain within the HFE cognitive limit.3031## Domain quick reference3233- Each crew activity in the mission phase is assigned a task ID, start34 time (minutes from the phase epoch), duration, and one of three workload35 levels: low (routine monitoring), medium (active procedure execution), or36 high (emergency response or complex multi-step operations). Workload level37 maps to a numeric value (low = 1, medium = 2, high = 3) used in index38 computation. An unrecognized level is a structural error that must be39 resolved before workload analysis proceeds.40- The time-averaged workload index for an assessment window is the sum of41 (workload_value × fraction_of_window_occupied) for all tasks active within42 that window. A window is typically one crew-hour. The index must not exceed43 the maximum allowable value (equivalent to one sustained high-level task)44 in any window; two concurrent high-level tasks push the index to 6, which45 always violates the limit.46- The concurrent task count at any instant must not exceed the cognitive47 limit drawn from the HFE requirement (typically three simultaneous tasks48 per crew member). The check fires at every task start and end event, not49 just at window boundaries; off-boundary violations are a common miss.50- After any cluster of consecutive high-demand assessment windows (index51 exceeding the high-demand threshold), a minimum rest gap must separate52 that cluster from the next. The gap is measured from the end of the last53 high-demand window in the first cluster to the start of the first54 high-demand window in the next cluster. A crew changeover or short55 procedure break shorter than the minimum does not satisfy the rest56 requirement.5758## Workflow59601. Collect all crew tasks for the mission phase. For each task record: a61 unique task ID, a short description, start time in minutes from the phase62 epoch (non-negative integer), duration in minutes (positive integer),63 workload level (low / medium / high), and required crew count (≥ 1).64 Reject any task entry that fails these structural checks before proceeding65 to workload analysis.662. Slide a one-hour assessment window across the full timeline span in67 60-minute steps. For each window compute the time-averaged workload index68 (sum of workload_value × overlap_minutes for all tasks in the window,69 divided by window duration in minutes). Flag any window where the index70 exceeds the maximum allowable workload level.713. Perform an event-sweep at every task start and end instant. Maintain an72 active-task count: increment on task start, decrement on task end. When73 a task starts, if the resulting count exceeds the cognitive limit, record74 a concurrent-task violation. Tasks ending and tasks starting at the same75 minute are ordered so ends are processed before starts, preventing a76 spurious violation when one task replaces another exactly.774. Identify all high-demand windows (index exceeds the high-demand78 threshold) and group consecutive windows into clusters. For each pair of79 adjacent clusters measure the inter-cluster gap in minutes. Flag any gap80 shorter than the minimum required rest duration.815. Aggregate all findings from steps 1 through 4. The timeline is82 workload-compliant only when all three finding lists are empty:83 structural errors, workload exceedances, concurrent-task violations, and84 rest-gap shortfalls.8586## Pitfalls8788- Applying task workload values as peak loads rather than time-weighted89 contributions — a high-level task occupying only half a window contributes90 index 1.5, not 3.0; sum the weighted products, do not take the window91 maximum.92- Treating a gap between tasks as a rest period without verifying its93 duration meets the minimum — procedure transitions and tool changeovers94 are not rest periods and must not be counted toward the rest requirement.95- Omitting low-workload tasks from the timeline on the assumption they have96 no effect — even low-level tasks accumulate when many are concurrent; a97 cluster of three simultaneous low-level tasks produces an index of 3,98 equal to one sustained high-level task, and all three count against the99 concurrent-task limit.100- Checking concurrent-task count only at window boundaries and missing101 intra-window spikes — the event-sweep must fire at each exact task102 start/end minute to catch violations that open and close within a window.103104## Behavior contract (gate 3)105106The task-entry validation, workload-index computation, concurrent-task107event-sweep, and rest-gap cluster check are exercised by the gate 3108contract test: scripts/test_e1011_timeline.py against109scripts/e1011_timeline_logic.py (stdlib unittest, offline). Run:110python3 scripts/test_e1011_timeline.py111112## Compliance113114- ECSS standards are freely downloadable (ESA); cite the source and115 paraphrase per standards-map.yaml.116- compliance: STANDARDS-REF, gated: false.