What Do Virtualization and SEAPATH Really Change for RTE?
Event Recap: LF Energy Summit Europe 2025
TL;DR
At LF Energy Summit Europe 2025, Bastien Desbos (RTE) presented how RTE is using SEAPATH to virtualize protection, automation, and control (PAC) systems. By running virtual machines on a three-server cluster, virtualizing functions results in less dedicated hardware, enables VM-level redundancy, and moves from turnkey supplier-specific systems toward interoperable architectures relying on standards such as IEC 61850.
Presentation Overview
Desbos began by outlining RTE’s historical PAC strategy. From 2000 to 2020, substations were delivered as turnkey systems from individual suppliers. Even with shared specifications, each supplier implemented solutions differently. System evolution required contracting changes separately across suppliers, increasing cost and rigidity for systems designed to last around 25 years.
RTE’s current approach aims for a single interoperable architecture using multi-supplier hardware. Integration is performed in-house and relies on standards such as IEC 61850. Servers are introduced into the PAC architecture, and key functions are virtualized.
Three virtualization approaches were considered: a full stack from one supplier, a proprietary virtualization layer, and an open source stack. RTE selected the open source path, using SEAPATH, to maintain transparency and control at the virtualization layer and reduce dependency on a single vendor.
In the RSpace program architecture described, RTE runs a cluster of three servers. On this cluster, RTE virtualizes:
-
Local HMI
-
Gateway / remote terminal unit
-
Internal automation, such as breaker failure logic
-
FTP services for remote fault recording retrieval
-
IED configuration tools
The stack described uses a Debian-based flavor on SEAPATH, KVM for virtualization, and automated deployment tooling.
A key operational change is redundancy. Rather than duplicating physical devices, virtual machines can restart on another server in the cluster if a server fails. Desbos cited a failover time of about one minute. This enables redundancy for more functions and provides greater remote visibility into system status, which RTE expects will reduce the need to send someone on site.
RTE currently has three substations running this architecture, with additional deployments planned. The next step under evaluation is the virtualization of protection functions. RTE launched a tender asking historical partners whether protection algorithms could be supplied as virtual machines and is currently testing with two partners, with completion planned next year.
Challenges discussed include integration across components, managing vendor lock-in at the software level, and long-term maintainability across servers, virtualization infrastructure, and applications.
FAQ
What is being virtualized?
Local HMI, gateway/RTU, automation functions, fault recording access, and configuration tools are running as virtual machines on a three-server cluster.
What redundancy model is used?
If a physical server fails, the affected virtual machine restarts on another server in the cluster, with an estimated failover time of about one minute.
Is protection being virtualized?
RTE is currently testing protection algorithms delivered as virtual machines by two partners.
About LF Energy
LF Energy is an open source foundation within the Linux Foundation focused on advancing collaboration in digital energy infrastructure.
Learn more: https://lfenergy.org
Last updated: February 26, 2026
