Beverage dispensing systems in commercial settings like restaurants, bars, stadiums, casinos, and others with large scale inventory sales tend to suffer from challenges with inventory loss, training, and transaction tracking. Many of these establishments suffer high “pour” rate costs that reflect the inventory loss that occurs in these situations. Each beverage dispensing location has a human user that physically dispenses the beverages for patrons. Oftentimes, users over-pour beverages, either intentionally or accidentally, which results in wasted inventory and lost profits. Further, these establishments tend to have high sales volumes of beverages, which generates a large amount of data and they often find inventory reconciliation with sales transaction very difficult.
Some owners use existing pour tracking systems can monitor the volume of a beverage being dispensed at a particular dispensing location by placing a flow rate sensor in-line with the dispensed beverage. However, those in-line tracking systems often cause decreased beverage pour quality, specifically with beverages like beer, because the in-line sensors disrupt the fluid flow of the beverage being dispensed. In the example of beer, the flow of the beer becomes turbulent as a result of being forced to flow over an in-line flow rate sensor which generates too much foam in the dispensed beer. If a beer is poured with too much foam, the user may choose to re-pour the beer or serve it to the patron with the risk that the patron will be dissatisfied with the quality of the beer. Also, the output from the conventional in-line flow rate systems is raw data of the volume of dispensed beverage at a particular beverage dispenser. Large establishments quickly generate immense amounts of data about beverages poured and owners are challenged to make sense of the raw data generated by the conventional systems.
The beverage dispensing art would benefit from improved beverage dispensing monitoring systems and methods that help improve accountability, data integrity, and profitability.
The disclosed beverage dispensing tap monitors are attached to beverage dispensing taps that are often, although not required to be, included in a beverage dispensing system with multiple beverage sources that are connected to corresponding multiple beverage dispensing taps. The beverage dispensing tap monitors have a tilt sensor that can sense when the beverage dispensing taps are in a closed position in which no beverage is being dispensed and an open position in which beverage is being dispensed from the tap by being able to track the position of the tap handle. When the tilt sensor determines that a tap is moved from a closed position to an open position, it triggers a clock to begin timing how long the tap is open and dispensing the beverage.
The monitor has processing circuitry that generates pour data about the beverage pour that is based on the amount of time the tap is open and assigns a unique tap identifier and/or a unique pour identifier to the data. The pour data is wirelessly transmitted by a wireless transceiver to a remote computing device. The wireless transceiver continuously awaits an acknowledgement from the remote computing device that the pour data was safely received. If the acknowledgement is not received within a particular time period, the pour data is stored in local memory in the monitor and another transmission attempt is scheduled for a later time. Additional data can be sent to the remote computing device along with the pour data including the type or brand of the dispensed beverage, the quality of the poured beverage, any ambient environment characteristics sensed around the beverage dispensing tap, and/or any other relevant information.
Features, functions, and advantages may be achieved independently in various embodiments of the present disclosure, or may be combined in yet other embodiments, further details of which can be seen with reference to the following description and drawings.
The disclosed beverage dispensing systems provide improved accountability, inventory tracking and monitoring, report generation, and reconciliation and variance analysis with sales transactions. A beverage dispensing monitor is attached to a beverage dispensing tap and can track the amount of time the tap is open and dispensing a beverage. The tracked time is sent to a reader that confirms and/or analyzes the tracked time and forwards it on to a central server and/or point-of-sale server. The beverages dispensed from the disclosed monitoring systems are most often beer but could also be wine or other beverage(s) dispensed through a beverage dispensing tap from a beverage source. The beverage source is typically remote from the beverage tap, which could mean that the beverage source is in a keg or other beverage container located in a cabinet or other housing below or near the beverage dispensing tap(s) or it could be remote like a back-room that stores multiple beverage container(s) and has a network of tubing and pumps that cause the beverage(s) to be delivered to the beverage taps for dispensing. The beverages can be chilled at the beverage source or anywhere along a pathway from the beverage source to the beverage dispensing tap. Any suitable beverage delivery system can be used in the disclosed beverage dispensing systems.
The readers 112, 114, 116 are typically located relatively local to the taps to which they are wirelessly connected. The wireless connection can be any suitable wireless network protocol and in some examples is a short range wireless connectivity standard like Bluetooth®. The readers 112, 114, 116 serve as a base station for their connected beverage dispensing taps and receive the transmitted data from each tap. The readers 112, 114, 116 transmit an acknowledgement back to the sending beverage dispensing tap when a transmission with pour data is received. The readers can store and analyze the received data in some examples before transmitting it along to a central server 118. The central server 118 stores the pour data in memory 120 and its processor can perform various analyses on the data, as desired.
The central server 118 can optionally interface with a point-of-sale 124 system like a conventional system that manages beverage pour transactions. The point-of-sale system 124 can be a conventional or custom point-of-sale server 124 with associated transaction software that permits users like bartenders and servers to enter patron orders and generate bills for the patron purchases. Conventional point-of-sale software only focuses on the input transaction of the user entering data into the system and does not track the actual inventory that is output from the system, whether to a customer or otherwise. Having a point-of-sale software system interface with the disclosed beverage dispensing tap monitors improves user accountability, inventory tracking, system integrity, and profit margin. The point-of-sale systems generate transaction data, such as the number and type of beverages that are entered as a purchase for a patron. That generated point-of-sale data can be compared to the data generated by the disclosed monitors, which compares the transaction data with the actual pour data. Such a comparison between transaction data and actual pour data can be performed in any suitable way and any type of output can be generated. In some examples, comparisons are made between the two data sets to identify discrepancies while other more complex analysis can be performed in other example systems such as variance analysis, system analysis, user accountability analysis, and the like. The output of the analysis between the point-of-sale transaction data and the pour data can be compiled into a report of any kind, such as a variance report. The reports can be customizable if desired by selecting specific data to analyze, such as data from a specific user or data related to a particular beverage and the like.
The first, closed position 316 prevents the beverage from flowing through the beverage spout 306 and the tap handle 302 is generally in an upright position. In the example shown in
To begin a beverage pour, a user engages the tap handle 302 when it is in the first, closed position 316 to pour a beverage of a chosen volume. To begin the pour, the user physically moves the handle to a second, open position 318 that allows beverage to flow through the spout 306 into a container like a glass or pitcher. In the example shown in
The beverage dispensing monitor 308 is attached to one of the arms 330 of the alignment bracket 310 with two screws 338, 340. One of the screws 338 is exposed at a position spaced apart from the tap 300 handle 302 and the body 304 that allows for easy access for a user if the monitor 308 needs to be removed from the alignment bracket 310 for any reason like maintenance or replacement. The second screw 340 is positioned near the neck 324 of the spout 306 when the alignment bracket 310 is secured to the beverage dispensing tap 300 and is accessible through a hole 342 in the opposing arm 328 of the bracket 310. A user would insert a screw driver or other removal mechanism through the hole 342 to engage with the screw 340 on the opposite arm 330.
The tilt sensor 502 can be any suitable tilt sensor 502 that can measure and quantify a tilt of an object along one or more axes. The tilt sensor 502 can be an accelerometer that is particularly useful in determining the position of an object in motion like when the tap handle begins to move from the first, closed position to the second, open position or the reverse. Other tilt sensors can also be used, such as a ball sensor, or other alternative tilt sensors. Multiple tilt sensors can be used as well.
The tilt sensor 502 is configured to sense a position of a beverage dispensing tap in at least a first, closed position and a second, open position, i.e, the tilt sensor can sense the physical orientation of the object to which it is attached. In the case of the tilt sensor 502 being an accelerometer, the accelerometer measures an object's proper acceleration in one or more axes, it can sense any movement of the beverage dispensing tap along its typical arc pathway from its closed position to its open position. A beer tap, for example, has a handle to which the monitor with the accelerometer is attached that senses when a user engages the handle to move it towards its open position to pour the beer. Because the monitor 500, with the tilt sensor 502 housed inside the monitor 500, moves in unison with the beverage dispensing tap, the tilt sensor 502 can physically sense the movement and/or the position of the beverage dispensing tap. The tilt sensor 502, or specifically an accelerometer, can sense the position of the beverage dispensing tap when the handle is in any position and during any time throughout the movement of the handle. The tilt sensor 502 is electrically coupled to a clock 504 that can measure the amount of time that the beverage dispensing tap is in the open position.
When the tilt sensor 502 senses that a user moved the tap handle, it generates an instruction that is sent via an electrical connection to the clock 504, in some examples. The connection between the tilt sensor 502 and the clock 504 can be any suitable electronics configuration to allow the two components to be electrically coupled to each other. The instruction causes the clock 504 to begin timing the pour of the beverage being dispensed from the beverage dispensing tap. The clock 504 is any suitable timing device that can track time in response to receiving a signal. The initiation signal is received by the clock 504, the clock 504 then begins timing the pour, and awaits an instruction to stop timing the pour. When the user returns the beverage dispensing tap to its closed position, which indicates that the pour has stopped, the tilt sensor 502, or in a specific example, an accelerometer, again senses movement in the tap and generates another instruction that is sent to the clock 504 and instructs the clock 504 to stop timing the pour. After the clock 504 receives a stop instruction to cease timing the pour, the clock 504 is programmed to await a subsequent instruction to receive another pour start instruction.
The clock 504 is electrically coupled in any suitable connection to processing circuitry 506, such as a suitable micro-controller. Some examples also electrically couple the tilt sensor 502 to the processing circuitry 506 although that arrangement is optional. The clock 504 is programmed to automatically generate data with the amount of time that the beverage dispensing tap was in the open position and automatically send it to the processing circuitry 506. The processing circuitry 506 assigns a unique tap identifier and/or a unique pour identifier to the data that it receives from the clock 504. The unique tap identifier is an electronic identifier that is unique to the tap at which the beverage was dispensed. The unique pour identifier is any data that is relevant to the pour, such as timestamp data, for example. One or both of the unique tap identifier and the unique pour identifier data can be assigned to the data received from the clock 504.
The processing circuitry 506 then optionally considers data received from other sensors 516 in the system, such as temperature sensors and pour quality sensors. For examples like beer dispensing systems with multiple kegs and a network of lines and pumps that dispense beer to dispensing taps at various service station, the beer needs to be kept at a particular desired temperature or within a range of temperatures to ensure quality beer is poured at the tap. These beer dispensing systems in particular need temperature control, sometimes from the keg to the dispensing tap. In some examples, the beer tap itself is kept at a particular temperature. A temperature sensor could be secured to the beer tap or other part of the dispensing system and can electrically transmit temperature data for the portion of the system that is monitors back to the processing circuitry in the tap monitor. A temperature sensor could also be included physically inside the monitor 500 with the tilt sensor 502 and clock 504. Such a temperature sensor can be programmed to sense temperature, either continuously, on-demand, or on a pre-determined schedule, the temperature of the beverage dispensing tap 500 or any other component of the system.
A pressure sensor could also be included in the system to measure pressure in any relevant place in the system to monitor system performance or to alert users of a malfunctioning line or potential damage. Beer dispensing systems, for example, are pressurized to a pressure within a particular desired range of pressures. If the pressure falls below or rises above the desired pressure range, the system malfunctions and need service or maintenance.
The processing circuitry 506 also includes a calibration module 512. The calibration module 512 is custom information specific to the particular pathway from the beverage dispensing source to the beverage dispensing tap 500. Each tap has varying features and characteristics so the calibration module 512 has calibration data 514 that is specific to each tap. The calibration data 514 includes any objective information that affects the flow rate of the beverage through the system including the distance between the beverage source and the tap, the configuration of the pathway of the line between the beverage source and the tap, the diameter of the line connecting the beverage source and the tap, the pressure within the line or the tap, a type of line or pump used, and the like. A user may include subjective information that might affect the flow rate of the beverage from the beverage source to the tap, which includes observation data or other data gleaned from the user's experience, or the calibration data may be based entirely on the objective data. The calibration data 514 may be periodically tested for accuracy and reliability to ensure that the final determination of pour data that is output by the processing circuitry is accurate. Calibration data 514 is used to normalize the output pour data from the processing circuitry. Because each pour is adjusted to a normalized value of a pour based on the specifics of each tap's physical characteristics, the output pour data can be compared between taps that have differing physical configurations and features.
The processing circuitry 506 generates pour data that is output to a wireless transceiver 508 for transmission to a remote computing device. The pour data is based on the data received from the clock 504 about the amount of time the clock 504 determined that the tap 500 was open and the unique tap identifier and/or the unique pour identifier. The pour data may be adjusted or analyzed by the processing circuitry 506 before it is transmitted to the wireless transceiver 508 for transmission.
The wireless transceiver 508 receives the pour data from the processing circuitry 506 and wirelessly transmits it to a remote computing device. The wireless transceiver 508 both sends and receives data—it sends the pour data to the remote computing device and it awaits an acknowledgement from the remote computing device that the pour data was properly received by the remote computing device. The remote computing device can be any suitable computing device that can wirelessly communicate with the wireless transceiver 508 including a computer, like a laptop, tablet, mobile phone, or desktop computer; a central server; or a base station, like a reader, a repeater, or some other receiver. The remote computing device can have memory and processing circuitry of its own and can be wirelessly connected to multiple taps in a networked system. The remote computing device memory can store pour data from each tap to which it is wirelessly connected for later use or for system reliability to ensure that the data is backed up. The remote computing device can also perform additional analysis on the data, such as analysis of pour data from multiple taps, data integration between the multiple taps, and the like. In some examples, the remote computing device has no additional processing capabilities.
The remote computing device is programmed to generate and transmit an acknowledgement message each time it successfully receives pour data from a beverage dispensing tap. In some examples, the remote computing device generates and transmits the acknowledgement message automatically each time it receives pour data and in other examples, the remote computing device generates an acknowledgement message only when the received pour data requests an acknowledgment message. The acknowledgement message includes data that indicates that the pour data was successfully received and could include other data, if desired. The remote computing device can also generate and transmit, either automatically or upon request by the monitor in the pour data, an error message if the remote computing device receives a message that appears to have pour data for a particular tap, but the message was not safely received for any reason.
The wireless transceiver 508 can continuously await the acknowledgement from the remote computing device. For this example system, the processing circuitry 506 in the monitor 500 locally stores the pour data if an acknowledgment is not received within a particular time period. The time period can be the usual time period that the system is expected to take for the pour data to be successfully transmitted to the remote computing device. If the acknowledgement is not received within the expected time period, the processing circuitry 506 could automatically generate an instruction for the wireless transceiver to re-send the pour data to the remote computing device and again await an acknowledgement in return. This process of repeatedly trying to send the pour data and awaiting an acknowledgement in response can be performed any multiple of times.
In some examples, the processing circuitry 506 is programmed to instruct the wireless receiver 508 to make two or three attempts to send the pour data and receive an acknowledgment in response. If no acknowledgment is received in the set number of attempts, in this case two or three attempts, then the processing circuitry 506 stores the pour data 524 locally in memory 522 in the monitor 500. In some examples, the processing circuitry 500 waits for a predetermined period of time, maybe several minutes or any desired amount of time, and again tries to successfully transmit the pour data 524 to the remote computing device. The pour data 524 stored in the memory 522 of the monitor 500 can be later accessible for analysis. Oftentimes, unsuccessful pour data transmission—those that do not receive an acknowledgment in return from the remote computing device—are caused by system or transmission errors. By saving the pour data 524 locally in the memory of the tap, it is preserved and can later be retrieved after the system is repaired.
The processing circuitry 506 in the beverage dispensing tap monitors 500 can include any desired amount and type of data analysis, compilation, and processing modules. For example, the beverage dispensing tap monitor 500 shown in
The processing circuitry 506 also can include a report generator 520 that can compile, organize, and output any desired report on any data gathered, stored, or analyzed by the monitor 500. As discussed above, some example reports include variance reports that compare the data generated by a point-of-sale server and the data generated by the monitors about the actual output of beverages. Any additional analyses of this data can be included in the reports.
If the tap is a recognized tap, then the reader calculates the size of the beverage that is poured based on the known brand of the beverage 706. The known brand is associated with a particular tap and is associated with the pre-programmed calibration data, as discussed above. The calibrated pour data is then stored in the reader's memory 708 and the product look-up unit or PLU for the dispensed beverage with the calibrated pour data is sent to the point-of-sale user station that received the patron transaction 710. The reader awaits an acknowledgement from the point-of-sale user station. If the acknowledgement is not received, then the calibrated pour data and PLU is saved to the reader memory and the reader attempts transmission of this data to the point-of-sale user station at a later time 714. If the reader receives an acknowledgment that the calibrated pour data and PLU are received by the point-of-sale user station, then the calibrated pour data and PLU are removed from the reader memory 716. The reader memory is also checked for any missed calibrated data and PLUs related to stored pours that were not transmitted properly 718.
The disclosure set forth above may encompass multiple distinct examples with independent utility. Although each of these has been disclosed in its preferred form(s), the specific embodiments thereof as disclosed and illustrated herein are not to be considered in a limiting sense, because numerous variations are possible. To the extent that section headings are used within this disclosure, such headings are for organizational purposes only. The subject matter of the disclosure includes all novel and nonobvious combinations and subcombinations of the various elements, features, functions, and/or properties disclosed herein. The following claims particularly point out certain combinations and subcombinations regarded as novel and nonobvious. Other combinations and subcombinations of features, functions, elements, and/or properties may be claimed in applications claiming priority from this or a related application. Such claims, whether broader, narrower, equal, or different in scope to the original claims, also are regarded as included within the subject matter of the present disclosure.
This application is a continuation of U.S. patent application Ser. No. 15/465,464, now U.S. Pat. No. 10,315,906, which claims benefit under 35 U.S.C. § 119(e) of the priority of U.S. Provisional Patent Application Ser. No. 62/311,301, filed Mar. 21, 2016, the entireties of which are hereby incorporated by reference for all purposes.
Number | Date | Country | |
---|---|---|---|
62311301 | Mar 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15465464 | Mar 2017 | US |
Child | 16436724 | US |