PASA_INTERZONAL_BOUNDARY

PASA_INTERZONAL_BOUNDARY shows the mapping of each Interzonal connector boundary to its constituent Energy Management System Branch IDs

Column Schema

BRANCHID

Branch Identifier

SQL Type: VARCHAR2(50) Polars Type: str

This column is mandatory, and a primary key.

BRANCHSUBID

Branch Sub-Identifier

SQL Type: VARCHAR2(50) Polars Type: str

This column is mandatory, and a primary key.

EFFECTIVEDATE

Effective date of this Interzonal connector boundary definition

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

INTERZONALCONNECTORID

The identifier for this Interzonal connector

SQL Type: VARCHAR2(50) Polars Type: str

This column is mandatory, and a primary key.

VERSIONNO

Version number for the Effective date

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

This column is mandatory, and a primary key.

BRANCH_TO_INTERZONAL_FLOWMULT

Multiplier(1 or -1) used to convert from Branch Flow direction to Interzonal connector flow direction

SQL Type: NUMBER(1,0) Polars Type: pl.Int8

This column is not mandatory.

BRANCHFROMSUBSTATION

Branch FromSubstation. Positive Branch Flow from FromSubstation to ToSubstation.

SQL Type: VARCHAR2(30) Polars Type: str

This column is not mandatory.

BRANCHTOSUBSTATION

Branch ToSubstation. Positive Branch Flow from FromSubstation to ToSubstation.

SQL Type: VARCHAR2(30) Polars Type: str

This column is not mandatory.

BRANCHTYPE

Branch Type(LN = Line, XF = Transformer, ZBR = Zero Impedance Branch)

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

This column is not mandatory.

LASTCHANGED

Date time this record was created

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

OPERATINGSTATUS

Active or inactive indicator

SQL Type: VARCHAR2(20) Polars Type: str

This column is not mandatory.

New Data Timing

On Change

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("EFFECTIVEDATE", "LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
    )
    .cast(
        {
            "BRANCHID": str,
            "BRANCHSUBID": str,
            "INTERZONALCONNECTORID": str,
            "VERSIONNO": int,  # or pl.UInt16
            "BRANCH_TO_INTERZONAL_FLOWMULT": int,  # or pl.Int8
            "BRANCHFROMSUBSTATION": str,
            "BRANCHTOSUBSTATION": str,
            "BRANCHTYPE": pl.Categorical,
            "OPERATINGSTATUS": str,
        }
    )
    # Deduplicate
    # We want one row per ['BRANCHID', 'BRANCHSUBID', 'EFFECTIVEDATE', 'INTERZONALCONNECTORID', 'VERSIONNO']
    # Tie-breaker: greatest value of LASTCHANGED
    .sort(LASTCHANGED, descending=False)
    .unique(
        subset=[
            "BRANCHID",
            "BRANCHSUBID",
            "EFFECTIVEDATE",
            "INTERZONALCONNECTORID",
            "VERSIONNO",
        ],
        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:

• BRANCHID

• BRANCHSUBID

• EFFECTIVEDATE

• INTERZONALCONNECTORID

• VERSIONNO

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
PARTICIPANT_REGISTRATION	PASA_INTERZONAL_BOUNDARY	1

This means that the CSV files start with metadata columns:

I,PARTICIPANT_REGISTRATION,PASA_INTERZONAL_BOUNDARY,1,...
D,PARTICIPANT_REGISTRATION,PASA_INTERZONAL_BOUNDARY,1,...

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

Copy as Markdown