The present invention generally relates to power distribution networks, and particularly relates to managing demand response resources in such networks.
Electricity grids use “demand response” (DR) mechanisms to control loading on the grid, such as by shedding load or delaying load. DR operations depend on having one or more customer loads configured to respond to DR signaling. In an example implementation, the operator(s) of a given power distribution network determine that a DR event is needed, demand responsive loads are selected for participation in the DR event, and signaling is sent accordingly, to control the selected demand responsive loads. Control actions include shut-off, which essentially takes the load off the grid, but may also include percent-reduction commands that allow given loads to be reduced but not entirely shut off.
The process of selecting demand responsive loads (customers) during a DR event is traditionally a random process where the customers are selected based on the similarity of the constraints in their utility contracts and the time constraints of the DR event issued. The location and number of customers chosen this way is not necessary optimal because of the random nature of the selection process.
Other known selection techniques include the use of “electrical distance” as the selection factor used to determine which demand responsive loads are selected for participation in a given DR event. This approach drives the load selection process according to power loss evaluations that are determined according to the electrical distance model, which disfavors or otherwise complicates its application to mesh networks and other complex topologies and/or to networks that include distributed generation systems.
In one aspect of the teachings herein, demand responsive loads are selected for involvement in a given DR event using an advantageous approach to selection that is based on using a mathematical network model to evaluate power loss in a power distribution network as a function of different combinations of demand responsive load selections and corresponding load reduction values. Using the model-based DR load selection as taught herein reduces the amount of load reduction that must be imposed on the power distribution network to achieve the required DR load reduction amount, based on minimizing power loss in the power distribution network, subject to a number of constraints.
In more detail, the mathematical network model comprises a mathematical representation of the power distribution network as a multi-phase unbalanced distribution network, including mathematical representations of the physical components in the power distribution network and the connecting relationships of those components. As overall power loss in the system is a function of different combinations of demand responsive load selections, the mathematical network model is used to evaluate system power loss amounts under different demand response load selections, in a manner that automatically accommodates mesh networks and other complex network topologies, distributed generation sources, etc.
In an example embodiment, a method is implemented in a computer system and selects demand responsive loads in a power distribution network for inclusion in a demand response (DR) event having a defined load reduction target. The method includes determining that the DR event has been triggered for the power distribution network, and identifying demand responsive loads in the power distribution network that are candidates for inclusion in the demand response event.
The method continues with selecting a set of the demand responsive loads to include in the DR event and determining corresponding load reduction values for the selected set of demand responsive loads. The selection of which demand responsive loads are included in the DR event, and the determination of the corresponding load reductions values to be used for the selected loads, is based on using a mathematical network model to evaluate power loss in the power distribution network. More particularly, the power loss is evaluated as a function of different combinations of demand responsive load selections and corresponding load reduction values.
The evaluation determines which combination of demand responsive load selections and corresponding load reduction values maximizes a reduction in power loss in the power distribution network, while simultaneously satisfying the defined load reduction target and a number of solution constraints. In other words, the evaluation determines a DR solution that satisfies the load reduction target for the DR event, while minimizing power loss in the power distribution network subject to network operating limits. The one or more network operating constraints include at least one of power flow limits, node voltage limits and distribution line capacity limits.
Advantageously, the mathematical network model and its associated system states provide a direct mechanism for ensuring compliance with the various network operating constraints. The method also includes saving or otherwise outputting a demand response solution that indicates the selected set of demand responsive loads and the corresponding load reduction values determined for the selected set of demand responsive loads.
In another embodiment, a computer system is configured to select demand responsive loads in a power distribution network for inclusion in a demand response event having a defined load reduction target. The computer system includes one or more memory or storage elements, input/output interface circuitry, and a processing circuit operatively associated with the input/output interface circuitry and the one or more memory or storage elements.
The processing circuit is configured to determine that the demand response event has been triggered for the power distribution network and identify demand responsive loads in the power distribution network that are candidates for inclusion in the demand response event. Further, the processing circuit is configured to select a set of the demand responsive loads to include in the demand response event and determine corresponding load reduction values for the selected set of demand responsive loads.
The processing circuits makes the determination based on using a mathematical network model to evaluate power loss in the power distribution network as a function of different combinations of demand responsive load selections and corresponding load reduction values, to determine which combination of demand responsive load selections and corresponding load reduction values maximizes a reduction in power loss in the power distribution network while simultaneously satisfying the defined load reduction target and a number of solution constraints that include one or more network operating constraints. The network operating constraints include at least one of power flow limits, node voltage limits and distribution line capacity limits.
The processing circuit is further configured to save or otherwise output a demand response solution that indicates the selected set of demand responsive loads and the corresponding load reduction values determined for the selected set of demand responsive loads. For example, the processing circuit saves the demand response solution to the memory or storage elements, e.g., for use by a computer-implemented control routine that coordinates the DR event, or the processing circuit outputs the demand response solution or control signaling corresponding to that solution via its associated input/output circuitry.
Of course, the present invention is not limited to the above features and advantages. Indeed, those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.
Correspondingly, the PDN 10 includes multiphase branches or lines 16, buses 18, and loads 20. At least some of the loads 20 are demand response (DR) event resources, meaning that they can be controlled to shed load from the PDN 10 in a DR event. While the loads are numbered 20-1, 20-2, and so on, this discussion uses suffixes only where necessary for clarity and otherwise the terms “load 20” and “loads 20” are used for convenience.
In at least some embodiments, the PDN 10 includes one or more distributed generation sources 22 and/or one or more distributed generation networks 24. By way of example, a “distributed generation source 22” is coupled to the PDN 10 and thus operates on the distribution side of the overall electrical grid. Distributed generation sources 22 include, for example, wind turbines, solar power sites, etc. It will be appreciated that such sources exhibit potentially wide variation in the amount of power they inject into the PDN 10—indeed, they may be offline altogether at certain times of day or during certain weather conditions. Larger networks 24 of these distribution generation sources 22—e.g., larger scale solar power or wind power farms—further complicate evaluation of power flow and capacity for the PDN 10.
In another complicating aspect, the actual topology of the PDN 10 may be quite complex. In an example case, the PDN 10 comprises a “mesh” network, wherein the many interconnecting nodes result in a multiplicity of branch/node variables to evaluate for an accurate assessment of power flows and overall system states in the PDN 10. As with the distributed generation complexities, these topology complications are automatically considered or subsumed into the network model used in the demand response (DR) event processing taught herein.
In any case, the smart meters shown by way of example are used to measure the load demand at respective customer premises and can be used to disconnect or adjust customer loads in a DR event. Thus, in this example context, the two-way communication links or mechanisms are used to convey (1) load measurement information from the customer site to the control center 30 and (2) control command(s) from the control center 30 (such as DR signaling) to the customer site(s). The meter data management system 31 located in the control center collects meter measurement and interacts with one or more other computer systems or functions with in the control center 30, e.g., with a computer system 32 that is in the control center 30.
The memory/storage 42 also stores “code” comprising a computer program product including computer program instructions that, when executed by the processor(s) 40, cause the computer system 32 to carry out DR event processing as taught herein. In this regard, the memory/storage 42 will be understood as broadly representing one or more types of computer-readable medium and may be the memory or storage elements 34 introduced in
In any case, the memory/storage 42 further stores solution constraint data 48 and may store one or more other applications 52, representing further functionality provided by the control center 30. The solution constraint data 48 includes limits, for example, on the node or bus 18 voltages permitted within the PDN 10, limits on the current magnitudes permitted for the branches 16, etc. In general, the solution constraint data 48 includes limits for the various system state variables represented in the mathematical network model 44 of the PDN 10, which may be broadly referred to as “network operating limits.” These constraints may be updated dynamically or from time to time as needed, and solution constraints 48 may also include other information, such as the targeted load reduction for a given DR event—i.e., the amount by which the overall demand or load in the PDN 10 is to be reduced using DR load control. Further solution constraints in the solution constraint data 48 may comprise specified load reduction limits for given demand responsive loads 20 in the PDN 10, time/date based limits on when given ones of the demand responsive loads 20 are available for participation in DR events, etc.
The mathematical network model 44, as directly implied by its name, is a mathematical representation of the physical network components and their connecting relationships. For example, the mathematical network model 44 (hereafter “model 44”) may include all the loads (nameplate information and load profiles), transformers (nameplate information and configurations), power sources (capacity), switching devices (type and loading capability), distribution lines (conductor type, length, and impedance characteristics) and the interconnections (configuration) between them.
The computer system 32 also includes one or more interfaces 50 that are used for any number of information inputs, such as receiving DR information, system state information—i.e., the most current or live data representing voltages, phases, currents, etc., in the PDN 10. The computer system 32 also may receive operator inputs through the interface(s) 50, such as inputs indicating that a DR event has been called—i.e., a DR event trigger signal. Further, the computer system 32 may receive demand data and demand forecasting data, distributed generation output data and output forecasting data, etc., via the interface(s) 50, and may output any generated DR event solutions and/or corresponding load control signaling via the interface(s) 50.
The computer system 32 therefore is programmed and operative to carry out certain DR event processing according to the teachings herein.
It will be understood that one or more of the method steps or operations presented in
With these points in mind, the method 300 includes determining that a demand response event has been triggered for the PDN 10 (“YES” from Block 302). For example, the method 300 may include monitoring current or forecasted demand for the PDN 10 against some defined demand limit, and triggering the DR event when overall demand is too high or is trending too high. In other configurations, the DR event is called by another computer system and signaled to the computer system 32, or the DR event is called by human operators and inputs into the computer system 32.
The method 300 further includes identifying demand responsive loads in the power distribution network that are candidates for inclusion in the demand response event (Block 304). Here, the identification of demand responsive loads 20 that are “candidates” for inclusion in the DR event may simply comprise identifying those loads 20 in the PDN 10 that are associated with DR customer service agreements or, more simply, with reference to a listing of those loads 20 in the PDN 10 that are demand responsive loads. In other embodiments, the processing at step 304 includes a more sophisticated screening, such as identifying the candidates as those demand responsive loads 20 that are not associated with contractual constraints—e.g., date restrictions, time-of-day restrictions, event duration restrictions—that would prevent them from being considered for the particular DR event at hand.
With the candidate demand responsive loads 20 thus determined, the method 300 continues with selecting a set of the demand responsive loads to include in the demand response event and determining corresponding load reduction values for the selected set of demand responsive loads (Block 306). This processing uses the model 44 to evaluate power loss in the PDN 10 as a function of different combinations of demand responsive load selections and corresponding load reduction values. That is, the particular demand responsive loads 20 that are selected for load reduction, and the particular amounts of load reduction applied to individual ones of those loads results in a particular change in overall system state for the PDN 10 and different system states correspond to different amounts of power loss within the PDN 10.
Thus, the model 44 allows the computer system 32 to evaluate the system states of the PDN 10, and thereby determine the power losses associated with different assumed combinations of load selections and corresponding load reduction values. Such processing may comprise performing a mathematical analysis, e.g., such as performing an iterative computational algorithm that uses the network model 44 to determine an optimized DR solution.
The optimization processing, which generally is looped or otherwise iterated, includes evaluating demand responsive load selections and load reduction values with respect to power loss in the PDN 10, subject to all applicable system constraints (Block 306B). Such processing progresses until an optimum solution is found (Block 306C), subject of course to any convergence time or iteration limits. The optimum solution is then saved or otherwise output (Block 306D).
This processing allows the computer system 32 to determine which combination of demand responsive load selections and corresponding load reduction values maximizes a reduction in power loss in the power distribution network, while simultaneously satisfying the defined load reduction target and a number of solution constraints. As noted, the solution constraints include one or more network operating constraints, including at least one of power flow limits, node voltage limits and distribution line capacity limits.
The particular combination of demand responsive loads 20 that is selected and the particular load reduction values determined for respective ones of the selected demand responsive loads 20 constitute the demand response solution. Or, more generally, the demand response solution saved or outputted by the computer system 32 as part of the method 300 (Block 308) indicates the selected set of demand responsive loads 20 and the corresponding load reduction values determined for the selected set of demand responsive loads 20.
For example, some embodiments of the method 300 include sending signaling to customer premises equipment corresponding to the selected set of demand responsive loads 20, indicating the corresponding load reduction values determined for the selected set of demand responsive loads 20, to effectuate the demand response solution. Note that load reduction values may be expressed, e.g., as percent reductions in current or maximum loading.
The method 300 also may be extended to include comparing the demand response solution to an alternative demand response solution, e.g., one based on a randomly selected set of the demand responsive loads 20, and selecting for implementation either the demand response solution computed according to the method 300 or the alternative demand response solution. The selection is made in dependence on which solution sheds the least amount of customer loading from the PDN 10.
Of course, it is expected that the computed solution outlined in the method 300 will yield superior results all or most of the time. However, having the added step of comparing the model-aided solution against a random selection can serve as a rationality check or safeguard of sorts, and it will be understood that some embodiments simply use the demand response solution as computed in the method 300 without considering alternative solutions.
That is, given the full modeling provided by the model 44, the demand response solution computed via the method 300 generally will be optimal with respect to net load reductions in the PDN 10—i.e., the targeted load reduction of any given DR event will be satisfied to the greatest extent possible by reducing power losses in the PDN 10, without violating any system constraints, as compared to simply shedding actual customer loads. This optimization is possible because, as noted, the model 44 comprises a mathematical representation of the PDN 10 as a multi-phase unbalanced distribution network, including mathematical representations of the physical components in the power distribution network and the connecting relationships of those physical components.
Using the model 44 to evaluate power loss in the PDN 10 comprises, for example, evaluating power flow equations by applying the power and current balance laws at each node or bus 18 represented in the model 44, according to a known set of load values corresponding to the demand responsive loads 20, as adjusted for any particular combination of load reduction values being considered. In one example, such processing comprises finding the combination of load reduction values that minimizes, subject to the solution constraints, a power loss function for the PDN 10. Here, the power loss function is expressed as a function of the load reduction values and of a set of system states, and the solution constraints include any load reduction limits and load reduction timing restrictions associated with the demand responsive loads, and further include the network operating constraints, as applied to the set of system states.
The power loss function also may span a number of time intervals. In such cases, the processing represented by Block 306 of
Another embodiment expresses the power loss function as a summation of branch power losses over a plurality of branches 16 represented in the model 44. This approach computes the (power) loss in each branch 16 as a function of the modeled branch resistance and the square of the branch current magnitude calculated according to each evaluated combination of load reduction values.
Yet another embodiment expresses the power loss function as a function of customer incentive payments that would arise from the application of each evaluated combination of load reduction values. That is, the utility may have agreements in place with given customers under which the utility is obligated to provide power discounts or provide billing credits, etc., whenever the demand responsive loads 20 of those customers are included in a DR event. This embodiment further highlights the economics.
To better understand these contemplated power loss function variations, consider again the model 44, which describes various distribution system components including distribution feeders, laterals, loads, transformers, capacitors, voltage regulators, distributed generators, and so on. Based on these component models, power flow equations are usually formulated by applying the power/current balance law at each bus/node. The solution of the power flow equations provides system operating status in terms of node voltage magnitudes and angles. Mathematical component models and power flow equations represent precisely and completely the static characteristics of each component as well as the entire distribution network operation status.
where
where
With the above in mind, and with reference to
The constant electric powers injected to bus k_a,b,c are Sgk
Component currents in Eq. (5)-(7) can be expressed in terms of bus voltages as derived in the component models. Using equation (5) as an example, the currents of phase A distribution line and capacitor are expressed as follow:
Ĩkm
Ĩk
Upon substitution of above relationships into equation (5):
Sgk
These equations express power conservation at bus k for phase A. Similar equations can be written for phase b and phase c at bus k and phases at other buses in the distribution system. All these equations constitute the three-phase unbalanced power flow equations.
Further, with n buses in PDN 10, and assuming that except for the one slack bus, there are n−1 buses. The minimum set of variables describing the state of the system are:
One may assume that bus 1 is always the slack bus, and that some buses do not have full three-phases, such that the corresponding bus voltage phase angle and magnitudes then do not exist.
The variables are the state variables x at issue in the model 44. The state vector will be determined from an appropriate set of independent equations. For the purpose of selecting these equations, consider the following equations:
Power flow processing may be based on the Newton-Raphson method in polar form, where the three-phase unbalanced power flow problem is mathematically formulated as the solution of a set of linear and nonlinear equations. In compact form these equations can be written as:
gp(x)=ƒp(δ,V)−bp(δ,V)=0
gq(x)=ƒq(δ,V)−bq(δ,V)=0
where
Direct application of Newton's numerical solution algorithm to the power flow equations is known as the Newton-Raphson method. Newton's method is reviewed in its general form and then applied to the power flow equations.
Consider a set of nonlinear equations:
Assume that estimates x10, . . . xm0 for the m variables are known. Further assume that these estimates do not satisfy the above equations, and thus a better estimate is necessary. Newton's method provides the means by which the new, better estimates can be obtained. For this purpose, the functions g1 . . . gm are linearized around the known estimate of x10, . . . xm0. The procedure yields:
In the above expression, h.o.t. stands for higher order terms.
Assuming that the actual solution x is very close to the guess x0, then the higher order terms will be negligible because they depend on terms (xi−xi0)k where k≧2. Thus, neglecting the higher order terms, the following equations are obtained:
In compact matrix notation, the above equations become:
The matrix
is recognized to be the Jacobian matrix of the functions g, computed at x0 and will be symbolized with J(x0). Vector x is solved from the above equation:
x=x0−J−1(x0)·g(x0)
The vector x is a better estimate of the solution than vector x0. The procedure can be applied to any vector xi yielding the following algorithm:
xi+1=xi−J−1(xi)·g(xi)
The algorithm should terminate whenever a vector xi has been found which makes the vector function g(xi) very small. Note that in this case, Eq. (10) is satisfied. In summary, the solution to a set of nonlinear equations can be obtained with the following steps:
Direct application of Newton's method on these equations yields:
where i is the iteration number in the solution procedure.
The teachings herein thus integrate the above model 44 and such processing, or variations thereof, into the selection of demand responsive loads 20 for inclusion in a given DR event, which may be detected or called in view of the circumstances illustrated in
However triggered, use of the model 44 in the demand responsive load selection procedure enables the computer system 32 to accurately assess the affect of various load selection combinations on the power loss in the PDN 10, and thus enables the computer system 32 to determine the combination that yields the greatest reduction in system loss while meeting the demand reduction requirement and satisfying all the network operating constraints such as node voltage and distribution line capacity limits. To achieve this objective, a general optimization problem is formulated in terms of the previously described power loss function, and is solved to obtain the demand responsive loads 20 that maximize the reduction in power loss in the system, while still meeting all applicable solution constraints.
The optimization problem explicitly includes the mathematical system loss calculation based on the demand responsive load selection. However, power flow equations and other necessary operating constraints are included as constraints, so that the solution of the model-based optimization problem provides the appropriately constrained outcome. Without the loss of generality, one example of such mathematical formulation is provided below.
One may formulate the problem as that of finding the combination of demand response control variables/signals (uDR) to be sent to customers enrolled in the DR program in order to minimize the power loss function given as
ƒ=PLoss(x,uDR) (11)
subject to the following constraints:
The power loss function can be represented in different formula, one example is provided below:
In this power loss function, the loss in each branch (including distribution lines and transformer legs) is calculated first based on the branch resistance and the square of branch current magnitude, the sum of all the branch loss is the system loss. Each branch current is a function of system state variables (node voltage x) and demand response control variables uDR.
In another optimization formulation variation, the algorithm can be solved for multiple time steps in the future (for example T time steps), in which case the objective function will be altered to include the time information as follows:
And the demand reduction balance would be dependent on the time step, since the expected desired demand reduction for time t changes based on the load forecast results:
ΔPLoss(t)+ΔPL(t)−ΔPDes(t)=0 (14)
In yet another formulation, if the utility customers receive incentive payments upon receiving and complying with a DR signal, then it is possible to consider the economics of these incentive payments in the objective function as well:
where N denotes the total number of customers who receive the DR signal and C, corresponds to the incentive payment made to each one, α and β are weighting factors corresponding to power loss and incentive payment, respectively.
However the power loss function is formulated, an example outline of the overall solution methodology appears below:
As noted, the computer system 32 also may double-check the computed demand response solution, such as by comparing it to a more traditionally computed solution, such as a random load selection. The comparison can be based on a user defined performance metric consisting of the main features mentioned above. The simplest form of metric can be a weighted linear combination. The final solution is selected, presented to the operator for approval and dispatched to the corresponding customers.
Notably, as a consequence of using the model 44, the computed demand response solution taught herein automatically accommodates a range of complexities, such as radial and meshed distribution network topologies. Use of the model 44 also permits the approach taught herein for demand responsive load selection to easily accommodate distributed generation sources 22 and 24 within the PDN 10. More broadly, it will be understood that the teachings herein exploit the model 44 to accommodate multi-phase, unbalanced distribution networks using detailed mathematical component models, such as Wye and/or Delta connected transformers (grounded or ungrounded), voltage dependent loads, and so on.
Notably, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention(s) is/are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic or descriptive sense only and not for purposes of limitation.
This application claims priority under 35 U.S.C. 119 from the U.S. provisional patent application identified by App. No. 61/779,412, which was filed on 13 Mar. 2013 and which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5642270 | Green et al. | Jun 1997 | A |
5815824 | Saga et al. | Sep 1998 | A |
6621179 | Howard et al. | Sep 2003 | B1 |
6670721 | Lof | Dec 2003 | B2 |
6697951 | Sinha et al. | Feb 2004 | B1 |
7149605 | Chassin et al. | Dec 2006 | B2 |
7274975 | Miller | Sep 2007 | B2 |
7478070 | Fukui et al. | Jan 2009 | B2 |
7653443 | Flohr | Jan 2010 | B2 |
7747739 | Bridges et al. | Jun 2010 | B2 |
7778738 | Taft | Aug 2010 | B2 |
7844370 | Pollack et al. | Nov 2010 | B2 |
7949435 | Pollack et al. | May 2011 | B2 |
7969042 | Corum | Jun 2011 | B2 |
8364609 | Ozog et al. | Jan 2013 | B2 |
8796884 | Naiknaware | Aug 2014 | B2 |
9118216 | Corum | Aug 2015 | B2 |
9455577 | Bhageria | Sep 2016 | B2 |
20040158360 | Garland, II et al. | Aug 2004 | A1 |
20050027636 | Gilbert et al. | Feb 2005 | A1 |
20070282495 | Kempton et al. | Dec 2007 | A1 |
20080040479 | Bridge et al. | Feb 2008 | A1 |
20090063680 | Bridges et al. | Mar 2009 | A1 |
20090066287 | Pollack et al. | Mar 2009 | A1 |
20090174365 | Lowenthal et al. | Jul 2009 | A1 |
20090187445 | Barclay et al. | Jul 2009 | A1 |
20090200988 | Bridges et al. | Aug 2009 | A1 |
20090210357 | Pudar et al. | Aug 2009 | A1 |
20090313104 | Hafner et al. | Dec 2009 | A1 |
20100013436 | Lowenthal et al. | Jan 2010 | A1 |
20100017045 | Nesler et al. | Jan 2010 | A1 |
20100079004 | Keefe et al. | Apr 2010 | A1 |
20100088261 | Montalvo et al. | Apr 2010 | A1 |
20100114387 | Chassin et al. | May 2010 | A1 |
20100138065 | Taft | Jun 2010 | A1 |
20100138066 | Kong et al. | Jun 2010 | A1 |
20100179704 | Ozog | Jul 2010 | A1 |
20100179862 | Chassin et al. | Jul 2010 | A1 |
20100211340 | Lowenthal et al. | Aug 2010 | A1 |
20100211643 | Lowenthal et al. | Aug 2010 | A1 |
20100235004 | Thind et al. | Sep 2010 | A1 |
20100250014 | Taft | Sep 2010 | A1 |
20100277121 | Hall et al. | Nov 2010 | A1 |
20110004355 | Wang et al. | Jan 2011 | A1 |
20110025556 | Bridges et al. | Feb 2011 | A1 |
20110029148 | Yang et al. | Feb 2011 | A1 |
20110035073 | Ozog | Feb 2011 | A1 |
20110046806 | Nagel et al. | Feb 2011 | A1 |
20110196546 | Muller et al. | Aug 2011 | A1 |
20110231028 | Ozog | Sep 2011 | A1 |
20130085624 | Yang et al. | Apr 2013 | A1 |
20130173331 | Mohagheghi et al. | Jul 2013 | A1 |
20130184889 | Fan | Jul 2013 | A1 |
20140285154 | Mohagheghi et al. | Sep 2014 | A1 |
20140316598 | Yang et al. | Oct 2014 | A1 |
20150378387 | Chow | Dec 2015 | A1 |
20160099567 | Sun | Apr 2016 | A1 |
Number | Date | Country |
---|---|---|
101689277 | Mar 2010 | CN |
2008118395 | Oct 2008 | WO |
2011018703 | Feb 2011 | WO |
2012057846 | May 2012 | WO |
2012082173 | Jun 2012 | WO |
2013066501 | May 2013 | WO |
Entry |
---|
Schroder et al., Power and cost aware distributed load management, Apr. 2010, 4 pages. |
Hoyer et al., Proactive dynamic resource management in virtualized data centers, May 2010, 10 pages. |
Pellley et al., Power routing: dynamic power provisioning in the data center, Mar. 2010, 12 pages. |
Doostizadeh, M. et al., “Optimal Energy Management of a Retailer with Smart Metering and Plug-In Hybrid Electric Vehicle”, 10th International Conference on Environment and Electrical Engineering (EEEIC), Rome, Italy May 8-11, 2011, pp. 1-5. |
Fang, X. et al., “Smart Grid—The New and Improved Power Grid: A Survey”, from http://www.public.asu.edu/˜xfang5/survey—smartgrid—2011.pdf, 2011, pp. 1-38. |
Fang, X. et al., “Smart Grid—The New and Improved Power Grid: A Survey”, IEEE Communications Surveys & Tutorials, vol. 14, No. 4, Fourth Quarter 2012, pp. 944-979. |
Kempton, W. et al., “Vehicle-to-Grid Power Implementation: From Stabilizing the Grid to Supporting Large-Scale Renewable Energy”, Journal of Power Sources, vol. 144, 2005, pp. 280-294. |
Kleinberg, M. R. et al., “Improving Service Restoration of Power Distribution Systems Through Load Curtailment of In-Service Customers”, IEEE Transactions on Power Systems, Vo. 26, No. 3, Aug. 2011, pp. 1110-1117. |
Pang, C. et al., “PHEVs as Dynamically Configurable Dispersed Energy Storage for V2B Uses in the Smart Grid”, 7th Mediterranean Conference and Exhibition on Power Generation, Transmission, Distribution and Energy Conversion, Agia Napa, Cyprus (Paper No. MED10/174), Nov. 7-10, 2010, pp. 1-6. |
Viawan, F. A. et al., “Protection Scheme for Meshed Distribution Systems with High Penetration of Distributed Generation”, Power Systems Conference: Advanced Metering, Protection, Control, Communication, and Distributed Resources, Clemson, SC, USA, Mar. 14-17, 2006, pp. 99-104. |
Mohagheghi, S., et al., “Dispatching Mobile Energy Resources to Respond to Electric Power Grid Conditions”, U.S. Appl. No. 13/820,691, filed Mar. 4, 2013. |
Mohagheghi, S., et al., “Systems and Methods for Predicting Customer Compliance with Demand Response Requests”, U.S. Appl. No. 13/991,591, filed Jun. 4, 2013. |
Mohagheghi, S., et al., “Systems and Methods for Restoring Service Within Electrical Power Systems”, U.S. Appl. No. 14/354,267, filed Apr. 25, 2014. |
Author Unknown, “Demand Response: An Introduction”, Rocky Mountain Institute. Overview of programs, technologies, and lessons learned; Southwest Energy Efficiency Project; Apr. 30, 2006. pp. 1-43. Boulder Colorado. |
Yang, F., et al., “Systems and Methods for Integrating Demand Response with Service Restoration in an Electric Distribution System”, U.S. Appl. No. 13/595,053, filed Aug. 27, 2012. |
Number | Date | Country | |
---|---|---|---|
20140316598 A1 | Oct 2014 | US |
Number | Date | Country | |
---|---|---|---|
61779412 | Mar 2013 | US |