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)
Global Privacy Control detected. We have honored it as your request to opt out of the sale and sharing of your personal information and of targeted advertising.Signal Global Privacy Control détecté. Nous l'avons respecté comme une demande d'opposition à la vente et à la communication de vos renseignements personnels ainsi qu'à la publicité ciblée.
Cookie policyPolitique relative aux témoins Privacy policyPolitique de confidentialité Do Not Sell or Share My Personal InformationNe pas vendre ni communiquer mes renseignements personnels
Your browser sent a Global Privacy Control signal. We treat it as a refusal for the purposes marked below, and those switches stay off.Votre navigateur a envoyé un signal Global Privacy Control. Nous le traitons comme un refus pour les finalités indiquées ci-dessous, et ces interrupteurs restent désactivés.
Needed for the site to work, to keep you signed in, to protect it from attacks and to remember your privacy choices and the settings you pick. Always on.Nécessaires au fonctionnement du site, pour vous garder connecté, le protéger contre les attaques et retenir vos choix de confidentialité et les réglages que vous choisissez. Toujours actifs.
Remember optional settings beyond the ones you pick yourself. Off until you allow it.Retenir des réglages facultatifs autres que ceux que vous choisissez vous-même. Désactivés tant que vous ne les autorisez pas.
Count visits and see how pages are used, so we can improve the site. Off until you allow it.Compter les visites et voir comment les pages sont utilisées, afin d'améliorer le site. Désactivés tant que vous ne les autorisez pas.
Show videos, maps and live data layers from other providers. They receive your IP address and may set their own cookies. Off until you allow it, or load a single item once.Afficher des vidéos, des cartes et des couches de données en direct d'autres fournisseurs. Ceux-ci reçoivent votre adresse IP et peuvent déposer leurs propres témoins. Désactivés tant que vous ne les autorisez pas, ou chargez un seul élément une fois.
Measure campaigns and personalise advertising. We use none today. Off until you allow it, and refused when your browser sends Global Privacy Control.Mesurer les campagnes et personnaliser la publicité. Nous n'en utilisons aucun actuellement. Désactivés tant que vous ne les autorisez pas, et refusés lorsque votre navigateur transmet le signal Global Privacy Control.
Nexus Observatory Inc. keeps a record of each choice as proof: a random consent ID, the time, your region and the rules applied, the choices, the notice shown, the page, a shortened IP address, a one-way code of your browser type and, if you are signed in, your account. Records are kept while your choice applies and for 3 years after, then deleted.Nexus Observatory Inc. conserve un registre de chaque choix à titre de preuve : un identifiant de consentement aléatoire, l'heure, votre région et les règles appliquées, les choix, l'avis affiché, la page, une adresse IP abrégée, un code à sens unique du type de navigateur et, si vous êtes connecté, votre compte. Les registres sont conservés tant que votre choix s'applique et pendant 3 ans par la suite, puis supprimés.
Untick to choose for this site only. You can change either at any time in Privacy choices.Décochez pour choisir pour ce site seulement. Vous pouvez modifier l’un ou l’autre à tout moment dans Vos choix de confidentialité.
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/
ReportingReporting, 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 protocolAt a glance
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.
Tatizo
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
Components
Interfaces
Where it works
In the story below
Scenes · 13
Next steps
Plan a deploymentOpen the Field Deployment StudioSee Operations centreSee Managed servicesOperations centre · Reporting
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.
What it does
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.
Energy management and monitoring
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.
Health, safety and evidence 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.
Time and place
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.
Metadata, provenance and catalogues
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.
Imani
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.
Ushahidi
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.
Operations
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.
Taarifa mpya
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.
How it scales
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.
Managed services
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 salesNext step
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 centreMore presentations
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 presentations01Ni nini
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
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
Structured inspection reports with findings, photos and sign-off.
We deploy, operate and maintain.
ISO/IEC 17020 (inspection bodies)
Data, software and interoperability
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
Revenue and sub-metering for loads, generation and tenants.
We design, integrate and operate.
IEC 62053 series (electricity metering)
02Architecture
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
01Jiunge Identity, attestation quote, signed policy.
02Admit Admitted for a stated scope, nothing wider.
03Eleza 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
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
Deployment scenarios from the sector research that rely on reporting.
Environment and climate05Open and enterprise
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
Survey, design, deployment and operation for reporting. The form names who receives your details.
Talk to usAsk for a quoteReporting, 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.
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.