Many regulated river systems support several resource assessment schemes to share the available resource (water) amongst users. In Source, a resource assessment system:

• is associated with only one scenario in a project, whereas a scenario may be associated with one or more resource assessment systems;
• can only have one owner, but any given owner or water user may be affected by more than one system; and
• supports multiple account types.

Note that resource assessment only operates correctly in a regulated system.

Image Removed

#anchor-24-anchor Figure 104 shows the various contextual menus available for each level in the resource assessment hierarchy. Note that similar types of accounts or systems have the same contextual menu. For example, all off-allocation systems have the same contextual menu, and all account types follow a similar trend.

Image Added

In practice there are a number of resource assessment methodologies used, which can be implemented in Source using a generic resource assessment tool, referred to as Simple Water Accounting. The next section provides details on configuring two types of resource assessment in Source - general and continuous sharing.

General Resource Assessment

For detailed information about resource assessment, refer to the Source Scientific Reference Guide. To enable General Resource Assessment:

• Choose Edit > Resource Assessment... from the Source main menu;
• Click + to the left of the project name (Figure 84104) to reveal the project’s active scenarios; and
• Right-click the scenario for which you wish to enable resource assessment and choose Add Simple System from the contextual menu (Figure 84104).

You can edit the system name by right clicking on the name and choosing Rename from the contextual menu. Type in the field and press the carriage-return.

Image Removed

Once a system has been added (Figure 85105), provide the following details:

Image Added

• Set the system Owner. There can only be one owner per system; and
• Set the Water Year Start date. The system will run for 365 days from the date set.

You can also configure an off-allocation system and an account type by right-clicking the system name and choosing from the contextual menu.

Adding an account type

A system may contain several account types, each consisting of many accounts that have common properties. With resource assessment, you can group accounts according to different levels of water security, or any other common criteria appropriate to a set of accounts.

To add a new account type, right-click the system name and choose Add Account Type (Figure 85105). If desired, you can edit the account type name to be more meaningful.

Image Removed

When an account type is selected, the right hand panel displays two tabs - Details and Allocation. The former (shown in Figure 86106) is a summary of operating information for each account type, whereas the latter (shown in Figure 87107) calculates account allocations using either a time series, expression or results from another scenario.

Image Added

Note that allocation data is interpreted as a cumulative volume allocated per unit share. This means that accounts are only credited if there is an increase in allocation volume since the previous timestep. An account is credited by calculating the increased volume multiplied by the number of shares that the account has in the resource assessment system.

The Originating Allocation System item in the Details tab is a feature relating to tagged trading. In the current version of Source, this functionality is not available.

Image Removed

Adding an account

In the Resource Assessment Explorer window (shown in Figure 87107), right-click on the Account Type in the left hand panel and choose Add Account from the contextual menu.

Image Added

You can configure the properties of an account using the panel displayed in Figure 88108. Note that:

Image Added

• Each account can have only one water user associated with it;
• You must enter the number of shares that the account has in the resource assessment system; and
• You can specify an opening account balance.

Account type triggers

A trigger initiates or cancels certain actions for an account type and can be configured using the properties panel shown in Figure 90. To set up a trigger, right-click the account type on the left hand panel and choose Add trigger.

Triggers can be set to activate on a particular date, a year start or end or the passing (either raising or falling) through a specified storage water level. When a trigger is activated it will initiate a pre-defined action, which is defined in the panel on the right hand side of the Triggers window. Possible actions include:

• Transferring a percentage of water to another account;
• Levelling accounts;
• Writing off accounts; and
• Truncating or assigning accounts.

An account type can have several triggers, each designed to initiate a particular action. Triggers can be prioritised by moving them up or down under Trigger Precedence.

Usage limits

You can limit water usage for all accounts by absolute volume or a per-unit-share, which can cover a water year or movable time window (shown in Figure 89). You can define any number of usage limits.

• To add a usage limit, right click on Account Type and choose Add Usage Limit;
• To delete a usage limit, right click on it, and choose Delete; and
• You can also rename it using the contextual menu.

Image Removed

Image Removed

Note that the usage limit, regardless of its position in the hierarchy, requires the same parameters to be configured. Figure 89 is therefore the same for all invocations of usage limit.

Image Removed

Continuous Sharing Resource Assessment

Usage limits

You can limit water usage for all accounts by absolute volume or a per-unit-share, which can cover a water year or movable time window (shown in Figure 109). You can define any number of usage limits.

Image Added

• To add a usage limit, right click on Account Type and choose Add Usage Limit;
• To delete a usage limit, right click on it, and choose Delete; and
• You can also rename it using the contextual menu.

Note The usage limit, regardless of its position in the hierarchy, requires the same parameters to be configured. Figure 109 is therefore the same for all invocations of usage limit.

Account type triggers

A trigger initiates or cancels certain actions for an account type and can be configured using the properties panel shown in Figure 110. To set up a trigger, right-click the account type on the left hand panel and choose Add trigger.

Image Added

Triggers can be set to activate on a particular date, a year start or end or the passing (either raising or falling) through a specified storage water level. When a trigger is activated it will initiate a pre-defined action, which is defined in the panel on the right hand side of the Triggers window. Possible actions include:

• Transferring a percentage of water to another account;
• Levelling accounts;
• Writing off accounts; and
• Truncating or assigning accounts.

An account type can have several triggers, each designed to initiate a particular action. Triggers can be prioritised by moving them up or down under Trigger Precedence.

Continuous Sharing Resource Assessment

A Continuous Sharing Resource Assessment System is one in which the behaviour of a water user has as little effect as possible on other water users within that system. For detailed information about continuous sharing resource assessment, refer to the Source Scientific Reference Guide. To enable it in Source:

• Choose Edit > Resource Assessment...;
• Click + to the left of the project name (Figure 84104) to reveal the project’s active scenarios; and
• Right-click the scenario for which you wish to enable resource assessment and choose Add Continuous Sharing from the contextual menu (Figure 84104).

You can rename the system using the same method for simple resource assessment systems. Refer to General Resource Assessment.

Image Removed

System ConfigurationSystem Configuration

To configure a continuous sharing system, start by selecting the owner whose share is described by this system from the Owner pop-up menu (Figure 91111) and define the start of the owner’s water year. The owner may be any one of the defined owners in the physical system being modelled. The other owners are assumed to use separate allocation systems, with all calculations occurring independently.Note At present, ownership is not guaranteed to be fully functional and should be used with care. Unless you have a specific need, use the default owner, Unassigned Water, for all allocation systems.

Image Added

The sharing of various system losses is based on long term averages. Over time, discrepancies will emerge which must be reconciled. You can control the frequency with which reconciliations occur using the Timesteps per Reconciliation field. The default is one time-step. Shortfalls identified during a reconciliation are treated as storage losses, gains as inflows. Losses and gains are shared equally and based on account share sizes, but ignore account priorities.

The reconciliation process also resolves situations such as when multiple resource assessment systems draw upon the same water (whether such a configuration is accidental or deliberate).

The second step is to specify the percentage shares that the owner has in each storage known to the system. You use the Owner Shares tab in the relevant Storage feature editors to accomplish this.

Next, select each storage that should participate in the continuous sharing system in the Unassigned Storages list and move it into the Assigned Storages list by clicking the button with the right arrow. Note that a storage can be removed from the Assigned Storages list by selecting the storage and clicking the button with the left arrow.

As each storage is added to the Assigned Storages list, the owner’s share in that storage is added to the Total Conceptual Storage field, which is the sum of the active capacity for this owner of all of the assigned storages in the resource allocation system. You can not edit this value directly.

By default, 100% of all allocations are considered to be high priority but you can designate a lesser proportion by adjusting the High Priority Allocation field. The related fields of High Priority Storage, Medium Priority Allocation and Medium Priority Storage adjust dynamically in response.

You can adjust the Medium Priority Threshold field to determine how inflows are assigned to accounts. The field behaves as follows:

• When storage is below the stipulated threshold, inflows are only assigned to high priority accounts; and
• When storage is at or above the stipulated level, inflows are assigned to both high priority and medium priority accounts according to the percentages entered in the respective priority allocation fields.

The default Medium Priority Threshold is zero which means that inflows will be assigned to both high priority and medium priority accounts.

The System Cap Balance Carryover specifies the maximum proportion of the owner’s annual resource cap that the system can carry over into the next water year.

Finally, you can define the loss characteristics of each storage in millimetres per day between one or more start- and end-date pairs within the water year. You can also import loss characteristics from a .CSV file formatted as shown in Table 57100.

Adding Accounts

To add accounts to a continuous sharing resource assessment system, switch to the Accounts tab (Figure 92112) and click Add Accounts to open the Add Accounts window (Figure 93113). The nodes which appear in the list on the left hand side of Figure 93113 are Water User nodes, otherwise known collectively as demand nodes. Select one of the nodes in this list and click OK.

To add accounts for more than one demand node to a resource assessment system, repeat the process of clicking Add Accounts, selecting the relevant demand node, and clicking OK.

Accounts are always added in pairs. Each demand node always has one high priority account plus one medium priority account. Note that, where the High Priority Allocation is 100% (Figure 91By default, an account of each type (ie a high priority and medium priority allocation account) is added for each water user, although only one account is required to have a maximum account balance greater than zero. Note that, where the High Priority Allocation is 100% (Figure 111), the medium priority account will remain unused.

You can delete an account-pair by selecting either of its members and clicking Delete Accounts. Image Modified

Account configuration

You can configure individual accounts by manipulating the controls shown in Figure 92112. Fields that are grey can not be adjusted. They fall into three categories:

• Values that are inherited from previous steps and which are included for reference. Examples include the Name, Type and Priority fields;
• Values that are set by reference to other values. The Maximum Balance column is an example; or
• Fields that must first be enabled explicitly. For example, you must enable the relevant Spec Cap checkbox before you can specify an Annual Cap.

You can allocate shares water by shares or volume. You can also specify a maximum cap (Max Cap) for an account by enabling the Spec Cap check-box and entering a capacity volumetric limit in megalitres. A value of zero means no cap is enforced.The share factor ((ML) in the ‘Annual Cap’ field. This cap will limit the annual volume diverted by the associated water user.

The share factor (Share Fact) defines the relationship between orders and the amount that must be released in response to those orders, having regard to losses and gains during transmission:

• A share factor in the range 0.0 < Share Fact < 1.0 indicates that a loss is expected to occur between the storage and supply point. The closer to zero, the greater the loss;
• A share factor of 1.0 indicates perfect transmission between the storage and supply point; and
• A share factor greater than 1.0 indicates gains are expected to occur during transmission, such as inflows from a tributary.

All share factors at a given priority level within a continuous sharing system are interrelated as follows:

Image Removed

Unless overridden, subsequent calculations, such as the maximum balance, inflow share and annual cap are based upon that ratio.

Image Removed

Removing components

You can remove components from the Resource Assessment Explorer hierarchy by right-clicking on the entry you want to remove, then choosing Delete from the contextual menu. You can only remove components that you added. You can not remove project or scenario components.

• ;
• To account for the transmission losses and gains, the volume of water released from a storage to meet a water user’s order is calculated as the Order divided by the Share Fact; and
• Accounts with a lower share factor are allocated a larger share of the storage to account for the transmission losses they incur.

All share factors at a given priority level within a continuous sharing system are interrelated as follows:

Image Added

Continuous Accounting

A Continuous Accounting (CA) resource assessment system can be created in Source to replicate the Resource assessment system used in the Gwydir and Namoi in NSW. There are a number of defining features of a CA system which differentiate it from continuous sharing and annual allocation systems:

• Assessments of whether a new allocation can be made occur intermittently (based on triggers defined within the plan) with a new allocation resulting in an additional volume of water added to user’s accounts. With continuous accounting, there is no end of year forfeiture of allocation. There are, however, limits on the volume that can be held in a general security account at any one time and usage limits may also apply;
• An account is maintained for the system as a whole to meet transmission and operation losses (TOL) for delivery of regulated water. An accounting process is followed to determine whether any of the available storage volume is unallocated. The unallocated volume remains after the following have been deducted from the active storage volume:
• reserve required for storage losses;
• reserve required for high security uses including an allowance for transmission losses to deliver these supplies;
• existing volume allocated to the generic system share/s;
• existing volumes allocated to general security entitlements in this system; and
• the volume required to be held in the system’s transmission and operation loss account.
• High security accounts are assigned an allocation based on a defined relationship between percentage of the high security reserve met and allocation to accounts. The reserve set aside for high security uses is generally greater than the volume that is allocated to the high security accounts. Whilst the full reserve volume is set aside at each resource assessment prior to making an additional allocation, the accounts are only assigned an allocation on an annual basis.

The enhancements to continuous accounting in Source over IQQM are:

• Ability to simulate more than one type of resource allocation and accounting method in the one scenario and to link one system to another;
• Ability to specify data to calculate the initial balance of the usage limit;
• Better simulation of management during dry periods including the ability to:
• Restrict allocations to high security accounts during dry periods where the required reserve cannot be met;
• Define the TOL factor as a variable depending on account balances. This allows a higher factor to be defined when balances are low, as a higher proportion of the allocations will be required to cover transmission losses; and
• Represent the rules which may reduce the required high security reserve.

Adding a continuous accounting system

A CA system can be added to a particular scenario in a project using the Resource Assessment Explorer (Edit > Resource Assessment...). Right click on the scenario and choose Add Continuous Accounting from the contextual menu (Figure 114). The parameters to configure are described in Table 101. The Resource Allocation Table defines the allocation priority when there is more than one account type. It also defines the TOL allocations for each eligible system account type.

When you add a CA system, the following account types are automatically loaded:

• Storage Loss Reserve - define the reserve required for evaporation and seepage losses from storage;
• High Security Group 1 - define the reserve required for high security users. Also allows you to define accounts which relate to this reserve and the method for allocating water to these accounts;
• High Security Group 2 - same as for High Security Group 1 but relates to a separate, lower priority group of high security users;
• Generic System Share 1 - used to allocate water to another Resource assessment system; and
• General Security 1 - allows you to define accounting rules and shares for general security accounts.

Note IQQM includes a number of inbuilt triggers which are not replicated in Source. For this reason, the Timesteps per assessment parameter may need to be set to 1. Additionally, to replicate IQQM, the TOL Share parameter on the high security account type should be zero.

Accounts

The Accounts tab (Figure 115) provides a summary of accounts which have been added to the High Security and General Security account types. Additional Water User Account information is also displayed for each General and High Security Account type. A description of the parameters in this tab are provided in Table 102.

Image Added

Note In IQQM, No. of shares is named Licence Volume. Additionally, the Initial balance and Previous Usage parameters are not available.

Storage Loss Reserve

The storage loss reserve (Figure 117) is a volume which is required to account for expected evaporation and seepage losses from the storage. The reserve is debited from the available resource prior to making any other allocations. It may be made a function of the current storage volume or area, which can be specified using an expression. A minimum percentage of the required reserve that must be maintained can also be specified; restrictions are applied to general security accounts (or lowest priority account type) to achieve the required minimum reserve.

Image Added

The following parameters must also be specified:

• Minimum to cover storage losses - Defines the percentage of required reserve below which borrowing occurs. This parameter is not available in IQQM, so it must be set to zero; and
• Storage Loss Reserve Requirement - the reserve required to cover storage evaporation and seepage losses. Note that in IQQM, this requirement is defined through the number of months that evaporation is take into account. In some cases the storage loss is combined into the carryover reserve.

High Security Groups

High Security Groups (Figure 118) define the reserve which is required for high security users (may also be referred to as essential supplies). The high security reserve requirement may be defined using two groups - a higher and lower priority group. In the case where only one group is required, you can delete the other by right clicking on the item and choosing Delete. Additional groups may also be added (right click on the CA system and choose the desired system to be added). This can be specified as a fixed value or as an expression. The latter can be used where there are rules that vary the high security reserve requirement.

Image Added

High Security accounts are treated as annual accounts with no carryover. In other words, at the start of a water year (as defined at the system level page) all accounts have the existing balance deleted and a new allocation is made. Allocation to high security accounts can be defined using a time series file or simulated based on whether or not the reserve requirement has been met. The Allocation Rules table allows you to define restrictions on allocations to high security accounts if the reserve requirement has not been completely met. The high security shares held by each water user is defined in Accounts. For example, if 1ML is the total reserve, and only 20% of the required high security reserve has been met, then high security accounts will only be given 0.3ML per entitlement share. Table 103 describes the parameters that must be specified.

Generic System Share

The generic system share (GSS) is used to allocate water to another resource assessment system. Water user accounts cannot be added directly to the GSS account from within the Resource Assessment Explorer. The accounts associated with the GSS are configured as part of the linked system. The GSS is credited as part of the continuous accounting allocation method and is debited when accounts in the linked Resource assessment system are debited. If an allocation is made to the GSS, this volume is distributed to users as part of the resource assessment phase of the linked system. The configuration dialog is shown in Figure 119.

Image Added

The following parameters must be specified for a GSS:

• Time Series Allocation - Enables the entry of a time series file for allocating to the GSS;
• Simulate Allocation - Define an expression to allocate to GSS. The value of the expression is treated as a volume to be added to the GSS account subject to available water limitations; and
• Total Volume Initial Balance - Initial balance in the GSS account.

GSS is generally used with resource assessment system linking to an annual accounting system where a portion of the resource assessment system is determined by the output of another system.

In the Resource Assessment Explorer, the Expression Editor dialog allows you to link two resource assessment systems using the Time of Evaluation tab. Normally, fields in the expression editor are lagged by a time-step (that is, they get their value from the last time-step to use in the current time-step). Enabling the During Resource Assessment checkbox results in the resource assessment system linked parameters being executed within the current time-step. As long as the resource assessment system appears above another resource assessment system in the hierarchical list, the values will be update-to-date in the time-step. Conversely, if one resource assessment system appears below a linked resource assessment system, its values will be lagged by a time-step.

General Security

This item (Figure 120) allows you to define accounting rules for accounts. The general security shares held by each water user is defined using the Accounts tab. The parameters that must be specified are described in Table 104.

Image Added

In the example below, allocations have been defined to general security account should be simulated using the in-built continuous accounting functionality. There is a maximum balance of 2ML per entitlement share. This means that if a water user has an entitlement of 200 shares, their maximum account balance is 400ML. Two usage limits have been defined. The first says that no more than 1.25 ML can be used per entitlement share in any water year. The second says that no more than 3ML can be used per entitlement share in any 3 consecutive water years. These rules replicate the conditions for the Namoi river system.

Ownership and resource assessment

Resource assessment systems are generally used with ownership when one owner has borrowed from a second owner, and payback is required. One method of paying back water can be accomplished through a resource assessment system. Refer to Borrow and payback with resource assessment for further details on configuring this arragement in Source.

Where: flux is the loss in millimetres per day for the recurrent period defined by start through end
start is the first day of each year represented as dd-mmm (eg "01-Jan") on which flux begins
end is the last day of each year represented as dd-mmm (eg "01-Jan") when flux ends.