UC2-4
RES scheduling control
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 | , | UC2-4 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|
| 1 | 2020-07-27T00:00:00 | ETRA, | First version | final |
1.3. Scope and Objectives of Use Case
| |
|---|
| Scope | GRIDFLEX, X-FLEX Platform |
| Objective(s) | |
| Related business case(s) | None |
1.4. Narrative of Use Case
Short description
RES scheduling control
Complete description
Grid operator is able to schedule the operation of its RES, storage assets, etc. to optimize the operation of the grid. This UC is envisioned to deal with assets directly managed by the operator of the grid, while assets from other actors will be indirectly operated through De-mand Side Management (DSM) in UC 2.10 and UC 2.11.
Any microgrid operator will have two simultaneous objectives when managing this kind of assets:
• Keep quality of the supply
• Minimize energy flows in and out of the microgrid (i.e. minimizing dependency on the external network and RES surplus, thus maximizing self-sufficiency)
This use case describes how those assets can be operated in an optimal way, following these assumptions:
• First schedule is optimized energy-wise (maximize self-sufficiency)
• Technical constraints (I or V congestions) coming from that schedule are assessed, which may deviate the original schedule from its optimal
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Relation to other use cases |
|---|
|
| Level of depth |
| Prioritisation |
| High |
| Generic, regional or national relation |
|
| Nature of the use cases |
|
| 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 |
|---|
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 | Main path | None | | Main path | | |
| 2 | Exception path 1 | None | | Exception path 1 | | |
Notes
4.2. Steps – Scenarios
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| 1 | Overall demand estimation | None | Grid measurements are used to es-timate an overall demand indicator (in terms of active power) for current time slot | None | | | | |
| 2 | Production estimation | None | Measurements from RES units are combined to calculate an overall production indicator (in terms of ac-tive power) | None | | | | |
| 3 | Demand forecast | None | Overall demand for the near future is calculated. | None | | | | |
| 4 | Production forecast | None | Overall production for the near fu-ture is calculated. | None | | | | |
| 5 | Optimization of storage units operation | None | Overall demand and production forecasts are combined with current storage units status to calculate the optimum schedule of those units for the next hours. | None | | | | |
| 6 | Validation of optimum schedule | None | Given the optimum schedule of the storage units, congestion in the next hours is assessed (trigger for UC 2.9). | None | | | | |
| 7 | Execution of optimum schedule | None | The new schedule effectively updates the previous one. GRIDFLEX control system triggers required actions on the field assets, following the gener-ated schedule. | None | | | | |
| Scenario Name: |
|---|
| Exception path 1 |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| 6 | Congestion detected | None | If the schedule cannot be approved due to an associated congestion, UC 2.11 is triggered. | None | | | | |
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|
| Req_ID | Req_Name | ‘RES scheduling control’ | |
| Identifier | Name | Description | mRID |
|---|
7. Common Terms and Definitions
| Key | Value | Refers to Section |
|---|