B2B Procedures Version 2.0 Final Determination Change Pack & Report

Transcription

1 Infomation Exchange Committee C/ - IEC Secetaiat AEMO Ltd Level Collins Steet Melboune VIC 3000 Tel: (03) Fax: (03) B2B Pocedues Vesion 2.0 Final Change Pack & Repot Pepaed by: Infomation Exchange Committee Vesion No: 1.00 Date:

2 Table of Contents 1. NOTICE OF FINAL DETERMINATION BACKGROUND MATTER UNDER CONSULTATION THE CONSULTATION PROCESS CONSIDERATION OF CONSULTATION SUBMISSION LIST OF SUBMISSIONS RECEIVED MEETINGS AND FORUMS CONSIDERATION OF B2B OBJECTIVE AND B2B PRINCIPLES MSATS IEC RECOMMENDATION - FINAL DETERMINATION PROPOSED CHANGES PROPOSED CHANGES TO THE B2B PROCEDURE CUSTOMER AND SITE DETAILS NOTIFICATION PROCESS PROPOSED CHANGES TO THE B2B PROCEDURE SERVICE ORDER PROCESS PROPOSED CHANGES TO THE B2B PROCEDURE METER DATA PROCESS PROPOSED CHANGES TO THE B2B PROCEDURE ONE WAY NOTIFICATION PROCESS PROPOSED CHANGES TO THE B2B PROCEDURE TECHNICAL GUIDELINE FOR B2B PROCEDURES PROPOSED CHANGES TO THE B2B PROCEDURE TECHNICAL DELIVERY SPECIFICATION ABBREVIATIONS ABBREVIATIONS B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 2 of 80

3 1. Notice of Final This Notice of Final Stage Consultation infoms all NEM Registeed Paticipants, Meteing Povides, Intending Paticipants and inteested paties that the Infomation Exchange Committee (IEC) is conducting the final stage of consultation on Business-to Business (B2B) Pocedues. The consultation is being conducted unde Clause 7.2.A.3(e) of the National Electicity Rules (the Rules) in accodance with the Rules Consultation equiements in clause 8.9 of the Rules. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 3 of 80

4 2. Backgound This document has been pepaed to document poposed amendments to the B2B Pocedues which have been in opeation since 23 Decembe 2004 and have been modified to suppot ongoing business impovements since that time. This document poposes changes to the cuent B2B Pocedues as ecommended by the B2B and MSATS Refeence Goup (BMRG) to the IEC and povides infomation on the impacts of these changes. The infomation povided meets the equiements fo changing the B2B Pocedues as detailed in Sections 7.2A.3 and 8.9 of the National Electicity Rules. The cuent Pocedues ae B2B Pocedues vesion v1.9. The poposed changes have been consideed by the IEC and endosed by the IEC's B2B and MSATS Refeence Goup (BMRG). Vesion 2.0 was eleased fo second stage of consultation on 17 June 2013 and submissions closed on 2 July The changes unde consultation have a poposed effective date of 13 Novembe B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 4 of 80

5 3. Matte unde consultation The matte unde consultation is descibed in the Notice of Consultation B2B Pocedue V2.0, published on AEMO s website at: Consultation The consultation elates to the B2B Poposal to amend the following B2B Pocedues fom Vesion 1.9 to Vesion 2.0; 1. Custome and Site Details Notification Pocess 2. Mete Data Pocess 3. One Way Notification Pocess 4. Sevice Ode Pocess 5. Technical Delivey Specification 6. Technical Guidelines fo B2B Pocedues The second stage of consultation pocess issued the following communication to consulted paties: AEMO Communication No Notice of Consultations Business-to-Business (B2B) Pocedues Vesion 2.0; NEM RoLR Pocesses v1.3; and MSATS Pocedues v3.8. The second stage of consultation closed on 2 July As equested by the IEC, all Paticipant esponses contained comment on the items identified in the consultation, namely; QC776 CSDN Poject This change pack elates to items ageed as the outwoking of QC776 Custome and Site Details Notification (CSDN) Poject as pe diective fom the IEC/RMEC. The CSDN Poject was established to addess a numbe of outstanding industy issues elating to Custome and Site Details Notifications (CSDN) pocesses, as well as identify efficiencies and impove the quality of data used in these pocesses. The enhancements that ae contained in this change pack ae: 1-N2 Ensue paticipants ae obliged to esolve the appopiate ejections This enhancement ensues that Event Codes and exception pocesses ae sufficient fo each tansaction pocess in ode to impove data quality. 1-N7 Modifications to Custome Details Request This enhancement evises the Custome Details Request (CDR) tansaction to assist paticipants in distinguishing between instances whee a esponse fom a Retaile could be automated, fom those equests whee manual follow-up may be equied. 2-N1 Remove Site Addess Notification This enhancement poposes to emove the SiteAddessNotification tansaction fo industy use. The basis of this is that thee appeas to be significant effot and ejections fo the tansaction with limited value fo the DNSP in eceiving this infomation. It is not poposed to emove the tansaction fom the asexml schema. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 5 of 80

6 5-N2 SensitiveLoad Reconciliation Only This enhancement poposes to limit o educe the obligation in the pocedues fo paticipants to pefom a Custome Details Reconciliation to only SensitiveLoad values (sensitive load o life suppot), whilst also intoducing the ability to quey and confim econciliation issues via B2B. Note: The consensus view of the BMRG duing the Daft was to withdaw this solution fom this consultation 1-N6 Complete Postal Addess The key focus of this enhancement is to ensue that Retailes povide a complete postal addess fo each NMI. In addition, the following mino and manifest changes wee identified: 1-N4 Claification of BUSINESSNAME field fomat This change poposes coect a mino eo in the lead in clause 'Defines a peson's legal name" fo the BUSINESSNAME field fomat in the B2B Technical Guidelines. 1-N5 Claify CDN infomation is fo Outage o Supply elated issues This change includes claification that Custome Details Notification (CDN) infomation being supplied to the DNSP should be that fo outage o supply elated issues and not Retail billing / mailing puposes. 3-N1 Remove unused custome details fom pocedue This change emoves the unused Custome Detail infomation (RebateCode, PensionHealthCadNumbe, FomDate and ToDate fields) fo the CustomeDetailsNotification so that they can no longe be used o efeenced. Note that thee will be no change to the asexml schema o B2B Bowse fo this change. 4-G1 Claification of Hazad and Access Details This change includes claity to Hazad and Access details povided in CSDN tansactions as opposed to those povided via a B2B Sevice Ode. Thee is no link between the two Hazad fields and needs to be made clea in the elevant Pocedues. CSDN infomation is pemanent infomation about a NMI and that simila data povided via a Sevice Ode is consideed tansitoy i.e. fo that individual field visit. Hazad/Access infomation on Sevice Ode does not negate the need to maintain pemanent Hazad/Access details via Site Access Notification. 5-G1 Claification of Sensitive Load and Life Suppot at Custome v NMI/Site This change equies a change to the pocedues to ensue that it is clea that the details fo sensitive load apply to the connection point, and life suppot is fo the custome at a connection point not the connection point itself. As diected by the IEC, the BMRG has woked though vaious options and ecommended the following amendments and updates to the B2B Pocedues to facilitate efficient B2B communication and emove identified ambiguities to achieve an impoved outcome fo all paticipants. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 6 of 80

7 QC829 Obligation to Povide Custome Lette fo NSW De-en non Payment This mino and manifest change involves aligning the B2B Pocedues Sevice Ode Pocess with the NSW juisdictional egulations, which was updated with the emoval of clause 13 fom schedule 2 of Electicity Supply (Geneal) Regulation As a esult, the equiement in NSW to povide notice to the custome afte disconnection of supply (de-enegisation) no longe applies. The esponses to the B2B Daft consultation and the eview by the BMRG detemined a numbe of mino amendments to claify the pocedues. Notable changes include: CSDN Pocedue emoval of poposed changes to section in elation to timing of Custome Details Request (enhancement 1-N7), afte the BMRG discussed timing issues between the Custome Details Notification and Custome Details Request whee thee wee diffeing views in elation to the definition of completion of a New Connection as well as the timefame fo allowing a Custome Details Request; and Technical Guideline fo B2B Pocedues amended new event code 1970 to be applicable fo CustomeDetailsNotification and SiteAccessNotification only. All submissions ae detailed in section 7 below and ae published on AEMO s website. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 7 of 80

8 4. The consultation pocess The following table is an outline of the consultation pocess to date. Action Stat Date End Date Notes IEC Initial Meeting ment by the IEC that a pima facie case exist and that consultation should commence. IEC issue notice of consultation fo publication by AEMO 04/04/ /04/2013 9/04/2013 9/04/2013 Complete Complete Paticipant submissions to be povided to AEMO. 10/04/ /05/2013 Mandatoy (min) 25 business days pemitted fo consultation esponses. Complete Submission eceipt date 16/05/ /05/2013 Complete Conside all valid submissions and pepae the Daft epot. This includes the change maked pocedues. IEC Meeting Review Daft Publish Daft consultation (incl. change maked B2B Pocedues) 17/05/ /05/ /06/ /06/ /06/ /06/2013 Within 20 Business days of the submission close date. Complete Paticipant submissions to Daft to be povided to AEMO. 18/06/ /07/2013 Mandatoy 10 business days pemitted fo consultation esponses. Complete Submission eceipt date 02/07/ /07/2013 Complete Conside all valid submissions and pepae the Final epot. This includes the change maked pocedues IEC Meeting Review Final AEMO Publish B2B v2.0 Final 03/07/ /07/ /08/ /08/ /08/ /08/2013 Within 30 Business Days of the submission close date Complete B2B Pocedue v2.0 effective date 13/11/ /11/2013 Poposed implementation date at the time of publication of this document. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 8 of 80

9 5. Consideation of consultation submission 5.1 List of submissions eceived The IEC eceived six submissions epesenting eight Paticipant oganisations in esponse to the notice of the second stage of consultation. The following is a list of espondents: Respondent Paticipant type/ole 1 AGL Retaile 2 Enegex Distibution Netwok Sevice Povide 3 EnegyAustalia Retaile 4 Oigin Enegy Retaile 5 Red Enegy Retaile 6 SA Powe Netwoks, CitiPowe & Poweco Distibution Netwok Sevice Povide Details of submissions eceived ae povided in section 7. Individual submissions eceived can also be viewed on AEMO s website at; Consultation 5.2 Meetings and foums No additional meeting o foums wee equested by industy paticipants. On behalf of the IEC, the BMRG met on the 16 July 2013 to conside the submissions and develop ecommendations to the IEC. 5.3 Consideation of B2B Objective and B2B Pinciples The IEC is equied to conside the B2B Objective and B2B Pinciples in consideing each submission eceived duing the second stage of consultation (clause 7.2A.3(g) of the Rules). The B2B Objective states: The benefits fom B2B Communications to Local Retailes, Maket Customes and Distibution Netwok Sevice Povides as a whole should outweigh the detiments to Local Retailes, Maket Customes and Distibution Netwok Sevice Povides as a whole. The B2B Pinciples ae: B2B Pocedues should povide a unifom appoach to B2B Communications in paticipating juisdictions in which thee ae no fanchise customes; B2B Pocedues should detail opeational and pocedual mattes and technical equiements that esult in efficient, effective and eliable B2B Communications; B2B Pocedues should avoid uneasonable discimination between Local Retailes, Maket Customes and Distibution Netwok Sevice Povides; and B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 9 of 80

10 B2B Pocedues should potect the confidentiality of commecially sensitive infomation. The BMRG consideed all consultation submissions and with egad to the B2B Objectives and Pincipals endosed the changes, unanimously o by consensus, fo ecommendation to the IEC. The IEC maintains that the poposed changes contained in this change pack satisfy the above B2B Objective and B2B Pinciples. 5.4 MSATS AEMO has advised that thee is no assessed impact to the Maket Settlements and Tansfes Solution (MSATS) Pocedues as a esult of this B2B Poposal. Changes have been poposed to the NEM RoLR Pocesses, Pat A - MSATS Pocedue: RoLR Pocedues; Pat B - B2B Pocedue: RoLR Pocess. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 10 of 80

11 6. IEC Recommendation - Final Unde Clause 7.2A.3 of the Rules, the IEC ecommends final detemination, that the B2B Pocedues be amended to include Vesion 2.0 of the following B2B Pocedues: 1. Custome and Site Details Notification Pocess 2. Mete Data Pocess 3. One Way Notification Pocess 4. Sevice Ode Pocess 5. Technical Delivey Specification 6. Technical Guidelines fo B2B Pocedues The consultation documents will be published on the AEMO website following IEC ecommendations, scheduled fo 12 August B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 11 of 80

12 7. Poposed Changes This section lists the changes poposed to the B2B Pocedues: Vesion 2.0. Poposed changes have been categoised as Pocedue changes as follows; Table 7.1 coves the poposed changes to the B2B Pocedue Custome and Site Details Notification Pocess. Table 7.2 coves the poposed changes to the B2B Pocedue Sevice Ode Pocess. Table 7.3 coves the poposed changes to the B2B Mete Data Pocess. Table 7.4 coves the poposed changes to the B2B Pocedue One Way Notification Pocess. Table 7.5 coves the poposed changes to the B2B Pocedue Technical Guideline fo B2B Pocedues. Table 7.6 coves the poposed changes to the B2B Pocedue Technical Delivey Specification. NOTE: All poposed additions to the B2B Pocedues ae highlighted in ed colou text and ae undelined. All poposed deletions fom the B2B Pocedues ae highlighted in ed stike though text. Example: Refeence. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 12 of 80

13 7.1 Poposed changes to the B2B Pocedue Custome and Site Details Notification Pocess N1 Section Application of this Pocedue Changes to Clause1.7 c: c. This Pocedue applies to Custome and Site Details in espect of the NMIs in the following Paticipating Juisdictions: Tansaction ACT NSW QLD SA VIC TAS Custome Yes Yes Yes Yes Yes Yes Details Request Custome Yes Yes Yes Yes Yes Yes Details Notification Custome Yes Yes Yes Yes Yes Yes Details Reconciliation Site Access Yes Yes Yes Yes Yes Yes Notification Site Addess Notification Yes Yes Yes Yes Yes Yes Section 1.5 Scope Changes to Clause1.5 b: 1.5 Scope a. This Pocedue defines the business ules and tansactions fo egula updates of Custome and Site Details fom the Retaile to the DNSP. The Pocedue must be used fo the econciliation of Custome and Site Details between Retailes and DNSPs. b. This Pocedue also povides fo the DNSP to equest custome details fom the Retaile. AGL with changes made fom Initial Consultation to Daft. Coection made to emove site addess notification and changes to clause 1.5B to change wods, this was ageed at the May 2013 BMRG foum. Enegex Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco Please note that if a Site Addess IEC Decision/Final The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 13 of 80

14 Notification is eceived (given the tansaction is still valid unde the cuent schema) we will accept any tansaction but will not eview o use the infomation in any way. IEC Decision/Final N1 Section Business Documents Changes to Clause a: a. Thoughout this Pocedue, the tem "Business Document" is used to efe to the key Tansactions sent between the Retaile and DNSP. In this Pocedue, the elevant Business Documents ae: 1. CustomeDetailsRequest 2. CustomeDetailsNotification 3. CustomeDetailsReconciliation 4. SiteAccessNotification 5. SiteAddessNotification BMRG COMMENTS: BMRG acknowledges the comment fom SA Powe Netwoks, CitiPowe & Poweco and unanimously ageed not to make any futhe changes. AGL d No changes made fom Initial Consultation to Daft. Enegex Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 14 of 80

15 IEC Decision/Final N1 Section Pocess Diagams Changes to Clause 2.1 b: b. The Timing Requiements fo the BusinessReceipt and the BusinessAcceptance/Rejection fo the SiteAccessNotification and SiteAddessNotification ae is identical to those fo the CustomeDetailsNotification. SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item. AGL d No changes made fom Initial Consultation to Daft. Enegex Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 15 of 80

16 IEC Decision/Final N2 Section Common business ules fo Notifications Changes to Clause 2.2.2: a. Subject to bc, Retailes must send the elevant Notification wheneve they become awae of Custome and Site Detail Changes (Changes). b. The Retaile must use easonable endeavous to send the CustomeDetailsNotification in the following situations: 1. At completion of tansfe, o 2. Fo a New Connection whee the custome details and access equiements ae assigned to the new NMI, o 3. When the custome moves out o moves in, o 4. Upon eceipt of outine updates povided by existing custome. h. The details povided in a CustomeDetailsNotification, and SiteAccessNotification and SiteAddessNotification must be the cuent SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item. AGL d Changes made fom initial Consultation to Daft B emoved fom business ules unde Refe to (efe to item 8.1.6) Inseted 5 business days to timing fo ejections Enegex Enegy Austalia Enegy Austalia - Oigin The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 16 of 80

17 details at the date and time that the Notification, was geneated. This date may be histoical in cetain situations. The ecipient should use the date the tansaction was geneated as the effective date fo the change of details and not the last modified date and time. Fo Life Suppot Changes efe to a., b and cb). i. A Retaile must investigate and povide an updated notification take coective action whee necessay within 5 business days upon eceiving a ejection of a notification tansaction. Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco IEC Decision/Final BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item N1 5-N2 Section Custome Details Request Changes to Clause c. The Retaile must povide a CustomeDetailsNotification in esponse to a valid CustomeDetailsRequest. The Retaile must not povide a SiteAccessNotification o SiteAddessNotification in esponse to a valid CustomeDetailsRequest. d. The DNSP must not use this tansaction to obtain mass updates of infomation. If a mass update of infomation is equied, the Reconciliation Pocess must be used. AGL d Changes made fom initial Consultation to Daft Discussed at May BMRG, ageed to e inset comments unde (d) and to Not emove as suggested in initial Consultation. Enegex The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 17 of 80

18 IEC Decision/Final Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item N5, 5-G1 Section Custome Details Notification Changes to Clause 2.2.4: Initiating a Custome Details Notification a. The Retaile must confim the specific contact fo the management of outages and supply issues fo each connection point. The Retaile must povide these details via the CustomeDetailsNotification fo each connection point. b. The Retaile must use easonable endeavous to send the CustomeDetailsNotification in the following situations: AGL d Changes made fom initial Consultation to Daft Replace text which was oiginally unde Common business ules to with the addition of new sub-sections, efomatting and eaanging of clauses): The IEC noted paticipant esponses and endoses the change ecommended by the BMRG. Final : Amended clauses b.2, b.4, c and a and emoved clause c Initiating a Custome Details Notification a. The Retaile must confim B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 18 of 80

19 1. At completion of tansfe, o 2. Fo a New Connection whee the custome details and access equiements ae assigned to the new NMI, o 3. When the custome moves out o moves in, o 4. Upon eceipt of outine updates povided by existing custome. c. If a Custome changes Retaile, the Old Retaile must not send a CustomeDetailsNotification. The New Retaile must send a CustomeDetailsNotification Life Suppot a. Life suppot applies to a custome at a connection point, to indicate the Retaile easonably believes thee ae custome health issues associated with loss of supply to the connection point. b. The Retaile must immediately advise the DNSP by telephone when they become awae of a Life Suppot situation (efe SensitiveLoad field, Section 4.2). The Retaile must subsequently send a CustomeDetailsNotification in accodance with the nomal Timing Requiements set out in Section In this case, the Changes ae effective fom the time of the telephone call fom the Retaile to the DNSP. c. Fo sites in South Austalia with Life Suppot equiements, the Retaile must fax a copy of the documentation veifying the Life Suppot equiements fo the Site to the DNSP. The BusinessAcceptance/Rejection tansaction does not indicate fomal acceptance of the Life Suppot infomation. Fomal acceptance occus once veification of the Life Suppot infomation is eceived as pe egulatoy equiements. In with Life suppot being assigned its own sub heade with emoving wods economic and safety issues fo Life Suppot unde with Insetion fo Sensitive load. with Vacant sites being assigned its own sub heade Vacant Sites AGL takes note that the IEC Committee discussed the tem sensitive load at the June 2013 meeting and noted that claification was needed on the definition. A. Cuickshank (AGL) noted that it was defined unde the Rules but industy also needed a common pocedue on how to handle this. AGL suppots this being futhe discussed at the BMRG. Enegex Whilst clause b has been emoved fom to , the ecommended changes as povided in the Daft discussed at the BMRG in late May have now not IEC Decision/Final the specific contact fo the management of outages and supply issues fo each connection point. The Retaile must povide these details via the CustomeDetailsNotificatio n fo each connection point. b. The Retaile must use easonable endeavous to send the CustomeDetailsNotificatio n in the following situations: 1. At completion of tansfe, o 2. Fo a At completion of a New Connection whee the custome details and access equiements ae assigned to the new NMI, o 3. When the custome moves out o moves in, o 4. Upon eceipt of outine updates povided by the existing custome. c. If a Custome changes Retaile, the Old Retaile must not send a CustomeDetailsNotificatio n. The New Retaile must send a CustomeDetailsNotificatio n. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 19 of 80

20 this case, the Changes ae effective fom the time the DNSP veifies the documentation povided by the Retaile. d. Whee the equiements fo Life Suppot ae no longe appopiate (fo example an occupie no longe meets the juisdictional equiements to be classified as a Life Suppot custome) a Retaile must send a CustomeDetailsNotification containing NMI, LastModifiedDateTime, a MovementType value of Update and SensitiveLoad value of None to the elevant DNSP and the DNSP must update thei ecods accodingly Sensitive Load a. Sensitive load applies to a connection point to indicate that the Retaile easonably believes thee ae economic, health o safety issues associated with loss of supply to the connection point b. The SensitiveLoad code Sensitive Load will not be used by the DNSP fo the pupose of deenegisation. The DNSP may use this infomation fo load o outage management puposes Vacant Sites a. Whee a Site is vacant (fo example, if a custome moves out), a Retaile must send a CustomeDetailsNotification containing NMI, LastModifiedDateTime, a MovementType value of Site Vacant and SensitiveLoad value of None to the elevant DNSP. a. Life suppot applies to a custome at a connection point, and sensitive load applies to a connection point to indicate that the Retaile easonably believes thee ae economic, health o safety issues associated with loss of supply to the connection point. b. The Retaile must immediately advise the been included. Request b. 2. Is ewoded as pe ou oiginal equest to: Fo aon completion of a New Connection whee the custome details and access equiements ae assigned to the new NMI With the emoval of Sensitive Load fom a, don t believe the changes to this clause ae what was intended. We wee endeavouing to claify that Life Suppot applies to a custome at a connection point and Sensitive Load othe than Life Suppot applies to a connection point ie not a peson. I don t believe that the Retaile easonably believes as the custome must povide poof in most juisdictions. Suggest this be amended simply to: a. Life suppot applies to a custome at a connection point whee thee would be health and safety issues associated with loss of supply to the connection point. Enegy Austalia Initial consultation esponse fom SAPN, Citipowe & Poweco indicated that Clause c can be emoved as SA no longe needs papewok exchange since the commencement of NECF on 1 Feb Please confim if this clause will/will IEC Decision/Final Life Suppot a. Life suppot applies to a custome at a connection point, whee a custome elies on life suppot equipment. to indicate the Retaile easonably believes thee ae custome health issues associated with loss of supply to the connection point. b. The Retaile must immediately advise the DNSP by telephone when they become awae of a Life Suppot situation (efe SensitiveLoad field, Section 4.2). The Retaile must subsequently send a CustomeDetailsNotificatio n in accodance with the nomal Timing Requiements set out in Section In this case, the Changes ae effective fom the time of the telephone call fom the Retaile to the DNSP. c. Fo sites in South Austalia with Life Suppot equiements, the Retaile must fax a copy of the documentation veifying the Life Suppot equiements fo the Site to the DNSP. The BusinessAcceptance/Rejec tion tansaction does not B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 20 of 80

21 DNSP by telephone when they become awae of a Life Suppot situation (efe SensitiveLoad field, Section 4.2). The Retaile must subsequently send a CustomeDetailsNotification in accodance with the nomal Timing Requiements set out in Section 3.2.3). In this case, the Changes ae effective fom the time of the telephone call fom the Retaile to the DNSP. c. Fo sites in South Austalia with Life Suppot equiements, the Retaile must fax a copy of the documentation veifying the Life Suppot equiements fo the Site to the DNSP. The BusinessAcceptance/Rejection tansaction does not indicate fomal acceptance of the Life Suppot infomation. Fomal acceptance occus once veification of the Life Suppot infomation is eceived as pe egulatoy equiements. In this case, the Changes ae effective fom the time the DNSP veifies the documentation povided by the Retaile. d. Whee the equiements fo Life Suppot ae no longe appopiate (fo example an occupie no longe meets the juisdictional equiements to be classified as a Life Suppot custome) a Retaile must send a CustomeDetailsNotification containing NMI, LastModifiedDateTime, a MovementType value of Update and SensitiveLoad value of None to the elevant DNSP and the DNSP must update thei ecods accodingly. e. The SensitiveLoad code Sensitive Load will not be used by the DNSP fo the pupose of deenegisation. The DNSP may use this infomation fo load o outage management puposes. f. Whee a Site is vacant (fo example, if a custome moves out), a Retaile must send a CustomeDetailsNotification containing NMI, not be emoved. a. Fo sites in South Austalia with Life Suppot equiements, the Retaile must fax a copy of the documentation veifying the Life Suppot equiements fo the Site to the DNSP. The BusinessAcceptance/Rejecti on tansaction does not indicate fomal acceptance of the Life Suppot infomation. Fomal acceptance occus once veification of the Life Suppot infomation is eceived as pe egulatoy equiements. In this case, the Changes ae effective fom the time the DNSP veifies the documentation povided by the Retaile. Oigin Suggest the following change to (2) Upon eceipt of outine updates povided by the existing custome. Suggest the following change to (3). The New Retaile must send a CustomeDetailsNotification Remove this pat of the clause as thee is aleady an obligation unde (2) 1. To send a notification at the completion of the tansfe. IEC Decision/Final indicate fomal acceptance of the Life Suppot infomation. Fomal acceptance occus once veification of the Life Suppot infomation is eceived as pe egulatoy equiements. In this case, the Changes ae effective fom the time the DNSP veifies the documentation povided by the Retaile. c. Whee the equiements fo Life Suppot ae no longe appopiate (fo example an occupie no longe meets the juisdictional equiements to be classified as a Life Suppot custome) a Retaile must send a CustomeDetailsNotificatio n containing NMI, LastModifiedDateTime, a MovementType value of Update and SensitiveLoad value of None to the elevant DNSP and the DNSP must update thei ecods accodingly Sensitive Load a. Sensitive load applies to a connection point to indicate that the Retaile easonably believes thee ae economic, health o safety issues associated with loss of supply to the connection B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 21 of 80

22 LastModifiedDateTime, a MovementType value of Site Vacant and SensitiveLoad value of None to the elevant DNSP. g. If a Custome changes Retaile, the Old Retaile must not send a CustomeDetailsNotification. The New Retaile must send a CustomeDetailsNotification in accodance with b above. h. The Retaile must confim who the specific contact fo the management of outages and supply issues is fo each connection point. The Retaile must povide these details via the CustomeDetailsNotification fo each connection point N2 Section Custome Details Reconciliation Changes to Clause 2.2.5: with the emaining changes Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco One modification equied as pe comments aised duing 1 st stage consultation: Clause c can be emoved as SA no longe needs papewok exchange since the commencement of NECF on 1 Feb BMRG COMMENTS: The BMRG noted the comment fom AGL egading the sensitive load definition, and unanimously accepted the changes poposed by Oigin and SA Powe Netwoks, CitiPowe & Poweco. Regading Enegex comments, the BMRG unanimously ageed to the woding update egading New Connection, and unanimously ageed to update a to align with the definition of life suppot as pescibed in NECF. AGL d IEC Decision/Final point. b. The SensitiveLoad code Sensitive Load will not be used by the DNSP fo the pupose of de-enegisation. The DNSP may use this infomation fo load o outage management puposes Vacant Sites a. Whee a Site is vacant (fo example, if a custome moves out), a Retaile must send a CustomeDetailsNotificatio n containing NMI, LastModifiedDateTime, a MovementType value of Site Vacant and SensitiveLoad value of None to the elevant DNSP. The IEC noted paticipant esponses and endoses the change ecommended by the B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 22 of 80

23 a. Paticipants must conduct a econciliation of Custome Details on a egula o as equied basis. Fo timing equiements see Clause f. b. The Reconciliation Pocess povides the DNSP with a complete snapshot of all NMI s with SensitiveLoad value othe than None, fo which the Retaile is financially esponsible, as at the time of the Reconciliation (as equied by the CustomeDetailsNotification). c. The Reconciliation Pocess must use the CustomeDetailsNotification tansaction with MovementType equal to Reconciliation. This fom of the CustomeDetailsNotification tansaction is called the CustomeDetailsReconciliation tansaction. d. The use of BusinessAcceptance/Rejections fo the CustomeDetailsReconciliation will be identical to that used fo the CustomeDetailsNotification, with the addition fo the use of CustomeDetailsReconciliationspecific EventCodes. e. The following apply to the delivey of CustomeDetailsReconciliation tansactions: 1. The equied delivey method fo the CustomeDetailsReconciliation tansaction and its Business Signals is the B2B e-hub, and if the B2B e-hub cannot be used the backup delivey method must be a DVD (any DVD Type). 2. The Retaile and DNSP must agee the timing of the Reconcilliation. This ageement shall conside at least the following citeia: i. File limits; ii. Conflicting scheduled econciliations with othe Changes made fom Initial Consultation to Daft. Reconciliation to emain as discussed and ageed at BMRG. Solution to continue to be socialised at BMRG and pioitised fo futue elease. Event codes have been emoved and Refeence to sensitive load has been emoved. Wods have been einseted fo delivey method. (H) and (I) (J) and (K) insets have been emoved Enegex Whee DVD is used, thee is no timing equiements egading the extact of data fom the FRMP s system and the povision of the data to the DNSP. Please conside timing equiements. Enegy Austalia Enegy Austalia - Oigin IEC Decision/Final BMRG. Final : Intoduce new clause e.2 v to addess the timing equiement aised by Enegex: e. The following apply to the delivey of CustomeDetailsReconciliation tansactions: 1. The equied delivey method fo the CustomeDetailsRecon ciliation tansaction and its Business Signals is the B2B e-hub, and if the B2B e-hub cannot be used the backup delivey method must be a DVD (any DVD Type). 2. The Retaile and DNSP must agee the timing of the Reconcilliation. This ageement shall conside at least the following citeia: i. File limits; ii. Conflicting scheduled econciliations with othe paticipants; iii. IT Suppot availability; and iv. Othe impacting activities.; and v. Timing B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 23 of 80

24 iii. iv. paticipants; IT Suppot availability; and Othe impacting activities. 3. If the delivey method is via the B2B e- Hub and the numbe of files exceeds 100, the Retaile must agee the timing of the Reconciliation with AEMO befoe commencing the Reconciliation. 4. Whee AEMO advises the Retaile that the CustomeDetailsReconciliation cannot be undetaken as ageed in clause e 2 the Retaile must contact the DNSP and agee a new date. 5. If tthe CustomeDetailsReconciliation tansaction is sent via the B2B e-hub, the tansaction must be sent as a Low Pioity asexml document. f. The Timing Requiements fo the use of the CustomeDetailsReconciliation tansaction and its Business Signals will be initiated and pocessed duing the months of May and Novembe of each yea o as ageed between the Paticipants using the Tansaction should futhe CustomeDetailsReconciliation be equied. g. A Reconciliation tansaction does not eplace the equiement fo the Notification of Custome Details Changes as descibed in sections and h. Whee a DNSP easonably believes the data they have eceived in a CustomeDetailsReconciliation tansaction is incoect, the DNSP may eject the data and quey the Retaile fo a given NMI by using the appopiate EventCode in the coesponding BusinessAcceptance/Rejection. i. Whee a DNSP easonably believes a NMI not Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: The BMRG ageed that thee is a timing issue as aised by Enegex and unanimously ageed with the poposed woding changes fo e 2 v. The BMRG unanimously ageed that no othe changes wee equied. IEC Decision/Final equiement whee delivey method is DVD. Apply missing undeline fomatting to CustomeDetailsReconciliation in clauses e 4 & 5: 4. Whee AEMO advises the Retaile that the CustomeDetailsReconc iliation cannot be undetaken as ageed in clause e 2 the Retaile must contact the DNSP and agee a new date. 5. If tthe CustomeDetailsReconc iliation tansaction is sent via the B2B e-hub, the tansaction must be sent as a Low Pioity asexml document. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 24 of 80

25 sent in the CustomeDetailsReconciliation tansaction has SensitiveLoad, the DNSP must aise the appopiate CustomeDetailsRequest tansaction to equest the Retaile confim SensitiveLoad. j. Whee a DNSP has ejected the infomation povided in a CustomeDetailsReconciliation tansaction, the Retaile must use easonable endeavous to confim that the infomation is coect. A Retaile must send a subsequent CustomeDetailsReconciliation with an appopiate MovementType code, fo the NMI in question to the DNSP. Fo timing equiements see clause a. k. A DNSP must not eject two consecutive CustomeDetailsReconciliation tansactions fo the same NMI. If the DNSP still believes the SenstitiveLoad value is incoect, the DNSP should contact the Retaile to esolve the issue. IEC Decision/Final N1 Section Site Addess Notification Deletion of Clause 2.2.6: Site Addess Notification a. The DNSP must comply with the following usage ules fo the Business Events listed in the table below when sending BusinessAcceptance/Rejections fo SiteAddessNotifications. Business Event Accept Addess identical to addess held by DNSP Usage The DNSP fully accepts the infomation povided by the Retaile and will update MSATS accodingly. The infomation povided by the Retaile matches the DNSP s ecods. The DNSP will not be updating its ecods based on the infomation povided by the Retaile. AGL d - No changes made fom Initial Consultation to Daft. Enegex Enegy Austalia Enegy Austalia - Oigin The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 25 of 80

26 Addess not accepted. MSATS coect Addess not accepted. MSATS to be updated The DNSP easonably believes the Site addess ecoded by the DNSP and MSATS is coect. The DNSP will not be updating its ecods o MSATS based on the infomation povided by the Retaile. The DNSP does not accept the Site addess povided by the Retaile. The DNSP investigation of the site addess has esulted in changes to its ecods and will esult in a coesponding change to MSATS. Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco IEC Decision/Final N1 Section Timing Requiement fo Poviding Notifications Changes to Clause b: b. In all othe situations, the Notification tansaction (Custome, Addess o Access details) must be povided within one business day of the elevant data being updated/changed (and the completion of the elated custome tansfe o New Connection, if applicable). Refe a and e f a. BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item. AGL d Changes made fom initial Consultation to Daft as ageed at May BMRG meeting. New connections have been inseted, howeve the completion of a new connection and tansfe was debated. It was ageed an ICF Should be aised to esolve the ambiguity, thee is diffeences of opinions. (e.g. CATS 2xxx, Sevice Ode completion, CATS 3xxx) Enegex The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 26 of 80

27 IEC Decision/Final N7 Section Timing Requiement fo Sending CustomeDetailsRequests Changes to Clause 3.2.4: a. The DNSP must not send a CustomeDetailsRequest fo a NMI befoe the Close of Business of the fifth business day following the date of the CATS notification of the completion of fo the Tansfe of the Connection Point. Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item. AGL d Changes made fom Initial Consultation to Daft (B) new insetion has been emoved until the Timing can be esolved via an ICF and CATS Notification has The IEC noted paticipant esponses and endoses the change ecommended by the BMRG. Final : Withdaw changes made to clause 3.2.4a duing Initial Consultation B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 27 of 80

28 b. The DNSP must not send a CustomeDetailsRequest fo a NMI befoe the Close of Business of the fifth business day following the completion of the New Connection of the Connection Point. been Inseted to esolve ambiguity. Enegex Enegy Austalia IEC Decision/Final and Daft. a. The DNSP must not send a CustomeDetailsRequest fo a NMI befoe the Close of Business of the business day following the completion of the Tansfe of the Connection Point. Enegy Austalia - Oigin Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: The BMRG discussed the timing issues of the CDN and CDR with diffeing views as to the definition of completion of a New Connection, as well as the timefame fo allowing CDRs. Consequently the BMRG unanimously ageed to discad all the poposed changes elated to this item, with the view that the cuent business pactices and intepetation B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 28 of 80

29 N1 Section Timing Requiement fo BusinessAcceptance/Rejection fo Notifications Changes to Clause 3.2.6: a. With the exception of SiteAddessNotification, tthe timing equiement fo BusinessAcceptance/Rejections is set out in section 4.10 of the B2B Pocedue Technical Delivey Specification. b. The DNSP must povide a BusinessAcceptance/Rejection to the Retaile within 15 Business Days of eceiving a SiteAddessNotification. of timefames should still apply even though the new CDR Reasons will be added (item A/solution ID 1- N7). AGL d No changes made fom Initial Consultation to Daft. Enegex Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco BMRG COMMENTS: IEC Decision/Final The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 29 of 80

30 IEC Decision/Final N2 Section Timing Requiement fo Sending CustomeDetailsReconciliation Remove addition of Clause 3.2.7: Timing Requiement fo Sending CustomeDetailsReconciliation a. A Retaile must send a new CustomeDetailsReconciliation fo the NMI in question within five business days of eceiving confimation of sensitive load o life suppot in elation to a CustomeDetailsReconciliation tansaction with MovementType equal to Reconciliation. BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item. AGL d Changes made fom Initial Consultation to Daft Remove addition of Clause Enegex Enegy Austalia Enegy Austalia - Oigin Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & Poweco The IEC noted paticipant esponses and publish the Final without change as detailed in the Daft. Final : No futhe changes made to the dafting of B2B Pocedue Custome and Site Details Notification Pocess v2.0. B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 30 of 80

31 Usage: Custome Details Request Poposal fo B2B Pocedues v 2.0 IEC Decision/Final BMRG COMMENTS: BMRG unanimously ageed with the changes as pe the Daft and have no futhe comments on this item A 5-N2, 5-G1, 1-N7 Changes to Clause 4.1 and addition of new clause 3.2.7: Timing Requiement fo Response to Rejected CustomeDetailsNotification a. The Retaile must send though a new CDN with updated/coected infomation, within five business days of eceiving the ejection. Section 4.1- CustomeDetailsRequest Tansaction Data Fiel d NMI NMI Che cksu m Rea Changes to Clause 4.1: Fom at CHAR (10) CHAR (1) VARC HAR(4 M O M Definition/Comments NMI (as used by MSATS). NMI Checksum (as used by MSATS). Allowed values Retuned Mail AGL d Changes made fom Initial Consultation to Daft Changes have been made to emove Reason. Rec - confim no SensitiveLoad Timing of two days has been emoved by DNSP Comments fo Rec confim life suppot emoved It is impotant to note that many DNSP s still conduct econciliation via manual methods (CD), theefoe in these cases a Rejection notification will not be sent by a etaile. Enegex The IEC noted paticipant esponses and endoses the change ecommended by the BMRG. Final : Amended clause a to incopoate feedback fom Enegex Timing Requiement fo Response to Rejected CustomeDetailsNotification a. Whee the Retaile is the cuent FRMP, tthe Retaile must send though a new CDN with updated/coected infomation, within five business days of eceiving the ejection. Amended Notes egading the allowed values elated to the value Othe to incopoate feedback fom SA Powe Netwoks, CitiPowe & Poweco. Othe means othe easons to the specified ones. If this Code is B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 31 of 80

32 son 0) Missing Custome Details Confim Life Suppot No esponse to ejected CDN Tansfe complete, no CDN eceived New Connection, no CDN eceived Data Quality Issue (explanation in SpecialNotes) Rec - confim no SensitiveLoad Othe (explanation in SpecialNotes) Notes egading the allowed values Retuned Mail means the DNSP has eceived etuned mail with the cuent PostalAddess held by the DNSP. Missing Custome Details means the DNSP easonably believes the custome details have changed and the Retaile has not povided a Notification of the Changes (e.g. move-in o tansfe has occued). Confim Life Suppot means the DNSP equies confimation of whethe the Connection Point has a Life Suppot equiement o not. No esponse to ejected CDN means that a DNSP has ejected a pevious CDN whee it was easonably expected the Retaile would send though a new CDN with updated/coected infomation, which has not yet been eceived as pe a. - This change should include whee necessay o something to indicate not equied whee the ejection was based on the sende not being the cuent FRMP Enegy Austalia Enegy Austalia - Oigin Suggest the following changes: New Connection completed, no CDN eceived New Connection completed, no CDN Received means a new connection has completed fo the NMI and the DNSP believes a CDN has not yet been eceived within the allowed timefame. IEC Decision/Final used, the DNSP must povide the details of the eason in the in SpecialNotes field. Othe must only be used fo scenaios not coveed by the specified allowed values. The DNSP must povide the details of the eason in the SpecialNotes field. Mino update to Reason field Definition/Comments to align with 32 schema changes: Allowed values Retuned Mail Missing Custome Details Confim Life Suppot No esponse to ejected CDN Tansfe ccomplete, no CDN Received New Connection, no CDN Received Data Quality Issue (explanation in SpecialNotes) Rec - confim no SensitiveLoad Othe (explanation in SpecialNotes) Tansfe ccomplete, no CDN Received means a tansfe has completed fo the NMI and the DNSP believes a CDN has not yet been eceived within the allowed timefame. Tansfe complete, no CDN eceived means a tansfe has completed fo the NMI and the DNSP believes a CDN has not yet been eceived within the allowed timefame. New Connection, no CDN Received means a new connection has completed fo the NMI and the DNSP believes a CDN has not yet been eceived within the allowed timefame. Data Quality Issue means that to the emaining changes Red Enegy Red Enegy - SA Powe Netwoks, CitiPowe & B2B Pocedues v2 0- Final - Change Pack - v1.00.doc 32 of 80