Sweden
Congestion management - Distributed Market Model
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 | Regional / local, | Sweden |
1.2. Version Management
Version No. | Date | Name of author(s) | Changes | Approval status |
---|
1 | 2019-07-23T00:00:00 | Vattenfall, | none | approved |
1.3. Scope and Objectives of Use Case
| |
---|
Scope | This BUC describes the actions that are carried out in case of congestions in the low voltage as well as medium voltage distribution grid using a peer to peer market. |
Objective(s) | • Local and regional DSOs want to give customers opportunity to optimize their resources |
• Local and regional DSOs meets grid needs with a market opportunity | |
• In addition, the flexibility provider wants to meet financial goals | |
Related business case(s) | n/a |
1.4. Narrative of Use Case
Short description
mitigate congestion at distribution level
Complete description
The BUC describes the steps that are followed to eliminate congestions in low-voltage and medium-voltage distribution system using flexiility provided by resources connected to both systems.
ID | Name | Description | Reference to mentioned use case objectives |
---|
23 | Cost of R&I solution VS grid alternative solution | Cost of R&I solution VS grid alternative solution | BUC SE-1b, |
1.6. Use case conditions
Relation to other use cases |
---|
|
Level of depth |
Prioritisation |
nice to have |
Generic, regional or national relation |
national |
Nature of the use cases |
business |
Further keywords for classification |
n/a |
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
---|
DSO | ENTSO-E | None | |
FPS | None | None | |
3.2. References
No. | References Type | Reference | Status | Impact on Use Case | Organistaor / Organisation | Link |
---|
| no reference has been used | none | n/a | n/a | | n/a |
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 | Long term process | Coordinet platform and functionalities interaction in national energy market | | Long term process | | |
Notes
4.2. Steps – Scenarios
Scenario Name: |
---|
Long term process |
Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
---|
1 | Flexibility needs to be exchanged in the day-ahead | Flexibility bids | Cooridnet receive bids (buy/sell) from FPS through DSOs, | get | FPS | DSO | | |
2 | Coordinet settles flexibility | Confirmation of the flexibility bids | Bids settlment by Coordinet platform (first come first serve), that communicates results to FPS | get | | FPS DSO | | |
3 | bids accepted | P2P market clearance | P2P market is cleared in a distributed manner by Coordinet platform | create | | FPS DSO | | |
Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
---|
6. Requirements (optional)
Category Identifier | Name | Description | mRID |
---|
Req_ID | Req_Name | ‘Congestion management - Distributed Market Model’ | |
Identifier | Name | Description | mRID |
---|
n/a | n/a | n/a | n/a |
7. Common Terms and Definitions
Key | Value | Refers to Section |
---|