Skip to content

LOSSMODEL

LOSSMODEL sets out segment breakpoints in loss model for each interconnector, used by LP Solver modelling of interconnector flows.

LOSSMODEL data is public, so is available to all participants.

Source

LOSSMODEL only changes annually, when there is a change in the interconnector.

Column Schema

EFFECTIVEDATE

Calendar date data set is effective

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

This column is mandatory, and a primary key.

Example: 1998/07/01 00:00:00

Note that AEMO represents dates as datetimes with a midnight time component.

INTERCONNECTORID

Interconnector identifier

SQL Type: VARCHAR2(10) Polars Type: pl.Categorical

This column is mandatory, and a primary key.

Examples:

  • N-Q-MNSP1
  • SNOWY1
  • V-SA
  • V-SN

LOSSSEGMENT

Segment Identifier (1 to 80 at present)

SQL Type: NUMBER(6,0) Polars Type: pl.Int32

This column is mandatory, and a primary key.

Examples: 1, 81

VERSIONNO

Version number within effective date

SQL Type: NUMBER(3,0) Polars Type: pl.UInt16

This column is mandatory, and a primary key.

Examples: 1, 2

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: 2003/11/25 15:41:18

MWBREAKPOINT

MW Value for segment

SQL Type: NUMBER(6,0) Polars Type: pl.Int32

This column is not mandatory.

Examples: 0, -5, 5, -2125, 3813

LOSSFACTOR

Not used

SQL Type: NUMBER(16,6) Polars Type: pl.Float64

This column is unused.

PERIODID

Not used

SQL Type: VARCHAR2(20) Polars Type: str

This column is unused.

New Data Timing

Annually, when there is a change in the interconnector

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"

# Dates are represented as datetimes at midnight

d_fmt = "%Y/%m/%d 00:00:00"

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("LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
        pl.col("EFFECTIVEDATE").str.strptime(pl.Date, d_fmt),
    )
    .cast(
        {
            "EFFECTIVEDATE": pl.Date(),
            "INTERCONNECTORID": pl.Categorical,
            "LOSSSEGMENT": int,  # or pl.Int32
            "VERSIONNO": int,  # or pl.UInt16
            "MWBREAKPOINT": int,  # or pl.Int32
            "LOSSFACTOR": pl.Float64,
            "PERIODID": str,
        }
    )
    # Drop deprecated/unused columns
    .drop("LOSSFACTOR", "PERIODID")
    # Deduplicate
    # We want one row per ['EFFECTIVEDATE', 'INTERCONNECTORID', 'LOSSSEGMENT', 'VERSIONNO']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(
        subset=["EFFECTIVEDATE", "INTERCONNECTORID", "LOSSSEGMENT", "VERSIONNO"],
        keep="last",
    )
)

Nemosis

from nemosis import dynamic_data_compiler

df = dynamic_data_compiler(
    '2024/01/01 00:00:00',
    '2024/01/31 00:00:00',
    "LOSSMODEL",
    "data/"
)

Nemosis only includes a subset of columns by default, as an optimisation. (i.e. the commonly used columns.) To include others:

from nemosis import defaults

defaults.table_columns["LOSSMODEL"] += ["LASTCHANGED", "LOSSFACTOR", "PERIODID"]
df = dynamic_data_compiler(...)

Example File

From PUBLIC_ARCHIVE_LOSSMODEL_FILE01_202609010000.zip

EFFECTIVEDATEVERSIONNOINTERCONNECTORIDPERIODIDLOSSSEGMENTMWBREAKPOINTLOSSFACTORLASTCHANGED
1998/07/01 00:00:002V-SN2-14482003/11/25 15:41:18
1998/07/01 00:00:002SNOWY11-8512003/11/25 15:41:18
1998/07/01 00:00:002SNOWY12-7762003/11/25 15:41:18
1998/07/01 00:00:002SNOWY13-7022003/11/25 15:41:18
1998/07/01 00:00:002SNOWY14-6282003/11/25 15:41:18
1998/07/01 00:00:002SNOWY15-5542003/11/25 15:41:18
1998/07/01 00:00:002SNOWY16-4802003/11/25 15:41:18
1998/07/01 00:00:002SNOWY17-4062003/11/25 15:41:18
1998/07/01 00:00:002SNOWY18-3322003/11/25 15:41:18
1998/07/01 00:00:002SNOWY19-2582003/11/25 15:41:18
1998/07/01 00:00:002SNOWY110-1842003/11/25 15:41:18
...

CSETP.WORLDDVD_LOSSMODELAEMOPUBLIC2026/10/0915:53:05001791525185564MONTHLY_ARCHIVE001791525185564
IMARKET_CONFIGLOSSMODEL1EFFECTIVEDATEVERSIONNOINTERCONNECTORIDPERIODIDLOSSSEGMENTMWBREAKPOINTLOSSFACTORLASTCHANGED
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002V-SN2-14482003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY11-8512003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY12-7762003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY13-7022003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY14-6282003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY15-5542003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY16-4802003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY17-4062003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY18-3322003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY19-2582003/11/25 15:41:18
DMARKET_CONFIGLOSSMODEL11998/07/01 00:00:002SNOWY110-1842003/11/25 15:41:18
...
CEND OF REPORT1003

EFFECTIVEDATE,VERSIONNO,INTERCONNECTORID,PERIODID,LOSSSEGMENT,MWBREAKPOINT,LOSSFACTOR,LASTCHANGED
"1998/07/01 00:00:00",2,V-SN,,2,-1448,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,1,-851,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,2,-776,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,3,-702,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,4,-628,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,5,-554,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,6,-480,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,7,-406,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,8,-332,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,9,-258,,"2003/11/25 15:41:18"
"1998/07/01 00:00:00",2,SNOWY1,,10,-184,,"2003/11/25 15:41:18"
...
C,SETP.WORLD,DVD_LOSSMODEL,AEMO,PUBLIC,2026/10/09,15:53:05,001791525185564,MONTHLY_ARCHIVE,001791525185564
I,MARKET_CONFIG,LOSSMODEL,1,EFFECTIVEDATE,VERSIONNO,INTERCONNECTORID,PERIODID,LOSSSEGMENT,MWBREAKPOINT,LOSSFACTOR,LASTCHANGED
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,V-SN,,2,-1448,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,1,-851,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,2,-776,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,3,-702,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,4,-628,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,5,-554,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,6,-480,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,7,-406,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,8,-332,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,9,-258,,"2003/11/25 15:41:18"
D,MARKET_CONFIG,LOSSMODEL,1,"1998/07/01 00:00:00",2,SNOWY1,,10,-184,,"2003/11/25 15:41:18"
...
C,"END OF REPORT",1003

Availability

Visibility: Public

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 1 MB when zipped, 13 MB as unzipped CSV.

Deduplication and PDR Loader Configuration

The primary keys are:

The transaction type is "INSERT-UPDATE", which means that you will likely see duplicate data with different values.

You should deduplicate by sorting based on LASTCHANGED, within each group of primary keys.

PDR Loader configuration is:

Report Name Report Subtype Version
MARKET_CONFIG LOSSMODEL 1

This means that the CSV files start with metadata columns:

I,MARKET_CONFIG,LOSSMODEL,1,...
D,MARKET_CONFIG,LOSSMODEL,1,...

ROW_FILTER_TYPE is LASTCHANGED

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