Industrial virtualization heads to the plant floor
End users are comfortable with virtualization in their information technology (IT) server rooms and desktops, and many similar benefits now can be realized with industrial programmable logic controllers (PLCs) and programmable automation controllers (PACs).
Commercially available technologies are almost always applied at a quicker pace in the consumer and information technology (IT) space than their industrial counterparts. For instance, virtualization technologies have been commonplace within IT environments, most often in server-based applications, for many years. On the other hand, industrial automation operations technology (OT) applications lagged by several years in adopting virtualization.
Today, virtualization has become mainstream for almost all OT products, practices, and applications, though it is still often used in computer-room environments. It is now common for OT system servers to host multiple virtual machines (VMs) for visualization, historian, redundancy and other uses.
Automation engineers use desktop-based virtualization to quickly create instances of development and testing systems. Virtualization provides benefits for quickly deploying systems, optimizing resource usage and backing up configurations.
The concepts and advantages of virtualization are commonly associated with PCs and servers, but they can be employed elsewhere. Recently, virtualization capability has been extended into more specialized and robust industrial programmable logic controllers (PLCs) and programmable automation controllers (PACs) used for process and machine automation.
This creates more options for end users, such as enabling analytics closer to the source of data. It also provides other benefits including enhanced productivity, efficiency and security.
A basic definition of virtualization is providing the ability to run more than one VM software operating system (OS) on a single hardware platform, allowing one physical computer to be more utilized as many virtual computers. Each VM must operate independently.
There are two types of virtualization, Type 1 and Type 2, depending on where the hypervisor is located. A hypervisor is the combination of hardware, firmware, and software running on the host machine and managing guest VMs.
Type 2 virtualization, which may be called “hosted,” is used for desktop and server PCs, with the hypervisor running on top of a traditional host OS already operating on the hardware. This creates virtual “sandboxes” where multiple OSs can run simultaneously, but it adds latency due to the underlying OS.
Type 1 virtualization, sometimes called “native,” utilizes a hypervisor running directly on the bare metal hardware without an underlying OS. The hypervisor partitions the hardware itself to each OS. This results in very low latency and jitter, which is ideal for real-time deterministic or time-sensitive applications. Type 1 offers greater performance than Type 2 because it has direct access to the hardware without delays due to a host OS system.
Until recently, virtualization has not been practical or possible at the plant floor level. Now, the development of a new class of PLCs and PACs leveraging multiple processor cores and virtualization offers the ability to extend the same virtualization concepts down into the industrial controller, providing an integrated approach.
Industrial controllers and virtualization
A common class of industrial controller for typical automation applications is the PLC, which has used a dedicated processor and specific real-time OS (RTOS) to provide high-speed deterministic control. The challenge to virtualizing PLC functions is maintaining high-speed determinism.
Today there are hardware advances common to the commercial PC world such as multicore processors and large memory. By using multicore technology and Type 1 virtualization, industrial controller platforms can now run multiple OSs on the same processor, including a RTOS for control which will experience little to no effect on the determinism and speed (Figure 1). A second Linux guest OS can be used for other edge processing. As the number of available cores increases in the future, even more OSs can be deployed.
For edge-located controllers, the possibility of running multiple OSs is a dramatic shift (Figure 2). The primary concern is maintaining a robust RTOS for control functionality, as with PLCs, so the automation functionality is not compromised. A secondary OS, operating as supplemental to the RTOS, provides additional computing options. The two OSs must be independent, but maintain the ability to interact.
The concept of running two OSs in an edge-located industrial controller can be further explained in terms of an “inner” and an “outer” loop, which may be familiar to users of cascaded process control loops (Figure 3). In this case, the inner loop is the RTOS VM for control, while the outer loop is a standard OS VM for added functions. For instance, the inner loop could monitor a process flow input, perform the proportional-integral-derivative (PID) calculations, and command the control valve output. The outer loop can advise the inner loop regarding the optimal flow rate, but it will not impact inner loop operation otherwise.
Another way of explaining the inner and outer loop concept is an analogy related to navigating a car. The inner loop is represented by the driver’s direct attention to drive the vehicle to its destination, while the outer loop could be the car’s dashboard navigation system providing supplementary information.
Therefore, the inner loop is mission critical and must always carry on operations without fail, even if the outer loop experiences a problem. On the other hand, the outer loop is valuable, but not essential, to basic system operation. The following sections explore this concept further.
Control remains the inner loop
PLCs provide the specialized functionality, robust packaging, and input/output (I/O) connectivity necessary to automate equipment and processes. These devices have gained processing power and networking capabilities to interact better with higher-level systems, with more advanced versions often called PACs. However, PLCs and PACs are still quite dedicated in their roles.
PLCs and PACs use many types of programming languages; ladder logic is the most popular. A basic measurement of PLC performance is how fast the controller can scan through the ladder logic, typically measured in milliseconds. All other overhead tasks must be handled so a deterministic scan time is preserved. The OS from a PC is not a good candidate for millisecond control because it must handle many overhead tasks such as graphics and user interface.
Superseding a PLC or PAC with a controller-based VM while maintaining the equivalent functionality requires the use of a RTOS. This RTOS provides the features needed for inner-loop PLC functionality without any performance-sapping features.
Extended capabilities live in the outer loop
Since control functionality remains essentially the same, the real advantage to controller virtualization is the addition of an outer-loop Linux VM carefully integrated in a cooperative manner. This VM can do anything a dedicated PC could, but at a lower cost, and packaged in a more compact form factor, with no need to integrate a PC to the controller.
It is not necessary for industrial users to take advantage of the extra OS right away, as they could use a virtualized controller for the basic PLC functionality. However, many users are finding a general-purpose Linux OS at the edge can enhance their applications by:
- Running machine learning elements
- Performing analytics
- Communicating to the cloud
- Using messaging queuing telemetry transport (MQTT) or some other publish-subscribe model to exchange information
- Executing optimization calculations to inform the controller VM
- Driving a local display
- Serving web pages.
These functions have required upstream computing resources. Users benefit from the efficiency of implementing these functions out at an edge-located OS, because they are taking advantage of locally available processing power and acting on the data as close to the source as possible. This removes layers of computing and streamlines networking usage. The ability to drive a local display or directly serve web pages out of the controller are examples of this.
Some of these functions are possible in standard PLCs today, but adding these capabilities into a traditional PLC must be carefully performed to prevent overloading. Also, when advanced features are added in a traditional PLC, it means users must work in the active control environment to make changes, which increases the risk of disrupting automation.
When implemented properly, an outer loop VM lets users safely perform processing out at the edge closer to the source of data, which unloads upstream networking and processing requirements.
Other controller virtualization considerations
Maintaining segregation between the RTOS and general-purpose OS in a virtualized industrial controller has been stressed for performance and security reasons, but the VMs still must have a means for interacting with each other and the outside world. Two tactics make this possible.
The first is to design the controller with separate Ethernet ports, each dedicated to a certain VM OS and isolated from others, which provides security by eliminating the possibility of a port accessing a VM other than what it is tied to. Typically, the RTOS port would be used for I/O communications while the OS port would be used for connections to the outside world. Isolated Ethernet ports ensure cyber-attacks on the OS network from the outside world can’t affect the RTOS network. This same concept extends to other hardware interfaces such as USB ports. The Type 1 virtualization hypervisor makes it possible to divide the hardware between VMs in this way.
Secondly, virtualized PLCs and PACs should be configured to allow VMs to interact only via standard predefined interfaces, such as a virtual network interface card running a secure protocol between the two VMs. In the industrial setting, OPC UA is becoming the platform of choice for secure protocols.
Using this method, the RTOS VM can provide field information to the OS VM, and the OS VM can inform the RTOS VM. This is a user-defined data exchange, with users exposing only essential data between the two VMs and performing any validation necessary to ensure robust RTOS operation.
Future-proofing through controller virtualization
Virtualized PLCs and PACs provide device consolidation at the edge, which in turn delivers performance gains and cost savings. Optimization configured at the edge results in smarter and more efficient machines while simplifying the architecture. Users can create impacting analytics executed at the edge, and update or upgrade these and other applications without impacting the actual control process. This is a safer approach than modifying the “always on” code of operating PLCs.
End users often prefer the controller virtualization approach because it gives them the same controller-type functionality they need and use today, while adding an optional layer of computing. This future-proofs their designs because they can grow as needed without expensive hardware replacement.
Some users see controller virtualization as analogous to their smartphones, which are first and foremost a phone, but also offer many other useful functions added as extra apps. This type of future-proofing ensures current investments will be protected without the need to predict the exact path of upcoming OT and IT advancements.
Keywords: Virtualization, PLC, PAC
Virtualization can deploy systems, optimize resource usage and back up configurations on the plant floor.
There are two types of virtualization: Hosted and native, which can be used depending on specific plant-floor needs.
End users prefer virtualization because it future-proofs their designs and saves them from committing to expensive hardware replacements.
What benefits would your plant floor see from virtualization?