Unified Query Interface for Multi-Source Data Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial software applications face challenges in efficiently integrating data from multiple databases with different structures and querying techniques, requiring numerous manual queries to retrieve relevant datasets.

Innovation Solution

A data integration system that accesses time series, event relational, and asset relational databases, allowing users to create graphical search templates to query data intuitively, generating reports based on user input and exporting data in formats like XML or JSON.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is retrieved from multiple databases with different structures using traditional methods, then data can be obtained, but the process requires a large number of individual queries and manual scripting

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidquery complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent combines multiple database queries into a single unified query operation. The system integrates data from time series databases, event relational databases, and asset relational databases through one consolidated query interface, eliminating the need for multiple separate queries and manual scripting operations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary layer (the unified query interface and integration system) that mediates between the user and multiple database sources. This intermediary handles the complexity of querying different database structures, translating user requests into appropriate queries for each database type without exposing complexity to the end user.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If traditional data retrieval methods are used across multiple database sources, then data can be collected, but the process becomes time-consuming and requires manual intervention

Engineering Contradiction:
Improvedata integration timeVSAvoidoperation simplicity
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The system performs preliminary actions by pre-establishing integration pathways and unified query interfaces between multiple database sources. This preparation work is done in advance, so when data retrieval is needed, the system can immediately execute consolidated queries without manual setup or sequential configuration of multiple query operations.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple individual queries are executed to retrieve data from different databases, then comprehensive data can be obtained, but the process requires manual scripting and data retrieval scripts

Engineering Contradiction:
Improvedata integration speedVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent creates a universal query interface that can handle multiple database types (time series, event relational, asset relational) through a single multi-functional system. This unified interface automatically adapts to different database structures and retrieves appropriate data without requiring separate scripting for each database type, thereby increasing both productivity and automation.

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

Data Source

PatentUS10360217B2Event based data collection, integration, and presentation
Publication Date: 2019.07.23 OSLSOFT LLC
  • US10360217B2 patent drawing
  • US10360217B2 patent drawing
  • US10360217B2 patent drawing

AI summary

A computer implemented method for data integration. An event relational database having a plurality of event frames related in a hierarchical structure is accessed. Each event frame representing a corresponding event within a corresponding timeframe. A graphical representation of the hierarchical structure of the event relational database is displayed in a graphical user interface. A user input is received selecting an event frame of the hierarchical structure from the graphical representation. A hierarchical search template is displayed based on the selected event frame of the hierarchical structure. The event relational database is searched with a search query corresponding to the hierarchical search template to identify one or more matching event frames of the hierarchical structure. The method also includes retrieving, from a time series database that includes time series data, a portion of the time series data corresponding to the one or more matching event frames.