INTERMITTENT_P5_PRED
Unconstrained Intermittent Generation Forecasts (UIGF) for 5-Minute Pre-dispatch. AEMO plans to remove this table in a Data Model version release after 5.6.
Column Schema
DUID
DUID (or Area for non-scheduled) where this forecast applies
Warning
This column may contain funny characters such as / (slash) or # (hash). This may break hive-style partitioning.
For more information, see the dedicated documentation page.
SQL Type: VARCHAR2(20)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
Example: W/HOE#2
FORECAST_PRIORITY
Unsuppressed forecasts with higher priority values are used in 5-Minute Predispatch in preference to unsuppressed forecasts with lower priority values
SQL Type: NUMBER(10,0)
Polars Type: pl.Int64
This column is mandatory, and a primary key.
INTERVAL_DATETIME
Interval within the current RUN_DATETIME where this forecast applies (dispatch interval ending)
SQL Type: DATE
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/01/20 00:05:00
OFFERDATETIME
Date and Time when this forecast submission was loaded
SQL Type: DATE
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/01/20 00:05:00
ORIGIN
Origin of this forecast (PARTICIPANTID, AWEFS/ASEFS, or another vendor)
SQL Type: VARCHAR2(20)
Polars Type: str
This column is mandatory, and a primary key.
RUN_DATETIME
Date and Time of the first interval of 5-Minute Predispatch where the forecast applies (dispatch interval ending)
SQL Type: DATE
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/01/20 00:05:00
FORECAST_MEAN
Forecast MW value for this interval_DateTime
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
FORECAST_POE10
Forecast 10% POE MW value for this interval_DateTime
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
FORECAST_POE50
Forecast 50% POE MW value for this interval_DateTime.
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
FORECAST_POE90
Forecast 90% POE MW value for this interval_DateTime
SQL Type: NUMBER(18,8)
Polars Type: pl.Float64
This column is not mandatory.
New Data Timing
Publication of 5-Minute Pre-dispatch solution. Data includes all valid forecasts for that interval
Code Examples
Polars
Casting is enums, categoricals etc is not essential, but may speed up parsing.
Swapping int for pl.UInt16, pl.Int32 would also speed up parsing. However some of the datatypes are inferred, so they may be wrong.
This code deduplicates for you. Deduplication is normally only required across multiple months.
This code assumes that all columns are present, which may not be true for older files.
import polars as pl
import polars.selectors as cs
# e.g. "2029/03/15 00:05:00"
dt_s_fmt = "%Y/%m/%d %H:%M:%S"
csv_paths = ["SOMEFILE.CSV", "OTHERFILE.CSV"]
lf = (
pl.concat(
[
pl.scan_csv(
csv_path, # must be unzipped beforehand
skip_rows=1, # skip the header
infer_schema=False, # much faster
)
.filter(cs.by_index(0) == "D") # drop the footer
.select(~cs.by_index(range(4))) # drop metadata columns
for csv_path in csv_paths
],
how="diagonal_relaxed",
)
.with_columns(
pl.col("INTERVAL_DATETIME", "OFFERDATETIME", "RUN_DATETIME").str.strptime(
pl.Datetime, dt_s_fmt
),
)
.cast(
{
"DUID": pl.Categorical,
"FORECAST_PRIORITY": int, # or pl.Int64
"ORIGIN": str,
"FORECAST_MEAN": pl.Float64,
"FORECAST_POE10": pl.Float64,
"FORECAST_POE50": pl.Float64,
"FORECAST_POE90": pl.Float64,
}
)
# Deduplicate
# We want one row per ['DUID', 'FORECAST_PRIORITY', 'INTERVAL_DATETIME', 'OFFERDATETIME', 'ORIGIN', 'RUN_DATETIME']
.unique(
subset=[
"DUID",
"FORECAST_PRIORITY",
"INTERVAL_DATETIME",
"OFFERDATETIME",
"ORIGIN",
"RUN_DATETIME",
],
keep="any",
)
)
Nemosis
This table is not yet available in Nemosis.
Availability
Visibility: Private
This table is not available in the public monthly MMSDM archive. Is is only available to registered market participants over FTP inside a VPN.
Deduplication and PDR Loader Configuration
The primary keys are:
PDR Loader configuration does not mention this table, so it is unclear how to choose which row to keep when there are multiple rows for a given set of primary keys.
Look at the data and use your best judgement.
Links
This page as JSON (schema documented here, but may change)
Download a JSON Schema specification for this table.
Official AEMO schema documentation
Other Information
Package: DEMAND_FORECASTS