...
A Source model consists of two parts - a project and one or more scenarios. A project is a wrapper for a collection of one or more scenarios. It identifies the project name, description, and any scenarios associated with the project.
A scenario is the representation of a node-link network in Source and describes the major processes in a river system or catchment that are modelled. This includes catchment and sub-catchment definition, rainfall runoff and constituent generation models, data sets and parameters.
Three scenario types are available in the core Source framework.
- A schematic scenario is primarily concerned with modelling longer time-scales;
- An operations scenario is primarily concerned with shorter time-scales. It utilises facilities for forecasting and working with unaccounted differences, and typically makes heavy use of the Tabular Editor; and
- A catchments scenario which deals with the management of upland catchment processes.
An Urban demand scenario, currently available in the same location as the others when the Urban plugin is installed, is used to represent the integrated urban water cycle networks (water supply, stormwater, wastewater), ranging in scale from a single allotment up to large clusters or small subdivisions.
Allotment Scale
...
...
Cluster Scale
A small grouping of 2 - 30 allotments, businesses and/or commercial premises.The cluster scale is particularly useful for exploring decentralised supply, treatment, reuse, and disposal options, as it enables potential for some economies of scale in infrastructure delivery, and ameliorates some of the need for expensive centralised distribution and collection infrastructure.
...
, or the impact of urban water use restrictions on total system water supply.
Figure 1. presents an outline of the steps and options available in creating and modelling Urban end-use demands within Source. While a Source Urban Developer Scenario can be run at a local scale representing single scenario urban demands, it is most powerful when run at a larger scale where modelled urban demands are incorporated into a Source scenario
While this documentation describes the configuration of a single Water Use node, multiple nodes can be added in an Urban Developer scenario, particularly if running the scenario in ‘stand-alone’ mode as a single Urban Configuration.
Figure 1. Using the Urban developer plugin to model urban demands in Source
Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
Navigating the User Guide
The Urban Developer Plugin User Guide contains two parts:
- Building and running an Urban Scenario in Source: describes how to create, configuration and run an urban water systems model
- Linked River System Scenarios: describes how to integrate an Urban Scenario with Source schematic or catchment Scenarios.
The Urban Developer Plugin User Guide assumes that readers are familiar with the eWater Source modelling framework.
Acknowledgements
eWater gratefully acknowledges the leadership, financial and technical support of Melbourne Water in the preparation of the Urban Developer Plugin. eWater also acknowledges the work of Dr Mark Thayer in developing the behavioural end-use stochastic simulator (BESS) for household water simulation that is used in Urban Developer.
This material has been adapted from:
eWater Cooperative Research Centre (2011) Urban Developer User Guide: Urban Developer v1.0.0, eWater Cooperative Research Centre, Canberra, 29 June 2011. ISBN 978-1-921543-40-1