1. DSS for Integrated Water Resources Management (IWRM) DSS Implementation DDr. Kurt Fedra ESS GmbH, Austria kurt@ess.co.at http://www.ess.co.at Environmental Software & Services A-2352 Gumpoldskirchen DDr. Kurt Fedra ESS GmbH, Austria kurt@ess.co.at http://www.ess.co.at Environmental Software & Services A-2352 Gumpoldskirchen

2. 2 What is a DSS ? a computer based problem solving system – Hardware, computing and communication – Software, DB/GIS, models, DSS proper – Data, information, knowledge – People, institutions that can assist non-trivial choice between alternatives in complex and controversial domains.

3. 3 Murphy’s Law No. …59 ?. The development of any software systems takes (much) longer than expected, even if this rule is taken into account

4. 4 Hardware requirements HW Changing very rapidly, not a real constraint, affordable standard PC/workstation/server powerful enough, most important: local technical support (global DHL delivery ?) Infrastructure: Clean, climate controlled roomsClean, climate controlled rooms Stable power supply (UPS)Stable power supply (UPS) Internet connection (bandwidth, reliability)Internet connection (bandwidth, reliability)

5. 5 Architecture: Distributed redundant architecture: Local control, needs more local resources, difficult to maintain, update, synchronize (will drift apart), more difficult to exchange/shared data and address common (regional) issuesLocal control, needs more local resources, difficult to maintain, update, synchronize (will drift apart), more difficult to exchange/shared data and address common (regional) issues Networked (centralized server, distributed clients): shared resources: server/cluster, RDBMS, backup, data, tools, easy to maintain and update, synchronize, but more limited local controlshared resources: server/cluster, RDBMS, backup, data, tools, easy to maintain and update, synchronize, but more limited local control

6. 6 DSS and model software Open Source Operating System (Linux), Ubuntu Application software: Do it yourself: cheap, flexible, unreliable, inefficient, heterogeneous, difficult to manage/controlDo it yourself: cheap, flexible, unreliable, inefficient, heterogeneous, difficult to manage/control Commercial: expensive (long term support), but reliable and efficient if maintained (costs)Commercial: expensive (long term support), but reliable and efficient if maintained (costs) Combined: commercial stable core with open interfaces to integrate custom made componentsCombined: commercial stable core with open interfaces to integrate custom made components

7. 7 DSS and model software Usability, ease of use, error free operation, intuitive understanding (communication, participation): INTEGRATION INTEGRATION Easy to change components in a distributed, open, modular architecture with standard protocols, interfaces, formats

8. 8 Architecture Distributed, web-based: Shared central resources, administrationShared central resources, administration Easy access for distributed users, easy communication, distributed resourcesEasy access for distributed users, easy communication, distributed resources Simple client requirements (PC with standard web browser, data import/export facilities)Simple client requirements (PC with standard web browser, data import/export facilities) CONSTRAINT: Internet access, bandwidth, reliability (latency can be measured …) improves fast.

9. 9

10. 10

11. 11 Components (wishlist, part 1) Object data base (nodes, reaches), DB administration (telemetry ?)Object data base (nodes, reaches), DB administration (telemetry ?) Monitoring data base (time series)Monitoring data base (time series) Embedded GIS (all objects geo-referenced)Embedded GIS (all objects geo-referenced) Hydro-meteorological scenarios (prognostic 3D models: MM5, WRF)Hydro-meteorological scenarios (prognostic 3D models: MM5, WRF) Rainfall-runoff model, semi-distributed (ungaged catchments) erosion, flooding, lateral inflow, calibration ?Rainfall-runoff model, semi-distributed (ungaged catchments) erosion, flooding, lateral inflow, calibration ?

12. 12 Components (wishlist part 2) Irrigation water demand estimation (incl. crop data base, production, yield)Irrigation water demand estimation (incl. crop data base, production, yield) Water resources model(s), dynamic water budget, allocation, economics (hydropower)Water resources model(s), dynamic water budget, allocation, economics (hydropower) Groundwater model (3D ?)Groundwater model (3D ?) Water quality model(s): DO/BOD, tracers, turbidity, for river and lakes/reservoirs;Water quality model(s): DO/BOD, tracers, turbidity, for river and lakes/reservoirs; Optimization (multi-criteria: water resources, water quality, socio-economics)Optimization (multi-criteria: water resources, water quality, socio-economics)

13. 13 Components (wishlist part 3) Watershed management, wetlands (land use dynamics, site suitability analysis, optimal project location)Watershed management, wetlands (land use dynamics, site suitability analysis, optimal project location) Fisheries management (Beverton-Holt ?)Fisheries management (Beverton-Holt ?) Regional development dynamics (demography, socio-economics)Regional development dynamics (demography, socio-economics) EIA (screening level project assessment)EIA (screening level project assessment) Embedded user manuals and training, tutorials, distance learning ?Embedded user manuals and training, tutorials, distance learning ?

14. 14 Components (wishlist part 4) COMMON TOOLS (integrated): Basic statistical analysis (non-parametric)Basic statistical analysis (non-parametric) Plotting, mapping (compatible GIS)Plotting, mapping (compatible GIS) Report generation (standard formats)Report generation (standard formats) Data exchange protocolsData exchange protocols User communication (groupware)User communication (groupware) –Discussion fora, FAQ, error log –Mailing lists, newsletter

15. 15 System integration (OOD) Modular architecture: Several “independent” models for different topics, but shared input/output;Several “independent” models for different topics, but shared input/output; Smaller models easier to test !Smaller models easier to test ! Cascading models, consistent coupling and integration (thematic, time and space)Cascading models, consistent coupling and integration (thematic, time and space)

16. 16 System integration (OOD) Modular architecture: Nested models (3 levels ?): Overall Nile basin water budgetOverall Nile basin water budget Major subcatchments (10-15 ?)Major subcatchments (10-15 ?) Local studies within the sub-catchmentsLocal studies within the sub-catchments Each sub-model provides input (its sub-basin outflow and performance) to the next level

17. 17 System integration (OOD) Common protocols, interfaces, formats: –Ontology (terminology, variable definitions units, formats, META data) –Data base structure (object oriented, geo- referenced (shared GIS), time-stamped) –Data exchange (SQL, import/export to PC formats for local processing) –User interface (consistent style and logic)

18. 18 Data requirements Never enough (historical time series, spatial coverage) – Data organisation, META data, uncertainty, sampling statistics – Innovative sources: remote sensing – Model generated estimates for complete, high-resolution synoptic data fields (hydrometeorology)

19. 19 Data requirements Planning applications : Historical data, long-term hydrometeorology for probabilistic analysis (climate change impacts ?)Historical data, long-term hydrometeorology for probabilistic analysis (climate change impacts ?) Operational management: Needs real-rime monitoring data (sensors, local telemetry (GSM/GPRS, UHF radio), telemetry (investment and maintenance effort)Needs real-rime monitoring data (sensors, local telemetry (GSM/GPRS, UHF radio), telemetry (investment and maintenance effort) Model based forecasts (precipitation  flow)Model based forecasts (precipitation  flow)

20. 20 Monitoring sensors: Meteorology Water levels Soil moisture Flow monitoring open channel, pipelines Water quality Telemetry: UHF, GSM, GPRS Meteorology Water levels Soil moisture Flow monitoring open channel, pipelines Water quality Telemetry: UHF, GSM, GPRS

21. 21 People and institutions Introduction of a DSS means institutional change (long term learning process)Introduction of a DSS means institutional change (long term learning process) Control of information is power, changes mean struggle, affect institutional structuresControl of information is power, changes mean struggle, affect institutional structures Training is essential: ON THE JOB training within the framework of relevant projectsTraining is essential: ON THE JOB training within the framework of relevant projects Academic training takes YEARS (brain drain)Academic training takes YEARS (brain drain)

22. 22 People and institutions Training requirements: Basics (academic) coordinated with local/regional universities ?Basics (academic) coordinated with local/regional universities ? Topical and tool oriented coursesTopical and tool oriented courses On-the-job training within specific projectsOn-the-job training within specific projects Distance learning toolsDistance learning tools ISSUES: tests, certification, accredidation ?

23. 23 DSS Implementation: Requires a well balanced consideration and careful integration of Hardware, computing and communication Hardware, computing and communication Software, DB/GIS, models, DSS proper Software, DB/GIS, models, DSS proper Data, information, knowledge Data, information, knowledge People (training), institutions, procedures People (training), institutions, procedures Serious long term commitment