UC8
Participation in explicit Demand Response schemes
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 | Component Layer, Communication Layer/ DER, Customer Premises/ Building, Operation, | UC8 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|
| 1 | 2021-04-27T00:00:00 | CERTH, | First proposal of use case | Draft |
1.3. Scope and Objectives of Use Case
| |
|---|
| Scope | Establish the most appropriate sequence of actions and collaboration among the available tools, in order at both end-user level and Energy Community (LEC) Level to participate in an explicit DR event, based on flexibility potential |
| Objective(s) | 1. Provide optimal solutions at LEC Level, according to the agreed role, i.e. Aggregator, Retailer, ESCO, and based on inputs such as demand/generation flexibility, forecast etc. |
| 2. Provide optimal solutions at end-user level, according to the agreed role of LEC, i.e. Aggregator, Retailer, ESCO, and based on inputs such as demand/generation flexibility, forecast of the particular end-user, in order for the latter to accept or reject any DR events that are offered to him/her. | |
| Related business case(s) | UC01 “Monitoring and Visualization of Metering & Sensor Energy Data in community buildings” |
| UC03 “Consumer demand-side flexibility forecasting” | |
| UC04 “Demand elasticity profiling-forecasting-aggregation” | |
| UC05 “Intra-Day district Level DER flexibility management for community self-balancing” | |
| UC06 “Day-ahead smart charging flexibility quantification via EV usage pattern profiling and forecasting” | |
| UC12 “Retailer day-ahead optimal pricing configuration for aggregated portfolio balancing” | |
1.4. Narrative of Use Case
Short description
Provide DR events at both LEC Level and end-user level, in order to provide appropriate services to the electricity market
Complete description
Regardless of their role, that is ESCO, Retailer or Aggregator, LECs can provide valuable services to both the electricity market and the local DSO, if so requested. Utilizing the appropriate assets available at the moment, their potential and forecast, the decision support system can provide the available option to the Local Energy community manager, and he/she can decide upon the appropriate course of action. This decision will trigger to send the appropriate DR signals to the assets available at that time. These assets can range from a local PV plant to an appliance connected to the grid. The availability of such assets, along with their rated power, current power, flexibility potential and forecast for that time period should be made aware to the LEC manager, in order to assign the appropriate DR signals to the appropriate assets. The availability of those assets is retrieved via notifying the end-users accordingly and having retrieved their informed consent. To that end an appropriate mathematical formulation of the optimization problem at hand will be shaped and the most suitable optimization techniques will be employed, ranging from mixed-integer linear programming to metaheuristics and robust optimization, depending on the circumstances.
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
| SR-01 | Number of data security incidents | None | None, |
1.6. Use case conditions
| Relation to other use cases |
|---|
|
| Level of depth |
| Prioritisation |
| High |
| Generic, regional or national relation |
| Regional |
| Nature of the use cases |
| Prosumer/End-User and Local Energy Community in all its roles (ESCO, Retailer, Aggregator) |
| Further keywords for classification |
| Explicit Demand Response, Aggregator, DER, prosumer, end-user |
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|
| Prosumer/Consumer | Stakeholder | The end user that consumes or produces also in the case of the prosumer | |
| Building/district Manager | Stakeholder | Person who manages property or district assets, usually not the end user of electricity but is responsible for billing and maintenance. | |
| LEC manager (Aggregator, Retailer, ESCO) | Stakeholder | Person who manages the whole LEC ecosystem | |
| Aggregator, DSO | Stakeholder | External Actor to the LEC strict ecosystem | |
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 |
|---|
| S01 | Receive DR request | None | | Receive DR request | | |
| S02 | Provide DR | None | | Provide DR | | |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Receive DR request |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|
| Req_ID | Req_Name | ‘Participation in explicit Demand Response schemes’ | |
| Identifier | Name | Description | mRID |
|---|
| INF01 | No. DR Events | | |
| (integer) | Number of DR events requested for the upcoming period | INF01 | |
| INF02 | DR duration | | |
| (float) | The duration of the DR events requested for the upcoming period | INF02 | |
| INF03 | Energy increase/decrease | | |
| (float) | The amount of energy to be in-/de-creased during the DR event | INF03 | |
| INF04 | End user preferences | | |
| (string) | Any specific preferences the end user may pertaining the DR events, such as, preferred period for participating in a DR event, preferred appliances for engaging in a DR event (e.g. washing machine, clothe dryer etc.), his/her availability for participating in DR events for the upcoming period, etc. | INF04 | |
| INF05 | End user energy consumption profile | | |
| (timeseries) | Forecast for the end user energy consumption baseline and upper/lower boundaries. | INF05 | |
| INF06 | End user DR engagement profile (float) | A metric of how actively or non-actively engaged is the end user regarding DR events. | INF06 |
| INF07 | timestamp | A time instant, which the DR event is to start/end. | INF07 |
| INF08 | DR control signal | An appropriate DR signal to be sent to a particular device, in order to in-/de-crease | INF08 |
7. Common Terms and Definitions
| Key | Value | Refers to Section |
|---|