Cross-connects live in a spreadsheet
Orders, patches and disconnects are tracked by hand, and the meet-me room drifts from the record.
Cross-connects are inventory objects with both ends, the customer and the order attached.
NETCOSM FOR DATA CENTRES
Every rack, port and cross-connect.
Model halls, cages, racks and cabling, track cross-connects to customers, and correlate access and device events.
Image: rack row and cross-connects, duotone in steel
What slows data centre operators down
Capacity questions take a survey
Free ports, power headroom and rack space are checked on site because nobody trusts the record.
Rack elevations, power and port occupancy kept current by the change process.
Access and device events are in different tools
Badge logs, PDU events and switch alerts are correlated after the fact, if at all.
One SIEM with the hall, cage and rack context on every event.
Across the facility lifecycle
The same record is used by sales engineering, provisioning, facilities and security.
- 01
Quote
Check space, power and port availability from the record, not a site visit.
DCIM - 02
Provision
Cross-connect and rack orders as workflows that update the inventory on completion.
Workflows - 03
Operate
Faults and planned work tied to the customers and cross-connects they affect.
Service desk · Impact - 04
Secure
Access, PDU and device events correlated with cage and rack.
SIEM - 05
Report
Per-customer inventory, SLA and security reports.
Reporting
"[PLACEHOLDER: data centre quote on migrating cross-connects from spreadsheets, subject to approval.]"
[X]kcross-connects migrated from spreadsheets in [X] weeks[PLACEHOLDER: needs sourced figure]
[X]%fewer site visits to confirm capacity[PLACEHOLDER: needs sourced figure]
[X] minfrom fault to affected-customer list[PLACEHOLDER: needs sourced figure]
Modules data centres start with
See one hall in Netcosm
Send us the rack and cross-connect records for one hall and we will load them into a demo tenant before the call.