Heterogeneous Execution Engines in Network Centric Process Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current process controllers are limited in executing control logic and data exchange across different types, requiring specific communication protocols and significant engineering efforts for inter-controller communication, which hinders the integration of legacy and new control logic.
Innovation Solution
A network-centric process control system with heterogeneous execution engines, utilizing a middleware service and communication components that allow nodes to use the same communication protocol for vertical communication, enabling existing control logic to coexist and exchange data without requiring controller-to-controller engineering, by identifying components through namespace IDs and sending entity values for runtime data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If controller-to-controller communication is engineered for each controller type pair, then data exchange between different controller types is enabled, but engineering effort and system complexity increase significantly
Solution Approach 1:
The patent implements a universal communication protocol that enables all controller types to exchange data using the same protocol, eliminating the need for separate communication engineering for each controller type pair. The protocol is designed to be type-agnostic, allowing any controller to communicate with any other controller through standardized interfaces and message formats.
Solution Approach 2:
The patent introduces a message broker or communication intermediary that facilitates data exchange between controllers of different types. This intermediary translates and routes messages between controllers using a standardized protocol, eliminating the need for direct point-to-point communication engineering between each controller pair.
2Reliability
If specific control engines are used for each controller type, then control logic execution is optimized for that controller type, but integration of legacy and new control logic becomes difficult
Solution Approach 1:
The patent segments the control system into independent control logic units that can be executed by different control engines. Each control logic unit is designed with standardized interfaces, allowing it to be migrated between different controller types and execution engines without modification, thus enabling seamless integration of legacy and new control logic.
Solution Approach 2:
The patent employs parameter-based configuration where control logic behavior is defined through standardized parameters and interfaces rather than hard-coded implementations. This allows the same control logic to be adapted to different controller types by changing parameters, enabling legacy control logic to run on modern controllers with different hardware architectures.
3Productivity
If legacy controllers are upgraded to modern hardware, then system performance and features improve, but existing control logic may not be compatible with new execution engines
Solution Approach 1:
The patent creates abstracted representations or models of legacy control logic that can be executed on modern control engines. Instead of directly porting legacy code, the system copies the essential behavior and logic structure into a standardized format that can run on new hardware while preserving the original control intent and functionality.
Solution Approach 2:
The patent performs preliminary abstraction and standardization of control logic during the upgrade process, before deployment to new hardware. This preliminary action ensures that control logic is prepared in a format compatible with modern execution engines, preventing compatibility issues after the upgrade and enabling seamless transition to new hardware platforms.
Data Source
AI summary
A method for heterogeneous execution engines in a network centric process control system. The network centric process control system includes a plurality of nodes and each node includes one or more control service components, a middleware service component, a middleware API subcomponent, an address space subcomponent, and a communication component, where each control service component, middleware service component, and communication component is a separate executable running in a separate operating system process as provided by a real time operating system of each node. The method is performed by the network centric process control system, and includes identifying, by the communication component, a component of a node of the network centric process control system by an indication of a namespace ID of the component, forwarding, by the communication component, a request to the address space subcomponent of the identified component, wherein an item ID for runtime data of the identified component indicates an entity in the address space corresponding to the runtime data, and sending, by the communication component, an entity value, wherein the entity value corresponds to the requested runtime data. A network centric process control system, a computer program, and a computer program product for heterogeneous execution engines are also presented.