Monitoring: heartbeats from every node arriving on the operations screens. The loop, step by step: 1. A wall of screens and a watching desk. 2. The chain from source to console stands ready. 3. Health lights show every site in green. 4. Each reading is stamped with time and place. 5. One site’s link quality starts to drift. 6. The edge verifies every signature first. 7. The monitor ranks the drift against baseline. 8. Only a confirmed result leaves the edge. 9. A warning reaches the duty engineer. 10. Relays carry the packets without reading them. 11. The engineer retunes the link remotely. 12. Sensors check that the response worked. 13. The light returns to green. 14. The alert arrives with its evidence attached. 15. Record, proof and action are archived together. 16. Everything settles back to idle.

01 / 16

A wall of screens and a watching desk

/

/

Monitoring, inside Operations centre: telemetry for software, metrics exposition, network and device management interfaces, data quality monitoring and more. Every item is traced to its specification, from OpenTelemetry specification (CNCF) to W3C Trace Context, and runs on the open Observatory Protocol.

Technologies

5

At the frontier

0

Protocol functions

3 of 12

Industries served

3

At a glance

Telemetry for software

Traces, metrics and logs from every service and agent in one model. In monitoring, part of Operations centre, the digital twins and observability layer holds telemetry for software, drawn against OpenTelemetry specification and W3C Trace Context and used beside data quality monitoring on the same sites.

সমস্যা

Fleets, sites and links, in one view

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

OpenTelemetry specification (CNCF) · W3C Trace Context

Specification

ISO 8000-8 (data quality measurement) · ISO 19157-1:2023

Specification

OpenMetrics (CNCF)

Specification

IETF RFC 6241 (NETCONF) · IETF RFC 7950 (YANG 1.1)

Specification

NIST SP 800-92 (log management)

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

উপকরণসমূহ

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

• Data quality monitoring
• Network and device management interfaces

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

1. Operations centre · Monitoring

   Fleets, sites and links, in one view

   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

   Telemetry for software

   Traces, metrics and logs from every service and agent in one model. In monitoring, part of Operations centre, the digital twins and observability layer holds telemetry for software, drawn against OpenTelemetry specification and W3C Trace Context and used beside data quality monitoring on the same sites.

   Specification

   OpenTelemetry specification (CNCF) · W3C Trace Context

3. Digital twins and observability

   Data quality monitoring

   Completeness, latency, validity and drift tracked per stream with alerts. In monitoring, part of Operations centre, the digital twins and observability layer holds data quality monitoring, drawn against ISO 8000-8 and ISO 19157-1:2023. We build it into every site for monitoring against that standard, and keep its version and its test results on the site’s record.

   Specification

   ISO 8000-8 (data quality measurement) · ISO 19157-1:2023

4. Digital twins and observability

   Metrics exposition

   Standard metric formats scraped from nodes and services. In monitoring, part of Operations centre, the digital twins and observability layer holds metrics exposition, drawn against OpenMetrics. We build it into every site for monitoring against that standard, and keep its version and its test results on the site’s record.

   Specification

   OpenMetrics (CNCF)

5. Digital twins and observability

   Network and device management interfaces

   Configuration and monitoring of network elements and appliances. In monitoring, part of Operations centre, the digital twins and observability layer holds network and device management interfaces, drawn against IETF RFC 6241 and IETF RFC 7950. We build it into every site for monitoring against that standard, and keep its version and its test results on the site’s record.

   Specification

   IETF RFC 6241 (NETCONF) · IETF RFC 7950 (YANG 1.1)

6. পর্যবেক্ষণ

   Security monitoring and logging

   Central collection and correlation of device, network and application events. In monitoring, part of Operations centre, the monitoring, incident response and governance layer holds security monitoring and logging, drawn against NIST SP 800-92. We build it into every site for monitoring against that standard, and keep its version and its test results on the site’s record.

   Specification

   NIST SP 800-92 (log management)

7. প্রমাণ

   Traced to its specifications

   We trace each part of monitoring to its specification: OpenTelemetry specification, W3C Trace Context and NIST SP 800-92. We keep the versions, configurations and test results of monitoring as signed records, so a buyer or an auditor can check what was delivered against what was specified.

   মানদণ্ড

   OpenTelemetry specification · W3C Trace Context · NIST SP 800-92 · OpenMetrics

8. Operations

   Every node watched, every incident closed

   The operations console shows every node of a network for monitoring 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 monitoring 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 monitoring, working from each site’s own record. Each visit updates that record, so the next crew knows what is on a site for monitoring, when it was last checked and why it changed, and plans spares from that history.

10. হালনাগাদ

    Updates in rings, with rollback

    Software and configuration reach a fleet for monitoring 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 monitoring returns to its last good release without a site visit.

11. How it scales

    One base unit, repeated

    A network for monitoring 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 monitoring 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 servicesTalk to sales

13. Next step

    Monitoring, planned with you

    Tell us the sites, the systems monitoring 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 monitoring, and the plan grows from one site to the network you need.

    Plan a deploymentOpen the Field Deployment StudioSee Operations centre

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.

In depth

Explainers

Stories

Places and networks

Heritage observatories

Interactive tools

01এটি কী

Digital twins and observability.

How observations move from the edge into stores, catalogues and APIs with their provenance, licence and residency attached, and how they interoperate through open standards and the open Observatory Protocol. How every node proves what it is and what it runs, how links and keys are protected, how software is traced to its source, how personal data is minimised, and how incidents are found and handled. Each technology below carries what it is, what we do with it, and the standard it is drawn against.

02Architecture

Where it sits, and what it speaks.

Monitoring 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যোগ দিন Identity, attestation quote, signed policy.

02Admit Admitted for a stated scope, nothing wider.

03বর্ণনা করুন What, where, how and by whom, with calibration.

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

05Observe Every value with quality and provenance.

06Qualify Tested against the specification, state on record.

07Federate Signed exchange across grids and trust domains.

08Orchestrate Software and configuration by signed plan.

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

10Exchange Products reach people and applications through versioned interfaces.

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

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

03On 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.

04In the field

Where this runs, sector by sector.

Deployment scenarios from the sector research that rely on monitoring.

05Open 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

06The rest of the line

Operations centre, area by area.

Bring us the site.

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