NETWORK_EQUIPMENTDETAIL
NETWORK_EQUIPMENTDETAIL Provides details on equipment that may have outages or ratings. A single piece of equipment may have multiple records if its details change. A line will typically have at least two valid records at a time, once for each end of the line.
Column Schema
ELEMENTID
Equipment element id
SQL Type: NUMBER(15,0)
Polars Type: pl.Int64
This column is mandatory, and a primary key.
Examples:
3, 3111
EQUIPMENTID
A unique identifier for this type of equipment at this substation
SQL Type: VARCHAR(30)
Polars Type: str
This column is mandatory, and a primary key.
Examples:
1110KV_7147217110KV_717110KV_721110KV_722110KV_731110KV_732110KV_733110KV_734
EQUIPMENTTYPE
The type of equipment. Valid values are: LINE = Line TRANS = Transformer CB = Circuit breaker ISOL = Isolator CAP = Capacitor REAC = Reactor UNIT = Unit
SQL Type: VARCHAR(10)
Polars Type: pl.Categorical
This column is mandatory, and a primary key.
Examples:
BUSCAPLINEN/AREACSVCTRANS
SUBSTATIONID
ID uniquely identifying the substation this equipment is located at
SQL Type: VARCHAR(30)
Polars Type: str
This column is mandatory, and a primary key.
Examples:
ABC_BACALALDINGAPDATSBATSBDSSBETSBLTS
VALIDFROM
The date that this record is applies from (inclusive)
SQL Type: TIMESTAMP(3)
Polars Type: pl.Datetime()
This column is mandatory, and a primary key.
Example: 2003/04/28 16:51:08.000
Unlike most datetime columns, this one includes a millisecond component.
e.g. 2029/03/15 00:00:00.123.
DESCRIPTION
A short description for this equipment.
SQL Type: VARCHAR(100)
Polars Type: str
This column is not mandatory.
Examples:
Abermain 2 100/33kV XFMRAbermain 3 100/33kV XFMRAbermain 3 110kV BUSAlan Shrff 11kV BUSAlc/prtlnd 1 220kV BUSAlc/prtlnd 2 500kV BUSAlc/prtlnd 2 500kV REACTAlc/prtlnd 3 500kV BUSAlc/prtlnd 33kV BUSAlc/prtlnd A2 33kV REACT
LASTCHANGED
The time that this record was last changed.
For more information, see the dedicated documentation page.
SQL Type: TIMESTAMP(3)
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2000/01/01 00:00:10.000
Unlike most datetime columns, this one includes a millisecond component.
e.g. 2029/03/15 00:00:00.123.
VALIDTO
The date that this record applies until (exclusive)
SQL Type: TIMESTAMP(3)
Polars Type: pl.Datetime()
This column is not mandatory.
Example: 2003/06/04 14:57:33.000
Unlike most datetime columns, this one includes a millisecond component.
e.g. 2029/03/15 00:00:00.123.
VOLTAGE
The voltage in KV for this equipment. Transformers may have multiple voltages defined. E.g. 132_110_33
SQL Type: VARCHAR(20)
Polars Type: str
This column is not mandatory.
Examples:
6.611138.6_11.6288_138_19.1288_138_19
New Data Timing
When equipment details are added or changed
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
# for "TIMESTAMP" columns
# Note that Polars uses slightly different format strings for fractional seconds to `dt.strptime`
# e.g. "2029/03/15 00:00:00.123".
dt_ms_fmt = "%Y/%m/%d %H:%M:%S%.3f"
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("VALIDFROM", "LASTCHANGED", "VALIDTO").str.strptime(
pl.Datetime, dt_ms_fmt
),
)
.cast(
{
"ELEMENTID": int, # or pl.Int64
"EQUIPMENTID": str,
"EQUIPMENTTYPE": pl.Categorical,
"SUBSTATIONID": str,
"DESCRIPTION": str,
"VOLTAGE": str,
}
)
# Deduplicate
# We want one row per ['ELEMENTID', 'EQUIPMENTID', 'EQUIPMENTTYPE', 'SUBSTATIONID', 'VALIDFROM']
# Tie-breaker: greatest value of ['LASTCHANGED']
.sort(["LASTCHANGED"], descending=False)
.unique(
subset=[
"ELEMENTID",
"EQUIPMENTID",
"EQUIPMENTTYPE",
"SUBSTATIONID",
"VALIDFROM",
],
keep="last",
)
)
Nemosis
This table is not yet available in Nemosis.
Example File
From PUBLIC_ARCHIVE_NETWORK_EQUIPMENTDETAIL_FILE01_202609010000.zip
| SUBSTATIONID | EQUIPMENTTYPE | EQUIPMENTID | VALIDFROM | VALIDTO | VOLTAGE | DESCRIPTION | LASTCHANGED | ELEMENTID |
| SYTS | BUS | 6MN1 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 500 | Sydenham 1 500kV BUS | 2003/04/28 16:54:12.000 | 2024 |
| TSTS | BUS | 3MN4 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 66 | Templestow 4 66kV BUS | 2003/04/28 16:54:12.000 | 2031 |
| TTS | BUS | 7MN1 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 220 | Thomastown 1 220kV BUS | 2003/04/28 16:54:12.000 | 2036 |
| TTS | BUS | 3MN4 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 66 | Thomastown 4 66kV BUS | 2003/04/28 16:54:12.000 | 2043 |
| WOTS | BUS | 3MN1 | 2003/04/28 16:54:03.000 | 9999/12/31 00:00:00.000 | 66 | Wodonga 1 66kV BUS | 2003/04/28 16:54:13.000 | 2068 |
| BETS | CAP | 3BCAP_66 | 2003/04/28 16:54:15.000 | 2024/07/01 15:06:56.518 | 66 | Bendigo 3B 66kV CAP | 2024/07/01 15:07:06.518 | 2080 |
| BTS | CAP | 1CAP_22 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 22 | Brunswick 1 22kV CAP | 2003/04/28 16:54:25.000 | 2082 |
| DDTS | CAP | 2CAP_330 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 330 | Dederang 2 330kV CAP | 2003/04/28 16:54:25.000 | 2086 |
| LY | CAP | 1CAP | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 66 | Loy Yang 1 66kV CAP | 2003/04/28 16:54:25.000 | 2103 |
| MLRC | CAP | Z12 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 165 | Mrrylnk Vc Z 12 165kV CAP | 2003/04/28 16:54:25.000 | 2106 |
| RTS | CAP | 1CAP_1B_66 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 66 | Richmond 1 66kV CAP | 2003/04/28 16:54:25.000 | 2113 |
| ... |
| C | SETP.WORLD | DVD_NETWORK_EQUIPMENTDETAIL | AEMO | PUBLIC | 2026/10/09 | 15:56:05 | 001791525365583 | MONTHLY_ARCHIVE | 001791525365583 | |||
| I | NETWORK | EQUIPMENTDETAIL | 2 | SUBSTATIONID | EQUIPMENTTYPE | EQUIPMENTID | VALIDFROM | VALIDTO | VOLTAGE | DESCRIPTION | LASTCHANGED | ELEMENTID |
| D | NETWORK | EQUIPMENTDETAIL | 2 | SYTS | BUS | 6MN1 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 500 | Sydenham 1 500kV BUS | 2003/04/28 16:54:12.000 | 2024 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | TSTS | BUS | 3MN4 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 66 | Templestow 4 66kV BUS | 2003/04/28 16:54:12.000 | 2031 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | TTS | BUS | 7MN1 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 220 | Thomastown 1 220kV BUS | 2003/04/28 16:54:12.000 | 2036 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | TTS | BUS | 3MN4 | 2003/04/28 16:54:02.000 | 9999/12/31 00:00:00.000 | 66 | Thomastown 4 66kV BUS | 2003/04/28 16:54:12.000 | 2043 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | WOTS | BUS | 3MN1 | 2003/04/28 16:54:03.000 | 9999/12/31 00:00:00.000 | 66 | Wodonga 1 66kV BUS | 2003/04/28 16:54:13.000 | 2068 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | BETS | CAP | 3BCAP_66 | 2003/04/28 16:54:15.000 | 2024/07/01 15:06:56.518 | 66 | Bendigo 3B 66kV CAP | 2024/07/01 15:07:06.518 | 2080 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | BTS | CAP | 1CAP_22 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 22 | Brunswick 1 22kV CAP | 2003/04/28 16:54:25.000 | 2082 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | DDTS | CAP | 2CAP_330 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 330 | Dederang 2 330kV CAP | 2003/04/28 16:54:25.000 | 2086 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | LY | CAP | 1CAP | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 66 | Loy Yang 1 66kV CAP | 2003/04/28 16:54:25.000 | 2103 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | MLRC | CAP | Z12 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 165 | Mrrylnk Vc Z 12 165kV CAP | 2003/04/28 16:54:25.000 | 2106 |
| D | NETWORK | EQUIPMENTDETAIL | 2 | RTS | CAP | 1CAP_1B_66 | 2003/04/28 16:54:15.000 | 9999/12/31 00:00:00.000 | 66 | Richmond 1 66kV CAP | 2003/04/28 16:54:25.000 | 2113 |
| ... | ||||||||||||
| C | END OF REPORT | 1003 |
SUBSTATIONID,EQUIPMENTTYPE,EQUIPMENTID,VALIDFROM,VALIDTO,VOLTAGE,DESCRIPTION,LASTCHANGED,ELEMENTID
SYTS,BUS,6MN1,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",500,"Sydenham 1 500kV BUS","2003/04/28 16:54:12.000",2024
TSTS,BUS,3MN4,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",66,"Templestow 4 66kV BUS","2003/04/28 16:54:12.000",2031
TTS,BUS,7MN1,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",220,"Thomastown 1 220kV BUS","2003/04/28 16:54:12.000",2036
TTS,BUS,3MN4,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",66,"Thomastown 4 66kV BUS","2003/04/28 16:54:12.000",2043
WOTS,BUS,3MN1,"2003/04/28 16:54:03.000","9999/12/31 00:00:00.000",66,"Wodonga 1 66kV BUS","2003/04/28 16:54:13.000",2068
BETS,CAP,3BCAP_66,"2003/04/28 16:54:15.000","2024/07/01 15:06:56.518",66,"Bendigo 3B 66kV CAP","2024/07/01 15:07:06.518",2080
BTS,CAP,1CAP_22,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",22,"Brunswick 1 22kV CAP","2003/04/28 16:54:25.000",2082
DDTS,CAP,2CAP_330,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",330,"Dederang 2 330kV CAP","2003/04/28 16:54:25.000",2086
LY,CAP,1CAP,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",66,"Loy Yang 1 66kV CAP","2003/04/28 16:54:25.000",2103
MLRC,CAP,Z12,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",165,"Mrrylnk Vc Z 12 165kV CAP","2003/04/28 16:54:25.000",2106
RTS,CAP,1CAP_1B_66,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",66,"Richmond 1 66kV CAP","2003/04/28 16:54:25.000",2113
...
C,SETP.WORLD,DVD_NETWORK_EQUIPMENTDETAIL,AEMO,PUBLIC,2026/10/09,15:56:05,001791525365583,MONTHLY_ARCHIVE,001791525365583
I,NETWORK,EQUIPMENTDETAIL,2,SUBSTATIONID,EQUIPMENTTYPE,EQUIPMENTID,VALIDFROM,VALIDTO,VOLTAGE,DESCRIPTION,LASTCHANGED,ELEMENTID
D,NETWORK,EQUIPMENTDETAIL,2,SYTS,BUS,6MN1,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",500,"Sydenham 1 500kV BUS","2003/04/28 16:54:12.000",2024
D,NETWORK,EQUIPMENTDETAIL,2,TSTS,BUS,3MN4,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",66,"Templestow 4 66kV BUS","2003/04/28 16:54:12.000",2031
D,NETWORK,EQUIPMENTDETAIL,2,TTS,BUS,7MN1,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",220,"Thomastown 1 220kV BUS","2003/04/28 16:54:12.000",2036
D,NETWORK,EQUIPMENTDETAIL,2,TTS,BUS,3MN4,"2003/04/28 16:54:02.000","9999/12/31 00:00:00.000",66,"Thomastown 4 66kV BUS","2003/04/28 16:54:12.000",2043
D,NETWORK,EQUIPMENTDETAIL,2,WOTS,BUS,3MN1,"2003/04/28 16:54:03.000","9999/12/31 00:00:00.000",66,"Wodonga 1 66kV BUS","2003/04/28 16:54:13.000",2068
D,NETWORK,EQUIPMENTDETAIL,2,BETS,CAP,3BCAP_66,"2003/04/28 16:54:15.000","2024/07/01 15:06:56.518",66,"Bendigo 3B 66kV CAP","2024/07/01 15:07:06.518",2080
D,NETWORK,EQUIPMENTDETAIL,2,BTS,CAP,1CAP_22,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",22,"Brunswick 1 22kV CAP","2003/04/28 16:54:25.000",2082
D,NETWORK,EQUIPMENTDETAIL,2,DDTS,CAP,2CAP_330,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",330,"Dederang 2 330kV CAP","2003/04/28 16:54:25.000",2086
D,NETWORK,EQUIPMENTDETAIL,2,LY,CAP,1CAP,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",66,"Loy Yang 1 66kV CAP","2003/04/28 16:54:25.000",2103
D,NETWORK,EQUIPMENTDETAIL,2,MLRC,CAP,Z12,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",165,"Mrrylnk Vc Z 12 165kV CAP","2003/04/28 16:54:25.000",2106
D,NETWORK,EQUIPMENTDETAIL,2,RTS,CAP,1CAP_1B_66,"2003/04/28 16:54:15.000","9999/12/31 00:00:00.000",66,"Richmond 1 66kV CAP","2003/04/28 16:54:25.000",2113
...
C,"END OF REPORT",1003
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 8 of 2024. 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 9 MB when zipped, 86 MB 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.
| Report Name | Report Subtype | Version |
|---|---|---|
| NETWORK | EQUIPMENTDETAIL | 1 |
| NETWORK | EQUIPMENTDETAIL | 2 |
This means that the CSV files start with metadata columns:
or
ROW_FILTER_TYPE is LASTCHANGED
Indexes
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: NETWORK