GCRI · Water Nexus
Innovation and practical technology
Technology relevant to water, climate and hazards and critical infrastructure: what it can do, the constraints it faces and its consequences for people and institutions.
The workspace for innovation and practical technology.
Innovation pipeline
Water · Stage gates · Example interface, not a record
By readiness level
Readiness criteria
pilot vs gate
Pilot issues
- I-1Data licence for pilot siteTo check5 d
- I-2Observer protocol signedDone4 d
Water Nexus · Innovation pipeline. Innovation pipeline: example names and illustrative values, not a record.
Evaluate before adopting.
- 01
Need
Which problem does the technology address, and for whom?
- 02
Evidence
What has been demonstrated, under what conditions, and what remains untested?
- 03
Constraints
Cost, skills, infrastructure, data and governance requirements.
- 04
Consequences
Effects on safety, rights, equity and the environment.
What could change water risk practice, and what it still has to show.
| Technology | What it could change | What remains to be shown |
|---|---|---|
| Wide-swath satellite altimetry (for example the SWOT mission) | River and lake levels in ungauged basins | Accuracy on narrow rivers and under vegetation; continuity beyond mission life |
| Machine-learning rainfall-runoff models | Better prediction in ungauged basins by learning across many catchments | Behaviour under unprecedented extremes and changing land use |
| Low-cost water-level and quality sensors | Denser observation for utilities and communities | Calibration drift, maintenance and data stewardship over years |
| Smart metering and leakage analytics | Visibility of non-revenue water and demand | Data protection, utility capacity to act on the data |
| Managed aquifer recharge | Storing wet-season water underground | Site-specific hydrogeology, water quality and long-term monitoring |
Promising methods are tried in Labs and built in Foundry; none is presented here as proven.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Does the platform endorse products?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.
