Section 55 of 102
54. Interface Model
Stable section ID: S05-CON-007-SECTION-55 · 55 content blocks
An Interface is the formally defined boundary through which two or more Entities exchange forces, energy, fluids, information, control, environmental effects, or access.
Each Interface shall define:
Interface Type and Instance IDs;
host;
domain;
local coordinate system;
controlled geometry;
datum system;
Compatibility Class;
Capability Declaration;
operating limits;
approach envelope;
engagement sequence;
locking method;
release method;
state model;
inspection method;
evidence;
current connection.
Example:
interface EC01_Node_Interface : StructuralInterface {
id: "s05:interface:ec01:node-side";
host: @EndCartridge_EC01;
domain: structural;
coordinates: @EC01_Interface_CS;
geometry: @S05_Structural_IF_SC03_Geometry;
datums: @EC01_Interface_Datums;
compatibility_class: @S05_Structural_IF_SC03;
- transfers: [
- axial,
- shear_y,
- shear_z,
- bending_y,
- bending_z,
- torsion
];
state: disconnected;
}
Multi-domain Interfaces shall identify each transferred function independently.
A physical Interface Instance shall remain distinct from the Interface Type defining its standard geometry and behavior.
Interface availability shall not imply compatibility with every Interface of similar appearance.
BDL shall support Interface states including:
available;
reserved;
aligned;
partially engaged;
seated;
locked;
connected;
commissioned;
operational;
degraded;
isolated;
faulted;
disconnected.