A Source model consists of two parts - a project file and one or more scenarios. A project file 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 represents the major processes in a water resources system using Source's node-link framework.
An Urban Scenario is used to represent the urban water cycle networks (water supply, stormwater, wastewater), ranging in scale from a single allotment up to large clusters or small subdivisions.
Once the Urban Developer Plugin has been installed, Urban Scenarios can be created like other scenarios in the core Source framework. Refer to Projects and scenarios for details. Figure 1 shows the main user interface for an Urban Scenario.
Figure 1. The Urban Scenario main user interface.
...
Demand and End-use Simulation
Urban Developer represents demand by simulating individual end-uses at the household level. The end-use categories included in Urban Developer are:
- outdoor/variable;
- shower;
- washing machine;
- toilets and
- indoor hand taps
These five end-uses typically comprise 93-98% of household water use (Thyer et al., 2008). End-uses such as baths and leaks are not modelled explicitly, but can be lumped with the outdoor/variable end-use. By separating demand into its individual users this provides the user with the flexibility to use different sources for each of the different types of end-use.
The urban demand is represented by a Water Use node. Urban Developer offers two methods for simulating the water use at a water use node, either:
- Average daily model, or
- Behavioural model, with three different configurations:
- Fixed appliances and occupancy specified for each water use node in the model
- Randomly sampled values for appliances and occupancy across the water use nodes in the model
- Average appliance demand (which can be used in conjunction with fixed or sampled appliances and occupancy).
Contents
| Child pages (Children Display) | ||
|---|---|---|
|
...