1. WaterWare description
Data management, Objects
Monitoring, time series
Hydro-meteorological data, forecasts
Rainfall-runoff: RRM, floods
Irrigation water demand
Water budget modelling
Water quality: STREAM, SPILL
Multi-criteria optimization, DSS
User support, system maintenance

2. Data management based OOD/ODB: OBJECT CLASSES
Implemented over industry standard RDBMS (SQL, e.g., ORACLE, MySQL, PostgreSQL)
DB structure uses high level of normalization:
Triplets: OBJECT ID, parameter, value
Supports dynamic DB structure extensions (add an attribute dynamically)
Supports Hypercube (OLAP) type search.

3. OBJECT CLASSES:
Structures: catchments, reservoirs, cities, irrigation districts, channels, wetlands, wellfields, aquifers, treatment plants …..
GIS, maps, overlays, spatial data
Monitoring stations, time series
Model scenarios, parameters
Auxiliary OBJECT CLASSES:
Technologies, crops, aquatic species, documents, plans, administrative data

4. OBJECT CLASS SELECTOR, one of several access mechanism to the data, top down for data management.

5. Embedded GIS, map layers for an interactive map composition tool, compatible with all major industry formats, alternative use of “live” GOOGLE maps !

6. Map catalog, (results from the map composition tool) for the selection of background maps that users can select from.

7. Map catalog examples, continued.

8. OBJECT CLASS “cities”, map display (over a live Google map) , cities scaled by population (example Turkey)

9. Configuration dialog for the OBJECT attribute display style (symbol color, size/scaling)

10. Sub-catchment, river basins: a central OBJECT class in WaterWare (direct input for the rainfall-runoff model)

11. Sub-catchment example including land use and elevation distributions.

12. OBJECT CLASS: river reach with a cross-section display/editor link
OBJECT CLASS: river reach with a cross-section display/editor link. Used for routing related parameters, lateral inflow coupling, interaction with the groundwater (in/ex filtration), and EVPT (bank evapotranspiration)

13. Reach editor (from the Water resources model) that inherits data from a reach object.

14. OBJECT CLASS: river reach, import of external descriptive data and parameters.

15. Interactive editing of river reach parameters: menu driven editor tool offers symbolic lables with associated numerical defaults to simplify editing. Can be extended with RULES, offers a trace/log function of changes (user, date, values).

16. OBJECT CLASS: reservoirs, storage node that effects flow (release rules) , evaporation, optional hydropower, diversion to alternative use/allocation.

17. Emebedded support tool
Emebedded support tool *unit converter) to support editing from external data sources using different units of measurement.

18. Linked support tool: interactive editor for a reservoir storage level/surface area/volume diagram

19. .OBJECT CLASS: city (consumption node) size, population, land use, and economic activity, distribution losses, can be used to estimate water demand.

20. City OBJECT: on screen digitization of “functional” city borders, based on satellite imagery (GOOGLE).

21. OBJECT CLASS: agricultural demand node (farm)
OBJECT CLASS: agricultural demand node (farm). Farm parameters (land use, economics) can be used to estimate water demand.

22. Farm object: editor for land use distribution.

23. Data driven architecture: HTML TEMPLATE that controls the layout for an OBJECT display (one of several layers of used define configuration options)

24. OBJECT CLASS: irrigation district
OBJECT CLASS: irrigation district. Can be edited directly, or inherit demand data from the IWD (irrigation water demand) estimation model.

25. Irrigation district editor: crop distribution editor, linked to a CROP data base.

26. CROP DATA BASE: provides crop specific physiological and economic data for the IWD model and the optimization branch.

27. CROP DATA BASE, example.

28. Monitoring station (meteorological parameters, optional air quality) links to the associated time series of monitoring data (selector at the bottom)

29. Monitoring station example, weather radar.

30. Monitoring station with associated time series including model generated data (re-analysis, dynamic downscaling)

31. Monitoring station example, streamflow.

32. Monitoring station, links to the associated time series of monitoring data (selector at the bottom) from various data sources (selector tabs above the time series list)

33. Monitoring time series, streamflow
Monitoring time series, streamflow. Upper panel shows multi-year data, panel below a select sub-period down to hourly data.

34. Monitoring time series, daily data within a month selected from the long-term overview (marked RED)

35. Data management: OBJECTS
Attributes: hypermedia, georeferenced
Dynamic instantiation (user/session specific)
Inheritance, overloading (interactive “intelligent” editors, change log, rule-based support)
Continuous integrity checks
Content analysis: basic statistics
Completeness/coverage
Consistency
Plausibility

36. OBJECT DATA ANALYSIS: (CLASSS or attribute filtered subset) analysis of attributes for completeness, consistency, plausibility (ranges)

37. OBJECT DATA ANALYSIS: summary of completeness analysis across the data base objects. The panel lower right logs the RTXPS driven continuous scheduled test runs.