Aircraft Maintenance Event Detection Using Carrier-Specific Indicator Normalization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Variations in how airlines track and schedule aircraft maintenance events make it challenging for maintenance, repair, and overhaul providers to predict maintenance events and prepare replacement components, as different carriers use different indicators and intervals.

Innovation Solution

A computing device analyzes aircraft usage data to identify potential and actual maintenance events, determines the indicators used by each carrier, and calculates maintenance intervals for each aircraft model, employing data mining, statistics, adaptive learning, and combinatorial processes to normalize variances and account for exogenous events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If carriers use different indicators and intervals for maintenance events, then carriers can optimize their specific operational needs and revenue generation, but it becomes difficult for MRO providers to predict maintenance events and prepare components

Engineering Contradiction:
Improvecarrier maintenance flexibilityVSAvoidmaintenance event prediction difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system segments the heterogeneous maintenance data from different carriers by identifying and separating their respective indicator types (flight hours, flight cycles, calendar time) and intervals. This segmentation allows the system to process each carrier's data according to its specific methodology while maintaining overall system functionality for prediction and component preparation.

Inventive Principle:
Principle #1Segmentation

2Productivity

If carriers modify manufacturer recommendations and apply different indicators across their fleets, then carriers can maximize revenue and operate aircraft at high utilization levels, but maintenance scheduling becomes inconsistent across the fleet

Engineering Contradiction:
Improveaircraft utilizationVSAvoidmaintenance scheduling consistency
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The system dynamically adapts to each carrier's maintenance scheduling approach by automatically detecting whether they use flight hours, flight cycles, or calendar time as their indicator, and adjusts its analysis accordingly. This dynamic adaptation allows the system to work with inconsistent carrier practices while maintaining accurate prediction capabilities for each carrier's specific fleet.

Inventive Principle:
Principle #15Dynamics

3Reliability

If MRO providers need to predict maintenance events across multiple carriers with varying practices, then component availability can be improved, but the complexity of analyzing and normalizing different data formats increases

Engineering Contradiction:
Improvecomponent availabilityVSAvoiddata analysis system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer that acts as a translator between different carrier maintenance data formats and a standardized analysis framework. This intermediary automatically detects the indicator type used by each carrier, normalizes the data accordingly, and enables consistent prediction algorithms to work across diverse data sources without requiring complex manual processing for each carrier's specific format.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10723487B2Systems and methods for detecting aircraft maintenance events and maintenance intervals
Publication Date: 2020.07.28 THE BOEING CO
  • US10723487B2 patent drawing
  • US10723487B2 patent drawing
  • US10723487B2 patent drawing

AI summary

A computing device for use in detecting maintenance events and maintenance intervals is provided. The computing device is configured to receive aircraft usage data for at least one carrier, identify at least one potential maintenance event in the usage data, identify at least one actual maintenance event in the usage data at least by comparing the usage data for a first aircraft of the at least one carrier to a second aircraft of the at least one carrier during each potential maintenance event, determine an indicator used by each carrier for scheduling maintenance events, determine a maintenance interval for each carrier for an aircraft model associated with at least the first aircraft.