MCC_CASESOLUTION
Top level table for each MCC dispatch rerun process. Note there will be one record for each dispatch interval
Column Schema
RUN_DATETIME
5-minute Dispatch Run identifier
SQL Type: DATE
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/09/01 00:05:00
New Data Timing
Each dispatch run
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("RUN_DATETIME").str.strptime(pl.Datetime, dt_s_fmt),
)
# Deduplicate
# We want one row per ['RUN_DATETIME']
.unique(subset=["RUN_DATETIME"], keep="any")
)
Nemosis
This table is not yet available in Nemosis.
Example File
From PUBLIC_ARCHIVE_MCC_CASESOLUTION_FILE01_202609010000.zip
| RUN_DATETIME |
| 2026/09/01 00:05:00 |
| 2026/09/01 00:10:00 |
| 2026/09/01 00:15:00 |
| 2026/09/01 00:20:00 |
| 2026/09/01 00:25:00 |
| 2026/09/01 00:30:00 |
| 2026/09/01 00:35:00 |
| 2026/09/01 00:40:00 |
| 2026/09/01 00:45:00 |
| 2026/09/01 00:50:00 |
| 2026/09/01 00:55:00 |
| ... |
| C | SETP.WORLD | DVD_MCC_CASESOLUTION | AEMO | PUBLIC | 2026/10/09 | 15:53:31 | 001791525211062 | MONTHLY_ARCHIVE | 001791525211062 |
| I | MCC | CASESOLUTION | 1 | RUN_DATETIME | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:05:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:10:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:15:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:20:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:25:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:30:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:35:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:40:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:45:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:50:00 | |||||
| D | MCC | CASESOLUTION | 1 | 2026/09/01 00:55:00 | |||||
| ... | |||||||||
| C | END OF REPORT | 1003 |
C,SETP.WORLD,DVD_MCC_CASESOLUTION,AEMO,PUBLIC,2026/10/09,15:53:31,001791525211062,MONTHLY_ARCHIVE,001791525211062
I,MCC,CASESOLUTION,1,RUN_DATETIME
D,MCC,CASESOLUTION,1,"2026/09/01 00:05:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:10:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:15:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:20:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:25:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:30:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:35:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:40:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:45:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:50:00"
D,MCC,CASESOLUTION,1,"2026/09/01 00:55:00"
...
C,"END OF REPORT",1003
Availability
Visibility: Private & Public Next-Day
This table is in the public monthly MMSDM archive.
I have collated the list of all those files into one place, in this CSV metadata file. (Columns year, month, url, compressed_size in bytes).
The earliest available data is month 1 of 2015. The most recent available data is month 9 of 2026.
Every month in between has a file. (No gaps.)
Data Size
Each year of data is approximately 286 KB when zipped, 3 MB as unzipped CSV.
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.
| Report Name | Report Subtype | Version |
|---|---|---|
| MCC | CASESOLUTION | 1 |
This means that the CSV files start with metadata columns:
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: MCC_DISPATCH