RP – Metering Co-ordinator
HIGHREADS
Purpose |
Identifies where a Basic, MRIM or VicAMI NMI has exceeded the meter installation capacity for the meter installation type |
Content |
BASIC MRIM AND VICAMI NMIS THAT EXCEED METER INSTALLATION CAPACITY
BASIC MRIM and VICAMI NMIs greater than 100MWh (NSW, QLD) or 160MWh (VIC, ACT, SA) or 150MWh (TAS) as per Metrology Procedure A (3.5) |
Recipient |
RP – Metering Co-ordinator |
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
Run Time |
Weekly report run on a Thursday @ 6 am |
Data Source |
MDM |
Header Values |
See headers |
Format |
aseXML compliant XML message with csv payload |
Header values details
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
1 |
QueryId |
HIGHREADS |
N/A |
Query Identifier |
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
3 |
ParticipantId |
RPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
4 |
RoleId |
RP |
Role |
This defines the relationship (Role) of the Participant with the NMI in CATS_NMI_PARTICIPANT_RELATIONS |
5 |
Source |
MDM |
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 |
MC |
PARTID |
Party |
Participant ID of the MC |
9 |
SDR_KET_3 |
n/a |
N/A |
Not applicable |
10 |
Start_Date |
2024-01-19 |
Fromdate |
Not applicable |
11 |
End_Date |
9999-12-31 |
Todate |
Not applicable |
12 |
Field |
n/a |
N/A |
[Not Applicable] |
13 |
LR |
PARTID |
Party |
Participant ID of the Local Retailer |
14 |
LNSP |
PARTID |
Party |
Participant ID of the LNSP |
15 |
TNI |
SJP1 |
TransmissionNodeIdentifier |
This value must correspond to a valid code in the CATS_TNI_Codes table |
16 |
Yearly_Sum_KWh |
175693.63999999998 |
N/A |
Yearly Sum of Consumption in KWh |
17 |
Value5 |
n/a |
N/A |
[Not Applicable] |
HIGHREADS Example:
<CSVData>
H,QueryId,Stat_Date,Participant_ID,Role_ID,Source,Table,NMI_ID,FRMP,SDR_KET_3,Start_Date,End_Date,Field, LR,LNSP,TNI,Yearly_Sum_KWh,Value5
D,HIGHREADS,2024-09-26,PARTID,RP,EMDM,,9999999999,PARTID,,,,,GLOPOOL,PARTID,SJP1,175693.63999999998,136
</CSVData>
METERERR
Purpose |
A list of NMIs where an incorrect metering installation type code may have been identified |
Content |
RESPONSIBLE PERSON NMI ERROR
The NMI within MSATS identified as possibly incorrect based on the invalid metering installations codes of BASIC, or MRIM post 1 December 2017 for small customers for RP group. Please investigate and arrange for MSATS to amend with the correct MITC or MC for the connection point(s) |
Recipient |
RP – Metering Co-ordinator |
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
Run Time |
Weekly report run on a Thursday @ 6 am |
Data Source |
CATS |
Header Values |
See headers |
Format |
aseXML compliant XML message with csv payload |
Header values details
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
1 |
QueryId |
METERERR |
N/A |
Query Identifier |
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
3 |
ParticipantId |
RPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
4 |
RoleId |
RP |
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 |
Meter_Serial |
112258 |
SerialNumber |
The Meter Serial ID uniquely identifies a meter for a given NMI, Maximum 12 Characters (alpha numeric) Unique for NMI |
9 |
SDR_Key3 |
n/a |
N/A |
[Not Applicable] |
10 |
StartDate |
2024-01-19 |
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 |
Bad_MITC_Count |
n/a |
N/A |
Count of possible incorrect meter types. |
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] |
METERERR Example:
<CSVData>
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,Meter_Serial,SDR_Key3,StartDate,EndDate,Field,Bad_MITC_Count,Value2,Value3,Value4,Value5
D,METERERR,2024-10-10,PARTID,RP,CATS,n/a,9999999999,267177,,,,n/a,1,,,,
</CSVData>
RPERR1
Purpose |
Identifies a list of RP Participant IDs that are incorrect based on the RP and FRMP relationship for a transmission connection point |
Content |
RESPONSIBLE PERSON PARTICIPANT ID ERROR
The RP Participant ID within MSATS identified as possibly incorrect based on the RP and FRMP relationship for a transmission connection point. Please investigate and arrange for MSATS to amend with the correct Participant ID relationship(s) for the transmission connection point(s) |
Recipient |
RP – Metering Co-ordinator |
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
Run Time |
Weekly report run on a Thursday @ 6 am |
Data Source |
CATS |
Header Values |
See headers |
Format |
aseXML compliant XML message with csv payload |
Header values details
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
1 |
QueryId |
RPERR1 |
N/A |
Query Identifier |
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
3 |
ParticipantId |
RPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
4 |
RoleId |
RP |
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 |
2024-01-19 |
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 |
PARTID |
Party |
Participant Id of the FRMP |
14 |
Value2 |
n/a |
N/A |
Participant ID of the LNSP |
15 |
Value3 |
n/a |
N/A |
[Not Applicable] |
16 |
Value4 |
n/a |
N/A |
[Not Applicable] |
17 |
Value5 |
n/a |
N/A |
[Not Applicable] |
RPERR1 Example:
<CSVData>
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,StartDate,EndDate,Field,frmp_id,Value2,Value3,Value4,Value5
D,RPERR1,2024-05-23,PARTID,RP,CATS,n/a,9999999999,WHOLESAL,UNIT,2020-07-01,9999-12-31,n/a,PARTID,PARTID,,,
</CSVData>
RPERR2
Purpose |
Identifies a list of RP Participant ID that are incorrect based on the RP and FRMP relationship for the connection point |
Content |
RESPONSIBLE PERSON PARTICIPANT ID ERROR
The RP Participant ID within MSATS identified as possibly incorrect based on the RP and FRMP relationship for the connection point. Please investigate and arrange for MSATS to amend with the correct Participant ID relationship(s) for the connection point(s) |
Recipient |
RP – Metering Co-ordinator |
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
Run Time |
Weekly report run on a Thursday @ 6 am |
Data Source |
CATS |
Header Values |
See headers |
Format |
aseXML compliant XML message with csv payload |
Header values details
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
1 |
QueryId |
RPERR2 |
N/A |
Query Identifier |
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
3 |
ParticipantId |
RPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
4 |
RoleId |
RP |
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 |
2024-01-19 |
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 |
PARTID |
Party |
Participant ID of the FRMP |
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] |
RPERR2 Example:
No example provided as there hasn’t been any errors reported in the last 12 month against this report.\
RPERR3
Purpose |
Identifies a list of RP Participant ID that are incorrect based on the RP and LNSP relationship for the connection point AND other than the following metering installation type codes: BASIC, MRIM, UMCP |
Content |
RESPONSIBLE PERSON PARTICIPANT ID ERROR.
The RP Participant ID within MSATS identified as possibly incorrect based on the RP and LNSP relationship for the connection point and other than the following metering installation type codes: BASIC, MRIM, UMCP. Please investigate and arrange for MSATS to amend with the correct Participant ID relationship(s) for the connection point(s) |
Recipient |
RP – Metering Co-ordinator |
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
Run Time |
Weekly report run on a Thursday @ 6 am |
Data Source |
CATS |
Header Values |
See headers |
Format |
aseXML compliant XML message with csv payload |
Header values details
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
1 |
QueryId |
RPERR3 |
N/A |
Query Identifier |
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
3 |
ParticipantId |
RPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
4 |
RoleId |
RP |
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 |
2024-01-19 |
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 |
lnsp_id |
PARTID |
Party |
Participant ID of the LNSP |
14 |
Bad_MITC_Count |
1 |
N/A |
Count of possible incorrect meter types |
15 |
Value3 |
n/a |
N/A |
[Not Applicable] |
16 |
Value4 |
n/a |
N/A |
[Not Applicable] |
17 |
Value5 |
n/a |
N/A |
[Not Applicable] |
RPERR3 Example:
<CSVData>
H,QueryId,Stat_Date,ParticipantID,RoleID,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,StartDate,EndDate,Field,lnsp_id,Bad_MITC_Count,Value3,Value4,Value5
D,RPERR3,2024-10-10,PARTID,RP,CATS,n/a,9999999999,,,2014-01-01,9999-12-31,n/a,PARTID,1,,,
</CSVData>
ME_EXPIRED
Purpose |
Identifies a list of exemptions that have exceeded their expiry date and set to expire |
Content |
Exemption has exceeded the expiry date and set to expire
The Exemption has exceeded the expiry date and set to expire |
Recipient |
RP – Metering Co-ordinator |
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
Run Time |
Weekly report run on a Thursday @ 6 am |
Data Source |
CATS |
Header Values |
See headers |
Format |
aseXML compliant XML message with csv payload |
Header values details
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
1 |
QueryId |
ME_EXPIRED |
N/A |
Query Identifier |
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
3 |
ParticipantId |
RPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
4 |
RoleId |
RP |
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 |
ME_ID |
000000000000000 |
N/A |
Meter Exemption ID |
8 |
Sdr_Key_2 |
n/a |
N/A |
[Not Applicable] |
9 |
Sdr_Key_3 |
n/a |
N/A |
[Not Applicable] |
10 |
Start_Date |
2024-01-19 |
Fromdate |
Start Date of Exemption |
11 |
End_Date |
9999-12-31 |
Todate |
End Date of Exemption |
12 |
Field |
n/a |
N/A |
[Not Applicable] |
13 |
ME_Status |
EXPIRED |
N/A |
Meter Exemption Status |
14 |
Category |
MALFUNCTION |
N/A |
Category of Exemption |
15 |
Type |
DEFECTIVE |
N/A |
Type of Malfunction |
16 |
Nature |
CUSTOMER |
N/A |
Nature of Malfunction |
17 |
NMI_Qt |
1 |
N/A |
NMI Quantity in Exemption |
ME_EXPIRED Example:
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,ME_ID,Sdr_Key_2,Sdr_Key_3,Start_Date,End_Date,Field,ME_Status,Category,Type,Nature,NMI_Qt
D,ME_EXPIRED,2024-05-23,PARTID,RP,CATS,n/a,000000000000000,,,2024-04-04,2024-05-21,n/a,EXPIRED,MALFUNCTION,DEFECTIVE,CUSTOMER,1
</CSVData>