The present disclosure relates to a method, an apparatus, a system and a computer program for conserving energy. More particularly, the disclosure relates to a novel implementation of voltage conservation using advanced infrastructure and substation centralized voltage control.
Electricity is commonly generated at a power station by electromechanical generators, which are typically driven by heat engines fueled by chemical combustion or nuclear fission, or driven by kinetic energy flowing from water or wind. The electricity is generally supplied to end users through transmission grids as an alternating current signal. The transmission grids may include a network of power stations, transmission circuits, substations, and the like.
The generated electricity is typically stepped-up in voltage using, for example, generating step-up transformers, before supplying the electricity to a transmission system. Stepping up the voltage improves transmission efficiency by reducing the electrical current flowing in the transmission system conductors, while keeping the power transmitted nearly equal to the power input. The stepped-up voltage electricity is then transmitted through the transmission system to a distribution system, which distributes the electricity to end users. The distribution system may include a network that carries electricity from the transmission system and delivering it to end users. Typically, the network may include medium-voltage (for example, less than 69 kV) power lines, electrical substations, transformers, low-voltage (for example, less than 1 kV) distribution wiring, electric meters, and the like.
The following describe subject matter related to power generation or distribution: Power Distribution Planning Reference Book, Second Edition, H. Lee Willis, 2004; Estimating Methodology for a Large Regional Application of Conservation Voltage Reduction, J. G. De Steese, S. B. Merrick, B. W. Kennedy, IEEE Transactions on Power Systems, 1990; Implementation of Conservation Voltage Reduction at Commonwealth Edison, IEEE Transactions on Power Systems, D. Kirshner, 1990; and Conservation Voltage Reduction at Northeast Utilities, D. M. Lauria, IEEE, 1987. Further, U.S. Pat. No. 5,466,973, issued to Griffioen on Nov. 14, 1995, describes a method for regulating the voltage at which electric energy is supplied at the delivery points in a network for distributing electricity.
The disclosure provides a novel method, apparatus, system and computer program for conserving energy in electric systems. More particularly, the disclosure provides a novel solution to conserve energy by implementing voltage conservation using advanced infrastructure and substation centralized voltage control.
According to an aspect of the disclosure, a voltage control and conservation (VCC) system is provided for monitoring, controlling and conserving energy. The VCC system comprises: a substation configured to supply electrical power to a plurality of user locations; a smart meter located at one of the plurality of user locations and configured to generate smart meter data based on a measured component of electrical power received by the smart meter; and a voltage controller configured to generate an energy delivery parameter based on the smart meter data, wherein the substation is further configured to adjust a voltage set point value of the electrical power supplied to the plurality of user locations based on the energy delivery parameter, and wherein the smart meter is configured to operate in a report-by-exception mode and sua sponte send the smart meter data to the voltage controller when the measured component of electrical power is determined to be outside of a target component band.
The VCC system may further comprise a second smart meter located at a second one of the plurality of user locations and configured to generate second smart meter data based on a second measured component of electrical power received by the second smart meter, wherein the voltage controller is further configured to determine an average user voltage component by averaging the measured component of electrical power received by the smart meter and the second measured component of electrical power received by the second smart meter.
The VCC system may further comprise a collector configured to receive the smart meter data from the smart meter and generate collector data, wherein the voltage controller is further configured to generate the energy delivery parameter based on the collector data.
In the VCC system, the target component band may include a target voltage band, and the voltage controller may be configured to compare the measured component of electrical power received by the smart meter to the target voltage band and adjust the voltage set point based on a result of the comparison.
The substation may comprise: a load tap change transformer that adjusts the voltage set point value based on a load tap change coefficient; or a voltage regulator that adjusts the voltage set point value based on the energy delivery parameter. The substation may comprise a distribution bus that supplies the electrical power to the plurality of user locations, wherein an electrical power supply voltage component is measured on the distribution bus.
The voltage controller may comprise: a meter automation system server (MAS); a distribution management system (DMS); and a regional operation center (ROC). The voltage controller may be configured to adjust the voltage set point at a maximum rate of one load tap change step. The voltage controller may be configured to adjust the voltage set point based on the average user voltage component. The voltage controller may be configured to maintain the measured component of electrical power received by the smart meter within the target voltage band based on the result of the comparison. The voltage controller may be configured to select said smart meter for monitoring and create a connection to said smart meter after receiving the smart meter data sent sua sponte by said smart meter while operating in the report-by-exception mode. The voltage controller may be configured to de-select another smart meter that was previously selected to be monitored. The voltage controller may be configured to create a connection to said smart meter and terminate a connection to said another smart meter. The sua sponte smart meter data received from said smart meter may be representative of a low voltage limiting level in the system. The voltage controller may be configured to: store historical component data that includes at least one of an aggregated energy component data at a substation level, a voltage component data at a substation level, and a weather data; determine energy usage at each of the plurality of user locations; compare the historical component data to the determined energy usage; and determine energy savings attributable to the system based on the results of the comparison of the historical component data to the determined energy usage. The voltage controller may be configured to determine energy savings attributable to the system based on a linear regression that removes effects of weather, load growth, or economic effects. The voltage controller may be further configured to increase the voltage set point when either the electrical power supply voltage component or the average user voltage component falls below a target voltage band.
According to a further aspect of the disclosure, a VCC system is provided that comprises: a substation configured to supply electrical power to a plurality of user locations; a smart meter located at one of the plurality of user locations and configured to generate smart meter data based on a measured component of electrical power received by the smart meter; and a voltage controller configured to control a voltage set point of the electrical power supplied by the substation based on the smart meter data. The smart meter may be configured to operate in a report-by-exception mode, which comprises sua sponte sending the smart meter data to the voltage controller when the measured component of electrical power is determined to be outside of a target component band.
The VCC system may further comprise: a second smart meter located at a second one of the plurality of user locations, the second smart meter being configured to generate second smart meter data based on a second measured component of electrical power received by the second smart meter, wherein the voltage controller is further configured to determine an average user voltage component by averaging the measured component of electrical power received by the smart meter and the second measured component of electrical power received by the second smart meter.
The substation may comprise: a load tap change transformer that adjusts the voltage set point value based on a load tap change coefficient; or a voltage regulator that adjusts the voltage set point value based on the energy delivery parameter. The substation may comprise a distribution bus that supplies the electrical power to the plurality of user locations, wherein an electrical power supply voltage component is measured on the distribution bus.
The voltage controller may be configured to increase the voltage set point when either the electrical power supply voltage component or the average user voltage component falls below a target voltage band. The voltage controller may be configured to adjust the voltage set point at a maximum rate of one load tap change step. The voltage controller may be configured to compare the measured component of electrical power received by the smart meter to a target component band and adjust the voltage set point based on a result of the comparison. The voltage controller may be configured to adjust the voltage set point based on the average user voltage component. The target component band may include a target voltage band, and the voltage controller may be configured to maintain the measured component of electrical power received by the smart meter within the target voltage band based on the result of the comparison.
According to a still further aspect of the disclosure, a method is provided for controlling electrical power supplied to a plurality of user locations. The method comprises: receiving smart meter data from a first one of the plurality of user locations; and adjusting a voltage set point at a substation based on the smart meter data, wherein the smart meter data is sua sponte generated at the first one of the plurality of user locations when a measured component of electrical power that is supplied to the first one of the plurality of user locations is determined to be outside of a target component band.
The method may further comprise maintaining the average user voltage component within the target voltage band. The method may further comprise measuring a voltage component of the supplied electrical power on a distribution bus. The method may further comprise increasing the voltage set point when either the electrical power supply voltage component or an average user voltage component falls below the target component band. The method may further comprise: selecting said smart meter for monitoring; and creating a connection to said smart meter after receiving the smart meter data sent sua sponte by said smart meter while operating in a report-by-exception mode. The method may further comprise de-selecting another smart meter from a group of smart meters previously selected to be monitored. The method may further comprise terminating a connection to said another smart meter. The method may further comprise: storing historical component data that includes at least one of an aggregated energy component data at a substation level, a voltage component data at a substation level, and a weather data; determining energy usage at each of the plurality of user locations; comparing the historical component data to the determined energy usage; and determining energy savings attributable to the system based on the results of the comparison of the historical component data to the determined energy usage. The target component band may include a target voltage band. The method may further comprise: determining the target voltage band; and comparing an average user voltage component to the target voltage band.
The voltage set point may be adjusted based on the result of comparing the average user voltage component to the target voltage band. The sua sponte smart meter data received from the smart meter may be representative of a low voltage limiting level in the system.
According to a still further aspect of the disclosure, a computer readable medium is provided that tangibly embodies and includes a computer program for controlling electrical power supplied to a plurality of user locations. The computer program comprises a plurality of code sections, including: a receiving smart meter data code section that, when executed on a computer, causes receiving smart meter data from a first one of the plurality of user locations; and a voltage set point adjusting code section that, when executed on a computer, causes adjusting a voltage set point at a substation based on the smart meter data, wherein the smart meter data is sua sponte generated at the first one of the plurality of user locations when a measured component of electrical power that is supplied to the first one of the plurality of user locations is determined to be outside of a target component band.
The computer program may comprise an average user voltage component maintaining code section that, when executed on the computer, causes maintaining the average user voltage component within the target voltage band. The computer program may comprise a voltage component measuring code section that, when executed on the computer, causes a voltage component of the supplied electrical power to be measured on a distribution bus. The computer program may include a voltage set point increasing code section that, when executed on the computer, causes increasing the voltage set point when either the electrical power supply voltage component or an average user voltage component falls below the target component band. The computer program may comprise: a smart meter selection code section that, when executed on the computer, causes selecting said smart meter for monitoring; and a connection creation code section that, when executed on the computer, causes creating a connection to said smart meter after receiving the smart meter data sent sua sponte by said smart meter while operating in a report-by-exception mode. The computer program may comprise a smart meter de-selecting code section that, when executed on the computer, causes de-selecting another smart meter from a group of smart meters previously selected to be monitored. The computer program may comprise connection terminating code section that, when executed on the computer, causes terminating a connection to said another smart meter.
The computer program may comprise: a storing code section that, when executed on the computer, causes storing historical component data that includes at least one of an aggregated energy component data at a substation level, a voltage component data at a substation level, and a weather data; an energy usage determining code section that, when executed on the computer, causes determining energy usage at each of the plurality of user locations; a comparing code section that, when executed on the computer, causes comparing the historical component data to the determined energy usage; and an energy savings determination code section that, when executed on the computer, causes determining energy savings attributable to the system based on the results of the comparison of the historical component data to the determined energy usage. The target component band may include a target voltage band. The computer program may comprise: a target voltage band determining code section that, when executed on the computer, causes determining the target voltage band; and a comparing code section that, when executed on the computer, causes comparing an average user voltage component to the target voltage band. The voltage set point may be adjusted based on the result of comparing the average user voltage component to the target voltage band. The sua sponte smart meter data received from the smart meter may be representative of a low voltage limiting level in the system.
Additional features, advantages, and embodiments of the disclosure may be set forth or apparent from consideration of the detailed description and drawings. Moreover, it is to be understood that both the foregoing summary of the disclosure and the following detailed description are exemplary and intended to provide further explanation without limiting the scope of the disclosure as claimed.
The accompanying drawings, which are included to provide a further understanding of the disclosure, are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the detailed description serve to explain the principles of the disclosure. No attempt is made to show structural details of the disclosure in more detail than may be necessary for a fundamental understanding of the disclosure and the various ways in which it may be practiced. In the drawings:
The present disclosure is further described in the detailed description that follows.
The disclosure and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments and examples that are described and/or illustrated in the accompanying drawings and detailed in the following description. It should be noted that the features illustrated in the drawings are not necessarily drawn to scale, and features of one embodiment may be employed with other embodiments as the skilled artisan would recognize, even if not explicitly stated herein. Descriptions of well-known components and processing techniques may be omitted so as to not unnecessarily obscure the embodiments of the disclosure. The examples used herein are intended merely to facilitate an understanding of ways in which the disclosure may be practiced and to further enable those of skill in the art to practice the embodiments of the disclosure. Accordingly, the examples and embodiments herein should not be construed as limiting the scope of the disclosure. Moreover, it is noted that like reference numerals represent similar parts throughout the several views of the drawings.
A “computer”, as used in this disclosure, means any machine, device, circuit, component, or module, or any system of machines, devices, circuits, components, modules, or the like, which are capable of manipulating data according to one or more instructions, such as, for example, without limitation, a processor, a microprocessor, a central processing unit, a general purpose computer, a super computer, a personal computer, a laptop computer, a palmtop computer, a notebook computer, a desktop computer, a workstation computer, a server, or the like, or an array of processors, microprocessors, central processing units, general purpose computers, super computers, personal computers, laptop computers, palmtop computers, notebook computers, desktop computers, workstation computers, servers, or the like.
A “server”, as used in this disclosure, means any combination of software and/or hardware, including at least one application and/or at least one computer to perform services for connected clients as part of a client-server architecture. The at least one server application may include, but is not limited to, for example, an application program that can accept connections to service requests from clients by sending back responses to the clients. The server may be configured to run the at least one application, often under heavy workloads, unattended, for extended periods of time with minimal human direction. The server may include a plurality of computers configured, with the at least one application being divided among the computers depending upon the workload. For example, under light loading, the at least one application can run on a single computer. However, under heavy loading, multiple computers may be required to run the at least one application. The server, or any if its computers, may also be used as a workstation.
A “database”, as used in this disclosure, means any combination of software and/or hardware, including at least one application and/or at least one computer. The database may include a structured collection of records or data organized according to a database model, such as, for example, but not limited to at least one of a relational model, a hierarchical model, a network model or the like. The database may include a database management system application (DBMS) as is known in the art. The at least one application may include, but is not limited to, for example, an application program that can accept connections to service requests from clients by sending back responses to the clients. The database may be configured to run the at least one application, often under heavy workloads, unattended, for extended periods of time with minimal human direction.
A “communication link”, as used in this disclosure, means a wired and/or wireless medium that conveys data or information between at least two points. The wired or wireless medium may include, for example, a metallic conductor link, a radio frequency (RF) communication link, an Infrared (IR) communication link, an optical communication link, or the like, without limitation. The RF communication link may include, for example, WiFi, WiMAX, IEEE 802.11, DECT, 0G, 1G, 2G, 3G or 4G cellular standards, Bluetooth, and the like.
The terms “including”, “comprising” and variations thereof, as used in this disclosure, mean “including, but not limited to”, unless expressly specified otherwise.
The terms “a”, “an”, and “the”, as used in this disclosure, means “one or more”, unless expressly specified otherwise.
Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.
Although process steps, method steps, algorithms, or the like, may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described does not necessarily indicate a requirement that the steps be performed in that order. The steps of the processes, methods or algorithms described herein may be performed in any order practical. Further, some steps may be performed simultaneously.
When a single device or article is described herein, it will be readily apparent that more than one device or article may be used in place of a single device or article. Similarly, where more than one device or article is described herein, it will be readily apparent that a single device or article may be used in place of the more than one device or article. The functionality or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality or features.
A “computer-readable medium”, as used in this disclosure, means any medium that participates in providing data (for example, instructions) which may be read by a computer. Such a medium may take many forms, including non-volatile media, volatile media, and transmission media. Non-volatile media may include, for example, optical or magnetic disks and other persistent memory. Volatile media may include dynamic random access memory (DRAM). Transmission media may include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor. Transmission media may include or convey acoustic waves, light waves and electromagnetic emissions, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
Various forms of computer readable media may be involved in carrying sequences of instructions to a computer. For example, sequences of instruction (i) may be delivered from a RAM to a processor, (ii) may be carried over a wireless transmission medium, and/or (iii) may be formatted according to numerous formats, standards or protocols, including, for example, WiFi, WiMAX, IEEE 802.11, DECT, 0G, 1G, 2G, 3G or 4G cellular standards, Bluetooth, or the like.
According to one non-limiting example of the disclosure, a voltage control and conservation (VCC) system 200 is provided (shown in
The VCC system 200 may be integrated into, for example, an existing load curtailment plan of an electrical power supply system. The electrical power supply system may include an emergency voltage reduction plan, which may be activated when one or more predetermined events are triggered. The predetermined events may include, for example, an emergency, a short circuit, an overheating of electrical conductors, when the electrical power output from the transformer exceeds, for example, 80% of it power rating, or the like. The VCC system 200 is configured to yield to the load curtailment plan when the one or more predetermined events are triggered, allowing the load curtailment plan to be executed to reduce the voltage of the electrical power supplied to the plurality of users.
As seen in
Each of the users 150, 160 may include an Advanced Meter Infrastructure (AMI) 155, 169. The AMI 155, 169 may be coupled to a Regional Operations Center (ROC) 180. The ROC 180 may be coupled to the AMI 155, 169, by means of a plurality of communication links 175, 184, 188, a network 170 and/or a wireless communication system 190. The wireless communication system 190 may include, but is not limited to, for example, an RF transceiver, a satellite transceiver, and/or the like.
The network 170 may include, for example, at least one of the Internet, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a personal area network (PAN), a campus area network, a corporate area network, a global area network (GAN), a broadband area network (BAN), or the like, any of which may be configured to communicate data via a wireless and/or a wired communication medium. The network 170 may be configured to include a network topology such as, for example, a ring, a mesh, a line, a tree, a star, a bus, a full connection, or the like.
The AMI 155, 169 may include any one or more of the following: A smart meter; a network interface (for example, a WAN interface, or the like); firmware; software; hardware; and the like. The smart meter may be configured to determine any one or more of the following: kilo-Watt-hours (kWh) delivered; kWh received; kWh delivered plus kWh received; kWh delivered minus kWh received; interval data; demand data; and the like. If the smart meter is a three phase meter, then the low phase voltage may be used in the average calculation. If the meter is a single phase meter, then the single voltage component will be averaged.
The AMI 155, 169 may further include one or more collectors (shown in
The VCC system 200 minimizes power system losses, reduces user energy consumption and provides precise user voltage control. The VCC system 200 may include a closed loop process control application that uses user voltage data provided by the ED system 300 to control, for example, a voltage set point VSP on a distribution circuit (not shown) within the ER system 500. That is, the VCC system 200 may control the voltages VSupply(t) of the electrical power ESupply(t) supplied to the users 150, 160, by adjusting the voltage set point VSP of the distribution circuit in the ER system 500, which may include, for example, one or more load tap changing (LTC) transformers, one or more voltage regulators, or other voltage controlling equipment to maintain a tighter band of operation of the voltages VDelivered(t) of the electric power EDelivered(t) delivered to the users 150, 160, to lower power losses and facilitate efficient use of electrical power EDelivered(t) at the user locations 150 or 160.
The VCC system 200 controls or adjusts the voltage VSupply(t) of the electrical power ESupply(t) supplied from the EC system 500 based on smart meter data, which includes measured voltage VMeter(t) data from the users 150, 160 in the ED system 300. The VCC system 200 may adjust the voltage set point VSP at the substation or line regulator level in the ER system 500 by, for example, adjusting the LTC transformer (not shown), circuit regulators (not shown), or the like, to maintain the user voltages VMeter(t) in a target voltage band VBand-n, which may include a safe nominal operating range.
The VCC system 200 is configured to maintain the electrical power EDelivered(t) delivered to the users 150, 160 within one or more voltage bands VBand-n. For example, the energy may be delivered in two or more voltage bands VBand-n substantially simultaneously, where the two or more voltage bands may be substantially the same or different. The value VBand-n may be determined by the following expression [1]:
VBand-n=VSP+ΔV [1]
where VBand-n is a range of voltages, n is a positive integer greater than zero corresponding to the number of voltage bands VBand that may be handled at substantially the same time, VSP is the voltage set point value and ΔV is a voltage deviation range.
For example, the VCC system 200 may maintain the electrical power EDelivered(t) delivered to the users 150, 160 within a band VBand-1 equal to, for example, 111V to 129V for rural applications, where VSP is set to 120V and ΔV is set to a deviation of seven-and-one-half percent (+/−7.5%). Similarly, the VCC system 200 may maintain the electrical power EDelivered(t) delivered to the users 150, 160 within a band VBand-2 equal to, for example, 114V to 126V for urban applications, where VSP is set to 120V and ΔV is set to a deviation of five (+/−5%).
The VCC system 200 may maintain the electrical power EDelivered(t) delivered to the users 150, 160 at any voltage band VBand-n usable by the users 150, 160, by determining appropriate values for VSP and ΔV. In this regard, the values VSP and ΔV may be determined by the EC system 400 based on the energy usage information for users 150, 160, received from the ED system 300.
The EC system 400 may send the VSP and ΔV values to the ER system 500 as energy delivery parameters CED, which may also include the value VBand-n. The ER system 500 may then control and maintain the voltage VDelivered(t) of the electrical power EDelivered(t) delivered to the users 150, 160, within the voltage band VBand-n. The energy delivery parameters CED may further include, for example, load-tap-changer (LTC) control commands.
The VCC system 200 may further measure and validate energy savings by comparing energy usage by the users 150, 160 before a change in the voltage set point value VSP (or voltage band VBand-n) to the energy usage by the users 150, 160 after a change in the voltage set point value VSP (or voltage band VBand-n), according to principles of the disclosure. These measurements and validations may be used to determine the effect in overall energy savings by, for example, lowering the voltage VDelivered(t) of the electrical power EDelivered(t) delivered to the users 150, 160, and to determine optimal delivery voltage bands VBand-n for the energy power EDelivered(t) delivered to the users 150, 160.
The ER system 500 may communicate with the ED system 300 and/or EC system 400 by means of the network 170. The ER system 500 is coupled to the network 170 and the EC system 400 by means of communication links 510 and 430, respectively. The EC system 500 is also coupled to the ED system 300 by means of the power lines 340, which may include communication links.
The ER system 500 includes a substation 530 which receives the electrical power supply EIn(t) from, for example, the power generating station 110 (shown in
The substation 530 may include a transformer (not shown), such as, for example, a load tap change (LTC) transformer. In this regard, the substation 530 may further include an automatic tap changer mechanism (not shown), which is configured to automatically change the taps on the LTC transformer. The tap changer mechanism may change the taps on the LTC transformer either on-load (on-load tap changer, or OLTC) or off-load, or both. The tap changer mechanism may be motor driven and computer controlled. The substation 530 may also include a buck/boost transformer to adjust and maximize the power factor of the electrical power EDelivered(t) supplied to the users on power supply lines 340.
Additionally (or alternatively), the substation 530 may include one or more voltage regulators, or other voltage controlling equipment, as known by those having ordinary skill in the art, that may be controlled to maintain the output the voltage component VSupply(t) of the electrical power ESupply(t) at a predetermined voltage value or within a predetermined range of voltage values.
The substation 530 receives the energy delivery parameters CED from the EC system 400 on the communication link 430. The energy delivery parameters CED may include, for example, load tap coefficients when an LTC transformer is used to step-down the input voltage component VIn(t) of the electrical power EIn(t) to the voltage component VSupply(t) of the electrical power ESupply(t) supplied to the ED system 300. In this regard, the load tap coefficients may be used by the ER system 500 to keep the voltage component VSupply(t) on the low-voltage side of the LTC transformer at a predetermined voltage value or within a predetermined range of voltage values.
The LTC transformer may include, for example, seventeen or more steps (thirty-five or more available positions), each of which may be selected based on the received load tap coefficients. Each change in step may adjust the voltage component VSupply(t) on the low voltage side of the LTC transformer by as little as, for example, about five-thousandths (0.5%), or less.
Alternatively, the LTC transformer may include fewer than seventeen steps. Similarly, each change in step of the LTC transformer may adjust the voltage component VSupply(t) on the low voltage side of the LTC transformer by more than, for example, about five-thousandths (0.5%).
The voltage component VSupply(t) may be measured and monitored on the low voltage side of the LTC transformer by, for example, sampling or continuously measuring the voltage component VSupply(t) of the stepped-down electrical power ESupply(t) and storing the measured voltage component VSupply(t) values as a function of time t in a storage (not shown), such as, for example, a computer readable medium. The voltage component VSupply(t) may be monitored on, for example, a substation distribution bus, or the like. Further, the voltage component VSupply(t) may be measured at any point where measurements could be made for the transmission or distribution systems in the ER system 500.
Similarly, the voltage component VIn(t) of the electrical power EIn(t) input to the high voltage side of the LTC transformer may be measured and monitored. Further, the current component ISupply(t) of the stepped-down electrical power ESupply(t) and the current component IIn (t) of the electrical power EIn(t) may also be measured and monitored. In this regard, a phase difference φIn(t) between the voltage VIn(t) and current IIn(t) components of the electrical power EIn(t) may be determined and monitored. Similarly, a phase difference φSupply(t) between the voltage VSupply(t) and current ISupply(t) components of the electrical energy supply ESupply(t) may be determined and monitored.
The ER system 500 may provide electrical energy supply status information to the EC system 400 on the communication links 430 or 510. The electrical energy supply information may include the monitored voltage component VSupply(t). The electrical energy supply information may further include the voltage component VIn(t), current components IIn(t), ISupply(t), and/or phase difference values φIn(t), φSupply(t), as a function of time t. The electrical energy supply status information may also include, for example, the load rating of the LTC transformer.
The electrical energy supply status information may be provided to the EC system 400 at periodic intervals of time, such as, for example, every second, 5 sec., 10 sec., 30 sec., 60 sec., 120 sec., 600 sec., or any other value within the scope and spirit of the disclosure, as determined by one having ordinary skill in the art. The periodic intervals of time may be set by the EC system 400 or the ER system 500. Alternatively, the electrical energy supply status information may be provided to the EC system 400 or ER system 500 intermittently.
Further, the electrical energy supply status information may be forwarded to the EC system 400 in response to a request by the EC system 400, or when a predetermined event is detected. The predetermined event may include, for example, when the voltage component VSupply(t) changes by an amount greater (or less) than a defined threshold value VSupplyThreshold (for example, 130V) over a predetermined interval of time, a temperature of one or more components in the ER system 500 exceeds a defined temperature threshold, or the like.
The ED system 300 includes a plurality of smart meters 330. The ED system 300 may further include at least one collector 350, which is optional. The ED system 300 may be coupled to the network 170 by means of a communication link 310. The collector 350 may be coupled to the plurality of smart meters 330 by means of a communication link 320. The smart meters 330 may be coupled to the ER system 500 by means of one or more power supply lines 340, which may also include communication links.
Each smart meter 330 is configured to measure, store and report energy usage data by the associated users 150, 160 (shown in
The smart meters 330 may average the measured voltage VMeter(t) and/or IMeter(t) values over predetermined time intervals (for example, 5 min., 10 min., 30 min., or more). The smart meters 330 may store the measured electrical power usage EMeter(t), including the measured voltage component VMeter (t) and/or current component IMeter(t) as smart meter data in a local (or remote) storage (not shown), such as, for example, a computer readable medium.
Each smart meter 330 is also capable of operating in a “report-by-exception” mode for any voltage VMeter(t), current IMeter(t), or energy usage EMeter(t) that falls outside of a target component band. The target component band may include, a target voltage band, a target current band, or a target energy usage band. In the “report-by-exception” mode, the smart meter 330 may sua sponte initiate communication and send smart meter data to the EC system 400. The “report-by-exception” mode may be used to reconfigure the smart meters 330 used to represent, for example, the lowest voltages on the circuit as required by changing system conditions.
The smart meter data may be periodically provided to the collector 350 by means of the communication links 320. Additionally, the smart meters 330 may provide the smart meter data in response to a smart meter data request signal received from the collector 350 on the communication links 320.
Alternatively (or additionally), the smart meter data may be periodically provided directly to the EC system 400 (for example, the MAS 460) from the plurality of smart meters, by means of, for example, communication links 320, 410 and network 170. In this regard, the collector 350 may be bypassed, or eliminated from the ED system 300. Furthermore, the smart meters 330 may provide the smart meter data directly to the EC system 400 in response to a smart meter data request signal received from the EC system 400. In the absence of the collector 350, the EC system (for example, the MAS 460) may carry out the functionality of the collector 350 described herein.
The request signal may include, for example, a query (or read) signal and a smart meter identification signal that identifies the particular smart meter 330 from which smart meter data is sought. The smart meter data may include the following information for each smart meter 130, including, for example, kilo-Watt-hours (kWh) delivered data, kWh received data, kWh delivered plus kWh received data, kWh delivered minus kWh received data, voltage level data, current level data, phase angle between voltage and current, kVar data, time interval data, demand data, and the like.
Additionally, the smart meters 330 may send the smart meter data to the meter automation system server MAS 460. The smart meter data may be sent to the MAS 460 periodically according to a predetermined schedule or upon request from the MAS 460.
The collector 350 is configured to receive the smart meter data from each of the plurality of smart meters 330 via the communication links 320. The collector 350 stores the received smart meter data in a local storage (not shown), such as, for example, a computer readable medium. The collector 350 compiles the received smart meter data into a collector data. In this regard, the received smart meter data may be aggregated into the collector data based on, for example, a geographic zone in which the smart meters 330 are located, a particular time band (or range) during which the smart meter data was collected, a subset of smart meters 330 identified in a collector control signal, and the like. In compiling the received smart meter data, the collector 350 may average the voltage component VMeter(t) values received in the smart meter data from all (or a subset of all) of the smart meters 330.
The EC system 400 is able to select or alter a subset of all of the smart meters 330 to be monitored for predetermined time intervals, which may include for example 15 minute intervals. It is noted that the predetermined time intervals may be shorter or longer than 15 minutes. The subset of all of the smart meters 330 is selectable and can be altered by the EC system 400 as needed to maintain minimum level control of the voltage VSupply(t) supplied to the smart meters 330.
The collector 350 may also average the electrical power EMeter(t) values received in the smart meter data from all (or a subset of all) of the smart meters 330. The compiled collector data may be provided by the collector 350 to the EC system 400 by means of the communication link 310 and network 170. For example, the collector 350 may send the compiled collector data to the MAS 460 (or ROC 490) in the EC system 400.
The collector 350 is configured to receive collector control signals over the network 170 and communication link 310 from the EC system 400. Based on the received collector control signals, the collector 350 is further configured to select particular ones of the plurality of smart meters 330 and query the meters for smart meter data by sending a smart meter data request signal to the selected smart meters 330. The collector 350 may then collect the smart meter data that it receives from the selected smart meters 330 in response to the queries. The selectable smart meters 330 may include any one or more of the plurality of smart meters 330. The collector control signals may include, for example, an identification of the smart meters 330 to be queried (or read), time(s) at which the identified smart meters 330 are to measure the VMeter(t), IMeter(t), EMeter(t) and/or φMeter(t) (φMeter(t) is the phase difference between the voltage VMeter(t) and current IMeter(t) components of the electrical power EMeter (t) measured at the identified smart meter 330), energy usage information since the last reading from the identified smart meter 330, and the like. The collector 350 may then compile and send the compiled collector data to the MAS 460 (and/or ROC 490) in the EC system 400.
The EC system 400 may communicate with the ED system 300 and/or ER system 500 by means of the network 170. The EC system 400 is coupled to the network 170 by means of one or more communication links 410. The EC system 400 may also communicate directly with the ER system 500 by means of a communication link 430.
The EC system 400 includes the MAS 460, a database (DB) 470, a distribution management system (DMS) 480, and a regional operation center (ROC) 490. The ROC 490 may include a computer (ROC computer) 495, a server (not shown) and a database (not shown). The MAS 460 may be coupled to the DB 470 and DMS 480 by means of communication links 420 and 440, respectively. The DMS 480 may be coupled to the ROC 490 and ER SYSTEM 500 by means of the communication link 430. The database 470 may be located at the same location as (for example, proximate to, or within) the MAS 460, or at a remote location that may be accessible via, for example, the network 170.
The EC system 400 is configured to de-select, from the subset of monitored smart meters 330, a smart meter 330 that the EC system 400 previously selected to monitor, and select the smart meter 330 that is outside of the subset of monitored smart meters 330, but which is operating in the report-by-exception mode. The EC system 400 may carry out this change after receiving the sua sponte smart meter data from the non-selected smart meter 330. In this regard, the EC system 400 may remove or terminate a connection to the de-selected smart meter 330 and create a new connection to the newly selected smart meter 330 operating in the report-by-exception mode. The EC system 400 is further configured to select any one or more of the plurality of smart meters 330 from which it receives smart meter data comprising, for example, the lowest measured voltage component VMeter(t), and generate an energy delivery parameter CED based on the smart meter data received from the smart meter(s) 330 that provide the lowest measured voltage component VMeter(t).
The MAS 460 may include a computer (not shown) that is configured to receive the collector data from the collector 350, which includes smart meter data collected from a selected subset (or all) of the smart meters 330. The MAS 460 is further configured to retrieve and forward smart meter data to the ROC 490 in response to queries received from the ROC 490. The MAS 460 may store the collector data, including smart meter data in a local storage and/or in the DB 470.
The DMS 480 may include a computer that is configured to receive the electrical energy supply status information from the substation 530. The DMS 480 is further configured to retrieve and forward measured voltage component VMeter(t) values and electrical power EMeter(t) values in response to queries received from the ROC 490. The DMS 480 may be further configured to retrieve and forward measured current component IMeter(t) values in response to queries received from the ROC 490. The DMS 480 also may be further configured to retrieve all “report-by-exception” voltages VMeter(t) from the smart meters 330 operating in the “report-by-exception” mode and designate the voltages VMeter(t) as one of the control points to be continuously read at predetermined times (for example, every 15 minutes, or less (or more), or at varying times). The “report-by-exception voltages VMeter(t) may be used to control the EC 500 set points.
The DB 470 may include a plurality of relational databases (not shown). The DB 470 includes a large number of records that include historical data for each smart meter 330, each collector 350, each substation 530, and the geographic area(s) (including latitude, longitude, and altitude) where the smart meters 330, collectors 350, and substations 530 are located.
For instance, the DB 470 may include any one or more of the following information for each smart meter 330, including: a geographic location (including latitude, longitude, and altitude); a smart meter identification number; an account number; an account name; a billing address; a telephone number; a smart meter type, including model and serial number; a date when the smart meter was first placed into use; a time stamp of when the smart meter was last read (or queried); the smart meter data received at the time of the last reading; a schedule of when the smart meter is to be read (or queried), including the types of information that are to be read; and the like.
The historical smart meter data may include, for example, the electrical power EMeter(t) used by the particular smart meter 330, as a function of time. Time t may be measured in, for example, discrete intervals at which the electrical power EMeter magnitude (kWh) of the received electrical power EMeter(t) is measured or determined at the smart meter 330. The historical smart meter data includes a measured voltage component VMeter(t) of the electrical energy EMeter(t) received at the smart meter 330. The historical smart meter data may further include a measured current component IMeter(t) and/or phase difference φMeter(t) of the electrical power EMeter(t) received at smart meter 330.
As noted earlier, the voltage component VMeter(t) may be measured at a sampling period of, for example, every five seconds, ten seconds, thirty seconds, one minute, five minutes, ten minutes, fifteen minutes, or the like. The current component IMeter(t) and/or the received electrical power EMeter(t) values may also be measured at substantially the same times as the voltage component VMeter(t).
Given the low cost of memory, the DB 470 may include historical data from the very beginning of when the smart meter data was first collected from the smart meters 330 through to the most recent smart meter data received from the smart meter 330s.
The DB 470 may include a time value associated with each measured voltage component VMeter(t), current component IMeter(t), phase component φMeter(t) and/or electrical power EMeter(T), which may include a timestamp value generated at the smart meter 330. The timestamp value may include, for example, a year, a month, a day, an hour, a minute, a second, and a fraction of a second. Alternatively, the timestamp may be a coded value which may be decoded to determine a year, a month, a day, an hour, a minute, a second, and a fraction of a second, using, for example, a look up table. The ROC 490 and/or smart meters 330 may be configured to receive, for example, a WWVB atomic clock signal transmitted by the U.S. National Institute of Standards and Technology (NIST), or the like and synchronize its internal clock (not shown) to the WWVB atomic clock signal.
The historical data in the DB 470 may further include historical collector data associated with each collector 350. The historical collector data may include any one or more of the following information, including, for example: the particular smart meters 330 associated with each collector 350; the geographic location (including latitude, longitude, and altitude) of each collector 350; a collector type, including model and serial number; a date when the collector 350 was first placed into use; a time stamp of when collector data was last received from the collector 350; the collector data that was received; a schedule of when the collector 350 is expected to send collector data, including the types of information that are to be sent; and the like.
The historical collector data may further include, for example, an external temperature value TCollector(t) measured outside of each collector 350 at time t. The historical collector data may further include, for example, any one or more of the following for each collector 350: an atmospheric pressure value PCollector(t) measured proximate the collector 350 at time t; a humidity value HCollector(t) measured proximate the collector 350 at time t; a wind vector value WCollector(t) measured proximate the collector 350 at time t, including direction and magnitude of the measured wind; a solar irradiant value LCollector(t) (kW/m2) measured proximate the collector 350 at time t; and the like.
The historical data in the DB 470 may further include historical substation data associated with each substation 530. The historical substation data may include any one or more of the following information, including, for example: the identifications of the particular smart meters 330 supplied with electrical energy ESupply(t) by the substation 530; the geographic location (including latitude, longitude, and altitude) of the substation 530; the number of distribution circuits; the number of transformers; a transformer type of each transformer, including model, serial number and maximum Megavolt Ampere (MVA) rating; the number of voltage regulators; a voltage regulator type of each voltage regulator, including model and serial number; a time stamp of when substation data was last received from the substation 530; the substation data that was received; a schedule of when the substation 530 is expected to provide electrical energy supply status information, including the types of information that are to be provided; and the like.
The historical substation data may include, for example, the electrical power ESupply(t) supplied to each particular smart meter 330, where ESupply(t) is measured or determined at the output of the substation 530. The historical substation data includes a measured voltage component VSupply(t) of the supplied electrical power ESupply(t), which may be measured, for example, on the distribution bus (not shown) from the transformer. The historical substation data may further include a measured current component ISupply(t) of the supplied electrical power ESupply(t). As noted earlier, the voltage component VSupply(t), the current component ISupply(t), and/or the electrical power ESupply(t) may be measured at a sampling period of, for example, every five seconds, ten seconds, thirty seconds, a minute, five minutes, ten minutes, or the like. The historical substation data may further include a phase difference value φSupply(t) between the voltage VSupply(t) and current ISupply(t) signals of the electrical power ESupply(t), which may be used to determine the power factor of the electrical power ESupply(t) supplied to the smart meters 330.
The historical substation data may further include, for example, the electrical power EIn(t) received on the line 520 at the input of the substation 530, where the electrical power EIn(t) is measured or determined at the input of the substation 530. The historical substation data may include a measured voltage component VIn(t) of the received electrical power EIn(t), which may be measured, for example, at the input of the transformer. The historical substation data may further include a measured current component IIn(t) of the received electrical power EIn(t). As noted earlier, the voltage component VIn(t), the current component IIn(t), and/or the electrical power EIn(t) may be measured at a sampling period of, for example, every five seconds, ten seconds, thirty seconds, a minute, five minutes, ten minutes, or the like. The historical substation data may further include a phase difference φIn(t) between the voltage component VIn(t) and current component IIn(t) of the electrical power EIn(t). The power factor of the electrical power EIn(t) may be determined based on the phase difference φIn(t).
According to an aspect of the disclosure, the EC system 400 may save aggregated kW data at the substation level, voltage data at the substation level, and weather data to compare to energy usage per smart meter 330 to determine the energy savings from the VCC system 200, and using linear regression to remove the affects of weather, load growth, economic effects, and the like, from the calculation.
In the VCC system 200, control may be initiated from, for example, the ROC computer 495. In this regard, a control screen 305 may be displayed on the ROC computer 495, as shown, for example, in
For system security, the substation 530 may be controlled through the direct communication link 430 from the ROC 490 and/or DMS 480.
Furthermore, an operator can initiate a voltage control program on the ROC computer 490, overriding the controls, if necessary, and monitoring a time it takes to read the user voltages VMeter(t) being used for control of, for example, the substation LTC transformer (not shown) in the ER system 500.
Referring to
The voltage component VSupply(t) and electrical power ESupply(t) values measured at substation 530 may be retrieved from the DMS 480 (Step 620). The current, or most recent voltage component VMeter(t) and electrical power EMeter(t) values received and measured at the selected subset of the plurality of smart meters 330 may be retrieved from the MAS 460 (or a local storage, such as, for example, a computer readable medium, in the ROC 490) (Step 630). The current, or most recent voltage component VMeter(t) and electrical power EMeter(t) values may have been measured by the select subset of smart meters 330 and forwarded to the MAS 460 via the collector 350, as described above.
Alternatively, the current, or most recent voltage component VMeter(t) and electrical power EMeter(t) values may have been retrieved directly from the collector 350 or the selected subset of the smart meters 330 (Step 630).
The current, or most recent voltage component VMeter(t) and electrical power subset EMeter(t) values may have been measured at the selected et of smart meters 330 in response to a smart meter data request signal received from the collector 350. The collector 350 may have sent the smart meter data request signal in response to a collector control signal received from the MAS 460 (or the ROC 490).
The current, or most recent voltage component VMeter(t) values may be averaged for the selected number of smart meters 330 to determine an average voltage component VMeter-Avg(t) value for the electrical power delivered to the selected smart meters 330. This average voltage component VMeter-Avg(t) value may then be compared to the target voltage band VBand-n to determine whether the average voltage component VMeter-Avg(t) value is within the target voltage band VBand-n (Step 650).
If the average voltage component VMeter-Avg(t) value is outside of the target voltage band VBand-n, then a determination is made to change the set point voltage VSP of the voltage component VSupply(t) output by the substation 530 (YES at Step 660). Energy delivery parameters CED may be generated and sent to the substation 530 to adjust the set point voltage VSP of the output voltage component VSupply(t) (Step 670). A new voltage set point voltage VSP value may be calculated by the DMS 480. Where a LTC transformer is used, the voltage set point voltage VSP value may be increased (or decreased) at a maximum rate of, for example, one volt about every, for example, fifteen minutes (Note: for example, a 0.625% voltage change per step in a LTC transformer). It is noted that the voltage set point voltage VSP value may be increased (or decreased) at a rate of, for example, a fraction of a volt, or multiple volts at one time. The energy delivery parameters CED may include, for example, load tap coefficients. The set point voltage VSP may be adjusted up (or down) by, for example, a fraction of a Volt (e.g., 0.01V, 0.02V, . . . , 0.1V, 0.2V, . . . , 1.0V, . . . , or the like).
Furthermore, when either the VSupply(t) or the VMeter-Avg(t) voltage components reach or fall below a predetermined minimum voltage range (for example, about 118V to about 119V), the set point voltage VSP may be increased. When the voltage set point VSP is raised, the VSupply(t) or the VMeter-Avg(t) voltage components should remain in a higher voltage band for, e.g., twenty-four hours before the voltage set point VSP may be lowered again.
If the average voltage component VMeter-Avg(t) value is within the target voltage band VBand-n, then a determination is made not to change the set point voltage VSP of the voltage component VSupply(t) output by the substation 530 (NO at Step 660), and a determination may be made whether to end the VCC process (Step 680). If a determination is made not to end the VCC process (NO at Step 680), the VCC process repeats.
According to an aspect of the disclosure, a computer readable medium is provided containing a computer program, which when executed on, for example, the ROC 495 (shown in
Referring to
A schedule may be generated to obtain smart meter data from the selected subset of smart meters 330 (Step 720). The schedule may include, for example, measuring the received voltage component VMeter(t) and electrical power EMeter(t) every, for example, five seconds, ten seconds, thirty seconds, one minute, five minutes, ten minutes, fifteen minutes, or the like, at the selected subset of smart meters 330. The generated schedule is provided to the collector 350 that is associated with the selected subset of smart meters 330 as part of a collector control signal (Step 730). The collector control signal may be generated at, for example, the ROC 490 or MAS 460 and sent to the collector 350 via communication link 410 and network 170.
The collector 350, based on the provided collector control signal or a previously received schedule, may send a smart meter data request signal to the selected subset of smart meters 330 via communication links 320. The smart meter data request signal may include, for example, the schedule provided in the collector control signal. The schedule may be stored at the selected subset of smart meters 330 and used by the smart meters 330 to control monitoring and reporting of the received voltage component VMeter(t) and electrical power EMeter(t) for the associated user 150 (160).
The collector 350 receives the reported smart meter data, including the voltage component VMeter(t) and electrical energy EMeter(t) for the associated user 150 (160), from the selected subset of smart meters 330 via communication links 320. The collector 350 compiles the received smart meter data, generating collector data and sending the collector data to the EC system 400.
The collector data is received from the collector 350 (Step 740) and stored locally (or remotely) in the EC system 400 (Step 750). In particular, the received collector data is stored locally in, for example, the ROC 490, the MAS 460 and/or the DB 470.
According to an aspect of the disclosure, a computer readable medium is provided containing a computer program, which when executed on, for example, the ROC 495 (shown in
Referring to
According to an aspect of the disclosure, a computer readable medium is provided containing a computer program, which when executed on, for example, the ROC 495 (shown in
As seen in
The waveforms 810 and 820 prior to time to show an example of voltage fluctuations in the electrical power ESupply(t) supplied by the substation 530 and electrical power EMeter(t) received by the users 150, 160, without the VCC system 200. The waveforms 810 and 820 after time t0 show an example of voltage fluctuations in the electrical power ESupply(t) supplied by the substation 530 and electrical power Emeter(t) received by the users 150, 160, with the VCC system 200. As seen in
Energy savings 807 (shown in
Comparing the data in
As shown in
The voltage VSupply(t) and electrical power ESupply(t) data shown in
ETotal/Customer=−4.54−0.260Dseason−0.213DType+0.0579H+0.0691VAvg+0.00524DMonth [2]
where: ETotal is a total power for a twenty-four hour period per customer for a particular day; DType is a day type (such as, for example, a weekend, a weekday, or a holiday) of the particular day; DSeason is one of four seasons corresponding to the particular day in the calendar year; DMonth is the particular day in the month; H is a Heating Degree Day level for the particular day; and V is the VAvg average voltage supplied per customer for the particular day.
The data shown in the example of
The historical data may be adjusted to match the heating degree day level for the measurements taken after the voltage control and/or conservation is carried out by the VCC system 200. For example, referring to
This process may be repeated for all measurements taken after the voltage conservation is turned on and compared to all similar days in the historical data taken for the matching season and other weather conditions. This may produce, for example, one-hundred-fifteen data points from, for example, 115 days of operation matched with all of the historical matching data. The resulting statistical analysis of this data is shown in
The normality of the data may be validated using the Anderson-Darling Normality test. In the case of the example of
ETotal=(−801+0.069Y+0.0722DType+0.094DYear+0.0138DMonth+0.126Tmax+0.131Tmin+9.84Tavg+10.1H−10.3C+0.251Pstd)−(0.102Tmax-d−0.101Tmin-d+0.892Tavg-d+0.693Hd−0.452Cd−0.025PR+0.967ETotalPrevious)
where: ETotal is a total power for a twenty-four hour period for a particular day; Y is a calendar year of the particular day; DType is a day type (such as, for example, a weekend, a weekday, or a holiday) of the particular day; DYear is the particular day in the calendar year; DMonth is the particular day in the month; Tmax is a maximum temperature for the particular day; Tmin is minimum temperature for the particular day; Tavg is the average temperature for the particular day; H is a Heating Degree Day level for the particular day; C is a Cooling Degree Day level; P is a barometric pressure for the particular day; Tmax-d is a maximum temperature for a closest comparison day to the particular day; Tmin-d is minimum temperature for the closest comparison day to the particular day; Tavg-d is the average temperature for the closest comparison day to the particular day; Hd is a Heating Degree Day level for the closest comparison day to the particular day; Cd is a Cooling Degree Day level for the closest comparison day to the particular day; PR is a Barometric pressure for the closest comparison day to the particular day; and ETotalPrevious is the total average hourly usage in MW on the closest comparison day to the particular day. The data shown in the example of
The historical data may be adjusted to match the heating degree day level for the measurements taken after the voltage control and/or conservation is carried out by the VCC system 200. For example, referring to
This process may be repeated for all measurements taken after the voltage conservation is turned on and compared to all similar days in the historical data taken for the matching season and other weather conditions. This may produce, for example, seventy-one data points from, for example, thirty days of operation matched with all of the historical matching data. The resulting statistical analysis of this data is shown in
The normality of the data may be validated using the Anderson-Darling Normality test. In the case of the example of
While the disclosure has been described in terms of exemplary embodiments, those skilled in the art will recognize that the disclosure can be practiced with modifications in the spirit and scope of the appended claims. These examples are merely illustrative and are not meant to be an exhaustive list of all possible designs, embodiments, applications or modifications of the disclosure.
This application is a continuation of application Ser. No. 12/774,507, filed May 5, 2010, and claims priority and the benefit thereof from U.S. Provisional Application No. 61/176,398, filed on May 7, 2009 and entitled VOLTAGE CONSERVATION USING ADVANCED METERING INFRASTRUCTURE AND SUBSTATION CENTRALIZED VOLTAGE CONTROL, the entirety of which are herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3900842 | Calabro et al. | Aug 1975 | A |
3970898 | Baumann et al. | Jul 1976 | A |
4054830 | Harrel | Oct 1977 | A |
4234904 | Fahlesson | Nov 1980 | A |
4291377 | Schneider et al. | Sep 1981 | A |
4302750 | Wadhwani et al. | Nov 1981 | A |
4307380 | Gander | Dec 1981 | A |
4309655 | Lienhard et al. | Jan 1982 | A |
4310829 | Rey | Jan 1982 | A |
4356553 | Steinle et al. | Oct 1982 | A |
4361872 | Spalti | Nov 1982 | A |
4365302 | Elms | Dec 1982 | A |
4434400 | Halder | Feb 1984 | A |
4513273 | Friedl | Apr 1985 | A |
4525668 | Lienhard et al. | Jun 1985 | A |
4540931 | Hahn | Sep 1985 | A |
4630220 | Peckinpaugh | Dec 1986 | A |
4686630 | Marsland et al. | Aug 1987 | A |
4689752 | Fernandes et al. | Aug 1987 | A |
4695737 | Rabon et al. | Sep 1987 | A |
4791520 | Stegmuller | Dec 1988 | A |
4843310 | Friedl | Jun 1989 | A |
4853620 | Halder et al. | Aug 1989 | A |
4881027 | Joder et al. | Nov 1989 | A |
4887028 | Voisine et al. | Dec 1989 | A |
4894610 | Friedl | Jan 1990 | A |
4896106 | Voisine et al. | Jan 1990 | A |
5028862 | Roth | Jul 1991 | A |
5032785 | Mathis et al. | Jul 1991 | A |
5055766 | McDermott et al. | Oct 1991 | A |
5066906 | Moore | Nov 1991 | A |
5124624 | De Vries et al. | Jun 1992 | A |
5128855 | Hilber et al. | Jul 1992 | A |
5136233 | Klinkenberg et al. | Aug 1992 | A |
5231347 | Voisine et al. | Jul 1993 | A |
5249150 | Gruber et al. | Sep 1993 | A |
5262715 | King et al. | Nov 1993 | A |
5270639 | Moore | Dec 1993 | A |
5272462 | Teyssandier et al. | Dec 1993 | A |
5298857 | Voisien et al. | Mar 1994 | A |
5343143 | Voisien et al. | Aug 1994 | A |
5432507 | Mussino et al. | Jul 1995 | A |
5466973 | Griffioen | Nov 1995 | A |
5475867 | Blum | Dec 1995 | A |
5511108 | Severt et al. | Apr 1996 | A |
5552696 | Trainor et al. | Sep 1996 | A |
5602750 | Severt et al. | Feb 1997 | A |
5604414 | Milligan et al. | Feb 1997 | A |
5610394 | Lee et al. | Mar 1997 | A |
5627759 | Bearden et al. | May 1997 | A |
5673252 | Johnson et al. | Sep 1997 | A |
5736848 | De Vries et al. | Apr 1998 | A |
5903548 | Delamater | May 1999 | A |
5918380 | Schleich et al. | Jul 1999 | A |
5963146 | Johnson et al. | Oct 1999 | A |
6006212 | Schleich et al. | Dec 1999 | A |
6026355 | Rahman et al. | Feb 2000 | A |
6172616 | Johnson et al. | Jan 2001 | B1 |
6218995 | Higgins et al. | Apr 2001 | B1 |
6219655 | Schleich et al. | Apr 2001 | B1 |
6333975 | Brunn et al. | Dec 2001 | B1 |
6373236 | Lemay, Jr. et al. | Apr 2002 | B1 |
6373399 | Johnson et al. | Apr 2002 | B1 |
6417729 | Lemay et al. | Jul 2002 | B1 |
6555997 | De Vries et al. | Apr 2003 | B1 |
6590376 | Bammert et al. | Jul 2003 | B1 |
6618684 | Beroset et al. | Sep 2003 | B1 |
6628207 | Hemminger et al. | Sep 2003 | B1 |
6633823 | Bartone et al. | Oct 2003 | B2 |
6636893 | Fong | Oct 2003 | B1 |
6650249 | Meyer et al. | Nov 2003 | B2 |
6653945 | Johnson et al. | Nov 2003 | B2 |
6667692 | Griffin | Dec 2003 | B2 |
6684245 | Shuey et al. | Jan 2004 | B1 |
6700902 | Meyer | Mar 2004 | B1 |
6703823 | Hemminger et al. | Mar 2004 | B1 |
6738693 | Anderson | May 2004 | B2 |
6747446 | Voisine et al. | Jun 2004 | B1 |
6747981 | Ardalan et al. | Jun 2004 | B2 |
6756914 | Fitzgerald et al. | Jun 2004 | B1 |
6757628 | Anderson et al. | Jun 2004 | B1 |
6762598 | Hemminger et al. | Jul 2004 | B1 |
6773652 | Loy et al. | Aug 2004 | B2 |
6778099 | Meyer et al. | Aug 2004 | B1 |
6798353 | Seal et al. | Sep 2004 | B2 |
6815942 | Randall et al. | Nov 2004 | B2 |
6816538 | Shuey et al. | Nov 2004 | B2 |
6832135 | Ying | Dec 2004 | B2 |
6832169 | Wakida et al. | Dec 2004 | B2 |
6838867 | Loy | Jan 2005 | B2 |
6847201 | De Vries et al. | Jan 2005 | B2 |
6859186 | Lizalek et al. | Feb 2005 | B2 |
6859742 | Randall et al. | Feb 2005 | B2 |
6867707 | Kelley et al. | Mar 2005 | B1 |
6868293 | Schurr et al. | Mar 2005 | B1 |
6873144 | Slater et al. | Mar 2005 | B2 |
6882137 | Voisine | Apr 2005 | B1 |
6885185 | Makinson et al. | Apr 2005 | B1 |
6888876 | Mason et al. | May 2005 | B1 |
6892144 | Slater et al. | May 2005 | B2 |
6900737 | Ardalan et al. | May 2005 | B1 |
6906507 | Briese et al. | Jun 2005 | B2 |
6906637 | Martin | Jun 2005 | B2 |
6940268 | Hemminger et al. | Sep 2005 | B2 |
6940711 | Heuell et al. | Sep 2005 | B2 |
6947854 | Swarztrauber et al. | Sep 2005 | B2 |
6954061 | Hemminger et al. | Oct 2005 | B2 |
6982390 | Heuell et al. | Jan 2006 | B2 |
6988043 | Randall | Jan 2006 | B1 |
6989667 | Loy | Jan 2006 | B2 |
6995685 | Randall | Feb 2006 | B2 |
7005844 | De Vries et al. | Feb 2006 | B2 |
7009379 | Ramirez | Mar 2006 | B2 |
7020178 | Mason et al. | Mar 2006 | B2 |
7043381 | Wakida et al. | May 2006 | B2 |
7046682 | Carpenter et al. | May 2006 | B2 |
7064679 | Ehrke et al. | Jun 2006 | B2 |
7075288 | Martin et al. | Jul 2006 | B2 |
7079962 | Cornwall et al. | Jul 2006 | B2 |
7084783 | Melvin et al. | Aug 2006 | B1 |
7089125 | Sonderegger | Aug 2006 | B2 |
7091878 | Holle et al. | Aug 2006 | B2 |
7109882 | Angelis | Sep 2006 | B2 |
7112949 | Voisine | Sep 2006 | B2 |
7116243 | Schleich et al. | Oct 2006 | B2 |
7119698 | Schleich et al. | Oct 2006 | B2 |
7119713 | Shuey et al. | Oct 2006 | B2 |
7126493 | Junker | Oct 2006 | B2 |
7126494 | Ardalan et al. | Oct 2006 | B2 |
7135850 | Ramirez | Nov 2006 | B2 |
7142106 | Scoggins | Nov 2006 | B2 |
7145474 | Shuey et al. | Dec 2006 | B2 |
7149605 | Chassin et al. | Dec 2006 | B2 |
7154938 | Cumeralto et al. | Dec 2006 | B2 |
7161455 | Tate et al. | Jan 2007 | B2 |
7167804 | Fridholm et al. | Jan 2007 | B2 |
7168972 | Autry et al. | Jan 2007 | B1 |
7170425 | Christopher et al. | Jan 2007 | B2 |
7176807 | Scoggins et al. | Feb 2007 | B2 |
7180282 | Schleifer | Feb 2007 | B2 |
7187906 | Mason et al. | Mar 2007 | B2 |
7196673 | Savage et al. | Mar 2007 | B2 |
7209049 | Dusenberry et al. | Apr 2007 | B2 |
7218998 | Neale | May 2007 | B1 |
7224158 | Petr | May 2007 | B2 |
7227350 | Shuey | Jun 2007 | B2 |
7230972 | Cornwall et al. | Jun 2007 | B2 |
7236498 | Moos et al. | Jun 2007 | B1 |
7236908 | Timko et al. | Jun 2007 | B2 |
7239125 | Hemminger et al. | Jul 2007 | B2 |
7239250 | Brian et al. | Jul 2007 | B2 |
7245511 | Lancaster et al. | Jul 2007 | B2 |
7262709 | Borleske et al. | Aug 2007 | B2 |
7274187 | Loy | Sep 2007 | B2 |
7277027 | Ehrke et al. | Oct 2007 | B2 |
7283062 | Hoiness et al. | Oct 2007 | B2 |
7283580 | Cumeralto | Oct 2007 | B2 |
7283916 | Cahill-O'Brien et al. | Oct 2007 | B2 |
7298134 | Weikel et al. | Nov 2007 | B2 |
7298135 | Briese et al. | Nov 2007 | B2 |
7301476 | Shuey et al. | Nov 2007 | B2 |
7308369 | Rudran et al. | Dec 2007 | B2 |
7308370 | Mason et al. | Dec 2007 | B2 |
7312721 | Mason et al. | Dec 2007 | B2 |
7315162 | Shuey | Jan 2008 | B2 |
7317404 | Cumeralto et al. | Jan 2008 | B2 |
7327998 | Kumar et al. | Feb 2008 | B2 |
7336200 | Osterloh et al. | Feb 2008 | B2 |
7339805 | Hemminger et al. | Mar 2008 | B2 |
7346030 | Cornwall | Mar 2008 | B2 |
7348749 | Ide et al. | Mar 2008 | B2 |
7355867 | Shuey | Apr 2008 | B2 |
7362232 | Holle et al. | Apr 2008 | B2 |
7362236 | Hoiness | Apr 2008 | B2 |
7365687 | Borleske et al. | Apr 2008 | B2 |
7417420 | Shuey | Aug 2008 | B2 |
7417557 | Osterloh et al. | Aug 2008 | B2 |
7421205 | Ramirez | Sep 2008 | B2 |
7427927 | Borleskey et al. | Sep 2008 | B2 |
7453373 | Cumeralto et al. | Nov 2008 | B2 |
7471516 | Voisine | Dec 2008 | B2 |
7479895 | Osterloh et al. | Jan 2009 | B2 |
7486056 | Shuey | Feb 2009 | B2 |
7495578 | Borleske | Feb 2009 | B2 |
7504821 | Shuey | Mar 2009 | B2 |
7505453 | Carpenter et al. | Mar 2009 | B2 |
7510422 | Showcatally et al. | Mar 2009 | B2 |
7516026 | Cornwall et al. | Apr 2009 | B2 |
7535378 | Cornwall | May 2009 | B2 |
7540766 | Makinson et al. | Jun 2009 | B2 |
7545135 | Holle et al. | Jun 2009 | B2 |
7545203 | Byeon et al. | Jun 2009 | B2 |
7561062 | Schleich et al. | Jul 2009 | B2 |
7561399 | Slater et al. | Jul 2009 | B2 |
7583203 | Uy et al. | Sep 2009 | B2 |
7584066 | Roytelman | Sep 2009 | B2 |
7616420 | Slater et al. | Nov 2009 | B2 |
7626489 | Berkman et al. | Dec 2009 | B2 |
7630863 | Zewigle et al. | Dec 2009 | B2 |
7639000 | Briese et al. | Dec 2009 | B2 |
7656649 | Loy et al. | Feb 2010 | B2 |
7671814 | Savage et al. | Mar 2010 | B2 |
7683642 | Martin et al. | Mar 2010 | B2 |
7688060 | Briese et al. | Mar 2010 | B2 |
7688061 | Briese et al. | Mar 2010 | B2 |
7696941 | Cunningham, Jr. | Apr 2010 | B2 |
7701199 | Makinson et al. | Apr 2010 | B2 |
7702594 | Scoggins et al. | Apr 2010 | B2 |
7729852 | Hoiness et al. | Jun 2010 | B2 |
7742430 | Scoggins et al. | Jun 2010 | B2 |
7746054 | Shuey | Jun 2010 | B2 |
7747400 | Voisine | Jun 2010 | B2 |
7747534 | Villicana et al. | Jun 2010 | B2 |
7756030 | Clave et al. | Jul 2010 | B2 |
7756078 | Van Wyk et al. | Jul 2010 | B2 |
7756651 | Holdsclaw | Jul 2010 | B2 |
7761249 | Ramirez | Jul 2010 | B2 |
7764714 | Monier et al. | Jul 2010 | B2 |
20020109607 | Cumeralto et al. | Aug 2002 | A1 |
20020158774 | Johnson et al. | Oct 2002 | A1 |
20030001754 | Johnson et al. | Jan 2003 | A1 |
20030122686 | Ehrke et al. | Jul 2003 | A1 |
20030187550 | Wilson et al. | Oct 2003 | A1 |
20040061625 | Ehrke et al. | Apr 2004 | A1 |
20040066310 | Ehrke et al. | Apr 2004 | A1 |
20040070517 | Ehrke et al. | Apr 2004 | A1 |
20040119458 | Heuell et al. | Jun 2004 | A1 |
20040150575 | Lizalek et al. | Aug 2004 | A1 |
20040192415 | Luglio et al. | Sep 2004 | A1 |
20040218616 | Ardalan et al. | Nov 2004 | A1 |
20040222783 | Loy | Nov 2004 | A1 |
20050024235 | Shuey et al. | Feb 2005 | A1 |
20050090995 | Sonderegger | Apr 2005 | A1 |
20050110480 | Martin et al. | May 2005 | A1 |
20050119841 | Martin | Jun 2005 | A1 |
20050119930 | Simon | Jun 2005 | A1 |
20050212689 | Randall | Sep 2005 | A1 |
20050218873 | Shuey et al. | Oct 2005 | A1 |
20050237047 | Voisine | Oct 2005 | A1 |
20050240314 | Martinez | Oct 2005 | A1 |
20050251401 | Shuey | Nov 2005 | A1 |
20050251403 | Shuey | Nov 2005 | A1 |
20050270015 | Hemminger et al. | Dec 2005 | A1 |
20050278440 | Scoggins | Dec 2005 | A1 |
20060001415 | Fridholm et al. | Jan 2006 | A1 |
20060012935 | Murphy | Jan 2006 | A1 |
20060038548 | Shuey | Feb 2006 | A1 |
20060043961 | Loy | Mar 2006 | A1 |
20060044157 | Peters et al. | Mar 2006 | A1 |
20060044851 | Lancaster et al. | Mar 2006 | A1 |
20060055610 | Borisov et al. | Mar 2006 | A1 |
20060056493 | Cornwall et al. | Mar 2006 | A1 |
20060071810 | Scoggins et al. | Apr 2006 | A1 |
20060071812 | Mason, Jr. et al. | Apr 2006 | A1 |
20060074556 | Hoiness et al. | Apr 2006 | A1 |
20060074601 | Hoiness et al. | Apr 2006 | A1 |
20060085147 | Cornwall et al. | Apr 2006 | A1 |
20060114121 | Cumeralto et al. | Jun 2006 | A1 |
20060126255 | Slater et al. | Jun 2006 | A1 |
20060145685 | Ramirez | Jul 2006 | A1 |
20060145890 | Junker et al. | Jul 2006 | A1 |
20060158177 | Ramirez | Jul 2006 | A1 |
20060158348 | Ramirez | Jul 2006 | A1 |
20060168804 | Loy et al. | Aug 2006 | A1 |
20060202858 | Holle et al. | Sep 2006 | A1 |
20060206433 | Scoggins | Sep 2006 | A1 |
20060217936 | Mason et al. | Sep 2006 | A1 |
20060224335 | Borleske et al. | Oct 2006 | A1 |
20060232433 | Holle et al. | Oct 2006 | A1 |
20060261973 | Junker et al. | Nov 2006 | A1 |
20070013549 | Schleich et al. | Jan 2007 | A1 |
20070063868 | Borleske | Mar 2007 | A1 |
20070091548 | Voisine | Apr 2007 | A1 |
20070096769 | Shuey | May 2007 | A1 |
20070115022 | Hemminger et al. | May 2007 | A1 |
20070124109 | Timko et al. | May 2007 | A1 |
20070124262 | Uy et al. | May 2007 | A1 |
20070147268 | Kelley et al. | Jun 2007 | A1 |
20070177319 | Hirst | Aug 2007 | A1 |
20070200729 | Borleske et al. | Aug 2007 | A1 |
20070205915 | Shuey et al. | Sep 2007 | A1 |
20070213880 | Ehlers | Sep 2007 | A1 |
20070229305 | Bonicatto et al. | Oct 2007 | A1 |
20070236362 | Brian et al. | Oct 2007 | A1 |
20070257813 | Vaswani et al. | Nov 2007 | A1 |
20070262768 | Holdsclaw | Nov 2007 | A1 |
20070271006 | Golden et al. | Nov 2007 | A1 |
20080001779 | Cahill-O'Brien et al. | Jan 2008 | A1 |
20080007247 | Gervals et al. | Jan 2008 | A1 |
20080007426 | Morand | Jan 2008 | A1 |
20080010212 | Moore et al. | Jan 2008 | A1 |
20080012550 | Shuey | Jan 2008 | A1 |
20080018492 | Ehrke et al. | Jan 2008 | A1 |
20080024115 | Makinson et al. | Jan 2008 | A1 |
20080062055 | Cunningham | Mar 2008 | A1 |
20080068004 | Briese et al. | Mar 2008 | A1 |
20080068005 | Briese et al. | Mar 2008 | A1 |
20080068006 | Briese et al. | Mar 2008 | A1 |
20080079741 | Martin et al. | Apr 2008 | A1 |
20080088475 | Martin | Apr 2008 | A1 |
20080097707 | Voisine | Apr 2008 | A1 |
20080111526 | Shuey | May 2008 | A1 |
20080116906 | Martin et al. | May 2008 | A1 |
20080129420 | Borisov et al. | Jun 2008 | A1 |
20080129537 | Osterloh et al. | Jun 2008 | A1 |
20080143491 | Deaver | Jun 2008 | A1 |
20080144548 | Shuey et al. | Jun 2008 | A1 |
20080180274 | Cumeralto et al. | Jul 2008 | A1 |
20080204272 | Ehrke et al. | Aug 2008 | A1 |
20080204853 | Hughes | Aug 2008 | A1 |
20080218164 | Sanderford | Sep 2008 | A1 |
20080219210 | Shuey et al. | Sep 2008 | A1 |
20080224891 | Ehrke et al. | Sep 2008 | A1 |
20080238714 | Ehrke et al. | Oct 2008 | A1 |
20080238716 | Ehrke et al. | Oct 2008 | A1 |
20080266133 | Martin | Oct 2008 | A1 |
20090003214 | Vaswani et al. | Jan 2009 | A1 |
20090003232 | Vaswani et al. | Jan 2009 | A1 |
20090003243 | Vaswani et al. | Jan 2009 | A1 |
20090003356 | Vaswani et al. | Jan 2009 | A1 |
20090015234 | Voisine et al. | Jan 2009 | A1 |
20090062970 | Forbes, Jr. et al. | Mar 2009 | A1 |
20090096211 | Stiesdal | Apr 2009 | A1 |
20090134996 | White, II et al. | May 2009 | A1 |
20090146839 | Reddy et al. | Jun 2009 | A1 |
20090153356 | Holt | Jun 2009 | A1 |
20090167558 | Borleske | Jul 2009 | A1 |
20090187284 | Kreiss et al. | Jul 2009 | A1 |
20090224940 | Cornwall | Sep 2009 | A1 |
20090245270 | Van Greunen et al. | Oct 2009 | A1 |
20090256364 | Gadau et al. | Oct 2009 | A1 |
20090262642 | Van Greunen et al. | Oct 2009 | A1 |
20090265042 | Molenkopf | Oct 2009 | A1 |
20090276170 | Bickel | Nov 2009 | A1 |
20090278708 | Kelley | Nov 2009 | A1 |
20090281673 | Taft | Nov 2009 | A1 |
20090281679 | Taft et al. | Nov 2009 | A1 |
20090284251 | Makinson et al. | Nov 2009 | A1 |
20090287428 | Holdsclaw | Nov 2009 | A1 |
20090294260 | Makinson et al. | Dec 2009 | A1 |
20090295371 | Pontin et al. | Dec 2009 | A1 |
20090296431 | Borisov | Dec 2009 | A1 |
20090299660 | Winter | Dec 2009 | A1 |
20090299884 | Chandra | Dec 2009 | A1 |
20090300191 | Pace et al. | Dec 2009 | A1 |
20090309749 | Gilbert et al. | Dec 2009 | A1 |
20090309756 | Mason | Dec 2009 | A1 |
20090310511 | Vaswani et al. | Dec 2009 | A1 |
20090312881 | Venturini et al. | Dec 2009 | A1 |
20090319093 | Joos et al. | Dec 2009 | A1 |
20100007521 | Cornwall | Jan 2010 | A1 |
20100007522 | Morris | Jan 2010 | A1 |
20100010700 | Hoiness et al. | Jan 2010 | A1 |
20100013632 | Salewske et al. | Jan 2010 | A1 |
20100026517 | Cumeralto et al. | Feb 2010 | A1 |
20100036624 | Martin et al. | Feb 2010 | A1 |
20100036625 | Martin et al. | Feb 2010 | A1 |
20100040042 | Van Greunen et al. | Feb 2010 | A1 |
20100045479 | Schamber et al. | Feb 2010 | A1 |
20100060259 | Vaswani et al. | Mar 2010 | A1 |
20100061350 | Flammer, III | Mar 2010 | A1 |
20100073193 | Flammer, III | Mar 2010 | A1 |
20100074176 | Flammer, III et al. | Mar 2010 | A1 |
20100074304 | Flammer, III | Mar 2010 | A1 |
20100103940 | Van Greunen et al. | Apr 2010 | A1 |
20100109650 | Briese et al. | May 2010 | A1 |
20100110617 | Savage et al. | May 2010 | A1 |
20100117856 | Sonderegger | May 2010 | A1 |
20100128066 | Murata et al. | May 2010 | A1 |
20100134089 | Uram et al. | Jun 2010 | A1 |
20100150059 | Hughes et al. | Jun 2010 | A1 |
20100157838 | Vaswani et al. | Jun 2010 | A1 |
20100188254 | Johnson et al. | Jul 2010 | A1 |
20100188255 | Cornwall | Jul 2010 | A1 |
20100188256 | Cornwall et al. | Jul 2010 | A1 |
20100188257 | Johnson | Jul 2010 | A1 |
20100188258 | Cornwall et al. | Jul 2010 | A1 |
20100188259 | Johnson et al. | Jul 2010 | A1 |
20100188260 | Cornwall et al. | Jul 2010 | A1 |
20100188263 | Cornwall et al. | Jul 2010 | A1 |
20100188938 | Johnson et al. | Jul 2010 | A1 |
20100192001 | Cornwall et al. | Jul 2010 | A1 |
Number | Date | Country |
---|---|---|
9685 | Feb 2008 | EA |
0 020 310 | Dec 1980 | EP |
2002-247780 | Aug 2002 | JP |
2004-096906 | Mar 2004 | JP |
2066084 | Aug 1996 | RU |
2200364 | Mar 2010 | RU |
1473008 | Apr 1989 | SU |
WO 9826489 | Jun 1998 | WO |
Entry |
---|
International Search Report and Written Opinion of the International searching Authority mailed Dec. 20, 2012 on related PCT Appln. PCT/US2010/033571. |
Number | Date | Country | |
---|---|---|---|
20130030591 A1 | Jan 2013 | US |
Number | Date | Country | |
---|---|---|---|
61176398 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12774507 | May 2010 | US |
Child | 13567473 | US |