---
title: "Managed services: Operations centre | Nexus Observatory"
description: "Managed services, inside Operations centre: service management, network operations centre, managed site operations, preventive maintenance and more."
url: https://observatory.global/operations/managed-services/
publisher: Nexus Observatory Inc.
updated: 2026-11-07
---

[Nexus Observatory](https://observatory.global/)

/

[Operations centre](https://observatory.global/operations/)

/

**Managed services** 

# We run it; you use what it observes.

Managed services, inside Operations centre: service management, network operations centre, managed site operations, preventive maintenance and more. Every item is traced to its specification, from ISO/IEC 20000-1:2018 to IETF RFC 3411 (SNMPv3), and runs on the open Observatory Protocol.

[Plan with us](https://observatory.global/contact/)

Architecture

[The protocol](https://observatory.global/protocol/specification/)

**Technologies**: 5
**At the frontier**: 0
**Protocol functions**: 3 of 12
**Industries served**: 3

At a glance

## Service management

Defined processes for incidents, problems, changes and service levels. In managed services, part of Operations centre, the operations, NOC, support and training layer holds service management, drawn against ISO/IEC 20000-1:2018 and used beside managed site operations on the same sites.

The problem

### We run it; you use what it observes

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.

Key facts

**Specification**: ISO/IEC 20000-1:2018
**Specification**: ISO/IEC 20000-1:2018 · ISO 55001:2024
**Specification**: ISO/IEC 20000-1:2018 · IETF RFC 3411 (SNMPv3)
**Specification**: ISO 17359 (condition monitoring guidelines) · ISO 13374 (data processing and communication)
**Specification**: EN 13306 (maintenance terminology) · IEC 60300-3-11 (reliability-centred maintenance)

Components

- Deployable field shelter with environmental control
- 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

**Radio**: Ethernet · Satellite (LEO/GEO)

Where it works

- Managed site operations
- Condition monitoring

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 · 13

Next steps

[Plan a deployment](https://observatory.global/operations/contact/deployment/)

[Open the Field Deployment Studio](https://observatory.global/studio/)

[See Operations centre](https://observatory.global/operations/)

[See Managed services](https://observatory.global/operations/managed-services/)

1. Operations centre · Managed services We run it; you use what it observes 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 Service management Defined processes for incidents, problems, changes and service levels. In managed services, part of Operations centre, the operations, NOC, support and training layer holds service management, drawn against ISO/IEC 20000-1:2018 and used beside managed site operations on the same sites. SpecificationISO/IEC 20000-1:2018
3. Operations, NOC, support and training Managed site operations Operating a site for a customer under an agreed plan, scope and reporting. In managed services, part of Operations centre, the operations, NOC, support and training layer holds managed site operations, drawn against ISO/IEC 20000-1:2018 and ISO 55001:2024. We build it into every site for managed services against that standard, and keep its version and its test results on the site’s record. SpecificationISO/IEC 20000-1:2018 · ISO 55001:2024
4. Operations, NOC, support and training Network operations centre Round-the-clock monitoring, alarms, triage and dispatch for every node. In managed services, part of Operations centre, the operations, NOC, support and training layer holds network operations centre, drawn against ISO/IEC 20000-1:2018 and IETF RFC 3411. We build it into every site for managed services against that standard, and keep its version and its test results on the site’s record. SpecificationISO/IEC 20000-1:2018 · IETF RFC 3411 (SNMPv3)
5. Maintenance Condition monitoring Using health data from nodes and power systems to plan interventions. In managed services, part of Operations centre, the maintenance, spares, refurbishment and upgrades layer holds condition monitoring, drawn against ISO 17359 and ISO 13374. We build it into every site for managed services against that standard, and keep its version and its test results on the site’s record. SpecificationISO 17359 (condition monitoring guidelines) · ISO 13374 (data processing and communication)
6. Maintenance Preventive maintenance Scheduled inspection, cleaning and replacement by asset class and environment. In managed services, part of Operations centre, the maintenance, spares, refurbishment and upgrades layer holds preventive maintenance, drawn against EN 13306 and IEC 60300-3-11. We build it into every site for managed services against that standard, and keep its version and its test results on the site’s record. SpecificationEN 13306 (maintenance terminology) · IEC 60300-3-11 (reliability-centred maintenance)
7. Evidence Traced to its specifications We trace each part of managed services to its specification: ISO/IEC 20000-1:2018, EN 13306 and IEC 60300-3-11. We keep the versions, configurations and test results of managed services as signed records, so a buyer or an auditor can check what was delivered against what was specified. StandardsISO/IEC 20000-1:2018 · EN 13306 · IEC 60300-3-11 · IETF RFC 3411
8. Operations Every node watched, every incident closed The operations console shows every node of a network for managed services with its state, its plan and its evidence. An alert arrives with its data and a runbook, acknowledging it opens a work order, and an incident for managed services closes only when the operator records the cause and verifies the fix.
9. Field service One crew, from survey to repair One crew surveys, installs, commissions, calibrates and repairs the sites for managed services, working from each site’s own record. Each visit updates that record, so the next crew knows what is on a site for managed services, when it was last checked and why it changed, and plans spares from that history.
10. Updates Updates in rings, with rollback Software and configuration reach a fleet for managed services in rings: one canary site first, then a few, then all, each ring gated on health and data completeness. A failed gate stops the wave, and each node for managed services returns to its last good release without a site visit.
11. How it scales One base unit, repeated A network for managed services starts with one base node and the instruments it reads. A station adds power and radio, a site adds a relay and a fleet repeats the proven site, so capacity for managed services grows by adding units, never by replacing what works.
12. 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/)
13. Next step Managed services, planned with you Tell us the sites, the systems managed services must work with and the outcome you need, with a map or a list of addresses if you have one. An engineer replies with a survey proposal, a design and a scope for managed services, and the plan grows from one site to the network you need. [Plan a deployment](https://observatory.global/operations/contact/deployment/) [Open the Field Deployment Studio](https://observatory.global/studio/) [See Operations centre](https://observatory.global/operations/)

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 **Deployable incident observatory**](https://observatory.global/use-cases/deployable-incident/)

[Use case **Avalanche detection site**](https://observatory.global/use-cases/avalanche-detection/)

[ISIC section · ISIC O **Public administration and defence; compulsory social security**](https://observatory.global/industries/o-public-administration-and-defence-compulsory-social-security/)

[Sector **Sports and events**](https://observatory.global/sectors/sports-events/)

### Explainers

[Explainer · Defence-adjacent (civil dual-use) **Defence-adjacent (civil dual-use) — Sectors** Lawful civil dual-use sensing only: northern observatories, satellite reach at high latitude, maritime safety and ice, and critical-infrastructure resilience.](https://observatory.global/industries/resilience/explainer/)

[Explainer · Sports and events **Sports and events, explained**](https://observatory.global/industries/events/explainer/)

[Platform **Operations centre** Alarms nobody owns](https://observatory.global/operations/)

[Platform **Connectivity** Public networks were not built for this site](https://observatory.global/connectivity/)

### 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 · Forest and wildfire **Seeing smoke sooner** A fire is cheapest to fight in its first hour. Ridge-top cameras, weather in the stand and satellite hot spots each see it at different times and scales;…](https://observatory.global/stories/wildfire/)

### Places and networks

[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 **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 **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 · Backhaul · Fresnel zone **Microwave backhaul across a river valley** An 18 GHz hop from the church tower to a mast on the far side of the flood plain: its first Fresnel zone, clearance over the town and trees, and what a new building in the path…](https://observatory.global/environments/networks/backhaul-fresnel/)

### 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 · United States · 1921 **Caltech Seismological Laboratory** A laboratory in Pasadena that gave earthquakes a number. The Richter magnitude scale of 1935 depended on one instrument type in many places, a lesson as relevant to networks today…](https://observatory.global/observatories/caltech-seismo-lab/)

### 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 it is

## Operations, NOC, support and training.

Everything that happens on the ground across a site's life: survey, permits, design packs, logistics, installation, acceptance, training, operations, maintenance, upgrades, decommission and recycling, done safely and recorded as evidence. Each technology below carries what it is, what we do with it, and the standard it is drawn against.

Field operations and lifecycle

### Service management

Defined processes for incidents, problems, changes and service levels.

We operate and support.

ISO/IEC 20000-1:2018

Field operations and lifecycle

### Network operations centre

Round-the-clock monitoring, alarms, triage and dispatch for every node.

We operate and support.

ISO/IEC 20000-1:2018 · IETF RFC 3411 (SNMPv3)

Field operations and lifecycle

### Managed site operations

Operating a site for a customer under an agreed plan, scope and reporting.

We operate, maintain and support.

ISO/IEC 20000-1:2018 · ISO 55001:2024

Field operations and lifecycle

### Preventive maintenance

Scheduled inspection, cleaning and replacement by asset class and environment.

We design and maintain.

EN 13306 (maintenance terminology) · IEC 60300-3-11 (reliability-centred maintenance)

Field operations and lifecycle

### Condition monitoring

Using health data from nodes and power systems to plan interventions.

We design, operate and maintain.

ISO 17359 (condition monitoring guidelines) · ISO 13374 (data processing and communication)

**02** Architecture

## Where it sits, and what it speaks.

Managed services draws on the spectrum below; the highlighted layers carry this area, and the protocol functions it speaks are marked.

Edge tiers and multi-access edge computing

9

Modular edge data centres and the AI tower in a box

8

Servers and accelerators

8

Storage and edge data management

6

Cooling and ruggedisation

10

Kubernetes and fleet orchestration

8

OTA updates, GitOps and software supply chain

8

Confidential computing and hardware trust

8

Device identity and attestation

8

PKI, secure boot and updates

7

Zero trust and network security

7

5G and wireless security

6

OT security and software supply chain

9

Privacy and data protection

7

Keys, cryptography and post-quantum migration

9

Monitoring, incident response and governance

8

01**Join** Identity, attestation quote, signed policy.

02**Admit** Admitted for a stated scope, nothing wider.

03**Describe** What, where, how and by whom, with calibration.

04**Time** One clock across the grid, with its error bound.

05**Observe** Every value with quality and provenance.

06**Qualify** Tested against the specification, state on record.

07**Federate** Signed exchange across grids and trust domains.

08**Orchestrate** Software and configuration by signed plan.

09**Correct** A correction marks what depends on it and publishes a new version.

10**Exchange** Products reach people and applications through versioned interfaces.

11**Prove** Signed proof receipts that an independent verifier can check.

12**Exit and decommission** An open exit path, and a record that closes.

**03** On the grid

## Every site joins one observing grid.

The open networks on the grid today, over real relief and the geodesic cells we count them into. A site built here enrols into the same grid.

## The observing grid

1. Open instruments on the observing grid.

**04** In the field

## Where this runs, sector by sector.

Deployment scenarios from the sector research that rely on managed services.

[Communities and rural Interim public-safety broadband where no national network exists Private LTE or 5G for fire and medical services in territories without a national public-safety network.](https://observatory.global/sectors/communities/)

[Government and public safety Deployable communications and sensing for incident command A cell on wheels with satellite backhaul, mesh telemetry and environment nodes at the incident base.](https://observatory.global/sectors/public-safety/)

[Industrial Mine-wide private LTE or 5G with environmental sensing Autonomy communications plus dust, blast vibration, slope and tailings monitoring.](https://observatory.global/sectors/industrial/)

[Industrial Continuous methane monitoring Fenceline sensors and optical gas imaging under regulatory leak-detection cadences.](https://observatory.global/sectors/industrial/)

[Agriculture Farm or cooperative agromet network with crop models Compact stations and soil probes feeding irrigation, disease and frost models.](https://observatory.global/sectors/agriculture/)

[Sports and events Stadium neutral-host 5G with crowd and environment sensing A private operations slice beside the carriers' network, with heat, air and lightning sensing.](https://observatory.global/sectors/sports-events/)

**05** Open and enterprise

## Open by default. Enterprise by contract.

The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.

Open, on the main site

- Status and incident record format

Enterprise, on this site

- Managed Site
- Network operations
- Service-level reporting

**06** The rest of the line

## Operations centre, area by area.

[Operations centre Monitoring Fleets, sites and links, in one view.](https://observatory.global/operations/monitoring/)

[Operations centre Incident response From first alarm to root cause.](https://observatory.global/operations/incident-response/)

[Operations centre Service levels Written as numbers you can measure.](https://observatory.global/operations/service-levels/)

[Operations centre Reporting Uptime, completeness and repairs, on record.](https://observatory.global/operations/reporting/)

## Bring us the site.

Survey, design, deployment and operation for managed services. The form names who receives your details.

[Talk to us](https://observatory.global/contact/)

[Ask for a quote](https://observatory.global/contact/sales-enquiry/)

[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/)
