Object Meta-Model for Automation System Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automation systems require multiple independent software programs for management, leading to complex and difficult-to-use global architectures due to lack of interoperability between tools for control, monitoring, and supervision, which complicates user interaction and integration.
Innovation Solution
A software system based on an object meta-model that allows independent software tools to cooperate within a unified architecture through a single object meta-model, enabling both functional and topological descriptions of automation systems, with composite objects and interfaces for mapping and communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple independent software programs are used to manage different aspects of automation systems, then each program can specialize in specific functions (control, monitoring, supervision), but the overall system complexity increases and interoperability between tools becomes difficult
Solution Approach 1:
The patent implements a universal object meta-model that serves multiple functions: it provides both topological description (hardware configuration) and functional description (control logic, monitoring, supervision) within a single framework. This allows the same data structure to support multiple software tools without requiring separate specialized programs, thereby reducing integration complexity while maintaining functional versatility.
Solution Approach 2:
The object meta-model acts as an intermediary layer between hardware components and software applications. By introducing this standardized intermediate representation, the patent enables different software tools (control systems, monitoring systems, supervision systems) to interact through a common interface, eliminating the need for complex direct integrations between multiple specialized programs.
2Adaptability or versatility
If independent software tools are designed separately for control, monitoring, and supervision, then each tool can be optimized for its specific function, but the ease of operation deteriorates due to difficulty in interconnection and integration
Solution Approach 1:
The unified object meta-model enables a single software environment to handle multiple functions (control, monitoring, supervision) that were previously required separate specialized tools. Users can access all these functions through one integrated interface rather than switching between multiple independent programs, significantly improving ease of operation while preserving functional optimization through the modular object structure.
3Device complexity
If a unified software architecture is implemented using a single object meta-model, then integration and interoperability improve, but the adaptability to handle diverse functional and topological descriptions may be compromised
Solution Approach 1:
The patent segments the automation system description into distinct object types (hardware objects, functional objects, composite objects) within the unified meta-model. Each object type has specific attributes and behaviors tailored to its function, allowing the system to handle diverse topological and functional descriptions while maintaining a single integrated architecture. This segmentation enables the unified model to adapt to different description requirements without compromising integration benefits.
Solution Approach 2:
The object meta-model uses parameterization to accommodate diverse functional and topological descriptions. By defining configurable parameters and attributes for different object types, the unified architecture can adapt to various automation system configurations and requirements. The model can represent both simple and complex systems by adjusting parameters rather than requiring different architectural approaches, thus maintaining both unity and versatility.
Data Source
AI summary
Managing an automation system that includes software requires a projects manager, an applications manager, and a topologies manager. The applications manager includes a single object-oriented functional description of the automation system based on an object meta-model. The functional description includes a plurality of composite functional objects, each of which further include a monitoring facet and a supervision facet. The monitor facet and the supervision facet each include a mapping interface. The topologies manager includes an object-oriented topological description of the automation system based on the object meta-model, and includes a plurality of topological objects. The projects manager includes a monitoring project and a supervision project which relate to the automation system. Monitoring facets are assigned to the monitoring project and supervision facets are assigned to the supervision project. Part of the topological objects are mapped with the monitoring facets and the supervision facets via mapping interfaces.