Navigation Data Comparison Interface for FMS Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating and comparing navigation databases in a Flight Management System (FMS) are manual, lack hierarchy, and fail to support data type comparisons, leading to incomplete and error-prone data conversion and integration.
Innovation Solution
A system and method for facilitating data communication using a controller module to receive, verify, and compare multiple navigation databases, converting data to a binary format, and generating a gold standard database for FMS, with interactive tools for side-by-side comparison and statistical analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual updating and comparison methods are used for navigation databases, then maintenance personnel can update the database per the 28-day cycle, but the process is error-prone and incomplete
Solution Approach 1:
The system enables automatic self-updating of navigation databases by comparing the current database with the new database and automatically identifying and implementing necessary updates without manual intervention, thereby improving reliability while maintaining ease of operation
Solution Approach 2:
The patent replaces manual mechanical updating processes with an automated electronic system that uses binary format comparison and automatic update generation, eliminating human error while keeping the interface simple for maintenance personnel
2Manufacturing precision
If traditional comparison methods are used without data type support, then the process is simple, but data conversion and integration are incomplete and error-prone
Solution Approach 1:
The system converts navigation database data into a standardized binary format with defined data types before comparison, ensuring precise data conversion and integration while maintaining manageable system complexity through systematic parameter standardization
Solution Approach 2:
The patent introduces a binary format intermediary layer between different navigation database formats, enabling accurate data conversion and comparison while keeping the system architecture organized and maintainable
3Adaptability or versatility
If no hierarchical data structure is used, then the system is simple, but it fails to support data type comparisons and integration
Solution Approach 1:
The patent segments the navigation database into hierarchical levels (database, data type, record, field) that enable systematic comparison and integration of different data types while maintaining a structured and manageable architecture
Solution Approach 2:
The system adds a hierarchical dimension to the data structure, organizing data into multiple levels (database, data type, record, field) that enable comprehensive comparison capabilities while keeping the implementation organized and scalable
4Measurement precision
If manual verification of data authenticity is used, then the process is simple, but it is time-consuming and may miss errors
Solution Approach 1:
The patent replaces manual verification processes with automated electronic verification using binary format comparison and digital signature validation, achieving precise data authenticity verification while significantly reducing the time required
Solution Approach 2:
The system performs automatic self-verification of data authenticity through embedded digital signatures and automated comparison processes, ensuring precise verification without requiring manual time investment
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system (39, 49) and method (400) for compiling and converting Aeronautical Radio Incorporated (ARINC) 424 or Digital Aeronautical Flight Information File (DAFIF) files into a binary database. The system (39, 49) and method (400) include a controller module (36, 46) for displaying a comparison interface (600, 700) using a data structure comprising a plurality of nodes (610, 716, 722) and a data architecture for supporting integration of multiple disparate navigation databases (504, 506). The controller module (36, 46) can also be configured for displaying an options box (500) within the comparison interface (600, 700). The controller module (36, 46) can receive a first user selection (508) related to a first database (504) and a second user selection (510) related to a second database (506). The controller (36) can display a comparison result (602, 604) that includes the first user selection (508) and the second user selection (510).