System frequency holds up during VRE dispatch availability issues
Widespread use of SCADA-based availability forecasts on 10 November 2026 didn't coincide with large frequency excursions.
Widespread use of SCADA-based availability forecasts on 10 November 2026 didn't coincide with large frequency excursions.
Yesterday we noted some strange (apparent) output pattern implied in SCADA data for Millmerran 2 (on Fri 9th Oct 2026). Today we take a closer look at what appears to be a SCADA Data Glitch, via 'next day public' data.
In this 6th article relating to the data glitch triggered frequency excursion on Wednesday 5th August 2026, we take another look at interconnectors, and start compiling a sequence of events.
A sudden drop in NSW demand was followed by apparent recovery in the next interval.
My ez2view ‘Mobile App’ has alerted me to a strange aberration in ‘Market Demand’ in both VIC and NSW regions, on Sunday evening 19th July 2026 … but the sum of the effects is best visualised by this NEMwatch snapshot at the 18:50.
On Friday 29th May 2026, the AEMO alsodeclared Scheduling Errors (together anointed number 76), with respect to the joint glitches on Thu 6th Nov 2025 and Tue 11th Nov 2025.
Yesterday one of our team members noted something strange at Wellington North Solar Farm ... here we take a quick look at the last few days and see a few things.
About the AEMO’s Reviewable Operating Incident Report ‘Self-forecasting errors and frequency excursion on 19 August 2025’.
We use a chart to see how semi-scheduled unit availabilities changed their origin. With interruptions to SCADA across NSW, many of the inputs that an availability forecast depends on could have been impacted.
One feature of a market suspension is the possibility for suspension pricing, which happened in this case. Did it influence energy offers?
A number of our ez2view 'large change in demand' alerts have triggered this afternoon Monday 23rd March 2026 with respect to NSW. But what's a 'real' change and what's 'phantom' (with the SCADA issues)?
Yesterday afternoon/evening (Tuesday 10th March 2026) the AEMO experienced a significant glitch in operations. I’ve posted this short note here to provide a more easily-accessible permanent record that we (and others) might refer back to later…
Adding to the list of articles we've collated about the frequency disturbance on Tuesday 19th August 2025, we're copying in what AEMO published in its 2025 Q3 monitoring report about the glitch.
In this article we take another step in trying to understand the source of the gremlins (on Thu 6th Nov 2025 and Tue 11th Nov 2025) that seemed to infect the dispatch process - inflating VIC 'Market Demand' with 'phantom' demand and driving frequency higher.
Following two instances of apparent data glitches (injecting 'phantom demand' and) driving frequency high, here's a collation of some other times (we've written about) where similar has happened.
In what seems to be a repeat of what happened last week Thursday 6th November 2025, some strange (and large) changes in 'Market Demand in Victoria appear to have driven a frequency excursion on Tuesday morning 11th November 2025
Today, we have the advantage of ‘next day public’ data, so are able to peel some more layers of the onion (in this article 'Dispatch Error') - with respect to the significant Frequency Spike on Thursday 6th November 2025 (which appears due to some gremlins...
This afternoon we saw mainland frequency briefly step above its normal operating band for approximately 20 minutes — potentially the result of a data glitch. In this quick piece, we unpack some market dynamics while it unfolded.