WO2020176261A1

WO2020176261A1 - Dispenser system with receptacle lockout feature and data transfer device

Info

Publication number: WO2020176261A1
Application number: PCT/US2020/017904
Authority: WO
Inventors: Christopher Dyer; Matthew S. Hayas
Original assignee: Delaware Capital Formation, Inc.
Priority date: 2019-02-26
Filing date: 2020-02-12
Publication date: 2020-09-03

Abstract

Systems, methods, and computer program products for dispensing chemical solutions. A dispenser (24) includes a controller (36) in communication with a source valve (30), a selector valve (32), one or more source readers (48), and a receptacle reader (68). The controller (36) retrieves data associated with a source container (40) by interrogating a source tag (52) using the source reader (48). In response to receiving an activation signal, the controller (36) retrieves data associated with a receptacle (47) from a receptacle tag (72) using the receptacle reader (68). The controller (36) then determines whether to dispense a solution (62) including a product (38) from the source container (40) into the receptacle (47) based at least in part on the data received from one or more of the source and receptacle tags (52), (72). Operational data related to the dispense operation may be stored by the controller (36) in a data transfer device (59) for downloading by a mobile device (14) and eventual storage in a central database (20).

Description

DISPENSER SYSTEM WITH RECEPTACLE LOCKOUT FEATURE AND DATA TRANSFER DEVICE

Technical Field

[0001] This invention relates to systems for selectively dispensing chemical solutions, and more particularly, to dispensing systems which read data from containers and use the data to control dispense operations.

Background

[0002] Industrial and commercial firms frequently require the use of chemical solutions, such as cleaning solutions. For example, a janitorial staff of a commercial building will often use various cleaning solutions to clean and disinfect floors, windows, and other surfaces. These solutions may be dispensed to users by a solution dispensing system that mixes a concentrated chemical solution with water. To allow users access to a variety of chemical solutions, the dispensing system may include a plurality of source stations. Each source station is configured to accept a container of concentrated chemical solution that is fluidically coupled to a dispensing station by a selector valve. The selector valve may thereby allow a user to select a desired container of chemical concentrate to be mixed with water and dispensed as a solution into a receptacle, such as a mop bucket or spray bottle. In this way, the user may obtain a solution containing soap, industrial cleaners, degreasers, sanitizers or other chemicals specifically intended for a particular use. Dispensing systems may thereby provide a convenient way for users to fill a receptacle with a diluted chemical solution.

[0003] Typically, the above type of dispensers are relatively simple mechanical affairs that do not monitor chemical usage. This can result in chemicals running out without the user noticing, in which case the dispenser may dispense water rather than the expected chemical solution. Incorrect solutions may also be dispensed due to operator error, such as selecting the wrong chemical or loading the wrong chemical into the dispenser.

[0004] Thus, there is a need for improved systems, methods, and computer program products for dispensing systems that monitor the dispensing of chemicals therefrom.

Summary

[0005] In an embodiment of the invention, a dispenser is provided. The dispenser includes a source station configured to receive a source container, a first reader located proximate to the source station, and a controller in communication with the first reader and comprising one or more processors and a first memory storing program code. The program code, when executed by the one or more processors, causes the controller to, in response to detecting a first event indicating the source station has been accessed, cause the first reader to transmit a first interrogation signal, receive first data associated with a source container located in the source station from the first reader, store the first data in the first memory, and determine whether to dispense a solution including a product in the source container based at least in part on the first data stored in the first memory.

[0006] In an aspect of the invention, the dispenser further includes a dispensing station and a second reader in communication with the controller and located proximate to the dispensing station, and the program code further causes the controller to, in response to detecting a second event, cause the second reader to transmit a second interrogation signal, receive second data associated with a receptacle from the second reader, and determine whether to dispense the solution including the product in the source container based at least in part on the second data.

[0007] In another aspect of the invention, the second event is reception of a second signal indicating a user is requesting a dispense operation.

[0008] In another aspect of the invention, the dispenser further includes a door that controls access to the source station and a sensor configured to provide a signal to the controller indicative of whether the door is open or closed, and detecting the first event indicating the source station has been accessed includes one or more of detecting that the door has been opened, detecting the door has been closed, or detecting a combination of the door being opened and the door being closed.

[0009] In another aspect of the invention, the dispenser further includes a dispense switch, and the program code further causes the controller to, after storing the first data in the first memory, enter a sleep mode, and in response to detecting activation of the dispense switch, exit the sleep mode, wherein whether to dispense the solution including the product in the source container is determined based at least in part on the first data in the first memory.

[0010] In another aspect of the invention, the dispenser further includes a data transfer device having a second memory, and the program code further causes the controller to store the first data in the second memory.

[0011] In another aspect of the invention, the program code causes the controller to store the first data in the second memory by transmitting a third interrogation signal carrying the first data to the data transfer device.

[0012] In another aspect of the invention, the program code further causes the controller to begin a dispense operation that dispenses the solution including the product in the source container by opening a source valve, and store second data in the second memory indicative of an amount of the product dispensed from the source container during the dispense operation.

[0013] In another aspect of the invention, the data transfer device is configured to receive a fourth interrogation signal from a mobile device, and in response to receiving the fourth interrogation signal, transmit the first data to the mobile device.

[0014] In another aspect of the invention, the program code further causes the controller to enter a sleep mode after storing the first data in the second memory, and the data transfer device transmits the first data to the mobile device without the controller exiting the sleep mode.

[0015] In another embodiment of the invention, a method of operating the dispenser is provided. The method includes, in response to detecting the first event indicating the source station has been accessed, transmitting the first interrogation signal, receiving the first data associated with the source container located in the source station, storing the first data in the first memory, and determining whether to dispense the solution including the product in the source container based at least in part on the first data stored in the first memory.

[0016] In an aspect of the invention, the method further includes, in response to detecting the second event, causing the second reader to transmit the second interrogation signal, receiving the second data associated with the receptacle from the second reader, and determining whether to dispense the solution including the product in the source container based at least in part on the second data.

[0017] In another aspect of the invention, the second event is reception of the second signal indicating the user is requesting the dispense operation.

[0018] In another aspect of the invention, detecting the first event indicating the source station has been accessed includes one or more of detecting that the door has been opened, detecting the door has been closed, or detecting a combination of the door being opened and the door being closed.

[0019] In another aspect of the invention, the method further includes, after storing the first data in the first memory, entering the sleep mode, and in response to detecting activation of the dispense switch, exiting the sleep mode, wherein whether to dispense the solution including the product in the source container is determined based at least in part on the first data in the first memory.

[0020] In another aspect of the invention, the method further includes storing the first data in the second memory. [0021] In another aspect of the invention the first data is stored in the second memory by transmitting the third interrogation signal carrying the first data to the data transfer device.

[0022] In another aspect of the invention, the method further includes beginning the dispense operation that dispenses the solution including the product in the source container by opening a source valve, and storing the second data in the second memory indicative of the amount of the product dispensed from the source container during the dispense operation.

[0023] In another aspect of the invention, the method further includes receiving the fourth interrogation signal from the mobile device at the data transfer device, and in response to receiving the fourth interrogation signal, transmitting the first data to the mobile device from the data transfer device.

[0024] In another embodiment of the invention, a computer program product is provided. The computer program product includes a non-transitory computer-readable storage medium and program code stored on the non-transitory computer-readable storage medium that, when executed by one or more processors, causes the one or more processors to, in response to detecting the first event indicating the source station has been accessed, cause the reader to transmit the first interrogation signal, receive the first data associated with the source container located in the source station received by the reader in response to the interrogation signal, store the first data in the first memory, and determine whether to dispense the solution including the product in the source container based at least in part on the first data stored in the first memory.

[0025] The above summary presents a simplified overview of some embodiments of the invention to provide a basic understanding of certain aspects of the invention discussed herein. The summary is not intended to provide an extensive overview of the invention, nor is it intended to identify any key or critical elements, or delineate the scope of the invention.

The sole purpose of the summary is merely to present some concepts in a simplified form as an introduction to the detailed description presented below.

Brief Description of the Drawings

[0026] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments of the invention and, together with the general description of the invention given above, and the detailed description of the embodiments given below, serve to explain the embodiments of the invention. [0027] FIG. 1 is a diagrammatic view of an exemplary operating environment including a dispenser, a mobile device, a network, a user system, a server, and a database in accordance with an embodiment of the invention.

[0028] FIG. 2A is a diagrammatic view of the dispenser of FIG. 1 including a plurality of source containers each containing a concentrated chemical solution with a source tag, a selector valve, a controller, and a data transfer device.

[0029] FIG. 2B is a diagrammatic view of the dispenser of FIG. 1 including the plurality of source containers each containing the concentrated chemical solution with the source tag, selector valve, controller, and data transfer device for another embodiment of the invention.

[0030] FIG. 2C is a perspective view of a source valve that may be used in an

embodiment of the dispenser of FIG. 1.

[0031] FIG. 3 is a perspective view of an embodiment of the invention in accordance with the dispensers of FIGS. 2A and 2B including a plurality of source stations and a dispensing station.

[0032] FIG. 4 is a perspective view of a source container including a fitting having a reader for reading the source tags of FIGS. 2 A and 2B.

[0033] FIG. 5 is a cross-sectional view of an exemplary station and source container that may be used with the dispensers of FIGS. 2A and 2B.

[0034] FIG. 6 is a flow-chart of a process for dispensing a diluted chemical solution using the dispenser of any of FIGS. 1, 2 A and 2B.

[0035] FIG. 7 is a flow-chart of a process for storing operational data in a database that may be implemented by one or more of the components of the operating environment of FIG. 1.

[0036] FIG. 8 is a diagrammatic view of a computer that may be used to implement one or more of the components or processes shown in FIGS. 1-7.

Detailed Description

[0037] Embodiments of the invention include a dispenser having one or more readers configured to read data from one or more containers. The dispenser may store the data in memory and determine whether to dispense a solution based at least in part on the data stored in the memory.

[0038] Embodiments of the invention may also include a data collection system having a plurality of dispensers each including a data transfer device. [0039] One type of dispenser that may be used in accordance with an embodiment of the invention includes a manually operated switch that activates a source valve. When activated, the source valve provides water to a mixing device, such as a venturi-based mixing device, or “eductor”. In response to the flow of water, the mixing device draws concentrated chemical solution from a source container and mixes the concentrated chemical solution with the water to produce a diluted chemical solution. This type of dispenser may include a controller and sensors that measure one or more operational parameters of the dispenser.

[0040] The controller may transmit the measurements to the data transfer device. The data transfer device may store the measurements as operational data in a non-volatile memory for later retrieval, e.g., by a mobile device. Data retrieved by the mobile device may then be uploaded to a database that manages data from the plurality of dispensers or dispending locations. The operational data stored in the database may then be accessed by other users or systems having authorization to do so.

[0041] FIG. 1 depicts an exemplary operating environment 10 in accordance with an embodiment of the invention. The operating environment 10 may include one or more dispensing locations 12, mobile devices 14, a user system 16, a server 18, a database 20, and a network 22. Each dispending location 12 may include one or more dispensers 24 each in communication with one or more of the mobile devices 14, the network 22, or a Local Access Network (LAN) 26.

[0042] Exemplary mobile devices 14 may include smart phones, tablet computers, or any other portable computing device, and may communicate with the network 22, dispenser 24, or LAN 26 using a suitable communication protocol. Exemplary communication protocols may include, but are not limited to, Wi-Fi®, Bluetooth®, Radio Frequency Identification (RFID), Near-Field Communication (NFC), Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), cdmaOne, CDMA2000, Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), and Integrated Digital Enhanced Network (iDEN).

[0043] The server 18 may comprise a computer system or cloud-based service that includes at least one running instance of an application which provides functionality for other applications or“clients”. Client applications may be hosted, for example, by one or more of the mobile devices 14, user system 16, or dispensers 24. Exemplary services that may be provided by the server 18 include an application server, a file server, a web server, a database server (e.g., that manages database 20), or any other suitable server. Operational data collected from the dispensers 24 by the mobile devices 14 may be uploaded to the server 18 and stored in the database 20 where the data can be accessed by other mobile devices 14 or the user system 16, e.g., using a web-browser or other client application.

[0044] To access operational data in the database 20, a user may be required to provide authentication information (e.g., user ID and password) to the server 18. Based on the identity of the user, the server 18 may control which data the user is allowed to access. This may allow data received from a plurality of facilities each having a different set of authorized users to be accessible to just those users, and to only provide data which the user requesting access is authorized to see. By way of example, the server may be configured to provide a user with data specific to their dispensing locations 12, data relating to certain products 38 or dispensing tips, data relating to selected types of dispensers 24, and usage data for each dispenser 24 at one of their dispensing locations 12.

[0045] FIG. 2A depicts an exemplary dispenser 24 including a source valve 30 that selectively couples a selector valve 32 to a water source 34 in response to signals from a controller 36 or activation by a user. The selector valve 32 may include an eductor or other mixing device that draws a concentrated chemical solution, or“product” 38 from a selected source container 40 in response to water flowing through the mixing device. The selector valve 32 may include a diluent port 42 configured to receive water from the water source 34 when the source valve 30 is activated, and plurality of chemical ports 44. Each chemical port 44 may be fluidically coupled to a respective source container 40 by a tube 45 having a distal end terminated by a connector 46. Each chemical port 44 may be selectively fluidically coupled to the mixing device of selector valve 32 based on the position of the selector valve 32 so that only product 38 from the selected source container 40 is fluidically coupled to the mixing device. Power may be supplied to the dispenser 24 using any suitable power source, such as a battery, photovoltaic cell, fuel cell, or the power grid.

[0046] The position of selector valve 32 may be controlled by the controller 36 (e.g., using a stepper motor), or through manual activation by a user. The selector valve 32 may include a position sensor that provides an indication of the position of the selector valve 32 to the controller 36. To this end, the selector valve 32 may include magnets (not shown) that interact with one or more Hall effect sensors in communication with the controller 36, or some other suitable switches or contacts. The selector valve 32 may thereby be configured to provide one or more signals to the controller 36 indicative of the position of the selector valve 32. The controller 36 may, in turn, determine the position of the selector valve 32 based on the received signal(s), with the selector valve position further indicating which chemical is selected. [0047] For embodiments of the invention using a stepper motor, the controller 36 may determine the position of the selector valve 32 based on an amount of rotation provided by the stepper motor. The selector valve 32 may include any suitable valve known in the art, such as those disclosed in U.S. Patent No. 6,655,401 entitled MULTIPLE CHEMICAL PRODUCT EDUCATIVE DISPENSER, to Sand et al., and U.S. Patent No. 5,653,261 entitled SELECTOR VALVE, to Dalhart et al., the disclosures of which are incorporated by reference herein in their entireties.

[0048] The positioning the selector valve 32 in a selected position may operatively couple one of the chemical ports 44 to its respective source container 40. The selector valve 32 may thereby allow the user to select which product 38 will be drawn into the water for dilution and discharge into a receiving container, or receptacle 47. The controller 36 may determine the flow rate of water through the selector valve 32 based on a known flow rate for the selector valve 32, a known flow-rate verses water pressure for the selector valve 32, or based on a signal received from a water flow sensor (not shown). A flow sensor may include a flow switch or a flow meter. A flow switch detects the presence of a flow when that flow exceeds a predetermined set point, and outputs a binary signal (e.g., TRUE or FALSE) indicating that the flow is either above or below the set point. In contrast, a flow meter detects a flow rate (i.e., a volume per unit time) and outputs a signal indicative of a level of the flow rate. For embodiments in which the controller 36 uses pressure or a measured flow-rate of the water, the dispenser 24 may include a water flow sensor (not shown) located between the water source 34 and diluent port 42 that detects the pressure or flow-rate of water provided by the water source 34.

[0049] In an alternative embodiment of the invention, the dispenser 24 may include sensors comprising flow switches that detect one or more of a flow of water between the source valve 30 and the diluent port 42 of selector valve 32, or a flow of product 38 between the selected source container 40 and the respective chemical port 44 of selector valve 32. The flow switches may provide one output (e.g., a low electrical impedance) in response to the flow of fluid through the flow switch exceeding a predetermined minimum flow rate, and another output (e.g., a high electrical impedance) when the flow of fluid through the flow switch is below the predetermined minimum flow rate. The predetermined minimum flow rate for a flow switch between the source valve 30 and selector valve 32 may be a flow rate which enables the product 38 to be drawn accurately and consistently into the mixing device of selector valve 32. The dispenser 24 may also include an in-line pressure regulator that regulates the water pressure provided to the selector valve 32 to a relatively consistent level when the source valve 30 is open. The use of pressure regulators in dispensing systems is described in more detail in U.S. Pat. No. 8,813,789, entitled“DISPENSER WITH INLINE PRESSURE REGULATOR”, issued on August 26, 2014, the disclosure of which is incorporated by reference herein in its entirety.

[0050] Each connector 46 may include a container reader 48 that transmits an

interrogation signal 50 in response to activation by the controller 36. Interrogation signals 50 may include a radio frequency, infrared optical, or other electromagnetic signal configured to provoke a response from or otherwise read data stored in a device, and may be transmitted in response to receiving a signal from the controller 36. The controller 36 may cause the container reader 48 to transmit the interrogation signal 50 in response to detecting an event indicating that the respective source container 40 has been accessed. This type of event may include, for example, receiving a signal from a sensor 51 indicting a door to a compartment holding the source container 40 has been opened, closed, opened then closed, that the weight of the source container 40 has changed, or that connector 46 has been removed from the source container 40.

[0051] In response to receiving the interrogation signal 50, a machine-readable source tag 52 integrated into or otherwise attached to the source container 40 may transmit a response signal 54 carrying data stored in the source tag 52. The data stored in the source tag 52 may include, for example, a Universally Unique Identifier (UUID) that uniquely identifies the source container 40, information relating to the product 38 (e.g., manufacturer, type of chemical, brand name, lot or batch number, date of manufacture, recommended dilution ratio, or hazmat information), the identity of the distributer, or any other information related to the product 38 or source container 40.

[0052] The source tag 52 may be an RFID tag, NFC tag, bar code, Quick Read (QR) code, or other type of tag that stores data which can be read by a machine. The container reader 48 may communicate the data encoded in the response signal 54 to the controller 36 over a wired connection (e.g., using a Universal Serial Bus (USB)) or wirelessly (e.g., using Bluetooth, NFC, or RFID signals).

[0053] The controller 36 may also be operatively coupled to a display 56, a dispense switch 58, a data transfer device 59, and, for embodiments in which the position of the selector valve 32 is controlled by the controller 36, a chemical selection switch 60.

[0054] The display 56 may include one or more Light Emitting Diodes (LEDs) or other visual indicators (e.g., a Liquid Crystal Display (LCD) screen) that indicate a status of the dispenser 24. Exemplary status information may include which chemical port 44 is selected by the selector valve 32, whether a dispense operation is active, whether the product 38 in the source container 40 is compatible with the connector 46 to which it is coupled, or whether a source container 40 is low on or has run out of product 38. In response to signals received from the controller 36, the display 56 may indicate one or more of a successful dispense operation (e.g., by outputting a green light), that an error was detected (e.g., by outputting a red light), or that the dispenser 24 requires maintenance (e.g., by outputting a flashing red light).

[0055] The dispense switch 58 may be configured to provide a signal to the controller 36 indicating when a user wants to dispense a chemical solution. In response to dispense switch 58 being activated, the controller 36 may open the source valve 30, thereby allowing water to enter the selector valve 32. The water entering the selector valve 32 may cause the mixing device to draw the respective product 38 through the selected chemical port 44 and into the selector valve 32. The product 38 may then mix with the water to produce a diluted chemical solution 62 that is discharged from a dispensing nozzle 64 of the dispenser 24 and into the receptacle 47. In an alternative embodiment of the invention, the dispenser 24 may have more than one dispense switch 58, e.g. one dispense switch 58 that activates a high flow rate or high concentration dispense operation and another dispense switch 58 that activates a low flow rate or low concentration dispense operation. The controller 36 may be configured to place the source valve 30 in an off condition in response to a loss of power, such as when one or more batteries that provide power to the dispenser 24 are removed.

[0056] The data transfer device 59 may include a transponder 65 or other processing circuitry in communication with a memory 66. The data transfer device 59 may be a stand alone device that is located proximate to the dispenser 24, e.g., attached to the dispenser 24 using adhesive or a bracket, or may be integrated into the dispenser 24. The data transfer device 59 may be a passive device that is powered solely by an external activation signal (e.g., an interrogation signal) received by the transponder 65, or may be an active device that also receives power from a persistent power source (e.g., a battery or photovoltaic cell). Active data transfer devices may be able to communicate over a greater range than passive devices, and may be configured to periodically transmit a signal that includes at least a portion of the data stored in the memory autonomously, e.g., a beacon signal including a UUID. The data transfer device 59 may be read-only (the data may be read but not changed), read/write (the data can be read and changed), or a combination in which a portion of the data is read only (e.g., the UUID), while another portion may be changed. Exemplary data transfer devices include NFC devices, RFID devices, devices that transmit using one or more Bluetooth standards, and the like.

[0057] Data stored in the memory 66 of data transfer device 59 may include a UUID that can be used to uniquely identify the dispenser 24. In response to receiving the interrogation signal, the transponder 65 may transmit a response signal that conveys the UUID as well as all or a portion of any other data stored in memory 66. The interrogation signal may be a radio frequency signal received from a mobile device 14 or the controller 36. The interrogation signal may also include data that can be stored in the memory 66 of data transfer device 59. In response to a user activating a data management application on the mobile device 14 or touching the mobile device 14 to the dispenser 24, the operational data stored in the memory 66 of data transfer device 59 may be downloaded to the mobile device 14. The mobile device 14 may also be configured to automatically start the data management application in response to pairing with the data transfer device 59, or in response to detecting a beacon signal transmitted by the data transfer device 59.

[0058] In operation, the controller 36 may transmit an interrogation signal to the data transfer device 59 that includes operational data. In response to receiving this interrogation signal, the data transfer device 59 may store the operational data in memory 66. The data transfer device 59 may then receive an interrogation signal from the mobile device 14, and transmit the stored operational data to the mobile device 14 in the response signal. In cases where the network 22 or LAN 26 is not available, the mobile device 14 may cache the data retrieved from the data transfer device 59 until a link to a network can be established. The mobile device 14 may transmit the data received from the data transfer device 59 (ether as it is received or from the cache) to one or more of the user system 16, server 18, or database 20 when a network is available.

[0059] The interrogation signal transmitted by the mobile device 14 may also write data to the memory 66 of data transfer device 59. For example, the mobile device 14 may download a location, a lookup table, a database update, a software or firmware update, or any other suitable data to the data transfer device 59. This downloaded data may be used by the data transfer device 59 itself, or forwarded to the controller 36. The mobile device 14 may also be used to perform system setup, e.g., by providing the location, types of products 38 that should be loaded into each source station, what products 38 should be used with what receptacle 47, and what the dilution ratio of each product 38 should be.

[0060] The dispenser 24 may also include a receptacle reader 68 in communication with the controller 36 and located proximate to the dispensing station where the receptacle 47 is to be positioned prior to filling. The controller 36 may cause the receptacle reader 68 to transmit an interrogation signal 70, either periodically or in response to an event, such as activation of the dispense switch 58. In response to receiving the interrogation signal 70, a receptacle tag 72 integrated into or otherwise attached to the receptacle 47 may transmit a response signal 74 carrying data stored in the receptacle tag 72. Data stored in the receptacle tag 72 may include data defining one or more characteristics of the receptacle (e.g., the volume or type of receptacle 47), a UUID uniquely identifying the receptacle 47, or any other suitable information. In response to receiving the response signal 74, the receptacle reader 68 may provide the received data to the controller 36 over a wired or a wireless connection as discussed above with respect to the container readers 48.

[0061] If the controller 36 recognizes the receptacle 47 based on the data received from the receptacle reader 68, the controller 36 may authorize dispensing of the diluted chemical solution 62. To this end, the controller 36 may cause the source valve 30 to open so that water is provided to the selector valve 32. If the controller 36 either does not recognize the response signal 74, or otherwise determines that the diluted chemical solution 62 should not be dispensed to the receptacle 47, the controller 36 may refrain from opening the source valve 30. In the event the controller 36 refrains from dispensing the diluted chemical solution, the controller 36 may also cause the display 56 to provide an indication that an error has occurred.

[0062] In an embodiment of the invention, when a mobile device 14 is proximate to the dispenser 24, the mobile device 14 may establish a connection, or“pair” with the data transfer device 59. A user of the mobile device 14 may then upload data to the data transfer device 59 that associates the data transfer device 59 with one or more of a physical location, updates a date and time in the controller 36, a product 38 to be dispensed by the chemical dispenser 24, or a type of dispenser tip installed in the mixing device of the dispenser 24. The mobile device 14 may determine an amount of each product 38 dispensed in each dispense operation based on operational data received from the data transfer device 59. For example, the amount of product 38 dispensed may be determined based on a duration of the dispense operation or an amount of time a flow switch between the selector valve 32 and the source container 40 indicates flow and a known flow rate for the mixing device. This known flow rate may be a published number for the dispenser tip used in a venturi-based mixing device, and may be associated with the UUID of the data transfer device 59 in a lookup table, for example. [0063] Referring now to FIG. 2B, in an alternative embodiment of the invention, the dispense switch 58 may be operatively coupled to the source valve 30 by a linkage 69. The linkage 69 may include a latching mechanism 71 that allows the linkage 69 to operate the source valve 30 when the latching mechanism 71 is in an enabled state, and the prevents the linkage 69 from operating the source valve 30 when the latching mechanism 71 in a disabled state. The latching mechanism 71 may be in communication with the controller 36 so that the controller 36 can selectively place the latching mechanism 71 in either the enabled state or the disabled state. The latching mechanism 71 may include, for example, an actuator (e.g., a motor or solenoid) in communication with the controller 36. The actuator may be configured to move a cam or other latching device between one position that places the latching mechanism 71 in the disabled state which restricts movement of the linkage 69, and another position that places the latching mechanism 71 in the enabled state which allows movement of the linkage 69. Thus, when the latching mechanism 71 is in the enabled state, activation of the 58 dispense switch causes the source valve 30 to open, and when the latching mechanism 71 is in the disabled state, activation of the dispense switch 58 does not cause the source valve 30 to open.

[0064] FIG. 2C depicts an exemplary source valve 30 operatively coupled to an exemplary selector valve 32. The source valve 30 includes a plunger 73 that is coupled to a valve body by a spring 75. The plunger 73 may include a magnet (not shown) that, when in sufficient proximity to a valve body 77, urges a diaphragm (not shown) enclosed by the valve body 77 into an open position, thereby opening the source valve 30. The spring 75 may be configured to urge the plunger 73 away from the valve body 77 so that absent any external forces on the plunger 73, the plunger 73 is maintained in a position away from the valve body 77. Thus, the source valve 30 may be maintained in a closed state by the spring 75 when the source valve 30 is not being activated.

[0065] FIG. 3 depicts an exemplary dispenser 24 shown with the receptacle 47 including the receptacle tag 72. The dispenser 24 includes a cabinet 76 defining a plurality of source stations 78 and a dispensing station 79, and a panel 80. Each source station 78 may be configured to accept one of the source containers 40 and include a door 82 for securing the source containers 40 in their respective source station 78. Each source station 78 may include the sensor 51 in the form of a switch or other device that provides a signal to the controller 36 indicating whether the respective door 82 is open or closed. The panel 80 may include the chemical selection switch 60 and a plurality of LEDs 84 comprising at least a portion of the display 56. Each door 82 may include a window or opening 90 that allows users to see into the source stations 78 while the doors 82 are closed. A housing including a removable cover 94 may provide access to selected components of the dispenser 24.

[0066] FIG. 4 depicts a connector 46 in accordance with an embodiment of the invention. The connector 46 includes a fitting 100 having a top surface 102, a bottom surface 104, and a cavity 106. The cavity 106 includes an opening on the bottom surface 104 configured to receive a cylindrical post 108 that projects outward from a top portion of the source container 40. The container reader 48 may be located within or proximate to the cavity 106, and the source tag 52 may be located within or proximate to the post 108 so that when the fitting 100 is placed on the source container 40, the container reader 48 is positioned near the source tag 52.

[0067] The distal end of the tube 45 may be operably coupled to the fitting 100 through an opening 110 in the top surface 102 thereof. The opening 110 may be configured to connect the distal end of the tube 45 to a male coupling 112 that projects outward from the bottom surface 104 of the fitting 100. The source container 40 may include a female coupling 114 configured to receive the male coupling 112 and that provides a fluid-tight seal. A cable 116 including one or more conductive elements (e.g., wires) operably coupling the container reader 48 to the controller 36 may be coupled to the tube 45 by one or more wire ties 118 to facilitate connection and removal of the fitting 100 to and from the source container 40.

[0068] FIG. 5 depicts a source station 120 that includes a housing 122 and a door 124 which provides access to a compartment 126. The compartment 126 may be configured to receive a source container 128 comprising a flexible container, such as a bag, pouch, or collapsible box. The source container 128 may include a port 130 into which a thin hollow tube having a sharpened tip, or“spike” 132 is inserted. The port 130 may include a membrane (not shown) that is pierced by the spike 132 when the spike 132 is inserted into the port 130, thereby establishing a path for fluid between the tube 45 and the interior of the source container 128.

[0069] The spike 132 may project outward from a coupler 134 including a ribbed nipple 136 configured to receive the distal end of tube 45. The container reader 48 may be located in the coupler 134, and the source tag 52 may be located in or on the source container 128 proximate to the port 130 so that the container reader 48 and source tag 52 are in close proximity after the spike 132 has been inserted into the port 130. A cable 138 including one or more conductive elements (e.g., wires) may emerge from the coupler 134 proximate to the ribbed nipple 136 and operably couple the controller 36 to the container reader 48. [0070] FIG. 6 depicts a flow-chart illustrating a process 140 that may be implemented by one or more of the controller 36 of dispenser 24 or any other suitable computing device of operating environment 10. In block 142, the process 140 may detect activation of the dispense switch 58. In cases where activation of the dispense switch 58 is detected by the controller 36, the process 140 may cause the controller 36 to wake up from a power conserving sleep mode. In response to detecting activation of the dispense switch 58, the process 140 may proceed to block 144 and interrogate one or more tags 52 of source containers 40 (e.g., the source tag 52 of the source container 40 currently selected by the selector valve 32) or the receptacle tag 72. Interrogating the tags 52, 72 may include causing the respective readers 48, 68 to transmit interrogation signals 50, 70, and receiving data contained in the corresponding response signals 54, 74.

[0071] In an embodiment of the invention, the process 140 may only interrogate the source tag 52 in response receiving a signal from the sensor 51 indicating the source container 40 may have been changed or otherwise altered. In this case, the data received from the source tag 52 may be stored in a memory (e.g., a memory of the controller 36 or the memory 66 of data transfer device 59), thereby eliminating the need to interrogate the source tag 52 each time the data stored in the source tag 52 is used by the process 140. In this embodiment of the invention, receiving a signal from the sensor 51 may also cause the controller 36 to wake up from the power conserving sleep mode.

[0072] In block 146, the process 140 may validate the receptacle 47. Validation may include determining if the receptacle 47 is compatible with the product 38 in the selected source container 40. This determination may include, for example, determining the type of product 38 in the selected source container 40 and the type of receptacle 47 in the dispensing station 79. The type of product 38 in the selected source container 40 may be determined, for example, based on a UUID embedded in the response signal 54, e.g., using a lookup table. Similarly, the type of receptacle 47 may also be determined based on a UUID embedded in the response signal 74 transmitted by receptacle tag 72, e.g., using the lookup table.

Compatibility between products 38 and receptacles 47 may also be determined by comparing respective UUIDs using a compatibility table, and the UUIDs may be embedded in a read only memory of the respective tags 52, 72 at the time of manufacture. The process 140 may also compare the UUID to a list or range of UUIDs stored in local memory (e.g., as a“white list” or“black list”) or embed the UUID in a query transmitted to the server 18.

[0073] In an embodiment of the invention, the process 140 may read the source tag 52 each time the door 82 of source station 78 is closed to check if the source container 40 has been changed. If the source container 40 has been changed (e.g., a different UUID is received from the source tag 52), the process 140 may query a database (e.g., database 20 or a manufacturer database) to determine the characteristics of the product 38 in the source container 40 based on the UUID. The product information associated with the source station 78 in question may then be updated in the dispenser 24 for use in determining when and how to dispense dilute solutions including the product 38.

[0074] If validation of the receptacle 47 is unsuccessful (“NO” branch of decision block 146), the process 140 may proceed to block 148. Validation may be unsuccessful, for example, if the product 38 is determined to be incompatible with the receptacle 47. The product 38 may be incompatible with the receptacle 47 if, for example, the receptacle 47 is intended for a different type of solution, e.g., window cleaner verses floor cleaner. Validation may also be unsuccessful if the process 140 fails to read the receptacle tag 72 (e.g., due to use of a receptacle 47 lacking a receptacle tag 72 or failure to place the receptacle 47 in the dispensing station 79), or the existence of any other condition under which the dispenser 24 is not authorized to dispense a diluted chemical solution 62 containing the selected product 38 into the receptacle 47 (e.g., the product 38 was not provided by an authorized supplier). In any case, in block 148, the process 140 may perform one or more of locking out the source container 40 (e.g., by disabling the linkage 69), causing the display to indicate the receptacle 47 is incompatible, and logging the error in memory 66 of data transfer device 59 before terminating.

[0075] If validation of the receptacle 47 is successful (“YES” branch of decision block 146), the process 140 may proceed to block 150. In block 150, the process 140 may validate the selected source container 40. This validation may include, for example, determining an amount of product 38 that has been dispensed from the source container 40 and comparing this amount to a known volume of the source container 40. If the volume dispensed is within a predetermined threshold of, or exceeds, the volume of the source container 40, the process 140 may determine that the source container 40 is either about to run out of product 38, or that additional solution has been added to the source container 40. In either case, this may result in the source container 40 failing validation.

[0076] If validation of the selected source container 40 is unsuccessful (“NO” branch of decision block 150), the process 140 may proceed to block 148 and display /log an error indicating the validation error. The display and logging of the error may be performed in a manner similar to that described above with respect to the failure to validate the receptacle 47. If validation of the selected source container 40 is successful (“YES” branch of decision block 150), the process 140 may proceed to block 152.

[0077] In block 152, the process 140 may open the source valve 30 (or enable the linkage 69 so that the dispense switch 58 activates the source valve 30) so that water is provided to the selector valve 32. The controller 36 may also start a dispense timer. The dispense timer may keep track of the amount of time the dispenser 24 is dispensing the diluted chemical solution 62. The dispense timer may also be used to determine if the dispenser 24 is operating properly, e.g., by comparing measured times to expected times for various parameters, such as the flow of water, the flow of product 38, and dispense times. Timing information may also be used to determine the amount of water, product 38, or diluted chemical solution 62 that has been consumed or dispensed during the dispense operation, or whether an error has occured.

[0078] In block 154, the process 140 may determine if the dispenser timer has exceeded a maximum activation time. The maximum activation time may be based on the volume of the receptacle 47 (which may be determine based on the UUID received from the receptacle tag 72) and a known flow rate of the source valve 30 or selector valve 32 in order to prevent overfilling of the receptacle 47.

[0079] If the maximum dispense time is exceeded (“YES” branch of decision block 154), the process 140 may proceed to block 156, close the source valve 30, and log the dispense time as indicated by the dispense timer before terminating. If the maximum dispense time has not been exceeded (“NO” branch of decision block 154), the process may proceed to block 158 and determine if the dispense switch 58 has been deactivated. If the dispense switch 58 has not been deactivated (“NO” branch of decision block 158), the process 140 may return to block 154 and continue dispensing the diluted chemical solution 62. If the dispense switch has been deactivated (“YES” branch of decision block 158), the process 140 may proceed to block 156, shut off the source valve 30, and log the activation time as described above.

[0080] In an embodiment of the invention, in response to validating the selected source container 40 and receptacle 47, the process 140 may open the selector valve 32 for a predetermined amount of time based on the flow rate through the source valve 30 and selector valve 32, and the volume of the receptacle 47. In this embodiment, the dispenser may dispense an appropriate amount of diluted chemical solution 62 in response to the user momentarily activating the dispense switch 58. In cases where the process 140 determines the dispenser 24 is not authorized to dispense the product 38, the process 140 may cause the display 56 to indicate an error has occurred, e.g., by causing an LED 84 associated with that source station 78 to emit a red light.

[0081] In an embodiment of the invention that includes one or more water or product flow sensors, in response to the user activating the dispense switch 58, the controller 36 may wake up from a sleep mode and start a timer. After a short delay sufficient to allow the flow of water through the mixing device of selector valve 32 to increase to a sufficient level (e.g., about one second), the controller 36 may receive a signal from the water flow sensor indicating flow from the water source 34 to the selector valve 32. After a further delay, the selector valve 32 may begin to draw product 38 from the selected source container 40, activating the product flow sensor. When the dispense switch 58 is released, the controller 36 may determine a duration of the dispense operation and store this data in the memory 66 of data transfer device 59. The controller 36 may then light one or more of the LEDs 84 to provide the user with feedback regarding whether the dispense operation was successful. The controller 36 may also use the sensor data to determine various operational parameters and store these operational parameters in the memory 66 of data transfer device 59.

[0082] FIG. 7 depicts a flow-chart illustrating a process 160 that may be implemented by one or more of the mobile device 14 or any other suitable computing device of operating environment 10. In block 162, the process 160 may transmit an interrogation signal configured to illicit a response from the data transfer device 59. If a response is not received (“NO” branch of decision block 164), the process 160 may either retransmit the interrogation signal or terminate. If a response is received, the process 160 may proceed to block 166.

[0083] In block 166, the process 160 may use one or more UUTDs received in the response to retrieve data associated therewith. The one or more UUTDs may include, for example, a UUID associated with the dispenser 24 or UUIDs received from something with which the dispenser communicates 24, such as a source container 40 or the data transfer device 59. The retrieval process may include querying a database (e.g., in the memory of the mobile device 14, the database 20, or another suitable database) to find data associated with the UUID. This data may include a type or serial number of the dispenser 24 to which the data transfer device 59 responding to the interrogation signal is attached, the latest software version for the controller 36, if the dispenser 24 is due for maintenance, or any other suitable information. In an embodiment of the invention, the process 160 may use at least a portion of the received data to auto-populate a display of the mobile device 14 with information regarding the dispenser 24, such as what types of products 38 are being dispensed by the dispenser 24. [0084] In block 168, the process 160 may determine if the software in the data transfer device 59 or any component in communication with the data transfer device 59 is up to date. This determination may be made, for example, by comparing a software version number received in the response signal to a software version number associated with the UUID. If the software not up to date (“NO” branch of decision block 168), the process 160 may proceed to block 170 and update the software. Updating the software may include obtaining the updated software from the server 18 and transmitting the software to the data transfer device 59 in another interrogation signal.

[0085] If the software checked is up to date (“YES” branch of decision block 168), the process 160 may proceed to block 172 and determine if a network is available. If a network is available (“YES” branch of decision block 172), the process 160 may proceed to block 174 and transmit data received in the response signal (e.g., operational data associated with the dispenser 24) to the server 18, e.g., for storage in the database 20. If a network is not available (“NO” branch of decision block 172), the process 160 may proceed to block 176 and cache the data in a local memory, e.g., in the mobile device 14.

[0086] Operational data may include a number of operations in which the receptacle 47 was compatible with the selected product 38, a number of operations in which the receptacle 47 was not compatible with the selected product 38, a number of operations in which the receptacle 47 was not detected (e.g., because the receptacle tag 72 was absent), the type of product 38 dispensed during the operation, the duration of a dispense cycle during the operation, which dispense switch was pressed (e.g., high flow rate or low flow rate), a total number of operations or a number of operations for one or more periods of time (e.g., total dispense operations or dispense operations per day), the number of operations for each of the one or more periods of time that were error-free, the cumulative duration of the error-free operations for each of the one or more periods of time, the number of operations during which errors were detected for each of the one or more periods of time, and the cumulative duration of operations having errors for each of the one or more periods of time. These exemplary parameters may be collected for each of the products 38.

[0087] By way of example, one type of error that may occur during a dispense operation relates to the amount of time between the controller 36 detecting activation of the dispense switch 58 and detecting one or more of a flow of water between source valve 30 and selector valve 32, a flow of product 38 between the source container 40 and the selector valve 32, or a flow of diluted chemical solution 62 through the dispensing nozzle 64. An error may be detected if one or more of these amounts of time is less than a minimum threshold (e.g., less than 30 ms for water or 50 ms for product 38) or more than a maximum threshold (e.g., more than 500 ms for water or 1000 ms for product 38). Another exemplary type of error may be detected when the dispense switch 58 is activated for a period of time having a duration less than a minimum threshold (e.g., less than 5 seconds) or more than a maximum threshold (e.g., more than 60 seconds).

[0088] Errors may also be indicated based on the timing or order of a sequence of events deviating from the timing or sequence expected during normal operation. For example, a normal dispense operation sequence may include detecting activation of the dispense switch 58, followed by detecting a flow of water between the source valve 30 and the selector valve 32, followed by detecting a flow of product 38 between the selected source container 40 and the selector valve 32, followed by detecting deactivation of the dispense switch 58. Thus, an error may be detected if the signals are received by the controller 36 indicating that this sequence of events occurred in a different order.

[0089] As another example of timing errors, the controller 36 may compare the amount of time the flow of water is detected between the source valve 30 and selector valve 32 to the amount of time the flow of product 38 is detected between the selected source container 40 and the selector valve 32. The controller 36 may determine an error has occurred if a difference between the amount of time the water or product 38 flows is less than a

predetermined amount of the total activation time, e.g., less than 80% of the total activation time.

[0090] By way of example, one type of error-free dispense operation may include the following sequence of events detected at the controller 36. The dispense operation may begin in response to the controller 36 detecting activation of the dispense switch 58. The controller 36 may then activate or enable the source valve 30 and begin monitoring the water flow sensor. The signal from the water flow sensor should indicate that a sufficient amount of water is flowing through the selector valve 32 within a predetermined maximum amount of time of the source valve 30 being opened, e.g., about 40ms. However, if the water flow sensor indicates water is flowing through the selector valve 32 too early, it could mean that the water flow sensor is faulty, e.g., that a flow switch of the water flow sensor is stuck in an open position. Thus, if the delay between opening the source valve 30 and detecting a sufficient flow of water through the selector valve 32 is less than a minimum amount of time (e.g., 20 ms) the controller 36 may determine an error has occurred. In any case, the water flow sensor should continue to indicate a sufficient amount of water is flowing through the selector valve 32 until the dispense switch 58 is released or a predetermined amount of time has elapsed.

[0091] For dispensers that include a product flow sensor, the controller 36 should detect flow of product 38 within a certain amount of time after detecting a sufficient flow of water. As with the water flow, the amount of time should fall within a range between a minimum amount of time and a maximum amount of time. The amount of time between sensing the flow of water and sensing the flow of product may be, for example, between 300 ms and 900 ms, depending on the type of dispenser 24. If the flow or product 38 is detected before the minimum amount of time has passed, (e.g., as soon as the dispense switch 58 is activated), it may indicate that a product flow switch is stuck in an open position. In any case, once the product flow signal has been received it should remain active until the dispense switch 58 is released.

[0092] Operational data may be used to determine one or more operational states of the dispenser 24 or source containers 40. For example, the total number of operations performed by the dispenser 24 since a previous point in time (e.g., the last servicing) may be compared to a threshold value, and a“maintenance required” state set if the total number of operations is greater than the threshold. The maintenance required state may also be entered if the number of errors in a period of time (e.g., in a day) or the percentage of operations including errors relative to the total number of operations in the period of time exceeds a threshold value. If a maintenance monitoring application on the server 18 determines a dispenser 24 will be needing maintenance soon, the application may transmit an alert that notifies a user of upcoming maintenance needs

[0093] The amount of product 38 dispensed during each operation may be determined based on the amount of time the product 38 flowed between the source container 40 and the selector valve 32 during the operation. This amount of time may be multiplied by a known flow rate for the mixing device in the dispenser 24 or a flow rate measured by a flow sensor if present. When used with an eductor-based mixing device, the known flow rate may be determined based on the type of dispenser tip used in the mixing device.

[0094] The data uploaded to the database 20 may be used to track individual dispensers 24 and source containers 40 using the UUTDs and location data uploaded to the database 20 by mobile devices 14. This data may be used, for example, to generate a map showing the last known location of each dispenser 24 or source container 40.

[0095] Embodiments of the invention may also be used to prevent one chemical supplier from using equipment supplied by another chemical supplier. This may be accomplished by creating rules that prohibit dispensing product 38 from a source container 40 having a UUID that is on a blacklist or that is not included on a whitelist, for example. This feature may be used to prevent the dispensing of product 38 from a source container 40 provided by a chemical supplier other than the supplier that provided the dispenser 24. For example, where the dispenser 24 was provided at a discount or under an agreement that the user would only purchase product from the supplier providing the dispenser 24. Dispensers 24 provided by a particular supplier may thereby be configured to prohibit another supplier’s product 38 from being dispensed.

[0096] Operational data may be used to estimate when the level of product 38 in a source container 40 is getting low. Based on an expected flow rate of water, the collective duration the dispense switch 58 has been activated since the source container 40 was installed, and the expected dilution ratio, the amount of product 38 remaining and an estimated time until the source container 40 is empty can be determined. The system may also improve its ability to predict low levels of product 38 over time by comparing predicted out of product times to actual out of product times, and adjust usage models based on the differences.

[0097] Uploading operational data to the database 20 may also facilitate maintenance tracking. For example, based upon an amount of usage recorded by the dispenser 24, the supplier may determine when certain types of maintenance are required. This data may also allow models to be developed that predict when certain components will wear out based on the duration of events, the number of events, and the types of product 38 dispensed.

[0098] Embodiments of the invention may be used to track usage, including which product 38 was used, how often it was used, when the source container 40 was changed, how may receptacles 47 were filled, and the average amount of diluted chemical solution that was dispensed into the receptacles 47.

[0099] Operational data may also be used to provide“proof of dispense” for deployments where this is required by regulations, such as a restaurant or hospital. Proof of dispense may be provided based on data from a product flow switch that confirms the product was dispensed during a dispense operation. The improved monitoring of operational parameters may also allow the system to determine the exact dilution ratio that was achieved during each dispense operation. Operational data may also be organized by operational environment, e.g., whether the dispensed solution was for a housekeeping, laundry, or kitchen environment of a particular dispensing location 12.

[0100] By providing data relating to how much of each product 38 is being dispensed, suppliers can charge customers a subscription fee based upon the number of products 38 being dispensed across multiple dispensers 24. Suppliers may also charge by the number of receptacles 47 filled. This data may also allow the system to calculate when a source container 40 will be empty, allowing the user to be alerted when it is time to reorder more product 38 or automatically shipping a new container to the dispensing location 12.

[0101] Dispensers 24 may be configured so that only authorized users are able to dispense a solution containing a product 38, and the system may also record who interacted with the system, what the interaction was, and when the interaction occurred. The dispenser 24 may use the UUIDs retrieved from the source container 40 or receptacle 47 to

automatically select and dispense the appropriate chemical when the end user loads a receptacle in the dispensing station 79.

[0102] Referring now to FIG. 8, embodiments of the invention described above, or portions thereof, may be implemented using one or more computer devices or systems, such as exemplary computer 200. The computer 200 may include a processor 202, a memory 204, an input/output (I/O) interface 206, and a Human Machine Interface (HMI) 208. The computer 200 may also be operatively coupled to one or more external resources 210 via the network 212 or I/O interface 206. External resources may include, but are not limited to, servers, databases, mass storage devices, peripheral devices, cloud-based network services, or any other resource that may be used by the computer 200.

[0103] The processor 202 may include one or more devices selected from

microprocessors, micro-controllers, digital signal processors, microcomputers, central processing units, field programmable gate arrays, programmable logic devices, state machines, logic circuits, analog circuits, digital circuits, or any other devices that manipulate signals (analog or digital) based on operational instructions stored in memory 204. Memory 204 may include a single memory device or a plurality of memory devices including, but not limited to, read-only memory (ROM), random access memory (RAM), volatile memory, non volatile memory, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, cache memory, or data storage devices such as a hard drive, optical drive, tape drive, volatile or non-volatile solid state device, or any other device capable of storing data.

[0104] The processor 202 may operate under the control of an operating system 214 that resides in memory 204. The operating system 214 may manage computer resources so that computer program code embodied as one or more computer software applications, such as an application 216 residing in memory 204, may have instructions executed by the processor 202. In an alternative embodiment, the processor 202 may execute the application 216 directly, in which case the operating system 214 may be omitted. One or more data structures 218 may also reside in memory 204, and may be used by the processor 202, operating system 214, or application 216 to store or manipulate data.

[0105] The I/O interface 206 may provide a machine interface that operatively couples the processor 202 to other devices and systems, such as the external resource 210 or the network 212. The application 216 may thereby work cooperatively with the external resource 210 or network 212 by communicating via the I/O interface 206 to provide the various features, functions, applications, processes, or modules comprising embodiments of the invention. The application 216 may also have program code that is executed by one or more external resources 210, or otherwise rely on functions or signals provided by other system or network components external to the computer 200. Indeed, given the nearly endless hardware and software configurations possible, persons having ordinary skill in the art will understand that embodiments of the invention may include applications that are located externally to the computer 200, distributed among multiple computers or other external resources 210, or provided by computing resources (hardware and software) that are provided as a service over the network 212, such as a cloud computing service.

[0106] The HMI 208 may be operatively coupled to the processor 202 of computer 200 to allow a user to interact directly with the computer 200. The HMI 208 may include video or alphanumeric displays, a touch screen, a speaker, and any other suitable audio and visual indicators capable of providing data to the user. The HMI 208 may also include input devices and controls such as an alphanumeric keyboard, a pointing device, keypads, pushbuttons, control knobs, microphones, etc., capable of accepting commands or input from the user and transmitting the entered input to the processor 202.

[0107] A database 220 may reside in memory 204, and may be used to collect and organize data used by the various systems, processes, or modules described herein. The database 220 may include data and supporting data structures that store and organize the data. In particular, the database 220 may be arranged with any database organization or structure including, but not limited to, a relational database, a hierarchical database, a network database, or combinations thereof. A database management system in the form of a computer software application executing as instructions on the processor 202 may be used to access the information or data stored in records of the database 220 in response to a query, which may be dynamically determined and executed by the operating system 214, other applications 216, or one or more modules. [0108] In general, the routines executed to implement the embodiments of the invention, whether implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions, or a subset thereof, may be referred to herein as“computer program code,” or simply“program code.” Program code typically comprises computer-readable instructions that are resident at various times in various memory and storage devices in a computer and that, when read and executed by one or more processors in a computer, cause that computer to perform the operations necessary to execute operations or elements embodying the various aspects of the embodiments of the invention. Computer-readable program instructions for carrying out operations of the embodiments of the invention may be, for example, assembly language, source code, or object code written in any combination of one or more programming languages.

[0109] Various program code described herein may be identified based upon the application within which it is implemented in specific embodiments of the invention.

However, it should be appreciated that any particular program nomenclature which follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified or implied by such nomenclature. Furthermore, given the generally endless number of manners in which computer programs may be organized into routines, procedures, methods, modules, objects, and the like, as well as the various manners in which program functionality may be allocated among various software layers that are resident within a typical computer (e.g., operating systems, libraries, API’s, applications, applets, etc.), it should be appreciated that the embodiments of the invention are not limited to the specific organization and allocation of program functionality described herein.

[0110] The program code embodied in any of the applications or modules described herein is capable of being individually or collectively distributed as a computer program product in a variety of different forms. In particular, the program code may be distributed using a computer-readable storage medium having computer-readable program instructions thereon for causing a processor to carry out aspects of the embodiments of the invention.

[0111] Computer-readable storage media, which is inherently non-transitory, may include volatile and non-volatile, and removable and non-removable tangible media implemented in any method or technology for storage of data, such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media may further include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid state memory technology, portable compact disc read-only memory (CD-ROM), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store data and which can be read by a computer. A computer-readable storage medium should not be construed as transitory signals per se (e.g., radio waves or other propagating electromagnetic waves, electromagnetic waves propagating through a transmission media such as a waveguide, or electrical signals transmitted through a wire). Computer-readable program instructions may be downloaded to a computer, another type of programmable data processing apparatus, or another device from a computer-readable storage medium or to an external computer or external storage device via a network.

[0112] Computer-readable program instructions stored in a computer-readable medium may be used to direct a computer, other types of programmable data processing apparatuses, or other devices to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions that implement the functions, acts, or operations specified in the flow-charts, sequence diagrams, or block diagrams. The computer program instructions may be provided to one or more processors of a general purpose computer, a special purpose computer, or other

programmable data processing apparatus to produce a machine, such that the instructions, which execute via the one or more processors, cause a series of computations to be performed to implement the functions, acts, or operations specified in the flow-charts, sequence diagrams, or block diagrams.

[0113] In certain alternative embodiments, the functions, acts, or operations specified in the flow-charts, sequence diagrams, or block diagrams may be re-ordered, processed serially, or processed concurrently consistent with embodiments of the invention. Moreover, any of the flow-charts, sequence diagrams, or block diagrams may include more or fewer blocks than those illustrated consistent with embodiments of the invention.

[0114] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the invention. As used herein, the singular forms“a”,“an” and“the” are intended to include both the singular and plural forms, and the terms“and” and“or” are each intended to include both alternative and conjunctive combinations, unless the context clearly indicates otherwise. It will be further understood that the terms“comprises” or“comprising,” when used in this

specification, specify the presence of stated features, integers, actions, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, integers, actions, steps, operations, elements, components, or groups thereof. Furthermore, to the extent that the terms“includes”,“having”,“has”,“with”,“comprised of’, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term“comprising”.

[0115] While all the invention has been illustrated by a description of various

embodiments, and while these embodiments have been described in considerable detail, it is not the intention of the Applicant to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art. The invention in its broader aspects is therefore not limited to the specific details, representative apparatus and method, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the Applicant’ s general inventive concept.

Claims

CLAIMS What is claimed is:

1. A dispenser comprising:

a source station configured to receive a source container;

a first reader located proximate to the source station; and

a controller in communication with the first reader and comprising one or more processors and a first memory storing program code that, when executed by the one or more processors, causes the controller to:

in response to detecting a first event indicating the source station has been accessed, cause the first reader to transmit a first interrogation signal,

receive first data associated with the source container located in the source station from the first reader,

store the first data in the first memory, and

determine whether to dispense a solution including a product in the source container based at least in part on the first data stored in the first memory.

2. The dispenser of claim 1 further comprising:

a dispensing station; and

a second reader in communication with the controller and located proximate to the dispensing station,

wherein the program code further causes the controller to:

in response to detecting a second event, cause the second reader to transmit a second interrogation signal,

receive second data associated with a receptacle from the second reader, and determine whether to dispense the solution including the product in the source container based at least in part on the second data.

3. The dispenser of claim 2 wherein the second event is reception of a second signal indicating a user is requesting a dispense operation.

4. The dispenser of claim 1 further comprising:

a door that controls access to the source station; and

a sensor configured to provide a signal to the controller indicative of whether the door is open or closed,

wherein detecting the first event indicating the source station has been accessed includes one or more of detecting that the door has been opened, detecting the door has been closed, or detecting a combination of the door being opened and the door being closed.

5. The dispenser of claim 1 further comprising a dispense switch, wherein the program code further causes the controller to:

after storing the first data in the first memory, enter a sleep mode; and

in response to detecting activation of the dispense switch, exit the sleep mode, wherein whether to dispense the solution including the product in the source container is determined based at least in part on the first data in the first memory.

6. The dispenser of claim 1 further comprising:

a data transfer device including a second memory, wherein the program code further causes the controller to store the first data in the second memory.

7. The dispenser of claim 6 wherein the program code causes the controller to store the first data in the second memory by transmitting a third interrogation signal carrying the first data to the data transfer device.

8. The dispenser of claim 6 wherein the program code further causes the controller to: begin a dispense operation that dispenses the solution including the product in the source container by opening a source valve; and

store second data in the second memory indicative of an amount of the product dispensed from the source container during the dispense operation.

9. The dispenser of claim 6 wherein the data transfer device is configured to:

receive a fourth interrogation signal from a mobile device; and

in response to receiving the fourth interrogation signal, transmit the first data to the mobile device.

10. The dispenser of claim 9 wherein the program code further causes the controller to enter a sleep mode after storing the first data in the second memory, and the data transfer device transmits the first data to the mobile device without the controller exiting the sleep mode.

11. A method of operating a dispenser including a controller, a first memory, a source station, and a first reader proximate to the source station, the method comprising:

in response to detecting a first event indicating the source station has been accessed, transmitting, by the first reader, a first interrogation signal;

receiving, by the first reader in response to the interrogation signal, first data associated with a source container located in the source station;

storing the first data in the first memory; and

determining, by the controller, whether to dispense a solution including a product in the source container based at least in part on the first data stored in the first memory.

12. The method of claim 11 wherein the dispenser further includes a dispensing station and a second reader in communication with the controller and located proximate to the dispensing station, the method further comprising:

in response to detecting a second event, causing the second reader to transmit a second interrogation signal;

receiving second data associated with a receptacle from the second reader; and determining whether to dispense the solution including the product in the source container based at least in part on the second data.

13. The method of claim 12 wherein the second event is reception of a second signal indicating a user is requesting a dispense operation.

14. The method of claim 11 wherein the dispenser further includes a door that controls access to the source station and a sensor configured to provide a signal to the controller indicative of whether the door is open or closed, and wherein detecting the first event indicating the source station has been accessed includes one or more of detecting that the door has been opened, detecting the door has been closed, or detecting a combination of the door being opened and the door being closed.

15. The method of claim 11 wherein the dispenser further includes a dispense switch, and further comprising:

after storing the first data in the first memory, entering a sleep mode; and

in response to detecting activation of the dispense switch, exiting the sleep mode, wherein whether to dispense the solution including the product in the source container is determined based at least in part on the first data in the first memory.

16. The method of claim 11 wherein the dispenser further includes a data transfer device including a second memory, and further comprising storing the first data in the second memory.

17. The method of claim 16 wherein the first data is stored in the second memory by transmitting a third interrogation signal carrying the first data to the data transfer device.

18. The method of claim 16 further comprising:

beginning a dispense operation that dispenses the solution including the product in the source container by opening a source valve; and

storing second data in the second memory indicative of an amount of the product dispensed from the source container during the dispense operation.

19. The method of claim 16 further comprising:

receiving a fourth interrogation signal from a mobile device at the data transfer device; and

in response to receiving the fourth interrogation signal, transmitting the first data to the mobile device from the data transfer device.

20. A computer program product comprising:

a non-transitory computer-readable storage medium; and

program code stored on the non-transitory computer-readable storage medium that, when executed by one or more processors, causes the one or more processors to:

in response to detecting a first event indicating a source station has been accessed, cause a reader to transmit an interrogation signal;

receive, from the reader, first data associated with a source container located in the source station received by the reader in response to the interrogation signal; store the first data in a first memory; and