...
A continuous accounting 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 (as shown here). The parameters to configure are described in Table 1. Note that 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 continuous accounting system, the following account types and triggers 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;
- Trigger Write-Off
- High Security Group 2 - same as for High Security Group 1 but relates to a separate, lower priority group of high security users;
- Trigger Write-Off
- Generic System Share 1 - used to allocate water to another Resource assessment system;
- General Security 1 - allows you to define accounting rules and shares for general security accounts;
- Usage Limit One Year; and
- Usage Limit Three Years.
Info | ||
---|---|---|
| ||
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. |
Figure 1. Continuous accounting (Configuration)
...
Item Name | Description | |
---|---|---|
Owner | Volume of water available for the system based on the ownership share of any assigned storages. Ignore for ownership off case. | |
Debit Type | Determines how water is deducted from all accounts associated with this continuous accounting system; based on either order or extractions. | |
Timesteps per Assessment | Defines number of time-steps between assessments. | |
Start of Water Year | Day-month that the water year starts for the continuous accounting system. Relevant for high security accounts as they are treated as annual accounts. The water year is also applicable to usage limits for the general security accounts. | |
No further resource assessments from this date | Day-month after which no further resource assessments should be conducted. | |
Assigned Storages Table | Lists all storage scenarios. These can be included as resources for the Resource Assessment System if required. |
The Resource Allocation Table defines the allocation priority when there is more than one account type:
- Account Type
...
- - Lists the account types available by default in a continuous accounting system
...
- ;
- Allocation Priority
...
- - Determines the order in which account types will be credited during a resource allocation
...
When you add a continuous accounting 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;
- Trigger Write-Off
- High Security Group 2 - same as for High Security Group 1 but relates to a separate, lower priority group of high security users;
- Trigger Write-Off
- Generic System Share 1 - used to allocate water to another Resource assessment system;
- General Security 1 - allows you to define accounting rules and shares for general security accounts;
- Usage Limit One Year; and
- Usage Limit Three Years.
...
icon | false |
---|
...
- ; and
- TOL Share - It also defines the TOL allocations for each eligible system account type.
Accounts
The Accounts tab (Figure 2) provides a summary of the accounts that have been added to the system. A description of the parameters in this tab are provided in Table 2.
Figure 2. Continuous Accounting (Accounts)
Info | ||
---|---|---|
| ||
Note: In IQQM, Number of shares is named Licence Volume. Additionally, the Initial balance parameter is not available. |
Table 2. Continuous Accounting, Accounts parameters
Item Name | Description |
---|---|
NameName of the account | Account name |
Account hostThe | host that is attached to Type of water user node which is associated with the account. |
Account type | The type of account |
Number of Shares | Defines the entitlement of the water user in terms of number of shares in the system. |
Initial balance | Initial account balance. If you are going to use the initial account function, you need to ensure that there is sufficient water in storages to cover the total initial balances as well as the required reserves and TOL balance. If the initial balances are set too high a warning message will be generated and the results may not follow the required logic. |
...
Figure 4. Continuous Accounting (Storage loss reserve)
...
High Security Groups
...
Figure 5. Continuous Accounting (High Security Group)
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 their 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 3 describes the parameters that must be specified.
...
Figure 6. Continuous Accounting (Generic system share)
The following parameters must be specified for a GSS:
...
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.
TO BE CHANGED:
In the Resource Assessment Explorer, when you choose to the Function Editor dialog allows you to link two resource assessment systems using the Time of Evaluation tab. Normally, fields in the function 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 up-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 7) 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 4. In the example shown in Figure 7, allocations have been defined to general security account should be simulated using the in-built continuous accounting functionality. There has been no restriction set on the minimum or maximum balance volumes. If, for example, 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 three consecutive water years. These rules replicate the conditions for the Namoi river system.
Figure 7. Continuous Accounting (General Security)
Table 4. Continuous Accounting, General Security parameters
Item Name | Description |
---|---|
Time series Allocation | Allows you to define a time series file of volume to be allocated per unit share at that time-step. This volume is added to user’s accounts based on their number of shares. It also allows you to specify a function for allocation to GS. |
Simulate Allocation | Determines the allocations to general security accounts which assess water availability. |
Maximum Balance | Defines the maximum volume of water which can be held in an account. If an allocation results in this limit being exceeded, then the excess amount is redistributed to other accounts. |
Minimum Balance | If a minimum balance is defined, then order or extractions will not be allowed if it will cause the balance to drop below the minimum specified. This is not included in IQQM. |
Usage limits
Click Usage Limit One Year to place a limit on account usage within one year (as shown in Figure 8). You can configure this for three years as well using the Usage Limit Three Years item. Table 5 shows the parameters that must be configured for both.
Figure 8. Continuous Accounting, General Security, Usage limit
...
Table 5. Continuous Accounting, General Security, Usage limit parameters
Item | Description |
---|---|
Period | Time period that the limit applies to - Moving Water Year or or Moving Window. If a usage limits relates to a single water year, choose choose Moving Water Year and and Years set set to 1. Where a "rolling years" usage limit has been defined in IQQM for general security accounts, these should be defined as as Moving Water Year limits limits in Source. |
Quantity | Specify if the limit is is Per Unit Share or an or an Absolute quantity. To replicate IQQM, set this parameter to to Per Unit Share. |
Years / Window | For a moving water year, enter the number of years the usage limit applies to. For a moving window, define the number of days that the usage limit applies to. |
Quantity setting | Usage limit over the period that is to be applied to all accounts. |