Field Device Data Conversion for Incompatible Automation Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in managing and synchronizing data across cloud-enabled databases that are not compatible with each other, limiting synergy effects and data exchange between different databases in industrial automation systems.
Innovation Solution
A method that utilizes a data conversion unit to retrieve, convert, and transmit data between incompatible cloud-enabled databases, allowing bidirectional data synchronization and enabling access to field device data from any connected database, regardless of its configuration, through a data conversion unit that communicates like a conventional edge device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in multiple proprietary databases with different data configurations, then data can be stored and accessed within each database, but data exchange between databases becomes impossible or very difficult
Solution Approach 1:
The patent introduces a data conversion unit that acts as an intermediary between incompatible databases. This unit converts data from the first database's configuration to the second database's configuration, enabling data exchange without requiring changes to the databases themselves. The conversion unit translates data formats, structures, and protocols to bridge the incompatibility gap.
Solution Approach 2:
The patent changes the data configuration parameters through the data conversion unit. It transforms data from one configuration format to another by modifying parameters such as data structure, encoding, and format. This allows the same data to be represented in multiple configurations compatible with different databases.
2Adaptability or versatility
If data conversion is implemented between databases, then data exchange becomes possible, but system complexity increases
Solution Approach 1:
The data conversion unit is designed as a standardized intermediary component that can be integrated into existing database systems without fundamentally altering them. By concentrating the conversion logic in a separate, modular unit, the complexity is isolated and managed independently from the core database systems.
Solution Approach 2:
The data conversion unit is designed with universal functionality to handle multiple database configurations and data formats. Rather than creating separate conversion mechanisms for each database pair, a single multi-functional conversion unit can adapt to various configurations, reducing overall system complexity.
3Ease of manufacture
If proprietary databases are used by different manufacturers, then each manufacturer can optimize their database for their specific applications, but synergy effects between different implementations become very difficult to achieve
Solution Approach 1:
The data conversion unit enables parameter changes between different database configurations, allowing each manufacturer to maintain their optimized proprietary formats while still enabling data exchange. The conversion process transforms parameters such as data structure, encoding, and format to bridge different implementations.
Solution Approach 2:
The conversion unit acts as a mediator that preserves the integrity of each manufacturer's proprietary database while enabling synergy effects through standardized data exchange. It allows collaborative applications to access and process data from multiple sources without requiring changes to the original database implementations.
Data Source
Figure 1~2
AI summary
The invention relates to a method for monitoring an automation system (A), in which system at least one field device (FG) is used, wherein a first database (DB1), in particular a cloud-capable database, has a first data configuration and contains field-device-related data, in particular measurement values, parameter values, identification data, and/or a diagnosis status of the field device (FG), a second database (DB2), in particular a cloud-capable database, has a second data configuration that is not compatible with the first data configuration, and the first and second data configurations define the file format of the data, or the semantics thereof and/or rules for organization and/or for storage of the data in the first and second databases (DB1, DB2), respectively, comprising: retrieving at least some of the data contained in the first database (DB1) by means of a data conversion unit (DE1), in particular an edge device or a gateway; converting the retrieved data into a format compliant with the second data configuration; and storing the converted data in the second database (DB2). The invention further relates to a data conversion unit designed to carry out the method according to the invention.