Skip to content

SETCFG_PARTICIPANT_MPF

SETCFG_PARTICIPANT_MPF shows the Market Participation Factors (MPF) for each participant for each connection point. The MPF values are used to determine recovery amounts for regulation FCAS.

SETCFG_PARTICIPANT_MPF data is available to all participants.

Volume

Approximately 20,000 records per year

Column Schema

CONNECTIONPOINTID

Connection point identifier

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

This column is mandatory, and a primary key.

Examples:

  • NASSHU02
  • QASSHU01
  • QSPS1S
  • QSPT1S
  • QWSB3W
  • STB31T
  • STET1T
  • VJL21W

EFFECTIVEDATE

Effective date of the MPF data

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

This column is mandatory, and a primary key.

Example: 2026/09/08 00:00:00

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

PARTICIPANTCATEGORYID

Participant Category

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

This column is mandatory, and a primary key.

Example: GENERATOR

PARTICIPANTID

Participant identifier

For more information, see the dedicated documentation page.

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

This column is mandatory, and a primary key.

Examples:

  • DIAMTEMP
  • SHUBMASP
  • SNODE1
  • TBBESS
  • WANDBESS
  • WOORBESS

VERSIONNO

Version number of the MPF data

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

This column is mandatory, and a primary key.

Example: 1

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/09/04 15:07:18

MPF

Market Participation Factor

SQL Type: NUMBER(15,5) Polars Type: pl.Float64

This column is not mandatory.

Example: 0

New Data Timing

When Market Participation Factors (MPF) data is updated

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(
        {
            "CONNECTIONPOINTID": pl.Categorical,
            "EFFECTIVEDATE": pl.Date(),
            "PARTICIPANTCATEGORYID": pl.Categorical,
            "PARTICIPANTID": pl.Categorical,
            "VERSIONNO": int,  # or pl.UInt16
            "MPF": pl.Float64,
        }
    )
    # Deduplicate
    # We want one row per ['CONNECTIONPOINTID', 'EFFECTIVEDATE', 'PARTICIPANTCATEGORYID', 'PARTICIPANTID', 'VERSIONNO']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(
        subset=[
            "CONNECTIONPOINTID",
            "EFFECTIVEDATE",
            "PARTICIPANTCATEGORYID",
            "PARTICIPANTID",
            "VERSIONNO",
        ],
        keep="last",
    )
)

Nemosis

This table is not yet available in Nemosis.

Example File

From PUBLIC_ARCHIVE_SETCFG_PARTICIPANT_MPF_FILE01_202609010000.zip

PARTICIPANTIDEFFECTIVEDATEVERSIONNOPARTICIPANTCATEGORYIDCONNECTIONPOINTIDMPFLASTCHANGED
SHUBMASP2026/09/08 00:00:001GENERATORNASSHU0202026/09/04 15:07:18
SHUBMASP2026/09/08 00:00:001GENERATORQASSHU0102026/09/04 15:07:18
TBBESS2026/09/15 00:00:001GENERATORSTB31T02026/09/11 15:07:33
WOORBESS2026/09/15 00:00:001GENERATORVJL21W02026/09/11 15:39:12
DIAMTEMP2026/09/18 00:00:001GENERATORSTET1T02026/09/16 14:52:47
SNODE12026/09/25 00:00:001GENERATORQSPS1S02026/09/23 09:25:40
SNODE12026/09/25 00:00:001GENERATORQSPT1S02026/09/23 09:25:40
WANDBESS2026/09/29 00:00:001GENERATORQWSB3W02026/09/25 16:30:04

CSETP.WORLDDVD_SETCFG_PARTICIPANT_MPFAEMOPUBLIC2026/10/0916:31:15001791527475886MONTHLY_ARCHIVE001791527475886
ISETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1PARTICIPANTIDEFFECTIVEDATEVERSIONNOPARTICIPANTCATEGORYIDCONNECTIONPOINTIDMPFLASTCHANGED
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1SHUBMASP2026/09/08 00:00:001GENERATORNASSHU0202026/09/04 15:07:18
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1SHUBMASP2026/09/08 00:00:001GENERATORQASSHU0102026/09/04 15:07:18
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1TBBESS2026/09/15 00:00:001GENERATORSTB31T02026/09/11 15:07:33
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1WOORBESS2026/09/15 00:00:001GENERATORVJL21W02026/09/11 15:39:12
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1DIAMTEMP2026/09/18 00:00:001GENERATORSTET1T02026/09/16 14:52:47
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1SNODE12026/09/25 00:00:001GENERATORQSPS1S02026/09/23 09:25:40
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1SNODE12026/09/25 00:00:001GENERATORQSPT1S02026/09/23 09:25:40
DSETTLEMENT_CONFIGSETCFG_PARTICIPANT_MPF1WANDBESS2026/09/29 00:00:001GENERATORQWSB3W02026/09/25 16:30:04
CEND OF REPORT11

PARTICIPANTID,EFFECTIVEDATE,VERSIONNO,PARTICIPANTCATEGORYID,CONNECTIONPOINTID,MPF,LASTCHANGED
SHUBMASP,"2026/09/08 00:00:00",1,GENERATOR,NASSHU02,0,"2026/09/04 15:07:18"
SHUBMASP,"2026/09/08 00:00:00",1,GENERATOR,QASSHU01,0,"2026/09/04 15:07:18"
TBBESS,"2026/09/15 00:00:00",1,GENERATOR,STB31T,0,"2026/09/11 15:07:33"
WOORBESS,"2026/09/15 00:00:00",1,GENERATOR,VJL21W,0,"2026/09/11 15:39:12"
DIAMTEMP,"2026/09/18 00:00:00",1,GENERATOR,STET1T,0,"2026/09/16 14:52:47"
SNODE1,"2026/09/25 00:00:00",1,GENERATOR,QSPS1S,0,"2026/09/23 09:25:40"
SNODE1,"2026/09/25 00:00:00",1,GENERATOR,QSPT1S,0,"2026/09/23 09:25:40"
WANDBESS,"2026/09/29 00:00:00",1,GENERATOR,QWSB3W,0,"2026/09/25 16:30:04"
C,SETP.WORLD,DVD_SETCFG_PARTICIPANT_MPF,AEMO,PUBLIC,2026/10/09,16:31:15,001791527475886,MONTHLY_ARCHIVE,001791527475886
I,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,PARTICIPANTID,EFFECTIVEDATE,VERSIONNO,PARTICIPANTCATEGORYID,CONNECTIONPOINTID,MPF,LASTCHANGED
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,SHUBMASP,"2026/09/08 00:00:00",1,GENERATOR,NASSHU02,0,"2026/09/04 15:07:18"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,SHUBMASP,"2026/09/08 00:00:00",1,GENERATOR,QASSHU01,0,"2026/09/04 15:07:18"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,TBBESS,"2026/09/15 00:00:00",1,GENERATOR,STB31T,0,"2026/09/11 15:07:33"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,WOORBESS,"2026/09/15 00:00:00",1,GENERATOR,VJL21W,0,"2026/09/11 15:39:12"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,DIAMTEMP,"2026/09/18 00:00:00",1,GENERATOR,STET1T,0,"2026/09/16 14:52:47"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,SNODE1,"2026/09/25 00:00:00",1,GENERATOR,QSPS1S,0,"2026/09/23 09:25:40"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,SNODE1,"2026/09/25 00:00:00",1,GENERATOR,QSPT1S,0,"2026/09/23 09:25:40"
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,WANDBESS,"2026/09/29 00:00:00",1,GENERATOR,QWSB3W,0,"2026/09/25 16:30:04"
C,"END OF REPORT",11

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 7 KB when zipped, 71 KB 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
SETTLEMENT_CONFIG SETCFG_PARTICIPANT_MPF 1

This means that the CSV files start with metadata columns:

I,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,1,...
D,SETTLEMENT_CONFIG,SETCFG_PARTICIPANT_MPF,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: SETTLEMENT_CONFIG