LinkedIn·Tuesday, 25 August 2026·1d ago
Why should a European energy application describe essentially the same Data Exchange Need again and again—in a different national process…
Project EDDIE
1,270 followers
Why should a European energy application describe essentially the same Data Exchange Need again and again—in a different national process and format?
It shouldn’t.
An application requesting validated hourly electricity data for the previous 12 months needs fundamentally the same data in France, Denmark, Spain or Austria.
What changes is the regional implementation:
→ Enedis Data Connect: redirect, customer login and callback
→ Energinet Eloverblik: API key, metering point and refresh token
→ aelec Datadis: portal approval, CUPS and DNI/NIF
→ EDA Energiewirtschaftlicher Datenaustausch GmbH and Austrian DSO portals: consent, Zählpunktnummer and XML/AS4 messages
Same Data Exchange Need. Very different regional journeys.
This is why Project EDDIE introduced DataNeeds.
An application expresses its Data Exchange Need once in EDDIE’s common European language:
→ What data is required?
→ From which source or asset?
→ For which timeframe and at what granularity?
→ For which purpose and under which policy?
→ Is historical, accounting, near-real-time or bidirectional grid-edge data exchange required — or additional interactions introduced e.g. through Project INSIEME?
Regional connectors translate that stable intent into the appropriate national permission journey, identifiers, interfaces and exchange formats.
The same declaration can also generate a fully customisable “Connect with EDDIE” button and permission popup. Status events, regional raw messages and harmonised payloads can be managed through dedicated Apache Kafka topics, while applications receive data through Kafka, AMQP or REST using common European information models.
This is more than an integration convenience.
If an application performs essentially the same job in every affected Member State, a Common European Energy Data Space must understand the application’s Data Exchange Need—not merely transport opaque files between systems.
A shared European expression of intent becomes the stable contract between:
→ the application
→ the customer
→ regional infrastructures
→ connectors and data-space services
→ common European information models
Express the need once. Translate it regionally. Consume it consistently across Europe.
Try it yourself:
EDDIE DataNeeds documentation:
https://lnkd.in/dhmP2wkB
Official EDDIE tutorial:
https://lnkd.in/dQzAtMfX
More about INSIEME and the operationalisation of CEEDS:
https://insieme.energy/
Implementation, architecture and platform-operations support:
EntArc.eu · FlexiData GmbH · Digital4Grids
#EnergyData #DataSpaces #CEEDS #EDDIE #INSIEME #Interoperability #SmartGrids #DigitalEnergy #OpenSource #Kafka #EuropeanUnion
♥ 12↻ 2
View on LinkedIn Cross-referenced
Related on the wire
As Project EDDIE nears its final review, we found time to pause and reflect on where it came from—and how far it has evolved. EDDIE did not…
Europe does not need one central database for energy data. It needs a trusted way to connect what already exists - and a common…
EDDIE as a backbone for Flexible Connection Agreements Flexible Connection Agreements are becoming an operational requirement. Article 6a…
Over the past years, EDDIE has grown into an extensive open-source toolset with a powerful and increasingly sophisticated set of features.…
After three years of collaboration, innovation, and dedication, the EDDIE Final Conference brought together partners, policymakers,…
Today, our consortium comes together for its final General Assembly 💚 As we approach the final stage of the project, this meeting is an…