1. Extended Reserve Technical Requirements Schedule (TRS) Presenters: Justin Blass, Project Manager Gillian Rodger, Power System Analysis Kevin Wronski, Compliance

2. Why are we here? Industry Brief Informed submissions Fit-for- purpose TRS Secure power system Desired outcome Direct Benefit End Benefit Deliverable We need you !

3. Engagement overview Workshop 2 Nov 2015 Industry Brief Nov 2016 Testing of AUFLS Systems Implementation Overview Workshop 1 Sep 2015 Overview Workshop 3 April 2016 TRS and supporting documents Informal Consultation Formal Consultation 11 Oct 2016 29 Nov 2016

4. Responsibility Overview Establish technical requirements Establish selection methodology ERM SO Provider Provide data for selection process Undertake selection process Implement selection process Provide extended reserve Monitor selection outcome We are here !

5. Transpower’s role Develop technical requirements report TRR Coordinate implementation plans Publish extended reserve schedule Imp. Plans Create technical requirements schedule TRS Establish technical requirements ER Sched Publish implementation guidelines Imp. Guide Issue statement of extended reserve obligations SERO Implement selection outcome

6. Why change AUFLS? https://www.transpower.co.nz/system-operator/about-system-operation- service/learning-centre 2 AUFLS blocks 16%, 16% 4 AUFLS blocks 10%, 10%, 6%, 6%

7. Technical Requirements Schedule 7 Sets out –the technical specification for extended reserve to support SO meeting the principal performance obligations –periodic testing and information provision requirements

8. The TRS clauses 24 clauses in total

9. The TRS clauses 5 clauses - ERM responsible for Extended reserve is only AUFLS AUFLS blocks are available at all times Acceptable range of AUFLS blocks Preference for AUFLS blocks selected Not impair SO ability to meet Security Policy quality targets

10. The TRS clauses 17 clauses – ER providers responsible for Conditions of AUFLS blocks to ensure desired system response Testing and reporting requirements Monitoring requirements Data resolution

11. AUFLS Systems in more detail The next few slides mainly review what we have presented in earlier workshops: What does an AUFLS system typically look like?; How should they behave?; How do we ensure they do what is intended of them?; and When they are triggered how do we know it they what they were designed to do?

12. AUFLS system topology

13. AUFLS block sizes TRS Clause 8

14. Operating time TRS Clause 12 Protection relay sensing time Adjustable ‘hold’ delay Tripping or auxiliary relay operating time Circuit breaker opening time Demand is disconnected Frequency Set point Frequency Total AUFLS operating time < 400ms Time A E B C D

15. AUFLS block settings AUFLS Block* Primary Frequency Secondary Frequency Frequency change rate Set Pt (Hz) Hold (ms) Set Pt (Hz) Hold (s) Set Pt (Hz) Hold (ms) Guard (Hz) 147.9100 247.710047.914 347.510047.714 447.310047.514-1.210048.5 *AUFLS systems must remain operative if guard voltage ≥ 50% of nominal V TRS Clause 14

16. Testing requirements Required for: New AUFLS systems Existing AUFLS systems: –with new (untested) settings –after maintenance or upgrade –for routine testing TRS Clause 17 - 19

17. Related documents Guidelines are available on: Testing methodology – in the amendments to the Companion Guide for Testing of Assets What information needs to be included in compliance reports – in the compliance report template

18. Reporting Required to demonstrate compliance: After any testing carried out To demonstrate a compliant response/non- response to a frequency event If a system is reasonably believed to be non- compliant then you must notify the system operator TRS Clause 19 - 21

19. Reporting ctd The first compliance report of any AUFLS system should be submitted to the system operator for review All compliance reports must be stored by the asset owner and may be requested by the system operator

20. Monitoring Required for every AUFLS system, and should include: Time stamped demand (MW) Be set to the highest resolution Have a sample rate of 1 sample every 100 ms or better TRS Clause 22 - 24

21. Monitoring ctd Data recorded must: Detail the duration of the operating time Be stored for 40 business days Be available upon request by the system operator

22. Where to from here? 1.Consider submissions -Close on 29 November 2016 -Publish summary of submission on website 2.Update and publish TRS -Publish TRS on website in early 2017

23. Any questions

24. Implement selection outcome overview Presenters: Justin Blass, Project Manager

25. Where are we now? Existing SchemeExisting Obligation -All distributors (exempted parties) -At least 16% demand per block at all times 47.9 47.8 47.7 47.6 47.5 47.4 47.3 6%10%16% % NI Load on AUFLS Freq setpoint (Hz)

26. Where are we going? Future SchemeFuture Obligation -Only selected distributors -Provide selected demand units 47.9 47.8 47.7 47.6 47.5 47.4 47.3 6%10%16% % NI Load on AUFLS Freq setpoint (Hz) *Frequency change rate trigger at -1.2 Hz/s *

27. How do we get there? Scheme change overDesired Outcomes -Maintain a secure system during implementation -Efficient planning and delivery of implementation 47.9 47.8 47.7 47.6 47.5 47.4 47.3 6%10%16% % NI Load on AUFLS Freq setpoint (Hz)

28. Implementation Overview Publish E.R. schedule Coordinate implementation plans Monitor and coordinate changes Carry out implementation Issue procurement notice Issue S.E.R.O. Delivery Phase Planning Phase ERM SO Provider Complete compliance reports Prepare implementation data set 1011 0100 0010 Prepare implementation plans Submit change request Publish Implementation guidelines

29. Planning Phase Outputs –an approved implementation plan –published ER Schedule –issued SERO Who’s involved? –All selected asset owners –All asset owners presently providing AUFLS –System Operator –ERM (data collection)

30. What is included? 1.Stop dates for all legacy “demand units” in the existing AUFLS scheme 2.Start dates for demand units selected to be armed in the procurement schedule 3.A point of contact for managing any requests and queries

31. Example Plan

32. What data is required? 1.Demand Profile –Provide half hourly average MW data for each existing demand units 2.Demand Unit Configuration –Sub-set of fields from data specification

33. When is data required? Jan 17 Nearest quarter end Submit implementation plans and planning data P.Sched. Data Set Implementation Planning – Legacy Data Set Implementation Planning – Data Set Submit procurement schedule data set 1 Year ERM issues procurement notice Implementation planning Apr 17Oct 17Nov 17Oct 16 Quarterly reporting begins

34. How will we review plans?

35. Delivery Phase Starts when SERO Issued Output: –Physical change over from old to new scheme –Up to date extended reserve schedule Focus –monitoring progress and managing changes

36. Managing change Submit a change request if you change a single or group of demand units where impact is: –greater than 1 week; OR –greater than 1 MW Change request should be submitted at least 2 weeks prior to the earlier of the old or new dates

37. Requirements on providers Terms and conditions Selection Methodology Extended Reserve Schedule Implementation plan Statement of extended reserve obligation Procurement Schedule Implementation requirements -Follow terms and conditions for all selected and all armed demand units -Notification of changes to start/stop dates -Maintain compliance reports ERM SO Provider Procurement Notice

38. Implementation Timeline Issue Procurement Notice Complete Implementation plans and submit data 40 business days 3 – 6 months Publish ER Schedule Issue SERO -Obligation change -Implementation can begin Implementation Complete PLANNINGDELIVERY Co-ordinationImplementation ERM SO Provider All start and stop dates have occurred

39. Questions