DISPATCH_MR_SCHEDULE_TRK

DISPATCH_MR_SCHEDULE_TRK records the Mandatory Restrictions Acceptance Schedule applied to this dispatch interval for this region. DISPATCH_MR_SCHEDULE_TRK is populated by the Dispatch process and records the MR Offer Stack applied in each dispatch interval. DISPATCH_MR_SCHEDULE_TRK is used by Settlements to calculate payments according to the correct MR offer stack.

DISPATCH_MR_SCHEDULE_TRK data is public to all participants.

Source

DISPATCH_MR_SCHEDULE_TRK updates are ad hoc.

Volume

2 rows per year.

Column Schema

REGIONID

Unique RegionID; Key reference to MR_Event_Schedule

For more information, see the dedicated documentation page.

The SQL type is VARCHAR2(10). This is actually a factor/enum, with values:

• QLD1

• VIC1

• TAS1

• NSW1

• SA1

• SNOWY1

This column is mandatory, and a primary key.

SETTLEMENTDATE

Date 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

LASTCHANGED

Date and time the record was last inserted/modified

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

MR_DATE

Mandatory Restriction date; Key reference to MR_Event_Schedule table

Warning

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

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

This column is not mandatory.

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

VERSION_DATETIME

Date Time the MR acceptance stack was created; Key reference to MR_Event_Schedule table

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

This column is not mandatory.

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

New Data Timing

Ad hoc

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", "MR_DATE", "VERSION_DATETIME"
        ).str.strptime(pl.Datetime, dt_s_fmt),
    )
    .cast({"REGIONID": pl.Enum(["QLD1", "VIC1", "TAS1", "NSW1", "SA1", "SNOWY1"])})
    # Deduplicate
    # We want one row per ['REGIONID', 'SETTLEMENTDATE']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["REGIONID", "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:

• REGIONID

• SETTLEMENTDATE

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
DISPATCH	MR_SCHEDULE_TRK	1

This means that the CSV files start with metadata columns:

I,DISPATCH,MR_SCHEDULE_TRK,1,...
D,DISPATCH,MR_SCHEDULE_TRK,1,...

Indexes

• LASTCHANGED

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: DISPATCH

Copy as Markdown