Patent Description:
Systems dispensing consumable products are ubiquitous in many environments today. For example, hand towel dispensers are commonplace in many private, semi-private and public washrooms, work areas, food processing stations and kitchens. Monitoring and refilling such dispensers can be a time consuming and laborious endeavor requiring, in some scenarios, that an attendant or building maintenance team member routinely check each dispenser and refill or service as needed. This process inevitably results in checking a dispenser and determining that no refill is required, resulting in an unnecessary visit to the dispenser, which leads to building management inefficiencies and additional costs.

US <NUM>/<NUM> A1 discloses a dispensing system having the features of the preamble of claim <NUM>. AU <NUM><NUM><NUM> A1 discloses a system for monitoring a washroom including product dispensers.

In general, the subject matter of this specification relates to managing the servicing process of dispensers and other devices for efficient maintenance.

One aspect of the present invention provides a dispensing system in accordance with claim <NUM>.

Another aspect of the present invention provides a method in accordance with claim <NUM>.

For example, products (e.g., hand towels or hand soap) from all dispensers are not generally consumed at the same rate (e.g., dispensers nearest the exit may be depleted sooner or at a faster rate than other dispensers in the washroom at less convenient locations). Thus it often happens that some dispensers need to be refilled during regularly scheduled service visits as they are empty or near empty while other dispensers, which may have significant product remaining, don't need to be refilled at that time. However, when service personnel enter a washroom they do not always know which dispensers need servicing (e.g., need to be refilled with product or have a malfunction) until they open and/or try to operate the dispenser. Thus, it may be that a washroom includes ten dispensers and only one needs to be serviced. Unfortunately, the service attendants do not know which, if any, need to be serviced so they check all dispensers, which can be a time consuming process.

To avoid unnecessarily checking dispensers that do not need to be serviced, a controller in the washroom, which communicates with the dispensers, enters a service mode (e.g., as caused by the service attendant) that audibly signals to the service attendant which dispenser(s) need to be serviced and the cause for the servicing (e.g., refill or to correct a malfunction). This reduces or eliminates the need to visit dispensers that don't need to be serviced and, for those that do, provides an indication of the particular service need. Thus the controller informs service attendants which dispensers to service, which, in turn, leads to improvements in the operational efficiencies in the care of the washroom and reduces costs (e.g., by reducing unnecessary service visits).

The present disclosure generally relates to managing the servicing of dispensers (e.g., hygienic dispensers). In some implementations, the dispensing system includes a controller located in a hygiene environment, e.g., a washroom, that communicates with the dispensers in that environment to determine the state or status of the dispensers. Such state or status information may include whether the dispenser is malfunctioning, has a low battery, the amount of consumable product remaining or used in the dispenser, whether the dispenser is low on consumable product, etc..

When the washroom is scheduled or about to be serviced, the controller can enter a service mode in which it audibly and, optionally, visually communicates to a service technician which dispensers need to be serviced and, optionally, the nature of such service need. For example, when in the service mode, the controller verbally announces (e.g., speak) the identity of the dispensers that need to be serviced (e.g., the paper towel dispenser next to the sink, the bath tissue dispenser in the middle stall, or dispenser XYZ) and the particular type of service to be performed (e.g., low paper, low battery, paper jam) and the controller may cause lights on the dispensers that need to be serviced to flash or otherwise illuminate. Thus the service technician only needs to focus on the dispensers with a service need and can bypass the others.

In some implementations, the controller can communicate the state or status of some or all of the dispensers (including the ones without an immediate service need) so that the service technician can determine if any proactive servicing or maintenance is warranted, in addition to the dispensers with immediate service needs. The operation of such a dispensing system is described in more detail below with reference to <FIG>.

<FIG> is a block diagram of an example environment in which a dispensing system <NUM> can be implemented. The dispensing system <NUM> includes a plurality of dispensers <NUM> and a controller <NUM> or data processing system <NUM>. The environment can include, for example, a semi-private or public washroom or break room or another space in which the dispensers <NUM> are located. The dispensers <NUM> can include, for example, hand towel dispensers 104a, bath tissue dispensers 104b, hand soap (or other cleansing) dispensers 104c, air care and facial care dispensers (not pictured), surface cleaning, sanitizing or disinfecting dispensers (not pictured) including for toilets or urinals, and/or the like. These types of dispensers <NUM> generally dispense consumable hygiene products, which are products intended to promote good hygiene or sanitation such as by cleaning or sanitizing a user and/or a surface. A dispenser <NUM>, more generally, is a device that holds consumable product and dispenses the consumable product in response to a stimulus, e.g., an environmental stimulus (e.g., light/darkness), at pre-determined (e.g., programmatically set) intervals or by manual user actuation such as pulling an exposed portion of the consumable product or via a pumping-type process (e.g., for some manual soap dispensers).

As described above, the dispensing system <NUM> includes a controller <NUM>. The controller <NUM> can communicate with the dispensers <NUM> across wireless or wired channels, or some combination thereof. For example, in some implementations, the controller <NUM> includes a transceiver and microprocessor to facilitate such communications. The controller <NUM> is described in more detail below in reference to <FIG>. In some implementations, as described above, the controller <NUM> communicates with the dispensers <NUM> (and other devices such as mobile devices) through one or more wireless communication channels such as, for example, the BLUETOOTH protocol, mesh-based (e.g., ZIGBEE) protocols, and/or through a WAN or LAN.

In some implementations, the controller <NUM> receives (or requests) from the dispensers <NUM> product usage information, product remaining information (e.g., the number of dispenses since the last refill or report from the dispenser <NUM>) and/or state/status information (e.g., fault conditions such as jams or low battery alerts). The controller <NUM> can store this data for later access and use ("Dispenser Condition Information"). The dispensers <NUM> can send the reports/information, for example, periodically (e.g., hourly or daily or after certain dispenser events such as after each dispense, a set number of dispenses or a fault condition like a jam), upon the controller's request and/or upon a low product condition (e.g., only <NUM>% of the product remains). The reports can include time stamps indicating the date and time of each dispense and the identity of the dispenser (e.g., a unique identifier of the dispenser).

As described above, the controller <NUM> is located in or proximate to the washroom in which the dispensers <NUM> it manages are located, as shown in <FIG>. The controller <NUM> is remote to all or at least some of these dispensers <NUM>. For example, the controller <NUM> can be located on the ceiling of the washroom (e.g., to provide a good communication path to the dispensers <NUM>) with the dispensers <NUM> being located on walls, in stalls, on countertops, among other places.

<FIG> is block diagram of an example controller <NUM>. The controller <NUM> can include a processor <NUM>, a memory <NUM>, a storage device <NUM>, and an input/output device <NUM>. Each of the components <NUM>, <NUM>, <NUM>, and <NUM> can, for example, be interconnected using a system bus <NUM>. The processor <NUM> is capable of processing instructions for execution within the controller <NUM>. In one implementation, the processor <NUM> is a single-threaded processor. In another implementation, the processor <NUM> is a multi-threaded processor. The processor <NUM> is capable of processing instructions stored in the memory <NUM> or on the storage device <NUM>.

The memory <NUM> stores information within the controller <NUM>. In another implementation, the memory <NUM> is a non-volatile memory unit or a combination of volatile and non-volatile memory.

The storage device <NUM> is capable of providing mass storage for the controller <NUM>.

The input/output device <NUM> provides input/output operations for the controller <NUM>. In one implementation, the input/output device <NUM> can include one or more of a network interface device(s), e.g., an Ethernet card, a serial communication device, e.g., and RS-<NUM> port, a wireless interface device or a transceiver, e.g., an <NUM> card, BLUETOOTH interface, ZIGBEE interface.

The controller <NUM> has a speaker and can also include other communication device(s) <NUM>, e.g., display device, lights, microphone, speakers, to receive input data or information and/or send or communicate output data or information or indications to other input/output devices or users, e.g., service attendants.

In some implementations, the controller <NUM> is separate and distinct from each dispenser <NUM>. However, in other implementations, the controller <NUM> may be integral to a dispenser <NUM>, e.g., part of the same device such that the integrated dispenser-controller functions both a dispenser <NUM> and the controller <NUM>. Further, in some implementations, there may be multiple controllers <NUM> managing a washroom, e.g., multiple controllers <NUM> may be required as one controller <NUM> may not be able to communication with all dispensers <NUM> depending on the wireless propagation characteristics of the washroom. In this scenario, the multiple controllers <NUM> may communicate with each other with one being the master controller <NUM> and the others secondary controllers <NUM> or each controller <NUM> may independently manage its own set of dispensers <NUM>.

The controller <NUM> has a service mode and an operation mode. The operation mode is a mode in which the controller <NUM> routinely communicates with the dispensers (e.g., receiving Dispenser Condition Information) to, monitor and manage dispenser operation, as described above. The service mode is a mode in which the controller <NUM> leaves the operation mode (or runs with it simultaneously) to aid service attendants in servicing the washroom by providing (e.g., through itself or by causing another device to do so) audible indications and, optionally, visual indications identifying which of the dispensers <NUM> in the washroom need to be serviced based on the Dispenser Condition Information and, optionally, what that (those) service need(s) is (are). Among others, based on or derived from the Dispenser Condition Information, the servicing needs can include (a) low or no consumable hygiene product remaining status (e.g., indicating that so the service attendant should refill the dispenser <NUM>), (b) an electrical or mechanical malfunction (e.g., a paper jam) to alert the attendant that the dispenser is not operating properly and that remedial action is needed and (c) a low battery condition indicating that the battery in the dispenser needs to be changed.

The controller <NUM> can enter the service mode in one or more ways. For example, the controller <NUM> enters the service mode in response to a verbal command as received through the microphone <NUM> of the controller <NUM> and/or in response to detecting the presence of an attendant in the washroom, e.g., via detection of a location beacon on a service attendant or the attendant accessing a keypad. The controller <NUM> may also or alternatively enter the service mode in response to receipt of a communication from a device, e.g., a service attendant issues an instruction through an application (e.g., integrated with an API on the controller <NUM>) on his/her mobile phone or device to the controller <NUM> to cause the controller <NUM> to enter the service mode. Or enter the service mode at predetermined times, e.g., at times corresponding to the service schedule for the washroom or as otherwise programmatically set by a system administrator or user.

Once in the service mode, the controller <NUM> indicates dispenser service needs to the service attendant by using its speaker <NUM> to verbally announce the name or identifier of the dispenser <NUM> that needs servicing and the nature of the particular serving need for that dispenser <NUM>, e.g., refill, paper jam, etc. In some implementations, the controller <NUM> can additionally or alternatively identify a dispenser <NUM> that needs servicing by describing to the service attendant its location in the washroom and/or dispenser type, e.g., based on data pre-programmed into the controller <NUM>.

In some implementations, the controller <NUM> can indicate dispenser service needs to the service attendant, for example, by wirelessly communicating the name or identifier of the dispenser that needs servicing and, optionally, the nature of the particular serving need for that dispenser <NUM>. For example, the controller <NUM> can send this information to a handheld device of the service attendant for display. Additionally or alternatively, the controller <NUM> can include a light and use the light to shine on the dispenser <NUM> that needs serviced by based on accessing a stored, preprogrammed map of the washroom with dispenser location to determine where to shine the light.

In some implementations, as described above, the controller <NUM> can send an instruction to the dispenser <NUM> to cause the dispenser <NUM> with a service need to visually (e.g., flashing a light or actuating a dispense or partial dispense cycle) or audibly (e.g., beeping) indicate it needs to be serviced. In some implementations, the controller <NUM> can additionally verbally identify the dispenser <NUM> and/or its servicing need while the dispenser <NUM> also indicates it needs to be serviced.

In some implementations, the controller <NUM> can indicate the dispensers' service needs in a batch form, e.g., one immediately after the other, or one-at-a-time and wait to indicate the next dispenser/service need until either the current dispenser <NUM> has been serviced, after a prescribed period of time (e.g., as set by an administrator), or as otherwise requested to by the service attendant. At any point, in response to a request from the service attendant, e.g., through the attendant's handheld device or verbally, the controller <NUM> can repeat any or all of the servicing needs.

In some implementations, after a dispenser <NUM> has been serviced the controller <NUM> can receive input from the service technician of such (or at the next report received from the dispenser <NUM>) and record that service event as having been completed. In response to receiving input that a dispenser <NUM> has been serviced, the controller <NUM> can provide a positive reinforcement communication to the attendant, for example, by playing music or speaking a positive message.

The controller <NUM> can re-enter the operation mode after all dispensers <NUM> have been serviced, after a pre-determined period or in response to instructions from the service attendant.

<FIG> is a flow chart of an example process for managing dispensers <NUM>. The dispensing system <NUM> performs the steps described with reference to <FIG>. In accordance with the present invention, the steps include providing an audible indication of a servicing need by verbally speaking both the servicing need of a dispenser <NUM> and its identifier through the speaker <NUM> of the controller <NUM>.

Although the above description has focused on serving dispensers in a washroom, the technology is applicable to other environments in which a central controller is managing remote devices that need to be serviced.

Implementations or aspects of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus.

The operations described in this specification can be implemented as operations performed by a data processing apparatus or system on data stored on one or more computer-readable storage devices or received from other sources.

The term data processing apparatus or data processing system encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing.

Implementations of the subject matter described in this specification may, in some implementations, be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.

Claim 1:
A dispensing system comprising:
a plurality of dispensers (<NUM>) each configured to be located in a same washroom and dispense a respective consumable hygiene product, wherein each of the plurality of dispensers (<NUM>) has an identifier; and
a controller (<NUM>) configured to be located in the washroom, remote to the plurality of dispensers (<NUM>) and having a service mode and an operation mode different than the service mode, the controller (<NUM>) configured to receive a request to enter into the service mode and to enter into the service mode in response to receiving the request, wherein the controller (<NUM>) has a speaker (<NUM>),
wherein, when in the service mode, the controller (<NUM>) is configured cause an audible indication of a servicing need of at least one of the plurality of dispensers (<NUM>), and wherein the servicing need is one of the at least one of the plurality of dispensers (<NUM>) having:
low or no consumable hygiene product remaining,
an electrical or mechanical malfunction, and
a low battery condition,
characterized in that:
when in the service mode, the controller (<NUM>) is configured to verbally speak both the servicing need of the at least one of the plurality of dispensers (<NUM>) and its identifier.