SSM_INDICATIVE_ROLL_DUID

Indicative rolling DUID schedule provides notice of system security status to service providers/TNSP. The intent is to provide forewarning of possible enablement instruction that may be required

Column Schema

CONTRACT_ID

Unique Contract Identifier used to create enablement.

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

This column is mandatory, and a primary key.

DUID

Dispatchable Unit Identifier

Warning

This column may contain funny characters such as / (slash) or # (hash). This may break hive-style partitioning.

For more information, see the dedicated documentation page.

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

This column is mandatory, and a primary key.

Example: W/HOE#2

INTERVAL_DATETIME

Interval date time

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

This column is mandatory, and a primary key.

Example: 2026/01/20 00:05:00

VERSION_DATETIME

Version date time

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

This column is mandatory, and a primary key.

Example: 2026/01/20 00:05:00

DUID_PARTICIPANTID

Primary recipient (SSM Service Provider) of enablement instruction.

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

This column is not mandatory.

DUID_STATUS

Scheduled pending, Scheduled approved, Instruction issued, Fulfilment, Available, Offline, Online, Outage

SQL Type: VARCHAR2(40) Polars Type: str

This column is not mandatory.

EQUIPMENT_TYPE

Dispatchable Unit resource (for example, GENERATOR, LOAD, BIDIRECTIONAL, SYNCHRONOUS CONDENSER).

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

This column is not mandatory.

INSTRUCTION_ID

Unique Instruction Identifier. Null where not applicable.

SQL Type: VARCHAR2(20) Polars Type: str

This column is not mandatory.

LASTCHANGED

Last changed date

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

MIN_DISPATCH_MW

Minimum Dispatch Target required for DUID to enable the contract.

SQL Type: NUMBER(18,8) Polars Type: pl.Float64

This column is not mandatory.

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("INTERVAL_DATETIME", "VERSION_DATETIME", "LASTCHANGED").str.strptime(
            pl.Datetime, dt_s_fmt
        ),
    )
    .cast(
        {
            "CONTRACT_ID": pl.Categorical,
            "DUID": pl.Categorical,
            "DUID_PARTICIPANTID": pl.Categorical,
            "DUID_STATUS": str,
            "EQUIPMENT_TYPE": pl.Categorical,
            "INSTRUCTION_ID": str,
            "MIN_DISPATCH_MW": pl.Float64,
        }
    )
    # Deduplicate
    # We want one row per ['CONTRACT_ID', 'DUID', 'INTERVAL_DATETIME', 'VERSION_DATETIME']
    # Tie-breaker: greatest value of LASTCHANGED
    .sort(LASTCHANGED, descending=False)
    .unique(
        subset=["CONTRACT_ID", "DUID", "INTERVAL_DATETIME", "VERSION_DATETIME"],
        keep="last",
    )
)

Nemosis

This table is not yet available in Nemosis.

Availability

Visibility: Private

This table is not available in the public monthly MMSDM archive. Is is only available to registered market participants over FTP inside a VPN.

Deduplication and PDR Loader Configuration

The primary keys are:

• CONTRACT_ID

• DUID

• INTERVAL_DATETIME

• VERSION_DATETIME

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
SSM	INDICATIVE_ROLL_DUID	1

This means that the CSV files start with metadata columns:

I,SSM,INDICATIVE_ROLL_DUID,1,...
D,SSM,INDICATIVE_ROLL_DUID,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: SYSTEM_SECURITY_MANAGEMENT

Copy as Markdown