4 Enhancements
4.1 High-level changes
Function |
Enhancement |
Description |
Impacted |
MSATS functionality |
---|---|---|---|---|
LMRP Site Defects Building or Property Name 2 |
New CATS NMI standing data attributes |
Entitled participant roles
|
NMI Standing Data |
|
|
LMRP Site defects IEC enhancements Shared Fuse Meter Replacement (One In All In) |
Changes to:
|
Initiating Participant roles and receiving roles
|
B2B |
LMRP |
New LegacyMtrReplacementPlan attribute |
LNSP |
B2M |
|
LMRP IEC enhancements Shared Fuse Meter Replacement (One In All In) |
Create new transaction |
Initiating Participant roles and receiving roles
|
B2B |
|
LMRP Site defects ERCF enhancements
|
Updated MSATS C1, C4, C7, Snapshot reports |
LNSP MC FRMP |
B2M |
|
|
LMRP |
New RM29 SDQ queries |
MC |
B2M |
|
LMRP Site defects Embedded Network Settlement Anomalies |
Update CR 5050/5051 to support updates to LMRP value Update to CR 4050/4051 to exclude EN Child NMI datastreams New CR 4060 to update EN Child NMI datastreams |
Entitled Participant roles and initiating Participant roles
|
B2M |
|
LMRP Site defects ROLR reports ERCF enhancements
|
Includes new LMRP and site defect attributes Changes to:
|
Entitled Participant roles and initiating Participant roles
|
B2M |
Site Defects ERCF and IEC enhancements Shared Fuse Meter Replacement (One In All In) |
Changes to:
New B2B Service Order Request subtypes:
|
Initiating Participant roles and receiving roles
|
B2B |
|
LMRP |
New fields |
Initiating Participant roles and receiving roles
|
B2M |
|
LMRP |
Changes to:
New B2B Service Order Request subtypes:
|
Initiating Participant roles and receiving roles
|
B2B |
|
Common B2B and B2M schema |
ICF-078 B004/22 B002/22
|
Address data enhancements for consistency and alignment to AS4590.1:2017 standard Align B2B and B2M field elements |
Entitled Participant roles
|
B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS.
|
LMRP |
New LMRP field
|
|
B2M |
|
Meter testing, inspections, and malfunctions |
New exemption types and configuration data impacting the web interface and API New exemption validation rules |
MC Meter Coordinator; The Role Code used in MSATS for an MC is RP. |
B2M |
4.2 Legacy meter replacement plan
The Legacy Meter Replacement Plan (LMRP Legacy Meter Replacement Plan) describes replacing all existing type 5 (excluding those with remote acquisition) and type 6 meters with type 4 (smart) meters by 30 November 2030 in the National Electricity Market See Relevant Rules or Procedures. To support this requirement, the LNSP in conjunction with applicable FRMP Financially Responsible Market Participant, usually a retailer, Generator, Market Customer or a Market Small Generator Aggregator, identified in respect of a connection point. Responsible for dealings with AEMO in relation to a specific load. and MC is required to record and maintain the LMRP in 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..
4.3 Site defects
A final rule introduces a new requirement for MSATS to specify the information that must be recorded when an MC identifies a defect at the metering installation.
AEMO Australian Energy Market Operator’s MSATS Procedures All of the following procedures: CATS Procedures, WIGS Procedures, MDM Procedures, NMI Standing Data Schedule, NMI Procedure, and Part A of the NEM RoLR Processes. requires the MC to record a Defect Flag, Defect Type, and Defect Issuing MC in MSATS.
4.4 Shared fuse meter replacement
A final rule introduces a Shared Fusing Meter Replacement Procedure which defines a One In All In process for meter upgrades on a shared fuse. When the smart meter installation at an NMI See Relevant Rules or Procedures requires the isolation of more than one customer at that NMI due to a shared network fusing arrangement, DNSPs, FRMPs, and MCs must coordinate efforts. This is required so that any legacy meters on the shared fuse are replaced at the same time.
For details of the One in All in process, see page 14 of the B2B Procedures v3.9 Consultation.
For information about IT changes supporting share fusing meter replacement, see High-level changes.
4.5 Embedded network settlement anomalies
The AEMC Australian Energy Market Commission. The rule maker for Australian electricity and gas markets.’s final rule determination Unlocking CER benefits through flexible trading, in agreement with AEMO that settlement anomalies with child NMIs can occur due to retrospective connections and disconnections.
The changes are:
- Limiting the ability for NMI datastreams in embedded networks to be activated or deactivated retrospectively.
- Continue to allow for retrospectively creating new Child NMIs.
- Continue to allow for retrospectively exchanging meters.
4.6 ICF077 auto populate LCCD field for new NMIs
In accordance with the CATS Procedures MSATS Procedures: CATS Procedure Principles and Obligations, all current financially responsible Market Participants (FRMPs) are obligated to maintain the Last Consumer An end use customer of energy. Change Date (LCCD) field within MSATS. AEMO introduced the LCCD field to better support the Consumer Data Right Rule (CDR Rule) and enables customers to access data which can span multiple retailers for the same NMI.
AEMO proposes to auto-populate the LCCD field to maintain the NMI completion process, where an NMI status is updated from Greenfield “G” to Active “A”. This impacts FRMPs who maintain the LCCD field within MSATS.
4.7 ICF078 address data enhancements
This ICF aligns the address standard in B2M Procedures with the AS4590.1:2017 standard. It supersedes the current NEM addressing which is based on the AS4590-1999 standard.
This change request includes the following changes:
- Increase character lengths in key address fields for capturing detailed address information and avoiding data truncation.
- Update enumerated values for address elements. This enhancement provides more accurate and complete address data and consistent data standards between B2B and B2M.
4.8 IEC - B004/22 - align B2B field lengths to the Australian Standard
A parallel change to ICF078 to update address element definitions to AS4590.1:2017.
4.9 IEC - B002/22 – align B2B and B2M field elements
This change resolves inconsistencies in the field, field lengths and associated enumerations in the B2M and B2B procedures and schemas. This can impact key industry functions. For example, when a customer provides hazard details to the Retailer See Relevant Rules or Procedures, the Retailer forwards this information to the applicable B2B participants.
4.10 ICF-079 NEM12 MDFF inconsistencies
Remove the inconsistency between clauses 4.4 and 4.5 of the Meter Data File Format Specification Metering data delivered to participants is to conform to the Meter Data File Format Specification, see Meter Data File Format on AEMO's website. NEM12 & NEM13 (MDFF Specification The Meter Data File Format Specification for NEM12 & NEM 13.) relating to the provision of 400 block data for actual reads.
4.11 Retailer of last resort reports
The AER See Relevant Rules or Procedures initiates a Retailer of Last Resort (ROLR Retailer of Last Resort. A scheme principally designed to ensure that in the event of retailer failure, arrangements are in place to ensure customers continue to receive electricity and/or gas supply.) event when a FRMP cannot support its financial obligations within the NEM. The ROLR reporting process is updated to improve the request and delivery of reports. The changes include:
- Discontinuing reports that are no longer required.
- Delivering ROLR reports to the Participant File Server The publishing point from AEMO systems to participant systems. Each participant is allocated an account and access to private and public areas. Participants are responsible for interfacing with the participant file server. outbox.
For details, see ROLR Reports.
4.12 Meter testing, inspections, and malfunctions
MCs can apply for a malfunction exemption for metering installations when they cannot repair the metering installation within the timeframes defined in clause 7.8.10(a) of the NER National Electricity Rules. The rules made under the National Electricity Law (NEL). They govern the day-to-day operations of the National Electricity Market (NEM) and provide the framework for network regulation..
The Final Rule removes the requirement for DNSPs to test their existing type 5 and type 6 meters during the acceleration phase of smart meter deployment. Additionally, all existing exemptions are included into the LMRP. Consequently, malfunctions during the acceleration phase only applies for type 1, type 2, type 3 and type 4 metering installations.
NER amendments and Exemption Procedure Exemption Procedure for Metering Installation Malfunctions. Meter Installation Malfunction define the expected timeframe to rectify a metering installation malfunction. AEMO has proposed changes to the Metering Installation Exemption Guideline Exemption Guideline forSmall Customer Metering Installation. in its consultation, streamlining MCs applying for a meter exemption.
The changes include:
- 4 new exemption types - Whole Current The participant can receive files compliant to the current aseXML version. Connected NMI, LV CT Low voltage current transformer Connected NMI, HV High voltage connected NMI, Family Failure and associated nature values.
- Deactivating old exemption type and nature configuration for the malfunction category.
- MSATS Web Portal - The meter exemptions interface new configuration field and checkbox for MCs to populate when raising and exemption.
- Automatic approval or rejection for some Whole Current Connected NMIs and Family Failure exemptions.
- Validation A process to test the veracity and integrity of metering data. to restrict continual exemption for same NMI and exclusion of non-conforming participants from automated processing.