The field of the present invention relates to computer systems. More particularly, embodiments of the present invention relate to energy management systems.
Consumers experiment with different ways of reducing household energy usage. For example, consumers may turn off air conditioning during certain parts of the day, run certain appliances only during the early morning hours, and replace large inefficient appliances with smaller energy efficient ones. Additionally, consumers may use measuring devices to calculate the energy usage rate of a particular device. Then, depending upon the measured energy usage, a consumer may decide to turn the device on and off to adjust the home's overall energy usage.
However, there exist limitations as to the current system for measuring the energy usage of a particular device. While a device's energy usage may be determined for a given point in time, it is unclear what this determination means. For example, an energy usage measurement might specify that a device is using 2 kilowatts per hour. While this information may be useful to a scientist, the average consumer is not well acquainted with the kilowatt. Furthermore, it is not clear to the consumer what the 2 kilowatts per hour static measurement means in context with the energy usage of a possible new device, other devices, and/or the entire household of devices. Thus, current energy usage measurements are cryptic and not very useful to the average consumer.
Accessing an energy management policy for a plurality of devices is described, wherein the devices are coupled with a first structure. The energy usage of the devices is monitored. An energy usage rule and energy usage is then compared. The energy management policy and energy usage is also compared. Based on the comparing, an instruction is generated to modify an energy usage profile of said device to correlate with the energy usage rule associated with the devices and the energy management policy, thereby enabling efficient energy management.
The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the present invention for managing energy usage and, together with the description, serve to explain principles discussed below:
The drawings referred to in this description should not be understood as being drawn to scale unless specifically noted.
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with various embodiment(s), it will be understood that they are not intended to limit the present invention to these embodiments. On the contrary, the present invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the various embodiments as defined by the appended claims.
Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, the present invention may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present embodiments.
Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present detailed description, discussions utilizing terms such as “accessing”, “monitoring”, “comparing”, “modifying”, “enabling”, “tracking”, “generating”, “estimating”, “alerting”, or the like, refer to the actions and processes of a computer system, or similar electronic computing device. The computer system or similar electronic computing device manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission, or display devices. The present invention is also well suited to the use of other computer systems such as, for example, optical and mechanical computers.
Embodiments in accordance with the present invention pertain to a system for managing energy usage. In one embodiment, the system described herein enables conservation of household energy by advising a user to modify the household's energy usage to correlate to a desired energy usage for that household.
More particularly, one embodiment of the present invention functions as a household energy manager. For example, the energy manager attaches to a household wall and replaces the typical heating-cooling thermostat controller. The energy manager then utilizes an energy-measuring module coupled with a household device to monitor the energy usage of the household device. For example, an energy-measuring module coupled with a dishwasher may measure a dishwasher utilizing 1.20 kilowatts per hour of electricity.
In addition to monitoring individual appliances, the energy manager may utilize an energy-measuring module, such as a smart meter, coupled with the house to monitor the total household's energy usage. For example, a smart meter may measure the overall energy usage of all appliances within a household, including the dishwasher, to be 21 kilowatts per hour of electricity.
The energy manager then may access an energy usage rule describing a desired energy usage for a device and/or the household. This energy usage rule may be preprogrammed and internal to the energy manager or may be accessed at a server positioned external to the energy manager. This server in turn may receive a demand-response call from an energy utility company. For example, a demand-response call may indicate that it is desirable that the aforementioned dishwasher is to use up to a maximum of 1.00 kilowatt per hour of electricity at any given time. Furthermore, an overall energy management policy may specify that the household may use up to a maximum of 20 kilowatts per hour of energy at any point in time.
Based on the comparison between the measured energy usage of a household device and that device's desired energy usage, the energy manager may modify the device's energy usage to conform with the overall desired energy usage. For example, based on the comparison between the dishwasher's measured 1.20 kilowatts per hour of energy usage, and the household's use of 21 kilowatts per hour of electricity, the energy manager may modify the dishwasher's energy usage by turning it off and on at time periods separate from other high energy usage appliances, to keep the overall household energy use below 20 kilowatts per hour at any given point in time.
Thus, an energy manager may utilize an internally preprogrammed energy usage rule and/or a demand-response call received via a server from an energy utility company to advise a user to modify a device's energy usage.
The following discussion will begin with a detailed description of the structure of components herein in accordance with the present invention. This discussion will then be followed by a detailed description of the operation and function of the components herein.
Energy Manager
Continuing with
Energy manager 100 is shown coupled wirelessly with device 204 via energy-measuring module 250a and compatible communication module 210. Of note, energy-measuring module 250a may be coupled with energy manager 100 in such a way as to be part of energy manager 100. Energy-measuring module 250a operates as an inductive donut surrounding the electrical cord that couples device 204 with an electrical outlet of first structure 140. As will be described herein, energy-measuring module 250a listens for information such as energy usage signatures specific to device 204. This information is communicated wirelessly to energy manager 100 via a wireless transmitter and receiver coupled with energy measuring module 250a and compatible communication module 210, such as but not limited to the wireless Ethernet, ZigBee, X10, or some other suitable wireless protocol.
In another embodiment, energy manager 100 is shown coupled wirelessly with energy-measuring module 250b. Energy-measuring module 250b may be a digital meter coupled with the outside of the home. Energy utility 240 has access to this digital meter. The digital meter provides information regarding the total energy usage of the household. This information is communicated wirelessly to energy manager 100 via a wireless transmitter and receiver coupled with energy-measuring module 250b and energy manager 100, such as such as but not limited to the wireless Ethernet, ZigBee, X10, or some other suitable wireless protocol.
In one embodiment, energy manager 100 is shown coupled wirelessly with energy-measuring modules 250c1 and 250c2 of a group of energy-measuring modules denoted as 250c, that are themselves coupled with subpanels positioned on the side wall and ceiling of first structure 140. Of note, in another embodiment, energy manager 100 may also be coupled with energy-measuring modules 250c1 and 250c2 via a wire. Additionally, energy manager 100 is well suited to being coupled with a plurality of more than two energy-measuring modules of energy-measuring module group 250c at any number of locations within first structure 140.
Energy-measuring modules 250c1 and 250c2 that are coupled with the subpanels and positioned in the proximity of device 204 listen for information such as energy usage signatures specific to device 204. For example, a certain amount of signal noise flows between and through energy-measuring modules 250c1 and 250c2. By identifying and comparing said signal noise received at energy-measuring modules 250c1 and 250c2, better granularity in reading the energy signature of device 204 can be obtained. The more 250c energy-measuring modules that are positioned at first structure 140, the more data that can be collected. The more data that can be collected, the more accurate is the determination of energy usage per device 204.
Of note, energy usage rule 202 may be any recommendation or instruction for energy usage as it relates to device 204, either alone, or as part of an energy management policy for one or more devices. In one embodiment, an energy management policy may designate the overall desired household energy usage as well as the desired energy usage for individual devices therein.
In one embodiment, energy usage rule 202 is preprogrammed within energy manager 100. In another embodiment, energy usage rule 202 is external to energy manager 100, located at server 225, and provided to server 225 via energy utility 240 or other Internet hosted servers. In one embodiment, server 225 acts as a central management server. Energy utility 240 is coupled with energy manager 100 via Internet 245 and server 225, and is coupled with first structure 140 via energy-measuring module 250b.
In another embodiment, unit 260 is coupled with device 204 and electrical outlet 265 with which device 204 is also coupled. Additionally, the present invention is well suited to having any number of units 260 coupled with any number of devices and any number of electrical outlets. Unit 260 is configured to receive an instruction to modify an energy usage profile of device 204 to correlate with device 204's energy usage rule. In essence, unit 260 may control the power to device 204. Of note, unit 260 may receive instructions to modify the energy usage profile of device 204 from any device capable of sending receivable instructions.
In one embodiment, an energy manager 100 coupled with a subpanel within first structure 140 wirelessly transmits an instruction to unit 260 to modify the energy usage profile of device 204. In another embodiment, user 255 may email an instruction to unit 260 to modify device 204 coupled therewith. More particularly, in one example, unit 260 is coupled with a lamp. Energy manager 100 sends a message to unit 260 that the lamp is utilizing too many kilowatts per hour of energy and needs to be turned down. Unit 260 then dims the lamp's lighting, thus decreasing the lamp's energy usage according to the instructions.
Continuing with
Operation
More generally, in embodiments in accordance with the present invention, energy manager 100 is used to monitor and instruct a user to modify the energy usage profile of one or more devices within a household to correlate to a desired energy usage for that device and/or household. In another embodiment, energy manager 100 is used to monitor and automatically modify the energy usage profile of one or more devices within a household to correlate to a desired energy usage for that device and/or household. Desired energy usage may be based on energy usage rules internal to energy manager 100 and/or energy usage rules ultimately received from an energy utility. Such an instruction and/or modification are particularly useful to conserve household energy usage.
More particularly, and referring to
An energy usage measurement of one or more devices refers to the total amount of energy measured for each device and/or for cumulative devices within first structure 140. For example, energy-measuring module 250a measures energy through a study of a device's energy usage signature that vacillates with its energy usage. For example, every device that plugs into an electrical system has a unique energy usage signature. In other words, every device exhibits unique signal patterns during its electrical usage. These signals are used to calculate a total amount of energy being used at any given time by device 204.
An energy usage profile of device 204 refers to the overall energy usage of device 204 and device's 204 interaction with other devices within first structure 140, taking into account all available input, such as user 255 input, energy utility 240 input, and/or other input received via Internet 245 and server 225. Additionally, an energy usage profile of device 204 may be integrated with an energy usage profile of a device located within one or more structures other than first structure 140.
In one embodiment, energy usage rule accessor 105 comprises server accessor 220, configured for accessing an energy management instruction at server 225, wherein server 225 is positioned apart from first structure 140. Server 225 holds instructions received from energy utility 240. These instructions, for example, may command energy manager 100 to conserve energy relating to one or more structures that are subscribed to a demand response program. This command to conserve energy may take the form of an instruction to turn down a thermostat's set-point in the summer and to turn up the thermostat's set-point in the winter during critical peak energy draw situations. In essence, the instructions provide that the AC is to be turned down in the summer and that the heater is to be turned down in the winter at certain critical points in time.
However, “cheaters” could put a local heat source such as a match (in the summer) or a local cold source such as an ice-cube (in the winter) to attempt to trick the thermostat that the adjustment being made will have a positive effect on the energy load. Energy manager 100 may then profile the actual energy load reduction vs. the projected energy load reduction. If it is determined that the difference between the actual energy load reduction vs. the projected energy load reduction is too great, then a demand response situation may be triggered.
In a demand response situation, energy manager 100 may ignore the actual temperature reading and may alert authorities of the cheating. For example, when the demand response situation has been triggered and using sophisticated algorithms, energy manager 100 may determine the appropriate actions in proceeding with an energy load reduction, regardless of the energy manager 100's local temperature reading. Energy manager 100 may also flag a server 225 as to suspicious behavior for later follow-up by authorities.
In another embodiment, user instruction accessor 230 is configured for accessing an instruction from user 255, wherein the instruction provides guidance as to user's 255 desired energy usage for device 204. For example, in one embodiment, user 255 may input information into energy manager 100 such as to what temperature user 255 would like a room to remain for the next five hours.
In one embodiment, the user instruction is a result of a dialogue generated by energy manager 100 with user 255. For example, energy manager 100 may create a dialogue with user 255 via text and/or sound to learn how and when to automatically modify the in-home environment taking into account the comfort of user 255. Energy manager 100, for example, may interview user 255 to improve user's personal satisfaction with the HVAC and energy automation effectiveness. One or all of the available energy manager 100's available user interfaces may query, “Are you cold, hot, or just right now?” or “We made the assumption due to the time of day and day-in-the-month not to turn the heat on at this time to save you money . . . did you like the decision?” The answers to these queries may be used to create an energy usage profile of user 255 and the household.
After establishing a home owner's preference in temperature and pattern of usage, energy manager 100 may also factor in local weather conditions into pro-active plans for heating and cooling. For example, an Internet hosted server (coupled with server 225 via Internet 245) may provide forecasted weather data for the home in neighborhood, identifiable by zip code. Energy manager 100 may use the anticipation of a coming weather pattern, user preference knowledge, and scheduled or critical peak energy rates (actual or expected) to take pro-active steps. For example, these pro-active steps may include gradually cooling down the house to 65 degrees throughout the morning until 11 am, while taking into account that user's 255 disregard for the cold in the morning as well as taking advantage of cheaper energy rates.
In another embodiment, an instruction is generated to modify an energy usage profile of first device 204 coupled with first structure 140 according to an energy usage profile of a second device coupled with a second structure, such that the energy usage associated with first structure 140 and the energy usage associated with the second structure does not occur at the same time. For example, two different homes both have an energy manager 100, are coupled with server 225, and enter into a local grid “balancing algorithm”. Home #1 wants to use its compressor. Home #2 wants to heat its swimming pool. If both homes use this type of energy at the same time, the power grid will be taxed with a cumulative amount of power usage. However, if the two homes stagger its energy usage, then the power grid's average usage will remain the same. In other words, when home #1 is done with using its compressor, the pool heater of home #2 will be recommended to be powered on.
For example, energy manager 100 of home #1 generates an instruction to the effect that home #1 should power on its compressor between the hours of 2 p.m. and 4 p.m. Energy manager 100 of home #2 generates an instruction to the effect that home #2 should power on its pool heater between the hours of 4 p.m. and 6 p.m. The residents of home #1 may then follow its energy manager 100's instructions. The residents of home #2 may also then follow its energy manager 100's instructions.
In another embodiment of the present invention, when home #1 is done with using its compressor, the pool heater of home #2 will automatically power on.
In other words, energy manager 100 causes “peak load management” to occur, in which some or all devices within a home may be turned off in critical peak power situations. This peak load management can be performed based on geography, such as but not limited to peak load management per house and peak load management per neighborhood.
In one embodiment of the present invention, energy manager 100 comprises interface compatibility module 205, configured for enabling coupling of energy manager 100 with compatible communication module 210, wherein energy manager 100 utilizes compatible communication module 210 to access an energy usage measurement. For example, interface compatibility module 205 provides a means of choosing the best method of Internet connectivity for user 255. It comprises a compatible communication module 210 that allows user 255 to buy a compatible wireless networking module, a household-wiring module, or other appropriate module that allows for further customization by user 255 to match user's 255 existing home network. For example, compatible communication module 210 enables the coupling of wireless connector 802.11 with energy manager 100. Wireless connector 802.11 then enables communication with energy measuring module 250a.
In another embodiment of the present invention, energy manager 100 comprises graphical display module 215, configured for enabling communication with user 255. For example, graphical display module 215 may include various aesthetic properties relating to color, texture, shape, and lighting. In one embodiment, graphical display module 215 may be a glass touch screen panel. The panel may be color and incorporate graphics. The panel may enable communication via icons, graphs, pie charts, etc.
In one embodiment, energy manager 100 generates an instruction that is receivable by a human user 255 of device 204. This instruction may be receivable through any number of mediums, including graphical display module 215 positioned as shown in
In one embodiment, energy manager 100 comprises passive power consumption tracker 235, configured for tracking a difference between the sum of energy usage of all devices, wherein all these devices are in an active state and coupled with first structure 140, and a total energy used within first structure 140 to generate a passive power consumption analysis. For example, energy manager 100 may provide calculated estimates of passive power consumption. The difference between the sum of each appliance's energy usage and the total energy usage is per household is passive power consumption and untracked power usage. This untracked power usage is un-optimizable usage. Passive power consumption is considered to be the most significant drain of power on a power grid. Wall nuts and other passive power drains are undocumented and yet pull more current than any other sink. Even though an appliance is “off” doesn't mean that the appliance isn't consuming power. Tracking this passive power usage increases the user's 255 awareness of energy usage and creates opportunities to conserve overall energy.
In one embodiment of the present invention, an upgrade to energy manager 100 is accessed. For example, energy manager 100 may access, via server 225, upgrades to its functionalities and interoperability capacity with devices. In one embodiment, device 204 is upgraded within the home. Energy manager 100 may then access, via server 225, device 204's manufacturer to receive upgraded energy standards for device 204.
It is important to note that energy manager 100 may be a direct replacement for the heating-cooling thermostat controller that connects to the home air conditioner/heater. For example, a consumer may purchase energy manager 100, pull their current thermostat off their household wall, and mount energy manager 100 in its place. Energy manager 100 then performs all of the air conditioner/heater operations that would be expected from the displaced heating-cooling thermostat as well as the operations attributable to energy manager 100 described herein. Furthermore, a new face plate may include, but is not limited to, an increased display size, a faster processor within, added features to make energy manager 100 more user friendly.
With reference to 310 of
With reference to 315 of
Thus, embodiments of the present invention enable the generation of an instruction for a user to modify an energy usage profile of one or more devices within a household to correlate to a desired energy usage for that device and/or household. Additionally, embodiments of the present invention enable the generation of an instruction to automatically modify an energy usage profile of one or more devices within a household to correlate to a desired energy usage for that device and/or household. Furthermore, an instruction to modify an energy usage profile for a device and/or household may be based on instructions from a user and instructions from a utility company via a server.
Example Computer System Environment
With reference now to
System 400 of
System 400 also includes computer usable non-volatile memory 410, e.g. read only memory (ROM), coupled to bus 404 for storing static information and instructions for processors 406A, 406B, and 406C. Also present in system 400 is a data storage unit 412 (e.g., a magnetic or optical disk and disk drive) coupled to bus 404 for storing information and instructions. System 400 also includes an optional alpha-numeric input device 414 including alphanumeric and function keys coupled to bus 404 for communicating information and command selections to processor 406A or processors 406A, 406B, and 406C. System 400 also includes an optional cursor control device 416 coupled to bus 404 for communicating user input information and command selections to processor 406A or processors 406A, 406B, and 406C. System 400 of the present embodiment also includes an optional display device 418 coupled to bus 404 for displaying information.
Referring still to
System 400 is also well suited to having a cursor directed by other means such as, for example, voice commands. System 400 also includes an I/O device 420 for coupling system 400 with external entities.
Referring still to
Computing system 400 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the present invention. Neither should the computing environment 400 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example computing system 400.
The present invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The present invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer-storage media including memory-storage devices.
With reference to 505 of
In one embodiment, method 500 further comprises estimating savings with regards to replacing device 204 with a new device, wherein the estimating is based on the analysis described herein of method 500. For example, by installing energy manager 100, user 255 can get contextual advice on how to efficiently and affordably upgrade user's 255 current HVAC unit. Energy manager 100 estimates how much money would be saved by installing a new HVAC unit based on algorithms that do the following: measure, store, and analyze energy usage history; utilize a Seasonal Energy Efficiency Rating (SEER) of a new HVAC unit and how it would profile in the current household; and measure current HVAC unit run time and the temperature drop rate over various time intervals.
Energy manager 100 may, through its back-end server 225 connection in Internet 245, enable partnerships with local (or national) HVAC companies. Energy manager 100 may change its line-up of eligible replacement HVAC units based on factors such as pricing and availability in real-time. Energy manager 100 may provide contextual advertisement for HVAC unit vendors, or for any other product or service. The messaging from energy manager's 100 face-plate, connected PC interface, or connected mobile interface provides such useful information as, “You would save $130 per month if you upgraded to a Y SEER AC.”
In yet another embodiment of the present invention, method 500 further comprises generating an analysis that informs user 255 of the costs associated with changing the settings of device 204. For example, energy manager 100 may generate an analysis that informs user 255 that changing the dishwasher to run at half power instead of at full power may save user 255 $20 per month.
In another embodiment, method 500 further comprises comparing the energy usage of first structure 140 with an energy usage of a second structure based on the analysis described herein of method 500. For example, with energy managers 100 in different homes, comparisons may be made between and among homes. A home in neighborhood N1 can compare its energy usage to a friend's home in neighborhood N2. Energy manager 100 may then relay to user 255 the following, “Your friend, Jim Smith, is spending $500 per month to heat/cool their house.” Or, energy manager 100 may relay to user 255, “Your sister's fridge is costing $50 per month to keep the food cold, which is in the top 10% of homes in the nation in terms of effectiveness and efficiency.” This neighbor comparison functionality works on competitive psychology. This functionality enables more sales of new and energy efficient units and overall electricity conservation for the power energy grid.
In another embodiment, method 500 further comprises alerting user 255 to specific maintenance tasks for device 204 that are recommended based on an analysis of energy usage of device 204 described herein. For example, method 500 comprises alerting user 255 that a new filter for device 204 is needed based on the analysis described herein of method 500. For example, energy manager 100 may estimate when enough time has passed based on overall usage to determine that a new filter for the HVAC unit is needed. Energy manager 100 may show reminders for replacing these HVAC filters. Energy manager 100 may show statistics on how much money is saved or lost by replacing or waiting to replace HVAC filters.
In another embodiment, method 500 further comprises calculating the efficiency of the HVAC correlated to the energy efficiency of the home (including insulation and air leakage through ducts, under doors, and around windows). For example, based on the duration that it takes to drop the temperature of the home to the desired temperature while taking into consideration the cost of electricity, energy manager 100 calculates the efficiency of the HVAC correlated to the energy efficiency of the home.
Similarly, energy manager 100 may calculate the current efficiency of an appliance such as a refrigerator. Utilizing an energy-measuring module 250a between the refrigerator and the electrical outlet, energy manager 100 can make algorithmic conclusions based on the setting and the history of the refrigerator. Thus, energy manager 100 may generate an analysis on the estimated energy efficiency of the refrigerator.
In another embodiment, method 500 further comprises alerting user 255 of a possible failure of device 204 based on an analysis of historical data or data on a remote server. This historical data includes the monitored energy usage data for device 204 described herein. Method 500 further comprises alerting user 255 of possible device 204 failure based on device's 204 history. For example, circuits sometimes begin to eat up larger and larger amounts of current or show erratic current draw before they fail. A “healthy history” of current usage per device 204 may be compared to current spikes or other erratic current draw to predict the failure of device 204.
In another embodiment, method 500 further comprises calculating the break even date of a replacement product. For example, energy manager 100 monitors the energy usage history for device 204. Then, after device 204 is replaced, energy manager 100 marks the replacement date. Energy manager 100 may then calculate the break even date and any realized savings based off of electric rate data. Energy manager 100 may then communicate these calculations to user 255 via graphical display module 215. Energy manager 100 may also communicate a victory notification to user 255.
In another embodiment, method 500 further comprises assisting user 255 with achieving a money savings goal by managing user's 255 energy usage. For example, a user's 255 financial savings goal and an interaction between user 255 and user's 255 device(s) 204 may result in a dialogue with device(s) 204 or even with the whole house. Energy manager 100 may also keep user 255 current on user's 255 financial savings. Energy manager 100 may tie its energy usage management of device(s) 204 with an incentive, such as, “By turning the AC up to 89 degrees, we are saving for our Fiji vacation.”.
In another embodiment, method 500 further comprises querying and negotiating with user 255 to assist user 255 in meeting an energy budget target. For example, energy manager 100 may both interview and negotiate with user 255. The interviews may be periodic questions, posed through user-interfaces. These question posed may relate to personal comfort, and preferences on HVAC and energy automation effectiveness. For example, one question might be, “Are you cold, hot, or just right at this time?” The answer to this question will inform energy manager 100 of the threshold of environmental comfort for user 255 based on a registered temperature reading. Energy manager 100 may also poll user 255 if user 255 is the only one home or if other friends or relatives are at home to determine what actions should be taken.
Another possible question may be, “We made the assumption due to the time of day and the day in the month not to turn the heat on at this time in order to save you money . . . did you like this decision?” A positive response from user 255 will reinforce the algorithmic decision made. Whereas a negative response will provide the initiative to make a change.
The negotiation (via email, SMS, Instant Messaging, or directly accessing the interface of energy manager 100) of user 255 with energy manager 100 relates to trying to help user 255 hit a pre-set energy budget target. For example, if after 20 days into the month the user's 255 trend line is above the forecasted month end bill and/or energy usage, energy manager 100 may send user 255 an SMS messaging requesting permission to turn the heat down three degrees.
In another embodiment, method 500 further comprises profiling a device 204 based on the history of device 204 and environmental factors. For example, energy manager 100 may support the use of one energy-measuring module 250a used to connect device 204 to energy manager 100. Based on the energy consumption over time and against assorted environmental factors energy manager 100 will profile device 100 as to its energy consumption, energy costs, and as a percentage of room device class, and whole-home totals. This one energy-measuring module 250a may be rotated around the home to eventually construct a whole home energy profile, with or without the presence of energy-measuring module 250b.
Furthermore, this device-level energy audit can be conducted over varying levels of time and report to user 255 its higher level of confidence on its estimates based on the variable of time allowed to measure a particular device 204. Energy manager 100 may compare similar devices of its class via information on Internet hosted servers. Moreover, energy manager 100 may compare similar devices for the home via historical information from one or more energy utility 240. Energy manager may also make a forecast regarding device 204 based on company trends and forecasts.
In another embodiment, method 500 further comprises managing an energy co-op of a pool of energy manager 100 user(s) 255. For example, energy manager(s) 100 is able to aggregate homes within and across neighborhoods, grouping them into a logical large single pool. A logical large single pool of houses might be homes located geographically near each other. Energy manager 100 thus provides a distributed “buying block” of energy user's 255. This “buying block”, having purchased from energy wholesalers, is able to act in a cooperative capacity as energy manager 100 user(s) 255. Beneficially, user(s) 255 would experience reduced energy costs. Server 225 may manage this co-op.
In yet another embodiment of the present technology, a plurality of energy usage signatures is aggregated by remote server 225. This plurality of energy usage signatures is compiled for comparison with subsequently received energy usage signatures. One or more of the energy usage signatures may be identified by user 255 of the device(s). In one embodiment, remote server 225 receives from user 255 of device 204 the identification information, including but not limited to device type, manufacturer, and model information to be associated with its energy usage signature. The server then aggregates this identification of device 204 in a database at server 225.
More particularly, energy manager 100 may detect a new energy usage signature within first structure 140. Energy manager 100 may notify user 255 that a new energy usage signature (device 204) exists and prompt user 255 for the device's identification. User 255 then may identify device 204 as washer model #4305. Energy manager 100 then sends this energy usage signature along with its identification to server 225. Remote server 255 stores this identification in a database that is accessible to users of device 204 and devices other than device 204. In this way, a database of energy usage signatures and related identifications is built and accessible by, but not limited to, users of various devices, manufacturers, and energy utility companies.
In another embodiment, the plurality of energy usage signatures of first structure 140 received by server 225 are provided for use and comparison of one or more energy usage signatures by an energy manager 100 in a second structure. For example, the energy usage signatures detected in structure 140 and their identification that is stored in a database at server 225 are provided to an energy manager 100 of a second structure for use and comparison with one or more energy usage signatures therein.
For example, energy manager 100 of a second structure uses the identified energy usage signatures associated with the devices in first structure 140 to identify the energy usage signatures detected in the second structure. In this manner, energy manager 100 takes advantage of a database of identifications of energy usage signatures located at a remote server in order to more quickly identify the devices within a household with which it is coupled. Of note, users of devices coupled with different structures provide assistance in the collection and identification of energy usage signatures for any number of devices.
With reference to 610 of
User 255 may access these instructions at, but not limited to, energy manager 100, at a device coupled with first structure 140, at a server 255 coupled with energy manager 100 and/or first structure 140, and/or at a device at a second structure coupled wired or wirelessly with first structure 140.
With reference to 615 of
Thus, embodiments of the present invention enable the generation of an instruction for a human user to modify an energy usage profile of one or more devices within a household to correlate to a desired energy usage for that device and/or household. Additionally, embodiments of the present invention enable the generation of an instruction to automatically modify an energy usage profile of one or more devices within a household to correlate to a desired energy usage for that device and/or household.
Thus, embodiments of the present invention increase consumer awareness as to conservation of energy by enabling the generation of an analysis of a device's energy usage. In one embodiment, the analysis informs a consumer of estimated savings with regards to replacing a device with a new device. In another embodiment, the analysis provides a comparison of the energy usage and energy costs of two different households. Furthermore, embodiments of the present invention inform a consumer when a new filter for a device is needed based on a generated analysis. Thus, embodiments of the present invention are beneficial by increasing a consumer's awareness of energy conservation opportunities.
Although the subject matter has been described in a language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
This application is a continuation of U.S. patent application Ser. No. 14/473,906 filed Aug. 29, 2014, which is incorporated herein by reference. U.S. patent application Ser. No. 14/473,906 is a continuation of U.S. patent application Ser. No. 13/327,459 filed on Dec. 15, 2011, which is incorporated herein by reference. U.S. patent application Ser. No. 13/327,459 is a continuation of U.S. patent application Ser. No. 12/241,588 filed on Sep. 30, 2008 (now U.S. Pat. No. 8,160,752), which is incorporated herein by reference. Furthermore, the subject matter of this application relates to the subject matter of the commonly assigned U.S. Provisional Application No. 60/977,015, filed on Oct. 2, 2007, entitled: “ENERGY MANAGEMENT PLATFORM,” which is incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
3991357 | Kaminski | Nov 1976 | A |
4117537 | Muench | Sep 1978 | A |
4183290 | Kucharczyk | Jan 1980 | A |
4223831 | Szarka | Sep 1980 | A |
4261037 | Hicks | Apr 1981 | A |
4324987 | Sullivan et al. | Apr 1982 | A |
4335847 | Levine | Jun 1982 | A |
4408711 | Levine | Oct 1983 | A |
4567557 | Bums | Jan 1986 | A |
4615380 | Beckey | Oct 1986 | A |
4644320 | Carr et al. | Feb 1987 | A |
4674027 | Beckey | Jun 1987 | A |
4682473 | Rogers, III | Jul 1987 | A |
4685614 | Levine | Aug 1987 | A |
4751961 | Levine et al. | Jun 1988 | A |
4897798 | Cler | Jan 1990 | A |
5086385 | Launey et al. | Feb 1992 | A |
5088645 | Bell | Feb 1992 | A |
5211332 | Adams | May 1993 | A |
5240178 | Dewolf et al. | Aug 1993 | A |
5244146 | Jefferson et al. | Sep 1993 | A |
5289362 | Liebl et al. | Feb 1994 | A |
5386491 | Mewissen et al. | Jan 1995 | A |
5395042 | Riley et al. | Mar 1995 | A |
5436510 | Gilbert | Jul 1995 | A |
5476221 | Seymour | Dec 1995 | A |
5481140 | Maruyama et al. | Jan 1996 | A |
5499196 | Pacheco | Mar 1996 | A |
5544036 | Brown et al. | Aug 1996 | A |
5555927 | Shah | Sep 1996 | A |
5611484 | Uhrich | Mar 1997 | A |
5684710 | Ehlers et al. | Nov 1997 | A |
5729474 | Hildebrand | Mar 1998 | A |
5778683 | Drees et al. | Jul 1998 | A |
5808294 | Neumann | Sep 1998 | A |
5833134 | Ho et al. | Nov 1998 | A |
5875430 | Koether | Feb 1999 | A |
5902183 | D'Souza | May 1999 | A |
5909378 | De Milleville | Jun 1999 | A |
5918474 | Khanpara et al. | Jul 1999 | A |
5924072 | Havens | Jul 1999 | A |
5924486 | Ehlers et al. | Jul 1999 | A |
5962989 | Baker | Oct 1999 | A |
5971597 | Baldwin et al. | Oct 1999 | A |
5977964 | Williams et al. | Nov 1999 | A |
6062482 | Gauthier et al. | May 2000 | A |
6066843 | Scheremeta | May 2000 | A |
6072784 | Agrawal et al. | Jun 2000 | A |
6095427 | Hoium et al. | Aug 2000 | A |
6098893 | Berglund et al. | Aug 2000 | A |
6108685 | Kutzik et al. | Aug 2000 | A |
6121593 | Mansbery et al. | Sep 2000 | A |
6122603 | Budike, Jr. | Sep 2000 | A |
6134511 | Subbarao | Oct 2000 | A |
6178362 | Woolard et al. | Jan 2001 | B1 |
6216956 | Ehlers et al. | Apr 2001 | B1 |
6349883 | Simmons et al. | Feb 2002 | B1 |
6356204 | Guindi et al. | Mar 2002 | B1 |
6370894 | Thompson et al. | Apr 2002 | B1 |
6385510 | Hoog et al. | May 2002 | B1 |
6396531 | Gerszberg et al. | May 2002 | B1 |
6415205 | Myron et al. | Jul 2002 | B1 |
6448896 | Bankus et al. | Sep 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6480803 | Pierret | Nov 2002 | B1 |
6528957 | Luchaco | Mar 2003 | B1 |
6591620 | Kikuchi et al. | Jul 2003 | B2 |
6645066 | Gutta et al. | Nov 2003 | B2 |
6654689 | Kelley et al. | Nov 2003 | B1 |
6704742 | Huth et al. | Mar 2004 | B1 |
6769482 | Wagner et al. | Aug 2004 | B2 |
6772096 | Murakami et al. | Aug 2004 | B2 |
6782294 | Reich et al. | Aug 2004 | B2 |
6785592 | Smith et al. | Aug 2004 | B1 |
6789739 | Rosen | Sep 2004 | B2 |
6868293 | Schurr et al. | Mar 2005 | B1 |
6874691 | Hildebrand et al. | Apr 2005 | B1 |
6983210 | Matsubayashi et al. | Jan 2006 | B2 |
6990821 | Singh et al. | Jan 2006 | B2 |
7024336 | Salsbury et al. | Apr 2006 | B2 |
7043341 | Gaullupe | May 2006 | B2 |
7055759 | Wacker et al. | Jun 2006 | B2 |
7062361 | Lane | Jun 2006 | B1 |
7092794 | Hill et al. | Aug 2006 | B1 |
7130719 | Ehlers et al. | Oct 2006 | B2 |
7149605 | Chassin et al. | Dec 2006 | B2 |
7149727 | Nicholls et al. | Dec 2006 | B1 |
7149729 | Kaasten et al. | Dec 2006 | B2 |
7185504 | Kasai et al. | Mar 2007 | B2 |
7188482 | Sadegh et al. | Mar 2007 | B2 |
7197365 | Hori et al. | Mar 2007 | B2 |
7218998 | Neale | May 2007 | B1 |
7225171 | Kikuchi et al. | May 2007 | B2 |
7232075 | Rosen | Jun 2007 | B1 |
7243044 | McCalla | Jul 2007 | B2 |
7274975 | Miller | Sep 2007 | B2 |
7317404 | Cumeralto et al. | Jan 2008 | B2 |
7353121 | Baraty | Apr 2008 | B2 |
7364093 | Garozzo | Apr 2008 | B2 |
7379791 | Tamarkin et al. | May 2008 | B2 |
RE40437 | Rosen | Jul 2008 | E |
7434742 | Mueller et al. | Oct 2008 | B2 |
7451937 | Flood et al. | Nov 2008 | B2 |
7469550 | Chapman, Jr. et al. | Dec 2008 | B2 |
7496430 | Mak | Feb 2009 | B2 |
7565227 | Richard et al. | Jul 2009 | B2 |
7636666 | van Putten et al. | Dec 2009 | B2 |
7644869 | Hoglund et al. | Jan 2010 | B2 |
7702424 | Cannon et al. | Apr 2010 | B2 |
7706928 | Howell et al. | Apr 2010 | B1 |
7738972 | Pouchak | Jun 2010 | B2 |
7747399 | Smith et al. | Jun 2010 | B2 |
7784704 | Harter | Aug 2010 | B2 |
7802618 | Simon et al. | Sep 2010 | B2 |
7839275 | Spalink et al. | Nov 2010 | B2 |
7848900 | Steinberg et al. | Dec 2010 | B2 |
7849698 | Harrod et al. | Dec 2010 | B2 |
7854389 | Ahmed | Dec 2010 | B2 |
7894943 | Sloup et al. | Feb 2011 | B2 |
8010237 | Cheung et al. | Aug 2011 | B2 |
8019567 | Steinberg et al. | Sep 2011 | B2 |
8021618 | Cooper | Sep 2011 | B1 |
8037022 | Rahman et al. | Oct 2011 | B2 |
8042048 | Wilson et al. | Oct 2011 | B2 |
8078330 | Brickfield | Dec 2011 | B2 |
8090477 | Steinberg | Jan 2012 | B1 |
8091375 | Crawford | Jan 2012 | B2 |
8095233 | Shankar et al. | Jan 2012 | B1 |
8131497 | Steinberg et al. | Mar 2012 | B2 |
8160752 | Weaver et al. | Apr 2012 | B2 |
8174381 | Imes et al. | May 2012 | B2 |
8180492 | Steinberg | May 2012 | B2 |
8219249 | Harrod et al. | Jul 2012 | B2 |
8423322 | Steinberg et al. | Apr 2013 | B2 |
8450995 | Wagner | May 2013 | B2 |
8457796 | Thind | Jun 2013 | B2 |
9081405 | Weaver et al. | Jul 2015 | B2 |
9322565 | Weaver et al. | Apr 2016 | B2 |
9500385 | Weaver et al. | Nov 2016 | B2 |
9507362 | Weaver et al. | Nov 2016 | B2 |
9507363 | Weaver et al. | Nov 2016 | B2 |
9523993 | Weaver et al. | Dec 2016 | B2 |
9600011 | Weaver et al. | Mar 2017 | B2 |
10048712 | Weaver et al. | Aug 2018 | B2 |
10108217 | Weaver et al. | Oct 2018 | B2 |
20010013123 | Freeman et al. | Aug 2001 | A1 |
20010025209 | Fukui et al. | Sep 2001 | A1 |
20010034569 | Yamamoto et al. | Oct 2001 | A1 |
20020013689 | Hunton | Jan 2002 | A1 |
20020024332 | Gardner | Feb 2002 | A1 |
20020059617 | Terakado et al. | May 2002 | A1 |
20020124992 | Rainer et al. | Sep 2002 | A1 |
20020178047 | Or et al. | Nov 2002 | A1 |
20020198629 | Ellis | Dec 2002 | A1 |
20030009401 | Ellis | Jan 2003 | A1 |
20030036810 | Petite | Feb 2003 | A1 |
20030036822 | Davis | Feb 2003 | A1 |
20030050738 | Masticola et al. | Mar 2003 | A1 |
20030066897 | Carner et al. | Apr 2003 | A1 |
20030070438 | Kikuchi et al. | Apr 2003 | A1 |
20030150927 | Rosen | Aug 2003 | A1 |
20030167150 | Shimura et al. | Sep 2003 | A1 |
20030171851 | Brickfield et al. | Sep 2003 | A1 |
20030187549 | Bohrer et al. | Oct 2003 | A1 |
20030192328 | Kikuchi et al. | Oct 2003 | A1 |
20030193405 | Hunt et al. | Oct 2003 | A1 |
20030216837 | Reich et al. | Nov 2003 | A1 |
20030216971 | Sick et al. | Nov 2003 | A1 |
20030233172 | Granqvist et al. | Dec 2003 | A1 |
20030233201 | Horst et al. | Dec 2003 | A1 |
20040002792 | Hoffknecht | Jan 2004 | A1 |
20040010561 | Kim et al. | Jan 2004 | A1 |
20040034484 | Solomita et al. | Feb 2004 | A1 |
20040088082 | Ahmed | May 2004 | A1 |
20040095237 | Chen et al. | May 2004 | A1 |
20040117330 | Ehlers et al. | Jun 2004 | A1 |
20040133314 | Ehlers | Jul 2004 | A1 |
20040192329 | Barbosa et al. | Sep 2004 | A1 |
20040225649 | Yeo et al. | Nov 2004 | A1 |
20040230344 | Gallupe et al. | Nov 2004 | A1 |
20040238653 | Alles | Dec 2004 | A1 |
20040249479 | Shorrock | Dec 2004 | A1 |
20040260490 | Matsubayashi et al. | Dec 2004 | A1 |
20050038571 | Brickfield et al. | Feb 2005 | A1 |
20050040943 | Winick | Feb 2005 | A1 |
20050043862 | Brickfield et al. | Feb 2005 | A1 |
20050043907 | Eckel | Feb 2005 | A1 |
20050049789 | Kelly et al. | Mar 2005 | A1 |
20050090915 | Geiwitz | Apr 2005 | A1 |
20050096797 | Matsubara et al. | May 2005 | A1 |
20050103874 | Erdman, Jr. | May 2005 | A1 |
20050119793 | Amundson et al. | Jun 2005 | A1 |
20050120012 | Poth et al. | Jun 2005 | A1 |
20050128067 | Zakrewski | Jun 2005 | A1 |
20050150968 | Shearer | Jul 2005 | A1 |
20050154495 | Shah | Jul 2005 | A1 |
20050171645 | Oswald et al. | Aug 2005 | A1 |
20050189429 | Breeden | Sep 2005 | A1 |
20050192727 | Shostak et al. | Sep 2005 | A1 |
20050192915 | Ahmed et al. | Sep 2005 | A1 |
20050194455 | Alles | Sep 2005 | A1 |
20050194456 | Tessier et al. | Sep 2005 | A1 |
20050234596 | Rietschel | Oct 2005 | A1 |
20050234600 | Boucher et al. | Oct 2005 | A1 |
20050245839 | Stivoric et al. | Nov 2005 | A1 |
20050270151 | Winick | Dec 2005 | A1 |
20050280421 | Yomoda et al. | Dec 2005 | A1 |
20060030954 | Bergman et al. | Feb 2006 | A1 |
20060065750 | Fairless | Mar 2006 | A1 |
20060080246 | Wyckoff | Apr 2006 | A1 |
20060106741 | Janarthanan | May 2006 | A1 |
20060111816 | Spalink et al. | May 2006 | A1 |
20060142900 | Rothman et al. | Jun 2006 | A1 |
20060149395 | Archacki et al. | Jul 2006 | A1 |
20060149414 | Archacki et al. | Jul 2006 | A1 |
20060167591 | McNally | Jul 2006 | A1 |
20060186214 | Simon et al. | Aug 2006 | A1 |
20060196953 | Simon et al. | Sep 2006 | A1 |
20060206220 | Amundson | Sep 2006 | A1 |
20060259199 | Gjerde et al. | Nov 2006 | A1 |
20060259332 | Brown | Nov 2006 | A1 |
20060267574 | Howard | Nov 2006 | A1 |
20060276938 | Miller | Dec 2006 | A1 |
20070043477 | Ehlers et al. | Feb 2007 | A1 |
20070045431 | Chapman, Jr. et al. | Mar 2007 | A1 |
20070067068 | Havlena et al. | Mar 2007 | A1 |
20070114295 | Jenkins | May 2007 | A1 |
20070115902 | Shamoon et al. | May 2007 | A1 |
20070118831 | Kondo | May 2007 | A1 |
20070138307 | Khoo | Jun 2007 | A1 |
20070155349 | Nelson et al. | Jul 2007 | A1 |
20070155379 | Shamoon et al. | Jul 2007 | A1 |
20070199336 | Tantot | Aug 2007 | A1 |
20070203860 | Golden et al. | Aug 2007 | A1 |
20070205297 | Finkam et al. | Sep 2007 | A1 |
20070214368 | Ota et al. | Sep 2007 | A1 |
20070227721 | Springer et al. | Oct 2007 | A1 |
20070239317 | Bogolea et al. | Oct 2007 | A1 |
20070250386 | Wyckoff | Oct 2007 | A1 |
20070276547 | Miller | Nov 2007 | A1 |
20080004725 | Wacker et al. | Jan 2008 | A1 |
20080011864 | Tessier et al. | Jan 2008 | A1 |
20080015740 | Osann | Jan 2008 | A1 |
20080015742 | Kulyk et al. | Jan 2008 | A1 |
20080147205 | Ollis et al. | Jun 2008 | A1 |
20080167756 | Golden et al. | Jul 2008 | A1 |
20080177423 | Brickfield et al. | Jul 2008 | A1 |
20080183335 | Poth et al. | Jul 2008 | A1 |
20080191045 | Harter | Aug 2008 | A1 |
20080221737 | Josephson et al. | Sep 2008 | A1 |
20080229226 | Rowbottom et al. | Sep 2008 | A1 |
20080273754 | Hick et al. | Nov 2008 | A1 |
20080277486 | Seem et al. | Nov 2008 | A1 |
20080281473 | Pitt | Nov 2008 | A1 |
20080282182 | Oosaka | Nov 2008 | A1 |
20080313021 | Nagafuchi et al. | Dec 2008 | A1 |
20080317292 | Baker et al. | Dec 2008 | A1 |
20090006873 | Bellofatto et al. | Jan 2009 | A1 |
20090018706 | Wittner | Jan 2009 | A1 |
20090021993 | Nakazawa | Jan 2009 | A1 |
20090043548 | Beekhuis | Feb 2009 | A1 |
20090045804 | Durling et al. | Feb 2009 | A1 |
20090050703 | Lifson et al. | Feb 2009 | A1 |
20090062970 | Forbes et al. | Mar 2009 | A1 |
20090076748 | Robertson et al. | Mar 2009 | A1 |
20090083167 | Subbloie | Mar 2009 | A1 |
20090099699 | Steinberg et al. | Apr 2009 | A1 |
20090171862 | Harrod et al. | Jul 2009 | A1 |
20090177294 | Baraty | Jul 2009 | A1 |
20090229288 | Alston et al. | Sep 2009 | A1 |
20090240381 | Lane | Sep 2009 | A1 |
20090254225 | Boucher et al. | Oct 2009 | A1 |
20090259713 | Blumrich et al. | Oct 2009 | A1 |
20090297901 | Kilian et al. | Dec 2009 | A1 |
20090307573 | Lavelle et al. | Dec 2009 | A1 |
20090309541 | Walrath | Dec 2009 | A1 |
20090327354 | Resnick et al. | Dec 2009 | A1 |
20100019051 | Rosen | Jan 2010 | A1 |
20100025483 | Hoeynck et al. | Feb 2010 | A1 |
20100063832 | Brown | Mar 2010 | A1 |
20100070084 | Steinberg et al. | Mar 2010 | A1 |
20100070086 | Harrod et al. | Mar 2010 | A1 |
20100070234 | Steinberg | Mar 2010 | A1 |
20100082174 | Weaver | Apr 2010 | A1 |
20100084482 | Kennedy et al. | Apr 2010 | A1 |
20100167783 | Alameh et al. | Jul 2010 | A1 |
20100168924 | Tessier et al. | Jul 2010 | A1 |
20100179704 | Ozog | Jul 2010 | A1 |
20100198713 | Forbes, Jr. et al. | Aug 2010 | A1 |
20100211224 | Keeling et al. | Aug 2010 | A1 |
20100222935 | Forbes et al. | Sep 2010 | A1 |
20100228601 | Vaswani et al. | Sep 2010 | A1 |
20100235004 | Thind | Sep 2010 | A1 |
20100262298 | Johnson et al. | Oct 2010 | A1 |
20100262299 | Cheung et al. | Oct 2010 | A1 |
20100280667 | Steinberg | Nov 2010 | A1 |
20100289643 | Trundle et al. | Nov 2010 | A1 |
20100308119 | Steinberg et al. | Dec 2010 | A1 |
20100318227 | Steinberg et al. | Dec 2010 | A1 |
20100324962 | Nesler et al. | Dec 2010 | A1 |
20110035060 | Oswald | Feb 2011 | A1 |
20110046792 | Imes et al. | Feb 2011 | A1 |
20110046805 | Bedros et al. | Feb 2011 | A1 |
20110046806 | Nagel et al. | Feb 2011 | A1 |
20110077758 | Tran et al. | Mar 2011 | A1 |
20110077896 | Steinberg et al. | Mar 2011 | A1 |
20110130887 | Ehlers, Sr. | Jun 2011 | A1 |
20110151837 | Winbush, III | Jun 2011 | A1 |
20110160913 | Parker et al. | Jun 2011 | A1 |
20110161251 | Carey et al. | Jun 2011 | A1 |
20110172841 | Forbes, Jr. | Jul 2011 | A1 |
20110185895 | Freen | Aug 2011 | A1 |
20110307103 | Cheung et al. | Dec 2011 | A1 |
20110307112 | Barrilleaux | Dec 2011 | A1 |
20120017611 | Coffel et al. | Jan 2012 | A1 |
20120065935 | Steinberg et al. | Mar 2012 | A1 |
20120085831 | Kopp | Apr 2012 | A1 |
20120089269 | Weaver et al. | Apr 2012 | A1 |
20120101637 | Imes et al. | Apr 2012 | A1 |
20120158350 | Steinberg et al. | Jun 2012 | A1 |
20120221151 | Steinberg | Aug 2012 | A1 |
20120252430 | Imes et al. | Oct 2012 | A1 |
20130151012 | Shetty et al. | Jun 2013 | A1 |
20150295408 | Weaver et al. | Oct 2015 | A1 |
20150301549 | Weaver et al. | Oct 2015 | A1 |
Number | Date | Country |
---|---|---|
2202008 | Feb 2000 | CA |
196069 | Dec 1991 | EP |
59106311 | Jun 1984 | JP |
01252850 | Oct 1989 | JP |
2008092681 | Apr 2008 | JP |
200249310 | Jun 2002 | WO |
2007-117245 | Oct 2007 | WO |
Entry |
---|
Applicant-Initiated Interview Summary dated Jul. 15, 2015, for U.S. Appl. No. 14/473,906, 4 pages. |
Applicant-Initiated Interview Summary dated Sep. 9, 2015, for U.S. Appl. No. 14/473,906, 3 pages. |
Applicant-Initiated Summary dated Apr. 18, 2016, for U.S. Appl. No. 14/473,906, 4 pages. |
Final Office Action dated Jul. 8, 2015, for U.S. Appl. No. 13/327,459, 25 pages. |
Final Office Action dated Mar. 30, 2011, for U.S. Appl. No. 12/241,588, 16 pages. |
Final Office Action dated May 1, 2015, for U.S. Appl. No. 14/473,906, 31 pages. |
Final Office Action dated Sep. 29, 2015, for U.S. Appl. No. 14/473,925, 40 pages. |
First Action Interview Pilot Program Pre-Interview Communication dated Jan. 2, 2015, for U.S. Appl. No. 14/473,925, 7 pages. |
Marceau, et al., titled, “Nonintrusive Load Disaggregation Computer Program to Estimate Energy Consumption of Major End Uses in Residential Buildings”, IEEE, 1999, pp. 1389-1403. |
Non-Final Office Action dated Apr. 21, 2015, for U.S. Appl. No. 14/473,925, 40 pages. |
Non-Final Office Action dated Dec. 21, 2015, for U.S. Appl. No. 14/473,906, 34 pages. |
Non-Final Office Action dated Dec. 29, 2014, for U.S. Appl. No. 14/473,906, 29 pages. |
Non-Final Office Action dated Jan. 15, 2016, for U.S. Appl. No. 14/789,716, 8 pages. |
Non-Final Office Action dated Jan. 9, 2015, for U.S. Appl. No. 13/327,459, 26 pages. |
Non-Final Office Action dated Mar. 1, 2016, for U.S. Appl. No. 13/327,459, 21 pages. |
Non-Final Office Action dated Mar. 16, 2016, for U.S. Appl. No. 14/473,925, 39 pages. |
Non-Final Office Action dated Oct. 13, 2010, for U.S. Appl. No. 12/241,588, 12 pages. |
Notice of Allowance and Fee(s) due dated Sep. 16, 2011, for U.S. Appl. No. 12/241,588, 9 pages. |
Notice of Publication dated Apr. 12, 2012, for U.S. Appl. No. 13/327,459. |
Notice of Publication dated Dec. 18, 2014, for U.S. Appl. No. 14/473,893. |
Notice of Publication dated Dec. 18, 2014, for U.S. Appl. No. 14/473,906. |
Notice of Publication dated Dec. 18, 2014, for U.S. Appl. No. 14/473,925. |
Notice of Publication dated Oct. 22, 2015, for U.S. Appl. No. 14/789,716. |
Preinterview First Office Action dated Dec. 24, 2014, for U.S. Appl. No. 14/473,893, 5 pages. |
Preinterview First Office Action dated Dec. 3, 2014, for U.S. Appl. No. 14/473,906, 31 pages. |
U.S. Appl. No. 14/752,453, filed Jun. 26, 2015, 31 pages. |
First Action Interview Office Action Summary dated Feb. 4, 2015, for U.S. Appl. No. 14/473,893, 5 pages. |
Notice of Allowance and Fee(s) due dated Apr. 24, 2015, for U.S. Appl. No. 14/473,893, 11 pages. |
Notice of Publication dated Dec. 18, 2014, for U.S. Appl. No. 14/475,274. |
Notice of Publication dated Mar. 5, 2015, for U.S. Appl. No. 14/542,252. |
Notice of Publication dated Dec. 18, 2014, for U.S. Appl. No. 14/475,029. |
Non-Final Office Action dated Dec. 24, 2014, for U.S. Appl. No. 14/475,029, 12 pages. |
First Action Interview Pilot Program Pre-Interview Communication dated Mar. 24, 2015, for U.S. Appl. No. 14/475,029, 4 pages. |
Non-Final Office Action dated May 18, 2015, for U.S. Appl. No. 14/475,029, 10 pages. |
Final Office Action dated Sep. 1, 2015, for U.S. Appl. No. 14/475,029, 10 pages. |
Examiner-Initiated Interview Summary dated Dec. 18, 2015, for U.S. Appl. No. 14/475,029, 2 pages. |
Notice of Publication dated Feb. 26, 2015, for U.S. Appl. No. 14/528,995. |
Aprilaire Electronic Thermostats Model 8355 User's Manual, Research Products Corporation, Revised Dec. 2000, 16 pages. |
Braeburn 5300 Installer Guide, Braeburn Systems, LLC, 2009, 10 pages. |
Braeburn Model 5200, Braeburn Systems, LLC, 2011, 11 pages. |
Ecobee Smart Si Thermostat Installation Manual, Ecobee, 2012, 40 pages. |
Ecobee Smart Si Thermostat User Manual, Ecobee, 2012, 44 pages. |
Ecobee Smart Thermostat Installation Manual, 2011, 20 pages. |
Ecobee Smart Thermostat User Manual, 2010, 20 pages. |
Electric Heat Lock Out on Heat Pumps, Washington State University Extension Energy Program, Apr. 2010, pp. 1-3. |
Honeywell Installation Guide FocusPRO TH6000 Series, Honeywell International, Inc., 2012, 24 pages. |
Honeywell Operating Manual FocusPRO TH6000 Series, Honeywell International, Inc., 2011, 80 pages. |
Honeywell Prestige IAQ Product Data 2, Honeywell International, Inc., 2012, 126 pages. |
Honeywell Prestige THX9321 and TXH9421 Product Data, Honeywell International, Inc., 68/0311, 2012, 126 pages. |
Honeywell Prestige THX9321-9421 Operating Manual, Honeywell International, Inc., 2011, 120 pages. |
Hunter Internet Thermostat Installation Guide, Hunter Fan Co., Aug. 14, 2012, 8 pages. |
Introducing the New Smart Si Thermostat, Datasheet [online]. Ecobee, [retrieved on Feb. 25, 2013]. Retrieved from the Internet: <URL: https://www.ecobee.com/solutions/home/smart-si/>, 4 pages. |
Lennox ComfortSense 5000 Owners Guide, Lennox Industries, Inc., Feb. 2008, 32 pages. |
Lennox ComfortSense 7000 Owners Guide, Lennox Industries, Inc., May 2009, 15 pages. |
Lennox iComfort Manual, Lennox Industries, Inc., Dec. 2010, 20 pages. |
Lux PSPU7323T Manual, LUX Products Corporation, 2009, 48 pages. |
NetX RP32-WIFI Network Thermostat Consumer Brochures, Network Thermostat, 2011, 2 pages. |
NetX RP32-WIFI Network Thermostat Specification Sheet, Network Thermostat, 2012, 2 pages. |
RobertShaw Product Manual 9620, Maple Chase Company, 2001, 14 pages. |
RobertShaw Product Manual 9825i2, Maple Chase Company, Jul. 17, 2006, 36 pages. |
SYSTXCCUIZ01-V Infinity Control Installation Instructions, Carrier Corp, May 31, 2012, 20 pages. |
T8611G Chronotherm IV Deluxe Programmable Heat Pump Thermostat Product Data, Honeywell Internationl Inc., 1997, 24 pages. |
TB-PAC, TB-PHP, Base Series Programmable Thermostats, Carrier Corp, May 14, 2012, 8 pages. |
The Perfect Climate Comfort Center PC8900A W8900A-C Product Data Sheet, Honeywell International Inc., Revised Apr. 2001, 44 pages. |
TP-PAC, TP-PHP, TP-NAC, TP-NHP Performance Series AC/HP Thermostat Instllation Instructions, Carrier Corp, 2007, Edition Date: Sep. 2007, 56 pages. |
Trane Communicating Thermostats for Fan Coil, Trane, May 2011, 32 pages. |
Trane Communicating Thermostats for Heat Pump Control, Trane, May 2011, 32 pages. |
Trane Install XL600 Installation Manual, Trane, Mar. 2006, 16 pages. |
Trane XL950 Installation Guide, Trane, Mar. 2011, 20 pages. |
Venstar T2900 Manual, Venstar, Inc., 2008, 113 pages. |
Venstar T5800 Manual, Venstar, Inc., 7, 2011, 63 pages. |
Vision PRO TH8000 Series Installation Guide, Honeywell International, Inc., 2012, 12 pages. |
Vision PRO TH8000 Series Operating Manual, Honeywell International, Inc., 2011, 96 pages. |
VisionPRO Wi-Fi Programmable Thermostat, Honeywell International, Inc., Operating Manual, Aug. 2012, 48 pages. |
White Rodgers (Emerson) Model 1F81-261 Installation and Operating Instructions, White Rodgers, 2010, 8 pages. |
White Rodgers (Emerson) Model IF98EZ-1621 Homeowner's User Guide, White Rodgers, 2012, 28 pages. |
Akhlaghinia et al., “Occupancy Monitoring in Intelligent Environment through Integrated Wireless Localizing Agents”, IEEE, 2009, 7 pages. |
Akhlaghinia et al., “Occupant Behaviour Prediction in Ambient Intelligence Computing Environment”, Journal of Uncertain Systems, vol. 2, No. 2, 2008, pp. 85-100. |
Allen et al., “Real-Time Earthquake Detection and Hazard Assessment by ElarmS Across California”, Geophysical Research Letters, vol. 36, L00B08, Mar. 2009, pp. 1-6. |
Chatzigiannakis et al., “Priority Based Adaptive Coordination of Wireless Sensors and Actors”, [online] Q2SWinet '06, Oct. 2, 2006 [Retrieved on Mar. 12, 2012]. Retrieved from the Internet: <URL: http://dl.acm.org/citation.cfm?id=1163681>. |
Deleeuw, “Ecobee WiFi Enabled Smart Thermostat Part 2: The Features Review”, Retrieved from <URL: http://www. homenetworkenabled.com/content.php?136-ecobee-WiFi-enabled-Smart-Thermostat-Part-2-The-Features-review>, Dec. 2, 2011, 5 pages. |
Gao et al., “The Self-Programming Thermostat: Optimizing Setback Schedules Based on Home Occupancy Patterns”, In Proceedings of the First ACM Workshop on Embedded Sensing Systems for Energy-Efficiency in Buildings, Nov. 3, 2009, 6 pages. |
Loisos et al., “Buildings End-Use Energy Efficiency: Alternatives to Compressor Cooling”, California Energy Commission, Public Interest Energy Research, Jan. 2000, 80 pages. |
Lu et al., “The Smart Thermostat: Using Occupancy Sensors to Save Energy in Homes”, In Proceedings of the 8th ACM Conference on Embedded Networked Sensor Systems, Nov. 3-5, 2010, pp. 211-224. |
Mozer, “The Neural Network House: An Environmental that Adapts to its Inhabitants”, AAAI Technical Report SS-98-02, 1998, pp. 110-114. |
Ros et al., “Multi-Sensor Human Tracking with the Bayesian Occupancy Filter”, IEEE, 2009, 8 pages. |
Wong et al., “Maximum Likelihood Estimation of ARMA Model with Error Processes for Replicated Observations”, National University of Singapore, Department of Economics, Working Paper No. 0217, 2002, 19 pages. |
Lien et al., “Remote-Controllable Power Outlet System for Home Power Management”, IEEE, Nov. 2007, pp. 1634-1641. |
Final office action dated Sep. 19, 2018 in related U.S. Appl. No. 15/351,202, all pages. |
U.S. Appl. No. 14/528,995, filed Oct. 30, 2014, Final Office Action dated May 22, 2017, all pages. |
Daryanian et al., “An Experiment in Real Time Pricing for Control of Electric Thermal Storage Systems”, “Transactions of Power Systems”, vol. 6, No. 4, Nov. 1991_pp. 1356-1365. |
U.S. Appl. No. 14/475,274, filed Sep. 2, 2014, First Action Interview Pilot Program Pre-Interview Communication dated Mar. 1, 2017, all pages. |
U.S. Appl. No. 14/475,274, filed Sep. 2, 2014, Non-Final Office Action dated Apr. 19, 2017, all pages. |
U.S. Appl. No. 14/542,252, filed Nov. 14, 2014, Final Office Action dated Jul. 14, 2017, all pages. |
Notice of Publication dated Oct. 15, 2015 in U.S. Appl. No. 14/752,453, 1 page. |
Non-Final Office action dated Jan. 15, 2016 in U.S. Appl. No. 14/752,453, 1 page. |
Notice of Allowance dated Jul. 25, 2016 in U.S. Appl. No. 14/752,453, 1 page. |
First Action Interview, Pre-interview communication dated Dec. 24, 2014 in U.S. Appl. No. 14/473,893, all pages. |
Notice of Publication dated Dec. 18, 2014 in U.S. Appl. No. 14/475,274, 1 page. |
Final Office action dated Nov. 28, 2017 in U.S. Appl. No. 14/475,274, 1 page. |
Nesler-C., “Adaptive Control of Thermal Process in Buildings,” iEEE, 1986, pp. 9-13. |
Final Office action dated Jul. 15, 2016 in U.S. Appl. No. 14/473,906, all pages. |
Advisory action dated Sep. 4, 2015 in U.S. Appl. No. 14/473,906, all pages. |
Notice of Allowance and Fee(s) Due dated Jul. 25, 2016 in U.S. Appl. No. 14/789,716, all pages. |
Notice of Publication dated Oct. 22, 2015 in U.S. Appl. No. 14/789,716, all pages. |
Notice of Allowance and Fee(s) Due dated Aug. 4, 2016 in U.S. Appl. No. 14/473,925, all pages. |
Non-Final Office action dated Jan. 12, 2017 in U.S. Appl. No. 14/542,252, all pages. |
Non-Final Office action dated Nov. 17, 2017 in U.S. Appl. No. 14/542,252, all pages. |
Non-Final Office action dated Jan. 12, 2017 in U.S. Appl. No. 14/528,995, all pages. |
Non-Final Office action dated Nov. 16, 2017 in U.S. Appl. No. 14/528,995, all pages. |
Notice of Allowance and Fee(s) Due dated Jul. 11, 2016 in U.S. Appl. No. 13/327,459, all pages. |
Non-Final Office action dated Dec. 5, 2017 in U.S. Appl. No. 15/351,188, all pages. |
Final Office action dated Sep. 19, 2018 in U.S. Appl. No. 15/351,202, all pages. |
Number | Date | Country | |
---|---|---|---|
20170059195 A1 | Mar 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14473906 | Aug 2014 | US |
Child | 15351217 | US | |
Parent | 13327459 | Dec 2011 | US |
Child | 14473906 | US | |
Parent | 12241588 | Sep 2008 | US |
Child | 13327459 | US |