elering-2
Anonymize energy data
1. Description of the Use Case
1.1. Name of the Use Case
| ID | Area /Domain(s)/Zone(s) | Name of the Use Case |
|---|
| 1 | Access to data, Market for flexibilities, Services related to end customers, | elering-2 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|
| 1 | 2018-04-12T00:00:00 | Kalle Kukk (Elering), | | |
| 2 | 2018-10-03T00:00:00 | Ricardo Jover (EDF), | UML model | |
| 3 | 2018-10-04T00:00:00 | Eric Suignard (EDF), | Version post WP5&9 physical meeting in Tallinn | |
| 4 | 2018-10-11T00:00:00 | Ricardo Jover (EDF), | Assumptions concerning users of the Application | |
| 5 | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 6 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review | |
1.3. Scope and Objectives of Use Case
| |
|---|
| Scope | Anonymization of personally identifiable data. |
| Objective(s) | Making private data available to other parties without authorization (permission) using anonymization techniques |
| Related business case(s) | |
1.4. Narrative of Use Case
Short description
Private data without identifying the person behind may be useful for some applications and services – e.g. for academic studies, benchmarking, reporting, etc. Using techniques to anonymize data makes access to data easier for these parties as no consent is needed from every individual consumer.
Complete description
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| Application and Data Hub have a prior agreement to exchange anonymized data or there is legal requirement for Data Hub to make certain anonymized data available |
| Prerequisites |
|---|
| Standard anonymization technique |
| Relation to other use cases |
|---|
|
| Level of depth |
| Prioritisation |
|
| Generic, regional or national relation |
|
| Nature of the use cases |
| SUC |
| Further keywords for classification |
|
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|
| Data Exchange Platform | System | Data exchange platform (DEP) is a communication platform the basic functionality of which is to secure data transfer (routing) from data providers (e.g. data hubs, flexibility service providers, TSOs, DSOs) to the data users (e.g. TSOs, DSOs, consumers, suppliers, energy service providers). DEP stores data related to its services (e.g. cryptographic hash of the data requested). The DEP does not store core energy data (e.g. meter data, grid data, market data) while these data can be stored by data hubs. Several DEPs may exist in different countries and inside one country. | |
| Data Hub | System | Data Hub is an information system which main functionality is to store and make available measurements (e.g. meter data, operational data) and associated master data. Data Hubs are not necessarily centralized in a country or in a region. | |
| Foreign Customer Portal | System | Customer Portal for another country.
Can also mean a separate portal in the same country. | |
| Application | System | Any kind of system connected to a Data Exchange Platform and used by a market participant who wishes to receive data. | |
| Data Hub Operator | Business | Data hub operator owns and operates an information system which main functionality is to store and make available electricity (also gas, heat) metering data and associated master data. Can be :
- Grid Data Hub Operator in the sphere of a System Operator
- Market Data Hub Operator in the sphere of a Market Operator
- Meter Data Hub Operator in the sphere of a Metered Data Operator
- Sub-meter Data Hub Operator in the sphere of an Energy Service Provider
| |
| DEP Operator | Business | Data exchange platform operator owns and operates a communication system which basic functionality is data transfer. | |
3.2. References
| No. | References Type | Reference | Status | Impact on Use Case | Organistaor / Organisation | Link |
|---|
4. Step by Step Analysis of Use Case
4.1. Overview of Scenarios
| No. | Scenario Name | Scenario Description | Primary Actor | Triggering Event | Pre-Condition | Post-Condition |
|---|
| 1 | Anonymize private data | | | | | |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Anonymize private data |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| 1.1 | | Anonymizes data | | | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | | | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| 1.2 | | Forwards anonymized data | | | 5351ac19-9ec2-47b9-9ead-4a28907df045 | | | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| 1.3 | | Forwards anonymized data | | | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | | | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| 1.4 | | Forwards anonymized data request |
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
| | 5351ac19-9ec2-47b9-9ead-4a28907df045 | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| 1.5 | | Forwards anonymized data request |
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
| | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| 1.6 | | Requests anonymized data |
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
| | 3b6d4cd1-7cd7-473e-af25-2cd3f990d415 | 5351ac19-9ec2-47b9-9ead-4a28907df045 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| 1.7 | | Sends anonymized data | | | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | | | e36aee2c-29d8-4331-b123-07eeafb6c6d9 73a08640-6aaa-4f28-9f05-92891fd0b16c 8457ec5f-579f-40ac-8536-437237c3d919 e3e7f71d-88e9-413a-960f-4400c9cd2bef |
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|
| 97336539-bfa7-4501-b370-ff9d6d4bf681 | Any Data | | —- |
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|
| Cat1 | Task 5.3 | Requirements integrated from Task 5.3. | 1880e39c-7084-4785-8c02-297057abe312 |
| Identifier | Name | Description | mRID |
|---|
| Req1 | ANO-ED-REQ-3 | Data source (e.g. meter data hub) ability to anonymize data | e36aee2c-29d8-4331-b123-07eeafb6c6d9 |
| Req2 | ANO-ED-REQ-4 | DEP ability to forward anonymized data from a data source to a data user | 73a08640-6aaa-4f28-9f05-92891fd0b16c |
| Req3 | ANO-ED-REQ-1 | Standard rules to anonymize data not to enable the identification of persons behind data | 8457ec5f-579f-40ac-8536-437237c3d919 |
| Req4 | ANO-ED-REQ-2 | Standard rules to anonymize data in order to ensure the comparability of anonymized data sets | e3e7f71d-88e9-413a-960f-4400c9cd2bef |
7. Common Terms and Definitions
| Key | Value | Refers to Section |
|---|