METERING COMPETITION EMBEDDED NETWORKS METER REPLACEMENT PROCESSES PROCEDURE CONSULTATION PARTICIPANT RESPONSE PACK. Participant: Pacific Hydro

Transcription

1 METERING COMPETITION EMBEDDED NETWORKS METER REPLACEMENT PROCESSES PROCEDURE CONSULTATION PARTICIPANT RESPONSE PACK Participant: Pacific Hydro Completion Date: 31 May 2016

2 Table of Contents 1. Glossary and Framework Meter Data File Format Metrology Procedure: Part A Metrology Procedure: Part B MSATS Procedures: CATS Procedure Principles and Obligations MSATS Procedures: MDM Procedures MSATS Procedures: Procedure for the Management of Wholesale, Interconnector, Generator and Sample (WIGS) NMIs NEM RoLR Process Part A and B MSATS Procedure: RoLR Procedures NMI Standing Data Schedule Service Level Procedures for MDP Service Level Procedures for MP Other Issues Related to Consultation Subject Matter...96

3 1. Glossary and Framework Clause Heading Participant Comments - Refer to the comments and embedded document in section 12. Metering Competition Embedded Networks Meter Replacement Processes Procedure Consultation - Participant Response Pack Page 3 of 99

4 2. Meter Data File Format Clause Heading Participant Comments Metering Competition Embedded Networks Meter Replacement Processes 1 INTRODUCTION 1.1 Purpose and Scope (c) This MDFF only has effect only for the purposes set out in the NER. The NER and the National Electricity Law prevail over this MDFF to the extent of any inconsistency. 1.2 Definitions and Interpretation 1.3 Related Documents 2 GENERAL RULES AND INFORMATION 3 TECHNICAL INFORMATION 3.1 Version details Procedure Consultation - Participant Response Pack Page 4 of 99

5 3.2 File delivery 3.3 File construction 4 INTERVAL METER READING FILE SPECIFICATION AND VALIDATION (NEM12) 4.1 Blocking cycle 4.2 Header record (100) 4.3 NMI data details record (200) 4.4 Interval data record (300) 4.5 Interval event record (400) 4.6 B2B details record (500) 4.7 End of data (900) Procedure Consultation - Participant Response Pack Page 5 of 99

6 5 BASIC METER READING FILE SPECIFICATION AND VALIDATION (NEM13) 5.1 Blocking cycle 5.2 Header record (100) 5.3 Basic meter data record (250) 5.4 B2B details record (550) 5.5 End of data (900) APPENDIX A TRANSACTION CODES FLAGS APPENDIX B FORMAT & UNIT OF MEASURE FIELD DETAILS APPENDIX C QUALITY FLAGS Suggest the Column headed Meaning of Quality Flag remain. APPENDIX D METHOD FLAGS Procedure Consultation - Participant Response Pack Page 6 of 99

7 APPENDIX E REASON CODES APPENDIX F OBSOLETE REASON CODES (ONLY TO BE USED WHEN PROVIDING HISTORICAL DATA) APPENDIX G SUMMARY OF FILE FORMAT AND BLOCKING APPENDIX H EXAMPLE INTERVAL DATA FILE (NEM12) H.1 Actual interval - Remote read meter H.2 Substituted interval - Remote read meter H.3 Interval data type 5 Estimate H.4 Multiple NMIs and data streams, remote read meter (all actual data) Procedure Consultation - Participant Response Pack Page 7 of 99

8 H.5 Remote interval data Multiple QualityMethod/ReasonCo de combination H.6 Metering data for meter change with configuration change type 5 H.7 Transfer occurs on the NSRD for type 5 meter H.8 Meter change: type 6 to type 5 APPENDIX I EXAMPLE CONSUMPTION DATA FILE (NEM13) I.1 Actual read values I.2 Normal meter read with Estimate I.3 Meter read and meter Procedure Consultation - Participant Response Pack Page 8 of 99

9 change I.4 Historical Data values I.5 Transfer read APPENDIX J EXAMPLE OF USE OF THE REGISTER READ FIELDS The tables show examples of how the Current and Previous Register Read fields are populated for an basic Accumulation Metered site. The scenario also includes a transfer of the Site to a new retailer on Date 3. Procedure Consultation - Participant Response Pack Page 9 of 99

10 3. Metrology Procedure: Part A Clause Heading Participant Comments Metering Competition Embedded Networks Meter Replacement Processes 1 INTRODUCTION 1.1 Purpose and Scope 1.2 Definitions and Interpretation 1.3 Related Documents 2 DISPUTE RESOLUTION The responsible person MC involved in a dispute of the kind referred to in clause must keep all records in relation to the dispute for a period of seven years from the date of the resolution of the dispute. Is this clause even necessary, given the reference to the dispute resolution process in 8.2 of the NER in this section? 3 RESPONSIBILITY FOR METER PROVISION Suggest the following change: Procedure Consultation - Participant Response Pack Page 10 of 99

11 Change the section heading to Responsibility for Meter Provision MC and MP These are the only two roles referenced in 3.1 Suggest the following changes: Remove this section heading and have the text come directly under the amended section 3 heading suggested above. 3.1 Overall requirements A responsible person MCs must use Metering Provider(s) MPs to provide, install, maintain and routinely test and maintain the relevant components, characteristics and service requirements of the metering installation as specified in the NER Rules and the metrology procedure, as appropriate. Two of the paragraphs reference the metrology procedure and the other this Procedure. Why the difference? 4 METERING INSTALLATION COMPONENTS The Following Changes are suggested: The components, their characteristics, and associated service requirements for metering installations that have not been detailed in the NER have been itemised are detailed in this section. 4.1 Requirement under National Measurement Act and use of Is there a reason for meter type 4A not being included in the paragraphs that reference CTs and VTs? Procedure Consultation - Participant Response Pack Page 11 of 99

12 Standards Remove the reference to New CTs and New VTs; all CTs and VTs for all metering installations must meet the relevant requirements. 4.2 Use of optical ports and pulse outputs Suggest removing the Pulse Output heading as there is not one for Optical Ports. Or create two subsections Pulse Output and Optical Ports. 4.3 Password allocation 4.4 x values calculation and use Should x values also apply to meter type 4A given it is type of manually read interval meter? 4.5 y values calculation and use 4.6 Grandfathering 4.7 Data storage requirements for meters 4.8 Meters and clocks A type 4A, 5 or 6 metering installation clock is to be reset to within + 20 seconds of Eastern Standard Time on each occasion that the metering installation is accessed, in accordance with in the circumstances referred to in sub-clauses paragraphs a) and b), and the maximum drift in the type 4A or 5 metering installation clock permitted between successive Meter Readings is seconds. Procedure Consultation - Participant Response Pack Page 12 of 99

13 4.9 Interval Meters Assume TI stands for trading Interval. The first use of a term should be written in full. TI should also be included in the Glossary. 5 MINIMUM SERVICES SPECIFICATION Completion Timeframes 5.1 Minimum Service Levels The services and completion timeframes for each service are detailed in Table 5.1. They will be measured from the time a request is received by the metering installation to the time of completion of the relevant service by the metering installation Completion Rates 5.2 Completion Rates The completion rates for each service are detailed in Table Upon request from AEMO, the MC must be able to provide evidence demonstrating that small customer metering installations are capable of performing to the completion rates, upon request by AEMO. Suggest moving the table under section 5.2 and renaming the table 5.1 Minimum Service Levels Completion Timeframes and Rates 5.3 Technical Requirements 6 SUMMATION METERING 7 EMBEDDED NETWORKS NSW (b) if the parent has an Accumulation Meter or an Interval Meter that is settled on the basis of accumulated energy data, the child must have a type 6 metering installation or, if the child has an Interval Meter, that meter it must be settled on the basis of accumulated energy data. Procedure Consultation - Participant Response Pack Page 13 of 99

14 Is there an issue here? If the child is transferring to a retailer it is likely the retailer will install a new meter, if all new meters installed must be advanced meters except for the exceptions provided for in the rules, how can settlement be based on accumulated energy data? Why is Australian Capital Territory abbreviated? The other states aren t. There is no mention of the Embedded Network Manager in this section on Embedded Networks. Is it the case the ENM has no responsibilities associated with the metering installations within an embedded Network? 8 REVERSION OF METERING INSTALLATION TYPES NSW (4) The responsible person MC must ensure that the energy consumed and measured by a meter, which is a sample interval meter installed for the purposes of calculating a Controlled Load Profile CLP, is settled in the wholesale electricity market on the basis of a metering installation type 6. There is no mention of 4A type metering installations in the section. I would assume, once an advanced meter was installed as a type 4A, it could only be made type 4 and it could not be replaced by an accumulation meter. 9 ROUTINE TESTING AND INSPECTION OF METERING INSTALLATIONS Unless the MC has an Asset Management Strategy, metering installations must be tested and inspected in accordance with clauses S7.96 and S7.69 of the NER. This section 93.6 specifies AEMO s requirements in respect of a proposed asset management strategy that an MC will need to take into consideration consider when seeking approval of an Asset Management Strategy. Where the responsible person is not the Local Network Service Provider, the responsible person. Once AEMO approves the Asset Management Strategy, Tthe MC must provide reasonable access to a copy of the Asset Management Strategy and test plan for to the each relevant MP Metering Provider Local Network Service Provider. Procedure Consultation - Participant Response Pack Page 14 of 99

15 Should the Asset Management Strategy also be provided to the FRMP who is responsible for appointing the MC? 10 INSTALLATION OF METER(S) 10.1 Installation by ASPs Will meter provision in NSW still be undertaken under the ASP scheme as a result of the PoC? If not, is this section still required? 11 METER CHURN 11.1 Who can Initiate a Meter Churn Who can Initiate a Meter Churn The MC for a metering installation can initiate a Meter Churn at any time. Is this accurate? Would it be better to provide the circumstances under which a meter churn can occur? E.g. faulty meter, end user transfer. Suggest removing at any time Who can Perform the Meter Churn 11.3 How is a Meter Churn to be Performed There are requirements in this clause to inform the MP and update the MP role in MSATS. The MP is not a recognised role in MSATS; it is either the MPB or MPC. It is suggested the clause reference the role(s) responsible. 12 DE-COMMISSIONING AND REMOVAL OF METERING (b) The ownership of the components of the existing meter is ascertained and arrangements made for these meter component parts to be returned to its their owner(s) within 10 business days Procedure Consultation - Participant Response Pack Page 15 of 99

16 EQUIPMENT AND NETWORK DEVICES unless otherwise agreed with the owner(s) of the components of the metering installation LNSP. There may be various components to the metering installation which may not be owned by a single party. Shouldn t the agreement be with the owner(s) of the metering installation components as the LNSP will not always be the owner of the meter? (b) (i) and (ii); these clauses could be combined as follows: Where the network device provides a control or switching service which facilitates the application of a Network tariff and that service is obsolete as a result of the Meter Churn LNSP Obligations if Alterations to Metering Installations Required 12.1 Network Devices Where an LNSP considers that an alteration is required to a metering installation to install accommodate, remove, or replace a network device installed at or near the metering installation, including the removal of any seal, the LNSP must: This clause states If an MC removes a network device The MP will physically remove the device but the MC will have the ultimate responsibility for the action taken. This is an ongoing issue within the document where one party is responsible for the actions carried out by another party. How should these clauses be worded? E.g. in this case The MC must ensure that where the removal of a network device is done in accordance with Request for testing type 1 6 metering installations 13 RESPONSIBILITY FOR METERING DATA SERVICES Procedure Consultation - Participant Response Pack Page 16 of 99

17 13.1 Metering data services 13.2 Metering data collection 13.3 Metering data storage The responsible person MC must ensure that metering data from the following is transferred to AEMO: Interval Metered interval metering data for first-tier loads, including Interval Metered First-Tier Controlled Loads, where required by the metrology procedure in those participating Jurisdictions where that interval metering data is to be provided for load profiling the purpose of Load Profiles; calculated metering data for first-tier loads, and accumulated metering data for First-Tier Controlled Loads in New South Wales and Queensland Access to energy data and metering data The following rewording is suggested: In New South Wales and Queensland the MC must ensure the following metering data is transferred to AEMO: Interval metering data for first tier loads which includes: (a) First Tier Controlled Loads; (b) Calculated metering data for first tier loads; Procedure Consultation - Participant Response Pack Page 17 of 99

18 (c) Accumulated metering data for first tier Controlled Loads Verification of metering data for type 4A, 5, 6 and 7 metering installations 13.6 Metering installation type 7 sample testing 13.7 Request for test of calculated metering data 13.8 AEMO s Metering Data Obligations 14 EMERGENCY PRIORITY PROCEDURES 14.1 Criteria for determining Emergency Condition 14.2 Metering Installations Affected 14.3 Prioritisation of Services by Metering Coordinator in Procedure Consultation - Participant Response Pack Page 18 of 99

19 Emergency Condition 14.4 Other Laws Prevail Procedure Consultation - Participant Response Pack Page 19 of 99

20 4. Metrology Procedure: Part B Clause Heading Participant Comments Metering Competition Embedded Networks Meter Replacement Processes 1 INTRODUCTION 1.1. Purpose and Scope 1.2. Definitions and Interpretation 1.3. Related Documents 2 PRINCIPLES FOR VALIDATION, SUBSTITUTION AND ESTIMATION 2.1. General Validation, Substitution and Estimation Requirements 2.2. Substitution requirement Procedure Consultation - Participant Response Pack Page 20 of 99

21 2.3. Estimation requirement 2.4. Metering data quality flags 2.5. Summary table of Substitution and Estimation Types 3 SUBSTITUTION FOR METERING INSTALLATION WITH REMOTE ACQUISITION OF METERING DATA 3.1. Application of section Substitution Rules Type 52 - Previous Meter Reading Method (with the Nearest Equivalent Day or Like Day method) Type 57 - Prior to First Reading - Customer Class Method Prior to the first Actual Meter Reading and where no previous metering data history exists for the connection point, the Metering Data Provider MDP may provide a Substitution or forward Estimation for the metering data based on the given ADL average daily load. The interval metering data must be profiled to suit the relevant End User customer class. Metering Data Provider MDPs electing to undertake this type of Substitution or forward Estimation must develop a suite of profiles acceptable to the responsible person MC for use and application Substitution Types Comments: Customer Class is referenced in the heading; however, it has been changed to End Procedure Consultation - Participant Response Pack Page 21 of 99

22 User class in the body of the description. Customer Class is not a defined term. NMI classification (small, Large, wholesale etc.) and Customer Classification (business. Residential) exist in the market; so what exactly is End User class and if determined it is a valid term, suggest it be defined and entered into the Glossary. Also as the FRMP is responsible for appointing the MC, it is suggested the suite of profiles developed by the MDP must also be acceptable to the FRMP. 4 SUBSTITUTION AND ESTIMATION FOR MANUALLY READ INTERVAL METERING INSTALLATIONS 4.1. Application of section Substitution and Estimation Rules 4.3. Substitution and Estimation Types 5 SUBSTITUTION AND ESTIMATION FOR METERING INSTALLATIONS WITH ACCUMULATED METERING DATA 5.1. Application of section 5 Procedure Consultation - Participant Response Pack Page 22 of 99

23 5.2. Substitution and Estimation Rules Type 64 - Agreed Method 5.3. Substitution and Estimation Types The Metering Data Provider MDP may undertake to use another method of metering data Substitution (which may be a modification of an existing Substitution type), where none of the existing Substitution types is are applicable, subject to making reasonable endeavours to form an an agreement between with the FRMP financially responsible Market Participant, the LR Local Retailer and the LNSP Local Network Service Provider for the connection point. The specifics of this Substitution type may involve a globally applied method. Why has reasonable endeavours been introduced into this clause? Suggest it be removed. 6 SUBSTITUTION AND ESTIMATION FOR CALCULATED METERING DATA (b) Where the Inventory Table has been updated is correct for the period concerned, the calculated metering data must be flagged as A (Actual) metering data provided as an actual value, however, when the Inventory Table is subsequently updated for the period concerned, the calculated metering data must be flagged as S metering data provided as a Substituted value; and 6.1. Substitution Rules The Metering Data Provider MDP must notify the LNSP Local Network Service Provider, LR Local Retailer and the financially responsible Market Participant FRMP for the connection point of any Substituted calculated metering data substitution by the Metering Data Provider MDP within two business days of the calculated metering data the Substitution being carried out by the Metering Data Provider MDP. Notification is achieved via the participant metering data file as detailed Procedure Consultation - Participant Response Pack Page 23 of 99

24 within the sevice service level procedures. Type 74 - Agreed Method The Metering Data Provider MDP may use another method of calculated metering data Substitution (which may be a modification of an existing Substitution type), where none of the existing Substitution types is applicable, subject to making reasonable endeavours to form an an agreement between the FRMP financially responsible Market Participant, the Local Retailer LR and the Local Network Service Provider LNSP for the connection point. The specifics of this Substitution type may involve a globally applied method Substitution and Estimation Types Why has reasonable endeavours been introduced into this clause? Suggest it be removed. 7 GENERAL DATA VALIDATION REQUIREMENTS 7.1. Validation requirements for all metering installations Metering Data Providers must assume and manage systems and processes on the basis that: Not sure what the relevance is of assume being added to this clause. Suggest it be removed Validation of interval metering data alarms 8 VALIDATION WITHIN THE METER READING PROCESS 8.1. Validations to be performed during collection of metering Procedure Consultation - Participant Response Pack Page 24 of 99

25 data from manually read interval metering installations 8.2. Validations to be performed during collection of accumulated metering data 9 VALIDATION AS PART THE REGISTRATION PROCESS 9.1. Validation metering installations with remote acquisition of metering data The following rewording is suggested: Following the installation or change to a metering installation with remote acquisition of metering data, MDPs must carry out the Validations listed below prior to the distribution of any interval metering data to AEMO or Registered Participants for the purposes of settlements: (a) In conjunction with the MP, ensure the metering installation is recording metering data correctly. (b) In conjunction with the MP, ensure all Data Streams are captured. (c) That the NMI is registered in MSATS. (d) The NMI is correct and is within the range allocated for the relevant NSP. (e) The metering data acquired is of an expected magnitude and profile for the End User type. What is meant by the End User Type? Do we mean End User Class as previously referenced in this 3.3? Suggest there is a consistency of terms and that it is captured in the Glossary, For whole current metering installaitons installation installed under 9.9A, 9.9B and 9.9C of the NER, MDPs must carry out the following Validation prior to the distribution of any interval metering data to AEMO or Registered Participants for the purposes of settlements: Procedure Consultation - Participant Response Pack Page 25 of 99

26 (a) That tthe metering data correctly pertains to the registered metering installation. (b) That tthe metering data acquired is of an expected magnitude and profile for the End User type. (c) That Aall Datastreams are captured. (d) That the NMI is registered in MSATS. (e) That Tthe NMI is within the range allocated for the relevant LNSP. Following any changes to a manually read interval metering installation Tthe MDP must carry out the following Validations on the CT for type 4A and 5 manually read interval metering installations after any changes to a metering installation prior to the distribution of any interval metering data to AEMO or Registered Participants for the purposes of settlements: The Metering Data ProviderMDP must Validate the metering data on registration of all current transformer type 4A and 5 metering installations to verify: (a) That tthe metering data correctly pertains to the registered metering installation, in conjunction with the Metering Provider MP. (b) That tthe magnitude and profile of the metering data is correct for the primary energy, in conjunction with the Metering Provider MP. (c) That aall Data streams are captured, in conjunction with the Metering Provider MP. (d) That tthe NMI is registered in MSATS. (e) That tthe NMI is within the range allocated for that the relevant LNSP Local Network Service Provider Validation for manually read interval metering installations MDPs must carry out the following Validation of all whole current type 4A and 5 manually read interval metering installations prior to the distribution of any interval metering data to AEMO or Registered Participants for the purposes of settlements The Metering Data ProviderMDP must Validate the metering data on registration of all whole current type 4A and 5 metering installations to verify: (a) That the metering data correctly pertains to the registered metering installation: Procedure Consultation - Participant Response Pack Page 26 of 99

27 (b) That the metering data acquired is of an expected magnitude and profile for the End User Customer type. (c) That all Data streams are captured. (d) That the NMI is registered in MSATS. (e) That the NMI is within the range allocated for that Local Network Service Provider the relevant LNSP. Remove That from the beginning of (a) to (e). Again there is an issue with the reference to end User type. Following any changes to a type 6 metering installation, MDPs must carry out the following Validation listed below prior to the distribution of any accumulated metering data or interval metering data to AEMO or Registered Participants for the purposes of settlements: The Metering Data ProviderMDP must Validate the metering data on registration of all type 6 metering installations to verify: (a) That the metering data correctly pertains to the registered metering installation. (b) That all Data streams are captured. (c) That the NMI is registered in MSATS. (d) That the NMI is within the range allocated for that Local Network Service Provider. the relevant LNSP. Remove That from the beginning of (a) to (d) Validation for metering installations with accumulated metering data 9.4. Validation for metering installations with calculated Procedure Consultation - Participant Response Pack Page 27 of 99

28 metering data 10 VALIDATION OF METERING DATA General Validations to be performed for all metering installations Validations to be performed for metering installations with check metering or partial check metering In 10.3 Undertake has been struck out and replaced with carry out. Yet in the rest of the clauses undertake remains. Is there a reason for this? Suggest the use of undertake for consistency Validations to be performed for manually read interval metering installations with CTs Validations to be performed for whole current manually read interval metering installations Validations to be performed for metering installations with accumulated metering Procedure Consultation - Participant Response Pack Page 28 of 99

29 data Validations to be performed for metering installations with calculated metering data 11 LOAD PROFILING CONVERSION OF ACCUMULATED METERING DATA Requirements for load profiling Profile Preparation Service - Controlled Load Profile Basic Meter Profiler Controlled Load Profile Preparation Service - Net System Load Profile Basic Meter Profiler - Net System Load Profile Procedure Consultation - Participant Response Pack Page 29 of 99

30 11.6. Start Dates and End Dates 12 UNMETERED LOADS DETERMINATION OF METERING DATA Requirement to produce calculated metering data (v) If an Unmetered Device is shared with another NMI, the proportion of load that is agreed by affected Registered Participants to be attributable to that NMI (k). Each k factor will be less than 1. The sum of the k factors for a shared Unmetered Device across each respective NMI must be equal to 1; Controlled Unmetered Loads (b) Each Unmetered Device in the Inventory Table is a unique combination of physical hardware, time control classification and shared portion. For example, if an Unmetered Device is shared with another NMI, the individual portions of the Unmetered Device(s) must be included in the Inventory Table as a separate Unmetered Device type on each NMI Other unmetered loads ON delay and OFF delay Traffic signal dimming (a) This clause Section applies from 1 July 2015 only to Jurisdictions where traffic signals are classified as a market load. Procedure Consultation - Participant Response Pack Page 30 of 99

31 13 SUBSTITUTION FOR TRANSFER Application The requirements of clause Sections and apply during a retailer of last resort RoLR Event or where a participating Jurisdiction has requested AEMO to undertake End -User Customer transfers requiring metering data Substitutions Manually read interval metering installations Manually read accumulation metering installations Procedure Consultation - Participant Response Pack Page 31 of 99

32 5. MSATS Procedures: CATS Procedure Principles and Obligations Clause Heading Participant Comments Metering Competition Embedded Networks Meter Replacement Processes QUICK REFERENCE GUIDE Notes: EN: Embedded Network, ENC: Embedded Network Child NMI, ENP: Embedded Network Parent NMI. Why remove the Embedded Network? It explains the abbreviation. Suggest removing NMI as this is referenced in the transactions above. HOW TO USE THIS DOCUMENT 1 INTRODUCTION 1.1 PURPOSE AND SCOPE 1.2 DEFINITIONS AND INTERPRETATION 1.3 COMMENCEMENT OF CHANGES Procedure Consultation - Participant Response Pack Page 32 of 99

33 1.4 RELATED DOCUMENTS 2 OBLIGATIONS BY ROLE 2.1 GENERAL OBLIGATIONS Suggest the following rewording: (e) A CATS Participant must not select an the Objection Code which applies to the reason for objection and must be able to produce evidence, upon request, to substantiate the use of an Objection Code. unless the Objection is fair and reasonable. (f)(e) A CATS Participant must not submit information to the MSATS system which cannot be demonstrated, when requested in accordance with the CATS Procedures enforcement process, that the information reasonably represents a business practice of that CATS ParticipantFor example, when an Objection is made using a specific Objection Code, the Participant who made the Objection must be able to produce evidence upon request to substantiate it. 2.2 FINANCIALLY RESPONSIBLE MARKET PARTICIPANT (g) (f) CATS Participants must use their best endeavours to comply with their obligations contained in these CATS Procedures to ensure that the transfer of a connection point NMI from one FRMP to another FRMP is not delayed, acknowledging the legitimate use of Objection Codes which can impact the progress of the NMI transfer. (b) (a) Initiate a Change Request for the transfer of a NMI in accordance with the applicable Timeframe Rules Jurisdictional rules. Subject to the retrospective and prospective periods in MSATS, the New FRMP must initiate the transfer: 1. Having the mandatory information required to initiate a valid transfer in MSATS,; and 2. No later than two business days after the conclusion of the Cooling-Off Period, as required by the relevant jurisdiction;. 3. Following a request for field work to be performed at the Connection Point by the LNSP RP or MP, the transfer is raised in accordance with 1 and 2 above. Procedure Consultation - Participant Response Pack Page 33 of 99

34 The Jurisdictional rules as they apply to the transfer of a NMI are not the same as the Time Frame rules in the procedures. The Jurisdictional rules determine whether the transfer can be done in the cooling off period or must be issued after the cooling off period has ended. Suggest re-instating the reference to Jurisdictional rules. 2.2(b) (a)3. was designed to allow retailers to wait for special read and reconnection service order responses to be returned to confirm the actual read date prior to the transfer request being submitted. This could be more than two days after the cooling off period. Suggest this clause be re-instated. (s) (o) Update or provide the Customer Classification Code established in MSATS for an consumer End User at a NMI where the Customer Classification Code has changed, within five business days of any New contract with an consumer End User at that connection point. 2.3 LOCAL NETWORK SERVICE PROVIDER Adopt the Role of Metering Coordinator (RP) who appoints the, MP MPB, MPC and MDP as required by the National Electricity Rules NER and any derogation to the National Electricity Rules. 2.4 LOCAL RETAILER 2.5 METERING DATA PROVIDER (a) Use reasonable endeavours to provide metering data to the New FRMP within two business days of a request for this information from the New FRMP. Timeframe Rules Jurisdictional rules define the period for which metering data can be requested. The Timeframe rules do not define the period for which the meter data can be requested. Procedure Consultation - Participant Response Pack Page 34 of 99

35 2.6 METERING PROVIDER CATEGORY B (b) Appoint an MP (updating the roles of MPB and MPC accordingly) for the provision, installation and maintenance of the metering installation, and ensure that the metering installation is provided, installed and maintained in accordance with the NER and the procedures authorised under the NER. 2.7 METERING COORDINATOR (c) Inform the LNSP when a connection point is remotely disconnected. To remove the confusion generated from the field id remaining as RP but holding the MC details, particularly with new entrants in the market taking up the role of MC and ENM, it is suggested the field id be changes to MC. It is understood this would require a co-ordinated approach by AEMO and participants. 2.8 RETAILER OF LAST RESORT 2.9 SECOND NETWORK SERVICE PROVIDER 2.10 AEMO (h)(k) Cancel/withdraw any incomplete dormant retail transfers, which remain incomplete after 7 months from the date of after initiation. Procedure Consultation - Participant Response Pack Page 35 of 99

36 2.11 EMBEDDED NETWORK MANAGER a) Initiate a Create NMI Change Request. This must be done within two business days of the mandatory data required by the Change Request becoming available. This mandatory information includes that consent from a retailer to be nominated as the FRMP in MSATS has been obtained by the ENM prior to initiating the Change Request. 3 CATS FUNCTIONALITY (g) A Change Request will be Completed on the date nominated as the Actual Change Date, if this is a future date, or on the earliest date after the Objection Logging Period has been reached, or if the Actual Change Date is a Retrospective Day all Objections have been removed, if the Actual Change Date is a Retrospective Date. 3.1 OVERVIEW This clause is confusing. Suggest the following: A prospective Change Request will be completed on the nominated Actual Change Date or on the earliest date after the Objection Logging Period has been reached. A retrospective Change request will be completed once all objections have been removed. If there are no objections, on the earliest date after the Objection Logging Period has been reached. 3.2 PRINCIPLES 3.3 TRANSACTION TYPES 3.4 CHANGE REQUESTS Procedure Consultation - Participant Response Pack Page 36 of 99

37 3.5 CHANGE REQUEST STATUS LIFE CYCLE The initiator of the transaction Change Request has withdrawn the transaction. 3.6 TRANSACTION VALIDATION When a transaction is Cancelled, notifications are sent to the relevant parties Participants in accordance with the Change Request Status Notification Rules. 3.7 VALID PROPOSED CHANGE DATE FOR PROSPECTIVE AND RETROSPECTIVE CHANGE REQUESTS Need to be consistent; if we have struck out transaction and replaced it with Change Request, this needs to flow through the document. (b) For a Retrospective Change, the Proposed Change Date must either be today s the date of on which the Change Request is submitted or a date prior to the date is was submitted in the past. 4 CATS CODES AND RULES FOR A CHANGE REQUEST 4.1 INTRODUCTION 4.2 CHANGE REASON CODE 4.3 ROLE CODES Procedure Consultation - Participant Response Pack Page 37 of 99

38 4.4 CHANGE REQUEST INITIATION RULES 4.5 JURISDICTION CODES 4.6 TIMEFRAME RULES BADDATA Used by a participant to indicate the standing data in the change request or the NMI Master Record is incorrect (e.g. meter serial number). If the participant role is incorrect; use NOTRESP. BADPARTY Used by the new MC. One or more of the roles of MDP, MPB or MPC nominated on the Change Retailer request is incorrect. Either it is not the participant required by the MC or the participant does not have the accreditation for the role to which they have been appointed. 4.7 OBJECTION CODES DATEBAD (1) (a) Used by a MDP. Applies to change of retailer requests for meter types 4A, 5 and 6 to indicate the proposed date in the change request does not align to the date the actual reading is scheduled to be taken. (b) Used by the current FRMP, MDP or MPC for retrospective change of retailer requests where one or both of the proposed change date or actual end date is incorrect. DEBT Used by the current FRMP. Applies to Change Retailer requests. Participants should check the relevant jurisdictional documents for conditions applying to objections for aged debt. Procedure Consultation - Participant Response Pack Page 38 of 99

39 DECLINED Used by a participant who does not or cannot perform the role for which they were nominated in the change request. NOACC (2) (1) Used by the MDP where there is no access to obtain metering data from a type 4A, 5 or 6 metering installation to facilitate a change of retailer request. NOTAPRD Used by the LNSP. The MPC and/or MPB is not accredited or authorised to operate within the LNSP area. Can be used more broadly where the participant is not approved to operate in the LNSP area. NOTRESP Used by a participant where they a not responsible for a role for which they have been nominated in a change request. RETRO Used by a participant to indicate they do not agree to a retrospective change request. BLOCK Used by AEMO. The objection is raised at the request of a jurisdiction or for operational reasons. CONTRACT (a) Used by the current FRMP and only applies to Large NMIs in QLD. A change of retailer request seeks to transfer an End User who is still under contract to the current FRMP. (b) Used by the MC and only applies to large NMIs in all jurisdictions where they are currently contracted to an End User. Procedure Consultation - Participant Response Pack Page 39 of 99

40 NOTRANS Used by the current FRMP and only applies to retrospective change of retailer requests. A check of their records shows no previous change of retailer request exists for the error correction change of retailer. NOTAWARE Used by the current FRMP and only applies to retrospective change of retailer requests. No communication has been received from the new FRMP advising a retrospectives change of retailer. CRCODE Used by a participant where the Change Reason Code does not apply to the NMI in the change request. Remove the Note (1) as it is contained in the Description. Note (2) becomes Note (1). It is suggested these codes be placed in alphabetical order in the table. 4.8 OBJECTION RULES 4.9 NMI CLASSIFICATION CODES Delete 4.9 (d); the table is already reference in (c) END USER CLASSIFICATION 4.11 STATUS CODES (NMI AND DATASTREAM) For code G use Applies when instead of Denotes to be consistent with the other descriptions. Procedure Consultation - Participant Response Pack Page 40 of 99

41 Agree with the new codes R and N 4.12 METERING INSTALLATION TYPE CODES Agree with the inclusion of the new meter Installation Type codes. Vic AMI meters are registered in MSATS as MRIM. Will AEMO update the code in MSATS for each Vic AMI meter? Will Vic AMI apply to all advanced meters in Vic or will those advanced meters still delivering data manually remain as MRIM? Table 4M 4.13 READ TYPE CODE Should PR also apply to type 4A metering installations? Should NB also apply when a type 4A metering installation is installed? 4.14 FIELD VALIDATION RULES 4.15 CHANGE REQUEST STATUS NOTIFICATION RULES 4.16 MAINTENANCE OF CODES AND RULES 4.17 DATASTREAM STATUS CODE 4.18 EMBEDDED NETWORK Procedure Consultation - Participant Response Pack Page 41 of 99

42 CODES AND RULES 4.19 OBTAINING ELECTRONIC DOWNLOADS OF CONFIGURATION RULES 5 CODES AND RULES FOR OTHER TRANSACTION TYPES 5.1 SEND CHANGE REQUEST STATUS NOTIFICATION 5.2 REQUEST PARTICIPANT DATA 5.3 RAISE OBJECTIONS 5.4 WITHDRAW A CHANGE REQUEST 5.5 WITHDRAW AN OBJECTION 5.6 REQUEST A NMI DISCOVERY SEARCH 5.7 PROVIDE A NMI DISCOVERY Need to include the transaction type code as it is referenced in the new (a). Procedure Consultation - Participant Response Pack Page 42 of 99

43 SEARCH RESPONSE 5.8 PROVIDE A CHANGE REQUEST RESPONSE Need to include the transaction type code as it is referenced in the new (a). 5.9 PROVIDE AN OBJECTION RESPONSE Need to include the transaction type code as it is referenced in the new (a) PROVIDE AN ACKNOWLEDGMENT OF A TRANSACTION 5.11 ADVISE OF AN UPDATE TO A CODE OR RULE Need to include the transaction type code as it is referenced in the new (a) REQUEST A REPORT 5.13 GUIDELINES FOR MANAGING CONCURRENT RETAIL TRANSFERS (a) Concurrent retail transfers are those where there is more than one Change of Retailer retail transfer transaction Change Request for a particular NMI at the same time in the MSATS system. (f) The existing Change of retailer Request shall also be is cancelled by MSATS and notifications will be sent to all the parties related to the Change of Retailer Request as per normal notifications (i.e. FRMP, MDP, RP MC etc). The reason for the cancellation shall also be provided in the notification AEMO BULK CHANGE TOOL 6 CHANGE RETAILER SMALL Procedure Consultation - Participant Response Pack Page 43 of 99

44 OR LARGE NMI 6.1 APPLICATION [ ] (a) The NMI could transfers from a Tier 1 Site to a Tier 2 Site, or from a Tier 2 Site to another Tier 2 Site, or from a Tier 2 Site to a Tier 1 Site; and 6.2 INITIATION RULES Suggest the FRMP Obligations be re-established as a heading. It appears other sections continue to use this heading. 6.3 OTHER OBLIGATIONS 6.4 OPTIONAL REQUIREMENTS 6.5 TIMEFRAME RULES It is strongly suggested the objection logging period remain at 5 days. Reducing it to one day, with an influx of new market MC entrants whose systems may not be to the level of sophistication as some participants and who may be relying on manual processes, will only lead to error and rework across the market. 6.6 OBJECTION RULES 6.7 CHANGE REQUEST STATUS NOTIFICATION RULES 7 CHANGE RETAILER - ERROR CORRECTIONS SMALL NMIS Procedure Consultation - Participant Response Pack Page 44 of 99

45 1024 Transfer missed This code is to be used is a situation where 1025 Transferred in Error This code it to be used is a situation where 7.1 APPLICATION [ ] 1026 Cooled Off This code it to be used is a situation where 1027 Customer Moves Out on or before CR completion date This code is to be used is a situation where 1028 Non-account holder signs contract This code is to be used when a A person 7.2 CONDITIONS PRECEDENT In section 6 the Conditions Precedent was removed and included under Initiation Rules. Suggest this is also done here for consistency. 7.3 INITIATION RULES 7.4 FRMP OBLIGATIONS These were included under the Initiating Rules in section 6. The formatting needs to be consistent. 7.5 MDP OBLIGATIONS 7.6 METERING COORDINATOR OBLIGATIONS Procedure Consultation - Participant Response Pack Page 45 of 99

46 7.7 TIMEFRAME RULES As per the comment in OBJECTION RULES 7.9 CHANGE REQUEST STATUS NOTIFICATION RULES 8 CHANGE RETAILER EMBEDDED NETWORKS SMALL OR LARGE 8.1 APPLICATION [ ] (a) the NMI could transfers 8.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 8.4 FRMP OBLIGATIONS 8.5 MDP OBLIGATIONS Procedure Consultation - Participant Response Pack Page 46 of 99

47 8.6 METERING COORDINATOR OBLIGATIONS 8.7 TIMEFRAME RULES As per the comment in OBJECTION RULES 8.9 CHANGE REQUEST STATUS NOTIFICATION RULES 9 PROVIDE DATA PROVIDE ACTUAL CHANGE DATE SMALL OR LARGE 9.1 APPLICATION [1500] 1500 Provide Actual Change Date (MDP) This is the situation where t The MDP is required to provide 9.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 9.4 MDP OBLIGATIONS Procedure Consultation - Participant Response Pack Page 47 of 99

48 9.5 TIMEFRAME RULES 9.6 OBJECTION RULES 9.7 CHANGE REQUEST STATUS NOTIFICATION RULES 10 CREATE NMI CREATE A NMI SMALL OR LARGE 2001 Create NMI Details Retrospective 10.1 APPLICATION [ ] Remove in that occurs before about Create NMI Details - Retrospective ( Tier 1 only) Remove in regard to and replace with about. This is consistent with the other clauses CONDITIONS PRECEDENT As per the comment in INITIATION RULES 10.4 LNSP Obligations Procedure Consultation - Participant Response Pack Page 48 of 99

49 10.5 MPB OBLIGATIONS 10.6 TIMEFRAME RULES As per the comment in OBJECTION RULES 10.8 CHANGE REQUEST STATUS NOTIFICATION RULES 11 CREATE NMI CREATE CHILD NMI - SMALL OR LARGE 11.1 APPLICATION [ ] Replace in regard to, in all three descriptions, with about. This is consistent with the previous sections CONDITIONS PRECEDENT As per the comment in INITIATION RULES 11.4 ENM Obligations 11.5 MPB OBLIGATIONS Procedure Consultation - Participant Response Pack Page 49 of 99

50 11.6 TIMEFRAME RULES As per the comment in OBJECTION RULES 11.8 CHANGE REQUEST STATUS NOTIFICATION RULES 12 CREATE NMI CREATE NMI, METERING INSTALLATION DETAILS AND MDM DATASTREAM SMALL OR LARGE 12.1 APPLICATION [ ] 12.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 12.4 LNSP Obligations 12.5 TIMEFRAME RULES As per the comment in 6.5. Procedure Consultation - Participant Response Pack Page 50 of 99

51 12.6 OBJECTION RULES 12.7 CHANGE REQUEST STATUS NOTIFICATION RULES 13 MAINTAIN METERING CREATE METERING INSTALLATION DETAILS SMALL OR LARGE 13.1 APPLICATION [ ] Replace in regard to with about in all three descriptions. This is consistent with previous sections CONDITIONS PRECEDENT As per the comment in INITIATION RULES 13.4 MPB Obligations 13.5 TIMEFRAME RULES 13.6 OBJECTION RULES Procedure Consultation - Participant Response Pack Page 51 of 99

52 13.7 CHANGE REQUEST STATUS NOTIFICATION RULES 14 MAINTAIN METERING EXCHANGE OF METERING INFORMATION SMALL OR LARGE 14.1 APPLICATION [ ] Replace in regard to with about in both descriptions. This is consistent with previous sections CONDITIONS PRECEDENT As per the comment in INITIATION RULES 14.4 MPB Obligations 14.5 TIMEFRAME RULES 14.6 OBJECTION RULES 14.7 CHANGE REQUEST STATUS NOTIFICATION RULES Procedure Consultation - Participant Response Pack Page 52 of 99

53 15 MAINTAIN METERING CHANGE METERING INSTALLATION DETAILS SMALL OR LARGE 15.1 APPLICATION [ ] 15.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 15.4 MPB Obligations 15.5 TIMEFRAME RULES 15.6 OBJECTION RULES 15.7 CHANGE REQUEST STATUS NOTIFICATION RULES 16 MAINTAIN METERING - ADVANCED CHANGE METERING INSTALLATION Procedure Consultation - Participant Response Pack Page 53 of 99

54 DETAILS - SMALL OR LARGE 16.1 APPLICATION [ ] 16.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 16.4 Metering Coordinator Obligations 16.5 TIMEFRAME RULES When preparing a Change Request, the Current M<C must choose 16.6 OBJECTION RULES 16.7 CHANGE REQUEST STATUS NOTIFICATION RULES 17 MAINTAIN METERING - ADVANCED EXCHANGE OF METERING - SMALL OR LARGE 17.1 APPLICATION [ ] Procedure Consultation - Participant Response Pack Page 54 of 99

55 17.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 17.4 Metering Coordinator Obligations 17.5 TIMEFRAME RULES 17.6 OBJECTION RULES 17.7 CHANGE REQUEST STATUS NOTIFICATION RULES 18 MAINTAIN METERING CHANGE NETWORK TARIFF CODE SMALL OR LARGE 18.1 APPLICATION [ ] 3100 Change Network Tariff the the Network Tariff Code 18.2 CONDITIONS PRECEDENT As per the comment in 7.2. Procedure Consultation - Participant Response Pack Page 55 of 99

56 19.3 INITIATION RULES 18.4 LNSP Obligations 18.5 TIMEFRAME RULES 18.6 OBJECTION RULES 18.7 CHANGE REQUEST STATUS NOTIFICATION RULES 19 MAINTAIN DATASTREAM CREATE MDM DATASTREAM SMALL OR LARGE 19.1 APPLICATION [ ] Replace in regard to with about in all three descriptions. This is consistent with previous sections CONDITIONS PRECEDENT As per the comment in INITIATION RULES 19.4 MDP Obligations Procedure Consultation - Participant Response Pack Page 56 of 99

57 19.5 TIMEFRAME RULES 19.6 OBJECTION RULES 19.7 CHANGE REQUEST STATUS NOTIFICATION RULES 20 MAINTAIN DATASTREAM - EXCHANGE OF DATASTREAM INFORMATION SMALL OR LARGE 20.1 APPLICATION [ ] 20.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 20.4 MDP Obligations 20.5 TIMEFRAME RULES 20.6 OBJECTION RULES Procedure Consultation - Participant Response Pack Page 57 of 99

58 20.7 CHANGE REQUEST STATUS NOTIFICATION RULES 21 MAINTAIN DATASTREAM CHANGE MDM DATASTREAM SMALL OR LARGE 21.1 APPLICATION [ ] 21.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 21.4 MDP Obligations 21.5 TIMEFRAME RULES 21.6 OBJECTION RULES 21.7 CHANGE REQUEST STATUS NOTIFICATION RULES Procedure Consultation - Participant Response Pack Page 58 of 99

59 22 MAINTAIN NMI UPDATE NEXT SCHEDULED READ DATE SMALL OR LARGE 22.1 APPLICATION [ ] 22.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 22.4 MDP Obligations 22.5 TIMEFRAME RULES 22.6 OBJECTION RULES 22.7 CHANGE REQUEST STATUS NOTIFICATION RULES 23 MAINTAIN NMI BACKDATE A NMI SMALL OR LARGE 23.1 APPLICATION [ ] Procedure Consultation - Participant Response Pack Page 59 of 99

60 23.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 23.4 LNSP OBLIGATIONS (5001 ONLY) 23.5 ENM OBLIGATIONS (5021 ONLY) 23.6 AEMO OBLIGATIONS 23.7 MPB OBLIGATIONS 23.8 TIMEFRAME RULES As per the comment in OBJECTION RULES CHANGE REQUEST STATUS NOTIFICATION RULES 24 MAINTAIN NMI CHANGE A NMI SMALL OR LARGE Procedure Consultation - Participant Response Pack Page 60 of 99

61 24.1 APPLICATION [ ] Replace in regard to with about in all three descriptions. This is consistent with previous sections CONDITIONS PRECEDENT As per the comment in INITIATION RULES 24.4 LNSP Obligations 24.5 TIMEFRAME RULES The current MDP can object according to Table 24.6 but in Table 24.5, there are zero days to lodge the objection OBJECTION RULES 24.7 CHANGE REQUEST STATUS NOTIFICATION RULES 25 MAINTAIN NMI CHANGE A NMI - CUSTOMER CLASSIFICATION CODE SMALL OR LARGE 25.1 APPLICATION [ ] Procedure Consultation - Participant Response Pack Page 61 of 99

62 25.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES 25.4 FRMP Obligations 25.5 TIMEFRAME RULES 25.6 OBJECTION RULES 25.7 CHANGE REQUEST STATUS NOTIFICATION RULES 26 MAINTAIN NMI CHANGE NMI EMBEDDED NETWORK (CHILD) SMALL OR LARGE 26.1 APPLICATION [ ] Replace in regard to with about in both descriptions. This is consistent with previous sections CONDITIONS PRECEDENT 26.3 INITIATION RULES Procedure Consultation - Participant Response Pack Page 62 of 99

63 26.4 ENM Obligations 26.5 TIMEFRAME RULES ** The ACT and Tasmanian regulators have not approved the use of embedded networks in their respective Jurisdictions. QLD jurisdiction has not approved embedded networks for SMALL consumers and has determined that there will be no new embedded networks for LARGE consumers. Why has this been deleted? Is this no longer correct. If it is correct suggest it is moved to section OBJECTION RULES 26.7 CHANGE REQUEST STATUS NOTIFICATION RULES 27 MAINTAIN NMI CHANGE PARENT NAME SMALL OR LARGE 27.1 APPLICATION [ ] 27.2 CONDITIONS PRECEDENT As per the comment in INITIATION RULES Procedure Consultation - Participant Response Pack Page 63 of 99