Process Module Logic Interface for Flexible Control Code Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In process engineering plants, the interaction between process control systems and process modules is often inflexible, making it difficult to diagnose and configure modules, especially when modules from different vendors provide similar functions but require target-specific control codes, which are not interchangeable.
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 flexible interaction and enabling diagnosis and configuration procedures through a graphical user interface, independent of target-specific control codes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If target-specific control codes are used for process modules from different vendors, then the process modules can be controlled to perform specific tasks, but the control codes are not interchangeable and require separate configuration and engineering for each module
Solution Approach 1:
The patent implements a universal control code structure that can be applied across multiple process modules from different vendors. The control code is designed with a standardized format that includes vendor-specific and module-specific parameters, allowing the same control code template to be reused across different module types while maintaining the ability to perform specific tasks. This eliminates the need to engineer separate control codes for each module.
Solution Approach 2:
The control code structure uses parameterization to accommodate different module types. By changing specific parameters within the standardized control code framework (such as vendor ID, module type, and task-specific parameters), the same control code can be adapted to control different process modules without requiring complete re-engineering. This allows flexible configuration while maintaining code reusability.
2Adaptability or versatility
If process modules from different vendors are integrated into a single process control system, then customization and economic production are enabled, but the interaction becomes inflexible and diagnosis becomes difficult
Solution Approach 1:
The control code is segmented into distinct sections: a standardized header portion that identifies the vendor and module type, and a task-specific portion that defines the operation. This segmentation allows the process control system to universally recognize and diagnose different module types through the standardized header while maintaining the ability to perform vendor-specific tasks through the task-specific portion.
Solution Approach 2:
The patent introduces an intermediary standardized control code structure that mediates between the process control system and diverse process modules. This intermediary layer provides a common interface that simplifies diagnosis and configuration by the process control system while still enabling communication with vendor-specific modules through the embedded vendor and module type information.
3Manufacturing precision
If vendor-specific control codes are used for each process module, then each module can be precisely controlled, but the control code engineering must be repeated for each module
Solution Approach 1:
The patent enables copying of standardized control code templates across multiple process modules. Once a control code template is created with the appropriate vendor and module type parameters, it can be copied and reused for controlling similar modules from the same vendor, eliminating the need to re-engineer control codes for each module while maintaining precise control through the parameterized structure.
Data Source
AI summary
An apparatus includes: a process control system; at least one process module; and a process module logic entity associated with the at least one process module. The process control system communicates with the at least one process module via a process module interface. The process module logic entity provides a control logic of the at least one process module.