Note: This is documentation for version 5.16 of Source. For a different version of Source, select the relevant space by using the Spaces menu in the toolbar above">Note: This is documentation for version 5.16 of Source. For a different version of Source, select the relevant space by using the Spaces menu in the toolbar above

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »

 

 

 

 

 

 

 

 

 

A Supply Point node (Figure 1) represents a location in the river where water can be extracted to meet demands. You can specify whether water is to be taken from regulated water, unregulated water or groundwater sources. 

Figure 1. Supply Point node

Supply point configuration

Enabling Extract water checkbox will ensure that the supply point extracts water. If disabled, water will not be given to the water user, and it will be passed downstream. This is the only difference between enabling and disabling the checkbox. Disable the Extract Water checkbox for demand models which require a flow at the supply point, but require the flow to remain in-stream, ie., the order will not actually be extracted. This could be used for shepherding environmental releases, for example.

The Groundwater checkbox signifies the supply point as a groundwater. In case of the Namoi model, when enabled, this type of account has the least priority for obtaining water. It must be used only when there is crop demand and there is no available regulated and supplementary water, and water from on farm storage to satisfy crop demand. Note that this groundwater account must not prevent off allocation diversion. You must set the maximum extraction rate (ML/day) for groundwater sources.


Enabling the Allow Orders checkbox essentially means that the supply of water to the water user is regulated. This will affect water distribution if account sharing has been set up in the Water user node. Refer to Account sharing (full Source version only);

Add Orders to Downstream Orders 

This option only applies to non-extractive use and is available when Extract Water is unchecked AND Allow Orders is checked. (It behaviour becomes similar to a minimum flow node)

If a water user attached to the supply point is 'requiring' water, the water user requirement volume is added to the downstream orders.

e.g Downstream of the supply point there is currently a 20ML order downstream, the water user requires 30ML, the supply point will order 30ML and the total ordered volume will be 50ML. 

When this option is unchecked it will only add to the order, if the water user requirement is greater than the downstream order, and it will only order the difference.

e.g Downstream of the supply point there is currently a 20ML order downstream, the water user requires 30ML, the supply point will order 10ML and the total ordered volume will be 30ML. 

Use Unregulated Flow to Satisfy Orders

This option is only available when Allow Orders is checked, Add Order to Downstream Orders is checked AND Extract Water is unchecked.

When this option is checked the forecast unregulated water is considered to be available and the supply point will only order the difference.

e.g Downstream of the supply point there is currently a 20ML order downstream, the water user requires 30ML, 10ML forecast unregulated water, the supply point will order 10ML, the total ordered volume will be 30ML. 

When this option is unchecked the forecast unregulated water is considered to be unavailable and will order the full amount.

e.g Downstream of the supply point there is currently a 20ML order downstream, the water user requires 30ML, 10ML forecast unregulated water, the supply point will order 20ML, the total ordered volume will be 40ML. 


Specifying an Over Order Factor  will allow you to choose apercentage factor representing additional water released to meet a particular order, eg a factor of 1.2 or 120% means that the demand is scaled up by 20% in the ordering phase. The additional water is sourced from the upstream storage

Units: Percentage or proportion

Allowable range: Positive integer (%) greater than or equal to 100. Values of less than 100 (%) or 1 (proportion) are changed back to 100% or 1.

Default value: 100%

Note: Accounts are not debited for the additional water ordered as a result of the over order factor.

During the flow phase, the extraction actually available to the water user is the minimum of i) the original order (not including the over order factor), or ii) the physical extraction capacity, or iii) any river flow constraints.

The over order factor does not necessarily need to incorporate all estimated delivery losses in the system. If there are upstream nodes or links which simulate losses in the system between the storage and the supply point, Source automatically increases the order to account for estimates of those losses. Refer to the individual node descriptions in the Source Scientific Reference Guide for methods used to estimate losses.

The over order factor is used to add further contingency to a storage release. It should therefore only be calibrated after the physical characteristics of the system have been completely configured. It is up to you to select (or calibrate) an over order factor which is realistic for the system (to ensure that unnecessary water is not released from the storage).

 

Overbank Threshold

The overbank threshold should be configured if you want to simulate floodplain harvesting by the water user. Overbank flow occurs if the flow rate in the river rises above the specified overbank threshold. Any overbank water can be used to meet the demand model or water user storage requirements without incurring a debit on the water user’s accounts.

Note: The following assumption is made - the overbank flow is pumped into the storage and as such is restricted to the storage pumping rate

Overbank Pump Capacity

The overbank pump capacity 

Diversion Threshold

The supply point will not be able to pump any water below the diversion threshold. It tries to mimic the fact that the pump may not be at the very bottom of the river. Therefore, you need a certain volume of water in the river before you can pump any at all. It affects the system during the flow phase of the supply point only.

Specify maximum account deduction (full Source version only)

If Extract water is not enabled, you can specify maximum account deduction which will limit water debited to an accounting system; if this deduction cap is more than total order water, the total order water is debited. This parameter can be specified as a value or a function.


 

Maximum Extraction Rate

 

Travel Time

Source determines the travel time from the closest and further storages to the supply point. This is done using the defined routing models on the links. Note that for storage routing models, you must enter an Average regulated flow, which is used to determine the travel time. After running a scenario, the calculated travel time can be viewed in the Recording Manager under type Miscellaneous and attribute Rules-based orders. Refer to Ordering for more information.

If there are multiple upstream storages which can provide water to the supply point then Source automatically determines which storage is used. In a rules based model, this works as follows:

If the storages are in series then all orders are sent to the closest storage. This storage must be configured so that it orders water from upstream storages to maintain a target operating level; and

If the storages are in parallel then a confluence node is used to join the two regulated branches. Rules specifying how to distribute orders between the two branches are specified at the Confluence node.

 You can set a limit for the overbank and diversion thresholds as well. 

Note: Only one of the effluents from a supply point node must connect to a water user node.

The absence of a limit on supply point pumping capacity can lead to a situation where the Maximum Extraction Rate result set cannot be displayed because it will contain infinite values resulting in an empty graph. If this occurs, consider setting both a finite limit on pumping capacity and an overbank threshold.

Checking constraints

When a constraint is enforced, there may be a difference between the amount of water ordered and released. The differences are recorded in the Recording Manager. For more information, refer to Identifying constraints.


  • No labels