New

Explore RenewMap: Operational Insights

Pages

Data sources & coverage

Where RenewMap's operational metrics come from, how often they update, and which regions, units and network equipment are covered.

This page is the reference sheet for the data behind Operational Insights. For the derivations themselves, start at the Operational metrics overview.

Sources

All the operational data in Operational Insights is derived from data published by the Australian Energy Market Operator (AEMO) via NEMWEB. Specifically:

  • unit-level operational telemetry, dispatch outcomes and declared availability
  • AEMO’s own forecast of what each semi-scheduled unit could have produced from the resource available
  • regional dispatch prices
  • unit registration details, including dispatch classification and loss factors
  • transmission equipment flow and rating measurements
  • network constraint definitions and their solved values, including marginal values

Update frequency and latency

Operational metrics are built from AEMO’s settled monthly record rather than its live feeds, so operational history runs to the end of the previous month, and the newest month appears partway through the current one.

Coverage

Market. The National Electricity Market only: Queensland, New South Wales (including the ACT), Victoria, South Australia and Tasmania. The Wholesale Electricity Market in Western Australia, the Northern Territory systems and the New Zealand market are not currently covered for operational data.

History. Operational metrics begin in January 2022 and run to the end of the previous month. Static project and network data extends much further back.

Resolution. 30 minutes derived from 5-minute dispatch intervals.

Projects and units. Generation and Load metrics only need published unit telemetry, which AEMO collects from a wider set of units than it centrally dispatches, including a number of non-scheduled generators. Curtailment and Revenue need an actual dispatch solution for the interval, which only exists for registered scheduled, semi-scheduled and bidirectional units. So a non-scheduled unit can show Generation with Curtailment and Revenue both blank, and a project with no telemetry at all (e.g. small projects) shows nothing.

Network equipment. Metrics exist only for transmission equipment that has published operational telemetry. AEMO publish some line flow data, but there is no public feed of every transmission line flow in the NEM. Coverage is consequently broad across the parts of the network that matter most for market outcomes. A single transmission line may combine several measurement points; line-level figures take the most conservative reading across them.

Timestamps and time zones

Two conventions apply everywhere in this dataset:

  • Period-start labelling. A half hour is labelled with the time it begins. The 14:00 period covers 14:00 to 14:30, and contains the six dispatch intervals AEMO labels 14:05 through 14:30. AEMO’s own files label intervals by their end time.
  • Market time. All timestamps are Australian Eastern Standard Time (UTC+10) with no daylight saving adjustment, all year, matching AEMO’s market time.

Known limitations

Each metric page carries its own caveats in full. Some important ones:

  • Spot only. Revenue excludes contracted revenue, FCAS, certificates and all costs. It is not project revenue. See Revenue & Missed Revenue.
  • Curtailment mixes network and economic causes. Both are reported together, and the split isn’t currently published. See Curtailment.
  • Network coverage is partial. Transmission equipment with no published telemetry appears nowhere, and that set doesn’t follow the network map. See Coverage.
  • Thermal constraints only. Voltage, transient stability, oscillatory and system strength limits are excluded from the headroom and binding metrics, and in some corridors those are the limits that actually bind. See Constrained Headroom.
  • Constraint-to-equipment matching is RenewMap’s own. AEMO doesn’t publish a mapping from constraints to specific lines, so we derive one. See Constrained Headroom.

Common questions

Why does RenewMap stop at the end of last month?

Because these metrics are built from AEMO’s monthly archive files, which are published after the month closes.

When exactly does the new month appear?

Expect the previous month to become available about half way through the following month.

Is this real-time data?

No. It’s a complete historical record, refreshed monthly.

Is anything modelled or simulated?

No. Dispatch outcomes, prices, telemetry and constraint solutions are all AEMO’s published values, used as published. Nothing is re-solved, re-forecast or simulated.

Does RenewMap use pre-dispatch or forecast data?

No, other than AEMO’s resource forecast for semi-scheduled units, which is what makes Curtailment measurable. Everything else is actual dispatch: what happened, not what was expected to happen.

Can I get 5-minute data instead of half-hourly?

Not currently. Half-hourly matches the market’s own trading interval convention. If 5-minute resolution is important to your work, tell us.

Why is there no data for Western Australia?

The WEM is a separate market with a different dispatch process and different data publications. These metrics are derived from NEM data.

Why does history start in January 2022?

AEMO moved from 30 minute to 5 minute settlement periods in late 2021, so 2022 was a logical starting point.

Something looks wrong. What now?

Let us know!

Last updated 2 August 2026