Patent Description:
Exemplary embodiments pertain to the art of aircraft cargo management, and more particularly to an aircraft cargo monitoring and maintenance system.

Items to be shipped via aircraft cargo are first loaded onto a Unit Load Device (ULD). ULDs are specially configured pallets or specially configured containers. ULDs are available in various sizes, shapes and capacities. Once a ULD is loaded with cargo items, the ULD is loaded onto the aircraft through the cargo hold doorway. The ULDs are moved in the cargo compartment by Power Drive Units (PDUs) mounted at floor level at fixed intervals down the length of the compartment. Once the ULD has been stowed in its final position it is restrained by means of mechanical or electro-mechanical restraint system. Freighter Common Turntables (FCTs) are installed in & forward of the doorway and can steer the ULDs to various positions as needed for IN/OUT, FWD/AFT, or pallet rotation modes. Multiple ULDs are brought onboard the aircraft and each is placed in its respective stowed position. PDUs and FCTs are referred to collectively as Line Replaceable Units.

A Master Control Panel, an Outside Control Panel and/or Local Control Panels are used in any combination or independently to control movement of ULDs. The cargo systems provide a dedicated display to enable the operator to monitor the status of ULD position and the status of the cargo line replaceable units. The master control panel provides the control system operation status and cargo system status to the display. The display additionally enables the operator to perform various maintenance operations on the cargo systems.

Conventional cargo system implements Cargo Maintenance Display Units (CMDUs) to display the cargo system status during normal operation (cargo loading mode). The CMDUs are fixed on the aircraft interior wall of each cargo compartments. <FIG> and <FIG> depict various modes of an exemplary CMDU in a conventional cargo maintenance system. <FIG> shows the cargo loading mode of a CMDU, which is used primarily in the cargo loading process. The cargo loading mode screen in a CMDU displays the graphical representation of the cargo compartment and displays the status information (like drive status, orientation and retraction status) of the cargo line replaceable unit. The CMDU receives the control system operation status and cargo system status from the master control panel.

The CMDU is also the maintenance interface for selecting maintenance operations to be run by the master control panel. The operator uses the CMDU menus and screens to display the requested Built-In Test Equipment fault log information and/or to initiate an interactive test. <FIG> shows a user interface screen displaying a maintenance mode screen of an existing CMDU, which is used in the cargo maintenance process. The cargo maintenance mode is accessed through the cargo loading mode and is generally password secured. The maintenance mode provides diagnostic information about the line replaceable units and allows the operator to execute diagnostic tests. The CMDU displays the cargo system status & control system operation status of the cargo compartment in which the CMDU is installed. In conventional cargo management systems, as depicted in <FIG>, the CMDU has a limited viewable display area, and the amount of details that are displayed in single page/screen is very high due to large amount of line replaceable units in each cargo compartment. The visual pages for the cargo loading mode and the maintenance mode are displayed separately in the CMDU of conventional systems, such as the CMDU displays depicted in <FIG> and <FIG>. This can make it difficult for the operator to correlate the details of the faulty line replaceable units (PDUs and/or FCTs) and make it difficult to perform diagnostic tests on the faulty line replaceable units.

Another weakness of conventional systems is that the process of identifying the fault/error information in the CMDU is not intuitive. The operator has to identify the line replaceable unit number from the cargo loading page, run diagnostic test in the maintenance test page and check the fault/error log information in the fault log page. This process can be time consuming, and may confuse the operator. The actual movement of the ULDs are not displayed in CMDU, instead the movement of the ULDs have to be monitored through the line replaceable unit status. This makes it difficult to understand the display and demands well trained personnel to monitor the cargo loading operations.

It is advantageous, therefore, to provide an intuitive system that answers these long-felt needs in the art of aircraft cargo monitoring and maintenance. <CIT> and <CIT> relate to cargo load and monitoring systems.

Disclosed is a system, as defined in claim <NUM>, for monitoring and maintaining aircraft cargo holds.

Also disclosed is a method, as defined in claim <NUM>, for monitoring and maintaining aircraft cargo holds.

<FIG> is a system diagram of a cargo maintenance display system <NUM> (hereafter "system <NUM>") according to an embodiment. <FIG> illustrates the high-level architecture of the system <NUM>, which is a cargo handling system that interfaces a Cargo Monitoring and Maintenance Display (CMMD) unit <NUM> (hereafter "command unit <NUM>") with multiple cargo moving equipment of an existing cargo handling system. The system <NUM> includes the command unit <NUM> connected (either with hard wire or wirelessly) with a plurality of control units via a network of communication channels <NUM>.

During a cargo loading operation, multiple ULDs are brought onboard the aircraft and each is placed in its respective stowed position. The ULDs are moved in the cargo compartment by Power Drive Units (PDUs) mounted at floor level of the aircraft cargo hold at fixed intervals down the length of the compartment. Freighter Common Turntables (FCTs) are installed in & forward of the doorway and can steer the ULDs to various positions as needed for IN/OUT, FWD/AFT, or pallet rotation modes. As previously described with respect to conventional systems, PDUs and FCTs are referred to collectively as Line Replaceable Units, or LRUs. Each master control panel installed in a respective cargo compartment is connected with the LRUs installed and/or operating in that particular compartment. For example, the master control panel <NUM> operates in cargo compartment <NUM>, master control panel <NUM> operates in cargo compartment <NUM>, and master control panel <NUM> operates in compartment <NUM>.

A Master Control Panel (MCP) controls movement of ULDs (upon which the cargos are sitting). The cargo system <NUM> provides a dedicated display to enable the operator to monitor the status of ULD position and the status of the cargo line replaceable units. The master control panels <NUM>, <NUM>, <NUM> provide the control system operation status and cargo system status to the display. The display additionally enables the operator to perform various maintenance operations on the cargo systems.

According to embodiments described herein, the command unit <NUM> includes a display (e.g., a display <NUM> as shown with respect to <FIG>). The display <NUM> is configured to show a status of the ULDs and a status of cargo Line Replaceable Units (LRUs) during a cargo item loading operation. As explained hereafter, the status of the ULDs and the LRUs can include information such as equipment and cargo item position, movement, faults and/or errors encountered during the movement of the cargo items, and other information. The cargo items, which are loaded on the ULDs, are moved by the system <NUM> into various separate compartments of the aircraft cargo hold.

An aircraft can include separate compartments for stowing cargos. For example, as shown in <FIG>, an aircraft cargo hold includes a main deck cargo compartment <NUM>, a forward lower lobe cargo compartment <NUM>, and an aft lower lobe cargo compartment <NUM>. Each of the cargo compartments <NUM>, <NUM>, and <NUM>, include a separate master control panel. For example, the main deck cargo compartment <NUM> includes a master control panel <NUM>, which is operatively connected (either wired or wirelessly) with a plurality of control units <NUM> (e.g., the PDUs, FCTs, etc.) for moving the cargos.

In other aspects, the command unit <NUM> is configured to display a live video feed from any cargo compartment of interest on the aircraft for visual tracking of the ULDs on the display <NUM> via a graphic user interface. <FIG> depicts a graphical user interface <NUM>, showing a representation of a main deck cargo compartment of an aircraft.

The graphical user interface <NUM> of the CMMD unit displays representations having two different aspect scales for a user to understand a status of individual and collective cargos as they are loaded onto and stowed in their respective compartments. The graphical user interface includes a compartment view <NUM>, and a detailed view <NUM>. The graphic user interface <NUM> further includes a selection panel <NUM>.

The compartment view <NUM> shows graphical representations of the cargo compartment with all the LRUs <NUM> in the cargo compartment <NUM>. Other features of interest are depicted such as, for example, a cargo doorway <NUM>.

The user interface <NUM> depicts a sliding marker window <NUM> (a box like representation) indicative of a region of interest shown in the above detailed view <NUM>.

As depicted in <FIG>, user interface <NUM> can output a current position of the ULDs <NUM>, movement of the ULDs <NUM>, and the status of all cargo LRUs <NUM> in the cargo compartment. The zones of the cargo compartment are depicted as zones <NUM>. These features are described in greater detail below with respect to the detailed view <NUM>. User input of a box limit selection enables the user to slide the marker window <NUM> from FWD to AFT of the cargo compartment view <NUM>. By sliding the marker window <NUM>, the detailed view <NUM> of the cargo compartment view <NUM> updates with the same representation as shown in the compartment view <NUM>, but in a zoomed view that shows greater detail. For example, according to an embodiment, the detailed view <NUM> shows the zoomed-in/detailed view of the cargo compartment region under focus of the marker window <NUM>. In one aspect, the detailed view <NUM> shows the details of the LRUs <NUM>, status of the LRUs <NUM>, movement of ULDs <NUM>, and fault/ error status of the LRUs <NUM> in detail. The detailed view <NUM> also enables an operator to select the faulty LRUs <NUM> for more detailed diagnostic information. Details of the compartment can include details such as, for example, a dividing marker <NUM> that marks the division between compartment zones.

The user interface <NUM> is a user touch enabled (e.g., a touch screen) user environment. The touch enabled display environment enables an operator to slide the detailed view <NUM> from a FWD position view (to the left of the cargo compartment) to an AFT position view (to the right of the cargo compartment).

The selection panel <NUM> shows a selection option <NUM> to select the different cargo compartments in the aircraft, and a selection options <NUM> to switch between a plan view as shown in <FIG> and a selection option for a video view <NUM> (depicted hereafter in <FIG>). The selection panel <NUM> also provides an option <NUM> to receive a user selection for different ULDs <NUM> upon which to focus.

<FIG> shows the command unit <NUM> displaying the Forward Lower Lobe (Forward LL) cargo compartment. <FIG> depicts a view screen of Aft Lower Lobe (Aft LL) cargo compartment. <FIG> and <FIG> are discussed in conjunction with one another. As depicted in <FIG>, a ULD <NUM> that is under focus is shown in the cargo compartment view <NUM>, within the marker window <NUM>. In the detailed view <NUM>, the zoomed view of the ULD <NUM> is shown, with a direction of travel arrow <NUM> indicating the travel direction of the ULD <NUM>. The display of the user interface <NUM> changes position in sync with the movement of the ULD <NUM>.

<FIG> depicts the display of faulty LRU <NUM> in both compartment view <NUM> and detailed view <NUM>. <FIG> also shows the display of fault/error indicator <NUM>. In one aspect, the fault/error indicator <NUM> provides information regarding a faulty LRU <NUM>. The detailed view <NUM> includes a popup interface <NUM> showing the detailed diagnostic information with recommended action(s). For example, the popup interface provides an option <NUM> for the operator to perform the diagnostic test on the faulty LRU <NUM>.

<FIG> depicts a user interface display of a diagnostic test result <NUM> updated to the popup interface by the processor <NUM>.

Operation of the system is now described in greater detail. <FIG> will be referenced together, in conjunction with following figures for ease of description. First, an operator selects the intended cargo compartment from the Selection Panel <NUM> (e.g., "Main Deck Compartment" <NUM>, as shown in <FIG>). Based on the user input, the processor <NUM> communicates with the selected MCP of the selected cargo compartment via. wired and/or wireless communication channel <NUM> (as shown in <FIG>). The command unit <NUM> displays the graphical representation of the selected cargo compartment in both the compartment view <NUM> and the detailed view <NUM>. The status of ULDs & the status of available LRUs in the selected cargo compartment are updated by the processor <NUM> in the compartment & detailed views <NUM>, <NUM>. The faulty LRUs <NUM> are displayed with fault/ error indicators <NUM> for easy identification of the problematic system component (shown in <FIG>). The operator can monitor the ULDs currently being driven through the control panels, and select the faulty LRU <NUM> from the detailed view <NUM> to diagnose the fault/ error. The command unit <NUM> then displays the popup interface <NUM> with basic fault information and the recommended actions to fix the faults. The operator may initiate the diagnostic test for the faulty LRU from the popup interface <NUM> by selecting the option <NUM>. As shown in <FIG>, the detailed diagnostic test result <NUM> is displayed to the operator.

The command unit <NUM> enables the operator to monitor the ULDs very closely. The operator selects the ULD <NUM> to track from the selection panel <NUM>. The marker window <NUM> in the compartment view <NUM> focuses the selected ULD and the detailed view <NUM> shows & focuses the selected ULD. As the ULD is driven towards FWD or AFT from the control panel (the direction of which shown with direction arrows <NUM>) the detailed view display <NUM> moves the background of the cargo compartment by maintaining the ULD <NUM> in the center of the display. The marker window <NUM> in the compartment view <NUM> moves in-line with the ULD <NUM> movement.

<FIG> and <FIG> respectively illustrate the operation of monitoring and tracking of ULDs. <FIG> shows that the ULD #<NUM><NUM> is currently in Zone #<NUM> and is highlighted using a different color. The compartment view <NUM> shows that the marker window <NUM> is centered at ULD #<NUM><NUM>. The detailed view <NUM> shows the LRUs of the cargo compartment in detail with the display centered at ULD #<NUM><NUM>. The detail view shows that ULD #<NUM><NUM> is currently over PDUs #25R, #26R, #27R and #28R. The display shows that the ULD #<NUM><NUM> is driven in the FWD direction and is represented by the direction arrow <NUM> on the ULD #<NUM><NUM>.

<FIG> shows that the ULD #<NUM><NUM> had moved from Zone #<NUM> to Zone #<NUM>. The detailed view <NUM> shows that the ULD #<NUM><NUM> is currently over PDUs #21R, #22R, #23R and #24R. In this case, the background of the display has moved to the right; with ULD #<NUM><NUM> still in focus and centered in the display. Note that the fault/error indicator <NUM> provides an indication of an erroneous LRU <NUM>.

The command unit <NUM> enables an operator to monitor the movement of ULDs via a live video feed/stream. <FIG> shows the AFT view video feed from the Forward LL cargo compartment of the aircraft cargo hold. Upon the selection of Video View <NUM> from the selection panel <NUM>, the command unit <NUM> displays the live video feed <NUM> from the selected cargo compartment (Forward LL Compartment, e.g.). The command unit <NUM> displays the video feed <NUM> from either FWD or AFT looking camera in the cargo compartment.

Embodiments of the present invention benefit the art in a number of ways. For example, connectivity to multiple cargo compartments makes the use of the system intuitive and easy to use. The command unit <NUM> connects to the MCP in any of the three cargo compartments. This helps in weight reduction due to removal of multiple CMDUs from main deck, forward lower lobe and aft lower lobe cargo compartments.

The CMMD unit displays a fault/error indicator on the faulty LRUs enabling the operator to retrieve the fault information and perform diagnostic test on the selected faulty LRU. This helps in faster debugging & diagnostics of faults in the Cargo Handling System without switching between multiple display pages/ screens.

In other aspects, the industry is benefitted by monitoring & tracking the cargo loading inside aircraft. The command unit <NUM> enables selective monitoring of ULD loading, and focuses on the selected ULD by centering it on the display screen and tracking the movement. The CMMD unit also provides the live video feed from the cargo compartment to visually track the ULD.

<FIG> depicts a flow diagram <NUM> of a method for monitoring and maintaining aircraft cargos. As shown in block <NUM>, the method <NUM> includes connecting a plurality of master control panels with at least one Line Replaceable Unit (LRU) operating in a cargo compartment of an aircraft and at least one unit load device (ULD). The at least one ULD and the at least one LRU are configured to move a cargo unit in the cargo compartment based on a control signal from the master control panel.

As shown in block <NUM>, the method includes connecting a command unit operatively with each master control panel of the plurality of master control panels. As depicted in block <NUM>, the processor <NUM> is configured for retrieving, via the processor <NUM>, a status of the cargo from each of the plurality of master control panels. At block <NUM>, the processor <NUM> displays, on an output device, a status of the at least one ULDs and a status of the at least one LRUs via the processor.

<FIG> illustrates a block diagram of an exemplary computing environment and computer system <NUM> for use in practicing the embodiments described herein. The environment and system described herein can be implemented in hardware, software (e.g., firmware), or a combination thereof. In an exemplary embodiment, a hardware implementation can include a microprocessor of a special or general-purpose digital computer, such as a personal computer, workstation, minicomputer, or mainframe computer. Computer <NUM> therefore can embody a general-purpose computer. In another exemplary embodiment, the implementation can be part of a mobile device, such as, for example, a mobile phone, a personal data assistant (PDA), a tablet computer, etc..

As shown in <FIG>, the computer <NUM> includes processor <NUM>. Computer <NUM> also includes memory <NUM> communicatively coupled to processor <NUM>, and one or more input/output adapters <NUM> that can be communicatively coupled via system bus <NUM>. Memory <NUM> can be communicatively coupled to one or more internal or external memory devices via a storage interface <NUM>. Communications adapter <NUM> can communicatively connect computer <NUM> to one or more networks <NUM>. System bus <NUM> can communicatively connect one or more user interfaces via input/output (I/O) adapter <NUM>. I/O adapter <NUM> can connect a plurality of input devices <NUM> to computer <NUM>. Input devices can include, for example, a keyboard, a mouse, a microphone, a sensor, etc. System bus <NUM> can also communicatively connect one or more output devices <NUM> via I/O adapter <NUM>. Output device <NUM> can include, for example, a display, a speaker, a touchscreen, etc..

Processor <NUM> is a hardware device for executing program instructions (aka software), stored in a computer-readable memory (e.g., memory <NUM>). Processor <NUM> can be any custom made or commercially available processor, a central processing unit (CPU), a plurality of CPUs, an auxiliary processor among several other processors associated with the computer <NUM>, a semiconductor based microprocessor (in the form of a microchip or chip set), or generally any device for executing instructions. Processor <NUM> can include a cache memory <NUM>, which can include, but is not limited to, an instruction cache to speed up executable instruction fetch, a data cache to speed up data fetch and store, and a translation lookaside buffer (TLB) used to speed up virtual-to-physical address translation for both executable instructions and data. Cache memory <NUM> can be organized as a hierarchy of more cache levels (L1, L2, etc.).

Processor <NUM> can be disposed in communication with one or more memory devices (e.g., RAM <NUM> ROM <NUM> one or more external databases <NUM>, etc.) via a storage interface <NUM>. Storage interface <NUM> can also connect to one or more memory devices including, without limitation, one or more databases <NUM>, and/or one or more other memory drives (not shown) including, for example, a removable disc drive, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-<NUM>, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives can be, for example, a drum, a magnetic disc drive, a magneto-optical drive, an optical drive, a redundant array of independent discs (RAID), a solid-state memory device, a solid-state drive, etc..

Memory <NUM> can include random access memory (RAM) <NUM> and read only memory (ROM) <NUM>. RAM <NUM> can be any one or combination of volatile memory elements (e.g., DRAM, SRAM, SDRAM, etc.). ROM <NUM> can include any one or more nonvolatile memory elements (e.g., erasable programmable read only memory (EPROM), flash memory, electronically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), tape, compact disc read only memory (CD-ROM), disk, cartridge, cassette or the like, etc.). Moreover, memory <NUM> can incorporate electronic, magnetic, optical, and/or other types of non-transitory computer-readable storage media. Memory <NUM> can also be a distributed architecture, where various components are situated remote from one another, but can be accessed by processor <NUM>.

The instructions in memory <NUM> can include one or more separate programs, each of which can include an ordered listing of computer-executable instructions for implementing logical functions. In the example of <FIG>, the instructions in memory <NUM> can include an operating system <NUM>. Operating system <NUM> can control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.

The program instructions stored in memory <NUM> can further include application data <NUM>, and for a user interface <NUM>.

I/O adapter <NUM> can be, for example but not limited to, one or more buses or other wired or wireless connections. I/O adapter <NUM> can have additional elements (which are omitted for simplicity) such as controllers, microprocessors, buffers (caches), drivers, repeaters, and receivers, which can work in concert to enable communications. Further, I/O adapter <NUM> can facilitate address, control, and/or data connections to enable appropriate communications among the aforementioned components.

I/O adapter <NUM> can further include a display adapter coupled to one or more displays. I/O adapter <NUM> can be configured to operatively connect one or more input/output (I/O) devices <NUM>, <NUM> to computer <NUM>. For example, I/O adapter <NUM> can connect a keyboard and mouse, a touchscreen, a speaker, a haptic output device, or other output device. Output devices <NUM> can include but are not limited to a printer, a scanner, and/or the like. Other output devices can also be included, although not shown. Finally, the I/O devices connectable to I/O adapter <NUM> can further include devices that communicate both inputs and outputs, for instance but not limited to, a network interface card (NIC) or modulator/demodulator (for accessing other files, devices, systems, or a network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, and the like.

According to some embodiments, computer <NUM> can include a wireless communications adapter <NUM>. Wireless communications adapter <NUM> can include GPS, cellular, mobile, and/or other communications protocols for wireless communication.

In some embodiments, computer <NUM> can further include communications adapter <NUM> for coupling to a network <NUM>.

Network <NUM> can be an IP-based network for communication between computer <NUM> and any external device. Network <NUM> transmits and receives data between computer <NUM> and devices and/or systems external to computer <NUM>. In an exemplary embodiment, network <NUM> can be a managed IP network administered by a service provider. Network <NUM> can be a network internal to an aircraft, such as, for example, an avionics network, etc. Network <NUM> can be implemented in a wireless fashion, e.g., using wireless protocols and technologies, such as WiFi, WiMax, etc. Network <NUM> can also be a wired network, e.g., an Ethernet network, an ARINC <NUM> network, a controller area network (CAN), etc., having any wired connectivity including, e.g., an RS232 connection, RS422 connection, etc. Network <NUM> can also be a packet-switched network such as a local area network, wide area network, metropolitan area network, Internet network, or other similar type of network environment. The network <NUM> can be a fixed wireless network, a wireless local area network (LAN), a wireless wide area network (WAN) a personal area network (PAN), a virtual private network (VPN), intranet or other suitable network system.

Network <NUM> can operatively connect computer <NUM> to one or more devices including device <NUM>, device <NUM>, and device <NUM>. Network <NUM> can also connect computer <NUM> to one or more servers.

If computer <NUM> is a PC, workstation, laptop, tablet computer and/or the like, the instructions in the memory <NUM> can further include a basic input output system (BIOS) (omitted for simplicity). The BIOS is a set of routines that initialize and test hardware at startup, start operating system <NUM>, and support the transfer of data among the operatively connected hardware devices. The BIOS is typically stored in ROM <NUM> so that the BIOS can be executed when computer <NUM> is activated. When computer <NUM> is in operation, processor <NUM> can be configured to execute instructions stored within the memory <NUM>, to communicate data to and from the memory <NUM>, and to generally control operations of the computer <NUM> pursuant to the instructions.

The computer readable storage medium can be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.

Computer readable program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

Claim 1:
A system for monitoring and maintaining a cargo hold of an aircraft comprising:
a plurality of master control panels (<NUM>, <NUM>, <NUM>) each operatively connected with at least one Line Replaceable Unit (LRU) operating in a cargo compartment of an aircraft and at least one unit load device (ULD), the at least one LRU configured to move the at least one ULD in the cargo compartment based on a control signal from the master control panel;
a command unit (<NUM>) operatively connected with each master control panel of the plurality of master control panels (<NUM>, <NUM>, <NUM>), the command unit (<NUM>) comprising a graphical user interface (<NUM>) and a processor configured to
retrieve, via the processor, a status of at least one on status of the at least one ULD and a status of the status of at least one LRU from each of the plurality of master control panels (<NUM>, <NUM>, <NUM>);
display on the graphical user interface (<NUM>), the status of the at least one ULD of a plurality of ULDs and the status of the at least one LRU via the processor; and
a pop-up window linked to a visual representation of a faulty LRU of the at least one LRU, and configured to
display the faulty LRU, including detailed diagnostic information with recommended actions;
display an option for a user to run a diagnostic test and display detailed diagnostic test results of the diagnostic test;
wherein the display provides together on the graphical user interface (<NUM>) a compartment view (<NUM>) and a detailed view (<NUM>), the detailed view (<NUM>) being for a region of interest indicated by a sliding marker window (<NUM>) located on the compartment view (<NUM>),
wherein:
the graphical user interface (<NUM>) is a user touch enabled display environment enabling an operator to slide the detailed view (<NUM>) from a FWD position view of the cargo compartment, to an AFT position view of the cargo compartment; and
the detailed view (<NUM>) includes the pop-up window (<NUM>) showing the detailed diagnostic information with recommended actions,
and wherein by user input, the sliding marker window (<NUM>) is configured to slide from FWD to AFT on the cargo compartment view (<NUM>), and the detailed view (<NUM>) of the cargo compartment view (<NUM>) responsively updates with a same representation as shown in the compartment view (<NUM>) in a zoomed view that shows greater detail.