WaterWare web version

1. a common data base used not only as a repository of information, but also as a communication medium (blackboard architecture) to link and coordinate the individual components. The main components already implemented on the web are:
2. a common web interface with all elements accessible over the Internet with a standard web browser.

For some guidance on how to build a working scenario,
please consult the Water Ware User Manual

WaterWare works on a topological network representation of a river basin that links numerous functional Nodes:

Water Resources Model and Nodes
Model description	Scenario Editor	Dynamic output TS	Reports, statistics
Consistency checks	Node editor	Start Nodes	Diversion Nodes
Confluence Nodes	Geometry Nodes	Control Nodes	Reservoir Nodes
Demand Nodes	Treatment Nodes	Recharge Nodes	Aquifers
End Nodes	Reaches

The on-line tools are accessible through a user authentication system. Users have access to all scenarios of the group (usually defined for a project or client), can view and copy them on a read-only basis. Only scenarios owned by a specific user can be changed or deleted by that user.

A common, shared public guest account is also available.

If you have any problems with your account, please contact info@ess.co.at

The WRM model interface provides tools to display an analyse model results, annual water budget summaries and a node by node analysis of water demand and supply through the network.

The main components are:

• Scenario selection;
• Summary display of network and model results;
• Budget analysis fro different demand sectors;
• Groundwater budegt.
• Node-level results, tabular and graphical.

As and auxiliary tool, a time-series import tool has been developed, to import time series data that can be prepared locally, e.g., using a simple spreadsheet like Excel, then to upload the data set to the WaterWare server and data bases.

Running the scenario

• a RUN button that can be used to trigger a run for a new or modified scenario;
• a RESULTS button, that indicates that results for theis scenario have already been computed and can be shown.

If the RUN button is pressed, the scenario checker (alternatively triggered by the button: CHECK) is automatically invoked; if no error is found, the model is run; if an arror is found, the report page of the scebnario checker is show providing guidance on how to fix the problems found. See also: WRM model scenario analysis.

The model run is performed as a background job; the run button, once pressed, is changed into a button called ABORT that can be used to kill the current model run. If and when a model run completes successfully, the ABORT button is changed to RESULTS on the next reload or revisit of the scenario page.