# DUDETAIL

> DUDETAIL sets out a records specific details for each unit including start type and whether normally on or off load. Much of this data is information only and is not used in dispatch or settlements.

> DUDETAIL is public data, and is available to all participants.
> 
> Source
> 
> DUDETAIL updates only when registration details change.
> 
> Note
> 
> To find the current set of details for selected dispatchable units,
> query the participant's local database as follows.
> 
> Select du.\* from dudetail du
> 
> where (du.[`EFFECTIVEDATE`](#effectivedate), du.[`VERSIONNO`](#versionno)) =
> 
> (
> 
> select effectivedate, max(versionno)
> 
> from dudetail
> 
> where [`EFFECTIVEDATE`](#effectivedate) = (select max(effectivedate)
> 
> from dudetail
> 
> where [`EFFECTIVEDATE`](#effectivedate) \<= sysdate
> 
> and duid = du.duid
> 
> and authoriseddate is not null)
> 
> and duid = du.duid
> 
> and authoriseddate is not null
> 
> group by effectivedate
> 
> )
> 
> and du.duid in ('UNIT1', 'UNIT2')
> 
> ;
> 
> The following notes apply to this SQL code:
> 
> · This table is specific to dispatch units only.
> 
> · If you wish to query details for a different date, substitute a date
> expression for "sysdate" in the "where [`EFFECTIVEDATE`](#effectivedate) \<= sysdate"
> clause.
> 
> · If you wish to list all the units, remove the line "and du.duid in
> ('UNIT1', 'UNIT2')"
> 
> · The DUDETAIL table does not indicate if a unit is active; this is done
> through ownership ([`STADUALLOC`](./STADUALLOC.md)) by an active station owned by an active
> participant ([`STATIONOWNER`](./STATIONOWNER.md) )
> 
> · If you wish to query Station details refer to [`STATION`](./STATION.md), [`STATIONOWNER`](./STATIONOWNER.md)
> and [`STADUALLOC`](./STADUALLOC.md).
> 
> · If you wish to look at connection point loss factors, refer to
> [`TRANSMISSIONLOSSFACTOR`](./TRANSMISSIONLOSSFACTOR.md).

## Column Schema

### DUID

> Dispatchable Unit Identifier

!!! danger "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](../../guide/querying.md#duid-genset-id-etc).

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

This column is mandatory, and a primary key.

Examples:

- `APD01`
- `APD02`
- `APS`
- `BARCALDN`
- `BARRON-1`
- `BARRON-2`
- `BAYNL1`
- `BDL01`
- `BHASZINC`
- `BLOWER`

### EFFECTIVEDATE

> Effective calendar date of record

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

This column is mandatory, and a primary key.

Example: `1998/10/25 00:00:00`

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

### VERSIONNO

> version of Dispatchable Unit details for this effective date

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

This column is mandatory, and a primary key.

Examples:
`1`, `48`

### ADG_ID

> Aggregate Dispatch Group to which this dispatch unit belongs

SQL Type: `VARCHAR2(20)`
Polars Type: `str`

This column is not mandatory.

### AGCCAPABILITY

> AGC Capability flag

SQL Type: `VARCHAR2(1)`
Polars Type: `pl.Boolean`

This column is not mandatory.

AEMO's documentation says this is a string type,
even though it is logically a binary value.
You may want to map letters to a boolean with `{'Y': 1, 'N': 0}`.

### AGGREGATED

> Identifies if a unit is aggregated. This flag was initially added in GENUNITS_UNIT table which is now deprecated with IESS release.

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

This column is not mandatory.

### AUTHORISEDBY

> User authorising record

SQL Type: `VARCHAR2(15)`
Polars Type: `str`

This column is not mandatory.

Example: `BATCH`

### AUTHORISEDDATE

> Date record authorised

!!! danger "Warning"
    Despite what the name suggests, this is a datetime, not a date.

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

This column is not mandatory.

Example: `1998/10/28 12:08:27`

### CONNECTIONPOINTID

> Country wide - Unique id of a connection point

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

This column is not mandatory.

Examples:

- `NBAY1`
- `NBAY2`
- `NBAY3`
- `NBAY4`
- `NBAYL`
- `NBKG1`
- `NBKG2`
- `NBLW`
- `NBLW1`
- `NBLW8`

### DISPATCHSUBTYPE

> Additional information for DISPATCHTYPE. For DISPATCHTYPE = LOAD, subtype value is WDR for wholesale demand response units. For DISPATCHTYPE = LOAD, subtype value is NULL for Scheduled Loads. For DISPATCHTYPE = GENERATOR type, the subtype value is NULL.

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

This column is not mandatory.

### DISPATCHTYPE

> Identifies LOAD, GENERATOR or BIDIRECTIONAL.

The SQL type is `VARCHAR2(20)`.
This is actually a factor/enum, with values:

- `GENERATOR`

- `LOAD`

- `BIDIRECTIONAL`

This column is not mandatory.

### INTERMITTENTFLAG

> Indicate whether a unit is intermittent (e.g. a wind farm)

SQL Type: `VARCHAR(1)`
Polars Type: `pl.Boolean`

This column is not mandatory.

AEMO's documentation says this is a string type,
even though it is logically a binary value.
You may want to map letters to a boolean with `{'Y': 1, 'N': 0}`.

### LASTCHANGED

> Last date and time record changed

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: `2008/12/10 09:21:25`

### LOAD_MIN_RAMP_RATE_DOWN

> Calculated Minimum Ramp Rate Down value accepted for Energy Offers or Bids on BDU Load component with explanation for energy imports (MW/min)

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

This column is not mandatory.

### LOAD_MIN_RAMP_RATE_UP

> Calculated Minimum Ramp Rate Up value accepted for Energy Offers or Bids on BDU Load component with explanation for energy imports (MW/min)

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

This column is not mandatory.

### MAXCAPACITY

> Maximum Capacity as used for bid validation

!!! danger "Warning"
    AEMO's documentation says that this is an integer (`NUMBER(6,0)`). Actually, the values in the CSV have fractional components.

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

This column is not mandatory.

Examples:
`13.55`, `1`, `137.5`, `3756`

### MAXRATEOFCHANGEDOWN

> Maximum ramp down rate for Unit (Mw/min)

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

This column is not mandatory.

### MAXRATEOFCHANGEDOWN_LOAD

> Lower Ramp rate applied to BDU Load component (MW/min)

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

This column is not mandatory.

### MAXRATEOFCHANGEUP

> Maximum ramp up rate for Unit (Mw/min)

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

This column is not mandatory.

### MAXRATEOFCHANGEUP_LOAD

> Raise Ramp rate applied to BDU Load component (MW/min)

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

This column is not mandatory.

### MAXSTORAGECAPACITY

> The rated storage capacity (MWh), information only

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

This column is not mandatory.

### MIN_RAMP_RATE_DOWN

> Calculated Minimum Ramp Rate Down value accepted for Energy Offers or Bids with explanation for energy imports (all DUID types and BDU Generation side) (MW/min)

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

This column is not mandatory.

### MIN_RAMP_RATE_UP

> Calculated Minimum Ramp Rate Up value accepted for Energy Offers or Bids with explanation for energy imports (all DUID types and BDU Generation side) (MW/min)

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

This column is not mandatory.

### MINCAPACITY

> Minimum capacity only for load side of BDU, otherwise 0 (MW)

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

This column is not mandatory.

### NORMALLYONFLAG

> For a dispatchable load indicates that the load is normally on or off.

SQL Type: `VARCHAR2(1)`
Polars Type: `pl.Categorical`

This column is not mandatory.

Examples:

- `N`
- `Y`

### PHYSICALDETAILSFLAG

> Indicates that the physical details for this unit are to be recorded

SQL Type: `VARCHAR2(1)`
Polars Type: `pl.Categorical`

This column is not mandatory.

### REGISTEREDCAPACITY

> Registered capacity for normal operations

!!! danger "Warning"
    AEMO's documentation says that this is an integer (`NUMBER(6,0)`). Actually, the values in the CSV have fractional components.

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

This column is not mandatory.

Examples:
`13.55`, `1`, `137.5`, `3756`

### REGISTEREDMINCAPACITY

> Registered minimum capacity only for load side of BDU, otherwise 0 (MW)

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

This column is not mandatory.

### SEMISCHEDULE_FLAG

> Indicates if the DUID is a Semi-Scheduled Unit

SQL Type: `VARCHAR2(1)`
Polars Type: `pl.Categorical`

This column is not mandatory.

Example: `N`

### SPINNINGRESERVEFLAG

> Indicates spinning reserve capability

SQL Type: `VARCHAR2(1)`
Polars Type: `pl.Categorical`

This column is not mandatory.

Examples:

- `N`
- `Y`

### STARTTYPE

> Identify unit as Fast or Slow

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

This column is not mandatory.

Examples:

- `FAST`
- `NOT DISPATCHED`
- `SLOW`

### STORAGEEXPORTEFFICIENCYFACTOR

> The storage energy export conversion efficiency. Number from 0 to 1 where 1 is lossless. Calculated as (decrease in exported energy / decrease in stored energy)

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

This column is not mandatory.

### STORAGEIMPORTEFFICIENCYFACTOR

> The storage energy import conversion efficiency. Number from 0 to 1 where 1 is lossless. Calculated as (increase in stored energy / increase in imported energy)

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

This column is not mandatory.

### VOLTLEVEL

> Voltage Level

SQL Type: `VARCHAR2(10)`
Polars Type: `str`

This column is not mandatory.

Examples:

- `11`
- `500`

## New Data Timing

> When registration details change

## 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"

# 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("AGCCAPABILITY").replace({"Y": 1, "N": 0}),
        pl.col("INTERMITTENTFLAG").replace({"Y": 1, "N": 0}),
    )
    .with_columns(
        pl.col("AUTHORISEDDATE", "LASTCHANGED").str.strptime(pl.Datetime, dt_s_fmt),
        pl.col("EFFECTIVEDATE").str.strptime(pl.Date, d_fmt),
    )
    # Polars can't cast string straight to bool. Need to go via something else.
    .cast(
        {
            "AGCCAPABILITY": pl.UInt8,
            "AGGREGATED": pl.UInt8,
            "INTERMITTENTFLAG": pl.UInt8,
        }
    )
    .cast(
        {
            "DUID": pl.Categorical,
            "EFFECTIVEDATE": pl.Date(),
            "VERSIONNO": int,  # or pl.UInt16
            "ADG_ID": str,
            "AGCCAPABILITY": pl.Boolean,
            "AGGREGATED": pl.Boolean,
            "AUTHORISEDBY": str,
            "CONNECTIONPOINTID": pl.Categorical,
            "DISPATCHSUBTYPE": pl.Categorical,
            "DISPATCHTYPE": pl.Enum(["GENERATOR", "LOAD", "BIDIRECTIONAL"]),
            "INTERMITTENTFLAG": pl.Boolean,
            "LOAD_MIN_RAMP_RATE_DOWN": int,  # or pl.Int32
            "LOAD_MIN_RAMP_RATE_UP": int,  # or pl.Int32
            "MAXCAPACITY": pl.Float64,
            "MAXRATEOFCHANGEDOWN": int,  # or pl.Int32
            "MAXRATEOFCHANGEDOWN_LOAD": int,  # or pl.Int32
            "MAXRATEOFCHANGEUP": int,  # or pl.Int32
            "MAXRATEOFCHANGEUP_LOAD": int,  # or pl.Int32
            "MAXSTORAGECAPACITY": pl.Float64,
            "MIN_RAMP_RATE_DOWN": int,  # or pl.Int32
            "MIN_RAMP_RATE_UP": int,  # or pl.Int32
            "MINCAPACITY": int,  # or pl.Int32
            "NORMALLYONFLAG": pl.Categorical,
            "PHYSICALDETAILSFLAG": pl.Categorical,
            "REGISTEREDCAPACITY": pl.Float64,
            "REGISTEREDMINCAPACITY": int,  # or pl.Int32
            "SEMISCHEDULE_FLAG": pl.Categorical,
            "SPINNINGRESERVEFLAG": pl.Categorical,
            "STARTTYPE": pl.Categorical,
            "STORAGEEXPORTEFFICIENCYFACTOR": pl.Float64,
            "STORAGEIMPORTEFFICIENCYFACTOR": pl.Float64,
            "VOLTLEVEL": str,
        }
    )
    # Deduplicate
    # We want one row per ['DUID', 'EFFECTIVEDATE', 'VERSIONNO']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["DUID", "EFFECTIVEDATE", "VERSIONNO"], keep="last")
)

```

### Nemosis

```py
from nemosis import dynamic_data_compiler

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

Nemosis only includes [a subset of columns](https://github.com/UNSW-CEEM/NEMOSIS/#accessing-additional-table-columns) by default, as an optimisation. (i.e. the commonly used columns.)
To include others:

```py
from nemosis import defaults

defaults.table_columns["DUDETAIL"] += ["ADG_ID", "AGGREGATED", "AUTHORISEDBY", "AUTHORISEDDATE", "DISPATCHSUBTYPE", "INTERMITTENTFLAG", "LOAD_MIN_RAMP_RATE_DOWN", "LOAD_MIN_RAMP_RATE_UP", "MAXRATEOFCHANGEDOWN", "MAXRATEOFCHANGEDOWN_LOAD", "MAXRATEOFCHANGEUP", "MAXRATEOFCHANGEUP_LOAD", "MAXSTORAGECAPACITY", "MIN_RAMP_RATE_DOWN", "MIN_RAMP_RATE_UP", "MINCAPACITY", "PHYSICALDETAILSFLAG", "REGISTEREDMINCAPACITY", "SEMISCHEDULE_FLAG", "SPINNINGRESERVEFLAG", "STORAGEEXPORTEFFICIENCYFACTOR", "STORAGEIMPORTEFFICIENCYFACTOR", "VOLTLEVEL"]
df = dynamic_data_compiler(...)
```

## Example File

From [PUBLIC_ARCHIVE_DUDETAIL_FILE01_202609010000.zip](https://www.nemweb.com.au/Data_Archive/Wholesale_Electricity/MMSDM/2026/MMSDM_2026_09/MMSDM_Historical_Data_SQLLoader/DATA/PUBLIC_ARCHIVE%23DUDETAIL%23FILE01%23202609010000.zip)

=== "Raw Text with Metadata"
    ```csv
    C,SETP.WORLD,DVD_DUDETAIL,AEMO,PUBLIC,2026/10/09,15:36:33,001791524193601,MONTHLY_ARCHIVE,001791524193601
    I,PARTICIPANT_REGISTRATION,DUDETAIL,7,EFFECTIVEDATE,DUID,VERSIONNO,CONNECTIONPOINTID,VOLTLEVEL,REGISTEREDCAPACITY,AGCCAPABILITY,DISPATCHTYPE,MAXCAPACITY,STARTTYPE,NORMALLYONFLAG,PHYSICALDETAILSFLAG,SPINNINGRESERVEFLAG,AUTHORISEDBY,AUTHORISEDDATE,LASTCHANGED,INTERMITTENTFLAG,SEMISCHEDULE_FLAG,MAXRATEOFCHANGEUP,MAXRATEOFCHANGEDOWN,DISPATCHSUBTYPE,ADG_ID,MINCAPACITY,REGISTEREDMINCAPACITY,MAXRATEOFCHANGEUP_LOAD,MAXRATEOFCHANGEDOWN_LOAD,MAXSTORAGECAPACITY,STORAGEIMPORTEFFICIENCYFACTOR,STORAGEEXPORTEFFICIENCYFACTOR,MIN_RAMP_RATE_UP,MIN_RAMP_RATE_DOWN,LOAD_MIN_RAMP_RATE_UP,LOAD_MIN_RAMP_RATE_DOWN,AGGREGATED
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/26 00:00:00",LD01,1,NLDP1,330,500,Y,GENERATOR,550,SLOW,,,Y,BATCH,"1998/10/28 12:08:27","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",OSB01,1,SNBN1,66,118,N,GENERATOR,118,SLOW,,,N,BATCH,"1998/10/29 18:06:36","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",OSB02,1,SNBN2,66,62,N,GENERATOR,62,SLOW,,,N,BATCH,"1998/10/29 18:06:36","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/26 00:00:00",LD01,2,NLDP1,330,500,Y,GENERATOR,550,SLOW,,,Y,BATCH,"1998/10/29 18:52:51","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",NPS1,2,SNPA1,275,265,Y,GENERATOR,280,SLOW,,,Y,BATCH,"1998/11/02 12:10:49","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",NPS2,2,SNPA2,275,265,Y,GENERATOR,280,SLOW,,,Y,BATCH,"1998/11/02 12:10:50","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",PLAYFB1,2,SPSD1,275,60,N,GENERATOR,63,SLOW,,,Y,BATCH,"1998/11/02 12:10:50","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",PLAYFB2,2,SPSD2,275,60,N,GENERATOR,63,SLOW,,,Y,BATCH,"1998/11/02 12:10:50","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",PLAYFB3,2,SPSD3,275,60,N,GENERATOR,63,SLOW,,,Y,BATCH,"1998/11/02 12:10:50","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",PLAYFB4,2,SPSD4,275,60,N,GENERATOR,63,SLOW,,,Y,BATCH,"1998/11/02 12:10:50","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    D,PARTICIPANT_REGISTRATION,DUDETAIL,7,"1998/10/25 00:00:00",CALL_A_1,2,QCAA1,132,30,N,GENERATOR,30,SLOW,,,Y,BATCH,"1998/11/02 12:11:39","2008/12/10 09:21:25",N,N,,,,,,,,,,,,,,,,
    ...
    C,"END OF REPORT",1003
    ```

## Availability

Visibility: Public

This table is in the public monthly [MMSDM archive](https://www.nemweb.com.au/Data_Archive/Wholesale_Electricity/MMSDM/).

I have collated the list of all those files into one place, in [this CSV metadata file](../../manifests/per_table/csv/DUDETAIL.csv). (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
965 KB when zipped,
10 MB as unzipped CSV.

## Deduplication and PDR Loader Configuration

The primary keys are:

- [`DUID`](#duid)

- [`EFFECTIVEDATE`](#effectivedate)

- [`VERSIONNO`](#versionno)

The transaction type is ["insert"](https://di-help.docs.public.aemo.com.au/Content/pdrLoader/How_it_works.htm?TocPath=pdrLoader%7CAbout+pdrLoader%7C_____5#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](https://nemweb.com.au/Reports/Current/MMSDataModelReport/PDRCONFIG/PROD_PUBLIC_PDR_CONFIG_FULL.zip) is:

| Report Name | Report Subtype | Version |
|---------------|-------------------|-----------|
| PARTICIPANT_REGISTRATION | DUDETAIL  | 6 |
| PARTICIPANT_REGISTRATION | DUDETAIL  | 7 |

This means that the CSV files start with metadata columns:

```csv
I,PARTICIPANT_REGISTRATION,DUDETAIL,6,...
D,PARTICIPANT_REGISTRATION,DUDETAIL,6,...
```

or

```csv
I,PARTICIPANT_REGISTRATION,DUDETAIL,7,...
D,PARTICIPANT_REGISTRATION,DUDETAIL,7,...
```

## Indexes

- [`LASTCHANGED`](#lastchanged)

## Links

[This page as JSON](../json/tables/DUDETAIL/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/DUDETAIL/json-schema.json) specification for this table.

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

## Other Information

Package: [PARTICIPANT_REGISTRATION](../packages/PARTICIPANT_REGISTRATION.md)
