LNSP – local network service provider queries

ADWNAN_INTERVAL

Purpose

Identifies where Datastreams are active but the status of the NMI is Not-Active and the MDP has sent non-zero metering data

Availability

ADWAN_INTERVAL will retire on 6 December 2026. From this date, participants must use the ADWAN_INTERVAL_ACT query

Content

ACTIVE DATASTREAM WITH A NON-ACTIVE NMI

List of all non-active NMIs, having an active Datastream(s) and non-zero data interval

 

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

MDM

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

ADWNAN_INTERVAL

N/A

Query Identifier

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

The relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

EMDM

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

SDR_Key2

n/a

N/A

[Not Applicable]

SDR_Key3

n/a

N/A

[Not Applicable]

SDR_Key4

n/a

N/A

[Not Applicable]

SDR_Key5

n/a

N/A

[Not Applicable]

Field

n/a

N/A

[Not Applicable]

MDP

MDPPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the MDP role

NMISTATUSCODE

D

Status

The code used to indicate the status of the NMI.

STARTDATE of current inactive NMISTATUSCODE record

22/03/2024

FromDate

Start date of current inactive NMI Status Code record in CATS_NMI_DATA in the format DD/MM/YYYY

MDM Datastream

E1

Suffix

The Suffix field in the CATS_DATA_STREAM table is used to identify a physical data source obtained from the meter

STARTDATE of current active MDM Datastream record

26/10/2022

FromDate

Start date of current active CATS_DATA_STREAM record in the format DD/MM/YYYY

 

Example
The real data in the example below is substituted with dummy data.

<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,SDR_Key4,SDR_Key5,Field,MDP,NMISTATUSCODE,STARTDATE of current inactive NMISTATUSCODE record,MDM Datastream,STARTDATE of current active MDM Datastream record
D,ADWNAN_INTERVAL,2024-06-10,AAAAA,LNSP,EMDM,n/a,9999999999,,,,,n/a,MDPPID,D,22/03/2024,E1,26/10/2022 
</CSVData>
            

ADWNAN_INTERVAL _ACT

Purpose

Identifies non-active NMIs where active datastreams contain non-zero interval data

Availability

The ADWNAN_INTERVAL _ACT query is available from the first weekly RM29 report run after 6 December 2026

Content

Lists non-active NMIs that have active datastreams (E, B, or N suffixes with datastream types I or P) and non-zero interval data. The query is provided to the LNSP associated with the NMI.

A NMI can appear multiple times if more than one active datastream meets the query criteria

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

MDM

Header Values

See headers

Format

aseXML compliant XML message with csv payload

Query inclusion criteria

A NMI is included in the query if it has a status of D, X or G, an active datastream, no embedded network child, and non-zero actual interval data in the relevant period. The query helps identify NMIs where actual meter reads may indicate an incorrect NMI status or an unrecorded reconnection.

The query uses a rolling assessment period starting 7 days before the query run date and extends back 140 days to capture Revision 2 changes.

The query excludes low-level actual reads below the configured meter creep threshold. This reduces investigation of negligible meter readings on non-active NMIs.

The minimum floor values are listed below.

Interval length

Floor value

5-minute

0.003 kWh

15-minute

0.01 kWh

30-minute

0.02 kWh

 

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

ADWNAN_INTERVAL_ACT

N/A

Query Identifier

Stat_Date

2027-01-11

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

The relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

EMDM

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

SDR_Key2

n/a

N/A

[Not Applicable]

SDR_Key3

n/a

N/A

[Not Applicable]

SDR_Key4

n/a

N/A

[Not Applicable]

SDR_Key5

n/a

N/A

[Not Applicable]

Field

n/a

N/A

[Not Applicable]

MDP

ACTIVMDP

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the MDP role

NMISTATUSCODE

D

Status

The code used to indicate the status of the NMI.

STARTDATE of current inactive NMISTATUSCODE record

2026/12/10

FromDate

Start date of current inactive NMI Status Code record in CATS_NMI_DATA in the format DD/MM/YYYY

MDM Datastream

E1

Suffix

The Suffix field in the CATS_DATA_STREAM table is used to identify a physical data source obtained from the meter

STARTDATE of current active MDM Datastream record

2024/09/18

FromDate

Start date of current active CATS_DATA_STREAM record in the format DD/MM/YYYY

 

Example
Copy
<CSVData> 
QueryId,Count,QueryCount 
ADWNAN_INTERVAL_ACT,3,3238
<CSVData>
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,SDR_Key4,SDR_Key5,Field,MDP,NMISTATUSCODE,STARTDATE of current inactive NMISTATUSCODE record,MDM Datastream,STARTDATE of current active MDM Datastream record
D,ADWNAN_INTERVAL_ACT,2027-01-11,ENERGEXP,LNSP,EMDM,,NMI0000001,,,,,,ACTIVMDP,D,2026/12/10,E1,2024/09/18
D,ADWNAN_INTERVAL_ACT,2027-01-11,ENERGEXP,LNSP,EMDM,,NMI0000002,,,,,,ACTIVMDP,D,2026/12/22,E1,2025/06/23
D,ADWNAN_INTERVAL_ACT,2027-01-11,ENERGEXP,LNSP,EMDM,,NMI0000003,,,,,,ACTIVMDP,X,2027/01/02,E1,2025/09/26
</CSVData>

ADWNAN_ BASIC

Purpose

Identifies where Datastreams are active but the status of the NMI is Not-Active and the MDP sends non-zero metering data

Content

ACTIVE DATASTREAM WITH A NON-ACTIVE NMI

 

List of all non-active NMIs, having an active Datastream(s) and non-zero data, Basic or Consumption

 

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

MDM

Header Values

See header

Format

aseXML compliant XML message with csv payload

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

ADWNAN_BASIC

N/A

Query Identifier

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

The relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

EMDM

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

SDR_Key2

n/a

N/A

[Not Applicable]

SDR_Key3

n/a

N/A

[Not Applicable]

SDR_Key4

n/a

N/A

[Not Applicable]

SDR_Key5

n/a

N/A

[Not Applicable]

Field

n/a

N/A

[Not Applicable]

MDP

MDPPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the MDP role

NMISTATUSCODE

D

Status

The code used to indicate the status of the NMI.

STARTDATE of current inactive NMISTATUSCODE record

22/03/2024

FromDate

Start date of current inactive NMI Status Code record in CATS_NMI_DATA in the format DD/MM/YYYY

MDM Datastream

E1

Suffix

The Suffix field in the CATS_DATA_STREAM table is used to identify a physical data source obtained from the meter

STARTDATE of current active MDM Datastream record

26/10/2022

FromDate

Start date of current active CATS_DATA_STREAM record in the format DD/MM/YYYY

 

Example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,SDR_Key4,SDR_Key5,Field,MDP,NMISTATUSCODE,STARTDATE of current inactive NMISTATUSCODE record,MDM Datastream,STARTDATE of current active MDM Datastream record
D,ADWNAN_BASIC,2024-06-10,AAAAA,LNSP,EMDM,n/a,9999999999,,,,,n/a,MDPPID,
</CSVData>

 

CTCERR

Purpose

Identifies where the Customer Threshold Code is not populated

 

Content

CUSTOMER THRESHOLD CODE

List of NMIs within MSATS without a Customer Threshold Code. Please enter the correct Customer Threshold Code

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

CTCERR

N/A

Query Identifier

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

The relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

CATS

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

SDR_Key2

n/a

N/A

[Not Applicable]

SDR_Key3

n/a

N/A

[Not Applicable]

NMIStart_Date

2024-09-26

FromDate

Start Date of the NMI or Start Date of Record Update

NMIEnd_Date

9999-12-31

ToDate

Date Record Ends

Field

n/a

N/A

[Not Applicable]

NMI_Status

A

Status

The code used to indicate the status of the NMI

NMI_Classification

SMALL

NMIClassificationCode

The code used to indicate the NMI Classification Code of this NMI

Value3

n/a

N/A

[Not Applicable]

Value4

n/a

N/A

[Not Applicable]

Value5

n/a

N/A

[Not Applicable]

 

Example

 

The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI,SDR_Key2,SDR_Key3,NMIStart_Date,NMIEnd_Date,Field,NMI_Status,NMI_Classification,Value3,Value4,Value5 
D,CTCERR,2024-10-07,PARTID,LNSP,CATS,n/a,9999999999,,,2024-09-26,9999-12-31,n/a,A,LARGE,,, 
</CSVData>

DLFERR

Purpose

Identifies where the DLF code assigned to the NMI is incorrect

Content

INCORRECT DLFS FOR NON-CHILD NMIS CREATED WITHIN MSATS

 

List of non-child NMIs created within MSATS that may have an incorrect DLF Code. Please investigate and correct the DLF code where applicable

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

DLFERR

N/A

Query Identifier

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

The relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

CATS

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI

9999999999

NMI

This number is unique for each connection point within the NEM

TNI

F001

TransmissionNode

Identifier

This value must correspond to a valid code in the CATS_TNI_Codes table

CODE

JL40

TransmissionNode

Identifier2

TNI Code assigned, by AEMO, to a distribution network into which energy normally flows through a connection point between adjacent distribution networks having a single NMI

This value must correspond to a valid code in the CATS_TNI_Codes table

Start_Date

2024-04-16

FromDate

Start Date of the NMI or Start Date of Record Update

End_Date

9999-12-31

ToDate

Date Record Ends

Field

n/a

N/A

[Not Applicable]

DLFVALUE

1.0482

DistributionLossFactorValue

Numeric value up to 5 decimal places, reflecting the value of the DLF Code

Value2

n/a

N/A

[Not Applicable]

Value3

n/a

N/A

[Not Applicable]

Value4

n/a

N/A

[Not Applicable]

Value5

n/a

N/A

[Not Applicable]

 

Example

The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI,TNI,CODE,Start_Date,End_Date,Field,DLFVALUE,Value2,Value3,Value4,Value5
D,DLFERR,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,F001,JL40,2024-04-16,9999-12-31,n/a,1.0482,,,,
</CSVData> 

 

LNSPERR_CHILD

Purpose

Identifies where the LNSP participant ID assigned to a Child NMI is incorrect

Content

LNSP PARTICIPANT ID ERROR FOR CHILD NMI

 

The LNSP Participant ID for child NMIs identified as possibly incorrect. Please investigate and arrange for MSATS to be amended with the correct data for the connection point(s)

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

LNSPERR_CHILD

N/A

Query Identifier

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

CATS

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

SDR_Key2

n/a

N/A

[Not Applicable]

SDR_Key3

n/a

N/A

[Not Applicable]

StartDate

2007-03-08

FromDate

Start Date of the NMI or Start Date of Record Update

EndDate

9999-12-31

ToDate

Date Record Ends

Field

n/a

N/A

[Not Applicable]

lnsp_id

PARTID

Party

Participant ID of the LNSP

Value2

n/a

N/A

[Not Applicable]

Value3

n/a

N/A

[Not Applicable]

Value4

n/a

N/A

[Not Applicable]

Value5

n/a

N/A

[Not Applicable]

 

Example

The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,StartDate,EndDate,Field,lnsp_id,Value2,Value3,Value4,Value5 
D,LNSPERR_CHILD,2024-09-30,PARTID,LNSP,CATS,n/a,9999999999,,,2007-03-08,9999-12-31,n/a,PARTID,,,,
</CSVData>

 

NMIST1

Purpose

Identifies where a CATS CR updated the NMI status to ‘A’ with an effective start date more than 5 days in the past

Content

NMI STATUS NOT UPDATED TO 'A' WITHIN 5 BUSINESS DAYS ERROR

 

List of NMIs within MSATS not updated to ACTIVE within 5 business days of the active state of site

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

QueryId

NMIST1

N/A

Query Identifier

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

Source

CATS

N/A

[Fixed value]

Table

n/a

N/A

[Not Applicable]

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

SDR_Key2

n/a

N/A

[Not Applicable]

SDR_Key3

n/a

N/A

[Not Applicable]

ProposedDate

n/a

N/A

Date used in the Change Request for the change to occur

CreateDate

n/a

N/A

Date the Change Request was raised

Field

n/a

N/A

[Not Applicable]

RequestID

1415800614

N/A

Change request ID of the Change Request raised

CR_Code

5051

N/A

Change request used to update the NMI Status

CR_Status

COM

N/A

Status of the Change Request

LastUpdate

n/a

N/A

Date of the Data Record change of the change request

Value5

n/a

N/A

[Not Applicable]

 

Example
The real data in the example below is substituted with dummy data.
<CSVData> 
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,ProposedDate,CreateDate,Field,RequestID,CR_Code,CR_Status,LastUpdate,Value5
D,NMIST1,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,,,2024-05-29,2024-06-07,n/a,1415800614,5051,COM,2024-06-08,
</CSVData>

 

NMIST2

Purpose

Identifies where a CATS CR updated the NMI status to ‘X’ with an effective start date more than 5 days in the past

Content

NMI STATUS NOT UPDATED TO 'X' WITHIN 5 BUSINESS DAYS ERROR

 

List of NMIs within MSATS not updated to EXTINCT within 5 business days of extinct state of site

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

NMIST2

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

SDR_Key2

n/a

N/A

[Not Applicable]

9

SDR_Key3

n/a

N/A

[Not Applicable]

10

Proposed_Date

2023-11-22

N/A

Date used in the Change Request for the change to occur

11

Create_Date

2024-06-06

N/A

Date the Change Request was raised

12

Field

n/a

N/A

[Not Applicable]

13

RequestID

1415632384

N/A

Change request ID of the Change Request raised

14

CR_Code

5051

N/A

Change request used to update the NMI Status

15

CR_Status

COM

N/A

Status of the Change Request

16

LastUpdate

2024-06-07

N/A

Date of the Data Record change of the change request

17

Value5

n/a

N/A

[Not Applicable]

 

Example

The real data in the example below is substituted with dummy data.
<CSVData> 
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,Proposed_Date,Create_Date,Field,RequestID,CR_Code,CR_Status,LastUpdate,Value5
D,NMIST2,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,,,2023-11-22,2024-06-06,n/a,1415632384,5051,COM,2024-06-07, 
</CSVData>

 

NMIST4

Purpose

Identifies where a CATS CR updated the NMI status to ‘D’ with an effective start date more than 5 days in the past

Content

NMI STATUS NOT UPDATED TO 'D' WITHIN 5 BUSINESS DAYS ERROR

 

List of NMIs within MSATS updated to be de-energised within 5 business days of de-energised state of the site

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

NMIST4

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

SDR_Key2

n/a

N/A

[Not Applicable]

9

SDR_Key3

n/a

N/A

[Not Applicable]

10

ProposedDate

2023-11-18

N/A

Date used in the Change Request for the change to occur

11

CreateDate

2024-06-03

N/A

Date the Change Request was raised

12

Field

n/a

N/A

[Not Applicable]

13

RequestID

1414804113

N/A

Change request ID of the Change Request raised

14

CR_Code

5051

N/A

Change request used to update the NMI Status

15

CR_Status

COM

N/A

Status of the Change Request

16

LastUpdate

2024-06-04

N/A

Date of the Data Record change of the change request

17

Value5

n/a

N/A

[Not Applicable]

 

Example
The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,ProposedDate,CreateDate,Field,RequestID,CR_Code,CR_Status,LastUpdate,Value5
D,NMIST4,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,,,2023-11-18,2024-06-03,n/a,1414804113,5051,COM,2024-06-04,
</CSVData> 

 

NONETAC

Purpose

Identifies where the NMI not having a Network Tariff

Content

MISSING NETWORK TARRIF CODE

 

List of NMIs within MSATS not having a Network Tariff Code. Please enter the correct Network Tariff Code

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

NONETAC

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI

9999999999

NMI

This number is unique for each connection point within the NEM

8

Serial_No

112258

SerialNumber

The Meter Serial ID uniquely identifies a meter for a given NMI, Maximum 12 Characters (alpha numeric)

Unique for NMI

9

Reg_ID

E1

RegisterID

The RegisterID used to identify a data source obtained from the meter, a single meter may provide multiple data sources

10

NMIStart_Date

2024-09-12

Fromdate

Start Date of the NMI or Start Date of Record Update

11

NMIEnd_Date

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

Calendar_Days

5350

N/A

Amount of Calendar Days NTC not populated

14

Value2

n/a

N/A

[Not Applicable]

15

Value3

n/a

N/A

[Not Applicable]

16

Value4

n/a

N/A

[Not Applicable]

17

Value5

n/a

N/A

[Not Applicable]

 

Example
The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI,Serial_No,Reg_ID,NMIStart_Date,NMIEnd_Date,Field,Calendar_Days,Value2,Value3,Value4,Value5 
D,NONETAC,2024-09-16, LNSPID,LNSP,CATS,n/a, 9999999999,6299880,1,2024-09-12,9999-12-31,n/a,5350,,,,
</CSVData>

 

SAMPLERR

Purpose

Identifies where a SAMPLE participant id has been assigned to a NMI not having a NMI Classification as SAMPLE

 

Content

SAMPLE PARTICIPANT ID ERROR

 

Participant ID's within MSATS for a nominated 'SAMPLE' meter connection point have been identified as incorrect, connection points where the Participant relationships are incorrect (i.e LR, FRMP and NMICLASS need to be set to 'SAMPLE'), or the NMICLASS of 'SAMPLE' is incorrect. Please investigate and arrange appropriate amendments within MSATS for the connection point(s)

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

SAMPLERR

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

SDR_Key2

n/a

N/A

[Not Applicable]

9

SDR_Key3

n/a

N/A

[Not Applicable]

10

StartDate

2001-12-22

Fromdate

Start Date of the NMI or Start Date of Record Update

11

EndDate

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

frmp_id

SAMPLE

Party

Participant ID of the FRMP

14

lr_id

SAMPLE

Party

Participant ID of the LR

15

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

16

Value4

n/a

N/A

[Not Applicable]

17

Value5

n/a

N/A

[Not Applicable]

 

Example
The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,StartDate,EndDate,Field,frmp_id,lr_id,NMI_Class,Value4,Value5 
D,SAMPLERR,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,,,2001-12-22,9999-12-31,n/a,SAMPLE,SAMPLE,SMALL,,
</CSVData>

 

TNIERR

Purpose

Identifies where an incorrect TNI has been assigned

 

Content

INCORRECT TNIS FOR NON-CHILD NMIS CREATED WITHIN MSATS

 

List of non-child NMIs created within MSATS that may have an incorrect TNI Code. Please investigate and correct the TNI Code

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

TNIERR

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI

9999999999

NMI

This number is unique for each connection point within the NEM

8

SDR_Key2

n/a

N/A

[Not Applicable]

9

SDR_Key3

n/a

N/A

[Not Applicable]

10

StartDate

2023-11-18

Fromdate

Start Date of the NMI or Start Date of Record Update

11

EndDate

9999-12-31

Todate

High End Date

12

Field

n/a

N/A

[Not Applicable]

13

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

14

TNI

NMBK

TransmissionNodeIdentifier

This value must correspond to a valid code in the CATS_TNI_Codes table

15

State

NSW

JurisdictionCode

Jurisdiction

16

Value4

n/a

N/A

[Not Applicable]

17

Value5

n/a

N/A

[Not Applicable]

 

Example
The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI,SDR_Key2,SDR_Key3,Start_Date,End_Date,Field,NMI_Class,TNI,State,Value4,Value5 
D,TNIERR,2024-10-07,PARTID,LNSP,CATS,n/a,9999999999,n/a,n/a,2023-11-18,9999-12-31,n/a,SMALL,NMBK,NSW,,
</CSVData>

 

SAPSDLF

Purpose

Identifies where a NMI has an incorrect TNI that is not in a SAPS area

Content

SAPS DLF ASSIGNED TO NON-SAPS NMI

 

The NMI assigned with a DLF Code of SAPS which is connected to a TNI code that is not in a SAPS Area, the DLF Code needs amendment to the appropriate DLF Code

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

SAPSDLF

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

SDR_Key2

n/a

N/A

[Not Applicable]

9

SDR_Key3

n/a

N/A

[Not Applicable]

10

StartDate

2023-11-18

Fromdate

Start Date of the NMI or Start Date of Record Update

11

EndDate

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

14

Settle_Ind

NEM

N/A

Settlement type (ISO, NEM, SAP)

15

DLF_Code

NHV1

DistributionLossFactorCode

A four character alpha-numeric code used to identify DLF values, all NMIs must be assigned a DLF Code, refer to AEMO Distribution Loss Factor documents for each financial year

16

TNI_Code

NRGE

TransmissionNodeIdentifier

This value must correspond to a valid code in the CATS_TNI_Codes table

17

Profile_Area

n/a

N/A

Profile Area (CITIPOWER,ERGONSAPS)

 

Example

No example provided as there hasn’t been any errors reported in the last 12 month against this report.

 

SAPSNONMI

Purpose

There are no active SAPS End User Connection Points assigned to the SAPS TNI where an active SAPS Generator Connection Point exists

Content

SAPS TNI DOES NOT HAVE AN ACTIVE SAPS END USER CONNECTION POINTS

 

There are no active SAPS End User Connection Points assigned to the SAPS TNI where an active SAPS Generator Connection Point exists

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

SAPSNONMI

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

SDR_Key2

n/a

N/A

[Not Applicable]

9

SDR_Key3

n/a

N/A

[Not Applicable]

10

StartDate

2023-11-18

Fromdate

Start Date of the NMI or Start Date of Record Update

11

EndDate

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

TNI_Code

F010

TransmissionNode

Identifier

This value must correspond to a valid code in the CATS_TNI_Codes table

14

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

15

NMI_Status

A

Status

Code used to indicate the status of the NMI

16

Value4

n/a

N/A

[Not Applicable]

17

Value5

n/a

N/A

[Not Applicable]

 

SAPSNONMI Example:

The real data in the example below is substituted with dummy data.
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,sdr_key_2,sdr_key_3,Start_Date,End_Date, Field, TNI_Code,NMI_Class,NMI_Status,Value4, Value5
D,SAPSNONMI,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,,,2024-05-27,9999-12-31,n/a,F010,NREG,G,,
</CSVData>

 

SAPSENP

Purpose

Embedded Networks are not valid within a SAPS this NMI has an Embedded Network Code assigned and needs correction

Content

SAPS NMI HAS AN EMBEDDED NETWORK CODE.

 

Embedded Networks are not valid within a SAPS this NMI has an Embedded Network Code assigned and needs amendment

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

SAPSENP

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

EmbNetParent

n/a

ParentEmbedded

NetworkIdentifier

Embedded Network Code

9

EmbNetChild

n/a

ChildEmbedded

NetworkIdentifier

Embedded Network Code

10

Start_Date

2023-11-18

Fromdate

Start Date of the NMI or Start Date of Record Update

11

End_Date

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

TNI_Code

NRGE

TransmissionNode

Identifier

This value must correspond to a valid code in the CATS_TNI_Codes table

14

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

15

NMI_Status

A

Status

Code used to indicate the status of the NMI

16

DLF_Code

NHV1

DistributionLossFactorCode

A four character alpha-numeric code used to identify DLF values, all NMIs must be assigned a DLF Code, refer to AEMO Distribution Loss Factor documents for each financial year

17

Value5

n/a

N/A

[Not Applicable]

 

Example

No example provided as there hasn’t been any errors reported in the last 12 month against this report.

 

SAPSNOGEN

Purpose

There is no active SAPS Generation Connection Point Assigned to the SAPS TNI to supply energy to the End User Connection Points

Content

SAPS TNI DOES NOT HAVE AN ACTIVE SAPS GENERATION CONNECTION POINT

 

There is no active SAPS Generation Connection Point Assigned to the SAPS TNI to supply energy to the End User Connection Points

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

SAPSNOGEN

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

sdr_key_2

n/a

N/A

[Not Applicable]

9

sdr_key_3

n/a

N/A

[Not Applicable]

10

Start_Date

2023-11-18

Fromdate

Start Date of the NMI or Start Date of Record Update

11

End_Date

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

TNI_Code

NRGE

TransmissionNode

Identifier

This value must correspond to a valid code in the CATS_TNI_Codes table

14

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

15

NMI_Status

A

Status

Code used to indicate the status of the NMI

16

Value4

n/a

N/A

[Not Applicable]

17

Value5

n/a

N/A

[Not Applicable]

 

Example

No example provided as there hasn’t been any errors reported in the last 12 month against this report.

 

NONSAPSDLF

Purpose

The NMI assigned with a DLF Code other that SAPS which is connected to a TNI code that is in a SAPS Area, the DLF Code needs amendment to the SAPS DLF Code

Content

DLF OTHER THAN SAPS ASSIGNED TO A SAPS NMI

 

The NMI assigned with a DLF Code other that SAPS which is connected to a TNI code that is in a SAPS Area, the DLF Code needs amendment to the SAPS DLF Code

Recipient

LNSP – Local Network Service Provider

Delivery

Participant Outbox (FTP), Participant API endpoint (API)

Run Time

Weekly report run on a Monday @ 6 am

Data Source

CATS

Header Values

See headers

Format

aseXML compliant XML message with csv payload

 

Output

Field

H Record

D Record

Standing Data for MSATS – Data Element Name

Description

1

QueryId

NONSAPSDLF

N/A

Query Identifier

2

Stat_Date

2024-06-10

N/A

YYYY-MM-DD

3

ParticipantId

LNSPID

Party

The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role

4

RoleId

LNSP

Role

This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS

5

Source

CATS

N/A

[Fixed value]

6

Table

n/a

N/A

[Not Applicable]

7

NMI_ID

9999999999

NMI

This number is unique for each connection point within the NEM

8

sdr_key_2

n/a

N/A

[Not Applicable]

9

sdr_key_3

n/a

N/A

[Not Applicable]

10

Start_Date

2023-11-18

Fromdate

Start Date of the NMI or Start Date of Record Update

11

End_Date

9999-12-31

Todate

Date Record Ends

12

Field

n/a

N/A

[Not Applicable]

13

TNI_Code

F001

TransmissionNode

Identifier

This value must correspond to a valid code in the CATS_TNI_Codes table

14

NMI_Class

SMALL

NMIClassificationCode

Code used to indicate the NMI Classification Code of this NMI

15

NMI_Status

A

Status

Code used to indicate the status of the NMI

16

Value4

n/a

N/A

[Not Applicable]

17

Value5

n/a

N/A

[Not Applicable]

 

Example
The real data in the example below is substituted with dummy data.
<CSVData> 
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,sdr_key_2,sdr_key_3,Start_Date,End_Date, Field, TNI_Code,NMI_Class,NMI_Status,DLF_Code, Value5
D,NONSAPSDLF,2024-06-10,AAAAA,LNSP,CATS,n/a,9999999999,,,2024-04-16,9999-12-31,n/a,F001,SMALL,A,JL40,
</CSVData>