ECSS Human Factors — Crew Physical Performance and Fatigue (space-systems/ecss/e1011-physical-perf)
Use when the task is to evaluate crew physical workload against the
physical performance and fatigue reference data of ECSS-E-ST-10-11C
§4.5.3 -- categorizing work tasks by metabolic rate, verifying
continuous-work duration limits, computing required recovery periods,
and checking daily accumulated workload against per-category caps.
Domain quick reference
- §4.5.3 maps metabolic rate (W) to five workload bands: REST
(below 65 W), LIGHT (65–174 W), MODERATE (175–294 W),
HEAVY (295–414 W), and VERY HEAVY (415 W and above). Thresholds
derive from ISO 8996 metabolic rate categories adapted for
space-environment crew assessments. Every crew task is placed into
exactly one band before any limit is applied.
- Continuous duration limits cap the uninterrupted work time per band:
LIGHT 480 min, MODERATE 120 min, HEAVY 45 min, VERY HEAVY 20 min.
A REST segment carries no practical continuous limit within a 24-hour
period. Exceeding the continuous limit for a band is a direct
physical-performance violation regardless of recovery state.
- Recovery is proportional to work intensity. The minimum rest period
following a work bout equals a multiplier times the bout duration:
LIGHT 0.25×, MODERATE 0.5×, HEAVY 1.0×, VERY HEAVY 2.0×.
Starting a new work bout before that rest period has elapsed is an
insufficient-recovery violation.
- Daily accumulated workload limits cap the total time in each band
across a full crew-day: LIGHT 480 min, MODERATE 240 min,
HEAVY 120 min, VERY HEAVY 60 min. These limits are independent of
the continuous-duration check; a schedule can pass all continuous
checks and still fail on daily accumulation.
Workflow
- Assign a metabolic rate (W) to every crew task in the schedule.
Reject any task with a negative or missing rate before the
assessment proceeds.
- Categorize each task into its workload band using the metabolic
rate thresholds. A task is placed in exactly one band; borderline
values use the lower-rate band convention (a rate equal to a
threshold is placed in the higher band, consistent with the
half-open interval [lower, upper)).
- For each work bout, compare its duration against the continuous
duration limit for its band. Record a continuous-limit violation
if the bout duration exceeds the limit.
- For each pair of consecutive work bouts, sum the rest time
between them and compare it to the required recovery for the
preceding bout (recovery_ratio × work_duration). Record an
insufficient-recovery violation if the accumulated rest falls short.
- Sum the work durations per band across the full schedule day.
Compare each band total against its daily accumulation limit.
Record a daily-limit violation for every band that is exceeded.
- Aggregate all violations. A schedule is compliant only when the
continuous-limit, insufficient-recovery, and daily-limit violation
lists are all empty.
Pitfalls
- Applying the daily limit check without first running the continuous
and recovery checks -- a schedule that passes daily totals can still
have single bouts that are too long or transitions with too little
rest; all three checks are mandatory.
- Treating the recovery ratio as a fixed number of minutes rather than
a multiple of the preceding work duration -- a 30 min HEAVY bout
requires 30 min of rest, but a 45 min HEAVY bout requires 45 min of
rest; the required rest scales with the bout length.
- Conflating the continuous limit with the daily limit -- a MODERATE
task can legally run for 120 min in a single bout but the crew-day
cap is 240 min; two full 120 min bouts with sufficient recovery
between them exhaust the daily allowance and a third bout (even a
short one) triggers a daily-limit violation.
- Dropping REST segments from the schedule before running the recovery
check -- REST time is what satisfies the recovery requirement; if
REST segments are filtered out early, the preceding-bout recovery
time will appear as zero and every transition will be flagged.
Behavior contract (gate 3)
The categorization, continuous-limit, recovery, and daily-accumulation
logic is exercised by the gate 3 contract test:
scripts/test_e1011_physical_perf.py against
scripts/e1011_physical_perf_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_physical_perf.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-physical-perf3description: "Use when evaluate crew physical performance and fatigue limits under ECSS-E-ST-10-11C §4.5.3: categorize each crew task by metabolic rate band (rest, light, moderate, heavy, or very heavy), check the continuous-work duration against the per-category allowable limit, compute the minimum required recovery period, flag any work bout that exceeds the sustained-performance threshold, and validate a full work-rest schedule against the daily workload accumulation limit for each category. Applicable to IVA and EVA crew scheduling, ergonomic compliance review, and mission-phase workload analysis. Trigger: ecss, e-st-10-system-scope, physical-performance, crew-workload, fatigue, metabolic-rate, work-rest-schedule, human-factors, ergonomics."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-physical-perf15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, physical-performance, crew-workload, fatigue, metabolic-rate, work-rest-schedule, human-factors]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Human Factors — Crew Physical Performance and Fatigue (space-systems/ecss/e1011-physical-perf)2324Use when the task is to evaluate crew physical workload against the25physical performance and fatigue reference data of ECSS-E-ST-10-11C26§4.5.3 -- categorizing work tasks by metabolic rate, verifying27continuous-work duration limits, computing required recovery periods,28and checking daily accumulated workload against per-category caps.2930## Domain quick reference3132- §4.5.3 maps metabolic rate (W) to five workload bands: REST33 (below 65 W), LIGHT (65–174 W), MODERATE (175–294 W),34 HEAVY (295–414 W), and VERY HEAVY (415 W and above). Thresholds35 derive from ISO 8996 metabolic rate categories adapted for36 space-environment crew assessments. Every crew task is placed into37 exactly one band before any limit is applied.38- Continuous duration limits cap the uninterrupted work time per band:39 LIGHT 480 min, MODERATE 120 min, HEAVY 45 min, VERY HEAVY 20 min.40 A REST segment carries no practical continuous limit within a 24-hour41 period. Exceeding the continuous limit for a band is a direct42 physical-performance violation regardless of recovery state.43- Recovery is proportional to work intensity. The minimum rest period44 following a work bout equals a multiplier times the bout duration:45 LIGHT 0.25×, MODERATE 0.5×, HEAVY 1.0×, VERY HEAVY 2.0×.46 Starting a new work bout before that rest period has elapsed is an47 insufficient-recovery violation.48- Daily accumulated workload limits cap the total time in each band49 across a full crew-day: LIGHT 480 min, MODERATE 240 min,50 HEAVY 120 min, VERY HEAVY 60 min. These limits are independent of51 the continuous-duration check; a schedule can pass all continuous52 checks and still fail on daily accumulation.5354## Workflow55561. Assign a metabolic rate (W) to every crew task in the schedule.57 Reject any task with a negative or missing rate before the58 assessment proceeds.592. Categorize each task into its workload band using the metabolic60 rate thresholds. A task is placed in exactly one band; borderline61 values use the lower-rate band convention (a rate equal to a62 threshold is placed in the higher band, consistent with the63 half-open interval [lower, upper)).643. For each work bout, compare its duration against the continuous65 duration limit for its band. Record a continuous-limit violation66 if the bout duration exceeds the limit.674. For each pair of consecutive work bouts, sum the rest time68 between them and compare it to the required recovery for the69 preceding bout (recovery_ratio × work_duration). Record an70 insufficient-recovery violation if the accumulated rest falls short.715. Sum the work durations per band across the full schedule day.72 Compare each band total against its daily accumulation limit.73 Record a daily-limit violation for every band that is exceeded.746. Aggregate all violations. A schedule is compliant only when the75 continuous-limit, insufficient-recovery, and daily-limit violation76 lists are all empty.7778## Pitfalls7980- Applying the daily limit check without first running the continuous81 and recovery checks -- a schedule that passes daily totals can still82 have single bouts that are too long or transitions with too little83 rest; all three checks are mandatory.84- Treating the recovery ratio as a fixed number of minutes rather than85 a multiple of the preceding work duration -- a 30 min HEAVY bout86 requires 30 min of rest, but a 45 min HEAVY bout requires 45 min of87 rest; the required rest scales with the bout length.88- Conflating the continuous limit with the daily limit -- a MODERATE89 task can legally run for 120 min in a single bout but the crew-day90 cap is 240 min; two full 120 min bouts with sufficient recovery91 between them exhaust the daily allowance and a third bout (even a92 short one) triggers a daily-limit violation.93- Dropping REST segments from the schedule before running the recovery94 check -- REST time is what satisfies the recovery requirement; if95 REST segments are filtered out early, the preceding-bout recovery96 time will appear as zero and every transition will be flagged.9798## Behavior contract (gate 3)99100The categorization, continuous-limit, recovery, and daily-accumulation101logic is exercised by the gate 3 contract test:102scripts/test_e1011_physical_perf.py against103scripts/e1011_physical_perf_logic.py (stdlib unittest, offline). Run:104python3 scripts/test_e1011_physical_perf.py105106## Compliance107108- ECSS standards are freely downloadable (ESA); cite the source and109 paraphrase per standards-map.yaml.110- compliance: STANDARDS-REF, gated: false.