Aircraft Fleet Data Reporting via Inherited Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data collection and reporting systems for vehicle fleets are inefficient due to manual management and differing data requirements between original equipment manufacturers (OEMs) and vehicle operators, leading to ineffectiveness and delays in data reporting across large populations.

Innovation Solution

A method and system that define a master reporting template by the OEM, which is communicated to vehicle operators, allowing for the creation of inherited reporting templates that include both OEM and operator-specific structures, with data collection and reporting streamlined through a centralized data hub connected to vehicles via a data port, ensuring consistent and automated reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual coordination is used for report updates between OEMs and vehicle operators, then flexibility in customizing reports is maintained, but reporting effectiveness decreases and delays occur

Engineering Contradiction:
Improvereport customization flexibilityVSAvoidreporting efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The reporting system is segmented into two distinct layers: a master reporting template maintained by the OEM that defines core report structures, and inherited reporting templates used by vehicle operators that can customize reports based on the master template. This segmentation allows each party to manage their specific requirements independently while maintaining overall system coordination, eliminating manual coordination delays while preserving customization flexibility.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If separate report structures are maintained for OEM and operator use, then specific data requirements are met, but management complexity increases

Engineering Contradiction:
Improvedata requirement satisfactionVSAvoidreport management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system merges the OEM's master reporting template with operator-specific inherited templates into a unified reporting framework. The master template serves as the foundation that incorporates operator requirements, allowing both OEM and operator data needs to be satisfied through a single integrated system rather than separate management processes, thereby reducing overall management complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The master reporting template is designed to be universal, serving both OEM monitoring needs and operator fleet management requirements. By making the template multi-functional and adaptable to different user needs through the inheritance mechanism, the system eliminates the need for separate report structures while still meeting specific data requirements of both parties.

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

3Adaptability or versatility

If ad-hoc report updates are implemented across multiple operators, then specific operational needs are addressed, but coordination difficulty increases with large operator populations

Engineering Contradiction:
Improveoperational need responsivenessVSAvoidcoordination ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The OEM performs preliminary actions by defining and maintaining the master reporting template in advance, which automatically becomes the basis for all operator reporting templates. This preliminary setup eliminates the need for ad-hoc coordination with each operator when updates are needed, as changes to the master template are automatically propagated to all inherited templates, making the system easy to operate even with large operator populations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10304262B2Aircraft data management system and method
Publication Date: 2019.05.28 RTX CORP
  • US10304262B2 patent drawing
  • US10304262B2 patent drawing
  • US10304262B2 patent drawing

AI summary

A method of data collection and reporting for a vehicle fleet includes defining a master reporting template at an original equipment manufacturer. The master reporting template includes one or more original equipment manufacturer report structures for original equipment manufacturer use. The master reporting template is communicated from the original equipment manufacturer to one or more vehicle operators. An inherited reporting template is defined at the vehicle operator including the one or more original equipment manufacturer report structures and one or more vehicle operator report structures for vehicle operator use. Data is collected from one or more vehicles of the vehicle fleet at a data hub via a data port at the one or more vehicles. The data collection is based on the contents of the inherited reporting template.