Skip to content
Skip to contentNexus Observatory

Reporting: the month’s records compiled into the customer report, each figure traceable. The loop, step by step: 1. An archive, a report and a reader. 2. Sensor, link, edge and console stand ready. 3. The month closes and the archive freezes. 4. Each reading is stamped with time and place. 5. The edge verifies every signature first. 6. Figures are computed from the signed record. 7. Only a confirmed result leaves the edge. 8. The report is built from those figures. 9. Relays carry the packets without reading them. 10. It is sealed with a signature and a date. 11. The reader opens it at the desk. 12. The alert arrives with its evidence attached. 13. Each number links back to its source. 14. Sensors check that the response worked. 15. The whole chain is archived for audit. 16. Everything settles back to idle.

01 / 16

An archive, a report and a reader

Nexus Observatory

/

Operations centre

/

Reporting
Uptime, completeness and repairs, on record.

Reporting, inside Operations centre: records management, inspection records, provenance, energy metering. Every item is traced to its specification, from ISO 15489-1:2016 to ISO 9001:2015 (documented information), and runs on the open Observatory Protocol.

Plan with usArchitectureThe protocol
Technologies
4
At the frontier
0
Protocol functions
3 of 12
Industries served
3

At a glance

Records management

Authentic, reliable and retrievable records for every site and asset. In reporting, part of Operations centre, the health, safety and evidence records layer holds records management, drawn against ISO 15489-1:2016 and ISO 9001:2015. We build it into every site for reporting against that standard, and keep its version and its test results on the site’s record.

مسئله

Uptime, completeness and repairs, on record

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 15489-1:2016 · ISO 9001:2015 (documented information)
Specification
IEC 62053 series (electricity metering)
Specification
ISO/IEC 17020 (inspection bodies)
Specification
W3C PROV-O · W3C PROV-DM
استانداردها
ISO 15489-1:2016 · ISO 9001:2015 · W3C PROV-O · W3C PROV-DM

Components

  • Rugged field tablet on a mast bracket
  • 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
Wi-Fi · LTE / 5G

Where it works

  • Inspection records

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 deploymentOpen the Field Deployment StudioSee Operations centreSee Managed services
  1. Operations centre · Reporting

    Uptime, completeness and repairs, on record

    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

    Records management

    Authentic, reliable and retrievable records for every site and asset. In reporting, part of Operations centre, the health, safety and evidence records layer holds records management, drawn against ISO 15489-1:2016 and ISO 9001:2015. We build it into every site for reporting against that standard, and keep its version and its test results on the site’s record.

    Specification
    ISO 15489-1:2016 · ISO 9001:2015 (documented information)
  3. Energy management and monitoring

    Energy metering

    Revenue and sub-metering for loads, generation and tenants. In reporting, part of Operations centre, the energy management and monitoring layer holds energy metering, drawn against IEC 62053 series. We build it into every site for reporting against that standard, and keep its version and its test results on the site’s record.

    Specification
    IEC 62053 series (electricity metering)
  4. Health, safety and evidence records

    Inspection records

    Structured inspection reports with findings, photos and sign-off. In reporting, part of Operations centre, the health, safety and evidence records layer holds inspection records, drawn against ISO/IEC 17020. We build it into every site for reporting against that standard, and keep its version and its test results on the site’s record.

    Specification
    ISO/IEC 17020 (inspection bodies)
  5. Time and place

    When and where, on every record

    Every record made for reporting carries its time, from a clock disciplined by satellite time or a PTP grandmaster, with the position and siting record of the station that made it. When time or position degrades, the record for reporting says so, and every user downstream sees the same warning.

  6. Metadata, provenance and catalogues

    Provenance

    Who and what produced each value, from which inputs, by which process and when. In reporting, part of Operations centre, the metadata, provenance and catalogues layer holds provenance, drawn against W3C PROV-O and W3C PROV-DM. We build it into every site for reporting against that standard, and keep its version and its test results on the site’s record.

    Specification
    W3C PROV-O · W3C PROV-DM
  7. اعتماد

    Proved before it is trusted

    A node joins a network for reporting only after its hardware root of trust answers an attestation challenge. Its keys stay in secure hardware, its software arrives signed and every record it makes for reporting carries a signature, so anyone downstream can check where a value came from.

  8. شواهد

    Traced to its specifications

    We trace each part of reporting to its specification: ISO 15489-1:2016, ISO 9001:2015 and W3C PROV-O. We keep the versions, configurations and test results of reporting as signed records, so a buyer or an auditor can check what was delivered against what was specified.

    استانداردها
    ISO 15489-1:2016 · ISO 9001:2015 · W3C PROV-O · W3C PROV-DM
  9. Operations

    Every node watched, every incident closed

    The operations console shows every node of a network for reporting 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 reporting closes only when the operator records the cause and verifies the fix.

  10. تازه‌ها

    Updates in rings, with rollback

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

  11. How it scales

    One base unit, repeated

    A network for reporting 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 reporting 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

    Reporting, planned with you

    Tell us the sites, the systems reporting 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 reporting, 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.

All presentations

In depth

Use case Deployable incident observatoryISIC section · ISIC O Public administration and defence; compulsory social securityUse case Avalanche detection siteISIC section · ISIC R Arts, entertainment and recreation

Explainers

Explainer · Defence-adjacent (civil dual-use) Defence-adjacent (civil dual-use) — SectorsLawful civil dual-use sensing only: northern observatories, satellite reach at high latitude, maritime safety and ice, and critical-infrastructure resilience.Explainer · Government and public safety Government and public safetyWildfire 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.سکو Operations centreAlarms nobody ownsسکو Field servicesSites fail between contractors

Stories

Story · Resilient operations When the links failObserving systems matter most on the days infrastructure fails. Designing for that day means local autonomy, stored power, store-and-forward delivery and…Story · Airspace and drones A shared sky below 120 metresFlying 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…Story · Forest and wildfire Seeing smoke soonerA 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;…

Places and networks

Guided tour · Guided 3D tour Wildfire forestCamera masts on the ridges, a weather station in the stand and a private cell: the red ground is what the ridge camera can see.Guided tour · Guided 3D tour Mountain valley siteA 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…Guided tour · Guided 3D tour River basinWater-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.Network scene · NTN · Satellite Satellite direct to device in a mountain valleyWhere 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.Network scene · IoT · Mesh IoT in the city: a street-light mesh and LoRaWANStreet-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.

Heritage observatories

Heritage observatory · Global network of about 150 stations; USGS and EarthScope (formerly IRIS) partnership · 1984 Global Seismographic NetworkAbout 150 digital broadband seismic stations in some 80 countries, sending data to open archives within minutes.Heritage observatory · United States · 1921 Caltech Seismological LaboratoryA 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…

Interactive tools

Interactive tool · Plan a site Field Deployment StudioTerrain, devices, coverage, viewshed, power and the best spot for a station, then a deployment request with the plan attached.

01چیستی آن

Health, safety and evidence records.

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. 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 a remote site is powered, stored, distributed, cooled, sealed, tested, grounded, held up and kept safe, from a solar-powered sensor to a hybrid microgrid on a guyed mast. Each technology below carries what it is, what we do with it, and the standard it is drawn against.

Field operations and lifecycle

Records management

Authentic, reliable and retrievable records for every site and asset.

We design, operate and maintain.

ISO 15489-1:2016 · ISO 9001:2015 (documented information)

Field operations and lifecycle

Inspection records

Structured inspection reports with findings, photos and sign-off.

We deploy, operate and maintain.

ISO/IEC 17020 (inspection bodies)

Data, software and interoperability

Provenance

Who and what produced each value, from which inputs, by which process and when.

We design, integrate and operate.

W3C PROV-O · W3C PROV-DM

Power, energy and ruggedisation

Energy metering

Revenue and sub-metering for loads, generation and tenants.

We design, integrate and operate.

IEC 62053 series (electricity metering)

02Architecture

Where it sits, and what it speaks.

Reporting 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.

The observing grid

  1. Open instruments on the observing grid.

04In the field

Where this runs, sector by sector.

Deployment scenarios from the sector research that rely on reporting.

Environment and climate

Methane fenceline and site-level continuous monitoring

Regulatory cadences in the EU and reporting levels in voluntary frameworks.
Government and public safety

National GBON surface and upper-air network

WMO-grade stations reporting through WIS 2.0, funded through the systematic-observations financing pathway.
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.
Industrial

Mine-wide private LTE or 5G with environmental sensing

Autonomy communications plus dust, blast vibration, slope and tailings monitoring.
Industrial

Continuous methane monitoring

Fenceline sensors and optical gas imaging under regulatory leak-detection cadences.
کشاورزی

Farm or cooperative agromet network with crop models

Compact stations and soil probes feeding irrigation, disease and frost models.

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.

Operations centre

پایش

Fleets, sites and links, in one view.
Operations centre

Incident response

From first alarm to root cause.
Operations centre

Managed services

We run it; you use what it observes.
Operations centre

Service levels

Written as numbers you can measure.

Bring us the site.

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

Talk to usAsk for a quote

Uptime, completeness and repairs, on record.

Reporting, inside Operations centre: records management, inspection records, provenance, energy metering. Every item is traced to its specification, from ISO 15489-1:2016 to ISO 9001:2015 (documented information), and runs on the open Observatory Protocol.

01چیستی آن

02Architecture

Where it sits, and what it speaks.

03On the grid

04In the field

Where this runs, sector by sector.

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
    Enterprise, on this site
      06The rest of the line

      Bring us the site.