Draft · research

European EDDIE and the origins of EDDIE UA: learning from a Horizon Europe research project

Зміст статті / On this page (11)
  1. The problem Europe set out to solve
  2. European Distributed Data Infrastructure for Energy – the verified facts
  3. Component one: EDDIE Framework
  4. Component two: AIIDA and on-site measurements
  5. Component three: Data Services Marketplace
  6. A data space is more than a giant central database
  7. Why we chose the name EDDIE UA
  8. What is specific to Ukraine
  9. A concrete industrial-customer journey
  10. What we borrow as principles – and what remains unproven
  11. Primary sources and further reading

The problem Europe set out to solve

Imagine a small company that creates an excellent energy-efficiency application. Its service analyses electricity readings, identifies unnecessary peaks and helps customers schedule flexible equipment. The company has already integrated with its national metering data platform. When it enters another European country, however, the energy-data entitlement process, identification, permission steps, meter reference data, messages, quality flags and interface can all be different. A second country requires another integration. Each bespoke implementation raises the cost of serving a new customer.

This is the gap between a consumer's legal right to access and share energy data and the reality of fragmented national procedures. The European EDDIE project researched how to provide interoperable services above these national arrangements, without pretending that every country has identical technical and legal requirements.

European Distributed Data Infrastructure for Energy – the verified facts

EDDIE stands for European Distributed Data Infrastructure for Energy. It was a European Union Horizon Europe research and innovation action, grant agreement 101069510. According to the European Commission's CORDIS project register, it ran from 1 January 2023 to 30 June 2026 and is now recorded as closed. Its reported total cost was €8,900,168.77, including €7,989,333.01 of EU funding. These are figures for the European research project, not a budget received by EDDIE UA.

CORDIS describes a multinational research partnership spanning energy-data exchange, academia, software engineering and energy-service organisations. That interdisciplinary nature matters. Energy data interoperability requires agreement about entitlements, workflows, responsibilities, security, customer usability and economic feasibility, as well as code.

The primary references are the CORDIS fact sheet, CORDIS reporting, the European EDDIE website and the project's technical architecture.

Component one: EDDIE Framework

The EDDIE Framework provides a common way for eligible energy service providers to request permission and obtain energy information from different regional or national data-sharing infrastructures. Region-specific connectors handle the particular processes and formats behind a more stable interface. One energy application can therefore avoid reimplementing every regional workflow from scratch.

The framework is not a database of every European customer's data. Entitlements, national operator responsibilities, retention rules and regional availability still matter. Its value is the interoperability layer and the separation of a provider's application from the changing mechanics of regional data access.

For example, the same industrial load-analysis service could work in several countries while distinct connectors deal with each national infrastructure. This is a useful design lesson for Ukraine, not a claim that all countries or services were fully connected at the end of the project.

Reference: EDDIE Framework architecture.

Component two: AIIDA and on-site measurements

The Administrative Interface for In-house Data Access (AIIDA) was designed to help customers share near-real-time energy measurements obtained from their own smart meters or connected equipment. The customer can manage connections and permissions, while compatible systems collect and pass on relevant data.

Why is this different from validated settlement history? An energy consultant analysing last month's bill may need official historical readings. An energy management system deciding when to charge an EV or reduce a flexible load may need much fresher site telemetry. The latter may be provisional or non-validated. These are different data products, with different quality requirements, legal consequences and safety boundaries.

EDDIE UA sees a relevant architectural principle here: distinguish access to official historical meter data from access to real-time device telemetry. But AIIDA is a specific European project component; it is not automatically the same product as Wesfin Edge, nor does our use of the concept imply ownership of the European technology.

Reference: AIIDA architecture.

Component three: Data Services Marketplace

The European EDDIE Marketplace addresses the discovery of services that actually make energy data useful. A customer might want an energy audit, flexibility assessment, battery-sizing study or automated EV charging. The provider needs a way to explain the service and request an appropriate access scope. Interoperability only creates value when it enables a legitimate service to be delivered.

A marketplace concept does not imply that all services were available to all citizens in every Member State. Deployment depends on supported regional connectors, lawful data access and customer adoption. That distinction between architectural ambition and verified coverage matters for our own communication.

Reference: European EDDIE architecture overview.

A data space is more than a giant central database

A central data warehouse is one possible storage arrangement. A data space is concerned with common standards, identities, permissions, provenance and the ability of independent systems to exchange information safely. It can be federated without relocating all original records under one institution. Conversely, some official functions may sensibly remain centralised by law.

For that reason, the European example is not evidence that maximum decentralisation is always best. It is evidence that separating national legal responsibilities from interoperable access procedures is a fruitful engineering and governance question.

Why we chose the name EDDIE UA

Our project name consciously refers to the subject matter and ambition of the European EDDIE research. We share the problem statement: energy data should be accessible to legally entitled users through interoperable, transparent and competitively neutral processes. “UA” identifies the Ukrainian jurisdiction and the need to address Ukrainian metering law, its participants, system architecture and market realities.

This naming choice signifies an intellectual reference, not an official Ukrainian branch, licensed franchise, European grant, technical partnership or endorsement. We have not presented EDDIE UA as an output of the Horizon Europe project. Nor do we claim that the European consortium commissioned, financed or approved our work.

The potential for brand and trademark confusion is real. Before relying on the name in commercial or institutional promotion, the rights, mark similarity, possible licensing issues and need for communication with European rights holders must be reviewed. If necessary, the name and visual identity may need to be distinguished further.

What is specific to Ukraine

The EU initiative dealt primarily with cross-border compatibility among European data environments. EDDIE UA studies one national electricity market: Ukraine's legally designated commercial metering administrator (AKO), Ukrenergo DataHub, metering points (EIC), metering service providers, distribution operators, independent aggregators and balancing responsible parties.

Our research hypothesis is to preserve one legally authoritative settlement framework while making information access technically interoperable – potentially through independent access services where legally permitted. But a centralised, open, geo-redundant API remains an equally legitimate alternative. A DNS-inspired directory is an engineering idea for discovery of the responsible technical source, not a licence for private nodes to rewrite official consumption figures.

We cannot copy a European software design and simply declare it compliant with Ukrainian law. The legal roles, entitlements, procedures, contracts, economic costs and actual implementation evidence must be established independently.

A concrete industrial-customer journey

Consider a refrigeration business with rooftop solar, flexible cold storage and a proposed battery. It knows its company registration number and EIC. Neither identifier alone proves entitlement to a customer record. A suitable service would verify the representative, confirm the lawful relationship to the metering point, determine the legitimate basis and specify the authorised recipient, historical period and purpose.

The customer then selects an independent energy specialist. That specialist reads only the permitted validated historical intervals with source, version and quality, and evaluates shifting refrigeration cycles, charging or battery sizing. The customer should be able to see the applicable access log and end the permission where the law provides for that procedure. A change of data provider should not silently switch the customer's electricity supplier, balancing party or official meter status.

A local site controller may simultaneously observe fast device telemetry and carry out safe industrial control. This must never be confused with legal authority to alter official settlement readings or to dispatch inverters through DataHub.

What we borrow as principles – and what remains unproven

We take the value of functional roles, reusable regional adapters, clear permission lifecycles, consumer choice and separation between validated and near-real-time data. Directive (EU) 2019/944 and Regulation (EU) 2023/1162 help frame a comparison. They are not automatically directly applicable Ukrainian law: their domestic effect requires analysis of Ukraine's legislation and applicable Energy Community commitments.

EDDIE UA still needs lawful operating arrangements, independent neutrality tests, security and identity infrastructure, evidence of fault tolerance, compatible sources and a proper comparison against an improved central API. A three-process synthetic laboratory is not a production federation. Green CI is not a statutory accreditation.

Primary sources and further reading