ECSS Human Factors — EVA and Planetary Surface Activity (space-systems/ecss/e1011-eva)
Use when the task is to design EVA and planetary surface activity
requirements for a space system under ECSS-E-ST-10-11C §4.7.10 --
specifying suit interfaces, EVA tool requirements, crew mobility
envelopes, consumable margins, and abort timelines.
Domain quick reference
- EVA design covers two environments: orbital microgravity (ISS
exterior, free-flyer) and planetary surfaces (lunar, Martian).
Each environment drives different mobility assumptions: handrail
translation speed and microgravity body positioning for orbital;
suited walking speed and terrain slope limits for planetary. The
surface type is determined before any timeline or force assessment.
- Suit interface parameters govern the physical connection between
crew and system: the suit's operating pressure must be validated
against the spacecraft cabin pressure to identify whether a pre-
breathe protocol is required to mitigate decompression sickness
risk. Life support endurance must cover the planned EVA duration
plus a 25% reserve. Thermal operating range must bracket the
expected environment temperatures at both extremes.
- Tool design requirements constrain force, reach, and grip. Suited
crewmembers are limited in the force they can apply (approximately
111 N one-handed, 222 N two-handed in typical EVA suits); any tool
requiring a higher operator force fails the EVA design requirement.
Reach envelopes and glove compatibility with the tool handle are
checked separately and are both gateable.
- Consumable margins apply to O2, electrical power, and thermal
control (metabolic heat removal). Each consumable is checked at
end-of-EVA against a required reserve fraction (default 25%) of
total supply. An EVA timeline that leaves any consumable below its
reserve fraction fails the margin check.
- Abort scenario verification confirms that the crew can return to
the airlock from the most distant worksite within the safe-return
time limit using remaining consumables. The abort translation time
is computed from worksite distance and surface-type translation
speed; the remaining consumable capacity must cover that return
duration.
Workflow
- Determine the surface type (microgravity, ISS exterior, lunar,
Martian) for the EVA activity. This sets the translation speed
and terrain slope limits used in all subsequent calculations.
- Check suit interface compatibility: confirm that life support
endurance covers planned duration with 25% margin; flag if suit
operating pressure is at or above cabin pressure (pre-breathe
protocol required); confirm environment temperatures fall within
the suit's thermal operating range. Reject the suit if any life
support or thermal check fails.
- Assess each EVA tool: confirm required operator force does not
exceed the suited operator force limit for the operation class
(one-hand or two-hand); confirm tool reach meets the task's
minimum reach; confirm the handle is compatible with the EVA
pressure glove. Flag every failing parameter as a distinct issue.
- Evaluate crew mobility: for planetary surfaces, compare terrain
slope against the surface-type trafficability limit; compute
estimated translation time from distance and speed; flag if
estimated time exceeds the allowed timeline allocation.
- Compute consumable margins at end of planned EVA duration: for
each consumable (O2 mass, electrical energy, coolant/thermal
capacity), subtract usage from supply and compare the remainder
against the required reserve fraction. Flag each consumable that
falls short.
- Verify the abort scenario: compute return time from furthest
worksite to airlock using the surface-type translation speed;
confirm return time is within the abort time limit; confirm
consumable remaining at abort trigger covers the return duration.
- Aggregate all findings. The EVA design is compliant only when
all suit, tool, mobility, consumable, and abort checks are clear.
Pitfalls
- Applying ISS translation speed to a planetary surface EVA and
underestimating return time -- suited walking on lunar or Martian
terrain is two to four times slower than handrail translation
in microgravity.
- Checking consumable margin against the remaining quantity at the
abort trigger instead of at planned end-of-EVA -- the margin
check applies to the full planned timeline; the abort check is
a separate verification against remaining capacity at abort time.
- Treating a pre-breathe flag as non-critical -- if suit operating
pressure is at or above cabin pressure, a pre-breathe protocol
is operationally required and must be captured in the EVA design
document; omitting it is a design gap, not a warning.
- Checking force against the operator maximum without also checking
the class limit -- the suited crewmember's personal force
capability may exceed the EVA class limit; both bounds must hold.
- Leaving terrain slope unverified for planetary EVAs because no
specific worksite has been selected -- the design requirement must
state the maximum slope for which the EVA is designed; if no value
is on record, flag the gap rather than assume flat terrain.
Behavior contract (gate 3)
The suit-interface, tool-assessment, mobility-evaluation,
consumable-margin, and abort-timeline logic is exercised by the
gate 3 contract test: scripts/test_e1011_eva.py against
scripts/e1011_eva_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_eva.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-eva3description: "Use when design EVA and planetary surface activity requirements for a space system under ECSS-E-ST-10-11C §4.7.10: verify suit interface compatibility (operating pressure, thermal envelope, life support endurance), assess tool design parameters (operator force limits, reach envelope, glove compatibility), evaluate crew mobility timelines and terrain trafficability, and compute consumable margins with required reserves for O2, power, and thermal control. Verify abort scenario timelines confirm safe crew return within consumable limits. Trigger: ecss, e-st-10-system-scope, eva, extravehicular-activity, suit-interface, eva-tools, crew-mobility, planetary-activity, consumable-margin."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-eva15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, eva, extravehicular-activity, suit-interface, eva-tools, crew-mobility, planetary-activity]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Human Factors — EVA and Planetary Surface Activity (space-systems/ecss/e1011-eva)2324Use when the task is to design EVA and planetary surface activity25requirements for a space system under ECSS-E-ST-10-11C §4.7.10 --26specifying suit interfaces, EVA tool requirements, crew mobility27envelopes, consumable margins, and abort timelines.2829## Domain quick reference3031- EVA design covers two environments: orbital microgravity (ISS32 exterior, free-flyer) and planetary surfaces (lunar, Martian).33 Each environment drives different mobility assumptions: handrail34 translation speed and microgravity body positioning for orbital;35 suited walking speed and terrain slope limits for planetary. The36 surface type is determined before any timeline or force assessment.37- Suit interface parameters govern the physical connection between38 crew and system: the suit's operating pressure must be validated39 against the spacecraft cabin pressure to identify whether a pre-40 breathe protocol is required to mitigate decompression sickness41 risk. Life support endurance must cover the planned EVA duration42 plus a 25% reserve. Thermal operating range must bracket the43 expected environment temperatures at both extremes.44- Tool design requirements constrain force, reach, and grip. Suited45 crewmembers are limited in the force they can apply (approximately46 111 N one-handed, 222 N two-handed in typical EVA suits); any tool47 requiring a higher operator force fails the EVA design requirement.48 Reach envelopes and glove compatibility with the tool handle are49 checked separately and are both gateable.50- Consumable margins apply to O2, electrical power, and thermal51 control (metabolic heat removal). Each consumable is checked at52 end-of-EVA against a required reserve fraction (default 25%) of53 total supply. An EVA timeline that leaves any consumable below its54 reserve fraction fails the margin check.55- Abort scenario verification confirms that the crew can return to56 the airlock from the most distant worksite within the safe-return57 time limit using remaining consumables. The abort translation time58 is computed from worksite distance and surface-type translation59 speed; the remaining consumable capacity must cover that return60 duration.6162## Workflow63641. Determine the surface type (microgravity, ISS exterior, lunar,65 Martian) for the EVA activity. This sets the translation speed66 and terrain slope limits used in all subsequent calculations.672. Check suit interface compatibility: confirm that life support68 endurance covers planned duration with 25% margin; flag if suit69 operating pressure is at or above cabin pressure (pre-breathe70 protocol required); confirm environment temperatures fall within71 the suit's thermal operating range. Reject the suit if any life72 support or thermal check fails.733. Assess each EVA tool: confirm required operator force does not74 exceed the suited operator force limit for the operation class75 (one-hand or two-hand); confirm tool reach meets the task's76 minimum reach; confirm the handle is compatible with the EVA77 pressure glove. Flag every failing parameter as a distinct issue.784. Evaluate crew mobility: for planetary surfaces, compare terrain79 slope against the surface-type trafficability limit; compute80 estimated translation time from distance and speed; flag if81 estimated time exceeds the allowed timeline allocation.825. Compute consumable margins at end of planned EVA duration: for83 each consumable (O2 mass, electrical energy, coolant/thermal84 capacity), subtract usage from supply and compare the remainder85 against the required reserve fraction. Flag each consumable that86 falls short.876. Verify the abort scenario: compute return time from furthest88 worksite to airlock using the surface-type translation speed;89 confirm return time is within the abort time limit; confirm90 consumable remaining at abort trigger covers the return duration.917. Aggregate all findings. The EVA design is compliant only when92 all suit, tool, mobility, consumable, and abort checks are clear.9394## Pitfalls9596- Applying ISS translation speed to a planetary surface EVA and97 underestimating return time -- suited walking on lunar or Martian98 terrain is two to four times slower than handrail translation99 in microgravity.100- Checking consumable margin against the remaining quantity at the101 abort trigger instead of at planned end-of-EVA -- the margin102 check applies to the full planned timeline; the abort check is103 a separate verification against remaining capacity at abort time.104- Treating a pre-breathe flag as non-critical -- if suit operating105 pressure is at or above cabin pressure, a pre-breathe protocol106 is operationally required and must be captured in the EVA design107 document; omitting it is a design gap, not a warning.108- Checking force against the operator maximum without also checking109 the class limit -- the suited crewmember's personal force110 capability may exceed the EVA class limit; both bounds must hold.111- Leaving terrain slope unverified for planetary EVAs because no112 specific worksite has been selected -- the design requirement must113 state the maximum slope for which the EVA is designed; if no value114 is on record, flag the gap rather than assume flat terrain.115116## Behavior contract (gate 3)117118The suit-interface, tool-assessment, mobility-evaluation,119consumable-margin, and abort-timeline logic is exercised by the120gate 3 contract test: scripts/test_e1011_eva.py against121scripts/e1011_eva_logic.py (stdlib unittest, offline). Run:122python3 scripts/test_e1011_eva.py123124## Compliance125126- ECSS standards are freely downloadable (ESA); cite the source and127 paraphrase per standards-map.yaml.128- compliance: STANDARDS-REF, gated: false.