ECSS Structures — Interface Verification by Test or Inspection (space-systems/ecss/interface-verification-test)
Use when the task is verifying that structural interfaces between spacecraft
subsystems or components meet their Interface Control Document (ICD) requirements,
following the procedure outlined in ECSS E-ST-32C clause 4.6.3.22. The procedure
covers categorizing each interface by type, selecting the appropriate verification
method, checking dimensional fit against the ICD tolerance stack, and confirming
every interface carries a valid ICD reference before declaring compliance.
Domain quick reference
- Clause 4.6.3.22 requires that each interface between structural assemblies be
formally verified either by physical inspection, by supporting analysis, or by
dedicated test, depending on the nature and criticality of the interface. The
method selected must be traceable to the ICD.
- Interfaces are grouped into five categories: mechanical (bolted, bonded,
riveted, welded joints and mating structural surfaces), electrical (connector
and harness pass-throughs that impose structural loads), thermal (conductive
and radiative contact surfaces that carry thermo-elastic loads), fluid
(pressure lines and fittings that transmit fluid-induced structural loads), and
optical (alignment-critical interfaces for sensors and instruments).
Each interface is placed in exactly one category before its verification
method is selected.
- Verification method selection follows the interface category and available
facility: electrical and optical interfaces require functional test; any
interface category where a dedicated test facility exists defaults to test;
otherwise inspection is the baseline method. Analysis alone is not a
standalone verification for dimensional fit — it supplements inspection or test.
- A dimensional fit check confirms that the measured gap or clearance at the
mating surface falls within the tolerance band specified in the ICD. The check
computes the deviation from the ICD nominal dimension and compares it against
the ±tolerance. A surface outside the band is a non-compliant finding.
- Every interface must carry a valid ICD reference. An interface with no ICD
reference is a non-compliant finding regardless of the dimensional result,
because traceability to a controlled requirement document cannot be established.
Workflow
- Collect the full interface inventory from the structural ICD set. For each
interface record the interface identifier, category (mechanical / electrical /
thermal / fluid / optical), the ICD nominal dimension and its ±tolerance, the
measured actual dimension, the ICD reference identifier, and the proposed
verification method.
- Validate every interface record for completeness before proceeding. Reject
any record that is missing a required field and flag it as an input error
rather than a compliance finding.
- Categorize each interface into exactly one of the five categories. Reject any
interface with an unrecognized category — do not silently assign a default.
- Confirm the proposed verification method is one of: inspection, analysis, or
test. Reject unrecognized methods with an explicit error.
- Perform the dimensional fit check for each interface: compute the deviation
of the actual dimension from the ICD nominal, check that it lies within the
±tolerance band, and record the result. Flag any interface outside the band
as a dimensional non-conformance finding.
- Check that every interface record carries a non-empty ICD reference string.
Flag any interface with a missing or blank ICD reference as a traceability
non-conformance finding.
- Aggregate the findings per interface: an interface is compliant only when
both the dimensional fit check passes and a valid ICD reference is present.
An interface with any finding is non-compliant.
- Summarize the assessment: report total interface count, compliant count,
non-compliant count, and the list of findings per interface. The structural
interface set is fully verified only when the non-compliant count is zero.
Pitfalls
- Skipping the ICD reference check and treating a clean dimensional result as
full compliance — an interface with no traceable ICD reference is not verified
regardless of its measured dimension.
- Applying the same verification method to all interfaces irrespective of
category — electrical and optical interfaces require functional test to confirm
their interface loads and alignment; inspection alone is insufficient.
- Treating analysis as a standalone verification method for dimensional fit —
analysis supports the verification but dimensional compliance must ultimately
be confirmed by a physical measurement (inspection) or by a dedicated test.
- Counting an interface as compliant when its tolerance band is unset or zero
because "no violation was found" — an unset tolerance means the ICD requirement
was never captured, which is itself a traceability finding, not a pass.
- Assigning interfaces to multiple categories to hedge against method
requirements — each interface belongs to exactly one category, and the
verification method follows from that single assignment.
Behavior contract (gate 3)
The interface categorization, verification method selection, dimensional fit
check, ICD reference validation, per-interface compliance determination, and
set-level aggregation logic are exercised by the gate 3 contract test:
scripts/test_interface_verification_test.py against
scripts/interface_verification_test_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_interface_verification_test.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase
per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: interface-verification-test3description: "Use when verify interface compliance between spacecraft structural4 subsystems or components per ECSS E-ST-32C clause 4.6.3.22: categorize each5 interface as mechanical, electrical, thermal, fluid, or optical; select the6 verification method (inspection, analysis, or test) appropriate to the interface7 type; perform dimensional fit checks against the tolerance stack in the Interface8 Control Document; confirm every interface carries a valid ICD reference; and9 aggregate per-interface findings to determine overall compliance. Trigger: ecss,10 e-st-32-structures-scope, interface-verification, icd, dimensional-fit,11 structural-interface, inspection, test-verification, fit-check."12license: Apache-2.013compliance: STANDARDS-REF14standards:15 - id: ecss16 reference-only: true17gated: false18domain: space-systems19pack: space-systems20compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"21metadata:22 source: https://skillmd.com/skills/ashfordeou/interface-verification-test23 domain: space-systems24 subdomain: ecss25 tags: [ecss, e-st-32-structures-scope, interface-verification, icd, dimensional-fit, structural-interface, inspection, test-verification, fit-check]26 version: 0.1.027 author: Aero Agent Skills28---2930# ECSS Structures — Interface Verification by Test or Inspection (space-systems/ecss/interface-verification-test)3132Use when the task is verifying that structural interfaces between spacecraft33subsystems or components meet their Interface Control Document (ICD) requirements,34following the procedure outlined in ECSS E-ST-32C clause 4.6.3.22. The procedure35covers categorizing each interface by type, selecting the appropriate verification36method, checking dimensional fit against the ICD tolerance stack, and confirming37every interface carries a valid ICD reference before declaring compliance.3839## Domain quick reference4041- Clause 4.6.3.22 requires that each interface between structural assemblies be42 formally verified either by physical inspection, by supporting analysis, or by43 dedicated test, depending on the nature and criticality of the interface. The44 method selected must be traceable to the ICD.45- Interfaces are grouped into five categories: mechanical (bolted, bonded,46 riveted, welded joints and mating structural surfaces), electrical (connector47 and harness pass-throughs that impose structural loads), thermal (conductive48 and radiative contact surfaces that carry thermo-elastic loads), fluid49 (pressure lines and fittings that transmit fluid-induced structural loads), and50 optical (alignment-critical interfaces for sensors and instruments).51 Each interface is placed in exactly one category before its verification52 method is selected.53- Verification method selection follows the interface category and available54 facility: electrical and optical interfaces require functional test; any55 interface category where a dedicated test facility exists defaults to test;56 otherwise inspection is the baseline method. Analysis alone is not a57 standalone verification for dimensional fit — it supplements inspection or test.58- A dimensional fit check confirms that the measured gap or clearance at the59 mating surface falls within the tolerance band specified in the ICD. The check60 computes the deviation from the ICD nominal dimension and compares it against61 the ±tolerance. A surface outside the band is a non-compliant finding.62- Every interface must carry a valid ICD reference. An interface with no ICD63 reference is a non-compliant finding regardless of the dimensional result,64 because traceability to a controlled requirement document cannot be established.6566## Workflow67681. Collect the full interface inventory from the structural ICD set. For each69 interface record the interface identifier, category (mechanical / electrical /70 thermal / fluid / optical), the ICD nominal dimension and its ±tolerance, the71 measured actual dimension, the ICD reference identifier, and the proposed72 verification method.732. Validate every interface record for completeness before proceeding. Reject74 any record that is missing a required field and flag it as an input error75 rather than a compliance finding.763. Categorize each interface into exactly one of the five categories. Reject any77 interface with an unrecognized category — do not silently assign a default.784. Confirm the proposed verification method is one of: inspection, analysis, or79 test. Reject unrecognized methods with an explicit error.805. Perform the dimensional fit check for each interface: compute the deviation81 of the actual dimension from the ICD nominal, check that it lies within the82 ±tolerance band, and record the result. Flag any interface outside the band83 as a dimensional non-conformance finding.846. Check that every interface record carries a non-empty ICD reference string.85 Flag any interface with a missing or blank ICD reference as a traceability86 non-conformance finding.877. Aggregate the findings per interface: an interface is compliant only when88 both the dimensional fit check passes and a valid ICD reference is present.89 An interface with any finding is non-compliant.908. Summarize the assessment: report total interface count, compliant count,91 non-compliant count, and the list of findings per interface. The structural92 interface set is fully verified only when the non-compliant count is zero.9394## Pitfalls9596- Skipping the ICD reference check and treating a clean dimensional result as97 full compliance — an interface with no traceable ICD reference is not verified98 regardless of its measured dimension.99- Applying the same verification method to all interfaces irrespective of100 category — electrical and optical interfaces require functional test to confirm101 their interface loads and alignment; inspection alone is insufficient.102- Treating analysis as a standalone verification method for dimensional fit —103 analysis supports the verification but dimensional compliance must ultimately104 be confirmed by a physical measurement (inspection) or by a dedicated test.105- Counting an interface as compliant when its tolerance band is unset or zero106 because "no violation was found" — an unset tolerance means the ICD requirement107 was never captured, which is itself a traceability finding, not a pass.108- Assigning interfaces to multiple categories to hedge against method109 requirements — each interface belongs to exactly one category, and the110 verification method follows from that single assignment.111112## Behavior contract (gate 3)113114The interface categorization, verification method selection, dimensional fit115check, ICD reference validation, per-interface compliance determination, and116set-level aggregation logic are exercised by the gate 3 contract test:117scripts/test_interface_verification_test.py against118scripts/interface_verification_test_logic.py (stdlib unittest, offline). Run:119python3 scripts/test_interface_verification_test.py120121## Compliance122123- ECSS standards are freely downloadable (ESA); cite the source and paraphrase124 per standards-map.yaml.125- compliance: STANDARDS-REF, gated: false.