Context-Based Cockpit Simulation for EFB Interface Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current aircraft cockpit simulation systems lack customization for specific aircraft types, leading to inefficient and error-prone flight preparation, as they require redundant information entry and do not match the in-cockpit user interface, resulting in additional training and increased error likelihood.

Innovation Solution

A context-based cockpit simulation system that includes a communication device, display, input/output interface, and processing unit, allowing selection of customizable Electronic Flight Book (EFB) graphical user interfaces (GUIs) matching the aircraft type, receiving and updating flight parameters from the Flight Management System (FMS), and displaying a cockpit clone to mimic actual aircraft settings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a generic EFB tool is used on remote devices, then the system is universally applicable to different aircraft types, but the user interface does not match the in-cockpit EFB and requires redundant information entry

Engineering Contradiction:
Improveuniversal applicabilityVSAvoiduser interface consistency
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system applies local quality by customizing the EFB interface specifically for each aircraft type rather than using a generic interface. The remote device EFB is configured to match the exact layout, format, and information structure of the corresponding in-cockpit EFB for each aircraft type, ensuring that pilots interact with identical interfaces whether working remotely or in the cockpit.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system creates accurate digital copies of the in-cockpit EFB interface on remote devices. The remote EFB replicates the visual appearance, information hierarchy, and interaction patterns of the actual cockpit EFB, allowing pilots to perform flight preparation tasks with the same interface they will use during the flight.

Inventive Principle:
Principle #26Copying

2Device complexity

If a non-customized EFB interface is used, then the system is simpler to implement, but additional crew training is required and error likelihood increases

Engineering Contradiction:
Improvesystem implementation complexityVSAvoiderror likelihood
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system changes the interface parameters (layout, format, information structure) of the remote EFB to match the specific aircraft type being flown. Rather than using a fixed generic interface, the system dynamically adjusts the EFB parameters based on the aircraft type, ensuring familiarity and reducing errors while maintaining implementation flexibility through parameterization.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If flight parameters are not automatically synchronized, then the system architecture is simpler, but redundant information entry is required and flight preparation efficiency decreases

Engineering Contradiction:
Improvesystem architecture complexityVSAvoidflight preparation efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system implements feedback by automatically synchronizing flight parameters between the remote device EFB and the aircraft's FMS. When parameters are entered or modified on the remote device, the system automatically transfers and updates the corresponding data in the aircraft system, eliminating redundant entry and ensuring data consistency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system merges the flight preparation data entry function with the aircraft's existing FMS system. Rather than treating the remote EFB as a separate standalone system requiring independent data entry, the system integrates it with the aircraft's flight management system, allowing single-entry data to be automatically available in both locations.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240194089A1Systems and methods for context-based cockpit simulation
Publication Date: 2024.06.13 HONEYWELL INTERNATIONAL INC
  • US20240194089A1 patent drawing
  • US20240194089A1 patent drawing
  • US20240194089A1 patent drawing

AI summary

A system includes a communication device, a display, an input/output interface, a processing device, and a memory, storing one or more instructions that cause the system to: receive electronic flight book (EFB) selection information for selecting one EFB GUI from a plurality of selectable EFB GUIs that provide an interface for entry and display of flight information; select one EFB GUI from the plurality of selectable EFB GUIs based on the received EFB selection information; display the selected EFB GUI on the display; receive one or more flight parameters from a flight management system (FMS); display one or more of the one or more flight parameters on the displayed EFB GUI; receive one or more changes to the one or more flight parameters via the input/output interface; and update one or more of the one or more flight parameters in the FMS based on the received one or more changes.