NEXUS AI / NETOPS
The telecom network you run, on the same map as the grid it keeps running.
NetOps manages the telecom network an electric distribution utility runs for itself — fibre, radio, racks and devices down to port level — and the joint-use contracts covering everyone else attached to its poles. Both sit against the electrical network model, so a telecom question is answered from the map.
A distribution utility runs a telecom network because the grid needs one. Protection, SCADA, substation telemetry and field communications all depend on it, and it grows the way the grid grows — one project at a time. The record ends up scattered: cables in the GIS if anywhere, racks and devices in a spreadsheet, circuits in an engineer's head, and the question of which substations go blind if a given route is cut answered by whoever has been there longest.
-
Hold the network as one record
Devices registered from a specification catalogue by manufacturer, model and technology. Inside plant modelled down to racks, frames, shelves, slots, cards and ports; fibre modelled to the splice.
-
Keep the circuits with the plant
The logical circuits that ride the fibre are held against the physical plant that carries them, so which protection or SCADA circuit runs over which fibre and which port is a lookup rather than an investigation.
-
Place it against the grid
Every telecom asset sits against the pole, structure, substation and feeder it depends on, read from the electrical network model. Which substations lose telemetry if this route is cut becomes the same kind of question as any other.
-
Plan change separately from the live record
Installations and upgrades are held in a design version, tracked from plan to as-built, with history retained across replacements — while operations keep working against the live record.
-
Stay honest about reality
The inventory is reconciled against the systems that already watch the network — the monitoring platform, the asset register — and what disagrees is presented as a list someone resolves, rather than silently overwritten.
Which substations go blind if this route is cut
Today that is answered by whoever has been there longest. Held against the network model, it is a trace.
Is there a free port, fibre or rack unit?
Capacity becomes a query instead of a site survey, because inside plant is modelled to the port and fibre to the splice.
A joint-use contract about to lapse
Pole-sharing agreements and the third-party equipment actually attached are both registered against the pole, with alerts ahead of expiry.
NetOps runs on its own, and gets better with the rest of the platform around it.
Gateway
Connects the GIS, the asset register and the monitoring platform once, and keeps them available to every pod.
Spatial Studio
Puts telecom alongside the electrical network, vegetation and joint use on one map, so overlapping risk is visible rather than inferred.
Workspace
Consolidates the results into reports and indicators — port utilization, spare capacity, asset lifecycle, contract exposure.
Assistant
Carries changes back into Smallworld, acting on the network model rather than only reporting on it.
Leaf Monitor
Brings vegetation risk against fibre routes, not only against conductors.
Each connection is made by API or by a direct database connection, and is defined once rather than per project.
- The electrical network model, through Gateway
- Direction: Read
- The monitoring platform and the asset register, through Gateway
- Direction: Read — for inventory reconciliation
- Spatial Studio
- Direction: The combined layer view
- Workspace
- Direction: Reports and indicators
| System | Direction |
|---|---|
| The electrical network model, through Gateway | Read |
| The monitoring platform and the asset register, through Gateway | Read — for inventory reconciliation |
| Spatial Studio | The combined layer view |
| Workspace | Reports and indicators |
Where it stops
- NetOps holds the record. Reconciliation shows where the record and reality disagree; a person resolves each one.
- It registers joint-use contracts and occupants. Invoicing against them stays in whatever system does that today.
- It carries a simplified telecom and joint-use map of its own. Seeing it alongside vegetation and the electrical network is what Spatial Studio is for.
Who can see what
People sign in with the corporate directory account they already have, and what they are allowed to see is enforced in four places: at the platform, inside each pod, on the map, and in the answers that come back to them.
Where it stands
Technical walkthrough · 8 min
See it in action — watch the 8-minute Nexus AI Platform walkthrough.
Recorded directly in the platform, with English narration and no slide deck. GIS, ERP, ADMS, and maintenance answering together, without replacing the systems you already run. The link arrives after you register.
Need to brief your leadership? The one-page brief
A technical session covers your estate, where the platform would run, and which pods come first.
Book a technical session