A quick and short post, which will really be Part 1 (time permitting) as this event has prompted a couple questions we’d like to explore as time permits.
Our ‘Notifications’ widget in ez2view triggered this morning at 03:06 (NEM time) on Thursday 2nd April 2026 to alert us to a trip of the Kogan Creek coal unit (which was, for a long period, the largest unit in the NEM):
![]()
Here’s a collage of three widgets in an ez2view window (including the ‘Unit Dashboard’ widget focused on KPP_1) that is time-travelled back to the 03:05 dispatch interval (NEM time) , and just manages to capture the trip in the end-of-interval value:
… and here’s the same window advanced to the 03:10 dispatch interval (NEM time) to capture the rebid that the AEMO received at 03:03 (NEM time) reflecting the trip:
… and here’s that same window, reverted to ‘Real-Time’ mode and currently capturing the 07:35 Dispatch Interval (NEM time):
I’ve increased the backwards and forwards time horizon in the ‘Unit Dashboard’ widget in order to capture:
1) The trip, now >4 hours earlier; and
2) The current expectation in PD/ST PASA that the unit availability will step back up at ~ 12:00 (NEM time) today.
We’ll come back to this (as time permits), not to look at the unit, but rather system effects with such a large trip.

Be the first to comment on "(Close to) Full Load trip of Kogan Creek early on Thursday 2nd April 2026"