The challenge is that existing standards assume a single unit of hardware and software, while virtualization separates the two. We are therefore working closely with notified bodies on this.

Our solution follows an "out-of-the-box" approach: our Virtual PLCnext Control is installed on generic hardware. Many of our customers use IPC or embedded platforms with a hypervisor or a container runtime environment as their base system. On top of that runs our virtual PLCnext Control, combined with additional containers for AI, data acquisition, or communication. This results in highly flexible architectures, and suddenly we’re in dialogue with traditional device manufacturers.

Do users need specific hardware for the Virtual PLCnext Control?

On the contrary – the goal is hardware freedom. However, on demand we qualify customer hardware, especially for series projects, to ensure stable operation. We also offer our own ultra-compact IPC with a preinstalled Virtual PLCnext Control.

Any container can be installed on it, such as our AI solution "MLnext" or systems for asset and device management. The whole setup is modular, like a Lego system – the customer combines their own building blocks with ours.

Does this mean the classic PLC is disappearing?

Definitely not. The virtual controller complements the classic PLC – it doesn’t replace it. There will always be machines that don’t require complex communication or IT integration. For simple, cost-sensitive applications with manageable I/O structures, the classic PLC remains ideal.

Virtualization always requires a certain level of hardware performance, even if implemented efficiently. For very small or highly encapsulated systems, it often makes little sense – those will continue to use traditional controllers.

What role does your own ecosystem PLCnext Technology and app store play?

There are apps that run inside the Virtual PLCnext Control and others that operate in parallel. Whether an app runs internally or externally depends on the desired level of integration.

So, you always need some IT know-how?

Correct. You don’t have to be a software developer, but a basic understanding of IT and container technologies is necessary.

How do you promote IT-OT convergence and mutual understanding between IT and OT teams?

It’s a cultural issue. IT and OT often pursue different goals: IT focuses on security, orchestration, and update cycles, while OT focuses on deterministic processing and availability. These worlds need to come together – otherwise friction is inevitable.

Communication is key: both sides must understand why the other acts the way it does.

Phoenix Contact at SPS 2025: Hall 9 Stand 310