Evidence: every test result filed with its raw data, method and signature. The loop, step by step: 1. A rack of results and a signing vault. 2. Sensor, link, edge and console stand ready. 3. A test result lands in the evidence store. 4. Each reading is stamped with time and place. 5. The vault seals it with a time stamp. 6. The sealed record is copied to the archive. 7. Relays carry the packets without reading them. 8. Signatures are checked before any model runs. 9. A hash chain links it to every earlier record. 10. The edge releases confirmed results only. 11. An auditor opens the record years later. 12. The console shows the evidence with the alert. 13. The hash still matches and the claim stands. 14. Instruments confirm the response took effect. 15. Record, proof and action are archived together. 16. Everything settles back to idle.

01 / 16

A rack of results and a signing vault

/

/

Evidence, inside Test and qualification: digital evidence handling, product security evaluation, records management, evidence chain of custody and more. Every item is traced to its specification, from ISO/IEC 27037 to ISO/IEC 15408 (Common Criteria), and runs on the open Observatory Protocol.

Technologies

5

At the frontier

0

Protocol functions

3 of 12

Industries served

4

At a glance

Digital evidence handling

Identification, collection and preservation of evidence after an incident. In evidence, part of Test and qualification, the monitoring, incident response and governance layer holds digital evidence handling, drawn against ISO/IEC 27037 and used beside evidence chain of custody on the same sites.

Inkinga

Every result, signed and kept

Datasheets promise performance in conditions nobody’s site will see. Buyers, auditors and regulators need results they can check, from tests they can repeat. Without independent, repeatable tests, every comparison between suppliers is a comparison between marketing documents; qualification replaces claims with measured results, published either way.

Key facts

Specification

ISO/IEC 27037

Specification

ISO/IEC 27037 · W3C PROV-O

Specification

WMO-No. 1192 (instrument and maintenance categories)

Specification

ISO/IEC 15408 (Common Criteria)

Specification

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

Components

• Rugged field tablet on a mast bracket
• Automatic weather station (AWS) to WMO siting practice
• Particulate monitoring station and sensor node
• Compact X-band weather radar / ISAC sensing node on a lattice tower top
• Street small-cell pole with an air-quality node
• “AI tower in a box”
• Hardware security module, 1U, in an edge rack
• Data hall row pair with cold-aisle containment

Interfaces

Radio

Wi-Fi · LTE / 5G

Where it works

• Evidence chain of custody
• Product security evaluation

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. Test and qualification · Evidence

   Every result, signed and kept

   Datasheets promise performance in conditions nobody’s site will see. Buyers, auditors and regulators need results they can check, from tests they can repeat. Without independent, repeatable tests, every comparison between suppliers is a comparison between marketing documents; qualification replaces claims with measured results, published either way.

2. What it does

   Digital evidence handling

   Identification, collection and preservation of evidence after an incident. In evidence, part of Test and qualification, the monitoring, incident response and governance layer holds digital evidence handling, drawn against ISO/IEC 27037 and used beside evidence chain of custody on the same sites.

   Specification

   ISO/IEC 27037

3. Health, safety and evidence records

   Evidence chain of custody

   Recording who handled field data, samples and devices and when. In evidence, part of Test and qualification, the health, safety and evidence records layer holds evidence chain of custody, drawn against ISO/IEC 27037 and W3C PROV-O. We build it into every site for evidence against that standard, and keep its version and its test results on the site’s record.

   Specification

   ISO/IEC 27037 · W3C PROV-O

4. Calibration

   Instrument lifecycle records

   Install, swap, calibration and fault history for each serial number. In evidence, part of Test and qualification, the calibration, metadata and quality control layer holds instrument lifecycle records, drawn against WMO-No. We build it into every site for evidence against that standard, and keep its version and its test results on the site’s record.

   Specification

   WMO-No. 1192 (instrument and maintenance categories)

5. Ukuqapha

   Product security evaluation

   Independent evaluation of security functions against protection profiles. In evidence, part of Test and qualification, the monitoring, incident response and governance layer holds product security evaluation, drawn against ISO/IEC 15408. We build it into every site for evidence against that standard, and keep its version and its test results on the site’s record.

   Specification

   ISO/IEC 15408 (Common Criteria)

6. Time and place

   When and where, on every record

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

7. Health, safety and evidence records

   Records management

   Authentic, reliable and retrievable records for every site and asset. In evidence, part of Test and qualification, 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 evidence 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)

8. Ukwethembeka

   Proved before it is trusted

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

9. Ubufakazi

   Traced to its specifications

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

   Amazinga

   ISO/IEC 27037 · ISO 15489-1:2016 · ISO 9001:2015 · WMO-No. 1192

10. Izibuyekezo

    Updates in rings, with rollback

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

11. How it scales

    One base unit, repeated

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

12. What you get

    Qualification and the works-with programme

    The conformance tool and test plans are open. Device and software qualification, the works-with programme and field trial management are contracted. Works-with testing gives makers a recognised way to show their products join any grid built on the specification, with results published either way.

    Talk to salesPartner with us

13. Next step

    Evidence, planned with you

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

    Plan a deploymentOpen the Field Deployment StudioSee Test and qualification

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

01Yini

Monitoring, incident response and governance.

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

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

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

Macro, small cells, DAS and repeaters

9

Massive MIMO and beamforming

7

NR bands, duplexing and synchronisation

9

NR features: RedCap, positioning, sidelink and verticals

9

Private networks and RAN sharing

7

Wi-Fi coexistence and convergence

8

6G and integrated sensing and communication

7

RAN planning, optimisation and assurance

6

01Joyina Identity, attestation quote, signed policy.

02Admit Admitted for a stated scope, nothing wider.

03Chaza 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 evidence.

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

• Conformance tool
• Test plans

Enterprise, on this site

• Device and software qualification
• Works-with programme
• Field trial management

06The rest of the line

Test and qualification, area by area.

Bring us the site.

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