Dual-Core Flight Management System for Military-Civil Airspace Compliance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Military aircraft operating in civilian or commercial airspace face restrictions due to lack of civil or commercial avionics capabilities, necessitating integration of civil and tactical flight management systems into a CNS/ATM compliant multi-core system, while also requiring independent updates to avoid full recertification of software components.
Innovation Solution
A dual-core flight management system with a civil and tactical flight management system manager, coupled with a platform interface manager, allows for independent updates and temporal/spatial isolation, enabling CNS/ATM compliance and unified interface control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If civil and tactical flight management systems are integrated into a multi-core system, then CNS/ATM compliance is achieved, but system complexity increases
Solution Approach 1:
The flight management system is divided into separate civil and tactical cores that operate independently but are integrated through a common interface. Each core maintains its own certification and operational independence while collectively enabling CNS/ATM compliance through the unified multi-core architecture.
2Productivity
If flight management system software is updated, then system functionality is improved, but recertification is required
Solution Approach 1:
The software is segmented into separate civil and tactical components that can be updated independently. Each component maintains its own certification status, allowing updates to one component without triggering recertification requirements for the entire system, thus reducing time loss.
3Ease of operation
If civil and tactical systems are integrated, then unified interface control is enabled, but isolation requirements increase
Solution Approach 1:
The system uses spatial and temporal segmentation to maintain isolation between civil and tactical components while providing unified interface control. Civil and tactical data are processed in separate cores with defined communication protocols, ensuring that updates or operations in one core do not affect the other, thus maintaining reliability.
Solution Approach 2:
An intermediary communication layer is introduced between the civil and tactical cores, managing data exchange and ensuring proper isolation. This intermediary handles the coordination between the two systems, allowing unified control while maintaining the necessary separation for reliability and certification purposes.
Data Source
AI summary
A flight management system (FMS) including a plurality of FMS components that can include a civil FMS component and a tactical FMS component. Each FMS component can have a processor programmed to execute an FMS software product. The FMS can also include a multi core FMS manager configured to control a plurality of flight management systems and coupled to the plurality of FMS components. The multi core FMS manager can include a plurality of FMS managers, each coupled to one of the FMS components, and a platform interface manager coupled to an avionics system. Each FMS manager can be adapted to transmit flight management data to, and to receive flight management data from, the FMS component to which it is coupled. The platform interface manager can be adapted to provide each FMS component access to the avionics system, such that an aircraft operator can control each FMS component via the FMS.