Integrating a Reservoir Operations Module into CyberWater

Name: Surabhi Upadhyay Affiliation: Colorado School of Mines Email: surabhi_upadhyay@mines.edu

1. Research Question or Modeling Problem

CyberWater currently provides tools for retrieving hydrologic and meteorological data, running hydrologic models, routing streamflow, and processing model outputs. However, reservoir operations are an important step between simulated river flow and downstream water-management outcomes. The main question is: How can a reservoir operations module be integrated into CyberWater so that users can simulate reservoir storage, release, and downstream flow using inflow generated from hydrologic models or retrieved from data sources? The reservoir module should be general enough to support different reservoirs and operating rules.

2. Desired Workflow Outcome

The desired outcome is a CyberWater workflow in which a user can: - Select a reservoir or study area. - Provide or retrieve reservoir inflow. - Provide reservoir characteristics and operating rules. - Define an initial reservoir storage. - Run the reservoir operations model. - Obtain time series of reservoir storage, release, and downstream flow (or reservoir outflow). - Visualize reservoir behavior within CyberWater. Ultimately, the reservoir operations module would connect hydrologic simulation with reservoir management.

3. Required Inputs

The reservoir operations module would require several inputs. Hydrologic inputs - Reservoir inflow - Simulation time step - Simulation period Inflow could come from: - A CyberWater hydrologic model - A routing model - Observed streamflow - A user-provided file Reservoir characteristics - Reservoir capacity - Initial storage - Minimum storage - Maximum storage Operating information - Release rules - Target storage - Minimum release - Maximum release Model configuration - Reservoir ID or name - Simulation settings - Model executable or Python code

4. CyberWater Components That Already Exist

Several existing CyberWater components could support the proposed reservoir operations workflow. - TimeRange and SpaceRange - Existing Data Agents could provide hydrologic or meteorological data needed by the workflow. - Outputs from hydrologic or routing models could provide the reservoir inflow. - Generic Model Agent could potentially be used to integrate a reservoir operations model into CyberWater.

5. Missing CyberWater Components or Development Needs for This Workflow

The main missing component would be a dedicated Reservoir Operations Module or Reservoir Model Agent. This component would need to: - Receive inflow time series. - Read reservoir characteristics. - Accept an initial storage condition. - Apply reservoir operating rules. - Calculate reservoir storage at each time step. - Calculate reservoir release. - Pass downstream release to other CyberWater models or analysis modules. Additional development may be needed for: - Reservoir-specific operating rules. - Rule curves. - Hydropower operating constraints. - Multi-reservoir systems. - Reservoir parameter databases.

6. Proposed End-to-End CyberWater Workflow

TimeRange + SpaceRange ↓ Hydrologic Data / Hydrologic Model ↓ Reservoir Inflow ↓ Reservoir Operations Module ↓ Storage + Release ↓ Downstream Routing ↓ Visualization

7. Risks and Uncertainty

Potential challenges include: - Reservoir operating rules differ substantially among reservoirs. - Some operating rules may not be publicly available. - Reservoir operations can depend on forecasts, water demand, hydropower requirements, and legal constraints. - Initial reservoir storage can strongly affect simulation results. - Different reservoir models may require different input formats. - Coupling reservoir operations with existing CyberWater routing models may require additional development.

8. Questions for the CyberWater Team

Few questions: - Could a reservoir operations model be integrated using the existing Generic Model Agent Toolkit? - Would it be better to develop a dedicated ReservoirAgent? - Can output from an existing hydrologic or RoutingAgent be passed directly to a reservoir operations module? - Can reservoir release then be passed back into the RoutingAgent for downstream simulation? - How should reservoir parameters and operating rules be stored within CyberWater?

9. CyberWater Team Feedback

I was not able to discuss the proposal in detail with the CyberWater team, but I had a brief conversation about the feasibility of integrating a reservoir operations model into CyberWater. The team indicated that the Generic Model Agent Toolkit could be used to integrate an existing Python-based reservoir release algorithm into CyberWater. This feedback was helpful because it confirmed that a new reservoir operations capability may not require developing an entirely new CyberWater framework from scratch.