ECSS Verification — Test Interface Control Document (space-systems/ecss/e1024-ticd)
Use when the task is to produce a test interface control document (TICD)
for a ground test campaign under ECSS-E-ST-10-24C §5.10 — enumerating every
interface connection between the unit under test (UUT) and ground support
equipment (GSE), defining signal properties and pin assignments, and verifying
the interface set is complete and self-consistent before the test begins.
Domain quick reference
- A TICD is the interface contract between the UUT and the GSE for a
specific test configuration. It captures every signal exchanged across
the test boundary: its type (electrical, power, data, mechanical, thermal,
RF, optical, or ground), its direction relative to the UUT (source, sink,
or bidirectional), and its physical location (connector identifier and pin
number). One TICD per test configuration; a changed configuration requires
a new or revised TICD before re-test.
- Signal types are grouped into interface categories. The set of required
categories for a given test is specified by the test specification or the
test procedure; the TICD must cover every required category. A TICD that
omits an entire required category (e.g. no power signals in a powered
functional test) is incomplete and blocks test readiness.
- Pin assignments must be unique within a connector: two signals cannot
share the same connector/pin pair. A ground reference signal must appear
at least once to establish the reference potential of the interface.
- Signal direction is defined relative to the UUT: source means the UUT
drives the signal; sink means the UUT receives it; bidirectional means
the UUT can both drive and receive on the same connection. A signal name
that appears simultaneously as source and sink in the same TICD indicates
a wiring conflict and must be resolved before test.
Workflow
- Identify the test configuration: record the TICD identifier, the UUT
name and configuration state, and the GSE assembly being interfaced.
A blank TICD identifier or test-item name stops the assessment —
both fields are mandatory traceability anchors.
- Enumerate every signal crossing the UUT/GSE boundary. For each signal
record: signal name, signal type (from the controlled vocabulary),
direction relative to the UUT, connector identifier, and pin number.
Reject any record that is missing a required field or carries an
unrecognized signal type or direction before it enters the assessment.
- Check pin assignments for uniqueness within each connector: flag any
connector/pin pair that is assigned to more than one signal. A conflict
here indicates a wiring error in the TICD that must be corrected before
the document can be baselined.
- Check for duplicate signal names across the TICD: two distinct physical
connections must not share the same signal name, as this makes the
document ambiguous and traceability from the test procedure to the
interface impossible.
- Confirm a ground reference signal is present: at least one signal of
type "ground" must appear in the TICD to establish the reference
potential. Absence of a ground reference is a TICD completeness failure.
- Compare the set of signal types present against the list of required
interface categories for this test. Flag each required category that
has no signal representative in the TICD.
- Check for direction conflicts: a signal name that appears as both source
and sink in the same TICD indicates a contradictory interface definition
and must be resolved.
- Aggregate all findings per step. The TICD is not ready for baseline
until every finding is resolved and the document re-assessed clean.
Pitfalls
- Baselineing a TICD before resolving pin conflicts — a shared connector/pin
pair causes physical wiring ambiguity that cannot be resolved at test time
without stopping the campaign.
- Omitting the ground reference signal on the assumption that GSE grounding
is implied — the TICD must explicitly record the reference potential
connection; implicit grounding is not traceable.
- Treating a TICD covering only a subset of required interface categories
as acceptable for a full functional test — an absent category means an
entire class of interfaces is uncontrolled, which invalidates the test
evidence for those interfaces.
- Reusing a TICD from a prior test configuration without issuing a new
revision when the connector pinout changes — stale TICD content silently
breaks traceability between the test procedure steps and the physical
interface.
- Recording a signal as bidirectional when it is in fact a fixed-direction
line — bidirectional designation requires explicit protocol justification;
treating every uncertain line as bidirectional inflates the interface
ambiguity and makes verification harder.
Behavior contract (gate 3)
The signal-record validation, pin-conflict, duplicate-name, ground-reference,
category-coverage, and direction-conflict logic is exercised by the gate 3
contract test: scripts/test_e1024_ticd.py against
scripts/e1024_ticd_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1024_ticd.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1024-ticd3description: "Use when produce test interface control documents (TICDs) for ground test interfaces under ECSS-E-ST-10-24C §5.10: identify every electrical, mechanical, data, and power interface between the unit under test and ground support equipment, define each signal's type, direction, connector, and pin assignment, verify pin assignments are unique, confirm a ground reference signal is present, and check that all required interface categories are covered before the test campaign begins. Trigger: ecss, e-st-10-system-scope, ticd, test-interface-control-document, ground-support-equipment, gse-interface, verification, ground-test."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/e1024-ticd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, ticd, test-interface-control-document, gse-interface, verification, ground-test]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Verification — Test Interface Control Document (space-systems/ecss/e1024-ticd)2324Use when the task is to produce a test interface control document (TICD)25for a ground test campaign under ECSS-E-ST-10-24C §5.10 — enumerating every26interface connection between the unit under test (UUT) and ground support27equipment (GSE), defining signal properties and pin assignments, and verifying28the interface set is complete and self-consistent before the test begins.2930## Domain quick reference3132- A TICD is the interface contract between the UUT and the GSE for a33 specific test configuration. It captures every signal exchanged across34 the test boundary: its type (electrical, power, data, mechanical, thermal,35 RF, optical, or ground), its direction relative to the UUT (source, sink,36 or bidirectional), and its physical location (connector identifier and pin37 number). One TICD per test configuration; a changed configuration requires38 a new or revised TICD before re-test.39- Signal types are grouped into interface categories. The set of required40 categories for a given test is specified by the test specification or the41 test procedure; the TICD must cover every required category. A TICD that42 omits an entire required category (e.g. no power signals in a powered43 functional test) is incomplete and blocks test readiness.44- Pin assignments must be unique within a connector: two signals cannot45 share the same connector/pin pair. A ground reference signal must appear46 at least once to establish the reference potential of the interface.47- Signal direction is defined relative to the UUT: source means the UUT48 drives the signal; sink means the UUT receives it; bidirectional means49 the UUT can both drive and receive on the same connection. A signal name50 that appears simultaneously as source and sink in the same TICD indicates51 a wiring conflict and must be resolved before test.5253## Workflow54551. Identify the test configuration: record the TICD identifier, the UUT56 name and configuration state, and the GSE assembly being interfaced.57 A blank TICD identifier or test-item name stops the assessment —58 both fields are mandatory traceability anchors.592. Enumerate every signal crossing the UUT/GSE boundary. For each signal60 record: signal name, signal type (from the controlled vocabulary),61 direction relative to the UUT, connector identifier, and pin number.62 Reject any record that is missing a required field or carries an63 unrecognized signal type or direction before it enters the assessment.643. Check pin assignments for uniqueness within each connector: flag any65 connector/pin pair that is assigned to more than one signal. A conflict66 here indicates a wiring error in the TICD that must be corrected before67 the document can be baselined.684. Check for duplicate signal names across the TICD: two distinct physical69 connections must not share the same signal name, as this makes the70 document ambiguous and traceability from the test procedure to the71 interface impossible.725. Confirm a ground reference signal is present: at least one signal of73 type "ground" must appear in the TICD to establish the reference74 potential. Absence of a ground reference is a TICD completeness failure.756. Compare the set of signal types present against the list of required76 interface categories for this test. Flag each required category that77 has no signal representative in the TICD.787. Check for direction conflicts: a signal name that appears as both source79 and sink in the same TICD indicates a contradictory interface definition80 and must be resolved.818. Aggregate all findings per step. The TICD is not ready for baseline82 until every finding is resolved and the document re-assessed clean.8384## Pitfalls8586- Baselineing a TICD before resolving pin conflicts — a shared connector/pin87 pair causes physical wiring ambiguity that cannot be resolved at test time88 without stopping the campaign.89- Omitting the ground reference signal on the assumption that GSE grounding90 is implied — the TICD must explicitly record the reference potential91 connection; implicit grounding is not traceable.92- Treating a TICD covering only a subset of required interface categories93 as acceptable for a full functional test — an absent category means an94 entire class of interfaces is uncontrolled, which invalidates the test95 evidence for those interfaces.96- Reusing a TICD from a prior test configuration without issuing a new97 revision when the connector pinout changes — stale TICD content silently98 breaks traceability between the test procedure steps and the physical99 interface.100- Recording a signal as bidirectional when it is in fact a fixed-direction101 line — bidirectional designation requires explicit protocol justification;102 treating every uncertain line as bidirectional inflates the interface103 ambiguity and makes verification harder.104105## Behavior contract (gate 3)106107The signal-record validation, pin-conflict, duplicate-name, ground-reference,108category-coverage, and direction-conflict logic is exercised by the gate 3109contract test: scripts/test_e1024_ticd.py against110scripts/e1024_ticd_logic.py (stdlib unittest, offline). Run:111python3 scripts/test_e1024_ticd.py112113## Compliance114115- ECSS standards are freely downloadable (ESA); cite the source and116 paraphrase per standards-map.yaml.117- compliance: STANDARDS-REF, gated: false.