|Entity ID||Entity name||Period ended||Measure|
|3CEP||Clean Energy Partners||31/07/2020||0.0|
|3CEP||Clean Energy Partners||31/08/2020||0.0|
|3ESP||Energy Solution Partners||31/08/2020||0.0|
|3SNT||Stephenson & Turner NZ||30/09/2020||0.0|
|3CEP||Clean Energy Partners||31/10/2020||0.0|
|3CEP||Clean Energy Partners||30/11/2020||10.0|
|3CEP||Clean Energy Partners||31/12/2020||0.0|
This report provides insights into consumer agent requests for consumption data from retailers on behalf of consumers. Users can view a range of measures including requests made from agents, responses from retailers, the average time for responses, or responses that take longer than 5 business days to action.
The Authority amended the Code to improve the EIEP13 process used by consumer agents to request consumption data from a retailer on behalf of a consumer. These changes addressed concerns that access to data and the use of that data to drive innovation were being hampered. The Code changes came into effect on 31 March 2020 and were designed to streamline access via standardised file formats and processes. This report provides insights into how agents and retailers are performing under the new process.
The ‘Request or response’ parameter separates the reporting for the entities making requests from those responding to the requests. This separation allows insights to be drawn into how individual retailers are responding to requests (relative to their peers) or how responses from retailers in aggregate are impacting agents and their business models. Responses are recorded in the month the request was made or the month the response. A competing retailer can also act as a consumer agent to request information about a consumers’ consumption and injection profile from the current retailer in order to present the customer a tailored offering. The counts in this report are ICPs covered by requests for the consumption data. An individual request may cover multiple ICPs.
Retail entities and parent companies in this report include retailers, traders, and consumer agents. The trader reflects the trader code used in the request or response. An option is included to aggregate retailers and agents separately.
Market segment breakdowns are available from September 2013 when ANZSIC codes were introduced into the registry in a field maintained by the trader. No breakdown is available at NSP level. Market segments are not mutually exclusive. Residential connections have no ANZSIC code. Small and Medium Enterprise (SME) connections are defined as those assigned meter categories 1 and 2 (low voltage up to 500A) with an ANZSIC code excluding those relating to central or local government and other utility services. Industrial connections have ANZSIC codes from A through E while commercial connections use ANZSIC codes F through Z. More information on ANZSIC codes is available at www.stats.govt.nz.
The ‘Measures’ parameter provides a range of different metrics that help show what requests are occurring, how many requests are declined, how many requests don't receive any response, how many requests take more than five business days to receive a response, and the average time to receive a response. For the measures that use business days in this report we are counting part days as a business day.
The ‘Show’ parameter allows users to view metrics as a count or relative measure (i.e. proportion). The proportion for the number of requests or responses will highlight the proportion of total requests (or responses) in that market segment that each entity (or group of entities) is responsible for. For the other measures, the proportion will represent the proportion of the entities' total requests (or responses) that the selected measure represents.
Visit the glossary for a list of defined terms used on the website.
Visit the forum to see if the information you are looking for is already available or ask a question to see if some of our informed users or staff can help?
Clicking the blue discussion tags below the notes will take you directly to discussions on that topic.