# STPASA_SYSTEMSOLUTION

> STPASA_SYSTEMSOLUTION is obsolete from 2005 End of Year Release. For solution information, see Region solution tables.
> STPASA_SYSTEMSOLUTION showed the results of the system capacity evaluations for each interval of the study.

!!! tip "Deprecation Warning"
    This table is in the [HISTORICAL TABLES](../packages/HISTORICAL TABLES.md) package,
    so is likely deprecated.

> STPASA_SYSTEMSOLUTION is public data.
> 
> Source
> 
> STPASA_SYSTEMSOLUTION is updated each STPASA run (half-hourly).
> 
> Volume
> 
> Rows per day: 48
> 
> Mb per month: \<1

## Column Schema

### INTERVAL_DATETIME

> The unique identifier for the interval within this study

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

This column is mandatory, and a primary key.

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

### CONSTRAINEDCAPACITY

> System energy constrained capacity MW subject to energy and network constraints

SQL Type: `NUMBER(12,2)`
Polars Type: `pl.Float64`

This column is not mandatory.

### LASTCHANGED

> Last changed date of this record

For more information, see the [dedicated documentation page](../../guide/querying.md#deduplication).

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

This column is not mandatory.

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

### RESERVECONDITION

> The system reserve condition: 0 Adequate, 1 LRC

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

This column is not mandatory.

### RESERVEREQ

> System total reserve requirement

SQL Type: `NUMBER(12,2)`
Polars Type: `pl.Float64`

This column is not mandatory.

### RUN_DATETIME

> Unique Timestamp Identifier for this study

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

This column is mandatory (but not a primary key).

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

### SURPLUSCAPACITY

> System capacity surplus MW, +/- values indicate surplus/deficit capacity

SQL Type: `NUMBER(12,2)`
Polars Type: `pl.Float64`

This column is not mandatory.

### SURPLUSRESERVE

> System reserve surplus MW, +/- values indicate surplus/deficit reserve

SQL Type: `NUMBER(12,2)`
Polars Type: `pl.Float64`

This column is not mandatory.

### SYSTEMDEMAND50

> Sum of Demand 50% PoE

SQL Type: `NUMBER(12,2)`
Polars Type: `pl.Float64`

This column is not mandatory.

### UNCONSTRAINEDCAPACITY

> System energy unconstrained capacity MW subject to energy and network constraints

SQL Type: `NUMBER(12,2)`
Polars Type: `pl.Float64`

This column is not mandatory.

## New Data Timing

> Each ST PASA run

## Code Examples

### Polars

Explicitly listing every column, casting to 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.

```python
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", "LASTCHANGED", "RUN_DATETIME").str.strptime(
            pl.Datetime, dt_s_fmt
        ),
    )
    # Polars can't cast string straight to bool. Need to go via something else.
    .cast({"RESERVECONDITION": pl.UInt8})
    .cast(
        {
            "CONSTRAINEDCAPACITY": pl.Float64,
            "RESERVECONDITION": pl.Boolean,
            "RESERVEREQ": pl.Float64,
            "SURPLUSCAPACITY": pl.Float64,
            "SURPLUSRESERVE": pl.Float64,
            "SYSTEMDEMAND50": pl.Float64,
            "UNCONSTRAINEDCAPACITY": pl.Float64,
        }
    )
    # Deduplicate
    # We want one row per ['INTERVAL_DATETIME']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["INTERVAL_DATETIME"], keep="last")
)

```

### Nemosis

This table is not yet available in [Nemosis](https://github.com/UNSW-CEEM/NEMOSIS/#static_table).

## Availability

AEMO's documentation states that this table's visibility is "Public".
However, it is not available in the public monthly [MMSDM archive](https://www.nemweb.com.au/Data_Archive/Wholesale_Electricity/MMSDM/).
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:

- [`INTERVAL_DATETIME`](#interval_datetime)

PDR Loader configuration does not mention this table, so it is unclear how to choose which row to keep when there are multiple rows for a given set of primary keys.

You should probably take the row with the maximum `LASTCHANGED`.

## Indexes

There is more than one index.

Index 1:

- [`LASTCHANGED`](#lastchanged)

Index 2:

- [`RUN_DATETIME`](#run_datetime)

## Links

[This page as JSON](../json/tables/STPASA_SYSTEMSOLUTION/bespoke.json) (schema documented [here](https://gitlab.com/MatthewDavis/mms-schema/-/blob/master/schema.py?ref_type=heads), but may change)

Download a [JSON Schema](../json/tables/STPASA_SYSTEMSOLUTION/json-schema.json) specification for this table.

[Official AEMO schema documentation](https://nemweb.com.au/Reports/Current/MMSDataModelReport/Electricity/ElectricityDataModelReport_files/Elec65.htm#1220)

## Other Information

Package: [HISTORICAL TABLES](../packages/HISTORICAL TABLES.md)
