...
...
This model also forecasts flows. Forecasting is required to estimate how much flow is likely to occur at a particular point in the system some time in the future, and hence how much additional water needs to be ordered to meet demand.
Create this model in Source as described in , which results in the window shown in Feature Editor 33. Click Edit to define the rules, which opens the Environmental Demand Model dialog (Figure 48), and Select... to specify where the output will be saved.
...
/requirements. These requirements may be directed at in-channel and/or floodplain habitats and ecosystems.
| Info | ||
|---|---|---|
| ||
In Source, Environmental Demand (ED) is modelled using the environmental demand node. Refer to Environmental Demand for further details. The node can be configured to fulfill either in-stream or floodplain requirements. It is important to note the two different ways in which an ED node can be set up. These are:
Note: Although it is essential to understand the two distinctions, it is possible to fulfill many in-stream and floodplain requirements in the same model by changing the configuration of the node. |
Using the node in Source
Double-click the node to open its feature editor, shown in Figure 1. If you have an account configured (using the Resource Assessment Explorer), you will be able to enable or disable Account Distribution using the contextual menu shown.
You can select whether the EDM is inclusive or exclusive of downstream orders. If inclusive (default value), then the order generated by the EDM will be the difference between the EDM’s water order and the downstream order. In this case, the Inclusive of Downstream Orders slider is selected to YES. This assumes that the EDM can take advantage of the required water downstream to meet all or part of its requirements. If the EDM is exclusive of the downstream order, the EDM’s water will be added to the downstream order - the slider is selected to NO.
Figure 1. Environmental Demand node
Flow rules
The four types of flow rules presented in the EDM have been designed to capture the most commonly defined environmental flow requirements specified in environmental flow studies and water regulations. These four types of environmental demand rules allow users to construct a collective environmental water requirement by using combinations of environmental demand rules. The four rule types are:
...
...
...
...
Forecasting
The basic approach to determining water order is to consider the collection of flow rules and determine how much water is required for a given day to meet these rules. As water is not consumed by the EDM, the water order is simply the difference between the calculated water required and the forecast flow at the extraction point on the future delivery day.The EDM allows two forecasting periods, a short term and a medium term. This approach is to reflect real world water management decision making, whereby, depending on the size of the catchment, river operators can generally make a very accurate prediction of the likely flow for the next few days to weeks. After that time the prediction is less accurate. You can use the Expression Editor or specify another scenario to define the method of forecasting. The recommended methods for the look ahead period are to refer to an upstream node with a known travel time.
Base flow
The base flow objective is designed to capture minimum flow rules, such as where flow should be maintained above a certain limit for particular periods of the year. Figure 48 shows the parameters that must be specified for base flow. The controls for Input data and Forecast allow you to upload data as a time series file, an expression, or linking to another scenario.
Figure 48. Water User node (Environmental Demand, Base flow)
...
...
...
...
Flow pattern
You can create a temporally varying rule by simply defining the pattern of the flow required as well as a trigger condition. The trigger condition will be either a set start day or a flow threshold which has to be reached.
Figure 3. Environmental demand node, Flow pattern
Minimum flow rule
The objective of this rule is to maintain a minimum flow in the model to maintain minimum habitat requirements, such as where flow should be kept above a certain limit for particular periods of the year. Figure 5 shows the parameters that must be specified for minimum flow.
Figure 4. Environmental demand node, Minimum rule
Translucency
This rule allows you to define conditions where flow would be allowed to pass through a storage or restrictions be placed on extraction in an unregulated system. It does not require an augmentation method as orders will be determined based on the inflows to the storage for the current time-step, and hence no forecasting is required.
Figure 5.
...
Conditions
The EDM also includes a condition tracker, which can be used to turn rules on and off. If the condition tracker falls bellow a threshold, the rule is turned on. If the condition tracker is above a threshold, then the rule is turned off. Only one condition tracker can be defined for a collection of rules. However, each individual rule can have its own threshold that decides when the rule is turned on. The condition tracker can be used to represent a multitude of environmental or accounting rules that turn flow rules on and off. Examples of using the condition tracker are:
- Representing the ‘health’ of an environmental asset; or
- Representing environmental rules that turn on and off when an account balance exceeds a certain level.
...
Environmental demand node, Translucency
Grouping and prioritising
Flow rules can be grouped into categories. The default category is selected using the contextual menu.
| Info | ||
|---|---|---|
| ||
| Note: In the default category, every flow rule within the category is considered at each time-step. In any other category, only one rule within the category can be considered at any one time. Rules are prioritised in the order in which they appear in Source. For example, in Figure 1, the Flood/Fresh rule will have a higher priority than the Minimum rule. |
Rule dependency
You can specify whether one flow rule will depend on another using the Add Rule Dependency button in the Flow Rules hierarchical item list. Figure 6, for example, shows that Flow Pattern Rule #1 will only come into effect when Minimum Rule #2's condition has been met.
Figure 6. Environmental demand node, Rule dependency
Condition
Flow rules can be made active or inactive dynamically during a modelling run. In order to control rules throughout the model run, each rule can have a defined condition threshold. This condition threshold is compared to the ‘condition’ time series for each time-step and the flow rule is turned on or off for that time-step as required. This functionality is specifically designed to allow the construction of asset based rule sets that vary according to water availability.