Modular Control Architecture Using a Common Data Model
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing control systems for complex technical systems, such as infrastructure networks, often require specific and rigid integration of assistance functions, limiting their flexibility and ability to optimize system responses effectively due to simplified numerical evaluations and complex data structures.
Innovation Solution
A method and arrangement where multiple independently operable functional modules access a common data model, comprising an interface, simulation, and output module, allowing for flexible control of technical systems by reducing reciprocal dependency between modules and enabling modular integration of monitoring, forecasting, and optimization functions without direct data interchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If assistance functions are specifically integrated into control engineering and control sequence, then system response optimization is achieved, but flexibility and adaptability to different applications are reduced
Solution Approach 1:
The control system is divided into independent functional modules (interface module, simulation module, output module, data-analytical modules) that can be selectively activated. Each module performs a specific function and accesses the common data model independently, allowing the system to be configured for different applications by enabling/disabling modules rather than requiring complete reintegration.
Solution Approach 2:
The common data model serves as a universal interface that all functional modules access using the same selection-data-specific mechanism. This universal data access structure allows the same core architecture to support multiple different control applications and configurations without requiring application-specific integration for each case.
2Reliability
If numerical evaluations and optimizations operate iteratively on complex data structures, then system optimization is achieved, but system complexity and computational burden increase
Solution Approach 1:
The common data model acts as an intermediary layer between the interface module (which captures raw operating data) and the simulation and data-analytical modules. This standardized intermediate structure simplifies data access patterns and reduces the complexity of data handling in iterative optimizations, as all modules access data through the same unified interface rather than requiring complex direct data interchange.
Solution Approach 2:
Complex computational tasks are segmented into separate functional modules (simulation module for dynamic response calculation, independent data-analytical modules for specific analyses). Each module performs its optimization or analysis independently by accessing the common data model, reducing the overall computational complexity compared to a monolithic iterative optimization system.
3Ease of operation
If functional modules require direct data interchange among one another, then comprehensive control functionality is achieved, but reciprocal dependency and integration complexity increase
Solution Approach 1:
The common data model serves as a mediator that enables all functional modules to access and share data without requiring direct inter-module communication. The interface module stores operating data in the common data model, and all other modules (simulation, output, data-analytical) access this data through the standardized interface, eliminating the need for direct data interchange between modules and reducing reciprocal dependency.
Data Source
AI summary
To control a technical system having multiple system components, multiple functional modules access a common data model. The functional modules in this case include an interface module, a simulation module and an output module. The data model includes data components associated with the system components and simulation model data for a simulation model of the technical system. The functional modules are actuated by a flow controller, wherein the flow controller and a respective functional module have functional-module-specific selection data transmitted between them that the respective functional module takes as a basis for accessing model data of the data model. The interface module continually captures operating data of the technical system and stores them in the data model by means of selection-data-specific access.