Draft · research

Practical starting point: preparing lawful access to energy data

Зміст статті / On this page (7)
  1. What you can do here
  2. 1. I run a business and want to understand consumption and flexibility
  3. 2. I am an independent aggregator using an external balancing responsible party
  4. 3. I am an engineer and want to test interoperability
  5. 4. I work with the administrator, a metering provider, distribution operator or regulator
  6. 5. How to interpret the downloadable example
  7. Primary sources

What you can do here

Identify your role, the required data and evidence, and inspect a synthetic example of scoped access, correction and revocation. Do not submit real EICs, metering profiles, contracts, passwords or signing credentials here. EDDIE UA does not connect to the production DataHub.

1. I run a business and want to understand consumption and flexibility

Goal: identify peaks, assess a battery, solar, refrigeration or EV charging, and estimate value after real costs.

Prepare privately: organisation name and registration identifier, your own metering points/EICs, authorised representatives, the required time period, the purpose of the analysis and the legal basis for sharing the requested information. An EIC identifies a metering point; it is not proof of access entitlement.

  1. Verify authority to represent the legal entity and the relationship to each metering point over the requested period.
  2. State a limited purpose, such as 12 months of interval history for peak and BESS sizing. Request only relevant data.
  3. Determine the lawful channel and requirements in the current rules of the metering administrator and service providers. EDDIE UA is not that channel.
  4. Check interval coverage, units, import/export sign, quality, time zone and subsequent corrections.
  5. Share with an independent analyst only under an established legal basis and appropriate safeguards.
  6. Compare conservative, base and optimistic scenarios including CAPEX, OPEX, purchased electricity, degradation, imbalance risk and service fees.

Deliverable: a clear analysis brief, verified authority, a metering-point/period inventory and quality requirements – not automatic access by entering a company number.

2. I am an independent aggregator using an external balancing responsible party

Goal: evaluate a client's flexibility while they retain their electricity supplier and external balancing responsible party (BRP).

  1. Establish the legal grounds, authorised representative and exact scope: metering points, period, data categories and expiration.
  2. Compare the use case against the administrator's verified current operating procedures. Do not assume an API exists or does not exist.
  3. Use only legitimately received data and preserve its origin, version and correction trace.
  4. Keep data access separate from an aggregation contract, BRP membership, market qualification and physical control rights.
  5. If the procedure is unclear, record the specific requested action, governing rule, observed result and question to the administrator rather than proclaiming a missing service.

Proposed research test: two equally eligible independent providers should face comparable access requirements, and lawful refusal reasons should be explainable without exposing protected data. This is a test hypothesis, not a claim about the administrator's verified performance.

Six practical use cases cover cold storage, retail sites, solar, apartment buildings and developers.

3. I am an engineer and want to test interoperability

Goal: build and check an information client without production customer data or credentials.

  1. Start with the synthetic JSON example. It is not an official DataHub schema, API, endpoint or certification test.
  2. Test the relationship between an authorised recipient, representative, metering point and time scope. An out-of-scope request fails in this model.
  3. Repeat a historical-data request after revocation; an old measurement is not, by itself, a continuing grant.
  4. Simulate a corrected reading without destroying the preceding revision or origin.
  5. Distinguish UTC instants that map to the same local clock hour during the autumn daylight-saving transition. A missing reading is not zero.
  6. Record expected versus observed outcomes, version, refusal reason and test evidence.

Deliverable: a repeatable synthetic conformance report for scopes, revocation, corrections, time and isolation. Passing these tests does not qualify any system for production access.

Architecture separates commercial-metering information flows from real-time control of physical energy resources.

4. I work with the administrator, a metering provider, distribution operator or regulator

We propose reviewing documented operations, not replacing the official metering system.

  • Which current document covers recipient categories, representation, interval history and refusal reasons?
  • How are revisions, quality, 23- and 25-hour days, revocations and audit events represented?
  • Which specifications, formats, conformance fixtures and versioning procedures can third-party integrators lawfully access?
  • How can non-discrimination be verified without exposing consumer profiles or security secrets?
  • Could a resilient central open API provide the same result more safely and economically? Federation is not a predetermined answer.

Regulatory status: as of 21 November 2026, agenda item 29 of the 24 November NCRECP meeting refers to future consideration of draft amendments, not an adopted resolution. Verify the actual outcome, publication and consultation terms after the meeting. Official meeting materials.

5. How to interpret the downloadable example

The JSON file contains illustrative permission scope, reading revisions and daylight-saving time, and revocation followed by a denied new request. Its status values and object fields are made up for teaching and must not be confused with any official exchange specification.

  • `case_type` – the event or right tested.
  • `scoped_permission` – the permitted recipient, point and period in the model.
  • `readings` – illustrative intervals, quality and revisions.
  • `expected_result` – how this educational model should behave, not a real DataHub response.
  • `not_an_official_api` – a prominent restriction on interpreting the file.

There is no public upload form for customer metering records. Start by verifying sources, not by submitting private data.

Primary sources

Project updates · FAQ · Participate