6 The Short Term Energy Market

Energy Scheduling Timetable and Process

6.1. [Blank]

6.2. Bilateral Submission Timetable and Process

6.2.1. A Market Participant may submit Bilateral Submission data for a

Trading Day to AEMO between:

$a$ 8:00 AM on the day that is seven days prior to the start of the Scheduling Day for the Trading Day; and

$b$ the Bilateral Submission Cutoff for the Trading Day.

Explanatory Note

Clause 6.2.2 is amended to restore the current arrangements for the processing of Standing Bilateral Submissions for the New WEM, i.e. so that they are used to make Bilateral Submissions for a Trading Day at the time the Trading Day enters the Bilateral Submission window.

6.2.2. Where, at the time specified in clause 6.2.1(a) for a Trading

Day:

$a$ AEMO holds a Standing Bilateral Submission applicable to the Trading Day for a Market Participant; and

$b$ the Standing Bilateral Submission conforms to the requirements of section 6.7 at that time,

AEMO must make the Standing Bilateral Submission the Bilateral Submission for the Trading Day for the Market Participant as at the time specified in clause 6.2.1(a).

Explanatory Note

Clause 6.2.2A requires AEMO to accept or reject Bilateral Submission data and to notify the Market Participant of its decision.

Industry feedback noted that this and other clauses in chapter 6 require AEMO to process data and notify the participant “as soon as practicable”, without a specified latest time. These activities are currently automated and completed in a matter of seconds. While a specified latest time is useful for manual processes with varying durations, the use of “as soon as practicable” for automated short duration processes is sufficient.

Clause 6.2.2A is further amended to reflect the above restoration of the current Bilateral Submission window arrangements.

6.2.2A. Where AEMO receives Bilateral Submission data from a Market

Participant under clause 6.2.1, AEMO must, as soon as practicable after receiving the Bilateral Submission data:

$a$ if the Bilateral Submission data complies with section 6.7 and was provided during the period described in clause 6.2.1, make the Bilateral Submission data the Bilateral Submission for the Trading Day; and

$b$ notify the Market Participant which submitted the Bilateral Submission data under clause 6.2.1, that:

i. the Bilateral Submission data has been made the Bilateral Submission for the Trading Day to which the Bilateral Submission data submitted under clause 6.2.1 relates; or

ii. AEMO rejects the Bilateral Submission data as it does not comply with section 6.7, or was not received during the period described in clause 6.2.1 for the Trading Day to which the Bilateral Submission data submitted under clause 6.2.1 relates.

Explanatory Note

Clause 6.2.3 is amended to:

reflect the above restoration of the current Bilateral Submission window arrangements;
require the Bilateral Submission quantities to be provided for each Trading Interval in the Bilateral Submission Results Window, instead of each Trading Interval in the Week-Ahead Schedule Horizon; and
update the list of events that will trigger an update of the Bilateral Submission quantities.

6.2.3. AEMO must maintain and provide to each Market Participant the

Bilateral Submission quantities associated with that Market Participant for each Trading Interval in the Bilateral Submission Results Window, including the party supplying, or being supplied by, the Market Participant. AEMO must update this information whenever AEMO:

$a$ makes a Bilateral Submission under clause 6.2.2;

$b$ accepts Bilateral Submission data under clause 6.2.2A(a); or

$c$ disregards cancelled Bilateral Submission data from a Bilateral Submission under clause 6.2.5(a).

6.2.4. [Blank]

6.2.4A. [Blank]

6.2.4B. A Market Participant may cancel Bilateral Submission data held

by AEMO for any Trading Interval during the period described in clause

6.2.1 for the Trading Day to which the cancelled Bilateral Submission

data relates.

6.2.5. Where any Bilateral Submission data is cancelled in accordance

with clause 6.2.4B, AEMO must, as soon as practicable:

$a$ disregard the cancelled Bilateral Submission data from the Bilateral Submission; and

$b$ notify the Market Participant which cancelled the Bilateral Submission that the data has been disregarded from the Bilateral Submission for the Trading Interval of the Trading Day to which the cancelled Bilateral Submission data relates.

6.2.6. [Blank]

6.2.7. By submitting Bilateral Submission data, a Market Participant

acknowledges that it is acting with the permission of all affected Market Participants.

6.2A. Standing Bilateral Submission Timetable and Process

Explanatory Note

Clause 6.2A.1 is amended to remove the current window for provision of Standing Bilateral Submission data to AEMO. Market Participants will be able to submit Standing Bilateral Submissions to AEMO at any time.

6.2A.1. A Market Participant may submit Standing Bilateral Submission

data to AEMO at any time.

Explanatory Note

Clause 6.2A.2 is amended to improve the drafting to clarify that AEMO is required to accept or reject Standing Bilateral Submission data and notify the Market Participant of its decision.

Industry feedback noted that the start of the next Scheduling day is midnight, potentially inconsistent with the Bilateral Submission Cutoff, which is 8.50am. While a specified latest time is useful for manual processes with varying durations, the use of “as soon as practicable” for automated short duration processes is sufficient, and for consistency with similar STEM clauses we have removed the specified latest time.

6.2A.2. AEMO must, as soon as practicable after receiving Standing

Bilateral Submission data under clause 6.2A.1:

$a$ accept the Standing Bilateral Submission data provided it complies with section 6.7 and revise the Standing Bilateral Submission to reflect the Standing Bilateral Submission data; and

$b$ notify the Market Participant which submitted the Standing Bilateral data under clause 6.2A.1 that:

i. AEMO accepts the Standing Bilateral Submission data and has revised the Standing Bilateral Submission to reflect the Standing Bilateral Submission data; or

ii. AEMO rejects the Standing Bilateral Submission data as it does not comply with section 6.7.

6.2A.2A. Standing Bilateral Submission data accepted by AEMO under

clause 6.2A.2 will apply from the next time that AEMO is required to use Standing Bilateral Submissions to make Bilateral Submissions under clause 6.2.2.

6.2A.3. Standing Bilateral Submission data must be associated with a day

of the week and when used as Bilateral Submission data will only apply to Trading Days commencing on that day of the week.

Explanatory Note

Clause 6.2A.4 is amended to clarify the level of granularity permitted for cancellations of Standing Bilateral Submission data.

Following the consultation period for Exposure Draft 2 further changes were made to clauses 6.2A.4 and 6.2A.5 to further clarify the intent of the clauses.

6.2A.4. A Market Participant may at any time cancel Standing Bilateral

Submission data accepted by AEMO under clause 6.2A.2(a) for Trading Intervals starting at a specified time on Trading Days starting on a specified day of the week.

6.2A.5. Where any Standing Bilateral Submission data is cancelled in

accordance with clause 6.2A.4, AEMO must, as soon as practicable:

$a$ disregard the cancelled Standing Bilateral Submission data from the Standing Bilateral Submission; and

$b$ notify the Market Participant which cancelled the Standing Bilateral Submission data under clause 6.2A.4, that the cancelled Standing Bilateral Submission data has been disregarded from the Standing Bilateral Submission,

for the Trading Intervals to which the cancelled Standing Bilateral Submission data relates.

Explanatory Note

New clause 6.3.1 requires AEMO to finalise the Electric Storage Resource Obligation Intervals for the next Trading Day and document its expectation of the Electric Storage Resource Obligation Intervals for the subsequent seven Trading Days by 6:50 AM on each Scheduling Day. This information is then made available to all Market Participants under clause 6.3A.2 and used to determine capacity adjusted outage quantity and Reserve Capacity Obligation Quantity estimates under clause ### 6.3A.3.

The deadline has moved from 8:00 AM (as proposed in Tranche 6 Exposure Draft 1) to 6:50 AM, in response to concerns raised by stakeholders during consultation that an 8:00 AM deadline would not give Market Participants enough notice of changes. The new deadline balances the need to give Market Participants adequate notice of changes and the security and reliability benefits of allowing AEMO to determine the final Electric Storage Resource Obligation Intervals for a Trading Day as late as possible.

6.3. Determination of Electric Storage Resource Obligation Intervals

6.3.1. AEMO must, in accordance with the WEM Procedure referred to in

clause 4.11.3A, determine and record the following information by 6:50 AM on each Scheduling Day:

$a$ the Electric Storage Resource Obligation Intervals that will apply during the Trading Day for the Scheduling Day; and

$b$ the Electric Storage Resource Obligation Intervals that AEMO expects will apply during each of the seven following Trading Days.

6.3A. Information to Support the Bilateral and STEM Submission Process

Explanatory Note

Clause 6.3A.1 is amended to:

reflect the above restoration of the current Bilateral Submission window arrangements;
require the total energy quantity to be published for each Trading Interval in the Bilateral Submission Results Window, instead of each Trading Interval in the Week-Ahead Schedule Horizon;
update the list of events that will trigger an update of the total energy quantity; and
capitalise the defined term “Bilateral Contracts”.

6.3A.1. AEMO must publish the total energy, in MWh, as measured at the

Reference Node, scheduled with AEMO under Bilateral Contracts for each Trading Interval in the Bilateral Submission Results Window. AEMO must update this information whenever AEMO:

$a$ makes a Bilateral Submission under clause 6.2.2;

$b$ accepts Bilateral Submission data under clause 6.2.2A(a); or

$c$ disregards cancelled Bilateral Submission data from a Bilateral Submission under clause 6.2.5(a).

Explanatory Note

Clause 6.3A.2 as proposed in Tranche 6 Exposure Draft 1 is replaced with two clauses, due to the change in deadline for determining and providing to Market Participants the final Electric Storage Resource Obligation Intervals for a Trading Day.

Revised clause 6.3A.2 requires AEMO to provide, by 6:50 AM on each Scheduling Day, details of the Electric Storage Resource Obligation Intervals for the next eight Trading Days, as determined under clause ### 6.3.1. (This replaces the previous requirement from the Tranches 2 and 3 Amendments to notify Market Participants with Electric Storage Resources of changes to the Electric Storage Resource Obligation Intervals for the next Trading Day in clause 6.2.8).

New clause 6.3A.2A requires AEMO to provide, by 8:00 AM on each Scheduling Day, a demand forecast for the Trading Day for the Scheduling Day (comprising Forecast Operational Demand and Forecast Operational Withdrawal), derived from the most recently determined Pre-Dispatch Schedule (which replaces the previous demand forecast requirement in clause 6.3A.3(g)). The clause has been updated since the consultation period for Exposure Draft 2 to use the appropriate new forecast quantities.

6.3A.2. AEMO must make the following information available to each

Market Participant by 6:50 AM on each Scheduling Day:

$a$ the Electric Storage Resource Obligation Intervals that will apply for the Trading Day for the Scheduling Day, as determined by AEMO under clause 6.3.1(a); and

$b$ the Electric Storage Resource Obligation Intervals that AEMO expects will apply for each of the seven Trading Days following the Trading Day for the Scheduling Day, as determined by AEMO under clause

6.3.1(b).

6.3A.2A. AEMO must make available to each Market Participant, by 8:00 AM

on each Scheduling Day, for each Trading Interval in the Trading Day for the Scheduling Day, the Forecast Operational Demand and Forecast Operational Withdrawal as determined from the most recent Pre-Dispatch Schedule that AEMO has made available to Market Participants.

Explanatory Note

Revised clause 6.3A.3 requires AEMO to do the following on the morning of each Scheduling Day between 8:00 AM and 8:30 AM:

record a snapshot of the approved Commissioning Test Plans, Planned Outages and Forced Outages that are expected to occur during the STEM Submission Information Window (the eight Trading Days starting with the Trading Day for the Scheduling Day);
use this snapshot information to determine the required STEM Submission quantity limits, capacity adjusted outage quantity estimates and Reserve Capacity Obligation Quantity estimates for each Trading Interval and/or Dispatch Interval (as appropriate) in the STEM Submission Information Window.

The Maximum Supply Capability and Maximum Consumption Capability limits are each set to a minimum of 0.001 MWh, to ensure that a Market Participant is always able to the submit a Portfolio Supply Curve/Portfolio Demand Curve with at least one Price-Quantity Pair. This removes the need to include distinct Participant Interval Minimum STEM Price and Participant Interval Maximum STEM Price parameters in STEM Submissions, because a Market Participant will be able to effectively specify these values through the minimum and maximum prices in their Price-Quantity Pairs.

Following further consultation:

clause 6.3A.3(g) is further amended to require the determination of capacity adjusted outage quantity estimates at the Facility level, as required for use in clauses 4.26.2AD(b) and 4.26.2AH(g); and
clause 6.3A.3(h) is further amended to require the determination of STEM RCOQs at the Facility level, as required for use in clauses 4.26.2AD(a) and 4.26.2AG(b).

6.3A.3. Between 8:00 AM and 8:30 AM each Scheduling Day, AEMO must:

$a$ identify and record the details of each approved Commissioning Test Plan that includes one or more Dispatch Intervals in the STEM Submission Information Window;

$b$ identify and record the details of each Planned Outage or Forced Outage for energy recorded by AEMO for a Scheduled Facility, Semi-Scheduled Facility or Non-Scheduled Facility with a duration that includes one or more Dispatch Intervals in the STEM Submission Information Window;

$c$ determine the Maximum Facility Supply Capability for each Scheduled Facility, Semi-Scheduled Facility and Non-Scheduled Facility f for each Dispatch Interval DI in the STEM Submission Information Window as:

\[\text{MFSC(f,DI)=}\frac{\text{MinAvail(f,DI)×LF(f,DI)}}{\text{12}}\]

where:

i. MinAvail(f,DI) is:

1. where no Planned Outages or Forced Outages for Facility f with a duration that includes Dispatch Interval DI were identified under clause

6.3A.3(b), the maximum sent out capacity of Facility f as recorded in

Standing Data for Dispatch Interval DI; and

2. otherwise, the minimum Remaining Available Capacity for energy recorded for Facility f in Dispatch Interval DI for the Planned Outages and Forced Outages identified under clause 6.3A.3(b); and

ii. LF(f,DI) is the Loss Factor for Facility f in Dispatch Interval DI;

$d$ determine the Maximum Facility Supply Capability for each Scheduled Facility, Semi-Scheduled Facility and Non-Scheduled Facility f for each Trading Interval t in the STEM Submission Information Window as:

\[\text{MFSC(f,t)=}\sum\_{\text{DI}\text{∈}\text{t}}^{}\text{MFSC(f,DI)}\]

where:

i. MFSC(f,DI) is the Maximum Facility Supply Capability determined by AEMO for Facility f for Dispatch Interval DI under clause 6.3A.3(c); and

ii. DI∊t denotes all Dispatch Intervals DI in Trading Interval t;

$e$ determine the Maximum Supply Capability for each Market Participant p for each Trading Interval t in the STEM Submission Information Window as:

\[\text{MSC(p,t)=max}\left( \text{0.001,}\\\sum\_{\text{f}\text{∈}\text{Facilities(p,t)}}^{}\text{MFSC(f,t)} \right)\]

where:

i. MFSC(f,t) is the Maximum Facility Supply Capability determined by AEMO for Facility f for Trading Interval t under clause 6.3A.3(d); and

ii. f∈Facilities(p,t) denotes all Scheduled Facilities, Semi-Scheduled Facilities and Non-Scheduled Facilities f registered to Market Participant p in Trading Interval t;

$f$ determine the Maximum Consumption Capability for each Market Participant p for each Trading Interval t in the STEM Submission Information Window as:

MCC(p,t)=max(0.001, StandingMCC(p,t))

where:

i. StandingMCC(p,t) is the maximum Loss Factor adjusted quantity of energy, in units of MWh, that could be consumed during Trading Interval t by Market Participant p’s Registered Facilities and Non‑Dispatchable Loads, as specified in Standing Data;

$g$ using the assumptions specified in clause 6.3A.4, determine and record an estimate of the Capacity Adjusted Forced Outage Quantity and Capacity Adjusted Planned Outage Quantity for each Scheduled Facility or Semi‑Scheduled Facility, and each Separately Certified Component of a Scheduled Facility or Semi‑Scheduled Facility, for each Dispatch Interval and each Trading Interval in the STEM Submission Information Window in which AEMO considers the relevant Facility will be in Commercial Operation; and

$h$ using the assumptions specified in clause 6.3A.4, determine and record an estimate of the Reserve Capacity Obligation Quantity for each Scheduled Facility or Semi-Scheduled Facility, and each Separately Certified Component of a Scheduled Facility or Semi-Scheduled Facility, for each Dispatch Interval in the STEM Submission Information Window in which AEMO considers the relevant Facility will be in Commercial Operation.

Explanatory Note

Revised clause 6.3A.4 sets out the assumptions that AEMO must use when determining capacity adjusted outage quantity and Reserve Capacity Obligation Quantity estimates under clause 6.3A.3.

6.3A.4. When determining Capacity Adjusted Planned Outage Quantity,

Capacity Adjusted Forced Outage Quantity and Reserve Capacity Obligation Quantity estimates on a Scheduling Day under clauses 6.3A.3(g) and

6.3A.3(h), AEMO must assume that:

$a$ the Electric Storage Resource Obligation Intervals for the Trading Days in the STEM Submission Information Window are the same as those determined by AEMO on the Scheduling Day under clause 6.3.1;

$b$ the Commissioning Test Plan details for each Facility for each Dispatch Interval in the STEM Submission Information Window are the same as those identified by AEMO on the Scheduling Day under clause

6.3A.3(a);

$c$ the Planned Outage and Forced Outage details for each Separately Certified Component for each Dispatch Interval in the STEM Submission Information Window are the same as those identified by AEMO on the Scheduling Day under clause 6.3A.3(b);

$d$ the maximum daily temperature at the site of each relevant Facility does not exceed 41 degrees Celsius on any Trading Day in the STEM Submission Information Window; and

$e$ the Reserve Capacity Obligation Quantity of an Electric Storage Resource is not reduced under clause 4.12.5(g) for any Dispatch Interval in the STEM Submission Information Window.

Explanatory Note

Revised clause 6.3A.5 requires AEMO to make available to Market Participants by 8:30 AM on the Scheduling Day the STEM Submission quantity limits, capacity adjusted outage quantity estimates and Reserve Capacity Obligation Quantity estimates that it has determined under clause 6.3A.3.

The clause as presented in Exposure Draft 1 is further amended to correct the cross-references in clauses 6.3A.5(b) and ### 6.3A.5(c).

6.3A.5. By 8:30 AM on each Scheduling Day, AEMO must make available to

each Market Participant the following parameters for information in forming its STEM Submissions:

$a$ for each Trading Interval in the STEM Submission Information Window:

i. the Maximum Facility Supply Capability determined on the Scheduling Day under clause 6.3A.3(d) for each Scheduled Facility, Semi-Scheduled Facility and Non-Scheduled Facility registered to the Market Participant in the Trading Interval;

ii. the Maximum Supply Capability determined on the Scheduling Day under clause 6.3A.3(e) for the Market Participant; and

iii. the Maximum Consumption Capability determined on the Scheduling Day under clause 6.3A.3(f) for the Market Participant;

$b$ for each Trading Interval in the STEM Submission Information Window, for each Separately Certified Component of a Scheduled Facility or Semi‑Scheduled Facility for which the Market Participant holds Capacity Credits in the Trading Interval and which AEMO considers to be in Commercial Operation in the Trading Interval:

i. the Capacity Adjusted Forced Outage Quantity estimate determined on the Scheduling Day under clause 6.3A.3(g); and

ii. the Capacity Adjusted Planned Outage Quantity estimate determined on the Scheduling Day under clause 6.3A.3(g); and

$c$ for each Dispatch Interval in the STEM Submission Information Window, for each Separately Certified Component of a Scheduled Facility or Semi‑Scheduled Facility for which the Market Participant holds Capacity Credits in the Dispatch Interval and which AEMO considers to be in Commercial Operation in the Dispatch Interval:

i. the Capacity Adjusted Forced Outage Quantity estimate determined on the Scheduling Day under clause 6.3A.3(g);

ii. the Capacity Adjusted Planned Outage Quantity estimate determined on the Scheduling Day under clause 6.3A.3(g); and

iii. the Reserve Capacity Obligation Quantity estimate determined on the Scheduling Day under clause 6.3A.3(h).

6.3B. STEM Submissions Timetable and Process

6.3B.1. A Market Participant may submit STEM Submission data for a

Trading Day to AEMO between:

$a$ 8:30 AM on the day that is seven days prior to the start of the Scheduling Day for the Trading Day; and

$b$ the STEM Submission Cutoff for the Trading Day.

Explanatory Note

Clause 6.3B.1A is amended to restore the current arrangements for the processing of Standing STEM Submissions for the new WEM, except that the processing will occur at 8:30 AM on the Scheduling Day instead of 9:00 AM.

The processing time has been moved from the time proposed in Exposure Draft 1 (i.e. when the Trading Day first enters the STEM Submission window), in response to a concern raised by Synergy that if

a STEM Submission is ‘trimmed’ to reflect a Planned Outage that is subject to a late cancellation; and
the Market Participant has system issues that prevent it from updating its STEM Submission on the Scheduling Day,

then the Market Participant could incur a Net STEM Shortfall and be exposed to Reserve Capacity refunds.

The new processing time falls after the final lock in of outages for a Trading Day on the Scheduling Day, which removes any risk that a Standing STEM Submission will be trimmed based on outage data that subsequently changes.

6.3B.1A. Where, at 8:30 AM on the Scheduling Day for a Trading Day:

$a$ AEMO does not hold a STEM Submission applicable to the Trading Day for the Market Participant;

$b$ AEMO holds a Standing STEM Submission applicable to the Trading Day for a Market Participant; and

$c$ the Standing STEM Submission conforms to the requirements of section 6.6 at that time,

AEMO must, subject to clause 6.3B.1B, make the Standing STEM Submission the STEM Submission for the Trading Day for the Market Participant as at 8:30 AM on the Scheduling Day for the Trading Day.

Explanatory Note

Clause 6.3B.1B is amended to move the details of the STEM Submission adjustment process to clause 6.3B.2. This process will also be used by AEMO for the daily adjustments to STEM Submissions required under the new clause 6.3B.1C.

6.3B.1B. If AEMO is required to use a Standing STEM Submission to make a

STEM Submission for a Trading Day under clause 6.3B.1A, but the Standing STEM Submission does not comply with section 6.6, then AEMO must, using the process specified in clause 6.3B.2, adjust the Standing STEM Submission to make it a valid STEM Submission with respect to each Trading Interval in the Trading Day.

Explanatory Note

New clause 6.3B.1C requires AEMO to review and adjust any previously accepted STEM Submissions that have become invalid following changes to relevant factors such as Outages, Commissioning Tests or Energy Price Limits.

6.3B.1C. Between 8:30 AM and 9:00 AM each Scheduling Day, AEMO must use

the process specified in clause 6.3B.2 to review and where necessary adjust each STEM Submission it holds for a Trading Interval in the STEM Submission Information Window.

Explanatory Note

New clause 6.3B.2 specifies the STEM Submission adjustment process used to ensure that the Price-Quantity Pairs in Portfolio Supply Curves and Portfolio Demand Curves comply with the requirements of section ### 6.6.

6.3B.2. AEMO must use the following process to adjust a Standing STEM

Submission to make a valid STEM Submission for a Trading Interval under clause 6.3B.1B and to review and adjust a STEM Submission for a Trading Interval under clause 6.3B.1C:

$a$ If the cumulative MWh quantity over all Price-Quantity Pairs in the Portfolio Supply Curve is greater than the Maximum Supply Capability for the Market Participant for the Trading Interval which was determined on the current Scheduling Day under clause 6.3A.3(e), the Price-Quantity Pairs must be adjusted downward so that the cumulative MWh quantity over all the Price‑Quantity Pairs equals the Maximum Supply Capability. This must be achieved by deleting successively or reducing the highest price Price‑Quantity Pairs until the cumulative MWh quantity over all remaining Price‑Quantity Pairs equals the Maximum Supply Capability.

$b$ If the cumulative MWh quantity over all Price-Quantity Pairs in the Portfolio Demand Curve is greater than the Maximum Consumption Capability for the Market Participant for the Trading Interval which was determined on the current Scheduling Day under clause 6.3A.3(f), the Price-Quantity Pairs must be adjusted downward so that the cumulative MWh quantity over all the Price‑Quantity Pairs equals the Maximum Consumption Capability. This must be achieved by deleting successively or reducing the highest price Price‑Quantity Pairs until the cumulative MWh quantity over all remaining Price‑Quantity Pairs equals the Maximum Consumption Capability.

$c$ If the price in any Price-Quantity Pair in the Portfolio Supply Curve or Portfolio Demand Curve is greater than the Energy Offer Price Ceiling which will apply (or which AEMO expects will apply) in the Trading Interval, the price in the Price-Quantity Pair must be replaced by the Energy Offer Price Ceiling which will apply (or which AEMO expects will apply) in the Trading Interval.

$d$ If the price in any Price-Quantity Pair in the Portfolio Supply Curve or Portfolio Demand Curve is less than the Energy Offer Price Floor which will apply (or which AEMO expects will apply) in the Trading Interval, the price in the Price-Quantity Pair must be replaced by the Energy Offer Price Floor which will apply (or which AEMO expects will apply) in the Trading Interval.

$e$ [Blank]

$f$ If multiple Price-Quantity Pairs in the Portfolio Supply Curve share the same price, they must be replaced with a single Price-Quantity Pair for that price with a MWh quantity equal to the sum of the MWh quantities in the Price-Quantity Pairs which are being replaced.

$g$ If multiple Price-Quantity Pairs in the Portfolio Demand Curve share the same price, they must be replaced with a single Price-Quantity Pair for that price with a MWh quantity equal to the sum of the MWh quantities in the Price-Quantity Pairs which are being replaced.

To avoid doubt, the process steps specified in this clause 6.3B.2 must be performed in the order listed, and a reference to a Portfolio Supply Curve or Portfolio Demand Curve in those clauses is a reference to the Portfolio Supply Curve or Portfolio Demand Curve as adjusted by any earlier steps in the process.

6.3B.3. Where AEMO receives STEM Submission data from a Market

Participant under clause 6.3B.1, AEMO must, as soon as practicable after receiving the STEM submission data:

$a$ if the STEM Submission data complies with section 6.6, make the STEM Submission data the STEM Submission for that Trading Day; and

$b$ notify the Market Participant which submitted the STEM Submission data under clause 6.3B.1, that:

i. the STEM Submission data has been made the STEM Submission for that Trading Day; or

ii. AEMO has rejected the STEM Submission data as it did not comply with section 6.6.

Explanatory Note

Clause 6.3B.4 is amended to:

reflect the above restoration of the current Standing STEM Submission arrangements;
clarify that the STEM Submission details provided by AEMO will incorporate any adjustments it has made under clauses 6.3B.1B or ### 6.3B.1C;
require the details to be provided for each Trading Interval in the STEM Submission Results Window, instead of each Trading Interval in the Week-Ahead Schedule Horizon; and
update the list of events that will trigger an update of the STEM Submission details.

6.3B.4. AEMO must maintain and provide to each Market Participant full

details of the Market Participant’s STEM Submissions, as adjusted under clauses 6.3B.1B and 6.3B.1C, for each Trading Interval in the STEM Submission Results Window. AEMO must update this information whenever AEMO:

$a$ makes a STEM Submission from a Standing STEM Submission under clause 6.3B.1A;

$b$ accepts STEM Submission data under clause 6.3B.3(a);

$c$ adjusts STEM Submission data under clause 6.3B.1C; or

$d$ disregards cancelled STEM Submission data under clause 6.3B.6(a).

6.3B.5. A Market Participant may cancel any STEM Submission data held by

AEMO for a Trading Interval in a Trading Day during the time interval specified for the Trading Day in clause 6.3B.1.

6.3B.6. Where any STEM Submission data is cancelled in accordance with

clause 6.3B.5, AEMO must, as soon as practicable:

$a$ disregard the cancelled STEM Submission data from the STEM Submission; and

$b$ notify the Market Participant which cancelled the STEM Submission data under clause 6.3B.5, that the cancelled STEM Submission data has been disregarded from the STEM Submission,

for the Trading Interval of the Trading Day to which the cancelled Standing STEM Submission data relates.

6.3C. Standing STEM Submission Timetable and Process

6.3C.1. A Market Participant may submit Standing STEM Submission data to

AEMO at any time.

6.3C.2. [Blank]

Explanatory Note

Clause 6.3C.3 is amended to improve the drafting and to clarify that AEMO is required to accept or reject Standing STEM Submission data and notify the Market Participant of its decision.

6.3C.3. AEMO must, as soon as practicable after receiving Standing STEM

Submission data under clause 6.3C.1:

$a$ accept the Standing STEM Submission data provided it complies with section 6.6 and revise the Standing STEM Submission to reflect the Standing STEM Submission data; and

$b$ notify the Market Participant which submitted the Standing STEM Submission data under clause 6.3C.1 that:

i. AEMO accepts the Standing STEM Submission data and has revised the Standing STEM Submission to reflect the Standing STEM Submission data; or

ii. AEMO rejects the Standing STEM Submission data as it does not comply with section 6.6.

6.3C.4. Standing STEM Submission data accepted by AEMO under clause

6.3C.3 will apply from the next time that AEMO is required to use

Standing STEM Submissions to make STEM Submissions under clause 6.3B.1A.

6.3C.5. [Blank]

6.3C.6. [Blank]

6.3C.6A. Standing STEM Submission data must be associated with a day of

the week and when used as STEM Submission data will only apply to Trading Days commencing on that day of the week.

6.3C.6B. A Market Participant may cancel Standing STEM Submission data

accepted by AEMO under clause 6.3C.3(a) for any Trading Interval of a day of the week at any time.

6.3C.6C. Where any Standing STEM Submission data is cancelled under

clause 6.3C.6B, AEMO must, as soon as practicable:

$a$ remove the cancelled Standing STEM Submission data from the Standing STEM Submission; and

$b$ notify the Market Participant which cancelled the Standing STEM Submission data under clause 6.3C.6B, that the cancelled Standing STEM Submission data has been removed from the Standing STEM Submission,

for the Trading Interval of the day of the week to which the cancelled Standing STEM Submission data relates.

6.3C.7. [Blank]

6.3C.8. [Blank]

6.3C.9. If a Market Participant’s ability to consume or supply energy in

any Trading Interval of a Trading Day is less than the maximum level of its STEM supply or consumption as indicated by its current Standing STEM Submission then that Market Participant must either:

$a$ submit to AEMO Standing STEM Submission data so as to revise its Standing STEM Submission to comply with this clause 6.3C.9; or

$b$ for each Trading Interval for which the current Standing STEM Submission over-states the Market Participant's supply or consumption capabilities, submit STEM Submission data that complies with section 6.6 to AEMO.

6.4. The STEM Auction Timetable and Process

6.4.1. AEMO must undertake the process described in section 6.9 and

determine the STEM Auction results for a Trading Day after the STEM Submission Cutoff, and before the STEM Results Deadline.

6.4.2. AEMO must determine the total quantity of energy scheduled to be

supplied under Bilateral Contracts and in the STEM Auction, by each Market Participant, for each Trading Interval of a Trading Day by the STEM Results Deadline.

6.4.3. AEMO must make available to each Market Participant the following

information in relation to a Trading Day by the STEM Results Deadline:

$a$ the Trading Intervals, if any, in which the STEM Auction was suspended;

$b$ the STEM Clearing Price in all Trading Intervals for which the STEM Auction was not suspended;

$c$ the quantities scheduled in respect of that Market Participant in the STEM Auction for each Trading Interval; and

$d$ the Net Contract Position of the Market Participant in each Trading Interval, as determined in accordance with clause 6.9.13.

6.4.4. [Blank]

6.4.5. [Blank]

Explanatory Note

Clause 6.4.6 is amended to:

update the list of information preparation clauses;
reflect that timelines other than the Bilateral Submission Cutoff, STEM Submission Cutoff and STEM Results deadline may need to be extended; and
refine the list of requirements that an extension must meet.

6.4.6. In the event of a failure of AEMO's software systems or

supporting infrastructure, or any delay in AEMO publishing a Pre-Dispatch Schedule which includes all Trading Intervals in the relevant Trading Day, or AEMO preparing information under clauses 6.2.3,

6.3.1, 6.3A.1, 6.3A.2, 6.3A.2A, 6.3A.3, 6.3A.5 or 6.3B.4, which prevents

AEMO from completing the relevant processes, AEMO may extend one or more of the timelines prescribed in sections 6.2, 6.3, 6.3A, 6.3B and this section 6.4, subject to any such extension:

$a$ not resulting in more than a two-hour delay to any of the timelines prescribed in sections 6.2, 6.3, 6.3A, 6.3B and this section

6.4;

$b$ maintaining a window of at least 120 minutes between AEMO making available the data referred to in clause 6.3A.2 and the Bilateral Submission Cutoff;

$c$ maintaining a window of at least 50 minutes between AEMO making available the data referred to in clause 6.3A.2A and the Bilateral Submission Cutoff;

$d$ maintaining a window of at least 20 minutes between AEMO making available the data referred to in clause 6.3A.5 and the Bilateral Submission Cutoff; and

$e$ maintaining a window of at least 110 minutes between each of the following events and the STEM Submission Cutoff:

i. AEMO making available to Market Participants the first Pre-Dispatch Schedule that includes all Trading Intervals in the relevant Trading Day;

ii. AEMO making available to Market Participants the data referred to in clause 6.2.3 as at the Bilateral Submission Cutoff; and

iii. AEMO making available to Market Participants the data referred to in clauses 6.3A.2A and 6.3A.5.

Explanatory Note

Clause 6.4.6A is amended to:

update the list of clauses under which information is made available;
reflect that timelines other than the Bilateral Submission Cutoff, STEM Submission Cutoff and STEM Results deadline may need to be extended; and
refine the list of requirements that an extension must meet.

6.4.6A. If AEMO becomes aware of an error in any of the information

contained in a Pre-Dispatch Schedule or made available to Market Participants under clauses 6.2.3, 6.3A.1, 6.3A.2, 6.3A.2A, 6.3A.5 or

6.3B.4 at any time before the publication of the relevant STEM Auction

results under clause 6.4.3 or a suspension of the STEM under clause

6.10.1, AEMO may:

$a$ publish or release (as applicable) corrected or updated versions of the information it has published or released under clauses 6.2.3,

6.3A.1, 6.3A.2, 6.3A.2A, 6.3A.5 or 6.3B.4; and

$b$ extend any of the relevant timelines prescribed in sections 6.2,

6.3, 6.3A, 6.3B and this section 6.4 to address the error, subject to

any such extension:

i. not resulting in more than a two-hour delay to any of the timelines prescribed in sections 6.2, 6.3, 6.3A, 6.3B and this section 6.4;

ii. maintaining a window of at least 120 minutes between AEMO making available to Market Participants the data referred to in clause 6.3A.2 and the Bilateral Submission Cutoff;

iii. maintaining a window of at least 50 minutes between AEMO making available to Market Participants the data referred to in clause 6.3A.2A and the Bilateral Submission Cutoff;

iv. maintaining a window of at least 20 minutes between AEMO making available to Market Participants the data referred to in clause 6.3A.5 and the Bilateral Submission Cutoff; and

v. maintaining a window of at least 110 minutes between each of the following events and the STEM Submission Cutoff:

1. AEMO making available to Market Participants the first error-free Pre-Dispatch Schedule that includes all Trading Intervals in the relevant Trading Day;

2. AEMO making available to Market Participants the data referred to in clause 6.2.3 as at the Bilateral Submission Cutoff; and

3. AEMO making available to Market Participants the data referred to in clauses 6.3A.2A and 6.3A.5.

Explanatory Note

Clauses 6.4.6B and 6.4.6C are amended to reflect that timelines other than the Bilateral Submission Cutoff, STEM Submission Cutoff and STEM Results Deadline may need to be extended.

6.4.6B. If AEMO extends one or more of the timelines in sections 6.2,

6.3, 6.3A, 6.3B and this section 6.4 under clauses 6.4.6 or 6.4.6A or

publishes or releases corrected information under clause 6.4.6A(a), AEMO must notify Rule Participants of any extension and any amended timelines and any corrected information as soon as possible.

6.4.6C. If AEMO considers that extending one or more of the timelines in

sections 6.2, 6.3, 6.3A, 6.3B and this section 6.4 under clauses 6.4.6 or 6.4.6A would not provide enough time to allow AEMO to undertake the process described in section 6.9 and publish a valid STEM Auction result under clauses 6.4.3(b), 6.4.3(c) and 6.4.3(d) by 1:30 PM on the relevant Scheduling Day, AEMO must suspend the STEM Auction under clause 6.10.1.

6.4.7. Once published under clause 6.4.3, STEM Clearing Prices cannot be

altered, either through disagreement under clause 9.20.6, or through dispute under clause 9.21.

6.5. [Blank]

STEM Submission and Bilateral Submission Formats

6.6. Format of STEM Submission and Standing STEM Submission Data

Explanatory Note

Clause 6.6.1 is amended to:

remove the concept of Participant Interval Minimum STEM Prices and Participant Interval Maximum STEM Prices; and
remove the requirement to specify an effective date for Standing STEM Submissions.

6.6.1. A Market Participant submitting STEM Submission data or a

Standing STEM Submission data must include the following information in the applicable submission:

$a$ the identity of the Market Participant making the submission;

$b$ for STEM Submission data, for each Trading Interval included in the submission:

i. a Fuel Declaration;

ii. a Portfolio Supply Curve; and

iii. a Portfolio Demand Curve;

$c$ for Standing STEM Submission data, the day of the week to which the submission relates, where data provided for a day of the week relates to the Trading Day commencing on that day, and for each Trading Interval included in the submission:

i. a Fuel Declaration;

ii. a Portfolio Supply Curve; and

iii. a Portfolio Demand Curve.

6.6.2. [Blank]

6.6.2A. For:

$a$ a Fuel Declaration the Market Participant must declare which of its Liquid Fuel capable Registered Facilities are assumed to be operating on Liquid Fuel in forming the Portfolio Supply Curve;

$b$ [Blank]

$c$ [Blank]

$d$ a Portfolio Supply Curve:

i. one or more Price-Quantity Pairs may be specified; and

ii. the cumulative MWh quantity over all Price-Quantity Pairs must not exceed the Maximum Supply Capability determined under clause 6.3A.3(e); and

$e$ a Portfolio Demand Curve:

i. one or more Price-Quantity Pairs may be specified; and

ii. the cumulative quantity included in the Price-Quantity Pairs must not exceed the Maximum Consumption Capability determined under clause

6.3A.3(f).

6.6.3. [Blank]

6.6.4. The maximum number of Price-Quantity Pairs which a Market

Participant may include in a Portfolio Supply Curve is 30.

6.6.5. For Price-Quantity Pairs in Portfolio Supply Curves:

$a$ each Price-Quantity Pair must comprise one price and one quantity;

$b$ each Price-Quantity Pair price must be:

i. in units of $/MWh expressed to a precision of $0.01/MWh;

ii. [Blank]

iii. greater than or equal to the Energy Offer Price Floor;

iv. less than or equal to the Energy Offer Price Ceiling; and

v. set such that no two Price-Quantity Pairs in a Portfolio Supply Curve have the same price;

$c$ each Price-Quantity Pair quantity must be

i. in units of MWh expressed to a precision of 0.001 MWh;

ii. Loss Factor adjusted; and

$d$ a Price-Quantity Pair means that the Market Participant is prepared to sell a quantity of energy into the STEM for that Price-Quantity Pair equal to:

i. 0 MWh if the STEM Clearing Price is less than the Price-Quantity Pair price;

ii. the Price-Quantity Pair quantity if the STEM Clearing Price is greater than the Price-Quantity Pair price; and

iii. an amount between 0 MWh and the Price-Quantity Pair quantity if the STEM Clearing Price equals the Price-Quantity Pair price.

6.6.6. [Blank]

6.6.7. The maximum number of Price-Quantity Pairs to be included in a

Portfolio Demand Curve is 30.

6.6.8. For Price-Quantity Pairs in Portfolio Demand Curves:

$a$ each Price-Quantity Pair price must be:

i. in units of $/MWh expressed to a precision of $0.01/MWh;

ii. less than or equal to the Energy Offer Price Ceiling;

iii. greater than or equal to the Energy Offer Price Floor; and

iv. set such that no two Price-Quantity Pairs in a Portfolio Demand Curve have the same price;

$b$ each Price-Quantity Pair quantity must be:

i. in units of MWh expressed to a precision of 0.001 MWh; and

ii. Loss Factor adjusted; and

$c$ a Price-Quantity Pair means that the Market Participant is prepared to buy a quantity of energy from the STEM for that Price-Quantity Pair equal to:

i. 0 MWh if the STEM Clearing Price is greater than the Price-Quantity Pair price;

ii. the Price-Quantity Pair quantity if the STEM Clearing Price is less than the Price-Quantity Pair price; and

iii. an amount between 0 MWh and the Price-Quantity Pair quantity if the STEM Clearing Price equals the Price-Quantity Pair price.

6.7. Format of Bilateral Submission Data

6.7.1. A Market Participant submitting Bilateral Submission data or

Standing Bilateral Submission data must include in the submission:

$a$ the identity of the Market Participant making the submission;

$b$ in the case of:

i. Bilateral Submission data, the Trading Day to which the submission relates; and

ii. Standing Bilateral Submission data, the day of the week to which the submission relates, where data provided for a day of the week relates to the Trading Day commencing on that day; and

$c$ for each Trading Interval included in the submission:

i. the net quantity of energy to be sold by the submitting Market Participant;

ii. the identity of each Market Participant purchasing the energy covered by the Bilateral Submission;

iii. the net quantity of energy sold to each Market Participant identified in clause 6.7.1(c)(ii); and

iv. the sum of the quantities in clauses 6.7.1(c)(i) and 6.7.1(c)(iii) must be zero.

6.7.2. All quantities specified in a Bilateral Submission or a Standing

Bilateral Submission:

$a$ must be in units of MWh;

$b$ must equal or exceed 0 MWh for net supply (that is, sold) by the relevant Market Participant;

$c$ must be less than 0 MWh for net consumption (that is, purchased) from the relevant Market Participant;

$d$ must be expressed to a precision of 0.001 MWh; and

$e$ must be Loss Factor adjusted.

6.7.3. A Market Participant must not specify quantities in a Bilateral

Submission or a Standing Bilateral Submission which exceed the quantity of energy that the Market Participant is contracted to supply to the relevant Market Participant.

6.7.4. A Market Participant must not significantly over-state its

consumption as indicated by its Net Contract Position with a regularity that cannot be explained by a reasonable allowance for forecast uncertainty or the impact of Loss Factors.

6.8. [Blank]

The STEM Auction Process

6.9. The STEM Auction

6.9.1. AEMO must undertake the process described in this clause 6.9 for

each Trading Interval in a Trading Day.

6.9.2. The Net Bilateral Position for Market Participant p in Trading

Interval t is:

$a$ the sum of the quantities of energy referred to in clauses

6.7.1(c)(i) and 6.7.1(c)(iii) for the Market Participant in all

Bilateral Submissions for Trading Interval t; or

$b$ zero if no Bilateral Submissions for Trading Interval t refer to the Market Participant.

6.9.3. Subject to clause 6.9.4, AEMO must determine STEM Offers and STEM

Bids for each Market Participant for each Trading Interval in accordance with Appendix 6 using the valid STEM Submissions and Bilateral Submissions relating to that Trading Interval.

6.9.4. Where AEMO does not hold a STEM Submission for a Market

Participant for a Trading Interval, AEMO must not determine STEM Offers or STEM Bids for that Market Participant in that Trading Interval.

6.9.5. AEMO must determine an aggregate STEM bid curve for each Trading

Interval from the STEM Bids where this aggregate STEM bid curve:

$a$ describes the quantity that Market Participants in aggregate wish to purchase from AEMO through the STEM at every price between, and including, the Energy Offer Price Floor and the Energy Offer Price Ceiling; and

$b$ passes through the point indicating zero consumption at the Energy Offer Price Ceiling.

6.9.6. AEMO must determine an aggregate STEM offer curve for each

Trading Interval from the STEM Offers where this aggregate STEM offer curve:

$a$ describes the quantity that Market Participants in aggregate wish to sell to AEMO through the STEM at every price between, and including, the Energy Offer Price Floor and the Energy Offer Price Ceiling; and

$b$ passes through the point indicating zero supply at the Energy Offer Price Floor.

6.9.7. AEMO will determine the STEM Clearing Price for a Trading

Interval as the lowest price at which the STEM offer curve for a Trading Interval intersects the STEM bid curve for the Trading Interval.

6.9.8. AEMO will determine the STEM Clearing Quantity for a Trading

Interval as the greatest quantity at which the STEM offer curve for the Trading Interval intersects the STEM bid curve for the Trading Interval.

6.9.9. All STEM Bid Price-Quantity Pairs for the Trading Interval with a

price greater than the STEM Clearing Price for the Trading Interval must be scheduled by AEMO.

6.9.10. A STEM Bid Price-Quantity Pair with a price equal to the STEM

Clearing Price for the Trading Interval must be scheduled by AEMO up to the Price-Quantity Pair quantity multiplied by:

$a$ the STEM Clearing Quantity less the total quantity for STEM Bid Price-Quantity Pairs scheduled by AEMO in accordance with clause 6.9.9; divided by

$b$ the total quantity for all STEM Bid Price-Quantity Pairs with a price equal to the STEM Clearing Price.

6.9.11. All STEM Offer Price-Quantity Pairs for a Trading Interval with

a price less than the STEM Clearing Price for the Trading Interval must be scheduled by AEMO.

6.9.12. A STEM Offer Price-Quantity Pair for a Trading Interval with a

price equal to the STEM Clearing Price for the Trading Interval must be scheduled by AEMO up to the Price-Quantity Pair quantity multiplied by:

$a$ the STEM Clearing Quantity less the total quantity for STEM Offer Price-Quantity Pairs scheduled by AEMO in accordance with clause 6.9.11; divided by

$b$ the total quantity for all STEM Offer Price-Quantity Pairs with a price equal to the STEM Clearing Price.

6.9.13. The Net Contract Position for Market Participant p in Trading

Interval t is:

$a$ the Net Bilateral Position for Market Participant p in Trading Interval t; minus,

$b$ the amount of energy purchased by the Market Participant from AEMO through the STEM at the STEM Clearing Price, which is the total quantity associated with Price-Quantity Pairs for Market Participant p scheduled by AEMO under clause 6.9.9 or 6.9.10 for Trading Interval t where this energy purchased is represented as a positive value; plus

$c$ the amount of energy sold by the Market Participant to AEMO through the STEM at the STEM Clearing Price, which is the total quantity associated with Price-Quantity Pairs for Market Participant p scheduled by AEMO under clause 6.9.11 or 6.9.12 for Trading Interval t where this energy sold is represented as a positive value.

6.10. Suspension of the STEM

6.10.1. AEMO must suspend the STEM Auction for a Trading Interval if

AEMO considers that it will not be in a position to undertake the process described in section 6.9 and publish a valid STEM Auction result under clauses 6.4.3(b), 6.4.3(c) and 6.4.3(d) for that Trading Interval by the STEM Results Deadline.

6.10.2. In the event that the STEM Auction for a Trading Interval is

suspended under clause 6.10.1, no Market Participant can purchase energy from or sell energy to AEMO through the STEM for that Trading Interval and no STEM Clearing Price is to be declared for that Trading Interval.

6.10.3. No compensation is due or payable to any Market Participant in

the event that the STEM Auction for a Trading Interval is suspended under clause 6.10.1.

6.11. [Blank]

Explanatory Note

Sections 6.11A (not shown) and 6.12 are deleted and replaced with provisions in the Central Dispatch Process in Chapter 6.

However, these sections are also amended by the October 2021 RCM Pricing Amendments as a result of tranche based dispatch payments for DSPs ceasing from the 2019 Reserve Capacity Cycle (i.e. from the 2021 Capacity Year). As these sections are deleted to reflect the amendments contained in the Tranches 2 and 3 Amendments, as those amending rules (made by the Minister at the date this companion version was prepared) will be commenced last, please refer to the October 2021 RCM Pricing Amendments to see the changes to sections 6.11A and 6.12 that will apply from 1 October 2021 until the relevant Tranches 2 and 3 Amendments commence.

Explanatory Note

Section 6.12 (The Non-Balancing Dispatch Merit Order) has been deleted by the Tranches 2 and 3 Amendments (Schedule C). Consequently:

the heading that was above section 6.12 is deleted; and
section 6.12 is reinserted as “[Blank]” to maintain the section number sequence.

6.12. [Blank]

6.13. [Blank]

6.14. [Blank]

6.15. [Blank]

6.16. [Blank]

Explanatory Note

Section 6.17 is deleted. Energy settlement quantities do not require the definition of a Metered Balancing Quantity - see section 9.9, and constraint payments and the Balancing Portfolio will no longer exist.

However, various clauses in section 6.17 are also amended by the October 2021 RCM Pricing Amendments as a result of tranche based dispatch payments for DSPs ceasing from the 2019 Reserve Capacity Cycle (i.e. from the 2021 Capacity Year). As this section is deleted to reflect the amendments contained in the Tranches 2 and 3 Amendments, as those amending rules (made by the Minister at the date this companion version was prepared) will be commenced last, please refer to the October 2021 RCM Pricing Amendments to see the changes to section 6.17 that will apply from 1 October 2021 until the relevant Tranches 2 and 3 Amendments commence.

Clause 6.17.6D(b)(ii) has also been amended by the Tranche 5 Amendments (Schedule B). Please refer to the Tranche 5 Amendments to see the amendments to clause 6.17.6D(b)(ii) that will apply until the section is deleted by the Tranches 2 and 3 Amendments.

6.17. [Blank]

6.18. [Blank]

6.19. [Blank]

6.20. [Blank]

Settlement Data

6.21. Settlement Data

6.21.1. AEMO must provide the following information to the settlement

system for each STEM Auction:

$a$ a flag for each Trading Interval indicating if the STEM Auction was suspended for that Trading Interval;

$b$ the STEM Clearing Price in each Trading Interval in units of $/MWh; and

$c$ for each Market Participant participating in the STEM Auction, the STEM quantity scheduled in each Trading Interval, in units of MWh, where this amount must be positive for a sale of energy to AEMO and negative for a purchase of energy from AEMO.

Explanatory Note

Section 6.21 is deleted and relevant provisions dealt with as part of new section 9.4.

However, clause 6.21.2 is also amended by the October 2021 RCM Pricing Amendments as a result of tranche based dispatch payments for DSPs ceasing from the 2019 Reserve Capacity Cycle (i.e. from the 2021 Capacity Year). As this clause is deleted to reflect the amendments contained in the Tranches 2 and 3 Amendments, as those amending rules (made by the Minister at the date this companion version was prepared) will be commenced last, please refer to the October 2021 RCM Pricing Amendments to see the changes to clause 6.21.2 that will apply from 1 October 2021 until the relevant Tranches 2 and 3 Amendments commence.

6.21.2. [Blank]

6.22. STEM Data

6.22.1. AEMO must publish on the WEM Website the following STEM summary

information:

$a$ for each Trading Interval in each completed Trading Day in the previous 12 calendar months:

i. the total STEM Offer quantity;

ii. the total STEM Bid quantity;

iii. whether the STEM was suspended in relation to the relevant Trading Interval;

iv. where the STEM was not suspended, the STEM quantity purchased by AEMO; and

v. where the STEM was not suspended, the STEM Clearing Price;

$b$ for each Trading Interval in each Trading Day during the 12 calendar months, before the end of the seventh day from the start of the Trading Day:

i. the STEM Offers by Market Participant;

ii. the STEM Bids by Market Participant;

iii. the quantity bought or sold in the STEM by Market Participant; and

iv. the Fuel Declaration made by Market Participant; and

$c$ the STEM Price for each Trading Interval of the current Trading Month for which STEM Auction results have been released to Market Participants.

Explanatory Note

The structure of Chapter 7 reflects the integration of the operation of the Real-Time Market and the Central Dispatch Process in accordance with the Security Constrained Economic Dispatch (SCED) market model.

More specifically:

Chapter 7 is renamed ‘Real-Time Market Operation and Dispatch’ and substantially amended; and
Chapters 7A and 7B are deleted.

As the name implies, SCED determines the most economic dispatch of individual resources across the SWIS. In the current market, AEMO schedules energy and Essential System Services separately, and congestion on the network is accounted for by amendments to the market dispatch.

The adoption of the SCED market model, which includes consideration of network constraints in the calculation of dispatch schedules, is essential for the SWIS in order to maintain system security as congestion increases. Adopting the SCED market model will require AEMO to replace the existing market and dispatch systems that it uses to operate the Wholesale Electricity Market.

Adopting a SCED market model is fundamental to realising the benefits of the sustainable and efficient management of network constraints, and is expected to deliver the following benefits.

transparent determination of the least-cost dispatch outcome for the market, accounting for generation offers and network conditions, and allowing Market Participants to respond, resulting in increased competition in the Real-Time Market and a downward pressure on the energy price over time;
greater automation in the calculation of network constraints, which improves network efficiency by allowing constraints to be set less conservatively without compromising system reliability; and
greater automation in the dispatch process, so that system security can be managed efficiently as the level of constraints increases, and the generation mix continues to change.

However, various clauses in Chapter 7 are also amended by the October 2021 RCM Pricing Amendments, including as a result of tranche based dispatch payments for DSPs ceasing from the 2019 Reserve Capacity Cycle (i.e. from the 2021 Capacity Year), the Tranche 1 Amendments, the Miscellaneous Amendments No. 1 and the Amending Rules contained in the Rule Change Panel's Final Report for Rule Change Proposal RC_2014_03 (Administrative Improvements to the Outage Process). As Chapter 7 is deleted to reflect the amendments contained in the Tranches 2 and 3 Amendments, as those amending rules (made by the Minister at the date this companion version was prepared) will be commenced last, please refer to the October 2021 RCM Pricing Amendments, Tranche 1 Amendments, Miscellaneous Amendments No. 1 and the Final Report for Rule Change Proposal RC_2014_03 (Administrative Improvements to the Outage Process) to see the changes to Chapter 7 that will either apply until the Tranches 2 and 3 Amendments to Chapter 7 commence, or that amend amending rules contained in the Tranches 2 and 3 Amendments.

Several clauses in Chapter 7 of the current WEM Rules have also been amended by the Tranche 5 Amendments (Schedule B). However, as this Chapter 7 reflects the amendments that will apply from the start of the new market, please refer to the Tranche 5 Amendments to see the amendments to those clauses that will apply until that time.

The key changes proposed to the Real-Time Market arrangements in Chapter 7 pursuant to the Tranche 6 Amendments include:

changes to the rules around the provision and use of Injection and Withdrawal forecasts for Semi-Scheduled Facilities and Non-Scheduled Facilities;
changes to the obligations to provide Real-Time Market Submissions for Non-Scheduled Facilities;
clarification of how AEMO uses Real-Time Market Submissions for Non-Scheduled Facilities in the Central Dispatch Process;
changes to the submission and dispatch arrangements for Demand Side Programmes;
clarification of the terminology, content requirements and processing rules for Real-Time Market Submissions; and
changes to the publication requirements for dispatch-related information.

The changes are described in more detail in the Explantory Notes to the relevant sections of Chapter 7.

7 Real-Time Market Operation and Dispatch

Explanatory Note

Section 7.1 provides a head of power for the Real-Time Market and for AEMO to document the new Real-Time Market Timetable in a WEM Procedure (which is required to be published on the WEM Website).

The Real-Time Market Timetable is the timetable developed by AEMO for the operation of the Real-Time Market and the provision of certain market information relating to, amongst other things, dispatch and pre-dispatch, and specifies who must do what and by when.

As the Real-Time Market Timetable is required to be documented by AEMO in a WEM Procedure, the Procedure Change Process in section 2.10 will need to be followed in relation to any proposed changes to the timetable.

7.1. Real-Time Market

7.1.1. AEMO must establish and operate the Real-Time Market.

7.1.2. AEMO must:

$a$ document the Real-Time Market Timetable in a WEM Procedure; and

$b$ operate the Real-Time Market according to the Real-Time Market Timetable.

Explanatory Note

Clause 7.1.3 is amended to extend the scope of the Real-Time Market Timetable to cover timelines for:

DSP Withdrawal Profile Submissions; and
the new DSP Week-Ahead Schedules and DSP Pre-Dispatch Schedules.

The timelines for the DSP Schedules are specified separately from the corresponding Market Schedules because they may not necessarily be generated at the same time.

Clause 7.1.3 is also amended to reflect that the publication of some information on the WEM Website may occur after the information is made available to Market Participants.

7.1.3. The Real-Time Market Timetable must include:

$a$ timelines for:

i. the submission of Real-Time Market Submissions and DSP Withdrawal Profile Submissions, including any subsequent or replacement submissions;

ii. the calculation and provision to Market Participants of the following information in a Dispatch Interval for the next Dispatch Interval:

1. Market Clearing Prices;

2. Dispatch Targets;

3. Dispatch Caps; and

4. Essential System Service Enablement Quantities;

iii. the calculation and provision to Market Participants of a Dispatch Schedule at least once each Dispatch Interval;

iv. the calculation and provision to Market Participants of a Pre-Dispatch Schedule at least once each Pre-Dispatch Interval;

v. the calculation and provision to Market Participants of a DSP Pre‑Dispatch Schedule at least once each Pre-Dispatch Interval;

vi. the calculation and provision to Market Participants of a Week-Ahead Schedule at least once each Trading Day;

vii. the calculation and provision to Market Participants of a DSP Week-Ahead Schedule at least once each Trading Day; and

viii. the publication of the information referred to in clauses 7.1.3(a)(ii) to 7.1.3(a)(vii) on the WEM Website; and

$b$ any other information that AEMO considers relevant to the operation of the Real-Time Market Timetable.

Explanatory Note

Section 7.2 provides the head of power for AEMO to operate a Central Dispatch Process in accordance with the SCED market model, the objective of which is to maximise the value (of schedulable load) and minimise the cost of supply while taking into account various constraints. See also the Explanatory Note to Chapter 7.

The mathematical formulation of the Dispatch Algorithm that AEMO uses in the Central Dispatch Process is to be published by AEMO in a WEM Procedure.

7.2. Central Dispatch Process

7.2.1. AEMO must establish and operate the Central Dispatch Process to dispatch Registered Facilities in order to balance electricity supply and demand, using its reasonable endeavours to maintain Power System Security and Power System Reliability in accordance with Chapter 3.

7.2.2. AEMO must use its reasonable endeavours to maximise the value of Real-Time Market trading:

$a$ within the parameters for maintaining Power System Security and Power System Reliability in accordance with Chapter 3; and

$b$ on the basis of Real-Time Market Submissions.

7.2.3. Where AEMO reasonably determines that an urgent change to the Dispatch Algorithm is required to maintain Power System Security and Power System Reliability in accordance with Chapter 3, AEMO may implement the change. Where AEMO makes a change to the Dispatch Algorithm in accordance with this clause 7.2.3, AEMO must:

$a$ publish the change on the WEM Website, and the reasons the change was required in order for AEMO to maintain Power System Security and Power System Reliability in accordance with Chapter 3; and

$b$ if the Power System Security and Power System Reliability issue that is being addressed by the change is not temporary, AEMO must as soon as practicable, submit a Procedure Change Proposal for revisions to the WEM Procedure referred to in clause 7.2.5.

Explanatory Note

Clause 7.2.4 is intended to be an exhaustive list of all of the types of constraints that may be included in the optimisation problem that the Dispatch Algorithm will need to solve. If additional necessary constraint types are identified, they will be added to this clause. To the extent that AEMO needs to depart from the Dispatch Algorithm, AEMO will adjust the inputs (clause 7.2.4(f)) or override the outputs through exercising its emergency powers (clause 3.5.5).

Clause 7.2.4(l) is amended to restore the term “Facility Performance Factors”, which was inadvertently changed to “Facility Performance Offsets” by the Tranche 5 Amendments (Schedule l, paragraph 44.2).

Clause 7.2.4(cA) and clause 7.2.4A have been included to ensure that the Unconstrained Injection Forecasts and Unconstrained Withdrawal Forecasts provided in Real-Time Market Submissions under section 7.4 are included in the Dispatch Algorithm, and to allow for alternative forecast quantities to be used where deemed necessary by AEMO.

Clause 7.2.4(d) is amended to refer to the appropriate forecast demand quantities.

7.2.4. The Dispatch Algorithm must seek to maximise the value of Real-Time Market trading by maximising:

$a$ the value of dispatched Load based on Real-Time Market Bids; less

$b$ the cost of dispatched energy and Frequency Co-optimised Essential System Services based on Real-Time Market Offers,

subject to:

$c$ respecting the quantities, Ramp Rate Limits and other limits specified in Real-Time Market Submissions;

(cA) the Unconstrained Injection Forecasts and Unconstrained Withdrawal Forecasts specified in Real-Time Market Submissions, or any alternative forecast quantities determined by AEMO under clause 7.2.4A;

$d$ dispatching sufficient energy to meet the Forecast Unscheduled Operational Demand, Unconstrained Withdrawal Forecast quantities for Non Scheduled Facilities and scheduled Withdrawal quantities for Scheduled Facilities and Semi-Scheduled Facilities;

$e$ respecting Network Constraints, as reflected in the Constraint Equations developed by AEMO in accordance with section 2.27A;

$f$ meeting Power System Security and Power System Reliability requirements as reflected in Constraint Equations developed by AEMO having regard to the WEM Procedures referred to in clauses 3.2.7 and 3.3.2, including any limits on maximum ramp rates;

$g$ Transmission Loss Factors and Distribution Loss Factors;

$h$ current levels of Injection and Withdrawal;

$i$ meeting the Essential System Service Standards as reflected in the Essential System Service requirements determined by AEMO in accordance with the WEM Procedure referred to in clause 3.11.7 and in Constraint Equations developed by AEMO having regard to that WEM Procedure;

(iA) implementing the terms of NCESS Contracts as reflected in Constraint Equations formulated by AEMO under clause 5.7.3;

$j$ energy Injection and Withdrawal capabilities as they vary by Charge Level;

$k$ respecting Oscillation Control Constraint Equations;

$l$ accounting for all relevant Contingency Lower Offsets, Contingency Raise Offsets and Facility Performance Factors in determining scheduled and dispatched quantities of Contingency Reserve;

$m$ accounting for all Facilities that are Inflexible;

$n$ taking into account the Largest Credible Supply Contingency relative to the scheduled or dispatched quantity of Contingency Reserve Raise; and

$o$ arrangements for dispatch of tied Real-Time Market Bids and tied Real-Time Market Offers.

7.2.4A. AEMO may determine and use as an input to the Dispatch Algorithm alternative forecast quantities to the Unconstrained Injection Forecast and Unconstrained Withdrawal Forecast provided in a Real-Time Market Submission if AEMO reasonably considers that the alternative forecast quantities are likely to be more accurate.

Explanatory Note

Clause 7.2.5(a) refers to the quantities of RoCoF Control Service and Contingency Reserve Raise, as these will be determined dynamically as part of the Dispatch Algorithm, while the required quantity of other ESS will be determined outside the Dispatch Algorithm and provided as an input.

Clause 7.2.5 is further amended to correct clause numbering errors.

7.2.5. AEMO must develop and document in a WEM Procedure:

$a$ the Dispatch Algorithm used by AEMO for the purpose of the Central Dispatch Process and setting Market Clearing Prices and the mathematical formulation of the Dispatch Algorithm, including:

i. the conversion of Facility Speed Factors into Facility Performance Factors;

ii. the calculation of Minimum RoCoF Control Requirement and Additional RoCoF Control Requirement;

iii. the calculation of the required quantity of Contingency Reserve Raise; and

iv. the maximum number of Price-Quantity Pairs that may be included in a Real-Time Market Submission for a Dispatch Interval for each Market Service,

in a form that:

v. sets out the form, scope and construction of each type of Constraint Equation;

vi. describes and quantifies the mechanism by which different Constraints are taken into account and prioritised, including in accordance with clauses 3.12.2 and 7.6.25; and

vi AEMO reasonably considers will enable a third party, such as the Market Auditor or the Economic Regulation Authority, to replicate the results of the Dispatch Algorithm by using the same inputs;

$b$ the methodology it uses to determine:

i. Contingency Raise Offsets;

ii. Contingency Lower Offsets;

iii. Facility Performance Factors;

iv. the Minimum RoCoF Control Requirement;

v. the Additional RoCoF Control Requirement;

vi. the RoCoF Control Requirement; and

vii. the RoCoF Upper Limit;

$c$ the processes to be followed by AEMO and Market Participants in accounting for Inflexible Facilities; and

$d$ any methodology for replacement of erroneous input data or substitution for missing input data.

Explanatory Note

Clause 7.2.6 provides a head of power for AEMO to relax Constraints.

The Market Clearing Engine is the software to be developed by AEMO to ensure the Central Dispatch Process maximises the value and minimises the cost of supply while taking into account various constraints. It may not be possible to respect all Constraints that need to be considered in a Dispatch Interval. Where this occurs, the solution is infeasible and the Market Clearing Engine would produce prices that do not reflect the cost of supply. As this would not be an acceptable outcome, AEMO will have the power to ensure Dispatch processes continue by relaxing Constraints in accordance with the WEM Procedure referred to in clause 7.2.8.

7.2.6. AEMO may relax the Constraints referred to in clause 7.2.4 in order to resolve infeasible dispatch solutions provided that any relaxation of a Constraint:

$a$ achieves a feasible dispatch outcome;

$b$ meets AEMO's obligations to maintain Power System Security and Power System Reliability in accordance with the WEM Rules;

$c$ would not endanger the safety of any person, damage equipment, or breach any applicable law;

$d$ meets the pricing principles listed in clause 7.11A.1; and

$e$ meets AEMO’s obligations to maximise the value of Real-Time Market trading under clause 7.2.4.

Explanatory Note

Clause 7.2.7 requires AEMO to publish details of any Constraints that were relaxed under clause 7.2.6 on the WEM Website as soon as practicable after the start of the relevant Dispatch Interval, and to prepare a quarterly report summarising, and providing further details, with respect to those relaxed Constraints. The quarterly report is part of the Congestion Information Resource referred to in clause 2.27B.3 (which is published on the WEM Website in accordance with clause 2.27B.2(b)).

7.2.7. AEMO must:

$a$ as soon as practicable after the start of the Dispatch Interval, publish on the WEM Website details of any Constraints relaxed under clause 7.2.6 for that Dispatch Interval; and

$b$ as soon as practicable after the end of each quarter, publish on the WEM Website a report summarising the total number, frequency and type of Constraints that were relaxed under clause 7.2.6 during that quarter.

Explanatory Note

Clause 7.2.8 requires AEMO to document the processes it will follow for the relaxation of Constraints under clause 7.2.6 and the preparation of reports in accordance with clause 7.2.7(b) in a WEM Procedure.

7.2.8. AEMO must document in a WEM Procedure the processes to be followed by AEMO for the relaxation of Constraints under clause 7.2.6.

Explanatory Note

Section 7.3 (which replaces current section 7.2) provides for continual publication of latest Load Forecasts with Market Schedules. Separate Non-Scheduled Generator forecasts are no longer required, as they will be submitted via Real-Time Market Offers.

Section 7.3 has been amended to use the new defined term “Forecast Unscheduled Operational Demand” for the demand forecast that is input to the Dispatch Algorithm. The Dispatch Algorithm outputs include Forecast Operational Demand and Forecast Operational Withdrawal, where:

Forecast Operational Demand is the total MW of Injection forecast to be required at the end of the interval to meet the Forecast Unscheduled Operational Demand and the Forecast Operational Withdrawal; and
Forecast Operational Withdrawal is the sum of the expected Non-Scheduled Facility Withdrawals and any “dispatched” Withdrawals of Scheduled Facilities or Semi-Scheduled Facilities.

7.3. Forecast Unscheduled Operational Demand

7.3.1. AEMO must prepare a Forecast Unscheduled Operational Demand for:

$a$ each Pre-Dispatch Interval within each Week-Ahead Schedule Horizon; and

$b$ each Dispatch Interval within each Dispatch Schedule Horizon.

7.3.2. The Forecast Unscheduled Operational Demand must represent AEMO’s best estimate of the total demand, in MW, to be served in the Pre-Dispatch Interval or Dispatch Interval, excluding:

$a$ any Withdrawal by Non-Scheduled Facilities; and

$b$ any Withdrawal quantities scheduled by the Dispatch Algorithm for Scheduled Facilities or Semi-Scheduled Facilities.

7.3.3. [Blank]

7.3.4. AEMO must document in a WEM Procedure the methodology and processes it follows for determining and publishing the Forecast Unscheduled Operational Demand under this section 7.3.

Explanatory Note

Section 7.4 sets out the obligations with respect to Real-Time Market Submissions, and is structured as follows:

clauses 7.4.1 to 7.4.11 – Obligations and Meanings;
clauses 7.4.12 to 7.4.20 - Real-Time Market Submissions for Demand Side Programmes;
clauses 7.4.21 to 7.4.37 – Timing;
clauses 7.4.38 to 7.4.45 – Format;
clauses 7.4.46 to 7.4.47 – Construction;
clauses 7.4.48 to 7.4.49 – Validation of Dispatch Bids and Offers;
clauses 7.4.50 to 7.4.53 – Processing; and
clauses 7.4.54 to 7.4.62 – Standing Submissions.

An overview of the main changes affecting section 7.4 is provided below.

Changes to Real-Time Market Submission terminology and processing rules

Section 7.4 has been amended to clarify the definitions of “Real-Time Market Submission” and “Standing Real-Time Market Submission” and the general processing rules for these submissions. Under the proposed changes:

A Real-Time Market Submission relates to a Registered Facility, Market Service and Dispatch Interval.
A Market Participant may include multiple Real-Time Market Submissions in a single electronic submission. AEMO will either accept the electronic submission (and all the Real-Time Market Submissions within it) or reject the electronic submission (and all the Real-Time Market Submissions within it).
A Standing Real-Time Market Submission is a default Real-Time Market Submission for a Registered Facility and Market Service for Dispatch Intervals starting at specified times on Trading Days of a specified type.
A Market Participant may include multiple Standing Real-Time Market Submissions in a single electronic submission, but must ensure that the Standing Real-Time Market Submissions in an electronic submission for a Registered Facility and Market Service, in combination, uniquely specify the default Real-Time Market Submission to apply for each Dispatch Interval in a generic Trading Week.
At any point in time, the Real-Time Market Submission for a Registered Facility, Market Service and Dispatch Interval is the (variation) Real-Time Market Submission most recently accepted by AEMO under clause 7.4.49(a)(i), or, if no such submission exists, the most recently accepted applicable Standing Real-Time Market Submission.

Changes to the provision and use of Injection and Withdrawal forecasts for Semi-Scheduled Facilities and Non-Scheduled Facilities

Previously, a Market Participant was required to ensure that the sum of the quantities in the Price-Quantity Pairs for Injection in its Semi-Scheduled Facility Real-Time Market Submission was equal to the Market Participant’s unconstrained Injection forecast for the Facility. While this arrangement provided an Injection forecast to AEMO, it could also restrict the level to which the Facility could be dispatched, because of the absence of Price-Quantity Pairs covering Injection levels above the Market Participant’s forecast. Additionally, the arrangement did not support the provision of Withdrawal forecasts.

Under the proposed new arrangements, the quantities in the Price-Quantity Pairs for energy for a Semi-Scheduled Facility or Non-Scheduled Facility should sum to the maximum quantity that the Market Participant considers the Facility could Inject/Withdraw assuming it was not constrained by AEMO (including on price), i.e. assuming no shortage of any intermittent fuel such as wind. The Market Participant will also include an Unconstrained Injection Forecast and Unconstrained Withdrawal Forecast, defined as follows, in each Real-Time Market Submission:

Unconstrained Injection Forecast: The expected MW level of Injection at the end of a Dispatch Interval for a Semi-Scheduled Facility or Non-Scheduled Facility, assuming that the Facility will not be subject to a Dispatch Instruction or direction from AEMO that limits its Injection, and allowing for expected conditions, commitment and control intentions and the effect of any Outages that have not been rejected for the Facility.
Unconstrained Withdrawal Forecast: The expected MW level of Withdrawal at the end of a Dispatch Interval for a Semi-Scheduled Facility or Non-Scheduled Facility, assuming that the Facility will not be subject to a Dispatch Instruction or direction from AEMO that limits its Withdrawal, and allowing for expected conditions, commitment and control intentions and the effect of any Outages that have not been rejected for the Facility

AEMO may use the Unconstrained Injection Forecasts and Unconstrained Withdrawal Forecasts provided in Real-Time Market Submissions as inputs to the Dispatch Algorithm, but may also use alternative forecasts if it reasonably considers they are likely to be more accurate.

Price-Quantity Pairs will continue to be used within the Dispatch Algorithm to determine Dispatch Caps for Semi-Scheduled Facilities. However, Semi-Scheduled Facilities will not be constrained where their Unconstrained Injection Forecasts or Unconstrained Withdrawal Forecasts are lower than the cleared Price-Quantity Pairs.

Changes to Real-Time Market Submission obligations for Non-Scheduled Facilities:

It is important for AEMO to have visibility of a Non-Scheduled Facility’s intentions to support the production of forward-looking Market Schedules and provide overall transparency to the market. For this reason, Market Participants will be required to submit Real-Time Market Submissions for their Non-Scheduled Facilities.

The submission requirements for Non-Scheduled Facilities have been separated from the requirements for the Registered Facilities being actively dispatched by AEMO through the Dispatch Algorithm (Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads). The Market Participant must declare its intentions (either Injection or Withdrawal) by including a single Price-Quantity Pair at the price cap/floor. The Market Participant will also provide an Unconstrained Injection Forecast and Unconstrained Withdrawal Forecast for each Dispatch Interval.

These inputs will be used in the Dispatch Algorithm to account for the expected impact of Non‑Scheduled Facilities, and will be included in the publication requirements to support transparency.

While Market Participants will be required to make Real-Time Market Submissions for Non-Scheduled Facilities, they will have a lower threshold for updating their submissions to reflect that they are not actively dispatched. The obligation to maintain accurate forecast quantities for a Non-Scheduled Facility will not attract civil penalties, and the requirement to update forecast quantities is reduced to when information supporting underlying expectations has significantly changed or the Market Participant is knowingly intervening in the operation of the Facility (e.g. has specific knowledge about Outages, commitment or control intentions of behind-the-meter components), as provided for under new clause 7.4.37A.

Relocation of provisions relating to Demand Side Programme submissions:

The provisions relating to DSP Withdrawal Profile Submissions and Standing DSP Withdrawal Profile Submissions have been moved from section 7.4 to a new section 7.4A.

7.4. Real-Time Market Submissions

Explanatory Note

Clauses 7.4.1 to 7.4.14 set out the obligations with respect to Real-Time Market Submissions and any restrictions on Real-Time Market Bids and Real-Time Market Offers for Registered Facilities with certain characteristics.

Clause 7.4.1 is amended to specify the Registered Facilities/Market Services for which Real-Time Market Submissions are required.

Real-Time Market Submissions – Obligations and meaning

7.4.1. A Market Participant must ensure that it has made a Real-Time Market Submission or Standing Real-Time Market Submission in accordance with this section 7.4 for each Dispatch Interval in the Week-Ahead Schedule Horizon:

$a$ for energy, for each of its Scheduled Facilities, Semi-Scheduled Facilities and Non-Scheduled Facilities; and

$b$ for each Frequency Co-optimised Essential System Service, for each of its Registered Facilities that is accredited to provide that Frequency Co‑optimised Essential System Service.

Explanatory Note

Clauses 7.4.1A, 7.4.1B and 7.4.1C describe how the Real-Time Market Submission for a Registered Facility, Market Service and Dispatch Interval is determined from any relevant submissions accepted by AEMO over time.

7.4.1A. If AEMO has not accepted a Real-Time Market Submission for a Registered Facility, Market Service and Dispatch Interval under clause 7.4.49(a)(i), but has accepted an applicable Standing Real-Time Market Submission, then the Standing Real-Time Market Submission is deemed to be the Real-Time Market Submission for the Registered Facility, Market Service and Dispatch Interval.

7.4.1B. A Real-Time Market Submission for a Registered Facility, Market Service and Dispatch Interval that AEMO accepts under clause 7.4.49(a)(i) replaces any previously accepted Real-Time Market Submission for, and has effect in relation to, the Registered Facility, Market Service and Dispatch Interval.

7.4.1C. If:

$a$ AEMO has not yet accepted a Real-Time Market Submission for a Registered Facility, Market Service and Dispatch Interval under clause 7.4.49(a)(i); and

$b$ AEMO accepts a Standing Real-Time Market Submission for the Registered Facility and Market Service that is applicable to the Dispatch Interval,

then the Standing Real-Time Market Submission replaces any previously accepted Standing Real-Time Market Submission as the deemed Real-Time Market Submission for the Registered Facility, Market Service and Dispatch Interval.

Explanatory Note

Clause 7.4.2 is intended to be a civil penalty provision but civil penalties will only apply to submissions for Dispatch Intervals in the Pre-Dispatch Schedule Horizon.

Clause 7.4.2 is amended to:

correct a clause reference error;
restrict the requirements to Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads (Non-Scheduled Facilities are covered in clause 7.4.2B and Demand Side Programmes are covered in section 7.4A); and
ensure that the requirements only apply to Dispatch Intervals within the Week-Ahead Schedule Horizon;
clarify the requirements relating to Outages;
include “control” in clause 7.4.2(b)(i) to cover the Market Participant’s intentions about how it will operate the components of its Registered Facility;
account for the replacement of Unadjusted Semi-Scheduled Injection Forecasts with Unconstrained Injection Forecasts and Unconstrained Withdrawal Forecasts; and
correct minor typographical errors.

7.4.2. Subject to clause 7.4.37, a Market Participant must make reasonable endeavours to ensure that its Real-Time Market Submission for each of its Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads for each Dispatch Interval accurately reflects:

$a$ for Dispatch Intervals in the Week-Ahead Schedule Horizon:

i. the Market Participant’s reasonable expectation of the capability of its Registered Facility to be dispatched in the Real-Time Market;

ii. any applicable tests required under these WEM Rules, including tests for Reserve Capacity under section 4.25;

iii. any Outage Plans applicable to the Dispatch Interval that have not been rejected, withdrawn or subjected to an Outage Recall Direction that affects the Dispatch Interval; and

iv. any applicable Forced Outages applying to the Dispatch Interval;

$b$ for Dispatch Intervals in the Pre-Dispatch Schedule Horizon, all information reasonably available to the Market Participant, including:

i. the Market Participant’s intentions for commitment, control and decommitment;

ii. the Market Participant’s intentions for providing Frequency Co-optimised Essential System Services; and

iii. in the case of a Semi-Scheduled Facility, any changes to the Market Participant’s Unconstrained Injection Forecast or Unconstrained Withdrawal Forecast that exceed the Tolerance Range or Facility Tolerance Range applicable to the Semi-Scheduled Facility; and

$c$ the prices at which the Market Participant intends the Registered Facility will participate in the Real-Time Market for:

i. Injections;

ii. Withdrawals; and

iii. providing a Frequency Co-optimised Essential System Service for which the Registered Facility is accredited,

as applicable.

Explanatory Note

Clause 7.4.2A is amended to correct a typographical error and to tie the obligation on a Market Participant to the Market Schedules that have been made available to it, because the publication of these schedules on the WEM Website may be delayed.

7.4.2A. In meeting the requirements of clause 7.4.2, a Market Participant must make reasonable endeavours to take into account information available in Market Schedules made available to the Market Participant by AEMO, including estimates of cleared energy and Essential System Service Enablement Quantities.

Explanatory Note

New clause 7.4.2B sets out the corresponding requirements for Non-Scheduled Facilities to the requirements specified for Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads in clause 7.4.2. Unlike clause 7.4.2, clause 7.4.2B is not intended to be a civil penalty provision.

7.4.2B. Subject to clause 7.4.37A, a Market Participant must make Real-Time Market Submissions for each of its Non-Scheduled Facilities that reflect, for each Dispatch Interval in the Week-Ahead Schedule Horizon:

$a$ the Market Participant’s reasonable expectation of the Injection and Withdrawal capability of the Non-Scheduled Facility, allowing for any known tests or Outages of the Non-Scheduled Facility;

$b$ the Market Participant’s Unconstrained Injection Forecast for the Non‑Scheduled Facility; and

$c$ the Market Participant’s Unconstrained Withdrawal Forecast for the Non‑Scheduled Facility.

7.4.3. A Real-Time Market Submission is deemed to constitute a declaration by an Authorised Officer of the Market Participant.

Explanatory Note

The SESSM is set out in section 3.15A.

Clause 7.4.4 describes specific obligations with respect to Real-Time Submissions for a Registered Facility where the relevant Market Participant holds a SESSM Award for the Registered Facility.

7.4.4. Where a Market Participant holds a SESSM Award for a Registered Facility, without limiting any other obligation or requirement under this section 7.4, the Market Participant must make Real-Time Market Submissions for the Registered Facility in accordance with the SESSM Award.

Explanatory Note

Amendments to clause 7.4.5 address the following issues:

When the Pre-Dispatch Schedule projects a shortfall in a Frequency Control Essential System Service (FCESS), clause 7.4.5(b) requires SESSM Award holders to update their Real-Time Market Submissions to offer all the available accredited capacity of their awarded Facilities as In‑Service Capacity. This could result in more capacity being offered as In-Service Capacity than is necessary or desirable.
The clause does not correctly account for a Facility that is not subject to any Outage in a Dispatch Interval, e.g. clause 7.4.5(a) would require the Market Participant to offer the maximum accredited quantity of the relevant FCESS instead of the contracted quantity in this situation.

Under the amendments, a Market Participant holding a SESSM Award must:

under normal conditions, offer (at least) the lower of their contracted quantity and available accredited capacity in the relevant FCESS, as either Available or In-Service Capacity (clause 7.4.5(a));
if the Reference Scenario for a Pre-Dispatch Interval projects a shortfall in the FCESS, ensure that they are offering all their available accredited capacity in the FCESS, as either Available or In‑Service Capacity (clause 7.4.5(b)); and
if the Reference Scenario for a Pre-Dispatch Interval or Dispatch Interval projects that the relevant Facility will be enabled to provide the FCESS, ensure that they are offering the relevant Essential System Service Enablement Quantity as In-Service Capacity, as well as sufficient In-Service energy capacity to facilitate the FCESS enablement (clause 7.4.5(c)).

The available accredited capacity of the Facility in the relevant FCESS is determined as:

the lowest Remaining Available Capacity for the FCESS under any applicable Outage for the Facility; or
if there are no applicable Outages, the maximum accredited quantity of the Facility for the FCESS.

Further amendments to clause 7.4.5 are proposed to:

use the correct defined term (SESSM Availability Quantity); and
clarify which Real-Time Market Submissions are relevant in clause 7.4.5(b).

7.4.5. For the purpose of a Real-Time Market Submission under clause 7.4.4, a Market Participant must:

$a$ for all Dispatch Intervals within the SESSM Service Timing and the Week-Ahead Schedule Horizon:

i. offer a quantity of the relevant Frequency Co-optimised Essential System Service greater than or equal to the lower of:

1. the sum of the relevant Base ESS Quantity and SESSM Availability Quantity; and

2. the lowest Remaining Available Capacity for that Frequency Co-optimised Essential System Service under any Outage applying to the Registered Facility in the Dispatch Interval, or, if there are no applicable Outages, the relevant maximum accredited quantity of that Frequency Co-optimised Essential System Service for the Registered Facility,

in Price-Quantity Pairs; and

ii. specify an offer price in Price-Quantity Pairs relating to the SESSM Availability Quantity not exceeding the SESSM Offer Cap for the SESSM Award;

Explanatory Note

Industry feedback proposed a separate notification to Market Participants. AEMO will publish schedules with information on the presence or absence of a shortfall. No additional notification is required, as Market Participants have a general obligation to take published Pre-Dispatch Schedules into account in their Real-Time Market Submissions.

$b$ where the Reference Scenario for a Pre-Dispatch Interval projects a shortfall in an awarded Frequency Co-optimised Essential System Service, ensure that the Real-Time Market Submissions for the Registered Facility and Frequency Co-optimised Essential System Service for that Pre-Dispatch Interval are offering a quantity of the relevant Frequency Co-optimised Essential System Service greater than or equal to the lowest Remaining Available Capacity for that Frequency Co-optimised Essential System Service under any Outage applying to the Registered Facility in the Pre-Dispatch Interval, or, if there are no applicable Outages, the relevant maximum accredited quantity of the Frequency Co-optimised Essential System Service for the Registered Facility; and

$c$ where the Reference Scenario for a Pre-Dispatch Interval or Dispatch Interval projects that the Registered Facility will be enabled to provide an awarded Frequency Co-optimised Essential System Service, ensure that the Real-Time Market Submissions for the Registered Facility for that Pre‑Dispatch Interval or Dispatch Interval:

i. present the relevant Essential System Service Enablement Quantity as In-Service Capacity; and

ii. offer sufficient capacity as In-Service Capacity for energy to allow the Registered Facility to be dispatched for energy between any relevant Enablement Limits.

7.4.6. Where the Reference Scenario for a Pre-Dispatch Interval or Dispatch Interval projects that a Registered Facility will be enabled to provide RoCoF Control Service, and all or part of the relevant Essential System Service Enablement Quantity is included in the Real-Time Market Submissions for the Registered Facility as Available Capacity, the Market Participant for the Registered Facility must submit updated Real-Time Market Submissions for the Registered Facility for that Pre-Dispatch Interval or Dispatch Interval as soon as practicable to:

$a$ present the relevant Essential System Service Enablement Quantity as In-Service Capacity; or

$b$ present the relevant Essential System Service Enablement Quantity such that the Registered Facility is not enabled for RoCoF Control Service in the Reference Scenario for the relevant Pre-Dispatch Interval or Dispatch Interval.

7.4.7. [Blank]

Explanatory Note

The Real-Time Market Submissions for Non-Scheduled Facilities will contain a single Price-Quantity Pair that reflects the Market Participant’s intentions for the Dispatch Interval. Clause 7.4.8 is replaced and clause 7.4.9 is removed accordingly.

7.4.8. A Market Participant must ensure that each Real-Time Market Submission for energy for its Non-Scheduled Facility includes:

$a$ if the Market Participant intends the Non-Scheduled Facility to be Injecting at the end of the Dispatch Interval, a single Price-Quantity Pair with:

i. a quantity equal to the intended maximum Injection MW level for the Dispatch Interval; and

ii. a price equal to the Energy Offer Price Floor when converted into a Loss Factor Adjusted Price; and

$b$ otherwise, a single Price-Quantity Pair with:

i. a quantity equal to the intended maximum Withdrawal MW level for the Dispatch Interval; and

ii. a price equal to the Energy Offer Price Ceiling when converted into a Loss Factor Adjusted Price.

7.4.9. [Blank]

Explanatory Note

In accordance with the new framework for ESS, Interruptible Loads will only be eligible to be accredited to provide Contingency Reserve Raise and not any other type of ESS. Clause 7.4.10 reflects the intent for Interruptible Loads to use a load association process similar to DSPs, and may be adjusted with the amending rules for Registration.

Industry feedback noted that it could be possible for the relevant Interruptible Load and DSP to be registered by different Market Participants. It will be the responsibility of the Market Participant for the Interruptible Load to monitor schedules for dispatch of an overlapping DSP.

7.4.10. A Market Participant must ensure that a Real-Time Market Submission for an Interruptible Load for a Dispatch Interval:

$a$ is for Contingency Reserve Raise only; and

$b$ includes zero MW in respect of any Associated Load of the Interruptible Load that is also an Associated Load of a Demand Side Programme that has been issued a Dispatch Instruction with a non-zero MW quantity for the same Dispatch Interval.

7.4.11. Where a Registered Facility has been accredited in accordance with section 2.34A to provide Contingency Reserve Raise subject to a Maximum Contingency Reserve Block Size, the quantities in each Price-Quantity Pair in the Real-Time Market Submissions for Contingency Reserve Raise for the Registered Facility must not exceed the applicable Maximum Contingency Reserve Block Size.

7.4.12. [Blank]

7.4.13. [Blank]

7.4.14. [Blank]

7.4.15. [Blank]

7.4.16. [Blank]

7.4.17. [Blank]

7.4.18. [Blank]

7.4.19. [Blank]

7.4.20. [Blank]

Explanatory Note

Clauses 7.4.21 to 7.4.37 set out the obligations and requirements regarding the timing for Market Participants to make Real-Time Market Submissions, including giving AEMO the power to specify earliest and latest times for submitting Real-Time Market Submissions.

Real-Time Market Submissions – Timing

Explanatory Note

Clause 7.4.21 allows Market Participants to update Real-Time Market Submissions for any Dispatch Interval as long as the update is made within the relevant horizon and before the Gate Closure for the relevant Dispatch Interval.

Clauses 7.4.21 to 7.4.24 are amended to:

simplify the drafting by making the specification of a Real-Time Market Submission Acceptance Horizon mandatory; and
clarify the submission timing limits in clause 7.4.21 (now moved to clause 7.4.23).

7.4.21. AEMO must specify a Real-Time Market Submission Acceptance Horizon in a WEM Procedure.

7.4.22. The Real-Time Market Submission Acceptance Horizon must not be less than four weeks before the relevant Dispatch Interval.

7.4.23. Subject to clause 7.4.35, a Market Participant may submit a Real-Time Market Submission for a Dispatch Interval at any time:

$a$ on or after the Real-Time Market Submission Acceptance Horizon for the Dispatch Interval; and

$b$ before the start of the Dispatch Interval.

7.4.24. [Blank]

7.4.25. [Blank]

Explanatory Note

Clauses 7.4.26 to 7.4.28 are amended to clarify the requirements to provide reasons for late submissions and submissions containing deviations from Standing Data parameters. A Market Participant will be required to provide a reason with any Real-Time Market Submission that:

is submitted for a Dispatch Interval in the Pre-Dispatch Schedule Horizon; or
contains parameter values that deviate from the corresponding Standing Data values.

The ERA may request further information from the Market Participant about any of the reasons included in a Real-Time Market Submission under clauses 7.4.26 or 7.4.27.

7.4.26. Where a Market Participant makes a Real-Time Market Submission for a Registered Facility and Market Service for a Dispatch Interval in the Pre‑Dispatch Schedule Horizon (including by submitting a new Standing Real‑Time Market Submission for the Registered Facility and Market Service), the Market Participant must:

$a$ specify the reason for the revision in the subsequent Real-Time Market Submission, and

$b$ create and maintain adequate detailed records (that are capable of independent verification) of the reasons for submitting the subsequent Real-Time Market Submission, including details of any changed circumstances, the time at which the Market Participant became aware of those changed circumstances and the impact of those circumstances that gave rise to the subsequent Real-Time Market Submission.

Explanatory Note

Clause 7.4.27 requires a Market Participant to provide reasons in a Real-Time Market Submission for any differences between the parameters specified in the Real-Time Market Submission for maximum and minimum enablement and maximum upwards and downwards ramp rates, and the corresponding parameters as specified in the Registered Facility’s Standing Data where that submission is made inside the Pre-Dispatch Schedule Horizon.

7.4.27. Where a Real-Time Market Submission specifies an Enablement Minimum, Enablement Maximum, Low Breakpoint, High Breakpoint, Maximum Upwards Ramp Rate or Maximum Downwards Ramp Rate, that is different to the Standing Enablement Minimum, Standing Enablement Maximum, Standing Low Breakpoint, Standing High Breakpoint, Standing Maximum Upwards Ramp Rate or Standing Maximum Downwards Ramp Rate value, as applicable, specified in the Standing Data for the Registered Facility, the Market Participant must:

$a$ specify the reason for the difference in the Real-Time Market Submission, and

$b$ create and maintain adequate detailed records (that are capable of independent verification) of the reasons for the differences between the relevant values specified in the Real-Time Market Submission and the corresponding values specified in the Standing Data.

Explanatory Note

Clause 7.4.28 gives the ERA the power to ask for explanations where there is a change in the parameters in an earlier and subsequent Real-Time Market Submission for the same Dispatch Interval, or with the relevant parameters as specified in Standing Data for the Registered Facility.

7.4.28. Where a Market Participant makes a Real-Time Market Submission that meets the conditions specified in clauses 7.4.26 or 7.4.27, the Economic Regulation Authority may request the Market Participant to provide further information about the reasons provided under clauses 7.4.26(a) or 7.4.27(a) (as applicable), including any records created under clauses 7.4.26(b) or 7.4.27(b) (as applicable).

7.4.29. A Market Participant must respond to a request by the Economic Regulation Authority under clause 7.4.28 by the time specified in the request, which must not be less than five Business Days.

7.4.30. AEMO must determine and publish the Gate Closure on the WEM Website. In determining the Gate Closure, AEMO must take into account the extent to which the Gate Closure is, in its reasonable opinion, required to prevent a significant and quantifiable risk to AEMO maintaining Power System Security and Power System Reliability in accordance with Chapter 3.

7.4.31. The Gate Closure determined by AEMO in accordance with clause 7.4.30:

$a$ must be as close as possible to the start of the relevant Dispatch Interval, subject to any significant and quantifiable risk identified by AEMO under clause 7.4.30; and

$b$ must not be more than 15 minutes before the start of the relevant Dispatch Interval.

7.4.32. AEMO may, from time to time, but subject to clauses 7.4.30 and 7.4.31, revise the Gate Closure by:

$a$ publishing on the WEM Website the revised Gate Closure and the date and time from which the revised Gate Closure will take effect; and

$b$ issuing a Market Advisory noting that AEMO has revised the Gate Closure.

7.4.33. Where a revised Gate Closure is closer to the start of the Dispatch Interval than the existing Gate Closure, AEMO must give at least three months' notice of the revision.

7.4.34. Where AEMO revises the Gate Closure under clause 7.4.32, AEMO must publish a report on the WEM Website stating:

$a$ its reasons for revising the Gate Closure; and

$b$ its assessment of any change in quantifiable risks to Power System Security or Power System Reliability that may result from the revision.

Explanatory Note

Clause 7.4.35 allows Market Participants to update a Real-Time Market Submission within Gate Closure for (only) the reasons specified in the clause.

Clause 7.4.35 is amended to:

correct the reference to Gate Closure (which is a point in time relative to a Dispatch Interval);
include the need to comply with clause 7.6.31(a) for an Inflexible Facility in the list of valid reasons for a submission after Gate Closure; and
clarify which adjustments are applicable in each of the circumstances listed.

7.4.35. A Market Participant must not make a Real-Time Market Submission for a Dispatch Interval after Gate Closure for the Dispatch Interval, except where the Real-Time Market Submission is made for the sole purpose of:

$a$ adjusting the Unconstrained Injection Forecast or Unconstrained Withdrawal Forecast for a Semi-Scheduled Facility or Non-Scheduled Facility;

$b$ adjusting Available Capacity, In-Service Capacity and quantities in Price‑Quantity Pairs for a Registered Facility that has suffered a Forced Outage, to reflect the Registered Facility’s Remaining Available Capacity under that Forced Outage;

$c$ adjusting the Dispatch Inflexibility Profile of a Scheduled Facility or Semi‑Scheduled Facility to reflect a delay in starting the Facility; or

$d$ complying with clause 7.6.31(a) in respect of a Registered Facility that has become Inflexible.

Explanatory Note

Clause 7.4.36, which specifies the Real-Time Market Submissions that AEMO should use for scheduling and dispatch, is amended to refer to the new clauses that explain how the “current” Real-Time Market Submission for a Registered Facility, Market Service and Dispatch Interval is determined.

7.4.36. AEMO must use the most recent Real-Time Market Submissions (as determined in accordance with clauses 7.4.1A, 7.4.1B and 7.4.1C) in the scheduling and dispatch of Registered Facilities in accordance with this Chapter 7.

Explanatory Note

Clause 7.4.37:

restrict sthe application of the clause to Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads;
reflects that Real-Time Market Submissions may not need to be updated when reviewed;
removes clause 7.4.37(b) because its intent is achieved by clause 7.4.37(a); and
extends the list of exceptions in clause 7.4.37(c) (renumbered to clause 7.4.37(b)) to include compliance with clause 7.6.31(a) for a Facility that has become Inflexible.

7.4.37. A Market Participant, for a Scheduled Facility, Semi-Scheduled Facility or Interruptible Load:

$a$ is only required to review, and if necessary update, Real-Time Market Submissions for Dispatch Intervals outside the Pre-Dispatch Schedule Horizon once per day; and

$b$ is not required to review and update Real-Time Market Submissions for Dispatch Intervals for which Gate Closure has passed, except for events referred to in clauses 7.4.35(b), 7.4.35(c) or 7.4.35(d).

7.4.37A. A Market Participant is not required to review or revise a Real-Time Market Submission for a Non-Scheduled Facility except where the Market Participant:

$a$ is intending to take controlled action to vary the Injection or Withdrawal of the Non-Scheduled Facility; or

$b$ has revised the information used to develop the Real-Time Market Submission for the Non-Scheduled Facility,

for a Dispatch Interval in the Pre-Dispatch Schedule Horizon, in which case the Market Participant must make reasonable endeavours to update the Real-Time Market Submission to reflect the revised information.

Explanatory Note

Clauses 7.4.38 to 7.4.45 describes the information that is required to be specified in Real-Time Market Submissions.

Clause 7.4.38 is amended to clarify that the permitted combinations of Real-Time Market Submissions within an electronic submission are prescribed in the WEM Procedure.

Real-Time Market Submissions – Format

7.4.38. AEMO must document in a WEM Procedure the format and methodology to be followed by Market Participants for making Real-Time Market Submissions, including the options to submit multiple Real-Time Market Submissions to AEMO in a single electronic submission, any relevant minimum tranche size for offers, the maximum allowable number of Price-Quantity Pairs for a Dispatch Interval and any specific requirements for Registered Facilities that offer Essential System Services and not energy.

Explanatory Note

Clause 7.4.39 is amended to:

reflect that a Real-Time Market Submission is for a Registered Facility, Market Service and Dispatch Interval; and
clarify the requirements relating to the provision of reasons.

7.4.39. A Real-Time Market Submission must specify:

$a$ the Registered Facility;

$b$ the Market Service;

$c$ the Dispatch Interval;

$d$ the reason for revision of the Real-Time Market Submission, if required under clause 7.4.26(a);

$e$ the reason for any difference between the values provided in the Real‑Time Market Submission and the corresponding Standing Data values, if required under clause 7.4.27(a);

$f$ the information specified in clauses 7.4.40 to 7.4.42 as applicable; and

$g$ any other information specified in the WEM Procedure to be documented by AEMO under clause 7.4.38.

Explanatory Note

Clause 7.4.40 is amended to:

use consistent terminology for a Real-Time Market Submission for energy;
restructure clause 7.4.40(g) to distinguish the items that apply to each Price-Quantity Pair individually from the items that apply to the Price-Quantity Pairs as a group; and
remove the requirements specified in clauses 7.4.40(g)(iv) and 7.4.40(g)(v), due to the high associated IT costs; and
include the requirement to provide an Unconstrained Injection Forecast and Unconstrained Withdrawal Forecast for a Semi-Scheduled Facility or Non-Scheduled Facility.

7.4.40. A Real-Time Market Submission for energy must, in addition to the matters listed in clause 7.4.39, specify, as applicable:

$a$ the In-Service Capacity for Injection in MW;

$b$ the Available Capacity for Injection in MW;

$c$ the In-Service Capacity for Withdrawal in MW;

$d$ the Available Capacity for Withdrawal in MW;

$e$ the Maximum Upwards Ramp Rate in MW per minute;

$f$ the Maximum Downwards Ramp Rate in MW per minute;

$g$ up to the number of Price-Quantity Pairs specified in the WEM Procedure referred to in clause 7.4.38, where:

i. for each Price-Quantity Pair:

1. the price is to be stated in dollars and whole cents per MWh;

2. the quantity is to be identified as either Available Capacity or In-Service Capacity; and

3. if the quantity is classified as Available Capacity, the Start Decision Cutoff for the quantity is to be provided in minutes;

ii. the sum of all positive MW quantities is to equal the total of Available Capacity and In-Service Capacity for Injection; and

iii. the sum of all negative MW quantities is to equal the total of Available Capacity and In-Service Capacity for Withdrawal;

$h$ if the Registered Facility is Inflexible; and

$i$ for a Semi-Scheduled Facility or Non-Scheduled Facility:

i. the Unconstrained Injection Forecast; and

ii. the Unconstrained Withdrawal Forecast.

Explanatory Note

Clauses 7.4.41 and 7.4.42 are amended to clarify that Market Participants are not required to offer all of their accredited FCESS capacity in their Real-Time Market Submissions (except where an obligation exists under other clauses or the terms of a SESSM Award).

7.4.41. A Real-Time Market Submission for a Registered Facility to supply Regulation or Contingency Reserve must, in addition to the matters listed in clause 7.4.39, specify:

$a$ the total available quantity of Regulation or Contingency Reserve, where this quantity is less than or equal to the maximum accredited capacity for Regulation or Contingency Reserve for that Dispatch Interval;

$b$ the In-Service Capacity for the relevant Frequency Co-optimised Essential System Service;

$c$ the Available Capacity for the relevant Frequency Co-optimised Essential System Service;

$d$ the Enablement Minimum of the relevant Frequency Co-optimised Essential System Service;

$e$ the Low Breakpoint of the relevant Frequency Co-optimised Essential System Service;

$f$ the High Breakpoint of the relevant Frequency Co-optimised Essential System Service;

$g$ the Enablement Maximum of the relevant Frequency Co-optimised Essential System Service; and

$h$ a ranking of Price-Quantity Pairs with MW quantities summing to the total of Available Capacity and In-Service Capacity for the Frequency Co‑optimised Essential System Service where the prices are to be stated in dollars and whole cents per MW per hour.

7.4.42. A Real-Time Market Submission for a Registered Facility to supply RoCoF Control Service must, in addition to the matters listed in clause 7.4.39, specify:

$a$ the total available quantity of RoCoF Control Service where this value is less than or equal to the maximum accredited capacity for RoCoF Control Service for that Dispatch Interval;

$b$ the Enablement Minimum of the RoCoF Control Service;

$c$ the Low Breakpoint of the RoCoF Control Service;

$d$ the High Breakpoint of the RoCoF Control Service;

$e$ the Enablement Maximum of the RoCoF Control Service; and

$f$ a ranking of Price-Quantity Pairs with MWs quantities summing to the total of Available Capacity and In-Service Capacity for the RoCoF Control Service where the prices are to be stated in dollars and whole cents per MWs per hour.

Explanatory Note

A Market Participant may include a Dispatch Inflexibility Profile in a Real-Time Market Submission for a Registered Facility where it wants its Registered Facility to be available to be dispatched in real-time as a Fast Start Facility.

Clause 7.4.43 is amended to clarify that Dispatch Inflexibility Profiles are included in Real-Time Market Submissions for energy.

7.4.43. A Market Participant may include a Dispatch Inflexibility Profile in a Real-Time Market Submission for energy for a Fast Start Facility in accordance with clause 7.4.44.

7.4.44. A Dispatch Inflexibility Profile for a Fast Start Facility must contain the following parameters to indicate its MW capacity and time related Inflexibilities at the time it is included in the Real-Time Market Submission:

$a$ the time, T1, in minutes, that the Registered Facility requires following the receipt of a Dispatch Instruction for the Registered Facility to start varying its level of Injection or Withdrawal from 0 MW in accordance with the Dispatch Instruction;

$b$ the time, T2, in minutes, that the Registered Facility requires after T1 (as specified in clause 7.4.44(a)) to reach a specified minimum level of Injection or Withdrawal;

$c$ the time, T3, in minutes, that the Registered Facility requires to be operated at or beyond its minimum level of Injection or Withdrawal before the Registered Facility can be safely and securely returned to Injection or Withdrawal of zero;

$d$ the time, T4, in minutes, following the receipt of a Dispatch Instruction to return its Injection or Withdrawal from the minimum level specified in clause 7.4.44(b) to zero, that the Registered Facility requires to fully comply with the Dispatch Instruction; and

$e$ the quantity, in MW, of Injection or Withdrawal that the Registered Facility must be operated at or beyond during the period in clause 7.4.44(c).

7.4.45. For a Fast Start Facility:

$a$ T1, T2, T3 and T4 must all be equal to or greater than zero;

$b$ the sum of (T1 + T2) must be less than or equal to 30 minutes; and

$c$ the sum of (T1 + T2 + T3 + T4) must be less than 60 minutes.

Explanatory Note

Clauses 7.4.46 and 7.4.47 deal with the construction of Real-Time Market Submissions. Each Registered Facility will be able to make Real-Time Market Offers for Injection and Real-Time Market Bids for Withdrawal. Unlike under the current WEM Rules, Scheduled Facilities will need to make Real-Time Market Bids for Withdrawal (if it is metered by the same meter), and be held to compliance with the relevant Dispatch Instruction for it.

Registered Facilities will still be able to operate within their applicable Tolerance Range or Facility Tolerance Range. For example, a Facility with a Dispatch Instruction of 0 MW could make a Withdrawal up to the Tolerance Range or Facility Tolerance Range applicable to the Facility without being in breach of the relevant WEM Rules.

Real-Time Market Submissions – Construction

Explanatory Note

Clause 7.4.46 is amended to remove the reference to “sent out quantities” because the term is not applicable to Withdrawal and the measurement location for Injection and Withdrawal is covered in the definitions of these terms.

7.4.46. A Market Participant must ensure that a Real-Time Market Submission for a Registered Facility for energy specifies Price-Quantity Pairs for all Injection and Withdrawal for the Registered Facility where:

$a$ the negative quantities in Price-Quantity Pairs for energy represent bids for Withdrawal; and

$b$ the positive quantities in Price-Quantity Pairs for energy represent offers for Injection.

7.4.46A. A Market Participant is not required to specify Price-Quantity Pairs for Withdrawals in its Real-Time Market Submission, where the Real-Time Market Submission is made in respect of a Registered Facility containing an Intermittent Load.

7.4.47. The prices in Price-Quantity Pairs in a Real-Time Market Submission:

$a$ apply at the network connection point or Electrical Location, as applicable, for the Registered Facility;

$b$ must increase monotonically with an increase in the available quantity for each Market Service; and

$c$ for Withdrawal must be lower than the prices in Price-Quantity Pairs for Injection.

Explanatory Note

Clauses 7.4.48 and 7.4.49 deal with the validation process of Real-Time Market Submissions. Significantly, AEMO will reject the whole Real-Time Market Submission for one ‘non-conforming / non-compliant’ record, rather than accept a Real-Time Market Submission in part.

Clauses 7.4.48 and 7.4.49 are amended to:

clarify the processing rules for electronic submissions containing Real-Time Market Submissions;
remove the reference to clause 7.4.9 (which has been deleted); and
remove the reference to clause 7.4.35, which relates to submissions made after Gate Closure, because AEMO is unable to assess whether a submission meets the exception criteria as part of the submission validation process.

Real-Time Market Submissions - Validation of Dispatch Bids and Offers

7.4.48. On receipt of an electronic submission containing one or more Real-Time Market Submissions in accordance with this section 7.4, AEMO must as soon as practicable:

$a$ acknowledge receipt of the electronic submission to the submitting Market Participant; and

$b$ determine whether the Real-Time Market Submissions in the electronic submission comply with the following requirements, as applicable:

i. the content requirements in clauses 7.4.10(a), 7.4.39, 7.4.40, 7.4.41, 7.4.42, 7.4.44, 7.4.45, 7.4.47(b) and 7.4.47(c);

ii. the pricing requirements in clause 7.4.8;

iii. the quantity requirements in clause 7.4.11; and

iv. the timing requirements in clause 7.4.23.

7.4.49. Where AEMO:

$a$ determines that an electronic submission complies with the requirements in clause 7.4.48(b), AEMO must:

i. accept the Real-Time Market Submissions and notify the submitting Market Participant that the Real-Time Market Submissions have been accepted, and

ii. make available to the Market Participant the data contained in the Real-Time Market Submissions as they will be used by AEMO in the Central Dispatch Process, including Loss Factor Adjusted Prices and non-Loss Factor Adjusted Prices; or

$b$ determines that the electronic submission, or any part of it, does not comply with the requirements referred to in clause 7.4.48(b), AEMO must:

i. reject the electronic submission and notify the submitting Market Participant that it has been rejected, and

ii. provide details of the reasons the electronic submission was rejected.

Explanatory Note

Clauses 7.4.50 to 7.4.53 deal with processing Real-Time Market Submissions, including the arrangements with respect to Loss Factor adjusted prices in Real-Time Market Submissions and the ability for AEMO to make adjustments to certain inputs for use in the Dispatch Algorithm.

Real-Time Market Submissions – Processing

7.4.50. AEMO must convert the prices in a Real-Time Market Submission for energy into Loss Factor Adjusted Prices, and must use those Loss Factor Adjusted Prices in the Dispatch Algorithm.

7.4.51. Where a Loss Factor Adjusted Price determined in accordance with clause 7.4.50 is outside the relevant Energy Offer Cap, AEMO must use the relevant Energy Offer Cap for the Real-Time Market Submission in the Dispatch Algorithm.

7.4.51A. Where a price in a Real-Time Market Submission for a Frequency Co-optimised Essential System Service:

$a$ is greater than the relevant FCESS Offer Price Ceiling, AEMO must use the relevant FCESS Offer Price Ceiling in the Dispatch Algorithm; and

$b$ is less than zero, AEMO must use a price of zero in the Dispatch Algorithm.

7.4.52. Where AEMO determines, based on the information available to it at the relevant time, that the capability of a Registered Facility to provide an Essential System Service differs from the quantities and technical parameters specified in the most recently submitted Real-Time Market Submission for the Registered Facility for the relevant Dispatch Interval, AEMO may adjust the following inputs to reflect the information available to it at that time, for use in the Dispatch Algorithm:

$a$ Enablement Minimum;

$b$ Enablement Maximum;

$c$ Low Breakpoint; and

$d$ High Breakpoint.

7.4.52A. Where AEMO adjusts inputs under clause 7.4.52, AEMO must, as soon as practicable, make the adjusted inputs and the reasons for the adjustment available to the Market Participant.

7.4.53. AEMO must document in a WEM Procedure:

$a$ the information and processes, including the application of any formulae, AEMO will use in making a determination under clause 7.4.52; and

$b$ the circumstances in which AEMO will adjust the inputs specified in clause 7.4.52.

Real-Time Market Submissions – Standing Submissions

7.4.54. A Market Participant may submit Standing Real-Time Market Submissions for a Registered Facility and Market Service at any time before Gate Closure for the first Dispatch Interval to which the submissions apply.

7.4.55. The Standing Real-Time Market Submissions in an electronic submission to AEMO for a Registered Facility and Market Service must, in combination, uniquely specify the default Real-Time Market Submission to apply for each Dispatch Interval in a generic Trading Week.

7.4.56. An electronic submission containing Standing Real-Time Market Submissions must specify the first Dispatch Interval to which the submissions apply.

7.4.57. Subject to clause 7.4.55, a Market Participant may specify the type of Trading Day to which a Standing Real‑Time Market Submission applies as:

$a$ all Trading Days starting on a specific day of the week;

$b$ all Trading Days starting on a weekday;

$c$ all Trading Days starting on a weekend;

$d$ all Trading Days starting on a Business Day;

$e$ all Trading Days starting on a non-Business Day; or

$f$ all Trading Days.

7.4.57A. AEMO must document in a WEM Procedure the format and methodology to be followed by Market Participants for making Standing Real-Time Market Submissions, including the options to submit Standing Real-Time Market Submissions for multiple Registered Facilities and Market Services in a single electronic submission.

Explanatory Note

Clauses 7.4.58 and 7.4.59 are amended to:

clarify the processing rules for electronic submissions containing Standing Real-Time Market Submissions; and
make consequential changes to the list of validation requirements in clause 7.4.58(b).

7.4.58. On receipt of an electronic submission containing one or more Standing Real-Time Market Submissions, AEMO must, as soon as practicable:

$a$ acknowledge receipt of the electronic submission to the submitting Market Participant; and

$b$ determine whether the Standing Real-Time Market Submissions in the electronic submission comply with the following requirements:

i. the content requirements in clauses 7.4.55, 7.4.56 and 7.4.57;

ii. the timing requirement in clause 7.4.54; and

iii. for each Standing Real-Time Market Submission in the electronic submission, as applicable:

1. the content requirements in clauses 7.4.10(a), 7.4.39, 7.4.40, 7.4.41, 7.4.42, 7.4.44, 7.4.45, 7.4.47(b) and 7.4.47(c);

2. the pricing requirements in clause 7.4.8; and

3. the quantity requirements in clause 7.4.11.

7.4.59. Where AEMO:

$a$ determines that an electronic submission complies with the requirements in clause 7.4.58(b), AEMO must:

i. accept the Standing Real-Time Market Submissions and notify the submitting Market Participant that the Standing Real-Time Market Submissions have been accepted, and

ii. make available to the Market Participant the data contained in the Standing Real-Time Market Submissions as it will be used by AEMO in the Central Dispatch Process; or

$b$ determines that the electronic submission, or any part of it, does not comply with the requirements referred to in clause 7.4.58(b), AEMO must:

i. reject the electronic submission and notify the submitting Market Participant that it has been rejected, and

ii. provide details of the reasons the electronic submission was rejected.

7.4.59A. A Standing Real-Time Market Submission for a Registered Facility and Market Service that AEMO accepts under clause 7.4.59(a) replaces any previously accepted Standing Real-Time Market Submission for Dispatch Intervals from the Dispatch Interval specified in clause 7.4.56.

7.4.60. When AEMO uses a Standing Real-Time Market Submission in the Dispatch Algorithm, AEMO must:

$a$ subject to clause 7.4.60(b), convert the prices in a Standing Real-Time Market Submission for energy into Loss Factor Adjusted Prices, and use those Loss Factor Adjusted Prices in the Dispatch Algorithm;

$b$ where a Loss Factor Adjusted Price determined under clause 7.4.60(a) is outside the relevant Energy Offer Cap, use the relevant Energy Offer Cap in the Dispatch Algorithm;

$c$ where a price in a Standing Real-Time Market Submission for a Frequency Co-optimised Essential System Service is greater than the relevant FCESS Offer Price Ceiling, use the relevant FCESS Offer Price Ceiling in the Dispatch Algorithm; and

$d$ where a price in a Standing Real-Time Market Submission for a Frequency Co-optimised Essential System Service is less than zero, use a price of zero in the Dispatch Algorithm.

7.4.61. It is the responsibility of each Market Participant to check that the data contained in its Standing Real-Time Market Submissions as it will be used by AEMO in the Central Dispatch Process is correct.

Explanatory Note

Clause 7.4.62 has been placed under a new sub-section heading because the contents of the clause relate to Real-Time Market Submissions as well as Standing Real-Time Market Submissions.

Clause 7.4.62 is also amended to remove the requirement for AEMO to document the types of day that can be nominated in a Standing Real-Time Market Submission in a WEM Procedure, because this is now specified in clause 7.4.57.

Real-Time Market Submissions and Standing Real-Time Market Submissions – Process Documentation

7.4.62. AEMO must document in a WEM Procedure the processes it must follow when:

$a$ acknowledging receipt of a Real-Time Market Submission under clause 7.4.48(a) or a Standing Real-Time Market Submission under clause 7.4.58(a);

$b$ validating a Real-Time Market Submission in accordance with clause 7.4.48(b) or a Standing Real-Time Market Submission in accordance with clause 7.4.58(b); and

$c$ accepting or rejecting a Real-Time Market Submission in accordance with clause 7.4.49 or a Standing Real-Time Market Submission in accordance with clause 7.4.59.

Explanatory Note

Feedback from AEMO’s implementation program identified a number of issues with the proposal to include Demand Side Programmes in the Dispatch Algorithm, including:

the potential for inaccurate identification of potential Demand Side Programme dispatch in the forward Market Schedules;
issues with the proposed tie-breaking approach; and
issues relating to the need to take into account the specific restrictions associated with the dispatch of Demand Side Programmes, e.g. notice periods, hours available for dispatch, maximum hours of dispatch per year, etc).

Due to these issues, Demand Side Programmes will not be dispatched using the Dispatch Algorithm. Instead, an alternative approach has been developed for the dispatch of these Facilities.

A key component of this approach is the requirement for Market Participants to provide DSP Withdrawal Profile Submissions that specify two forecast quantities for each Dispatch Interval:

a DSP Unconstrained Withdrawal Quantity, which is the Market Participant’s estimate of the average MW consumption of its Demand Side Programme in the Dispatch Interval assuming that the Demand Side Programme is not affected by any Dispatch Instruction or Reserve Capacity Test; and
a DSP Constrained Withdrawal Quantity, which the DSP Unconstrained Withdrawal Quantity adjusted to take into account the impact of any impending dispatch or Reserve Capacity Tests about which the Market Participant has been advised.

The two values are expected to be identical for most Dispatch Intervals.

New section 7.4A sets out the obligations with respect to DSP Withdrawal Profile Submissions. The clauses below are structured similarly to the clauses in section 7.4 (Real-Time Market Submissions), but are included in a separate section to reflect that these obligations apply only to Demand Side Programmes.

7.4A. DSP Withdrawal Profile Submissions

7.4A.1. A Market Participant must ensure that it has made a DSP Withdrawal Profile Submission or Standing DSP Withdrawal Profile Submission in accordance with this section 7.4A for each Dispatch Interval in the Week-Ahead Schedule Horizon for each of its Demand Side Programmes.

7.4A.2. If AEMO has not accepted a DSP Withdrawal Profile Submission for a Demand Side Programme and Dispatch Interval under clause 7.4A.15(a), but has accepted an applicable Standing DSP Withdrawal Profile Submission, then the Standing DSP Withdrawal Profile Submission is deemed to be the DSP Withdrawal Profile Submission for the Demand Side Programme and Dispatch Interval.

7.4A.3. A DSP Withdrawal Profile Submission for a Demand Side Programme and Dispatch Interval that AEMO accepts under clause 7.4A.15(a) replaces any previously accepted DSP Withdrawal Profile Submission for, and has effect in relation to, the Demand Side Programme and Dispatch Interval.

7.4A.4. If:

$a$ AEMO has not yet accepted a DSP Withdrawal Profile Submission for a Demand Side Programme and Dispatch Interval under clause 7.4A.15(a); and

$b$ AEMO accepts a Standing DSP Withdrawal Profile Submission for the Demand Side Programme that is applicable to the Dispatch Interval,

then the Standing DSP Withdrawal Profile Submission replaces any previously accepted Standing DSP Withdrawal Profile Submission as the deemed DSP Withdrawal Profile Submission for the Demand Side Programme and Dispatch Interval.

Explanatory Note

Clauses 7.4A.5 to 7.4A.8 set out the requirements for a Market Participant to review and update the DSP Withdrawal Profile Submissions for its Demand Side Programme when AEMO:

indicates that the Demand Side Programme may be dispatched over a specific period in a Market Advisory;
issues a Dispatch Instruction to the Demand Side Programme to curtail its consumption;
issues a Dispatch Instruction to the Demand Side Programme to end a period of curtailment; or
issues a notification of a Reserve Capacity Test for the Demand Side Programme.

Clause 7.4A.9 requires the Market Participant, if it has been requested to revise its DSP Withdrawal Profile Submissions for a period, to make reasonable endeavours to ensure that the DSP Unconstrained Withdrawal Quantities and DSP Constrained Withdrawal Quantities remain as accurate as possible for that period.

7.4A.5. If AEMO identifies a Demand Side Programme in a Market Advisory under clause 7.11.6(cA)(i), then the relevant Market Participant must:

$a$ as soon as practicable review, and if necessary update, the DSP Withdrawal Profile Submissions for the Demand Side Programme for, subject to clause 7.4A.9A, each future Dispatch Interval before the end of the Trading Day in which the period specified under clause 7.11.6(cA)(ii) falls; and

$b$ for the purposes of determining DSP Constrained Withdrawal Quantities, assume the Demand Side Programme will be subject to Dispatch Instructions that curtail the Withdrawal of the Demand Side Programme by the maximum quantity consistent with its Reserve Capacity Obligations for the period specified under clause 7.11.6(cA)(ii).

7.4A.6. If AEMO issues a Dispatch Instruction with a non-zero MW quantity to a Demand Side Programme under clause 7.6.15, then the Market Participant must:

$a$ as soon as practicable and no later than one hour before the Dispatch Interval from which the Dispatch Instruction applies, review, and if necessary update, the DSP Withdrawal Profile Submissions for the Demand Side Programme for, subject to clause 7.4A.9A, each future Dispatch Interval before the end of the Trading Day in which the Dispatch Interval specified under clause 7.6.11A(c) falls; and

$b$ for the purposes of determining the applicable DSP Constrained Withdrawal Quantities, take into account the timeframes and quantities in the Dispatch Instructions that have been issued to the Demand Side Programme and assume that AEMO will issue a Dispatch Instruction with a zero MW quantity that will apply from the Dispatch Interval specified under clause 7.6.11A(e).

7.4A.7. If AEMO issues a Dispatch Instruction with a zero MW quantity to a Demand Side Programme under clause 7.6.15, then the Market Participant must:

$a$ as soon as practicable and no later than one hour before the Dispatch Interval from which the Dispatch Instruction applies, review, and if necessary update, the DSP Withdrawal Profile Submissions for the Demand Side Programme for, subject to clause 7.4A.9A, each future Dispatch Interval in the Trading Day in which the Dispatch Interval specified under clause 7.6.11A(c) falls; and

$b$ for the purposes of determining the applicable DSP Constrained Withdrawal Quantities, take into account the time from which the Dispatch Instruction will apply.

7.4A.8. If a Market Participant receives a notification relating to a Reserve Capacity Test of a Demand Side Programme under clause 4.25.9(h), the Market Participant must:

$a$ as soon as practicable and no later than one hour before the Reserve Capacity Test is due to commence, review and update the DSP Withdrawal Profile Submissions for the Demand Side Programme for, subject to clause 7.4A.9A, each future Dispatch Interval in the Trading Day in which Reserve Capacity Test will be conducted; and

$b$ take the information provided in the notification under clause 4.25.9(h) into account in determining the relevant DSP Constrained Withdrawal Quantities.

7.4A.9. A Market Participant must make reasonable endeavours to ensure that when any of the conditions specified in clauses 7.4A.5, 7.4A.6, 7.4A.7 or 7.4A.8 apply, the DSP Unconstrained Withdrawal Quantities and DSP Constrained Withdrawal Quantities in its DSP Withdrawal Profile Submissions for the Demand Side Programme accurately reflect the Market Participant’s reasonable expectation of the Withdrawal of the Demand Side Programme during the applicable Dispatch Intervals under the required assumptions.

7.4A.9A. For the purposes of updating DSP Withdrawal Profile Submissions under clauses 7.4A.5, 7.4A.6, 7.4A.7 or 7.4A.8, a Market Participant must not include a future Dispatch Interval in its updated DSP Withdrawal Profile Submissions, where the Market Participant reasonably determines that despite its best endeavours, its updated DSP Withdrawal Profile Submissions for the Dispatch Interval will not be received by AEMO before the start of the Dispatch Interval.

DSP Withdrawal Profile Submissions – Timing

7.4A.10. A Market Participant may submit a DSP Withdrawal Profile Submission for a Dispatch Interval at any time:

$a$ on or after the Real-Time Market Submission Acceptance Horizon for the Dispatch Interval; and

$b$ before the start of the Dispatch Interval.

7.4A.11. AEMO must use the most recent DSP Withdrawal Profile Submission (as determined in accordance with clauses 7.4A.2, 7.4A.3 and 7.4A.4) in the scheduling and dispatch of Demand Side Programmes in accordance with this Chapter 7.

Explanatory Note

Clauses 7.4A.12 to 7.4A.15, which set out the format and validation requirements for DSP Withdrawal Profile Subsmissions, are consistent with the corresponding provisions for Real-Time Market Submissions.

DSP Withdrawal Profile Submissions – Format

7.4A.12. AEMO must document in a WEM Procedure the format and methodology to be followed by Market Participants for making DSP Withdrawal Profile Submissions, including the options to submit multiple DSP Withdrawal Profile Submissions to AEMO in a single electronic submission.

7.4A.13. A DSP Withdrawal Profile must specify:

$a$ the Demand Side Programme;

$b$ the Dispatch Interval;

$c$ a DSP Unconstrained Withdrawal Quantity;

$d$ a DSP Constrained Withdrawal Quantity; and

$e$ any other information specified in the WEM Procedure to be documented by AEMO under clause 7.4A.12.

DSP Withdrawal Profile Submissions – Validation

7.4A.14. On receipt of an electronic submission containing one or more DSP Withdrawal Profile Submissions in accordance with this section 7.4A, AEMO must as soon as practicable:

$a$ acknowledge receipt of the electronic submission to the submitting Market Participant; and

$b$ determine whether the DSP Withdrawal Profile Submissions in the electronic submission comply with the following requirements, as applicable:

i. the content requirements in clause 7.4A.13; and

ii. the timing requirements in clause 7.4A.10.

7.4A.15. Where AEMO:

$a$ determines that an electronic submission complies with the requirements in clause 7.4A.14(b), AEMO must accept the DSP Withdrawal Profile Submissions and notify the submitting Market Participant that the DSP Withdrawal Profile Submissions have been accepted, or

$b$ determines that the electronic submission, or any part of it, does not comply with the requirements referred to in clause 7.4A.14(b), AEMO must:

i. reject the electronic submission and notify the submitting Market Participant that it has been rejected, and

ii. provide details of the reasons the electronic submission was rejected.

Explanatory Note

The arrangements for Standing DSP Withdrawal Profile Submissions are the same as those used for Standing Real-Time Market Submissions, except that the deadline for the submissions is two hours before the first Dispatch Interval to which the submissions apply (instead of Gate Closure).

The process documentation requirements for DSP Withdrawal Profile Submissions and Standing DSP Withdrawal Profile Submissions are also similar to the requirements for Real-Time Market Submissions and Standing Real-Time Market Submissions.

DSP Withdrawal Profile Submissions – Standing Submissions

7.4A.16. A Market Participant may submit Standing DSP Withdrawal Profile Submissions for a Demand Side Programme at any time up to two hours before the first Dispatch Interval to which the submissions apply.

7.4A.17. The Standing DSP Withdrawal Profile Submissions in an electronic submission to AEMO for a Demand Side Programme must, in combination, uniquely specify the default DSP Withdrawal Profile Submission to apply for each Dispatch Interval in a generic Trading Week.

7.4A.18. An electronic submission containing Standing DSP Withdrawal Profile Submissions must specify the first Dispatch Interval to which the submissions apply.

7.4A.19. Subject to clause 7.4A.17, a Market Participant may specify the type of Trading Day to which a Standing DSP Withdrawal Profile Submission applies as:

$a$ all Trading Days starting on a specific day of the week;

$b$ all Trading Days starting on a weekday;

$c$ all Trading Days starting on a weekend;

$d$ all Trading Days starting on a Business Day;

$e$ all Trading Days starting on a non-Business Day; or

$f$ all Trading Days.

7.4A.20. AEMO must document in a WEM Procedure the format and methodology to be followed by Market Participants for making Standing DSP Withdrawal Profile Submissions, including the options to submit Standing DSP Withdrawal Profile Submissions for multiple Demand Side Programmes in a single electronic submission.

7.4A.21. On receipt of an electronic submission containing one or more Standing DSP Withdrawal Profile Submissions, AEMO must, as soon as practicable:

$a$ acknowledge receipt of the electronic submission to the submitting Market Participant; and

$b$ determine whether the Standing DSP Withdrawal Profile Submissions in the electronic submission comply with the following requirements:

i. the content requirements in clauses 7.4A.17, 7.4A.18 and 7.4A.19;

ii. the timing requirement in clause 7.4A.16; and

iii. for each Standing DSP Withdrawal Profile Submission in the electronic submission, the content requirements in clause 7.4A.13.

7.4A.22. Where AEMO:

$a$ determines that an electronic submission complies with the requirements in clause 7.4A.21(b), AEMO must accept the Standing DSP Withdrawal Profile Submissions and notify the submitting Market Participant that the Standing DSP Withdrawal Profile Submissions have been accepted; or

$b$ determines that the electronic submission, or any part of it, does not comply with the requirements referred to in clause 7.4A.21(b), AEMO must:

i. reject the electronic submission and notify the submitting Market Participant that it has been rejected, and

ii. provide details of the reasons the electronic submission was rejected.

7.4A.23. A Standing DSP Withdrawal Profile Submission for a Demand Side Programme that AEMO accepts under clause 7.4A.22(a) replaces any previously accepted Standing DSP Withdrawal Profile Submission for Dispatch Intervals from the Dispatch Interval specified in clause 7.4A.18.

DSP Withdrawal Profile Submissions and Standing DSP Withdrawal Profile Submissions – Process Documentation

7.4A.24. AEMO must document in a WEM Procedure the processes it must follow when:

$a$ acknowledging receipt of a DSP Withdrawal Profile Submission under clause 7.4A.14(a) or a Standing DSP Withdrawal Profile Submission under clause 7.4A.21(a);

$b$ validating a DSP Withdrawal Profile Submission in accordance with clause 7.4A.14(b) or a Standing DSP Withdrawal Profile Submission in accordance with clause 7.4A.21(b); and

$c$ accepting or rejecting a DSP Withdrawal Profile Submission in accordance with clause 7.4A.15 or a Standing DSP Withdrawal Profile Submission in accordance with clause 7.4A.22.

Explanatory Note

Clauses 7.5.1 to 7.5.4 deal with the Dispatch Algorithm to be used by AEMO for the scheduling and dispatch of energy and ESS.

This section ties into the Constraints Framework, and deals with AEMO’s selection of Constraint Equations and Constraint Sets for inclusion in the Dispatch Algorithm, but not the formulation of constraints, unless there is no appropriate Constraint Equation already in the Constraints Library. AEMO’s obligations with respect to formulating Constraint Equations are set out in section 2.27A.

7.5. Dispatch Algorithm

Network Constraints

7.5.1. For each Dispatch Interval:

$a$ AEMO must reasonably determine, based on the latest information available to it, whether a Network Constraint has the potential to affect dispatch in the Dispatch Interval; and

$b$ for each Network Constraint identified by AEMO under clause 7.5.1(a), AEMO must select one or more Constraint Equations or Constraint Sets to use in the Dispatch Algorithm for the Dispatch Interval to address the Network Constraints identified.

7.5.2. Without limiting AEMO’s obligations under clause 7.5.1, AEMO must use Fully Co-Optimised Network Constraint Equations to reflect the Network Constraints identified under clause 7.5.1(a) unless, in AEMO’s reasonable opinion:

$a$ a Fully Co-Optimised Network Constraint Equation for the Network Constraint that affects, or is likely to affect, dispatch in the Dispatch Interval is not appropriate;

$b$ an Alternative Network Constraint Equation is available to better address the Network Constraint that affects, or is likely to affect, dispatch in the Dispatch Interval; and

$c$ if the Alternative Network Constraint Equation is used, AEMO will continue to meet its obligations under section 7.2,

in which case, AEMO may use the Alternative Network Constraint Equation in the Dispatch Algorithm for the expected duration of the relevant Network Constraint.

7.5.3. If the Constraints Library does not contain a Constraint Equation or Constraint Set that accurately reflects the Network Constraint identified under clause 7.5.1, then without limiting AEMO’s obligations to formulate Constraint Equations under section 2.27A, AEMO must formulate a new Constraint Equation or Constraint Set for use in the Dispatch Algorithm for the Network Constraint and update the Constraints Library in accordance with clause 2.27A.7.

7.5.4. AEMO must document in a WEM Procedure:

$a$ the process to be used by AEMO for selecting, applying, invoking and revoking Constraint Equations or Constraint Sets in response to Network Constraints for use in the Dispatch Algorithm; and

$b$ the circumstances in which AEMO will use Fully Co-optimised Network Constraint Equations and Alternative Network Constraint Equations in the Dispatch Algorithm.

Essential System Services Constraints

7.5.5. AEMO must include Constraint Equations for the dispatch of Essential System Services in the Dispatch Algorithm.

Explanatory Note

Clause 7.5.6 is intended to apply to Regulation Raise, Regulation Lower and Contingency Reserve Lower. The requirements for these services will be set outside the Dispatch Algorithm, and are necessary inputs to determining whether security standards are being met, and feeding into the RoCoF Control Service requirement.

7.5.6. Where the WEM Procedure referred to in clause 3.11.7 provides that the quantity of a Frequency Co-optimised Essential System Service is to be determined outside the Central Dispatch Process, AEMO must include Constraint Equations in the Dispatch Algorithm that, subject to clause 7.4.5(b), ensure the exogenously determined quantity of that Frequency Co-optimised Essential System Service is procured from the Real-Time Market.

Explanatory Note

Clause 7.5.7 is intended to apply to Contingency Reserve Raise and RoCoF Control Service. The requirements for these services will be set based on the lowest cost combination of facilities, including limiting the dispatch of facilities to reduce the requirement.

7.5.7. Where the WEM Procedure referred to in clause 3.11.7 provides that the quantity of a Frequency Co-optimised Essential System Service is dependent on factors within the Central Dispatch Process, AEMO must include Constraint Equations in the Dispatch Algorithm that, subject to clauses 3.12.2 and 7.2.4(e), ensure that a sufficient quantity of that Frequency Co-optimised Essential System Service is procured to meet the Essential System Service Standards.

Explanatory Note

Clause 7.5.8 provides a head of power for AEMO to undertake pre-processing so that the Dispatch Algorithm will only include Real-Time Market Offers for the supply of FCESS for Registered Facilities operating between Enablement Limits.

7.5.8. Where a Real-Time Market Submission for a Registered Facility specifies non-zero quantities in its Price-Quantity Pairs for any Frequency Co-optimised Essential System Service, then:

$a$ if the Registered Facility is operating between its Enablement Limits at the beginning of a Dispatch Interval or a Pre-Dispatch Interval, AEMO may, in accordance with the WEM Procedure referred to in clause 7.2.5, include Constraint Equations in the Dispatch Algorithm to ensure the Energy Dispatch Target for that Registered Facility will not be less than the Minimum Enablement Limit, and not more than the Maximum Enablement Limit; or

$b$ if the Registered Facility is not operating between its Enablement Limits at the beginning of a Dispatch Interval or a Pre-Dispatch Interval, AEMO may, in accordance with the WEM Procedure referred to in clause 7.2.5, exclude the Real-Time Market Offers to provide any Frequency Co‑optimised Essential System Service specified in the Real-Time Market Submission for the Registered Facility from the Dispatch Algorithm.

Explanatory Note

Clause 7.5.9 relates to the requirements for AEMO to include Constraint Equations that involve Electric Storage Resources in the Dispatch Algorithm.

Electric Storage Constraints will allow more efficient use of storage resources by including the relevant constraints in the Dispatch Algorithm, instead of requiring the relevant Market Participants to frequently adjust their Real-Time Market Offers for their storage resources. This ‘opt-in’ process is aimed at pure storage resources.

Storage Constraints

7.5.9. For a Scheduled Facility that comprises only Electric Storage Resources, AEMO may include Constraint Equations relating to restrictions on the simultaneous dispatch of energy and Frequency Co-optimised Essential System Services, to ensure that Dispatch Targets and Essential System Service Enablement Quantities for the Scheduled Facility are able to be achieved based on the Charge Level, storage capacity, Injection capability and Withdrawal capability for the Scheduled Facility, accounting for relevant losses in the charging or discharging process.

Explanatory Note

The registration provisions will include a clause that allows Market Participants to designate whether they want Energy Storage Constraints (to be developed by AEMO) to apply to their facility.

7.5.10. For Registered Facilities which the Market Participant notified AEMO that operation of the Registered Facility is subject to Energy Storage Constraints, AEMO must include Constraint Equations relating to restrictions on the simultaneous dispatch of energy and Frequency Co-optimised Essential System Service, to ensure that Dispatch Targets and Essential System Service Enablement Quantities for the Registered Facility are able to be achieved based on the Charge Level, storage capacity, Injection capability and Withdrawal capability for the Scheduled Facility, accounting for relevant losses in the charging or discharging process.

7.5.10A. Where a Market Participant notifies AEMO that operation of a Registered Facility is not subject to Energy Storage Constraints, AEMO must not include Constraint Equations in the Dispatch Algorithm for that Facility under clause 7.5.10.

Dynamic parameters

7.5.11. AEMO must determine the Contingency Raise Offset and Contingency Lower Offset for each Dispatch Interval and Pre-Dispatch Interval of each Market Schedule and in making a determination AEMO must have regard to:

$a$ System Inertia;

$b$ Load Relief;

$c$ Droop Response expected from synchronised Registered Facilities;

$d$ the size of the Largest Credible Supply Contingency;

$e$ the size of the Largest Credible Load Contingency; and

$f$ any other relevant factors specified in the WEM Procedure referred to in clause 7.2.5.

7.5.12. AEMO must determine the Minimum RoCoF Control Requirement, the Additional RoCoF Control Requirement and the RoCoF Control Requirement for each Dispatch Interval and Pre-Dispatch Interval of each Market Schedule and in making a determination AEMO must have regard to:

$a$ Facility Performance Factors;

$b$ System Inertia from sources other than Registered Facilities;

$c$ the size of the Largest Credible Supply Contingency;

$d$ Contingency Raise Offset;

$e$ Contingency Lower Offset; and

$f$ any other relevant factors specified in the WEM Procedure referred to in clause 7.2.5.

7.5.13. AEMO must determine a Facility Performance Factor for Contingency Reserve Raise and Contingency Reserve Lower for each Registered Facility that is accredited, in accordance with section 2.34A, to provide that Essential System Service for each Dispatch Interval and Pre-Dispatch Interval of each Market Schedule and in making a determination AEMO must have regard to:

$a$ Facility Speed Factors;

$b$ System Inertia;

$c$ the size of the Largest Credible Supply Contingency;

$d$ the size of the Largest Credible Load Contingency; and

$e$ any other relevant factors specified in the WEM Procedure referred to in clause 7.2.5.

7.5.14. AEMO must determine and publish on the WEM Website the RoCoF Upper Limit at least annually.

7.6. Dispatch

Explanatory Note

Clauses 7.6.1 to 7.6.22 deal with the Dispatch of Facilities in the Real-Time Market via Dispatch Instructions determined by the Dispatch Algorithm.

Clauses 7.6.1 and 7.6.2 are amended to reflect that only Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads are dispatched by WEMDE using the Dispatch Algorithm.

Dispatch Instructions

7.6.1. AEMO must centrally dispatch Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads based on their Real-Time Market Bids and Real-Time Market Offers using the Dispatch Algorithm.

7.6.2. AEMO must use the Dispatch Algorithm to set Dispatch Targets, Dispatch Caps and Essential System Service Enablement Quantities for each Scheduled Facility, Semi-Scheduled Facility and Interruptible Load for each Dispatch Interval.

7.6.3. AEMO must document in a WEM Procedure the processes to be followed by AEMO and Market Participants for the dispatch of Registered Facilities where the Dispatch Algorithm is not able to be successfully run for a Dispatch Interval, including:

$a$ where a previous Market Schedule will be used as the basis for issuing Dispatch Instructions; and

$b$ where a previous Market Schedule will not be used as the basis for issuing Dispatch Instructions, the basis for dispatch and issuing Dispatch Instructions in those circumstances.

7.6.4. AEMO must use the Central Dispatch Process to set:

$a$ the Market Clearing Prices for each Dispatch Interval in accordance with sections 7.11A, 7.11B and 7.11C; and

$b$ the Reference Trading Prices for each Trading Interval in accordance with clause 7.11A.1(b).

Explanatory Note

The phrase “in respect of a Dispatch Interval” has been removed from this general description of a Dispatch Instruction because Dispatch Instructions are no longer proposed to be issued for each Dispatch Interval to Demand Side Programmes. The clauses detailing the contents of Dispatch Instructions contain the required granularity details, so they do not need to be included in this clause.

7.6.5. A Dispatch Instruction is an instruction issued by AEMO to a Market Participant in respect of a Registered Facility, directing the Market Participant to:

$a$ vary the Injection or Withdrawal of the Registered Facility; or

$b$ enable the Registered Facility to provide a quantity of a Frequency Co-optimised Essential System Service.

Explanatory Note

Clause 7.6.5A allows AEMO to dispatch a Demand Side Programme to maintain Power System Security or Power System Reliability. This may be required in the event of a capacity shortfall or other low reserve condition, to conserve fuel during a major fuel shortfall or to relieve a security constraint.

Clause 7.6.5B sets out the principles AEMO must follow in determining which Demand Side Programmes should be dispatched, and for how long and what quantities the Facilities should be dispatched.

Clause 7.6.5C requires AEMO to document in a WEM Procedure the processes it will use to decide that the dispatch of Demand Side Programmes is required and to select Demand Side Programmes for dispatch.

7.6.5A. AEMO may issue Dispatch Instructions to a Demand Side Programme where AEMO reasonably considers that the dispatch of a Demand Side Programme is required to restore or maintain Power System Security or Power System Reliability.

7.6.5B. AEMO must issue Dispatch Instructions to Demand Side Programmes in accordance with the following principles:

$a$ AEMO must not issue Dispatch Instructions to a Demand Side Programme that restrict the absolute value of Withdrawal below the Facility’s Relevant Level by more than the Facility’s Reserve Capacity Obligation Quantity in a Dispatch Interval, except with the prior agreement of the Market Participant; and

$b$ when selecting Demand Side Programmes for dispatch to meet a potential energy shortfall, AEMO must:

i. take into account Market Schedules and any information provided by Market Participants in response to a Market Advisory issued under clause 7.11.5(gA) for the relevant period;

ii. avoid the dispatch of Demand Side Programmes beyond the extent that AEMO considers may reasonably be necessary to restore or maintain Power System Security and Power System Reliability;

iii. where a Demand Side Programme has an Associated Load which is also an Associated Load of an Interruptible Load, and that Interruptible Load is expected to provide an Essential System Service during the relevant period, prefer dispatch of other Demand Side Programmes; and

iv. only discriminate between Demand Side Programmes based on response time and availability, except where required under clause 7.6.5B(b)(iii).

7.6.5C. AEMO must document in a WEM Procedure:

$a$ how AEMO will determine that the dispatch of Demand Side Programmes under clause 7.6.5A may be required; and

$b$ the process that AEMO will use to select Demand Side Programmes for dispatch, which must be consistent with the principles specified in clause 7.6.5B.

7.6.6. AEMO is not required to issue a Dispatch Instruction for Automatic Generator Control movements where:

$a$ AEMO is adjusting the provision of Regulation within the quantity of Regulation enabled;

$b$ AEMO has direct control of a Registered Facility under clause 7.6.30 and the adjustments relate to implementation of a previously recorded Dispatch Instruction; or

$c$ the Facility is providing a System Restart Service.

Explanatory Note

Clause 7.6.7 allows AEMO to issue a direction to a Network Operator to support the operation of Central Dispatch Process. For example, adjusting an open point on the network or adjusting network voltage.

7.6.7. AEMO may direct a Network Operator to do, or not do, an act, matter or thing, if it reasonably determines the act, matter or thing is required to support or enable AEMO’s operation of the Central Dispatch Process.

7.6.7A. A Network Operator is not required to comply with a direction referred to in clause 7.6.7 if such compliance would endanger the safety of any person, damage equipment, or breach any applicable law.

Explanatory Note

Clause 7.6.8 sets out the information AEMO is required to include in a Dispatch Instruction.

Clause 7.6.8 is amended to:

restrict the clause to Dispatch Instructions for Scheduled Facilities, Semi-Scheduled Facilities and Interruptible Loads (Dispatch Instructions for Demand Side Programmes are covered in new clause 7.6.11A);
clarify what is included in Dispatch Instructions for the different Facility Classes; and
clarify that the quantities referred to in clause 7.6.8(d)(iii) are not the actual Dispatch Targets or Dispatch Caps for the Facility (which are sent out values) but their “as‑generated” equivalents.

7.6.8. For each Dispatch Instruction for a Scheduled Facility, Semi-Scheduled Facility or Interruptible Load, AEMO must record:

$a$ details of the Registered Facility to which the Dispatch Instruction relates;

$b$ the time the Dispatch Instruction was issued;

$c$ the Dispatch Interval to which the Dispatch Instruction applies;

$d$ for a Scheduled Facility or Semi-Scheduled Facility:

i. the Dispatch Target or Dispatch Cap for the Dispatch Interval, as applicable, under clause 7.6.10 or 7.6.11;

ii. where the Registered Facility is a Semi-Scheduled Facility, the Dispatch Forecast for the Dispatch Interval;

iii. where AEMO has agreed to process Dispatch Targets or Dispatch Caps for the Registered Facility on an as-generated basis, the equivalent as-generated values for the Dispatch Target, Dispatch Cap or Dispatch Forecast as applicable; and

iv. Essential System Service Enablement Quantities; and

$e$ for an Interruptible Load:

i. Essential System Service Enablement Quantities.

7.6.8A. AEMO may record, for a Dispatch Instruction to a Scheduled Facility or Semi-Scheduled Facility, the ramp rate to be maintained by the Registered Facility until the Dispatch Target is reached, which must not exceed the Maximum Upwards Ramp Rate or the Maximum Downwards Ramp Rate of the Registered Facility, as applicable.

7.6.9. At the same time as, or as soon as practicable after, AEMO issues a Dispatch Instruction for a Registered Facility, AEMO must make the information recorded in accordance with clauses 7.6.8 or 7.6.11A available to the Market Participant for the Registered Facility.

Explanatory Note

Scheduled Facilities will always get a Dispatch Target which must be met within the Facility’s relevant dispatch tolerance and subject to other service activation (e.g. Regulation).

Semi-Scheduled Facilities will receive:

a Dispatch Cap (which must not be exceeded beyond the Facility’s relevant dispatch tolerance); or
if the Facility has been cleared to provide an Essential System Service, a Dispatch Target (which must be met within the Facility’s relevant dispatch tolerance).

In normal operations, the Dispatch Cap will be the Facility’s nameplate capacity, but will be less where the Facility has been cleared for only part of its capacity due to a tiered offer structure or a Constraint.

It is noted that as currently drafted clause 7.6.11 may restrict how a hybrid facility participates in ESS provision. The ETIU and AEMO are exploring the possibility of allowing Market Participants to provide the ESS response from a component of the Registered Facility, rather than the Registered Facility as a whole at the sent-out point. Further amendments to clause 7.6.11 may be required to reflect that work.

7.6.10. Each Dispatch Instruction for a Scheduled Facility must include a Dispatch Target.

7.6.11. Each Dispatch Instruction for a Semi-Scheduled Facility must include:

$a$ a Dispatch Cap; or

$b$ a Dispatch Target, where the Registered Facility has a non-zero Essential System Service Enablement Quantity for Contingency Reserve or Regulation.

Explanatory Note

Clause 7.6.11A reflects the differences between Dispatch Instructions for Demand Side Programmes and the Dispatch Instructions that are issued by the Dispatch Algorithm for other Facility Classes. These include the following:

Dispatch Instructions for Demand Side Programmes are issued in accordance with the required notice period for the Facility (usually two hours);
a Dispatch Instruction is usually only issued to a Demand Side Programme when a change is required to its consumption, whereas Dispatch Instructions are issued to other Facilities every five minutes;
the start time for a Demand Side Programme (i.e. the time from which the Dispatch Instruction applies) must fall on a Trading Interval boundary, to support the relevant settlement calculations;
the meaning of a Dispatch Instruction is different for Demand Side Programmes:
- a non-zero MW quantity means that the consumption of the Demand Side Programme must be curtailed to less than or equal to the specified level by the start time shown in the Dispatch Instruction; and
- the Market Participant is expected to maintain at least this level of curtailment until the start time of the next Dispatch Instruction it receives for the Demand Side Programme; and
- a zero MW quantity means that the consumption of the Demand Side Programme no longer needs to be curtailed from the start time shown in that Dispatch Instruction; and
Dispatch Instructions with non-zero MW quantities will include an estimated end time for the dispatch – the Market Participant will use this estimate to update its DSP Constrained Withdrawal Quantities, but must not end its curtailment except in accordance with a zero MW quantity Dispatch Instruction.

7.6.11A. For each Dispatch Instruction issued for a Demand Side Programme, AEMO must record:

$a$ details of the Demand Side Programme to which the Dispatch Instruction relates;

$b$ the time the Dispatch Instruction was issued;

$c$ the Dispatch Interval from which the Dispatch Instruction applies, where this must be the first Dispatch Interval of a Trading Interval;

$d$ the MW quantity representing the required Withdrawal restriction, where:

i. a non-zero MW quantity represents a required reduction in the absolute value of Withdrawal from the Relevant Demand for the Demand Side Programme; and

ii. a zero MW quantity indicates that the Demand Side Programme is no longer required to restrict its Withdrawal; and

$e$ if a non-zero MW quantity is specified, the estimated Dispatch Interval from which the Dispatch Instruction may no longer apply, where this must be the first Dispatch Interval of a Trading Interval.

Explanatory Note

Clause 7.6.12 is amended to:

clarify that AEMO will not issue Dispatch Instructions to Non-Scheduled Facilities (although it may still issue directions to them where necessary);
explain how Non-Scheduled Facilities will be treated by the Dispatch Algorithm – treating the Facilities as Inflexible means that they will not set prices or be included in any tie-breaking processes; and
describe the key Dispatch Algorithm output that AEMO must record (and later publish) for Non-Scheduled Facilities.

7.6.12. AEMO must not issue Dispatch Instructions to Non-Scheduled Facilities, but must:

$a$ use the Real-Time Market Submissions of Non-Scheduled Facilities as input to the Dispatch Algorithm;

$b$ treat Non-Scheduled Facilities as Inflexible for the purposes of the Dispatch Algorithm; and

$c$ record the Dispatch Forecast determined by the Dispatch Algorithm for each Non-Scheduled Facility for each Dispatch Interval.

Explanatory Note

Clause 7.6.13 is amended to provide clarity on the obligation for a Demand Side Programme when actively curtailed. The Demand Side Programme consumption must be at or below the required level by the start time of the Dispatch Instruction, and must remain at or below the required level until the start time of the next Dispatch Instruction, which may either be to increase or decrease curtailment, or return to uncurtailed levels.

7.6.13. Where AEMO has issued a Dispatch Instruction with a non-zero MW quantity to a Demand Side Programme, the Market Participant must maintain an absolute MW level of Withdrawal from the Demand Side Programme less than or equal to the level required in the Dispatch Instruction from the start of the Dispatch Interval specified under clause 7.6.11A(c) until the start of the Dispatch Interval specified under clause 7.6.11A(c) for the next Dispatch Instruction issued to the Demand Side Programme.

Explanatory Note

Clause 7.6.13A is amended to provide clarity on when a Demand Side Programme may return to uncurtailed levels. A zero MW Dispatch Instruction indicates that the Demand Side Programme is no longer curtailed. However, as AEMO must issue the non-zero Dispatch Instruction ahead of time, the Demand Side Programme may not consume above the level specified in the previous non-zero MW Dispatch Instruction until the start time of the zero MW Dispatch Instruction.

7.6.13A. Where AEMO has issued a Dispatch Instruction with a zero MW quantity to a Demand Side Programme, the Market Participant may, from the start of the Dispatch Interval specified under clause 7.6.11A(c) for the Dispatch Instruction, increase the absolute MW level of Withdrawal of the Demand Side Programme above the level specified in the previous Dispatch Instruction.

Explanatory Note

Clause 7.6.14 is amended to:

include AEMO’s powers of direction in an Emergency Operating State; and
clarify that the clause applies to Dispatch Instructions issued to Scheduled Facilities and Semi-Scheduled Facilities; and
clarify that the linear profiles are based on estimates of the Registered Facility’s Injection or Withdrawal level at the start of the Dispatch Interval because the Dispatch Algorithm must determine the Dispatch Instructions ahead of the Dispatch Interval.

7.6.14. Subject to clause 7.10.14, unless the Dispatch Instruction is issued to implement a direction under clauses 3.4.4 or 3.5.5 or section 7.7, AEMO must determine the ramp rate in a Dispatch Instruction for a Scheduled Facility or Semi-Scheduled Facility using a linear profile between the Registered Facility’s estimated Injection or Withdrawal at the start of the Dispatch Interval and at the end of the Dispatch Interval covered by the Dispatch Instruction.

Explanatory Note

Clause 7.6.15, which sets out the requirement for AEMO to respect Standing Data minimum notice periods for Demand Side Programmes, is amended to reflect the proposed changes to the dispatch of Demand Side Programmes and the replacement of Appendix 1.

7.6.15. AEMO must issue a Dispatch Instruction to a Demand Side Programme before the Dispatch Interval from which the Dispatch Instruction applies, in accordance with the minimum response time specified for the Facility under Appendix 1(f)(iv).

7.6.16. [Blank]

Explanatory Note

Clause 7.6.17 is amended to clarify that because the Dispatch Algorithm is not directly processing Demand Side Programmes, AEMO must consider the impact of the Dispatch Instructions it issues to Demand Side Programmes (using the information provided by Market Participants in their revised DSP Withdrawal Profile Submissions) and, depending on the quantity and timeframes, may update the Forecast Unscheduled Operational Demand to reflect the impact in the forward Market Schedules where necessary.

The clause has been further amended following the consultation period for Exposure Draft 2 to use the new term Forecast Unscheduled Operational Demand.

7.6.17. Where AEMO issues a Dispatch Instruction to a Demand Side Programme, AEMO must review and if necessary adjust the Forecast Unscheduled Operational Demand for the relevant period to account for any expected changes to the Withdrawal of the Demand Side Programme’s Associated Loads.

7.6.18. AEMO must document in a WEM Procedure:

$a$ the processes AEMO and Market Participants must follow in issuing, recording, receiving, confirming and responding to Dispatch Instructions; and

$b$ the methodology and data requirements for conversion of sent-out figures to as-generated figures where AEMO agrees to convert sent-out figures to as-generated figures for the purposes of implementing Dispatch Instructions for a Registered Facility.

Explanatory Note

Clause 7.6.19 is amended to clarify that Market Participants are not always required to confirm the receipt of a Dispatch Instruction, as contemplated under clauses 7.6.6 and 7.6.20 (AGC control of Facilities).

7.6.19. Where a Market Participant is required to confirm the receipt of a Dispatch Instruction, AEMO must ensure that the communication methods used for issuing Dispatch Instructions allow the Market Participant to confirm the receipt of the Dispatch Instruction before the start of the Dispatch Interval to which the Dispatch Instruction relates in accordance with clause 7.6.20.

7.6.20. A Market Participant must confirm receipt of a Dispatch Instruction that was not issued by AEMO electronically via the Automatic Generation Control System for the Registered Facility in accordance with the WEM Procedure referred to in clause 7.6.18.

7.6.21. AEMO must not issue a Dispatch Instruction for a Dispatch Interval that has already ended.

7.6.22. AEMO must maintain a record of:

$a$ each Dispatch Instruction;

$b$ each confirmation of receipt of a Dispatch Instruction, where confirmation is required; and

$c$ each notification from a Market Participant under clause 7.6.31,

in a consolidated electronic form which enables the Market Auditor to audit the information, and is sufficient for use in settlement.

Explanatory Note

Clause 7.6.23 deals with tiebreaking arrangements. As most of the tiebreaking will be undertaken post-processing, AEMO will be given the ability to override Dispatch Algorithm outputs in certain circumstances without negating the entire process.

The intent of the priority order is to resolve tied offers by:

ensuring Registered Facilities are able to meet Dispatch Targets;
preferring Registered Facilities that would maintain consistency with dispatch in the previous Dispatch Interval;
preferring DSPs over other types of Registered Facilities to preserve flexible capacity (this is expected to only occur where there is a shortfall – if both are offered at the price cap, we would rather retain the flexibility of the other facility (e.g. a battery discharging) than the inflexible DSP);
preferring DSPs that do not share an Associated Load with an Interruptible Load over DSPs that do; and
ensuring dispatch would be shared between tied offers. For example, if 10MW was required and the Generator A tied offer tranche is for 20MW, Generator B tied offer tranche is for 30MW, the pro-rata loading would be 4MW for Generator A and 6MW for Generator B.

Clause 7.6.23 is amended to reflect the removal of Demand Side Programmes from the Dispatch Algorithm. Note that the requirement in clause 7.6.23(d) has been relocated to clause 7.6.5B(b)(iii).

Clause 7.6.23 has been further amended to remove clause 7.6.23(b). AEMO has advised that this requirement adds complexity to the tie-break mechanism and would increase project costs. AEMO has built the tie-break mechanism to mirror the NEM implementation, which does not consider clause 7.6.23(b).

Tiebreaking

7.6.23. Where the Dispatch Algorithm determines a Degenerate Solution, AEMO may issue Dispatch Instructions that override the output of the Dispatch Algorithm to the extent required to adjust the Dispatch Target of one or more Registered Facilities with tied Price-Quantity-Pairs, and in doing so must seek to, in the following priority order:

$a$ ensure that Dispatch Targets can be met by Registered Facilities; and

$b$ ensure pro-rata loading of tied Price-Quantity Pairs.

Explanatory Note

Clauses 7.6.24 and 7.6.25 allow AEMO to include Constraint Equations in the Dispatch Algorithm that seek to avoid large changes in dispatch (for both energy and ESS) for a small benefit. AEMO will be required to publish the impacts of these as for other binding constraints as part of the Congestion Information Resource. The intention is that the Constraint Violation Penalty for these constraints should be set higher than tiebreaking constraints, lower than all other constraints, and low enough to avoid noticeable impact on market prices.

The reference to historic costs in clause 7.6.26 is to provide a clear review scope.

7.6.24. AEMO may include Oscillation Control Constraint Equations in the Dispatch Algorithm to reduce the occurrence of:

$a$ Degenerate Solutions that result in inconsistent Dispatch Targets between Dispatch Intervals; and

$b$ significant changes in Essential System Services Enablement Quantities between Dispatch Intervals.

7.6.25. Where AEMO includes Oscillation Control Constraint Equations in the Dispatch Algorithm in accordance with clause 7.6.24, AEMO must ensure that:

$a$ the Dispatch Algorithm firstly takes into account all Constraint Equations other than Constraint Equations used to avoid Degenerate Solutions;

$b$ the Dispatch Algorithm violates an Oscillation Control Constraint Equation only in order to take into account other Constraints (according to the formulation specified under clauses 7.2.4(e) and 7.2.4(f)); and

$c$ the Constraint Relaxation process in clause 7.2.6 is applied when the Dispatch Algorithm determines that it is necessary to violate an Oscillation Control Constraint Equation.

7.6.26. When setting the parameters of Oscillation Control Constraint Equations, which determine the extent to which Oscillation Control Constraint Equations will bind, AEMO must consider the historic cost of binding Oscillation Control Constraint Equations as published in the Congestion Information Resource and the benefits to Power System Security and Power System Reliability of those Oscillation Control Constraint Equations.

7.6.27. AEMO must document in a WEM Procedure:

$a$ the process to be followed by AEMO when issuing Dispatch Instructions that override the output of the Dispatch Algorithm for Dispatch Intervals where the Dispatch Algorithm determines a Degenerate Solution pursuant to clause 7.6.23; and

$b$ situations that are deemed to be significant for the purposes of clause 7.6.24(b).

Explanatory Note

Clauses 7.6.28 to 7.6.30 replace section 7.8 of the current WEM Rules, but retain existing arrangements allowing AEMO to control Registered Facilities.

Clause 7.6.28 is further amended to ensure that AEMO can dispatch a Facility for energy or other equipment (e.g. a synchronous condenser) for ESS through AGC if agreed.

The Tranche 5 Amendments ‘insertion’ of clause 7.6.28 will not commence because the clause will have been created by the Tranches 2 and 3 Amendments. The Tranche 6 Amendments will replace the clause as intended in the Tranche 5 Amendments, with one additional change – clause 7.6.28(b) is extended to allow AEMO to limit the Withdrawal of Semi-Scheduled Facilities as well as their Injection, because a Dispatch Instruction to a Semi-Scheduled Facility could contain a Dispatch Cap for either Injection or Withdrawal.

AEMO Control of Registered Facilities

7.6.28. AEMO may, where required for a Registered Facility or equipment to participate in the Central Dispatch Process, or to provide an Essential System Service, or otherwise by agreement with a Market Participant, control specified operations of a Registered Facility or equipment, including:

$a$ the starting, loading and stopping of one or more of the Market Participant’s Scheduled Facilities; and

$b$ limiting the Injection or Withdrawal of one or more of the Market Participant’s Semi‑Scheduled Facilities.

7.6.29. The operational control of a Registered Facility by AEMO pursuant to an agreement referred to in clause 7.6.28:

$a$ does not remove AEMO’s obligation to record Dispatch Instructions for those Registered Facilities; and

$b$ does not affect or modify a Market Participant’s rights and obligations in respect of a Registered Facility under these WEM Rules. To avoid doubt, notwithstanding AEMO’s operational control, a Market Participant must comply with the obligations in section 7.10.

7.6.30. Where AEMO maintains operational control over a Registered Facility, AEMO must operate the Registered Facility in compliance with Dispatch Instructions recorded for the Registered Facility.

Explanatory Note

Clauses 7.6.31 and 7.6.32 provide a head of power for respecting Registered Facility dispatch inflexibilities.

Information about dispatch inflexibilities needs to be able to be verified. This verification could be done by either AEMO or the ERA. Which entity is better placed to perform such verifications is being considered further, and that may result in further amendments to clauses 7.6.31 and 7.6.33.

Dispatch Inflexibilities

7.6.31. Where a Market Participant reasonably expects that its Registered Facility will be unable to comply with a Dispatch Instruction for the Registered Facility in a future Dispatch Interval, the Market Participant must immediately:

$a$ amend its Real-Time Market Submission for the Registered Facility by specifying:

i. the Registered Facility is Inflexible in the relevant Dispatch Interval; and

ii. a single offer tranche which specifies the fixed level of Injection, Withdrawal, or Frequency Co-optimised Essential System Service enablement, at which the Registered Facility must be operated in the Dispatch Interval;

$b$ provide AEMO with a reason why the Registered Facility is Inflexible which must be able to be independently verified; and

$c$ if required, submit any Outages for the Registered Facility in accordance with section 3.21.

7.6.32. AEMO must use reasonable endeavours to issue Dispatch Instructions consistent with:

$a$ a Real-Time Market Submission that specifies a Registered Facility as Inflexible; and

$b$ a Registered Facility’s Dispatch Inflexibility Profile.

7.6.33. AEMO must document in a WEM Procedure the forms of independent verification to be used to support a reason given under clause 7.6.31(b).

7.7. Scarcity and Intervention

7.7.1. AEMO may direct a Market Participant to vary the reactive power output of a Registered Facility in accordance with Chapter 3A.

7.7.2. Where AEMO has entered into a Supplementary Capacity Contract, AEMO may direct the relevant resource to provide an Eligible Service in accordance with the terms of the Supplementary Capacity Contract.

7.7.2A. In the event of a system shutdown or major supply disruption, AEMO may dispatch System Restart Service Providers to provide System Restart Services, and must dispatch facilities in accordance with the System Restart Plan and Local Black Start Procedures.

7.7.3. Where AEMO has issued a Low Reserve Condition Declaration relating to an actual or projected shortfall in Essential System Services, AEMO may direct a Market Participant to make a Real-Time Market Submission for a Registered Facility that has been accredited to provide an Essential System Service in accordance with section 2.34A, that requires a quantity specified by AEMO of Essential System Service to be offered up to the maximum accredited quantity, or the lowest Remaining Available Capacity under any Outage, applying to the Registered Facility for that Frequency Co-optimised Essential System Service in any of the Dispatch Intervals covered by the Low Reserve Condition Declaration.

7.7.4. Where AEMO has issued a Low Reserve Condition Declaration relating to an actual or projected shortfall in energy and the Short Term PASA, Medium Term PASA or the Reference Scenario for the Pre-Dispatch Schedule projects that a Registered Facility will be needed to provide energy, AEMO may, as applicable:

$a$ where the projected energy shortfall will occur within four weeks of the date of the notice:

i. reject one or more Planned Outages for the Registered Facility; or

ii. issue an Outage Recall Direction to the Registered Facility; or

$b$ where the projected energy shortfall will occur within one week of the date of the notice, direct the relevant Market Participant to make a Real-Time Market Submission for a Registered Facility offering its full Reserve Capacity Obligation Quantity as In-Service Capacity.

7.7.5. Where AEMO has issued a Low Reserve Condition Declaration and the Short Term PASA or the Reference Scenario for the Pre-Dispatch Schedule projects that a Registered Facility will be needed to provide an Essential System Service, AEMO may direct a Market Participant to synchronise the Registered Facility to provide the Essential System Service.

7.7.6. Following a Contingency Event that results in a SWIS Frequency outside the Normal Operating Frequency Excursion Band, AEMO may adjust Essential System Service requirements to allow for an orderly transition back to full Essential System Service Enablement Quantities.

7.7.7. Following a Contingency Event that results in a SWIS Frequency outside the Normal Operating Frequency Excursion Band, if AEMO reasonably determines that the Dispatch Algorithm is not appropriately scheduling Registered Facilities for Essential System Services, AEMO may reduce the quantity of one or more Frequency Co-optimised Essential System Service requirement, including to zero, to reflect the activation of enabled Registered Facilities.

7.7.8. Where AEMO issues a direction to a Market Participant in accordance with this section 7.7 or under clauses 3.4.4, 3.4.5 or 3.5.5, AEMO must, as soon as practicable, input appropriate Constraint Equations in the Dispatch Algorithm to ensure that the Dispatch Algorithm generates Dispatch Targets that will allow the Registered Facility to comply with those directions.

7.7.9. A Dispatch Instruction issued by AEMO as a result of a direction issued by AEMO in accordance with this section 7.7 or under clauses 3.4.4, 3.4.5 or 3.5.5, must be consistent with the Registered Facility's data held by AEMO, including Standing Data, at the time the Dispatch Instruction is determined.

7.7.10. Where AEMO directs a Market Participant to vary the operation of a Registered Facility in a way that is not fully set out in a Dispatch Instruction, AEMO must record:

$a$ the date, time, and duration of the direction;

$b$ the name of the Registered Facility;

$c$ the nature of the direction (for example, commitment, fuel choice, reactive power output); and

$d$ the reason for the direction.

7.7.11. Subject to clause 7.7.12, Market Participants must comply with directions given by AEMO in accordance with this section 7.7.

7.7.12. A Market Participant is not required to comply with a direction referred to in clause 7.7.11 if it would endanger the safety of any person, damage equipment, or breach any applicable law.

7.7.13. Where a Market Participant cannot, in accordance with clause 7.7.12, comply with a direction from AEMO under this section 7.7, the Market Participant must notify AEMO as soon as possible and provide the reasons why it cannot comply, which must be one or more of the reasons specified in clause 7.7.12.

7.7.14. AEMO must document in a WEM Procedure the process it will use to determine which Registered Facility to direct under clauses 7.7.3, 7.7.4 or 7.7.5.

Explanatory Note

Section 7.8 sets out the requirements for Market Schedules to be determined and published by AEMO.

Several clauses in section 7.8 have been amended to clarify that Market Schedules are both “made available to Market Participants” (through APIs, etc) and published on the WEM Website.

7.8. Market Schedules

7.8.1. AEMO must determine, make available to Market Participants and publish on the WEM Website the following Market Schedules in accordance with the Real-Time Market Timetable:

$a$ Week-Ahead Schedules;

$b$ Pre-Dispatch Schedules; and

$c$ Dispatch Schedules.

7.8.2. AEMO must use processes that are consistent with the principles in section 7.11A in determining Market Schedules.

7.8.3. AEMO must determine Market Schedules comprising multiple Scenarios.

7.8.4. Where AEMO determines a Market Schedule comprising multiple Scenarios, AEMO must designate a Reference Scenario for each Market Schedule.

Explanatory Note

Clause 7.8.5 set sets out what a Reference Scenario represents and what it must include.

Although the Reference Scenario represents the mid-point of the range of expected outcomes, AEMO may consider the rest of the range in operating the power system. Where AEMO needs to take action based on wider projections, AEMO will issue a Low Reserve Condition Declaration.

7.8.5. A Reference Scenario for a Dispatch Schedule must:

$a$ represent AEMO’s best estimate of future dispatch and market outcomes;

$b$ take into account:

i. Enablement Minimums;

ii. Low Breakpoints;

iii. High Breakpoints;

iv. Enablement Maximums;

v. whether each Facility is Inflexible; and

vi. Planned Outages and Forced Outages; and

$c$ exclude any Available Capacity in Real-Time Market Submissions where the Start Decision Cutoff for the Registered Facility has passed.

7.8.5A. A Reference Scenario for a Pre-Dispatch Schedule or Week-Ahead Schedule must:

$a$ represent AEMO’s best estimate of future dispatch and market outcomes; and

$b$ exclude any Available Capacity in Real-Time Market Submissions where the Start Decision Cutoff for the Registered Facility has passed.

Explanatory Note

Clause 7.8.6 is intended to provide guidance on a minimum required set of Scenarios, and to provide flexibility for AEMO to define the details of the Scenario, and to add other Scenarios.

Clause 7.8.6(b) is amended to replace ‘In Service Capacity’ with ‘In-Service Capacity’.

Following the consultation period for Exposure Draft 2, clauses 7.8.6(a) and 7.8.6(c) have been deleted. AEMO has advised that the outcomes of the scenarios listed under clause 7.8.6(a) and 7.8.6(c) are not useful and would increase IT development and storage costs and administrative burden for no real benefit to the market. The sub-clauses have been renumbered accordingly.

7.8.6. In determining Week-Ahead Schedules and Pre-Dispatch Schedules, AEMO must include Scenarios that:

$a$ include In-Service Capacity in Real-Time Market Submissions, and exclude Available Capacity in Real-Time Market Submissions;

$b$ use a higher load forecast than the Reference Scenario; and

$c$ use a lower load forecast than the Reference Scenario.

7.8.7. All of the inputs for each Market Schedule must be recorded by AEMO in a form which will enable a third party, including the Market Auditor, to audit each Market Schedule.

7.8.8. AEMO may determine and make available to Market Participants any Market Schedule or DSP Schedule more frequently than specified in clauses 7.1.3(a)(iii) to 7.1.3(a)(vii).

7.8.9. AEMO must document in a WEM Procedure the processes for determining Market Schedules, including:

$a$ the number and types of Scenarios;

$b$ the principles, methodologies and calculations used to determine:

i. input data for each Market Schedule; and

ii. input data for each Scenario; and

$c$ how AEMO will apply clause 7.5.9 to each Market Schedule, including:

i. for each type of Market Schedule; and

ii. Dispatch Intervals or Pre-Dispatch Intervals within each Market Schedule.

Explanatory Note

New section 7.8A defines the requirements for the publication of information relating to potential and expected dispatch capability of Demand Side Programmes. The structure and timing of the two proposed DSP Schedules (the DSP Pre-Dispatch Schedule and DSP Week-Ahead Schedule) mirrors the corresponding Pre-Dispatch Schedule and Week-Ahead Schedule, except that information is provided for each Dispatch Interval (not Trading Interval) in the relevant period.

The schedules include two new values determined by AEMO for each Demand Side Programme for each Dispatch Interval:

DSP Forecast Capacity, which is the forecast total available reduction in MW of a Demand Side Programme, taking into the Facility’s Relevant Demand, RCOQ and Minimum Consumption (as estimated by AEMO at the time); and
DSP Forecast Reduction, which is the expected reduction in MW of a Demand Side Programme based on its submitted DSP Unconstrained Withdrawal Quantities and DSP Constrained Withdrawal Quantities.

7.8A. DSP Schedules

7.8A.1. A DSP Pre-Dispatch Schedule or DSP Week-Ahead Schedule is a schedule that includes, for each Demand Side Programme, for each Dispatch Interval in the Pre‑Dispatch Schedule Horizon or Week-Ahead Schedule Horizon (as applicable):

$a$ the DSP Unconstrained Withdrawal Quantity and DSP Constrained Withdrawal Quantity provided by the Market Participant in its DSP Withdrawal Profile Submission;

$b$ AEMO’s reasonable estimate based on the information available to AEMO of:

i. the Demand Side Programme’s Relevant Demand in the applicable Trading Interval;

ii. the sum of the Minimum Consumption of each Associated Load of the Demand Side Programme in the applicable Trading Interval; and

iii. the Reserve Capacity Obligation Quantity of the Demand Side Programme in the Dispatch Interval;

$c$ the DSP Forecast Capacity, determined by AEMO in accordance with clause 7.8A.3; and

$d$ the DSP Forecast Reduction, determined by AEMO in accordance with clause 7.8A.4.

7.8A.2. AEMO must determine, make available to Market Participants and publish on the WEM Website the following DSP Schedules in accordance with the Real-Time Market Timetable:

$a$ DSP Week-Ahead Schedules; and

$b$ DSP Pre-Dispatch Schedules.

7.8A.3. The DSP Forecast Capacity for a Demand Side Programme in a Dispatch Interval is:

DSPForecastCapacity = max(0, DSPUWQ – max(MinLoad, RD – RCOQ))

where:

DSPUWQ is the Unconstrained Withdrawal Quantity provided by the Market Participant in its DSP Withdrawal Profile Submission for the Demand Side Programme and Dispatch Interval;

MinLoad is AEMO’s reasonable estimate, based on the information available to it, of the sum of Minimum Consumption of each Associated Load of the Demand Side Programme in the applicable Trading Interval;

RD is AEMO’s reasonable estimate, based on the information available to it, of the Relevant Demand of the Demand Side Programme in the applicable Trading Interval; and

RCOQ is AEMO’s reasonable estimate, based on the information available to it, of the Reserve Capacity Obligation Quantity of the Demand Side Programme in the Dispatch Interval.

7.8A.4. The DSP Forecast Reduction for a Demand Side Programme in a Dispatch Interval is:

DSPForecastReduction = DSPUWQ – DSPCWQ

where:

DSPUWQ is the Unconstrained Withdrawal Quantity provided by the Market Participant in its DSP Withdrawal Profile Submission for the Demand Side Programme and Dispatch Interval; and

DSPCWQ is the Constrained Withdrawal Quantity provided by the Market Participant in its DSP Withdrawal Profile Submission for the Demand Side Programme and Dispatch Interval.

7.9. Commitment

7.9.1. Where a Real-Time Market Submission for a Registered Facility does not specify a Dispatch Inflexibility Profile, the Registered Facility must commence the process of starting and synchronising without instruction or direction from AEMO to be eligible for dispatch in a Dispatch Interval covered by the Real-Time Market Submission.

7.9.2. If a Market Participant intends to synchronise a Registered Facility, or any part of it, for which it has not specified a Dispatch Inflexibility Profile, then it must notify AEMO of the expected time of synchronisation by designating the Registered Facility’s capacity as In-Service Capacity in the Real-Time Market Submission for the Registered Facility.

7.9.3. If a Market Participant intends to desynchronise a Registered Facility, or any part of it, for which it has not specified a Dispatch Inflexibility Profile, the Market Participant must notify AEMO of the expected time of desynchronisation by updating the Real-Time Market Submission for the Registered Facility to reflect the Registered Facility’s Available Capacity and In-Service Capacity.

7.9.4. If a Market Participant intends to synchronise or desynchronise an unregistered Energy Producing System serving an Intermittent Load, the Market Participant to which the Intermittent Load is registered must notify AEMO of the expected time of synchronisation or desynchronisation of the unregistered Energy Producing System.

7.9.5. Clauses 7.9.2 and 7.9.3 do not apply where:

$a$ AEMO issues a Dispatch Instruction to the Registered Facility that requires synchronisation or desynchronisation within one hour of the time the Dispatch Instruction is issued; or

$b$ AEMO has directed the Registered Facility to synchronise or desynchronise under clause 3.5.5 or section 7.7.

7.9.6. AEMO may request a Market Participant provide further notification to AEMO immediately before synchronising or desynchronising a Registered Facility, or any part of it. A Market Participant must comply with a request under this clause 7.9.6.

7.9.7. AEMO may direct a Market Participant to not synchronise or desynchronise the Registered Facility, or any part of it, as applicable, if:

$a$ AEMO reasonably considers that the synchronisation or desynchronisation of a Registered Facility, or any part of it, is required to enable AEMO to maintain Power System Security and Power System Reliability in accordance with Chapter 3;

$b$ the synchronisation or desynchronisation of the Registered Facility, or any part of it, is not in accordance with the relevant Dispatch Instruction;

$c$ AEMO reasonably considers that it would be unable to operate the Central Dispatch Process or utilise the Dispatch Algorithm in accordance with section 7.2 if synchronisation or desynchronisation were to occur; or

$d$ in the case of a Registered Facility undergoing a Reserve Capacity Test or a Commissioning Test, the synchronisation or desynchronisation is not in accordance with the Reserve Capacity Test or Commissioning Test Plan, as applicable, for the Registered Facility approved by AEMO under section 3.21A.

7.9.8. A Market Participant must comply with a direction by AEMO in accordance with clause 7.9.7 unless complying with the direction would endanger the safety of any person, damage equipment, or breach any applicable law.

7.9.9. Where a Market Participant cannot comply with a direction from AEMO under clause 7.9.7, in accordance with clause 7.9.8, the Market Participant must notify AEMO as soon as possible and provide the reasons why it cannot comply, which must be one or more of the reasons specified in clause 7.9.8.

7.9.10. [Blank]

7.9.11. A Market Participant for an Interruptible Load which was activated in response to a Contingency Event must:

$a$ obtain approval from AEMO prior to initiating the Restoration Profile for the Interruptible Load; and

$b$ notify AEMO if the Restoration Profile for the Interruptible Load is not the same as the Restoration Profile in the Standing Data for the Interruptible Load.

Explanatory Note

Section 7.10 sets out the obligations regarding Market Participants’ compliance with Dispatch Instructions.

The obligations of AEMO and the ERA in relation to Market Participants’ compliance (from clause 7.10.4) are dealt with in the Monitoring and Compliance WEM Rules.

The dispatch compliance obligations for Demand Side Programmes have been moved to new clause 7.10.1A.

Clause 7.10.1 is also amended to remove the words “sent out” because the relevant quantities are all “sent out” quantities (e.g. the as-generated equivalent of a Dispatch Target is not the Dispatch Target).

The clause has also been restructured to remove any potential ambiguity around the meaning of “the Dispatch Target or Dispatch Cap, Essential System Service Enablement Quantities and Ramp Rate”.

Dispatch Compliance

7.10. Compliance with Dispatch Instructions

7.10.1. A Market Participant must comply with the following in the most recently issued Dispatch Instruction applicable to its Scheduled Facility, Semi-Scheduled Facility or Interruptible Load for the Dispatch Interval:

$a$ the Dispatch Target or Dispatch Cap as applicable;

$b$ Essential System Service Enablement Quantities; and

$c$ Ramp Rate.

7.10.1A. A Market Participant must comply with the most recently issued Dispatch Instruction applicable to its Demand Side Programme in a Dispatch Interval.

7.10.2. A Market Participant is not required to comply with clause 7.10.1 if:

$a$ such compliance would endanger the safety of any person, damage equipment or breach any applicable law;

$b$ the actual Injection or Withdrawal of the Registered Facility does not, at any time the Dispatch Instruction applies:

i. vary, by more than the applicable Tolerance Range or Facility Tolerance Range, from a linear profile between the Injection or Withdrawal of the Facility at the start of the Dispatch Interval and the Dispatch Target at:

1. the time at which the Dispatch Target would be reached by ramping at the ramp rate specified in the Dispatch Instruction; or

2. if no ramp rate is specified in the Dispatch Instruction, the end of the Dispatch Interval;

ii. exceed by more than the applicable Tolerance Range or Facility Tolerance Range a linear profile between the Injection or Withdrawal of the Facility at the start of the Dispatch Interval and the Dispatch Cap at:

1. the time at which the Dispatch Cap would be reached by ramping at the ramp rate specified in the Dispatch Instruction; or

2. if no ramp rate is specified in the Dispatch Instruction, the end of the Dispatch Interval;

$c$ both of the following apply:

i. the Market Participant notifies AEMO, in accordance with clause 3.21.2(a), that its Registered Facility has been affected by or will be affected by a Forced Outage; and

ii. the quantity of the relevant Remaining Available Capacity for the Forced Outage notified is consistent with the extent to which the Market Participant did not comply with the most recently issued Dispatch Instruction applicable to its Registered Facility for the Dispatch Interval;

$d$ the Registered Facility has been granted permission under clause 7.10.14 to ramp at a fixed rate, complies with the Dispatch Target or Dispatch Cap, as relevant, and ramps at the ramp rate specified in the Real-Time Market Submission for the Registered Facility;

$e$ AEMO was unable to issue Dispatch Instructions to a Fast Start Facility in accordance with clause 7.6.32(b), and that Facility is responding according to its Dispatch Inflexibility Profile; or

$f$ the Market Participant was conducting a Commissioning Test on a Facility as part of an approved Commissioning Test Plan, and was unable to comply with clause 7.10.1 in a Dispatch Interval due to a failure of the Facility’s equipment.

7.10.2A. A Market Participant is not required to comply with clause 7.10.1A if such compliance would endanger the safety of any person, damage equipment or breach any applicable law.

7.10.3. Notwithstanding clause 7.10.2(b), a Market Participant must not consistently operate its Registered Facility at the extremes of the Tolerance Range or Facility Tolerance Range applicable to the Registered Facility.

7.10.4. Where a Semi-Scheduled Facility contains an Electric Storage Resource, a Market Participant must not operate the Electric Storage Resource to increase the deviation of the Semi-Scheduled Facility’s Injection or Withdrawal from the Semi-Scheduled Facility’s Dispatch Forecast, unless the deviation is:

$a$ instructed as part of the delivery of one or more Essential System Services; or

$b$ to provide a required response as part of the Facility’s Registered Generator Performance Standard.

7.10.5. AEMO must document in a WEM Procedure the method for calculating an Electric Storage Resource’s contribution to the relevant Semi-Scheduled Facility’s deviation from its Dispatch Forecast for the purposes of clause 7.10.4.

7.10.6. Where a Market Participant can control the Injection or Withdrawal of a Semi-Scheduled Facility, it must not exercise that control so as to increase the deviation of the Semi-Scheduled Facility’s Injection or Withdrawal from the Semi-Scheduled Facility’s Dispatch Forecast, unless this deviation is:

$a$ instructed as part of the delivery of one or more Essential System Services; or

$b$ to provide a required response as part of the Facility’s Registered Generator Performance Standard.

7.10.7. Where a Market Participant becomes aware that it cannot comply or fully comply with a Dispatch Instruction, and that non-compliance is not covered under clause 7.10.2(b) through 7.10.2(e), it must notify AEMO as soon as practicable.

7.10.8. Where a Market Participant has notified AEMO under clause 7.10.7 that it cannot comply or fully comply with a Dispatch Instruction the Market Participant must provide AEMO with the reason it cannot comply or cannot fully comply with the Dispatch Instruction.

Explanatory Note

Clause 7.10.9 deals with two different situations:

where a participant has a one-off notification under 7.10.7 (cannot comply due to safety / damage); and
where a participant has repeated non-compliance.

In both cases, it is important that the Market Participant updates its Real-Time Market Submission, and that AEMO has the power to adjust inputs if necessary.

7.10.9. Where a Market Participant notifies AEMO under clause 7.10.7 that it cannot comply or fully comply with a Dispatch Instruction, or AEMO observes repeated non-compliance by the Market Participant in accordance with the WEM Procedure referred to in clause 2.15.4:

$a$ AEMO may adjust inputs to the Dispatch Algorithm to accurately reflect the capability of the relevant Registered Facility; and

$b$ the Market Participant must immediately after notifying AEMO under clause 7.10.7 update its Real-Time Market Submissions to accurately reflect the capability of its Registered Facility.

7.10.10. The Economic Regulation Authority may, at any time, request a Market Participant to provide further information in respect of the reasons that it could not comply or fully comply with a Dispatch Instruction, including further information to clarify any reason provided under clause 7.10.8.

7.10.11. A Market Participant must respond to any request from the Economic Regulation Authority under clause 7.10.10 by the time specified in the request.

7.10.12. Where a Registered Facility is only capable of ramping at a fixed rate, the Market Participant for the Registered Facility may apply to AEMO for permission to ramp at a fixed rate in response to Dispatch Instructions.

7.10.13. A Market Participant must provide evidence in support of an application made under clause 7.10.12, including any information specified in the WEM Procedure referred to in clause 7.10.21.

7.10.14. Where AEMO receives an application under clause 7.10.12 and is satisfied that the relevant Registered Facility is only able to ramp at a fixed rate, AEMO must permit the Registered Facility to ramp at a fixed rate in response to Dispatch Instructions.

7.10.15. AEMO must notify a Market Participant and the Economic Regulation Authority, in writing, of its decision under clause 7.10.14 to grant permission or not and provide written reasons for its decision.

7.10.16. A Market Participant that has been granted permission in accordance with clause 7.10.14 must immediately notify AEMO if any works to the Registered Facility that is the subject of the permission results in the Facility being capable of ramping with a linear profile to the end of a Dispatch Interval to meet Dispatch Instructions.

7.10.17. In response to a notification under clause 7.10.16, AEMO may, by notice in writing to the Market Participant and the Economic Regulation Authority, revoke permission granted by it under clause 7.10.14.

7.10.18. A Facility accredited to provide Contingency Reserve must be capable of responding according to its accredited capability (including Facility Speed Factor), and sustain the required response for a period of at least 15 minutes following any Contingency Event.

Explanatory Note

Clause 7.10.19 is amended to use the defined term Automatic Generation Control System and clarify that commands from AEMO’s Automatic Generation Control System are not to be confused with Dispatch Instructions.

7.10.19. Where a Market Participant receives a Dispatch Instruction to enable a Facility to provide a quantity of Regulation Raise or Regulation Lower in a Dispatch Interval, the Market Participant must ensure that the Facility (subject to the Facility’s maximum ramp rates in relation to the provision of the relevant Essential System Service) is able to provide the full enabled MW quantity of response at any time during the Dispatch Interval, according and subject to commands from AEMO’s Automatic Generation Control System.

Explanatory Note:

Clause 7.10.20 is amended so that Maximum Contingency Reserve Block Size is not limited to Contingency Reserve Raise. The definition of Maximum Contingency Reserve Block size in the Glossary is also amended accordingly.

7.10.20. A Registered Facility that has been accredited in accordance with section 2.34A to provide Contingency Reserve Raise subject to a Maximum Contingency Reserve Block Size may respond to a Contingency Event using the whole quantity of all cleared or partially cleared Contingency Reserve Raise Price-Quantity Pairs.

7.10.21. AEMO must document in a WEM Procedure:

$a$ the processes to be followed by AEMO when it observes repeated non-compliance by a Market Participant in accordance with the WEM Procedure referred to in clause 2.15.4;

$b$ the processes to be followed by a Market Participant making an application under clause 7.10.12 or notifying AEMO under clause 7.10.16;

$c$ the information to be provided by a Market Participant in support of an application under clause 7.10.12;

$d$ the processes to be followed by AEMO in determining whether or not to grant permission under clause 7.10.14 or to revoke permission under clause 7.10.17; and

$e$ the timeline for assessing an application under clause 7.10.12 and notifying a Market Participant of its decision in accordance with clause 7.10.15, which must not exceed 10 Business Days from the date AEMO receives the application.

Explanatory Note

This section brings together sections 6.19 (Market Advisories) and 7.11 (Dispatch Advisories) in the current WEM Rules.

The WEM Rules still reflect the arrangements when the IMO and System Management each had a head of power to issue notices to the market. Now that AEMO carries out both functions, the current Dispatch Advisories and Market Advisories frameworks will be merged into a new Market Advisory notice.

The new Market Advisory notice will not contain the same level of information as the current notices as a lot of information will be visible in the Pre-Dispatch Schedule. The intent is for as much information as possible to be provided via the standard market operation processes, with Market Advisories being used for exceptions.

Market Advisories

7.11. Market Advisories

7.11.1. A Market Advisory is a notification published by AEMO on the WEM Website that there has been, or is likely to be, an event that AEMO reasonably considers may impact Power System Security, Power System Reliability or the operation of the Central Dispatch Process, the Real-Time Market, the Short Term Energy Market or the Reserve Capacity Mechanism.

7.11.2. AEMO must issue a Market Advisory for future potential events if it considers there to be a high probability that the event will occur unless the event has already been signalled in a Pre-Dispatch Schedule.

7.11.3. Market Advisories must be released as soon as practicable after AEMO becomes aware of a situation requiring the release of a Market Advisory and AEMO must update the Market Advisory as soon as possible after new, relevant information becomes available to it.

7.11.3A. Where AEMO must respond to an unexpected and sudden event, AEMO may issue a Market Advisory after the event has occurred.

7.11.4. AEMO must withdraw a Market Advisory and inform notify Market Participants, Network Operators and the Economic Regulation Authority of the withdrawal of a Market Advisory as soon as practicable once the situation that the Market Advisory relates to has finished.

7.11.5. AEMO must release a Market Advisory in the event of, or in anticipation of, any circumstance which would, in AEMO’s reasonable opinion, significantly threaten Power System Security or Power System Reliability, including but not limited to, the following circumstances:

$a$ the SWIS is in, or is expected to be in, an Emergency Operating State;

$b$ the SWIS is unable to be, or is expected that it cannot be, operated in accordance with the Power System Security Principles;

$c$ System Restart Service is, or is expected to be, enabled for purposes other than a test;

$d$ AEMO is unable to maintain the SWIS in a Reliable Operating State;

$e$ the whole or any part of the WEM Rules, including, without limitation, in respect to the operation of the Real-Time Market, have been, or are expected to be, suspended in accordance with clause 2.44.1;

$f$ fuel supply on a Trading Day is at risk, or is significantly more restricted than usual;

$g$ involuntary load shedding is occurring or is expected to occur that AEMO reasonably considers may impact Power System Security, Power System Reliability or the operation of Central Dispatch Process;

(gA) AEMO reasonably considers that the dispatch of Demand Side Programmes may occur for a Trading Day as a result of a potential energy shortfall identified in accordance with the WEM Procedure referred to in clause 7.6.5C;

$h$ significant degradation or failure of AEMO market or control systems required for the normal conduct of the operation of the Real-Time Market and the Central Dispatch Process;

$i$ an AEMO Intervention Event has occurred, or is expected to occur; and

$j$ a significant Contingency Event has occurred, as detailed in the WEM Procedure referred to in clause 7.11.8,

unless the situation has already been signalled through a Low Reserve Condition Declaration, Pre-Dispatch Schedule, or in the information published under section 3.22, as applicable.

Explanatory Note

Clause 7.11.6 sets out the information AEMO is required to include in a Market Advisory.

Clause 7.11.6 is further amended to add clause 7.11.6(cA), which specifies the information AEMO must include in a Market Advisory relating to potential Demand Side Programme dispatch.

7.11.6. Subject to clause 7.11.6B, a Market Advisory must contain the following information:

$a$ the date and time that the Market Advisory is released;

$b$ the time period for which the Market Advisory is expected to apply;

$c$ details of the situation that the Market Advisory relates to, including the location, extent and seriousness of the situation where AEMO is able to reasonably estimate this information at the time the Market Advisory is issued;

(cA) where the Market Advisory relates to the circumstances described in clause 7.11.5(gA), AEMO’s estimate of:

i. which Demand Side Programmes may be dispatched; and

ii. the period during which the Withdrawal of the Demand Side Programmes may potentially be curtailed;

$d$ any actions AEMO plans to take in response to the situation, including whether AEMO’s actions constitute an AEMO Intervention Event;

$e$ the latest time at which AEMO would need to intervene through an AEMO Intervention Event should the response from Market Participants not be such as to obviate the need for the AEMO Intervention Event;

$f$ where relevant, a description of the actions AEMO has taken or is taking in response to the situation; and

$g$ where AEMO has developed the WEM Procedure referred to in clause 7.11.8, whether that WEM Procedure applies to the situation.

7.11.6A. AEMO must issue an updated Market Advisory containing the information in clause 7.11.6(c) as soon as practicable where AEMO revises an estimate of the information or after AEMO is able to reasonably determine the information.

7.11.6B. If any information that would otherwise be released under clauses 7.11.6(c), 7.11.6(d) or 7.11.6(e) is confidential or has a confidentiality status that would prevent the Economic Regulation Authority from releasing the information, AEMO must:

$a$ release that information to the Economic Regulation Authority but, subject to clause 7.11.6B(b), ensure that the Market Advisory contains information of only a general or aggregate nature so that the information publicly released is not confidential; and

$b$ include in the Market Advisory the details of any circumstance that has given rise to AEMO issuing the Market Advisory, including:

i. the name of the Registered Facility or Network element where that Registered Facility or Network element has caused or materially contributed to the circumstances giving rise to the Market Advisory;

ii. the name of the Registered Facility, or Registered Facilities, that are likely to be dispatched in response to the Market Advisory; and

iii. unless already published, any changes to the inputs to the Dispatch Algorithm that AEMO has made or intends to make in response to the situation identified in the Market Advisory, including changes to Constraint Equations.

7.11.6C. Where AEMO is required to:

$a$ make changes to any inputs to the Dispatch Algorithm; or

$b$ issue a direction to a Market Participant or a Network Operator,

prior to issuing a Market Advisory, AEMO may make any such changes and issue any such direction as if a Market Advisory had already been issued.

7.11.7. Market Participants, Network Operators and the Economic Regulation Authority must inform AEMO as soon as practicable if they become aware of any circumstances that might reasonably be expected to result in AEMO issuing a Market Advisory.

7.11.8. AEMO may document in a WEM Procedure the processes to be followed by AEMO and Market Participants with respect to the events or situations specified in, or contemplated by, this section 7.11, including:

$a$ a description of events that AEMO would consider significant for the purposes of 7.11.5(j);

$b$ the processes to be followed by Market Participants after receiving a relevant Market Advisory; and

$c$ the processes to be followed by AEMO after it has issued a relevant Market Advisory.

Explanatory Note

The new price determination provisions are set out in the following new sections:

section 7.11A – Price Determination Principles;
section 7.11B – Determination of Market Clearing Prices; and
section 7.11C – Corrections to Price Determinations and Intervention Pricing.

Section 7.11A sets out the principles for using the Dispatch Algorithm to determine Market Clearing Prices, including handling situations where AEMO applies manual constraints on Registered Facilities, and those constraints mean that the Real-Time Market Submissions of that Facility will not flow through into marginal prices for energy or ESS.

Price Determination

7.11A. Price Determination Principles

7.11A.1. The principles applying to the determination of prices in the Real-Time Market are:

$a$ subject to this section 7.11A, a Market Clearing Price at the Reference Node is determined by AEMO using the Central Dispatch Process for each Dispatch Interval;

$b$ a Reference Trading Price is determined by AEMO as the time-weighted average of the Market Clearing Prices for energy for each Dispatch Interval in a Trading Interval;

$c$ Registered Facilities which operate in accordance with a direction in the Central Dispatch Process are to be taken into account by AEMO, but AEMO must not use the applicable Real-Time Market Offers or Real-Time Market Bids for those Registered Facilities in the calculation of the Market Clearing Price for the relevant Market Service in the relevant Dispatch Interval;

$d$ where a Registered Facility is Inflexible, AEMO must take the Inflexibility of the Registered Facility into account in the Central Dispatch Process, but must not use the price in the Real-Time Market Offer or Real-Time Market Bid for that Registered Facility for the applicable Market Service in the calculation of the Market Clearing Price for that Market Service in the relevant Dispatch Interval;

$e$ Loss Factors and Constraint Equations are to be taken into account by AEMO in the calculation of Market Clearing Prices;

$f$ where the Injection or Withdrawal of a Registered Facility is limited above or below the level at which it would otherwise have been dispatched by AEMO on the basis of its Real-Time Market Offer or Real-Time Market Bid for energy due to a Constraint Equation included in the Dispatch Algorithm under clause 7.5.8(a):

i. the Registered Facility’s Real-Time Market Offer or Real-Time Market Bid for energy, as applicable, is to be taken into account by AEMO in the determination of dispatch, but the Real-Time Market Offer or Real-Time Market Bid, as applicable, is not to be used by AEMO in the calculation of the Market Clearing Price for energy in the relevant Dispatch Interval; and

ii. the Registered Facility’s Real-Time Market Submissions for other Frequency Co-optimised Essential System Services are to be used by AEMO in the determination of dispatch and taken into account in determining the Market Clearing Prices for those Market Services;

$g$ subject to section 9.9, AEMO must apply the Reference Trading Price to both sales and purchases of energy in the relevant Trading Interval;

$h$ when a Market Clearing Price is determined for a Frequency Co-optimised Essential System Service, AEMO must apply that price to purchases of that Frequency Co-optimised Essential System Service in the relevant Dispatch Interval; and

$i$ where there is a shortfall in a Frequency Co-optimised Essential System Service, AEMO must set the Market Clearing Price for that service to the difference between the Energy Offer Price Ceiling and the Energy Offer Price Floor.

Explanatory Note

Section 7.11B describes how Market Clearing Prices are to be determined by AEMO.

In abnormal situations, the approach for determining Market Clearing Prices is:

where the Dispatch Algorithm fails to run, AEMO will use the ‘forecast’ prices (clause 7.11B.1);
when the Dispatch Algorithm runs but with faulty inputs, AEMO will use the prices from the previous Dispatch Interval (Affected Dispatch Interval – clause 7.11C.1); and
where AEMO intervenes, AEMO will run a ‘what if’ run without the intervention inputs and use the prices from that run (Intervention Dispatch Interval – clause 7.11C.6). These ‘what if’ runs will still be run in the same dispatch timeframe, and results published at dispatch time.

7.11B. Determination of Market Clearing Prices

7.11B.1. Subject to section 7.11C, where AEMO runs the Dispatch Algorithm, AEMO must determine a Market Clearing Price for each Market Service for a Dispatch Interval.

7.11B.1A. If AEMO fails to run the Dispatch Algorithm to determine Market Clearing Prices for any Dispatch Interval, then the Market Clearing Prices for that Dispatch Interval are:

$a$ if the Dispatch Interval has been included in a previous Dispatch Schedule, the Market Clearing Prices determined for the Dispatch Interval in the most recent Dispatch Schedule that includes the Dispatch Interval; or

$b$ if the Dispatch Interval has not been included in a previous Dispatch Schedule, the Market Clearing Prices determined for the Pre-Dispatch Interval containing the Dispatch Interval in the Reference Scenario for the most recent Pre-Dispatch Schedule that includes the Dispatch Interval.

7.11B.2. Subject to clauses 7.11B.3, 7.11B.4 and 7.11B.5, the Market Clearing Price for a Market Service represents the marginal value of that Market Service at the Reference Node at that time, which is calculated as the cost of meeting an incremental change in the requirement for the Market Service at that time in accordance with clause 7.6.4.

Explanatory Note

Clause 7.11B.3 is amended to reflect that Demand Side Programmes are no longer included in the Dispatch Algorithm and there is no need to set the Market Clearing Price for energy to the Energy Offer Price Cap because a Demand Side Programme has been dispatched.

Clause 7.11B.3(c) is also amended to correct a clause reference error.

7.11B.3. If, for any Dispatch Interval:

$a$ the Market Clearing Prices for the Dispatch Interval have not already been determined by the Central Dispatch Process;

$b$ AEMO reasonably determines that the Central Dispatch Process may determine that there is insufficient capacity to meet all load; and

$c$ AEMO has issued a manual load shed direction to a Network Operator under clause 3.4.4,

then AEMO must set the Energy Market Clearing Price for the Dispatch Interval to equal the Energy Offer Price Ceiling.

7.11B.3A. If, for any Dispatch Interval, the Energy Market Clearing Price determined using the Dispatch Algorithm is:

$a$ greater than the Energy Offer Price Ceiling, then AEMO must set the Energy Market Clearing Price in that Dispatch Interval to equal the Energy Offer Price Ceiling; and

$b$ less than the Energy Offer Price Floor, then AEMO must set the Energy Market Clearing Price in that Dispatch Interval to equal the Energy Offer Price Floor.

7.11B.3B. If, for any Dispatch Interval, the Market Clearing Price for a Frequency Co‑optimised Essential System Service determined using the Dispatch Algorithm is:

$a$ greater than the applicable FCESS Clearing Price Ceiling, then AEMO must set the Market Clearing Price for the Frequency Co-optimised Essential System Service in that Dispatch Interval to equal the applicable FCESS Clearing Price Ceiling; and

$b$ less than zero, then AEMO must set the Market Clearing Price for the Frequency Co-optimised Essential System Service in that Dispatch Interval to equal zero.

7.11B.4. If, for any Dispatch Interval, AEMO has determined that the Dispatch Interval is an Affected Dispatch Interval under clause 7.11C.1A, then AEMO must set the Market Clearing Prices for the Dispatch Interval in accordance with section 7.11C.

7.11B.4A. If, for any Dispatch Interval, AEMO has not determined that the Dispatch interval is an Affected Dispatch Interval, and AEMO has declared the Dispatch Interval to be an Intervention Dispatch Interval under clause 7.11C.6, then AEMO must set the Market Clearing Prices for the Dispatch Interval in accordance with clauses 7.11C.7, 7.11C.8, 7.11C.9 and 7.11C.10.

7.11B.5. If, for any Dispatch Interval, the Market Clearing Price for a Frequency Co-optimised Essential System Service determined using the Dispatch Algorithm is less than zero, then AEMO must set the Market Clearing Price for the Frequency Co-optimised Essential System Service in that Dispatch Interval to zero.

Explanatory Note

New clauses 7.11C.1 to 7.11C.4 set out a regime that gives AEMO the ability to identify incorrect inputs and adjust prices accordingly. Real-time ex-ante pricing provides limited time for AEMO to identify incorrect input data before it is used in the Central Dispatch Process to generate Dispatch Instructions and determine the Market Clearing Prices.

7.11C. Corrections to Price Determinations and Intervention Pricing

7.11C.1. AEMO must develop procedures for the automatic identification of Affected Dispatch Intervals, and must document in a WEM Procedure the conditions or circumstances that would identify a Dispatch Interval as an Affected Dispatch Interval.

7.11C.1A. AEMO must use the procedures developed under clause 7.11C.1 to determine whether each Dispatch Interval is an Affected Dispatch Interval.

7.11C.2. Where AEMO determines that a Dispatch Interval is an Affected Dispatch Interval, and no more than 30 minutes have passed since the publication of the Market Clearing Prices for the Affected Dispatch Interval, AEMO must:

$a$ replace all Market Clearing Prices with the corresponding prices for the Last Correct Dispatch Interval; and

$b$ if AEMO has already calculated the relevant Reference Trading Price, recalculate and adjust the Reference Trading Price, in accordance with clause 7.11A.1(b).

7.11C.3. As soon as reasonably practicable after the action referred in clause 7.11C.2, AEMO must publish on the WEM Website a report outlining:

$a$ the reasons for determining that a Dispatch Interval was an Affected Dispatch Interval;

$b$ whether that determination was correct; and

$c$ what action will be taken to minimise the risk of a similar event in future.

7.11C.4. At least once each year, AEMO must review the effectiveness of the automated processes developed by AEMO under clause 7.11C.1 and publish a report on the WEM Website detailing the findings of the review.

7.11C.5. A report under clause 7.11C.4 must:

$a$ cover the 12-month period since the end of the period covered by the last report;

$b$ be published within 3 months of the end of the review period covered by the report; and

$c$ include the following:

i. details of all Affected Dispatch Intervals which should not have been identified as Affected Dispatch Intervals;

ii. the reasons why the Affected Dispatch Intervals identified under clause 7.11C.5(c)(i) were identified as Affected Dispatch Intervals; and

iii. details of any Dispatch Intervals that AEMO has subsequently determined should have been identified by AEMO as Affected Dispatch Intervals, but were not.

7.11C.5A.AEMO must develop and submit a Procedure Change Proposal where it considers that a change is required to the WEM Procedure developed under clause 7.11C.1 as a result of a report that it has published under clause 7.11C.4.

Explanatory Note

Clauses 7.11C.6 to 7.11C.11 set out a regime that is intended to ensure that Market Clearing Prices are not depressed by reason of AEMO’s manual intervention. For example, if AEMO directs a Registered Facility on, then it will displace a cheaper Facility, and the marginal price of the next unit of energy will be lower than it otherwise would have been (i.e. because that cheaper generation is now available to provide the marginal unit of energy).

This is a structural effect that is not dealt with by the uplift payment mechanism, because even though the directed Market Participant could be made whole via an uplift payment if negatively mispriced, all other relevant Market Participants would receive a lower Market Clearing Price because of the intervention.

7.11C.6. AEMO must declare a Dispatch Interval to be an Intervention Dispatch Interval where one or more AEMO Intervention Events were in effect in the Dispatch Interval.

7.11C.7. Subject to clauses 7.11C.8(a) and 7.11C.8(b), if, in AEMO's reasonable opinion, the reason for an AEMO Intervention Event is to obtain either:

$a$ a Market Service for which a Market Clearing Price is determined by the Dispatch Algorithm; or

$b$ a service that is a direct substitute for a Market Service for which a Market Clearing Price is determined by the Dispatch Algorithm,

then AEMO must, in accordance with the methodology or assumptions to be documented in the WEM Procedure referred to in clause 7.11C.11, set the Market Clearing Prices for an Intervention Dispatch Interval at the values which AEMO, in its reasonable opinion, considers would have applied as the Market Clearing Prices for that Dispatch Interval had the AEMO Intervention Event not occurred.

Explanatory Note

Where AEMO intervenes to change the dispatch of a Registered Facility that is on the other side of a constraint from the Reference Node, the intervention will not affect the Market Clearing Price at the Reference Node, so no intervention pricing change is required.

Where AEMO intervenes to change the dispatch of a Registered Facility that is not behind a constraint, it will affect the market clearing price at the Reference Node.

Islanding would be an extreme constraint, in which the Market Clearing Price would be set at the Reference Node, and generators in Islands would qualify for uplift pricing.

7.11C.8. If, in AEMO’s reasonable opinion, the reason for an AEMO Intervention Event is to obtain:

$a$ energy or a Frequency Co-optimised Essential System Service which, as a result of a Constraint, is only capable of being provided by a Registered Facility in a part of the SWIS which does not include the Reference Node due to the Constraint;

$b$ demand response which, as a result of a Constraint, is needed to reduce demand for energy or Frequency Co-optimised Essential System Service in a part of the SWIS which does not include the Reference Node due to the Constraint; or

$c$ a service for which a Market Clearing Price is not determined by the Dispatch Algorithm, regardless of whether energy or Frequency Co-optimised Essential System Services are also provided incidental to the provision of the service,

then AEMO must continue to set the Market Clearing Prices for the Intervention Dispatch Interval in accordance with section 7.11B, excluding 7.11B.4A.

7.11C.9. If more than one AEMO Intervention Event is in effect in respect of an Intervention Dispatch Interval, AEMO must set the Market Clearing Prices pursuant to clause 7.11C.7 as if:

$a$ the services described in clause 7.11C.7 were not provided; and

$b$ energy or any Essential System Services provided incidental to the provision of any services described in clause 7.11C.8 were taken into account.

7.11C.10. AEMO must use its reasonable endeavours to set Market Clearing Prices according to clause 7.11C.7 as soon as practicable following an AEMO Intervention Event, but may continue to set Market Clearing Prices as if no AEMO Intervention Event had occurred for Dispatch Intervals before the later of:

$a$ if AEMO is able to operate the SWIS in accordance with the Power System Security Principles, the Dispatch Interval immediately following the first Intervention Dispatch Interval; or

$b$ if AEMO is not able to operate the SWIS in accordance with the Power System Security Principles, the second Dispatch Interval after AEMO became able to operate the SWIS in accordance with the Power System Security Principles after the first Intervention Dispatch Interval.

7.11C.11. AEMO must document in a WEM Procedure the methodology it will use, and any assumptions it may be required to make, to determine the Market Clearing Prices under clauses 7.11C.7, 7.11C.8 and 7.11C.10. The methodology must, wherever reasonably practicable:

$a$ be consistent with the principles for the determination of Market Clearing Prices set out in section 7.11A; and

$b$ enable AEMO to determine and publish such prices in accordance with the applicable timeframes for the publication of the Market Clearing Prices under these WEM Rules.

Real-Time Market Suspension and Administered Pricing

7.11D. Real-Time Market Suspension

7.11D.1. AEMO may suspend the Real-Time Market:

$a$ in the event of a system shutdown or major supply disruption;

$b$ when AEMO has been requested by the Minister, under clause 2.44.1, to suspend the market or operate all or part of the power system in connection with the exercise of emergency powers; or

$c$ when AEMO determines that it is necessary because it has become impossible to maintain Power System Security in accordance with the provisions of these WEM Rules due to:

i. failure of its IT systems;

ii. loss of communications or control systems required to maintain Power System Security; or

iii. any other reason as identified in the WEM Procedure published under clause 7.11D.4.

7.11D.2. Where AEMO deems, in its reasonable opinion, it is practicable to resume the Central Dispatch Process it must:

$a$ lift any suspension of the Real-Time Market at commencement of the next practicable Trading Interval, in accordance with the process described in the WEM Procedure referred to in clause 7.11D.4; and

$b$ resume the determination of Market Clearing Prices.

7.11D.3. AEMO must issue a Market Advisory when suspending or lifting the suspension of the Real-Time Market.

7.11D.4. AEMO must document in a WEM Procedure:

$a$ the process by which AEMO will determine to suspend the Real-Time Market;

$b$ the reasons AEMO may suspend the Real-Time Market;

$c$ the processes which Market Participants are required to follow during the suspension; and

$d$ the processes AEMO will follow during the suspension including the process to lift the suspension which must provide a notice period of not less than two hours.

Explanatory Note

Section 7.11E is added to set out how Market Clearing Prices for a Market Service (Energy and any Frequency Co-optimised Essential System Services) when the Real-Time Market has been suspended.

In the event that a major system event has occurred, such as a system wide shutdown, AEMO would suspended the Real-Time Market and Central Dispatch. During this period AEMO will enact its processes to direct facilities to recover the system. For the duration of the suspension the Market Clearing Price for energy will be set to Energy Offer Price Cap and all FCESS prices and quantities will be set to zero.

In the event that WEMDE or the Real-Time Market systems are not working, and participants are not able to submit credible offers or AEMO systems have insufficient data to be used to set Market Clearing Prices, the Market Clearing Prices for a given interval will be the same as the average Market Clearing Price from the previous four completed Trading Weeks.

Where previous prices are not available for a particular Market Service (for example, if WEMDE fails at the start of the new market), clause 7.11E.4 provides guidance on how AEMO should set prices.

Section 7.11D will not apply to emergency circumstances, such as a system black event or emergency operating state.

7.11E. Administered Pricing in the Event of Market System Failure

7.11E.1. If the Real-Time Market is suspended under clause 7.11D.1(a), AEMO must set the final Market Clearing Prices for each Market Service in any Dispatch Interval during the suspension as follows:

$a$ the Final Energy Market Clearing Price is to equal the Energy Offer Price Ceiling;

$b$ the Final Regulation Raise Market Clearing Price is to equal zero and the Essential System Service Enablement Quantity for each Registered Facility accredited for Regulation Raise for the Dispatch Interval is zero;

$c$ the Final Regulation Lower Market Clearing Price is to equal zero and the Essential System Service Enablement Quantity for each Registered Facility accredited for Regulation Lower for the Dispatch Interval is zero;

$d$ the Final Contingency Reserve Raise Market Clearing Price is to equal zero and the Essential System Service Enablement Quantity for each Registered Facility accredited for Contingency Reserve Raise for the Dispatch Interval is zero;

$e$ the Final Contingency Reserve Lower Market Clearing Price is to equal zero and the Essential System Service Enablement Quantity for each Registered Facility accredited for Contingency Reserve Lower for the Dispatch Interval is zero; and

$f$ the Final RoCoF Control Service Market Clearing Price is to equal zero and the RoCoF Control Service requirements for the Dispatch Interval is zero.

7.11E.2. If the Real-Time Market is suspended under clause 7.11D.1(b), AEMO must set the final Market Clearing Prices for each Market Service in any Dispatch Interval during the suspension as requested by the Minister.

7.11E.3. If the Real-Time Market is suspended under clause 7.11D.1(c), AEMO must set the final Market Clearing Prices for each Market Service in any Dispatch Interval during the suspension as the average final Market Clearing Price for that Market Service in the equivalent intervals in the four most recent completed Trading Weeks.

7.11E.4. Where, for the purposes of clause 7.11E.3, a Market Clearing Price is not available for a Market Service for an equivalent Dispatch Interval in the four most recent completed Trading Weeks referred to in clause 7.11E.3, AEMO must set the final Market Clearing Prices for each Market Service as follows:

$a$ where there is no Final Energy Market Clearing Price available for the equivalent Dispatch Interval, AEMO must set the Final Energy Market Clearing Price as the average price for energy from the most recently published price for energy for 28 consecutive Trading Days for the equivalent Dispatch Interval;

$b$ where there is no Final Regulation Raise Market Clearing Price available for the equivalent Dispatch Interval, AEMO must set the Final Regulation Raise Market Clearing Price as the average price for Regulation Raise, or equivalent service, from the most recently published price for the service for 28 consecutive Trading Days for the equivalent Dispatch Interval;

$c$ where there is no Final Regulation Lower Market Clearing Price available for the equivalent Dispatch Interval, AEMO must set the Final Regulation Lower Market Clearing Price as the average price for Regulation Lower, or equivalent service, from the most recently published price for the service for 28 consecutive Trading Days for the equivalent Dispatch Interval;

$d$ where there is no Final Contingency Reserve Raise Market Clearing Price available for the equivalent Dispatch Interval, AEMO must set the Final Contingency Reserve Raise Market Clearing Price as:

Margin(di) × Energy_Price(di)

where:

i. Margin is the Spinning Reserve margin price as the most recent determination by the Economic Regulation Authority for the equivalent Dispatch Interval; and

ii. Energy_Price is the average price for energy from the most recently published energy prices for 28 consecutive Trading Days for the equivalent Dispatch Interval;

$e$ where there is no Final Contingency Reserve Lower Market Clearing Price available for the equivalent Dispatch Interval, AEMO must set the Final Contingency Reserve Lower Price Market Clearing Price using an estimation method that takes into account the quantum and price set by the Economic Regulation Authority for load rejection reserve; and

$f$ where there is no Final RoCoF Control Service Market Clearing Price available for the equivalent Dispatch Interval, AEMO must set the RoCoF Control Service requirements for the Dispatch Interval to zero and set the Final RoCoF Control Service Market Clearing Price to zero.

7.11E.5. All administered prices set under clauses 7.11E.3 and 7.11E.4 will be subject to a floor of $0.

7.11E.6. To avoid doubt, and without limiting clause 1.55.9, for the purposes of the time periods specified in clauses 7.11E.3 and 7.11E.4, AEMO may, to the extent it considers necessary to set the final Market Clearing Prices specified in those clauses, use any data and information under the Pre-Amended Rules (as defined in clause 1.55.9) that it considers reasonable to use in the circumstances.

7.12. [Blank]

Settlement and Monitoring Data

Explanatory Note

Section 7.13 is amended to reflect the amended relevant information under these WEM Rules.

Section 7.13 is amended to clarify where information must be provided directly to Market Participants (e.g. via a portal or B2B mechanism) or published on the WEM Website, and the associated timeframes.

The WEM Website is a lower availability solution than a Market Participant interface, therefore while AEMO must make efforts to publish data in a timely manner to the WEM Website, there are occasions where making the data available may be delayed (e.g. WEM Website maintenance, or general data latency).

The changes in this section include:

separating the requirements to make certain information available to Market Participants from the requirements to publish that information on the WEM Website;
clarifying the requirements for demand forecasts and the reporting of actual Injection and Withdrawal quantities;
removing the requirement to publish non-Reference Scenario Market Schedule information on the WEM Website (note the information will still be made available to Market Participants and will Public Information);
reducing the maximum delay permitted in publishing Market Schedule-related information on the WEM Website to one Business Day; and
minor enhancements to improve the clarity of the drafting.

7.13. Settlement and Monitoring Data

7.13.1. AEMO must make available to Market Participants:

$a$ for each Pre-Dispatch Interval of each Pre-Dispatch Schedule or Week-Ahead Schedule, within 30 minutes of determining that Market Schedule; and

$b$ for each Dispatch Schedule, within 5 minutes of determining that Dispatch Schedule,

the following information:

$c$ total quantity of Real-Time Market Offers for In-Service Capacity for each Market Service;

$d$ total quantity of Real-Time Market Offers for Available Capacity for each Market Service;

$e$ total quantity of Real-Time Market Bids for In-Service Capacity for energy;

$f$ total quantity of Real-Time Market Bids for Available Capacity for energy; and

$g$ Intervention Constraints.

Explanatory Note

Clause 7.13.1A is amended to:

clarify that the Forecast Operational Demand is associated with the Reference Scenario, and that other forecasts may be used for other Scenarios; and
include a new defined term “Near Binding Constraint Equations” in clause 7.13.1A(i) – the definition has been proposed to resolve an issue that arises where the right hand side of a Constraint Equation is zero.

7.13.1A. AEMO must make available to Market Participants:

$a$ for each Pre-Dispatch Interval in each Scenario of each Pre-Dispatch Schedule or Week-Ahead Schedule, within 30 minutes of determining that Market Schedule; and

$b$ for each Scenario of each Dispatch Schedule, within 5 minutes of determining that Dispatch Schedule,

the following information:

$c$ the Forecast Unscheduled Operational Demand or, where applicable, the alternative forecast used for the Scenario;

(cA) the Forecast Operational Demand or, where applicable, the equivalent forecast determined for the Scenario;

(cB) the Forecast Operational Withdrawal or, where applicable, the equivalent forecast determined for the Scenario;

$d$ the projected total quantity required of each Frequency Co-optimised Essential System Service;

$e$ projected shortfalls in each Market Service;

$f$ projected Dispatch Targets, Dispatch Caps and Dispatch Forecasts as applicable for each Registered Facility. To avoid doubt, AEMO must identify which Facility each quantity is associated with;

$g$ projected Essential System Service Enablement Quantities as applicable for each Registered Facility. To avoid doubt, AEMO must identify which Facility each quantity is associated with;

$h$ binding Constraint Equations;

$i$ Near Binding Constraint Equations;

$j$ projected Market Clearing Prices for each Market Service;

$k$ the Minimum RoCoF Control Requirement;

$l$ the Additional RoCoF Control Requirement;

$m$ the RoCoF Control Requirement;

$n$ the Contingency Raise Offset;

$o$ the Contingency Lower Offset;

$p$ Facility Performance Factors; and

$q$ the identity of each Registered Facility that was subject to a Commissioning Test or a Reserve Capacity Test.

7.13.1B. Within 5 minutes of each time AEMO uses the Dispatch Algorithm for the purposes of the Central Dispatch Process, and no later than the end of the relevant Dispatch Interval, AEMO must make available to Market Participants:

$a$ Dispatch Targets, Dispatch Caps, Dispatch Forecasts as applicable for each Facility;

$b$ Essential System Service Enablement Quantities as applicable for each Registered Facility and each Frequency Co-optimised Essential System Service;

$c$ the Market Clearing Price for each Market Service for the relevant Dispatch Interval;

$d$ binding Constraint Equations;

$e$ Near Binding Constraint Equations;

$f$ the Minimum RoCoF Control Requirement;

$g$ the Additional RoCoF Control Requirement;

$h$ the RoCoF Control Requirement;

$i$ the Contingency Raise Offset;

$j$ the Contingency Lower Offset;

$k$ Facility Performance Factors; and

$l$ the AEMO estimated quantity of Not In-Service Capacity for each Scheduled Facility or Semi-Scheduled Facility for which a Market Participant holds Capacity Credits, in each Dispatch Interval.

7.13.1C. Within 5 minutes of the end of a Trading Interval, AEMO must make available to Market Participants the Reference Trading Price for that Trading Interval.

Explanatory Note

Clause 7.13.1CA has been further amended to require AEMO to re-publish a Market Clearing Price or a Reference Trading Price once it has been revised as a result of an Affected Interval or Intervention Event.

7.13.1CA. Where a Market Clearing Price has been impacted by an Affected Dispatch Interval or AEMO Intervention Event, AEMO must:

$a$ determine revised Market Clearing Prices for each Market Service for the relevant Dispatch Interval;

$b$ determine the revised Reference Trading Price for the relevant Trading Interval; and

$c$ make the revised prices referred to in clauses 7.13.1CA(a) and 7.13.1CA(b) available to Market Participants as soon as practicable.

7.13.1CB. Where a Market Clearing Price has been impacted by a suspension of the Real-Time Market under clause 7.11D.1, AEMO must, based on the final Market Clearing Prices for each Market Service for each Dispatch Interval during the suspension as determined by AEMO in accordance with section 7.11E:

$a$ determine revised Market Clearing Prices for each Market Service for each relevant Dispatch Interval;

$b$ determine the revised Reference Trading Price for each relevant Trading Interval; and

$c$ make the revised prices referred to in clauses 7.13.1CB(a) and 7.13.1CB(b) available to Market Participants as soon as practicable.

7.13.1D. For each Pre-Dispatch Interval or Dispatch Interval in each Scenario in each Market Schedule, AEMO must, within 30 minutes of the completion of the Market Schedule (or within 5 minutes of completion for the Dispatch Schedule), make available to each Market Participant:

$a$ which of its Registered Facilities clause 7.5.8(a) applies to;

$b$ which of its Registered Facilities clause 7.5.8(b) applies to; and

$c$ the Estimated FCESS Uplift Payment for each of its Scheduled Facilities and Semi-Scheduled Facilities.

Explanatory Note

Clause 7.13.1E is amended to better align AEMO’s data publication requirements with the inputs and outputs of the Dispatch Algorithm, and the requirements of downstream Settlement equations.

Clause 7.13.1E is amended to:

clarify that the listed information is published on the WEM Website;
remove the reference to Unadjusted Semi-Scheduled Injection Forecasts in clause 7.13.1E(a)(iii);
remove redundant words from clause 7.13.1E(a)(iv);
clarify in clause 7.13.1E(b) that maximum daily ambient temperatures are only published for Scheduled Facilities and Semi-Scheduled Facilities, and that they are determined using the method specified for the Facility in Standing Data; and
extend the list of items to be published in clause 7.13.1E(c) to include Unconstrained Injection Forecasts, Unconstrained Withdrawal Forecasts and Inflexibility indicators;
use standard language for the decrease of a Demand Side Programme and update the cross reference in clause 7.13.1E(d); and
require (in new clause 7.13.1E(h)) the publication of any alternative forecast quantities determined and used by AEMO in the Central Dispatch Process under clause 7.2.4A.

7.13.1E. AEMO must prepare and publish on the WEM Website the following data for a Trading Day by noon on the first Business Day following the day on which the Trading Day ends:

$a$ the following SCADA data for each Dispatch Interval of the Trading Day:

i. an estimate of the MWh Injection or Withdrawal of each Scheduled Facility, Semi-Scheduled Facility or Non‑Scheduled Facility monitored by AEMO’s SCADA system;

ii. [Blank]

iii. where it is available to AEMO for use in the Central Dispatch Process, data that has been used to adjust Essential System Service submissions for each Facility;

iv. the Charge Level immediately prior to the start of the Dispatch Interval of each Electric Storage Resource that is part of a Semi-Scheduled Facility or Scheduled Facility and monitored by AEMO’s SCADA system;

v. the MWh output or consumption of each separate electricity producing unit in each Energy Producing System supplying an Intermittent Load for which, in AEMO’s reasonable opinion, the information provided under clause 2.30B.3(g) does not show that if a Contingency Event or an event behind the relevant connection point affects the Energy Producing System the net Injection or Withdrawal of the Facility will change by less than 10 MW;

vi. the EOI Quantity of each Scheduled Facility, Semi-Scheduled Facility and Non-Scheduled Facility;

vii. the Operational Demand;

viii. the Operational Withdrawal; and

ix. any other SCADA data used as an input into the Central Dispatch Process;

(aA) for each Trading Interval of the Trading Day, an estimate, derived from SCADA data, of the MWh Injection or Withdrawal of each Scheduled Facility, Semi-Scheduled Facility or Non-Scheduled Facility monitored by AEMO’s SCADA system;

$b$ the maximum daily ambient temperature at the site of each Scheduled Facility or Semi-Scheduled Facility, recorded in accordance with the method specified in Appendix 1(b)(viii) or Appendix 1(c)(viii) as applicable;

$c$ details of each Real-Time Market Submission used in the Central Dispatch Process for Dispatch Intervals in that Trading Day, including, as applicable:

i. the Registered Facility ID;

iA. the Market Service;

ii. Price-Quantity Pairs;

iii. In-Service Capacity for Injection;

iv. Available Capacity for Injection;

v. In-Service Capacity for Withdrawal;

vi. Available Capacity for Withdrawal;

vii. the Maximum Upwards Ramp Rate;

viii. the Maximum Downwards Ramp Rate;

ix. Enablement Minimums;

x. Enablement Maximums;

xi. Low Breakpoints;

xii. High Breakpoints;

xiii. Dispatch Inflexibility Profiles;

xiv. any reasons for revisions in accordance with clauses 7.4.26(a) or 7.4.27(a);

xv. if the Registered Facility is Inflexible;

xvi. the Unconstrained Injection Forecast; and

xvii. the Unconstrained Withdrawal Forecast;

$d$ where applicable, for each Trading Interval of the Trading Day, the requested decrease in absolute value of Withdrawal for each Demand Side Programme calculated under clause 7.13.5;

$e$ where applicable, for each Scheduled Facility or Semi-Scheduled Facility and each Dispatch Interval of the Trading Day, the Congestion Rental in respect of the full set of Network Constraints, calculated under clause 7.14.1;

$f$ where applicable, for each Scheduled Facility or Semi-Scheduled Facility and each Dispatch Interval, the Energy Uplift Price and the Uplift Payment Mispricing Trigger;

$g$ for each Dispatch Interval of the Trading Day:

i. all Facility Risks for that Dispatch Interval; and

ii. for each Network Contingency which is a Credible Contingency Event that is taken into account when setting the Contingency Reserve Raise requirement under clause 7.2.4 in that Dispatch Interval:

1. the Network Risk associated with that Network Contingency; and

2. the Registered Facilities whose Facility Risks are included in the Network Risk associated with that Network Contingency; and

$h$ for each Dispatch Interval of the Trading Day, for each Semi-Scheduled Facility and Non-Scheduled Facility, any alternative forecast quantities to the Unconstrained Injection Forecast and Unconstrained Withdrawal Forecast provided by the Market Participant in its Real-Time Market Submission that were determined and used by AEMO in the Central Dispatch Process under clause 7.2.4A.

Explanatory Note

Further amendments include:

where necessary, requirements to make information available to Market Participants need to be separated from the requirements to publish that information on the WEM Website;
the requirements for DSP Schedules and DSP Dispatch Instruction details need to be included in this section;
extensions for making information available to Market Participants under clauses 7.13.1, 7.13.1A, 7.13.1B, 7.13.1C, 7.13.1CA and 7.13.1D are not required;
extensions for making DSP Schedules and Dispatch Instruction details available to Market Participants are not required;
the extension contemplated in clause 7.13.1F should also apply to clause 7.13.1G, because AEMO may reasonably encounter a delay in collecting the relevant information;
extensions for publications under clauses 7.13.1, 7.13.1A, 7.13.1B, 7.13.1C, 7.13.1CA and the publications of DSP Schedules and Dispatch Instructions are only required because of temporary WEM Website technical issues, and not because of delays in collecting the relevant information.

To achieve the required outcomes:

clauses 7.13.F, 7.13.1G and 7.13.1H are deleted;
clause 7.13.1G is reinserted as clause 7.13.1F to improve the logical flow of the clauses;
a new clause 7.13.1G specifies the requirement to provide DSP Pre-Dispatch Schedules and DSP Week-Ahead Schedules to Market Participants;
new clause 7.13.1H requires the provision to Market Participants of DSP Dispatch Instructions;
new clause 7.13.1I requires AEMO to publish the information referred to under clauses 7.13.1 – 7.13.1CA (excluding non-Reference Scenario details under clause 7.13.1A) and 7.13.1G-7.13.1H on the WEM Website as soon as practicable after making the information available to Market Participants;
new clause 7.13.1J allows AEMO, where it is prevented by a temporary technical issue from publishing data on the WEM Website under clause 7.13.1I, to delay the publication of the data on the WEM Website by up to one Business Day;
Clause 7.13.1J is renumbered to 7.13.1K; and
clause 7.13.1H is reinserted as clause 7.13.1L, and amended to replace the reference to clause 7.13.1G(a) to reflect the renumbering of clause 7.13.1G.

7.13.1F. AEMO must prepare and publish on the WEM Website, for each Trading Interval and Dispatch Interval of a Trading Day, by noon on the first Business Day following the day on which the Trading Day ends:

$a$ an estimate of the total quantity of energy not served (in MWh) due to involuntary load shedding (manual and automatic); and

$b$ an estimate of the change in Withdrawal (in MWh) of any Interruptible Loads in the provision of Contingency Reserve Raise.

7.13.1G. AEMO must make available to Market Participants, for each Dispatch Interval of each DSP Pre-Dispatch Schedule or DSP Week-Ahead Schedule, within 30 minutes of determining that DSP Schedule, the following information:

$a$ for each Demand Side Programme:

i. DSP Unconstrained Withdrawal Quantity;

ii. DSP Constrained Withdrawal Quantity;

iii. estimated Relevant Demand;

iv. estimated sum of the Minimum Consumption of each Associated Load of the Demand Side Programme;

v. estimated Reserve Capacity Obligation Quantity;

vi. DSP Forecast Capacity; and

vii. DSP Forecast Reduction;

$b$ the sum of the DSP Forecast Capacities of each Demand Side Programme; and

$c$ the sum of the DSP Forecast Reductions of each Demand Side Programme.

7.13.1H. Within five minutes of each time AEMO issues a Dispatch Instruction to a Demand Side Programme, AEMO must make available to Market Participants the details of that Dispatch Instruction.

7.13.1I. AEMO must publish the following information on the WEM Website as soon as practicable after it has made the information available to Market Participants:

$a$ the information referred to in clauses 7.13.1, 7.13.1B, 7.13.1C, 7.13.1CA, 7.13.1CB, 7.13.1G and 7.13.1H; and

$b$ the information referred to in clause 7.13.1A for the Reference Scenario of the applicable Market Schedule.

7.13.1J. If AEMO is prevented by a temporary technical issue from publishing data on the WEM Website under clause 7.13.1I, AEMO may delay the publication of the data on the WEM Website by up to one Business Day.

7.13.1K. If AEMO is prevented from completing the relevant processes that enable the recording of the data described in clauses 7.13.1E or 7.13.1F, AEMO may delay the preparation and publication of the data on the WEM Website by up to two Business Days.

7.13.1L. AEMO may, if it reasonably considers it is required in order to estimate, or support AEMO’s estimate of, the quantity referred to in clause 7.13.1F(a), request information from Rule Participants in respect to any involuntary load shedding. A Rule Participant must comply with a request under this clause 7.13.1L within the time specified in the request.

Explanatory Note

Clauses 7.13.2 and 7.13.6 are amended to cater for estimates that AEMO is required to produce in order to run Relevant Level calculations. If a Facility that contains an Intermittent Generation System or Non-Scheduled Facility is participating in the Relevant Level Methodology, then actual outputs of those Facilities are required to support the RLM calculation. If the Facility was curtailed during an RLM interval, or is yet to enter service, then AEMO is required to estimate the quantities needed for the calculations.

These amendments allow for different combinations of Facilities that may have Intermittent Generation Systems (Scheduled, Semi-Scheduled), as well as for Non-Scheduled Facilities that do not have Intermittent Generation Systems, but are still participating in the RLM.

The revisions clarify when estimates are required, and for which Facilities, and also clarify when the estimates should be published.

7.13.2. Where AEMO is required to develop estimates under clause 7.13.6, AEMO must publish those estimates as soon as practicable after the date specified in clause 4.1.11.

7.13.3. AEMO must document in a WEM Procedure the procedure to be followed by Rule Participants in providing settlement and monitoring data to AEMO.

7.13.4. AEMO must:

$a$ determine the Operational Demand Estimate and Operational Withdrawal Estimate from SCADA data for Registered Facilities at least once every minute; and

$b$ publish each Operational Demand Estimate and Operational Withdrawal Estimate on the WEM Website as soon as practicable after its determination under clause 7.13.4(a),

and these values are not required to be maintained on the WEM Website after their initial publication.

Explanatory Note

Clause 7.13.5 is amended to reflect the simpler dispatch arrangements proposed for Demand Side Programmes and the removal of the need to account for ramp rates when determining the requested quantity of reduction.

Due to the increased simplicity, the quantity will be provided as a MW value and the requirement for AEMO to develop a WEM Procedure has been removed.

7.13.5. AEMO must, for the purposes of clauses 7.13.1E(d) and 4.26.2D, calculate, for each Demand Side Programme for each Trading Interval, the quantity, in MW, by which the Facility was requested by the applicable Dispatch Instruction to curtail the absolute value of its Withdrawal during that Trading Interval, where the quantity:

$a$ must be measured as a requested decrease from the Facility’s Relevant Demand (and so must not include any quantity above the Relevant Demand); and

$b$ must not take account of the Facility’s actual performance in response to the Dispatch Instruction.

Explanatory Note

Clause 7.13.6 is amended to account for situations where a Network limitation means that a Facility would not have been able to send out any energy regardless of what Dispatch Instruction it was issued by AEMO.

7.13.6. Where an estimate is required to support the Relevant Level Methodology for a Registered Facility that:

$a$ contains an Intermittent Generating System; or

$b$ is a Non-Scheduled Facility,

AEMO must estimate, for the Intermittent Generating System or Non-Scheduled Facility, for each Trading Interval, the maximum quantity of sent out energy in MWh which the Intermittent Generating System or Non-Scheduled Facility could have potentially generated in the Trading Interval had the output of the Registered Facility associated with the Intermittent Generating System or the Non-Scheduled Facility not been restricted by a Dispatch Instruction or Network limitation during that Trading Interval, in accordance with the WEM Procedure referred to in clause 7.13.8.

7.13.7. If AEMO reasonably believes that the estimate determined under clause 7.13.6 was incorrect, it must revise the estimate for use in the Relevant Level Methodology.

Explanatory Note

Clause 7.13.8 is amended to clarify that AEMO will actually use the methods it specifies in the WEM Procedure to determine estimates under clause 7.13.6.

Clause 7.13.8 is also amended to use standard clause reference terminology.

7.13.8. AEMO must develop a WEM Procedure specifying:

$a$ the methods that AEMO will use to determine estimates under clause 7.13.6;

$b$ the process for revising an estimate under clause 7.13.7; and

$c$ the information that a Market Participant must provide to AEMO for each of the Market Participant’s Registered Facilities to support the preparation of estimates under clauses 7.13.6 and 7.13.7.

Not In-Service Capacity

Explanatory Note

Section 7.13A enables AEMO to determine the Not-In-Service Capacity for each Registered Facility that is assigned Capacity Credits. Market Participants for Facilities that are assigned Capacity Credits are required to present the Facility's capacity at least up to its Reserve Capacity Obligation Quantity in their market submissions as ‘available’ or ‘in-service’. If a price/quantity offer is “in merit” for a Trading Interval, or directed to be in service by AEMO, the relevant Market Participant must, subject to applicable start up timeframes, amend the availability declaration to ‘in service’. When this is not the case, the Not-In-Service capacity will be subject to capacity refunds.

These clauses will commence with the majority of dispatch clauses on the New WEM Commencement Day.

However, as this section 7.13A reflects the amendments contained in the Miscellaneous Amendments No. 2, as those amending rules (made by the Minister at the date this companion version was prepared) will be commenced last, please refer to the Miscellaneous Amendments No. 1 to see section 7.13A (Determination and Publication of RoCoF Upper Limit) that will apply until it is then deleted (in accordance with the Amending Rules in that same instrument) and section 7.13A below commenced.

7.13A. Not In-Service Capacity

7.13A.1. AEMO must determine the Not In-Service Capacity for each Scheduled Facility or Semi-Scheduled Facility f for which a Market Participant holds Capacity Credits, in the Dispatch Interval DI as either:

$a$ where AEMO has directed a Registered Facility to offer its capacity as In Service:

NISCap(f,DI) = Max(0, Min(RCOQ(f,DI), ReqDispEnergy(f,DI)) – Max(ISSDCEnergy(f,DI), ISDispEnergy(f,DI))

or

$b$ otherwise:

NISCap(f,DI) = Max(0, Min(RCOQ(f,DI), EstDispEnergy(f,DI)) – Max(ISSDCEnergy(f,DI), ISDispEnergy(f,DI))

where:

i. NISCap(f,DI) is the Not In-Service Capacity quantity for the relevant Facility f in Dispatch Interval DI;

ii. EstDispEnergy(f,DI) is the quantity of estimated energy dispatch immediately prior to the Start Decision Cutoff time for the relevant Facility f in Dispatch Interval DI, calculated in accordance with clause 7.13A.2;

iii. ISSDCEnergy(f,DI) is the quantity of In-Service Capacity offered immediately after the Start Decision Cutoff time for the relevant Facility f in Dispatch Interval DI, calculated in accordance with clause 7.13A.3;

iv. ISDispEnergy(f,DI) is the total MW quantity of In-Service Capacity for the relevant Facility f included in the Real-Time Market Offers for energy that were used to formulate Dispatch Instructions and calculate Market Clearing Prices for Dispatch Interval DI; and

v. ReqDispEnergy(f,DI) is the quantity of In-Service Capacity for the relevant Facility f required by AEMO in Dispatch Interval DI.

Explanatory Note

Clauses 7.13A.2 and 7.13A.3 are amended to reflect the restructure of clause 7.4.40(g).

The clauses have also been amended to reflect that Market Schedules may be made available to Market Participants before they are published on the WEM Website.

7.13A.2. EstDispEnergy(f, DI) for each Scheduled Facility or Semi-Scheduled Facility f in Dispatch Interval DI is determined from the most recent Market Schedule made available to Market Participants before the Start Decision Cutoff from the Price-Quantity Pair for Injection for the relevant Facility f with the longest minimum time to synchronise, as specified in clause 7.4.40(g)(i)(3), as applicable:

$a$ where at least one Dispatch Schedule has been made available to Market Participants that contains Dispatch Interval DI within a Trading Interval, the total MW quantity of energy scheduled for dispatch in the Dispatch Interval DI for the relevant Facility f determined in the Reference Scenario of the Dispatch Schedule; or

$b$ where at least one Pre-Dispatch Schedule has been made available to Market Participants that contains Dispatch Interval DI within a Trading Interval, then the total MW quantity of energy scheduled for dispatch in the Trading Interval for the relevant Facility f determined in the Reference Scenario of the Pre-Dispatch Schedule; or

$c$ where at least one Week-Ahead Schedule has been made available to Market Participants that contains Dispatch Interval DI within a Trading Interval, then the total MW quantity of energy scheduled for dispatch in the Trading Interval for the relevant Facility f determined in the Reference Scenario of the Week-Ahead Schedule; or

$d$ otherwise, zero.

7.13A.3. ISSDCEnergy(f,DI) for each Scheduled Facility or Semi-Scheduled Facility f in Dispatch Interval DI is determined from the most recent Market Schedule made available to Market Participants after the Start Decision Cutoff from the Price-Quantity Pair for Injection for the relevant Facility f with the longest minimum time to synchronise, as specified in clause 7.4.40(g)(i)(3), as applicable:

$a$ where at least one Dispatch Schedule has been made available to Market Participants that contains Dispatch Interval DI within a Trading Interval, the total MW quantity of In-Service Capacity included in the Real-Time Market Submission for energy from the relevant Facility f in the Dispatch Interval DI; or

$b$ where at least one Pre-Dispatch Schedule has been made available to Market Participants that contains Dispatch Interval DI within a Trading Interval, the total MW quantity of In-Service Capacity included in the Real-Time Market Submission for energy from the relevant Facility f in the Trading Interval; or

$c$ where at least one Week-Ahead Schedule has been made available to Market Participants that contains Dispatch Interval DI within a Trading Interval, the total MW quantity of In-Service Capacity included in the Real-Time Market Submission for energy from the relevant Facility f in the Trading Interval; or

$d$ otherwise, zero.

Explanatory Note

Clause 7.14.1 is inserted to provide the formula for determining the Congestion Rental which AEMO uses to calculate Energy Uplift Payments in clause 9.9.9 and is required to prepare and publish under clause 7.13.1E(e).

Clause 7.14.1 is amended to clarify the relevant Facility Classes and remove unnecessary cross references.

Congestion Rental

7.14. Calculation of Congestion Rental

7.14.1. AEMO must calculate for each Registered Facility and each Dispatch Interval of a Trading Day, the Congestion Rental in respect of the full set of Network Constraints. The Congestion Rental for Registered Facility f in Dispatch Interval DI is:

$CongestionRental\left( \text{f,DI} \right)\text{=}\text{\\}\sum\_{\text{n}\text{∈}\text{N}}^{}{\text{Conge}\text{s}\text{tionCoefficient}\left( \text{f,n,DI} \right)\text{\\}\text{×}\text{\\}\text{Mar}\text{g}\text{inalConstraintValue(n,DI)}}$

Where:

$a$ ConstraintCoefficient(f,n,DI) is the coefficient of Registered Facility f in respect of the cleared energy quantity of Registered Facility f in Network Constraint n in Dispatch Interval DI;

$b$ MarginalConstraintValue(n,DI) is the marginal value of Network Constraint n in Dispatch Interval DI; and

$c$ n∈N denotes all Network Constraints applied in Dispatch Interval DI.