Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Summary

Benchmarking performance is key to understanding the efficacy of your decision making and enables you to interrogate, and thereby improve, the decision making process.

Performance metrics will evolve as manual bids transition to algo bids and as the sophistication of algo bids improves. Therefore the number and types of reports will develop over time.

Tip

Click Report to access the Performance Reports.

...

Benchmarking Algo ‘what if’ against Actual Manual

...

Hover over Report and click the report you wish to view

...

Actual (Manual) vs Algo ‘what if’

The first report compares the gross margin of Actual Manual bids against Algo “what if” bids. Other metrics such as the difference in volumes are also reported.

Note that as manual bids are replaced by Algo bids, new benchmarking reports will then compare Algo actual gross margin against Algo “perfect hindsight” gross margin where perfect hindsight is calculated by rerunning the Algos using actual price outcomes to formulate optimal volumes from which gross margin is derived.

...

Using the Performance Report

Tip

Select a Date and a DUID

...

Info
  • If more than one DUID is selected then all values are aggregated in the report.

  • The Report will automatically update as the date is changed or the selected duid(s) change.

Report content

  • A break down of the gross margin by service for both the Algo ‘what if’ and the manual actual bid (see gross margin description below).

  • The difference between these values. Note that the difference is defined as “Algo ‘what if’ - minus Manual Actual”

  • Specific business case effects on gross margin that can be attributed to items specifically referenced in the original business plan, namelycertain market conditions:

    • The service allocation stack (SAS) for lowerFCAS and RaiseFCAS.

      • Gross margin difference is attributed to lowerFCAS SAS when Algo expected energy target is greater than manual expected energy target. Therefore the algorithms increase energy generation in order to increase lowerFCAS gross margin resulting in overall greater gross margin.

      • Gross margin difference is attributed to raiseFCAS SAS when Algo expected energy target is less than manual expected energy target. Therefore the algorithms decrease energy generation in order to increase raiseFCAS gross margin resulting in overall greater gross margin.

    • Avoiding negative regulation gross margin for either lowerReg or raiseReg due to the change in generated energy.

      • Gross margin difference is attributed to Algo avoiding negative gross margin if the Algo regulation volume is zero for Algo, and to avoid double counting for service allocation stackSAS (above), the Algo and manual energy bid must be the same.

Tip

Click on the ‘greater and less than’ symbols to expand and contract components of gross margin

...

Info
  • The unit of all values is $. The exception is volume which is MW/5min.

Note that energy
  • Energy volume is the average totalcleared of the dispatch interval ending and beginning.

...

Tip

You may ‘Click and Hold’ on any column heading to then move the column with you mouse

...

Tip

Click on ‘column’ to list all the columns. Check or uncheck to hide or make visible.

...

Gross Margin Description

As a first order approximation, total gross margin includes the revenue gained from providing a service plus the impact on the energy produced and the fuel used in providing an FCAS service.

Info

Gross Margin = Service Revenue + Impact on Energy Revenue + Impact on Fuel Value + Other

Service

Service Revenue

Change in Impact on Energy Revenue

Impact on Fuel Value

Other

Energy

Average Totalcleared * RRP

N/A this value is factored into service revenue

Average Totalcleared * Fuel Cost

contingency RaiseFCAS liability

Note: fuel cost is assumed to be constant

contingency RaiseFCAS liability

refer to AEMO literature for a derivation

LowerReg

LowerRegEnablement * LowerRegRRP

- Utilisation1 * LowerRegEnabled * energyRRP

+ Utilisation * LowerRegEnabled * Fuel Cost

RaiseReg

RaiseRegEnablement * RaiseRegRRP

+ Utilisation * RaiseRegEnabled * energyRRP

- Utilisation * RaiseRegEnabled * Fuel Cost

Sum of Contingency FCAS

Sum of (ContingencyFCASEnablement * ContingencyFCASRRP)

Contingency FCAS utilisation is currently considered zero however this may change (particularly 5min FCAS)

...