Från DNO till DSO LinkedIn Artikel (2026)

“Från DNO till DSO – och vad det faktiskt betyder för elnätet och driftcentralen,” LinkedIn article, published 2026-09-14. An unnamed grid-operations practitioner’s essay on what the DNO→DSO transition actually changes in day-to-day control-room (driftcentral) practice — distinct from the rest of this wiki’s DSO coverage, which is almost entirely regulatory/market framing (obligations, procurement, DNDPs). This is a practitioner’s argument and framing, not a primary data source or official report — treat claims here as one experienced operator’s perspective, not established fact, unless independently corroborated elsewhere in the wiki.

Core argument

DNO vs. DSO is about the word “operator,” not a rebrand. DNO (Distribution Network Operator) implies owning, maintaining, and repairing the grid. DSO (Distribution System Operator) implies actively following, controlling, and assessing the grid while it is in operation — a materially bigger shift than the name change suggests, driven by the grid becoming more “mobile” (more local production, batteries, EVs, variable power flows) rather than by any dramatic rise in total electricity consumption. The author explicitly pushes back on framing this as driven by an “inevitable explosion” in electricity use: actual Swedish electricity consumption has fallen since the Barsebäck 1 closure in 1999 (heat pumps, district heating, solar, and — the author’s emphasis — rising electricity and grid prices), even though Svenska kraftnät’s own long-term forecasts still project substantial future growth. The author’s point: DSO isn’t justified by “every station is about to hit its ceiling” — many substations rarely reach even 50% loading in high-load periods (the author adds this does not mean they are wrongly built — reserve, switching options and future connections must be counted) — but by localized, intermittent, direction-variable problems (voltage, local production, reserve-feed limitations) that a purely reactive, energy-total-focused operating model doesn’t catch.

Reactive vs. proactive control-room work. Traditional driftcentral work is reactive by design (and reasonably so) — a breaker trips, an alarm fires, a smart meter reports an outage, and the operator responds to what has already happened. DSO work extends this earlier: understanding what is about to happen, not just what already has. Not all faults give warning (a dug-up cable is a dug-up cable), but many do — temperature changes, recurring earth faults, voltage variation, rising load, communication problems, short interruptions, deviating meter readings.

ADMS’s actual job, distinguished from SCADA. SCADA shows what the installation is doing; ADMS is meant to help understand what that means — fusing network model, SCADA, outage management, metering, customer data, fault indicators, work-order status, and reserve-feed options into one coherent situational picture, so the operator isn’t personally acting as the integration layer across a dozen separate systems during a live event. The author is explicit that ADMS should reduce what an operator has to look at, not add another screen.

FLISR, named explicitly (FLISR (the raw gives only “find the fault, disconnect as little as possible, restore the rest”; the acronym expansion is added)) — automatic-reconfiguration logic that can only work as well as the underlying physical network allows: an ADMS can compute a perfect alternative switching plan in seconds, but if there’s no physical alternative feed path, the calculation is moot. The author argues Swedish local grids often have limited switching options and single-transformer substations, meaning more redundancy investment (extra feed points, more remote-controlled breakers, dual transformers in high-consequence locations) is a precondition for FLISR/automation actually paying off, not an optional extra.

AI’s proposed role is narrow and specific: not narrative-generating AI, but pattern-finding in volumes a human operator would otherwise miss — a recurring earth-fault alarm, a transformer behaving anomalously, a voltage shift correlated with a specific production plant coming online, several fault indicators converging on the same cable section.

Organizational model — the Kraftringen Nät example. At Kraftringen Nät, control-room operators (driftledare) work as VHI (vakthavande ingenjör / duty engineer) two weeks in an eight-week rotation; the other six weeks are other tasks or standby cover, during which the same people can work more as driftingenjörer (the author adds that the driftledare should not do all analysis in the company) — analyzing past events, following up on faults, checking meter readings, reviewing recurring alarms, evaluating automation performance, and identifying where better remote control or reserve feeds are needed. The author’s argument: this rotation is a strength, not just a scheduling artifact — control-room experience makes the analysis work sharper, and analysis work makes the next control-room shift better prepared. The author predicts the driftingenjör role becomes more important, not less, as the grid becomes more automated — the analysis and oversight work (checking automation’s decisions, catching small problems before they grow) has to sit with someone who isn’t simultaneously running live operations.

Relevance to this wiki

• Distribution System Operator: the page currently covers DSO almost entirely as a regulatory/market role (procurement obligations, DNDP, unbundling) with no coverage of what the DSO transition means operationally in the control room — this source fills that gap directly.
• Digitalization and Smart Grid: names ADMS/DMS in its layer table without further detail; this source is a good plain-language expansion of what ADMS actually does versus SCADA.
• FLISR: the term used in this source (FLISR, common in North American/vendor literature) for the same automated-reconfiguration pattern already documented in the wiki under the European-literature term FDIR (from the Vattenfall self-healing ingest). Treated as synonyms — see the glossary entry.
• Kraftringen Nät: this essay used Kraftringen’s own driftledare/driftingenjör rotation as its example — Kraftringen’s own DNDP, filed the same month, independently corroborates the essay’s ADMS argument from the primary-source side. A rare same-company, same-window confirmation between a practitioner argument and a regulatory filing.