MNSP_BIDOFFERPERIOD
MNSP_BIDOFFERPERIOD shows availability for 5-minute periods for a specific Bid and LinkID for the given Trading Date and period. MNSP_BIDOFFERPERIOD is a child to
MNSP_DAYOFFERand links toBIDOFFERFILETRKfor 5MS Bids.
Column Schema
LINKID
Identifier for each of the two MNSP Interconnector Links. Each link pertains to the direction from and to.
SQL Type: VARCHAR2(20)
Polars Type: str
This column is mandatory, and a primary key.
Examples:
BLNKTASBLNKVIC
OFFERDATETIME
Time this bid was processed and loaded
SQL Type: TIMESTAMP(3)
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2026/05/05 15:16:58.000
Unlike most datetime columns, this one includes a millisecond component.
e.g. 2029/03/15 00:00:00.123.
PERIODID
Period ID, 1 to 288
SQL Type: NUMBER(3,0)
Polars Type: pl.Int16
This column is mandatory, and a primary key.
Examples:
1, 288
TRADINGDATE
The trading date this bid is for
SQL Type: DATE
Polars Type: pl.Date()
This column is mandatory, and a primary key.
Example: 2026/07/02 00:00:00
Note that AEMO represents dates as datetimes with a midnight time component.
BANDAVAIL1
Availability at price band 1
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 0
BANDAVAIL2
Availability at price band 2
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Examples:
0, 100
BANDAVAIL3
Availability at price band 3
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 100
BANDAVAIL4
Availability at price band 4
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 100
BANDAVAIL5
Availability at price band 5
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 100
BANDAVAIL6
Availability at price band 6
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 100
BANDAVAIL7
Availability at price band 7
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Examples:
78, 94
BANDAVAIL8
Availability at price band 8
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 0
BANDAVAIL9
Availability at price band 9
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 0
BANDAVAIL10
Availability at price band 10
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 0
FIXEDLOAD
Fixed unit output, in MW. A value of NULL means no fixed load so the unit is dispatched according to bid and the market.
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
MAXAVAIL
Maximum planned availability MW
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 0
PASAAVAILABILITY
Allows for future use for Energy bids, being the physical plant capability including any capability potentially available within 24 hours
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 438
RAMPUPRATE
Ramp rate (MW / min) in the positive direction of flow for this MNSP link for this half-hour period
SQL Type: NUMBER(6)
Polars Type: pl.Int32
This column is not mandatory.
Example: 200
RECALL_PERIOD
The advance notice(in hours) that a Scheduled Resource requires to achieve the PASA Availability MW for this trading interval
SQL Type: NUMBER(8,3)
Polars Type: pl.Float64
This column is not mandatory.
Example: 0
New Data Timing
Generated as submissions are processed in next-day reports
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
# Dates are represented as datetimes at midnight
# e.g. "2029/03/15 00:00:00"
d_fmt = "%Y/%m/%d 00:00:00"
# for "TIMESTAMP" columns
# Note that Polars uses slightly different format strings for fractional seconds to `dt.strptime`
# e.g. "2029/03/15 00:00:00.123".
dt_ms_fmt = "%Y/%m/%d %H:%M:%S%.3f"
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("TRADINGDATE").str.strptime(pl.Date, d_fmt),
pl.col("OFFERDATETIME").str.strptime(pl.Datetime, dt_ms_fmt),
)
.cast(
{
"LINKID": str,
"PERIODID": int, # or pl.Int16
"TRADINGDATE": pl.Date(),
"BANDAVAIL1": pl.Float64,
"BANDAVAIL2": pl.Float64,
"BANDAVAIL3": pl.Float64,
"BANDAVAIL4": pl.Float64,
"BANDAVAIL5": pl.Float64,
"BANDAVAIL6": pl.Float64,
"BANDAVAIL7": pl.Float64,
"BANDAVAIL8": pl.Float64,
"BANDAVAIL9": pl.Float64,
"BANDAVAIL10": pl.Float64,
"FIXEDLOAD": pl.Float64,
"MAXAVAIL": pl.Float64,
"PASAAVAILABILITY": pl.Float64,
"RAMPUPRATE": int, # or pl.Int32
"RECALL_PERIOD": pl.Float64,
}
)
# Deduplicate
# We want one row per ['LINKID', 'OFFERDATETIME', 'PERIODID', 'TRADINGDATE']
.unique(subset=["LINKID", "OFFERDATETIME", "PERIODID", "TRADINGDATE"], keep="any")
)
Nemosis
This table is not yet available in Nemosis.
Example File
From PUBLIC_ARCHIVE_MNSP_BIDOFFERPERIOD_FILE01_202607010000.zip
| LINKID | TRADINGDATE | OFFERDATETIME | PERIODID | MAXAVAIL | FIXEDLOAD | RAMPUPRATE | BANDAVAIL1 | BANDAVAIL2 | BANDAVAIL3 | BANDAVAIL4 | BANDAVAIL5 | BANDAVAIL6 | BANDAVAIL7 | BANDAVAIL8 | BANDAVAIL9 | BANDAVAIL10 | PASAAVAILABILITY | RECALL_PERIOD |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 1 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 2 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 3 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 4 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 5 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 6 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 7 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 8 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 9 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 10 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 11 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| ... |
| C | SETP.WORLD | DVD_MNSP_BIDOFFERPERIOD | AEMO | PUBLIC | 2026/08/08 | 12:31:31 | 001786156291071 | MONTHLY_ARCHIVE | 001786156291071 | |||||||||||||
| I | BIDS | MNSP_BIDOFFERPERIOD | 2 | LINKID | TRADINGDATE | OFFERDATETIME | PERIODID | MAXAVAIL | FIXEDLOAD | RAMPUPRATE | BANDAVAIL1 | BANDAVAIL2 | BANDAVAIL3 | BANDAVAIL4 | BANDAVAIL5 | BANDAVAIL6 | BANDAVAIL7 | BANDAVAIL8 | BANDAVAIL9 | BANDAVAIL10 | PASAAVAILABILITY | RECALL_PERIOD |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 1 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 2 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 3 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 4 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 5 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 6 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 7 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 8 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 9 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 10 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| D | BIDS | MNSP_BIDOFFERPERIOD | 2 | BLNKTAS | 2026/07/02 00:00:00 | 2026/05/05 15:17:09.000 | 11 | 0 | 200 | 0 | 100 | 100 | 100 | 100 | 100 | 94 | 0 | 0 | 0 | 438 | 0 | |
| ... | ||||||||||||||||||||||
| C | END OF REPORT | 1003 |
LINKID,TRADINGDATE,OFFERDATETIME,PERIODID,MAXAVAIL,FIXEDLOAD,RAMPUPRATE,BANDAVAIL1,BANDAVAIL2,BANDAVAIL3,BANDAVAIL4,BANDAVAIL5,BANDAVAIL6,BANDAVAIL7,BANDAVAIL8,BANDAVAIL9,BANDAVAIL10,PASAAVAILABILITY,RECALL_PERIOD
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",1,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",2,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",3,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",4,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",5,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",6,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",7,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",8,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",9,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",10,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",11,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
...
C,SETP.WORLD,DVD_MNSP_BIDOFFERPERIOD,AEMO,PUBLIC,2026/08/08,12:31:31,001786156291071,MONTHLY_ARCHIVE,001786156291071
I,BIDS,MNSP_BIDOFFERPERIOD,2,LINKID,TRADINGDATE,OFFERDATETIME,PERIODID,MAXAVAIL,FIXEDLOAD,RAMPUPRATE,BANDAVAIL1,BANDAVAIL2,BANDAVAIL3,BANDAVAIL4,BANDAVAIL5,BANDAVAIL6,BANDAVAIL7,BANDAVAIL8,BANDAVAIL9,BANDAVAIL10,PASAAVAILABILITY,RECALL_PERIOD
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",1,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",2,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",3,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",4,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",5,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",6,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",7,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",8,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",9,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",10,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
D,BIDS,MNSP_BIDOFFERPERIOD,2,BLNKTAS,"2026/07/02 00:00:00","2026/05/05 15:17:09.000",11,0,,200,0,100,100,100,100,100,94,0,0,0,438,0
...
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 3 of 2021. The most recent available data is month 7 of 2026.
Every month in between has a file. (No gaps.)
Warning
The filenames of zips may not correspond to the tables. These can be mixed up with MNSP_PEROFFER. Check column 2 and 3 inside the CSV against REPORT_NAME and REPORT_SUBTYPE to be sure. I have already done this for you, and listed all URLs in this metadata file.
Data Size
Each year of data is approximately 169 KB when zipped, 2 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 | Undisclosed |
|---|---|---|---|
| BIDS | MNSP_BIDOFFERPERIOD | 1 | |
| BIDS | MNSP_BIDOFFERPERIOD | 2 | |
| OFFER | MNSP_BIDOFFERPERIOD | 1 | ⚠️ |
Warning
Some of these file mappings are not in the published PDR Loader configuration file, even though files for this table exist with those metadata values. Mappings marked with ⚠️ have been added by me after manually inspecting those files.
This means that the CSV files start with metadata columns:
or
or
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: BIDS