Data provision changes Extended reserve manager Consultation briefings 31 October 2016 - Wellington 3 November 2016 - Auckland

Contents Summary of changes Unit configuration file Unit load file Uploading to the portal Cleaning and estimating data © Copyright NZX Ltd. 2016

In response to feedback The key changes: Unit configuration csv fields simplified, better explanations Unit load csv simplified and layout changed Portal changes Instructions and checklists to clean data Instructions for estimating missing or bad data

Example – unit configuration file Unit Configuration Changes 19 fields remain the same Removed fields – double-ups or no longer needed: currently used currently provide flexible currently armed SCADA indication SCADA capable Clarified the instructions: General rule: state the characteristics the demand unit will have when in service. current block allocation – 1 or 2 if currently on an AUFLS block at point of submission, or N if not Altered fields: existing functionality = trip control df/dt – U or B only – existing relays will be U for under-frequency only, or B for both df/dt and u/f. All new relays will be B as they must be supplied with both. flexible capability – S or N – S for the demand unit is capable of being armed and disarmed via SCADA remote control or N if no fast response capable – Y or N – when in service, will the demand unit be capable of responding within <250ms New fields: zone substation – text identifier, or N for no zone sub tested block 1 tested block 2 tested block 3 tested block 4 Note: N to all for the first selection process. Y for second / later selection processes where the demand unit is configured and tested for the AUFLS block settings. © Copyright NZX Ltd. 2016

Example – unit load file Unit Load Changes Major change to file format. Instead of 50-54 columns holding all trading periods for 1 day for a Demand Unit, we now have 4 columns holding the data for one trading period for one Demand Unit. (old file format on top, new file format on bottom) Also: Header changed – now column headings Removed fields: flow direction checksum Altered fields: date becomes trading period © Copyright NZX Ltd. 2016

Example – unit load file Start of daylight saving © Copyright NZX Ltd. 2016

Example – unit load file End of daylight saving © Copyright NZX Ltd. 2016

Screenshots of new portal © Copyright NZX Ltd. 2016

Screenshots of new portal – Successful file upload © Copyright NZX Ltd. 2016

Screenshots of new portal – File upload failure © Copyright NZX Ltd. 2016

File upload process Portal changes More flexibility in grouping your unit load data Better help / validation comments on the portal Samples of unit load and unit configuration files © Copyright NZX Ltd. 2016

Cleaning data – zeros Data specification: instructions section 4.3, checklist section 5.5 1.3 million zeros submitted in the most recent year of data Some zeros are valid (see 4.3.1, page 21) ERM did not query the submitted zeros to the level proposed in the data specification ERM may query: >6 contiguous zeros (3 hours for a planned outage) >50 zeros per demand unit per year (total outages) © Copyright NZX Ltd. 2016

Cleaning data – negatives, spikes Data specification: instructions section 4.3, checklist section 5.5 Negative values must be confirmed (injections are rare) Spikes, swells: must be identified for each year and demand unit identify any trading period MW value that is >200% of the average annual MW value © Copyright NZX Ltd. 2016

Estimating data Guidance provided: Data specification section 4.4 Guidance provided: Copy from most relevant similar period OR Average of several equivalent periods © Copyright NZX Ltd. 2016

Draft data specification This is a draft specification The data specification is subject to finalising the selection methodology so changes may occur. © Copyright NZX Ltd. 2016

Questions © Copyright NZX Ltd. 2016