SYSTEMS AND METHODS FOR IMPROVING WATER USAGE EFFICIENCY

Abstract

Provided herein are systems and methods for improving water usage efficiency. One embodiment includes receiving water usage data associated with a building unit over a period of time, where the building unit includes a first plurality of water fixtures that are monitored by the first monitoring device, determining a leak benchmark for the first plurality of water fixtures, and determining whether the water usage data meets the leak benchmark for the first plurality of water fixtures. In some embodiments the method includes in response to determining that the water usage data meets the leak benchmark for the first plurality of water fixtures, determining that a water leak is occurring in the building unit, analyzing the water usage data to determine a likely water fixture of the first plurality of water fixtures that is experiencing the water leak, and reporting data related to the water leak to an administrator.

Description

CROSS REFERENCE

This application claims the benefit of U.S. Provisional Application Serial Number 63/743,980, filed on January 10, 2025, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments described herein generally relate to systems and methods for improving water usage efficiency and, more specifically, to embodiments for determining water leaks in multi-fixture environments.

BACKGROUND

In many residential, commercial, and industrial properties, water usage is a significant issue. Specifically, many multi-tenant residential properties and large-scale commercial and industrial properties, water usage can account for a large portion of expenses for maintaining the property. In the residential market, a property owner may have dozens of units under management. Many property owners include the cost of water in the rental price, primarily because it is often difficult and costly to account for water costs at the unit level. As such, leaks often go undetected, thus causing unnecessary expense to the property owner, which can cause increases in rent prices for the tenants.

As such, a need exists in the industry for systems and methods for improving water usage efficiency, as described herein.

SUMMARY

Provided herein are systems and methods for improving water usage efficiency. One embodiment includes receiving water usage data associated with a building unit over a period of time, where the building unit includes a first plurality of water fixtures that are monitored by the first monitoring device, determining a leak benchmark for the first plurality of water fixtures, and determining whether the water usage data meets the leak benchmark for the first plurality of water fixtures. In some embodiments the method includes in response to determining that the water usage data meets the leak benchmark for the first plurality of water fixtures, determining that a water leak is occurring in the building unit, analyzing the water usage data to determine a likely water fixture of the first plurality of water fixtures that is experiencing the water leak, and reporting data related to the water leak to an administrator.

Also included are embodiments of a system for improving water usage efficiency. Some embodiments include a monitoring device that is coupled to a water line of a building unit. The monitoring device may be configured to monitor water usage of the building unit. Some embodiments include a computing device that is communicatively coupled with the monitoring device. The computing device may include a memory component and a processor. The memory component may store logic that, when executed by the processor, causes the system to receive water usage data associated with the building unit over a period of time, where the building unit includes a plurality of water fixtures, determine a leak benchmark for the plurality of water fixtures, and determine whether the water usage data meets the leak benchmark for the plurality of water fixtures. The logic may be configured to perform the following in response to determining that the water usage data meets the leak benchmark for the plurality of water fixtures: determine that a water leak is occurring in the building unit, analyze the water usage data to determine a likely water fixture of the plurality of water fixtures that is experiencing the water leak, and determine whether the water leak meets an emergency threshold. In some embodiments, in response to determining that the water leak meets the emergency threshold, the logic may cause the monitoring device to alter water flow to the plurality of water fixtures.

Some embodiments include a non-transitory computer-readable storage medium for improving water usage efficiency. Embodiments of the non-transitory computer-readable storage medium may include logic that, when executed by a computing device, causes the computing device to receive, from a monitoring device, water usage data associated with a building unit over a period of time, where the building unit includes a plurality of water fixtures, determine a leak benchmark for the plurality of water fixtures, and determine whether the water usage data meets the leak benchmark for the plurality of water fixtures. In some embodiments, the logic causes the computing device, in response to determining that the water usage data meets the leak benchmark for the plurality of water fixtures: determine that a water leak is occurring in the building unit, analyze the water usage data to determine a likely water fixture of the plurality of water fixtures that is experiencing the water leak, and provide a user interface that includes at least one user selectable option to cause the first monitoring device alter water flow to the plurality of water fixtures.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments set forth in the drawings are illustrative and exemplary in nature and not intended to limit the disclosure. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals and in which:

FIG. 1 depicts an environment for improving water usage efficiency according to embodiments provided herein;

FIG. 2A depicts usage of a flow device at a single point of entry in two different building units, according to embodiments provided herein;

FIG. 2B depicts usage of flow devices at points of use in two different building units, according to embodiments provided herein;

FIG. 3 depicts a flowchart for improving water usage efficiency, according to embodiments provided herein;

FIG. 4 depicts another flowchart for improving water usage efficiency, according to embodiments provided herein; and

FIG. 5 depicts a computing device for improving water usage efficiency according to embodiments provided herein.

DETAILED DESCRIPTION

Embodiments disclosed herein include systems and methods for improving water usage efficiency. Some embodiments may be configured to actively monitor water usage utilizing hardware and software. Depending on the particular embodiment, hardware may be coupled to a water line at the point of use (at the fixture), as a single point of use for a building unit, or a dual point of use for a building unit, such as a commercial unit, an industrial unit, and/or a residential unit. Regardless, these embodiments may be configured to monitor water usage and determine, based on historical usage and benchmarks, if a leak is occurring in the unit. Some embodiments may be further configured to determine, based on the water usage, a fixture that is likely the source of the leak. Some embodiments may be configured to diagnose a solution for addressing the leak and/or may further configured to alter water usage of that unit, until the leak is addressed. The systems and methods for improving water usage efficiency incorporating the same will be described in more detail, below.

Referring now to the drawings, FIG. 1 depicts an environment for improving water usage efficiency according to embodiments provided herein. As illustrated, a network 100 may be coupled to a user computing device 102, a remote computing device 104, and building unit 106, and a water delivery source 108. The building unit 106 may be coupled to the network via a water meter 110 and/or a monitoring device 112.

The network 100 may include a wide area network (WAN), local area network (LAN), and/or personal area network (PAN). Example WANs might include the internet, a WiMax network, a cellular network, a public switched telephone network (PSTN), and/or the like. Example LANs might include an Ethernet network, a wireless fidelity (Wi-Fi) network, and/or the like. Example PANs might include Bluetooth, Zigbee, a wired connection, and/or other peer-to-peer networks.

In addition to the network 100, building unit 106 may be coupled to the water delivery source 108 via a water line, such that the water delivery source 108 can provide water to the building unit 106. The water meter 110 may be an in-line flowmeter or other device for monitoring water usage of the building unit 106 and as such, may be coupled to the water line. Depending on the embodiment, the water delivery source 108 and/or the water meter 110 may also be coupled to the network 100 for communicating water usage data to the water delivery source 108. Similarly, the monitoring device 112 may be coupled to the building unit 106 via the water line as well as communicatively coupled to the remote computing device 104 and/or user computing device 102 via the network 100.

Coupled to the network 100 is the user computing device 102. The user computing device 102 may include any personal computer, laptop, mobile device, or other computing device for receiving data from one or more of the other devices provided in FIG. 1, receiving input from a user, and providing output, as provided herein. As described above, some embodiments may be configured for to provide leak detection data associated with the building unit 106, as well as options for addressing the leak.

The remote computing device 104 is also coupled to the network 100. The remote computing device 104 may be configured as a server, personal computer, laptop, mobile device, and/or other computing device or virtual instance of a computing device for providing the functionality provided herein. The remote computing device 104 may include a memory component 140 that stores data collection logic 144a and leak determination logic 144b. As described in more detail below, the data collection logic 144a and the leak detection logic 144b represent software that is executed by the remote computing device 104 but may be implemented by one or more different pieces of software. In the example of FIG. 1, the data collection logic 144a may be configured to cause the remote computing device 104 to receive data from a plurality of different monitoring devices 112 and format that data for utilization by the leak determination logic 144b. Similarly, the leak determination logic 144b may be configured to cause the remote computing device 104 to identify leaks, identification leak location, and proscribe or actuate change in the system to address the leak.

The building unit 106 may be configured as any residential, commercial, and/or industrial building or set of buildings that utilize water via one or more fixtures 210. The water delivery source 108 may be any water company or other supplier of water to the building unit 106. Accordingly, the water meter 110 may be deployed by the water delivery source 108 for determining usage. In some embodiments, the water meter 110 may have no connectivity (thus requiring a human to inspect the water meter 110 to determine usage. However, some embodiments may be configured such that the water meter 110 is coupled to the network 100 for reporting usage directly to the water delivery source 108 and/or remote computing device 104. Similarly, the monitoring device 112 may be coupled to the water line, as well as the network 100. As described in more detail below, the monitoring device 112 may be configured to take multiple water readings per second for the building unit 106 for determining usage and leaks. As such, some embodiments of the monitoring device 112 may include one or more sensors for taking these measurements, as well as a computing device (with hardware, software, and firmware similar to those depicted for the remote computing device 104). However, some embodiments may be configured such that the monitoring device 112 merely includes hardware, software, firmware for taking the measurements and communicating that data to the remote computing device 104.

It should be understood that the monitoring device 112 may be configured as an “in flow” device (where the pipe is cut and the monitoring device 112 is inserted -similar to a valve) or the monitoring device 112 may be configured as a clip-on device. The monitoring device 112 may also be configured to communicate with the remote computing device 104 via a gateway, which may operate similar to a router. A plurality of monitoring devices 112 may communicate to one gateway. Regardless, the monitoring device 112 may be configured to track gallons, events, and flow time of water, as well as battery life, sensor signal and other internal system health features. In some embodiments, the monitoring device 112 may be configured to spin about 1000-2000 times per gallon and/or measure flow to the about the 1000^th of a gallon.

FIG. 2A depicts usage of a flow device at a single point of entry in two different building units 206, according to embodiments provided herein. As illustrated, the building units 206a, 206b may be configured in the same building and/or different buildings but are coupled to the same meter 208 for monitoring and billing water usage. The building unit 206a may include fixtures 210a-210f (such as a first plurality of water fixtures and a second plurality of water fixtures), which represent a toilet, sink, bathtub, washer, refrigerator, and sink, each of which pulls water. Similarly, the building unit 206b includes fixtures 210g-201l, each of which pulls water for that unit. Other water fixtures 210, such as a water heater, humidifier, etc. may also be present. Because there is only one meter 208 for both units (and the units may only be checked once per month), the water delivery source 108 (FIG. 1) does not know from which unit the water is being pulled. Accordingly, a first monitoring device 212a and a second monitoring device 212b may be installed on the water lines to each of the respective building units 206a, 206b, which can not only monitor each individual building unit 206a, 206b, but are configured with hardware and software to take multiple readings per second.

Accordingly, the data captured by the monitoring devices 212a, 212b may be communicated to the remote computing device 104 (FIG. 1), which may analyze the received data to determine whether the building units 206a, 206b have any leaks. In one example, a determination may be made that the toilet 210a is a 1.8-gallon toilet. However, the monitoring device 112 notices that water usage tends to spike at 2.2-gallon intervals. As such, these embodiments may be configured to determine that a leak has occurred and that the leak is likely from the toilet 210a. Similarly, embodiments provided herein may determine other leak profiles for the toilet 210a and/or other fixtures 210 to quickly identify and diagnose leaks.

As another example, if the water usage gradually increases and is sustained even through the night, when there should be no usage, embodiments may be configured to determine that there is a leak in the sink. Embodiments may also know the models of the sinks and/or type of water fixture in the building unit 206 and thus determine which sink is more likely to leak (e.g., from other users’ data, from age, from usage, etc.). Some embodiments may additionally determine a solution (temporary and/or permanent) to the problem, based on the leak profile. Referring back to a previous example, if the toilet 210a spikes at 2.2-gallon intervals, embodiments may determine that the flapper seal is not the problem, but instead, the flapper may remain open for too long during a flush. As such, these embodiments may provide a temporary solution (e.g., add weight to the flapper) and/or a permanent solution (e.g., replace the flapper).

In addition to identifying the leak and the location of the leak, some embodiments may provide this information to the user computing device 102 (FIG. 1) for an administrator to view and/or take action. The information provided to the user may include an identifier of the building unit 106, usage volume, leak volume, likely solution, etc. Similarly, some embodiments may be configured to address the leak. As an example, some embodiments of the monitoring device 212a may be configured to shut water supply to the building unit 206a during nighttime hours (or other hours) to prevent the leak from continuing until a permanent solution is implemented.

As will be understood, embodiments provided in FIG. 2A utilize only one monitoring unit 220a, 220b per unit. As such, determining the fixture(s) 210 that are leaking may be performed based on the profile of the leak and/or probabilities based on the age of the appliances, the reliability of the appliances, etc. Additionally, while some embodiments may be configured to identify a single fixture 210 that is leaking, some embodiments may identify a class of fixture 210 (e.g., toilet, sink, washer, etc.). Similarly, as some embodiments may have information regarding the model and age of the fixtures 210, each of those particular fixtures 210 may conform to a specific leak profile, such that the specific fixture 210 may be identified. As an example, if a particular model of Toto toilet typically leaks according to a predetermined pattern after a predetermined age, if a leak is detected that matches that pattern, embodiments may identify the Toto toilet as the leaking fixture 210. Additionally, some embodiments may be configured to identify and/or update the registry of fixtures 210 in a building unit 206, based on a leak profile determined. As an example, if a Toto toilet leak profile is detected, but the building unit 206 does not have a Toto toilet registered, these embodiments may be configured to determine that the registry is incorrect, identify the leak source, and update the fixture registry to include a Toto toilet. Similarly, some embodiments may be configured to determine a number and type of fixtures 210 based on the water usage of the building unit 206.

FIG. 2B depicts usage of flow devices at points of use in two different building units 206, according to embodiments provided herein. Similar to the example of FIG. 2A, FIG. 2B provides two building units 206a, 206b. However, in this example, monitoring units 220a-220l are coupled at a point of use of the fixtures 210a-210l, respectively. As such, the algorithm for detecting and diagnosing leaks is slightly different, because each monitoring device 220 is specifically coupled to a known fixture. As such, at least some embodiments may be configured such that different algorithms are run for toilets than for sinks, bathtubs, etc. and/or for different models of fixtures. Specifically, because the monitoring units 220 are coupled to individual fixtures 210, the monitoring units 220 may identify a leak based on an increase is water usage and/or a pattern that is specific to a particular fixture type (or model). As an example, if a toilet 210a is displaying continuous water usage overnight, this may signify a toilet leak. However, if a hose spigot shows continuous water usage overnight, this may be indicative of a sprinkler that waters the lawn and not a leak.

FIG. 3 depicts a flowchart for improving water usage efficiency, according to embodiments provided herein. As illustrated in block 350, a determination may be made regarding the type of attachment or monitoring device 112. In response to determining that the type of monitoring device 112 is a point of use device, the process proceeds to block 352 to determine the type of point of use device. If the type of point of use device is a toilet 210a, at block 354, a toilets benchmark for daily/hourly gallons, events, and flow time is selected. If the type of point of use device is a water heater, at block 356, a water heater benchmark is selected for daily, hourly/gallons, events, and flow time.

If at block 350, the type of monitoring device 112 is a single point of entry or a dual point of entry, at block 360, single point of entry or dual point of entry benchmarks for daily/hourly gallows, events, and flow times may be selected. From block 354, 356, and 360, the process proceeds to block 358 to determine whether hourly gallons, events, and flow time is above the hourly benchmark. If so, the process proceeds to block 360, to calculate hourly leak gallons as the sum of all gallons in an hour where gallons, events, or flow time are above the benchmark. From block 360 or from block 358 if the hourly gallons, events, and flow time is not above the hourly benchmark, the process proceeds to block 362 to determine whether the daily aggregated hourly leak gallons are above a benchmark. If so, at block 364, the amount of leak equal to daily aggregated hourly leak gallons may be recorded. If not, at block 366, a determination may be made regarding whether running hours or daily flow time is above the benchmark. If so, at block 368, an amount of leak equal to total amount of gallons may be recorded. If not, at block 370, a determination of no leak may be made.

FIG. 4 depicts another flowchart for improving water usage efficiency, according to embodiments provided herein. As illustrated in block 450, water usage data associated with a building unit 106 may be received over a period of time, where the building unit 106 includes a plurality of water fixtures 210. In block 452, a leak benchmark for the plurality of water fixtures 210 may be determined. In block 454, a determination may be made regarding whether the water usage data meets the leak benchmark for the plurality of water fixtures 210. In block 456, if the water usage data does not meet the benchmark, a determination that no leak is occurring may be made. However, in response to determining that the water usage data meets the leak benchmark for the plurality of water fixtures 210, in block 458, a determination may be made that a water leak is occurring in the building unit 106. In block 460, the water usage data may be analyzed to determine a likely water fixture 210 of the plurality of water fixtures 210 that is experiencing the water leak. In block 462, data related to the water leak may be reported to an administrator.

It will be understood that some embodiments may be configured to additionally provide a user interface to an administrator (e.g., a customer service representative, plumber, landlord, etc.). Specifically, upon determining that there is a leak and/or a likely water fixture 210 that is leaking, the administrator may be provided with a user interface. The user interface may provide information about the leak (e.g., where, how much water is leaking, proposed permanent solution, proposed temporary solution, etc.). Additionally, the user interface may include one or more user-selectable options for the administrator to control the monitoring device 112, such as altering the amount of water flowing, shutting off the water flow, turning on the water flow, etc.).

Additionally, some embodiments may be configured to automatically alter water flow via the monitoring device 112. As example, if the leak meets an emergency threshold, these embodiments may cause the monitoring device 112 to cause automatic action to the water flow, such as shutting down, reducing, or otherwise altering the water flow.

FIG. 5 depicts a computing device for improving water usage efficiency according to embodiments provided herein. As illustrated, the remote computing device 104 includes a processor 530, input/output hardware 532, a network interface hardware 534, a data storage component 536 (which stores unit data 538a, benchmark data 538b, and/or other data, as described above), and a memory component 140. The memory component 140 may be configured as volatile and/or nonvolatile memory and as such, may include random access memory (including SRAM, DRAM, and/or other types of RAM), flash memory, secure digital (SD) memory, registers, compact discs (CD), digital versatile discs (DVD) (whether local or cloud-based), and/or other types of non-transitory computer-readable medium. Depending on the particular embodiment, these non-transitory computer-readable mediums may reside within the remote computing device 104 and/or external to the remote computing device 104.

The memory component 140 may store operating logic 542, the data collection logic 144a, and the leak determination logic 144b. Each of these logic components may include a plurality of different pieces of logic, each of which may be embodied as a computer program, firmware, and/or hardware, as an example. A local communication interface 546 is also included in FIG. 5 and may be implemented as a bus or other communication interface to facilitate communication among the components of the remote computing device 104.

The processor 530 may include any processing component operable to receive and execute instructions (such as from a data storage component 536 and/or the memory component 140). As described above, the input/output hardware 532 may include and/or be configured to interface with speakers, microphones, and/or other input/output components.

The network interface hardware 534 may include and/or be configured for communicating with any wired or wireless networking hardware, including an antenna, a modem, a LAN port, wireless fidelity (Wi-Fi) card, WiMAX card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices. From this connection, communication may be facilitated between the remote computing device 104 and other computing devices.

The operating logic 542 may include an operating system and/or other software for managing components of the remote computing device 104. As discussed above, the data collection logic 144a may reside in the memory component 140 and may be configured to cause the processor 508 to collect data from the monitoring devices 112 and format for analysis as well as develop the benchmark data 538. The leak determination logic 144b may be configured for causing a computing device (such as the remote computing device 104) to analyze the data received, compare with benchmark data 538, identify leaks, locate leaks, and determine solutions to the leaks.

It should be understood that while the components in FIG. 5 are illustrated as residing within the remote computing device 104, this is merely an example. In some embodiments, one or more of the components may reside external to the remote computing device 104 or within other devices, such as the user computing device 102 and/or the monitoring device 112 depicted in FIG. 1. It should also be understood that, while the remote computing device 104 is illustrated as a single device, this is also merely an example. In some embodiments, the data collection logic 144a and the leak detection logic 144b may reside on different computing devices.

As an example, one or more of the functionalities and/or components described herein may be provided by the remote computing device 104, the user computing device 102, and/or the monitoring device 112. Depending on the particular embodiment, any of these devices may have similar components as those depicted in FIG. 5. To this end, any of these devices may include logic for performing the functionality described herein.

Additionally, while the remote computing device 104 is illustrated with the data collection logic 144a and the leak determination logic 144b as separate logical components, this is also an example. In some embodiments, a single piece of logic may provide the described functionality. It should also be understood that while the data collection logic 144a and the leak detection logic 144b are described herein as the logical components, this is also an example. Other components may also be included, depending on the embodiment.

As illustrated above, various embodiments for systems and methods for improving water usage efficiency are disclosed. These embodiments save drastic amounts of water that would otherwise be wasted through leakage. Additionally, these embodiments utilize sophisticated monitoring devices 112 that measure water usage multiple times per second, thereby allowing these embodiments to measure micro-changes to water usage that could not otherwise be detected.

While particular embodiments and aspects of the present disclosure have been illustrated and described herein, various other changes and modifications can be made without departing from the spirit and scope of the disclosure. Moreover, although various aspects have been described herein, such aspects need not be utilized in combination. Accordingly, it is therefore intended that the appended claims cover all such changes and modifications that are within the scope of the embodiments shown and described herein.

It should now be understood that embodiments disclosed herein include systems, methods, and non-transitory computer-readable mediums for improving water usage efficiency. It should also be understood that these embodiments are merely exemplary and are not intended to limit the scope of this disclosure.

Claims

1. A method for improving water usage efficiency comprising:

receiving, by a computing device via a first monitoring device, water usage data associated with a building unit over a period of time, wherein the building unit includes a first plurality of water fixtures that are monitored by the first monitoring device;

determining, by the computing device, a leak benchmark for the first plurality of water fixtures;

determining, by the computing device, whether the water usage data meets the leak benchmark for the first plurality of water fixtures;

in response to determining that the water usage data meets the leak benchmark for the first plurality of water fixtures:

determining, by the computing device, that a water leak is occurring in the building unit;

analyzing, by the computing device, the water usage data to determine a likely water fixture of the first plurality of water fixtures that is experiencing the water leak; and

reporting, by the computing device, data related to the water leak to an administrator.

2. The method of claim 1, further comprising determining whether the water leak meets an emergency threshold and in response to determining that the water leak meets the emergency threshold, causing the first monitoring device to alter water flow to the first plurality of water fixtures.

3. The method of claim 1, further comprising: determining, from the water usage data a pattern of water usage; and determining, based on the pattern of water usage a type of water fixture that is experiencing the water leak.

4. The method of claim 1, further comprising determining at least one of the following: a temporary solution to the water leak or a permanent solution to the water leak.

5. The method of claim 1, further comprising: determining at least one of the following based on the water usage data: a type of water fixture in the building unit or a model of water fixture in the building unit; and updating a fixture registry.

6. The method of claim 1, further comprising determining whether the first monitoring device is configured as at least one of the following: a single point of entry or a dual point of entry.

7. The method of claim 1, further comprising in response to determining that the water usage data does not meet the leak benchmark for the first plurality of water fixtures, determining that the building unit is not experiencing the water leak.

8. The method of claim 1, further comprising providing a user interface that includes at least one user selectable option to cause the first monitoring device alter water flow to the first plurality of water fixtures.

9. The method of claim 1, wherein the computing device is coupled with a second monitoring device that services a second plurality of water fixtures in the building unit.

10. A system for improving water usage efficiency comprising: a monitoring device that is coupled to a water line of a building unit, wherein the monitoring device is configured to monitor water usage of the building unit; and a computing device that is communicatively coupled with the monitoring device, the computing device including a memory component and a processor, the memory component storing logic that, when executed by the processor, causes the system to perform at least the following: receive water usage data associated with the building unit over a period of time, wherein the building unit includes a plurality of water fixtures; determine a leak benchmark for the plurality of water fixtures; determine whether the water usage data meets the leak benchmark for the plurality of water fixtures; in response to determining that the water usage data meets the leak benchmark for the plurality of water fixtures: determine that a water leak is occurring in the building unit; analyze the water usage data to determine a likely water fixture of the plurality of water fixtures that is experiencing the water leak; determine whether the water leak meets an emergency threshold; and in response to determining that the water leak meets the emergency threshold, cause the monitoring device to alter water flow to the plurality of water fixtures.

11. The system of claim 10, wherein the logic further causes the system to perform at least the following: determine, from the water usage data a pattern of water usage; and determine, based on the pattern of water usage a type of water fixture that is experiencing the water leak.

12. The system of claim 10, wherein the logic further causes the system to determine at least one of the following: a temporary solution to the water leak or a permanent solution to the water leak.

13. The system of claim 10, wherein the logic further causes the system to perform at least the following:

determine at least one of the following based on the water usage data: a type of water fixture in the building unit or a model of water fixture in the building unit; and

update a fixture registry.

14. The system of claim 10, wherein the logic further causes the system to determine whether the monitoring device is configured as at least one of the following: a single point of entry or a dual point of entry.

15. The system of claim 10, wherein in response to determining that the water usage data does not meet the leak benchmark for the plurality of water fixtures, the logic further causes the system to determine that the building unit is not experiencing the water leak.

16. A non-transitory computer-readable storage medium for improving water usage efficiency comprising logic that, when executed by a computing device, causes the computing device to perform at least the following:

receive, from a monitoring device, water usage data associated with a building unit over a period of time, wherein the building unit includes a plurality of water fixtures;

determine a leak benchmark for the plurality of water fixtures;

determine whether the water usage data meets the leak benchmark for the plurality of water fixtures;

in response to determining that the water usage data meets the leak benchmark for the plurality of water fixtures:

determine that a water leak is occurring in the building unit;

analyze the water usage data to determine a likely water fixture of the plurality of water fixtures that is experiencing the water leak; and

provide a user interface that includes at least one user selectable option to cause the first monitoring device alter water flow to the plurality of water fixtures.

17. The non-transitory computer-readable storage medium of claim 16, wherein the logic further causes the computing device to perform at least the following: determine, from the water usage data a pattern of water usage; and determine, based on the pattern of water usage a type of water fixture that is experiencing the water leak.

18. The non-transitory computer-readable storage medium of claim 16, wherein the logic further causes the computing device to perform at least the following:

determine at least one of the following based on the water usage data: a type of water fixture in the building unit or a model of water fixture in the building unit; and

update a fixture registry.

19. The non-transitory computer-readable storage medium of claim 16, wherein the logic further causes the computing device to determine whether the monitoring device is configured as at least one of the following: a single point of entry or a dual point of entry.

20. The non-transitory computer-readable storage medium of claim 16, wherein in response to determining that the water usage data does not meet the leak benchmark for the plurality of water fixtures, the logic further causes the computing device to determine that the building unit is not experiencing the water leak.