--- title: "Operations centre platform | Nexus Observatory" description: "Operations: the network operations centre watching every site, crews dispatched from it. An operations centre watching a whole network." url: https://observatory.global/operations/ publisher: Nexus Observatory Inc. updated: 2026-11-07 --- 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 us](https://observatory.global/contact/) Reference architecture [The open protocol](https://observatory.global/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 1. The system, part by part 2. Assembly 3. Installation 4. Deployment 5. Connections 6. Operation 7. Failure and recovery 8. Scale and federation 9. What you get Scenes · 18 Next steps [Plan a deployment](https://observatory.global/operations/contact/deployment/) [Get support](https://observatory.global/operations/contact/support/) [See Managed services](https://observatory.global/operations/managed-services/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) 1. 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. 2. 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. 3. 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. 4. 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. 5. 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. 6. 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. 7. 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. 8. 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. 9. 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. 10. 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](https://observatory.global/operations/service-levels/) 11. 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](https://observatory.global/operations/reporting/) 12. 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](https://observatory.global/operations/monitoring/) 13. 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](https://observatory.global/operations/incident-response/) 14. 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. 15. 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. 16. 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. 17. 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](https://observatory.global/operations/managed-services/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) 18. 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](https://observatory.global/operations/contact/deployment/) [Get support](https://observatory.global/operations/contact/support/) More presentations ## 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](https://observatory.global/presentations/) ### In depth [Use case **Avalanche detection site**](https://observatory.global/use-cases/avalanche-detection/) [Use case **Deployable incident observatory**](https://observatory.global/use-cases/deployable-incident/) [ISIC section · ISIC O **Public administration and defence; compulsory social security**](https://observatory.global/industries/o-public-administration-and-defence-compulsory-social-security/) [Use case **Stadium operations private 5G slice**](https://observatory.global/use-cases/stadium-5g/) ### Explainers [Explainer · Government and public safety **Government and public safety** Wildfire cameras on real terrain, GBON station density, street-flood alert thresholds, CAP alerting with the authority in the loop and the radio horizon of a deployable cell.](https://observatory.global/industries/public-safety/explainer/) [Explainer · Sports and events **Sports and events, explained**](https://observatory.global/industries/events/explainer/) ### Stories [Story · Resilient operations **When the links fail** Observing systems matter most on the days infrastructure fails. Designing for that day means local autonomy, stored power, store-and-forward delivery and…](https://observatory.global/stories/resilient-ops/) [Story · Mountains and avalanche terrain **Snowpack, slope and signal** Avalanche forecasting reasons about the likelihood and size of avalanches on given terrain. The observations behind it come from a few stations in hard…](https://observatory.global/stories/mountain-avalanche/) [Story · Airspace and drones **A shared sky below 120 metres** Flying beyond visual line of sight turns a drone from a camera on a stick into infrastructure. It needs a command link that holds, an identity others can…](https://observatory.global/stories/airspace-drones/) ### Places and networks [Guided tour · Guided 3D tour **Wildfire forest** Camera masts on the ridges, a weather station in the stand and a private cell: the red ground is what the ridge camera can see.](https://observatory.global/environments/wildfire-forest/) [Guided tour · Guided 3D tour **Mountain valley site** A private 5G tower, an automatic weather station, a compact radar and a seismic vault on real alpine terrain, joined to an edge data centre that admits, times and publishes every…](https://observatory.global/environments/mountain-valley/) [Guided tour · Guided 3D tour **River basin** Water-level gauges along a river valley floor, a weather station and an edge node: the red isoline is the ground that lies within a few metres of the lowest point of the reach.](https://observatory.global/environments/river-basin/) [Network scene · NTN · Satellite **Satellite direct to device in a mountain valley** Where the valley cell cannot reach, phones on the pass road connect straight to a low-orbit satellite, which relays through its feeder link to a gateway.](https://observatory.global/environments/networks/ntn-d2d/) [Network scene · IoT · Mesh **IoT in the city: a street-light mesh and LoRaWAN** Street-light controllers form a radio mesh that routes around a failed node to its border router, while meters and sensors report to a rooftop LoRaWAN gateway.](https://observatory.global/environments/networks/iot-city/) ### Heritage observatories [Heritage observatory · Global network of about 150 stations; USGS and EarthScope (formerly IRIS) partnership · 1984 **Global Seismographic Network** About 150 digital broadband seismic stations in some 80 countries, sending data to open archives within minutes.](https://observatory.global/observatories/iris-gsn/) [Heritage observatory · China · 132 **Zhang Heng's seismoscope** In 132 CE a court astronomer presented a bronze urn that, it was recorded, told the capital of an earthquake no one in Luoyang had felt. No original survives.](https://observatory.global/observatories/zhang-heng-seismoscope/) ### Interactive tools [Interactive tool · Configure a station **Station Builder** Configure a station part by part in 3D, check the rules as you go and request a quote for the assembly.](https://observatory.global/studio/builder/) **01** · What this platform covers ## Operations centre, area by area. Choose an area for its systems, standards, the industries it serves and how we deliver it. [01 Monitoring Fleets, sites and links, in one view.](https://observatory.global/operations/monitoring/) [02 Incident response From first alarm to root cause.](https://observatory.global/operations/incident-response/) [03 Managed services We run it; you use what it observes.](https://observatory.global/operations/managed-services/) [04 Service levels Written as numbers you can measure.](https://observatory.global/operations/service-levels/) [05 Reporting Uptime, completeness and repairs, on record.](https://observatory.global/operations/reporting/) **02** · Built on the open protocol ## One protocol under every platform. Marked: the functions this platform leans on hardest. The protocol itself is open, so what you build here runs anywhere the protocol runs. 01 JOIN 02 ADMIT 03 DESCRIBE 04 TIME 05 OBSERVE 06 QUALIFY 07 FEDERATE 08 ORCHESTRATE **03** · Open and enterprise ## Open by default. Enterprise by contract. The open layer lives on the main site, free to use and build on. Enterprise services are delivered under contract by Nexus Observatory Inc. Open, on the main site - Status and incident record format Enterprise, on this site - Managed Site - Network operations - Service-level reporting **04** · Industries served ## The industries that build on operations centre. Each industry has its own site: its use cases, its community and the enterprise path, with this platform among the systems behind it. [Industry **Public safety** Warning time, gained at the sensor.](https://observatory.global/industries/public-safety/) [Industry **Civil resilience** Infrastructure that reports before it fails.](https://observatory.global/industries/resilience/) [Industry **Events** Venues that sense and connect at peak load.](https://observatory.global/industries/events/) **05** · Every platform ## Every platform, one architecture. One platform for each technical area of our work, on the same protocol, the same data and the same design. [Protocol & Grid](https://observatory.global/grid-services/) [Software](https://observatory.global/software/) [Hardware & power](https://observatory.global/hardware/) [Sensors & instruments](https://observatory.global/sensors/) [Connectivity](https://observatory.global/connectivity/) [Edge compute & AI](https://observatory.global/edge-ai/) [Earth observation & GeoAI](https://observatory.global/earth-observation/) [Field services](https://observatory.global/field-services/) [Data & licensing](https://observatory.global/data-products/) [Space and satellite systems](https://observatory.global/space/) [Positioning, navigation and timing](https://observatory.global/pnt/) [Security and trust](https://observatory.global/security-trust/) [Digital twins and simulation](https://observatory.global/digital-twins/) [Design and integration](https://observatory.global/integration/) [Test and qualification](https://observatory.global/qualification/) [Operations centre](https://observatory.global/operations/) [Training and enablement](https://observatory.global/training/) [Frontier labs](https://observatory.global/labs/) ## Bring us the site. We bring the survey, the design and the crew. Nexus Observatory Inc. The form names who receives your details. [Talk to us](https://observatory.global/contact/) [Create account](https://observatory.global/register/) [Nexus Observatory](https://observatory.global/) **Operations centre** . Every node watched. Every incident closed. [Talk to us](https://observatory.global/contact/) Operations centre - [Overview](https://observatory.global/operations/) - [Areas](https://observatory.global/operations/areas/) - [Technologies](https://observatory.global/operations/technologies/) - [Architecture](https://observatory.global/operations/architecture/) - [Industries](https://observatory.global/operations/industries/) - [Resources](https://observatory.global/operations/resources/) - [Contact](https://observatory.global/operations/contact/) Platforms - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Positioning, navigation and timing](https://observatory.global/pnt/) - [Security and trust](https://observatory.global/security-trust/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Design and integration](https://observatory.global/integration/) - [Test and qualification](https://observatory.global/qualification/) - [Operations centre](https://observatory.global/operations/) - [Training and enablement](https://observatory.global/training/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Presentations](https://observatory.global/presentations/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Observatory Protocol](https://observatory.global/protocol/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Careers](https://observatory.global/contact/careers/) - [Press](https://observatory.global/contact/press/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/) [Status](https://status.observatory.global/) [Help translate](https://observatory.global/translate/)