Scheduled maintenance credit user interface

Abstract

This invention provides a scheduled maintenance credit user interface. [Solution] An aircraft maintenance user interface is provided. The interface includes an alarm indicator that displays alarms related to aircraft systems that must be addressed for aircraft maintenance compliance. A compliance window indicator displays a normalized sliding scale of the percentage of lead time elapsed between the alarm and the maintenance compliance deadline. A remaining unit indicator displays the number of units used out of the total number of allocated units that measure the remaining lead time.

Description

Technical Field

[0001] Cross-Reference to Related Applications This application is related to U.S. Patent Application No. _________, Attorney Docket No. 24-0406-US-PSP, entitled "Scheduled Maintenance Credit Data Health Management and Tracking of Compliance Lead Time Remaining", filed on the same date as this specification, assigned to the same assignee, and incorporated herein by reference in its entirety.

[0002] The present disclosure generally relates to aircraft maintenance, and more particularly to an interface for monitoring maintenance tasks and providing notifications as to when maintenance must be completed.

Background Art

[0003] An Aircraft Health Management (AHM) system is a comprehensive solution designed to monitor and manage the health and performance of an aircraft in real time. The AHM system collects and analyzes data from various aircraft systems to detect anomalies, predict potential failures, and optimize maintenance actions. This capability is important for airlines to ensure operational efficiency, enhance safety, and reduce maintenance costs.

[0004] ACARS (Aircraft Communications Addressing and Reporting System) is a digital data link system used to transmit messages between aircraft and ground stations. Introduced to replace voice communications, it has since become a crucial component of modern aviation communications. Airlines use ACARS to monitor the status of their aircraft, transmit operational instructions, and receive data on the aircraft's position, speed, altitude, and other parameters. ACARS can transmit data on the aircraft's systems and performance, enabling maintenance teams to be notified of any problems before the aircraft lands. This data can then be used to schedule maintenance and minimize aircraft downtime. [Overview of the project] [Means for solving the problem]

[0005] An exemplary embodiment provides an aircraft maintenance user interface. The interface includes a dashboard that displays alerts related to aircraft systems that must be addressed to comply with the aircraft's MRBR Appendix M task description, which are registered for situation-based monitoring. A compliance window indicator displays a normalized sliding scale of the percentage of lead time elapsed between the alert and the maintenance compliance deadline. A remaining unit indicator displays the number of units used out of the total number of allocated units that measure the remaining lead time.

[0006] Another embodiment provides a system for displaying an aircraft maintenance user interface. The system comprises a storage device for storing program instructions, and one or more processors operably connected to the storage device and executing the program instructions to cause the system to display a dashboard that displays alerts related to aircraft systems that must be addressed to comply with the aircraft's MRBR Appendix M task description, a compliance window indicator that displays a normalized sliding scale of the percentage of lead time elapsed between the alert and the maintenance compliance deadline, and a remaining unit indicator that displays the number of units used out of the total number of allocated units to measure the lead time.

[0007] Another embodiment provides a computer program product for displaying an aircraft maintenance user interface. The computer program product comprises a computer-readable storage medium having program instructions embodied to perform display operations; a dashboard for displaying alerts related to aircraft systems that must be addressed in order to comply with the aircraft's MRBR Appendix M task description; a compliance window indicator for displaying a normalized sliding scale of the percentage of lead time elapsed between the alert and the maintenance compliance deadline; and a remaining unit indicator for displaying the number of units used out of the total number of allocated units to measure the remaining lead time.

[0008] The features and functions can be achieved individually in various embodiments of this disclosure and can also be combined in other embodiments, which can be understood in more detail by referring to the following description and drawings.

[0009] Novel features that may be considered characteristics of the exemplary embodiments are described in the appended claims. However, the exemplary embodiments and their preferred modes of use, further purposes, and features are best understood by referring to the following detailed description of the exemplary embodiments of this disclosure in conjunction with the appended drawings. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram of an aircraft maintenance user interface according to an exemplary embodiment. [Figure 2] This figure shows a process flow for handling and resolving alarms according to an exemplary embodiment. [Figure 3] This figure shows a scheduled maintenance interface for a new alarm system according to an exemplary embodiment. [Figure 4A] This figure shows a threshold alarm detail panel according to an exemplary embodiment. [Figure 4B] This figure shows a workflow status dropdown menu according to an exemplary embodiment. [Figure 5A] This figure shows a status details panel marked as having been addressed according to an exemplary embodiment. [Figure 5B] This figure shows an update status details panel according to an exemplary embodiment. [Figure 5C] This figure shows a status details panel marked as resolved according to an exemplary embodiment. [Figure 5D] This figure shows a status details panel to mark for rework according to an exemplary embodiment. [Figure 6A] This figure shows a post-response alarm dashboard user interface for post-response alarms, according to an exemplary embodiment. [Figure 6B] This figure shows a post-response alarm dashboard user interface for post-response alarms, according to an exemplary embodiment. [Figure 7]A diagram showing the "No Report" detailed panel when reports of an associated aircraft system according to an exemplary embodiment are not received during a specified number of flight cycles. [Figure 8] A flowchart showing the necessary actions to be taken for various types of transmission stops from an aircraft. [Figure 9A] A diagram showing the fleet data integrity display according to an exemplary embodiment. [Figure 9B] A diagram showing the fleet data integrity display according to an exemplary embodiment. [Figure 10A] A diagram showing the aircraft data integrity detailed panel according to an exemplary embodiment. [Figure 10B] A diagram showing the data fault reason dropdown menu according to an exemplary embodiment. [Figure 11] A diagram showing a specific detailed panel of the ACARS MEL category of a data fault according to an exemplary embodiment. [Figure 12] A diagram showing the aircraft data integrity detailed panel after entry of an ACARS MEL related data fault according to an exemplary embodiment. [Figure 13] A diagram showing the update detailed panel of a queued classified data fault according to an exemplary embodiment. [Figure 14] A diagram showing the aircraft data integrity detailed panel at the resumption of data reception according to an exemplary embodiment. [Figure 15] A diagram showing the resolution detailed panel of a queued classified data fault according to an exemplary embodiment. [Figure 16] A diagram showing a specific detailed panel of the maintenance check category of a data fault according to an exemplary embodiment. [Figure 17] A diagram showing the aircraft data integrity detailed panel after verification of maintenance check status information according to an exemplary embodiment. [Figure 18] A diagram showing the aircraft data integrity detailed panel showing an updated verification of the maintenance check status according to an exemplary embodiment. [Figure 19] A diagram showing an updated details panel for a pending maintenance check according to an exemplary embodiment. [Figure 20A] A diagram showing an automatic resolution notice in fleet data health indication according to an exemplary embodiment. [Figure 20B] A diagram showing an automatic resolution notice in fleet data health indication according to an exemplary embodiment. [Figure 21] A diagram showing a resolved status details panel providing details of automatic resolution of a data fault according to an exemplary embodiment. [Figure 22] A diagram showing a specific details panel for other categories of data faults according to an exemplary embodiment. [Figure 23] A diagram showing an aircraft data health details panel after entry of other related data faults according to an exemplary embodiment. [Figure 24] A diagram showing an updated details panel for other classified data faults according to an exemplary embodiment. [Figure 25] A diagram showing a specific details panel for other categories of data faults according to an exemplary embodiment. [Figure 26] A diagram showing an aircraft data health details panel after entry of an operation stop related data fault according to an exemplary embodiment. [Figure 27] A diagram showing an updated details panel for a data fault classified as an operation stop according to an exemplary embodiment. [Figure 28] A block diagram of a data processing system according to an exemplary embodiment. [Figure 29] A diagram of a method for manufacturing and maintaining an aircraft according to an exemplary embodiment. [Figure 30] A block diagram of an aircraft in which an exemplary embodiment may be implemented.

Best Mode for Carrying Out the Invention

[0011] An exemplary embodiment recognizes and takes into account that airline operators must schedule periodic maintenance checks of aircraft systems. These checks incur costs associated with labor and the early replacement of system components.

[0012] The exemplary embodiment provides a user interface for notifying airline operators when maintenance needs to be performed on an aircraft based on monitored system sensor readings and flight history, eliminating the need for regularly scheduled checks mandated by the FAA. The exemplary embodiment also helps operators maintain airworthiness compliance even when data is not being received from registered aircraft by notifying operators of transmission outages and providing recommendations for manual actions that may be required to maintain compliance until the outage can be restored.

[0013] An exemplary embodiment utilizes a prognostic warning engine in Aircraft Health Management (AHM). The warning engine generates alerts displayed to the operator based on real-time data received during the aircraft's flight. This exemplary embodiment also relies on new capabilities for calculating airworthiness compliance status and risk levels.

[0014] Referring here to Figure 1, a block diagram of an aircraft maintenance user interface is depicted according to an exemplary embodiment. The aircraft maintenance user interface 100 can be integrated into an aircraft health management (AHM) system.

[0015] The aircraft maintenance user interface 100 displays a new alert 116 related to an aircraft system that has reached an operational threshold requiring maintenance to meet aircraft compliance requirements (see Figure 3). The aircraft maintenance user interface 100 also displays a post-action alert 118 indicating that a work instruction has been initiated (see Figure 6).

[0016] The aircraft maintenance user interface 100 displays an alert indicator 102 that shows alerts related to aircraft systems that must be addressed for aircraft maintenance compliance. The aircraft maintenance user interface 100 also displays a compliance window indicator 104 that visually shows the window of remaining opportunities to meet the aircraft compliance deadline. This compliance window displays a normalized sliding scale of the percentage of lead time elapsed between threshold alerts and the maintenance compliance deadline. The aircraft maintenance user interface 100 also complements the compliance window indicator 104 by displaying a remaining unit indicator 106 that shows the number of window units used out of the total allocation. These units may include units of time or operational cycles.

[0017] Upon reviewing the alarm 118 after the response, the aircraft maintenance user interface 100 also displays a compliance status 108 indicating the current stage of the workflow for addressing the alarm in question.

[0018] The aircraft maintenance user interface 100 provides an alarm detail panel 110 that slides in as a second layer in response to a click on the alarm indicator 102 (see Figure 4).

[0019] If an aircraft fails to send aircraft system reports within a specified number of flight cycles, an alert is displayed on the aircraft maintenance interface 100. Clicking the alert slides out the "No Report" details panel 114 (see Figure 7).

[0020] The aircraft maintenance user interface 100 also provides a fleet data health display 120, which provides a more detailed breakdown of data failures among them (see Figures 9A and 9B). Aircraft are listed in the fleet data health display 120 under different categories 122 of reasons for data failure. When an aircraft entry under category 124 is selected, the aircraft health details panel 126 slides open, which can provide a general or specific view according to category 124 (see Figures 10 and 12).

[0021] The aircraft maintenance user interface 100 is generated by a display system 156. The display system 156 is a physical hardware system and includes one or more display devices capable of displaying the aircraft maintenance user interface 100.

[0022] The display device in the display system 156 may include at least one of the following: a light-emitting diode (LED) display, a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, a computer monitor, a projector, a flat panel display, a head-up display (HUD), a head-mounted display (HMD), or any other suitable device capable of outputting information for the visual presentation of information.

[0023] The aircraft maintenance user interface 100 may be implemented in software, hardware, firmware, or a combination thereof. If software is used, the operations performed by the aircraft maintenance user interface 100 may be carried out by program code configured to run on hardware such as a processor unit. If firmware is used, the operations performed by the aircraft maintenance user interface 100 may be carried out by program code and data, which may be stored in persistent memory for operation on a processor unit. If hardware is used, the hardware may include circuitry that operates to perform the operations in the aircraft maintenance user interface 100.

[0024] In exemplary examples, hardware can take the form of at least one of the following: a circuit system, an integrated circuit, an application-specific integrated circuit (ASIC), a programmable logic device, or other suitable types of hardware configured to perform several operations. Programmable logic devices can be configured to perform several operations. The device can be reconfigured later or permanently configured to perform several operations. Examples of programmable logic devices include programmable logic arrays, programmable array logic, field-programmable logic arrays, field-programmable gate arrays, and other suitable hardware devices. Furthermore, processes can be implemented as organic components integrated with inorganic components, or as organic components only, excluding humans. For example, a process can be implemented as a circuit of organic semiconductors.

[0025] The computer system 150 is a physical hardware system and includes one or more data processing systems. If the computer system 150 has multiple data processing systems, these systems communicate with each other using a communication medium. The communication medium can be a network. The data processing systems can be selected from at least one of the following: a computer, a server computer, a tablet computer, or other suitable data processing systems.

[0026] As illustrated, the computer system 150 includes several processor units 152 capable of executing program code 154 that carries out the process in the exemplary example. As used herein, one of the several processor units 152 is a hardware device and consists of hardware circuits, such as those on an integrated circuit, that process instructions and program code that operate the computer. When the several processor units 152 execute program code 154 for the process, the several processor units 152 are one or more processor units that may be on the same computer or on different computers. In other words, the process can be distributed among processor units on the same computer or on different computers within the computer system. Furthermore, the several processor units 152 may be the same type of processor unit or different types of processor units. For example, the several processor units could be at least one of a single-core processor, a dual-core processor, a multi-processor core, a general-purpose central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), or some other type of processor unit.

[0027] Figure 2 shows a process flow for processing and resolving threshold alarms according to an exemplary embodiment. An aircraft maintenance user interface 100 may be used to help monitor and perform operations in process 200.

[0028] The AHM analyst monitors for new alerts (operation 202). When a new alert 204 is received, the AHM analyst uses the aircraft maintenance user interface 100 to document the work instructions (created in the airline maintenance planning system) related to the alert (operation 206).

[0029] Work instructions are supplied to the compliance manager and the maintenance team. The maintenance team receives the work instructions (operation 208) and completes the work instructions (operation 210).

[0030] The compliance manager can use the aircraft maintenance user interface 100 to monitor the alarm after it has been addressed (operation 212) and mark the work instruction as complete (operation 214). The compliance manager also verifies the work to ensure that the issue that generated the alarm 204 has actually been resolved (operation 216). If the issue is resolved, the alarm is marked as resolved and completed (operation 218) and can be reviewed in the AHM history (operation 220).

[0031] If the completed work order does not resolve the problem, a rework alert 222 is generated and process 200 is restarted.

[0032] Figure 3 shows a scheduled maintenance interface for new alarms according to an exemplary embodiment. Interface 300 is an example interface for displaying new threshold alarms and "no report" alarms.

[0033] Interface 300 includes an alarm indicator 302 that displays thresholds or “not reported” alarms regarding aircraft systems that must be addressed for aircraft maintenance compliance.

[0034] The compliance window indicator 304 displays a normalized sliding scale representing the percentage of lead time elapsed between the time an alert was received and the maintenance compliance deadline. In this example, the compliance window starts on the left and progresses to the deadline on the right. If the issue causing the alert is not resolved by the time the indicator reaches the deadline, the aircraft in question must be grounded, resulting in lost flight time and revenue.

[0035] The remaining units indicator 306 displays the number of units used (e.g., elapsed time, flight time, or flight cycles) out of the total number of allocated units that measure the opportunity for the remaining lead time window. The remaining units indicator 306 visually displays the counting number on the normalized sliding scale of the compliance window indicator 304.

[0036] The flight stage indicator 308 displays the flight stage at which a threshold alert is generated. In this example, the flight stages are divided into OOOI, which stand for Out (leaving the gate), Off (takeoff), On (landing, "weight on the wheels"), and In (arriving at the gate).

[0037] The history indicator 310 displays the operational history of the aircraft system that led to the beginning of a problem that triggers a threshold alarm. The history indicator 310 shows the flight segment leading to the aircraft's current flight segment at the right end of the indicator (flight segment 0). A black circle in the history indicator indicates an alarm generated during that flight segment.

[0038] Figure 4B shows a threshold alarm detail panel according to an exemplary embodiment. The alarm detail panel 400 slides in as a second layer in response to a click on the threshold alarm title displayed on the alarm indicator 302 within the interface 300. The alarm detail panel 400 includes the aircraft system history 402 leading to the threshold alarm. The current parametric value 404 of the aircraft system is displayed against the threshold 406.

[0039] Compliance status 408 indicates the current status of the workflow for addressing threshold alerts. Compliance status 408 can be updated via a dropdown menu 410 for selecting the status display, as shown in Figure 4B.

[0040] The alarm details panel 400 also includes a link to document 412, which details the necessary maintenance tasks related to the aircraft system to resolve threshold alarms.

[0041] The alarm details panel 400 also includes a description 414 of threshold alarms and actions related to resolving threshold alarms.

[0042] Figures 5A to 5D show examples of status details panels that pop up in response to clicking on the workflow status to invoke the dropdown menu 410. The dropdown menu 410 allows the user to select a specific version of the status display according to the stage of the workflow.

[0043] Figure 5A shows a status indicator to mark as addressed according to an exemplary embodiment. Using the status indicator 500A to mark as addressed, work can be initiated on a new threshold alarm. It includes a list 502 of maintenance tasks related to the aircraft system for resolving the threshold alarm and a work instruction entry field 504.

[0044] Figure 5B shows an update status display according to an exemplary embodiment. After the work has begun, the threshold alarm update status display 500B adds an input field 506 to confirm that the work instruction has been completed.

[0045] Figure 5C shows a status indicator to mark as resolved according to an exemplary embodiment. After a work instruction is completed, the work must then be verified to ensure that the work has actually resolved the problem. The status indicator 500C to mark as resolved adds an input field 508 to confirm that the condition that triggered the threshold alarm has been resolved.

[0046] Figure 5D shows a status indicator to mark for rework according to an exemplary embodiment. If the completion of the work order does not adequately resolve the issue, the user can select rework status indicator 500D to initiate a new threshold alarm that should return the work to the work queue. Note that the rework alarm does not reset the compliance window.

[0047] Figures 6A and 6B show a dashboard user interface for post-response alarms according to an exemplary embodiment. After new threshold alarms are marked as post-response (meaning work has been initiated to address them), they are moved to interface 600. Interface 600 includes data fields similar to interface 300 for new alarms, but also includes a compliance status field 602 and an associated work instruction field 604. Status detail panels 500A–500D can also be accessed and updated via the compliance status field 602.

[0048] In addition to generating an alarm when an aircraft system exceeds an operating threshold, an alarm is also generated if no reports regarding the aircraft system are sent by the aircraft during a specified number of flight cycles. For example, during a flight cycle, reports may be received for all aircraft systems except for brake service reports.

[0049] Figure 7 shows a “No Report” detail panel in an exemplary embodiment, which occurs when a report from the associated aircraft system is not received during a specified number of flight cycles. The Report Suspension detail panel 700 is similar to the Warning detail panel 400 but is specific to the missing report.

[0050] The “No Report” details panel 700 slides in as a second layer in response to clicking the “No Report” alert displayed on the alert indicator 302. The “No Report” details panel 700 includes links 702 for each report received regarding the flight cycles of the aircraft system in question for a specified number of flight cycles.

[0051] The “No Report” details panel 700 further includes a link 704 to documentation detailing the necessary manual procedures and compliance tasks related to the aircraft system to address the outage for maintenance compliance purposes.

[0052] Compliance status 708 provided details about the current status of the “No Report” alert.

[0053] Figure 8 shows a flowchart illustrating the process for dealing with a complete transmission failure, in which no data is received from the aircraft for a specified period (assuming 24 hours in this example, but other periods can also be used). If the aircraft is not transmitting, mitigating this transmission failure depends on whether the aircraft is flying at the time of the data failure.

[0054] If an aircraft is in service, a data failure can impact compliance. While the aircraft may normally be in service, the ACARS system is experiencing a Minimum Equipment List (MEL) delay. As a result, the AHM did not receive data from the ACARS channel. In this situation, the operator must schedule manual maintenance tasks and verify the aircraft's status with the AHM every 24 hours. ACARS MEL situations typically last 1-3 days.

[0055] Alternatively, the aircraft may be in normal service, but there may be another reason why the AHM is not receiving data from the aircraft. The operator must identify and investigate the data failure, schedule manual maintenance tasks to ensure compliance, and verify the aircraft's status using the AHM every 24 hours.

[0056] If the aircraft is not in service, compliance is not affected. An aircraft may be grounded due to unforeseen issues such as system malfunctions (e.g., the air conditioning system not working). If an aircraft is grounded, the operator must verify its status every 24 hours and ensure that the aircraft is transmitting data properly when it returns to service. Such unscheduled groundings typically last between 24 and 72 hours.

[0057] Alternatively, the aircraft may be undergoing a lengthy routine maintenance check. In this situation, the operator must verify the expected completion date at regular intervals and ensure that the aircraft is properly transmitting data when it returns to service. A lengthy maintenance check typically lasts for three to four months.

[0058] Figures 9A and 9B show a fleet data health indicator according to an exemplary embodiment. As shown in Figures 9A and 9B, the fleet data health indicator 900 includes different categories of data transmission outages as described above. Following the flowchart in Figure 8, these categories include Unknown Reason, ACARS MEL, Other, Grounded, and Under Maintenance Check. The fleet data health indicator 900 may also include a category of recently recovered aircraft that have resumed data transmission.

[0059] Figure 10A shows an aircraft data health details panel according to an exemplary embodiment. Clicking entry 902 under the category of Fleet Data Health Display 900 causes the aircraft data health details panel 1000A to slide in as a second layer. The aircraft data health details panel 1000A includes a status summary 1002A and a history of aircraft data failures 1004.

[0060] The aircraft data health details panel 1000A further includes a list of manual maintenance tasks 1006 that may be required as a result of data failures.

[0061] The data failure reason dropdown menu 1008 on the aircraft data health details panel 1000A, shown in Figure 10B, allows the user to select and change the data failure category. In response to the selection of a data failure category from the dropdown menu, a special details panel pops up. The special details panel contains data entry fields specific to the selected data failure category.

[0062] In this example, the selected aircraft entry 902 in Fleet Data Health Indicator 900 is currently listed as unknown due to data failure reason.

[0063] Figure 11 shows a specific detail panel for the ACARS MEL category of data failure in an exemplary embodiment. Detail panel 1100 is conceptually similar to the “No Report” detail panel 700, but its functionality is extended to cover situations where no data has been received from the aircraft regarding any of the aircraft systems.

[0064] The detail panel 1100 pops up in response to the selection of ACARS MEL from the dropdown menu 1008. The detail panel 1100 includes a reason field 1102 that lists the reason for the selected data failure and a MEL log page entry field 1104. The detail panel 1100 provides a work order entry field 1106 that lists the manual maintenance tasks 1108 required as a result of the ACARS MEL data failure. The detail panel 1100 also includes a status notification 1110 that indicates how often the status must be checked during an ACARS MEL data failure.

[0065] Figure 12 shows an aircraft data health detail panel after an entry for an ACARS MEL-related data failure, according to an exemplary embodiment. In response to ACARS MEL being selected as the reason for the data failure and saving the data entered in the required fields of detail panel 1100, the updated aircraft data health detail panel 1000B includes an extended status summary 1002B which includes the MEL log page and MEL reference, as well as an identification of the person who made the entry.

[0066] The ACARS MEL selection also moves each aircraft entry from the Unknown Reason column in Fleet Data Health Indicator 900 to the ACARS MEL column.

[0067] Status notification 1204 provides information about the time until the next verification specific to the ACARS MEL status. A list of the required maintenance task steps 1206 is presented in an expandable menu. Each registered system may require a different set of manual maintenance tasks.

[0068] Action description 1208 describes the current status of the workflow for addressing data failures and the individuals responsible for entering and updating information related to the workflow.

[0069] The dropdown menu 1210 allows the user to access the details panel to update or resolve the status of data failures.

[0070] Figure 13 shows an update details panel for a pending classified data failure, according to an exemplary embodiment. The details panel 1300 is invoked via a drop-down menu 1210 and is used to provide a verification update in accordance with the requirements listed in the status notification 1204.

[0071] Input field 1302 allows the user to verify the status of an ongoing ACARS MEL status, which can be supplemented by a comment in additional comment entry field 1304. Verification resets the verification period, as described in status notification 1306.

[0072] Figure 14 shows the aircraft data health detail panel upon resumption of data reception, according to an exemplary embodiment. Once the problem causing the data failure is resolved, the aircraft resumes transmitting data, which is received by the AHM.

[0073] The resumption of this data transmission is indicated by status notification 1402 on the aircraft data health details panel 1000C. As situation-based monitoring resumes for the aircraft, the user must ensure that any manual work orders scheduled during the data failure have been canceled to maintain compliance.

[0074] Here too, the dropdown menu 1210 allows the user to access the details panel to resolve the data failure status.

[0075] Figure 15 shows a resolution details panel for a pending classified data fault according to an exemplary embodiment. The resolution details panel 1500 pops up in response to a resolution selection from the drop-down menu 1210.

[0076] Input field 1502 allows the user to verify that the MEL deferral has been resolved. Input field 1504 allows the user to verify that all work orders associated with the MEL status have been completed or canceled if they are no longer needed. These verifications can be supplemented with comments in additional comment entry field 1506.

[0077] Each type of data failure requires a different detail panel to account for the differences in their respective timelines and workflows.

[0078] Figure 16 shows a specific detail panel for the data failure maintenance check category in an exemplary embodiment. Referring back to Figure 10, the detail panel 1600 is invoked by selecting a maintenance check from the drop-down menu 1008.

[0079] The detail panel 1600 includes a reason field 1602 for listing the reasons for the selected data failure and an estimated end date entry field 1604 for specifying the expected completion date of the maintenance check.

[0080] The detail panel 1600 also includes a status notification 1606 that indicates how often the status must be verified during a maintenance check.

[0081] Unlike ACARS MEL data failures, this situation poses no compliance threat, and therefore there are no work instructions to specify in relation to the service check. The service work performed during the service check is predetermined and standardized.

[0082] Figure 17 shows an aircraft data health detail panel after verification of maintenance check status information, according to an exemplary embodiment. In response to maintenance check being selected as the reason for the data failure and saving the data entered in the required fields of detail panel 1600, the updated aircraft data health detail panel 1000D includes an extended status summary 1002C which includes identification of the person making the entry.

[0083] The maintenance check selection also moves each aircraft entry from the "Unknown Reason" column in the Fleet Data Health Indicator 900 to the "Maintenance Check" column.

[0084] Status notification 1704 provides information about the time until the next verification specific to the maintenance check. A list of registered maintenance tasks 1706 is presented in an expandable menu.

[0085] Action description 1708 indicates the current status of the maintenance check and the person responsible for entering and updating information related to the workflow.

[0086] Figure 18 shows an aircraft data health details panel indicating updated verification of the maintenance check status, according to an exemplary embodiment. If the maintenance check is not verified within the required 30 days, a notification will appear in the status notification 1804 of the aircraft data health details panel 1000E. Here again, the drop-down menu 1210 can be used to pull up special detail panels to update or resolve the situation.

[0087] Figure 19 shows an update details panel for a pending service check according to an exemplary embodiment. The update details panel 1900 is invoked from the drop-down menu 1210 and is used to provide verification of an ongoing service check. The update details panel 1900 is similar to the details panel 1600 and provides an input field 1902 for updating the verification status to confirm that the service check is still in progress.

[0088] Figures 20A and 20B show an automated resolution notification in the fleet data health display according to an exemplary embodiment. When an aircraft emerges from a data failure due to grounding or maintenance checks and begins retransmitting data, an automated resolution notification 2000 is displayed in the fleet data health display 900, and the aircraft entry is automatically moved to the recently recovered column.

[0089] The view button 2002 within the automatic resolution notification 2000 can be used to call up the resolved status details panel, as shown in Figure 21.

[0090] Figure 21 shows a resolved status details panel that provides details of the automatic resolution of data faults according to an exemplary embodiment. The resolved status details panel 2100 provides details of the data faults that have been automatically resolved.

[0091] Figure 22 shows a specific detail panel for other categories of data failures according to an exemplary embodiment. The detail panel 2200 pops up in response to other selections from the drop-down menu 1008. The detail panel 2200 includes a reason field 2202 that lists the reasons for the selected data failure. The detail panel 2200 provides a work order entry menu 2204 and an additional comments entry field 2206 to provide an explanation for why the data failure does not fall into any of the other categories. The detail panel 2200 also includes a status notification 2208 that indicates how often (e.g., every 24 hours) the status should be checked during a data failure.

[0092] Figure 23 shows an aircraft data health detail panel after an entry for another related data failure, according to an exemplary embodiment. In response to selecting "Other" as the reason for the data failure and saving the data entered in the required fields of detail panel 2200, the updated aircraft data health detail panel 1000F includes an extended status summary 1002D which includes an identification of the person making the entry.

[0093] Other options also move each aircraft entry from the "Unknown Reason" column to the "Other" column in the Fleet Data Health Indicator 900.

[0094] Status notification 2304 provides information about the time until the next verification, which is specific to other circumstances. A list of work instructions 2306 for the required maintenance tasks is presented in an expandable menu. Each work instruction may require a different set of maintenance tasks.

[0095] Action description 2308 indicates the current status of the workflow to address the transmission suspension and the person responsible for entering and updating information related to the workflow.

[0096] The dropdown menu 1210 here also allows the user to access the details panel to update or resolve the data failure status.

[0097] Figure 24 shows an update detail panel for other classified data failures according to an exemplary embodiment. The detail panel 2400 is invoked via a dropdown menu 1210 within the aircraft data health detail panel 1000F and is used to provide verification updates for each requirement listed in the status notification 2304.

[0098] Input field 2402 allows the user to verify that the status of other data failure conditions is continuing, which can be supplemented by comments in additional comment entry field 2404.

[0099] Figure 25 shows a specific detail panel for other categories of data failures according to an exemplary embodiment. The detail panel 2500 pops up in response to other selections from the drop-down menu 1008. The detail panel 2500 includes a reason field 2502 that lists the reasons for the selected data failure. The detail panel 2200 provides an additional comment entry field 2504. The detail panel 2500 also includes a status notification 2506 that indicates how often (e.g., every 24 hours) the status must be checked during a data failure.

[0100] Figure 26 shows an aircraft data health detail panel after an entry for a grounding-related data failure, according to an exemplary embodiment. In response to selecting grounding as the reason for the data failure and saving the data entered in the required fields of detail panel 2500, the updated aircraft data health detail panel 1000G includes an extended status summary 1002E which includes an identification of the person making the entry.

[0101] The grounding selection also moves each aircraft entry from the "Unknown Reason" column to the "Grounding" column in the Fleet Data Health Indicator 900.

[0102] Status notification 2604 provides information about the time until the next verification specific to the downtime. A list of required manual maintenance tasks 2606 is presented in an expandable menu. Each procedure may require a different set of maintenance tasks.

[0103] Action description 2608 indicates the current status of the workflow to address the transmission suspension and the person responsible for entering and updating information related to the workflow.

[0104] Here too, the dropdown menu 1210 allows the user to access the details panel to update or resolve the data failure status.

[0105] Figure 27 shows an update details panel for a data failure classified as grounding, according to an exemplary embodiment. The details panel 2700 is invoked via a dropdown menu 1210 within the aircraft data health details panel 1000G and is used to provide verification updates for each requirement listed in the status notification 2604.

[0106] Input field 2702 allows the user to update the verification time for aircraft that are grounded, which may be supplemented by comments in additional comment entry field 2704.

[0107] Figure 28 shows a block diagram of a data processing system according to an exemplary embodiment. The data processing system 2800 may be used to implement the computer system 150 in Figure 1. In this exemplary example, the data processing system 2800 includes a processor unit 2804, memory 2806, persistent storage 2808, a communication unit 2810, an input / output (I / O) unit 2812, and a communication framework 2802 that provides communication between these units and the display 2814. In this example, the communication framework 2802 takes the form of a bus system.

[0108] The processor unit 2804 functions to execute instructions for software that can be loaded into memory 2806. Depending on the specific implementation, the processor unit 2804 may be multiple processors, multiprocessor cores, or some other type of processor. In one example, the processor unit 2804 comprises one or more conventional general-purpose central processing units (CPUs). In an alternative embodiment, the processor unit 2804 comprises one or more graphical processing units (GPUs).

[0109] Memory 2806 and persistent storage 2808 are examples of storage devices 2816. A storage device is any hardware capable of storing at least one of the following information, such as data, program code in executable form, or other suitable information, temporarily, persistently, or both temporarily and persistently. Storage devices 2816 may also be referred to as computer-readable storage devices in these exemplary examples. Memory 2806 in these examples may be, for example, random-access memory or any other suitable volatile or non-volatile storage device. Persistent storage 2808 may take various forms depending on the particular implementation.

[0110] For example, the persistent storage 2808 may include one or more components or devices. For example, the persistent storage 2808 may be a hard drive, flash memory, a rewritable optical disk, a rewritable magnetic tape, or any combination thereof. The medium used by the persistent storage 2808 may be removable. For example, a removable hard drive may be used for the persistent storage 2808. In these exemplary examples, the communication unit 2810 provides communication with other data processing systems or devices. In these exemplary examples, the communication unit 2810 is a network interface card.

[0111] The input / output unit 2812 enables the input and output of data to and from other devices that may be connected to the data processing system 2800. For example, the input / output unit 2812 may provide a connection for user input via at least one of a keyboard, mouse, or some other suitable input device. Furthermore, the input / output unit 2812 may send output to a printer. The display 2814 provides a mechanism for displaying information to the user.

[0112] Instructions for at least one of an operating system, an application, or a program may be placed in a storage device 2816 that communicates with the processor unit 2804 through a communication framework 2802. Processes of different embodiments may be executed by the processor unit 2804 using computer implementation instructions that may be placed in memory, such as memory 2806.

[0113] These instructions are referred to as program code, computer-readable program code, or computer-readable program code, which can be read and executed by the processor of the processor unit 2804. In different embodiments, the program code may be embodied on different physical or computer-readable storage media, such as memory 2806 or persistent storage 2808.

[0114] The program code 2818 is arranged in a functional form on a selectively removable computer-readable medium 2820 and can be loaded or transferred to the data processing system 2800 for execution by the processor unit 2804. The program code 2818 and the computer-readable medium 2820 form a computer program product 2822 in these exemplary examples. In one example, the computer-readable medium 2820 may be a computer-readable storage medium 2824 or a computer-readable signaling medium 2826.

[0115] In these exemplary examples, the computer-readable storage medium 2824 is not a medium for propagating or transmitting the program code 2818, but a physical or tangible storage device used to store the program code 2818. The computer-readable storage medium 2824 as used herein should not be interpreted as a transient signal in itself, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmitting media (e.g., light pulses passing through optical fiber cables), or electrical signals transmitted through wires.

[0116] Alternatively, the program code 2818 may be transferred to the data processing system 2800 using a computer-readable signal medium 2826. The computer-readable signal medium 2826 may be, for example, a propagated data signal containing the program code 2818. For example, the computer-readable signal medium 2826 may be at least one of an electromagnetic signal, an optical signal, or any other suitable type of signal. These signals may be transmitted over at least one of a communication link, such as a wireless communication link, an optical fiber cable, a coaxial cable, a wire, or any other suitable type of communication link.

[0117] The various components shown for the data processing system 2800 do not impose architectural limitations on how different embodiments may be implemented. Different exemplary embodiments may be implemented for the data processing system 2800 in a data processing system that includes components in addition to or instead of those shown. Other components shown in Figure 28 may differ from those shown in the exemplary examples. Different embodiments may be implemented using any hardware device or system capable of executing the program code 2818.

[0118] Exemplary embodiments of this disclosure may be described in relation to the aircraft manufacturing and maintenance method 2900 shown in Figure 29 and the aircraft 3000 shown in Figure 30. First, looking at Figure 29, a diagram of an aircraft manufacturing and maintenance method according to an exemplary embodiment is shown. During the production preparation stage, the aircraft manufacturing and maintenance method 2900 may include the specifications and design 2902 and material procurement 2904 of the aircraft 3000 shown in Figure 30.

[0119] During production, the components and subassemblies of the aircraft 3000 in Figure 30 are manufactured 2906 and system integration 2908 is carried out. Subsequently, the aircraft 3000 in Figure 30 can be brought into service 2912 after certification and transport 2910. While in service 2912 by the customer, the aircraft 3000 in Figure 30 is scheduled for periodic maintenance and inspections 2914, which may include improvements, reconfigurations, modifications, and other maintenance or service inspections.

[0120] Each of the processes of the Aircraft Manufacturing and Maintenance Method 2900 may be carried out or performed by a system integrator, a third party, an operator, or a combination of these. In these examples, the operator may be a customer. For the purposes of this explanation, a system integrator may include, but is not limited to, any number of aircraft manufacturers and subcontractors of large systems; a third party may include, but is not limited to, any number of vendors, subcontractors, and suppliers; and an operator may be an airline, leasing company, military, and service organization, etc.

[0121] Referring here to Figure 30, a diagram of an aircraft in which an exemplary embodiment may be carried out is shown. In this example, the aircraft 3000 is produced by the aircraft manufacturing and maintenance method 2900 of Figure 29 and may include a fuselage 3002 having several systems 3004 and internal 3006. Examples of systems 3004 include one or more of the propulsion system 3008, electrical system 3010, hydraulic system 3012, and environmental system 3014. Any number of other systems may be included. Although an aerospace example is shown, various exemplary embodiments may be applied to other industries such as the automotive industry.

[0122] The apparatus and methods embodied herein may be employed in at least one of the steps of the aircraft manufacturing and maintenance inspection method 2900 shown in Figure 29. In one exemplary example, components or subassemblies produced in the manufacturing of components and subassemblies 2906 of Figure 29 can be manufactured or produced in a similar manner to components or subassemblies produced while the aircraft 3000 is in service 2912 of Figure 29. In yet another example, one or more device embodiments, method embodiments, or combinations thereof can be used in production stages such as the manufacturing of components and subassemblies 2906 of Figure 29, and system integration 2908. One or more device embodiments, method embodiments, or combinations thereof may be used while the aircraft 3000 is in service 2912, during maintenance and inspection 2914 of Figure 29, or both. By using several different exemplary embodiments, the assembly of the aircraft 3000 can be significantly accelerated, the cost of the aircraft 3000 can be reduced, or the assembly of the aircraft 3000 can be accelerated and the cost of the aircraft 3000 can be reduced simultaneously.

[0123] As used herein, the phrase “at least one of” means, when used with a list of items, that one or more different combinations of the listed items may be used, and only one of each item in the list may be required. In other words, “at least one of” means that any combination and number of items from the list may be used, but not all items in the list may be required. An item may be a specific object, thing, or category.

[0124] For example, non-limitingly, “at least one of item A, item B, or item C” could include item A, item A and item B, or item B. This example could also include item A, item B, and item C, or item B and item C. Naturally, any combination of these items is possible. In some exemplary examples, “at least one of” could, for example, without limitation, two item A, one item B, and ten item C, four item B and seven item C, or other preferred combinations.

[0125] As used herein, "several" when used in relation to an item means one or more items. For example, "several different types of networks" means one or more different types of networks. In illustrative examples, "set" when used with a reference item means one or more items. For example, "set of metrics" means one or more of the metrics.

[0126] The descriptions of various exemplary embodiments are presented for illustrative and explanatory purposes only and are not intended to be exhaustive or to limit to embodiments of the form disclosed. The various exemplary examples describe components that perform actions or operations. In the exemplary embodiments, components can be configured to perform the actions or operations described. For example, a component may have a structural configuration or design that gives the component the ability to perform the actions or operations described as being performed by the component in the exemplary examples. Furthermore, the terms “includes,” “includes,” “has,” “contains,” and their variations thereof, as used herein, are intended to be as comprehensive as the term “comprises” as an open transitional term that does not exclude any additional or other elements.

[0127] Many modifications and variations will be apparent to those skilled in the art. Furthermore, various exemplary embodiments may offer different features compared to other preferred embodiments. One or more selected embodiments have been chosen and described to best illustrate the principles and practical applications of the embodiments and to enable those skilled in the art to understand the disclosure for various embodiments with various modifications suitable for specific intended uses. [Explanation of Symbols]

[0128] 100 Aircraft Maintenance User Interfaces 102 Alarm Indicator 104 Compliance Window Indicator 106 Remaining Unit Indicator 108 Compliance Status 110 Alarm Details Panel 114 No Report Details Panel 116 New Alert 118 Alarm after response 120 Fleet Data Health Indicator 122 Categories 124 categories 126 Aircraft Health Details Panel 150 Computer Systems 152 processor units 154 Program Code 156 Display Systems 200 processes 202 Monitor new alerts 204 New Alert 206 Create work instructions 208 Receive work instructions 210 Complete work instructions 212 Monitor alarms after response. 214 Mark work instructions as complete. 216 Is it effective? 218 Mark alarm as resolved / closed 220 Review in history 222 Rework the alarm. 300 Interfaces 302 Descriptions 304 Compliance Window 306 remaining units 308 Flight Stage Indicator 310 History Indicator 400 Alarm Details Panel 402 Aircraft System History 404 Parametric Values 406 threshold 408 Compliance Status 410 Dropdown Menu 412 documents 414 descriptions Status display after 500A compatibility update 500B Threshold Alarm Update Status Display 500C Resolved Status Display 500D Rework Status Display 502 List of maintenance tasks 504 Work Order Entry Field Input fields 506, 508 600 Interfaces 602 Compliance Status Field 604 Work Instruction Field, 700 Report Stop Details Panel 702 Link for reporting 704 Link to document 708 Compliance Status 900 Fleet Data Health Indicator 902 entries 1000A, 1000B, 1000C, 1000D, 1000E, 1000F, 1000G Aircraft Data Health Details Panel 1002A Status Summary 1002B, 1002C, 1002D, 1002D Extended Status Summary 1004 History of data failures 1006 List of manual maintenance tasks 1008 Data Failure Reason Dropdown Menu 1100 ACARS MEL Category Specific Details Panel 1102 Reason field 1104 MEL log page entry field 1106 Work Instruction Entry Field 1108 List of manual maintenance tasks 1110 Status Notification 1002B Extended Status Summary 1204 Status Notification 1206 List of necessary maintenance task procedures 1208 Action Description 1210 Dropdown Menu 1300 Update Details Panel 1302 Input Fields 1304 Additional Comment Entry Field 1306 Status Notification 1402 Status Notification 1500 Resolution Details Panel 1502 Input Fields 1504 Input Fields 1506 Additional Comment Entry Field 1600 Data Failure Maintenance Check Category Specific Details Panel 1602 Reason field 1604 Estimated end date entry field 1606 Status notification indicating frequency 1704 Status Notification 1706 Registered maintenance tasks 1708 Action Description 1804 Status Notification 1900 Update Details Panel 1902 Input Fields 2000 Automatic Resolution Notification 2002 View Button 2100 Resolved Status Details Panel 2200 Specific details panel for data failures in other categories 2202 Reason field: List the reasons for data failures. 2204 Work Instruction Entry Menu 2206 Additional Comment Entry Field 2208 Status notification indicating frequency 2304 Status Notification 2306 List of work instructions 2308 Action Description 2400 Detailed Panel 2402 Input Fields 2404 Additional Comment Entry Field 2500 Detail Panel 2502 Reason field 2504 Additional Comment Entry Field 2506 Status notification indicating frequency 2604 Status Notification 2606 List of Manual Maintenance Task Procedures 2608 Action Description 2700 Detail Panel 2702 Input Fields 2704 Additional Comment Entry Field 2800 Data Processing Systems 2802 Communication Framework 2804 Processor Unit 2806 memory, 2808 persistent storage 2810 Communication Unit 2812 Input / Output Unit 2814 Display 2816 Storage Devices 2818 Program Code 2820 Computer-readable media 2822 Computer Program Products 2824 Computer-readable storage media 2826 Computer-readable signaling medium 2900 Aircraft Manufacturing and Maintenance Inspection Methods 2902 Specifications and Design 2904 Material Procurement 2906 Manufacturing of components and subassemblies 2908 System Integration 2910 Authentication and Transport 2912 in service 2914 Maintenance and inspection 3000 aircraft 3002 aircraft 3004 System 3006 Internal 3008 Propulsion System 3010 Electrical Systems 3012 Hydraulic System 3014 Environmental Systems

Claims

1. Aircraft maintenance user interface (300), A warning indicator (302) that displays warnings related to aircraft systems that must be addressed for aircraft maintenance compliance, A compliance window indicator (304) displays a normalized sliding scale of the percentage of lead time elapsed between the aforementioned alarm and the maintenance compliance deadline, A remaining unit indicator (306) that displays the number of units used out of the total number of allocated units to measure the remaining lead time, and An aircraft maintenance user interface equipped with the following features.

2. The aforementioned unit is elapsed time, Flight time or The interface according to claim 1, comprising a flight cycle.

3. The interface according to claim 1, further comprising a history indicator (310) that displays the operation history of the aircraft system leading to the aforementioned alarm.

4. The interface according to claim 1, further comprising an alarm detail panel (400) which slides in as a second layer in response to a click of the alarm displayed on the alarm indicator, the alarm detail panel including the history of the aircraft system leading to the alarm (402), the current parametric value of the aircraft system against a threshold (404), and the compliance status (408).

5. The interface according to claim 4, wherein the alarm detail panel further includes a link (412) to a document detailing the necessary maintenance tasks related to the aircraft system in order to resolve the alarm.

6. The interface according to claim 4, wherein the alarm detail panel further comprises a description (414) of the alarm and the actions relating to the resolution of the alarm.

7. The interface according to claim 4, further comprising a second detail panel (500) that pops up in response to a click of the compliance status, the second detail panel including necessary maintenance tasks (502) related to the aircraft system for resolving the alarm and an entry field (504) for entering work instructions.

8. The interface according to claim 7, wherein the second detail panel further comprises an input field (506) for confirming that a work instruction has been completed.

9. The interface according to claim 7, wherein the second detail panel further comprises an input field (508) for confirming that the condition causing the alarm has been resolved.

10. The interface according to claim 1, further comprising a detail panel (700) for no-report reports, which slides into view as a second layer in response to clicking on a no-report alert displayed on the alert indicator, the detail panel for no-report reports providing links (702) to each report received during a flight cycle relating to the aircraft system during a specified number of flight cycles.

11. The interface according to claim 10, wherein the details panel for the no-report report further includes a link (704) to a document detailing the necessary manual procedures and compliance tasks related to the aircraft system for maintenance compliance.

12. The interface according to claim 1, further comprising a fleet data health display (900) including different categories of data failures for automated periodic reporting relating to the aircraft system.

13. The aforementioned category is, Reason unknown, ACARS MEL, others, Service suspension, or The interface according to claim 12, comprising at least one of the following: undergoing maintenance check.

14. The interface according to claim 12, further comprising a category for recently recovered aircraft that have resumed sending reports.

15. The interface according to claim 12, further comprising an aircraft data health details panel (1000) which slides into view as a second layer in response to clicking an entry under one of the categories, wherein the aircraft data health details panel includes a history of data failures for the aircraft (1004) and a drop-down menu (1008) for selecting and changing data failure categories.

16. The interface according to claim 15, wherein the aircraft data health details panel further includes a list (1006) of manual maintenance tasks required as a result of the data failure.

17. The interface according to claim 15, further comprising a special detail panel (1100) that pops up in response to the selection of a data failure category from the dropdown menu within the aircraft data health detail panel, wherein the special detail panel includes data entry fields specific to the selected category of data failure.

18. The interface according to claim 12, wherein a resolution notification (2000) automatically pops up in the fleet data health display when the aircraft resumes transmitting the periodic reports.

19. A system for displaying an aircraft maintenance user interface, A storage device that stores program instructions, operably connected to the aforementioned storage device, and executing the program instructions to the aforementioned system, A warning indicator (302) that displays warnings related to aircraft systems that must be addressed for aircraft maintenance compliance, A compliance window indicator (304) displays a normalized sliding scale of the percentage of lead time elapsed between the aforementioned alarm and the maintenance compliance deadline, A remaining unit indicator (306) that displays the number of units used out of the total number of allocated units to measure the remaining lead time, and One or more processors configured to display A system for displaying an aircraft maintenance user interface, equipped with the necessary features.

20. A computer program product for displaying an aircraft maintenance user interface, A computer-readable storage medium having program instructions embodied to perform a display operation, A warning indicator (302) that displays warnings related to aircraft systems, which must be addressed for aircraft maintenance compliance, A compliance window indicator (304) displays a normalized sliding scale of the percentage of lead time elapsed between the aforementioned alarm and the maintenance compliance deadline, A remaining unit indicator (306) that displays the number of units used out of the total number of allocated units to measure the remaining lead time, and A computer program product that includes the following features.

Images