Virtual I/O Switchover for Reconfigurable Process Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current industrial control systems face limitations in scalability, reconfigurability, reliability, and performance due to hardware-driven architectures, which restrict their ability to efficiently manage data and I/O operations, leading to issues with data archiving, communication resource utilization, and system responsiveness.

Innovation Solution

A multi-purpose hardware/software architecture decouples hardware from software, enabling dynamic simulation and run-time process control through a virtualized environment that abstracts I/O operations, allowing for easier scaling, reconfiguration, and improved reliability and availability by using virtual and physical components that cooperate for batch and continuous process control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hardware-driven architecture is used in process control systems, then system stability and reliability are maintained, but scalability and reconfigurability are limited

Engineering Contradiction:
ImprovereconfigurabilityVSAvoidhardware architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is segmented into virtualization management nodes, I/O servers, and virtual I/O components. Each segment operates independently but cooperates through standardized interfaces, allowing individual components to be modified, upgraded, or replaced without affecting the entire system. This segmentation enables reconfigurability while maintaining overall system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An I/O server acts as an intermediary layer between physical I/O devices and control software. This intermediary abstracts the hardware complexity, allowing the control system to interact with standardized interfaces rather than dealing with diverse hardware directly. The intermediary enables easier reconfiguration and scaling while maintaining reliable hardware connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If virtualized components are introduced to improve scalability and reconfigurability, then system flexibility increases, but communication overhead and data routing complexity increase

Engineering Contradiction:
ImprovescalabilityVSAvoiddata routing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The I/O server is designed as a universal component that can manage multiple types of I/O devices and support various communication protocols through a single standardized interface. This multi-functionality reduces the need for specialized routing logic for different device types, simplifying data routing while enabling scalable system expansion.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses configurable parameters and settings that can be adjusted through software rather than hardware modifications. Virtual I/O components can be dynamically configured with different parameters to adapt to changing system requirements, allowing scalability without increasing routing complexity through fixed hardware configurations.

Inventive Principle:
Principle #35Parameter changes

3Ease of repair

If node switchovers are performed in traditional control systems, then system maintenance is enabled, but switchover time and potential control disruptions increase

Engineering Contradiction:
Improvemaintenance accessibilityVSAvoidswitchover time
Core Design Contradiction:
Ease of repairVSLoss of time

Solution Approach 1:

Hot standby virtual I/O components are pre-configured and ready before any failure or maintenance event occurs. The virtualization management node maintains redundant virtual components that can immediately take over control functions, eliminating the need for time-consuming switchovers during maintenance or failure scenarios.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Virtual I/O components create software-based copies of physical I/O functionality that can be replicated and activated instantly. These virtual copies serve as immediate replacements during maintenance operations, allowing seamless transition without physical hardware intervention and minimizing control disruptions.

Inventive Principle:
Principle #26Copying

4Reliability

If physical and virtual components cooperate in the same control system, then system resilience and fault tolerance improve, but integration complexity and synchronization requirements increase

Engineering Contradiction:
Improvefault toleranceVSAvoidintegration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The virtualization management node implements continuous monitoring and feedback mechanisms that track the status of both physical and virtual components. This feedback system automatically detects failures, triggers appropriate switchovers, and coordinates synchronization between physical and virtual components, managing integration complexity through automated control rather than manual coordination.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system replaces physical hardware interconnections with software-based virtual connections. Virtual I/O components communicate with control software through standardized data interfaces rather than physical wiring, eliminating the need for complex mechanical integration while maintaining reliable communication between physical and virtual system elements.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11599100B2Ease of node switchovers in process control systems
Publication Date: 2023.03.07 FISHER ROSEMOUNT SYST INC
  • US11599100B2 patent drawing
  • US11599100B2 patent drawing
  • US11599100B2 patent drawing

AI summary

A Multi-Purpose Dynamic Simulation and run-time Control platform includes a virtual process environment coupled to a physical process environment, where components/nodes of the virtual and physical process environments cooperate to dynamically perform run-time process control of an industrial process plant and/or simulations thereof. Virtual components may include virtual run-time nodes and/or simulated nodes. The MPDSC includes an I/O Switch which delivers I/O data between virtual and/or physical nodes, e.g., by using publish/subscribe mechanisms, thereby virtualizing physical I/O process data delivery. Nodes serviced by the I/O Switch may include respective component behavior modules that are unaware as to whether or not they are being utilized on a virtual or physical node. Simulations may be performed in real-time and even in conjunction with run-time operations of the plant, and/or simulations may be manipulated as desired (speed, values, administration, etc.). The platform simultaneously supports simulation and run-time operations and interactions/intersections therebetween.