Source - DHV Presentation 2026-04-27

Type: Presentation slides (59 pp) Author: Ei (Energimarknadsinspektionen) + Svenska kraftnät Date: 2026-04-27 Context: Slides used at the digital stakeholder consultation meeting (digitalt möte) on the centralt datahanteringsverktyg (DHV) proposal. Complements Source - Ei Förslag Centralt Datahanteringsverktyg (2026), the written consultation document from the same process. Written stakeholder comments were due 8 May 2026 (ärende 2025-103808).

Summary

Ei and Svk presented the emerging DHV+FIS architecture to stakeholders at an April 27, 2026 digital meeting. The presentation is the most detailed publicly available exposition of the two-component architecture ahead of the formal September 2026 report to government.

Key content

Machine-readable network tariff explicitly in scope

DHV explicitly includes maskinläsbar elnätstariff för styrtjänster (machine-readable network tariff for steering services) as a data category within scope. This directly addresses the effekttariff integration gap: each DSO currently designs its tariff differently, making it impossible to build standardised automated steering services across DSO boundaries. Norway’s Elhub experience is cited as the explicit lesson: “Borde ha inkluderat data om nättariffer” — it should have included tariff data. By incorporating machine-readable tariffs from the start, DHV intends to enable automated peak-control and demand-response services that today require bespoke integration per DSO.

Two-component architecture confirmed

DHV (the grunddata layer): single source of truth for all electricity market master data — metering points, grid contracts, supply contracts, customer-BRP-supplier mapping, meter values, network tariffs. Performs centralised grid settlement (nätavräkning). Manages customer consents via “Mina sidor.”

FIS (flexibilitetsinformationssystem): the flexibility data layer — national registration of flexibility resources, prequalification, activation reference profiles, settlement basis. FIS requires DHV v1 to be operational first.

Six design principles (from the presentation)

1. No direct actor-to-actor communication — all exchange via DHV
2. DHV takes over DSO administrative tasks (settlement, data distribution)
3. DHV as single source of truth for delivery structure
4. Centralised consent management
5. FIS for all flexibility resource data nationally
6. Mina sidor portal for customer access

Stakeholder concerns raised at the meeting

• Data quality governance: who is responsible for ensuring accuracy of master data? Multiple actors currently hold overlapping, inconsistent records.
• Transition costs: migrating from ~170 heterogeneous DSO systems to a single central architecture is a significant integration project for smaller DSOs.
• Privacy / GDPR: centralising customer data including consumption values creates data protection obligations that need clear legal basis.
• Aggregator access rights: aggregators need direct access to metering data for resource management; the FIS design must ensure that access is equally available to all qualifying service providers, not mediated through suppliers or DSOs.
• Sequencing risk: the dependency (FIS cannot go live until DHV v1 is operational) means any delay to DHV delays the NC DR FIS obligations.

Nordic comparison

The Norway lesson (Elhub) is presented as primary reference for the centralised approach: the model works, but tariff data omission created a gap that had to be corrected. Finland and Denmark are also cited as evidence for centralisation. Austria’s decentralised (P2P) model is the negative reference: E-Control found it inadequate — opaque costs, difficult debugging, no central statistics.

Relevance to wiki