RES scheduling control

1. Description of the Use Case

1.1. Name of the Use Case

IDArea /Domain(s)/Zone(s)Name of the Use Case

1.2. Version Management

Version No.DateName of author(s)ChangesApproval status
12020-07-27T00:00:00ETRA,First versionfinal

1.3. Scope and Objectives of Use Case

ScopeGRIDFLEX, X-FLEX Platform
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

1.5. Key Performance Indicatiors (KPI)

IDNameDescriptionReference to mentioned use case objectives

1.6. Use case conditions


1.7. Further information to the use case for classification/mapping

Relation to other use cases
Level of depth
Generic, regional or national relation
Nature of the use cases
Further keywords for classification

1.8. General remarks

General remarks

2. Diagrams of Use Case

3. Technical Details

3.1. Actors

Actor NameActor TypeActor DescriptionFurther information specific to this Use Case

3.2. References

No.References TypeReferenceStatusImpact on Use CaseOrganistaor / OrganisationLink

4. Step by Step Analysis of Use Case

4.1. Overview of Scenarios

No.Scenario NameScenario DescriptionPrimary ActorTriggering EventPre-ConditionPost-Condition
1Main pathNoneMain path
2Exception path 1NoneException path 1


4.2. Steps – Scenarios

Scenario Name:
Main path
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
1Overall demand estimationNoneGrid measurements are used to es-timate an overall demand indicator (in terms of active power) for current time slotNone
2Production estimationNoneMeasurements from RES units are combined to calculate an overall production indicator (in terms of ac-tive power)None
3Demand forecastNoneOverall demand for the near future is calculated.None
4Production forecastNoneOverall production for the near fu-ture is calculated.None
5Optimization of storage units operationNoneOverall demand and production forecasts are combined with current storage units status to calculate the optimum schedule of those units for the next hours.None
6Validation of optimum scheduleNoneGiven the optimum schedule of the storage units, congestion in the next hours is assessed (trigger for UC 2.9).None
7Execution of optimum scheduleNoneThe 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/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
6Congestion detectedNoneIf the schedule cannot be approved due to an associated congestion, UC 2.11 is triggered.None

5. Information Exchanged

Information exchanged IDName of InformationDescription of Information ExchangedRequirement

6. Requirements (optional)

Category IdentifierNameDescriptionmRID
Req_IDReq_Name‘RES scheduling control’

7. Common Terms and Definitions

8. Custom Information (optional)

KeyValueRefers to Section