> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/model/scenarios/hydropower.md). # Hydropower reservoir Hydropower reservoir: the coupled risk across water, energy, infrastructure and biodiversity, and the applied response of the programme pillars, as a teaching context of the Nexus model. **Where this fits:** water, energy, infrastructure and biodiversity · Labs, Foundry, Nexus Standards and Nexus Reports · the Nexus Consortium · the whole programme year · teaching context. > A dam stores water for power and flood control, and reshapes the river's sediment, fish passage and wetlands downstream. **In brief.** In this teaching context water is hit first. 4 of the six sectors are in play through 6 of the fifteen relations, a coupling of 0.41 of the whole system, and the teaching cascade amplifies the initial shock ×1.90. On the response side, 4 of the six pillars apply, with 7 of the eighteen handoffs in play and 2 feedback loops closed. All sector values are **teaching values for a typical city-region, not measurements for any place**; the applications are illustrative and the cited values are published benchmarks, not forecasts.
Two hexagons for hydropower reservoir. Left, coupled risk: water is hit first; 4 of the six sectors (water, energy, infrastructure and biodiversity) are in play through 6 of the fifteen relations, and the teaching cascade amplifies the initial shock 1.90 times. Right, applied response: 4 of the six programme pillars apply (Labs, Foundry, Standards and Reports), with 7 of the eighteen handoffs between them in play and 2 feedback loops closed; the cited headline value is 4 : 1 benefit to cost. Underneath, the eight phases of the programme year in which handoffs happen.

Coupled risk, applied response: hydropower reservoir. Left: teaching values for a typical city-region, not measurements. Right: illustrative applications and the measure each pillar answers for; values are published benchmarks (World Bank, Lifelines, 2019), not forecasts. Source: the sectors and pillars model published on the GCRI, GRF and GRA home pages, vendored and hash-pinned in tools/figures/vendor/nexus-model. As of 2026-10-21.

Figure data (text alternative) | Element | Kind | Description | Value | | ------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | Water and Energy | Relation in play | Water to energy: cooling water and hydropower (0.6); Energy to water: pumping and treatment (0.5) | 0.55 | | Water and Infrastructure | Relation in play | Water to infrastructure: erosion and flood damage (0.3); Infrastructure to water: pipes, dams and treatment works (0.6) | 0.45 | | Water and Biodiversity | Relation in play | Water to biodiversity: environmental flows (0.6); Biodiversity to water: watershed regulation (0.5) | 0.55 | | Energy and Infrastructure | Relation in play | Energy to infrastructure: power for transport and telecoms (0.8); Infrastructure to energy: transmission and fuel logistics (0.6) | 0.70 | | Energy and Biodiversity | Relation in play | Energy to biodiversity: pollution from backup fuels (0.2); Biodiversity to energy: biomass (0.1) | 0.15 | | Infrastructure and Biodiversity | Relation in play | Infrastructure to biodiversity: coastal and river defences (0.2); Biodiversity to infrastructure: storm surge protection (0.2) | 0.20 | | Water | Sector | first hit, then depends on infrastructure for pipes, dams and treatment works | stress 0.68 | | Energy | Sector | depends on water for cooling water and hydropower | stress 0.17 | | Infrastructure | Sector | depends on energy for power for transport and telecoms | stress 0.13 | | Food | Sector | outside this context | – | | Health | Sector | outside this context | – | | Biodiversity | Sector | depends on water for environmental flows | stress 0.16 | | Amplification | Cascade | Shock 0.6 at Water, gain 0.35, 4 rounds; coupling 0.41 of the total | ×1.90 | | F01 | Handoff | Universe to Foundry: Admitted mission becomes a cycle project with a decision case | Readiness preparation | | F02 | Handoff | Foundry to Universe: Core Build Report and go or no-go evidence | Controlled build | | F03 | Handoff in play | Foundry to Reports: Sealed observations and indicator series behind a profile | Closeout | | F04 | Handoff | Universe to Reports: After-action and scenario findings for chapters 10 and 13 | After-action review | | F05 | Handoff in play | Foundry to Reports: National Portfolio movement for chapter 11 | After-action review | | F06 | Handoff in play | Reports to Standards: Method and correction findings as change proposals | Correction | | F07 | Handoff | Universe to Standards: Docket items that need a standard or a profile | Docket review | | F08 | Handoff in play | Standards to Foundry: Composed mission profiles and national adoption records | Readiness preparation | | F09 | Handoff | Standards to Academy: Each adopted standard or profile becomes a course module | Renewal | | F10 | Handoff | Universe to Academy: Assessed cycle tasks become completion evidence | Closeout | | F11 | Handoff | Academy to Universe: Qualified participants for the next cycle's roles | Renewal | | F12 | Handoff | Reports to Universe: Q4 synthesis informs the next-year mandate | Renewal | | F13 | Handoff in play | Foundry to Standards: Validation and monitoring evidence for conformance review | Controlled build | | F14 | Handoff | Foundry to Academy: Each system's rooms become a learning-by-doing course | Planning | | R1 | Handoff in play | Standards to Reports: Applied in editions | Around the ring | | R2 | Handoff | Reports to Academy: Taught in the open | Around the ring | | R3 | Handoff | Academy to Labs: Questions become experiments | Around the ring | | R4 | Handoff in play | Labs to Foundry: Tested prototypes are built | Around the ring | | Labs | Pillar | Inflow forecasts and sediment models for the reservoir | Forecast skill ↑ | | Foundry | Pillar | Basin twin trades power, flood storage and river flows | Release options tested ↑ | | Universe | Pillar | Release-rule exercise with operators and downstream users | Users at the table ↑ | | Standards | Pillar | Common records for releases, flows and fish passage | Flow records shared ↑ | | Reports | Pillar | Basin profile: storage, output and river health | Basin indicators ↑ 4 : 1 | | Academy | Pillar | Course on multi-purpose reservoir operation | Operators qualified ↑ | | Value at risk | Cited value | At least, by households and firms in low- and middle-income countries to infrastructure disruptions. World Bank, Lifelines, 2019 | $390B a year at least, in infrastructure disruption costs to households and firms in low- and middle-income countries | | Return on resilience | Cited value | Net benefit of more resilient infrastructure in developing countries, over the life of the assets. World Bank, Lifelines, 2019 | 4 : 1 benefit to cost | | Planning | Phase (Q1, G0) | F14 Each system's rooms become a learning-by-doing course | 1 handoff(s) | | Readiness preparation | Phase (Q2, G2) | F01 Admitted mission becomes a cycle project with a decision case; F08 Composed mission profiles and national adoption records | 2 handoff(s) | | Controlled build | Phase (Q2, G3) | F02 Core Build Report and go or no-go evidence; F13 Validation and monitoring evidence for conformance review | 2 handoff(s) | | Closeout | Phase (Q3, G5) | F03 Sealed observations and indicator series behind a profile; F10 Assessed cycle tasks become completion evidence | 2 handoff(s) | | After-action review | Phase (Q3) | F04 After-action and scenario findings for chapters 10 and 13; F05 National Portfolio movement for chapter 11 | 2 handoff(s) | | Correction | Phase (Q4) | F06 Method and correction findings as change proposals | 1 handoff(s) | | Docket review | Phase (Q4) | F07 Docket items that need a standard or a profile | 1 handoff(s) | | Renewal | Phase (Q4, G7) | F09 Each adopted standard or profile becomes a course module; F11 Qualified participants for the next cycle's roles; F12 Q4 synthesis informs the next-year mandate | 3 handoff(s) |
## Coupled risk | Sector | In this context | Stress after four rounds | | --------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------------------------ | | [Water](/organization/model/sectors/water.md) | Hit first; then depends on infrastructure for pipes, dams and treatment works | 0.68 | | [Energy](/organization/model/sectors/energy.md) | Depends on water for cooling water and hydropower | 0.17 | | [Infrastructure](/organization/model/sectors/infrastructure.md) | Depends on energy for power for transport and telecoms | 0.13 | | [Food](/organization/model/sectors/food.md) | Outside this context | – | | [Health](/organization/model/sectors/health.md) | Outside this context | – | | [Biodiversity](/organization/model/sectors/biodiversity.md) | Depends on water for environmental flows | 0.16 | Amplification ×1.90; 6 of the 15 relations in play; coupling 0.41 of the total. Teaching values for a typical city-region, not measurements for any place. Coupling is the summed strength of the relations in play, as a share of all fifteen. **What it means for a study.** A reservoir couples water, energy, infrastructure and ecosystems in one asset. Operating it for power, flood storage or river health is a trade-off, and each release rule moves stress between sectors. A study has to model the basin, not the dam. ## Applied response | Pillar | Illustrative application | Measure it answers for | Better when | Sectors served | | ----------------------------------------------------------------- | --------------------------------------------------------- | ---------------------- | ----------- | ----------------------------- | | [Labs](/organization/programme/labs.md) (applied) | Inflow forecasts and sediment models for the reservoir | Forecast skill | higher | Water, Biodiversity | | [Foundry](/organization/programme/foundry.md) (applied) | Basin twin trades power, flood storage and river flows | Release options tested | higher | Water, Energy, Infrastructure | | [Nexus Universe](/organization/programme/universe.md) | Release-rule exercise with operators and downstream users | Users at the table | higher | Water, Energy | | [Nexus Standards](/organization/programme/standards.md) (applied) | Common records for releases, flows and fish passage | Flow records shared | higher | Water, Biodiversity | | [Nexus Reports](/organization/programme/reports.md) (applied) | Basin profile: storage, output and river health | Basin indicators | higher | Water, Energy, Biodiversity | | [Risk Academy](/organization/programme/academy.md) | Course on multi-purpose reservoir operation | Operators qualified | higher | Water, Energy | **What it means for a response.** The response turns the trade-off into an explicit, shared decision. Labs improves inflow and sediment forecasts; the Foundry builds a basin model that tests release options; Standards gives operators and regulators common records for releases, flows and fish passage; Reports publishes a basin profile of storage, output and river health. The operator and the competent authority decide the release rules. In every case the responsible government, operator or licensed institution decides and acts; the programme informs that decision. ## Published benchmarks | Slot | Value | What it measures | Source | | -------------------- | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | Value at risk | $390B a year at least, in infrastructure disruption costs to households and firms in low- and middle-income countries | At least, by households and firms in low- and middle-income countries to infrastructure disruptions | [World Bank, Lifelines, 2019](https://openknowledge.worldbank.org/handle/10986/31805) | | Return on resilience | 4 : 1 benefit to cost | Net benefit of more resilient infrastructure in developing countries, over the life of the assets | [World Bank, Lifelines, 2019](https://openknowledge.worldbank.org/handle/10986/31805) | | Avoided loss | – | No published benchmark for this context | – | Each value is international evidence with its own scope, cited on the same line. None is a forecast for any project or place. See [Method and limits](/organization/model/method-and-limits.md) for how to read the values precisely. ## On the public sites The same context, with the same values, is shown on the [GRA industry platforms](https://globalriskalliance.com/industry-platforms/) page. ## Related pages [All scenarios](/organization/model/scenarios.md) · [Coupled risk](/organization/model/coupled-risk.md) · [Applied response](/organization/model/applied-response.md) · [Water](/organization/model/sectors/water.md) · [Energy](/organization/model/sectors/energy.md) · [Infrastructure](/organization/model/sectors/infrastructure.md) · [Biodiversity](/organization/model/sectors/biodiversity.md) ## Sources * World Bank, Lifelines, 2019. * The model data: the "Coupled risk, applied response" section of the [GCRI home page](https://therisk.global/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/model/scenarios/hydropower.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.