Historian Query Retrieval Using Summary Data Alignment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for retrieving data in industrial process control environments are inefficient, leading to excessive processor resource utilization and network bandwidth consumption, particularly due to cyclical retrieval services that process large volumes of data.

Innovation Solution

The implementation of an operational historian system that includes a replication component to generate summary data values from source data and a retrieval component to determine whether to retrieve source or summary tag data based on query cycle duration, thereby optimizing data retrieval and reducing unnecessary resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional cyclical retrieval services are used to retrieve process data, then data can be obtained from the system, but processor resources and network bandwidth are excessively utilized

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidprocessor resource utilization
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments the data retrieval process into two distinct paths: one for summary data and one for source data. The retrieval service is divided into components that independently determine whether to return summary data or source data based on query parameters, avoiding the need to process and transmit all source data in every query cycle.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter being returned based on query characteristics. When queries have long time intervals or large cycle durations, the system returns summary data (aggregated statistics). When queries require detailed analysis or have short time intervals, the system returns source data. This dynamic parameter selection optimizes resource utilization.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If conventional cyclical retrieval services process all source data values, then complete data is available for queries, but network bandwidth is overloaded

Engineering Contradiction:
Improvedata completenessVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary data from the complete source data set. The determination component analyzes query parameters and extracts either summary data (when sufficient for the query) or only the specific source data values needed, rather than transmitting all source data values regardless of query requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates summary data as a simplified copy of source data that contains aggregated information (min, max, average, etc.). This summary copy can satisfy many queries without needing the complete source data, reducing network bandwidth consumption while maintaining data reliability for appropriate query types.

Inventive Principle:
Principle #26Copying

3Loss of energy

If summary data is used for retrieval, then processor resources and network bandwidth are reduced, but query parameter satisfaction may be compromised

Engineering Contradiction:
Improveprocessor resource utilizationVSAvoidquery parameter satisfaction
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The determination component acts as a feedback mechanism that evaluates query parameters against data characteristics. It continuously assesses whether summary data or source data should be returned based on the specific query requirements, ensuring that query parameter satisfaction is maintained while optimizing resource usage.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent implements a dynamic retrieval strategy where the data type returned (summary or source) changes based on query characteristics. The system adaptively selects the appropriate data format rather than using a fixed approach, allowing it to satisfy diverse query parameters while maintaining efficiency.

Inventive Principle:
Principle #15Dynamics

4Measurement precision

If source data values are retrieved for every query cycle, then accurate data is provided, but the system becomes slow and inefficient

Engineering Contradiction:
Improvedata accuracyVSAvoiddata retrieval speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent applies partial action by retrieving and returning only the necessary portion of data needed to satisfy the query. When summary data is sufficient, only summary data is returned rather than all source data values, improving retrieval speed while maintaining adequate accuracy for the query's needs.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12242235B2Summarization retrieval in a process control environment
Publication Date: 2025.03.04 AVEVA SOFTWARE LLC
  • US12242235B2 patent drawing
  • US12242235B2 patent drawing
  • US12242235B2 patent drawing

AI summary

Operational historian system retrieving summary data values and source data values based on alignment between a summarization cycle duration and a query cycle duration. A retrieval service process executing on a historian device utilizes a summarization cycle duration, including start and/or end times thereof, and a query cycle duration, including start and/or end times thereof, to determine whether to retrieve, via a communications network, source tag data and/or summary tag data from memory storage devices.