Process Module Logic Interface for Flexible Plant Diagnosis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The interaction between process control systems and process modules is inflexible, as existing systems only have information on the services provided by each module through its interface, making diagnosis and configuration challenging, especially when modules from different vendors have varying target-specific control codes.
Innovation Solution
A process control system configured to communicate with process modules via a process module interface, incorporating a process module logic entity that provides control logic, allowing for diagnosis and configuration procedures that map process module values to control logic, and presenting this logic through a graphical user interface, enabling identification of errors and implementation of control functions without relying on vendor-specific control codes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If vendor-specific control codes are used for each process module, then the control logic can be precisely implemented for each module, but the system becomes inflexible and difficult to diagnose across different vendors' modules
Solution Approach 1:
The patent introduces an intermediary layer between the process control system and vendor-specific control codes. This intermediary translates and standardizes communications between the control system and different vendors' modules, allowing precise control to be maintained while enabling flexibility across multiple vendors. The intermediary acts as a mediator that handles vendor-specific variations without exposing them to the main control system.
Solution Approach 2:
The control system is segmented into distinct layers: a standardized interface layer that handles vendor-specific control codes and a core control logic layer that remains vendor-agnostic. This segmentation allows the system to maintain precise control through standardized interfaces while adapting to different vendors' specific implementations through the segmented interface layer.
2Ease of manufacture
If detailed control logic is hidden within each process module, then vendor-specific implementations are protected, but diagnosis and configuration become challenging
Solution Approach 1:
The patent implements feedback mechanisms that provide information about the control logic execution and module status back to the operator interface. This feedback enables operators to diagnose issues by observing control logic behavior without exposing the actual vendor-specific code, thus maintaining module independence while improving diagnosability through observable feedback signals.
Solution Approach 2:
Instead of exposing actual vendor-specific control codes, the system creates and uses standardized representations or copies of the control logic at the interface level. These copies allow diagnosis and configuration operations to be performed on standardized models rather than proprietary code, making troubleshooting easier while preserving the original vendor-specific implementations.
3Ease of operation
If a standardized interface is used for all process modules, then system integration is simplified, but vendor-specific control functionalities may be lost
Solution Approach 1:
The patent implements a universal standardized interface that can handle multiple vendor-specific functionalities through a common communication protocol. The standardized interface is designed to be multi-functional, accommodating different vendors' control codes and modules while maintaining a uniform interface structure, thus achieving both integration ease and preservation of vendor-specific functionalities.
Solution Approach 2:
The system uses parameter changes to adapt the standardized interface to vendor-specific requirements. By dynamically adjusting interface parameters based on the connected module type, the system maintains a consistent standardized interface structure while configuring it to handle specific vendor functionalities, thus preserving control functionality without sacrificing integration simplicity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The disclosure describes an apparatus (100) comprising a process control system (10); at least one process module (50, 60); and a process module logic entity (26) associated with the at least one process module (50, 60), wherein the process control system is configured to communicate with the at least one process module (50, 60) via a process module interface; and wherein the process module logic entity (26) provides a control logic of the process module (50, 60). The disclosure also relates to a method comprising providing an apparatus (100) or providing a model of an apparatus (100) as described, the method further comprising reflecting the control logic of the process module (50, 60) in a procedure, typically in a diagnosis procedure or in a configuration procedure. Yet further, the disclosure relates to corresponding computer program product and a corresponding data processing device.