Data Conversion Gateway for Incompatible Automation Databases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In industrial automation systems, field devices produce data that are often stored in proprietary databases, making it difficult to achieve synergistic effects due to incompatibility between different cloud-capable databases, which limits data exchange and integration.

Innovation Solution

A method and data conversion unit that retrieve and convert data from one cloud-capable database to another with a different configuration, enabling the transmission and storage of field device-related data across incompatible databases, allowing access to data from multiple sources through a data conversion unit acting as an edge device or gateway.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If proprietary databases are used for storing field device data, then data storage and management are simplified for individual systems, but data exchange and integration between different systems become difficult

Engineering Contradiction:
Improvedata storage and managementVSAvoiddata exchange and integration
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces a data conversion unit as an intermediary component that mediates between proprietary databases with different data configurations. This converter translates data between incompatible formats, enabling exchange between systems while each system maintains its own proprietary database structure. The converter acts as a bridge that resolves the contradiction by allowing both individual system simplicity and cross-system integration.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data conversion units are deployed to enable data exchange between incompatible databases, then data integration capability is improved, but system complexity increases

Engineering Contradiction:
Improvedata integration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The data conversion unit is designed with universal functionality to handle multiple proprietary database formats and configurations. Rather than requiring separate conversion tools for each database pair, a single multi-functional converter can translate between various data configurations, reducing overall system complexity while maintaining high integration capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If multiple proprietary databases are maintained for different field devices, then each database can be optimized for its specific purpose, but synergistic effects between different databases cannot be achieved

Engineering Contradiction:
Improvedatabase optimizationVSAvoidsynergistic effects
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The data conversion unit enables synergistic effects by mediating between optimized proprietary databases. Each database can remain specialized and optimized for its specific field devices, while the converter allows cross-referencing, data correlation, and integrated analysis across different databases, achieving productivity benefits without compromising individual database optimization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11514018B2Method and data conversion unit for monitoring an automation system
Publication Date: 2022.11.29 ENDRESS HAUSER PROCESS SOLUTIONS AG
  • US11514018B2 patent drawing

AI summary

The invention includes a method for monitoring an automated plant having at least one field device, wherein a first cloud-capable database, having a first data configuration and containing field device related data including measured values, parameter values, identification data, and diagnostic status of the field device, wherein a second cloud-capable database having a second data configuration incompatible with the first data configuration, and wherein the first and the second data configurations define file formats of the data, the method comprises: retrieving at least a part of the data contained in the first database by means of a data conversion unit, especially an edge device or a gateway; converting the retrieved data into a format conforming to the second data configuration; and storing the converted data in the second database. The invention further includes a data conversion unit, which is embodied for executing the method of the invention.