Physical. Logical. Service. One record.
Model every duct, fibre, port and circuit from the chamber to the customer service, and see what depends on what.
| PORT | DEVICE | CIRCUIT | SERVICE | STATE |
|---|---|---|---|---|
| xe-1/0/0 | RTR-MAN-01 | CCT-LL-00402 | L3 IP transit 10G | Up |
| xe-1/0/1 | RTR-MAN-01 | CCT-LL-00407 | L2 Ethernet 1G | Up |
| xe-1/0/2 | RTR-MAN-01 | CCT-BH-00031 | Backhaul OLT-SAL-04 | Degraded |
| xe-1/0/3 | RTR-MAN-01 | CCT-LL-00419 | L2 Ethernet 1G | Alert |
| xe-1/0/4 | RTR-MAN-01 | — | Spare | Free |
| ge-0/0/12 | SW-MAN-03 | CCT-LL-00388 | L2 Ethernet 100M | Up |
| ge-0/0/13 | SW-MAN-03 | CCT-LL-00391 | L2 Ethernet 1G | Up |
| och-1/1 | MUX-MAN-01 | OCH-1550.12 | DWDM λ12 to LDS | Up |
From duct to splice, drawn on the map
Record ducts, chambers, cables, joints, splitters and ODFs against real geography. Every fibre keeps its path, so a cut shows its exact position and the premises behind it.
- Ducts, chambers, poles and cables on OS base maps
- Splice records and splitter trees per joint
- Loss budgets calculated per path
- Import from GIS, CAD and spreadsheets
Every layer of a circuit, end to end
Model SDH, DWDM and OTN paths alongside IP and Ethernet services. Leased lines, VLANs and prefixes sit on the same record as the fibre and ports that carry them.
- SDH, DWDM and OTN trails with wavelength plans
- IPAM with prefixes, VLANs and VRFs
- Leased lines with A and B ends, supplier and contract
- Layered view from fibre to service
Sites, racks, devices and every patch
Rack elevations, power and cabling, with cross-connects traced to the customer. IPAM allocations stay tied to the interfaces that use them.
- Rack elevations with power and weight
- Port-level patching and cross-connects
- Device lifecycle and warranty
- Floor plans for halls and cages
- Power
- 2 × 650 W · A+B
- Mgmt
- 10.24.8.17/32
- X-conn
- XC-0931 → [CUSTOMER]
Know who is affected before the phone rings
Select any resource, or let an alert select it for you, and Netcosm walks the dependency graph to the services and customers that rely on it.
- Dependency graph across all layers
- Affected customers, SLAs and premises counts
- Planned-work impact before approval
- One click from alert to ticket
The inventory is what the SIEM reads
Each security event is matched by IP, hostname or interface to an inventory record, then followed through the dependency graph. There is no export, no sync job and no second tool.
Integrations
[PLACEHOLDER: confirm supported list]Questions engineers ask
Can we migrate from spreadsheets, NetBox or an existing OSS?
Yes. We map your existing exports to the Netcosm data model and run a trial import into a separate tenant before cut-over. [PLACEHOLDER: typical migration time]
Do we have to use the SIEM to use the inventory?
No. Each capability can be licensed on its own. The link between them is available as soon as both are enabled.
Where is our data hosted?
All customer data is stored and processed in UK regions. [PLACEHOLDER: confirm provider and region]
Is there anything to install?
No servers. Log collection uses a lightweight forwarder or direct syslog to a UK endpoint; everything else runs in the browser.
How do you model splices and splitters?
Joints hold splice trays with fibre-to-fibre records; splitters are first-class objects with ratio and port mapping, so light paths can be traced end to end.
Is there an API?
Every object is available through a documented REST API with webhooks for changes, so your provisioning and billing systems can read and write the same record.
Bring a sample of your network
Send us an export from your current records and we will load it into a demo tenant before the call.