EACL-HU-02

HV/MV transformer overload

1. Description of the Use Case

1.1. Name of the Use Case

IDArea /Domain(s)/Zone(s)Name of the Use Case
1Hungary,EACL-HU-02

1.2. Version Management

Version No.DateName of author(s)ChangesApproval status
32021-08-31T00:00:00Bálint Hartmann,
Péter Sőrés,
Bálint Sinkovics,NoneNone

1.3. Scope and Objectives of Use Case

ScopeIncreasing renewable penetration causes overloading of HV/MV transformers. The main scope of EACL-HU-02 is to mitigate overloading of HV/MV transformers by activating flexibility services.
Objective(s)The objective of the use case is to avoid overloading of HV/MV transformers in all operational states of the power system.
Related business case(s)EACL-HU-01

1.4. Narrative of Use Case

Short description

Need: Due to the proliferation of PV plants, connected to DSO MV lines or directly to the MV side of HV/MV substations, overloading of HV/MV transformers is a forecoming issue in Hungary. This technical issue can be mitigated by P and/or Q on MV level. Service: Overloading issues of HV/MV transformers can be mitigated by P and/or Q injection/consumption on MV level.

Complete description

The BUC operates on two time horizons, each related to the specified grid service: • capacity auction • and energy activation (scheduled), respectively. Capacity auctions will be driven by technical needs of the DSOs, which are determined on a weekly basis based on weekly maintenance plans. Gate opens at W-1 Monday 0:00 and closes at W-1 Friday 14:00, thus enabling bidders a fairly long time to place bids, but the market can be cleared during working hours on W-1. Results of the auction are to be published by W-1 Friday 15:00.

Energy bids can be submitted between W-1 Monday 0:00 and D-1 6:00. The early gate opening supports the procurement of services that are expected to be necessary with probability. The gate closure on D-1 allows SOs to procure services based on day-ahead predictions and network calculations. Results of the clearing are to be published by D-1 7:00, which is 60 minutes ahead of local daily balancing capacity market gate closure, and well before the active period of DAM market bidding. This allows market players to participate on flexibility and day-ahead markets separately, and also supports that uncleared flexibility bids are submitted to shorter horizon markets (DAM, BAM).

1.5. Key Performance Indicatiors (KPI)

IDNameDescriptionReference to mentioned use case objectives
1Number of flexibility service provider assets involved in the serviceThere are different assets in the location with flexibility service provision capabilities, which can contribute to the needs of the DSO. The KPI reflects on the number of assets involved.None,

1.6. Use case conditions

Assumptions
Prerequisites
EACL-HU-02

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
National
Nature of the use cases
Business Use Case
Further keywords for classification
HV/MV transformer, DSO congestion management

1.8. General remarks

General remarks

2. Diagrams of Use Case

EACL-HU-02_scenario1_activities EACL-HU-02_scenario2_activities EACL-HU-02_scenario3_activities EACL-HU-02_scenario4_activities

3. Technical Details

3.1. Actors

Actor NameActor TypeActor DescriptionFurther information specific to this Use Case
DSO• Grid Access Provider
• Data Provider
• System operatorActive actor Responsible for maintaining service quality (e.g. EN 50160) and quantifying flexibility service needs Participates in energy auctions and energy activations
TSO• System Operator
• Data ProviderPassive actor Receives information on capacity auctions and energy activations
FSP• Flexibility/Balancing Service Provider
• Resource aggregator
• Producer / Consumer
• Party connected to the grid
• Flexibility service provider being aggregatorProvides services for the DSO Provides information to the TSO in case of activations through schedules
Market operator• Market operator
• Data Provider
• Merit Order List ResponsibleResponsible for market clearing
OneNet common platform• Flexibility register provider // consent administrator
• TSO-DSO coordinator platform provider // coordinated cap. calculator
• Market interface provider / market information aggregatorResponsible for the necessary TSO-DSO coordination

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
1PrequalificationProduct and grid prequalificationPrequalification
2ForecastingDSO determines the volume and spatial-temporal location of flexibility needsForecasting
3W-1 flexibility procurementCollection of supply bid in the order book, market clearing in W-1W-1 flexibility procurement
4D-1 flexibility procurementCollection of supply bid in the order book, market clearing in D-1D-1 flexibility procurement

Notes

4.2. Steps – Scenarios

Scenario Name:
Prequalification
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
1.1NonePrequalification requestFSP requests prequalificationNoneFSPDSOI-01
1.2NoneProduct and grid prequalificationDSO executes prequalificationNoneDSODSO
1.3NoneApproval of prequalificationDSO informs FSP of the prequalification resultNoneDSOFSPI-02
1.4NonePrequalification resultsPrequalification result is sent to the Market Operator (MO)NoneDSOI-03
Scenario Name:
Forecasting
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
2.1NoneDSO receives data for modelling flexibility needsDSO collects past grid and external forecasting dataNoneDSODSOI-04
2.2NoneDSO determines flexibility needsDSO determines the amount and spatial-temporal location of service needsNoneDSODSO
2.3NoneDSO informs TSO on flexibility needsDSO-TSO data exchangeNoneDSOTSOI-05
2.4NoneDSO delivers flexibility needsDSO informs MO of the flexibility needsNoneDSOI-05
Scenario Name:
W-1 flexibility procurement
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
3.1NoneFlexibility market opening, DSO needs announcedMarket interface announces flexibility needsNoneI-05
3.2NoneFSPs submit bidsFSP submit bids to W-1 & D-1 order bookNoneFSPI-06
3.3NoneW-1 and D-1 FSP bid prequalificationFSP bid prequalification by MONone
3.4NoneFSP bids deliveredFSP bids are submitted to W-1 & D-1 order bookNoneI-06
3.5NoneClearingClearing is executedNone
3.6NoneResults of the clearing are transferred and announcedMarket operator shares clearing result with the market interfaceNoneI-07
Scenario Name:
D-1 flexibility procurement
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
4.1NoneDSO receives data for modelling flexibility needsDSO collects past grid and external forecasting dataNoneDSODSOI-08
4.2NoneDSO determines flexibility needsDSO determines the amount and spatial-temporal location of service needsNoneDSODSO
4.3NoneDSO informs TSO on flexibility needsDSO-TSO data exchangeNoneDSOTSOI-05
4.4NoneDSO delivers flexibility needsDSO informs MO of the flexibility needsNoneDSOI-05
4.5NoneFlexibility market opening, DSO needs announcedMarket interface announces flexibility needsNoneI-05
4.6NoneFSPs submit bidsFSP submit bids to D-1 order bookNoneFSPI-06
4.7NoneD-1 FSP bid prequalificationFSP bid prequalification by MONone
4.8NoneFSP bids deliveredFSP bids are submitted to D-1 order bookNoneI-06
4.9NoneClearingClearing is executedNoneI-07
4.10NoneAnnouncementMarket operator shares clearing result with the market interfaceNone

5. Information Exchanged

Information exchanged IDName of InformationDescription of Information ExchangedRequirement

6. Requirements (optional)

Category IdentifierNameDescriptionmRID
Req_IDReq_Name‘HV/MV transformer overload’
IdentifierNameDescriptionmRID
I-01FSP initialization data for prequalificationType of service unit identifier (name, location, technical parameters)I-01
I-02FSP qualification resultStatus of FSP prequalification (successful/ not successful);I-02
I-03FSP qualification resultLocation identifier and product parameters (ID, POD, P, Q, activation time, sensitivity factor), assignment of FSP to congested substation/MV feederI-03
I-04Historical grid operation dataset for flexibility service need modelling (W-1)Grid condition status and outage from maintenance; Time series data of consumer/prosumer/ producer plans; Historical data for production forecasting (either profile or time series);I-04
I-05Flexibility service needQuantity, type (capacity/activation), bid price, location, timing of demandI-05
I-06FSP supply bidW-1/D-1 priced bid (+additional parameters)I-06
I-07Clearing resultGeneral action (clearing) results; List of accepted bidsI-07
I-08Weather forecast and historical grid operation dataset for flexibility service need modelling (D-1)Weather forecast; Grid condition status and outage from maintenance; Time series data of consumer/ prosumer/ producer plans; Historical data for production forecasting (either profile or time series);I-08

7. Common Terms and Definitions

8. Custom Information (optional)

KeyValueRefers to Section