Cross-Version Schema Matching for Distributed Data Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial plants with multiple entities and control software solutions face challenges in maintaining data consistency and compatibility across different software systems, leading to time-consuming and error-prone manual reconciliation processes.

Innovation Solution

A computer-implemented method for automatically converting data representations into data queries in a distributed data storage system, using an initial data storage model and derived sub-models, with conversion rules to align data formats and units, and providing a quality parameter for information loss tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual reconciliation processes are used to maintain data consistency across different software systems, then data compatibility can be maintained, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improvedata consistencyVSAvoidreconciliation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical reconciliation processes with an automated computer-implemented system. The conversion module automatically converts data representations between different data models using predefined conversion rules, eliminating the need for manual data matching and reconciliation across heterogeneous software systems.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces an intermediary conversion module that acts as a mediator between different data models. This module contains predefined conversion rules that automatically translate data representations between source and target data models, facilitating seamless data exchange without manual intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual reconciliation processes are used to maintain data consistency across different software systems, then data compatibility can be maintained, but the process becomes error-prone

Engineering Contradiction:
Improvedata consistencyVSAvoidreconciliation effort
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent replaces manual mechanical reconciliation processes with an automated computer-implemented system. The conversion module automatically converts data representations between different data models using predefined conversion rules, eliminating the need for manual data matching and reconciliation across heterogeneous software systems.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service data reconciliation through automated conversion. The conversion module autonomously performs data representation conversion without requiring manual intervention, making the system self-sufficient in maintaining data consistency across different software solutions.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If data formats and units are standardized across all software solutions, then data compatibility improves, but system flexibility and adaptability decrease

Engineering Contradiction:
Improvedata compatibilityVSAvoidsystem heterogeneity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary conversion module that acts as a mediator between different data models. This module contains predefined conversion rules that automatically translate data representations between source and target data models, facilitating seamless data exchange without manual intervention while preserving system heterogeneity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent dynamically changes data representation parameters through automated conversion. The system transforms data between different representations based on the target data model requirements, allowing flexible adaptation to various software solutions without forcing standardization across the entire system.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If automatic conversion is implemented between data representations, then productivity improves, but conversion accuracy may be compromised

Engineering Contradiction:
Improvedata conversion efficiencyVSAvoidconversion accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent performs preliminary actions by pre-defining conversion rules for common data representation transformations. These predefined rules are stored in the system and automatically applied during conversion operations, ensuring both efficiency and accuracy by leveraging established conversion patterns.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms to verify conversion accuracy. The conversion module monitors and validates data transformations, ensuring that converted data maintains its integrity and accuracy while achieving high productivity through automation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4708065A1Automatic cross- version schema matching for data requests in distributed data retention systems
Publication Date: 2026.03.11 SIEMENS AG
  • EP4708065A1 patent drawingFigure 1
  • EP4708065A1 patent drawingFigure 2
  • EP4708065A1 patent drawingFigure 3~5

AI summary

The invention relates to a computer-implemented method, a computer-implemented device, a system, and a computer program product for automatically converting a data representation into data requests to a distributed data storage system, comprising providing an initial data storage model as part of the distributed data storage system, which contains information about a data representation associated with the initial data storage model; providing a different sub-model derived from the initial data storage model as part of the data storage system, which contains information about a data representation associated with the derived sub-model; receiving a data request, comprising a request to provide data from the distributed data storage system and at least one parameter indicative of a data storage model of the requested data; and loading the requested data from the distributed data storage system.Converting the loaded data from a data representation associated with a data storage model of the loaded data into a data representation according to the data storage model requested by the data request, if the requested data storage model does not match the stored data storage model, and providing the converted data.