DHV Presentation 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 — though this appears on an earlier, separate slide about customer-facing functions, before DHV/FIS are formally introduced, so its explicit inclusion within DHV’s own scope is an inference rather than a directly-stated scope item. Norway’s Elhub experience is cited as the explicit lesson, under “Lärdomar från andra länders datahanteringsverktyg” (presenter Mattias Johansson, Ei): “Norge (Elhub) • Outnyttjad potential för statistik och efterfrågeflexibilitet, Borde ha inkluderat data om nättariffer” — unused potential for statistics and demand flexibility, [and] should have included tariff data. (The claims that per-DSO tariff design variance currently blocks standardized automated steering services, and that DHV intends to enable automated peak-control/demand-response services that today require bespoke per-DSO integration, are not stated in the raw presentation — they were unsupported additions and have been removed.)

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 and settlement basis (the raw text does not use the specific term “activation reference profiles”). FIS requires DHV v1 to be operational first.

Design principles (from the presentation)

The raw presentation’s own explicit principles slide (“Implementering av DHV och FIS”) lists only three bullets, not six — an earlier version of this page listed six items not traceable to any single slide in the deck:

1. Tydligt centralt ansvar (Svenska kraftnät) — clear central responsibility
2. Bygger vidare på befintligt arbete där det är lämpligt (Elmarknadshubb) — builds on existing work where appropriate
3. Stegvist införande för att minimera risk — phased introduction to minimize risk

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 a heterogeneous landscape of DSO systems to a single central architecture is a significant integration project for smaller DSOs (the raw text does not give a specific DSO-system count — an earlier version’s “~170” figure was unsourced and has been removed).
• Privacy / GDPR: centralising customer data including consumption values creates data protection obligations that need clear legal basis.
• 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 model is the negative reference: E-Control found it inadequate — opaque costs, difficult debugging, no central statistics.

Relevance to wiki