Systems and methods for status reporting for aircraft

An aircraft monitoring system includes a sensor operatively connected to at least a portion of an aircraft, a memory configured to store instructions, and a processor disposed in communication with the memory and the sensor. The processor, upon execution of the instructions, is configured to display a graphical representation of the portion of the aircraft reflecting real-time monitoring activity, and display a monitoring controller. A method of providing a graphical user interface (GUI) for an aircraft monitoring system includes displaying a graphical representation of at least a portion of an aircraft's geometry reflecting real-time monitoring activity. The method includes displaying one or more monitoring controllers. Each monitoring controller is associated with at least a portion of an aircraft monitoring system and a location on the aircraft's geometry.

BACKGROUND

1. Description of Related Art

Aircraft monitoring systems, such as health monitoring systems are comprised of sensors, smart sensors, distributed controllers, hub controllers, Ground Station(s) and potentially servers that all play a role in the collection and processing of the data for such systems. There are multiple functions that take time from the time that data collection is started for a given portion or sub-system of the overall system to the time that results are available to an operator. For example, sensing, data transfer, data conversion, data re-factoring, data storage, data mining and data analysis functions are typically performed before an operator can view the aircraft health results in such a context. Additionally, in modern aircraft health monitoring systems it is possible to have multiple smart sensors, controllers and ground stations simultaneously collecting and processing data for the same aircraft at the same time but at different rates.

In sensor based aircraft health monitoring systems, such as health and usage management systems (HUMS) and structural health monitoring (SHM) systems, results are typically displayed as text and only for a single subsystem at any given time. The conventional techniques have been considered satisfactory for their intended purpose. However, there is an ever present need for improved aircraft monitoring systems.

SUMMARY

An aircraft monitoring system includes a sensor operatively connected to at least a portion of an aircraft, a memory configured to store instructions, and a processor disposed in communication with the memory and the sensor. The processor, upon execution of the instructions, is configured to display a graphical representation of the portion of the aircraft, and display a monitoring controller.

Each monitoring controller can include an active progress indicator representative of the progress toward a monitoring sub-function for the portion of the aircraft in real-time. Each monitoring controller can include at least one status indicator representative of the real-time status of a monitoring sub-function for the portion of the aircraft.

In accordance with another aspect, a method of providing a graphical user interface (GUI) for an aircraft monitoring system includes displaying a graphical representation of at least a portion of an aircraft's geometry. The method includes displaying one or more monitoring controllers. Each monitoring controller is associated with at least a portion of an aircraft monitoring system and a location on the aircraft's geometry.

In accordance with some embodiments, displaying the one or more monitoring controllers includes displaying each monitoring controller in a respective position more proximate to a portion of the graphical representation that corresponds to the location on the aircraft's geometry associated with the monitoring controller than to other portions of the graphical representation. The graphical representation can include displaying a first portion of the aircraft's geometry and a second portion of the aircraft's geometry. Displaying the one or more monitoring controllers can include displaying a first monitoring controller associated with the first portion. The first monitoring controller can be positioned closer to the first portion than the second portion.

Each monitoring controller can include at least one of an active progress indicator or a passive status indicator. Each monitoring controller can include a user entry area for receiving at least one of an on command, a start command or a download command. Displaying the one or more monitoring controllers can include displaying, for each monitoring controller, a plurality of passive status indicators indicative of statuses of respective sub-functions and, simultaneously, an active progress indicator indicative of which of the sub-functions is in progress. The method can include displaying both the active progress indicator and one of the plurality of passive status indicators to which the active progress indicator relates with a common graphical theme in order for a user to easily ascertain an overall status of the sub-functions

The method can include providing a user entry area for receiving a start command configured and adapted to begin monitoring sub-functions for a plurality of monitoring controllers. The method can include displaying an active progress indicator that corresponds to the monitoring controller and is representative of the progress of a monitoring sub-function for the portion of the aircraft monitoring system associated therewith. The monitoring sub-function can include acquiring data, downloading data, transferring data, converting data and/or uploading data.

The method can include displaying a passive status indicator representative of the status of a monitoring sub-function for the portion of the aircraft monitoring system associated therewith. The method can include displaying a health status of at least one portion of the aircraft with a health indicator overlaid onto a portion of the graphical representation of the aircraft to which the health status pertains. The method can include providing a user entry area associated with the health indicator for receiving user commands to initiate system action. Displaying the graphical representation can include displaying the graphical representation on a computing device having a display screen. Displaying the one or more monitoring controllers can include displaying the one or more monitoring controllers on a computing device having a display screen.

In accordance with another aspect, a non-transitory computer readable storage medium has one or more computer programs stored therein associated with an aircraft monitoring system. The computer programs include instructions, which, when executed by a processor of a computer system, cause the processor to display a graphical representation of at least a portion of an aircraft's geometry and display one or more monitoring controllers. Each monitoring controller is associated with at least a portion of the aircraft monitoring system and a location on the aircraft's geometry.

DETAILED DESCRIPTION

Reference will now be made to the drawings wherein like reference numerals identify similar structural features or aspects of the subject disclosure. For purposes of explanation and illustration, and not limitation, a partial view of an exemplary embodiment of a graphical user interface (GUI) for an aircraft monitoring system in accordance with the disclosure is shown inFIG. 1and is designated generally by reference character100. Other embodiments of methods and systems in accordance with the disclosure, or aspects thereof, are provided inFIGS. 2-12, as will be described. The systems and methods described herein provide a graphical approach to status reporting that allows the operator to stay focused on results and other tasks at hand while still presenting a compact graphical status that can be easily overlaid on relevant result-oriented depictions of the aircraft.

The compactness of the systems and methods of the present disclosure provide advantages over traditional systems and methods. With traditional systems and methods, the nature of the display (text) does not permit compact, multi-dimensional status information that provides status and progress toward that status. Instead, traditional GUIs for aircraft monitoring systems typically only include a single status for the overall system in text form. Embodiments of the present disclosure permit display of the status and progress for multiple simultaneous subsystems that run at different rates. Moreover, embodiments of the present disclosure utilize easily recognizable status patterns that can be distinguished at a glance even when viewed from a distance. Additionally, the compact, graphical nature of the embodiments of the present disclosure provide status reporting that is easily viewed on modern devices such as tablets or smart phones.

As shown inFIG. 1, a graphical user interface (GUI)100includes a graphical representation of an aircraft's geometry102. A method of providing a GUI, e.g. GUI100, includes displaying a graphical representation of at least a portion of an aircraft's geometry, e.g. graphical representation102. The graphical representation102includes a fuselage section104and two wing sections106,108. The graphical representation102is shown with grid lines that schematically represent segments105of a given monitored area, e.g. the fuselage or wing portions. Multiple segments105are typically monitored as a group as part of a single aircraft monitoring system (or a portion thereof), e.g. segments105of a given wing section106are monitored together and the monitoring is controlled by a given one of monitoring controllers110a-110d.

The method includes displaying monitoring controllers, e.g. monitoring controllers110a-110d. The display of the monitoring controllers110a-110dis dynamic (e.g. the display can change depending on which monitoring controllers are being used, or which ones the user wishes to view). For example, if the fuselage is being monitored, monitoring controller110bthat corresponds to an aircraft monitoring system, e.g. aircraft monitoring system150(described below and shown inFIG. 12), that monitors the fuselage (or the portion thereof) will be displayed. This approach keeps the operator focused on the geometry of the aircraft by enabling in-place status updates within the context of the relevant aircraft geometry. Displaying the graphical representation102can include displaying the graphical representation102and/or the one or more monitoring controllers110a-110don a computing device having a display screen, e.g. display162, as shown inFIG. 12.

With reference now toFIGS. 1-4, each monitoring controller110a-110dis associated with a respective aircraft monitoring system150(described below), or a portion thereof. The cursor indicator (which is show as an icon of a hand) is optional and may not be necessary in embodiments where a touch interface is used. Moreover, while four cursor indicators are shown, only one is typically shown at one time. The method includes displaying each of the monitoring controllers in a respective position that is closer to the portion of the graphical representation that corresponds to the actual location on the aircraft's geometry associated with the monitoring controller than to other portions of the graphical representation. For example, displaying the graphical representation102includes displaying a first portion of the aircraft's geometry, e.g. a wing section106, and a second portion of the aircraft's geometry, e.g. a fuselage104. As another example, displaying monitoring controller110aincludes displaying monitoring controller110ain a position that is closer to the wing section106than the fuselage104, as monitoring controller110ais associated with at least a portion of an aircraft monitoring system, e.g. system150, that monitors the actual wing section.

With reference now toFIGS. 3-4, each monitoring controller110a-110dincludes an active progress indicator114and at least one of passive status indicators116a-116e. The method herein includes depicting multiple process states in real-time by way of multiple monitoring controllers110a-110d, and also provides a second dimension of overall status for each monitoring controller by depicting completion states through passive status indicators116a-116ealongside one or more real-time, active state indicators, e.g. progress indicators114. In this way, each monitoring controller110a-110dreports the status of a given process and a steady progression toward a completion state of that process in real-time and in an easily discernable manner. The passive status indicators116a-116e, as described in more detail below, remain visible even after the function associated therewith has been completed thereby displaying a de-facto roadmap toward the final completed process state.

With reference now toFIGS. 3-4, each monitoring controller110a-110dincludes respective user entry areas118a-118cfor receiving an “on” command, a “start” command or a “download” command. Each user entry area118acorresponds to an area for receiving an “on” command, user entry area118bcorresponds to an area for receiving a “start” command and118ccorresponds to an area for receiving a “download” command. User entry areas118a-118care dynamically selectable. Moreover, those skilled in the art will readily appreciate that each monitoring controller can include other user entry areas that correspond to other commands and/or functions. Once selected, user entry area118bis configured and adapted to trigger at least one sensor, e.g. sensor152, of an aircraft monitoring system, e.g. system150(described below) to begin monitoring. User entry area118cis associated with a downloading function and, when selected, will trigger a downloading function for the portion of the aircraft monitoring system associated therewith. The method also includes providing a user entry area, e.g. user entry area119, that is configured and adapted to trigger all (or a selected group of) the monitoring controllers, e.g. monitoring controllers110a-110d(thereby providing the ability to control multiple aircraft monitoring systems or portions thereof) and the corresponding sensors that are operatively connected thereto. User entry area119includes three separate user entry areas119a-119c, similar to118a-118c, except that user entry areas119a-119ccan trigger monitoring functions (and their respective sub-functions) for a plurality of monitoring controllers.

Monitoring controllers110a-110dare well-suited to partial processing scenarios. For example, if sensors associated with monitoring controllers110a-110dhave already acquired data and the data is currently stored in memory156of aircraft monitoring system150. The operator can opt to perform a “Download Only” function that downloads pre-existing data from the system150without performing a real-time data acquisition. This, in turn, is reflected by the status indicators116a-116edescribed below. For example, instead of showing a status indicator116aassociated with acquiring, only116b-116ewould be shown. There are other scenarios where one or more of the process states (and therefore process indicators116a-116e) could be intentionally skipped. Any skipped process state would be readily ascertainable because of the lack of one or more indicators116a-116ewould be visually apparent.

As shown inFIG. 4, the method includes displaying a plurality of passive status indicators, e.g. one or more of passive status indicators116a-116e, representative of the status of a monitoring sub-function for the portion of the aircraft monitoring system, e.g. aircraft monitoring system150, associated therewith. The monitoring functions (e.g. the sub-functions) includes acquiring data, downloading data, transferring data, converting data, analyzing data, and/or uploading data. Status indicators116a-116eare representative of the end-states for respective sub-functions, e.g. when a given sub-function is in progress or completed, its status indicator is visible. In this way, status indicators116a-116ereadily show the status of the overall monitoring function for a given controller110a-110dand their associated aircraft monitoring system.

The method includes displaying an active progress indicator, e.g. active progress indicator114, representative of which of the sub-functions is in progress and/or the status of the sub-function for the portion of the aircraft monitoring system associated therewith. The method includes displaying both the active progress indicator and one of the plurality of passive status indicators to which the active progress indicator relates with a common graphical theme, e.g. the common pattern of active progress indicator114cand passive status indicator116cto which it relates, in order for a user to easily ascertain an overall status of the sub-functions. This method of displaying on GUI100provides a compact representation of complex status information that can be readily ascertained from a distance. This approach enables the operator to stay focused on incremental results while still viewing the overall status of the system. By utilizing high contrast, well differentiated images, e.g. by way of the patterns shown inFIGS. 6A-9B, it is easier to understand the status of the aircraft monitoring system at a glance (even when viewed from a distance). This results in status monitoring that is conducive to being displayed and viewed on modern devices such as tablets and smartphones.

With continued reference toFIGS. 3-4, the method includes displaying a health status, e.g. the health status indicated by cross-hatching113b, color or the like, of at least one portion of the aircraft with a health indicator113boverlaid onto at least one segment, e.g. the segment105, of the graphical representation of the aircraft's geometry102to which the health status pertains. The method includes providing a user entry area associated with the health indicator113bfor receiving user commands to initiate system action. In the embodiment ofFIGS. 3-4, user entry area is defined by the segment112bof the graphical representation102overlaid with health indicator113b, such that by touching, clicking or otherwise selecting segment112b, a user can select one or more actions to be taken in response to the health indicator. This can include initiating maintenance, scheduling further inspection, or the like.

The progression of the display functions of the monitoring controllers110a-110dof the GUI is depicted byFIGS. 5A-9B.FIGS. 5A-5Cdepict a portion of one of controllers110a-110dincluding a status indicator116aand a progress indicator114a. Progress indicator114aofFIG. 5Ais shown as a series of concentric circles and is indicative of an aircraft monitoring system, e.g. aircraft monitoring system150, acquiring data from one or more sensors, e.g. sensors152.FIG. 5Bis the same asFIG. 5A, except thatFIG. 5Aincludes a progress icon115. Progress icon115inFIG. 5Bis shown as a series of circles arranged in an arcuate pattern overlaid on the status indicator116a. Progress icon115can be dynamic, for example, the circles can move in a ring-shaped path along status indicator116a(as shown by the position change of progress icon115fromFIG. 6A to 6B) to provide the operator with a sense that the system is continuing to perform a given function, which forFIG. 5B, is acquiring data. It is contemplated that in some embodiments, instead of being circles arranged in an arcuate pattern, a progress icon115can give more detail about the progress within a particular state (e.g. depicting percent complete overlaid on top of the particular status indicator116).FIG. 5Cshows status indicator116awithout progress indicator114a. InFIG. 5C, status indicator116ais a single circle that indicates that the acquiring is completed. The completion of the acquiring function is represented by the single circle without the inner concentric circles (e.g. the progress indicator114a) being present.

FIGS. 6A-6Bdepict two status indicators116aand116band a progress indicator114b. InFIG. 6A, status indicators for two separate functions, e.g. the acquiring/acquired (116a) and the downloading/downloaded (116b), are shown. InFIG. 6A, status indicator116arepresents the “acquired” state (due to the absence of the concentric circles). The presence of progress indicator114b(in the form of a downward arrow), is indicating that the downloading function is still in progress. InFIG. 6B, the end state for downloading is shown. In this depiction, status indicator116bshows the end-state for “downloaded” as a bar positioned underneath status indicator116a. (which has a circular shape). The status indicators116aand116bofFIG. 6B, without progress indicator114b, indicate that the system has finished acquiring and downloading.

FIGS. 7A-7Bdepict three status indicators116a-116cand a progress indicator114c, which is shown as a sideways facing arrow. The direction of arrow114c(e.g. progress indicator) is pointing toward the status that is in progress, which in the case ofFIG. 7Ais the transferring of data. InFIG. 7A, the acquiring and downloading functions have been completed and are signified by status indicators116aand116b. Status indicator116cand active progress indicator114calso share a common pattern. In a display, this pattern indicates to a user that the progress indicator114crelates to status indicator116c. A common graphical theme (pattern, color, or the like) can be used for other status indicators, e.g.116a,116band116d-116e, and their respective progress indicators114a-114band114d-114e. Each set can have a distinct pattern so as to easily distinguish between them, e.g.116aand114acan be striped as to distinguish between the dotted pattern of116cand114c. InFIG. 7B, the completion of the transferred state is shown by status indicator116c, e.g. the vertical bar on the right-hand side of status indicator116a, without the progress indicator114cbeing present. The pattern or graphical theme of status indicator116cremains in order to distinguish from other status indicators. Those skilled in the art will readily appreciate that the status indicators116aand116bfor acquiring and downloading are also depicted, thereby showing a steady progression toward a final completion state. Status indicators116aand116bcould also retain their respective colors or patterns in order to distinguish between the status indicators.

FIGS. 8A-8Bdepict four status indicators116a-116dand a progress indicator114d. InFIG. 8A, progress indicator114dis a looped arrow which indicates that the system is converting data. InFIG. 8A, the acquiring, downloading and transferring has been completed and each completed function is signified by a respective status indicator116a,116band116c. InFIG. 8B, the completion of the converting is represented by the horizontal bar of status indicator116don the top side of status indicator116awithout the progress indicator114dbeing present. Those skilled in the art will readily appreciate that the status indicators116a,116band116cfor acquiring, downloading and transferring are also depicted inFIG. 8B, thereby showing a steady progression toward a final completion state.

FIG. 9Adepicts five status indicators116a-116eand a progress indicator114e. The progress indicator114eis indicative of the system analyzing data. InFIG. 9B, the progress icon115is no longer shown as the analyzing function and the overall system process has been completed, which results in a completed status indicator116. Once ready, the results associated with a given monitor controller110a-110dare depicted as overlays on the aircraft geometry to which they correspond, as shown by the cross-hatched pattern in portion112bofFIG. 4. While the five status indicators116a-116e, their respective progress indicators114a-114e, and their given functions are described above as being displayed/performed in a sequence, those skilled in the art will readily appreciate that the display of at least two of the status indicators116a-116ecan be initiated concurrently with one another, or in a different order from that described above, and/or that the display of at least two of the progress indicators114a-114ecan be initiated concurrently with one another, or in a different order from that described above.

As shown inFIG. 10, in accordance with some embodiments, a status indicator216cincludes an error indicator218c. In this way, status indicator216cis used to show the status of a given function of the system, like status indicator116c, but also depicts whether there is an error in the function represented by status indicator216c. Error indicator218cis overlaid on status indicator216cto depict this. Other error indicators, like218c, can be used in conjunction with116a-116b, and/or116d-116e.FIG. 10depicts three status indicators216a-216cthat each correspond to a different function of the system, which are similar to116a-116c. Noticeably, no progress indicator, e.g.114c, or progress icon, e.g. progress icon115, is shown because the progress was interrupted by an error, which prompts the display of error indicator218c. Error indicator218cis shown overlaid on the status indicator116cfor the corresponding function (in this instance, transferring) that has the error. It is also contemplated that error indicator218ccould be a cancellation indicator or other end state. It is also contemplated that, in view of an error, a progress icon, e.g. progress icon115, could be included, for example, if the detected error does not stop the progress of the overall system.

Those skilled in the art will readily appreciate that the specific graphics and icons (e.g. arrows, bars, circles, etc.) listed above are only one example of the concept represented by this approach. The geometry of the graphics can be varied while still conforming to the embodiments of the present invention. For example, the styling of the graphics is flexible in this approach. The important piece is to include at least the following secondary states for each process state and to ensure that the styling sufficiently distinguishes between different states even when viewed from a distance. Moreover, while the graphics are depicted herein in black and white, varying patterns and/or colors may be used. For example, status indicators116a-116ecan be colored teal, orange, blue, fuchsia and green, respectively. The dynamic progress indicators114a-114ecan be similarly colored or patterned to match their associated status indicators,116a-116e, respectively. There are a variety of suitable colors that may be used. As long as the colors provide sufficient contrast with the background color to distinguish them from any background and that bright enough colors are used (again, relative to the background) to ensure that the differences in state can be easily detected from a distance.

With reference now toFIG. 11, another embodiment of status indicators and progress indicator is shown.FIG. 11shows nine status indicators316a-316e′. A square is formed by eight of the status indicators316b-316e′ and a circle in the middle of the square is the ninth status indicator316a. Each side of the square is broken into two regions, e.g.316aand316a′. In the embodiment ofFIG. 11, the arrow used for progress indicator314is angled toward its final state, or the state in progress, or in any other suitable way that designates which state it applies.

Those skilled in the art will readily appreciate that the shapes used for progress indicators114a-e,214and314do not have to be an arrow or concentric circles. Moreover, the shapes used for status indicators116a-116e,216a-216eand316a-316e′ do not have to be a circle or a bar. Depending on the number of system functions and statuses, the status indicators can form a square without a circle, a triangle with a circle, a trapezoid and so on.

FIG. 12shows a block diagram of an exemplary embodiment of an aircraft monitoring system150in accordance with embodiments of the present disclosure. The aircraft monitoring system150includes a plurality of sensors152operatively connected to at least a portion of an aircraft154. The system150includes a computer system153having a memory156configured to store instructions, and a processor158disposed in communication with the memory and the sensor. The processor158, upon execution of the instructions, is configured to display a graphical representation of at least a portion of an aircraft, e.g. graphical representation102, and display a monitoring controller, e.g. at least one of monitoring controllers110a-110d, as shown inFIGS. 1-4, on a display162. Each monitoring controller includes an active progress indicator representative of the function of the system150. Each monitoring controller includes at least one status indicator representative of the status of the system150, or a function thereof.

In accordance with another embodiment, a method for monitoring an aircraft with an aircraft monitoring system, e.g. system150, includes acquiring data with at least one sensor, e.g. sensor152, and downloading the data from the sensor to a computer system, e.g. computer system153. The method includes analyzing the data with the computer system (or another computer system external to the aircraft monitoring system) and includes providing a GUI as described above. For example, displaying a graphical representation, e.g. graphical representation102, of a portion of an aircraft on a display, e.g. display162. The method includes displaying a monitoring controller, e.g. at least one of monitoring controllers110a-110d, on the display.

In various embodiments, computer system153may be a server, a mainframe computer system, a workstation, a network computer, a desktop computer, a laptop, a tablet computer, a smartphone or the like, and/or include one or more of a field-programmable gate array (FPGA), application specific integrated circuit (ASIC), microcontroller, microprocessor, or the like.

Computer system153is only one example of a suitable system and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the disclosure described herein. Regardless, computer system153is capable of being implemented and/or performing any of the functionality set forth hereinabove.

Computer system153may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system153may be practiced in distributed data processing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed data processing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

Computer system153is shown inFIG. 12in the form of a general-purpose computing device. The components of computer system153may include, but are not limited to, one or more processors or processing units158, a system memory156, and a bus168that couples various system components including system memory156to processor158.

Computer system153typically includes a variety of computer system readable media. Such media may be any available media that is accessible by any portions of system150, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory156can include computer system readable media in the form of volatile memory, such as random access memory (RAM) and/or cache memory. Computer system153may further include other removable/non-removable, volatile/non-volatile computer system storage media, e.g. such as flash memory by way of a USB (universal serial bus). By way of example only, a storage system can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus168by one or more data media interfaces. As will be further depicted and described below, memory156may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the present disclosure.

Program/utility166, having a set (at least one) of program modules may be stored in memory156by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules generally carry out the functions and/or methodologies of embodiments of the present disclosure as described herein.

Computer system153may also communicate with one or more external devices160such as a keyboard, a pointing device, a display162, etc.; one or more devices that enable a user to interact with computer system153; and/or any devices (e.g., network card, modem, etc.) that enable display162, external devices160or sensors152to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces164. Still yet, computer system153can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via a network adapter. As depicted, the network adapter communicates with the other components of the system150via bus168. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system153. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

The block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block or in the above detailed description may occur out of the order noted in the figures or described in the above detailed description. For example, two blocks or functions shown/described in succession may, in fact, be executed substantially concurrently, or the blocks or functions may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams, function described in the above detailed description, combinations of blocks in the block diagrams or combination of functions described in the above detailed description, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It is to be appreciated the embodiments of the present disclosure include software algorithms, programs, or code that can reside on a computer useable medium having control logic for enabling execution on a machine having a computer processor. The machine typically includes memory storage configured to provide output from execution of the computer algorithm or program.

As used herein, the term “software” is meant to be synonymous with any code or program that can be in a processor of a host computer, regardless of whether the implementation is in hardware, firmware or as a software computer product available on a disc, a memory storage device, or for download from a remote machine. The embodiments described herein include such software to implement the logic, equations, relationships and algorithms described above. One skilled in the art will appreciate further features and advantages of the illustrated embodiments based on the above-described embodiments. Accordingly, the illustrated embodiments are not to be limited by what has been particularly shown and described, except as indicated by the appended claims.

The methods and systems of the present disclosure, as described above and shown in the drawings, provide for a method of providing a graphical user interface (GUI) for an aircraft monitoring system with superior properties including a more compact display, ease of use and multi-dimensional display of information. While the apparatus and methods of the subject disclosure have been shown and described with reference to preferred embodiments, those skilled in the art will readily appreciate that changes and/or modifications may be made thereto without departing from the scope of the subject disclosure.