Industrial accidents, infrastructure failures and hazardous-material releases are technological hazards whose consequences depend on design, maintenance, instrumentation and the natural hazards that can trigger them. This section of the Energy and critical infrastructure subsite sets records for accident events, instrument and sensor data, asset condition and Natech triggers so that operators, regulators and responders learn from incidents using comparable records rather than narrative reports alone. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Nexus Standards (2026). Technological and industrial hazard standards: area brief, Energy and Critical Infrastructure (PROPOSED). https://nexustandards.com/energy-infrastructure/technological-hazard-standards/. Last reviewed 2026-10-17.
Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.
The hazard and threat families section of Energy and Critical Infrastructure. Scope as the area context entry states it (PROPOSED).
In scope 5
Out of scope 3
Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.
Hazards and threats 5
Sectors 4
Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.
No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.
OpenStreetMap planet and replicationpending admission
OpenStreetMap Foundation and contributors · minutely
ODbL-1.0
GRIx governed readregister row exists
eMARS Major Accident Reporting Systempending admission
European Commission JRC (Major Accident Hazards Bureau) · event-driven
European Commission reuse policy; licence to be recorded by Legal
browser-direct readproposed register row
PubChem compound, hazard and GHS classification recordspending admission
U.S. National Library of Medicine (NCBI) · continuous
Public domain for NCBI content; per-source terms for contributed data
build-time snapshotproposed register row
Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).
Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.
Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.
adopt5
UNDRR-ISC Hazard Information ProfilesUNDRR and International Science Councilregister · undrr-isc-hazard-information-profilesOGC SensorThings APIOpen Geospatial Consortiumregister · ogc-sensorthings-apiSemantic Sensor Network Ontology (SSN/SOSA)W3C and OGCproposed register rowCommon Alerting Protocol Version 1.2OASIS Emergency Management TCregister · oasis-cap-1-2PROV-O: The PROV OntologyW3Cregister · w3c-prov-oClosed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
The Nexus Standards the area context entry lists; the registry row lists NS-0, NS-3, NS-9, NS-11. Every one is proposed or specified; none is adopted by an authority.
Status proposed · 12 rules stated. Read NS-0 · The rules for this area
Status proposed · 0 rules stated. Read NS-3 · The rules for this area
Status proposed · 5 rules stated. Read NS-9 · The rules for this area
Status proposed · 6 rules stated. Read NS-11 · The rules for this area
Version and feed state per standard; every row reads source feed pending admission until a register row admits a feed.
Today · from the registryTest suites, conformance statements and attestations per standard; no attestation is recorded yet, and none would certify.
PlannedReference deployments and the sandbox on simulated data; planned until the path is wired.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
GCRI Canada may admit accident and sensor records with calibration and causal analysis method as research evidence; GCRI Canada decides under its own evidence and research rules, and no approval is implied.
GRF may record operators publishing lessons-learned records on the shared profile as a dialogue item; GRF decides under its own recognition rules, and no recognition or endorsement is implied.
GRA may read asset-condition and Natech exposure records when it reviews industrial project risk; GRA decides under its own capital-readiness rules, and no approval, rating or investment view is implied.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Accident, sensor and Natech records with causal analysis and calibration lineage.
No working group is chartered yet; a community may charter this one under NS-13 through a docket.
This area has a row in registry/subsites.yaml (status planned), so it carries five depth pages and the register crosswalk of its domains.
The rules of each listed standard, read through the specification reader.
Depth · CrosswalkEvery register entry in the area's domains, by relation, with the crosswalk graph.
Depth · Records and schemasScope, record, schema explorer and how a UNI resolves.
Depth · ConformanceClauses, evidence and attestations; no step is a certification.
Depth · ReadinessThe area beside the three pathways, as a matrix.
4 Nexus Standards · 5 domains · 50 external standards · 34 issuing bodies · 1 consumers. Relations are register entries (adopt, profile, crosswalk, cite), never compliance claims; names belong to their stewards.
Crosswalk graph94 nodes and 123 links from registry/external-standards.yaml, registry/subsites.yaml and registry/consumers.yaml. Relations (adopt, profile, crosswalk, cite) are register entries, never compliance claims.
The registry holds no geography for the area itself: areas are not places. The one geography it implies is where the bodies that issue the area's external standards sit.
| Body | Seat | Register entries |
|---|---|---|
| NIST | Gaithersburg, Maryland, United States | 7 |
| ISO/IEC JTC 1/SC 27 | Geneva, Switzerland | 3 |
| IEC TC 57 | Geneva, Switzerland | 2 |
| IEC TC 65 | Geneva, Switzerland | 2 |
| ISO/TC 268 | Geneva, Switzerland | 2 |
| ISO/TC 299 | Geneva, Switzerland | 2 |
| OASIS Cyber Threat Intelligence TC | Woburn, Massachusetts, United States | 2 |
| European Parliament and Council | Brussels, Belgium | 1 |
| FIRST CVSS Special Interest Group | Cary, North Carolina, United States | 1 |
| IEC TC 65 with ISA (ISA/IEC 62443) | Geneva, Switzerland | 1 |
| IEEE | Piscataway, New Jersey, United States | 1 |
| IETF | Wilmington, Delaware, United States | 1 |
| ISO/IEC JTC 1/SC 39 | Geneva, Switzerland | 1 |
| ISO/TC 212 | Geneva, Switzerland | 1 |
| ISO/TC 251 | Geneva, Switzerland | 1 |
| ISO/TC 301 | Geneva, Switzerland | 1 |
| ISO/TC 59/SC 13 | Geneva, Switzerland | 1 |
| ITU-R | Geneva, Switzerland | 1 |
| ITU-T SG15 | Geneva, Switzerland | 1 |
| North American Electric Reliability Corporation | Atlanta, Georgia, United States | 1 |
| TNFD | London, United Kingdom | 1 |
| WHO, FAO, UNEP, WOAH | Rome, Italy | 1 |
| World Health Organization | Geneva, Switzerland | 1 |
| World Health Organization (World Health Assembly) | Geneva, Switzerland | 1 |
1 subsites: no geography in the registry (areas, not places) · 2 consumers: repositories, no geography · 19 Nexus Standards: documents, no geography · 10 issuing bodies without a fixed public seat, listed not drawn: Convention on Biological Diversity; IUCN; UN Statistical Commission; WHO; International Atomic Energy Agency; International Civil Aviation Organization; and more · Programme regions of the ecosystem coverage register: named, not drawn (no coordinates in the registry)
Standards globe24 issuing bodies with a public seat, 50 register entries, H3 cells at resolutions 1 to 4. Seats are city coordinates, not registry fields; subsites, consumers and standards have no geography, so none is drawn. Plate carrée still map; globe with script.
| Area on the sites | Artifact kinds | Governing standards | Pages |
|---|---|---|---|
| Critical infrastructure (GCRI Canada field gateway; GRF and GRA counterparts) | data, dataset, report, map, documentation | NS-1, NS-3, NS-3b, NS-4, NS-5 | therisk.global/fields/infrastructure/ |
| Industry and robotics (GCRI Canada field gateway; GRF and GRA counterparts) | data, dataset, report, map, documentation | NS-1, NS-3, NS-3b, NS-4, NS-5 | therisk.global/fields/industry/ |
From the ecosystem coverage register: what the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) sites publish on this area, as claimed there and not evaluated here.
Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them. No Risk Academy faculty pathway is linked to this area yet; one is linked when a faculty publishes a pathway that fits.
Risk Academy disciplines that teach Technological and industrial hazard standards, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.
Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.
Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.