elering-16
Provide list of suppliers and ESCOs
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 | Market for flexibilities, Services related to end customers, Access to data, | elering-16 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|---|---|---|---|
| 1 | 2018-04-12T00:00:00 | Richárd Balog (Mavir), | ||
| 2 | 2018-07-11T00:00:00 | Florentin Dam (AKKA), | UML modeling | |
| 3 | 2018-07-19T00:00:00 | Florentin Dam (AKKA), | Fusion of the two initial scenarios Added a new scenario | |
| 4 | 2018-07-23T00:00:00 | Florentin Dam (AKKA), | Added the detailed activities for the second scenario | |
| 5 | 2018-07-25T00:00:00 | Florentin Dam (AKKA), | Added details on the two scenarios, scope and prerequisite | |
| 6 | 2018-08-02T00:00:00 | Eric Suignard (EDF), | ||
| 7 | 2018-09-21T00:00:00 | Eric Suignard (EDF), | ||
| 8 | 2018-10-04T00:00:00 | Eric Suignard (EDF), | Version post WP5&9 physical meeting in Tallinn | |
| 9 | 2018-10-17T00:00:00 | Eric Suignard (EDF), | Version reviewed by WP5&9 partners | |
| 10 | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 11 | 2019-06-13T00:00:00 | Eric Suignard (EDF), | Elering review | |
| 12 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review |
1.3. Scope and Objectives of Use Case
| Scope | Set up, store and share the list of suppliers and service providers. |
| Objective(s) | To make available the list of suppliers and service providers |
| Related business case(s) |
1.4. Narrative of Use Case
Short description
- Set up and share the list of suppliers and service providers to be made available through a data exchange platform for the interested parties. The list is available for authorised parties who can get in contact with suppliers and service provider for any kind of business purpose.
2) Set up and share the list of aggregators to be made available through a flexibility platform for the individual Flexibility Service Providers. Individual Flexibility Service Providers can contact the aggregators in the list and find a suitable one.
Complete description
1.5. Key Performance Indicatiors (KPI)
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| The communication channel is protected |
| Prerequisites |
|---|
| The user has to authenticate in order to be able to see the list in the flexibility platform. |
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 |
|---|---|---|---|
| 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. | |
| Aggregator | Business | Aggregate and maximise value of portfolio(s) of resources (cf. definition in T3.3 deliverable). | |
| Data User | Business | Any person who uses data. Can be a Data Owner or a Data Delegated Third party. | |
| 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). | |
| Flexibility Platform | System | Flexibility Platform (FP) for System Operators and Flexibility Service Providers that enables the trading of different flexibility products and services. A FP is operated by a Market Operator. Available to System Operators and Flexibility Services Providers. It is used to support the prequalification, the bidding, the activation and the verification processes, ensuring coordination between activities undertaken by several operators using the same flexible resources. Several national and regional FPs may exist. | |
| 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 | Registration on the Data Exchange Platform with verification | A supplier or service provider register to use data exchange platform | ||||
| 2 | Presenting the list of aggregators on flexibility platform |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Registration on the Data Exchange Platform with verification |
| 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 | Fill in a registration form | 4c6daeab-d76a-411a-b30e-b78cd5094b54 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 1.2 | Upload necessary documents | Modsarus Use Case::InstanceName=ESCO information Modsarus Use Case::InstanceDescription= | 4c6daeab-d76a-411a-b30e-b78cd5094b54 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 65fdb554-4b6f-4d8f-9034-e1c53eef2a88 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | ||
| 1.3 | Generate user account with all details | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 1.4 | Send account, usage and authentication information | Modsarus Use Case::InstanceName=Authenticate Information Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 4c6daeab-d76a-411a-b30e-b78cd5094b54 | 79077332-56bd-437e-8295-63b9a9dab5bd | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | ||
| 1.5 | Send a notification of refusal to the ESCO | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 1.6 | Send a notification of acceptance to the ESCO | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 1.7 | Add the ESCO in the list in the DEP of its country | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 1.8 | Add the ESCO in the list in the DEP of other countries too | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 1.9 | Make the new Energy Service Provider accessible in the list of suppliers and ESCOs. | f3850003-cd20-463b-891f-a2ab28c75bb1 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 |
| Scenario Name: |
|---|
| Presenting the list of aggregators on flexibility platform |
| 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 | Request for being listed in the platform | Modsarus Use Case::InstanceName=Aggregator information Modsarus Use Case::InstanceDescription= | b6fabe30-8a3f-459b-a964-c6bfd75fce83 | 908bfa7a-c616-4b2b-a712-04aac115429b | 13fa3203-6c24-47ca-904c-34647b438bb4 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | ||
| 2.2 | Request for being listed in the platform | b6fabe30-8a3f-459b-a964-c6bfd75fce83 | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 2.3 | Review the request | 908bfa7a-c616-4b2b-a712-04aac115429b | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 2.4 | Send a notification of refusal to the aggregator | 908bfa7a-c616-4b2b-a712-04aac115429b | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 | |||||
| 2.5 | Include the aggregator in the list and send notification of acceptance | 908bfa7a-c616-4b2b-a712-04aac115429b | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 |
5. Information Exchanged
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|---|---|---|
| 65fdb554-4b6f-4d8f-9034-e1c53eef2a88 | ESCO information | —- | |
| 79077332-56bd-437e-8295-63b9a9dab5bd | Authenticate Information | —- | |
| 13fa3203-6c24-47ca-904c-34647b438bb4 | Aggregator information | —- |
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 | ESCO-REQ1 | List of suppliers and ESCOs is available through DEP; List of aggregators is available through flexibility platform additionally | 540a5c74-d66e-4dcf-95e0-d01d365a42d0 |
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|