Ontology-Based Automation Integration for Subsystem Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software tools for modular automation systems lack interoperability, hindering their ability to assist engineers in process and automation engineering workflows due to disparate terminologies, data models, and operating systems, which prevents seamless integration and communication between subsystems.
Innovation Solution
The integration of automation engineering subsystems is achieved through the use of an ontological model that translates local terminologies to a common ontology, enabling horizontal and vertical integration, and facilitating communication and data exchange between heterogeneous subsystems via a semantic facilitation and integration layer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple heterogeneous automation engineering subsystems are integrated to provide comprehensive engineering capabilities, then the functionality and versatility of the system increases, but the complexity of integration and interoperability increases due to disparate terminologies, data models, and operating systems
Solution Approach 1:
The patent implements an integration subsystem that acts as an intermediary between heterogeneous automation engineering subsystems. This mediator translates and maps disparate terminologies, data models, and communication protocols into a unified framework, enabling seamless interoperability while maintaining the independence and functionality of each individual subsystem. The integration subsystem resolves terminology conflicts and data format inconsistencies without requiring modifications to the original subsystems.
2Ease of manufacture
If subsystems use their own local terminologies and data models to maintain independence and specialized functionality, then the ease of manufacture and deployment of individual subsystems improves, but the interoperability and communication capability between subsystems deteriorates
Solution Approach 1:
The patent creates a universal integration subsystem capable of interfacing with multiple different automation engineering subsystems simultaneously. This universal interface maintains the specialized functionality and local terminologies of each subsystem while providing a common communication framework that enables reliable interoperability. The integration subsystem adapts to various data models and protocols without requiring each subsystem to conform to a single standard.
3Reliability
If comprehensive data translation and mapping between subsystems is implemented to achieve seamless interoperability, then the communication capability improves, but the processing time and computational resources increase
Solution Approach 1:
The patent implements preliminary action by pre-defining terminology mappings, data model relationships, and translation rules in the integration subsystem before actual data exchange occurs. This preparatory configuration enables rapid translation and mapping operations during runtime, reducing processing time while maintaining comprehensive interoperability. The integration subsystem establishes communication protocols and data transformation rules in advance, avoiding computationally intensive real-time analysis.
Data Source
AI summary
A method performed by an integration subsystem for integrating a plurality of automation engineering subsystems into an aggregate system, the method comprising using at least one ontological model to interface a first said automation engineering subsystem with a second said automation engineering subsystem. Interoperability of the subsystems is therefore facilitated.


