Upcoming Changes in Data Flow Contents

Implementation Timeline for 2024 and 2025.

As mentioned in our previous news, eSett will implement several changes to the data flows gradually over the course of 2024 and 2025. While these changes may seem relatively minor, it is crucial for you to familiarize yourself with them and evaluate their impact on your systems. These modifications will eventually affect the communication of data flows both from market participants to eSett and vice versa.

Starting in October 2025, eSett will move to phase 2 of the implementation. This means that incoming data flows should only use the new asset type codes for Production Unit (PU) types or the new standard code for the bilateral trade process type. At the same time, eSett will start using only the new codes in outgoing data exchange: data packages and information service. The exact timing will be announced closer to the change.

The material related to the data exchange has already been updated and is available in https://ediel.org/nordic-balance-settlement-nbs/. Kindly contact eSett’s customer service if you have any questions about the change or its impacts.

Update in Bilateral Trade Process Type from Z05 to A59

Currently, the Bilateral Trade reporting process uses the local code “Z05 Bilateral trade” as a process type in the XML header section. This code will be replaced by the standardized code “A59 Internal trade reporting”. The new code “A59” has been in use for Bilateral Trade data flows reported to eSett from February 2024 in parallel with the old code. The new code “A59” will be used for outgoing data from eSett to BRPs starting from October 2025.

Impacted data flows:

  • (BITI) Receive BIT values
    [ENTSO-E ESS Schedule Document]
  • (BICO) Bilateral Trade Intermediate Confirmation Report
    [ENTSO-E ESS Confirmation Report]
  • (BICO) Bilateral Trade Final Confirmation Report
    [ENTSO-E ESS Confirmation Report]
  • DP Bilateral Trades
    [ENTSO-E ESS Confirmation Report]
  • INFS Request: Bilateral Trades
    [ENTSO-E ESS Schedule Document]

Schedule:

  • The new code “A59” may be used for BITI data flows starting from 29.02.2024 as the new system version is deployed.
  • The new code “A59” will be used for incoming and outgoing data from eSett to BRPs from October 2025 (estimate). The exact timing will be communicated later.

 

Changing PU types

Several PU types use local Z-codes as their asset type in the XML files. These Z-codes will be replaced by standard codes. New asset type codes have been in use when reporting data to eSett from April 2024 in parallel with the old codes. The new asset type codes will be used for outgoing data from eSett starting from October 2025.

Impacted data flows:

  • (PRUI) Production Unit – IN
    [NEG Resource Object (Production Unit) Master Data Document]
  • (MEPI) Receive Merged Production values
    [NEG (ebIX® based) Aggregated Data per MGA (E31, E44) – production]
  • DP Production Units – All
    [NEG Resource Object (Production Unit) Master Data]
  • DP Production Units – Delta
    [NEG Resource Object (Production Unit) Master Data]
  • DP REs’ Merged Production Data per Type and MGA
    [NEG (ebIX® based) Aggregated Data per MGA (E31, E44) – production]
  • DP REs’ Production Data per Type and MGA
    [NEG (ebIX® based) Aggregated Data per MGA (E31, E44) – production]
  • INFS Request: Merged Production
    [NEG (ebIX® based) Aggregated Data per MGA (E31, E44) – production]
  • INFS Request: Production per Production Unit Type and MGA
    [NEG (ebIX® based) Aggregated Data per MGA (E31, E44) – production]

 

Schedule:

  • New asset type codes may be used for incoming data to eSett starting from April 2024.
  • New asset type codes will be used for incoming and outgoing data from eSett to market parties from October 2025 (estimate). Exact timing will be communicated later.