AIRAC Validity Decision Support for Flight-Critical AIXM Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The transition from AIS to AIM introduces AIXM data format with variable validity periods, creating discrepancies with fixed AIRAC cycles, leading to manual and labor-intensive decision-making challenges for analysts in aviation data management, particularly in Flight Management Systems (FMS), where analysts must manually compare validity periods and determine flight-critical changes.
Innovation Solution
A decision-making support system that automatically compares AIXM file valid times with AIRAC cycle dates, identifies feature changes, determines flight criticality, and generates change notices and alerts, reducing manual workload by providing automated decision support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual comparison of validity periods is performed by analysts, then accuracy in identifying flight-critical changes is maintained, but productivity is reduced due to labor-intensive processes
Solution Approach 1:
The patent replaces the manual mechanical process of comparing validity periods with an automated computer-implemented system. The system automatically compares the valid time attribute of AIXM data features with AIRAC cycle effective dates, identifies discrepancies, and determines flight-critical status without human intervention in the comparison process, thereby maintaining accuracy while significantly improving productivity
Solution Approach 2:
The system enables self-service by automatically performing the entire workflow of validity period comparison, discrepancy identification, and flight-critical determination. The automated generation of change notices and alerts allows the system to serve itself in identifying and reporting issues without requiring analyst intervention for each comparison task
2Productivity
If automated comparison system is implemented, then productivity is improved by reducing manual workload, but device complexity increases due to additional processing requirements
Solution Approach 1:
The patent segments the decision-making process into distinct modular components: (1) receiving AIXM data with valid time attributes, (2) comparing valid times with AIRAC effective dates, (3) identifying discrepancies, (4) determining flight-critical status, and (5) generating change notices. This segmentation allows each function to be implemented as a separate processing module, managing complexity while enabling automated high-productivity operation
Solution Approach 2:
The system introduces an intermediary automated processing layer between the raw AIXM data and the final decision output. This intermediary automatically performs validity period comparisons and generates structured change notices, acting as a mediator that translates complex data validation requirements into actionable alerts without requiring direct human intervention in the comparison process
3Adaptability or versatility
If manual determination of flight-critical changes is performed, then adaptability to different change scenarios is maintained, but loss of time occurs due to repetitive manual analysis
Solution Approach 1:
The patent implements a dynamic system that can adapt to different change scenarios through configurable parameters and flexible comparison logic. The system dynamically adjusts its analysis based on the specific valid time attributes of incoming AIXM data and the relevant AIRAC cycle effective dates, enabling it to handle various change scenarios automatically without sacrificing adaptability while eliminating time-consuming repetitive manual analysis
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Decision making support is provided. The method comprises receiving input of a current data file, wherein the current data file includes a valid time for features within the current data file. The valid time of the current data file is compared with Aeronautical Information Regulation and Control (AIRAC) cycle effective dates. Responsive to a discrepancy between the valid time of the current data file and the AIRAC cycle effective dates, the system determines if a feature change resulting from the discrepancy is flight critical. The feature change and a proposed solution with suggested text are displayed to a user in a dashboard. Responsive to input of agreement from the user to the proposed solution, the system automatically creates a change notice with the suggested text, a business process management ticket, and a data entry into a database.