Systems and Methods for Detecting Unexpected Utility Usage

• US 20110178937A1
• Filed: 01/15/2010
• Published: 07/21/2011
• Est. Priority Date: 01/15/2010
• Status: Abandoned Application

• Current Assignee: Jonathan Bud Bowman
• Original Assignee: Jonathan Bud Bowman
• Inventors: Bowman, Jonathan Bud
• Application Number:
  US12/687,878
• Publication Number:
  US 20110178937A1
• Time in Patent Office: Days
• US Class Current: 705/314
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 50/06 Energy or water supply
• CPC Class Codes: G06Q 50/16 Real estate
• CPC Class Codes: G06Q 50/163 Real estate management

Abstract

A utility management system associated with at least one multiple unit residential facility comprises an onsite metering system configured to monitor at least one metering sensor. A property management system is configured to communicate occupancy data for at least one residential unit. A utility management server comprises a usage database capable of receiving usage data from the onsite metering system, along with an occupancy database capable of receiving occupancy data from the property management system. The utility management server also includes usage analysis software configured to compare the usage data with the occupancy data for at least one residential unit to determine whether one or more exceptions exist. A notice generation system is configured to receive exception data from the utility usage analysis system. The notice generation system is capable of running notice generation software configured to generate a notice when an exception has been identified in the exception data.

Claims

1. A utility management system associated with at least one multiple unit residential facility comprising:

at least one onsite metering system configured to monitor at least one metering sensor;

at least one property management system configured to communicate occupancy data for at least one residential unit;

at least one utility management server in communication with the at least one onsite metering system and the at least one property management system, the at least one utility management server comprising;

at least one usage database capable of receiving usage data from the at least one onsite metering system;

at least one occupancy database capable of receiving occupancy data from the at least one property management system;

at least one utility usage analysis system having usage analysis hardware capable of running usage analysis software configured to compare the usage data with the occupancy data for at least one residential unit to determine whether one or more exceptions exist; and

at least one notice generation system configured to receive exception data from the at least one utility usage analysis system, the at least one notice generation system having notice generation hardware capable of running notice generation software configured to generate at least one notice when one or more exceptions have been identified in the exception data.

2. The system of claim 1, wherein at least one of the following occurs one of continuously, periodically and on-demand:

the at least one onsite metering system is configured to monitor the at least one metering sensor;

the at least one property management system is configured to communicate occupancy data;

the at least one utility management server is capable of receiving the usage data from the at least one metering server and occupancy data from the at least one property management system;

the usage analysis software is configured to compare the usage data with the occupancy data; and

the notice generation software is configured to compare the exception data to one or more notice preferences

3. The system of claim 1, wherein at least one exception is determined based on a lockstep comparison of the usage data to the occupancy data for at least one residential unit.

4. The system of claim 1, wherein the at least one utility usage analysis system further comprises at least one usage threshold database capable of storing at least one default usage threshold.

5. The system of claim 1, wherein the usage threshold database is capable of receiving and storing at least one user-defined usage threshold communicated via at least one user interface.

6. The system of claim 1, wherein the usage analysis software is configured to determine that at least one exception exists when the occupancy data indicates that at least one residential unit is unoccupied and the usage data for the at least one residential unit one of meets and exceeds at least one usage threshold.

7. The system of claim 1, wherein the usage analysis software is configured to determine that at least one exceptions exist when the occupancy data indicates that at least one residential unit is occupied and the usage data for the at least one residential unit one of meets and exceeds at least one usage threshold.

8. The system of claim 1, wherein the usage analysis software is configured to determine that at least one exception exists when the occupancy data indicates that at least one residential unit is occupied and the usage data for the at least one residential unit one of meets and falls below at least one usage threshold.

9. The system of claim 1, wherein the utility usage analysis system further comprises at least one exception database configured to receive exception data from the usage analysis software.

10. The system of claim 1, wherein the at least one notice generation system is capable of receiving the exception data from the at least one exception database.

11. The system of claim 1, wherein the at least one notice generation system further comprises at least one notice preference database capable of storing at least one default notice preference.

12. The system of claim 1, wherein the notice preference database is capable of receiving and storing at least one user defined notice preference communicated via at least one user interface.

13. The system of claim 1, wherein the notice generation software is configured to compare the exception data to at least one notice preference and generate at least one notice when at least one notice preference has been satisfied by the exception data.

14. The system of claim 1, wherein the notice generation software is configured to generate at least one notice when no exceptions are identified in the exception data by the notice generation software.

15. A method of identifying unexpected usage of a utility comprising:

receiving usage data in at least one onsite metering system from at least one metering sensor;

communicating the usage data from the at least one onsite metering system to at least one usage database;

receiving the usage data in the at least one usage database;

communicating occupancy data from at least one property management system to at least one occupancy database;

receiving the occupancy data in the at least one occupancy database;

comparing the usage data with the occupancy data for at least one residential unit;

determining whether one or more exceptions has occurred based on comparing the usage data to the occupancy data for the at least one residential unit; and

generating one or more notices when one or more exceptions have been identified.

16. The method of claim 15, wherein at least one of the following occurs one of continuously, periodically and on-demand:

receiving usage data in at least one onsite metering system;

communicating the usage data from the at least one onsite metering system to at least one usage database;

communicating occupancy data from at least one property management system to at least one occupancy database;

comparing the usage data with the occupancy data for at least one residential unit;

determining whether one or more exceptions have occurred; and

generating one or more notices when one or more exceptions have been identified.

17. The method of claim 15, wherein determining whether one or more exceptions has occurred further comprises performing a lockstep comparison of the usage data to the occupancy data for at least one residential unit.

18. The method of claim 15, further comprising comparing usage data with at least one usage threshold for the at least one residential unit.

19. The method of claim 18, wherein determining that one or more exceptions exist comprises determining that the occupancy data for the at least one residential unit indicates that the at least one residential unit is unoccupied and the usage data for the at least one residential unit one of meets and exceeds the at least one usage threshold.

20. The method of claim 18, wherein determining that one or more exceptions exist comprises determining that the occupancy data for the at least one residential unit indicates that the at least one residential unit is occupied and the usage data for the at least one residential unit one of meets and exceeds the at least one usage threshold.

21. The method of claim 18, wherein determining that one or more exceptions exist comprises determining that the occupancy data for the at least one residential unit indicates that the at least one residential unit is occupied and the usage data for the at least one residential unit one of meets and falls below the at least one usage threshold.

22. The method of claim 15, further comprising receiving exception data for the at least one residential unit in at least one notice generation system.

23. The method of claim 15, further comprising comparing the exception data for the at least one residential unit to at least one notice preference and generating at least one notice when at least one notice preference has been satisfied by the exception data for the at least one residential unit.

24. The method of claim 15, further comprising generating at least one notice when no exceptions have been determined.