Restroom Maintenance Automation System

Abstract

A restroom management system, the restroom management system having: a sensor, the sensor is used to generate operability level data of a restroom component; a controller, the controller is used to modify the operation of the restroom component; and a central management system, the central management system is used to access the operability level data, communicate with the controller and evaluate the operability data to determine the actionable event type of the restroom component, and the central system is further configured to place the restroom component in the problem-solving state in response to determining that the event type is the automatic resolution event, and then place the restroom component in one of the normal operating state or the disabled state based on evaluating the operability level data after the problem-solving state; and in response to determining that the event type is the assisted resolution event, keep the restroom component in the normal operating state or place it in the disabled state, and cause a message to be sent to an attendant.

Description

[0001] This application claims priority to U.S. Provisional Patent Application Serial No. 62 / 678,363, filed on May 31, 2018, the entire contents of which are incorporated herein by reference. Background Art

[0002] The present disclosure is directed to automating (or semi-automating) certain aspects of restroom service and maintenance.

[0003] Systems range in use in restrooms from toilet paper and toilet paper dispensers to toilets and urinals. Servicing such systems can be a time-consuming endeavor, as a personal visit may be required each time a maintenance need arises. In addition, timely cleaning or repairs (e.g., refilling toilet paper, hand towel, and soap dispensers), user satisfaction, and providing good sanitation require that any system failures or depleted dispensers, for example, be addressed quickly. However, keeping restrooms clean and well-stocked can be a challenge, given the limited resources available to service restrooms at most facilities. Summary of the invention

[0004] Generally speaking, the subject matter of this specification relates to automating (or semi-automating) restroom repair and maintenance.

[0005] Generally speaking, one aspect of the subject matter described in this specification can be implemented in a system that includes a functional sensor configured to generate operability level data of a restroom component that defines a state of the restroom component; a controller configured to modify the operation of the restroom component, wherein the restroom component has a normal operating state, a problem solving state, and a disabled state, wherein the normal operating state is a normal function of the restroom component, the problem solving state is used to perform maintenance on the restroom component, and the disabled state is used to disable the restroom component to stop it from operating; and a central management system configured to access the operability level data, communicate with the controller, and evaluate the operability data to determine a restroom component state. The actionable event type of the hand rest component, wherein the actionable event type includes an automatic resolution event and an assisted resolution event, and the central management system is further configured to, in response to determining that the actionable event type is an automatic resolution event, cause the controller to place the restroom component in a problem-solving state for a predetermined period of time or sequence, and then place the restroom component in one of a normal operating state or a disabled state based on the evaluation of the operability level data after the problem-solving state; and in response to determining that the actionable event type is an assisted resolution event, cause the controller to keep the restroom component in a normal operating state or place the restroom component in a disabled state based on the operability level data, and cause a message to be sent to a restroom attendant to repair the restroom component. Other embodiments of this aspect include corresponding methods, apparatus, and computer program products.

[0006] Another aspect of the subject matter described in this specification can be implemented by the following method, which includes: accessing operability data of the state of a specified toilet component from a sensor; analyzing the operability data to determine an actionable event type for the toilet component, wherein the actionable event type includes an automatic resolution event and an assisted resolution event; in response to determining that the actionable event type is an automatic resolution event, instructing the toilet component to enter a problem resolution state, and then after the problem resolution state, based on an evaluation of the operability level data, instructing the toilet component to enter one of a normal operating state or a disabled state; and in response to determining that the actionable event type is an assisted resolution event, instructing the toilet component to enter a normal operating state or a disabled state based on an evaluation of the operability level data. Other embodiments of this aspect include corresponding systems, devices, and computer program products.

[0007] The specific embodiment of the theme described in this specification can be implemented to realize one or more of the following advantages.For example, it is time-consuming and expensive to repair a restroom, because each maintenance event usually requires a maintenance service person to visit the restroom and perform maintenance.In many cases, the service person is arranged on a fixed schedule, and even if maintenance is currently required, the restroom is only visited at a specified time.The restroom maintenance automation system can eliminate the need for maintenance visits in some cases, and assist maintenance needs in other cases.Because the number of maintenance visits of the service person can be reduced or the workload required during the visit can be minimized, for example, because the restroom maintenance automation system may have solved some maintenance needs without the participation of the service person, the cost associated with the maintenance of the restroom is reduced.The restroom maintenance automation system can also improve the user's satisfaction with the restroom, because the restroom can be repaired when it needs maintenance, and it is not necessary to always wait for the next scheduled maintenance visit of the service person, so that the restroom can be in a state of disrepair until the next visit after a few days or weeks.

[0008] The details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1A is a block diagram of an exemplary environment in which a restroom maintenance automation system may be implemented.

[0010] Figure 1B is a right side cross-sectional view of an exemplary dispenser.

[0011] Figure 1C for Figure 1B Perspective view of a dispenser.

[0012] Figure 1D Side cutaway view of a toilet with the valve closed.

[0013] Figure 1E For valve open Figure 1D Side cutaway view of a toilet bowl.

[0014] Figure 2 A flow chart illustrating the operation of an exemplary restroom maintenance automation system.

[0015] Like reference numbers in the various drawings indicate like elements. DETAILED DESCRIPTION

[0016] The present disclosure as a whole relates to automating or semi-automating restroom maintenance tasks, such as clearing a clogged drain in a urinal or toilet or clearing a paper jam in a dispenser, and otherwise assisting with restroom maintenance. In some embodiments, a restroom system facilitates such automation or semi-automation, and the system includes: a sensor that monitors the functional state of a restroom component (e.g., a dispenser, toilet, urinal, sink, etc.); a controller that is used to change the operation of the restroom component from a normal operating state to a problem-solving state or a disabled state, and then back; and a central management system that indicates to the controller which state the restroom component should be in based on the functional state of the restroom component.

[0017] For example, a restroom has a toilet, and the restroom maintenance system includes a sensor that monitors the water level in the toilet tank, a first controller that controls the position of a water valve in a water supply pipe that supplies water to the toilet, and a second controller that controls an actuator to flush the toilet. In response to the sensor reporting a high water level, indicating that there may be a blockage, the system can cause the second controller to flush the toilet two or more times in a row to try to clear the blockage. Or the system can cause the controller to activate a dispenser in the toilet to release a dissolving agent into the tank in an attempt to clear the blockage. In these ways, the system automates the maintenance of the toilet. If after these flushes or treatments, the sensor reports a normal water level, the system 102 determines that the blockage has been cleared and the toilet is in normal operation.

[0018] However, if the sensor continues to report a high water level, the system can cause the first controller to close the valve to prevent the toilet from overflowing. In addition, the system can send a message to alert a service person that the toilet requires additional maintenance. In this way, the system assists in the maintenance of the toilet. The operation of such a restroom maintenance system is described in more detail below.

[0019] Restroom components include, for example, a dispenser 104, a sink / faucet 134, a toilet 130, and a urinal 136, as shown in FIG. Figure 1A, which is a block diagram of an exemplary environment in which the restroom maintenance automation system 100 may be implemented. Figure 1A The environment in also includes a central management system (e.g., a data processing device) 102, and in some embodiments, a gateway 139 to facilitate communication between the restroom components and the central management system 102. In some embodiments, the gateway 139 is a router or other network communication device. In some embodiments, the restroom components and the central management system 102 can communicate directly on a wireless or wired channel, or some combination thereof, or communicate through an intermediary. For example, the central management system 102 includes a transceiver and a microprocessor to facilitate such communication.

[0020] As described above, the lavatory component may include a dispenser 104 . Figure 1B is a right side cross-sectional view of an exemplary dispenser 104, and Figure 1C yes Figure 1B 104 . A dispenser 104 or hygienic dispenser 104 dispenses a consumable hygienic product 105 (e.g., toilet paper, hand towels, hand sanitizer, soap, lotion, deodorant, air freshener, etc.) that is intended to promote good hygiene or sanitation, such as by cleaning or disinfecting a user and / or a surface. In some embodiments, more generally, the dispenser 104 is a device that holds a consumable hygienic product 105 and dispenses the product 105 at predetermined (e.g., programmatically set) intervals in response to a stimulus such as an environmental stimulus (e.g., light / darkness) or by manual user actuation such as pulling out an exposed portion of the consumable or via a pump-type process (e.g., for some manual soap dispensers). Although Figure 1B A roll product dispenser 104 (e.g., a paper towel dispenser 104a) is shown, but other sanitary dispensers are also contemplated, including, for example, a soap / disinfectant dispenser 104c for a toilet 130 or urinal 136, etc., a bath towel dispenser 104b, an air freshener dispenser (not shown), a hand or facial care product dispenser (not shown), a seat cushion dispenser (not shown), a surface cleaning, disinfecting or sterilizing dispenser (not shown). Such dispensers 104 are typically refillable so that once the product 105 stored in the dispenser 104 is exhausted, a maintenance service person can refill the dispenser 104 with additional product 105.

[0021] The dispenser 104 includes a body 107 or an outer cover 107, such as a composite housing or a metal housing. The outer cover 107 completely or partially encloses a product holding area 102 or interior 102 of the dispenser 104. The product holding area 102 holds, for example, a product 105 to be dispensed by the dispenser 104, and in some embodiments, holds one or more electrical or mechanical components for implementing the dispensing process, such as a motor, a battery, a roller, a sensor to determine when a user desires a dispense, etc., as described in more detail below.

[0022] The dispenser 104 also includes a dispensing mechanism 110. The dispensing mechanism 110 operates to dispense a portion of the consumables 105 in the holding area 102 (e.g., dispensing a length of roll paper 105 for drying hands or dispensing a small piece of soap 105 or disinfectant to clean hands). In some embodiments, for example, for roll paper towels 105 or wipes 105 or toilet paper 105, the dispensing mechanism 110 is an electromechanical feeding mechanism that includes a motor 119 or operates in conjunction with the motor, which feeds a length of roll paper 105 through an opening 123 in the body 107 to present it to the user in response to a stimulus such as a user waving a hand near the dispenser 104. For example, the dispensing mechanism 110 may include a series of rollers 122 through which a portion of the roll 105 is fed, so that when the dispensing mechanism 110 is actuated, it pulls and unwinds the roll 105 (or causes the roll 105 to be pulled and unwinded) to feed a portion of the roll 105 to the user. In some embodiments, the motor 119 can be integral with the roll holder 106 and cause the spindle 109 of the roll holder 106 (e.g., on which the roll product 105 is mounted) to rotate, thereby enabling the roll 105 to be unwound and dispensed. In the case of a liquid soap or disinfectant or lotion dispenser 104, for example, the motor 119 can be a pump 119 that draws the liquid product 105 from a bottle, box, or other container containing the liquid product and sprays the drawn product to the user to achieve the dispensing operation.

[0023] In some embodiments, the dispenser 104 is a user-driven dispensing unit, e.g., the dispensing process is not powered by a motor or other electromechanical generator. For example, for a roll-type paper product dispenser 104, such as a paper towel or toilet paper dispenser 104, a user can grab the exposed tail of the roll 105 and pull to dispense more product 105. For a liquid soap or disinfectant dispenser 104, a user can depress or otherwise manually actuate a pump (e.g., a dispensing mechanism 110) to draw the product 105 from its container and dispense the product 105.

[0024] In some embodiments, the dispenser 104 includes a processor 118, such as a microprocessor or microcontroller 118. The processor 118 is a device that executes instructions stored in a memory or otherwise accessible by the processor 118. The processor 118 interfaces with other devices / components in the dispenser 104 that can be used to communicate with external devices, such as a motor 119 and a transceiver 117, and in some embodiments controls their operation. The dispenser also includes a functional sensor 116, as described in more detail below.

[0025] As mentioned above, the lavatory components may include a toilet 130, among other components. Figure 1D A side cross-sectional view of toilet 130 with valve 132 closed, and Figure 1E For valve 132 to be opened Figure 1D A side cross-sectional view of a toilet 130. When the valve is in the open position ( Figure 1D ), water can fill the water tank for normal operation. When valve 132 is closed ( Figure 1C ), preventing water from filling the tank.

[0026] The system 100 includes a functional sensor 116 coupled directly or indirectly to a corresponding restroom component. A functional sensor 116 is a device that generates or determines operability level data that defines a mechanical or operational state or status of a corresponding restroom component or associated product 105, as applicable. Exemplary functional sensors 116 include consumable (e.g., product 105) level sensors, water flow sensors, flush valve sensors, and motor current sensors.

[0027] The consumable level sensor 116 tracks, for example, the amount of product 105 remaining in the dispenser 104 or the amount of product 105 used in the dispenser 104 since the last refill. An exemplary consumable level sensor 116 is an arm mounted on a pivot at one end and disposed at the other end at the periphery of the roll of paper product 105. As the roll 105 is used, its diameter decreases and the arm pivots causing its angular displacement to change. The change in angular displacement can be used to determine the amount of product 105 used.

[0028] As another example, the consumable level sensor 116 is an infrared or sonic detection system that measures the distance between itself and the product 105, and changes in this distance can be used to track the product 105 being used. For example, as a roll of paper towels 105 is used, its diameter decreases, and the sensor 116 can detect and measure this decrease. Or as a stack of folded paper towels 105 is used, the height of the stack decreases, and the sensor 116 can detect and measure this decrease in height, which in turn can be used to determine the amount of product 105 that has been used or remains.

[0029] In some embodiments, mass sensor 116 may be used to measure the decrease in weight of product 105 as product 105 is depleted. This change in weight may be used to determine the amount of product 105 remaining.

[0030] Functional sensors 116 may include water flow sensors 116. Exemplary water flow sensors 116 include positive displacement flow meters and piston flow meters. Water flow sensors 116 may be used to determine whether water is being discharged from, for example, sink 134, toilet 130, or urinal 136. As described above, functional sensors 116 may also include flush valve sensors 116. Flush valve sensors 116 may be contact position sensors, potentiometers, piezoelectric transducers, etc. Flush valve sensors 116 may be positioned to trigger when, for example, a toilet or urinal handle is actuated to cause a flush. Functional sensors 116 may also include motor current sensors 116. Motor current sensors 116 detect the amount of current drawn by a motor (e.g., motor 119). Exemplary motor current sensors 116 include Hall effect sensors and may, for example, determine current usage in dispenser 104, including overcurrent conditions indicating a blockage or other fault.

[0031] System 100 includes one or more controllers 133. Controller 133 is a device that modifies or changes the operating state of toilet components. In some embodiments, controller 133 is or includes a data processing device (e.g., a microcontroller) that communicates with certain features and functions of toilet components and controls certain features and functions of toilet components. For example, controller 133 may include (or control) an actuator to control a water flow valve 132 or a switch to control motor 119 to manage the operation of toilet components. Controller 133 may be located at the same location as toilet components or away from toilet components. In some embodiments, one controller 133 manages one toilet component. In other embodiments, multiple controllers 133 manage the operating state of toilet components. In other embodiments, one controller 133 manages multiple toilet components.

[0032] As described above, the system 100 also includes a central management system 102. The system 102 can communicate with the functional sensors 116 to receive operability data (or otherwise access operability data) from one or more restroom components. In some embodiments, the system 102 periodically polls the sensors 116 to collect operability data, the sensors 116 push data to the system 102 on a predetermined schedule, the sensors 116 (or restroom components) send data to the system 102 in response to detecting abnormal operability data (e.g., data outside the specifications or parameters set by the administrator), or some combination thereof. The system 102 can evaluate the operability data to determine the actionable event type for each restroom component, which can be an automatic resolution event or an assisted resolution event.

[0033] An actionable event is a maintenance or repair need for a restroom component. For example, an actionable event is a low product 105 condition of a dispenser 104, i.e., the dispenser 104 is running low on product 105, a malfunction of a dispenser 104, such as a paper jam or dead batteries, or a malfunction of a toilet 130, urinal 135, or sink 134 (such as a water blockage / blocked pipe). An automated resolution event is an event that the system 102 determines, at least initially, does not require service personnel intervention to resolve a maintenance or repair need. An assisted resolution event is an event that the system 102 determines requires service personnel intervention to fully resolve a maintenance or repair need.

[0034] At least in part in response to the type of actionable event and the outcome of its attempted resolution, the system 102 causes the controller 133 to place the restroom component in one of three operating states: (i) a normal operating state, (ii) a problem-solving state, and (iii) a disabled state. The normal operating state defines that the restroom component is operating normally, for example, within the manufacturer's standard operating specifications. The problem-solving state defines that the restroom component requires maintenance. The disabled state defines that the restroom component has been disabled to prevent the restroom component from functioning / operating, for example, in the disabled state, the dispenser 104 will not dispense the product 105, and the toilet 130 will not flush.

[0035] You can refer to the following Figure 2 Describing the functionality of the system 100 , the figure is a flow chart 200 of the operation of an exemplary restroom maintenance automation system 100 .

[0036] The operability data is evaluated (202). Based on the evaluation, the system 102 determines whether an actionable event exists. For example, the system 102 may determine whether an actionable event exists (if the operability data levels / states require an actionable event) based on a comparison of the operability data to a predetermined lookup table or other mapping of various operability data levels or states and corresponding actionable event types. In some embodiments, each restroom component has its own lookup table that can be updated by an administrator and accessed by the system 102. Thus, based on the evaluation of the operability data, the system 102 may determine that an actionable event exists and that the actionable event is of an automatic resolution type (204) or an assisted resolution type (212), or that an actionable event does not exist when the operability data indicates that the restroom component is operating within normal operating parameters.

[0037] In response to determining that the actionable event is of the automatic resolution type, the system 102 instructs the controller 133 to place the restroom component in a problem-solving state (206). For each restroom component, there may be multiple problem-solving states. The system determines the specific problem-solving state to place the component in based on the operability data (e.g., based on a lookup table). For example, the functional sensors of the toilet 130 are a flush valve sensor and a water flow sensor, and the system 102 evaluates the operability data, for example, in response to a flush valve actuation from the flush valve sensor, by analyzing a water flow reading from the water flow sensor and comparing the water flow reading to a predetermined water flow parameter. If the system 102 determines from the evaluation that the toilet 130 is clogged, the system 102 determines (e.g., based on the instructions in the lookup table) that the problem-solving state for the clog is to flush the toilet 130 three times. The system 102 then accesses the operability data after the problem-solving state (e.g., the flushing process in the above example) (returning to step 202). More generally, when the controller 133 places the restroom component in the problem-solving state, it will last for a predetermined sequence (eg, three flushes) or time period (30 seconds of flushing).

[0038] If the operability data indicates that the same problem resolution state exists after the problem resolution process (e.g., three flushes), the system 102 instructs the controller 103 to place the toilet component in a disabled state (208) to prevent further use of the toilet component. The system also causes a predetermined message to be sent to a service person to repair the toilet component, and in some embodiments, the message includes a specific problem resolution state (218). In some embodiments, for a specific problem resolution state of certain toilet components, the system 102 can cause other toilet components to be placed in a disabled state, for example based on instructions in a lookup table. For example, if the toilet 130 is blocked and the problem cannot be solved by the automatic resolution process, the system 102 can cause the controller 133 of the toilet 130 to disable the toilet 130, such as rotating the water valve 132 to close the toilet 130, and optionally, cause the controller 133 of the toilet paper dispenser 104 of the toilet 130 to also enter a disabled state to prevent the user from putting (additional) toilet paper 105 into the blocked toilet 130 and making the blockage worse.

[0039] However, if system 102 determines that the fault or maintenance requirement no longer exists because the fault or maintenance was resolved during the problem resolution state, system 102 instructs controller 133 to return the restroom component to a normal operating state according to predetermined instructions (e.g., set or programmed by an administrator) (210).

[0040] In response to determining that the actionable event is of the assisted resolution type, the system 102 instructs the controller 133 to place the restroom component in a normal operating state (216) or a disabled state (214) according to a lookup table or other pre-specified instructions. For example, the operability data for the paper towel dispenser 104 may indicate that the product 105 in the dispenser 104 is low and needs to be refilled. In response, the system 102 instructs the controller 133 of the dispenser 104 to maintain the dispenser 104 in the normal operating state because the dispenser 104 is operating normally, but the paper 105 is running low. However, when the restroom component will require maintenance, the system 102 causes a predetermined message to be sent to the service personnel to repair the restroom component, and in some embodiments, the message includes the reason for the specific assisted resolution state (218).

[0041] As another example, the operability data of the paper towel dispenser 104 may indicate that the product 105 in the dispenser 104 is completely depleted and needs to be refilled. In response, the system 102 instructs the controller 133 of the dispenser 104 to place the dispenser 104 in a disabled operating state (e.g., disabling the motor 119 and / or flashing an indicator light to indicate that the product 105 in the dispenser 104 is depleted) because the dispenser 104 cannot operate without the product 105. When the restroom component requires (e.g., immediate) maintenance, the system 102 causes a predetermined message to be sent to a service person to repair the restroom component, which in some embodiments includes a specific reason to assist in resolving the state (218).

[0042] Referring to yet another example, system 102 may evaluate operability data for toilet 130 and determine (e.g., based on data from flush and water flow sensors) that the toilet is completely clogged, and in response, instruct controller 133 to place toilet 130 in a disabled state (e.g., as part of an assisted resolution event type) and cause a predetermined message to be sent to a service person to repair toilet 130, which in some embodiments includes a specific reason for the disabled state (218).

[0043] In some embodiments, the system 100 analyzes operability data from multiple toilet components to determine whether an actionable event has occurred, and if so, the type of actionable event. In some embodiments, the system 102 can access first operability data from a first sensor specifying consumable usage from a first toilet component, and second operability data from a second sensor specifying an operational state of a second toilet component. For example, the system 102 analyzes the first operability data set and the second operability data set (e.g., from the same time period), and determines high consumable usage from a first toilet component (e.g., a toilet paper dispenser 104 with abnormally high usage), and a low operational state of a second toilet component (e.g., a toilet 130 with an outlet water flow rate lower than a normal water flow rate). Therefore, based on predefined instructions, the system 102 can determine that an excess of toilet paper 105 is deposited in the toilet 130, resulting in a blockage. The system 102 can then take necessary actions to remedy the situation (e.g., step 204 or step 212).

[0044] Implementation

[0045] Embodiment 1. A toilet management system, comprising:

[0046] a function sensor configured to generate operability level data of a restroom component defining a state of the restroom component; a controller configured to modify the operation of the restroom component, wherein the restroom component has a normal operation state, a problem resolution state, and a disabled state, wherein the normal operation state is a normal function of the restroom component, the problem resolution state is used to perform maintenance on the restroom component, and the disabled state is used to disable the restroom component from operating; and a central management system configured to access the operability level data, communicate with the controller, and evaluate the operability data to determine an actionable event type for the restroom component, wherein the actionable event The types include automatic resolution events and assisted resolution events, and the central management system is further configured to: in response to determining that the actionable event type is the automatic resolution event, cause the controller to place the restroom component in the problem resolution state for a predetermined time period or sequence, and then place the restroom component in one of the normal operating state or the disabled state based on evaluating the operability level data after the problem resolution state; and in response to determining that the actionable event type is the assisted resolution event, cause the controller to maintain the restroom component in the normal operating state or place the restroom component in the disabled state based on the operability level data, and cause a message to be sent to a restroom service personnel to repair the restroom component.

[0047] Embodiment 2. A system as described in embodiment 1, wherein the restroom component includes one of a paper towel dispenser, a urinal, a toilet, a toilet paper dispenser, a faucet, a soap dispenser, and a disinfectant dispenser.

[0048] Embodiment 3. A system as described in Embodiment 1 or 2, wherein the functional sensor includes at least one of a consumable level sensor, a water flow sensor, a flush valve sensor, and a motor current sensor.

[0049] Embodiment 4. The system of any of the preceding embodiments, wherein in the automatic resolution event and in response to placing the restroom component in the disabled state, includes causing a message to be sent to restroom attendant to repair the restroom component.

[0050] Embodiment 5. The system of any of the preceding embodiments, wherein the auxiliary resolution event is refilling the restroom component with a consumable product.

[0051] Embodiment 6. The system of any of the preceding embodiments, wherein the problem resolved state comprises actuating the toilet component one or more times.

[0052] Embodiment 7. A system as described in Embodiment 1, wherein the restroom component includes a toilet or a urinal, the functional sensor includes a flush valve sensor and a water flow sensor, and evaluating the operability data includes determining a water flow reading from the water flow sensor in response to a flush valve actuation from the flush valve sensor, and comparing the water flow reading to a predetermined water flow parameter.

[0053] Embodiment 8. The system of embodiment 7, wherein the predetermined time period or sequence for the problem resolution state includes flushing the toilet or urinal a specified number of times.

[0054] Embodiment 9. The system of Embodiment 7, wherein the disabled state comprises causing the toilet or the urinal to not flush.

[0055] Embodiment 10. A method comprising accessing operability data of an operating state of a specified restroom component from a sensor; analyzing the operability data to determine an actionable event type for the restroom component, wherein the actionable event type includes an automatic resolution event and an assisted resolution event; in response to determining that the actionable event type is the automatic resolution event, instructing the restroom component to enter the problem resolution state, and then after the problem resolution state, based on an evaluation of the operability level data, instructing the restroom component to enter one of the normal operating state or the disabled state; and in response to determining that the actionable event type is the assisted resolution event, instructing the restroom component to enter the normal operating state or the disabled state based on an evaluation of the operability level data.

[0056] Embodiment 11. The method of embodiment 10, wherein responsive to determining that the actionable event type is the assisted resolution event includes instructing that a message be sent to restroom attendant to repair the restroom component.

[0057] Embodiment 12. The method of embodiment 10 or 11, wherein the restroom component comprises one of a paper towel dispenser, a urinal, a toilet, a toilet paper dispenser, and a faucet.

[0058] Embodiment 13. A method as described in Embodiment 10, 11 or 12, wherein the sensor includes at least one of a consumable level sensor, a water flow sensor, a flush valve sensor and a motor current sensor.

[0059] Embodiment 14. The method of embodiment 10, wherein in the automatic resolution event and in response to indicating that the restroom component entered the disabled state includes instructing that a message be sent to restroom attendant to repair the restroom component.

[0060] Embodiment 15. The method of Embodiment 10, 12, or 13, wherein analyzing the operability data includes determining that the restroom component is blocked or partially blocked and determining that the actionable event type is the auto-resolve event type.

[0061] Embodiment 16. The method of Embodiment 10, 12, or 13, wherein analyzing the operability data includes determining that the restroom component is completely blocked, and determining that the actionable event type is the assisted resolution event type.

[0062] Embodiment 17. A method comprising accessing first operability data from a first sensor specifying consumable product usage from a first restroom component, and second operability data from a second sensor specifying an operating state of a second restroom component; analyzing the first operability data and the second operability data to determine an actionable event type for the restroom, wherein the actionable event type includes an automatic resolution event and an assisted resolution event, and the analysis includes determining high-consumable product usage from the first restroom component and determining a low operating state of the second restroom component; in response to determining that the actionable event type is the automatic resolution event, after the problem resolution state, based on an evaluation of the operability level data, indicating that the restroom component in the restroom enters one of the normal operating state or the disabled state; and in response to determining that the action event type is the assisted resolution event, based on an evaluation of the operability level data, indicating that the restroom component enters the normal operating state or the disabled state.

[0063] Embodiment 18. The method of embodiment 17, wherein the first lavatory component is a toilet paper or paper towel dispenser and the second lavatory component is a toilet or urinal.

[0064] Implementations of the subject matter and operations described in this specification may 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 combinations of one or more of them. Implementations of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage medium for execution by a data processing device or for controlling the operation of the data processing device. Alternatively or in addition, the program instructions may be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device for execution by the data processing device.

[0065] A computer storage medium may be, or may be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. In addition, although a computer storage medium is not a propagated signal, a computer storage medium may be a source or destination of computer program instructions encoded in an artificially generated propagated signal. A computer storage medium may also be, or may be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).

[0066] The operations described in this specification may 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.

[0067] The term data processing equipment or data processing system covers all kinds of equipment, devices and machines for processing data, including, for example, programmable processors, computers, systems on chip, or multiple or combinations of the foregoing. The equipment may include special logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits). In addition to hardware, the equipment may also include code that creates an execution environment for the computer program in question, such as code that constitutes processor firmware, protocol stacks, database management systems, operating systems, cross-platform runtime environments, virtual machines, or a combination of one or more of them. The equipment and execution environment can implement a variety of different computing model infrastructures, such as web services, distributed computing, and grid computing infrastructures.

[0068] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including assembly or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing portions of one or more modules, subroutines, or codes). A computer program may be deployed to execute on a single computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communication network.

[0069] The processes and logic flows described in this specification may be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows may also be performed by, and the device may be implemented as, a dedicated logic circuit such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0070] Processors suitable for executing computer programs include, for example, general-purpose microprocessors and special-purpose microprocessors, and any one or more processors of any kind of digital computer. In general, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic element of a computer is a processor for performing actions according to instructions, and one or more memory devices for storing instructions and data. In general, a computer will also include one or more large-capacity storage devices for storing data, such as a disk, a magneto-optical disk, or an optical disk, or be operatively connected to them to receive data therefrom or to transmit data thereto or both. However, a computer need not have such a device. In addition, a computer can also be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), just to name a few examples. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and storage devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0071] Implementations of the subject matter described in this specification may be implemented in a computing system that includes a back-end component (e.g., as a data server) or includes a middleware component (e.g., an application server) or includes a front-end component (e.g., a client computer with a graphical user interface or a web browser through which a user can interact with implementations of the subject matter described in this specification), or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), interconnected networks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0072] The computing system may include a client and a server. The client and the server are generally far away from each other and usually interact through a communication network. The relationship between the client and the server is generated because the computer program runs on the corresponding computer and has a client-server relationship between each other. In some embodiments, the server transfers data (e.g., HTML pages) to the user's computer (e.g., in order to display data to the user and receive user input from the user who interacts with the user's computer). Data generated at the user's computer (e.g., the result of user interaction) can be received from the user's computer at the server.

[0073] Although this specification contains many specific implementation details, these details should not be interpreted as limitations on the scope of any invention or the content that can be claimed, but as descriptions of features specific to a particular embodiment of a particular invention. Certain features described in the context of a separate embodiment in this specification may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although features may be described above as working in certain combinations, even initially required, one or more features from the claimed combination may be deleted from the combination under some circumstances, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0074] Similarly, although the operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or that all of the operations shown are performed to achieve the desired results. In some cases, multitasking and parallel processing can be advantageous. In addition, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated in a single software product or packaged in multiple software products.

[0075] This written description does not limit the invention to the precise terms set forth. Therefore, although the invention has been described in detail with reference to the above examples, those skilled in the art may implement changes, modifications and variations to these examples without departing from the scope of the invention.

Claims

1. A toilet management system, comprising: a functional sensor configured to generate operability level data of a restroom component defining a status of the restroom component, wherein the restroom component is a paper towel dispenser or a toilet paper dispenser, wherein the functional sensor comprises at least one of a consumable level sensor and a motor current sensor; a controller configured to modify the operation of the restroom component, wherein the restroom component has a normal operating state, a problem solving state, and a disabled state, wherein the normal operating state is a normal function of the restroom component, the problem solving state is for performing maintenance on the restroom component and the disabled state is for disabling the restroom component from operation; and a central management system configured to access the operability level data, communicate with the controller and evaluate the operability level data to determine an actionable event type for the restroom component, wherein the actionable event type includes an automatic resolution event and an assisted resolution event, the operability level data indicating that a consumable product in a paper towel dispenser or toilet paper dispenser is completely depleted or indicating that the paper towel dispenser or toilet paper dispenser is jammed, and the central management system is further configured to: responsive to determining that the actionable event type is the auto-resolve event, causing the controller to place the restroom component in the problem-resolved state for a predetermined period of time or sequence and then, after the problem-resolved state, placing the restroom component in one of the normal operating state or the disabled state based on evaluating the operability level data, wherein the problem-resolved state includes disabling a paper towel dispenser or a toilet paper dispenser; as well as In response to determining that the actionable event type is the assisted resolution event, based on operability level data, causing the controller to place the restroom component in the normal operating state or place the restroom component in the disabled state and causing a message to be sent to restroom attendant to repair the restroom component.

2. The system of claim 1, wherein placing the restroom component in the disabled state in response to the automatically resolving event includes causing a message to be sent to restroom service personnel to repair the restroom component.

3. The system of claim 1, wherein the auxiliary resolution event is refilling the restroom component with a consumable product.

4. The system of claim 1, wherein the problem resolved state comprises actuating the lavatory component one or more times.

5. A toilet management method, comprising: accessing operational data of a status of a specified restroom component from a sensor, wherein the restroom component is a paper towel dispenser or a toilet paper dispenser, wherein the sensor includes at least one of a consumable level sensor and a motor current sensor; analyzing the operability data to determine an actionable event type for the restroom component, wherein the actionable event type includes an automatic resolution event and an assisted resolution event, wherein the operability data indicates that a consumable product in a paper towel dispenser or a toilet paper dispenser is completely depleted or indicates that the paper towel dispenser or the toilet paper dispenser is jammed; responsive to determining that the actionable event type is the auto-resolve event, directing the restroom component to enter a problem-resolved state for a predetermined period of time or sequence, and then, after the problem-resolved state, directing the restroom component to enter one of a normal operating state or a disabled state based on an evaluation of the operability data, wherein the problem-resolved state includes disabling a paper towel dispenser or a toilet paper dispenser; and In response to determining that the actionable event type is the assisted resolution event, and based on an evaluation of the operability data, the lavatory component is instructed to enter the normal operating state or the disabled state.

6. The method of claim 5, wherein responsive to determining that the actionable event type is the assisted resolution event comprises instructing that a message be sent to restroom attendant to repair the restroom component.

7. The method of claim 5, wherein in the auto-resolve event and in response to indicating that the restroom component entered the disabled state includes instructing that a message be sent to restroom attendant to service the restroom component.

8. A toilet management method, comprising: accessing first operability data from a first sensor specifying consumable usage from a first restroom component and second operability data from a second sensor specifying an operational state of a second restroom component, wherein the first restroom component is a toilet paper dispenser or a paper towel dispenser and the second restroom component is a toilet or a urinal, the second sensor comprising a flush valve sensor and a water flow sensor, wherein each of the first restroom component and the second restroom component has a normal operating state, a problem solving state, and a disabled state, wherein the normal operating state is a normal function of the restroom component, the problem solving state is for performing maintenance on the restroom component, and the disabled state is for disabling the restroom component from operation; analyzing the first operability data and the second operability data to determine actionable event types for the restroom, wherein the actionable event types include automatic resolution events and assisted resolution events, and the analyzing includes determining high consumable usage from the first restroom component and determining a low operational state for the second restroom component; responsive to determining that the actionable event type is the auto-resolve event, placing a second restroom component in its problem-resolved state for a predetermined period of time or sequence during which the second restroom component is actuated a specified number of times, and then, after the problem-resolved state, directing a second restroom component in the restroom to enter one of a normal operating state or a disabled state based on an evaluation of second operability data, wherein evaluating the second operability data includes, in response to flush valve actuation from the flush valve sensor, determining a water flow reading from a water flow sensor and comparing the water flow reading to a predetermined water flow parameter to determine whether the toilet or urinal is clogged; responsive to determining that the actionable event type is the assisted resolution event, causing a message to be sent to restroom attendant personnel to service a second restroom component and, based on an evaluation of the operability data, instructing the second restroom component to enter a normal operating state or a disabled state; as well as In response to instructing the second restroom component to enter a disabled state based on a determination that the toilet or urinal is clogged based on an evaluation of the second operability data, the first restroom component is instructed to enter its disabled state.

Images