System and method for detecting scale accumulation in a brewing device in an aircraft

Abstract

The present disclosure relates to a system and method for detecting scale accumulation in a brewing device in an aircraft. The system for detecting scale accumulation in aircraft brewing may include at least one of a monitoring subsystem or a monitoring component, at least one sensor device, and at least one controller. The at least one sensor device may be configured to generate and transmit data of an amount of scale accumulation in at least one of the monitored subsystems or monitored components. The at least one controller may be configured to receive the transmitted data, generate a trend based on the received data and at least one of historical data or a baseline, compare the trend to at least one threshold value, and generate a timeline for scale accumulation maintenance based on the comparison of the trend to the at least one threshold value. The data may be pressure difference data or heating temperature difference data.

Description

Background Art

[0001] The operation and / or reliability of selected aircraft equipment, such as brewing devices and other aircraft galley inserts, may depend on the quality of potable water accessed into the aircraft equipment. One measure of potable water quality includes the amount of scale buildup (e.g., calcium deposit buildup) in the fluid systems of the aircraft equipment. Scale buildup may result in reduced performance of the aircraft equipment and lead to eventual blockage within the fluid systems of the selected aircraft equipment, which may result in failure of the aircraft equipment. Summary of the invention

[0002] According to one or more embodiments of the present disclosure, a system for detecting scale accumulation in an aircraft brewing device is disclosed. The system may include at least one of the monitored subsystems or monitored components of the aircraft brewing device. The system may include at least one sensor device configured to generate and transmit pressure difference data of the amount of scale accumulation in at least one of the monitored subsystems or monitored components. The system may include at least one controller coupled to the at least one sensor device. The at least one controller may be configured to receive the pressure difference data of at least one of the monitored subsystems or monitored components. The at least one controller may be configured to generate a trend based on at least one of the pressure difference history data of at least one of the monitored subsystems or monitored components or the baseline pressure difference of at least one of the monitored subsystems or monitored components and the received pressure difference data. The at least one controller may be configured to compare the trend with at least one pressure difference threshold value. The at least one controller may be configured to generate a timeline for scale accumulation maintenance of at least one of the monitored subsystems or monitored components based on the comparison of the trend with the at least one pressure difference threshold value. At least one of the monitored subsystems or monitored components may be capable of maintenance based on the generated timeline.

[0003] In some embodiments, the timeline may indicate one or more predictive maintenance intervals for at least one of a monitored subsystem or a monitored component.

[0004] In some embodiments, at least one controller may be configured to alert a user of a timeline including one or more predictive maintenance intervals for at least one of a monitored subsystem or a monitored component.

[0005] In some embodiments, the timeline may indicate a need for immediate maintenance of at least one of the monitored subsystems or monitored components.

[0006] In some embodiments, at least one controller may be configured to alert a user of a timeline indicating a need for prompt maintenance of at least one of a monitored subsystem or a monitored component.

[0007] In some embodiments, at least one controller may be configured to disconnect at least one of the monitored subsystems or monitored components based on a comparison of the trend to at least one pressure differential threshold value.

[0008] In some embodiments, at least one sensor device may be mounted external to at least one of the monitored subsystems or monitored components within the aircraft brewing apparatus.

[0009] In some embodiments, at least one sensor device may be installed within at least one of the monitored subsystem or the monitored component.

[0010] In some embodiments, at least one of the monitored subsystems or monitored components may lead to at least one aircraft brewing device outlet.

[0011] In some embodiments, at least one of the monitored subsystem or the monitored component may be configured to receive fluid from a fluid supply.

[0012] In some embodiments, the fluid supply may be mounted within the aircraft brewing device.

[0013] In some embodiments, the fluid supply source may be mounted external to the aircraft brewing device.

[0014] In some embodiments, at least one of the monitored subsystem or monitored component may be configured to receive fluid from a fluid supply via at least one flow measurement device.The at least one flow measurement device may be configured to generate and transmit data.

[0015] In some embodiments, at least one controller may be configured to receive data transmitted by at least one flow measurement device.

[0016] According to one or more embodiments of the present disclosure, a system for detecting scale accumulation in an aircraft brewing device is disclosed. The system may include at least one of the monitored subsystems or monitored components of the aircraft brewing device. The system may include at least one sensor device configured to generate and transmit heating temperature difference data of the amount of scale accumulation in at least one of the monitored subsystems or monitored components. The system may include at least one controller coupled to the at least one sensor device. The at least one controller may be configured to receive heating temperature difference data of at least one of the monitored subsystems or monitored components. The at least one controller may be configured to generate a trend based on at least one of the heating temperature difference historical data of at least one of the monitored subsystems or monitored components or the baseline heating temperature difference of at least one of the monitored subsystems or monitored components and the received heating temperature difference data. The at least one controller may be configured to compare the trend with at least one heating temperature difference threshold value. The at least one controller may be configured to generate a timeline for scale accumulation maintenance of at least one of the monitored subsystems or monitored components based on the comparison of the trend with at least one heating temperature difference threshold value. At least one of the monitored subsystems or monitored components may be capable of maintenance based on the generated timeline.

[0017] This summary is provided only as an introduction to the subject matter fully described in the detailed description and drawings. This summary should not be considered to describe essential features, nor should it be used to determine the scope of the claims. In addition, it should be understood that both the foregoing summary and the following detailed description are merely exemplary and illustrative and do not necessarily limit the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The detailed description is described with reference to the accompanying drawings. The use of the same reference numerals in different instances in the description and the drawings may indicate similar or identical items. Various embodiments or examples ("examples") of the present disclosure are disclosed in the following detailed description and the drawings. The drawings are not necessarily to scale. In general, unless otherwise provided in the claims, the operations of the disclosed processes may be performed in any order. In the drawings:

[0019] Figure 1A is a block diagram of a system for detecting scale accumulation in an aircraft brewing device according to one or more embodiments of the present disclosure;

[0020] Figure 1B is a block diagram of a system for detecting scale accumulation in an aircraft brewing device according to one or more embodiments of the present disclosure;

[0021] Figure 2Ais a block diagram of a system for detecting scale accumulation in an aircraft brewing device according to one or more embodiments of the present disclosure;

[0022] Figure 2B is a block diagram of a system for detecting scale accumulation in an aircraft brewing device according to one or more embodiments of the present disclosure;

[0023] Figure 3 is a flow chart of a method for detecting scale accumulation in an aircraft brewing device according to one or more embodiments of the present disclosure;

[0024] Figure 4 is a graph showing pressure differential versus the number of cycles in operation according to one or more embodiments of the present disclosure;

[0025] Figure 5 is a flow chart of a method for detecting scale accumulation in an aircraft brewing device according to one or more embodiments of the present disclosure; and

[0026] Figure 6 is a graph showing heating temperature difference versus the number of cycles in operation according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0027] Reference will now be made in detail to the disclosed subject matter, which is illustrated in the accompanying drawings.

[0028] Before explaining one or more embodiments of the present disclosure in detail, it should be understood that the embodiments are not limited in their application to the details of the construction and arrangement of the components or steps or methods set forth in the following description or shown in the accompanying drawings. In the following detailed description of the embodiments, many specific details may be set forth in order to provide a more thorough understanding of the present disclosure. However, it will be clear to those of ordinary skill in the art who benefit from the present disclosure that the embodiments disclosed herein may be practiced without some of these specific details. In other cases, well-known features may not be described in detail to avoid unnecessarily complicating the present disclosure.

[0029] As used herein, a letter following a reference number is intended to reference an embodiment of that feature or element, which may be similar but not necessarily identical to the preceding element or feature having the same reference number (e.g., 1, 1a, 1b). Such shorthand notation is used only for convenience and should not be construed as limiting the present disclosure in any way unless expressly stated to the contrary.

[0030] In addition, unless expressly stated to the contrary, "or" refers to an inclusive or, not an exclusive or. For example, condition A or B is satisfied by any of the following: A is true (or exists) and B is false (or does not exist), A is false (or does not exist) and B is true (or exists), and both A and B are true (or exist).

[0031] In addition, "a" or "an" may be used to describe elements and components of the embodiments disclosed herein. This is merely for convenience, and "a" and "an" are intended to include "one" or "at least one", and the singular also includes the plural, unless otherwise clearly indicated.

[0032] Finally, as used herein, any reference to "one embodiment" or "some embodiments" means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment disclosed herein. The phrase "in some embodiments" appearing in various places in the specification are not necessarily all referring to the same embodiment, and an embodiment may include one or more of the features expressly described or inherently present herein, or any combination of subcombinations of two or more such features, together with any other features that may not necessarily be expressly described or inherently present in the disclosure.

[0033] Figure 1A-Figure 6 Generally, a system and method for detecting scale accumulation in an aircraft brewing device in accordance with one or more embodiments of the present disclosure are shown.

[0034] The operation and / or reliability of selected aircraft equipment, such as brewing devices and other aircraft galley inserts, may depend on the quality of potable water accessed into the aircraft equipment. One measure of potable water quality includes the amount of scale buildup (e.g., calcium deposit buildup) in the fluid systems of the aircraft equipment. Scale buildup may result in reduced performance of the aircraft equipment and lead to eventual blockage within the fluid systems of the selected aircraft equipment, which may result in failure of the aircraft equipment.

[0035] Due to the considerable variation in the quality of drinking water used by aircraft operators and / or obtained at different restocking locations (e.g., typically tarmacs, hangars, airports in general or other restocking locations), known systems or methods for detecting scale accumulation may not be implemented within an aircraft brewing device.

[0036] For example, one known system or method includes detecting scale accumulation based on multiple brews performed on the unit. However, this method may require a single supply of drinking water to ensure a relatively consistent input value when determining the amount of scale accumulation in the brewing device.

[0037] As another example, other known systems or methods include taking measurements using fiber optic sensors, total reflection probes, and / or quartz crystals with pre-calcified sensitive regions. These known systems or methods may not be feasible due to the size of the brewing device and / or the cost of including the necessary components.

[0038] Therefore, it would be desirable to provide a system and method for detecting scale accumulation in an aircraft brewing device. The system and method should be able to determine scale accumulation regardless of changes in drinking water quality and / or changes in drinking water supply. The system and method should fit within size constraints and / or cost constraints that may dictate the construction of an aircraft brewing device.

[0039] Figure 1A-Figure 2B A system 100 for detecting scale accumulation in an aircraft brewing device 102 in accordance with one or more embodiments of the present disclosure is generally illustrated.

[0040] The brewing device 102 may include a monitored subsystem 104. In general, the brewing device 102 may house a brewing system including one or more subsystems, such as the monitored subsystem 104, wherein the monitored subsystem 104 may be any subsystem with the potential for scale accumulation. The brewing device 102 may include a monitored component 200. In general, the brewing device 102 may house a brewing system including one or more subsystems, each of which includes one or more components, such as the monitored component 200, wherein the monitored component 200 may be any component with the potential for scale accumulation. It is noted herein that the monitored component 200 may be a component of the monitored subsystem 104.

[0041] For example, the brewing system of the brewing device 102 may include one or more heating subsystems 104 (e.g., a heat exchanger subsystem, etc.) having any number of heating components 200 known in the art (e.g., one or more heating elements, one or more heat-resistant components, etc.). As another example, the brewing system of the brewing device 102 may include one or more fluid subsystems 104 having any number of fluid components 200 known in the art (e.g., fluid components including one or more tubes or tube couplers, one or more pipes or pipe couplers, one or more valves, one or more solenoids, etc.). As another example, the brewing system of the brewing device 102 may include one or more electrical subsystems 104 having any number of electrical components 200 known in the art (e.g., one or more wiring harnesses, one or more junction boxes, one or more sensors, etc.).

[0042] The various systems and subsystems within the brewing device 102 may share any number of components. For example, the brewing device 102 may include one or more heating elements external to or integrated within a fluid component (e.g., a heater-type water tank, etc.). Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0043] It is noted herein that the brewing device 102 may include a plurality of monitored subsystems 104. Furthermore, it is noted herein that the brewing device 102 may include a plurality of monitored components 200. Further, it is noted herein that the brewing device 102 may include a plurality of monitored subsystems 104 and a plurality of monitored components 200. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0044] The monitored subsystem 104 and / or the monitored component 200 can be coupled (e.g., physically, fluidically, and / or electrically) to a fluid source 106. For example, the fluid source 106 can include a fluid tank (e.g., a water tank). In general, the fluid source 106 can include a fluid supply, such as a water supply, a milk or cream supply, an air supply, a steam supply, or other supply of fluid for preparing a beverage using the beverage device 102.

[0045] The fluid source 106 may be onboard the brewing device 102 (e.g., Figure 1A and Figure 2A The fluid source 106 may include an aircraft fluid supply onboard an aircraft in which the brewing device 102 is installed (e.g., Figure 1B and Figure 2B It is noted herein that the brewing device 102 may include an onboard fluid source 106, or may not include an onboard fluid source 106, wherein the aircraft fluid supply is directly coupled to one or more components of the brewing device 102. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0046] The monitored subsystem 104 and / or monitored component 200 may be directly coupled to the fluid source 106. The monitored subsystem 104 and / or monitored component 200 may be indirectly coupled to the fluid source 106 via one or more auxiliary components. For example, the monitored subsystem 104 and / or monitored component 200 may be coupled to the fluid source 106 via the flow measurement device 108. For example, the flow measurement device 108 may be onboard the brewing device 102 (e.g., as shown in FIG. 1 ). Figure 1A and Figure 2A In addition, the flow measurement device 108 may be mounted on an aircraft in which the brewing device 102 is installed (e.g., as shown in FIG. Figure 1B and Figure 2B). The flow measurement device 108 may be configured to provide information to help determine scale accumulation within the monitored subsystem 104 and / or the monitored component 200. However, it is noted herein that the flow measurement device 108 may be optional. Therefore, the above description should not be construed as limiting the present disclosure, but merely illustrative.

[0047] The monitored subsystem 104 and / or the monitored component 200 may be coupled (e.g., physically, fluidically, and / or electrically) to an aircraft brewing device outlet 110. For example, the outlet 110 may include a foam wand, a foam nozzle, a hot water tap, a cold water tap, a brew cup nozzle, a carafe or server nozzle, or other components configured to output a prepared beverage or a fluid used to prepare a beverage from the brewing device 102.

[0048] The brewing device 102 may be included outside the monitored subsystem 104 (e.g., Figure 1A and Figure 1B 200) and / or one or more sensor devices 112 external to the monitored component 200. For example, the one or more sensor devices 112 may include one or more pressure sensing devices. For example, the one or more pressure sensing devices may measure a fluid pressure difference across the monitored subsystem 104 and / or the monitored component 200.

[0049] The one or more sensor devices 112 may include a pressure transducer sensor or sensor probe installed in the fluid circuit between the fluid source 106 and the monitored subsystem 104 and in the fluid circuit between the monitored subsystem 104 and the brewing device outlet 110, so that the one or more sensor devices 112 can receive pressure readings to determine the fluid pressure differential. It is noted herein that the fluid circuit between the fluid source 106 and the monitored subsystem 104 and between the monitored subsystem 104 and the brewing device outlet 110 may include a fluid branch circuit leading to the one or more sensor devices 112, so that the one or more sensor devices 112 can internally determine the fluid pressure differential (e.g., the one or more sensor devices 112 are in a housing separate from the main fluid circuit and are configured to receive the branch fluid circuit).

[0050] It is noted herein that one or more sensor devices 112 may need to be added to the aircraft brewing apparatus 102, wherein the one or more sensor devices 112 include a pressure sensing device. Furthermore, it is noted herein that the pressure sensing device may be integrated within the monitored subsystem 104 and / or the monitored component 200. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0051] The brewing device 102 may include one or more sensor devices 112 (e.g., Figure 2A and Figure 2B ). For example, the one or more sensor devices 112 may include one or more temperature sensing devices. For example, the one or more temperature sensing devices 112 may measure a heating temperature difference across the monitored subsystem 104 and / or the monitored component 200.

[0052] It is noted herein that one or more sensor devices 112 may be installed in the aircraft brewing apparatus 102 and re-purposed, wherein the one or more sensor devices 112 include a temperature sensing device. Furthermore, it is noted herein that the temperature sensing device may be external to the monitored subsystem 104 and / or the monitored component 200. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0053] The brewing device 102 may include an aircraft brewing device controller 114. The brewing device controller 114 may be coupled (e.g., physically coupled and / or electrically coupled) to one or more sensor devices 112. The brewing device controller 114 may be coupled (e.g., physically coupled, fluidically coupled and / or electrically coupled) to a flow measurement device 108, wherein the flow measurement device 108 is installed within the brewing device 102.

[0054] The brewing device 102 can be coupled (eg, physically coupled, fluidically coupled, and / or electrically coupled) to the aircraft controller 116. For example, Figure 1A and Figure 2A As shown, the aircraft controller 116 can be coupled to the brewing device controller 114, and the brewing device controller 114 can be coupled to one or more components of the brewing device 102. As another example, Figure 1B and Figure 2B As shown, the aircraft controller 116 may be directly coupled to one or more components of the brewing device 102. It is noted herein that the brewing device 102 may include the brewing device controller 114, or may not include the brewing device controller 114, wherein the aircraft controller 116 is directly coupled to one or more components of the brewing device 102. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0055] The brewing device controller 114 and / or the aircraft controller 116 may be configured to transmit and / or receive data. As another example, the brewing device controller 114 and / or the aircraft controller 116 may be configured to record an event log and may transmit the event log (e.g., to other onboard or offboard controllers, etc.). As another example, the brewing device controller 114 and / or the aircraft controller 116 may be configured to receive information and / or commands in response to or independently of the transmitted event log. As another example, the brewing device controller 114 and / or the aircraft controller 116 may be configured to determine the type and / or timing of maintenance in response to or independently of the recorded event log.

[0056] The brewing device controller 114 and / or the aircraft controller 116 may include one or more processors and memory. The memory may store one or more sets of program instructions. One or more processors may be configured to execute the one or more sets of program instructions to perform one or more of the various steps described throughout the present disclosure. The brewing device controller 114 and / or the aircraft controller 116 may include one or more communication interfaces. The brewing device controller 114 and / or the aircraft controller 116 may include or be coupled to a user interface. The user interface may include one or more display devices. The user interface may include one or more user input devices.

[0057] The brewing device controller 114 and / or the aircraft controller 116 may be configured to determine the need for maintenance of the brewing device 102 based on one or more selected thresholds or threshold values. For example, one or more thresholds or threshold values ​​may be predetermined and stored in a memory. As another example, one or more thresholds or threshold values ​​are set by an operator.

[0058] For example, the one or more selected thresholds may include a single upper bound and / or a single lower bound. For example, the single upper bound and / or the single lower bound may be at a level where the need for maintenance is predictive (e.g., determining when scale accumulation will be at a selected blockage level or at a complete blockage), thereby allowing a user to determine when to perform the recommended maintenance. Additionally, the single upper bound and / or the single lower bound may be at a level where the need for maintenance is immediate when the aircraft brewing device 102 is in danger of malfunctioning or rupturing (e.g., scale accumulation is at a selected blockage level or at a complete blockage).

[0059] As another example, the one or more selected thresholds include a plurality of upper bounds and / or a plurality of lower bounds. For example, the plurality of upper bounds and / or the plurality of lower bounds may include a first level, where the need for maintenance is predictive to allow a user to determine when to perform recommended maintenance, and may include a second level, where the need for maintenance is immediate, where the aircraft brewing device 102 is in danger of malfunctioning or rupturing.

[0060] Figure 3 A method or process 300 for detecting scale accumulation in an aircraft brewing device is shown in accordance with one or more embodiments of the present disclosure.

[0061] The accumulation of scale in the monitored subsystem 104 and / or the monitored component 200 may result in an increase in the pressure differential across the monitored subsystem 104. For example, in the absence of or little scale accumulation, the pressure differential may be low. As another example, the pressure differential may increase as the amount of scale accumulation increases.

[0062] In step 302, data of a pressure differential of a monitored subsystem or monitored component may be received. The aircraft brewing device controller 114 and / or the aircraft controller 116 may receive data from one or more sensor devices 112 to determine a pressure differential across the monitored subsystem 104 and / or the monitored component 200. The data may be stored within the aircraft brewing device controller 114 and / or the aircraft controller 116 (e.g., in a memory).

[0063] In step 304 , a trend may be generated based on the received data of the pressure differential and at least one of historical data of the pressure differential or a baseline pressure differential. The historical data and / or the baseline pressure differential may be stored in the aircraft brewing device controller 114 and / or the aircraft controller 116 .

[0064] The trend may be compared to at least one pressure differential threshold value in step 306. The at least one pressure differential threshold value may be stored within the aircraft brewing device controller 114 and / or the aircraft controller 116 (eg, within a memory).

[0065] The comparison with the trend may be a determination of whether at least one pressure differential threshold value is met or exceeded. Determining that at least one pressure differential threshold value is met or exceeded may include a single reading pressure differential between the fluid pressure from the fluid source 106 to the monitored subsystem 104 and the fluid pressure from the monitored subsystem 104 to the aircraft brewing device outlet 110. Further, determining that at least one pressure differential threshold value is met or exceeded may include comparing the historical pressure differential with a real-time or near real-time pressure differential between the fluid pressure from the fluid source 106 to the monitored subsystem 104 and the fluid pressure from the monitored subsystem 104 to the aircraft brewing device outlet 110. Further, determining that at least one pressure differential threshold value is met or exceeded may include comparing the baseline pressure differential with a real-time or near real-time difference between the fluid pressure from the fluid source 106 to the monitored subsystem 104 and the fluid pressure from the monitored subsystem 104 to the aircraft brewing device outlet 110.

[0066] It is noted herein that the determination that at least one pressure differential threshold value is met or exceeded may include a combination of data. For example, the determination that at least one pressure differential threshold value is met or exceeded may include comparing previously recorded and stored data of the pressure differential determined by the first sensor device 112 with baseline data recorded using a separate sensor device 112 downstream of the first sensor device 112. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0067] In step 308, the monitored subsystem or monitored component may be disconnected. In the event that the process 300 measures a pressure differential that meets or exceeds at least one pressure differential threshold value, the aircraft brewing device controller 114 and / or the aircraft controller 116 may shut down the monitored subsystem 104 and / or the monitored component 200. However, it is noted herein that step 308 may be optional (e.g., in the event that the need for maintenance of the monitored subsystem or monitored component is not critical to the aircraft brewing device 102).

[0068] In step 310, a predictive maintenance timeline may be generated for maintenance based on a comparison with at least one pressure differential threshold value. The predictive maintenance timeline may indicate when a specific threshold value will be met. For example, the specific threshold value may be a predictive maintenance threshold value. As another example, the specific threshold value may be an immediate maintenance threshold value.

[0069] In step 312, a user may be alerted to the predictive maintenance timeline. In step 314, a user may be alerted to the need for prompt maintenance. In the event that the process 300 measures a pressure differential that meets or exceeds at least one pressure differential threshold value, the aircraft brewing device controller 114 and / or the aircraft controller 116 may notify a user (e.g., an onboard crew member, a maintenance worker, a field test operator, a factory production line operator, etc.) that the aircraft brewing device 102 requires maintenance. For example, the timeline may indicate one or more predictive maintenance intervals. As another example, the timeline may indicate the need for prompt maintenance.

[0070] Data, trends and / or thresholds may be compiled and presented to the user in a graphical format. Figure 4 A graph 400 comparing pressure differential versus the number of cycles in operation is shown according to one or more embodiments of the present disclosure. As the number of cycles in operation increases, each pressure differential reading 402 can be compiled and trends toward a predictive maintenance threshold value 404 can be monitored and / or an immediate maintenance threshold value 406 can be monitored. In a future time frame or in an immediate time frame, a user may be able to review the trend to determine a timeline when maintenance may be necessary.

[0071] Although embodiments of the present disclosure illustrate that an alert requiring immediate maintenance may follow the generation of a predictive maintenance timeline, it is noted herein that an alert requiring immediate maintenance may occur after determining that at least one pressure differential threshold value is met or exceeded. For example, an alert may occur after determining that the immediate maintenance threshold 406 has been met or exceeded. In this example, a predictive maintenance timeline may not be generated, or may be generated independently of an alert requiring immediate maintenance. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0072] Based on the predictive maintenance timeline and / or the indication that prompt maintenance is needed, the monitored subsystem or monitored component can be maintained for scale accumulation. For example, the monitored subsystem or monitored component can be cleaned or replaced. As another example, one or more components (e.g., fluid lines) leading to or leaving the monitored subsystem or monitored component can be cleaned or replaced. As another example, in the event that the generated timeline indicates a false positive for the need for maintenance, one or more sensor devices 112 can be cleaned or replaced.

[0073] In this regard, the process 300 may be configured to detect scale accumulation in the aircraft brewing device 102 regardless of drinking water quality and / or drinking water supply. Because the process 300 may require the use of an added sensor device 112 and / or an integrated and repurposed sensor device 112, implementing the process 300 may not require substantial (or even significant) changes to the size of the aircraft brewing device 102 and / or the design or cost of manufacturing the aircraft brewing device 102.

[0074] It is noted herein that pressure can be measured in any pressure unit known in the art, including but not limited to Pascal (Pa), pounds per square inch (psi), Torr (Torr), bar (bar) or atmospheric pressure (atm). Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0075] Figure 5 A method or process 500 for detecting scale accumulation in an aircraft brewing device is shown in accordance with one or more embodiments of the present disclosure.

[0076] During heat transfer from the heating subsystem to the fluid subsystem, the accumulation of scale in the monitored subsystem 104 and / or the monitored component 200 can cause a reduction in the heating temperature differential. For example, during heat transfer to a fluid path in which there is little or no scale accumulation, there may be a significant heating temperature differential. As another example, during heat transfer to the fluid path, as the amount of scale accumulation increases, the heating temperature differential can decrease.

[0077] It is noted herein that one example definition of a heating temperature differential may be the difference between the temperature at the completion point of the operation and the temperature at the target set point. However, it is noted herein that the heating temperature differential is not limited to the example definition, and the heating temperature differential may be defined based on additional or alternative metrics. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0078] In step 502, data of a heating temperature difference of a monitored subsystem or monitored component may be received. The aircraft brewing device controller 114 and / or the aircraft controller 116 may receive data from one or more sensor devices 112 to determine a heating temperature difference across the monitored subsystem 104 and / or the monitored component 200. The data may be stored within the aircraft brewing device controller 114 and / or the aircraft controller 116 (e.g., in a memory).

[0079] In step 504, a trend may be generated based on the received data of the heating temperature difference and at least one of the historical data of the heating temperature difference or the baseline heating temperature difference. The historical data and / or the baseline heating temperature difference may be stored in the aircraft brewing device controller 114 and / or the aircraft controller 116.

[0080] The trend may be compared to at least one heating temperature difference threshold value in step 506. The at least one heating temperature difference threshold value may be stored within the aircraft brewing device controller 114 and / or the aircraft controller 116 (eg, within a memory).

[0081] The comparison to the trend may be a determination of whether at least one heating temperature difference threshold value is met or exceeded. Determining that at least one heating temperature difference threshold value is met or exceeded may include a single reading heating temperature difference from the monitored subsystem 104 and / or the monitored component 200. Additionally, determining that at least one heating temperature difference threshold value is met or exceeded may include comparing a historical heating temperature difference with a real-time or near real-time heating temperature difference from the monitored subsystem 104 and / or the monitored component 200. Additionally, determining that at least one heating temperature difference threshold value is met or exceeded may include comparing a real-time or near real-time difference between a baseline heating temperature difference and a heating temperature difference from the monitored subsystem 104 and / or the monitored component 200.

[0082] It is noted herein that the determination that at least one heating temperature difference threshold value is met or exceeded may include a combination of data. For example, determining that at least one heating temperature difference threshold value is met or exceeded may include comparing previously recorded and stored data of the heating temperature difference determined by the first sensor device 112 with baseline data recorded using a separate sensor device 112 downstream of the first sensor device 112. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0083] In step 508, the monitored subsystem or monitored component may be turned off. In the event that the process 500 measures a heating temperature difference that meets or exceeds at least one heating temperature difference threshold value, the aircraft brewing device controller 114 and / or the aircraft controller 116 may shut down the monitored subsystem 104 and / or the monitored component 200. However, it is noted herein that step 508 may be optional (e.g., in the event that the need for maintenance of the monitored subsystem or monitored component is not critical to the aircraft brewing device 102).

[0084] In step 510, a predictive maintenance timeline may be generated for maintenance based on a comparison with at least one temperature threshold value. The predictive maintenance timeline may indicate when a specific threshold value will be met. For example, the specific threshold value may be a predictive maintenance threshold. As another example, the specific threshold value may be an immediate maintenance threshold.

[0085] In step 512, a user may be alerted to the predictive maintenance timeline. In step 514, a user may be alerted to the need for prompt maintenance. In the event that the process 500 measures a heating temperature difference that meets or exceeds at least one heating temperature difference threshold value, the aircraft brewing device controller 114 and / or the aircraft controller 116 may notify a user (e.g., an onboard crew member, a maintenance worker, a field test operator, a factory production line operator, etc.) that the aircraft brewing device 102 requires maintenance. For example, the timeline may indicate one or more predictive maintenance intervals. As another example, the timeline may indicate the need for prompt maintenance.

[0086] Data, trends and / or thresholds may be compiled and presented to the user in a graphical format. Figure 6 A graph 600 comparing heating temperature differentials versus the number of cycles in operation is shown according to one or more embodiments of the present disclosure. As the number of cycles in operation increases, each heating temperature differential reading 602 can be compiled and trends toward predictive maintenance thresholds 604 can be monitored and / or immediate maintenance thresholds 606 can be monitored. In the future time frame or in the immediate time frame, a user may be able to review the trend to determine a timeline when maintenance may be necessary.

[0087] Although embodiments of the present disclosure illustrate that a warning that immediate maintenance is required may follow the generation of a predictive maintenance timeline, it is noted herein that a warning that immediate maintenance is required may occur after determining that at least one heating temperature difference threshold value is met or exceeded. For example, a warning may occur after determining that the immediate maintenance threshold 606 has been met or exceeded. In this example, a predictive maintenance timeline may not be generated, or may be generated independently of a warning that immediate maintenance is required. Therefore, the above description should not be construed as a limitation of the present disclosure, but is merely illustrative.

[0088] Based on the predictive maintenance timeline and / or the indication that prompt maintenance is needed, the monitored subsystem or monitored component can be maintained for scale accumulation. For example, the monitored subsystem or monitored component can be cleaned or replaced. As another example, one or more components (e.g., fluid lines) leading to or leaving the monitored subsystem or monitored component can be cleaned or replaced. As another example, in the event that the generated timeline indicates a false positive for the need for maintenance, one or more sensor devices 112 can be cleaned or replaced.

[0089] In this regard, the process 500 may be configured to detect scale accumulation in the aircraft brewing device 102 regardless of drinking water quality and / or drinking water supply. Because the process 500 may require the use of an added sensor device 112 and / or an integrated and repurposed sensor device 112, implementing the process 500 may not require substantial (or even significant) changes to the size of the aircraft brewing device 102 and / or the design or cost of manufacturing the aircraft brewing device 102.

[0090] It is noted herein that pressure may be measured in any pressure unit known in the art, including but not limited to Celsius (C), Fahrenheit (F), or Kelvin (K). Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0091] It is noted herein that the method or process 300, 500 is not limited to the steps and / or sub-steps provided. The method or process 300, 500 may include more or fewer steps and / or sub-steps. The method or process 300, 500 may perform the steps and / or sub-steps simultaneously. The method or process 300, 500 may perform the steps and / or sub-steps sequentially, including in the order provided or in an order different from the order provided. Therefore, the above description should not be interpreted as limiting the scope of the present disclosure, but is merely illustrative.

[0092] In this regard, the present disclosure relates to systems and methods for detecting scale accumulation in an aircraft brewing device. The systems and methods may be able to determine scale accumulation regardless of changes in drinking water quality and / or changes in drinking water supply. The systems and methods may fit within size constraints and / or cost constraints that may dictate the construction of an aircraft brewing device.

[0093] It is noted herein that the aircraft brewing device 102, the aircraft brewing device controller 114, and / or the aircraft controller 116 (and / or selected components of the aircraft brewing device 102, the aircraft brewing device controller 114, and / or the aircraft controller 116) may be configured in accordance with, but not limited to, guidelines and / or standards set forth by the Federal Aviation Administration (FAA), the European Aviation Safety Agency (EASA), or any other aviation certification agency or organization; the American National Standards Institute (ANSI), the Aeronautical Radio Corporation (ARINC), or any other standard setting organization or company; the Radio Technical Commission for Aeronautics (RTCA), or any other guidance agency or organization, etc. However, it is noted herein that the aircraft brewing device 102 may not need to meet any regulations or design limitations. Therefore, the above description should not be construed as limiting the present disclosure, but is merely illustrative.

[0094] Although embodiments of the present disclosure relate to avionic environments, such as aircraft, it is noted herein that the aircraft brewing device 102 configured for systems and methods for determining scale accumulation is not limited to avionic environments and / or aircraft components within avionic environments. For example, the aircraft brewing device 102 can be configured to operate in any type of vehicle known in the art. For example, the vehicle can be any personal equipment or vehicle based on air, space, land, or water; any commercial equipment or vehicle based on air, space, land, or water; any military equipment or vehicle based on air, space, land, or water known in the art. As another example, the aircraft brewing device 102 can be a device sold for commercial or industrial use in a home or business. Therefore, the above description should not be construed as a limitation of the present disclosure, but merely an illustration.

[0095] Although the present disclosure has been described with reference to the embodiments shown in the accompanying drawings, equivalents may be used and substituted herein without departing from the scope of the claims. The components shown and described herein are merely examples of systems / devices and components that may be used to implement embodiments of the present disclosure, and may be replaced with other devices and components without departing from the scope of the claims. In addition, any dimensions, degrees, and / or numerical ranges provided herein are to be understood as non-limiting examples unless otherwise stated in the claims.

Claims

1. A system for detecting scale accumulation in an aircraft brewing device, comprising: at least one of the monitored subsystems or monitored components of the aircraft brewing device; at least one sensor device configured to generate and transmit differential pressure data of an amount of scale accumulation in the at least one of the monitored subsystems or monitored components; as well as at least one controller coupled to the at least one sensor device, the at least one controller being configured to: receiving pressure differential data for the at least one of a monitored subsystem or a monitored component; generating a trend based on at least one of historical pressure differential data for the at least one of the monitored subsystems or monitored components or a baseline pressure differential for the at least one of the monitored subsystems or monitored components and the received pressure differential data; comparing the trend to at least one pressure difference threshold value; as well as generating a timeline for scale accumulation maintenance in the at least one monitored subsystem or monitored component based on a comparison of the trend to the at least one pressure differential threshold value, The at least one of the monitored subsystems or monitored components can be maintained based on the generated timeline. 2 . The system of claim 1 , the timeline indicating one or more predictive maintenance intervals for the at least one of a monitored subsystem or a monitored component.

3. The system of claim 2, wherein the at least one controller is configured to: A user is alerted to the timeline including the one or more predictive maintenance intervals for the at least one of a monitored subsystem or a monitored component. 4 . The system of claim 1 , the timeline indicating a need for immediate maintenance of the at least one of a monitored subsystem or a monitored component.

5. The system of claim 4, wherein the at least one controller is configured to: A user is alerted to the timeline indicating a need for immediate maintenance of the at least one of the monitored subsystems or monitored components.

6. The system of claim 1, wherein the at least one controller is configured to: The at least one of the monitored subsystem or monitored component is disconnected based on a comparison of the trend to the at least one pressure differential threshold value.

7. The system of claim 1, wherein the at least one sensor device is mounted external to the at least one of the monitored subsystems or monitored components within the aircraft brewing apparatus.

8. The system of claim 1, the at least one sensor device being installed within the at least one of a monitored subsystem or a monitored component.

9. The system of claim 1, said at least one of a monitored subsystem or a monitored component leading to at least one aircraft brewing device outlet.

10. The system of claim 1, the at least one of the monitored subsystem or monitored component being configured to receive fluid from a fluid supply.

11. The system of claim 10, said fluid supply being mounted within said aircraft brewing device.

12. The system of claim 10, said fluid supply being mounted external to said aircraft brewing device.

13. The system of claim 10, the at least one of the monitored subsystem or monitored component being configured to receive fluid from a fluid supply via at least one flow measurement device, the at least one flow measurement device being configured to generate and transmit data.

14. The system of claim 13, the at least one controller being configured to receive data transmitted by the at least one flow measurement device.

15. A system for detecting scale accumulation in an aircraft brewing device, comprising: at least one of the monitored subsystems or monitored components of the aircraft brewing device; at least one sensor device configured to generate and transmit heating temperature differential data of an amount of scale accumulation in the at least one of the monitored subsystems or monitored components; as well as at least one controller coupled to the at least one sensor device, the at least one controller being configured to: receiving heating temperature differential data for the at least one of a monitored subsystem or a monitored component; generating a trend based on at least one of historical heating temperature differential data for the at least one of the monitored subsystems or monitored components or a baseline heating temperature differential for the at least one of the monitored subsystems or monitored components and the received heating temperature differential data; comparing the trend to at least one heating temperature difference threshold value; as well as generating a timeline for scale accumulation maintenance in the at least one monitored subsystem or monitored component based on a comparison of the trend to the at least one heating temperature difference threshold value, The at least one of the monitored subsystems or monitored components can be maintained based on the generated timeline.

Images