ECSS System Engineering — Configuration Assembly Constraints (space-systems/ecss/e10-config-assembly)
Use when the task is capturing the configuration assembly constraints
of ECSS-E-ST-10C clause 5.4.2.3 -- checking the physical and
functional grouping rules that decide which configuration items (CIs)
may be integrated into the same physical assembly, accounting each
assembly's mass against its budget, and deriving the integration
sequence across assemblies from their functional dependencies.
Domain quick reference
- Clause 5.4.2.3 requires that CIs proposed for one physical assembly
satisfy a physical rule set before integration: a shared mounting
zone/interface, hazard separation between an energetic item (e.g.
a pyrotechnic device) and a non-energetic item, and no EMI role
conflict between an EMI-sensitive item and an EMI-emitting item.
Two neutral, same-zone, non-hazardous items are always physically
compatible.
- A separate functional rule set groups CIs that belong to the same
function group -- they are expected to integrate together. When a
functional grouping expectation collides with a physical rule (the
CIs share a function group but fail a physical check), that is a
functional grouping conflict: the functional expectation cannot be
honored as-is and the assembly plan must change, not the check.
- Each physical assembly carries an allocable mass budget; the total
mass of every CI assigned to it must not exceed that budget. An
assembly with no budget on record is itself a finding -- the
requirement was never captured, not a pass by default.
- Assemblies with a functional dependency between them (one must be
integrated before another) must be sequenced in that order; a cycle
in the dependency set means no valid integration sequence exists and
the dependency capture itself is wrong.
Workflow
- Inventory every configuration item proposed for a given physical
assembly, with its mounting zone, hazard class (energetic or
none), EMI role (sensitive, emitter, or neutral), mass, and
function group (or none). Reject a CI record missing a required
attribute or carrying an unrecognized hazard class or EMI role.
- For every pair of CIs in the assembly, check physical
compatibility: flag a mounting-zone mismatch, flag hazard
separation when exactly one of the pair is energetic, and flag an
EMI conflict when one is sensitive and the other is an emitter.
- For every pair sharing a function group, check whether the
physical compatibility check for that pair failed; if so, record a
functional grouping conflict distinct from the physical finding.
- Sum the mass of every CI in the assembly and compare it to the
assembly's allocable mass budget; flag an exceedance, and
separately flag an assembly with no budget captured.
- Aggregate the pairwise findings and the mass finding per assembly;
the assembly is not integration-ready until both are clear.
- Across assemblies with a captured functional dependency (one
assembly must integrate before another), derive the integration
sequence by dependency order; a cycle means the dependency capture
must be corrected before a sequence can be produced.
Pitfalls
- Treating a mounting-zone match alone as sufficient for physical
compatibility -- hazard separation and EMI role conflicts are
independent checks and must all clear, not just the zone match.
- Resolving a functional grouping conflict by dropping the physical
finding instead of flagging both -- the functional expectation does
not override a hazard-separation or EMI-conflict requirement.
- Leaving an assembly's mass budget unset and reading "no exceedance"
as compliant -- an unset budget means the requirement was never
captured, which is itself a finding.
- Picking an arbitrary integration order when assemblies have no
captured dependency between them -- absence of a dependency is not
itself a constraint violation, but a captured dependency cycle is
and must be corrected, not worked around by re-ordering silently.
Behavior contract (gate 3)
The physical-compatibility, functional-grouping-conflict,
mass-budget, and integration-sequence logic is exercised by the gate
3 contract test: scripts/test_e10_config_assembly.py against
scripts/e10_config_assembly_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e10_config_assembly.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e10-config-assembly3description: "Use when determining the physical and functional grouping rules that govern how configuration items are assembled for integration under ECSS-E-ST-10C clause 5.4.2.3: check every pair of configuration items proposed for one physical assembly for mounting-zone match, hazard separation between energetic and non-energetic items, and EMI role conflict between a sensitive and an emitting item; flag a functional grouping conflict when items sharing a function group are physically incompatible; account each assembly's total mass against its allocable mass budget; and derive a dependency-ordered integration sequence across assemblies. Trigger: ecss, e-st-10c, configuration assembly, configuration item grouping, physical grouping rules, functional grouping rules, integration sequence, mass budget, hazard separation, emi conflict."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/e10-config-assembly15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10c, config-assembly, configuration-items, integration-sequence, mass-budget, hazard-separation]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Configuration Assembly Constraints (space-systems/ecss/e10-config-assembly)2324Use when the task is capturing the configuration assembly constraints25of ECSS-E-ST-10C clause 5.4.2.3 -- checking the physical and26functional grouping rules that decide which configuration items (CIs)27may be integrated into the same physical assembly, accounting each28assembly's mass against its budget, and deriving the integration29sequence across assemblies from their functional dependencies.3031## Domain quick reference3233- Clause 5.4.2.3 requires that CIs proposed for one physical assembly34 satisfy a physical rule set before integration: a shared mounting35 zone/interface, hazard separation between an energetic item (e.g.36 a pyrotechnic device) and a non-energetic item, and no EMI role37 conflict between an EMI-sensitive item and an EMI-emitting item.38 Two neutral, same-zone, non-hazardous items are always physically39 compatible.40- A separate functional rule set groups CIs that belong to the same41 function group -- they are expected to integrate together. When a42 functional grouping expectation collides with a physical rule (the43 CIs share a function group but fail a physical check), that is a44 functional grouping conflict: the functional expectation cannot be45 honored as-is and the assembly plan must change, not the check.46- Each physical assembly carries an allocable mass budget; the total47 mass of every CI assigned to it must not exceed that budget. An48 assembly with no budget on record is itself a finding -- the49 requirement was never captured, not a pass by default.50- Assemblies with a functional dependency between them (one must be51 integrated before another) must be sequenced in that order; a cycle52 in the dependency set means no valid integration sequence exists and53 the dependency capture itself is wrong.5455## Workflow56571. Inventory every configuration item proposed for a given physical58 assembly, with its mounting zone, hazard class (energetic or59 none), EMI role (sensitive, emitter, or neutral), mass, and60 function group (or none). Reject a CI record missing a required61 attribute or carrying an unrecognized hazard class or EMI role.622. For every pair of CIs in the assembly, check physical63 compatibility: flag a mounting-zone mismatch, flag hazard64 separation when exactly one of the pair is energetic, and flag an65 EMI conflict when one is sensitive and the other is an emitter.663. For every pair sharing a function group, check whether the67 physical compatibility check for that pair failed; if so, record a68 functional grouping conflict distinct from the physical finding.694. Sum the mass of every CI in the assembly and compare it to the70 assembly's allocable mass budget; flag an exceedance, and71 separately flag an assembly with no budget captured.725. Aggregate the pairwise findings and the mass finding per assembly;73 the assembly is not integration-ready until both are clear.746. Across assemblies with a captured functional dependency (one75 assembly must integrate before another), derive the integration76 sequence by dependency order; a cycle means the dependency capture77 must be corrected before a sequence can be produced.7879## Pitfalls8081- Treating a mounting-zone match alone as sufficient for physical82 compatibility -- hazard separation and EMI role conflicts are83 independent checks and must all clear, not just the zone match.84- Resolving a functional grouping conflict by dropping the physical85 finding instead of flagging both -- the functional expectation does86 not override a hazard-separation or EMI-conflict requirement.87- Leaving an assembly's mass budget unset and reading "no exceedance"88 as compliant -- an unset budget means the requirement was never89 captured, which is itself a finding.90- Picking an arbitrary integration order when assemblies have no91 captured dependency between them -- absence of a dependency is not92 itself a constraint violation, but a captured dependency cycle is93 and must be corrected, not worked around by re-ordering silently.9495## Behavior contract (gate 3)9697The physical-compatibility, functional-grouping-conflict,98mass-budget, and integration-sequence logic is exercised by the gate993 contract test: scripts/test_e10_config_assembly.py against100scripts/e10_config_assembly_logic.py (stdlib unittest, offline). Run:101python3 scripts/test_e10_config_assembly.py102103## Compliance104105- ECSS standards are freely downloadable (ESA); cite the source and106 paraphrase per standards-map.yaml.107- compliance: STANDARDS-REF, gated: false.