Redispatch 2.0
for plant operators
As a plant operator, we support you in the implementation of Redispatch 2.0
Since October 1, 2021, new regulations for grid congestion management have been introduced in Germany as part of the Grid Expansion Acceleration Act (NABEG): the so-called Redispatch 2.0 procedure.
However, the originally planned implementation on 1.10.2021 to the new Redispatch 2.0 procedure has been delayed, so that the balance sheet compensation for redispatch measures is currently not yet provided by the network operators across the board.
Obligations for plant operators in redispatch 2.0
Redispatch 2.0 fundamentally changes the market processes. Renewable energy plants are now fully integrated into the redispatch process. Compared to the previous feed-in management, the plant operator must now make more decisions and report information.
We will be happy to support you in your preparations and, if required, take over all your additional processes.
This is what plant operators must do for their plants
- Clarification of TR and SR IDs (technical resource ID and controllable resource ID).
- Determination of the person in charge of the operation (EIV)
- Determination of the operator of a technical resource (BTR)
- Assignment to a balancing model (forecast or planned value model)
- Determination of the billing variant for the outage work
- Determination of the call-off variant (acquiescence or request case)
Market roles in redispatch 2.0
As a plant operator, you can assign all essential obligations to us. You can designate us as your deployment manager (EIV) and we will also be happy to take on the role of technical resource operator (BTR) for you.
The Operations Officer (EIV)
For each of your solar and wind parks, you must name an EIV to the connection network operator, who will make the necessary data reports.
Since this obligation is closely linked to the electricity marketing processes, it is a good idea for us, as your direct marketer, to assume the role of EIV for you.
As EIV, we check your controllable resource IDs (SR-IDs) assigned to your plants and report your balancing model, call-off variant and billing procedure to the connection network operator. We build the interface to the DataProvider RAIDA/Connect+ or to other systems of the network operators and operate the interface.
In addition, we generate various data and report these within specified deadlines and in compliance with certain processes via the connect+ data exchange platform.
As EIV, we take over for you
- the transmission of master data,
- the transmission of non-utilization data,
- the transmission of planning data (in the planned value model) and
- the implementation of control in the event of a call.
The operator of a technical resource (BTR)
The second role relevant to plant operators is that of BTR.
As BTR we take over for you:
- the transmission of meteorological ex-post data (peak procedure),
- the determination and reconciliation of billing-relevant outage work, and
- the provision of real-time data.
- The handling of all market communication processes via EDIFACT.
Keep track of this data
What is the next step with Redispatch 2.0?
We expect the status quo to remain in place for some time, as it will take some time to resolve all operational difficulties with Redispatch 2.0.
In the meantime, we will continue to provide balance sheet compensation for installations for which this is not currently provided.
Did you already know?
Redispatch 2.0 aims to reduce the costs of network security measures and to further increase the predictability of measures and associated processes. The introduction of a more comprehensive, plan-based process is intended to further increase network security. The inclusion of all controllable generation plants with an output of 100 kW or more will make it possible to solve grid bottlenecks more efficiently and proactively across all grid levels in the future.
Redispatch 2.0 includes all conventional generation plants, CHP plants, renewable energy plants and storage systems with an output of 100 kW or more, as well as plants that can be permanently controlled by a grid operator.
In general, the plant operator must be able to provide data (master data, planning data and non-usability as well as real-time data for dimensioning Redispatch 2.0 measures) and be able to calculate the billing-relevant downtime for billing purposes. The plant operator can take on the role of the person in charge of operations (EIV) himself or outsource essential tasks to a service provider.
The planning data must be reported to the network operators two days in advance ("D-2 14:30"). The planning data is updated one day in advance ("D-1 14:30"). Further changes to the planning data must be reported until physical delivery.
The postal distribution center is the DataProvider for the transmission of master data, planning data and non-usability to the network operators.
No, real-time data is not exchanged "file-based" and therefore cannot be exchanged via the mail distribution center.
The legislator adopted the new requirements for the management of grid congestion through an amendment to the Grid Expansion Acceleration Act (NABEG) on 13 May 2019. In concrete terms, the rules are implemented by further specifications of the BNetzA (ordinances), which are based on an industry proposal of the BDEW.
During the transitional solution, the balancing group managers will continue to take over the procurement of the shortfalls in the amount of the downtime, which are later to be provided by the network operators as balance sheet compensation. Legally, the direct marketers act according to the management without a mandate. During the transitional solution, the balance sheet compensation for grid security measures is reduced to 0 MWh. Instead, balancing group managers receive financial compensation in the form of a mixed price, which is made up of 72.5% of the ID1 and 27.5% of the reBAP (cross-control area balancing energy price). From the first March 1, 2022, a three-month parallel test phase will begin, which should enable the timely and safe implementation of the processes associated with Redispatch 2.0.
