House number to suffix
- Addition of House Number To Suffix to Australian Address.
- Addition of HouseNumberToSuffix as an NMI Standing Data See National Electricitiy Rules item.
- Mappings of aseXML A standard for energy transactions in XML. A set of schemas and usage guidelines that define how data should be exchanged under FRC in the gas and electricity industries in Australia. to CND CATS NMI Data and transforms.
- Updates to the CR2000 and CR5000 series change request logic to include HouseNumberToSuffix.
- The new NMI See Relevant Rules or Procedures Standing Data item, HouseNumberToSuffix, used for NMI Discovery Search 2 The process of entering a NMI and NMI Checksum in MSATS to obtain NMI Standing Data. For more detail, see the NMI Standing Data Access Rules in the CATS Procedures..
- Updates to the MSATS Market Settlement and Transfer Solutions. The procedures published by AEMO under clause 7.2.8 of the National Electricity Rules, which include those governing the recording of financial responsibility for energy flows at a connection point, the transfer of that responsibility between market participants, and the recording of energy flows at a connection point. Browser to support the submission and viewing of HouseNumberToSuffix.
- Ability to view HouseNumberToSuffix using the following services:
- CATS Reports (C1, C4, C7)
- MSATS Snapshot Report
- Updates to the Bulk Data Tool (BDT) to include HouseNumberToSuffix.
- Updates to the Blind Update Tool Allows participants to submit a csv formatted payload containing data for new CATS Standing Data fields requiring a value A limited subset of CATS CR validations is applied to a BUT Submission The History Model is not updated so not suitable for Settlement or Compliance Standing Data (BUT Blind Update Tool) to include HouseNumberToSuffix.
NMI standing data
The following field is defined as a new data item for NMI Standing Data at the NMI level:
Field |
Table |
Data type |
Default value |
Procedure use |
---|---|---|---|---|
HouseNumberToSuffix |
CATS_NMI_DATA |
Varchar2 Max length 1 Pattern: \p{L}\p{N}]{1} a-z or A-Z or 0-9 |
Null |
Optional |
Change request status notification rules
The existing CATS Customer Administration and Transfer Solution. A set of procedures, principles and obligations made under the National Electricity Rules as part of Market Settlement and Transfer Solutions (MSATS), and applicable to NMI (National Metering Identifier) small and large classifications. notification rules apply to HouseNumberToSuffix. You can find a list of the current CATS notification rules by Change Reason Code A code that identifies a type of Change Request. It defines rules such as what NMI information can be updated and which roles will receive a Change Request Notification each time the Change Request Status is updated. in the following locations:
CR |
Change reason code |
Notification rule |
---|---|---|
Create NMI |
2000 |
CATS Procedures Principles and Obligations section 9.1.8. Procedure for Management of WIGS NMIS 4.1.8. |
2001 |
||
2520 |
CATS Procedures Principles and Obligations section 9.4.7. |
|
2521 |
||
2020 |
CATS Procedures Principles and Obligations section 9.2.8. Procedure for Management of WIGS NMIS 4.2.8. |
|
2021 |
||
2500 |
CATS Procedures Principles and Obligations section 9.3.7. Procedure for Management of WIGS NMIS 4.3.7. |
|
2501 |
||
Maintain NMI |
5050 |
CATS Procedures Principles and Obligations section 12.3.7. Procedure for Management of WIGS NMIS 7.2.6. |
5051 |
||
5001 |
CATS Procedures Principles and Obligations section 12.2.10. Procedure for Management of WIGS NMIS 7.1.10. |
|
5021 |
||
5060 |
CATS Procedures Principles and Obligations section 12.5.7. Procedure for Management of WIGS NMIS 7.3.7. |
|
5061 |
||
5100 |
CATS Procedures Principles and Obligations section 15.1.7. Procedure for Management of WIGS NMIS 9.1.7. |
|
5101 |
Standing data access rules
To comply with the Standing Data Access Rules The National Gas or Electricity rules., only participants with a current role for a NMI can query the HouseNumberToSuffix in CATS report requests. The fields are accessible by the following Participant Roles:
Field |
Jurisdiction |
Standing Data Access Rights |
|||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
FRMP |
LR |
LNSP |
MDP |
MPB |
MPC |
RP |
RoLR |
NEMM |
NSP2 |
||
HouseNumberToSuffix |
All |
ü |
ü |
ü |
ü |
ü |
ü |
ü |
û |
ü |
ü |
NMI discovery type 2 – obtain standing data
For a NMI Discovery Search 2, the HouseNumberToSuffix is available. If a NMI does not have a value for the HouseNumberToSuffix, the NMIStandingDataResponse does not contain the NMI Standing Data element.
The HouseNumberToSuffix is accessible using a NMI Discovery Search 2 for the following roles:
Data Item |
Jurisdiction |
Request an NMI Discovery Search 2 |
|||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
FRMP |
LR |
LNSP |
MDP |
MPB |
MPC |
RP |
RoLR |
NEMM |
NSP2 |
||
HouseNumberToSuffix |
ALL |
ü |
û |
ü |
û |
û |
û |
ü |
û |
ü |
û |
Change reason code by role
The following tables describe which roles can use CRs to set and maintain the HouseNumberToSuffix:
Event |
Change Reason Code |
Initiating Role |
Description |
---|---|---|---|
Create NMI |
2000 |
New LNSP |
Create NMI |
2001 |
New LNSP |
||
2520 |
New LNSP |
Create NMI, MDM Datastream & Metering Installation Details – Child NMI |
|
2521 |
New LNSP |
||
2020 |
New LNSP |
Create NMI Details – Child |
|
2021 |
New LNSP |
||
2500 |
New LNSP |
Create NMI, NMI Datastream & metering installation details |
|
2501 |
New LNSP |
||
Maintain NMI |
5050 |
Current LNSP |
Change NMI Details |
5051 |
Current LNSP |
||
5001 |
Current LNSP |
Backdate NMI Start Date |
|
5021 |
Current LNSP |
||
5060 |
Current LNSP |
Change NMI Details – Child |
|
5061 |
Current LNSP |
||
AEMO-Initiated Updates |
5100 |
AEMO |
AEMO-Initiated Standing Data Updates |
5101 |
AEMO |
B2M transactions
Where a NMI currently has a value for HouseNumberToSuffix, participants can submit a NMIStandingDataRequest transaction and receive a NMIStandingDataResponse with the HouseNumberToSuffix element and value, if they have the following:
- They have a role allowing NMI Discovery Search 2 requests.
- A B2M Business-to-Market CATS schema preference set to aseXML r43 or later.
The NMIStandingDataResponse displays the value in the following aseXML r43 element:
Parent Element Name: |
Element Name: |
---|---|
<MasterData> </MasterData> |
<HouseNumberToSuffix> |
B2M transforms
For participants whose B2M aseXML schema Specification to describe the structure of an aseXML message. preference is lower than aseXML r42, MSATS removes the HouseNumberToSuffix element and adds a comment flagging the removal.
There is no transform between r43 and r42.
Bulk data tool
The Bulk Data Tool (BDT) request transaction ase:CATSBulkDataRequest supports the aseXML schema version r43 for the ase:NMIStandingData element:
<NMIStandingData xsi:type="ase:ElectricityStandingData" version="r43">
The BDT ase:CATSBulkDataRequest supports the new NMI data XML eXtensible Mark-up Language. types:
XML type |
XPath to aseXML node |
---|---|
ase:House |
HouseNumberToSuffix |
The value for HouseNumberToSuffix in a CATSBulkDataRequest is validated using the following criteria:
- Regular expression pattern \p{L}\p{N}]{1}
- One character in length
- a-z or A-Z or 0-9
- The Initiating Role The role a company has with a connection point in CATS. A single company can have more than one role associated with a NMI. to establish a new NMI with a HouseNumberToSuffix using a CATSBulkDataRequest must be the New LNSP.
- The Initiating Role to update a NMI with a HouseNumberToSuffix using a CATSBulkDataRequest must be Current LNSP As defined in the MSATS Procedures, CATS Procedures. The LNSP identified on the current NMI master record..
Blind update tool
The Blind Update Tool (BUT) supports participants’ updates to the HouseNumberToSuffix value against an NMI.
MSATS web portal
Change Request – [New/Edit] – NMI Standing Data
CR2000 and CR5000 series
For CR Change Request 2000 and 5000 series, in the Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS. – [New/Edit] – NMI Standing Data interface, there is a new HouseNumberToSuffix text box in the Address section.
NMI Information > obtain standing data – Results
The NMI Information > Obtain Standing Data – Results interface includes the new House Number To Suffix in the Address Information section.
NMI Information> NMI Master > NMI Master – View
For participants with a role against the NMI, the NMI Information> NMI Master > NMI Master – View interface includes a label for HouseNumberToSuffix in the Address Information section.
NMI Information > Point In Time NMI Master Summary
For participants with a role against the NMI, the NMI Information > Point In Time NMI Master Summary interface includes a label for HouseNumberToSuffix in the address information section:
Transactions > Change Request > Change Request – Summary
The Transactions > Change Request The way information is returned from an API. In a request, the client provides a resource URL with the proper authorization to an API server. The API returns a response with the information requested. > Change Request – Summary interface includes a label for HouseNumberToSuffix in the NMI Standing Data section:
Transactions > Notifications > Notifications – List
Transactions > Notifications > Notifications – View
For participants with a role against the NMI, the Transactions > Notifications > Notifications – View interface includes a label for HouseNumberToSuffix:
C1 report
Where a HouseNumberToSuffix value exists, participants can obtain it through a CATS C1 report request, if they have:
- A relationship to the NMI according to the Standing Data Access Rules.
- A B2M CATS schema preference set to aseXML.r43 or later.
The report response value displays in the following aseXML element:
Table name |
Replication block |
Row xsi type: |
Element name |
---|---|---|---|
CATS_NMI_DATA |
ElectricityNMIMaster |
ElecticityNMIMasterRow |
<HouseNumberToSuffix> |
5.7.12 C4 NMI master report
Where a HouseNumberToSuffix value exists, participants can obtain it through a CATS C4 report request, with report name: Master and report type: Detailed, if they have:
- A relationship to the NMI according to the Standing Data Access Rules.
- A B2M CATS schema preference set to aseXML.r43 or later.
The report response value displays in the following aseXML element:
Table name |
Replication block |
Row xsi type: |
Element name |
---|---|---|---|
CATS_NMI_DATA |
ElectricityNMIMaster |
ElecticityNMIMasterRow |
<HouseNumberToSuffix> |
5.7.13 C7 new participant access report
Where a HouseNumberToSuffix value exists, participants can obtain it through a CATS C7 report request, if they have:
- A nomination Energy Rules Terms for a role for the NMI in a CR1000 or CR6000 series Change Request in Requested A status point of a Change Request.(REQ), Pending A status point of a Change Request. (PEND), or Objected A status point of a Change Request. (OBJ) status.
- A relationship to the NMI according to the Standing Data Access Rules.
- A B2M CATS schema preference set to aseXML.r43 or later.
The report response value displays in the following aseXML element:
Parent element |
Element name |
---|---|
<MasterData> </MasterData> |
<HouseNumberToSuffix> |
5.7.14 Snapshot report
Where a HouseNumberToSuffix value exists, participants can obtain it through a Snapshot report request.
The report response value displays in the following aseXML element:
Table name |
Replication block |
Row xsi type: |
Element name |
---|---|---|---|
CATS_NMI_DATA |
ElectricityNMIMaster |
ElecticityNMIMasterRow |
<HouseNumberToSuffix> |
5.7.15 MSATS generic field names
AEMO Australian Energy Market Operator uses the CND_[nn] framework. Where possible, participants should use the Procedural field names defined in the Standing Data for MSATS. AEMO does not support participants using the Oracle database table and field names. For participants using the C1 CATS Transaction See Relevant Rules or Procedures Field Validations report these are the new MSATS field name mappings.
Procedural field |
MSATS field |
Data type |
Table |
Details |
---|---|---|---|---|
HouseNumberToSuffix |
CND_10 |
VARCHAR(500) |
CATS_NMI_DATA |
From this Release, participant submitted values for HouseNumberToSuffix must match the regular expression:
|