Nile Basin Initiative
Water Resources Planning and Management Project
Needs Assessment for and Conceptual Design of the Nile Basin Decision Support System
WP 1.1, Activity 1.1.9: Modules for the DSS Awareness/Training Workshops
For the hands on sessions with a water resources model systems and DSS,
specific case study example from the Nile basin can be used subject
to data availability.
The data requirements for a demonstration case are summarized below;
see also
Please note that all data for a (sub-basin) case study can be
imported (on-line, interactive web based upload tools for registered users)
to and used from a generic, web based
that is directly coupled with the model system.
Demo case data requirements:
Data for a water resources simulation or optimization scenario can be entered and
edited interactively with the on-line (web based) tools that also provide support
such as completeness checking; however, to be able to do this efficiently,
these data have to be prepared;
- Model domain: a definition and description of the hydrographic unit
(catchment) to be simulated; please note that WaterWare uses a topological network
representation the can also include interbasin transfers, i.e., elements outside
a primary hydrographic unit, subject to hydraulic connectivity.
Specific parameters include: domain size (in square km) and toal population,
as most indicators are normalized by area, polulation, or flow (m3).
Data format: textual description, map (e.g., shape file) of the catchment boundaries,
corresponding DEM;
Model specific dfata requirements fora water resources model scenario are defined
in some detail in
the WRM user manual.
- Default hydrometeorology: WaterWare operates on a (water) year basis; for the estimation
of groundwater recharge, direct rainfall, and evapotranspiration, one global set of timeseries
of precipitation and air temperature (daily total and daily average, respectively) should be defined.
Please note that for each node, additional time series can be specified.
Where no local time series data are defined, the global default will be used.
Data format: CSV, (can be exported from a spreadsheet) 365 records of:
DATETIME, value with an associated META DATA
record describing the monitoring station, paramteer, measurement method, data source, etc.
See also: Time Series Import dialog
- Basin structure: this is the list of
OBJECTS (or NODES) for the model
representation together with their connectivity by river reaches.
The NODES should be chosen according to the problem addressed; They cover:
- START or INPUT nodes that describe sources of water for the water resources system;
these are, primarily, upstream (and possibly ungauged, see below) sub-ctachments and
their tributaries, and wells, wellfields and natural springs.
- DEMAND NODES that describe locations of water demand and use
such as cities and settlements, irrigation districts, major industries,
as well as environmental water uses (wetlands).
- STRUCTURAL NODES that includes diversions and confluences, and storage points
such as reservoirs or natural lakes.
For each NODE, we need a name, type, location (connectivity),
and time series of supply, demand, or diversion or release rules, respectivly.
General parameters include the fraction of consumptive use at all demand nodes,
loss terms, and allocation priority rules at diversions.
The detailed data requirements for each NODE type are defined in the corresponding
NODE specific manual pages
- Economic data (cost/benefit)
For the basic economic evaluation and computation of economic (cost/benefit)
criteria, a number of economic parameters are required at each node for either a
- simulation model scenario
- multi-criteria optimization scenario
the final discrete multi-criteria DSS tool only uses interactive specifications,
so no special data need to be prepared.
These simple economic data are, in general:
- annualized investment and annual fixed and variable costs for
each relevant part of the water services system (supply and structural nodes);
- volume (flow) specific benefits for useful demands satisfied (at demand nodes;
can also include benefits of compliance at control node);
- penalties for shortfalls, but also exceedances (flooding) at control nodes;
- Optimization scenarios
An optimization scenario
(phase I, satisficing) consists of:
- A baseline WRM simulation scenario including the baseline economics;
- A set of (generic) INSTRUMENTS that
can be applied to the corresponding node types;
these are stored in a
Water Technologies Data Base
- A selection of instruments configured and applied to specific nodes;
- A set of global and sectoral CONSTRAINTS.
These are fomulated interactively on the CRITERIA the model computes.
|
