Part Distress Evaluation Using DRM and Cumulative Damage Thresholds
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current diagnostic and prognostic methods for complex systems like aircraft and engines lack effective early detection of hardware distress, leading to unplanned shutdowns and increased maintenance costs due to inadequate evaluation of individual components.
Innovation Solution
A method that combines distress rank model (DRM) and cumulative damage model (CDM) data analysis to determine if aircraft parts exceed predetermined thresholds, generating notifications for maintenance actions based on the evaluation of these models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional diagnostic methods are used for complex systems, then system operation continues without interruption, but early detection of hardware distress is insufficient leading to unplanned shutdowns
Solution Approach 1:
The patent applies preliminary action by evaluating component distress before actual failure occurs. The system continuously monitors component conditions and predicts potential failures in advance, allowing maintenance to be scheduled proactively rather than reactively. This prevents unplanned shutdowns by detecting distress early in the component lifecycle.
Solution Approach 2:
The patent segments the complex system into individual evaluatable components. Rather than treating the entire system as one unit, it breaks down the diagnosis into component-level assessments using distress rank models and cumulative damage models. This segmentation enables more precise early detection of specific hardware distress without requiring full system shutdowns.
2Productivity
If traditional maintenance scheduling is used, then maintenance is performed on fixed schedules, but this leads to increased maintenance costs and reduced engine availability
Solution Approach 1:
The patent implements dynamic maintenance scheduling based on actual component condition rather than fixed time intervals. The system continuously updates distress assessments and adjusts maintenance timing dynamically. Components are maintained when their distress rank or cumulative damage reaches thresholds, not at predetermined schedules, optimizing engine availability while controlling maintenance costs.
Solution Approach 2:
The patent changes the maintenance parameter from time-based to condition-based. Instead of scheduling maintenance at fixed time intervals, the system uses distress rank values and cumulative damage metrics as the primary parameters for determining when maintenance is needed. This parameter change allows maintenance to be performed only when necessary, reducing unnecessary maintenance events.
3Measurement precision
If comprehensive system evaluation is performed, then early detection capability is improved, but system complexity and evaluation time increase
Solution Approach 1:
The patent reduces system complexity by segmenting the evaluation process into two independent models: distress rank model (DRM) and cumulative damage model (CDM). Each model evaluates specific aspects of component condition using separate algorithms and data requirements. This segmentation allows the system to maintain high measurement precision while managing complexity through modular, independent evaluation pathways.
Solution Approach 2:
The patent applies partial action by implementing a two-threshold evaluation system where maintenance is triggered if either the DRM threshold OR the CDM threshold is exceeded. This partial evaluation approach provides sufficient detection accuracy without requiring both models to agree, reducing computational complexity while maintaining reliable distress detection.
Data Source
AI summary
A method of evaluating a part is characterized by obtaining data representing a distress rank model (DRM) and a cumulative damage model (CDM) for the part. Based on the data, the method ascertains a DRM value for the part and a CDM value for the part. The method determines whether the DRM value is at or above a predetermined DRM threshold and whether a CDM value is at or above a predetermined CDM threshold. If either the DRM value or the CDM value is at or above at least one respective threshold, an action related to the part is generated.