elering-14
Manage sub-meter 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, Operational planning and forecasting, Services related to end customers, | elering-14 |
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-05-07T00:00:00 | Kalle Kukk (Elering), Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 3 | 2018-08-11T00:00:00 | Kalle Kukk (Elering), Graham Oakes (Upside), Mitchell Curtis (Upside), | ||
| 4 | 2018-05-17T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 5 | 2018-05-25T00:00:00 | Kalle Kukk (Elering), Olav Rossøy (Enoco), | ||
| 6 | 2018-06-06T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 7 | 2018-08-02T00:00:00 | Eric Suignard (EDF), | ||
| 8 | 2018-09-21T00:00:00 | Eric Suignard (EDF), Ricardo Jover (EDF), | Remarks from Innogy, Elering and EirGrid. | |
| 9 | 2018-10-04T00:00:00 | Eric Suignard (EDF), | Version post WP5&9 physical meeting in Tallinn | |
| 10 | 2018-10-17T00:00:00 | Eric Suignard (EDF), | Version reviewed by WP5&9 partners | |
| 11 | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 12 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review |
1.3. Scope and Objectives of Use Case
| Scope | Using data exchange platform for exchanging sub-meter data. A sub-meter data is a data measured by a non-revenue grade meter and related to tariffs. |
| Objective(s) | Support easy access to sub-meter data |
| Related business case(s) |
1.4. Narrative of Use Case
Short description
Communication with different energy consuming and producing devices should be enabled in an organized way to satisfy the needs of different stakeholders. Customers need to monitor and control their devices. Flexibility service providers (flexibility aggregators) and other energy service providers need access for service provision based on these devices. TSOs and DSOs need information for flexibility settlement.
Complete description
1.5. Key Performance Indicatiors (KPI)
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| Every individual and organization has the right to make the decisions regarding the data of their devices, incl. easy access to these data by themselves and granting access to third parties. |
| Prerequisites |
|---|
| Sub-meter data operator is needed. |
1.7. Further information to the use case for classification/mapping
| Relation to other use cases |
|---|
| Level of depth |
| Prioritisation |
| Generic, regional or national relation |
| Nature of the use cases |
| SUC |
| Further keywords for classification |
1.8. General remarks
| General remarks |
|---|
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|---|---|---|
| Customer | Business | Consumer, generator or storage facility owner. | |
| Sub-Meter Data Collection Tool | System | Sub-Meter Data Collection Tool is an information system which main functionality is to collect measurements from In-House Devices. Data is published to Sub-Meter Data Collection Tool, not requested by the tool. | |
| 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. | |
| Automation Controller | System | Automation Controller is an information system which main functionality is to send activation signals to In-House Devices. | |
| In-House Device | System | Any kind of electrical device installed at a customer’s location. E.g. heat pump, water boiler, EV charger. | |
| 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. | |
| Flexibility Service Provider | Business | Can be a Distribution Network Flexibility Provider or a Transmission Network Flexibility Provider (cf. definitions in T3.3 deliverable). Similar to Flexibility Aggregator. Can be both aggregator and individual consumer/generator. Type of Energy Service Provider. | |
| Energy Service Provider | Business | A party offering energy-related services to any other party (adapted from ENTSOE-EFET-ebIX harmonized role model). Energy service provider (ESCO – energy service company) is a market-based role which is responsible for delivering energy services to the customers (or to other parties of behalf of the customers). In case these services necessitate the access to customer’s data, the consent of this customer is required. Examples of the executors of this role include aggregator, flexibility service provider, energy efficiency provider, energy monitoring provider. Can also be an Aggregator or a Generator (cf. definitions in T3.3 deliverable). | |
| 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 :
| |
| 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 | Collect sub-meter data | |||||
| 2 | Ensure data collection from sub-meter level devices to be made available over DEP | |||||
| 3 | Enable sending control signals to devices over DEP |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Collect sub-meter 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 | Send sub-meter data | Modsarus Use Case::InstanceName=Sub-Meter Data Modsarus Use Case::InstanceDescription= | 7f424812-b086-4dc4-be53-b79b2acbec68 | 6d6da729-6f3c-49f4-ac5b-8834147a20a8 | 4bb24bb0-7f1f-419d-a6a2-c15c8cd3557f | 6b0fd1d1-63a7-4e3e-a987-f19ef3e82850 82a2cdb6-181d-4091-a640-794ce6ccb8a8 | ||
| 1.2 | Check sub-meter data quality | Modsarus Use Case::InstanceName=Sub-Meter Data Modsarus Use Case::InstanceDescription= | 6d6da729-6f3c-49f4-ac5b-8834147a20a8 | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 4bb24bb0-7f1f-419d-a6a2-c15c8cd3557f | 6b0fd1d1-63a7-4e3e-a987-f19ef3e82850 82a2cdb6-181d-4091-a640-794ce6ccb8a8 | ||
| 1.3 | Store sub-meter data | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 6b0fd1d1-63a7-4e3e-a987-f19ef3e82850 82a2cdb6-181d-4091-a640-794ce6ccb8a8 |
| Scenario Name: |
|---|
| Ensure data collection from sub-meter level devices to be made available over DEP |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|---|---|---|---|---|---|---|---|
| 2.1 | Forward sub-meter data | Modsarus Use Case::InstanceName=Sub-Meter Data Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 cd408e86-b417-4753-9694-7e517e2d852a | 4bb24bb0-7f1f-419d-a6a2-c15c8cd3557f | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | ||
| 2.2 | Process data request | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | |||||
| 2.3 | Receive sub-meter data | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | |||||
| 2.4 | Receive sub-meter data | cd408e86-b417-4753-9694-7e517e2d852a | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | |||||
| 2.5 | Request specific consumption or generation data of devices | Modsarus Use Case::InstanceName=Request on Sub-Meter Data Modsarus Use Case::InstanceDescription= | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 90883b6f-5b55-41d2-b437-0f3b354fa345 | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | ||
| 2.6 | Request specific consumption or generation data of devices | Modsarus Use Case::InstanceName=Request on Sub-Meter Data Modsarus Use Case::InstanceDescription= | cd408e86-b417-4753-9694-7e517e2d852a | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 90883b6f-5b55-41d2-b437-0f3b354fa345 | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | ||
| 2.7 | Check existence of valid consent | Modsarus Use Case::InstanceName=Customer Consent Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | bbac2544-418c-4356-b574-c4b6bf048588 | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | ||
| 2.8 | Forward request on sub-meter data | Modsarus Use Case::InstanceName=Request on Sub-Meter Data Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 90883b6f-5b55-41d2-b437-0f3b354fa345 | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd | ||
| 2.9 | Send sub-meter data | Modsarus Use Case::InstanceName=Sub-Meter Data Modsarus Use Case::InstanceDescription= | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 4bb24bb0-7f1f-419d-a6a2-c15c8cd3557f | 595982bc-539c-4bc9-9e6d-f025a932c60a 4a886828-21d2-4e11-ae98-a7d6ca505cb9 2532dcb1-85fa-4cbe-baf5-c777cff73215 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 7031117d-1837-4c9a-badc-c13ea831acaf f85ceac5-708f-4b4c-94af-5749149a676e 7387fec5-9fed-4842-ba6b-54843d92873d dc149914-c8cd-43c3-ab32-65bbd30a3ce2 e07bb719-575d-4c26-aaa3-6a40c8ecdf63 426c7705-9872-4475-87ff-0887cff16879 0762ff37-9e63-405d-b133-4c3c6d4981dd |
| Scenario Name: |
|---|
| Enable sending control signals to devices over DEP |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|---|---|---|---|---|---|---|---|
| 3.1 | Send activation order | Customer (consumer/generator) can order directly the Sub-Meter Data Operator to activate his/her devices. Modsarus Use Case::InstanceName=Control Signal Modsarus Use Case::InstanceDescription= | cd408e86-b417-4753-9694-7e517e2d852a | 0d0473c7-bfd2-4750-91ee-4c1453277b1e 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | c2c65024-04a2-4643-9c45-ac85151b327e | 2532dcb1-85fa-4cbe-baf5-c777cff73215 | ||
| 3.2 | Send activation order | An activation order can be sent by Energy Service Provider to Sub-Meter Data Operator (operating Automation Controller), based on the defined coordination mechanisms and TSO’s or DSO’s request to activate some flexibility. Modsarus Use Case::InstanceName=Control Signal Modsarus Use Case::InstanceDescription= | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | c2c65024-04a2-4643-9c45-ac85151b327e | 2532dcb1-85fa-4cbe-baf5-c777cff73215 | ||
| 3.3 | Check existence of valid consent | Modsarus Use Case::InstanceName=Customer consent Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | bbac2544-418c-4356-b574-c4b6bf048588 | 2532dcb1-85fa-4cbe-baf5-c777cff73215 | ||
| 3.4 | Forward control signal | Modsarus Use Case::InstanceName=Control Signal Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 0d0473c7-bfd2-4750-91ee-4c1453277b1e | c2c65024-04a2-4643-9c45-ac85151b327e | 2532dcb1-85fa-4cbe-baf5-c777cff73215 | ||
| 3.5 | Send control signal | Modsarus Use Case::InstanceName=Control Signal Modsarus Use Case::InstanceDescription= | 0d0473c7-bfd2-4750-91ee-4c1453277b1e | 7f424812-b086-4dc4-be53-b79b2acbec68 | c2c65024-04a2-4643-9c45-ac85151b327e | 2532dcb1-85fa-4cbe-baf5-c777cff73215 |
5. Information Exchanged
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|---|---|---|
| 4bb24bb0-7f1f-419d-a6a2-c15c8cd3557f | Sub-Meter Data | Time resolution:1 second. Content: energy, active power, reactive power, time-stamp, sub-meter ID, type of device behind the sub-meter (e.g. car charger, heating facility), energy flow direction (generation or consumption). | —- |
| 90883b6f-5b55-41d2-b437-0f3b354fa345 | Request on Sub-Meter Data | —- | |
| bbac2544-418c-4356-b574-c4b6bf048588 | Customer Consent | —- | |
| c2c65024-04a2-4643-9c45-ac85151b327e | Control Signal | —- |
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 | SUBMET-REQ1 | Collection of data from sub-meters | 6b0fd1d1-63a7-4e3e-a987-f19ef3e82850 |
| Req2 | SUBMET-REQ3 | Storing sub-meter data in a data hub | 82a2cdb6-181d-4091-a640-794ce6ccb8a8 |
| Req9 | SUBMET-REQ5 | Transmission protocols of sub-metering | 7387fec5-9fed-4842-ba6b-54843d92873d |
| Req10 | SUBMET-REQ7 | Ability of DEP to forward activation orders from a customer (data owner) or application (energy service provider) to devices | dc149914-c8cd-43c3-ab32-65bbd30a3ce2 |
| Req11 | SUBMET-REQ2 | Ability of DEP to forward sub-meter data from data hub to customer (data owner) and application (energy service provider) | e07bb719-575d-4c26-aaa3-6a40c8ecdf63 |
| Req12 | SUBMET-REQ4 | Data format of sub-metering | 426c7705-9872-4475-87ff-0887cff16879 |
| Req13 | SUBMET-REQ6 | SLA between customer and energy service provider | 0762ff37-9e63-405d-b133-4c3c6d4981dd |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat2 | Functional | Functional requirements | 59e7899c-d9ee-4534-81a6-81b37dce5e81 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req3 | Sub-Meter Collection Tool collects data from devices | Data is published to Sub-Meter Collection Tool, not requested by it. <br/>Sub-Meter Data Collection Tool checks quality of received data: check within the scope of the device, e.g. that data packets are well formed and within reasonable bounds for the device, and across multiple devices, e.g. that readings from sub-meters are consistent with the aggregate reading from the main meter in the location. This quality check is very dependent on the geometry/setup of the sub meters (sub-meters of sub-meters, generated power, thermal energy…). Validation is therefore highly application/use case specific.<br/>Then, Sub-Meter Collection Tool sends data to Data Hub for storing. | 595982bc-539c-4bc9-9e6d-f025a932c60a |
| Req5 | Data Hub is used by Sub-Meter Data Operators | 2532dcb1-85fa-4cbe-baf5-c777cff73215 |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat3 | Performance | b50a27e2-b8b9-4aaa-947a-a459914dbda5 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req4 | Sub-meter data must be available up to one second later after reception | 4a886828-21d2-4e11-ae98-a7d6ca505cb9 |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req6 | Data format for sub-metering: JSON, RFC8259/ECMA404. | 6bdb83c1-a2dd-4591-8fd2-3dfb567d4883 | |
| Req7 | Transmission protocols for sub-metering: MQTT, ISO/IEC PRF 20922, TLS, RFC6176 | 7031117d-1837-4c9a-badc-c13ea831acaf | |
| Req8 | Terms of conditions to be agreed between customer and energy service provider – specify which data from which devices to be exchanged, which granularity (e.g. hourly, 1 second), when available (e.g. once a day, very close to real time), etc | f85ceac5-708f-4b4c-94af-5749149a676e |
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|