Dispenser monitoring system

Abstract

Disclosed herein are a dispenser monitoring system and methods relating thereto. The monitoring system includes a node device, a sensor device, and a remote computing device. The node device includes: a sensor device adapted to be fitted to a dispenser; an activation sensor for detecting movement of the sensor device; and a transmitter for transmitting activation data based on detected movement of the sensor device. The remote computing device includes: a receiver for receiving the transmitted activation data; and a processor for executing computer instructions to: process the activation data; and generate at least one report based on the activation data.

Description

DISPENSER MONITORING SYSTEMRelated Application

[0001] This application is related to Australian Provisional Patent Application No. 2023902062 titled “Dispenser monitoring system” and filed 29 June 2023 in the name of Mezrit Pty Ltd, the entire content of which is incorporated by reference, as if fully set forth herein.Technical Field

[0002] The present disclosure relates to a system and method for monitoring the usage of one or more dispensers.Background

[0003] A dispenser is a device that is configured to deliver stored contents in prescribed amounts. A dispenser typically includes a container for storing contents and a delivery aperture for delivering a prescribed amount of the contents to a user, upon activation. Dispensers may be used in relation to solids, liquids, and gases and the dispensing head may take many different forms, depending on the application.

[0004] Dispensers include vending machines and the like, which dispense a selected good through a delivery aperture that is often in a form of a receptacle accessible by a user. Dispensers also include liquid dispensers, such as used in relation to soaps, detergents, oils, water, fertilisers, and the like. Liquid dispensers typically include a container to which is attached a pump nozzle, an inlet tube, and a piston. In use, a user activates the piston, which forces liquid into the inlet tube for delivery through the pump nozzle. Each pump of the piston corresponds to a predefined dosage of liquid being dispensed from the container. Dispensers may also be utilised in relation to powders and granules.

[0005] Dispensers may be manually activated, in which the user is required to physically activate a piston or other actuation means to dispense contents from the dispenser. Alternatively, dispensers may include sensors that detect the presence of a user and dispense a predefined amount of content upon detection of the presence of a user. Such sensors may include photo sensors and the like.

[0006] In many scenarios, particularly in the healthcare, food, and hospitality industries, it is important that people wash their hands in accordance with prescribed sanitary procedures. Such sanitary procedures often require staff members to wash their hands when using bathrooms, when entering a healthcare facility, immediately before physicallycontacting a patient, or immediately before preparing food. Despite the best efforts to provide soap and sanitiser dispensers at all appropriate locations, along with appropriate instructions, some people fail to execute the prescribed sanitary procedures and it is not presently possible to determine whether those sanitary procedures have been followed or not in order to assess compliance with predetermined health requirements.

[0007] It is important for facility managers and administrators to know the level of contents in dispensers throughout one or more locations or facilities. In many circumstances, liquid soap and sanitiser dispensers run out of contents, resulting in people having to locate alternative dispensers or otherwise failing to adhere to sanitary procedures.

[0008] Existing approaches for monitoring the level of contents in dispensers typically utilise a paper-based system, in which an individual visits each dispenser and makes a notation regarding the level of contents in each dispenser. Such approaches are prone to inaccuracy, relying on a human to estimate a content level, often through an opaque or semi-opaque dispenser container. Further, human error may result in the content levels of some dispensers being missed, poorly estimated, or even falsely recorded.

[0009] It is also difficult for facility managers and administrators to determine whether there are sufficient dispensers provided at a location or the usage experienced by individual dispensers.

[0010] Thus, a need exists for a method and system for remotely monitoring dispensers.Summary

[0011] The present disclosure relates to a system and associated methods for monitoring the usage of dispensers.

[0012] A first aspect of the present disclosure provides a dispenser monitoring system comprising: a node device, the node device including: a sensor device adapted to be fitted to a dispenser; an activation sensor for detecting movement of the sensor device; a transmitter for transmitting activation data based on detected movement of the sensor device; and a remote computing device, the remote computing device including: a receiver for receiving the transmitted activation data; and a processor for executing computer instructions to: process the activation data; andgenerate at least one report based on the activation data.

[0013] A second aspect of the present disclosure provides a dispenser monitoring system comprising: a first network of at least one gateway device, each gateway device including: a radio frequency receiver for receiving activation data; and a transmitter for transmitting the activation data; a second network of a plurality of node devices, each node device being associated with a gateway device and each node device including: a sensor device adapted to be fitted to a dispenser; an activation sensor for detecting movement of the sensor device; and a radio frequency transmitter for transmitting, to an associated gateway device, activation data based on detected movement of the sensor device; and a remote computing device, the remote computing device including: a receiver for receiving the transmitted activation data from each of the gateway devices; a database; and a processor for executing computer instructions to: append the received activation data to the database; and generate at least one report based on the database.

[0014] According to another aspect, the present disclosure provides an apparatus for implementing any one of the aforementioned methods.

[0015] According to another aspect, the present disclosure provides a computer program product including a computer readable medium having recorded thereon a computer program that when executed on a processor of a computer implements any one of the methods described above.

[0016] Other aspects of the present disclosure are also provided.Brief Description of the Drawings

[0017] One or more embodiments of the present disclosure will now be described by way of specific example(s) with reference to the accompanying drawings, in which:

[0018] Fig. 1 is a schematic representation of a dispenser monitoring system;

[0019] Fig. 2 is a schematic representation illustrating further detail of an embodiment of the node device and the gateway of the system of Fig. 1 ;

[0020] Fig. 3 is a schematic representation of a node device and dispenser;

[0021] Fig. 4A is a schematic block diagram representation of the node device of Fig. 3;

[0022] Fig. 4B is a schematic representation of a printed circuit board (PCB) layout for an embodiment of the node device of Fig. 3;

[0023] Fig. 5 is a schematic block diagram representation of a system that includes a general purpose computer on which one or more embodiments of the present disclosure may be practised;

[0024] Fig. 6 is a schematic block diagram representation of a system that includes a general smartphone on which one or more embodiments of the present disclosure may be practised;

[0025] Fig. 7A is a schematic diagram of a coin battery and measurement circuit;

[0026] Fig. 7B a schematic diagram of a battery circuit implemented using AA batteries;

[0027] Fig. 7C is a schematic diagram of a measurement circuit;

[0028] Fig. 8 is a schematic diagram of a Bluetooth / Mesh MCU processor;

[0029] Fig. 9A is a schematic diagram of a programming port to enable programming of a node device;

[0030] Fig. 9B is a schematic diagram of a debug port for assistance in debugging a node device;

[0031] Figs 10A and 10B are schematic diagrams of circuitry for implementing an activation sensor;

[0032] Fig. 11 A is a schematic diagram of a first LED indication circuit;

[0033] Fig. 11 B is a schematic diagram of a second LED indication circuit;

[0034] Fig. 12A is a schematic diagram of a first circuit that includes a memory module;

[0035] Fig. 12B is a schematic diagram of a second circuit that includes a memory module;

[0036] Fig. 13 is a schematic diagram of a NorFlash memory circuit; and

[0037] Fig. 14 illustrates signal processing associated with detection of actuation of a dispenser.

[0038] Method steps or features in the accompanying drawings that have the same reference numerals are to be considered to have the same function(s) or operation(s), unless the contrary intention is expressed or implied.Detailed Description

[0039] The present disclosure provides a method and system for remotely monitoring dispenser usage. Some embodiments utilise an automated network of nodes that transmit dispenser usage to a central computing device. Each node is associated with at least one dispenser, wherein each dispenser is equipped with an activation sensor that detects activation of the respective dispenser. Each node is also associated with a transmitted for transmitting activation data acquired by the activation sensors associated with that node to the central computing device.

[0040] Depending on the implementation, the activation sensors may be either integral with the dispenser or able to be retro-fitted to the dispenser. In some embodiments, the activation sensors are able to be retro-fitted to the dispenser and are so adapted that the sensors may be fitted to any dispenser, irrespective of the orientation of the dispenser.

[0041] Fig. 1 is a schematic representation of a system 100 for remotely monitoring dispenser usage, in accordance with one or more embodiments of the present disclosure. The system 100 includes a central computing device 110 that may be implemented using one or more computing devices, including personal computers, computer servers, cloud-hosted computing devices, or any combination thereof.

[0042] The system 100 also includes a network of dispenser nodes 120. In the example of Fig. 1 , the network of dispenser nodes 120 includes a first dispenser node 130, a second dispenser node 140, and a third dispenser node 150. Each of the dispenser nodes 130, 140, 150 includes a dispenser and an associated node device. Each node device includes an activation sensor adapted to detect activation of the associated dispenser.

[0043] The first dispenser node 130 includes a first dispenser 132 and a first node device 134. The second dispenser node 140 includes a second dispenser 142 and a second node device 144. The third dispenser node 150 includes a third dispenser 152 and a third node devicel 54. It will be appreciated that the network of dispenser nodes 120 may include any number of dispenser nodes, depending on the particular application. Further, the dispenser nodes may be co-located at a single location or distributed over a plurality of locations, depending on the implementation.

[0044] As indicated above, each node device 134, 144, 154 includes an activation sensor adapted to detect activation of the associated dispenser, 132, 142, 152, respectively. In various embodiments, the activation sensor may be implemented using one or more actuators, photosensors, or the like, or any combination thereof. In preferred embodiments, the activation sensor is adapted to be retro-fitted to existing dispensers.

[0045] Each node device 134, 144, 154 also includes a transmitter for transmitting activation data relating to activation of the respective dispensers 132, 142, 152 to the central computing device 110. In the embodiment of Fig. 1 , the node devices 134, 144, 154 transmit activation data to the remote computing device 110 via an intermediary gateway 160. The gateway 160 is coupled to the remote computing device 110 via a communications network 165.

[0046] The communications network 165 may comprise one or more wired communications links, wireless communications links, or any combination thereof. In particular, the communications network 165 may include a local area network (LAN), a wide area network (WAN), a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, such as a Public Switch Telephony Network (PSTN) or a cellular mobile telephony network, the Internet, or any combination thereof.

[0047] In the example of Fig. 1 , the gateway 160 is identified as a cellular gateway, but any network gateway capable of coupling to the remote computing device 110 may be utilised.

[0048] In one or more alternative embodiments, the gateway 160 and remote computing device 110 are each coupled to a LAN.

[0049] Whilst the example of Fig. 1 shows a single gateway 160, it will be appreciated that any number of gateways may be utilised, as required by the network topology and location of the dispenser nodes. Further, each of the node devices 134, 144, 154 may be coupled to the gateway 160 by one or more wired or wireless couplings, or any combination thereof. In some embodiments, the node devices 134, 144, 154 communicate with the gateway 160 via a wireless communications protocol, such as Long Range (LoRa), Wi-Fi, Bluetooth, Zigbee, Z-Wave, 6L0WPAN, RFID, NFC, 4G / 5G, NB- IOT, LTE, and the like.

[0050] In the example of Fig. 1 , the remote computing device 100 includes a data system 170 and a reporting system 180. The data system 170 receives activation data from each of the node devices 134, 144, 154, via the communications network 165. The data system 170 may be implemented using one or more computing devices, such as a computer server or the like, or a cloud-hosted computing service, such as Amazon Web Services (AWS) offered by Amazon Web Services, Inc. as shown in the example of Fig. 1 .

[0051] The reporting system 180 may be integral with the data system 170 or, alternatively, may be implemented using a separate computing device. The reporting system 180 provides a user interface for viewing by users. The user interface mayinclude, for example, a dashboard via which a user can monitor activation data across the network of node devices. The reporting system 180 also provides reports on the use of the dispensers 132, 142, 152. Most dispensers dispense a known amount for each dispenser activation. Accordingly, monitoring the activation of each dispenser enables the reporting system 180 to provide real-time or near-real time stock-levels for each dispenser 132, 142, 152.

[0052] The reporting system 180 also provides an interface for external viewing, such as via a software application (“app”) or web-browser executing on a user device 190. The user computing device 190 may be implemented, for example, using a personal computer, smartphone, tablet computing device, or the like.

[0053] Depending on the implementation, the reporting system 180 is able to display to a user dashboard, via an app or web-browser, various reports that may include, for example, the number of dispenser actuations per dispenser and / or per region, compliance for a region based on number of known or detected users relative to dispenser actuations, heat maps indicating the rate of dispenser actuation, and the like. In some embodiments, the reporting system 180 collects data based on the number of actuations (e.g., pushes) per device. The system determines when the contents of a dispenser need to be replaced, based on the volume of the dispenser, the amount dispensed per actuation, and the rate of actuations. A region may relate to a single node device, an array of node devices, a geographical area (such as a building floor or section, building, campus, or broader area), or other user-defined area.

[0054] Studying the reports enables a user to determine a level of compliance for a given region, as well as assisting with stock levels within dispensers, and identifying the need for relocation of node devices and / or introduction or deletion of node devices.

[0055] Some embodiments utilise a unique node device identifier allocated to each respective node device. In some implementations, the unique node device identifier is positioned on the respective node device or associated dispenser, such as by a sticker, label, engraving, or the like. In some implementations, the unique node device identifier is presented as a serial number or barcode. A barcode can be a 1 D (e.g., thin black lines), 2D (e.g. DataMatrix, Quick Response (QR) code), or 3D barcode (e.g., “Bumpy Barcode”).

[0056] In some embodiments, a node device identifier in the form of a QR code is affixed to each node device and a user is able to scan the QR code to retrieve data associated with that node device. The data may include, for example, but is not limited to, installation date, total number of actuations, number of actuations for a specified period,date of refill, date of battery installation, predicted date of refill, predicted date of battery replacement, and the like.

[0057] The system 100 for remotely monitoring dispenser usage enables the remote computing device 110 to acquire and process activation data from each of the node devices. Such a system 100 enables data driven management of commercial cleaning and infection control environment services.

[0058] Some embodiments utilise node devices that can be fitted to existing dispenser devices in order to monitor activation / use of the dispenser devices and transmit activation data to a central computing device. The central computing device processes the activation data to generate reports on one or more of dispenser usage, dispenser stock levels, and the like.

[0059] The reports may include one or more of bar charts, graphs, heat maps, and the like. Such reports enable a user to monitor the frequency of use of dispensers at different locations. The reports may be utilised for compliance auditing to ensure that staff use dispensers in bathrooms, food handling environments, and healthcare facilities. In such embodiments, compliance reports may be supplemented by associating employee identifiers with a particular region or set of dispensers. The reports may also be utilised to identify locations for which more dispenser are required and, conversely, locations from which dispenser may be removed. The reports may also be utilised to identify staff or regions for which training is required, more signage is required, or a combination thereof. In some embodiments, the reports show developments over time, based on acquired longitudinal data.

[0060] In some embodiments, the central computing device processes activation data to predict future activities relating to one or more of the dispensers. The future activities may include, for example, refilling the dispenser and replacing a battery of the node device. For example, the central computing device stores a volume of liquid associated with a particular dispenser and the amount dispensed by each actuation. By tracking actuation data associated with that dispenser over time, the central computing device predicts a time by which the volume of liquid in that dispenser will reach a predefined low threshold and require replacement.

[0061] The central computing device is programmed to send one or more notifications relating to the remaining levels of liquid in the respective dispensers and send notifications when the central computing device determines that the predefined low threshold has been reached for a dispenser or within a predefined buffer period before that time. Such notifications may include messages on a dashboard, SMS text messages, in-appmessages, emails or the like, or any combination thereof. Such notifications can also be used to manage ordering of supplies. In some embodiments, the notifications feed into an inventory management system to automatically populate future orders of supplies.

[0062] For example, a liquid dispenser stores 1000mL and each actuation dispenses 2mL, representing 500 actuations to empty the dispenser. A node device associated with the dispenser detects and transmits actuation data to a central computing device, which tracks the actuation data. In this example, a predefined low threshold associated with the dispenser is 100mL and a buffer period of 50mL is also predefined.

[0063] When the central computing device receives actuation data indicating that 425 actuations have occurred, the central computing device determines that the dispenser has reached the buffer period, being within 50mL of the lower threshold. The central computing device issues an initial notification. When the central computing device receives actuation data indicating that a further 25 actuations have occurred, the central computing device sends a further notification that the dispenser has reached the lower threshold of 100mL remaining and needs to be refilled. Depending on inventory management, the central computing device also orders more refills or cartridges for the dispenser.

[0064] The actual buffer period and lower threshold depend on the particular application. Further, in some embodiments the central computing device determines the rate of actuations associated with a dispenser or set of dispensers, enabling rates of usage to be determined across one or more dispensers, regions, and the like. This enables the central computing device to be used to monitor and manage large numbers of dispensers and associated inventories.

[0065] In some embodiments, a user interface associated with the central computing device displays a current status of the volume of product in each dispenser and / or a rate of actuation for each dispenser or predefined groups of dispensers, thus providing a user with a visual indication of the status of the dispensers.

[0066] In some embodiments, the system for monitoring dispenser usage utilises a proximity sensor to identify the presence of a user. The proximity sensor may be a standalone sensor, such as a sensor attached to a door or door frame for detecting the passage of a user through a doorway or located proximal to a dispenser to detect the presence of a user near the dispenser. Alternatively, the node device may include the proximity sensor, which detects the presence of a user within a predefined range of the node device. The central computing device is able to correlate proximity data derivedfrom the proximity sensor with activation data derived from the activation sensor to determine a degree of compliance for each dispenser.

[0067] For example, in a scenario in which a soap dispenser is located in a bathroom, there is a requirement that a person using the bathroom must wash their hands, which requires activating the dispenser to dispense soap. A proximity sensor identifies the presence of a user in the bathroom and activation data from a node device can then confirm whether or not that user utilised the dispenser to dispense soap. Activation data derived from an activation sensor of the node device can be correlated against proximity data, by the central computing device, to provide reports on the compliance of users washing hands when visiting the bathroom.

[0068] In a simpler scenario, the activation data is correlated against a number of users for a known location to determine compliance. In such a scenario, there is no need for proximity sensors to detect the presence of users. Rather, there is a predefined understanding of the normal usage by a person that can be correlated for the number of users known to be associated with, or located at, a particular site or location.

[0069] Compliance reports can be used to generate training messages to be sent out to users, such as emails or Short Message Service (SMS) text messages, or to produce education leaflets for printing and display at various locations for which compliance is below a predefined minimum compliance threshold or to reward compliance above a predefined reward compliance threshold.

[0070] Fig. 2 is a schematic block diagram representation illustrating further detail of an embodiment of the node device 134 and the gateway 160 of the system 100 of Fig. 1 . The node device 134 in the example of Fig. 2 includes a data module, a management module, a MQ Telemetry Transport (MQTT) module, a management module, a Zephor Real-Time Operating System (RTOS) module, a Boot Loader, a peripherals module, and a radio module. The radio module of the node device 134 is utilised to couple the node device 134 to the gateway 160 via an OpenThread LAN 250.

[0071] The Thread network 250 is a low-power, high security wireless communications network. MQTT-SN protocol is used at the local network, to enable the node device 134 to sleep as much as possible, thus conserving battery power.

[0072] The gateway 160 in the example of Fig. 2 is a cellular gateway that is implemented using a Linux Embedded PC, Eclipse Paho implementation of MQTT and MQTT-SN. The gateway 160 is implemented using hardware that includes a Universal Serial Bus (USB) port coupled to a USB840F Network Co-Processor (NCP) 161 for coupling the gateway 160 to the OpenThread LAN 250. The hardware also includes aM.2 port for a serial coupling to a cellular modem 162, such as provided by QuecteL The cellular modem couples the gateway 160 to the remote computing device 110 via the communications network 165. The gateway 160 translates the MQTT-SN protocol to MQTT, for connection to the AWS cloud infrastructure 110.

[0073] Whilst the embodiment of Fig. 2 shows the node device 134 and the cellular gateway 160 as discrete components, other embodiments may equally be practised in which the node device 134 and gateway 160 are integrated, such that the node device 134 incorporates a transmitter for coupling the node device 134 to the remote computing device 110 via a communications network 165. For example, the node device 134 optionally incorporates a cellular transceiver.

[0074] Fig. 3 is a schematic representation of a node device 320 in accordance with one or more embodiments of the present disclosure. The node device 320 is able to be retro-fitted to a dispenser, such as the dispenser 330 in the example of Fig. 3. In the example of Fig. 3, the dispenser 330 is supported by a horizontal shelf 360 that is attached to a wall 370. It will be appreciated that many other arrangements may be practised for supporting the dispenser 330, including custom holders, enclosures, supports, and the like. In other embodiments, the dispenser 330 may be simply placed on a substantially horizontal surface or other platform configured to support or hold the dispenser 330.

[0075] The dispenser 330 includes a container 350 for storing a liquid that is to be dispensed via an inlet tube 340 and a pump nozzle 345. A user is able to dispense liquid from the dispenser 330 by depressing the pump nozzle 345, which activates a piston (not shown) within the container 350, thus pumping liquid from the container 350 to exit the nozzle 345.

[0076] In the example of Fig. 3, the node device 320 includes a sensor device in the form of a collar 310 that is adapted to be fitted to a vertical portion of the inlet tube 340 of the dispenser 330. Depending on the implementation, the collar 330 may include one or more fastening means, such as a grub screw, clip, adhesive, friction tape, or the like to secure the collar 330 to a vertical portion of the inlet tube 340. In some embodiments, the collar is implemented using an elasticated body portion that is able to be stretched over the inlet tube 340 and positioned in place, and then held in place by friction.

[0077] The node device 320 includes a housing 315 that is adapted to be located in proximity to the collar 310, when the collar 310 is attached to the dispenser 330. In the example of Fig. 3, the housing 315 is attached to the vertical wall 370.

[0078] Fig. 4A is a schematic block diagram representation of functional components of the node device 320 contained within the housing 315. The housing 315 of the node device 315, in the example of Figs 3 and 4, includes an activation sensor 410, a processor 415, a radio transmitter 420, and a memory storage unit 425. The housing 315 also includes a power source (not shown), such as a battery or a coupling to a mains power supply.

[0079] Fig. 4B is a schematic representation of a printed circuit board (PCB) layout for an embodiment of the node device of Fig. 3.

[0080] Some embodiments utilise a battery as the power source, such as a lithium manganese dioxide battery. In particular, some embodiments utilise a 3V, OOmAh CR2477 button-type battery. Other embodiments utilise one or more AA batteries, such as 2 x FR6 Lithium (i.e. , 2 x 3500mAh) batteries. However, it will be appreciated by a person skilled in the art that many different batteries or other power supplies may equally be practised without departing from the spirit and scope of the present disclosure.

[0081] The activation sensor 410 detects movement of a paired sensor device, being collar 310 secured to the dispenser 330. In some embodiments, the activation sensor is implemented using a magnetometer or accelerometer that acts in combination with a magnet or other sensor device attached to or integral with the collar 315. The collar and magnet are positioned such that movement of the magnet 310 relative to the housing 315 causes actuation of the activation sensor in the housing 315. Depending on the implementation, the sensor device (e.g., magnet) may be affixed to the collar using one or more clamps, clips, slots, brackets, adhesives, fasteners, or any combination thereof. Alternatively, the sensor device may be embedded within the collar, such as a magnet positioned within a moulded plastic collar or the like.

[0082] Different collars may be implemented to accommodate different types of dispensers. In the example of Fig. 3, the collar 310 is positioned on a vertical portion of the inlet tube 310, wherein the inlet tube is vertically disposed in a downwards direction when a user dispenses fluid, causing the collar 310 to be vertically displaced relative to the housing 315. The activation sensor 410 in the housing 315 detects the movement of the magnet in the collar 315 and counts an activation of the dispenser 330.

[0083] It will be appreciated that many different forms of collars may be equally practised. Further, alternative embodiments forgo the collar altogether, instead affixing a sensor device, such as a magnet, to the inlet tube or other appropriate component by any suitable fixation means. Such fixation means may include, but are not limited to, one or more clamps, clips, slots, brackets, adhesives, fasteners, or the like, or any combinationthereof. In further alternative arrangements, the sensor device is integral with the inlet tube of the dispenser.

[0084] In alternative embodiments, the activation sensor is implemented using an alternative form of motion sensor that detects visual movement. In some embodiments, the activation sensor has a range in the order of 50 metres. In further embodiments, the activation sensor has a range in the order of 30 metres. It will be appreciated that different ranges may be utilised in relation to the activation sensor, depending on the particular application and implementation. In further embodiments, a range in the order of 0.5m, 1 m, 2-5m, 10m, or 20m may equally be utilised.

[0085] In use, the housing 315 is positioned sufficiently close to the collar 310 to ensure an accurate reading for the particular form of activation sensor and sensor device that are being utilised.

[0086] The activation sensor 410 is coupled to the processor 415, such that when the sensor 410 detects movement of the collar 310, the sensor 410 sends a message to the processor 415. The processor 415 is coupled to each of the memory 425 and the radio transmitter 420. The processor 415 executes computer program instructions to implement a sensor detection system in accordance with one or more embodiments of the present disclosure. The memory 425 may be used to store a log of activation times. Further, the memory 425 may be used to store transmission instructions for data to be transmitted to a remote computing device. The transmission instructions may include, for example, but are not limited to, transmission frequency, data format, node device identifier, and the like.

[0087] The activation sensor 410 detects each movement of the collar 310 and records the number of depressions, or “pumps”. In some embodiments, the activation sensor 410 is implemented using an accelerometer that generates a first signal upon detecting movement of the collar 310, wherein the first signal is filtered in order to determine a single actuation of the pump 330. The number of pumps is stored in the memory 425 for later transmission by the radio transmitter 420. In some embodiments, a time filter is applied to a set of detected actuations in order to identify a number of pumps associated with each user. In some embodiments, software executing on the processor 415 applies the time filter. In other embodiments, software executing on the remote computing device 110 applies the time filter on data received from one or more dispenser nodes.

[0088] In a simple example, all activations of a pump within a predefined time period are assigned to a particular user. The predefined time period may vary depending on the application. In some embodiments, the predefined time period is in the range of 1 to 30seconds, with some embodiments utilising a predefined time period in the range of 1 to 20 seconds, 1 to 10 seconds, or the like.

[0089] The radio transmitter 420 may be a transmitter only or a transceiver, depending on the implementation. In some embodiments, the radio transmitter 420 is configured to transmit data in accordance with one or more wireless communications protocols, such as Long Range (LoRa), Wi-Fi, Bluetooth, Zigbee, Z-Wave, 6L0WPAN, RFID, NFC, 4G / 5G, NB-IOT, LTE, and the like.

[0090] Some embodiments utilise a sensor device that incorporates a magnet, with a corresponding magnetometer utilised in the activation sensor. Such embodiments enable automatic calibration. Further, the use of a magnet-based sensor device enables any angle of dispenser installation on any axis. This means that the node device may be readily deployed to existing dispenser devices, without having to modify the installation of the dispensers.

[0091] Further, the magnet is able to be placed at any orientation, allowing for use with different dispenser devices having different inlet tubes and nozzles. Such embodiments are also resilient, being resistant to environmental shocks, bumps from users, and the like. Further, such embodiments have low power usage, providing long service intervals and low maintenance.

[0092] The operation of the embodiment of Figs 1 to 4 will now be described. Initially, the node device 320 is installed on the dispenser 330, with the sensor device 310 attached to the dispenser 330 and the housing installed in proximity to the dispenser 330.

[0093] An accelerometer interrupt signal wakes up the activation sensor 410, implemented in this example with a magnetometer, and the processor 415, once the magnetometer detects acceleration or movement of the sensor device 310 has exceeded a predefined threshold. In this example, the sensor device 310 incorporates a magnet and the magnetometer detects movement of the sensor device 310.

[0094] The processor 415 calculates a sum vector for the axis - data from the accelerometer, allowing the node device to function irrespective of the mounting angle of the sensor device 310 and the dispenser 330. The processor 415 applies a high pass filter to eliminate any DC component, which results in not needing to calibrate a node device for every new location or rotation. Further, the processor 415 then conditions the activation signal from the magnetometer by applying a low-pass filter to remove high frequencies (corresponding to noise).

[0095] The dispenser monitoring system utilises the impulse response of the high-pass filter and sets two peak detectors - a first peak detector for values above zero, and asecond peak detector for values below zero. The processor determines activation of the dispenser when a sequence of incoming pulses from the peak detectors is in accordance with a predefined sequence. This minimises the number of false-positives detected.

[0096] When the dispenser 330 is actuated, the magnetometer 410 wakes the processor 415 and processing of the magnetometer activation signals is performed. When a pump signature is recognized, a timestamped count is recorded.

[0097] Fig. 14 illustrates detection of activation of a dispenser, with each of the signals 1410, 1420, 1430 illustrating transformation of the signal from raw values to a vector and then band pass.

[0098] The node device 320 is programmed to transmit activation data at predefined transmission periods to the gateway 160 for further transmission to the remote computing device 110. Depending on the implementation, the predefined transmission periods may be hourly, every three hours, every four hours, every six hours, twice a day, once a day, or any other user-defined period.

[0099] The gateway 160 forwards the activation data to the remote computing device 110, which stores the received activation data by appending the activation data to a real-time database associated with the node device 320.

[0100] In some embodiments, a network of node devices is deployed across one or more sites. In such embodiments, the real-time database is associated with a client facility, wherein the client facility administers the site(s) at which the node devices are deployed.

[0101] The remote computing device 110 utilises one or more processors to process the received activation data, alone or in combination with other stored data from the real-time database, in order to generate reports. Reports may correlate dispenser usage with site specific data, to determine usage, maintenance schedules, and the like.

[0102] The remote computing device 110 provides a user interface in the form of a dashboard that is accessible by users, such as a user of the mobile computing device 190 of Fig. 1 or a user that uses a computing device to communicate with the remote computing device 110 via a communications network. The contents displayed on the dashboard may vary, depending on implementation and application. However, in some embodiments the dashboard provides one or more primary screens for administration and operation of the dispenser monitoring system. In this context, “administration” relates to the initial provisioning of client information, node devices and gateways; network and firmware updates. “Operations” relates to monitoring connectivity, errors and battery status, and monitoring and reporting dispenser usage.

[0103] In some embodiments, a software application (“app”) is associated with the dispenser monitoring system, wherein the app is installed on a mobile computing device, such as a smartphone or portable tablet. The app may be used by individuals whose job it is to replace empty dispensers. In some embodiments, the app provides an indication of when a dispenser is empty, based on a number of activations detected for that dispenser. In some embodiments, the app also indicates the type of product to be replaced in the respective dispenser. This is important, as different dispensers may be utilised for different products (e.g., soap, sanitiser, etc.) or the same products in different concentrations, depending on the location of the particular dispensers. On refilling a dispenser, the user is able to update the app. As the volume of each dispenser is known and the amount dispensed with each actuation of the dispenser is also known, the remote computing device 110 is able to monitor accurately the level of product in each dispenser under control of the dispenser monitoring system.

[0001] The dispenser monitoring system of the present disclosure may be practised using one or more computing devices, such as a general purpose computer, computer server, distributed cloud-based architecture, a combination thereof, or any similar architecture that is programmed to perform one or more of the functions shown and described in relation to Figs 1 to 4, thus giving rise to a new and improved computing device. In particular, the node device 320 and remote computing device 110 are advances in computer technology implemented utilising one or more computing devices.

[0002] Fig. 5 is a schematic block diagram of a system 500 that includes a general purpose computer 510. The general purpose computer 510 includes a plurality of components, including: a processor 512, a memory 514, a storage medium 516, input / output (I / O) interfaces 520, and input / output (I / O) ports 522. Components of the general purpose computer 510 generally communicate using one or more buses 548.

[0003] The memory 514 may be implemented using Random Access Memory (RAM), Read Only Memory (ROM), or a combination thereof. The storage medium 516 may be implemented as one or more of a hard disk drive, a solid state “flash” drive, an optical disk drive, or other storage means. The storage medium 516 may be utilised to store one or more computer programs, including an operating system, software applications, and data. In one mode of operation, instructions from one or more computer programs stored in the storage medium 516 are loaded into the memory 514 via the bus 548. Instructions loaded into the memory 514 are then made available via the bus 548 or other means for execution by the processor 512 to implement a mode of operation in accordance with the executed instructions.

[0004] One or more peripheral devices may be coupled to the general purpose computer 510 via the I / O ports 522. In the example of Fig. 5, the general purpose computer 510 is coupled to each of a speaker 524, a camera 526, a display device 530, an input device 532, a printer 534, and an external storage medium 536. The speaker 524 may be implemented using one or more speakers, such as in a stereo or surround sound system. In the example in which the general purpose computer 510 is utilised to implement one or more of the functions of a dispenser monitoring system, one or more peripheral devices may relate to node devices 134, 320 or gateways 160.

[0005] The camera 526 may be a webcam, or other still or video digital camera, and may download and upload information to and from the general purpose computer 510 via the I / O ports 522, dependent upon the particular implementation. For example, images recorded by the camera 526 may be uploaded to the storage medium 516 of the general purpose computer 510. Similarly, images stored on the storage medium 516 may be downloaded to a memory or storage medium of the camera 526. The camera 526 may include a lens system, a sensor unit, and a recording medium.

[0006] The display device 530 may be a computer monitor, such as a cathode ray tube screen, plasma screen, or liquid crystal display (LCD) screen. The display 530 may receive information from the computer 510 in a conventional manner, wherein the information is presented on the display device 530 for viewing by a user. The display device 530 may optionally be implemented using a touch screen to enable a user to provide input to the general purpose computer 510. The touch screen may be, for example, a capacitive touch screen, a resistive touchscreen, a surface acoustic wave touchscreen, or the like.

[0007] The input device 532 may be a keyboard, a mouse, a stylus, drawing tablet, or any combination thereof, for receiving input from a user. The external storage medium 536 may include an external hard disk drive (HDD), an optical drive, a floppy disk drive, a flash drive, solid state drive (SSD), or any combination thereof and may be implemented as a single instance or multiple instances of any one or more of those devices. For example, the external storage medium 536 may be implemented as an array of hard disk drives.

[0008] The I / O interfaces 520 facilitate the exchange of information between the general purpose computing device 510 and other computing devices. The I / O interfaces may be implemented using an internal or external modem, an Ethernet connection, or the like, to enable coupling to a transmission medium. In the example of Fig. 5, the I / O interfaces 522 are coupled to a communications network 538 and directly to a computingdevice 542. The computing device 542 is shown as a personal computer, but may equally be practised using a smartphone, laptop, or a tablet device. Direct communication between the general purpose computer 510 and the computing device 542 may be implemented using a wireless or wired transmission link.

[0009] The communications network 538 may be implemented using one or more wired or wireless transmission links and may include, for example, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, such as a Public Switch Telephony Network (PSTN), a mobile telephone cellular network, a short message service (SMS) network, or any combination thereof. The general purpose computer 510 is able to communicate via the communications network 538 to other computing devices connected to the communications network 538, such as the mobile telephone handset 544, the touchscreen smartphone 546, the personal computer 540, and the computing device 542.

[0010] One or more instances of the general purpose computer 510 may be utilised to implement one or more functions of remote computing device 110 of Fig. 1 . In such an embodiment, the memory 514 and storage 516 are utilised to store data relating to activation data, distribution of node devices, number of node devices, number of personnel, and the like. Software for implementing the dispenser monitoring system is stored in one or both of the memory 514 and storage 516 for execution on the processor 512. The software includes computer program code for implementing method steps in accordance with the functional modules described herein.

[0011] Fig. 6 is a schematic block diagram of a system 600 on which one or more aspects of a dispenser monitoring method and system of the present disclosure may be practised. The system 600 includes a portable computing device in the form of a smartphone 610, which may correspond to the computing device 190 of Fig. 1 to be used by a registered user of the dispenser monitoring system. The smartphone 610 includes a plurality of components, including: a processor 612, a memory 614, a storage medium 616, a battery 618, an antenna 620, a radio frequency (RF) transmitter and receiver 622, a subscriber identity module (SIM) card 624, a speaker 626, an input device 628, a camera 630, a display 632, and a wireless transmitter and receiver 634. Components of the smartphone 610 generally communicate using one or more bus connections 648 or other connections therebetween. The smartphone 610 also includes a wired connection 645 for coupling to a power outlet to recharge the battery 618 or for connection to a computing device, such as the general purpose computer 510 of Fig. 5. The wired connection 645 may include one or more connectors and may beadapted to enable uploading and downloading of content from and to the memory 614 and SIM card 624.

[0012] The smartphone 610 may include many other functional components, such as an audio digital-to-analogue and analogue-to-digital converter and an amplifier, but those components are omitted for the purpose of clarity. However, such components would be readily known and understood by a person skilled in the relevant art.

[0013] The memory 614 may include Random Access Memory (RAM), Read Only Memory (ROM), or a combination thereof. The storage medium 616 may be implemented as one or more of a solid state “flash” drive, a removable storage medium, such as a Secure Digital (SD) or microSD card, or other storage means. The storage medium 616 may be utilised to store one or more computer programs, including an operating system, software applications, and data. In one mode of operation, instructions from one or more computer programs stored in the storage medium 616 are loaded into the memory 614 via the bus 648. Instructions loaded into the memory 614 are then made available via the bus 648 or other means for execution by the processor 612 to implement a mode of operation in accordance with the executed instructions.

[0014] The smartphone 610 also includes an application programming interface (API) module 636, which enables programmers to write software applications to execute on the processor 612. Such applications include a plurality of instructions that may be preinstalled in the memory 614 or downloaded to the memory 614 from an external source, via the RF transmitter and receiver 622 operating in association with the antenna 620 or via the wired connection 645.

[0015] The smartphone 610 further includes a Global Positioning System (GPS) location module 638. The GPS location module 638 is used to determine a geographical position of the smartphone 610, based on GPS satellites, cellular telephone tower triangulation, or a combination thereof. The determined geographical position may then be made available to one or more programs or applications running on the processor 612.

[0016] The wireless transmitter and receiver 634 may be utilised to communicate wirelessly with external peripheral devices via Bluetooth, infrared, or other wireless protocol. In the example of Fig. 6, the smartphone 610 is coupled to each of a printer 640, an external storage medium 644, and a computing device 642. The computing device 642 may be implemented, for example, using the general purpose computer 510 of Fig. 5.

[0017] The camera 626 may include one or more still or video digital cameras adapted to capture and record to the memory 614 or the SIM card 624 still images or videoimages, or a combination thereof. The camera 626 may include a lens system, a sensor unit, and a recording medium. A user of the smartphone 610 may upload the recorded images to another computer device or peripheral device using the wireless transmitter and receiver 634, the RF transmitter and receiver 622, or the wired connection 645.

[0018] In one example, the display device 632 is implemented using a liquid crystal display (LCD) screen. The display 632 is used to display content to a user of the smartphone 610. The display 632 may optionally be implemented using a touch screen, such as a capacitive touch screen or resistive touchscreen, to enable a user to provide input to the smartphone 610.

[0019] The input device 628 may be a keyboard, a stylus, or microphone, for example, for receiving input from a user. In the case in which the input device 628 is a keyboard, the keyboard may be implemented as an arrangement of physical keys located on the smartphone 610. Alternatively, the keyboard may be a virtual keyboard displayed on the display device 632.

[0020] The SIM card 624 is utilised to store an International Mobile Subscriber Identity ( IMS I) and a related key used to identify and authenticate the user on a cellular network to which the user has subscribed. The SIM card 624 is generally a removable card that can be used interchangeably on different smartphone or cellular telephone devices. The SIM card 624 can be used to store contacts associated with the user, including names and telephone numbers. The SIM card 624 can also provide storage for pictures and videos. Alternatively, contacts can be stored on the memory 614.

[0021] The RF transmitter and receiver 622, in association with the antenna 620, enable the exchange of information between the smartphone 610 and other computing devices via a communications network 690. In the example of Fig. 6, RF transmitter and receiver 622 enable the smartphone 610 to communicate via the communications network 690 with a cellular telephone handset 650, a smartphone or tablet device 652, a computing device 654 and the computing device 642. The computing devices 654 and 642 are shown as personal computers, but each may be equally be practised using a smartphone, laptop, or a tablet device.

[0022] The communications network 690 may be implemented using one or more wired or wireless transmission links and may include, for example, a cellular telephony network, a dedicated communications link, a local area network (LAN), a wide area network (WAN), the Internet, a telecommunications network, or any combination thereof. A telecommunications network may include, but is not limited to, a telephony network, suchas a Public Switch Telephony Network (PSTN), a cellular (mobile) telephone cellular network, a short message service (SMS) network, or any combination thereof.

[0023] When one or more functions of the dispenser monitoring system described herein are implemented using the smartphone 610 of Fig. 6, a software application (“app”) executing on the processor 612 may be utilised to implement any one or more of the functions described and shown in relation to Figs 1 to 4. In some implementations, the app is a native app executing on the smartphone 600. In alternative implementations, the app is a web-based app displayed in a browser executing on the processor 612, with the smartphone 610 coupled to a remote server, such as the computing device 642, on which the app is executing.

[0024] Fig. 7A is a schematic diagram of a coin battery and measurement circuit that may be used in one or more embodiments as a power supply for the node device.

[0025] Fig. 7B is a schematic diagram of an alternative battery circuit that may be used in one or more embodiments as a power supply for the node device, in which power is provided by 2 AA (FR6 Lithium) batteries in series. Suitable batteries include the Energizer L91 PLCell FR6 AA.

[0026] Fig. 7C is a schematic diagram of a measurement circuit implemented using the XC9276 DC / DC converter chip from Torex Semiconductor Ltd.

[0027] Fig. 8 is a schematic diagram of a Bluetooth / Mesh MCU processor that may be used to implement the radio frequency transmitter 420 of Fig. 4. In the example of Fig. 8, the processor is the nRF52840 processor manufactured by Nordic Semiconductor. The nRF52840 processor provides protocol support for Bluetooth LE, Bluetooth mesh, Thread, Zigbee, 802.15.4, ANT and 2.4 GHz proprietary stacks.

[0028] Some embodiments utilise a power converter integral to a processor chip utilised to implement the radio frequency transmitter 420 of Fig. 4. Other embodiments utilise an external power converter, such as the XC9276 DC / DC converter chip from TOREX Semiconductor Ltd. Different implementations may have different magnetic sensitivity and / or radiofrequency (rf) transmission range.

[0029] Fig. 9A is a schematic diagram of a programming port to enable programming of the node device 320. Fig. 9B is a schematic diagram of a debug port for assistance in debugging the node device 320.

[0030] Figs 10A and 10B are schematic diagrams of circuitry for implementing an activation sensor, which may be utilised to implement the activation sensor 415 of Fig. 4. In the example of Fig. 10A, the activation sensor utilises the DRV5032FBDBZR processorfrom Texas Instruments, which is an ultra-low-power digital switch Hall effect sensor that can be used to implement a magnetic sensor for use with a paired sensor device implemented using a magnet. In the example of Fig. 10B, the activation sensor utilises the LSM303AGRTR processor from STMicroelectronics, with inputs from one or more of an accelerometer, a magnetometer, and a temperature sensor. The activation sensor determines actuation of a dispenser by detecting movement of a sensor device located on the dispenser.

[0031] Fig. 11 A is a schematic diagram of a first LED indication circuit that is used to illuminate a light emitting diode (LED) to indicate that the node device is powered and conforms with a manufacturing compliance test procedure.

[0032] Fig. 11 B is a schematic diagram of a second, alternative LED indication circuit that is used to illuminate a light emitting diode (LED) to indicate that the node device is powered and conforms with a manufacturing compliance test procedure.

[0033] Fig. 12A is a schematic diagram of a first circuit that includes an EEPROM memory module that may be utilised to store device configuration values. Fig. 12B is a schematic diagram of a second, alternative circuit that includes an EEPROM memory module that may be utilised to store device configuration values. In each of the examples of Fig. 12A and Fig. 12B, the EEPROM memory module is implemented using the AT24CS16-MAHM-E chip from Microchip Technology. It will be appreciated that many different EEPROM modules and circuits may equally be practised.

[0034] Fig. 13 is a schematic diagram of a NorFlash memory circuit that may be utilised in one or more embodiments to store data records associated with actuation of a dispenser. The flash memory can be utilised as a backup 'memory' when the network is unavailable or between the telemetry periodic publishing. In the example of Fig. 13, the NorFlash memory is implemented using the MX25R1635FZUIHO chip from Macronix International Co., Ltd, but other chips and circuits may equally be practised without departing from the spirit and scope of the present application.Industrial Applicability

[0104] The arrangements described are applicable to the cleaning, food, hospitality, healthcare, and service industries.

[0105] The foregoing describes only some embodiments of the present invention, and modifications and / or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.

[0106] Reference throughout this specification to “one embodiment”, “an embodiment,” “some embodiments”, or “embodiments” means that a particular feature, structure orcharacteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[0107] While some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0108] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

[0109] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practised without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

[0110] Note that when a method is described that includes several elements, e.g., several steps, no ordering of such elements, e.g., of such steps, is implied, unless specifically stated.

[0111] In the context of this specification, the word “comprising” and its associated grammatical constructions mean “including principally but not necessarily solely” or “having” or “including”, and not “consisting only of”. Variations of the word "comprising", such as “comprise” and “comprises” have correspondingly varied meanings.

[0112] Similarly, it is to be noticed that the term coupled should not be interpreted as being limitative to direct connections only. The terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other but may be. Thus, the scope of the expression “a device A coupled to a device B” should not be limited to devices or systems wherein aninput or output of device A is directly connected to an output or input of device B. It means that there exists a path between device A and device B which may be a path including other devices or means in between. Furthermore, “coupled to” does not imply direction. Hence, the expression “a device A is coupled to a device B” may be synonymous with the expression “a device B is coupled to a device A”. “Coupled” may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

[0113] As used throughout this specification, unless otherwise specified, the use of ordinal adjectives "first", "second", "third", “fourth”, etc., to describe common or related objects, indicates that reference is being made to different instances of those common or related objects, and is not intended to imply that the objects so described must be provided or positioned in a given order or sequence, either temporally, spatially, in ranking, or in any other manner.

[0114] Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms.

Claims

We claim:1 . A dispenser monitoring system comprising: a node device, said node device including: a sensor device adapted to be fitted to a dispenser; an activation sensor for detecting movement of said sensor device; a transmitter for transmitting activation data based on detected movement of said sensor device; and a remote computing device, said remote computing device including: a receiver for receiving said transmitted activation data; and a processor for executing computer instructions to: process said activation data; and generate at least one report based on said activation data.

2. The system according to claim 1 , wherein said sensor device includes: a collar adapted to be secured to said dispenser; and a magnet.

3. The system according to claim 2, wherein said collar includes a securing means selected from the group consisting of: a grub screw, a clip, adhesive, friction tape, and elasticated band.

4. The system according to any one of claims 1 to 3, wherein said activation sensor is implemented using at least one of a magnetometer and an accelerometer.

5. The system according to any one of claims 1 to 4, wherein the report includes a measure of compliance based on a correlation of number of activations of said dispenser and a number of users associated with the node device.

6. The system according to any one of claims 1 to 5, wherein said process of said remote computing device is adapted to provide a dashboard for display on a display device.

7. The system according to claim 6, wherein the dashboard displays information derived from the number of activations detected for the dispenser.

8. The system according to any one of claims 1 to 7, wherein said transmitter is adapted to transmit wirelessly in accordance with at least one wireless communication protocolselected from the group consisting of: Long Range (LoRa), Wi-Fi, Bluetooth, Zigbee, Z-Wave, 6L0WPAN, RFID, NFC, 4G / 5G, NB-IOT, and LTE.

9. The system according to any one of claims 1 to 8, wherein processing said activation data by said processor of said remote computing device includes: identifying a number of activations of said dispenser; and applying a time filter to identify which activations of said dispenser correspond to respective users.

10. The system according to claim 9, wherein identifying which activations of said dispenser correspond to respective users utilises a predefined time period, wherein said predefined time period is in the range of 1 second to 30 seconds.

11. A dispenser monitoring system comprising: a first network of at least one gateway device, each gateway device including: a radio frequency receiver for receiving activation data; and a transmitter for transmitting said activation data; a second network of a plurality of node devices, each node device being associated with a gateway device and each node device including: a sensor device adapted to be fitted to a dispenser; an activation sensor for detecting movement of said sensor device; and a radio frequency transmitter for transmitting, to an associated gateway device, activation data based on detected movement of said sensor device; and a remote computing device, said remote computing device including: a receiver for receiving said transmitted activation data from each of the gateway devices; a database; and a processor for executing computer instructions to: append said received activation data to said database; and generate at least one report based on said database.

12. The system according to claim 11 , wherein said database is associated with a client.

13. The system according to claim 12, wherein the plurality of node devices are distributed across multiple sites associated with the client.

14. The system according to any one of claims 11 to 13, wherein at least one of said reports relates a level of usage of the dispensers to which the sensor devices are fitted.

15. The system according to any one of claims 11 to 14, wherein at least one of said reports relates to at least one of: the number of dispenser actuations per dispenser; the number of dispenser actuations per region; compliance for a region based on number of known or detected users relative to dispenser actuations; and a heat map indicating the rate of dispenser actuation.

Images