Orchestration Layer for Modular Plant State Change Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing modular technical systems face challenges in efficiently orchestrating technical modules due to complex interactions and dependencies, leading to inflexibility and increased communication loads.
Innovation Solution
A computer-implemented orchestration body that reads input variables from technical modules, determines additional variables based on module conditions, and enables or prevents state changes through a trigger system, acting as a middleware between operators and technical modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If technical modules are orchestrated using classic automation engineering concepts with detailed communication links and process sequences, then the system can achieve precise control and coordination, but the implementation becomes complex and difficult due to lack of relevant knowledge among process engineers
Solution Approach 1:
The patent introduces an intermediary layer (the orchestration system with standardized interfaces) between the process engineers and the complex automation control mechanisms. This intermediary handles the complexity of communication links and process sequences internally while presenting a simplified interface to users, thus maintaining control precision without requiring engineers to master complex automation concepts
Solution Approach 2:
The patent segments the orchestration system into modular components with standardized interfaces (such as the Module Type Package concept). Each technical module is divided into independent, self-describing units that can be orchestrated through standardized mechanisms, reducing the overall complexity while maintaining precise control through structured composition
2Adaptability or versatility
If the plant is modified by removing and replacing individual modules to respond to changing market conditions, then the time-to-market can be significantly shortened and flexibility improved, but the orchestration of modules becomes more complex due to increasing numbers of modules and their interactions
Solution Approach 1:
The patent implements universal standardized interfaces (such as those defined in VDI/VDE/NAMUR 2658) that allow different technical modules to be orchestrated through common mechanisms. This universality enables flexible plant modifications while keeping orchestration complexity manageable, as the same standardized interfaces handle both simple and complex module compositions
3Adaptability or versatility
If granular functions are offered by technical modules to enable flexible orchestration, then larger functions can be assembled more flexibly, but more effort is required for coordination and engineering of these granular functions
Solution Approach 1:
The patent applies preliminary action by pre-defining standardized interfaces and communication protocols (such as the Module Type Package) before the actual orchestration takes place. This preliminary standardization reduces the engineering effort required later when assembling granular functions, as the coordination mechanisms are already established and documented
Data Source
Figure 1
Figure 2
AI summary
A computer-implemented orchestration instance (9) is proposed for orchestrating at least one technical module (2, 3) within a technical plant (1), in particular a process or manufacturing plant, which is configured to: - read an input variable (10, 11, 13, 14) from the technical module (2, 3), which input variable (10, 11, 13, 14) indicates a readiness of the technical module (2, 3) to change a state of the technical module (2, 3); - determine another variable whose value depends on one or more further states, values, or other variable data of the technical module (2, 3) or one or more further technical modules (2, 3); - upon the presence of certain combinations of values of the input variable (10, 11, 13, 14) and the further variable, trigger a change in the state of the technical module (2, 3) from outside the technical module (2, 3). to enable or prevent modules (2, 3).