Power System Damage Scoring With Periodic Analysis Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing engine damage monitoring systems face challenges in balancing the frequency of damage analysis, as high frequency consumption of computing resources prevents other engine monitoring and control functions, while low frequency analysis leads to reduced accuracy and delayed detection of catastrophic damage.

Innovation Solution

A damage control system that receives operating and damage measurements, stores them in a damage profile, and uses a damage model to determine a damage score based on the frequency of operating states and damage measurements, configuring control devices to manage engine operation accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If damage models analyze the operating state and damage at a relatively high frequency, then the accuracy of damage detection is improved, but a relatively high amount of computing resources are consumed

Engineering Contradiction:
Improvedamage detection accuracyVSAvoidcomputing resources consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent segments the continuous damage analysis process into discrete periodic updates. Instead of continuously analyzing damage at high frequency, the system divides time into periods and performs damage model analysis only at periodic intervals, thereby reducing overall computing resource consumption while maintaining sufficient detection accuracy through the periodic nature of the updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements periodic damage analysis by updating the damage model at predetermined time intervals rather than continuously. The system periodically receives operating measurements, identifies operating states, and updates damage scores at these periodic intervals, which reduces computing resource consumption while maintaining effective monitoring through the periodic refresh of damage assessments.

Inventive Principle:
Principle #19Periodic action

2Use of energy by moving object

If damage models analyze the damage at a relatively low frequency, then computing resources are conserved, but the damage models lose accuracy with respect to predictability or determining a cumulative damage

Engineering Contradiction:
Improvecomputing resources consumptionVSAvoiddamage prediction accuracy
Core Design Contradiction:
Use of energy by moving objectVSMeasurement precision

Solution Approach 1:

The patent applies preliminary action by continuously accumulating and storing operating measurements and damage measurements in memory during operation, even between periodic damage model updates. This preliminary data collection ensures that when the damage model does execute periodically, it has access to comprehensive accumulated data, thereby maintaining high prediction accuracy despite the low frequency of actual model updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent maintains continuity of useful action by continuously collecting and storing relevant measurements and operating data throughout the engine's operation. While the damage model updates periodically, the system continuously monitors and accumulates data, ensuring that the useful action of data collection is continuous while the computationally intensive modeling occurs only periodically, thus balancing resource conservation with accuracy.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If damage models continuously monitor the engine to detect damage, then the detection accuracy is improved, but the system consumes high computing resources preventing monitoring and control of other engine aspects

Engineering Contradiction:
Improvedamage detection reliabilityVSAvoidsystem resource allocation
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the monitoring functions by separating continuous lightweight data collection from periodic intensive damage analysis. The system continuously monitors operating parameters with simple measurements, then segments the computationally intensive damage model execution to occur only at periodic intervals, thereby maintaining reliable damage detection while freeing resources for other engine control functions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements periodic damage model execution rather than continuous monitoring. The damage model updates at predetermined intervals while other engine monitoring and control functions operate continuously, allowing the system to maintain reliable damage detection capability without the computing resource consumption of continuous intensive analysis, thus enabling proper resource allocation across multiple system functions.

Inventive Principle:
Principle #19Periodic action

4Use of energy by moving object

If the frequency of damage analysis is reduced, then computing resources are conserved, but damage may be detected after it has reached a catastrophic level

Engineering Contradiction:
Improvecomputing resources consumptionVSAvoiddamage detection timing
Core Design Contradiction:
Use of energy by moving objectVSLoss of time

Solution Approach 1:

The patent applies preliminary action by continuously accumulating damage measurements and operating data in memory before periodic damage model updates. This continuous preliminary data collection ensures that when the damage model executes periodically, it immediately has access to the latest damage information, enabling timely detection of catastrophic damage conditions without the time loss that would result from waiting for the next periodic update cycle.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where damage scores are continuously updated based on accumulated measurements and fed back into the control system. The periodic damage model analysis provides feedback on cumulative damage levels, and this feedback loop ensures that when damage reaches critical thresholds, the system can quickly detect and respond to it in the next periodic cycle, minimizing detection delay while conserving resources.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11226358B2Power system damage analysis and control system
Publication Date: 2022.01.18 CATERPILLAR INC
  • US11226358B2 patent drawing
  • US11226358B2 patent drawing
  • US11226358B2 patent drawing

AI summary

A damage analysis and control system is disclosed. An example process may include receiving a data set of measurements associated with a period of operation of a power system. The data set of measurements may identify a frequency that the power system is in an operating state during the period of operation, and the data set of measurements may identify a frequency of damage measurements associated with the operating state. The process may include determining, using a damage model and the data set of measurements, a damage score for the operating state during the period of operation of the power system. The process may include determining that the damage score satisfies a threshold damage score associated with the damage model and performing an action associated with the power system based on the damage score satisfying the threshold damage score.