Interfaces

Interfaces, Conduits and ICDs

An interface is a Conduit: it connects to two assets or ports and transfers the Input/Outputs (items) that cross it.

Where to find it

Conduit attributes: Capacity and Units, Latency, Connector/Pins, Medium, Owner, Interface Status (Draft → Proposed → Agreed → Baselined) and TBD/TBR.
Input/Output attributes: Size and Units, Data Rate and Data Rate Units, Protocol/Format, Message/Data Definition.
Link interface requirements with traced from; requirements linked by satisfies are listed too. A requirement created from the picker gets the Interface Requirement label.
Capacity check: sums each item's Data Rate (or Size when no rate is set), converted to the conduit's units, and compares the total with Capacity. A bundle conduit counts its child conduits' items. Items whose units do not convert are reported as a unit mismatch.
Where to edit: the inspector for an IBD connector or an ICD conduit shows conveyed items, status, owner, TBD/TBR, requirements and the capacity check.
Outputs: the ICD's Export ICD Table (CSV) and Export ICD Document (Word); the Interface Register's Export CSV and per-row ICD.