MDP – metering data provider queries
ADWNAN_INTERVAL _SUBS
|
Purpose |
Identifies non-zero interval data submitted against a non-active NMI |
|
Availability |
The ADWNAN_INTERVAL _SUBS 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 MDP role for the NMI. A NMI can appear multiple times if more than one active datastream meets the query criteria |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 at least one trading interval with a quality flag of S, F or E during the relevant period. 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. |
Output
|
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
|
QueryId |
ADWNAN_INTERVAL_SUBS |
N/A |
Query Identifier |
|
Stat_Date |
2027-01-11 |
N/A |
YYYY-MM-DD |
|
ParticipantId |
ACTIVMDP |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
RoleId |
MDP |
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 |
NMI0000001 |
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] |
|
LNSP |
ENERGEXP |
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
<CSVData>
QueryId,Count,QueryCount
ADWNAN_INTERVAL_SUBS,3,3238
<CSVData>
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,SDR_Key2,SDR_Key3,SDR_Key4,SDR_Key5,Field,LNSP,NMISTATUSCODE,STARTDATE of current inactive NMISTATUSCODE record,MDM Datastream,STARTDATE of current active MDM Datastream record
D,ADWNAN_INTERVAL_SUBS,2027-01-11,ACTIVMDP,MDP,EMDM,,NMI0000001,,,,,,ENERGEXP,D,2026/12/10,E1,2024/09/18
D,ADWNAN_INTERVAL_SUBS,2027-01-11,ACTIVMDP,MDP,EMDM,,NMI0000002,,,,,,ENERGEXP,D,2026/12/22,E1,2025/06/23
D,ADWNAN_INTERVAL_SUBS,2027-01-11,ACTIVMDP,MDP,EMDM,,NMI0000003,,,,,,ENERGEXP,X,2027/01/02,E1,2025/09/26
</CSVData>
15ERRS
|
Purpose |
Identifies where reads are received that are greater than 2 business days from the CR1000 actual change date |
|
Content |
ACTUAL CHANGE DATES NOT COMPLIANT WITH CATS PROCEDURES
List of NMIs for which the 1500 Change Request submitted in response to a FRMP CR1000 nominates an 'Actual Change Date' that is not within the 2 business days of reading the meter, (taken as the difference between the Actualchangedate and the Maintcreatedate of the CR1500 submitted) |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
15ERRS |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
NMI. This number is unique for each connection point within the NEM |
|
8 |
CREQUESTID |
1111111111 |
N/A |
Change Request ID |
|
9 |
SDR_KEY3 |
N/A |
N/A |
[Not Applicable] |
|
10 |
MDPCreateDt |
2024-09-19 |
N/A |
Date CR was Created |
|
11 |
MDPActualDate |
2024-09-03 |
N/A |
Actual Change Date in the CR |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
DIFFDATE |
16 |
N/A |
Amount of days difference between the Actual Change Date and the date it was created |
|
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] |
15ERRS example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,CREQUESTID,SDR_KEY3,MDPCreateDt,MDPActualDate,Field,DIFFDATE,Value2,Value3,Value4,Value5
D,15ERRS,2024-09-25,PARTID,MDP,CATS,N/A,9999999999,1111111111,N/A,2024-09-19,2024-09-03,N/A,16,,,,
</CSVData>
DANDS
|
Purpose |
Identifies where a NMI has multiple active datastreams, this may include Duplicate Non-Interval suffixes, Duplicate Interval suffixes or Interval and Non-Interval suffixes active for the same settlement date |
|
Content |
DUPLICATE ACTIVE DATSTREAMS
List of NMI with duplicate active datastreams or Interval and Non-Interval datastreams active for the same period. Please amend the datastreams assignments urgently |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
DANDS |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
SUFFIX_1 |
11 |
suffix |
Datastream Suffix |
|
9 |
METER_TYPE_1 |
C |
datastreamtype |
Datastream Type |
|
10 |
DS_START_DATE_1 |
2022-02-22 |
startdate |
Datastream Start Date |
|
11 |
DS_END_DATE_1 |
9999-12-31 |
enddate |
Datastream End Date |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
SUFFIX_2 |
K1 |
suffix |
Datastream Suffix |
|
14 |
METER_TYPE_2 |
N |
datastreamtype |
Datastream Type |
|
15 |
DS_START_DATE_2 |
06-SEP-2024 |
startdate |
Datastream Start Date |
|
16 |
DS_END_DATE_2 |
31-DEC-9999 |
enddate |
Datastream End Date |
|
17 |
Value5 |
N/A |
N/A |
[Not Applicable] |
DANDS example
<CSVData>
H,QueryId,Stat_Date,PARTICIPANTID,ROLEID,Source,Table,NMI_ID,SUFFIX_1,METER_TYPE_1,DS_START_DATE_1,DS_END_DATE_1,Field,SUFFIX_2,METER_TYPE_2,DS_START_DATE_2,DS_END_DATE_2,Value5
D,DANDS,2024-10-09,PARTID,MDP,CATS,N/A,9999999999,11,C,2022-02-22,9999-12-31,N/A,K1,N,06-SEP-2024,31-DEC-9999,
</CSVData>
DSERR
|
Purpose |
Identifies where a NMI Datastream not having a status code ‘A’ active or ‘I’ inactive |
|
Content |
DATASTREAM STATUS ERROR
List of NMI suffixes or datastreams that have an incorrect status Code. Status Codes for datastreams in MSATS may only have the status codes of I or A. Please amend the status codes accordingly |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
DSERR |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
SUFFIX |
11 |
suffix |
Datastream Suffix |
|
9 |
PROFILENAME |
NOPROF |
ProfileName |
The Profile Name identifies the name of the algorithmically derived shape used to allocate a Datastream's consumption to TIs, this value must correspond to a valid code in the PROFILE table |
|
10 |
DS_Start_Date |
06-SEP-2024 |
startdate |
Datastream Start Date |
|
11 |
DS_End_Date |
31-DEC-9999 |
enddate |
Datastream End Date |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
STREAMSTATUSCODE |
A |
ElectricityDataStream/Stat us |
Code used to indicate the status of the suffix, this value must correspond to a valid Datastream Status Code as specified in the MSATS Procedures: CATS procedures |
|
14 |
DATASTREAMTYPE |
I |
DataStreamType |
Indicates the primary function of the ElectricityDatastream Suffix. i.e. inclusion within NEM Settlement calculations, UFE analysis, profile peeloff or Vic TUOS This value must correspond to a valid DataStreamType in the Data Stream Type Codes reference table |
|
15 |
Value3 |
N/A |
N/A |
[Not Applicable] |
|
16 |
Value4 |
N/A |
N/A |
[Not Applicable] |
|
17 |
Value5 |
N/A |
N/A |
[Not Applicable] |
DSERR example
No example provided as there hasn’t been any errors reported in the last 12 month against this report.
MASDS
|
Purpose |
Identifies where there is Active E & D suffixes or B & A suffixes with a NMI Datastream type of ‘I’ active for the same settlement day |
|
Content |
MULTIPLE ACTIVE SETTLEMENT DATASTREAMS
List of NMIs having multiple active settlement datastreams of different suffix codes |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
MASDS |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
SUFFIX_1 |
11 |
suffix |
Datastream Suffix |
|
9 |
DS_TYPE_1 |
C |
datastreamtype |
Datastream Type |
|
10 |
START_DATE |
2022-02-22 |
startdate |
Datastream Start Date |
|
11 |
END_DATE |
9999-12-31 |
enddate |
Datastream End Date |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
SUFFIX_2 |
K1 |
suffix |
Datastream Suffix |
|
14 |
DS_TYPE_2 |
N |
datastreamtype |
Datastream Type |
|
15 |
START_DATE_2 |
06-SEP-2024 |
startdate |
Datastream Start Date |
|
16 |
END_DATE_2 |
31-DEC-9999 |
enddate |
Datastream End Date |
MASDS example
No example provided as there hasn’t been any errors reported in the last 12 month against this report.
MASDSWN
|
Purpose |
Identifies where there is an Active E, D, B or A suffix and an Active N suffix with a NMI Datastream type of ‘I’ active for the same settlement day |
|
Content |
MULTIPLE ACTIVE SETTLEMENT DATASTREAMS WITH NET
List of NMIs having multiple active settlement datastreams of different suffix codes one of which is a Net code |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
MASDSWN |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
SUFFIX_1 |
N1 |
suffix |
Datastream Suffix |
|
9 |
DS_TYPE_1 |
I |
datastreamtype |
Datastream Type |
|
10 |
START_DATE |
2020-05-15 |
startdate |
Datastream Start Date |
|
11 |
END_DATE |
9999-12-31 |
enddate |
Datastream End Date |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
SUFFIX_2 |
B1 |
suffix |
Datastream Suffix |
|
14 |
DS_TYPE_2 |
I |
datastreamtype |
Datastream Type |
|
15 |
START_DATE_2 |
07-OCT-2024 |
startdate |
Datastream Start Date |
|
16 |
END_DATE_2 |
31-DEC-9999 |
enddate |
Datastream End Date |
MASDSWN example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,SUFFIX_1,DS_TYPE_1,START_DATE,END_DATE,Field,SUFFIX_2,DS_TYPE_2,START_DATE_2,END_DATE_2
D,MASDSWN,2024-10-09,PARTID,MDP,CATS,N/A,9999999999,N1,I,2020-05-15,9999-12-31,N/A,B1,I,07-OCT-2024,31-DEC-9999,
</CSVData>
MDPERR
|
Purpose |
Identifies where a MDP is incorrectly assigned to a NMI with a Basic meter installed |
|
Content |
POSSIBLE INCORRECT MDP ASSIGNMENT
List of NMIs for which the MDP assignment may be incorrect. Please amend where required |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
MDPERR |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
SUFFIX |
11 |
suffix |
Datastream Suffix |
|
9 |
METER_TYPE |
SMALL |
datastreamtype |
Datastream Type |
|
10 |
DS_Start_Date |
2022-02-22 |
startdate |
Datastream Start Date |
|
11 |
DS_End_Date |
9999-12-31 |
enddate |
Datastream End Date |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
IS_ACTIVE |
A |
maintactflg |
NMI Status |
|
14 |
LR |
PARTID |
Party |
Local Retailer Participant ID |
|
15 |
FRMP |
PARTID |
Party |
FRMP Participant ID |
|
16 |
Value4 |
N/A |
N/A |
[Not Applicable] |
|
17 |
Value5 |
N/A |
N/A |
[Not Applicable] |
MDPERR example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,SUFFIX,METER_TYPE,DS_Start_Date,DS_End_Date,Field,IS_ACTIVE,LR,FRMP,Value4,Value5
D,MDPERR,2024-10-09,PARTID,MDP,CATS,N/A,9999999999,11,SMALL,2022-02-22,9999-12-31,N/A,A,PARTID,PARTID,GLOPOOL,
</CSVData>
MDPERR2
|
Purpose |
Identifies where a MDP is incorrectly assigned to a NMI with a COMMS meter installed |
|
Content |
COMMS METERS WITH INCORRECT MDP
List of NMIs for which the MDP assignment may be incorrect. Please amend where required |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
MDPERR2 |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
METERSERIAL |
112258 |
SerialNumber |
The Meter Serial ID uniquely identifies a meter for a given NMI, maximum 12 Characters (alpha numeric) Unique for NMI |
|
9 |
NMI_CLASS |
SMALL |
NMIClassificationCode |
Code used to indicate the NMI Classification Code of this NMI |
|
10 |
DS_START_DATE |
2022-11-23 |
startdate |
Datastream Start Date |
|
11 |
DS_END_DATE |
9999-12-31 |
enddate |
Datastream End Date |
|
12 |
ACTIVE_FLAG |
A |
maintactflg |
Datastream Status |
|
13 |
FRMP |
PARTID |
Party |
FRMP Participant ID |
|
14 |
LNSP |
PARTID |
Party |
LNSP Participant ID |
|
15 |
LR |
GLOPOOL |
Party |
Local Retailer Participant ID |
|
16 |
MITC |
COMMS4D |
meterinstallcode |
Meter Installation Type Code |
MDPERR2 example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,METERSERIAL,NMI_CLASS,DS_START_DATE,DS_END_DATE,field,ACTIVE_FLAG,FRMP,LNSP,LR,MITC
D,MDPERR2,2024-08-14,PARTID,MDP,CATS,N/A,9999999999,3087252,SMALL,2022-11-23,9999-12-31,N/A,A,PARTID,PARTID,GLOPOOL,COMMS4D
</CSVData>
NONSRD
|
Purpose |
Identifies where the Next Schedule Read Date is null |
|
Content |
NEXT SCHEDULED READ DATES THAT ARE NULL IN MSATS BASIC, MRIM and MRAM metered sites where the 'Next Scheduled Read Date' is null in MSATS. Please arrange these update urgently. Please also note: A 'count' is provided for metered sites where there is a large number of NSRD are null, (>60,000) otherwise the information provided is at the meter level The results of the NSRD query depends on the correctness of Meter Register information in the Meter register table updated by the MPB |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
NONSRD |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
METERINSTALLCODE |
COMMS4 |
InstallationTypeCode |
The InstallationTypeCode may identify attributes of a physical metering installation, metering data collection methods or metering data calculation methods, this value must correspond to a valid Meter Installation Type Code |
|
8 |
NMI_ID |
9999999999 |
NMI |
This number is unique for each connection point within the NEM |
|
9 |
SERIAL_NO |
112258 |
SerialNumber |
The Meter Serial ID uniquely identifies a meter for a given NMI, maximum 12 Characters (alpha numeric) Unique for NMI |
|
10 |
NMISTARTDATE |
2023-06-13 |
startdate |
Start date of the record that has a historical NSRD |
|
11 |
NMIENDDATE |
9999-12-31 |
enddate |
End date of the Record |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
Value1 |
N/A |
N/A |
[Not Applicable] |
|
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] |
NONSRD example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,METERINSTALLCODE,NMI_ID,SERIAL_NO,NMISTARTDATE,NMIENDDATE,Field,Value1,Value2,Value3,Value4,Value5
D,NONSRD,2024-08-14,PARTID,MDP,CATS,N/A,BASIC,9999999999,1202258,2023-06-13,9999-12-31,N/A,,,,,
</CSVData>
NSRD
|
Purpose |
Identifies where the Next Scheduled Read Date is not updated in MSATS |
|
Content |
NEXT SCHEDULED READ DATES THAT HAVE NOT BEEN UPDATED IN MSATS
BASIC, MRIM and MRAM metered sites where the 'Next Scheduled Read Date' is not updated. Please arrange to have these updated urgently. Please also note: A 'count' is provided for BASIC metered sites where there is a large number of NSRD not updated (nominally >60,000) otherwise the information provided is at the meter level The results of the NSRD query are also dependant on the Meter Register information being correct in the Meter register table as updated by the MPB |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
NSRD |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
METERINSTALLCODE |
COMMS4 |
InstallationTypeCode |
The InstallationTypeCode may identify attributes of a physical metering installation, metering data collection methods or metering data calculation methods, this value must correspond to a valid Meter Installation Type Code |
|
9 |
SERIAL_NO |
112258 |
SerialNumber |
The Meter Serial ID uniquely identifies a meter for a given NMI, maximum 12 Characters (alpha numeric) Unique for NMI |
|
10 |
NMISTART_DATE |
2024-03-04 |
startdate |
Start date of the record that has a historical NSRD |
|
11 |
NMIEND_DATE |
9999-12-31 |
enddate |
End date of the Record |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
Value1 |
N/A |
N/A |
[Not Applicable] |
|
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] |
NSRD example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,METERINSTALLCODE,NMI_ID,SERIAL_NO,NMIStart_Date,NMIEnd_Date,Field,Value1,Value2,Value3,Value4,Value5
D,NSRD,2024-09-25,PARTID,MDP,CATS,N/A,BASIC,9999999999,001397,2024-03-04,9999-12-31,N/A,,,,,
</CSVData>
NWADS
|
Purpose |
Identifies an active NMI not having active Datastreams |
|
Content |
NMIs WITHOUT ACTIVE DATASTREAMS
List of active connection points, which have no active datastream(s), under the CATS Procedures, Change Retailer (Section 6) 6.1.4 (c) the MDP is required to ensure an active NMI suffix is defined once the NMI has transferred. Please ensure that active datastreams are assigned to these NMI's urgently
|
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
NWADS |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
FRMP |
PARTID |
Party |
FRMP Participant ID |
|
9 |
LR |
PARTID |
Party |
Local Retailer Participant ID |
|
10 |
MAINTCREATEDT |
2016-04-07 |
maintcreatedt |
Date Record Created |
|
11 |
STARTDATE |
2016-03-18 |
startdate |
Start Date of Record |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
NMISTATUSCODE |
A |
Status |
Code used to indicate the status of the NMI |
|
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] |
NWADS example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI,FRMP,LR,MAINTCREATEDT,STARTDATE,Field,NMISTATUSCODE,Value2,Value3,Value4,Value5
D,NWADS,2024-09-25,PARTID,MDP,CATS,N/A,9999999999,PARTID,GLOPOOL,2016-04-07,2016-03-18,N/A,A,,,,
</CSVData>
TWADS
|
Purpose |
Identifies where a transaction is waiting for a read to complete the actual change date |
|
Content |
MSATS TRANSACTIONS WAITING ACTUAL (CHANGE) DATES
List of change of retailer transactions sitting in MSATS waiting for the MDP to submit the actual change date, where the 'proposed date' has reached. Please process these transactions |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 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 |
TWADS |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-06-10 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
The party in CATS_NMI_PARTICIPANT_RELATIONS ID whose relationship (Role) with the NMI is in the LNSP role |
|
4 |
RoleId |
MDP |
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 |
FRMP |
PARTID |
Party |
FRMP Participant ID |
|
9 |
Requestid |
N/A |
N/A |
Change Request ID for Transfer |
|
10 |
N/A |
N/A |
N/A |
[Not Applicable] |
|
11 |
N/A |
N/A |
N/A |
[Not Applicable] |
|
12 |
Field |
N/A |
N/A |
[Not Applicable] |
|
13 |
ProposedDate |
N/A |
N/A |
Proposed Date of Transfer |
|
14 |
Readtypecode |
RTDA |
ReadTypeCode |
Code to denote the method and frequency of Meter Reading |
|
15 |
Value3 |
N/A |
N/A |
[Not Applicable] |
|
16 |
Value4 |
N/A |
N/A |
[Not Applicable] |
|
17 |
Value5 |
N/A |
N/A |
[Not Applicable] |
TWADS example
<CSVData>
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,FRMP,Requestid,N/A,N/A,Field,ProposedDate,Readtypecode,Value3,Value4,Value5
D,TWADS,2024-08-14,PARTID,MDP,CATS,N/A,9999999999,ENGYAVIC,1410691867,,,N/A,09-MAY-24,SP,,,
</CSVData>
SUBSTITUTIONTYPES
|
Query ID |
SUBSTITUTIONTYPES |
|
Purpose |
Results sent to MDPs identifying when obsolete Substitution Type 16 data is sent. This Substitution Type is obsolete from 4 November 2024 |
|
Content |
A list of NMIs where readings have been submitted for an interval meter with Substitution Type 16 A list of change of retailer transactions sitting in MSATS waiting for the MDP to submit the actual change date, where the proposed date has been reached. Please process these transactions |
|
Recipient |
MDP – Metering Data Provider |
|
Delivery |
Participant Outbox (FTP), Participant API endpoint (API) |
|
Run Time |
Weekly report run on a Wednesday @ 6 am |
|
Data source |
MDM |
|
Format |
aseXML compliant XML message with csv payload |
Output
|
Field |
H Record |
D Record |
Standing Data for MSATS – Data Element Name |
Description |
|
1 |
QueryId |
SUBSTITUTIONTYPES |
N/A |
Query Identifier |
|
2 |
Stat_Date |
2024-07-08 |
N/A |
YYYY-MM-DD |
|
3 |
ParticipantId |
MDPID |
Party |
Participant ID |
|
4 |
RoleId |
MDP |
Role |
Participant role ID |
|
5 |
Source |
EMDM |
N/A |
System for data |
|
6 |
Table |
null |
N/A |
MSATS table |
|
7 |
NMI_ID |
9999999999 |
NMI |
Active or inactive NMI |
|
8 |
SFX |
E1 |
Suffix |
The Suffix field in the CATS_DATA_STREAM table. It is used to identify a physical data source that is obtained from the meter |
|
9 |
SDR_Key3 |
N/A |
N/A |
N/A |
|
10 |
SDR_Key4 |
N/A |
N/A |
N/A |
|
11 |
SDR_Key5 |
N/A |
N/A |
N/A |
|
12 |
Field |
N/A |
N/A |
N/A |
|
13 |
SettDate |
2024-07-08 |
N/A |
Settlement date in the format YYYY-MM-DD |
|
14 |
DistinctQualityMethod |
F16 |
|
Distinct Quality Methods submitted during the settlement period using a Substitution Type that is not supported under the Procedures, this applies to any read value including zero |
|
15 |
Value3 |
N/A |
N/A |
N/A |
|
16 |
Value4 |
N/A |
N/A |
N/A |
|
17 |
Value5 |
N/A |
N/A |
N/A |
Example
<?xml version="1.0" encoding="UTF-8"?><ase:aseXML xmlns:ase="urn:aseXML:r43" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:aseXML:r43 http://www.nemmco.com.au/aseXML/schemas/r43/aseXML_r43.xsd"><!--This file is the result of transformation from r44 to r43-->
<Header>
<From description="Australian Energy Market Operator Limited">NEMMCO</From>
<To description="Australian Energy Market Operator Limited ">NEMMCO</To>
<MessageID>NEMMCO-MSG-1281618243</MessageID>
<MessageDate>2024-07-09T12:57:26+10:00</MessageDate>
<TransactionGroup>CATS</TransactionGroup>
<Priority>Medium</Priority>
<SecurityContext>NEMMCOBATCH</SecurityContext>
<Market>NEM</Market>
</Header>
<Transactions>
<Transaction transactionID="CATS-3021175243" transactionDate="2024-07-09T12:57:26+10:00" initiatingTransactionID="238542876">
<ReportResponse version="r39">
<ReportParameters xsi:type="ase:CATSStandingDataQualityReportParameters">
<ReportName>StandingDataQualitySummary</ReportName>
<RunDate>2024-07-09T12:57:26+10:00</RunDate>
</ReportParameters>
<ReportResults xsi:type="ase:CSVReportFormat">
<CSVData>
QueryId,Count,QueryCount
15ERRS,0,0
DSERR,0,0
NONSRD,0,13
NSRD,623126,7344759
NWADS,3,820
SUBSTITUTIONTYPES,10,23
TWADS,2,627</CSVData>
</ReportResults>
<Event severity="Information">
<Code>0</Code>
<Explanation>Success.</Explanation>
</Event>
</ReportResponse>
</Transaction>
<Transaction transactionID="CATS-3021175244" transactionDate="2024-07-09T12:57:26+10:00" initiatingTransactionID="238542876">
<ReportResponse version="r39">
<ReportParameters xsi:type="ase:CATSStandingDataQualityReportParameters">
<ReportName>StandingDataQualityReport</ReportName>
<RunDate>2024-07-09T12:57:26+10:00</RunDate>
</ReportParameters>
<ReportResults xsi:type="ase:CSVReportFormat">
<CSVData>
H,QueryId, Stat_Date, ParticipantId, RoleId, Source, Table, NMI_ID, SFX, SDR_Key3, SDR_Key4, SDR_Key5, Field, SettDate, DistinctQualityMethod,Value3,Value4,Value5
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305002468,E1,,,,N/A,13/05/2024,S16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,09/02/2024,S16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,06/06/2024,E16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,04/06/2024,A16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,02/06/2024,F16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,30/05/2024,S16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,15/06/2024,S16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,24/06/2024,S16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,19/05/2024,E16,,,
D,SUBSTITUTIONTYPES,2024-07-08,NEMMCO,MDP,EMDM,N/A,6305134803,E1,,,,N/A,03/06/2024,E16,,,
H,QueryId,Stat_Date,ParticipantId,RoleId,Source,Table,NMI_ID,FRMP,Requestid,N/A,N/A,Field,ProposedDate,Readtypecode,Value3,Value4,Value5
D,TWADS,2024-07-08,NEMMCO,MDP,CATS,N/A,6305239757,COVAU,1407737391,,,N/A,23-APR-24,SP,,,
D,TWADS,2024-07-08,NEMMCO,MDP,CATS,N/A,6305483865,VICLUMO,1406514479,,,N/A,18-APR-24,SP,,,
</CSVData>
</ReportResults>
<Event severity="Information">
<Code>0</Code>
<Explanation>Success.</Explanation>
</Event>
</ReportResponse>
</Transaction>
</Transactions>
</ase:aseXML>