Source - Svk IA DR Webinar Part 1 (2025)

Type: Internal webinar presentation (Svk, C2 - Internal) Presented by: Yvonne Ruwaida (Svk) Date: 2025-03-28 Title: “Implementing Regulation Demand Response — Del 1”

Webinar presenting the draft EU Implementing Act on Demand Response (IA DR) — the data interoperability implementing regulation being developed by ENTSO-E and EU DSO Entity as a companion instrument to the Network Code on Demand Response. This is Part 1 of a multi-part webinar series; Part 2 was planned for later in 2025.

Context

The IA DR is mandated by Arts. 23–24 of Directive 2019/944, which require the Commission to adopt implementing acts establishing interoperability requirements and non-discriminatory procedures for access to metering, demand response, and customer switching data. The same legal mandate produced IR 2023/1162 (metering data) in July 2023. The IA DR builds directly on IR 2023/1162’s architecture.

By March 2025, Phase 1 of the IA DR was in external consultation at EU DSO Entity (deadline: April 4, 2025). Phase 1 would then be submitted to the European Commission in Q2 2025. Phase 2 was planned for autumn 2025 (submission to EC Q4 2025). Entry into force of the full IA DR as a Commission implementing regulation is estimated 2027.

Key claims

Scope: what the IA DR covers

The IA DR addresses information exchange in three contexts where DSOs are directly involved:

1. DSO has customers participating in balancing markets
2. DSO is a buyer of services for congestion management and voltage regulation
3. DSO has flexible connection agreements (villkorade avtal)

What the IA DR does not cover:

• SO-to-SO information exchange (forecasts, historical data, grid model) → national T&C or EU method
• Inter-market information exchange (bid forwarding from local to balancing market) → national T&C
• Product standards (EU method)

15–18 processes in two phases

Phase 1 (submitted Q2 2025) includes 15+ processes split by DSO-relevance category:

Always affects DSO (regardless of role):

1. General access to flexibility register (public information)
2. General access to flexibility register (data, by eligible party)
3. CU registration
4. Update CU
5. De-registration CU
6. Suspension of CU by an entitled party
7. Re-activation of CU
8. Service provider registration
9. Service contract revocation by customer
10. Service contract termination by flexibility service provider
11. Baseline data handling
12. Quantification of the delivered services
13. Settlement

Affects DSO depending on role: 14. Service Provider switching (initiated by new SP) 15. Third party CU Operator registration

Phase 2 (submitted Q4 2025) adds:

• SPG/U registration and related processes (1–9: registration, application, update, de-registration, suspension, grid prequalification, switching, revocation, confirmation)
• CU grid prequalification (10), switching (11), revocation (12), termination (13)
• Product verification (14)
• Activation or execution of a flexibility product (15)
• Flexible connection agreement (16)
• Temporary limits (17)
• Bidding (18)

New role taxonomy

The IA DR introduces several new functional roles not in IR 2023/1162:

Existing roles carried over: Final Customer, Service Provider, Eligible Party, Metered Data Administrator, Connecting System Operator, Procuring System Operator, Entitled Party, Affected Party.

EU reference model architecture

The IA DR uses the same 5-layer EU reference model as IR 2023/1162:

• Business layer: business objectives and roles
• Function layer: use cases, data sharing, permission management
• Information layer: data models (CIM, etc.)
• Communication layer: protocols and data formats (CSV, XML)
• Component layer: data exchange platforms, hardware

Member states must document their national implementation in an EU database (starting June 2025). This documentation forms the basis for evaluating compliance and guiding external actors.

Timeline for EU data standardization pipeline

(*Estimated; not formally published)

Process example — Baseline (Process 12)

Step 12.1: Eligible party (per national T&C) sends relevant data to the Baseline Calculator Step 12.2: Baseline Calculator determines baseline using the baseline method and relevant data Step 12.3: Baseline Calculator sends baseline to Baseline Provider; Baseline Provider makes it available to entitled parties

Connection to IR 2023/1162

Process 13 (making measurement data available for CU quantification) builds on IR 2023/1162 — the key difference is that the data request is for a CU identifier, not a facility/accounting-point ID. This is the architectural connection between the metering data system and the flexibility system.

Relevance to wiki

• Network Code on Demand Response: The IA DR is the data interoperability companion instrument to the NC DR. The NC DR sets market rules; the IA DR sets data exchange processes. The NC DR page’s section on “Implementing Act under EMD Art. 24” refers to the same instrument.
• Flexibility Communication Protocols: The IA DR’s communication layer (protocols, data formats) is the regulatory vehicle for standardized protocol requirements.
• Ei: Ei will be involved in national implementation of IA DR through the same T&C process as NC DR.
• Elmarknadshubb: The FIS CU-module and SP-module operators described here are the functional roles that Sweden’s DHV+FIS architecture must accommodate.