WaterWare concepts and data requirements

1. WaterWareconcepts and data requirements DDr. Kurt Fedra ESS GmbH, Austria kurt@ess.co.at http://www.ess.co.at Environmental Software & Services A-2352 Gumpoldskirchen

2. Water Resources Management must be analyzed in a broad systems context: • Socio-economic aspects(costs and benefits, jobs, institutions, regulations) • Environmental aspects(water quality, water allocation, alternative use) • Technological aspects(constraints, BAT, clean technologies, water efficiency, reuse and recycling)

3. A river basin perspective: Basic principle: Conservation laws (mass, energy) are used to describe dynamic water budgets. Basic unit: hydrographic catchment or river basin, naturally bounded, well defined. Complications: • inter-basin transfer • aquifer across catchments boundaries

4. EU Regulatory response Directive 2000/60/EC Framework for Community action in the field of water policy. (11) Objectives of preserving, protecting, and improving the environment … rectified at source, polluter should pay.

5. 2000/60/EC (12) …balanced development … potential benefits and costs of action or lack of action. • Policy must take into account …vulnerability of aquatic ecosystems … (27) Ultimate objective … elimination of priority hazardous substances …2455/2001/EC

6. 2000/60/EC (33) Unit: river basin (same ecological, hydrological and hydrogeological system); transboundary coordination. (36) Development of water status … monitored by the Member States on a systematic and comparable basis.

7. 2000/60/EC (38) .. Use of economic instruments …may be appropriate. An economic analysis of water services based on long-term forecasts of supply and demand for water in the river basin district will be necessary …

8. 2000/60/EC (46) ..ensure the participation of the general public … in the establishment and updating of river basin management plans… …provide proper information (Article 14, public information and consultation)

9. 2000/60/EC Article 5: Member States shall ensure for each river basin district: • Analysis of its characteristics • A review of impacts of human activities … • An economic analysis of water use.

10. 2000/60/EC Article 9: Recovery of costs for water services (Annex III), polluter pays principle. Pricing policies for efficient use. Adequate contributions of different groups (industry, agriculture, households)

11. 2000/60/EC In summary: • Integrated management (P/NP, S/G, Q/Q) • River-basin oriented • River basin management plans, monitoring, reporting • Economic analysis and instruments (efficiency) • Public information and consultation

12. WaterWare (EUREKA 486) is an information and decision support system for water resources management. • support river-basin scale planning, operational management, • monitoring, • water allocation, • pollution control, • environmental impact assessment tasks.

13. WaterWare (EUREKA 486) Object-oriented structure including • Embedded GIS; basic topography, DEM, land use/cover, soils, geology, surface water,… • Monitoring data (real-time) • Water resources network (topological) of NODES and REACHES • Demand/supply objects (e.g., cities) • Simulation Models (supply, demand, quality, economics) • Optimisation, EIA expert system

14. WaterWare (EUREKA 486) Embedded GIS: All objects are georeferenced. Background maps: • Landuse, land cover, infrastructure • Water courses and surface water • Geology, groundwater • Digitial Terrain model (DEM)

15. WaterWare (EUREKA 486) Is a system of linked (cascading) dynamic bass budget models: • Operates on a DAILY time step • Keeps track of all demand and supply data (and associated costs and benefits) for each node at each time step • Usual operational period: • Water year (12 months) • Reports for arbitrary sets of nodes (classes), can compute reliability in a stochastic framework.

18. WaterWare (EUREKA 486) Monitoring data (daily time series): Monitoring stations area georeferenced. • Meteorological data (precipitation, temperature, PEVT) • Flow data • Cannel flow, pumping, diversions, reservoir release, consumption, return flow, etc. • Water quality: turbidity, nutrients, salinity, DO/BOD, agrochemicals, heavy metals, coliforms, …

22. WaterWare River Basin Object: • Sub-catchments • Reservoirs, hydraulic structures • Demand Nodes: cities, industries, irrigation areas, wetlands • Monitoring stations • River network (nodes, reaches) • Aquifers

26. WaterWare Irrigation water demand model • Size, extraction/conveyane • Irrigation technology • Crop distribution • Cropping patterns • Groundwater head/depth • Crop specific water demands OR FAO factors • Costs/benefits

28. Application Example

29. Application Example

30. WaterWare Treatment plants • Size (hydraulic/retention capacity) • “consumptive use” • Treatment technology • Efficiency (by pollutant/class) • Investment/OMR costs

32. WaterWare Networks: topology of nodes and links Links connect the nodes, representing the flow of water. Links can be • open channels, natural or man made, • or pipelines.

33. WaterWare Minimal Network: 1 start node (inflow) 1 end node (outflow) Realistic cases: 10-300 nodes

37. Water demand Consumptive use Intake (quality constr., conveyance loss Production process return flow (pollution) recycling

38. Water demand Depends on: • Conveyance losses • Production volume, area irrigated, inhabitants • Efficiency of use: • Water, production, irrigation technology, • Recycling strategies Demand has quantitative and qualitative elements, usually involves water treatment For a given cost of water, an optimal strategy can be computed based on investment cost, discount rate, and project lifetime (NPV)

40. Conflicting use More than 70% of water is generally used for agriculture (irrigation); Added value per unit water used in industry is usually between 50 to 100 times higher than in agriculture; Domestic (including tourism) use of water is comparatively small, but with high quality requirements and low elasticity, seasonal variability. Environmental use (low flow, quality constraints).

43. Benefit and Costs Nodes are described by cost functions: • Investment • Operating cost (OMR) • Life time of project/structure • Discount rates Benefits per unit water supplied and used. Computation of NPV (net present value) for comparison of scenarios

44. Quality integration • Demand nodes produce return flow of modified quality • Flow regime results in different dilution and self-purification behavior. • Results of the WRM feed water quality models (flow, effluents)TELEMAC • Water quality models for surface and groundwater

48. Application Example The Kelantan River north-eastern peninsular Malaysia. • Catchment of about 15,000 km2 • Altitude difference of more than 2100 m • Average runoff of about 500 m3/sec • Monsoon climate. rainfall with extreme monthly values between 0 and 1750 mm in dry and wet months The main problem: reliability of water resources for the rice paddies that supply about 12 % of national production. Efficiency: low, water is free for farmers.

49. Application Example

50. Application Example