...
Source has many standard recorders for flow nodes, which can also be reported for the Environmental Flow Node. Additional recorders specific to the Environmental Flow Node are found under ‘Environmental Flow – Name of Node – Actions – Name of Action’. The environmental flow node has a standard set of node recorders that are common across all Source nodes. Specialist recorders are then present in each node type in addition to these common recorders. Environmental Flow Nodes
...
specialist recorders are all present at
...
the Action level.
Actions
Spell Based Action
...
Average Recurrence Interval: Based on Desired Frequency. For example, Desired Frequency is 2 in 3 years, the Average Return Interval is 3/2 = 1.5 (x365 days) = 547.5 days.
Cumulative Spell Shortfall: Records the difference between the Cumulative Spell Target Volume and the Cumulative Spell Volume (actual). This is used to track success based on volume.
...
Full Requirement (Managed Spells): As the recorder above, but includes the requirement for managed spells only.
Number of Spells Completed in Season: The number of spells that were completed in a season. This includes completed spells, as well as spells that started but were stopped, when they were not able to be successfully completed within the season anymore. The counter is reset once the season is finished. A A spell is considered complete once it completes the rise-target-fall pattern or the spell has failed to meet it's success criteria and stopping failed actions is enabled. The counter is reset at the end of the action's season.
Number of Spells Started in Season: Number of times the start spell threshold flow value is exceeded within the required season, and therefore a spell is considered started. This includes ordered spells and natural spells as well as successful and unsuccessful spells. This includes completed spells, as well as spells that started but were stopped, when they were not able to be successfully completed within the season anymore. The counter is reset once the season is finished. The counter is reset at the end of the action 'Spell Threshold season.
Required Target Volume: This is the flow target level specified by the user (used to calculate success based on target level). This will reduce according to the proportion specified in the target success criteria.
Residual Requirement: This is the order the environmental flow node would have to place on top of the downstream order to reach the full requirement. The full requirement is reduced based on downstream orders, minimum upstream constraints and other actions of higher priority. When the upstream minimum constraint is larger than the full requirement, no order will be placed by the flow node (i.e. the residual requirement would be zero). The requirement is calculated at the order phase. The Residual Requirement is not restricted by account balances. When not managed by an EFM, the Residual Requirement will always be zero. [IT3] The Residual Requirement is not limited by available water in accounts.
Number of Successful Spells Completed in Season: Number of spells this season that are successful in a season. A season spell is deemed successful if the delivered volume meets the requirements specified by the action's success criteria. This includes both ordered and natural spells. The counter is reset at the end of the action's season.
Required Target Volume: This is the flow target level specified by the user (used to calculate success based on target level).
Residual Requirement: This recorder is only non-zero when the environmental flow node is used with a flow manager. The residual requirement is the amount this action will have to try to order. The full requirement is reduced based on downstream orders, minimum upstream constraints and other actions at this node that are a higher priority. This value is not restricted by account balances.
Spell Extension: Recorder flags days when spell was extended
Successful time steps in current spell: During a spell, this records the number of time steps that had a flow rate within the specified proportion of target flow required to mark success. If End spell if it will fail is not selected the count of successful time steps in the current spell will remain at the same value until either the next time step that meets the success criteria or the end of the current spell, whichever occurs first. If End spell if it will fail is selected the count of successful time steps in the current spell will continue to increase until the success criteria is not met. If the spell fails prior to the end of the spell the maximum count of of successful time steps is recorded twice, indicating the time step following the maximum had not changed. In both cases the spell counter is reset to zero at the end of the spell.
For example, if the target flow is 10,000 ML/d and an 80% proportion was specified as required for success (see Success Criteria), then all days with flow >= 8,000ML/d are recorded as successful days.
...
Volume ordered is constrained by the account balance (if the EFN is managed by the EFM), whereas Residual Requirement is not. The volume is calculated at the order phase. Volume ordered will be deducted during ordering phase for order debit or during flow phase for use debit. For order debit it will debit the order at min travel time.the order when the order is placed (i.e. the latest possible timestep for the water to arrive based on travel time). For example: if there is a EFN and a storage node with 2 days travel time - if an order is placed on the 1/1/2000 it will be debited on the 1/1/2000 in order debit (i.e. when the order is placed in the system). For use debit, the account is debited on the 3/1/2000 (i.e. when the water arrives).
Timesteps Spell is Actively Ordering: The number of timesteps a spell will attempt to place orders. This gets reset after the spells fall phase. This is used in environmental flow manager functions to This recorder indicates when ordering for the action is turned on. It includes the rise and fall phase. In this case ‘ordering’ means the node is actively managing the delivery of the action, it not necessarily means any orders are made. For example, the amount of water required may be zero (due to downstream orders or minimum constraints), then the ‘ordering’ for the action is still on, only the amount ordered is zero. This can be used in environmental flow manager functions to determine if an action is currently ordering.
, and is often used in the function to estimate cost of an action to allow for cost to reduce as the action progresses.
Translucency Action
Recorders available for translucency actions are listed below. If they are defined as above no further explanation is given.
...
Under ‘Groups’ > Group Name > ‘Actions’ > Action Name:
Enabled[IT1] : Recorder indicates when the Environmental Flow Manager has enabled an event.
Priority:[IT2] Recorder Recorder showing the priority of the action. The priority of an action is determined given condition and importance,as per the equation below.
Priority = Condition / Importance
Priority is used as a ranking, i.e. the action with lowest priority will be considered first.
...
The table also presents per Portfolio, Initial Balance (excluding adjustment), Initial Balance (including adjustment), Final Balance (including adjustment), and Total Adjustment.
Portfolios
Under ‘Portfolios’ > Portfolio Name:
...
Total Balance Adjustment: The sum of all account balance adjustments.
[IT1]Not sure why this is reported for the actions, as the EMF enables group (not individual actions)
[IT2]This should be the priority for the action – but currently it seems to be set to the group priority… Could this be checked and reported?
Manager Priority: A recorder that contains a snapshot of the priorisation process every timestep. It contains the groups priority, estimate cost, total portfolio balance as it was when that group was prioritised. This means that a groups priority in this recorder and the estimate cost recorder may give different values since the estimate cost recorder contains the value at the end of the priorisation process. The table also includes portfolio balances before and after prioritisation.
Flow Manager – Portfolios - Portfolio Name:
...
Resource Assessment was already existing in Source and is not specific to the Environmental Flow Functionality. The only difference in reporting is that Portfolios are listed under account hosts. Resource assessment recorders are reported per account, aggregated per account type, and aggregated per account host and aggregated for the whole system. For details see Resource assessment.
Other relevant recorders (part of already existing Source software)
...
Account Balance Pre Exit - Resource Assessment- X Accounting Recorder- Account Types - Account Type X- Account Balance Pre Exit This is useful because it gives you the account balance after the resource assessment phase, but before the environmental flow manager evaluation phase and the ordering phase. The account balance recorder is the account balance at the end of the entire timestep.