Skip to content

DISPATCHCASE_OCD

DISPATCHCASE_OCD shows the key data to indicate when an over-constrained dispatch (OCD) re-run actually occurred. One record per over-constrained dispatch interval.

Deprecation Warning

This table is in the HISTORICAL TABLES package, so is likely deprecated.

The DISPATCHCASE_OCD data is public.

Source

The occurrences of Over-constrained dispatch (OCD) or binding intra-regional network constraints (BNC) re-runs are ad hoc, with significant dependencies on the configuration or events in the physical power system. Potentially updated every 5 minutes.

Volume

Rows per day: ~2

Mb per month: \<1

The estimates on the number of rows are based on a 1% occurrence rate for OCD runs.

Note

Due to the close dependency with the dispatch process, the OCD and BNC data models use a “CaseSolution” key table in the same manner as the DISPATCHCASESOLUTION table.

Column Schema

SETTLEMENTDATE

End date and time of the dispatch interval

Warning

Despite what the name suggests, this is a datetime, not a date.

SQL Type: DATE Polars Type: pl.Datetime()

This column is mandatory, and a primary key.

Example: 2026/01/20 00:05:00

RUNNO

Dispatch run no; always 1

This column only ever takes one value: 1

(The SQL type is NUMBER(3,0).)

AEMO marked this column as mandatory, and a primary key. However, since it only ever takes one value, you can ignore it.

LASTCHANGED

Last date and time record changed

For more information, see the dedicated documentation page.

SQL Type: DATE Polars Type: pl.Datetime()

This column is not mandatory.

Example: 2026/01/20 00:05:00

New Data Timing

Adhoc, potentially every 5 minutes

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("SETTLEMENTDATE", "LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
    )
    .cast({"RUNNO": pl.Enum(["1"])})
    # Drop deprecated/unused columns
    .drop("RUNNO")
    # Deduplicate
    # We want one row per ['RUNNO', 'SETTLEMENTDATE']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["RUNNO", "SETTLEMENTDATE"], keep="last")
)

Nemosis

This table is not yet available in Nemosis.

Availability

AEMO's documentation states that this table's visibility is "Public". However, it is not available in the public monthly MMSDM archive. AEMO probably call this public because it is available to all market participants over private FTP.

There is a chance that is is still public to non-participants. It may only be available for some months; or (rarely) it may be available in a non-standard location.

Deduplication and PDR Loader Configuration

The primary keys are:

The transaction type is "insert", which means that you will usually not see duplicate data. If you do, you can deduplicate based on the primary keys, without sorting first. Rows from different files with the same primary keys should have the same values.

PDR Loader configuration is:

Report Name Report Subtype Version
DISPATCHOCD CASE 1

This means that the CSV files start with metadata columns:

I,DISPATCHOCD,CASE,1,...
D,DISPATCHOCD,CASE,1,...

Indexes

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: HISTORICAL TABLES