5MS Metering Focus Group – Notes and Actions Included

5MS Metering Focus Group – Notes and Actions Included
9:00am – 3:00pm Monday 4 March 2019 AEMO Office: Level 10, 10 Eagle Street, BRISBANE Face-to-face only This slide pack was developed for the Joint Metering/Systems Focus Group meeting. This version of the slides has been annotated with notes from the meeting. These additional notes are on new slides that have a yellow background.

Attendees Emily Brodie AEMO Mark Riley AGL Energy Limited Blaine Miner
Name Company / Department Emily Brodie AEMO Mark Riley AGL Energy Limited Blaine Miner Shawn Tan Energy Australia David Ripper Stephanie Lommi Red Lumo Simon Tu Taran Nanda Origin Energy Jim Agelopoulos Victor Sanchez Infigen Robert Speedy Ty Crowhurst IntelliHub Alex Polonetskiy Ausgrid Justin Stute Mondo Alex Skaria Flow Power Jane Hutson Energy QLD Chantal Wright Momentum Energy Mark Leschke Metering Dynamics Dino Ou Endeavour Energy Jackie Mayo Divya Kapoor Jeff Roberts Evoenergy Doug Miles Origin Paul Greenwood Vector Jonathon Briggs Mark Pilkington Citipower/Powercor Justin Betlehem AusNet Services Paul Willacy Aurora Energy Linda Brackenbury PlusES

Agenda NO Time AGENDA ITEM Responsible Preliminary Matters 1
9:00am - 9:15am Welcome, Introduction and General Housekeeping Blaine Miner (AEMO) Matters for Noting and Discussion 2 9:15am - 10:45am Metering Procedure Changes Package 1 David Ripper (AEMO) 10:45am - 11:00am Break 3 11:00am - 11:45am Global Settlements 4 11:45am - 12:15pm Metering Procedure Changes Package 2 12:15pm – 12:45pm Lunch 5 12:45pm – 1:15pm Metering Procedure Changes Package 3 1:15pm - 1:45pm File size and communications capabilities Jim Agelopoulos (AEMO) 1:45pm - 2:00pm 7 2:00pm – 2:30pm Reconciliation Support 8 2:30pm – 3:00pm Additional Time for Agenda Items, Other Business and Next Steps

Metering Procedure Changes Package 1
Blaine Miner

Metering Procedures Update – Package 1 Consultation
First Stage Consultation AEMO received 15 submissions (including two late submissions) from Retailers, LNSPs, Meter Providers, Meter Data Providers and intending participants. AEMO identified three material issues The proposed profiling approach for 15 and 30-minute interval meters Changes to the delivery of meter data to AEMO Industry standard optical port performance and the volume of metering data stored in a metering installation. Jurisdictional amendments to the Metrology Procedures, submitted to AEMO by the COAG Energy Council, were also included in the Draft Procedure changes Second Stage/Draft Consultation AEMO received 11 submissions from Retailers, LNSPs, Meter Providers, Meter Data Providers and intending participants.

Package 1 - Material Issues
Description AEMO Analysis AEMO Conclusion The proposed profiling approach for 15 and 30-minute interval meters AGL questioned how 30- minute small customer generation (e.g. solar) should be profiled to five- minute levels and how this profiling would ultimately impact the net system load profile (NSLP). AGL had undertaken some initial analysis of five-minute and 30-minute solar data and determined that there could be at least a 10% error rate. Its analysis also suggested that the error rate would be greater during the dusk and dawn periods, coinciding with increased consumer usage. Broad support was received for AEMO’s proposed profiling approach for 15 and 30-mintute meter reads. The magnitude of any imbalance that occurs within a 15 or 30-minute period is likely to be small in comparison to the imbalances that occur across a 3-month accumulation reads. No alternative profiling approach was proposed by AGL or other stakeholders. As no preferred alternative has been identified, AEMO will maintain its proposed profiling approach.

Description AEMO Analysis AEMO Conclusion Changes to the delivery of meter data to AEMO AEMO proposed to more closely align the MDP’s meter data delivery processes for AEMO and market participants. Stakeholder feedback supported AEMO’s objective to more closely align the MDP’s meter data delivery processes. Lower level granularity of meter data, being provided to AEMO, is becoming more important in supporting its core functions, Global Settlements, as well as supporting emerging initiatives such as Distributed Energy Resources and Consumer Data Rights. AEMO recognises the potential challenges certain stakeholders may have in fully aligning meter data delivery processes for Basic meter data reads. AEMO believes that the transition to MDFF for Basic meter reads should be implemented progressively over an appropriate period of time. AEMO supports the alignment and uniformity of meter data delivery by MDPs to AEMO and other market participants. Proposed changes: MDFF NEM12 files to be the required file format for all interval meter data being delivered to AEMO from 1 July NEM12 meter data to be delivered to AEMO as per the meter’s configuration i.e. 5, 15 or 30min from 1 July 2021 NEM12 register level and reactive meter data to be delivered to AEMO from 1 July 2021, even where the CATS NMI Data Stream records are at the Net level

Description AEMO Analysis AEMO Conclusion Changes to the delivery of meter data to AEMO AEMO proposed an arrangement that seeks to align the delivery of meter data for market settlement with existing formats used for B2B Stakeholder feedback has been very strong in supporting AEMO’s objective to more closely align the MDP’s meter data delivery processes to AEMO and market participants. Granularity of meter data, being provided to AEMO, is becoming more important in supporting its core functions, as well as supporting emerging initiatives such as Distributed Energy Resources and Consumer Data Rights. AEMO recognises the potential challenges certain stakeholders may have in fully aligning meter data delivery processes for Basic meter data reads. AEMO believes that certain alignments may be best implemented progressively over an appropriate period of time. Proposed changes: Net datastream records to be progressively replaced by Register level data stream records in the CATS NMI Data Stream (CNDS) table MDFF NEM13 files to be supported by AEMO from 1 July 2021 however AEMO will continue to support and accept MDMF files for Basic meter reads Meter data to be delivered consistently by MDPs to both AEMO and market participants

Interim Net Read Construction Solution
Leverages the 4 fields highlighted below to interpret the meter data being received and ‘constructs’ Net meter data where required e.g. CNDS record is Net (N1) and we receive suffix E1, the system will see that the NMI config is E1 and Q1 and will know to create Net meter data values based on the E1 reads received to support current energy allocation processes MDPs can send MDFF to AEMO without having to first update CNDS standing data records Where the CNDS data stream is Net and the required NMI config register level meter data has not been received, a Net meter read estimate is calculated and an exception report is sent to the MDP.

Interim Solution Use Cases
Description Scenario Net CNDS Suffix with E1 and B1 meter reads Use Case - N1 is registered in the CNDS. - MDFF file is sent to AEMO containing CSVIntervalData for IntervalValue1 with the following meter data: - A read with MDMDataStreamIdentifier = N1 and a NMISuffix = B1. - A second read with MDMDataStreamIdentifier = N1 and a NMISuffix = E1. - Two reactive load reads for K1 and Q1. Meter Data Load - The 4 reads in the CSVIntervalData will be loaded as B1, E1, K1, Q1. - A sign shall be applied to the loaded register level reads based on the first character of the NMISuffix. - 'E1' for IntervalValue1 = (+) - 'B1' for IntervalValue1 = (-) 2.000 - Sign change applied due to the first character of the suffix ‘B1’ being an B. - A 5th N1 read shall be created. - N1 shall be constructed from E1 and B1 reads that share the same NMI, IntervalDate and MDMDataStreamIdentifier. - ‘E1’ - ‘B1’ = ‘N1’. - (+) = (+) 8.000 Exception Reporting N/A Settlements - At settlements the CNDS registered data stream ‘N1’ shall be assessed - As ‘N1’ exists for IntervalValue1, ‘N1’ shall be read from the loaded meter data - (+) shall be used as the settlement actual ((+) = (+) 8.000) CNDS Suffix N1

Description Scenario Net CNDS Suffix with no E1 or B1 meter reads Use Case - N1 is registered in the CNDS. - MDFF file is sent to AEMO containing CSVIntervalData for IntervalValue1 with the following reads: - Two reactive load reads for K1 and Q1. - No reads for the MDMDataStreamIdentifier that has been supplied. Meter Data Load - The 2 reads in the CSVIntervalData will be loaded as K1, Q1. - No net read shall be constructed. Exception Reporting - RM11 report generated to highlight missing N1 Settlements - At settlements the CNDS registered data stream ‘N1’ shall be assessed - As ‘N1’ does not exist for IntervalValue1, an estimate for the N1 data stream shall be used for settlements based on the NMI like-day read or ADL CNDS Suffix N1

Description Scenario Net CNDS Suffix with missing B1 meter reads Use Case - N1 is registered in the CNDS - MDFF file is sent to AEMO containing CSVIntervalData for IntervalValue1 with the following reads: A read with MDMDataStreamIdentifier = N1 and a NMISuffix = E1 The NMISuffix B1 defined in NMIConfiguration has not been supplied Two reactive load reads for K1 and Q1 Meter Data Load The 3 reads in the CSVIntervalData will be loaded as E1, K1, Q1 A sign shall be applied to the loaded register level reads based on the first character of the NMISuffix 'E1' for IntervalValue1 = (+) A 4th N1 read shall be loaded N1 shall be constructed from E1 ‘E1’ = ‘N1’. (+) = (+) Exception Reporting - Meter Data Response will highlight missing ‘B1’ based on the NMIConfiguration with reads delivered Settlements - At settlements the CNDS registered data stream N1 shall be assessed - As N1 exists for IntervalValue1, N1 shall be read from the loaded meter data - (+) shall be used as the settlement value - In this use case the N1 may not truly representative of the energy allocations for the NMI CNDS Suffix N1

Description Scenario Register level CNDS Suffix with E1 and B1 meter reads Use Case - E1 and B1 is registered in the CNDS - MDFF file is sent to AEMO containing CSVIntervalData for IntervalValue1 with the following reads: - A read with MDMDataStreamIdentifier = E1 and a NMISuffix = E1 - A read with MDMDataStreamIdentifier = B1 and a NMISuffix = B1 - Two reactive load reads for K1 and Q1 Meter Data Load - The 4 reads in the CSVIntervalData will be loaded as E1, B1, K1, Q1 - A sign shall be applied to the loaded register level reads based on the first character of the NMISuffix - 'E1' for IntervalValue1 = (+) - 'B1' for IntervalValue1 = (-) 2.000 Sign change applied due to the first character of the suffix ‘B1’ being an B As the CNDS Suffix is at the register level, no Net read needs to be constructed Exception Reporting N/A Settlements (+) shall be used as the settlement value ((+) (-) = (+) 8.000) CNDS Suffix E1 and B1

Description Scenario Register level CNDS Suffix with missing B1 meter reads Use Case - E1 and B1 is registered in the CNDS - MDFF file is sent to AEMO containing CSVIntervalData for IntervalValue1 with the following reads: - A read with MDMDataStreamIdentifier = Null and a NMISuffix = E1 - The NMISuffix ‘B1’ defined in the CNDS has not been supplied - Two reactive load reads for K1 and Q1 Meter Data Load - The 3 reads in the CSVIntervalData will be loaded as E1, K1, Q1 - A sign shall be applied to the loaded register level reads based on the first character of the NMISuffix 'E1' for IntervalValue1 = (+) As the CNDS Suffix is at the register level, no Net read needs to be constructed Exception Reporting - RM11 report generated to highlight missing B1 Settlements - (+) shall be used as the E1 settlement value - B1 will be estimated for settlements and stored against the NMI with a (-) sign CNDS Suffix E1 and B1

AEMO Responses to Draft Determination Submissions - Changes to Meter Data Delivery to AEMO

Participant Feedback AEMO Response AusNet Proposal for the use of non-energy register level data from 1 July 2021 has not been justified. Non-energy register level data is only typically used for demand tariff network billing. It is not a billable quantity in the NEM wholesale markets which AEMO operates. Improved power factor will reduce technical losses in the network and consequently contribute to the reduction of UFE. The provision of reactive energy components will allow AEMO to correlate such UFE reductions with improved network utilisation when preparing the UFE reports that are mandated by the NER.

Participant Feedback AEMO Response Citipower/ Powercor Page 12 of the Draft Report and Determination under section Meter Data Frequency states ‘MDPs must put in place processes to ensure meter data version alignment between AEMO and other market participants’. CitiPower Powercor seeks clarification re what is meant by version alignment? Does it mean if an MDFF file is rejected by AEMO & not the retailer (or vice versa)? The intention of this statement is to elicit feedback from MDPs as to how they can best support the alignment of meter data versioning between AEMO and other market participants e.g. MDPs put processes in place to ensure that if meter data is to be sent to one interested party, for example as a response to a PMDR, that all interested parties receive the meter data. Page 12 of the Draft Report and Determination under section Meter Data Granularity states ‘Net data stream records to be progressively replaced by Register level data stream records in the CATS NMI Data Stream (CNDS) table, with the aim of having a sunset period for this transition to occur’ CitiPower Powercor seeks clarification re the above statement whether it is intended to imply both: - New interval meters (from 01/07/2021) will only have E1, B1, Q1, K1 or similar datastreams in the CNDS table, and - Existing interval meters will have their N1, N2,… datastreams in this table replaced by E1, E2 etc. datastreams progressively replaced from 01/07/2021 Correct. All new datastream records are to be created at the register level from 1 July 2021. Existing Net datastream records can remain active post 1 July 2021 until an update to the Datastream record is required e.g. meter replacement. Where an update is required, the Net datastream is to be inactivated and any new datastreams records are to be created at the register level.

Participant Feedback AEMO Response Energy Queensland Supports the gradual transition of Net data stream records to register level data streams but would like to see a more structured time-line applied to this, and an indication of how the MPBs and MDPs would coordinate updates to the CATS NMI Data Stream table so the MDM Contributory Suffix on the Meter Register is kept in-line with Data Stream changes. All new datastream records are to be created at the register level from 1 July 2021. Existing Net datastream records can remain active post 1 July 2021 until an update to the Datastream record is required e.g. meter replacement. Where an update is required, the Net datastream is to be inactivated and any new datastreams records are to be created at the register level. AEMO are not proposing any changes to the current coordination between MDPs and MPBs. Meridian/ Powershop We are supportive of AEMO being able to receive additional metering (register level and non-energy) data provided that it does not impose significant additional obligations on Participants (e.g. should be optional) and it does not result in significant changes to AEMO’s core systems. Consequently we are comfortable with the option of provision of non-energy data and the provision of register level data if AEMO continues to provide participants with NET data (whether provided directly from the MDP or calculated by AEMO from register level data). The reception of register level active (kWh) and reactive (kVarh) meter data has been allowed for within the scope of AEMO’s 5MS system design. AEMO would like to further understand the comment regarding AEMO continuing to ‘…provide participants with NET data (whether provided directly from the MDP or calculated by AEMO from register level data).’.

Participant Feedback AEMO Response Plus ES Disagrees with the proposed need for the MDP to continue to have to manage datastreams for meter data delivered at a register level. PLUS ES takes this position for the following reasons: - a. NMI Suffixes are currently maintained in MSATS by the MPB within the NMI Meter Register table. The population of this information is mandatory. b. Obligations currently exist on the MPB and MDP to manage the accuracy and consistency of register and suffix information within the NMI Meter Register table. Refer MSATS Procedures clauses 2.4 (k), 2.4 (q), 2.5 (a) c. Obligations currently exist on the MDP to align information contained within the MDFF with MSATS (ie Register IDs). This obligation only exists for type 4, 4A and 5 metering installations, but could easily be expanded to all metering types. d. Retailers currently validate metering data supplied in the MDFF against the NMI Meter Register table. This is common practice among most retailers. e. The duplication of suffix and register information in the Datastream table is an unnecessary overhead and will likely lead to confusion and discrepancies The fundamental redesign of MSATS is not within the scope of the 5MS project. Therefore, the 5MS project is not proposing to change the current obligations between MDPs and MPBs, regarding the maintenance of the CATS Register Identifier and Datatsream tables.

Participant Feedback AEMO Response Plus ES Disagrees with placing an obligation on MDPs to provide metering data associated with reactive energy unless the supply of such metering data is required to support the settlement process. Metering data for reactive energy is collected for all WIGS and LARGE customers, and a relatively insignificant number of SMALL customers. In most cases, both import and export reactive energy flows are measured to support the network tariff. In the majority of instances, the energy measured against the import channel (K1) is zero. The inclusion of this metering data, where it is not required to support the settlement process places an unnecessary increase on the volumes of data being sent to MSATS. AEMO’s requirements are changing, in part, as a result of the Global Settlement Rule, New clause B – Reporting by AEMO of unaccounted for energy trends. Improved power factor will reduce technical losses in the network and consequently contribute to the reduction of UFE. The provision of reactive energy components will allow AEMO to correlate such UFE reductions with improved network utilisation when preparing the UFE reports that are mandated by the NER.

Participant Feedback AEMO Response Red/Lumo AEMO did not respond to our questions, we again request clarification on: 1. What validation processes and issues has AEMO considered? 2. How will the rejection process work? Who is notified? 3. Will the notification processes also be amended? If AEMO rejects a file is the FRMP notified MTRD validations shall either be: An extension of existing MDMT validations New validations based on the MDFF specification. The MTRD MACK and TACK shall be returned as 2 separate files where the MACK shall contain aseXML & message validations and the TACK contains MDFF, standing data & Replacement Read validations. As AEMO expects to receive MDFF each time the MDP resends a MTRD transaction, some existing MDMT validations will need to be relaxed to prevent unnecessary market messaging. Where a rejection occurs the sending MDP will receive the MACK & TACK. Upon sending the correcting MTRD transaction the MDP shall send the MDFF file to all Participants (AEMO, FRMP, LNSP, etc.) in a manner similar to the PMD/VMD process. No, the notifications process is not expected to be amended.

Participant Feedback AEMO Response Red/Lumo Clarifications requested regarding the provisioning of energy and non-energy meter data to AEMO: 1. What information pertaining to energy or non-energy is being proposed? And for what purpose would AEMO or other market participants require non-energy information? 2. Participants currently pay through contractual agreements for the provision of non-energy data (see PlusES feedback in Stage 1) will AEMO pay for this or will AEMO share all data with the retailer also? 3. How would additional data be stored? what confidentiality requirements would be placed on it? who would have access? Will AEMO’s legislated indemnity apply to data that isn’t covered under the Rules or Procedures? 4. How will this data be used differently to the current reporting obligation retailers have to AEMO such as Demand Side Participation and being proposed as part of the Distributed Energy Resources Guideline? Could AEMO not meet their UFE obligations from information currently being provided. 5. What additional functions does AEMO see itself performing with the data (energy and non-energy) it receives? Will these functions be completed on a user-pays basis or will the costs of conducting these functions be paid for by all customers? How will AEMO use the additional data if not to perform additional functions? The meter reads to be sent to AEMO would include import and export kWhs (E and B) and import and export kVarhs (Q and K). The provision of active and reactive energy should form part of an MDPs core minimum service. As MDPs are currently paid for these minimum services by FRMPs, AEMO does not believe that any additional cost is justified. The data would be stored in AEMO’s MDM solution. Access and treatment of the data would be on the same basis as today. Improved power factor will reduce technical losses in the network and consequently contribute to the reduction of UFE. The provision of reactive energy components will allow AEMO to correlate such UFE reductions with improved network utilisation when preparing the UFE reports that are mandated by the NER. AEMO is proposing to receive this data to create efficiencies to its current core functions, including settlement query/dispute management, as well as fulfilling its NER obligations associated to UFE Trend reporting.

Participant Feedback AEMO Response Red/Lumo Do not support the reception of register level meter data and firmly believe that this must not be considered for change at this time. AEMO supports the alignment and uniformity of meter data delivery by MDPs to AEMO and other market participants. Uniformity is expected to result in operational efficiencies for MDPs as well as contribute to the reduction of settlement related queries and disputes, which as discussed in the AEMC’s Global Settlement Rule consultation represents a significant cost to the industry. AEMO’s understanding is that the delivery of register level meter data to AEMO is already allowed for in Chapter 7 of the NER. AEMO noted in their draft determination that there was participant support to this initiative however, the multiple concerns and questions from Metering Providers and some retailers that were not addressed. AEMO must not make a new obligation on the provision of metering data without addressing the concerns raised by participants who will ultimately bare the cost of this optional, AEMO led implementation. Are there any other questions or concerns participants believe AEMO have not been addressed?

Description AEMO Analysis AEMO Conclusion Optical port and the volume of meter data storage Landis+Gyr noted that the requirements outlined in Metrology Procedure Part A clause 3.2, section C, were incompatible with the industry standard optical port and the volume of metering data stored in a metering installation. AEMO agrees that the timeframe to download 90 days of interval metering data, currently stated in Metrology Procedure: Part A clause 3.2(c), may not be achievable for 5- minute metering data. AEMO proposes to change the download to 90 seconds or less per Datastream.

Metering Procedure Changes Package 1 - Notes
Topic outcomes and discussions: Profiling approach for 15 and 30min meter data Agreement that AEMO’s profiling approach was suitable for the transition to 5MS and GS. Participants and AEMO noted that as additional 5min meter data became available over time, the profiling approach could be reconsidered e.g. possible inclusion for solar, business and residential profiles. Interim Net Read Construction Solution: AEMO presented five net read construction use cases related to the following scenarios: Net CNDS Suffix with E1 and B1 metering data Net CNDS Suffix with no E1 or B1 metering Data Net CNDS Suffix with missing B1 metering data Register level CNDS Suffix with E1 and B1 metering data Register level CNDS Suffix with missing B1 metering data Changes to meter data delivery: General acceptance of MDP meter data delivery alignment for AEMO and market participants. Question from Endeavour as to whether MDPs have to re-send all applicable register level data (e.g. E and B) even where only 1 register had changed (e.g. E)? AGL – It would make it simpler if MDPs sent all of the registers AEMO will relax the current validation rule that prevents MDP Version Date Time equal to a previously submitted read being summitted. Origin queried the value of CNDS data and suggested that AEMO should instead rely of the CRI table for register level information AEMO responded by saying That Retailer systems do not consistently rely on CRI table information today, some do but others have configured their systems to rely on CNDS data instead, so there is no consistency approach in the market The fundamentals/table construct of MSATS is out of scope of the 5MS program AEMO’s ‘Interim Net Read Construction Solution’ attempted to strike a balance between participant operational impacts and register level settlement transparency AEMO’s approach was supported by AusNet Services Feedback that AEMO needs to clearly communicate that it is not compulsory to provide AEMO with non-energy data i.e. any meter data that is not active or reactive energy (E, B, Q, and K) Discussion regarding the potential obligation of an MDP to re-send meter data to all participants when a Retailer requested a PMD or VMD. Endeavour – MDPs should only send the data to all participants when the meter data has changed since the last delivered version PlusES - send to all when the data changes Question asked regarding if AEMO would expect for Net Datastreams to be replaced by register level Datastreams in the following use cases (1) Re-Energisation \ De-Energisation (2) ADL calculation AEMO position that any new record created in the register table is the trigger to populate the Datastream table with individual Datastreams that are to be used for settlements.

Actions MFG to provide additional use cases for net read construction. AEMO to follow up with Powershop on comment regarding AEMO continuing to ‘…provide participants with NET data (whether provided directly from the MDP or calculated by AEMO from register level data).’. and share AEMO’s response with MFG AEMO to clarify meter data delivery approach in final determination including: Clarifying that reactive energy K and Q Datastreams are not required for energy settlements and consequently not required in the CNDS Table Reactive energy data is required by AEMO to support AEMO’s obligation to analyse and report on UFE in accordance with the Global Settlements Rule. If provided in the Datastream table, MDP must indicate that these are not to be used in settlements Non-energy data is not reactive energy data, non-energy data includes volts ,amps, pf etc. AEMO confirmed that it is not compulsory to send non-energy data to AEMO. AEMO to confirm logic to accept metering data with date/time stamp “equal to or greater than” validation rather than current “greater than” validation in order to avoid rejecting actual metering data that is re-sent.

Global Settlements Blaine Miner

Global settlement implementation timeline
1 December 2019 AEMO procedures updated for both 5MS and GS 1 July 2021 5MS begins AEMO starts publishing UFE data 6 February 2022 GS begins 1 March 2022 AEMO’s first annual report on UFE trends New annual report [NER B] and new reporting guidelines [NER B(d) and ] New procedure required [NER (d) and ]

Maintain and Receive Standing and Meter Data
1 Maintain and Receive Standing and Meter Data 2 Calculate Energy Purchases & Sales Load 3 Calculate UFE Load by Local Area per Trading Interval 4 Apportion and Allocate UFE Load (Based on Loss Adjusted ‘accounted – for’ Energy) 5 Calculate Purchases, Sales and UFE Dollars 6 Publish Statements, Invoices and Reports 7 Receive & Investigate Settlement Queries / Disputes 8 Action Dispute Outcomes 9 Prepare & Publish UFE Trend Analysis / Reporting What’s changed due to GS? Considerations All the meter data MDPs deliver today to AEMO, plus Tier 1 accumulation metering data Non-market unmetered loads now in MSATS, including agreed meter data volumes Non-market Unmetered loads to be processed through MSATS The load profile and size to be agreed upon by the customer, DNSP, retailer and AEMO in accordance with AEMO’s updated metrology procedures and unmetered load guidelines, including: the methodology for calculating a load and load profile for non- market unmetered load; and the provision of the estimated volumes of non-market unmetered load to AEMO for inclusion in settlement AEMO to update their unmetered load guidelines and metrology procedures in accordance with the rules consultation procedures By 1 December 2019, AEMO must review and where necessary amend and publish the following documents: Market Settlement and Transfer Solution Procedures, Metrology Procedures and Service Level Procedures MDPs to provide meter data for ALL connection points to AEMO Creation and activation of 1st tier NMIS in MSATS Creation, cleanse & activation of associated NMI standing data, Datastreams and Registers Delivery of ALL meter data to AEMO No longer delivering 2nd tier meter data to LR Best treatment of non-market unmetered loads e.g. categorisation The creation of NMIs for non-market unmetered loads Creation & activation of associated NMI standing data, Datastreams and Registers Determination of the methodology for calculating a load and load profile for non-market unmetered loads The provision of the estimated volumes of non-market unmetered load to AEMO Updating of unmetered load data tables Delivery of non-market unmetered load meter data to AEMO

Calculate Energy Purchases & Sales Load
1 Maintain and Receive Standing and Meter Data 2 Calculate Energy Purchases & Sales Load 3 Calculate UFE Load by Local Area per Trading Interval 4 Apportion and Allocate UFE Load (Based on Loss Adjusted ‘accounted – for’ Energy) 5 Calculate Purchases, Sales and UFE Dollars 6 Publish Statements, Invoices and Reports 7 Receive & Investigate Settlement Queries / Disputes 8 Action Dispute Outcomes 9 Prepare & Publish UFE Trend Analysis / Reporting What’s changed due to GS? Considerations Bottom up as opposed to a top down approach Not changing Embedded networks will continue to be settled using settlements by difference within the network Treatment of VTN’s is unchanged (primary contributor to UFE being allocated at the Local Area level) VTNs are retained for the purposes of settlement. Changes to meter data aggregation process for Settlements purposes

Calculate and Allocate UFE Load and Dollars
1 Maintain and Receive Standing and Meter Data 2 Calculate Energy Purchases & Sales Load 3 Calculate UFE Load by Local Area per Trading Interval 4 Apportion and Allocate UFE Load (Based on Loss Adjusted ‘accounted – for’ Energy) 5 Calculate Purchases, Sales and UFE Dollars 6 Publish Statements, Invoices and Reports 7 Receive & Investigate Settlement Queries / Disputes 8 Action Dispute Outcomes 9 Prepare & Publish UFE Trend Analysis / Reporting What’s changed due to GS? Considerations UFE = TME - DDME – ADME UFE is the total unaccounted for energy amount (in MWh) to be determined TME is the amount of electrical energy, expressed in MWh, flowing at each of the transmission network connection points in the local area in the trading interval DDME is the amount of electrical energy, expressed in MWh, flowing at each of the distribution network connection points in the local area which are connected to an adjacent local area, in the trading interval ADME is the aggregate of the amounts represented by (ME x DLF) for that trading interval for each connection point assigned to the transmission network connection point or virtual transmission node UFE calculated for each local area to be allocated across all market customers in that local area based on their ‘accounted-for’ energy UFE charges now levied on applicable market customers based on their ‘accounted-for’ energy in a local area Cross boundary/border scenarios Establish NSP2 in MSATS

Publish Statements, Invoices and Reports
1 Maintain and Receive Standing and Meter Data 2 Calculate Energy Purchases & Sales Load 3 Calculate UFE Load by Local Area per Trading Interval 4 Apportion and Allocate UFE Load (Based on Loss Adjusted ‘accounted – for’ Energy) 5 Calculate Purchases, Sales and UFE Dollars 6 Publish Statements, Invoices and Reports 7 Receive & Investigate Settlement Queries / Disputes 8 Action Dispute Outcomes 9 Prepare & Publish UFE Trend Analysis / Reporting What’s changed due to GS? Considerations AEMO must publish information to enable each Market Customer in a local area to verify the unaccounted for energy amounts allocated to that Market Customer’s market connection points in that local area for each trading interval in accordance with a procedure developed and published by AEMO Confidentiality matters New and/or modified reporting

Manage Settlement Queries / Disputes
1 Maintain and Receive Standing and Meter Data 2 Calculate Energy Purchases & Sales Load 3 Calculate UFE Load by Local Area per Trading Interval 4 Apportion and Allocate UFE Load (Based on Loss Adjusted ‘accounted – for’ Energy) 5 Calculate Purchases, Sales and UFE Dollars 6 Publish Statements, Invoices and Reports 7 Receive & Investigate Settlement Queries / Disputes 8 Action Dispute Outcomes 9 Prepare & Publish UFE Trend Analysis / Reporting What’s changed due to GS? Considerations Queries and disputes will be received concerning UFE load How AEMO will work with Market Participants in investigating queries/disputes, where necessary

Prepare & Publish UFE Trend Analysis / Reporting
1 Maintain and Receive Standing and Meter Data 2 Calculate Energy Purchases & Sales Load 3 Calculate UFE Load by Local Area per Trading Interval 4 Apportion and Allocate UFE Load (Based on Loss Adjusted ‘accounted – for’ Energy) 5 Calculate Purchases, Sales and UFE Dollars 6 Publish Statements, Invoices and Reports 7 Receive & Investigate Settlement Queries / Disputes 8 Action Dispute Outcomes 9 Prepare & Publish UFE Trend Analysis / Reporting What’s changed due to GS? Considerations AEMO to report on: Total UFE by Local Area, UFE against benchmarks, Sources of UFE by Local Area, Recommendations to improve visibility of UFE by Local Area and Recommended actions to reduce the amounts of UFE in each local area. Reporting period is at least once per year. First report due by 1 March (NER ) Network Service Providers, Market Participants, Metering Data Providers, Metering Providers, Embedded Network Managers and large customers must provide to AEMO such information and assistance as AEMO reasonably requires to prepare the report AEMO to determine, maintain and publish UFE reporting guidelines that set out AEMO’s approach to preparing and publishing the report required, including how the purpose of the report will be achieved. Guides due 1 December 2022. What processes need to be established for Network Service Providers, Market Participants, Metering Data Providers, Metering Providers, Embedded Network Managers and large customers to provide requested information and assistance to AEMO

Other Considerations What’s changed due to GS?
TNSP metering coordinator obligation Introduces a requirement that only the local transmission network service provider may be appointed as metering coordinator in relation to a transmission connection point that is not a market connection point. As this is a regulatory obligation on the TNSP under the NER, this service would be a prescribed transmission service. Transmission connection point metering TNSP at the connection point should be the metering coordinator and the LNSP be nominated as the metering coordinator for metering installations at points that connect a distribution network with a transmission network.

Other Considerations What’s changed due to GS?
Distribution connection point metering DNSPs associated with a flow between adjacent DNSPs to jointly determine the appointment of the Metering Coordinator. DNSPs to be the metering coordinator for metering installations that measure flows between adjacent DNSP networks. Metering coordinator between two DNSPs A metering coordinator may only be appointed with respect to a connection point that connects adjacent distribution networks by agreement between the two DNSPs related to that connection point

Other Considerations What’s changed due to GS? Non-market generators
Only a generating unit whose entire output is consumed by market load at the same connection point must be classified as a non- market generating unit. A generating unit that wants to sell its output to a market customer must become a registered participant, or operate via an intermediary who is a registered participant. Billing for distribution services Distribution services based on metered energy for first tier customers and non-registered customers must be calculated by a DNSP from settlements ready data obtained from AEMO’s metering database for customers with types 1-3 metering installations, and from either metering data in accordance with the Metrology Procedures or settlements ready data for customers with types 4, 4A, 5, 6 or 7 metering installations. The final rule also removes the ability for a DNSP to bill a local retailer for distribution services used by non-registered customers.

Global Settlements - Notes
Topic outcomes and discussions: Procedure changes: Transition through 01 Jul 2021 through 06 Feb 2022 needs to be clearly articulated in the Procedures AEMO proposes to produce, where appropriate, two versions of a Procedure to reflect 5MS and Global Settlements differing implementation timeframes. Procedures to clarify when MDPs send metering data to LRs and when they don’t. For how long after 06 Feb 2022 should LRs have access to “lost customer” metering data to support settlements revision? Cross Border/Boundary energy: Proposal to define Cross Border energy flow as between adjacent Local Areas in different Jurisdictions. Proposal to define Cross Boundary energy flow as between adjacent Local Areas in the same Jurisdiction. MC appointment: Clarification sought to determine whether LNSP or TNSP will breach ring-fencing requirements when appointing MC in accordance with Global Settlements Rule. Actions AEMO to specifically identify in Procedures when MDPs must send and stop sending metering data to LRs. AEMO to identify where cross border/boundary energy flows exist MFG to identify any other form of cross Border/boundary energy flow.

David Ripper

Matters being considered: 5MS Rule Global Settlement Rule Changes in meter data delivery to AEMO Procedures: MSATS Procedures: Metering Data Management (MDM) Procedures MDM File Format and Load Process National Metering Identifier CATS Procedures Principles and Obligations Procedures for the Management of WIGS NMIS ROLR procedure: Part A Metrology Procedure Part A Metrology Procedure Part B MDFF Specification NEM12 and NEM13 Exemption Procedure - Metering Provider Data Storage Requirements Service Level Procedure: Metering Data Provider Services Service Level Procedure: Metering Provider Services Retail Electricity Market Glossary and Framework

HLIA for Metering Package 2
Procedure Description Item HLIA Metering Data Management (MDM) Procedures The MDM Procedure details the management of metering data within MSATS, including profiles and meter read conversions. 5MS Changes to Profiling methodologies, underlying calculations and processes to support: 15/30min interval meter data, NSLPs and CLPs Changes to RM reports as required e.g. references to instead of 48 trading intervals Global Settlements Remove references as required concerning: Local Retailer, 1st Tier and 2nd Tier Changes to settlements load aggregation process Changes to RM reports including content and delivery Meter Data Delivery to AEMO Review references to ‘settlements ready data’ Review ‘Load Data’ sections to reflect MDFF scenarios

Procedure Description Item HLIA MDM File Format and Load Process Specifies the Meter Data Management (MDM) Format to be used by MDPs for the provision of metering data to AEMO. 5MS Update references to 288 trading intervals or 5-minute data as required. Also details the process for uploading the MDM files and the validations that occur when a file is submitted. Global Settlements No changes identified at this stage Meter Data Delivery to AEMO Removal of MDM delivery for interval meter data Addition of MDFF requirements and examples Removal of net meter data, net datastream and aggregation to 30-minute requirements Review of validation and load requirements

Procedure Description Item HLIA Metrology Procedure Part A The metrology procedure provides information on the application of metering installations to connection points, and sets out 5MS Considered in Package 1 provisions for metering installations and metering data services. Global Settlements Remove references as required concerning: Local Retailer, 1st Tier and 2nd Tier Changes to support the inclusion of non-market unmetered loads Meter Data Delivery to AEMO No changes identified at this stage

Procedure Description Item HLIA Metrology Procedure Part B Procedures for: - Validation, substitution and estimation - Converted of accumulation meter data - Calculation of metering data for unmetered market loads 5MS Covered in Package 1 - Requirements regarding sample meters for controlled loads Global Settlements Review references to First Tier and Second Tier Addition of processes and requirements for non-market unmetered loads Meter Data Delivery to AEMO No changes identified at this stage

Procedure Description Rule HLIA National Metering Identifier Procedure The NMI Procedure - Sets out the structure for NMIs to be used in the NEM 5MS No changes identified at this stage - Describes the Process under which NMIs are allocated - Details data streams for each category of metering installation Global Settlements NMI allocation and requirements for non-market unmetered loads Meter Data Delivery to AEMO Include provisions to support MDFF metering data file delivery to AEMO Review requirements of Net meter data

Procedure Description Rule HLIA Retail Electricity Market Glossary and Framework Contains a dictionary of terms used within the various Procedures and supporting 5MS Covered in Package 1 documentation, and how they fit together. Global Settlements Changes to Glossary (section 5) to ensure ongoing alignment with associated Procedures Inclusion of the process description for non-market unmetered loads Meter Data Delivery to AEMO

Procedure Description Rule HLIA Service Level Procedure: Metering Data Provider Services Details the obligations, technical requirements, measurement processes and performance requirements to be met by MDPs in the 5MS Remove meter churn scenario – type 6 replaced with new type 6 provision of metering data services for all metering installations types and the maintenance of a metering data services database Global Settlements Remove references and requirements, as required, concerning: Local Retailer, 1st Tier and 2nd Tier Include requirements regarding non-market unmetered loads Update required regarding cross boundary/border supply points between distribution networks or Local Retailer regions Review datastream activation requirements for type 6 meters that were tier 1 Meter Data Delivery to AEMO Include provisions to support MDFF metering data delivery to AEMO Review references to ‘settlements ready data’

Procedure Description Rule HLIA Service Level Procedure: Metering Provider Services Details the obligations and processes to be met by MPs who are accredited an registered by AEMO to 5MS No changes identified at this stage provide metering provision services in the NEM. Global Settlements Meter Data Delivery to AEMO

Procedure Description Rule HLIA CATS Procedures Principles and Obligations Specifies the change request process to update MSATS. 5MS No changes identified at this stage Documents how Participants must select the most applicable Transaction Type Code or Change Request Code for their proposed transaction. Global Settlements Remove references as required concerning: Local Retailer, 1st Tier and 2nd Tier Meter Data Delivery to AEMO

Procedure Description Rule HLIA Procedures for the Management of WIGS NMIS Specifies the change request process to update MSATS. 5MS No changes identified at this stage Documents how Participants must select the most applicable Transaction Type Code or Change Request Code for their proposed transaction. Global Settlements Remove references as required concerning: Local Retailer, 1st Tier and 2nd Tier Meter Data Delivery to AEMO

Procedure Description Rule HLIA Exemption Procedure - Metering Provider Data Storage Requirements New document detailing the exemption procedure relating to data storage requirements (originally intended to be included in Metrology Procedure Part A) 5MS New Procedure required Global Settlements No changes identified at this stage Meter Data Delivery to AEMO

Procedure Description Rule HLIA ROLR procedure: Part A 5MS No changes identified at this stage Global Settlements Include ADL in NMI List reports Meter Data Delivery to AEMO

Procedure Description Rule HLIA MDFF Specification NEM12 and NEM13 Specifies the MDFF for interval metering data (NEM12 File) and accumulated metering data (NEM13 File) The MDFF is used by Metering Data Providers for the provision of metering data to Service Providers and Registered Participants 5MS Covered in Package 1 Global Settlements No changes identified at this stage Meter Data Delivery to AEMO Include AEMO as recipient of MDFF

Topic Outcomes Procedure changes: AEMO presented proposed Procedure changes identified in HLIAs related to 5MS Rule Global Settlement Rule Changes in meter data delivery to AEMO ROLR Procedure: Part A changes to be included in Package 2 Add ADL to NMI List reports (ROLR_13 and ROLR_14) to assist ROLR retailers identify prudential exposure when ROLR event occurs. Actions MFG to identify any other Package 2 Procedure changes required to facilitate: AEMO to further explain approach to Procedure versioning for Procedures that encompass 2 or more substantive commencement dates e.g. 5MS and Global settlement. MFG to re-convene by teleconference before the Procedure Package 2 is released

David Ripper

Matters being considered: 5MS Rule Global Settlement Rule Changes in meter data delivery to AEMO Procedures: Standing Data for MSATS Guide to MSATS and B2B terms MSATS -CATS Hints and Tips and NMI Discovery Understanding Load Profiles Published from MSATS Guide to the Role of the Metering Coordinator (MC) Accreditation Checklists - Metering Providers, Metering Data Providers & Embedded Network Managers Guidelines to the National Measurement Act Special Sites and Technology Related Conditions within the National Electricity Market Unmetered Load Guideline - Determination of Device Load and Annual Energy Consumption for Unmetered Device Types

Procedure Description Rule HLIA Standing Data for MSATS Provides a detailed description of the data items populated in the MSATS NMI Standing Data tables and contains information on the type of data, a brief 5MS Changes to CATS_NMI_DATA_STREAM table: Data Stream Suffix, Data Stream Type, Profile Name description of each data item and whether the input of the data is mandatory. Global Settlements Remove references as required concerning: Local Retailer, 1st Tier and 2nd Tier Review Sections 14 and 15 related to data stream status for tier 1 and tier 2 NMIs. Meter Data Delivery to AEMO No changes identified at this stage

Procedure Description Rule HLIA Guide to MSATS and B2B terms This guide assists participants of the Retail National Electricity Market (NEM) to understand the terms used in the retail electricity market procedures and the Market 5MS No changes identified at this stage Settlement and Transfer Solution (MSATS) participant IT system. Global Settlements Meter Data Delivery to AEMO

Procedure Description Rule HLIA MSATS - CATS Hints and Tips and NMI Discovery Hints and tips on different transactions in CATS, including explanations of common errors and rejections, tips on reports and answers to common 5MS No changes identified at this stage questions arising from a failed NMI Discovery Search. Global Settlements Update to advise that Tier 1 NMIs must also have datastream status set to ‘A’ Meter Data Delivery to AEMO

Procedure Description Rule HLIA Understanding Load Profiles Published from MSATS Provides an overview of the load profiles produced by MSATS which AEMO publishes on the website. 5MS Replace 30-minute references with 5-minute Replace 48 intervals with 288 Update sample RM20 to reflect 288 intervals Changes for converting 15/30-minute and basic meter data to 5-minute resolution Global Settlements Review references to first tier and second tier Meter Data Delivery to AEMO No changes identified at this stage

Procedure Description Rule HLIA Guide to the Role of the Metering Coordinator (MC) Provides information on the role and responsibilities of MCs under the NER and procedures authorised under the NER. 5MS No changes identified at this stage Global Settlements Meter Data Delivery to AEMO

Procedure Description Rule HLIA Accreditation Checklists - Metering Providers, Metering Data Providers & The Accreditation Checklists are questions applicants are required to complete as part of the qualification process set out in the Qualification Procedure. 5MS No changes identified at this stage Embedded Network Managers Global Settlements Meter Data Delivery to AEMO Changes to the MDP checklist where the meter data files format requirement are to change for the delivery to MSATS.

Procedure Description Rule HLIA Guidelines to the National Measurement Act The purpose of this Guideline is to provide clarification of the requirements of the National Measurement Act in relation to its application on metering installations. 5MS No changes identified at this stage Global Settlements Meter Data Delivery to AEMO

Procedure Description Rule HLIA Special Sites and Technology Related Conditions within the National Electricity Market Describes situations where special site or technology related conditions exist in the NEM, defines the different categories of these situations and provides a list of these. 5MS No changes identified at this stage Global Settlements Meter Data Delivery to AEMO

Procedure Description Rule HLIA Unmetered Load Guideline - Determination of Device Load and Annual Energy Consumption for Unmetered Device Types Guideline is to provide industry with assistance in determining the device load or annual energy consumption of an unmetered device to support proposals to modify the NEM load table. 5MS Section 10 to be updated to 5-minute data from 30- minute Global Settlements Update document to include references to non-market unmetered loads Meter Data Delivery to AEMO No changes identified at this stage

Topic Outcomes: Procedure/Guideline changes: AEMO presented proposed Procedure/Guideline changes identified in HLIAs related to 5MS Rule Global Settlement Rule Changes in meter data delivery to AEMO Actions No actions recorded

File size and communications capabilities
Jim Agelopoulos

Market Facing Communications
Continued support for legacy interfaces to support transition / contingency FTP Protocol MSATS Browser (contingency and low volume interface) 5MS Systems uplift to: Meet 5MS and GS Rule Change requirements Market Facing message exchange protocols (e.g. RESTful APIs) Data exchange protocols over Internet B2M via API Non-functional requirements due to increase in the volume of data and enriched data (e.g. MDFF data)

B2M Communications - B2M via API
AEMO Proposal Discussion Legacy B2M Web Services shall remain via MarketNet shall be extended for access via the Internet (VPN) B2M Message Submission via FTP via MSATS Browser via Internet (VPN) facing Push API B2M Message Response Participants to elect FTP or API by Transaction Group via Internet (VPN) facing Pull API No further services outside of the legacy B2M Synchronous Web Services shall be developed Message Submission and Response protocols are independent API Message patterns (Internet) API modelled on SMP Asynchronous Push-Push API modelled on SMP Asynchronous Push-Pull Some variation message payloads to reflect the differences between B2M and B2B

B2M Communications - B2M via API
AEMO Proposal Discussion Additional Hub Message Managing APIs Flow Control Notification API Flow Message Acknowledgement Validation Failure Hub Flow Control Report Extension of the SMP HMGT transaction group to B2M Benefits Next Steps By providing a API Market communications platforms accessible through the Internet, Participants can move away from MarketNet for their B2M communications Provide a uniform set of market facing interfaces for Retail B2B and B2M communications Gives equal access to Participants to undertake Retail B2M communications Participants do not have to maintain a legacy protocol AEMO publish Draft Technical Specifications AEMO to publish Draft B2M to eHub Technical Guide (new)

B2M Communications - File Size
Discussion AEMO Functional Testing is complete AEMO systems support messages with large (10MB) CSV payloads Messages with large volumes of transactions are problematic AEMO Load and performance testing Scheduled for 1st and 2nd week of March Results of Industry Functional Testing Participants to discuss progress on their testing Next Steps AEMO to publish Draft Technical Specifications Output of the analysis to ultimately support B2BWG/IEC considerations

File size and communications capabilities - Notes
Topic Outcomes: • Discussion and interest around a statement that AEMO’s long term strategy is to eventually retire the FTP (Hokey Pokey) protocol AusNet Services, PlusES & Powercor requested a timeline communicated ASAP as they have EDPR submissions coming up Discussion around Maximum File size and its link to Transaction maximums AGL suggests removing the file size from the Procedure and introduce a configurable capability to adjust the File Size and the Transaction maximums incrementally "By Notice" (within 10 days for example) AEMO’s recommended analysis approach was to consider both file size and transaction maximums Actions AEMO to come back to participants about when AEMO will announce the proposed retirement date for FTP (Hokey Pokey) Participants to assess the impact of file size and transaction maximums on their systems AEMO to consider removing file size from Procedures and Guides

Reconciliation Support
Blaine Miner

Reconciliation Support
Background Ergon Retail approached AEMO late last regarding a potential ‘Profiled Meter Data Delivery’ proposal Momentum Energy also mentioned in their Metering P1 consultation response that their preference was for AEMO to provide two sets of meter data feeds, from 1 July 2021, one which had been profiled and the other data set as provided by the MDP With this in mind, AEMO has been considering: The current level of reconciliation support it provides to the market today What opportunities may exist to enhance this level of support in a 5MS/GS environment How proposals, such as the ones raised by Ergon and Momentum, should be captured and assessed going forward, including: Value proposition Delivery channel Industry and Program implications Next Steps AEMO is seeking the PWG’s support in AEMO running a workshop which focuses specifically on reconciliation related activities, including: The reconciliation challenges Retailers may encounter in a 5MS/GS environment Opportunities in addressing these potential issues What support Retailers may require from AEMO and other market participants in a 5MS/GS world The new GS UFE publishing and trend analysis requirements For this workshop to be successful, representatives will need to have an in-depth understanding of settlements and billing reconciliation activities

Reconciliation Support - Notes
Topic Outcomes: AEMO presented context regarding a potential Settlements Reconciliation workshop The workshop will only occur if sufficient industry interest is received by AEMO Actions: MFG to give feedback on their interest in a settlements reconciliation workshop and what content would be of most value

Additional Time for Agenda Items and General Business
Blaine Miner

General Business Items - Notes
Topic Outcomes: Metering installation data storage exemption Stakeholders enquired about whether all type 4 meters and type 5 meters were eligible for the storage exemption. Discussion about extending exemption process beyond 01 July 2021 to facilitate 5-minute conversion of metering installations that were installed prior to 01 December 2018 and are not Type 1, 2 and 3 or Type 4 at a transmission network connection point of Type 4 at a distribution connection point where FRMP is a Market Generator or SGA. Non-market unmetered loads Clarification required to determine whether non-market unmetered load NMIs will be contestable Will these remain “franchise” unmetered loads? COAG EC to formally confirm status of “franchise” loads or classify them as market unmetered loads? Metering installation time clock error Stakeholders requested a review of the impact of 20 second time clock error on type 4, 4A and 5 metering installations producing 5-minute metering data Readiness Stakeholders identified that 5MS implementation will need to readiness stage: Comment that a readiness working group needs equal representation from systems and operations Comment that a transition ‘walk through’ of procedures would be useful Actions AEMO to clarify the with the AEMC the policy intent behind the 5MS meter data storage exemption that applies to Type 1-3 meters and the subset of Type 4, but not all Type 4. AEMO to seek clarification from AEMC whether intent of Global Settlements Rule is for non-market unmetered loads to be contestable. AEMO to consider a separate focus group, potentially via teleconference, to concentrate on non-market unmetered loads. Remaining DNSPs to provide AEMO with non-market unmetered load information to support GS implementation MFG to provide information on the scope and materiality of the 20 second time clock error standard in the context of 5MS.

Reconciliation Support - Notes
Topic Outcomes: Readiness Working Group Is AEMO going to produce a Terms of Reference ? Need a balance of operational and systems people represented Need a view on the detail for Transition Again calling for a high level walkthrough of the Transition Potentially a quantum change of data delivery on Day 1 Call for new nominations to MFG Accreditation question MDP and MPs might need to go through 'a level' of accreditation For example If an MP has a process to reconfigure then they may not need to Reliant on MP and MDPS to "look inwardly" at their systems Discussion about 20 sec drift on clock Actions Participants to assess their own position on the MFG

Next Steps Blaine Miner

Next Steps Workshop outcomes and actions to be circulated
Request to consider new nominations Package 2 - Considers impacts from 5MS & GS Rules - April 2019 (Consultation as per NER 8.9) Note Some Procedures will require amendments with different effective dates. In these instances we plan on providing 2 versions of the Initial Draft Procedures with the Issues Paper e.g. version 1.0 of a specific procedure may be change marked to include any 5MS related changes (with an effective date of 1 July 2021) whereas version 2.0 of the procedure may use the ‘clean’ version of version 1.0 to then communicate the GS changes (with an effective date of 6 Feb 2022). Metering Installation Data Storage Exemption Procedure will now be a separate procedure - We originally advised Participants that it would be included in Metrology Procedure: Part A but the Exemption procedure actually has a finite life and ends by 1 July Exemptions can only be granted for Types 1, 2, and 3 and the sub-set of type 4. As these are all to be producing 5-minute metering data by 1 July 2021, no further exemptions will be granted after that date. We therefore can’t include this Exemption Procedure in the Metrology Procedure that becomes effective from 1 July 2021. Package 3 - Considers impacts from 5MS & GS Rules - April 2019 (Publish Only)

Consolidated Action List
Workshop Section Responsible Due Date 1 Metering Procedure Changes P1 MFG to provide additional use cases for net read construction. MFG Fri 29 Mar 2 AEMO to follow up with Powershop on comment regarding AEMO continuing to ‘…provide participants with NET data (whether provided directly from the MDP or calculated by AEMO from register level data).’. and share AEMO’s response with MFG AEMO 3 AEMO to clarify meter data delivery approach in final determination including: Clarifying that reactive energy K and Q data streams are not required for energy settlements and consequently not required in the CNDS Table Reactive energy data is required by AEMO to support AEMO’s obligation to analyse and report on UFE in accordance with the Global Settlements Rule. If provided in the Datastream Table, MDP must indicate that these are not to be used in settlements Non-energy data is not reactive energy data, non-energy data includes volts ,amps, pf etc. AEMO confirmed that it is not compulsory to send non-energy data to AEMO. Fri 22 Mar – Final Determination Published 4 AEMO to confirm logic to accept metering data with date/time stamp “equal to or greater” than validation rather than current “greater than” validation in order to avoid rejecting actual metering data that is re-sent. 5 Global Settlements AEMO to specifically identify in Procedures when MDPs must send and stop sending metering data to LRs. 6 AEMO to identify where cross border/boundary energy flows exist 7 MFG to identify any other form of cross Border/boundary energy flow. 8 Metering Procedure Changes P2 MFG to identify any other Package 2 Procedure changes required to facilitate: 5MS Rule Global Settlement Rule Changes in meter data delivery to AEMO Topic Outcomes: Actions

Consolidated Action List
Workshop Section Responsible Due Date 9 Metering Procedure Changes P2 AEMO to further explain approach to procedure versioning for procedures that encompass 2 or more substantive commencement dates e.g. 5MS and Global settlement. AEMO Fri 29 Mar 10 MFG to re-convene by teleconference before the Procedure Package 2 is released 11 File size and communications capabilities AEMO to come back to participants about when AEMO will announce the proposed retirement date for FTP (Hokey Pokey) 12 Participants to assess the impact of file size and transaction maximums on their systems MFG 13 AEMO to consider removing file size from Procedures and Guides 14 Reconciliation Support MFG to give feedback on their interest in a settlements reconciliation workshop and what content would be of most value 15 General Business AEMO to clarify the with the AEMC the policy intent behind the 5MS meter data storage exemption that applies to type 1-3 meters and the subset of type 4, but not all type 4. 16 AEMO to seek clarification from AEMC whether intent of Global Settlements Rule is for non-market unmetered loads to be contestable. 17 AEMO to consider a separate focus group, potentially via teleconference, to concentrate on non-market unmetered loads. 18 Remaining DNSPs to provide AEMO with non-market unmetered load information to support GS implementation 19 MFG to provide information on the scope and materiality of the 20 second time clock error standard in the context of 5MS. Topic Outcomes: Actions

Thank you for your attendance and participation!

5MS Metering Focus Group – Notes and Actions Included

Similar presentations

Presentation on theme: "5MS Metering Focus Group – Notes and Actions Included"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

5MS Metering Focus Group – Notes and Actions Included

Similar presentations

Presentation on theme: "5MS Metering Focus Group – Notes and Actions Included"— Presentation transcript:

Similar presentations

About project

Feedback