Systems and methods for determining and utilizing customer energy profiles for load control for individual structures, devices, and aggregation of same

Information

  • Patent Grant
  • 10985556
  • Patent Number
    10,985,556
  • Date Filed
    Thursday, October 25, 2018
    6 years ago
  • Date Issued
    Tuesday, April 20, 2021
    3 years ago
Abstract
A system and method for creating and making use of customer profiles, including energy consumption patterns. Devices within a service point, using the active load director, may be subject to control events, often based on customer preferences. These control events cause the service point to use less power. Data associated with these control events, as well as related environment data, are used to create an energy consumption profile for each service point. This can be used by the utility to determine which service points are the best targets for energy consumption. In addition, an intelligent load rotation algorithm determines how to prevent the same service points from being picked first each time the utility wants to conserve power.
Description
BACKGROUND OF THE INVENTION
1. Field of the Invention

The present invention relates generally to electrical power load control systems and, more particularly, to creating customer profiles using energy consumption patterns.


2. Description of Related Art

Customer profiles are often used by systems for a variety of reasons. One reason is to promote customer loyalty. This involves keeping information about not only the customer, but about the customer's actions as well. This may include information about what the customer owns (i.e., which devices), how they are used, when they are used, etc. By mining this data, a company can more effectively select rewards for customers that give those customers an incentive for continuing to do business with the company. This is often described as customer relationship management (CRM).


Customer profile data is also useful for obtaining feedback about how a product is used. In software systems, this is often used to improve the customer/user experience or as an aid to testing. Deployed systems that have customer profiling communicate customer actions and other data back to the development organization. That data is analyzed to understand the customer's experience. Lessons learned from that analysis is used to make modifications to the deployed system, resulting in an improved system.


Customer profile data may also be used in marketing and sales. For instance, a retail business may collect a variety of information about a customer, including what customers look at on-line and inside “brick-and-mortar” stores. This data is mined to try to identify customer product preferences and shopping habits. Such data helps sales and marketing determine how to present products of probable interest to the customer, resulting in greater sales.


However, the collection of customer profile information by power utilities has been limited to customer account information. Because power utilities typically are unable to collect detailed data about what is happening inside a customer's home or business, including patterns of energy consumption by device, there has been little opportunity to create extensive customer profiles.


SUMMARY OF THE INVENTION

Embodiments described herein utilize the Active Load Management System (ALMS) that is fully described in commonly-owned published patent application US 2009/0062970. The ALMS captures energy usage data at each service point and stores that data in a central database. This data describes all of the energy consumed by devices owned by each customer, as well as additional information, such as customer preferences. Other embodiments of the ALMS focus on use of this information in the calculation of carbon credits or for the trading of unused energy.


In one embodiment, a system and method are provided for creating and making use of customer profiles, including energy consumption patterns. Devices within a service point, using the active load director, may be subject to control events, often based on customer preferences. These control events cause the service point to use less power. Data associated with these control events, as well as related environment data, are used to create an energy consumption profile for each service point. This can be used by the utility to determine which service points are the best targets for energy consumption. In addition, an additional algorithm determines how to prevent the same service points from being picked first each time the utility wants to conserve power.


In one embodiment, a method is provided for determining and using customer energy profiles to manage electrical load control events on a communications network between a server in communication with an electric utility and a client device at each of a plurality of service points. A customer profile is generated at the server for each of a plurality of customers including at least energy consumption information for a plurality of controllable energy consuming devices at an associated service point. The plurality of customer profiles is stored in a database at the server for use in load control events. The plurality of customer profiles are aggregated into a plurality of groups based on at least one predetermined criterion. A candidate list of service points for load control events based on the predetermined criterion is generated at the server. A load control event is sent to at least one selected service point in the candidate list of service points in response to an energy reduction request including a target energy savings received from the electric utility via the communications network. An energy savings for the plurality of controllable energy consuming devices resulting from the load control event at the selected service point is determined at the server. The server determines if the resulting energy savings is at least equal to the target energy savings. The load control event is sent to at least one selected additional service point in the candidate list of service points in order to reach the target energy savings, if the target energy savings has not been reached.


In one embodiment, a system is provided for determining and using customer energy profiles to manage electrical load control events on a communications network between a server in communication with an electric utility and a client device at each of a plurality of service points. The system includes a memory storing a database containing a plurality of customer profiles for load control events wherein each customer profile includes at least energy consumption information for a plurality of controllable energy consuming devices at an associated service point; and a server processor, cooperative with the memory, and configured for managing electrical load control events on the communications network to the plurality of service points by: generating a customer profile for each of a plurality of customers; aggregating the plurality of customer profiles into a plurality of groups based on at least one predetermined criterion; generating a candidate list of service points for load control events based on the predetermined criterion; sending a load control event to at least one selected service point in the candidate list of service points in response to an energy reduction request including a target energy savings received from the electric utility via the communications network; determining an energy savings for the plurality of controllable energy consuming devices resulting from the load control event at the selected service point; determining if the resulting energy savings is at least equal to the target energy savings; and sending the load control event to at least one selected additional service point in the candidate list of service points in order to reach the target energy savings.





BRIEF DESCRIPTION OF THE DRAWINGS

These and other advantages and aspects of the embodiments of the invention will become apparent and more readily appreciated from the following detailed description of the embodiments taken in conjunction with the accompanying drawings, as follows.



FIG. 1 is a block diagram of an exemplary IP-based, Active Load Management System (ALMS).



FIG. 2 is a block diagram illustrating an exemplary active load director (ALD) server included in the active load management system.



FIG. 3 is a block diagram illustrating an exemplary active load client (ALC) included in the active load management system.



FIG. 4 is a graph illustrating how drift is calculated.



FIG. 5 is a graph illustrating how service points are selected for optimal drift.



FIG. 6 is an operational flow diagram illustrating an exemplary Intelligent Load Rotation algorithm.





DETAILED DESCRIPTION

Before describing in detail exemplary embodiments, it should be observed that the embodiments described reside primarily in combinations of apparatus components and processing steps related to actively managing power loading on an individual subscriber or service point basis, determining the customer profile of individual devices aggregated to related service points, and optionally tracking power savings incurred by both individual subscribers and an electric utility. Accordingly, the apparatus components and method steps have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments disclosed so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.


The term “electric utility” refers to any entity that generates and distributes electrical power to its customers, that purchases power from a power-generating entity and distributes the purchased power to its customers, or that supplies electricity created by alternative energy sources, such as solar power, wind power or otherwise, to power generation or distribution entities through the Federal Energy Regulatory Commission (FERC) electrical grid or otherwise. The present invention provides for systems and methods relating to an electric grid operator or any market participant associated with an electric grid, including retail electrical providers.


Embodiments of the invention include a number of novel concepts, including a customer profile, drift, and intelligent load rotation as more fully described below. A customer profile captures patterns of power consumption for each customer. The drift concept includes a method for calculating drift, which is important in estimating power savings within thermal control devices. The intelligent load rotation concept includes a method for selecting customers for utility-initiated control events using intelligent load rotation.


The embodiments described utilize concepts disclosed in commonly-owned published patent application US 2009/0062970, entitled “System and Method for Active Power Load Management” which is incorporated by reference in its entirety herein. The following paragraphs describe the Active Management Load System (ALMS), Active Load Director (ALD), and Active Load Client (ALC) in sufficient detail to assist the reader in the understanding of the embodiments described herein. More detailed description of the ALMS, ALD, and ALC can be found in US 2009/0062970.


It should be noted that control events and other messaging used in embodiments of the invention include regulated load management messages. Regulated load management messages contain information used to apply control of the electric supply to individual appliances or equipment on customer premises. The load to be controlled includes native load and operating reserves including regulating, spinning, and non-spinning types.


Active Load Management System


FIG. 1 depicts an exemplary IP-based Active Load Management System (ALMS) 10 that may be utilized by a utility in the embodiments described herein. The exemplary ALMS 10 monitors and manages power distribution via an active load director (ALD) 100 connected between one or more utility control centers (UCCs) 200 and one or more Active Load Clients (ALCs) 300. The ALD 100 may communicate with the utility control center 200 and each active load client 300 either directly or through a network 80 using the Internet Protocol (IP) or any other connection-based protocols. For example, the ALD 100 may communicate using RF systems operating via one or more base stations 90 using one or more well-known wireless communication protocols. Alternatively, or additionally, the ALD 100 may communicate via a digital subscriber line (DSL) capable connection, cable television based IP capable connection, or any combination thereof. In the exemplary embodiment shown in FIG. 1, the ALD 100 communicates with one or more active load clients 300 using a combination of traditional IP-based communication (e.g., over a trunked line) to a base station 90 and a wireless channel implementing the WiMax protocol for the “last mile” from the base station 90 to the active load client 300.


Each ALC 300 is accessible through a specified address (e.g., IP address) and controls and monitors the state of individual smart breaker modules or intelligent appliances 60 installed in the business or residence 20 to which the ALC 300 is associated (e.g., connected or supporting). Each ALC 300 is associated with a single residential or commercial customer. In one embodiment, the ALC 300 communicates with a residential load center 400 that contains smart breaker modules, which are able to switch from an “ON” (active) state to an “OFF” (inactive) state, and vice versa, responsive to signaling from the ALC 300. Typically, each smart breaker controls a single appliance (e.g., a washer/dryer 30, a hot water heater 40, an HVAC unit 50, or a pool pump 70).


Additionally, the ALC 300 may control individual smart appliances directly (e.g., without communicating with the residential load center 400) via one or more of a variety of known communication protocols (e.g., IP, Broadband over Power Line (BPL) in various forms, including through specifications promulgated or being developed by the HOMEPLUG Powerline Alliance and the Institute of Electrical and Electronics Engineers (IEEE), Ethernet, Bluetooth, ZigBee, Wi-Fi, WiMax, etc.). Additionally or alternatively to WiMax, other communications protocols may be used, including but not limited to a “1 G” wireless protocol such as analog wireless transmission, first generation standards based (IEEE, ITU or other recognized world communications standard), a “2-G” standards based protocoal such as “EDGE or CDMA 2000 also known as 1×RTT”, a 3G based standard such as “High Speed Packet Access (HSPA) or Evolution for Data Only (EVDO), any accepted 4G standard such as “IEEE, ITU standards that include WiMax, Long Term Evolution “LTE” and its derivative standards, any Ethernet solution wireless or wired, or any proprietary wireless or power line carrier standards that communicate to a client device or any controllable device that sends and receives an IP based message.


Typically, a smart appliance 60 includes a power control module (not shown) having communication abilities. The power control module is installed in-line with the power supply to the appliance, between the actual appliance and the power source (e.g., the power control module is plugged into a power outlet at the home or business and the power cord for the appliance is plugged into the power control module). Thus, when the power control module receives a command to turn off the appliance 60, it disconnects the actual power supplying the appliance 60. Alternatively, a smart appliance 60 may include a power control module integrated directly into the appliance, which may receive commands and control the operation of the appliance directly (e.g., a smart thermostat may perform such functions as raising or lowering the set temperature, switching an HVAC unit on or off, or switching a fan on or off).


Also as shown in FIG. 1, a service point 20 may have its own power generation on-site, including solar panels, fuel cells, or wind turbines. This is indicated by the power generating device 96. The power generating device 96 connects to the Active Load Client 300. Power that is added by the power generating device 96 is added to the overall utility capacity. The utility provides credit to the service point owner based on the energy produced at the service point.


The service point 20 also contains the Customer Dashboard 98. This is a web-based interface used by the customer to specify preferences for the use of the Active Load Management System at the customer's service point. These preferences include control event preferences, bill management preferences, and others.


Active Load Director

Referring now to FIG. 2, the ALD 100 may serve as the primary interface to customers, as well as to service personnel. In the exemplary embodiment depicted in FIG. 2, the ALD 100 includes a utility control center (UCC) security interface 102, a UCC command processor 104, a master event manager 106, an ALC manager 108, an ALC security interface 110, an ALC interface 112, a web browser interface 114, a customer sign-up application 116, customer personal settings 138, a customer reports application 118, a power savings application 120, an ALC diagnostic manager 122, an ALD database 124, a service dispatch manager 126, a trouble ticket generator 128, a call center manager 130, a carbon savings application 132, a utility power and carbon database 134, a read meter application 136, and a security device manager 140.


In one embodiment, customers interact with the ALD 100 using the web browser interface 114, and subscribe to some or all of the services offered by the power load management system 10 via a customer sign-up application 116. In accordance with the customer sign-up application 116, the customer specifies customer personal settings 138 that contain information relating to the customer and the customer's residence or business, and defines the extent of service to which the customer wishes to subscribe. Customers may also use the web browser interface 114 to access and modify information pertaining to their existing accounts.


The ALD 100 also includes a UCC security interface 102 which provides security and encryption between the ALD 100 and a utility company's control center 200 to ensure that no third party is able to provide unauthorized directions to the ALD 100. A UCC command processor 104 receives and sends messages between the ALD 100 and the utility control center 200. Similarly, an ALC security interface 110 provides security and encryption between the ALD 100 and each ALC 300 on the system 10, ensuring that no third parties can send directions to, or receive information from, the ALC 300. The security techniques employed by the ALC security interface 110 and the UCC security interface 102 may include conventional symmetric key or asymmetric key algorithms, or proprietary encryption techniques.


The master event manager 106 maintains the overall status of the power load activities controlled by the power management system 10. The master event manager 106 maintains a separate state for each utility that is controlled and tracks the current power usage within each utility. The master event manager 106 also tracks the management condition of each utility (e.g., whether or not each utility is currently being managed). The master event manager 106 receives instructions in the form of transaction requests from the UCC command processor 104 and routes instructions to components necessary to complete the requested transaction, such as the ALC manager 108 and the power savings application 120.


The ALC manager 108 routes instructions between the ALD 100 and each ALC 300 within the system 10 through an ALC interface 112. For instance, the ALC manager 108 tracks the state of every ALC 300 serviced by specified utilities by communicating with the ALC 300 through an individual IP address. The ALC interface 112 translates instructions (e.g., transactions) received from the ALC manager 108 into the proper message structure understood by the targeted ALC 300 and then sends the message to the ALC 300. Likewise, when the ALC interface 112 receives messages from an ALC 300, it translates the message into a form understood by the ALC manager 108 and routes the translated message to the ALC manager 108.


The ALC manager 108 receives from each ALC 300 that it services, either periodically or responsive to polling messages sent by the ALC manager 108, messages containing the present power consumption and the status (e.g., “ON” or “OFF”) of each device controlled by the ALC 300. Alternatively, if individual device metering is not available, then the total power consumption and load management status for the entire ALC 300 may be reported. The information contained in each status message is stored in the ALD database 124 in a record associated with the specified ALC 300. The ALD database 124 contains all the information necessary to manage every customer account and power distribution. In one embodiment, the ALD database 124 contains customer contact information and associated utility companies for all customers having ALCs 300 installed at their residences or businesses, as well as a description of specific operating instructions for each managed device (e.g., IP-addressable smart breaker or appliance), device status, and device diagnostic history.


Another message that can be exchanged between an ALC 300 and the ALC manager 108 is a status response message. A status response message reports the type and status of each device controlled by the ALC 300 to the ALD 100. When a status response message is received from an ALC 300, the ALC manager 108 logs the information contained in the message in the ALD database 124.


In one embodiment, upon receiving instructions (e.g., a “Cut” instruction) from the master event manager 106 to reduce power consumption for a specified utility, the ALC manager 108 determines which ALCs 300 and/or individually controlled devices to switch to the “OFF” state based upon present power consumption data stored in the ALD database 124. The ALC manager 108 then sends a message to each selected ALC 300 containing instructions to turn off all or some of the devices under the ALC's control.


A read meter application 136 may be optionally invoked when the UCC command processor 104 receives a “Read Meters” or equivalent command from the utility control center 200. The read meter application 136 cycles through the ALD database 124 and sends a read meter message or command to each ALC 300, or to ALCs 300 specifically identified in the UCC's command, via the ALC manager 108. The information received by the ALC manager 108 from the ALC 300 is logged in the ALD database 124 for each customer. When all the ALC meter information has been received, the information is sent to the requesting utility control center 200 using a business to business (e.g., ebXML) or other desired protocol.


Active Load Client


FIG. 3 illustrates a block diagram of an exemplary active load client 300 in accordance with one embodiment of the present invention. The depicted active load client 300 includes a smart breaker module controller 306, a communications interface 308, a security interface 310, an IP-based communication converter 312, a device control manager 314, a smart breaker (B1-BN) counter manager 316, an IP router 320, a smart meter interface 322, a smart device interface 324, an IP device interface 330, and a power dispatch device interface 340. The active load client 300, in this embodiment, is a computer or processor-based system located on-site at a customer's residence or business. The primary function of the active load client 300 is to manage the power load levels of controllable, power consuming load devices located at the residence or business, which the active load client 300 oversees on behalf of the customer. In an exemplary embodiment, the active load client 300 may include dynamic host configuration protocol (DHCP) client functionality to enable the active load client 300 to dynamically request IP addresses for itself and/or one or more controllable devices 402-412, 60 managed thereby from a DHCP server on the host IP network facilitating communications between the active load client 300 and the ALD 100. The active load client 300 may further include router functionality and maintain a routing table of assigned IP addresses in a memory of the active load client 300 to facilitate delivery of messages from the active load client 300 to the controllable devices 402-412, 60. Finally, the power generation device 96 at the service point 20 sends data about power generated to the power dispatch device interface 340.


A communications interface 308 facilitates connectivity between the active load client 300 and the ALD server 100. Communication between the active load client 300 and the ALD server 100 may be based on any type of IP or other connection protocol including, but not limited to, the WiMax protocol. Thus, the communications interface 308 may be a wired or wireless modem, a wireless access point, or other appropriate interface.


A standard IP Layer-3 router 320 routes messages received by the communications interface 308 to both the active load client 300 and to any other locally connected device 440. The router 320 determines if a received message is directed to the active load client 300 and, if so, passes the message to a security interface 310 to be decrypted. The security interface 310 provides protection for the contents of the messages exchanged between the ALD server 100 and the active load client 300. The message content is encrypted and decrypted by the security interface 310 using, for example, a symmetric encryption key composed of a combination of the IP address and GPS data for the active load client 300 or any other combination of known information. If the message is not directed to the active load client 300, then it is passed to the IP device interface 330 for delivery to one or more locally connected devices 440. For example, the IP router 320 may be programmed to route power load management system messages as well as conventional Internet messages. In such a case, the active load client 300 may function as a gateway for Internet service supplied to the residence or business instead of using separate Internet gateways or routers.


An IP based communication converter 312 opens incoming messages from the ALD server 100 and directs them to the appropriate function within the active load client 300. The converter 312 also receives messages from various active load client 300 functions (e.g., a device control manager 314, a status response generator 304, and a report trigger application 318), packages the messages in the form expected by the ALD server 100, and then passes them on to the security interface 310 for encryption.


The device control manager 314 processes power management commands for various controllable devices logically connected to the active load client 300. The devices can be either smart breakers 402-412 or other IP based devices 60, 460, such as smart appliances with individual control modules (not shown). The device control manager 314 also processes “Query Request” or equivalent commands or messages from the ALD server 100 by querying a status response generator 304 which maintains the type and status of each device controlled by the active load client 300, and providing the status of each device to the ALD server 100.


The status response generator 304 receives status messages from the ALD server 100 and, responsive thereto, polls each controllable device 402-412, 60, 460 under the active load client's control to determine whether the controllable device 402-412, 60, 460 is active and in good operational order. Each controllable device 402-412, 60, 460 responds to the polls with operational information (e.g., activity status and/or error reports) in a status response message. The active load client 300 stores the status responses in a memory associated with the status response generator 304 for reference in connection with power reduction events.


The smart device interface 324 facilitates IP or other address-based communications to individual devices 60 (e.g., smart appliance power control modules) that are attached to the active load client 300. The connectivity can be through one of several different types of networks including, but not limited to, BPL, ZigBee, Wi-Fi, Bluetooth, or direct Ethernet communications. Thus, the smart device interface 324 is a modem adapted for use in or on the network connecting the smart devices 60 to the active load client 300.


The smart breaker module controller 306 formats, sends, and receives messages to and from the smart breaker module 400. In one embodiment, the communications is preferably through a BPL connection. In such embodiment, the smart breaker module controller 306 includes a BPL modem and operations software. The smart breaker module 400 contains individual smart breakers 402-412, wherein each smart breaker 402-412 includes an applicable modem (e.g., a BPL modem when BPL is the networking technology employed) and is preferably in-line with power supplied to a single appliance or other device. The B1-BN counter manager 316 determines and stores real time power usage for each installed smart breaker 402-412. For example, the counter manager 316 tracks or counts the amount of power used by each smart breaker 402-412 and stores the counted amounts of power in a memory of the active load client 300 associated with the counter manager 316.


The smart meter interface 322 manages either smart meters 460 that communicate using BPL or a current sensor 452 connected to a traditional power meter 450. When the active load client 300 receives a “Read Meters” command or message from the ALD server 100 and a smart meter 460 is attached to the active load client 300, a “Read Meters” command is sent to the meter 460 via the smart meter interface 322 (e.g., a BPL modem). The smart meter interface 322 receives a reply to the “Read Meters” message from the smart meter 460, formats this information along with identification information for the active load client 300, and provides the formatted message to the IP based communication converter 312 for transmission to the ALD server 100.


Customer Profiles

The embodiments disclosed make use of the “customer profiles” concept. The ALMS enables data to be gathered to generate a profile of each customer, including information about controllable energy consuming devices, and the related individual structures or service points. Customer profiles reside within the Active Load Director Database 124 in the Active Load Director 100. Included in this customer profile is the customer's pattern of energy consumption. The customer profile includes, but is not limited to, the following: (1) customer name; (2) customer address; (3) geodetic location; (4) meter ID; (5) customer programs (possibly including program history); (6) device information, including device type and manufacturer/brand; (7) customer energy consumption patterns; and (8) connection and disconnection profile. The connection/disconnection profile can include service priority (i.e., elderly, police, etc.) and disconnection instructions.


The customer profile is created by using data gathered from within the ALMS. Data gathered or calculated includes, but is not be limited to, the following: (1) set points; (2) energy and average energy used in a given time period; (3) energy and average energy saved in a given time period; (4) drift time per unit temperature and average drift time; and (5) power time per unit temperature and average power time per unit temperature.


In other embodiments, additional data called “variability factors” may be captured by the ALMS as part of the customer profile, including, but not limited to, the following: (1) outside temperature, (2) sunlight, (3) humidity, (4) wind speed and direction, (5) elevation above sea level, (6) orientation of the service point structure, (7) duty duration and percentage, (8) set point difference, (9) current and historic room temperature, (10) size of structure, (11) number of floors, (12) type of construction (brick, wood, siding etc.) (13) color of structure, (14) type of roofing material and color, (15) construction surface of structure (built on turf, clay, cement, asphalt etc.), (16) land use (urban, suburban, rural), (17) latitude/longitude, (18) relative position to jet stream, (19) quality of power to devices, (20) number of people living in and/or using structure and (21) other environmental factors.


Additional factors may also be deemed necessary for determining unique energy consumption patterns and generating performance curves and data matrices for usage in load control events and other purposes detailed in this and related patent applications.


By way of example, based upon the reduction in consumed power, the systems and methods of the present invention provide for generating at the control center a power supply value (PSV) corresponding to the reduction in consumed power by the power consuming device(s). Importantly, the PSV is an actual value that includes measurement and verification of the reduction in consumed power; such measurement and verification methods may be determined by the appropriate governing body or authority for the electric power grid(s). Power Supply Value (PSV) is calculated at the meter or submeter or at building control system or at any device or controller that measures power within the standard as supplied by the regulatory body(ies) that govern the regulation of the grid. PSV variations may depend on operating tolerances, operating standard for accuracy of the measurement. The PSV enables transformation of curtailment or reduction in power at the device level by any system that sends or receives an IP message to be related to or equated to supply as presented to the governing entity that accepts these values and award supply equivalence, for example of a power generating entity or an entity allowed to control power consuming devices as permitted by the governing body of the electric power grid, e.g., FERC, NERC, etc.


PSV may be provided in units of electrical power flow, monetary equivalent, and combinations thereof. Thus, the PSV provides an actual value that is confirmed by measurement and/or verification, thereby providing for a curtailment value as a requirement for providing supply to the power grid, wherein the supply to the power electric power grid is provided for grid stability, voltage stability, reliability, and combinations thereof, and is further provided as responsive to an energy management system or equivalent for providing grid stability, reliability, frequency as determined by governing authority for the electric power grid and/or grid operator(s).


As part of the Active Load Directory (ALD), the methods described herein consolidate this information creating a historic energy consumption pattern reflecting the amount of energy used by each service point to maintain its normal mode of operation. This energy consumption pattern is part of a customer's profile.


Energy consumption patterns are subject to analysis that may be used for a variety of different types of activities. For example, based on the energy consumption patterns created from this data, the ALD will derive performance curves and/or data matrices for each service point to which the Active Load Management System is attached and determine the amount of energy reduction that can be realized from each service point. The ALD will create a list of service points through which energy consumption can be reduced via demand side management, interruptible load, or spinning/regulation reserves. This information can be manipulated by the ALD processes to create a prioritized, rotational order of control, called “intelligent load rotation” which is described in detail below. This rotational shifting of the burden of the interruptible load has the practical effect of reducing and flattening the utility load curve while allowing the serving utility to effectively group its customers within the ALD or its own databases by energy efficiency.


The practical application of this data is that in load control events, a utility can determine the most efficient service points to dispatch energy from, or more importantly derive the most inefficient service points (e.g., homes, small businesses, communities, structures, or devices) within the utility's operating territory. Based on this information, highly targeted conservation programs could have an immediate impact to improve energy efficiency. From a marketing perspective, this is invaluable information because it contains the comfort preference of a service point compared against the capabilities of the service point's energy consuming devices, or the lack of efficiency of those devices. From a national security point of view, the profiles could be used to determine habits of monitored end customers in a similar fashion to how Communications Assistance for Law Enforcement Act (CALEA) is used by law enforcement for wire-tapping. Utilities may use energy consumption patterns to categorize or group customers for service, control event, marketing, sales, or other purposes. Other uses of energy consumption patterns are possible that determine or predict customer behavior.


Generally, the embodiments described encompass a closed loop system and method for creating a customer profile, calculating and deriving patterns of energy drift, and making use of those patterns when implemented through the machinery of a system comprised of load measurement devices combined with the physical communications link and when these inputs are manipulated through a computer, processor, memory, routers and other necessary machines as those who are skilled in the art would expect to be utilized.


Drift

The embodiments described also make use of the concept of “drift.” The data gathered for the customer profile is used to empirically derive the decay rate or drift, temperature slope, or a dynamic equation (f{x}) whereby the service point (or device) will have a uniquely derived “fingerprint” or energy usage pattern.


Drift occurs when a climate-controlled device begins to deviate from a set point. This may occur both normally and during control events. Customers define the upper and lower boundaries of comfort in customer preferences, with the set point in the middle of those boundaries. During normal operation, a climate controlled device will attempt to stay near the device's set point. However, all devices have a duty cycle that specifies when the device is in operation because many devices are not continuously in operation. For a climate-controlled device, the duty cycle ends when the inside temperature reaches, or is within a given tolerance of, the set point. This allows the device to “drift” (upward or downward) toward a comfort boundary temperature. Once the boundary temperature is reached, the duty cycle begins again until the inside temperature reaches, or is within a given tolerance of, the set point which ends the duty cycle.


Therefore, drift is the time it takes for a climate-controlled device to move from the set point to the upper or lower comfort boundary. Drift is calculated and recorded for each service point and for each device associated with the service point. The inverse of drift is “power time” which is the time it takes for the device to move from the comfort boundary to the set point.


Drift may also occur during a control event. A control event is an action that reduces or terminates power consumption of a device. During a control event, a climate-controlled device will drift toward maximum or minimum control event boundaries (upper or lower) until it reaches that boundary which is normally outside the comfort boundary. Once it reaches the control event boundary, the ALMS returns power to the device to enable it to reach the set point again.


As an example, an HVAC system may have a set point of 72 degrees and a minimum and maximum temperature of 68 degrees and 76 degrees, respectively. On a cold day, a control event would cause the HVAC system to begin to lose power and move toward the minimum temperature. Once the structure reaches the minimum temperature, the control event would end, and power would be restored to the HVAC system, thus causing the temperature to rise toward the preferred temperature. A similar but opposite effect would take place on a warm day.


In some embodiments, drift, as well as other measurements available from the active load director data base 124, are used to create an energy consumption pattern for each service point. Additional measurements may include vacancy times, sleep times, times in which control events are permitted, as well as variability factors referred to previously.


A device that resides within an energy-efficient structure will have a tendency to cool or heat more slowly, thus exhibiting a lower rate of drift. These devices may be subject to control events for longer periods of time, commensurate with the rate of drift, because it takes them longer to drift to a comfort boundary.


In another embodiment, the active load director server 100 identifies service points that have an optimum drift for power savings. The power savings application 120 calculates drift for each service point and saves that information in the active load director data base 124.


Intelligent Load Rotation

The embodiments disclosed also make use of the “intelligent load rotation” concept. Intelligent load rotation uses machine intelligence to ensure that the same service points are not always selected for control events, but distributes control events over a service area in some equitable way.


There are a variety of ways in which intelligent load rotation may be implemented. In one embodiment of intelligent load rotation, service points are simply selected in a sequential list until the end is reached, after which selection starts at the top of the list again. This is a fairly straightforward approach that may be implemented by any one skilled in the art.



FIG. 6 illustrates an operational flow diagram of the basic intelligent load rotation algorithm 1800. All other embodiments of intelligent load rotation are based on this embodiment. In general, the algorithm goes through each service point within a group of service points, and sends control events to each of those service points until enough energy savings have been obtained.


In its most basic form, the algorithm first identifies a group selection criteria as indicated in logic block 1802. This may be as simple as all service points or may be more complex, such as selecting service points within a specified drift or within a specified geographic area. The group selection criteria may include, but is not limited to, any of the following: (1) random selection of service points; (2) drift; (3) grouping of logical geodetic points by a utility; (4) efficiency rating of appliances; (5) ALD customer preferences; (6) capacity of devices; (7) proximity to transmission lines; (8) pricing signals (both dynamic and static); and (9) service priority, based upon an emergency situation (i.e. fire, police, hospital, elderly, etc.).


The algorithm then identifies an individual service point selection criterion as indicated in logic block 1804. This is the criterion for selecting individual service points within a group. In its simplest embodiment, this criterion involves sequential selection of service points within the group. Other criteria may include random selection, selection based on number of previous control events, or other criteria.


Next, the algorithm creates a candidate list of service points based on the group selection criteria as indicated in logic block 1806. From this list, the algorithm selects a service point based on the individual service point selection criteria as indicated in logic block 1810. The ALMS then sends a control event to the selected service point as indicated in logic block 1814, and calculates the energy savings of that control event based on drift calculation as indicated in block 1816. The algorithm then determines if more energy savings are needed to reach the savings target as indicated in decision block 1820. If not, then the ALMS records where the algorithm ended in the candidate list as indicated in block 1824 and exits. If more energy savings are needed, then the ALMS determines if any more service points are in the candidate list as indicated in decision block 1830. If there are no more service points in the candidate list, then the algorithm returns to the beginning of the candidate list again in logic block 1840. Otherwise, if there are more service points in the candidate list, the algorithm simply returns to logic block 1810.


In an alternate embodiment, decision block 1820 may be modified to determine if more service points are to be selected from this group.


There are many other embodiments of intelligent load rotation. Many embodiments are based on the group selection criteria. Service points may be grouped by geography or some other common characteristic of service points. For example, groups might include “light consumers” (because they consume little energy), “daytime consumers” (because they work at night), “swimmers” (for those who have a pool and use it), or other categories. These categories are useful to the utility for quickly referring to customers with specific energy demographics. The utility may then select a number of service points in each group for control events to spread control events among various groups.


In another embodiment, optimum drift can be used as the group selection criteria. Because those service points will use the least energy, the utility may want to select those service points that are the most energy efficient.


In another embodiment, a group of service points is selected that have had the fewest control events in the past. This ensures that service points with the most control events in the past will be bypassed in favor of those who have received fewer control events.


In another embodiment, with reference to FIGS. 4-5, drift is used as a means of intelligent load rotation. As data is collected by the ALMS, it is possible to calculate the total drift of a device over time, as shown in FIG. 4. The calculation for one service point represents one vector on the graph. Each vector represents the drift for a single service point. To identify the service points with the optimal drift, the ALD 100 determines the median drift and all service points having a drift that is within one standard deviation away from that median. That represents the shaded area in the graph depicted in FIG. 5. If sufficient service points cannot be found that are within one standard deviation, then the second standard deviation can be selected.


In another embodiment, energy consumption patterns in customer profiles are used to identify service points that are the best targets for excess power sharing. This would occur when renewable energy such as solar or wind is added to the grid, resulting in power that cannot be compensated for by the grid. This could occur, for example, on very windy days. When this happens, utilities are faced with the problem of what to do with the excess energy. Instead of cutting power to service points in order to affect power savings, a utility could add energy to service points in order to effect power dissipation. The service points selected by the utility may be different (or even the inverse) of those selected for power savings. The devices at these service points would be turned on if they were off or set points for climate-controlled devices would be adjusted to heat or cool more than normal. Spread out over many control points, this can provide the energy dissipation needed.


In a further embodiment, energy consumption patterns within customer profiles could be used to identify opportunities for up selling, down selling, or cross selling. These opportunities may be determined by the power utility or by its partners. Data from customer profiles may be used to provide insights on inefficient devices, defective devices, or devices that require updating to meet current standards. Customer profile data may also be used to identify related sales opportunities. For example, if energy consumption patterns suggest that the customer may be very interested in personal energy conservation, then sales efforts could be directed toward that individual concerning products related to that lifestyle. This information can be used by the utility or its partners to provide incentives to customers to buy newer, updated devices, or obtain maintenance for existing devices. The customer is given the option to opt out of having his customer profile used for sales and marketing efforts, or for regulating energy conservation. The customer profile makes use of open standards (such as the CPExchange standard) that specify a privacy model with the customer profile. The use of consumption patterns in this manner is governed by national, state, or local privacy laws and regulations.


A further embodiment of using customer profiles to identify sales opportunities involves the use of device information to create incentives for customers to replace inefficient devices. By identifying the known characteristics and/or behavior of devices within a service point, the invention identifies those customers who may benefit from replacement of those devices. The invention estimates a payback period for replacement. This information is used by the ALMS operator to create redemptions, discounts, and campaigns to persuade customers to replace their devices.


It should be noted that many terms and acronyms are used in this description that are well-defined in the telecommunications and computer networking industries and are well understood by persons skilled in these arts. Complete descriptions of these terms and acronyms, whether defining a telecommunications standard or protocol, can be found in readily available telecommunications standards and literature and are not described in any detail herein.


As used in the foregoing description, the term “ZigBee” refers to any wireless communication protocol adopted by the Institute of Electrical and Electronics Engineers (IEEE) according to standard 802.15.4 or any successor standard(s), and the term “Bluetooth” refers to any short-range communication protocol implementing IEEE standard 802.15.1 or any successor standard(s). The term “High Speed Packet Data Access (HSPA)” refers to any communication protocol adopted by the International Telecommunication Union (ITU) or another mobile telecommunications standards body referring to the evolution of the Global System for Mobile Communications (GSM) standard beyond its third generation Universal Mobile Telecommunications System (UMTS) protocols. The term “Long Term Evolution (LTE)” refers to any communication protocol adopted by the ITU or another mobile telecommunications standards body referring to the evolution of GSM-based networks to voice, video and data standards anticipated to be replacement protocols for HSPA. The term “Code Division Multiple Access (CDMA) Evolution Date-Optimized (EVDO) Revision A (CDMA EVDO Rev. A)” refers to the communication protocol adopted by the ITU under standard number TIA-856 Rev. A.


It will be appreciated that embodiments or components of the systems described herein may be comprised of one or more conventional processors and unique stored program instructions that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions for managing power load distribution, and tracking and controlling individual subscriber power consumption and savings in one or more power load management systems. The non-processor circuits may include, but are not limited to, radio receivers, radio transmitters, antennas, modems, signal drivers, clock circuits, power source circuits, relays, meters, smart breakers, current sensors, and customer input devices. As such, these functions may be interpreted as steps of a method to distribute information and control signals between devices in a power load management system. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of functions are implemented as custom logic. Of course, a combination of the two approaches could be used. Thus, methods and means for these functions have been described herein. Further, it is expected that one of ordinary skill in the art, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein, will be readily capable of generating such software instructions, programs and integrated circuits (ICs), and appropriately arranging and functionally integrating such non-processor circuits, without undue experimentation.


In the foregoing specification, the invention has been described with reference to specific embodiments. However, one of ordinary skill in the art will appreciate that various modifications and changes may be made without departing from the scope of the present invention as set forth in the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present invention.


The corresponding structures, materials, acts, and equivalents of all means plus function elements in any claims below are intended to include any structure, material, or acts for performing the function in combination with other claim elements as specifically claimed.


In addition, it is possible to use some of the features of the embodiments disclosed without the corresponding use of the other features. Accordingly, the foregoing description of the exemplary embodiments is provided for the purpose of illustrating the principles of the invention, and not in limitation thereof, since the scope of the present invention is defined solely by the appended claims.

Claims
  • 1. A system for active load management in an electric power grid based on customer energy profiles, comprising: a server processor constructed and configured for network communication with a multiplicity of service points in the electric power grid;wherein each of the multiplicity of service points comprises a multiplicity of controllable energy consuming devices, wherein the multiplicity of controllable energy consuming devices comprises at least one temperature control device;wherein the server processor is operable to: create a customer energy profile comprising an energy consumption pattern for each of the multiplicity of service points,send a first load control event to at least one service point in response to an energy reduction request including a target energy savings,generate a Power Supply Value (PSV) for each of the multiplicity of controllable energy consuming devices at each service point based on the customer energy profile for each service point, wherein the PSV is a determined monetary value or an electrical power flow value based on an equivalent measurement and verification of a reduction in consumed power by each of the multiplicity of controllable energy consuming devices, wherein the equivalent measurement and verification of the reduction in consumed power is a measurement and verification of curtailment as supply, in units of electrical power flow, accepted by governing entities for awarding customers supply equivalence, anddetermine an energy savings at the at least one service point based on the PSV for each of the multiplicity of controllable energy consuming devices at the at least one service point.
  • 2. The system of claim 1, wherein the customer energy profile further comprises a customer name, a customer address, a geodetic location, a meter identifier, customer programs, device information, and connection and disconnection profiles.
  • 3. The system of claim 1, wherein the customer energy profile is created based on data collected from a corresponding service point, comprising set points, energy and average energy used in a given time period, energy and average energy saved in a given time period, drift time per unit temperature and average drift time, and power time per unit temperature and average power time per unit temperature.
  • 4. The system of claim 3, wherein the data collected from the corresponding service point further comprises variability factors including outside temperature, sunlight, humidity, windspeed and direction, elevation above sea level, orientation of the corresponding service point structure, duty duration and percentage, set point difference, current and historic room temperature, number of floors, types of construction, color of construction, types of roofing material and color, construction surface of structure, land use, latitude and longitude, relative position to jet stream, quality of power to devices, number of people living in and using the corresponding service point structure, and/or other environmental factors.
  • 5. The system of claim 1, wherein the server processor is operable to predict customer behaviors based on the customer profile for each of the multiplicity of service points.
  • 6. The system of claim 1, wherein the energy consumption pattern is based on energy consumption data, drifts, vacancy times, sleep times, and times during which control events are permitted.
  • 7. The system of claim 1, wherein a multiplicity of PSVs is aggregated into at least one aggregate PSV.
  • 8. The system of claim 1, further comprising a database in network communication with the server processor operable for storing a multiplicity of customer energy profiles for the multiplicity of service points.
  • 9. The system of claim 1, wherein the server processor is further operable to receive the energy reduction request from an electric grid operator or any market participant associated with the electric power grid.
  • 10. The system of claim 1, wherein the server processor is further operable to generate a candidate list of service points for the first load control event based on a predetermined criterion and select the at least one service point from the candidate list.
  • 11. The system of claim 10, wherein the predetermined criterion is based on a random selection, a drift factor, a logical geodetic point, an efficiency rating for each controllable temperature control device at an associated service point, a customer preference, a proximity to a transmission line, a pricing signal, and/or a priority for an emergency situation.
  • 12. The system of claim 1, wherein the server processor is further operable to determine the energy savings at the at least one service point is at least equal to the target energy savings.
  • 13. The system of claim 1, wherein the server processor is further operable to send a second load control event to at least one additional service point in order to reach the target energy savings.
  • 14. A system for active load management in an electric power grid based on customer energy profiles, comprising: a server processor constructed and configured for network communication with a multiplicity of service points in the electric power grid, wherein each of the multiplicity of service points comprises a multiplicity of controllable energy consuming devices;wherein the server processor is operable to: create a multiplicity of customer energy profiles for the multiplicity of service points,send a load control event to at least one service point,generate a Power Supply Value (PSV) for each of the multiplicity of controllable energy consuming devices at each service point based on each customer energy profile for each service point, wherein the PSV is based on an equivalent measurement and verification of a reduction in consumed power by each of the multiplicity of controllable energy consuming devices, wherein the equivalent measurement and verification of the reduction in consumed power is a measurement and verification of curtailment as supply, in units of electrical power flow, accepted by governing entities for awarding customers supply equivalence, anddetermine an energy savings at the at least one service point based on the PSV for each of the multiplicity of controllable energy consuming devices at the at least one service point.
  • 15. The system of claim 14, wherein each of the multiplicity of customer profiles comprises an energy consumption pattern, wherein the server processor is further operable to identify service points for excess power sharing based on the energy consumption pattern in each of the multiplicity of customer profiles.
  • 16. The system of claim 14, wherein the PSV is in units of electric power flow and/or monetary equivalent.
  • 17. The system of claim 14, wherein the load control event is in response to an energy reduction request from an electric grid operator.
  • 18. A system for active load management in an electric power grid based on customer energy profiles, comprising: a server processor constructed and configured for network communication with a database and a multiplicity of service points in the electric power grid,wherein each of the multiplicity of service points comprises a multiplicity of controllable energy consuming devices;wherein the server processor is operable to: create a multiplicity of customer energy profiles for the multiplicity of service points,send a load control event to at least one service point in response to an energy reduction request including a target energy savings,generate a Power Supply Value (PSV) for each of the multiplicity of controllable energy consuming devices at each service point based on each customer energy profile for each service point, wherein the PSV is a determined monetary value or an electrical power flow value based on an equivalent measurement and verification of a reduction in consumed power by each of the multiplicity of controllable energy consuming devices, wherein the equivalent measurement and verification of the reduction in consumed power is a measurement and verification of curtailment as a supply, in units of electrical power flow, accepted by governing entities for awarding customers supply equivalence,calculate an energy savings at the at least one service point based on the PSV for each of the multiplicity of controllable energy consuming devices at the at least one service point, anddetermine the energy savings is at least equal to the target energy savings;wherein the database is operable to store the multiplicity of customer energy profiles and energy data resulting from the load control event.
  • 19. The system of claim 18, wherein the server processor is operable to identify inefficient devices and defective devices based on each customer profile for each service point.
  • 20. The system of claim 18, wherein inefficient service points are operable to be identified based on the multiplicity of customer profiles.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to and claims priority from the following applications. This application is a continuation of U.S. application Ser. No. 14/790,579 filed Jul. 2, 2015, which is a continuation of U.S. application Ser. No. 13/464,665 filed May 4, 2012 and issued as U.S. Pat. No. 9,177,323, which is a continuation-in-part of U.S. patent application Ser. No. 13/019,867 filed Feb. 2, 2011 and issued as U.S. Pat. No. 8,996,183. U.S. patent application Ser. No. 13/019,867 is a continuation-in-part of U.S. patent application Ser. No. 12/715,124 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,010,812, which is a division of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 13/019,867 is also a continuation-in-part of U.S. patent application Ser. No. 12/715,195 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,032,233, which is a division of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 13/019,867 is further a continuation-in-part of U.S. patent application Ser. No. 12/001,819 filed on Dec. 13, 2007, which is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 13/019,867 is further a continuation-in-part of U.S. patent application Ser. No. 12/775,979 filed on May 7, 2010 now U.S. Pat. No. 8,396,606. U.S. patent application Ser. No. 12/775,979 is a continuation-in-part of U.S. patent application Ser. No. 12/001,819 filed Dec. 12, 2007, which is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/775,979 is also a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/775,979 also claims priority under 35 U.S.C. § 119(e) upon U.S. Provisional Application No. 61/215,725 filed on May 8, 2009. U.S. patent application Ser. No. 13/019,867 is further a continuation-in-part of U.S. patent application Ser. No. 12/783,415 filed on May 19, 2010 now abandoned. U.S. patent application Ser. No. 12/783,415 is a continuation-in-part of U.S. patent application Ser. No. 12/715,124 filed on Mar. 1, 2010 and issued as U.S. Pat. No. 8,010,812, which is a division of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/783,415 is also a continuation-in-part of U.S. patent application Ser. No. 12/001,819 filed on Dec. 13, 2007, which is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 filed on Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/783,415 also claims priority under 35 U.S.C. § 119(e) upon U.S. Provisional Application No. 61/216,712 filed on May 20, 2009. U.S. patent application Ser. No. 13/019,867 is a continuation-in-part of U.S. patent application Ser. No. 12/896,307 filed on Oct. 1, 2010 and issued as U.S. Pat. No. 8,527,107. U.S. patent application Ser. No. 12/896,307 is a continuation-in-part of U.S. patent application Ser. No. 12/715,124 filed Mar. 1, 2010 and issued as U.S. Pat. No. 8,010,812, which is a division of U.S. patent application Ser. No. 11/895,909 filed Aug. 28, 2007 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/896,307 is also a continuation-in-part of U.S. patent application Ser. No. 12/715,195 filed Mar. 1, 2010 and issued as U.S. Pat. No. 8,032,233, which is also a division of U.S. patent application Ser. No. 11/895,909 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/896,307 is further a continuation-in-part of U.S. patent application Ser. No. 12/702,640 filed Feb. 9, 2010 and issued as U.S. Pat. No. 8,131,403. U.S. patent application Ser. No. 12/702,640 is a continuation-in-part of U.S. patent application Ser. No. 11/895,909 and issued as U.S. Pat. No. 7,715,951. U.S. patent application Ser. No. 12/702,640 also claims priority upon U.S. Provisional Application No. 61/150,978 filed Feb. 9, 2009 and U.S. Provisional Application No. 61/176,752 filed May 8, 2009. U.S. patent application Ser. No. 12/896,307 further claims priority under 35 U.S.C. § 119(e) upon U.S. Provisional Application No. 61/279,072 filed on Oct. 15, 2009. All of the above-mentioned documents are incorporated herein by reference in their entirety.

US Referenced Citations (427)
Number Name Date Kind
3906242 Stevenson Sep 1975 A
4023043 Stevenson May 1977 A
4589075 Buennagel May 1986 A
4799059 Grindahl et al. Jan 1989 A
4819180 Hedman et al. Apr 1989 A
4819229 Pritty et al. Apr 1989 A
5237507 Chasek Aug 1993 A
5361982 Liebl et al. Nov 1994 A
5388101 Dinkins Feb 1995 A
5462225 Massara et al. Oct 1995 A
5481546 Dinkins Jan 1996 A
5502339 Hartig Mar 1996 A
5544036 Brown et al. Aug 1996 A
5570002 Castleman Oct 1996 A
5592491 Dinkins Jan 1997 A
5640153 Hildebrand et al. Jun 1997 A
5644173 Elliason et al. Jul 1997 A
5675503 Moe et al. Oct 1997 A
5696695 Ehlers et al. Dec 1997 A
5721936 Kikinis et al. Feb 1998 A
5926776 Glorioso et al. Jul 1999 A
5973481 Thompson et al. Oct 1999 A
6018690 Saito et al. Jan 2000 A
6037758 Perez Mar 2000 A
6078785 Bush Jun 2000 A
6102487 Oevreboe Aug 2000 A
6107693 Mongia et al. Aug 2000 A
6115676 Rector et al. Sep 2000 A
6154859 Norizuki et al. Nov 2000 A
6216956 Ehlers et al. Apr 2001 B1
6233327 Petite May 2001 B1
6254009 Proffitt et al. Jul 2001 B1
6304552 Chapman et al. Oct 2001 B1
6366217 Cunningham et al. Apr 2002 B1
6374101 Gelbien Apr 2002 B1
6437692 Petite et al. Aug 2002 B1
6519509 Nierlich et al. Feb 2003 B1
6529839 Uggerud et al. Mar 2003 B1
6535797 Bowles et al. Mar 2003 B1
6577962 Afshari Jun 2003 B1
6583521 Lagod et al. Jun 2003 B1
6601033 Sowinski Jul 2003 B1
6602627 Liu et al. Aug 2003 B2
6621179 Howard Sep 2003 B1
6622097 Hunter Sep 2003 B2
6622925 Carner et al. Sep 2003 B2
6633823 Bartone et al. Oct 2003 B2
6671586 Davis et al. Dec 2003 B2
6681154 Nierlich et al. Jan 2004 B2
6687574 Pietrowicz et al. Feb 2004 B2
6718761 Merswolke et al. Apr 2004 B2
6732055 Bagepalli et al. May 2004 B2
6747368 Jarrett Jun 2004 B2
6778882 Spool et al. Aug 2004 B2
6784807 Petite et al. Aug 2004 B2
6832135 Ying Dec 2004 B2
6834811 Huberman et al. Dec 2004 B1
6836737 Petite et al. Dec 2004 B2
6862498 Davis et al. Mar 2005 B2
6865450 Masticola et al. Mar 2005 B2
6868293 Schurr et al. Mar 2005 B1
6879059 Sleva Apr 2005 B2
6891838 Petite et al. May 2005 B1
6904336 Raines et al. Jun 2005 B2
6906617 Meulen Jun 2005 B1
6909942 Andarawis et al. Jun 2005 B2
6914533 Petite Jul 2005 B2
6914893 Petite Jul 2005 B2
6934316 Cornwall et al. Aug 2005 B2
6944555 Blackett et al. Sep 2005 B2
6961641 Forth et al. Nov 2005 B1
6990593 Nakagawa Jan 2006 B2
7003640 Mayo et al. Feb 2006 B2
7019667 Petite et al. Mar 2006 B2
7035719 Howard et al. Apr 2006 B2
7039532 Hunter May 2006 B2
7053767 Petite et al. May 2006 B2
7088014 Niedich et al. Aug 2006 B2
7103511 Petite Sep 2006 B2
7123994 Welk et al. Oct 2006 B2
7133750 Raines et al. Nov 2006 B2
7136725 Paciorek et al. Nov 2006 B1
7141321 McArthur et al. Nov 2006 B2
7142949 Brewster et al. Nov 2006 B2
7177728 Gardner Feb 2007 B2
7181320 Whiffen et al. Feb 2007 B2
7184861 Petite Feb 2007 B2
7200134 Proctor et al. Apr 2007 B2
7206670 Pimputkar et al. Apr 2007 B2
7209804 Curt et al. Apr 2007 B2
7209840 Petite et al. Apr 2007 B2
7233843 Budhraja et al. Jun 2007 B2
7263073 Petite et al. Aug 2007 B2
7263450 Hunter Aug 2007 B2
7274975 Miller Sep 2007 B2
7289887 Rodgers Oct 2007 B2
7295128 Petite Nov 2007 B2
7305282 Chen Dec 2007 B2
7313465 O'Donnell Dec 2007 B1
7343341 Sander et al. Mar 2008 B2
7345998 Cregg et al. Mar 2008 B2
7346463 Petite et al. Mar 2008 B2
7366164 Habib et al. Apr 2008 B1
7397907 Petite Jul 2008 B2
7406364 Rissanen et al. Jul 2008 B2
7412304 Uenou Aug 2008 B2
7424527 Petite Sep 2008 B2
7440871 McConnell et al. Oct 2008 B2
7451019 Rodgers Nov 2008 B2
7468661 Petite et al. Dec 2008 B2
7480501 Petite Jan 2009 B2
7486681 Weber Feb 2009 B2
7492617 Petter et al. Feb 2009 B2
7528503 Rognli et al. May 2009 B2
7536240 McIntyre et al. May 2009 B2
7541941 Bogolea et al. Jun 2009 B2
7565227 Richard et al. Jul 2009 B2
7650425 Davis et al. Jan 2010 B2
7697492 Petite Apr 2010 B2
7711796 Gutt et al. May 2010 B2
7715951 Forbes et al. May 2010 B2
7738999 Petite Jun 2010 B2
7739378 Petite Jun 2010 B2
7747165 Emery et al. Jun 2010 B2
7940901 Paraskevakos et al. May 2011 B2
8010812 Forbes et al. Aug 2011 B2
8032233 Forbes et al. Oct 2011 B2
8032461 Winter et al. Oct 2011 B2
8046110 Mayor et al. Oct 2011 B2
8068938 Fujita Nov 2011 B2
8131403 Forbes et al. Mar 2012 B2
8145361 Forbes et al. Mar 2012 B2
8260468 Ippolito et al. Sep 2012 B2
8260470 Forbes et al. Sep 2012 B2
8295989 Rettger et al. Oct 2012 B2
8307225 Forbes et al. Nov 2012 B2
8315717 Forbes et al. Nov 2012 B2
8315743 Sackman et al. Nov 2012 B2
8359124 Zhou et al. Jan 2013 B2
8359215 Robbins et al. Jan 2013 B1
8364609 Ozog Jan 2013 B2
8396606 Forbes et al. Mar 2013 B2
8407252 Bennett et al. Mar 2013 B2
8417569 Gross Apr 2013 B2
8428752 Bennett et al. Apr 2013 B2
8442917 Burke May 2013 B1
8457802 Steven et al. Jun 2013 B1
8463449 Sanders Jun 2013 B2
8473111 Shankar et al. Jun 2013 B1
8527107 Forbes et al. Sep 2013 B2
8571930 Galperin Oct 2013 B1
8583520 Forbes Nov 2013 B1
8588991 Forbes Nov 2013 B1
8600556 Nesler et al. Dec 2013 B2
8684266 Bennett et al. Apr 2014 B2
8761952 Forbes Jun 2014 B2
8805552 Forbes Aug 2014 B2
8806239 Forbes Aug 2014 B2
8890505 Forbes Nov 2014 B2
8996183 Forbes Mar 2015 B2
9177323 Forbes Nov 2015 B2
20010030468 Anderson et al. Oct 2001 A1
20010038343 Meyer et al. Nov 2001 A1
20020019758 Scarpelli Feb 2002 A1
20020019802 Malme et al. Feb 2002 A1
20020035496 Fukushima et al. Mar 2002 A1
20020036430 Welches et al. Mar 2002 A1
20020109607 Cumeralto et al. Aug 2002 A1
20020138176 Davis et al. Sep 2002 A1
20020143693 Soestbergen et al. Oct 2002 A1
20020161648 Mason et al. Oct 2002 A1
20020198629 Ellis Dec 2002 A1
20030009401 Ellis Jan 2003 A1
20030009705 Thelander et al. Jan 2003 A1
20030036820 Yellepeddy et al. Feb 2003 A1
20030083980 Satake May 2003 A1
20030144864 Mazzarella Jul 2003 A1
20030149937 McElfresh et al. Aug 2003 A1
20030158632 Nierlich et al. Aug 2003 A1
20030167178 Jarman et al. Sep 2003 A1
20030176952 Collins Sep 2003 A1
20030225483 Santinato et al. Dec 2003 A1
20030229572 Raines et al. Dec 2003 A1
20030233201 Horst et al. Dec 2003 A1
20040006439 Hunter Jan 2004 A1
20040024483 Holcombe Feb 2004 A1
20040044571 Bronnimann et al. Mar 2004 A1
20040088083 Davis et al. May 2004 A1
20040095237 Chen et al. May 2004 A1
20040107025 Ransom et al. Jun 2004 A1
20040117330 Ehlers et al. Jun 2004 A1
20040128266 Yellepeddy et al. Jul 2004 A1
20040138834 Blackett et al. Jul 2004 A1
20040153170 Santacatterina et al. Aug 2004 A1
20040158478 Zimmerman Aug 2004 A1
20040158541 Notarianni et al. Aug 2004 A1
20040162793 Scott et al. Aug 2004 A1
20040193329 Ransom et al. Sep 2004 A1
20040225514 Greenshields et al. Nov 2004 A1
20040230533 Benco Nov 2004 A1
20050021397 Cui et al. Jan 2005 A1
20050033481 Budhraja et al. Feb 2005 A1
20050055432 Rodgers Mar 2005 A1
20050065742 Rodgers Mar 2005 A1
20050080772 Bem Apr 2005 A1
20050096856 Lubkeman et al. May 2005 A1
20050096857 Hunter May 2005 A1
20050096979 Koningstein May 2005 A1
20050097204 Horowitz et al. May 2005 A1
20050125243 Villalobos Jun 2005 A1
20050127680 Lof et al. Jun 2005 A1
20050138432 Ransom et al. Jun 2005 A1
20050192711 Raines et al. Sep 2005 A1
20050192713 Weik et al. Sep 2005 A1
20050197742 Scott et al. Sep 2005 A1
20050216302 Raji et al. Sep 2005 A1
20050216580 Raji et al. Sep 2005 A1
20050234600 Boucher et al. Oct 2005 A1
20050240314 Martinez Oct 2005 A1
20050240315 Booth et al. Oct 2005 A1
20050246190 Sander et al. Nov 2005 A1
20050267642 Whiffen et al. Dec 2005 A1
20050276222 Kumar et al. Dec 2005 A1
20050288954 McCarthy et al. Dec 2005 A1
20060020544 Kaveski Jan 2006 A1
20060020596 Liu et al. Jan 2006 A1
20060022841 Hoiness et al. Feb 2006 A1
20060025891 Budike Feb 2006 A1
20060031934 Kriegel Feb 2006 A1
20060064205 Ying Mar 2006 A1
20060069616 Bau Mar 2006 A1
20060106635 Ulrich et al. May 2006 A1
20060142900 Rothman et al. Jun 2006 A1
20060142961 Johnson et al. Jun 2006 A1
20060161310 Lal Jul 2006 A1
20060161450 Carey et al. Jul 2006 A1
20060168191 Ives Jul 2006 A1
20060190354 Meisel et al. Aug 2006 A1
20060195334 Reeb et al. Aug 2006 A1
20060212350 Ellis et al. Sep 2006 A1
20060224615 Korn et al. Oct 2006 A1
20060241244 Soeda et al. Oct 2006 A1
20060241314 Sullivan et al. Oct 2006 A1
20060271244 Cumming et al. Nov 2006 A1
20060271314 Hayes Nov 2006 A1
20060276938 Miller Dec 2006 A1
20060282328 Gerace et al. Dec 2006 A1
20070021874 Rognli et al. Jan 2007 A1
20070038563 Ryzerski Feb 2007 A1
20070058453 Shaffer et al. Mar 2007 A1
20070058629 Luft Mar 2007 A1
20070070895 Narvaez Mar 2007 A1
20070085702 Walters et al. Apr 2007 A1
20070091900 Asthana et al. Apr 2007 A1
20070094043 Bannai et al. Apr 2007 A1
20070100503 Balan et al. May 2007 A1
20070100961 Moore May 2007 A1
20070150353 Krassner et al. Jun 2007 A1
20070156621 Wright et al. Jul 2007 A1
20070156887 Wright et al. Jul 2007 A1
20070174114 Bigby et al. Jul 2007 A1
20070192333 Ali Aug 2007 A1
20070203722 Richards et al. Aug 2007 A1
20070204176 Shaffer et al. Aug 2007 A1
20070213878 Chen Sep 2007 A1
20070214118 Schoen et al. Sep 2007 A1
20070214132 Grubb et al. Sep 2007 A1
20070255457 Whitcomb et al. Nov 2007 A1
20070260540 Chau et al. Nov 2007 A1
20070282495 Kempton et al. Dec 2007 A1
20070286210 Gutt et al. Dec 2007 A1
20070291644 Roberts et al. Dec 2007 A1
20070299562 Kates Dec 2007 A1
20080010212 Moore et al. Jan 2008 A1
20080015976 Sandor et al. Jan 2008 A1
20080040223 Bridges et al. Feb 2008 A1
20080091625 Kremen Apr 2008 A1
20080104026 Koran May 2008 A1
20080109387 Deaver et al. May 2008 A1
20080130673 Cregg et al. Jun 2008 A1
20080147465 Raines et al. Jun 2008 A1
20080154801 Fein et al. Jun 2008 A1
20080165714 Dettinger et al. Jul 2008 A1
20080172312 Synesiou et al. Jul 2008 A1
20080177423 Brickfield et al. Jul 2008 A1
20080177678 Martini et al. Jul 2008 A1
20080186202 Vaswani et al. Aug 2008 A1
20080195462 Magdon-Ismail et al. Aug 2008 A1
20080224892 Bogolea et al. Sep 2008 A1
20080231114 Tolnar et al. Sep 2008 A1
20080238710 Tolnar et al. Oct 2008 A1
20080249832 Richardson et al. Oct 2008 A1
20080255899 McConnell et al. Oct 2008 A1
20080263025 Koran Oct 2008 A1
20080270223 Collins et al. Oct 2008 A1
20080272934 Wang et al. Nov 2008 A1
20080281473 Pitt Nov 2008 A1
20080306824 Parkinson Dec 2008 A1
20080306830 Lasa et al. Dec 2008 A1
20080313632 Kumar et al. Dec 2008 A1
20080319893 Mashinsky et al. Dec 2008 A1
20090012996 Gupta et al. Jan 2009 A1
20090018884 McConnell et al. Jan 2009 A1
20090024718 Anagnostopoulos et al. Jan 2009 A1
20090038343 Gibson Feb 2009 A1
20090043519 Bridges et al. Feb 2009 A1
20090043520 Pollack et al. Feb 2009 A1
20090045804 Durling et al. Feb 2009 A1
20090055031 Slota et al. Feb 2009 A1
20090055032 Rodgers Feb 2009 A1
20090062970 Forbes et al. Mar 2009 A1
20090063228 Forbes Mar 2009 A1
20090088907 Lewis et al. Apr 2009 A1
20090112701 Turpin Apr 2009 A1
20090112758 Herzig Apr 2009 A1
20090124241 Krishnaswamy et al. May 2009 A1
20090125462 Krishnaswamy et al. May 2009 A1
20090135836 Veillette May 2009 A1
20090138362 Schroedl et al. May 2009 A1
20090157529 Ehlers et al. Jun 2009 A1
20090187344 Brancaccio et al. Jul 2009 A1
20090187499 Mulder et al. Jul 2009 A1
20090198384 Ahn Aug 2009 A1
20090228335 Niyogi et al. Sep 2009 A1
20090240381 Lane Sep 2009 A1
20090240677 Parekh et al. Sep 2009 A1
20090281673 Taft Nov 2009 A1
20090281674 Taft Nov 2009 A1
20090313034 Ferro et al. Dec 2009 A1
20090313103 Ambrosio et al. Dec 2009 A1
20090319415 Stoilov et al. Dec 2009 A1
20100076835 Silverman Mar 2010 A1
20100082464 Keefe Apr 2010 A1
20100094981 Cordray et al. Apr 2010 A1
20100106575 Bixby Apr 2010 A1
20100106641 Chassin et al. Apr 2010 A1
20100138452 Henkin et al. Jun 2010 A1
20100163634 Klein et al. Jul 2010 A1
20100169175 Koran Jul 2010 A1
20100179862 Chassin et al. Jul 2010 A1
20100191862 Forbes et al. Jul 2010 A1
20100217452 McCord et al. Aug 2010 A1
20100217549 Galvin et al. Aug 2010 A1
20100217550 Crabtree et al. Aug 2010 A1
20100217642 Crubtree et al. Aug 2010 A1
20100218108 Crabtree et al. Aug 2010 A1
20100235008 Forbes et al. Sep 2010 A1
20100274407 Creed Oct 2010 A1
20100293045 Burns et al. Nov 2010 A1
20100306033 Oved et al. Dec 2010 A1
20100324748 Voysey Dec 2010 A1
20100328849 Ewing et al. Dec 2010 A1
20100332373 Crabtree et al. Dec 2010 A1
20110007824 Bridges et al. Jan 2011 A1
20110015802 Imes Jan 2011 A1
20110025556 Bridges et al. Feb 2011 A1
20110029655 Forbes et al. Feb 2011 A1
20110055036 Helfan Mar 2011 A1
20110060474 Schmiegel et al. Mar 2011 A1
20110080044 Schmiegel Apr 2011 A1
20110106729 Billingsley et al. May 2011 A1
20110115302 Slota et al. May 2011 A1
20110130982 Haag et al. Jun 2011 A1
20110133655 Recker et al. Jun 2011 A1
20110145061 Spurr et al. Jun 2011 A1
20110147360 Hammerstrom Jun 2011 A1
20110161250 Koeppel et al. Jun 2011 A1
20110172841 Forbes Jul 2011 A1
20110178610 Gamble et al. Jul 2011 A1
20110185303 Katagi et al. Jul 2011 A1
20110196546 Muller et al. Aug 2011 A1
20110196547 Park et al. Aug 2011 A1
20110204717 Shaffer Aug 2011 A1
20110204719 Sackman et al. Aug 2011 A1
20110208366 Taft Aug 2011 A1
20110208367 Sackman et al. Aug 2011 A1
20110231028 Ozog Sep 2011 A1
20110235656 Pigeon Sep 2011 A1
20110251730 Pitt Oct 2011 A1
20110257809 Forbes et al. Oct 2011 A1
20110258022 Forbes et al. Oct 2011 A1
20110267202 Efthymiou et al. Nov 2011 A1
20110270452 Lu et al. Nov 2011 A1
20110270682 Valin Nov 2011 A1
20120004872 Oh et al. Jan 2012 A1
20120029897 Cherian et al. Feb 2012 A1
20120059532 Reifenhaeuser et al. Mar 2012 A1
20120078427 Jang et al. Mar 2012 A1
20120089263 Park et al. Apr 2012 A1
20120095841 Luckerman et al. Apr 2012 A1
20120101652 Shin et al. Apr 2012 A1
20120131100 Van Olst et al. May 2012 A1
20120146799 Bell et al. Jun 2012 A1
20120153888 Jung Jun 2012 A1
20120154171 Hurri et al. Jun 2012 A1
20120196482 Stokoe Aug 2012 A1
20120205977 Shin et al. Aug 2012 A1
20120221162 Forbes Aug 2012 A1
20120223840 Guymon et al. Sep 2012 A1
20120226384 Forbes Sep 2012 A1
20120232816 Oh et al. Sep 2012 A1
20120239218 Forbes Sep 2012 A1
20120239219 Forbes Sep 2012 A1
20120245753 Forbes Sep 2012 A1
20120259760 Sgouridis et al. Oct 2012 A1
20120296799 Playfair et al. Nov 2012 A1
20120310800 Xia et al. Dec 2012 A1
20120316691 Boardman et al. Dec 2012 A1
20120316697 Boardman et al. Dec 2012 A1
20130006435 Berrios et al. Jan 2013 A1
20130031201 Kagan et al. Jan 2013 A1
20130035802 Khaitan et al. Feb 2013 A1
20130036311 Akyol et al. Feb 2013 A1
20130038468 Wang et al. Feb 2013 A1
20130079939 Thomas et al. Mar 2013 A1
20130079943 Darden Mar 2013 A1
20130110297 Reichmuth et al. May 2013 A1
20130123998 King et al. May 2013 A1
20130144768 Rohrbaugh Jun 2013 A1
20130173360 Thatcher Jul 2013 A1
20130191260 Michael Jul 2013 A1
20140018969 Forbes Jan 2014 A1
20140025486 Bigby et al. Jan 2014 A1
20140039699 Forbes, Jr. Feb 2014 A1
20140039701 Forbes Feb 2014 A1
20140039703 Forbes Feb 2014 A1
20150303691 Forbes Oct 2015 A1
Foreign Referenced Citations (15)
Number Date Country
1729223 Dec 2006 EP
2000078748 Mar 2000 JP
2001306839 Nov 2001 JP
2004180412 Jun 2004 JP
2004248174 Sep 2004 JP
2006060911 Mar 2006 JP
2007132553 May 2007 JP
20050045272 May 2005 KR
20060036171 Apr 2006 KR
20070008321 Jan 2007 KR
100701298 Mar 2007 KR
20070098172 Oct 2007 KR
20080112692 Dec 2008 KR
2007136456 Nov 2007 WO
2008125696 Oct 2008 WO
Non-Patent Literature Citations (19)
Entry
B.J. Kirby, Spinning Reserve from Responsive Loads, Oak Ridge National Laboratory, United States Dept. of Energy, Mar. 2003 (54 pages).
Byers J. Risk Management and Monetizing the Commodity Storage Option. Natural Gas & Electricity [serial online]. Jul. 2005; 21 (12)1-8. Available from: Business Source Complete, Ipswich, MA.
C.W. Gellings and W.M. Smith, Integrating Demand-Side Management into Utility Planning, Proceedings of the IEEE, vol. 77, Issue: 6, Jun. 1989, pp. 908-918 (Abstract only).
Eric Hirst and Brendan Kirby, Opportunities for Demand Participation in New England Contingency-Reserve Markets, New England Demand Response Initiative, Feb. 2003 (15 pages).
Eric Hirst and Richard Cowart, Demand Side Resources and Reliability, New England Demand Response Initiative, Mar. 20, 2002 (32 pages).
Galvin Electricity Institute: Frequently Asked Questions, printed Apr. 23, 2014, same page available through archive.org unchanged Mar. 1, 2008.
GE Digital Energy Residential Electrical Metering Brochure. Sep. 12, 2012. https://web.archive.org/web/20120912144353/http://www.gedigitalenergry.com/products/brochures/1210-Family.pdf.
Illinois General Assembly: Public Act 094-0977, Effective Date: Jun. 30, 2006.
Kamat R., Oren S. Two-Settlement Systems for Electricity Markets under Network Uncertainty and Market Power Journal of Regulatory Economics [serial online]. Jan. 2004; 25(1):5-37.
Kathleen Spees and Lester B. Lave, Demand Response and Electricity Market Efficiency, The Electricity Journal, vol. 20, Issue 3, Apr. 2007 (online Mar. 27, 2007), pp. 69-85 (Abstract only).
L.T. Anstine, R.E. Burke, J.E. Casey, R. Holgate, R.S. John, and H.G. Stewart, Application of Probability Methods to the Determination of Spinning Reserve Requirements for the Pennsylvania-New Jersey-Maryland Interconnection; IEEE Transactions on Power Apparatus and Systems, vol. 82, Issue 68, Oct. 1963, pp. 726-735 (Abstract only).
Lobsenz G. Maryland Regulators Reject BG&E Smart Grid Proposal. Energy Daily [serial online]. Jun. 23, 2010; (118): 3. Available from: Business Source Complete, Ipswich, MA.
M. Rashidi-Nejad, Y.H. Song, and M.H. Javidi-Dasht-Bayaz, Operating Reserve Provision in Deregulated Power Markets, IEEE Power Engineering Society Winter Meeting, vol. 2, 2002, pp. 1305-1310 (Abstract only).
Michael Ahlheim and Friedrich Schneider; “Allowing for Household Preferences in Emission Trading, A Contribution to the Climate Policy Debate”; Environmental and Resource Economics, vol. 21, pp. 317-342; Kluwer Academic Publishers; The Netherlands; 2002.
Olivier Rousse; “Environmental and economic benefits resulting from citizens' participation in CO.sub.2 emissions trading: An efficient alternative solution to the voluntary compensation of CO.sub.2 emissions”, Energy Policy 36 (2008), pp. 388-397; Oct. 29, 2007 (online).
Pablo A. Ruiz and Peter W. Sauer, Valuation of Reserve Services, IEEE Proceedings of the 41 .sup.st Hawaii International Conference on System Sciences, 2008 (9 pages).
Paul Darbee, Insteon Compared, SmartLabs, Inc., Jan. 2, 2006, 69 pages.
Paul Darbee, Insteon the Details, Smarthome, Inc., Aug. 11, 2005, 68 pages.
Zhu Jinxiang, G. Jordan, and S. Ihara, The Market for Spinning Reserve and Its Impacts on Energy Prices, IEEE Power Engineering Society Winter Meeting, vol. 2, 2000, pp. 1202-1207 (Abstract Only).
Related Publications (1)
Number Date Country
20190067940 A1 Feb 2019 US
Provisional Applications (3)
Number Date Country
61279072 Oct 2009 US
61215725 May 2009 US
61216712 May 2009 US
Divisions (4)
Number Date Country
Parent 11895909 Aug 2007 US
Child 12715124 US
Parent 13019867 Feb 2011 US
Child 12715124 US
Parent 11895909 Aug 2007 US
Child 12715195 US
Parent 13019867 Feb 2011 US
Child 12715195 US
Continuations (2)
Number Date Country
Parent 14790579 Jul 2015 US
Child 16170706 US
Parent 13464665 May 2012 US
Child 14790579 US
Continuation in Parts (18)
Number Date Country
Parent 13019867 Feb 2011 US
Child 13464665 US
Parent 12896307 Oct 2010 US
Child 13019867 US
Parent 12715124 Mar 2010 US
Child 12896307 US
Parent 12715124 Mar 2010 US
Child 13019867 US
Parent 12715195 Mar 2010 US
Child 12715124 US
Parent 12702640 Feb 2010 US
Child 12715195 US
Parent 13019867 Feb 2011 US
Child 12715195 US
Parent 12715195 Mar 2010 US
Child 13019867 US
Parent 12001819 Dec 2007 US
Child 13019867 US
Parent 12775979 May 2010 US
Child 12001819 US
Parent 11895909 Aug 2007 US
Child 12775979 US
Parent 12001819 Dec 2007 US
Child 11895909 US
Parent 13019867 Feb 2011 US
Child 11895909 US
Parent 12783415 May 2010 US
Child 13019867 US
Parent 12715124 Mar 2010 US
Child 12783415 US
Parent 12001819 Dec 2007 US
Child 12715124 US
Parent 12702640 Feb 2010 US
Child 12715124 US
Parent 11895909 Aug 2007 US
Child 12702640 US