# European electricity data-access framework

> Legal sources: Directive (EU) 2019/944 and Commission Implementing Regulation (EU) 2023/1162. EU reference procedures are not automatically directly applicable Ukrainian law.

## Why access to data matters

Independent aggregation, energy management and consumer choice depend on trustworthy access to readings. Under European policy, a retail electricity customer may use an independent service provider, subject to applicable permissions and other lawful bases. Transparent procedures are essential to prevent a service provider from being disadvantaged simply because it is not affiliated with the incumbent operator.

Directive 2019/944 Article 17 deals with independent aggregation. Article 23 concerns data-management rights and secure, non-discriminatory access. Article 24 covers interoperability. Implementing Regulation 2023/1162 provides reference roles and procedural information exchanges.

## Functional roles are not necessarily separate companies

The reference model distinguishes the metered data administrator, metering point administrator, data access provider, permission administrator, eligible party and final customer. A single organisation can perform more than one role. The regulation does **not** require a DNS-like federation or multiple statutory commercial metering administrators. The mapping from these functional roles to Ukrainian legal entities requires independent legal assessment.

## Six distinct consumer and market procedures

### P1 – Customer access to validated historical readings

The customer identifies and authenticates through an authorised procedure, the system checks rights to a metering point and provides structured, quality-labelled, time-bound information. This is not an unrestricted publication of all customer profiles.

### P2 – Access by an eligible third party

An aggregator or service provider demonstrates permission or another valid legal basis and receives only the specified metering history or future data. Access to existing data and continuing provision must be explicitly distinguished.

### P3 – Termination of a third-party service

A service provider ends its energy service, including the appropriate data-access workflow. Termination may be subject to ongoing lawful processing needs. This procedure is not identical to customer revocation.

### P4 – Customer revokes active permission

The customer withdraws a permission where revocation is applicable; this change is recorded and enforced. Existing legal retention obligations may remain. A revoked grant must not become a back door for new requests.

### P5 – Activation of near-real-time smart meter data

A permitted local interface is activated in accordance with the relevant meter, customer rights and technical safeguards. It should be described separately from historical validated settlement information.

### P6 – Reading near-real-time data

An authorised compatible energy management system reads the activated data with timing and quality context. This does not make the national data exchange a second-by-second control channel for batteries or inverters.

## Clause-to-acceptance mapping

Art 17: demonstrate independent aggregator onboarding without privileged technical exceptions. Art 23: test lawful basis, audit records, transparency and equal access. Art 24: test schema versioning and interoperability across independent implementations. Regulation Articles 5–8: validate the role responsibilities and permission lifecycle. Article 9: distinguish local near-real-time reading. Annex procedures: exercise P1–P6 independently.

A passing synthetic unit test is not proof of conformity with the Regulation. A real conformity claim needs official national applicability analysis, implementation evidence and independent assessment.


## Why legal rights need operational interoperability

A consumer's right to share energy data does not by itself create a working integration. National markets can differ in customer identification, permission lifecycle, data formats, market roles and the processing of corrected readings. Energy service companies need predictable interactions as well as abstract legal entitlements.

Commission Implementing Regulation (EU) 2023/1162 sets out a reference model for accessing metering and consumption data. It does not require one EU-wide database. Instead, it clarifies functional participants and procedural exchanges so different national systems can be understood through comparable descriptions. One organisation can carry several functions. Application in Ukraine remains a matter of applicable Ukrainian law and international obligations, not an automatic consequence of copying EU software.

## One metering point, several functional responsibilities

Take an industrial customer with a smart meter. A metering-point administrator maintains the relevant reference relationship. A metered-data administrator stores validated historic readings. A permission administrator records customer-granted access rights where applicable. A data-access provider facilitates a permitted request. In some jurisdictions, several functions are performed by one organisation.

The point is to make the actions and accountability clear, not to dictate that Ukraine establish separate private firms for every EU role. A technical separation of functions is not a transfer of statutory metering authority.

## Six procedures, six distinct journeys

### P1 – A customer retrieves historical readings

The customer's identity and legal relationship to the point are established through the required process. Structured intervals, timestamps, sources and quality information are returned. Corrections must not make past versions silently disappear from relevant audit evidence.

### P2 – An independent service gains defined access

An eligible aggregator or energy-efficiency company demonstrates its lawful entitlement and receives only the requested categories, point and period. The customer's EIC does not become a public password, and granting data access cannot itself switch supplier or balancing responsibility.

### P3 – An eligible party terminates its service

The service provider ends the relevant relationship and the corresponding access workflow. Distinct legal obligations may still require retention of previously obtained records. This is not equivalent to consumer-initiated permission revocation.

### P4 – A consumer revokes active permission

Revocation follows the defined procedure and must affect new access attempts under that permission. Previously lawful processing and any independent lawful basis require separate legal treatment.

### P5 and P6 – Near-real-time meter information

An authorised compatible local interface is first activated and then read by the appropriate system. Fast readings may be non-validated, while official historic settlement data follow their own legal procedures. This distinction is crucial for site EMS and industrial safety.

## What equal technical treatment actually means

A useful access framework should document onboarding evidence, request states, denial reasons, supported formats, test fixtures, schema changes and a review route. A market entrant should not need informal privileged knowledge to reach the same documented interface that an incumbent uses. Metrics such as median and p95 onboarding time may help examine equal treatment, but they are not binding service levels without an appropriate legal procedure.

## European EDDIE as a complementary example

The Horizon Europe EDDIE research project explored an interoperable framework, on-site near-real-time data access through AIIDA and a marketplace for energy services. These are research architecture components, not legally mandatory software products under Regulation 2023/1162. Learn more in [our extensive independent history of European EDDIE and EDDIE UA's name](?page=european-eddie).


## References

- [Directive (EU) 2019/944](https://eur-lex.europa.eu/eli/dir/2019/944/2025-10-12)
- [Implementing Regulation (EU) 2023/1162](https://eur-lex.europa.eu/eli/reg_impl/2023/1162/oj/eng)
- [Ukrainian framework](?page=regulatory)
