The present disclosure generally relates to the field of electrical utility usage mitigation and optimization using energy storage systems and related fields.
Electrical energy and power generation and distribution has been a mainstay for residential and commercial energy needs all over the world and for many years. Various forms of electrical energy generation have been devised, including coal fired power plants, nuclear power plants, hydroelectric plants, wind harness plants, and others. All of these forms of electrical energy generation are well known to those of skill in the art of power generation and details of their operation need not be set forth herein.
As power generation has advanced, power usage has increased. Due to advances in technology and cultural factors, the demand for electrical energy steadily rises. Energy production facilities and distributors such as electrical utility providers therefore meet the rising demand for electricity with greater production capabilities. However, utility providers do not need to provide the same magnitude of electrical power to consumers at all times. Consumer needs greatly fluctuate based on the time of day, time of year, and other related factors. Therefore, utility providers have implemented programs wherein they charge more per watt of energy consumed during predetermined periods of time when overall consumer demand is expected to be higher than usual. These programs are referred to herein as “time-of-use” energy billing programs. These programs help the providers offset their costs of operating peaking power plants that are primarily brought online during those high-demand periods of time, and are not typically directly associated with the activity of any single consumer.
Utility providers have also implemented programs to charge consumers for consuming energy at high power levels. Under these programs, the consumer is billed a “demand charge” that is based on and directly related to the highest magnitude of power drawn from the grid at some point during a billing period. Therefore, these programs are referred to herein as “demand charge” energy billing programs. The magnitude of the power level used to determine the demand charge may be determined in a number of ways, and the most common methods of calculation are based on measuring the instantaneous power draw of the site at any point in time over the billing period (or within a subdivision of the billing period) or an average power draw of the site over a period of time within the billing period. For example, under the average power draw scheme, the utility provider measures the average consumption of the consumer's site over a plurality of time periods (e.g., consecutive 15-minute spans of time) within the billing period (e.g., one month), and the highest average power during one of those time periods is the basis for the demand charge for that billing period. Consumers are constantly in need of ways to limit utility costs and to improve the efficiency of their consumption of utility power.
One aspect of the present disclosure relates to a method of managing electrical utility consumption based on tracking and responding to energy consumption signals. In one embodiment, the method may comprise receiving a first energy tracking notification from a utility meter at a customer site at a first time. This utility meter may be connected to a utility distribution grid. The method may further comprise receiving a second energy tracking notification from the utility meter at a second time, wherein the second energy tracking notification may be sent after a quantity of energy is consumed by the customer site from the utility distribution grid. Next, the method may comprise determining a representative power level of the customer site drawn from the utility distribution grid between the first time and the second time based on the quantity of energy, determining an energy surplus or deficit based on a difference between the representative power level and a target power level, and operating a load curtailment system to transfer energy to or from the utility distribution grid. The energy transferred may offset the energy surplus or deficit within a subdivision of a billing period.
In some embodiments, the representative power level is an average power level drawn by the customer site between the first time and the second time. The first and second energy tracking notifications may be received within the subdivision of the billing period. That subdivision may have a duration of about 15 minutes or less. The load curtailment system may also comprise an energy storage device.
In some configurations, the method may further comprise tracking a duration of transferring energy to or from the utility distribution grid using the load curtailment system and stopping the energy transfer once the energy deficit or surplus should have been eliminated via the energy transfer. Operating the load curtailment system may comprise transferring energy at a single power level until the energy transferred offsets the energy surplus or deficit. The first energy tracking notification may be received prior to a start time of the subdivision of the billing period. The first energy tracking notification may also be received after a start time of the subdivision of the billing period. The load curtailment system may be charged or discharged over a fraction of a remaining time between the second time and an end of the subdivision of the billing period, and in some cases the quantity of energy may be no greater than an amount of energy consumed at the target power level over about one tenth of a total duration of the subdivision of the billing period.
Another aspect of the disclosure relates to a non-transitory computer-readable medium storing code for controlling a load curtailment system. The code may comprise instructions executable by a processor to: receive a first energy tracking notification from a utility meter at a customer site at a first time, with the utility meter being connected to a utility distribution grid, receive a second energy tracking notification from the utility meter at a second time, with the second energy tracking notification being sent after a quantity of energy is consumed by the customer site from the utility distribution grid, determine a representative power level of the customer site drawn from the utility distribution grid between the first time and the second time based on the quantity of energy, determine an energy surplus or deficit based on a difference between the representative power level and a target power level, and operate a load curtailment system to transfer energy to or from the utility distribution grid. The energy transferred may offset the energy surplus or deficit within a subdivision of a billing period.
Yet another aspect of the disclosure relates to an apparatus for controlling a load curtailment system. The apparatus may comprise a processor, memory in electronic communication with the processor, and instructions stored in the memory, wherein instructions may be executable by the processor to receive a first energy tracking notification from a utility meter at a customer site at a first time, with the utility meter being connected to a utility distribution grid, receive a second energy tracking notification from the utility meter at a second time, with the second energy tracking notification being sent after a quantity of energy is consumed by the customer site from the utility distribution grid, determine a representative power level of the customer site drawn from the utility distribution grid between the first time and the second time based on the quantity of energy, determine an energy surplus or deficit based on a difference between the representative power level and a target power level, and operate a load curtailment system to transfer energy to or from the utility distribution grid. The energy transferred may offset the energy surplus or deficit within a subdivision of a billing period.
The above summary of the present invention is not intended to describe each embodiment or every implementation of the present invention. The Figures and the detailed description that follow more particularly exemplify one or more preferred embodiments.
The accompanying drawings and figures illustrate a number of exemplary embodiments and are part of the specification. Together with the present description, these drawings demonstrate and explain various principles of this disclosure. A further understanding of the nature and advantages of the present invention may be realized by reference to the following drawings. In the appended figures, similar components or features may have the same reference label.
While the embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the instant disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.
Consumers that are billed high demand charges often take measures to mitigate those charges. Some popular mitigation techniques include load shedding, supplemental electricity generation, and energy storage load control. When using energy storage load control, the consumer may discharge an energy storage system to provide power to consumer load during periods of time in which the power drawn from the utility grid would be high and may recharge the energy storage system at times when the power draw from the grid is lower than usual so that the energy storage has enough charge to offset loads when a new peak power draw occurs.
Conventional energy storage load control systems are prone to costly failures. They are reactive, meaning the system monitors the instantaneous power draw of the site from the grid and, if the power draw exceeds a certain “setpoint” threshold of power draw, the system reactively discharges energy storage to prevent the power draw from increasing the maximum recorded power draw that would be used to calculate the demand charge. These kinds of reactive systems are unreliable for reducing demand charges because inverters used to convert the energy stored by the energy storage device into power available to loads at the site cannot immediately react to commands. Therefore, the power level of consumption at the site may exceed the setpoint before the energy storage system is able to react appropriately. Also, for many load profiles, the power draw changes quickly, and the energy storage load control system is not well equipped to react when the power draw frequently changes above and below the setpoint of the site because it leads to excessive battery cycling between charge and discharge. The high amount of cycling leads to wear and tear on batteries and other components. Also, the slow reaction time of the system may lead to back-feeding energy into the meter and other wasteful usage of stored energy. Accordingly, there is a need for improvements and innovation in the field of electrical utility usage mitigation and optimization using energy storage systems.
In some cases, utility providers assess demand charges based on the average power draw over portions of a billing period rather than assessing demand charges based on the maximum instantaneous or short-term power draw at any given moment within a billing period. Generally, the total time in the billing period is divided into a plurality of segments or subdivisions, and the utility provider determines the average power draw of the consumer in each individual subdivision. At the end of the billing period, the customer may then be charged a demand charge based on the average value that is the highest for that billing period. For example, the utility provider may divide the billing period into 15-minute increments and may determine average power levels of the consumer's site for each of the 15-minute increments. The highest average power level (corresponding to one of the 15-minute increments) may then be used to determine the demand charge assessed for that billing period.
The present disclosure generally relates to methods, apparatuses, and systems used to manage electrical utility consumption, including, for example, electrical utility consumption that results in grid power level-based demand charges from an electrical utility provider. Therefore, some systems and methods of the present disclosure are configured to track and control the average power level of the plurality of subdivisions of the billing period in order to manage the demand charge assessed by the provider. Because the average load needs to be managed rather than the instantaneous load, the load control system does not always need to immediately charge or discharge to react to peaks that occur in the power draw of the site from the grid. Also, the average load may be advantageous to track and control because it is generally more predictable than the instantaneous power draw of the consumer.
Some consumers use utility load controllers that track the average power draw in order to manage demand charges. These controllers operate in a hybrid mode wherein battery cycling and switching is reduced by using a combination of instantaneous peak shaving and management of an “energy deficit” tracked for each subdivision of a billing period. These hybrid systems may receive measurements of the instantaneous power draw of the site from the grid and may instantaneously respond to the power level by charging or discharging the energy storage to keep the power level from exceeding the setpoint of the billing period. They may also use the measurements of the instantaneous power draw and use predictive algorithms to extrapolate near term power consumption and average consumption, thereby making energy storage charging and discharging decisions less erratic and unpredictable by tracking and managing the average consumption as well.
The utility consumer may also have access to information from the utility provider (e.g., from the utility meter), wherein the utility meter produces a signal for the customer each time a predetermined quantity of energy is consumed by the customer's site from the utility grid. Using these energy consumption signals as guideposts, an energy storage consumption management system may track the amount of grid-based energy consumed by the site over time, and the power draw over that time can be back-calculated from the energy value.
Because the average power draw is used by the utility provider to determine the demand charge, consumption management systems such as those described in the present disclosure may feed energy to the grid that offsets any energy “surplus” amount that would make the average power draw (over a specific subdivision of the billing period) to be greater than the setpoint at the end of the subdivision and thereby cause a new or increased demand charge. Similarly, if there is an energy “deficit” amount that would make the average power draw be less than the setpoint at the end of the subdivision, the system may draw energy from the grid to offset the deficit, such as in situations when energy storage needs to be recharged. The energy fed into the grid to offset the deficit or surplus may be fed before or after a peak in power draw occurs. Thus, the reaction time of the energy storage consumption management system is not as important as in conventional systems. The present systems and methods may therefore be referred to as energy-based load management systems because they are solely reliant on managing consumption based on energy consumption signals rather than power-based or power- and energy-based “hybrid” load management systems.
Typically, the utility provider determines the quantity of energy consumed (i.e., the “energy quantum” or “quantum value”) between the signals (i.e., “ticks”) from the utility meter that indicate that energy consumption has occurred. Therefore, accurate predictions of future energy consumption based on the timing of those ticks is highly dependent upon the size of the quantum value relative to the power draw of the site. During instances of very high power draw, ticks from the meter come relatively quickly and regularly because a relatively large amount of energy is being consumed over time. When power draw drops to a relatively low level, the ticks either cease or come more slowly. A sudden drop from high to low demand may be interpreted by a load controller as a loss of connectivity to the meter, resulting in a continuation of peak shaving activity (e.g., discharging energy storage) when it is unnecessary. This may be referred to herein as “back-feeding” the meter. Back-feeding may deplete the energy storage and cause unnecessary discharging costs to alleviate non-existent high demand.
Apparatuses, systems, and methods of the present disclosure logic may in some cases address these issues by using a completely energy-based calculation to control energy storage charging and discharging while managing the power level used to calculate demand charges. The present systems and methods may recalculate power commands when an energy measurement tick or signal is updated and received, and may not rely on extrapolated power consumption values, thereby eliminating operational edge cases where predicted consumption may lead the controller to spiral out of control. Commands to charge or discharge the energy storage may be configured to eliminate an energy surplus or deficit observed based on the consumption curtailment setpoint and an energy measurement at the beginning of a subdivision (e.g., a 15-minute span) of the billing period. The system may also track how long it has been operating at the latest power command, and may be configured to stop the system once the deficit or surplus of energy should have been eliminated, thereby eliminating runaway charging or discharging events. This may also avoid scenarios where the system response is so large that it causes the site to back-feed or consume energy at a severely depressed rate, which may essentially stop the energy based meter updates and cause old control commands to follow extrapolated power values (which can be very high) and to provoke a huge discharge response that can detrimentally completely discharge the energy storage.
In some embodiments, the utility meter may provide instant power and energy signals or reports. Embodiments of the systems and methods of this disclosure may be used with these instant signals by having the system controller interpret these instant reports as if they were tick-based reports with a very small quantum value.
The present description provides examples, and is not limiting of the scope, applicability, or configuration set forth in the claims. Thus, it will be understood that changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure, and various embodiments may omit, substitute, or add other procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to certain embodiments may be combined in other embodiments.
Additional detail and embodiments will be provided with reference to the figures.
The site 100 may have at least one consumption management system 112 connected to the meter 106, panel 108, and/or loads 110. The consumption management system 112 may alternatively be referred to as a load curtailment system. The consumption management system 112 may comprise a system controller 114 in electronic communication with an energy storage system (ESS) 116 and an inverter 118 (or other converter apparatus). The consumption management system 112 may have a wired or wireless connection to any of the other components at the site 100. In
The system controller 114 may receive information from the meter 106, loads, 110, energy storage 116, inverter 118, and any other components at the site 100. The system controller 114 may also have a connection to a network 120 such as, for example, the Internet, via a network connection or other transceiver apparatus. The system controller 114 may therefore be in one-way or two-way connection with a remote location to report information or receive instructions. The system controller 114 may comprise a computing device configured to send and receive electronic signals and to execute instructions stored in a memory device using a processor. See
The energy storage 116 may alternatively be referred to as a load curtailment device or an energy storage system (ESS). The energy storage 116 may comprise a storage device for electrical energy, such as, for example, a battery bank, capacitor bank, flywheel system, or other related energy storage system capable of being charged by electrical energy and discharged to provide electrical energy. The inverter 118 may link the energy storage 116 to the panel 108. For example, the inverter 118 may comprise a two-way DC-AC inverter that allows the energy storage 116 to provide AC power to the panel 108 or to charge the energy storage 116 with DC power. In some embodiments, converters other than an inverter may be used, or the inverter 118 may be omitted, depending on the electrical system being used at the site 100. Accordingly, the energy storage 116 and inverter 118 are shown here for example purposes, but other devices and combinations of devices may be used by those having skill in the art to implement the functions and features of embodiments the present disclosure.
The energy storage 116 may be charged to draw energy from the utility distribution grid 104 or may be discharged to provide energy to the utility distribution grid 104. When charging, the energy storage 116 may increase the consumption recorded from the grid 104 at the meter 106, and when discharging, the energy storage 116 may decrease consumption recorded from the grid 104 via the meter 106. In this manner, discharging the energy storage 116 may reduce the recorded power draw of the site 100 (e.g., the recorded power draw of the loads 110 from the grid 104) that would be used to determine a demand charge for the consumer. Charging the energy storage 116 may increase the recorded power draw of the site 100.
Thus, when the average power draw of the site within a subdivision of a billing period exceeds a predetermined setpoint (i.e., there is an energy surplus), the energy storage 116 may be discharged during that subdivision to drive down and reduce the average power draw during that subdivision. If the average power draw is below the setpoint within the subdivision, the energy storage 116 may be charged from the grid 104 in a manner that drives up the average power draw within the subdivision without causing the average to exceed the setpoint.
Operation of the consumption management system 112 within a billing period is explained in detail herein in connection with
The plurality of subdivisions may each have a predetermined length. Generally, the subdivisions have equal lengths. For example, each subdivision may comprise a length of 5 minutes, 10 minutes, 15 minutes, 60 minutes, or any other division of time that is less than or equal to the duration of the billing period. Thus, the time between T1 and T2 may correspond to the time between 12:15 p.m. and 12:30 p.m. on one day of the billing period. In some embodiments, there is a single subdivision of the billing period extending from time TA to time TB. However, utility providers commonly practice assessing demand charges based on a plurality of subdivisions, with one common subdivision duration being 15 minutes. Therefore, a plurality of 15-minute subdivisions within a month-long billing period is used herein for example purposes in explaining the function and operation of the present apparatuses, systems, and methods.
In the billing period subdivision shown in
Referring again to
More signals are received by the system controller between the time of signal S4 and the end of the subdivision at time T2. When the signals are received in fast succession, such as between signal S5 and signal S9, the system controller may react by discharging energy storage in a manner proportional to the amount needed to bring the average power draw from time T1 to the time of signal S9 to or below the setpoint. When the signals are received more spaced apart, such as between signal S9 and signal S11, the controller may slow the discharging if needed or allow the energy storage to recharge if the average power draw for the subdivision is expected to end up below the setpoint.
Accordingly, as shown in
The average power draw may be calculated using the energy tracking signals without needing to track and react to instantaneous changes to the direct load profile. This may be advantageous because typical inverters operate most efficiently when they operate at full power, whether that operation is drawing power from the grid or providing power to the grid. Thus, rather than using the inverter or other converter to provide an exactly proportional response that mirrors any change to a load profile, the load curtailment system may charge or discharge using the inverter at its full capacity at all times to provide demand charge management without incurring the costs of undue conversion inefficiencies. The inverter may also not be required to react immediately to changes in the power draw of the site. Rather, the inverter may be given much more time, such as the entire remaining time in the subdivision after receiving an energy tracking signal, to start up and provide its charging or discharging function without detrimental effect on the future calculation of the demand charge for the billing period.
In some configurations, the energy tracking notification may be a notification that a quantity of energy (i.e., a quantum value) has been consumed by the site from the utility distribution grid, such as the signal S1 shown in
In other embodiments, the first energy tracking notification may be a notification of the start of a billing period (e.g., notification that time TA has been reached) or at the start of a subdivision of a billing period (e.g., notification that time T1 has been reached). Therefore, the first energy tracking notification may be a notification that energy consumption should be tracked from the time it is received (e.g., from time TA or T1 onward). The meter 106 may provide the signal of the start of a new subdivision or billing period, and in some cases the system controller may receive the signal from a separate clock or timer from the meter.
In some arrangements, the first energy tracking notification may be provided before the start of the billing period or subdivision of the billing period. For example, the first energy tracking notification may be signal R1 in
The method 200 may further comprise receiving a second energy tracking notification from the utility meter at a second time, as shown in block 204. The second energy tracking notification may be received by the system controller 114. The second energy tracking notification may be sent after a quantity of energy is consumed by the customer site from the utility distribution grid. The second energy tracking notification may be received after the first energy tracking notification is received. As explained above, the time between the first and second energy tracking notifications may be variable and dependent upon the power draw of the site and the size of the quantum value of the site that is typically set by the utility provider. Thus, in order to determine whether a load management action needs to be taken, the method 200 may further comprise determining a representative power level of the customer site drawn from the utility distribution grid between the first time and the second time based on the quantum of energy, as indicated in block 206. In one example, the system controller 114 may determine the representative power level. The power level or power draw may be the average power consumed by the site (e.g., in watts) across the time between the first and second times.
Additionally, in some embodiments the first energy tracking notification may be the start time of a subdivision of a billing period (e.g., time T1). In that case, the site may or may not have consumed the quantum value of energy between the first energy tracking notification and the second energy tracking notification. Nevertheless, the system may estimate that the energy consumed between the first and second energy tracking notifications is equal to the quantum value.
The method may be implemented at a location where a setpoint or target power level is predetermined. For example, a load curtailment system at a site may be sized, configured, and optimized to manage a certain predetermined amount of curtailment for that site. An example site could have a system configured to reduce the maximum average power draw by 5 kilowatts (or some other target value), thereby reducing the demand charge billed to the site due to the maximum average load of the subdivisions of the billing period being 5 kilowatts lower than would otherwise have occurred. Accordingly, the method 200 may comprise comparing the power draw based on the first and second energy consumption notifications to determine whether there is an energy surplus or deficit in the billing period. In some embodiments, the surplus or deficit may be determined based on a difference between the representative power level (e.g., the average power level between the energy consumption notifications) and a target power level (e.g., the setpoint for the billing period), as indicated in block 208. In one example, the system controller 114 may determine the energy deficit or surplus.
The method 200 may further comprise operating a load curtailment system to transfer energy to or from the utility distribution grid, wherein the transferred energy offsets the energy surplus or deficit within a billing period, as shown in block 210. In one example, the system controller 114 may perform the transfer of energy to or from the utility distribution grid to offset the energy surplus or deficit. This part of the method 200 may comprise transferring energy from an energy storage system (e.g., 116) to the grid or charging the energy storage system from the grid using an inverter (e.g., 118) or other conversion device. The offset energy may be at least an amount of energy required to eliminate the surplus or to at least partially eliminate the deficit. In some arrangements, the energy transfer may be configured to be performed at the maximum possible transfer rate of any conversion equipment (e.g., inverters) at all times.
The following example embodiment provides one way that a system controller may perform its functions described in method 200. Over time, a plurality of inputs may be provided to the system controller. These inputs may determine the behavior of the system controller as it manages the peak power draw of the site. The relationship of these inputs is provided below. The inputs may comprise:
Edeficit, which represents the energy deficit of the current demand measuring period/subdivision of the billing period. This value may be provided in kilowatt-hours or equivalent units and may be expressed as a negative number if there is a surplus of energy consumption during the current subdivision;
Enewest tick, which represents the most recent total energy consumption value measured by the meter. This value may be provided in kilowatt-hours or equivalent units and may represent the cumulative energy consumed by the site at the time a quantum value of energy has been consumed by the site;
Einitial, which represents the cumulative energy measured by the meter at the beginning of the demand measurement period. The time of Einitial may vary from case to case, and may be the same as Enewest tick. This value may be provided in kilowatt-hours or equivalent units;
P, which represents the raw power request to the inverter without state-of-charge (SOC) limits on the energy storage and limits on the inverter. A positive value may represent charging the energy storage, and a negative value may represent discharging the energy storage. This value may be provided in kilowatts or equivalent units;
Tlength, which represents the total length of demand measurement period/the current subdivision of the billing period;
Tnewest tick, which represents the time at which the most recent energy tick measurement signal has been received by the controller;
Tinitial, which represents the time of the last energy tick in the previous demand measurement period. Tinitial may vary according to the operating scheme used at the site, as explained in further detail below;
Tcurrent, which represents the current time;
SP, which represents the peak shaving setpoint. This value may be provided in kilowatts or equivalent units. The setpoint may be the value used by the utility to determine a demand charge of the site at the end of the billing period. Alternatively, the setpoint may be a power value that the customer does not wish to exceed for reasons other than incurring demand charges, such as, for example, a power value that when exceeded may cause damage to electrical components or connections at the site; and
α, which represents a tuning parameter having a value greater than 0 and less than or equal to 1. This parameter may define how much of the remaining time in the subdivision of the billing period that the controller should use to offset Edeficit. For example, if α=0.5, then the value of P will be set to erase any energy deficit or surplus in half of the timer remaining in the subdivision of the billing period. A value of 1 for α may be the least aggressive setting that allows the system to take the entire remaining time of the demand measurement period to remove the energy deficit, while a value close to 0 will make the system try to remove the energy deficit as soon as possible. The optimal tuning parameter a for each site may be dependent on site characteristics such as demand profile and demand sources, and will require individual tuning for every site. In some embodiments, however, the value of a may be at least about 0.2 in order to avoid aggressive cycling of the inverter.
Using the inputs described above, the controller may implement the following logic. The following logic is provided as an example and should not be viewed as limiting the types of operations that may be used to achieve the purposes and perform the functions of the controller.
The controller may determine the energy deficit (or surplus) as follows:
Edeficit=Enewest tick−Einitial−SP*(Tnewest tick−Tinitial) [Equation 1]
The controller may follow the following logic with the energy deficit (or surplus). The power P may be determined as:
P=−Edeficit/(α*(Tlength−Tnewest tick+Tinitial), [Equation 2]
wherein if
(Edeficit>0) and (−Edeficit<(P*(Tcurrent−Tnewest tick))), [Equation 3]
then P=0 (in order to prevent the system from over-discharging if the site's energy consumption is so low that the ticks cease to occur), and if
(Einitial=Enewest tick), [Equation 4]
then P=0 (in order to prevent the system from automatically attempting to charge the energy storage at the beginning of each subdivision of the billing period).
This controller logic may work well when a reasonably sized quantum value is used for the metering device. This may not be the case, so a maximum threshold for the quantum value (relative to typical site consumption rates) may be implemented, beyond which a site will not meet the criteria for achieving reasonable peak shaving/load management performance. For example, if the quantum value only allows for one or two energy tracking notification signals to be received by the controller in a subdivision of a billing period even though there is high power draw, the site may not be a good candidate for the present systems and methods. In some embodiments, the quantum value threshold may therefore be one tenth or less of the subdivsion's energy consumption during critical (e.g., high-power-draw) hours.
In some configurations, the controller's logic may detect and prevent back feeding of energy into the grid. The determination of Equation 3 shown above may help to address this issue given an energy tick-based measurement scenario. Using Equation 3, the controller may automatically stop discharge once the battery has discharged enough energy to completely remove the energy deficit calculated with the most updated energy values. The sensitivity of the control logic to back feeding may be directly correlated to the size of the quantum value, so more stringent criterion may have to be enforced if there are strict requirements imposed by a utility or customer against back feeding. If all types and degrees of back feeding are forbidden at a site, more equipment may be installed for instantaneous monitoring of site power levels.
The controller logic may operate under an assumption that the setpoint is set correctly, and therefore will operate the battery with maximum effort (i.e., maximum energy transfer rates) until hitting internal state-of-charge (SOC) thresholds for the energy storage system. The controller may not have the ability to affect the curtailment value, as that would erode the authority of an associated curtailment generation service (CGS) and may confound curtailment calculation inputs, which may ultimately yield lower performing curtailment values. Instead, the system controller may be designed to provide signals on system resource health to the CGS, such as frequency of reaching critically low SOC ranges.
In one embodiment, the value of Tinitial may be equal to T0, where T0 represents the starting time of the subdivision of the billing period in question. In
In a second embodiment, Tinitial may be equal to time of the most recent tick signal in the previous subdivision of the billing period before T0. In
In a third embodiment, Tinitial is the time of the first tick in the present subdivision of the billing period. In
In some cases, device 305 may communicate with a remote storage device, and/or a remote server (e.g., server 155). For example, one or more elements of device 305 may provide a direct connection to a remote server via a direct network link to the Internet via a POP (point of presence). In some embodiments, one element of device 305 (e.g., one or more antennas, transceivers, etc.) may provide a connection using wireless techniques, including digital cellular telephone connection, Cellular Digital Packet Data (CDPD) connection, digital satellite data connection, and/or another connection.
Many other devices and/or subsystems may be connected to one or may be included as one or more elements of system 300 (e.g., cell radio module, battery, utility equipment monitor, and so on). In some embodiments, all of the elements shown in
The signals associated with system 300 may include wireless communication signals such as radio frequency, electromagnetics, LAN, WAN, VPN, wireless network (using 802.11, for example), 345 MHz, Z-WAVE®, cellular network (using 3G and/or Long Term Evolution (LTE), for example), and/or other signals. The radio access technology (RAT) of system 300 may be related to, but are not limited to, wireless wide area network (WWAN) (GSM, CDMA, and WCDMA), wireless local area network (WLAN) (including BLUETOOTH® and Wi-Fi), WiMAX, antennas for mobile communications, antennas for Wireless Personal Area Network (WPAN) applications (including radio frequency identification devices (RFID) and UWB). In some embodiments, one or more sensors (e.g., current or voltage sensors, ammeters, volt meters, magnetic sensors, and/or other sensors) may be connected to some elements of system 300 via a network using the one or more wired and/or wireless connections.
Processor 320 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 320 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor 320. Processor 320 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting a thermostat with downcast light).
Memory 325 may include RAM and ROM. The memory 325 may store computer-readable, computer-executable software 330 including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 325 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware and/or software operation such as the interaction with peripheral components or devices. In some embodiments, the memory 325 may be part of a non-transitory computer-readable medium that is separable from the device 305, such as, for example, a CD-ROM, DVD-ROM, flash memory drive, and other similar data storage devices.
Software 330 may include code to implement aspects of the present disclosure, including code to support operation of a system controller for energy-based load management. Software 330 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 330 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein. For example, the software 330 may be configured to perform the methods described in connection with
Transceiver 335 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 335 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 335 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas. The transceiver 335 may communicate bi-directionally with external computing devices 360 and 365, remote computing devices (via connection to network 120), one or more utility meter 106, a server 155, one or more building management systems and utility monitoring services, or combinations thereof.
I/O controller 340 may manage input and output signals for the device 305. I/O controller 340 may also manage peripherals not integrated into the device 305. In some cases, I/O controller 340 may represent a physical connection or port to an external peripheral. In some cases, I/O controller 340 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, OS-X®, UNIX®, LINUX®, or another known operating system. In other cases, I/O controller 340 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, I/O controller 340 may be implemented as part of a processor. In some cases, a user may interact with device 305 via I/O controller 340 or via hardware components controlled by I/O controller 340. In some arrangements, an external computing device 360, 365 may be used to interact with the device 305.
User interface 345 may enable a user to interact with device 305. In some embodiments, the user interface 345 may include an audio device, such as an external speaker system, an external display device such as a display screen, and/or an input device (e.g., remote control device interfaced with the user interface 345 directly and/or through the I/O controller module).
The curtailment controller 315 may provide a connection to an inverter 118 and energy storage 116. Thus, information about the status of the inverter 118 (e.g., its power level, health, temperature, and other status information) and the status of the energy storage 116 (e.g., its state of charge (SOC), voltage, temperature, cycle count, and other status information) may be communicated to the device 305. The curtailment controller 315 may also provide a control interface with the inverter 118 and energy storage 116 to perform the functions of the device 305 and system controllers described herein.
Various inventions have been described herein with reference to certain specific embodiments and examples. However, they will be recognized by those skilled in the art that many variations are possible without departing from the scope and spirit of the inventions disclosed herein, in that those inventions set forth in the claims below are intended to cover all variations and modifications of the inventions disclosed without departing from the spirit of the inventions. The terms “including:” and “having” come as used in the specification and claims shall have the same meaning as the term “comprising.”
Number | Name | Date | Kind |
---|---|---|---|
1831553 | Byles | Nov 1931 | A |
4023043 | Stevenson | May 1977 | A |
4059747 | Brody | Nov 1977 | A |
4277691 | Lunn | Jul 1981 | A |
4520274 | Stants | May 1985 | A |
4731547 | Alenduff et al. | Mar 1988 | A |
5500561 | Wilhelm | Mar 1996 | A |
5644173 | Elliason et al. | Jul 1997 | A |
5703442 | Notohamiprodjo et al. | Dec 1997 | A |
5798633 | Larsen et al. | Aug 1998 | A |
5816491 | Berkeley et al. | Oct 1998 | A |
5930773 | Crooks et al. | Jul 1999 | A |
6037758 | Perez | Mar 2000 | A |
6067482 | Shapiro | May 2000 | A |
6134124 | Jungreis et al. | Oct 2000 | A |
6157874 | Cooley | Dec 2000 | A |
6172432 | Schnackenberg et al. | Jan 2001 | B1 |
6476519 | Weiner | Nov 2002 | B1 |
6522031 | Provanzana et al. | Feb 2003 | B2 |
6542791 | Perez | Apr 2003 | B1 |
6563048 | Holt et al. | May 2003 | B2 |
6618709 | Sneeringer | Sep 2003 | B1 |
6652330 | Wasilewski | Nov 2003 | B1 |
6671586 | Davis et al. | Dec 2003 | B2 |
6728646 | Howell et al. | Apr 2004 | B2 |
6785592 | Smith et al. | Aug 2004 | B1 |
6868293 | Schurr et al. | Mar 2005 | B1 |
6882904 | Petrie et al. | Apr 2005 | B1 |
6889122 | Perez | May 2005 | B2 |
6900556 | Provanzana et al. | May 2005 | B2 |
6902837 | McCluskey et al. | Jun 2005 | B2 |
6977446 | MacKay | Dec 2005 | B2 |
7060379 | Speranza et al. | Jun 2006 | B2 |
7069161 | Gristina et al. | Jun 2006 | B2 |
7122916 | Nguyen et al. | Oct 2006 | B2 |
7132833 | Layden et al. | Nov 2006 | B2 |
7142949 | Brewster et al. | Nov 2006 | B2 |
7171374 | Sheehan et al. | Jan 2007 | B1 |
7193872 | Siri | Mar 2007 | B2 |
7274975 | Miller | Sep 2007 | B2 |
7482710 | Ichinose et al. | Jan 2009 | B2 |
7778738 | Taft | Aug 2010 | B2 |
7782021 | Kelty et al. | Aug 2010 | B2 |
7783544 | Horowitz | Aug 2010 | B2 |
7818226 | Brawley et al. | Oct 2010 | B2 |
7844529 | Ziade et al. | Nov 2010 | B2 |
7863866 | Wolf | Jan 2011 | B2 |
7873441 | Synesiou et al. | Jan 2011 | B2 |
7894946 | Kulyk et al. | Feb 2011 | B2 |
7943250 | Johnson et al. | May 2011 | B1 |
7949615 | Ehlers et al. | May 2011 | B2 |
8024077 | Torre et al. | Sep 2011 | B2 |
8078330 | Brickfield et al. | Dec 2011 | B2 |
8090600 | Ziade et al. | Jan 2012 | B2 |
8126794 | Lange et al. | Feb 2012 | B2 |
8396726 | Ziade et al. | Mar 2013 | B2 |
8417391 | Rombouts et al. | Apr 2013 | B1 |
8442698 | Fahimi et al. | May 2013 | B2 |
8588989 | Heath et al. | Nov 2013 | B1 |
8682491 | Fakos et al. | Mar 2014 | B2 |
8706650 | Ozog | Apr 2014 | B2 |
8761949 | Mansfield | Jun 2014 | B2 |
8761952 | Forbes | Jun 2014 | B2 |
8912672 | Pendray et al. | Dec 2014 | B2 |
8930269 | He et al. | Jan 2015 | B2 |
8983673 | Chow | Mar 2015 | B2 |
9002670 | Hurri et al. | Apr 2015 | B2 |
9003216 | Sankar et al. | Apr 2015 | B2 |
9007027 | Prosser | Apr 2015 | B2 |
9048671 | Prosser | Jun 2015 | B2 |
9235825 | Shao | Jan 2016 | B2 |
9312698 | Subbotin et al. | Apr 2016 | B2 |
9431827 | Chow et al. | Aug 2016 | B2 |
9489701 | Emadi et al. | Nov 2016 | B2 |
20010043013 | Abe | Nov 2001 | A1 |
20020120368 | Edelman et al. | Aug 2002 | A1 |
20030041016 | Spool et al. | Feb 2003 | A1 |
20030055677 | Brown et al. | Mar 2003 | A1 |
20030230443 | Cramer et al. | Dec 2003 | A1 |
20040024483 | Holcombe | Feb 2004 | A1 |
20040084965 | Welches et al. | May 2004 | A1 |
20040215529 | Foster et al. | Oct 2004 | A1 |
20050043862 | Brickfield et al. | Feb 2005 | A1 |
20050102068 | Pimputkar et al. | May 2005 | A1 |
20050138929 | Enis et al. | Jun 2005 | A1 |
20060017328 | Bryde | Jan 2006 | A1 |
20060276938 | Miller | Dec 2006 | A1 |
20070005192 | Schoettle et al. | Jan 2007 | A1 |
20070061021 | Cohen et al. | Mar 2007 | A1 |
20070103835 | Sorenson | May 2007 | A1 |
20070156559 | Wolzenski et al. | Jul 2007 | A1 |
20080046387 | Gopal et al. | Feb 2008 | A1 |
20080114499 | Hakim et al. | May 2008 | A1 |
20080167756 | Golden et al. | Jul 2008 | A1 |
20080172312 | Synesiou et al. | Jul 2008 | A1 |
20080183337 | Szabados | Jul 2008 | A1 |
20080191675 | Besser et al. | Aug 2008 | A1 |
20080203975 | Burlak et al. | Aug 2008 | A1 |
20080272934 | Wang et al. | Nov 2008 | A1 |
20080281473 | Pitt | Nov 2008 | A1 |
20090006279 | Buettner et al. | Jan 2009 | A1 |
20090048716 | Marhoefer | Feb 2009 | A1 |
20090088907 | Lewis et al. | Apr 2009 | A1 |
20090157529 | Ehlers et al. | Jun 2009 | A1 |
20090212745 | Kelty | Aug 2009 | A1 |
20090216688 | Kelty et al. | Aug 2009 | A1 |
20090222143 | Kempton | Sep 2009 | A1 |
20090243540 | Choi et al. | Oct 2009 | A1 |
20090254396 | Metcalfe | Oct 2009 | A1 |
20090307117 | Greiner et al. | Dec 2009 | A1 |
20090317694 | Ängquist et al. | Dec 2009 | A1 |
20100017045 | Nesler et al. | Jan 2010 | A1 |
20100023337 | Case | Jan 2010 | A1 |
20100072947 | Chan et al. | Mar 2010 | A1 |
20100114389 | Chatterton et al. | May 2010 | A1 |
20100145534 | Forbes et al. | Jun 2010 | A1 |
20100174419 | Brumfield et al. | Jul 2010 | A1 |
20100174643 | Schaefer et al. | Jul 2010 | A1 |
20100217550 | Crabtree et al. | Aug 2010 | A1 |
20100217642 | Crubtree et al. | Aug 2010 | A1 |
20100253244 | Snook et al. | Oct 2010 | A1 |
20100262296 | Davis et al. | Oct 2010 | A1 |
20100271802 | Recker et al. | Oct 2010 | A1 |
20100274602 | Kaufman et al. | Oct 2010 | A1 |
20100280978 | Shimada et al. | Nov 2010 | A1 |
20100283606 | Tsypin et al. | Nov 2010 | A1 |
20100286937 | Hedley et al. | Nov 2010 | A1 |
20100295514 | Burlak et al. | Nov 2010 | A1 |
20100301771 | Chemel et al. | Dec 2010 | A1 |
20100301773 | Chemel et al. | Dec 2010 | A1 |
20100324962 | Nesler et al. | Dec 2010 | A1 |
20100327800 | Reineccius | Dec 2010 | A1 |
20100332373 | Crabtree et al. | Dec 2010 | A1 |
20110004358 | Pollack et al. | Jan 2011 | A1 |
20110022419 | Ziade et al. | Jan 2011 | A1 |
20110035061 | Altonen et al. | Feb 2011 | A1 |
20110040666 | Crabtree et al. | Feb 2011 | A1 |
20110046806 | Nagel et al. | Feb 2011 | A1 |
20110046904 | Souilmi | Feb 2011 | A1 |
20110082598 | Boretto et al. | Apr 2011 | A1 |
20110133655 | Recker et al. | Jun 2011 | A1 |
20110137481 | Manz et al. | Jun 2011 | A1 |
20110166710 | Kordik et al. | Jul 2011 | A1 |
20110173109 | Synesiou et al. | Jul 2011 | A1 |
20110184574 | Roux et al. | Jul 2011 | A1 |
20110193518 | Wright et al. | Aug 2011 | A1 |
20110196692 | Chavez et al. | Aug 2011 | A1 |
20110204720 | Ruiz et al. | Aug 2011 | A1 |
20110208369 | Yang et al. | Aug 2011 | A1 |
20110231320 | Irving | Sep 2011 | A1 |
20110251933 | Egnor et al. | Oct 2011 | A1 |
20110301894 | Sanderford | Dec 2011 | A1 |
20110309799 | Firehammer | Dec 2011 | A1 |
20120010757 | Francino et al. | Jan 2012 | A1 |
20120016528 | Raman et al. | Jan 2012 | A1 |
20120029720 | Cherian et al. | Feb 2012 | A1 |
20120035777 | Park | Feb 2012 | A1 |
20120059607 | Rebec et al. | Mar 2012 | A1 |
20120061963 | Thisted | Mar 2012 | A1 |
20120065789 | Scelzi et al. | Mar 2012 | A1 |
20120065792 | Yonezawa et al. | Mar 2012 | A1 |
20120074780 | Fleck | Mar 2012 | A1 |
20120083930 | Ilic et al. | Apr 2012 | A1 |
20120101639 | Carralero et al. | Apr 2012 | A1 |
20120101921 | Anderson et al. | Apr 2012 | A1 |
20120130556 | Marhoefer | May 2012 | A1 |
20120185105 | McMullin | Jul 2012 | A1 |
20120197452 | Matthews et al. | Aug 2012 | A1 |
20120242148 | Galati | Sep 2012 | A1 |
20120245744 | Prosser et al. | Sep 2012 | A1 |
20120245751 | Gow et al. | Sep 2012 | A1 |
20120310416 | Tepper et al. | Dec 2012 | A1 |
20130018821 | Shao | Jan 2013 | A1 |
20130024342 | Horowitz et al. | Jan 2013 | A1 |
20130030590 | Prosser | Jan 2013 | A1 |
20130030595 | Chow et al. | Jan 2013 | A1 |
20130047010 | Massey et al. | Feb 2013 | A1 |
20130060719 | Burke et al. | Mar 2013 | A1 |
20130085614 | Wenzel et al. | Apr 2013 | A1 |
20130117004 | Schultz et al. | May 2013 | A1 |
20130134780 | Parsonnet | May 2013 | A1 |
20130173191 | McDonald et al. | Jul 2013 | A1 |
20130190939 | Lenox | Jul 2013 | A1 |
20130226544 | Mcconaghy et al. | Aug 2013 | A1 |
20130232151 | Shao | Sep 2013 | A1 |
20130271083 | Williams | Oct 2013 | A1 |
20130274935 | Deshpande et al. | Oct 2013 | A1 |
20130285610 | Katou et al. | Oct 2013 | A1 |
20130297092 | Willig et al. | Nov 2013 | A1 |
20130325197 | Mansfield | Dec 2013 | A1 |
20140019171 | Koziol | Jan 2014 | A1 |
20140039710 | Carter et al. | Feb 2014 | A1 |
20140067140 | Gow | Mar 2014 | A1 |
20140070756 | Kearns et al. | Mar 2014 | A1 |
20140074306 | Lu et al. | Mar 2014 | A1 |
20140122906 | Whitted et al. | May 2014 | A1 |
20140152007 | Sterregaard et al. | Jun 2014 | A1 |
20140163755 | Potter et al. | Jun 2014 | A1 |
20140379160 | Fallon | Dec 2014 | A1 |
20150015213 | Brooks et al. | Jan 2015 | A1 |
20150025917 | Stempora | Jan 2015 | A1 |
20150094965 | Schneider et al. | Apr 2015 | A1 |
20150295449 | Prosser | Oct 2015 | A1 |
20160006245 | Chow | Jan 2016 | A1 |
20160055412 | Carroll et al. | Feb 2016 | A1 |
20160161932 | Shao | Jun 2016 | A1 |
20160360336 | Gross et al. | Dec 2016 | A1 |
20170038786 | Asghari et al. | Feb 2017 | A1 |
20170060162 | Holzman et al. | Mar 2017 | A1 |
20170063083 | Holzman | Mar 2017 | A1 |
20170098229 | Vickery et al. | Apr 2017 | A1 |
20170098279 | Vickery et al. | Apr 2017 | A1 |
20170099056 | Vickery et al. | Apr 2017 | A1 |
20170102726 | Goldsmith | Apr 2017 | A1 |
20170243139 | Dzierwa et al. | Aug 2017 | A1 |
20170324256 | Mcmorrow et al. | Nov 2017 | A1 |
20170331290 | Burlinson | Nov 2017 | A1 |
20180358835 | Tian | Dec 2018 | A1 |
Number | Date | Country |
---|---|---|
0111525 | Feb 2001 | WO |
2017035258 | Mar 2017 | WO |
2017040586 | Mar 2017 | WO |
2017059340 | Apr 2017 | WO |
2017059345 | Apr 2017 | WO |
2017059350 | Apr 2017 | WO |
Entry |
---|
“DOE-2 Engineers Manual,” Nov. 1982 (763 pages). |
Author Unknown, “Load aggregation of multiple facilities,” published at “http://www.obvius.com/applicationnotes.php,” (4 pages). |
Author Unknown, “Load Curtailment/Demand Response,” published at “http://www.obvius.com/applicationnotes.php,” (4 pages). |
International Search Report for International Patent Application No. PCT/US2016/048448, dated Nov. 18, 2016 (2 pages). |
International Search Report for International Patent Application No. PCT/US2016/049587, dated Nov. 15, 2016 (2 pages). |
International Search Report for International Patent Application No. PCT/US2016/054965, dated Nov. 16, 2016 (4 pages). |
International Search Report for International Patent Application No. PCT/US2016/054973, dated Nov. 16, 2016 (4 pages). |
International Search Report International Patent Application No. PCT/US2016/054983, dated Nov. 16, 2016 (4 pages). |
Norris et al.,“NAS Battery Demonstration at American Electric Power: A Study for the DOE Energy Storage Program,” Sandia Report, Mar. 2007, pp. 1-55. |
Pedrasa et al.,“Robust Scheduling of Residential Distributed Energy Resources Using a Novel Energy Service Decision-Support Tool,” IEEE, 2011 (8 pages). |
Craft, “Local Energy Management Through Mathematical Modeling and Optimization,” 2004 (223 pages). |
Iman et al., “A Distribution-Free Approach to Inducing Rank Correlation Among Input Variables,” Communications in Statistics—Stimulation and Computation, 1982, pp. 311-334, vol. 11, No. 3. |
Jeon et al., “Using deferrable demand in a smart grid to reduce the cost of electricity for customers”, Journal of Regulatory Economics, Springer Science+Business Media New York. (Year:2015). |
Johnson et al., “Renewable Generation Capacity and Wholesale Electricity Price Variance”, Energy Journal, International Association for Energy Economics, Inc. (Year: 2019). |
Stylianos et al., “Optimal Bidding Strategy for Electric Vehicle Aggregators in Electricity Markets”, IEEE Transactions on Power Systems, vol. 28, No. 4, (Nov. 2013). |
Number | Date | Country | |
---|---|---|---|
20180342867 A1 | Nov 2018 | US |