FIELD

[0001] Examples of a beer keg tracking and beer quality (BKBQ) system are described. In various examples, the BKBQ system enables collection of a range of data from a plurality of beer kegs throughout a beer keg cycle. The BKBQ system may include a sensor system configured to beer kegs enabling efficient collection of temperature, location, force, keg tap status data throughout a beer keg cycle to provide relevant data and analysis to BKBQ system users including breweries and pubs. In various embodiments, the BKBQ system enables monitoring a best-before date for a beer and, based on events, enables a best-before date to be dynamically updated.

BACKGROUND

[0002] Each day millions of beer kegs are transported between a) breweries where beer is made, b) warehouses where full beer kegs are stored, c) to pubs, bars, restaurants where the beer is consumed and d) back to the breweries where the empty beer kegs are washed, stored and re-filled.

[0003] Standard size aluminum beer kegs are one of the primary means of transporting and storing beer during this transportation and consumption cycle. In addition, at the pubs, bars, restaurants (collectively referred to herein as “pubs”), beer kegs also serve as an important component of the delivery system to a beer glass and ultimately to the customer.

[0004] A typical aluminum beer keg is worth about $100-$200 depending on size. Beer kegs are typically owned by the breweries who are thus primarily responsible for keeping track of them, cleaning and maintaining them and replacing them when necessary. Depending on the size of a brewery, a brewery may own dozens, hundreds or thousands of kegs in a variety of sizes. The vast majority of beer kegs that are delivered to pubs most often have a volume in the range of about 20 liters up to about 100 liters to enable the handling of the beer kegs by personnel without or with minimal need for mechanized lifting equipment. That is, kegs of this size enable personnel to load delivery trucks at the brewery/warehouse, unload the kegs at the pub and use basic dolly systems to move the kegs to storage/dispensing rooms or various areas in pubs.

[0005] As beer brewing is a volume-based and rapid turnover business, the movement of beer kegs between breweries and pubs is generally quick-paced with the typical pub receiving deliveries daily or weekly and the brewery making daily deliveries and empty- keg pickups.

[0006] Given the fast-paced nature of the business and the large number of kegs that are moving around, there a variety of problems that arise.

SUMMARY

[0007] In accordance with one embodiment, a system is described, the system comprising: a keg sensor system connected to a beer keg, the keg sensor system having: at least one sensor for detecting keg events and obtain keg events data; a controller and communication interface configured to receive keg events data from the at least one sensor and to communicate keg events data to a central computer system; wherein the central computer system (CCS) includes at least one processor having tangible, non-transitory computer-readable media comprising program instructions executable by the at least one processor such that the CCS is configured to determine, based on keg events data from the beer keg, out-of-specification events for a beer keg.

[0008] In various embodiments:

• the CCS is configured to store a BBD for the beer keg, and to determine, based on out-of-specification events for a beer keg if the BBD for the beer keg is to be adjusted;

• the at least sensor includes a keg port sensor configured to detect tapping the beer keg and wherein the CCS is configured to calculate an adjusted BBD based on a time the beer keg is tapped;

• the at least one sensor includes a temperature sensor configured to measure temperature of the beer keg and wherein the CCS is configured to determine out-of-specification temperature events and adjust the BBD based on out-of- specification temperature events;

• the at least one sensor includes a force sensor configured to measure movement of the beer keg and wherein the CCS is configured to determine out-of-specification movement events and adjust the BBD based on out-of- specification movement events;

• the system includes a location sensor and the controller is configured to store location data and report location data to the CCS;

• the communication interface is configured to enable communication with a wide area network via a cellular communication system;

• the communication interface is configured to enable communication a local area network (LAN) via a LAN communication system;

• the CCS is configured to report out-of-specification events to a brewery;

• the CCS is configured to report an adjusted BBD to system users including any one of or both of a brewery computer system and a pub computer system; and/or,

• the CCS is configured to calculate a relative freshness score for a keg at a pub, the relative freshness score based on the number of days until a BBD and where the system reports the relative freshness score to the pub and where the pub includes a pub display for displaying the relative freshness score to pub patrons.

[0009] In another aspect, a method for monitoring and adjusting a best-before date (BBD) of beer within a beer keg having a sensor system is described, the sensor system including a unique identifier and a keg location sensor within a computerized beer keg system, the method comprising the steps of: registering and activating the unique identifier of a beer keg within the computerized beer keg system; upon filling the beer keg with beer, assigning a best-before date (BBD) to the beer keg; after filling, reporting keg events to a central system; adjusting the BBD based on a BBD adjustment algorithm; and, reporting an adjusted BBD to at least one system user.

[0010] In various embodiments:

• keg events include a time of beer keg opening;

• keg events include out-of-specification temperature events;

• keg events include out-of-specification force events;

• system users include any one of or a combination of breweries and pubs.

• where if the keg location sensor reports a keg is at a pub, an updated BBD is reported to the pub;

• the BBD adjustment algorithm evaluates an amount of time and a quantitative value of an out-of-specification event and calculates the adjusted BBD based on a relative severity of the time and quantitative value of an out-of- specification event;

• the CCS monitors location data for a beer keg and flags location data indicating a beer keg is at unauthorized location;

• the CCS monitors unauthorized location events including filling events at unauthorized locations;

• empty beer kegs are flagged by CCS;

• the CCS monitors a time of keg opening and a time of keg emptying and calculates a rate of consumption based on the keg opening and keg emptying and a keg volume;

• the CCS correlates the rate of consumption to a total inventory of similar beer product at a pub and based on a rate of consumption relative to the total inventory triggers beer keg delivery to a pub or not; and/or, the CCS reports a rate of consumption to the pub.

[0011] In another aspect, a keg sensor is described, the keg sensor comprising: a body having a bottom surface for connection to a keg adjacent a keg port opening, the body containing: a controller having transient memory, the controller connected to: a temperature sensor for measuring temperature of the keg; a movement sensor for measuring movement of the keg; a keg status sensor for detecting keg status events; and, a location system for detecting keg location within a wide area network wherein data from each of the temperature sensor, movement sensor, keg status sensor and location system are stored in the transient memory and periodically uploaded to a central computer system (CCS) via the wide area network.

[0012] In various embodiments:

• the keg status sensor is a capacitance sensor configured to detect connection of a keg tap to the keg;

• the capacitance sensor is a differential capacitance sensor having two or more sensor plates and where connection of a beer keg tap to a beer keg is differentiated from events not associated with connecting a beer keg tap to the beer keg by field signals at each sensor plate;

• the body includes a through-bore configured for placement around a beer keg opening and enabling connection of a beer keg tap;

• the body includes a sensor section and an auxiliary section containing the location system and a location system antenna;

• the auxiliary section contains at least one antenna connected to the location system and where each antenna is aligned parallel to an axis of the beer keg;

• the force sensor and controller are configured to collect force data that signals any one of or a combination of keg inversion, low speed keg movement, keg cleaning, keg filling, keg emptying, high speed keg movement and impact; • the keg opening sensor and controller are configured to detect any one or a combination of keg tap sealing and keg tap opening;

• the temperature sensor and controller are configured to detect that a keg is at any one or a combination of a cleaning temperature, an ambient temperature and a cold temperature;

• the location system includes a local area network system configured to connect to a wireless local area network and determine a location within the local area network; and/or,

• the location system includes a wide area network system configured to connect to a wireless wide area network and determine a location within the wide area network.

[0013] In another aspect, a computer system for monitoring beer keg status throughout a beer keg cycle is described, the computer system having a database of in-specification conditions for a beer keg throughout a beer keg cycle including in-specification conditions of location, force, temperature and keg tap status, the computer system configured to: receive location data from a beer keg within a wide area network; keg temperature data including any one of or a combination of cleaning, ambient and cold storage temperature data; keg force data including any one of or a combination of keg inversion, low speed keg movement, keg cleaning, keg filling, keg emptying, high speed keg movement and impact; and, keg tapping data from the beer keg including any one of or a combination of keg sealing and keg opening, and where combinations of the keg location data, keg temperature data, keg force data and keg tapping data are compared to the in-specification conditions within the database to determine if a keg is in specification.

[0014] In various embodiments:

• if a beer keg is at a dispensing location and the keg tapping data indicates the keg has been tapped, the computer system monitors a time since the keg was tapped and provides a product alert if the time since tapping exceeds a shelf-life threshold; and/or, • the computer system communicates the product alert to a local computer associated with a current location of the beer keg.

[0015] In another aspect, a method of collecting beer keg data to determine beer keg status throughout a beer keg cycle is described, comprising the steps of : on a beer keg having a sensor system with a controller: collecting movement data from a movement sensor, the movement sensor configured to collect movement data within threshold ranges and where the movement data signals any one of or a combination of: keg inversion; keg movement within a facility; keg cleaning; keg filling; keg emptying; keg movement within a vehicle; and, impact; determining keg location from a location sensor, the location sensor configured to determine keg location within a wide area network; collecting keg tap data from a keg tap sensor, the keg tap sensor configured to detect any one of or a combination of: keg tap sealing; keg tap opening; keg tap flow; collecting temperature data from a temperature sensor, the temperature sensor configured to collect temperature data within threshold ranges and where the temperature data signals any one of or a combination of: the keg is at a cleaning temperature; the keg is at ambient temperature; the keg is at a cold temperature; wherein combinations of the movement data, keg tap data, temperature data and location data enable determination of keg status throughout a beer keg cycle.

[0016] In various embodiments, the method includes combinations of the following:

• flagging beer kegs for maintenance/replacement based on force data;

• calculating a best-before date based on a keg tap opening signal and reporting the best-before date to a pub computer system in advance of the best-before date and/or after the best-before date;

• activating a product promotion algorithm within a pub computer system in advance of the best-before date;

• calculating a beer consumption rate based on a keg tap opening signal and an empty keg signal and reporting the beer consumption rate to a pub computer system; • calculating a beer consumption rate based on a keg tap opening signal and an empty keg signal and reporting the beer consumption rate to a brewery computer system; and/or,

• monitoring unauthorized keg filling by analysis of a combination of location data, temperature data and force data.

[0017] In another aspect, a method of predicting out-of-specification events of beer kegs within a distributed network utilizing a machine learning database and algorithm trained with historical beer keg data from a plurality of beer kegs within a distributed network is described, the steps including; introducing historical temperature, movement and location data from a plurality of beer kegs within a distributed network into a database, the historical data including beer quality events; analyzing the historical data to extract events of interest relating to beer handling and correlating the events of interest to beer quality events; testing the analyzed data using a machine-learning algorithm and deriving a classifier prediction model; and introducing current beer keg data into the prediction model and analyzing the current beer keg data to produce a beer quality assessment for one or more kegs at a location.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Various objects, features and advantages will be apparent from the following description of particular embodiments, as illustrated in the accompanying drawings. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of various embodiments. Similar reference numerals indicate similar components.

FIGURE 1 is a schematic plan view of a beer keg sensor and sub-systems in accordance with one embodiment.

FIGURE 1A is a schematic side view of a beer keg sensor configured to a beer keg in accordance with one embodiment.

FIGURE 1 B is a rendering of a beer keg sensor configured to a beer keg in accordance with one embodiment. FIGURE 2 is an overview of a typical beer keg cycle and locations where a beer keg sensor in accordance with the invention may report location data.

FIGURE 2A is an overview of a beer keg communication system and network in accordance one embodiment.

Figure 3 is a representative plot showing how the relative freshness of beer and a best-before date may change under different out-of-specification scenarios.

Figure 3A is a representative plot showing how the relative freshness of one beer keg and a best-before date may be dynamically adjusted under different out-of-specification scenarios.

FIGURE 3B shows representative sensor data collected at an authorized brewery (AB) in accordance with one embodiment.

FIGURE 3C shows representative sensor data collected at a pub in accordance with one embodiment.

FIGURE 3D shows representative sensor data collected at an unauthorized brewery in accordance with one embodiment.

Figure 4 is a flowchart describing a process for updating a best-before date in accordance with one embodiment.

DESCRIPTION

[0019] There is a need for systems and methods that improve beer keg tracking and beer quality monitoring. There is also a need for systems that improve collection of a range of data from a beer keg throughout a beer keg cycle and that enable monitoring a best-before date for a beer and, based on events, enable a best-before date to be dynamically updated.

Rationale

[0020] The inventors who have experience in developing sensor systems for applications for a range of consumer products recognized that there are various inefficiencies with the handling of beer kegs throughout a typical beer keg cycle as well as the various sensor systems that have been employed to track beer kegs. The inventors recognized that inefficiencies include the cost of the sensors together with the type data that can be collected from a beer keg throughout the beer keg cycle.

Keg Tracking, Loss and Damage

[0021] A beer keg cycle is a complex operation requiring careful handling of beer kegs throughout various cycle steps that may include cleaning, filling and storing beer kegs at a brewery, delivering beer kegs to pubs and returning the beer kegs to specific breweries. Breweries may be required to manage the cycle steps that may involve multiple breweries and multiple pubs that product is being delivered to. Pubs may be required to coordinate the receipt of many beer kegs from different breweries and ensure that one brewery’s kegs are returned to the correct brewery. In addition, many people may handle beer kegs throughout the cycle including the personnel to on-load and off load trucks and transport the beer kegs into the storage or dispensing areas of a pub.

[0022] As a result of this complexity and the variety of personnel (e.g. brewery, delivery and pub personnel), many beer kegs are either lost or damaged each year. Beer kegs may be lost due to theft from warehouses, pubs, delivery vehicles and the breweries or they may be damaged due to accidents during handling. Dropping a full beer keg onto a hard surface from a relatively low height can result in significant or catastrophic damage to a keg.

[0023] Estimates are that 5% of a brewery’s beer kegs may require replacing each year due to loss and/or damage or simply as part of the on-going equipment replacement.

Lost or damaged beer kegs are expensive to breweries due to the cost of replacing them, but also due to the potential loss of the beer. That is, a full beer keg that is stolen or catastrophically damaged is a greater loss than an empty keg.

[0024] In North America, estimates are that hundreds of thousands of beer kegs are lost or damaged each year that must then be replaced. [0025] Lost or damaged beer kegs increase the overall cost of the beer to pubs insomuch as the cost of replacing the beer kegs is ultimately passed on to the customer (i.e. the pub or the end-consumer).

Product Freshness

[0026] Breweries will typically go to great lengths to maintain consistency in their products as the brand value of the brewery and individual products can be dramatically affected by product that is or is perceived as being poor quality and/or out-of- specification. Breweries are generally able to control the manufacturing and handling procedures that will ensure that product is in-specification throughout the brewing process and whilst in the custody of the brewer. However, as soon as the custody of a beer keg is lost either at the point a beer keg leaves a brewery or upon arrival at a pub, it is out of the brewery’s control to ensure that the keg is handled in a manner that ensures the best-before date (BBD) is not shortened and the quality of the beer is not compromised.

[0027] Depending on the beer brewing process/product together with how the keg is handled and stored, keg beers will have different shelf lives within a keg. Generally, a brewer will be able to advise on the shelf life based on the type of beer (e.g. pasteurized or unpasteurized) and the assumption/recommendation that the beer be stored at a particular temperature (e.g. in the range of 3-6°C). The typical shelf life for a pasteurized beer may be 6-9 months whereas an unpasteurized beer may be 10-60 days depending on a number of factors including the processes by which the beer may have been made.

[0028] However, maintaining in-specification parameters (such as temperature and agitation) outside of the brewery and throughout the beer keg cycle may be quite variable. While certain transportation companies and pubs may be highly consistent in following procedures to ensure that transportation and storage parameters are maintained, others may not. In addition, occasional variations in weather, and/or any number of handling and storage problems can lead to situations where a percentage of a pub’s beer kegs are exposed to events that could have an effect on the beer. In various examples, a beer keg may be inadvertently exposed to warmer temperatures and/or agitation that can have the effect of decreasing shelf life of the beer. Problems can also occur within breweries as well. [0029] Importantly, in one example, a brewer and a pub may not be aware of the temperature that a beer keg may have been exposed, how long that temperature exposure may have been and the location where a temperature incident may have occurred.

[0030] Further still, pubs and their personnel are generally not aware of and/or may not care about the nuances of maintaining beer freshness and may only notice, be concerned or take action when a customer complains.

[0031] Complaints can be made to pubs themselves but also to the breweries through customer feedback systems through their websites and other communication media.

This type of reporting can be quite unfocussed. For example, a customer may have visited three pubs over the course of an evening and felt that the beer at pub 2 didn’t taste good and the following day writes an email to the brewery complaining about the beer. While the customer may have mentioned pub 2, the reliability of the data will be questionable.

[0032] Best-before dates are general approximations of shelf life that are made based on an assumption that the beer keg is kept in specification before the best-before date. Generally, while not being bound to any particular theory, it is generally understood that the greater the number of out-of-specification events that occur, the best-before date will decrease (i.e. occur sooner). Precise calculation of changes in best-before dates due to out-of-specification events is not accurate and may be affected by a number of factors. Basically, it is understood that if you mistreat the beer (e.g. expose it to higher temperatures and/or shake it), it may go off more quickly.

[0033] Importantly, as noted above, it is beneficial for the brewery to ensure that their brand is being properly represented and it desirable that they are made aware with greater precision about the nature and location of potential problems with their products.

[0034] That is, in the example above, if a customer complains that they received bad beer at pub 2, the brewery ideally can look to see if this complaint correlates with out-of- specification events at or near pub 2. If yes, this may be sufficient to trigger investigation. If no, the complaint may be dismissed or at least only logged as a data point. [0035] Accordingly, there is a need for systems and methods of effectively capturing temperature and movement data from beer kegs and utilizing that data to assist breweries, transporters and pubs in minimizing equipment and product loss risks.

[0036] There is also a need for low-cost, and low-power sensor systems that can be configured to a beer keg and that can reliably collect and report data back to a central computer system.

[0037] In addition, there has been a need for systems that enable the analysis of temperature, movement and location data to provide effective information to breweries, pubs and consumers regarding beer keg movement and product quality as well as best- before date assessment.

Unauthorized Filling

[0038] Another problem is pub owners filling beer kegs with off-brand beer and selling that beer as the product of the brand-name brewery. In these situations, a brand-name beer may be delivered to the pub and sold in the normal course. However, when the keg is empty, the pub may refill the keg with the off-brand beer by another brewery at a lower price.

[0039] Under current systems, the brand-name brewery is none the wiser as the keg may simply not be returned to the brand-name brewery until towards the end of the typical beer shelf life allowing the pub to potentially re-fill the keg several times within that window.

[0040] Accordingly, there has been a need for systems to minimize the ability of a pub to potentially sell off-brand from an on-brand keg.

[0041] Systems and methods for addressing these inefficiencies are described including sensor systems that can efficiently obtain and track data from a beer keg and that provides meaningful data to various system users including breweries and pubs. One example objective is to provide sensor systems that are low cost to users (for example, breweries) and that enable monitoring/adjusting best-before dates based on data that has been collected. In one example, best-before dates are monitored/adjusted based on the time that a beer keg has been tapped/opened and may have been subjected to various out-of-specification events.

Scope of Language

[0042] The terminology used herein is for the purpose of describing example embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

[0043] It will be understood that when an element is referred to as being “on”, “attached” to, “connected” to, “coupled” with, “contacting”, etc., another element, it can be directly on, attached to, connected to, coupled with or contacting the other element or intervening elements may also be present. In contrast, when an element is referred to as being, for example, “directly on”, “directly attached” to, “directly connected” to, “directly coupled” with or “directly contacting” another element, there are no intervening elements present.

[0044] It will be understood that, although the terms “first”, “second”, etc. may be used herein to describe various elements, components, etc., these elements, components, etc. should not be limited by these terms. These terms are only used to distinguish one element, component, etc. from another element, component. Thus, a “first” element, or component discussed herein could also be termed a “second” element or component without departing from the teachings. In addition, the sequence of operations (or steps) is not limited to the order presented in the claims or figures unless specifically indicated otherwise.

[0045] Other than described herein, or unless otherwise expressly specified, all of the numerical ranges, amounts, values and percentages, such as those for amounts of materials, elemental contents, times and temperatures, ratios of amounts, and others, in the following portion of the specification and attached claims may be read as if prefaced by the word “about” even though the term “about” may not expressly appear with the value, amount, or range. Accordingly, unless indicated to the contrary, the numerical parameters set forth in the following specification and attached claims are approximations that may vary depending upon the desired properties sought to be obtained. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques.

[0046] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art.

[0047] Various aspects will now be described with reference to the Figures. For the purposes of illustration, components depicted in the Figures are not necessarily drawn to scale and are drawn to represent spatial and/or functional relationships between described elements.

[0048] As such, emphasis is placed on highlighting the various contributions of the components to the functionality of various example embodiments. A number of possible alternative features are introduced during the course of this description. It is to be understood that, according to the knowledge and judgment of persons skilled in the art, such alternative features may be substituted in various combinations to arrive at different embodiments.

Beer Keg Tracking and Beer Quality Sensor

[0049] With reference to Figures 1, 1A and 1B, an example sensor system (SS) 10 for monitoring and tracking the location of a beer keg 12 is described. The SS 10 is described in conjunction with a beer keg and beer quality (BKBQ) system that is one environment within which multiple sensor systems may be deployed and form part of.

[0050] As described herein, a beer keg 12 has a generally cylindrical body 12a having an interior 13, an upper surface 12b with a keg port 12c. The typical keg includes a handle/stacking flange 12d that provides protection to equipment configured to the keg port and that allows kegs to be stacked on one another and that provides protection to the keg port. The keg port allows connection of a keg valve/coupler assembly 14 to the keg as shown in Figure 1A.

[0051] An example sensor system 10 includes a sealed and waterproof body 10a (including main body 10a1 and auxiliary body 10a2) for connection to a beer keg 12 and specifically adjacent the keg port 12c and a connected keg valve/coupler assembly 14.

[0052] As shown in Figure 1, the body 10a contains a self-contained sensor package, that in one example, may include a controller 10b with associated memory 10b1, a temperature sensor 10c for measuring the temperature of a beer keg, a force sensor 10d for measuring force/movements of the beer keg, a keg status sensor 10e for detecting keg tapping/opening, a wireless communications system 10f for reporting and receiving data to a network and a power source/battery 10g. Other components may include an anti-tamper sensor 10h and LED status display 10i. The communication system may include both local area network (LAN) 10f 1 and wide area network (WAN) 10f2 communication systems. The sensor system may also include an externally configured code 10j.

[0053] As shown in Figures 1, 1A and 1B, in one example, the sensor body 10a1 is a generally circular body having an opening 11 for placement over and around a keg port 12c and valve/coupler assembly 14. The opening 11 is sized in order to allow the connection of standard valve/coupler assemblies to the keg without interference but also to bring the temperature and keg status sensors as described herein into close proximity to the keg and the valve/coupler assembly 14. The shape/design of the sensor body may be any suitable body that can be effectively configured/connected to the keg. In various examples, the sensor body could be a “u-shaped” body or “o-shaped” body that is place around the key valve. Other shapes/configurations are contemplated.

[0054] In various examples, the sensor system 10 is attached to a beer keg 12 by adhesives that provide a substantially permanent connection of the sensor system to a beer keg. In other examples, mechanical connections may be utilized.

[0055] The various sensors that may form part of a sensor system 10 are now described together with the various forms of data that may be obtained from each sensor as well as the processes by which the sensor system may be used to provide information about the status of a beer keg with a wider BKBQ system. Each sensor as described below may provide data that when interpreted with data collected from other sensors may provide status information about a beer keg.

Temperature Sensor

[0056] In one example, the temperature sensor (TS) 10c monitors the temperature of the beer keg over time. As noted above, the TS is placed in good thermal contact with the beer keg; however, this is not strictly necessary as measurement of temperature in close proximity to a beer keg may be sufficient. The temperature sensor may monitor temperatures from about 3°C to about 100°C during normal use. However, situations may occur where empty beer kegs are left outside in winter and hence, in various examples, are sufficiently robust to not fail if exposed to low temperatures (i.e. to about - 40°C). Normal temperatures during use will generally include three main temperature ranges. These include a “cold temperature” range, namely about 0°C - 6°C, which will be experienced and defined as the time when the beer keg has been filled with product and is being stored and/or transported. An “ambient temperature” range may be experienced and is defined as the time when the beer keg is empty and is being stored or transported and will typically be in the range of +5°C to +40°C depending on climate. However, as above, in certain areas, the ambient temperature range may be greater, for example between about -40°C to about +40°C. A “cleaning temperature” range may be experienced and is defined as the time when the beer keg is being cleaned and exposed to high temperature fluids and may be in the range of about 85°C-100°C.

Force Sensor

[0057] In various examples, the force sensor (FS) 10d monitors various movement and/or acceleration loads on the beer keg over time. Various movements or accelerations may include “cleaning”, “filling”, “storage”, “movement”, “emptying” and “damage” movements. In various examples, each may be identified by particular signal frequencies, signal peaks and durations as well as timing between events.

[0058] For example, a cleaning acceleration may be recognized by a rapid inversion of the beer keg immediately prior to cleaning, together with a sudden temperature increase and a second rapid inversion and temperature drop after cleaning has been completed. The time between cleaning, filling and storage is typically low and may thus provide secondary/error-proofing information that confirms or supports this keg status.

[0059] In one example, a filling acceleration may be recognized as a vibration of a particular frequency and duration. In addition, filling may be detected by the temperature pattern.

[0060] In one example, a storage acceleration may be recognized by movement which is then followed by lack of signal of a duration longer than a threshold timeframe. This may include checking location data (as described below) which may be particularly relevant for monitoring unauthorized filling of a keg.

[0061] In one example, a movement acceleration may be recognized by a signal having a variable frequency and duration longer than a threshold timeframe on its own or possibly in conjunction with a stable temperature.

[0062] In one example, an emptying acceleration may be recognized by a signal having a low frequency vibration, low duration and repetition over a threshold timeframe.

[0063] In one example, a damage acceleration may be recognized by a peak signal of high acceleration possibly in conjunction with a short threshold timeframe.

Keg Tap/Status Sensor

[0064] The sensor system may include a keg tap/status sensor 10e (referred to herein as a keg status sensor). In one example, the keg status sensor is at least one capacitance sensor (CS). The capacitance sensor detects changes in capacitance around or adjacent a keg port 12c and/or valve/coupler assembly 14 that in some examples may be a proxy for various activities including opening and closing of the keg (i.e. tapping).

[0065] For example, a sealed keg with a plug 16 (i.e. a metal or plastic plug/seal) in the keg opening may have a threshold capacitance. When the plug is opened or removed, and a valve/coupler assembly connected, the CS will detect a change in capacitance that may be interpreted that the keg has been opened and tapped. [0066] In one example, the capacitance sensor system may be a differential capacitive sensor configured within the auxiliary body. Importantly, the CS may be configured to filter out other events such as keg stacking to ensure that false keg tapping signals are not recorded. Opening a keg and inserting a valve/coupler assembly may be distinguished from a signal derived from stacking kegs by looking for characteristic signals. Specifically, in one example, capacitive plates are configured at opposite sides of the auxiliary body and may measure changes in capacitance at each side. If a keg is stacked on top of another, signals off both plates will generally be the same whereas, the insertion of a valve/coupler assembly may have different signals at each side indicating that the keg has been tapped. The same concept may be applied to determine if the keg has been inverted and remains inverted against a floor.

[0067] In other examples, other keg status sensor types including infra-red, laser, ultrasound and thru-beam sensors may be incorporated to detect keg tapping activity.

Anti-Tampering Sensor

[0068] In various examples, a sensor system may include an anti-tampering sensor (ATS) 10h that may detect attempts to open or detach the sensor system 10 from the keg. In one example, the ATS may be in contact with the keg and measure conductivity across two probes contacting the keg such that if conductivity is lost, this is a signal that the sensor system has become fully or partially separated from the keg.

Location/Communication Sensors

[0069] In various examples, as shown in Figures 1 and 2A, the sensor system may include a location detection and communications system 10f that determines the location of the sensor system/keg, communicates location and sensor data to a local area network (LAN) 30 and/or wide area network (WAN) 31 and receives instructions/data from a central communications system 41 as well as local computer/embedded systems 40 and/or portable computer systems 41a and/or a customer interface 40b.

[0070] As one objective of the system is to provide a cost-effective solution to users (e.g. breweries and pubs), in various examples, the communications interface enables a combination of both coarse and fine location determination depending on the proximity/availability of different networks and the desired objectives of the users. In various examples, the precision of location data is not critical and “coarse” location data (e.g. within 50m-5km) may provide sufficient information for effective keg monitoring under certain deployment scenarios. In other scenarios, greater precision is obtained. In various examples, depending on the desired accuracy, communication systems using different protocols may be implemented, the choice of communication system taking into account the actual cost of communication system electronics and ongoing data costs.

[0071] In various examples, the system may utilize cellular or LORA signals to obtain and record coarse positioning information within a wide-area network and Bluetooth Low Energy (BLE) systems and/or WiFi within local-area networks to obtain and record fine positioning information (< about 50m). In each case, data from the sensors may be communicated to the cloud and delivered to various monitoring computer systems as described below.

[0072] In various examples and in the case of the LAN system being WiFi, the WiFi system within the sensor system turns on, looks for SSID’s and when a connection is made, communicates with the cloud which based on SSID location information may then be used to look up a physical location of the keg.

[0073] Cellular or LORA systems may be used to both locate the system and to transmit data to the network. In various examples, the system may be configured to deliver data on a schedule (for example, twice per day). Various protocols may be used such as POLTE™ service that provide low-cost location reporting within a cellular network. Location accuracy may vary between 50 m - 5 km depending on cell tower locations relative to the sensor system.

[0074] Close range location determination may be desirable within various locations within authorized breweries to pin-point keg location during specific stages of the keg cycle. For example, various quality control and efficiency measures may be implemented by precise determination of the location of a keg at a particular time within a brewery. As explained below, this may include pin-pointing if a keg is in storage, has been cleaned, has been filled and/or has entered or left the brewery. BLE systems may require auxiliary BLE beacons to be placed in known locations such as specific zones within a brewery and/or at specific pubs which are known to the central system. Thus, in various examples, a keg may report to a specific beacon, and the precise location of the keg can be determined based on a known location of a specific beacon.

[0075] Further, BLE systems may allow for communication with nearby smart devices (e.g. smart phones, tablets and the like) and/or networks for certain activities such as system activation, servicing and/or software updates. For example, during installation a technician may activate the sensor system and perform system checks at the time a keg is introduced and activated by a brewery. Similarly, servicing and maintenance may be initiated through a BLE system by a technician with a portable computer system (e.g. a smart phone or tablet) 40a, Figure 2A.

[0076] In various examples, BLE systems may also enable individual pubs to track keg movement within the pub to detect and provide information to the pub including product life monitoring and inventory control as explained below. Such functionality may also be accomplished with WAN and LAN’s by recognition/identification of serial numbers of kegs on premises.

[0077] In various examples, BLE systems may have low power requirements which are beneficial to enhance battery life.

[0078] Location data may be collected at regular intervals according to various protocols that may obtain a desired granularity of data but may also be optimized to enhance battery life. For example, when a reliable connection is not established, the system may store data until such time that a reliable connection to a network is established.

[0079] In various examples, in order to enhance connection to WANs and LANs, the communications system may be contained in a separate auxiliary-body 10a2 distinct the main sensor body 10a1. The auxiliary-body may be taller to enhance antenna orientation and performance for the communications systems.

[0080] In other embodiments, other network system/protocols may be utilized. For example, LORA or SubGig networks may be utilized to both send/receive data and provide location services using machine to machine communications. [0081] In various examples, where it is desirable to minimize costs, the sensors may collect data, but only transmit it once it has access to a WAN device. In this example, this may reduce costs by not requiring a live/real-time connection to the central computer system 41. In various examples, a user may not require live information and may only obtain keg data once the keg returns to brewery. In various examples, once the keg returns, keg data may be downloaded (e.g. via BLE or WiFi (LAN)) to a network within the filling station. In various examples, this may be utilized as a system that may be deployed with less complexity compared to systems where live data is collected and reported throughout the beer keg cycle.

Status LED

[0082] In various examples, a sensor system may be provided with an optional status LED 10i to signal that the system is operating correctly or not. For example, a slow- blinking LED may indicate correct operation whereas a faster blinking LED may indicate a problem.

Battery

[0083] In various examples, a power system/battery 10g has sufficient capacity for up to about 12-24+ months use before requiring replacement. In various examples, battery voltage is monitored and may be reported to the central computer system to identify when a battery should be replaced. In various examples, access to the battery is obtained through a sealable access port (not shown).

Sensor System Code

[0084] In various examples, the sensor system may include an external code 10j for keg identification particularly during activation or maintenance. In other examples, pubs may obtain ID data from the kegs to aid in inventory control within the pubs. A code may be a scannable code such as a barcode, QR code or other codes as are known.

Sensor System Controller

[0085] In various examples, a controller (also referred to herein as processor(s)) 10b receives data from sensors, and provides that data to memory 10b1 for storage and/or to the communications interface for transmittal to the central system and/or to a local computer 40 and/or local technician’s interface 40a. All data that is collected by individual sensors may add a date and time signature. As noted, the controller may include associated memory 10b1 including data memory to store data from the sensors and application memory to enable sensor functions to be performed. Various functions for collecting and storing data include but are not limited to: a. Activation at time thresholds to activate the temperature sensor. b. Activation at time thresholds to activate the location sensor(s). c. Activation of the force sensor in response to impact thresholds. d. Activation of the keg status (e.g. capacitance) sensors in response to changes in keg status/capacitance. e. Battery voltage monitoring to report state-of-charge of the battery. f. LED activation in response to status data. g. Activation in response to tampering. h. Activation to receive software updates i. Adding a time/date signature to all collected data. j. Activation in response to location sensors thresholds being exceeded.

[0086] The controller/processor(s) 10b may comprise clock-driven computing component(s) configured to process data, and the memory 10b1 may comprise a computer-readable medium (e.g., a tangible, non-transitory computer-readable medium, data storage loaded with one or more of the software components) configured to store instructions for performing various operations and/or functions. The controller/processor(s) 10b are configured to execute the instructions stored on the memory 10b1 to perform one or more of the operations.

[0087] In some examples, the memory 10b1 may be configured to store data associated with the sensor system 10, such as various operational characteristics such as device version information, brewery location, and/or other information regarding the broader operating environment of a beer keg cycle. Stored data may comprise one or more state variables that are periodically updated and used to describe a state of the sensor system 10.

Keg Cycle

[0088] As shown in Figures 2 and 2A, in various examples, the system is designed to operate within a beer keg cycle and specifically to obtain data during authorized and unauthorized movement of a beer keg. A representative example of a beer keg cycle within an authorized brewery 20, trucks 22 and a pub 30 is described.

[0089] At an authorized brewery 20, a keg may move between a first storage area 20a to a cleaning area 20b, to a filling area 20c and a second cold storage area 20d.

[0090] That is, kegs returning from a pub 30 may be initially stored in a warm storage area (i.e. not refrigerated area) 20a before being cleaned in a cleaning area 20b. During cleaning a keg is inverted for hot (i.e. greater than ambient temperature) cleaning fluids to be injected into the overturned keg through the keg port. During this process, for example, the system 10 may detect specific movements such as movement of the kegs along a conveyer belt and the inversion and re-inversion of the keg before and after cleaning. In addition, during cleaning the temperature sensor may detect a rapid rise and fall in temperature and the capacitance sensor may detect the presence of specific cleaning equipment (for example cleaning nozzles/pipes being introduced into the keg port) and/or the removal of any seals. The location system may also confirm the location of the keg within the brewery.

[0091] After cleaning, the keg may be returned to a storage location (may be a “cleaned” storage location) or to a filling location 20c. Filling may be detected by a rapid drop in temperature to the “cold temperature”, possibly together with signature changes in capacitance. When the keg is full and the keg port has been sealed, a “sealed” capacitance level may be measured. Other signals such as a “stacked” keg signal may also be noted. In various examples, the location system may also confirm the location of the keg within the brewery. Accurate confirmation of the location of the keg within the brewery via the various positioning systems described may be used as a means to verify/confirm the authenticity of the contents of the keg, that is, that the keg has been filled with intended beer.

[0092] After filling, the keg may be placed in a “cold storage” location 20d prior to loading on a vehicle during which temperature may be monitored to determine any changes in temperature.

[0093] Kegs may be loaded onto trucks 22 for delivery to pubs 30 (30, 30a-30e) which represent a delivery route a truck 22 may take. At an example pub 30, depending on the size of the pub, and if local area detection equipment 50 is installed at the pub and desired data may be, the location system may detect the movement of a keg through the storage and dispensing steps at the pub. That is, a keg may arrive at an arrivals location 30a and successively be moved to a cold storage area 30b, dispensing area 30c and when empty to a warm storage area 30d. During each of these locations, the temperature, acceleration and capacitance sensors may monitor movement, location, temperature and capacitance. However, in one example, this level of granularity of location data may not be required or desired at certain pubs.

Best-Before Date (BBD) and Adjusted Best-Before Date (ABBD)

[0094] In various examples, the capacitance sensor may detect the time that the keg is tapped for dispensing thus enabling the BKBQ system to establish a time-point to monitor beer freshness based on a known/estimated shelf-life. Based on data collected from the various sensors, the best-before data may be dynamically adjusted by the BKBQ system. In various examples, a best-before date (BBD) may be sent to the pub on keg opening and an adjusted best-before date (ABBD) may be sent to the pub if that keg is approaching a freshness date (e.g. a BBD or ABBD).

[0095] For example, as shown in Figure 3, depending on the time of and nature of out- of-specification events, the BBD may be dynamically adjusted. If a beer keg is maintained within specification, a maximum or optimum best-before date Z may be estimated by the brewery based on their general knowledge of their product. Generally, the “relative freshness” of a beer may decline slightly over the normal life 1, and then drop off more rapidly T closer to the best-before date as shown by representative freshness curves (1-5). Out-of-specification events or tapping/opening the keg (Events A-l; scenarios 1-5) may have an affect on the freshness curve and may decrease the time until the beer is considered below a threshold quality.

[0096] When a keg is opened or tapped, the rate at which the relative freshness declines may increase. Similarly, out-of-specification events may also increase the rate at which relative freshness declines. Figure 3 illustrates how relative freshness may decline based on different events for a hypothetical beer keg shown as scenarios 1-5. Figure 3B shows the steps that may be followed to dynamically adjust a best-before date based on particular events.

[0097] With reference to Figure 3, scenario 1 shows an example maximum product freshness curve if the beer keg is stored properly and never opened. Scenario 2 shows a product freshness curve where the keg is opened in a pub and consumption/dispensing occurs without events. Scenarios 3, 4 and 5 show example product freshness curves where out-of-specification events have occurred.

[0098] In one example, scenario 2 shows a keg being opened at time C and dispensed in the usual manner. Generally, after a keg has been opened, the rate at which the relative freshness declines may increase.

[0099] In one example, scenario 3 shows a curve where the keg may have been stored longer than scenario 3 where it was then subjected to a shaking event at D and was then opened at I.

[0100] In one example, scenario 4 shows a curve where the keg was opened at B and the keg was not emptied quickly and at H was subjected to a temporary temperature increase due to a power failure at the pub which triggered a more rapid decrease in relative freshness.

[0101] In one example, scenario 5 shows a curve where at the time of delivery of the keg to the pub, a first event A occurred where the keg was left in the sun for two hours in the summer and was then dropped at time F before being opened at G. As can be seen, the relative freshness of keg under scenario 5 shows the greatest decrease in relative freshness and best-before date. [0102] Figure 3A illustrates steps that may be undertaken to determine an adjusted best-before date.

[0103] As with Figure 3, a maximum best-before date is shown as scenario 1 with a calculated maximum best-before date Z. In one example, as above for scenario 5, the keg was left in the sun at time A wherein the amount of time (in this example case-2 hours) and the maximum temperature of the keg (for example the keg reached a temperature of 10° C) may be recorded and reported to the CCS. Based on the quantitative measures of time and temperature, these values may be correlated to a decrease in BBD as shown by line 5’. For example, absent of any further events, the BBD could be updated based on the projection of freshness decline between times A and Z as shown by 5’. In this example, as a result of the temperature event at A, the rate of freshness decline may be calculated based on the relative magnitude of the out-of- specification event. In this example, 2 hours @ 10 °C, resulted in a calculated decline curve as shown by 5’. If the temperature event was less severe, for example 2 hours @

5 °C, the calculated decline curve may have been 5A or if it had been more severe, for example 3 hours @ 12 °C, the calculated decline curve may have been 5B. As such, depending on the relative severity of the event, the BBD may be unaffected as the decline curve intersects with the maximum BBD curve (i.e. for 5’ and 5A) but may be affected as shown for 5B where the decline curve intersects with the freshness threshold at T.

[0104] As shown, if subsequent events occur as shown by way of example, at F and G, the BBD may be progressively updated as best-before date (BBD) X (line 6’) and then BBD W (line T).

[0105] As such, and depending on the timing, nature and duration of events, an adjusted best-before date (ABBD) may be estimated and communicated to either or both of the brewery and the pub based on an understanding of the relative severity of any out-of-specification events.

[0106] For example, a BBD algorithm, based on a temperature event of a particular severity, the CCS may determine that the best-before date is advanced 14 days and thus, the beer should be consumed within a shorter time period, for example within 3 days if the best-before date was originally 17 days away. The BKBQ system may then communicate with the pub that the BBD has been advanced which may then be used by the pub to take decisions regarding that product. Such actions may be that the pub will promote consumption of that particular beer possibly by offering a discount on that beer or some other promotion.

Empty Keg

[0107] In addition, the BKBQ system may notify the pub/brewery that a keg is empty. In one embodiment, a combination of movement and temperature may be used to signal that a keg is empty; such as a rise to ambient temperature as the keg is disconnected from dispensing equipment and moved to a storage location. As the BKBQ system may have determined the time at which the keg was opened and may determine when the keg is empty this also may also enable a calculation of the consumption rate between time 1 (keg opening) and time 2 (keg emptied) (together with knowledge of the volume of the keg) which may be useful to both the pub and brewery for the purposes of ordering and delivery of new kegs.

[0108] When the keg is empty, the pub may move the keg to a storage area for return to the brewery. Depending on the pub, this may be back to a cold storage area or to a warm storage area. In either case, the temperature sensor and accelerometer may detect movement over a relatively short period of time that may be confirmed by a location sensor.

[0109] In various examples, the keg may be returned to the authorized brewery (AB) for cleaning and refilling. The sensors may detect the movement to a truck and movement on the truck. As shown in Figure 2, a truck’s route back to an AB may include stops at multiple pubs 30b-30e which may be detected by the location sensor. As pubs 30b-30e may be known authorized pubs, no unauthorized brewery/pub warnings may be triggered as explained below.

[0110] The sensors may also determine that the keg has been returned to the AB and the cycle begins anew. Unauthorized Breweries/Pubs/Theft/Damage

[0111] Importantly, the BKBQ system may detect unauthorized activity including re-filling a keg at an unauthorized location such as an unauthorized brewery/pub 21 and/or theft of the keg. Unauthorized filling may be detected by a combination of the location sensors, temperature, keg status (capacitance) and force sensors as described above, where the location sensors confirm that the keg is not at an authorized brewery. When detected, the AB may receive a report allowing appropriate action/notification to be taken with the pub by the AB.

[0112] In various examples, theft of a keg may be detected by the location sensors detecting the keg being outside of an authorized zone including authorized pubs or known routes. Theft may be detected immediately or over a period of time depending on circumstances.

[0113] In various examples, damage to a keg may also be detected by rapid accelerations and/or various signal patterns such as a slow rise in keg temperature if a keg is leaking for example.

User Application Software

[0114] The BKBQ system may be provided with application software to enable users including brewery personnel and pub personnel to receive data about individual and/or groups of kegs at one or more local computers 40. A central computer system 41 may communicate with equipment within the network for data collection and to provide software updates.

[0115] In one example, brewery personnel may be provided with relevant inventory information such as the current number of empty, cleaned, filled, and stored kegs in their facilities (amongst other data) as may have been determined by the BKBQ system collecting and reporting data to a central computer system 41. Other data may include information about the number of kegs in transit, within pub facilities, the number of kegs filled with unauthorized contents, and lost and/or at unauthorized locations (amongst other data) as may have been determined by the BKBQ system collecting and reporting data to a central computer system 41. In addition, the brewery may receive information about keg status at a pub, including temperature, best-before dates, date/time of a keg being opened and other events as described above, if kegs at a pub are communicating with the network.

[0116] Information available to pubs may include information about the status of kegs that have been ordered, are in transit, as well as information about shelf life for kegs in the pub. Consumption estimates may be provided to assist the pub in ordering new supplies.

Sensor Data

[0117] Table 1 summarizes various signal patterns that allows the BKBQ system to monitor a variety/range of events within a beer keg cycle. Further, as shown in Figures 3B-3D, representative signals from sensors that may be configured are shown.

Examples are shown for capacitance, force/acceleration, location and temperature as may be collected at different locations including an authorized brewery (AB), a pub or an unauthorized brewery 21 or location under various situations. As shown in Table 1 and Figures 3B-3D, the combination of different sensor signals may provide important event/status information to system users. The following events and signal patterns are not meant to be definitive and other patterns may be recognized representing other conditions based on the different types of sensors that have been configured, the specific data collected by those sensors and various thresholds that may be associated with various sensors. It is understood that any data collected from one or more sensors may have a time stamp associated with each data point, and the time order of data, may be interpreted as corresponding to a specific type of event.

Table 1 -Representative Signals, Patterns and Status Conclusions

[0118] Importantly, the BKBQ system may not require any hardware to be installed at the brewery or the pub; rather all data may be transmitted/received at defined times and/or when a communication link may be established. This may provide an advantage over systems that require equipment to be installed in breweries and/or pubs. In one example, all data collected during the beer keg is stored in memory and is only retrieved and analyzed when the beer keg has returned to the brewery and data uploaded to the central computer system from the brewery. [0119] In other examples, real-time and/or greater precision is desired and beacon/hub hardware 50 as shown in Figure 2 may be installed in locations where more accurate location tracking is required particularly at breweries and larger pubs.

Machine Learning

[0120] In various embodiments, data collected throughout the BKBQ system will include data associated with a significant number of beer kegs, pubs, authorized breweries and out-of-specification events including unauthorized filling. Over time, data collected may be analyzed for various patterns of data that may be helpful to breweries and pubs in improving the efficiencies of each business.

[0121] For example, data patterns associated with a brewery may be used to actively monitor the status and utilization of beer keg equipment within the brewery itself as well as with their customers. Such data may be useful for the purposes of determining appropriate inventories of kegs based on historical patterns of keg cycle events including events such as damage, maintenance and theft and from an analysis of that data suggest actions that reduce such events and/or to enable planning for such events. For example, over time it may be determined that out-of-specification events are occurring with an increased frequency within a particular area/route such that pro-active steps may be taken to reduce/mitigate the effects of these events.

[0122] In another example, keg utilization and movement monitoring within a brewery or pub may suggest inefficiencies within a brewery or pub for example, a determination that kegs are spending too much time within a particular zone of a brewery or are being stored outside of ideal conditions at a pub.

[0123] Historical data may be utilized to predict the likelihood of future events based on historical patterns where the data is utilized within learning models to understand the affect of out-of-specification events and also predict out-of-specification events across a distributed network.

[0124] In one example, over time, as data is collected around out-of-specification events, improved predictions of the affect of out-of-specification events may be made. For example, correlations between relative freshness and events may lead to improved accuracy in calculating best-before dates.

[0125] In one example, as shown in Figure 4, a representative flowchart of the process for dynamically updating a BBD is shown as a beer keg may move throughout a beer keg cycle. In this example, a beer keg is registered and activated 60a at which time it may be considered to be actively within a beer keg cycle where depending on the configuration of the BKBQ system, data may be periodically collected and reported to users.

[0126] In this example, the BKBQ system may analyze data 60b from the keg and determine if the keg has been filled 60c. If the keg has been filled, the BKBQ system may assign a BBD 60d based on a predetermined BBD for a particular beer that the keg has been filled with.

[0127] The keg may be stored within a brewery or delivered to a pub 60e. Depending on the location, the BDD may be reported to the brewery or pub 60f.

[0128] On an ongoing basis, the central computer system may receive keg data 60g and may initially determine keg location 60h (e.g. brewery, in transit, pub). In each case, the BKBQ system may collect and analyze data to determine if the keg is/has been in specification 60i and whether the keg has been tapped 60j. If it is determined that the keg was not in-specification, the out-of-specification event may be analyzed 60k to determine if the BBD should be updated 60I. If so, the BBD may be reported to the keg location 60m. Similarly, if it is determined that the keg has been tapped 60j, a similar process may be followed.

[0129] A representative example of adjusting a BBD is as follows. A new customer/pub orders a number of kegs from the brewery. Half the kegs are a pasteurized product and half are an unpasteurized product with a shorter BBD. The pub is located in a rural location that requires travel over a rough road for 10km. As the customer is new, there is no data about this pub or details/past information about the keg cycle for this pub. After delivery, the BKBQ system receives data from the kegs. An initial out-of-specification event is reported indicating that the kegs were subjected to significant shaking during transport. A second out-of-specification event is detected indicating an elevated temperature. The system analyzes the data and calculates a 4-day reduction in BBD for the unpasteurized beer and 2-day reduction in BBD for the pasteurized beer with the majority of the reduction being determined as being a result of the temperature issue. Over time, and with repeated deliveries, it may be determined that the first delivery was an aberration with respect to the temperature and no further events are detected. However, the shaking events continue as they cannot be avoided during transport. Hence, the pub may be made aware and understand that the product they receive may have a shorter BBD.

[0130] In another example, data may reveal that deliveries to pubs that must travel across rough roads for a period of time subject the kegs to shaking motions that affect the best-before dates. Thus, the BKBQ system may learn from this, wherein if customers are located in areas where similar shaking will occur, the system may automatically update the best-before dates for that new customer based on learned conclusions from the system.

[0131] Specifically, the steps of predicting out-of-specification events may include introducing historical temperature, force and location data from a plurality of beer kegs within a distributed network into a database, the historical data including beer quality events and analyzing the historical data to extract events of interest relating to beer handling and correlating the events of interest to beer quality events.

[0132] The models may test the analyzed data using various algorithms including machine-learning algorithms to train the models to recognize out-of-specification events.

[0133] After training, current beer keg data may be introduced into the prediction model to determine the likelihood of certain out-of-specification events occurring within the network.

[0134] As additional historical data is collected, the models may be refined and testing against the enlarged datasets may look for and identify additional events and improve the accuracy of the predictions. Sensor System Cost

[0135] It is an objective of the BKBQ system that the cost of the system is low but retains flexibility in deployment. In various examples, the sensor system 10 primarily functions as a data collection and communication system that does not affect normal handling of beer kegs by persons operating within the beer keg cycle. As data may be collected at intervals and may not inherently require immediate reporting to provide meaningful data for analysis, system components and the cost of data communication may utilize low cost, lower power and lower cost communication protocols. Data analysis may be conducted centrally that may be reported back to the users and system updates may be communicated back to the keg sensor system when data communication is optimal.

Customer Interface

[0136] In various examples, the system may be provided with a customer interface 40b that provides a signal to a pub customer regarding the legitimacy and/or relative freshness of the beer they are drinking from a glass within the pub.

[0137] As shown in Figure 2A, freshness data may be communicated back to the pub that is relevant to specific kegs of beer that are known to be at that pub. For pub personnel, this data may be useful to understand if any issues exist with respect to the products being served to customers. In addition, some data may also be displayed to the customer including data that verifies the legitimacy of the freshness of the beer (i.e. “this beer is ‘guaranteed’ fresh”). Such information may be presented to the customer in various forms such as a TV display in the pub certifying that Brewery X beer is fresh. For example, if Brewery X is serving 4 different beers at the pub, each beer may, for example, be listed on a TV with a graphical indication of the freshness of that specific keg. For example, a graphical indication may be for example a graphical symbol showing “green for fresh” and “orange for not as fresh”, and/or a bar slider and/or a “freshness number”. Thus, the customer sitting at a table may be able to look at the TV and see that the beer from Brewery X is being guaranteed as fresh whereas the beer from Brewery Y is not shown. Thus, for the customer sitting in a pub, making a decision on which beer to buy, this may provide effective information to the customer that results in one brewery/beer being selected over another. [0138] Although the present invention has been described and illustrated with respect to various examples and embodiments, it is not to be so limited since modifications and changes can be made therein which are within the full, intended scope of the invention as understood by those skilled in the art.