Leading service provider for Transmission System Operators (TSOs) in the European electricity market.

We are pleased to invite you to participate in upcoming LTFBA test sessions scheduled as follows:

• Yearly Auction Test Session (CORE  & Nordic Regions): 9 July 2026
• Monthly Auction Test Session (CORE  & Nordic Regions): 10 July 2026

These sessions are intended to provide Market Participants with the opportunity to:

• Familiarise themselves with the LTFBA auction setup
• Navigate the platform and explore its functionalities
• Submit and manage bids within the tool

Please note that these sessions are dedicated to practical testing within our Auction tool's test environment, allowing participants to actively interact with the system and validate their processes.

Registration

Market Participants interested in joining are kindly requested to register by replying to this email with the following information:

• Company name
• EIC code
• Name of participant(s)
• Email address(es)
• eCAT username(s) (if available)

Further details, including access information and session timelines, will be shared with registered participants ahead of the test dates.

Should you have any questions, please do not hesitate to contact us.
We look forward to your participation.

1. TSO(s)*:

RTE-TSO

2. Identification of affected Long Term Transmission Rights:

ES-FR

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

03-07-2026 00:00 - 01:00 1280 MW

03-07-2026 01:00 - 02:00 1280 MW

03-07-2026 02:00 - 03:00 1280 MW

03-07-2026 03:00 - 04:00 1280 MW

03-07-2026 04:00 - 05:00 1280 MW

03-07-2026 05:00 - 06:00 1280 MW

03-07-2026 07:00 - 08:00 1280 MW

03-07-2026 08:00 - 09:00 1280 MW

03-07-2026 09:00 - 10:00 1280 MW

03-07-2026 10:00 - 11:00 1280 MW

03-07-2026 11:00 - 12:00 1280 MW

03-07-2026 12:00 - 13:00 1280 MW

03-07-2026 13:00 - 14:00 1280 MW

03-07-2026 14:00 - 15:00 1280 MW

03-07-2026 15:00 - 16:00 1280 MW

03-07-2026 16:00 - 17:00 1280 MW

03-07-2026 17:00 - 18:00 1280 MW

03-07-2026 18:00 - 19:00 1280 MW

5. Amount of LTTR remaining after curtailment:

03-07-2026 00:00 - 01:00 919 MW

03-07-2026 01:00 - 02:00 919 MW

03-07-2026 02:00 - 03:00 919 MW

03-07-2026 03:00 - 04:00 919 MW

03-07-2026 04:00 - 05:00 963 MW

03-07-2026 05:00 - 06:00 963 MW

03-07-2026 07:00 - 08:00 460 MW

03-07-2026 08:00 - 09:00 460 MW

03-07-2026 09:00 - 10:00 460 MW

03-07-2026 10:00 - 11:00 460 MW

03-07-2026 11:00 - 12:00 460 MW

03-07-2026 12:00 - 13:00 460 MW

03-07-2026 13:00 - 14:00 460 MW

03-07-2026 14:00 - 15:00 460 MW

03-07-2026 15:00 - 16:00 460 MW

03-07-2026 16:00 - 17:00 460 MW

03-07-2026 17:00 - 18:00 460 MW

03-07-2026 18:00 - 19:00 460 MW

6. Information on exact operational limit(s) that are expected to be violated in the absence of curtailment :

   03/07/2026

      00:00-01:00 Network Security

      01:00-02:00 Network Security

      02:00-03:00 Network Security

      03:00-04:00 Network Security

      04:00-05:00 Network Security

      05:00-06:00 Network Security

      07:00-08:00 Balaruc-Montpellier 225kV

      08:00-09:00 Balaruc-Montpellier 225kV

      09:00-10:00 Balaruc-Montpellier 225kV

      10:00-11:00 Balaruc-Montpellier 225kV

      11:00-12:00 Balaruc-Montpellier 225kV

      12:00-13:00 Balaruc-Montpellier 225kV

      13:00-14:00 Balaruc-Montpellier 225kV

      14:00-15:00 Balaruc-Montpellier 225kV

      15:00-16:00 Balaruc-Montpellier 225kV

      16:00-17:00 Balaruc-Montpellier 225kV

      17:00-18:00 Balaruc-Montpellier 225kV

      18:00-19:00 Balaruc-Montpellier 225kV

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s) ? :

   The available remedial actions were assessed as insufficient or ineffective to avoid the violation of operational security limits

1. TSO(s)*:

CGES

2. Identification of affected Long Term Transmission Rights:

IT-ME

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

03-07-2026 06:00 - 07:00 400 MW

03-07-2026 07:00 - 08:00 400 MW

03-07-2026 08:00 - 09:00 400 MW

03-07-2026 09:00 - 10:00 400 MW

03-07-2026 10:00 - 11:00 400 MW

03-07-2026 11:00 - 12:00 400 MW

03-07-2026 12:00 - 13:00 400 MW

03-07-2026 13:00 - 14:00 400 MW

03-07-2026 14:00 - 15:00 400 MW

5. Amount of LTTR remaining after curtailment:

03-07-2026 06:00 - 07:00 0 MW

03-07-2026 07:00 - 08:00 0 MW

03-07-2026 08:00 - 09:00 0 MW

03-07-2026 09:00 - 10:00 0 MW

03-07-2026 10:00 - 11:00 0 MW

03-07-2026 11:00 - 12:00 0 MW

03-07-2026 12:00 - 13:00 0 MW

03-07-2026 13:00 - 14:00 0 MW

03-07-2026 14:00 - 15:00 0 MW

6.          Information on exact operational security limit(s) that are expected to be violated in the absence of curtailment *:

HVDC Monita

7.          Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s) *?

During the CC process, all the remedial actions provided by the TSOs are already considered by the CCC

1. TSO(s)*:

CGES

2. Identification of affected Long Term Transmission Rights:

ME-IT

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

03-07-2026 06:00 - 07:00 400 MW

03-07-2026 07:00 - 08:00 400 MW

03-07-2026 08:00 - 09:00 400 MW

03-07-2026 09:00 - 10:00 400 MW

03-07-2026 10:00 - 11:00 400 MW

03-07-2026 11:00 - 12:00 400 MW

03-07-2026 12:00 - 13:00 400 MW

03-07-2026 13:00 - 14:00 400 MW

03-07-2026 14:00 - 15:00 400 MW

5. Amount of LTTR remaining after curtailment:

03-07-2026 06:00 - 07:00 0 MW

03-07-2026 07:00 - 08:00 0 MW

03-07-2026 08:00 - 09:00 0 MW

03-07-2026 09:00 - 10:00 0 MW

03-07-2026 10:00 - 11:00 0 MW

03-07-2026 11:00 - 12:00 0 MW

03-07-2026 12:00 - 13:00 0 MW

03-07-2026 13:00 - 14:00 0 MW

03-07-2026 14:00 - 15:00 0 MW

6.          Information on exact operational security limit(s) that are expected to be violated in the absence of curtailment *:

HVDC Monita

7.          Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s) *?

During the CC process, all the remedial actions provided by the TSOs are already considered by the CCC

1. TSO(s)*:

RTE-TSO

2. Identification of affected Long Term Transmission Rights:

ES-FR

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

02-07-2026 11:00 - 12:00 1280 MW

02-07-2026 12:00 - 13:00 1280 MW

02-07-2026 13:00 - 14:00 1280 MW

02-07-2026 14:00 - 15:00 1280 MW

02-07-2026 15:00 - 16:00 1280 MW

02-07-2026 16:00 - 17:00 1280 MW

02-07-2026 17:00 - 18:00 1280 MW

5. Amount of LTTR remaining after curtailment:

02-07-2026 11:00 - 12:00 963 MW

02-07-2026 12:00 - 13:00 963 MW

02-07-2026 13:00 - 14:00 963 MW

02-07-2026 14:00 - 15:00 963 MW

02-07-2026 15:00 - 16:00 712 MW

02-07-2026 16:00 - 17:00 712 MW

02-07-2026 17:00 - 18:00 712 MW

6. Information on exact operational limit(s) that are expected to be violated in the absence of curtailment :

   02/07/2026

      11:00-12:00 Network Security

      12:00-13:00 Network Security

      13:00-14:00 Network Security

      14:00-15:00 Network Security

      15:00-16:00 Network Security

      16:00-17:00 Network Security

      17:00-18:00 Network Security

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s) ? :

   The available remedial actions were assessed as insufficient or ineffective to avoid the violation of operational security limits

1. TSO(s)*:

RTE-TSO

2. Identification of affected Long Term Transmission Rights:

FR-ES

3. Triggering event:

Curtailment to ensure operation remains within Operational Security Limits

4. Affected volume in MW / hour for each concerned period:

02-07-2026 04:00 - 05:00 1599 MW

02-07-2026 05:00 - 06:00 1599 MW

5. Amount of LTTR remaining after curtailment:

02-07-2026 04:00 - 05:00 1316 MW

02-07-2026 05:00 - 06:00 1316 MW

6. Information on exact operational limit(s) that are expected to be violated in the absence of curtailment :

   02/07/2026

      04:00-05:00 Network Security

      05:00-06:00 Network Security

7. Why alternative measures are not sufficient to avoid the expected violation of operational security limit(s) ? :

   The available remedial actions were assessed as insufficient or ineffective to avoid the violation of operational security limits

Please be informed that we will deploy a new version 1.3.0. of our Publication Tool today at 5:00 PM.

During the deployment, you may experience a brief service interruption of up to 30 seconds.

Thank you for your understanding.

Jao operations.