Responsibilities of each Party.
Data transfer, security, and storage.
Duration and Review of the MoU.
This Memorandum of Understanding (MoU) is made on the 28th day of June 2024 between The Central Statistics Office, Skehard Road, Cork, T12 X00E (CSO) and ESB Networks, Three Gateway, East Wall Road, Dublin 3, D03 R583 (ESBN)
CSO | Central Statistics Office. |
ESBN | ESB Networks |
GDPR | General Data Protection Regulation. |
JLG | Joint Liaison Group. |
MoU | Memorandum of Understanding. |
ToR | Terms of Reference. |
“Act”The Statistics Act, 1993 as may be amended from time to time.“Breach” Has the meaning assigned by Article 4(12) of the General Data Protection Regulation (GDPR).“Controller”Has the meaning assigned by Article 4(7) GDPR.“Data” Information, relating to ESBN’s delivery of energy, as detailed in Appendix 1 and Appendix 2.“Personal Data” Has the meaning assigned by Article 4(1) GDPR.“Processing” Has the meaning assigned by Article 4(2) GDPR.“Purpose”The collection, compilation, extraction, and dissemination for statistical purposes of information concerning the electricity network in Ireland.
The CSO was established in 1949 and became a statutory body in 1994, under the Statistics Act, 1993 (the ‘Act’).
ESBN is the Distribution System Owner and Operator in Ireland, licenced by the Commission for Regulation of Utilities under the Electricity Regulation Act, 1999, as amended by the European Communities (Internal Market in Electricity) Regulations 2000-2008. ESBN is a wholly owned subsidiary of the Electricity Supply Board.
The functions of the CSO are set out in the Act. In particular Section 10 states that the functions of the Office are the collection, compilation, extraction and dissemination for statistical purposes of information relating to economic, social and general activities and conditions in the State. The Office has the authority to co-ordinate official statistics compiled by public authorities to ensure, in particular, adherence to statistical standards and the use of appropriate classifications and has the authority to assess the statistical potential of the records maintained by public authorities and to ensure that the potential is realised. Furthermore, the CSO has legal obligations regarding the development, production, and dissemination of European statistics under Regulation 223/2009.
The function of ESB Networks DAC is to operate and ensure the maintenance of and develop, as necessary, a safe, secure, reliable, and efficient electricity Distribution System, taking into account exchanges with other interconnected systems, with a view to ensuring that all reasonable demands for electricity are met and having due regard for the environment.
The Act assigns the CSO authority to assess the statistical potential of the records maintained by public authorities and, in conjunction with them, to ensure that this potential is realised. This MoU sets out areas of mutual responsibility and understanding between the CSO and ESBN in the use of administrative data for statistical purposes in accordance with Section 30 of the Act.
The purpose of this MoU is to clarify the roles and responsibilities of, as well as the areas of cooperation between, the CSO and ESBN regarding information concerning the electricity distribution network more particularly described in Appendix 1 and Appendix 2 (the ‘Data’).
This agreement is a MoU and is not intended to create binding or legal obligations on either Party. The MoU is entered into on the understanding that it is subordinate to the relevant legislation, set out below under ‘Legal Background’, governing each Party.
This MoU also sets out a shared understanding of the parties in relation to data protection issues that may arise and roles relating to the compilation, transfer, and use of the Data. The processing of personal data of data subjects is governed by the Act, the Data Protection Act, 2018 (the ‘2018 Act’) and the GDPR.
The data controller for personal data is ESBN. When the Data is transferred to the CSO, the CSO becomes the data controller of the data file it holds. ESBN remains the controller for the data file it holds. It follows then that it is the responsibility of the CSO to report any personal data breach (a ‘Breach’) relating to the Data it holds.
In the event of a Breach relating to the data the CSO will inform the Data Protection Officer of ESBN and also inform ESBN of the breach through the Joint Liaison Group (JLG). This notification will be made within 24 hours. In addition, the CSO will refer to their own data breach procedures and may report the breach to the Data Protection Commission as appropriate. ESBN will not be held responsible for any loss, damage or injury caused as a result of such a breach.
In the event of a breach relating to the Data the CSO will inform ESBN through the JLG, in advance, of any decision to issue a public statement in relation to the breach. Similarly, ESBN will inform the CSO through the JLG, in advance, of any decision to issue a public statement in relation to the breach.
ESBN will not provide additional data or operational support in respect of the notification of data subjects in the event of a breach relating to CSO data.
All data provided to the CSO under this agreement shall be treated as strictly confidential and will be used solely for statistical purposes and in line with this agreement. Transfer and processing of the Data shall be done in accordance with the Act, the 2018 Act, the GDPR, EU law and in accordance with the CSO’s Code of Practice, in particular its protocol on data matching where one or more datasets originate from outside of the CSO.
The transfer and processing of the Data is covered by, inter alia, the following provisions:
Any data produced by the CSO from the Data, will be published in aggregate form which does not identify, or permit the identification of, any individuals or businesses. Raw data will not be disclosed by the CSO.
The CSO will request the Data, or parts thereof, by means of a request pursuant to Section 30 of the Act, such request specifying the Data requested and, where relevant, the relevant period.
The Data shall be transferred to the CSO at the frequencies outlined Appendix 1 and Appendix 2. ESBN shall not be required to furnish the Data more than once in respect of any period, however further data extracts may be sent if agreed between the parties to be necessary. The transfer will be in the form of an encrypted file via a secure file transfer protocol. The method of transfer will be reviewed regularly and updated if a more secure method becomes available.
Data will be retained, securely stored and processed by the CSO in accordance with CSO policies. Data files provided by ESBN to the CSO, will be deleted by the CSO when they are no longer needed for statistical production.
ESBN will provide the CSO with the Data in an agreed format. Information on data formats and delivery frequency shall be provided by ESBN in respect of the data files schedule. In accordance with CSO policies on the control of Data the CSO will not copy this Data onto removable media (including laptop computers) unless appropriate security provisions are in place (i.e., encryption and password access) and there is an agreed business need to do so, in which case the CSO will inform ESBN of such need via the JLG.
The data is provided “as is”. Without prejudice to ESBN’s obligations under Data Protection Laws, ESBN shall not be obliged to verify, and makes no warranties, representations or undertaking whatsoever (express or implied) in respect to the accuracy, completeness or currency of the Data, or any information which ESBN may be required to provide pursuant to the Act. The CSO shall not be entitled to assume that the Data is accurate, complete, or up to date at any time or provides any indicators as to the status of a given property.
An ESBN and CSO Joint Liaison Group (JLG) will be convened, in accordance with the CSO’s standard Data Governance Framework. The JLG will oversee the data sharing as agreed between the parties summarised in this MoU and specified in any Section 30 Request.
The Terms of Reference (ToR) for the JLG will be agreed between ESBN and the CSO. The ToR will cover, amongst other things, membership of the JLG, frequency of meetings and scope of the JLG. Changes to the ToR must be jointly agreed by both parties.
This MoU will be published on the CSO website (cso.ie) and the ESBN website.
This MoU will remain in force until a new one is entered into or either the CSO or ESBN revoke it. Depending on events, this MoU may be amended, subject to the mutual agreement of ESBN and the CSO.
This MoU will be reviewed biennially by both ESBN and the CSO. Any changes to the MoU shall only be made with the mutual written agreement of ESBN and the CSO.
Signed | Signed |
---|---|
Jennifer Banim | Nicholas Tarrant |
Central Statistics Office | ESB Networks |
Jennifer Banim | Nicholas Tarrant |
Director General | Managing Director |
Date: 28/06/2024 | Date: 01/07/2024 |
1.1.Data:
Information relating to new electricity connections, for the quarter period requested.
1.2. Purpose:
The collection, compilation, extraction, and dissemination, for statistical purposes, of information concerning the electricity network in Ireland, in particular new connections associated with housing completions.
1.3.Transfer Frequency:
ESBN shall transfer the Data, detailed below, to the CSO every quarter as soon as is practically possible after the end of the quarter to which the Data relates.
1.4. Data Points:
Table 1 of 1: DG01/2 New Connections File | |||
# | Variable | Description | Purpose |
---|---|---|---|
1 | Meter Point reference Number (MPRN) | The unique identifier for each service delivery point. | Allows the CSO to compile statistics on unique new connections and can be used to cross reference with other databases held by the CSO which contain this variable. |
2 | Address | Gives location of the property. | Can be used to cross reference and for validation by the CSO for classification purposes |
3 | Generic Longitude and Latitude | Provides actual / approximate location of dwellings. | Allows for assigning dwellings to geographies such as local authority |
4 | Created date, authorised date, energised date and current meter point status | Relate to the lifecycle of the MPRN and indicate the different stages that an MPRN can go through. | Allow the CSO to examine time period between authorisation and energised date of properties. All data provided is of a current status of ‘Energised’. |
5 | DUoS Group | Denotes the distribution use of system tariff applying to the MPRN. Generally domestic new connections will be DG01 (Urban Domestic) or DG02 (Rural Domestic). | Allows the CSO to classify new connections as urban or rural, an important distinction for housing policy |
6 | Connection type (NC no.) | Describes the nature of a connection, e.g. NC10 (Domestic Single), NC20 (Domestic Scheme) and NC40 (Apartments). | Allows the CSO to classify new dwellings into single, scheme, and apartments. |
7 | Comments | Identifies reconnections and non-dwellings such as sheds, farms, or electric fences. | Used to cross reference and for validation by the CSO for classification purposes. |
2.1. Data:
Information relating to meter consumption figures, in kilowatt-hours, and associated customer and meter location details.
2.2 Purpose:
The collection, compilation, extraction, and dissemination, for statistical purposes, of information concerning the electricity network in Ireland, in particular:
2.3 Transfer Frequency:
ESBN shall transfer the Data, detailed below, to the CSO annually.
2.4 Data Points
Table 1 of 5: Customer File | ||||
# | Variable | Description | Purpose | |
---|---|---|---|---|
1 | MPRN (live Meters) | The unique identifier for each service delivery point | Unique identifier within file. Used to match customer file with data consumption and other ESBN files. Used to match ESB data with Building Energy Ratings and other energy statistics files containing MPRN. | |
2 | Organisation | Name of the business account holder (excludes names from the DG01 and DG02 extracts). | A change of customer could explain a change in consumption levels. To cross-check data in the CSO Business Energy Use survey. For matching with the CSO Business Register, Census of Population etc. for NACE coding and data quality checking to ensure that we are matching the same household using the Eircode. | |
3 | House number | House, apartment, building number. | Needed to uniquely identify an apartment or house or business unit etc. | |
4 | Street names | Premises street and road names. | Needed to uniquely identify an apartment or house or business unit etc. for geographical coding | |
5 | District | ESB district (Cork, Midleton etc.). | Used for county coding of the customer and for summary analyses. | |
6 |
|
ESB region (CK, GW, etc.). | Used for county coding of the customer and for summary statistics. | |
7 | Country | Country location of the premises. | Used for address coding of the customer and for checking if the data record has been read correctly e.g. region codes should not appear in this field. | |
8 | Eircode | Eircode of premises. | Eircode of customer. Used for matching with other microdata sources such as the Census of Population, Gas meter file, CSO Survey of Income and Living Conditions, Building Energy Ratings, etc |
Table 2 of 5: Quarterly Consumption File | |||
# | Variable | Description | Purpose |
---|---|---|---|
1 | MPRN | The unique identifier for each service delivery point | Unique identifier within file. Used to match with customer and other files. |
2 | DUoS group | Tariff group associated with the MPRN | Classifies customer by urban residential, rural residential, business by connection voltage, etc. Used to identify sub-sectors driving electricity consumption. |
3 | Day consumption | kWh recorded at the meter during daytime hours in each quarter. | Consumption figure, tariff price may vary for a meter with day-time consumption. |
4 | Night consumption | kWh recorded at the meter during night-time hours in each quarter | Consumption figure, tariff price may vary for a meter with night-time consumption. |
5 | 24-hour consumption | kWh recorded at the meter during 24 hours in each quarter. | Consumption figure. |
6 | Night Off Peak KWH | kWh recorded at the meter during off peak night-time hours in each quarter. | Consumption figure, tariff price may vary for a meter with night-time consumption. |
7 | Peak KWH | kWh recorded at the meter during peak hours in each quarter. | Consumption figure, tariff price may vary for a meter with night-time consumption. |
8 | QH Day Off Peak KWH | Quarter Hour kWh recorded at the meter during off peak daytime hours in each quarter – For business customers only. | Consumption figure, tariff price may vary for a meter with day-time consumption. |
9 | QH Night Off Peak KWH | Quarter Hour kWh recorded at the meter during off peak night-time hours in each quarter – For business customers only. | Consumption figure, tariff price may vary for a meter with day-time consumption. |
10 | QH Peak KWH | Quarter Hour kWh recorded at the meter during peak daytime hours in each quarter – For business customers only. | Consumption figure, tariff price may vary for a meter with day-time consumption. |
Table 3 of 5: Latitude and Longitude File | |||
# | Variable | Description | Purpose |
---|---|---|---|
1 | MPRN | The unique identifier for each service delivery point. | Unique identifier within file. Used to match with customer and other files. |
2 | Latitude | Provides approximate location of the meter location (where known). | Assists with geographical coding and analysis. |
3 | Longitude | Provides approximate location of the meter location (where known). | Assists with geographical coding and analysis. |
4 | X-coordinate | Provides approximate location of the meter location (where known). | Assists with geographical coding and analysis. |
5 | Y-coordinate | Provides approximate location of the meter location (where known). | Assists with geographical coding and analysis. |
6 | Sub-latitude | Provides approximate location of the Sub-Station location (where known). | Assists with geographical coding and analysis. |
7 | Sub-longitude | Provides approximate location of the Sub-Station location (where known). | Assists with geographical coding and analysis. |
8 | Sub X-coordinate | Provides approximate location of the Sub-Station location (where known). | Assists with geographical coding and analysis. |
9 | Sub Y-coordinate | Provides approximate location of the Sub-Station location (where known). | Assists with geographical coding and analysis. |
10 | Smart meter indicator | Yes/Null field to indicate if a Smart meter has been installed. | Indicates the quality of the data as a Smart meter is more accurate than an estimated or customer meter reading. |
Table 4 of 5: DG10 and TCON Data File | |||
# | Variable | Description | Purpose |
---|---|---|---|
1 | File name. | Contains MPRN number. | To know the customer that the consumption relates to. |
2 | Date and time period. | The date and 15-minute time period that the consumption is for. | To compile consumption statistics, look at seasonality, link with electricity generation data to calculate percentage generated from renewables etc. |
3 | 15-minute consumption. | kWh recorded in 15-minute periods at the meter during the day. | Consumption figure. Having the data at 15-minute intervals, will enable us to analyse the demand from large energy users throughout the day. |
Table 5 of 5: DG10 and TCON Customer File | |||
# | Variable | Description | Purpose |
---|---|---|---|
1 | MPRN | The unique identifier for each service delivery point. | Unique identifier within file. Used to match with customer and other files. |
2 | Customer name | The name of the business customer. | For matching with the CSO Business Register, for thematic releases such as Data Centres, for aggregating consumption data to an enterprise level, etc. |
3 | Customer address details | The address of the customer. | Used to match with CSO Business Register and to assist with identifying business parks where data centres are located. |