Operations: the network operations centre watching every site, crews dispatched from it. The loop, step by step: 1. An operations centre watching a whole network. 2. The chain from source to console stands ready. 3. A station stops reporting at dusk. 4. Monitoring flags the silent station. 5. Each reading is stamped with time and place. 6. The last signed report fixes the fault time. 7. The relay forwards sealed packets untouched. 8. Signatures are checked before any model runs. 9. The edge ranks likely causes and nearby crews. 10. The edge releases confirmed results only. 11. A crew leaves for the site. 12. Sensors check that the response worked. 13. The centre follows the repair live. 14. The console shows the evidence with the alert. 15. The whole chain is archived for audit. 16. Everything settles back to idle.

01 / 16

An operations centre watching a whole network

Nexus Observatory

Operations centre

Every node watched. Every incident closed.

Monitoring of fleets, sites and links around the clock where contracted, incident response from first alarm to root cause, managed services that run the network for you, and service levels written as numbers you can measure on your own dashboard.

Plan with usReference architectureThe open protocol

At a glance

Every node watched, every incident closed

The operations centre monitors fleets, sites and links around the clock where contracted, responds to incidents from first alarm to root cause, runs managed services and writes service levels as numbers you can measure. Every node has an owner on every shift, and every alarm ends with a recorded cause and a verified fix.

The problem

Alarms nobody owns

Networks generate alarms day and night. Without a team that owns them, alarms are muted, incidents repeat and service levels are argued about instead of measured. Nobody can say how well the network is really performing, or what each outage cost the people relying on it.

Components

Pole-mounted edge gateway node
Particulate monitoring station and sensor node
Radar stream gauge on a road bridge
Street small-cell pole with an air-quality node
“AI tower in a box”
Data hall row pair with cold-aisle containment
Network operations centre with a curved video wall
Field-service crew vehicle

Interfaces

Instruments: SDI-12 · RS-485 / Modbus RTU · 4–20 mA
Radio: Ethernet · LTE-M / NB-IoT · LoRaWAN
Time and position: GNSS 1PPS
Security: TPM 2.0
Publishing: MQTT

Where it works

Uptime, completeness and repairs, on record

In the story below

The system, part by part
Assembly
Installation
Deployment
Connections
Operation
Failure and recovery
Scale and federation
What you get

Scenes · 18

Next steps

Plan a deployment Get support See Managed services Talk to sales

The problem
Alarms nobody owns
Networks generate alarms day and night. Without a team that owns them, alarms are muted, incidents repeat and service levels are argued about instead of measured. Nobody can say how well the network is really performing, or what each outage cost the people relying on it.
What it does
Every node watched, every incident closed
The operations centre monitors fleets, sites and links around the clock where contracted, responds to incidents from first alarm to root cause, runs managed services and writes service levels as numbers you can measure. Every node has an owner on every shift, and every alarm ends with a recorded cause and a verified fix.
The system
One station, part by part
Before anything is installed, the station is laid out as its parts: instrument, logger and edge compute, secure element, GNSS timing, radio, power, enclosure, wiring, earthing, mast and foundation.
Assembly
Built and tested before it ships
Each part is fitted to the pole and the enclosure, wired through surge protection to one earth, powered and bench-tested until it signs its first reading.
Installation
Installed on site
The crew arrives with the tested kit: foundation, mast raised and guyed, instruments mounted, cables run in conduit, the enclosure fitted out and the site commissioned.
Deployment
Site after site, one design
The same station goes in at every site on the plan, each commissioned against the same checklist, until the field is covered.
Wiring
Signal, power and time, wired
Inside one site the instrument’s signal pair runs to the logger, solar charges the battery that feeds the load, GNSS time reaches the clock and the logger hands its records to the radio.
Connections
Backhaul, time and power
The relay carries every site to the edge over a point-to-point link, the grandmaster’s time reaches every clock, and each site keeps its power through the night.
Time
Every event on one timeline
Alarms, changes, readings and repairs are stamped against the same disciplined clock, so the timeline of an incident can be rebuilt exactly. Root cause analysis starts from facts, not from the order in which people remember things happening, and the timeline is kept with the incident record.
Service levels
Written as numbers you can measure
Availability, data completeness and restoration times are defined in the contract and measured from the same data you can see on your own dashboard. Breaches are reported with their cause and the action taken, never hidden in an average. Credits for missed levels are automatic.
See Service levels
Reporting
Uptime, completeness and repairs, on record
Monthly reports show what happened, what was fixed and what changed, each line traceable to the incident and the data behind it. Reports are delivered on a fixed schedule and kept, so trends over months and years are easy to see.
See Reporting
Monitoring
Fleets, sites and links, in one view
Every node’s health, data completeness and links are shown together, with the trend that matters for each, so a problem is seen as a pattern before it becomes an outage. Thresholds and baselines are set per node and per site, so an alert means something and is never ignored as noise.
See Monitoring
Incident response
From first alarm to root cause
An alarm opens an incident with its evidence and runbook; responders contain it, restore service and record the root cause, and the fix is verified before the incident closes. Post-incident reviews feed back into the runbooks and the design, so the same failure is not suffered twice.
See Incident response
Dispatch
The right crew with the right part
When a remote fix is not enough, a work order goes to the field crew with the node’s record, the fault and the parts list. Parts, tools and access are arranged before the crew leaves, so a visit fixes the fault the first time.
Change
Changes planned, staged and reversible
Every change to the network is planned, staged in rings and reversible, with the operations team watching the health gates. Changes are scheduled around the network’s busy periods, and every change has an owner and a way back. Nothing changes without a recorded owner.
How it scales
Automation first, people for judgement
Routine detection, triage and recovery are automated; people handle judgement and exceptions. That is how one team can run a growing fleet without the service level slipping. Each automated action is logged and reviewed, so the automation itself is monitored like everything else.
Managed services
We run it; you use what it observes
The status and incident record format is open. Managed Site, network operations and service-level reporting are contracted; pricing follows the sites and the service levels chosen, and changes as the network grows. You keep the data and the records; we keep the network healthy, updated, calibrated and repaired to the levels agreed.
See Managed services Talk to sales
Next step
Hand us the night shift
Tell us what you run and what it must achieve. We propose the monitoring, the response and the service levels. The proposal states the service levels, the reporting and the escalation path before anything changes hands; we take over without losing the network’s history.
Plan a deployment Get support

See it from every side.

Each opens as a full-screen presentation: deeper pages on the same subject, explainers, stories, guided tours of the places, network scenes and the observatories that came before.

All presentations