Training engineers: a radio site designed, measured and tuned in the lab. The loop, step by step: 1. A bench, a radio unit and a monitor antenna. 2. Sensor, link, edge and console stand ready. 3. The engineer captures a live radio frame. 4. Each reading is stamped with time and place. 5. The capture reaches the analysis rack. 6. The relay forwards sealed packets untouched. 7. The edge verifies every signature first. 8. They decode each field against the standard. 9. Only a confirmed result leaves the edge. 10. They change a setting and watch the effect. 11. Sensors check that the response worked. 12. The lab report records what changed and why. 13. The console shows the evidence with the alert. 14. The whole chain is archived for audit. 15. Everything settles back to idle.

01 / 15

A bench, a radio unit and a monitor antenna

/

/

Engineers, inside Training and enablement: measurement uncertainty, field calibration and intercomparison, RF commissioning, node enrolment and attestation at first boot. Every item is traced to its specification, from JCGM 100:2008 (GUM) to JCGM 200:2012 (VIM), and runs on the open Observatory Protocol.

Technologies

4

At the frontier

0

Protocol functions

3 of 12

Industries served

3

At a glance

Measurement uncertainty

Uncertainty budgets that travel with every reading. In engineers, part of Training and enablement, the calibration, metadata and quality control layer holds measurement uncertainty, drawn against JCGM 100:2008 and JCGM 200:2012. We build it into every site for engineers against that standard, and keep its version and its test results on the site’s record.

The problem

Design, integration and the protocol in depth

Networks run for years; staff change. A system only the vendor understands is a system you rent forever, and one that degrades the day the vendor leaves. Training is how a network stays yours, and how its quality survives staff changes, contracts and years.

Key facts

Specification

JCGM 100:2008 (GUM) · JCGM 200:2012 (VIM)

Specification

WMO Regional Instrument Centres · WMO instrument intercomparisons

Specification

Observatory Protocol specification (open) · IETF RFC 9334

Specification

IEC 62037 series (passive intermodulation)

Standards

JCGM 100:2008 · JCGM 200:2012 · IEC 62037 series · WMO Regional Instrument Centres

Components

• Rugged shock-isolated 7U transit rack case, lids off
• Automatic weather station (AWS) to WMO siting practice
• Particulate monitoring station and sensor node
• Seismometer vault station (broadband, solar powered, GNSS-timed)
• LoRaWAN gateway, endpoint and soil probe
• Deployable field shelter with environmental control
• Data hall row pair with cold-aisle containment
• Operations console with a video wall

Interfaces

Radio

Ethernet

Time and position

PTP (IEEE 1588)

Where it works

• Node enrolment and attestation at first boot

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. Training and enablement · Engineers

   Design, integration and the protocol in depth

   Networks run for years; staff change. A system only the vendor understands is a system you rent forever, and one that degrades the day the vendor leaves. Training is how a network stays yours, and how its quality survives staff changes, contracts and years.

2. What it does

   Measurement uncertainty

   Uncertainty budgets that travel with every reading. In engineers, part of Training and enablement, the calibration, metadata and quality control layer holds measurement uncertainty, drawn against JCGM 100:2008 and JCGM 200:2012. We build it into every site for engineers against that standard, and keep its version and its test results on the site’s record.

   Specification

   JCGM 100:2008 (GUM) · JCGM 200:2012 (VIM)

3. Calibration

   Field calibration and intercomparison

   Travelling standards, field checks and intercomparisons between instruments. In engineers, part of Training and enablement, the calibration, metadata and quality control layer holds field calibration and intercomparison, drawn against WMO Regional Instrument Centres and WMO instrument intercomparisons. We build it into every site for engineers against that standard, and keep its version and its test results on the site’s record.

   Specification

   WMO Regional Instrument Centres · WMO instrument intercomparisons

4. Installation

   Node enrolment and attestation at first boot

   Each node enrols, attests and receives its first signed plan before going live. In engineers, part of Training and enablement, the installation, commissioning and acceptance layer holds node enrolment and attestation at first boot, drawn against Observatory Protocol specification and IETF RFC 9334.

   Specification

   Observatory Protocol specification (open) · IETF RFC 9334

5. Time and place

   When and where, on every record

   Every record made for engineers 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 engineers says so, and every user downstream sees the same warning.

6. Installation

   RF commissioning

   Antenna alignment, sweep, return loss and passive intermodulation checks. In engineers, part of Training and enablement, the installation, commissioning and acceptance layer holds RF commissioning, drawn against IEC 62037 series. We build it into every site for engineers against that standard, and keep its version and its test results on the site’s record.

   Specification

   IEC 62037 series (passive intermodulation)

7. Trust

   Proved before it is trusted

   A node joins a network for engineers 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 engineers carries a signature, so anyone downstream can check where a value came from.

8. Evidence

   Traced to its specifications

   We trace each part of engineers to its specification: JCGM 100:2008, JCGM 200:2012 and IEC 62037 series. We keep the versions, configurations and test results of engineers as signed records, so a buyer or an auditor can check what was delivered against what was specified.

   Standards

   JCGM 100:2008 · JCGM 200:2012 · IEC 62037 series · WMO Regional Instrument Centres

9. Operations

   Every node watched, every incident closed

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

10. Updates

    Updates in rings, with rollback

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

11. How it scales

    One base unit, repeated

    A network for engineers 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 engineers grows by adding units, never by replacing what works.

12. What you get

    Academy paths, on-site enablement

    Academy paths, guides and the glossary are open. Operator and technician training and on-site enablement are contracted; pricing follows the people trained and the sites involved, and the material remains available to your team. Courses can run on your site, at ours or remotely for the theory, with the practical parts always on real equipment.

    Start a learning pathTalk to sales

13. Next step

    Engineers, planned with you

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

    Plan a deploymentOpen the Field Deployment StudioSee Training and enablement

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

01What it is

Calibration, metadata and quality control.

Instruments placed in the air, water, ground and spectrum, from weather stations to seismometers, radars and cameras, with the calibration, metadata and quality control that make their readings evidence. 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.

02Architecture

Where it sits, and what it speaks.

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

Survey and site acquisition

8

Permitting and approvals

7

Design packs and logistics

8

Installation, commissioning and acceptance

9

Operations, NOC, support and training

8

Maintenance, spares, refurbishment and upgrades

10

Decommission and recycling

7

Health, safety and evidence records

9

Meteorology (WMO No. 8 classes)

10

Air quality and atmospheric composition

7

Hydrology and water

7

Ocean and coastal

7

Seismic, geodetic, geomagnetic and radiation

8

RF, acoustics, cameras and radar

9

Calibration, metadata and quality control

7

Frontier and research

6

01Join Identity, attestation quote, signed policy.

02Admit Admitted for a stated scope, nothing wider.

03Describe 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 engineers.

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

• Academy paths
• Guides and glossary

Enterprise, on this site

• Operator and technician training
• On-site enablement

06The rest of the line

Training and enablement, area by area.

Bring us the site.

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