Aircraft Maintenance Requirement Capture System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The development and maintenance of centralized aircraft maintenance systems are complex and costly due to the large number of interconnected equipment items and diverse protocols, requiring lengthy fine-tuning and involving multiple cultural teams, with current information capture methods lacking formalism for homogeneity, consistency, and completeness.

Innovation Solution

A device and method for defining and capturing maintenance requirements iteratively, ensuring data consistency and completeness through a centralized system with input modules, verification mechanisms, and user profiles, generating configuration databases for the maintenance system, and providing a man-machine interface for tailored information sharing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If information capture is carried out through aircraft systems specification documents without formalism, then flexibility in capturing diverse equipment information is maintained, but homogeneity, consistency and completeness of the captured information cannot be guaranteed

Engineering Contradiction:
Improveability to capture diverse equipment informationVSAvoidhomogeneity and consistency of captured information
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent introduces formal parameter definitions and constraints for maintenance information capture. By establishing standardized parameters with specific data types, validation rules, and mandatory fields, the system ensures homogeneous and consistent information capture across diverse aircraft equipment while maintaining adaptability through configurable parameter schemas.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent segments the information capture process into structured components: equipment identification parameters, fault message parameters, alarm parameters, and report parameters. Each segment has defined validation rules and data formats, enabling systematic verification of completeness and consistency while accommodating diverse equipment types through modular parameter sets.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the number of connected items of equipment is increased to comprehensively monitor the aircraft, then diagnosis coverage is improved, but the complexity and time required for system integration and fine tuning increases significantly

Engineering Contradiction:
Improvediagnosis coverageVSAvoidsystem integration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal maintenance information capture system that can handle multiple equipment types and protocols through standardized parameter definitions. The same structured framework accommodates diverse equipment by configuring appropriate parameters rather than requiring separate integration approaches for each device, thereby reducing overall system complexity.

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

Solution Approach 2:

The system uses configurable parameters to adapt to different equipment characteristics without changing the underlying system architecture. By defining equipment-specific parameters within a unified framework, the system maintains consistent processing logic across hundreds of connected items while capturing their unique attributes.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If multiple parties from different cultures are involved in fine tuning the system, then diverse expertise is utilized, but the difficulty of capturing maintenance information in an unambiguous and consistent manner increases

Engineering Contradiction:
Improvediverse expertise utilizationVSAvoidambiguity in maintenance information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent enforces homogeneous information structure through standardized parameter definitions, data formats, and validation rules. This homogeneous framework provides a common language for diverse teams, eliminating ambiguity by ensuring all parties capture and interpret maintenance information in the same structured manner while still accommodating different expertise areas.

Inventive Principle:
Principle #33Homogeneity

Solution Approach 2:

The system incorporates automated verification mechanisms that provide immediate feedback on captured information for completeness and consistency. Validation rules check parameter values against defined constraints, and the structured format enables automated detection of ambiguities or inconsistencies, allowing diverse teams to self-correct without extensive manual review.

Inventive Principle:
Principle #23Feedback

4Manufacturing precision

If the capture phase is made iterative to ensure completeness, then information accuracy is improved, but the time required for system integration is significantly lengthened

Engineering Contradiction:
Improveinformation accuracyVSAvoidsystem integration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent establishes parameter validation rules, data format specifications, and completeness checks before the actual information capture process. By preparing the structured framework and verification mechanisms in advance, the system enables accurate information capture in fewer iterations, reducing the overall time required while maintaining high accuracy standards.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides automated feedback during the capture process through validation rules that immediately identify incomplete or inconsistent information. This real-time feedback eliminates the need for multiple manual review iterations by catching errors early and guiding corrective actions, thereby maintaining information accuracy while reducing total integration time.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9718563B2Method and device for requirement capture for a system for centralized maintenance for aircraft
Publication Date: 2017.08.01 THALES SA
  • US9718563B2 patent drawing
  • US9718563B2 patent drawing
  • US9718563B2 patent drawing

AI summary

A requirement capture device for a centralized maintenance system for aircraft is composed of a means for capturing and parametrizing the various characteristics of the centralized maintenance system. It allows the various parties to the fine tuning of the CMS system to define the data set specific to their domain in a common framework. User profiles are defined for each of the users affording them configuration possibilities specific to their domain. After validation of the parameters input, a configuration file is generated.