Composition — networks
Selira Relay
Sites, cabinets, spans and field work as one operation — what the inventory says, what monitoring sees and what the engineer found, side by side. Relay shows where they disagree, and since when. The newest composition, it starts from the field-service demo — sites, crews, dispatch — on sample data.
A composition is the platform already configured for one kind of operation — its things, its words, its systems. You start here and change it, not from an empty model.
Where it gives first
Lay a new demand on the network as it actually runs
A business asks for 10G by March. The demand is laid on the real path at the busy hour, forecast to March — the cabinet, the exchange, and the ring's other side if a span is cut — each taken as the network actually runs, not as it was designed. Where it would break the ring's protection, Relay says so and prepares the ways round it, each with its price. A scenario, with illustrative numbers: modelling like this is where Relay is going.
Dense by nature, best on a larger screen
[ fig. 1 · relay · a scenario · 11/11 · 10G by 12 Mar · ring protected ]
The questions it is built around
What is actually in that cabinet?
The inventory says a card is in a slot. Monitoring says the port is dark. The engineer who swapped it eight months ago wrote it in a spreadsheet that never made it back.
- Actually there
- What is in this cabinet according to each system, and did anyone physically confirm it?
- Audit gap
- Where does the inventory assert equipment that no field visit has confirmed since last year?
- Along a path
- Everything on this span, across sites, including what is installed inside something else.
- Who can touch it
- Which engineers are currently authorised for this equipment at this site, and until when?
What the composition contains
The physical network
Sites, cabinets, racks, shelves, slots and spans as walkable containment, including equipment that contains other equipment.
Equipment and serials
Serialised units with their placement history, so a card that moved three times has three claims, not one overwritten field.
Field work
Visits, tasks and confirmations as claims under the engineer’s authority — the strongest evidence in the estate, and usually the least integrated.
Source bindings
Inventory, operational support and field systems each keeping their own version, with conflicts surfaced rather than resolved.
Authorisation
Competencies and site access with validity windows, so “who may do this” is answerable as of a date.
The audit view
The gap between what is asserted and what has been confirmed, ranked by how long it has been since anybody looked.
Bring the cabinet nobody is sure about.
We will show you every system's version, how strong each one is, and when anybody last confirmed it.