Nexus StandardsWater and Food SystemsSectors and industries
Area · registry row planned

Water utilities and basins

The water utilities and basins section of the Water and Food Systems subsite covers drinking-water and wastewater utilities, basin authorities and irrigation operators: how their water-safety, asset, drought and flood records are identified and verified, and how they crosswalk to the WHO drinking-water and water-safety-plan guidance and the transboundary water instruments. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.

Area recordWater and Food Systems
  1. TierSectors and industries
  2. Registryregistry row · planned
  3. Nexus StandardsNS-0, NS-3, NS-9, NS-10, NS-11
  4. Open standards5
  5. Feeds4 · 0 admitted
  6. Couplings4
  7. Last reviewed2026-10-17

Context entry PROPOSED for the Nexus Standards registry.

UNI
NXS-STD-DC-000003
Status
PROPOSEDregistry row · planned · scope EWS
Last reviewed
area context bank
Cite this page

Nexus Standards (2026). Water utilities and basins: area brief, Water and Food Systems (PROPOSED). https://nexustandards.com/water-food/water-utilities-sector-standards/ · UNI NXS-STD-DC-000003. Last reviewed 2026-10-17.

Download the profile

Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.

01Scope

Water utilities and basins: what the area covers, and what it leaves to others.

The sectors and industries section of Water and Food Systems. Scope as the area context entry states it (PROPOSED).

In scope 5

  • Water-safety plan and incident records for drinking-water supply
  • Asset condition, outage and continuity records for treatment, networks and dams
  • Basin water balance, abstraction and allocation records with boundary versions
  • Drought and flood operational triggers and their alert messages
  • Transboundary basin data-sharing obligations expressed as clauses

Out of scope 3

  • Tariff setting or utility regulation decisions
  • Engineering design of treatment works
  • Water-quality laboratory accreditation, which this section does not address

Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.

03Nexus Standards that apply

5 Nexus Standards for this area.

The Nexus Standards the area context entry lists; the registry row lists NS-0, NS-3, NS-9, NS-10, NS-11. Every one is proposed or specified; none is adopted by an authority.

  1. 01

    NS-0 · Constitution and principles

    Status proposed · 12 rules stated. Read NS-0 · The rules for this area

  2. 02

    NS-3 · GRIx record UNIs (grammar, legacy crosswalk, allocation authority)

    Status proposed · 0 rules stated. Read NS-3 · The rules for this area

  3. 03

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status proposed · 5 rules stated. Read NS-9 · The rules for this area

  4. 04

    NS-10 · Policies and clauses (machine-readable obligations, enforcement in commons and command rooms)

    Status proposed · 7 rules stated. Read NS-10 · The rules for this area

  5. 05

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status proposed · 6 rules stated. Read NS-11 · The rules for this area

04Restricted compatibility profiles

No closed standard is named for this area.

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

The working group may name closed standards later; they would be listed here by name and link only.

05Hazards and sectors

What acts on this area, and who carries it.

Hazards and threats 5

DroughtRiverine and urban floodingContamination eventsDam and asset failurePower outages

Sectors 1

water-utilities
06Systemic couplings

4 couplings to other areas and subsites.

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

Canvas · the area and its couplingsDesign, not a record
Water utilities and basins: systemic couplingsThe couplings the area context bank records for Water utilities and basins: 1 area in Water and Food Systems, 3 areas in other subsites and 3 subsites reached. Each coupling carries a mechanism stated in the context bank (PROPOSED); a reading aid, not a dependency proof.

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.

  1. Energy utilities and gridsEnergy and Critical InfrastructurePumping and treatment depend on grid supply while hydropower and thermal cooling depend on river flow, so outage and low-flow records must share time and asset identifiers.
  2. Health systemsHealth and BiosecurityContamination events and service interruptions drive waterborne disease; utility incident records feed health surveillance signals.
  3. Agriculture and land useWater and Food SystemsIrrigation and municipal abstraction share basin allocations; drought restrictions propagate from one to the other through allocation decisions.
  4. Cities and the built environmentCities and the Built EnvironmentUrban flooding and combined-sewer overflows couple drainage assets with land use and building exposure.
07Data and feeds

4 sources, with provider, licence and delivery path.

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.

Every feed · pending admission

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.

Admitted
0
none yet
Register row exists
3
recorded for the GRIx path
Proposed row
1
terms to be recorded
Delivery
3 GRIx · 0 plugin · 0 browser · 1 snapshot
GRIx first, then plugin, browser-direct, snapshot
  • Aqueduct 4.0 Water Risk Atlaspending admission

    World Resources Institute · versioned releases

    CC BY 4.0

    GRIx governed readregister row exists

  • GloFAS global flood forecastspending admission

    Copernicus Emergency Management Service · daily

    CEMS-Floods datasets licence

    GRIx governed readregister row exists

  • World Development Indicatorspending admission

    World Bank · annual with quarterly updates

    CC BY 4.0

    GRIx governed readregister row exists

  • AQUASTATpending admission

    Food and Agriculture Organization of the United Nations · annual

    CC BY 4.0 under the FAO Statistical Database Terms of Use

    build-time snapshotproposed register row

08Readiness

What each pathway can read from this area.

GCRI Canada evidence pathway

GCRI Canada

Incident, outage and water-balance records with record UNIs and correction history become readable as evidence for the GCRI Canada pipeline, which applies its own admissibility rules.

Open the GCRI Canada evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

A utility or basin authority that publishes its water-safety-plan clauses and continuous attestations gives GRF a record trail it may consider; nothing is recognised by adoption.

Open the Recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

Resilience investments in networks and storage can carry verified service-continuity baselines into a GRA capital-readiness assessment, decided by GRA alone.

Open the Capital pathway

Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.

11Audiences

Who works with this area: 4 audiences.

  1. Utility operators and regulators
  2. Basin authorities and river commissions
  3. Irrigation operators
  4. Public-health agencies
12Working group

The working-group charter, proposed.

Scope

Profile utility incident, asset-continuity and basin allocation records and crosswalk them to WHO water-safety guidance and transboundary water instruments.

No working group is chartered yet; a community may charter this one under NS-13 through a docket.

Deliverables · 3
  1. Water-safety-plan incident record profile
  2. Basin water balance and allocation record profile with boundary versioning
  3. Crosswalk to WHO GDWQ and Water Safety Plan manual sections (by section number and URL)
Liaison targets · 4
  • World Health Organization (WASH) liaison sought
  • UNECE Water Convention secretariat liaison sought
  • International Water Association liaison sought
  • FAO AQUASTAT liaison sought
13Open problems

3 open problems an expert would start with.

  1. Service-interruption data are rarely published at asset level, so Sendai D-5 counts cannot be reconciled with utility records.
  2. Transboundary basins lack shared, versioned boundaries and gauging records, which blocks cascade analysis across borders.
  3. Water-stress indicators are annual and national while operational risk is daily and sub-basin.
14Registry depth

The registry row: scope EWS, 2 crosswalk domains.

This area has a row in registry/subsites.yaml (status planned), so it carries five depth pages and the register crosswalk of its domains.

Crosswalk graph · water utilities and basinsFrom the registry
Water utilities and basins: the register crosswalk42 nodes on four orbits (Nexus Standards and consumers inside, then domains, external standards and issuing bodies) joined by 54 register links.
Nexus StandardsDomainsExternal standardsIssuing bodiesConsumers

5 Nexus Standards · 2 domains · 20 external standards · 14 issuing bodies · 1 consumers. Relations are register entries (adopt, profile, crosswalk, cite), never compliance claims; names belong to their stewards.

Crosswalk graph42 nodes and 54 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.

Standards globe · Water utilities and basins: issuing bodiesFrom the registry
Where the issuing bodies of the external standards register sitA plate carrée world map with Natural Earth coastlines, H3 resolution 2 hexagons at the public seats of 12 issuing bodies and one dot per seat. 20 register entries.
Issuing bodies' seats (12)H3 cells, resolution 2 (4); darker, more register entriesSubsites, consumers, standards: no geography in the registry
Issuing bodies and their seats (12)
BodySeatRegister entries
ISO/TC 224Geneva, Switzerland4
IEC TC 65Geneva, Switzerland2
ISO/TC 268Geneva, Switzerland2
ISO/TC 299Geneva, Switzerland2
European Parliament and CouncilBrussels, Belgium1
IEC TC 65 with ISA (ISA/IEC 62443)Geneva, Switzerland1
IEEEPiscataway, New Jersey, United States1
ISO/TC 251Geneva, Switzerland1
ISO/TC 59/SC 13Geneva, Switzerland1
ITU-RGeneva, Switzerland1
ITU-T SG15Geneva, Switzerland1
UNECE (Water Convention) with partners including FAORome, Italy1

1 subsites: no geography in the registry (areas, not places) · 2 consumers: repositories, no geography · 19 Nexus Standards: documents, no geography · 2 issuing bodies without a fixed public seat, listed not drawn: International Civil Aviation Organization; International Maritime Organization · Programme regions of the ecosystem coverage register: named, not drawn (no coordinates in the registry)

Standards globe12 issuing bodies with a public seat, 20 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 sitesArtifact kindsGoverning standardsPages
Water (GCRI Canada field gateway; GRF and GRA counterparts)data, dataset, report, map, documentationNS-1, NS-3, NS-3b, NS-4, NS-5therisk.global/fields/water/

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.

15References

4 sourced references.

Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.

16Learning

Risk Academy faculties for this area.

Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.

17Key terms

Terms used on this page.

UNI
Unique Nexus Identifier: identifies and resolves an artifact and its record; it never certifies truth, readiness or approval.
PROPOSED
Drafted content that no authority has adopted. Every area entry here is a proposal to the Nexus Standards registry.
cite
Relation: the external standard is cited by identifier and URL as a reference.
crosswalk
Relation: Nexus clauses are mapped to parts of the external standard by number, never by text.
adopt
Relation: the external standard is used as published, values validated against it.
pending admission
No legal register row admits this source for display on public pages yet, so nothing is read from it.
GRIx
The governed data layer of Nexus Foundry: external data is read through it with its licence and source release.
docket
A public change record under NS-13, decided by editors with written reasons.
attestation
An evaluator's recorded result for one clause and one subject under NS-11; never a certification.
liaison sought
A liaison the working group would ask the body for; none is held unless the body confirms it in writing.
19Learn and apply

Where Water utilities and basins is taught, worked on and run.

Risk Academy disciplines that teach Water utilities and basins, 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.

Risk Academy

Disciplines and courses

20Questions

Questions and answers.

Is the Water utilities and basins area adopted?
No. The area entry is PROPOSED content for the Nexus Standards registry beside its registry row. Adoption of any standard is a recorded authority decision and none is recorded today.
Are the feeds on this page live?
No. Every feed is pending admission: no legal register row admits it for public pages yet, so nothing is read from it here.
How do I change this brief?
Through a docket under NS-13: a pull request against the area context bank or the registry, decided by editors with written reasons.
Nexus Standards

Shape this brief: Water utilities and basins.

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.

Skip to toolbar