ECSS Human Factors — Physical and Psycho-physiological Environment Characterisation (space-systems/ecss/e1011-phys-env)
Use when the task is the physical and psycho-physiological environment
characterisation required by ECSS-E-ST-10-11C §4.2.1.6 -- categorizing
environment parameters, verifying assessment coverage across all mission
phases, checking each parameter value against its human-performance
acceptability bound, and flagging deficiencies before the characterisation
is declared complete.
Domain quick reference
- §4.2.1.6 splits the environment into two families: physical parameters
(thermal: temperature and humidity; acoustic: noise level; vibration:
whole-body rms acceleration; lighting: illuminance; atmospheric
composition: oxygen and CO2 partial pressures) and psycho-physiological
parameters (workload index, stress/fatigue index, sleep adequacy metric).
Each parameter is categorized into exactly one family before its value
is checked.
- Each parameter carries an acceptability bound derived from HFE literature
and applicable standards; a value within [lower_bound, upper_bound] is
within the range that supports sustained human performance. A value
outside that range is flagged as an exceedance, regardless of family.
- Coverage is required across all mission phases and operational contexts
defined in the human-centred design planning document; a parameter not
yet assessed is a coverage gap, which is itself a finding, not a pass.
- Bounds may be tightened by mission-specific requirements (e.g. a stricter
CO2 limit for long-duration missions) by overriding the default bounds
map; the default bounds supplied by this skill are the common HFE
baseline, not a mission design rule.
Workflow
- Inventory every environment parameter relevant to the mission profile
and categorize each one as physical or psycho-physiological. Reject an
unrecognized parameter before it enters the assessment.
- Verify that all required parameters have been assessed; list any
parameter with no measured or predicted value as a coverage gap.
Do not treat an uncovered parameter as implicitly acceptable.
- For each assessed parameter, retrieve the applicable human-performance
acceptability bound (use the default if no mission-specific bound is
defined) and check whether the measured or predicted value falls within
[lower_bound, upper_bound].
- Flag every parameter whose value lies outside its bound as an
exceedance; record the parameter name, measured value, and the bound
that was violated.
- Aggregate exceedances and coverage gaps into the environment review
result; the characterisation is acceptable only when both lists are
empty.
- Report the full review result to the human-centred design planning
process for integration into the context-of-use description.
Pitfalls
- Omitting psycho-physiological parameters from the characterisation and
treating only the physical environment as complete -- §4.2.1.6 explicitly
requires both families; a characterisation with no workload, stress, or
sleep data is an incomplete assessment.
- Using default bounds without checking for mission-specific overrides --
long-duration or confined-habitat missions routinely impose tighter CO2
and noise limits than the HFE baseline; applying the default bound in
those contexts can mask a real exceedance.
- Treating a parameter with no assessed value as within bounds -- an
unassessed parameter represents an unknown risk, not compliance; the
correct finding is a coverage gap, not a pass.
- Collapsing all acoustic exceedances into a single "noise problem" flag
without recording the measured value -- the exact level is needed to size
the required mitigation and to verify that the corrected design brings the
value back within bound.
Behavior contract (gate 3)
The parameter categorization, bounds checking, coverage assessment, and
environment review aggregation logic is exercised by the gate 3 contract
test: scripts/test_e1011_phys_env.py against
scripts/e1011_phys_env_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_phys_env.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-phys-env3description: "Use when assess the physical and psycho-physiological environments relevant to human performance under ECSS-E-ST-10-11C §4.2.1.6: categorize each environment parameter as physical (thermal, acoustic, vibration, lighting, or atmospheric composition) or psycho-physiological (workload, stress, sleep adequacy), verify that all required parameters have been assessed for the applicable mission phase, check each measured or predicted value against its human-performance acceptability bound, flag any parameter that falls outside the acceptable range, and confirm full coverage before closing the environment characterisation. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, physical-environment, psycho-physiological, human-performance, thermal, acoustic, vibration, illuminance, atmospheric-quality."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-phys-env15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, e-st-10-11c, physical-environment, psycho-physiological, human-performance, thermal, acoustic, vibration, illuminance, atmospheric-quality]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Human Factors — Physical and Psycho-physiological Environment Characterisation (space-systems/ecss/e1011-phys-env)2324Use when the task is the physical and psycho-physiological environment25characterisation required by ECSS-E-ST-10-11C §4.2.1.6 -- categorizing26environment parameters, verifying assessment coverage across all mission27phases, checking each parameter value against its human-performance28acceptability bound, and flagging deficiencies before the characterisation29is declared complete.3031## Domain quick reference3233- §4.2.1.6 splits the environment into two families: physical parameters34 (thermal: temperature and humidity; acoustic: noise level; vibration:35 whole-body rms acceleration; lighting: illuminance; atmospheric36 composition: oxygen and CO2 partial pressures) and psycho-physiological37 parameters (workload index, stress/fatigue index, sleep adequacy metric).38 Each parameter is categorized into exactly one family before its value39 is checked.40- Each parameter carries an acceptability bound derived from HFE literature41 and applicable standards; a value within [lower_bound, upper_bound] is42 within the range that supports sustained human performance. A value43 outside that range is flagged as an exceedance, regardless of family.44- Coverage is required across all mission phases and operational contexts45 defined in the human-centred design planning document; a parameter not46 yet assessed is a coverage gap, which is itself a finding, not a pass.47- Bounds may be tightened by mission-specific requirements (e.g. a stricter48 CO2 limit for long-duration missions) by overriding the default bounds49 map; the default bounds supplied by this skill are the common HFE50 baseline, not a mission design rule.5152## Workflow53541. Inventory every environment parameter relevant to the mission profile55 and categorize each one as physical or psycho-physiological. Reject an56 unrecognized parameter before it enters the assessment.572. Verify that all required parameters have been assessed; list any58 parameter with no measured or predicted value as a coverage gap.59 Do not treat an uncovered parameter as implicitly acceptable.603. For each assessed parameter, retrieve the applicable human-performance61 acceptability bound (use the default if no mission-specific bound is62 defined) and check whether the measured or predicted value falls within63 [lower_bound, upper_bound].644. Flag every parameter whose value lies outside its bound as an65 exceedance; record the parameter name, measured value, and the bound66 that was violated.675. Aggregate exceedances and coverage gaps into the environment review68 result; the characterisation is acceptable only when both lists are69 empty.706. Report the full review result to the human-centred design planning71 process for integration into the context-of-use description.7273## Pitfalls7475- Omitting psycho-physiological parameters from the characterisation and76 treating only the physical environment as complete -- §4.2.1.6 explicitly77 requires both families; a characterisation with no workload, stress, or78 sleep data is an incomplete assessment.79- Using default bounds without checking for mission-specific overrides --80 long-duration or confined-habitat missions routinely impose tighter CO281 and noise limits than the HFE baseline; applying the default bound in82 those contexts can mask a real exceedance.83- Treating a parameter with no assessed value as within bounds -- an84 unassessed parameter represents an unknown risk, not compliance; the85 correct finding is a coverage gap, not a pass.86- Collapsing all acoustic exceedances into a single "noise problem" flag87 without recording the measured value -- the exact level is needed to size88 the required mitigation and to verify that the corrected design brings the89 value back within bound.9091## Behavior contract (gate 3)9293The parameter categorization, bounds checking, coverage assessment, and94environment review aggregation logic is exercised by the gate 3 contract95test: scripts/test_e1011_phys_env.py against96scripts/e1011_phys_env_logic.py (stdlib unittest, offline). Run:97python3 scripts/test_e1011_phys_env.py9899## Compliance100101- ECSS standards are freely downloadable (ESA); cite the source and102 paraphrase per standards-map.yaml.103- compliance: STANDARDS-REF, gated: false.