Interfaces
Every interface in one register.
An interface is a conduit between two assets or ports, carrying the items that cross it. Holarch keeps every interface in a register with its status, owner and requirements, checks capacity, and generates interface control documents.
What you can do
Interface register
Every conduit in the project with its endpoints, status, owner, TBD/TBR, conveyed items, requirements and capacity check. Status cards count interfaces from Draft to Baselined; click one to filter.
Items and attributes
Conduits have capacity, latency, connector, medium and owner. Items have size, data rate, protocol and message definition. Link interface requirements to each conduit.
Capacity check
The data rates of the conveyed items are converted to the conduit's units and compared with its capacity. Over-capacity links turn red; units that do not convert are reported.
Interface control diagrams
Show the interface between two parent assets: the conduits, their items, status, latency and capacity.
ICD documents
Export an ICD document in Word with the interface register, a status summary and one section per conduit, or an ICD table in CSV with every interface attribute.
N² and I² views
The N² diagram shows functions on the diagonal and the I/O they exchange. The I² diagram shows assets on the diagonal and the conduits between them. Both export to CSV.
How it works
- Draw the connections. Create connectors in an internal block diagram, or conduits in an asset or interface control diagram.
- Describe each interface. Select a connector and add its conveyed items, interface status, owner and interface requirements in the inspector.
- Set capacities. Enter the conduit's capacity and each item's data rate or size; the capacity check runs as you type.
- Review. Open Interfaces → Interface Register and filter by status.
- Publish the ICD. Click Export ICD Document (Word) in the ICD toolbar, or ICD on a register row for one interface.