The present disclosure pertains to systems and methods for detecting the occurrence of a fault that is likely to result in a fault induced delayed voltage recovery (FIDVR) event and to implementing control strategies to avoid or reduce the severity of the FIDVR event.
Non-limiting and non-exhaustive embodiments of the disclosure are described, including various embodiments of the disclosure, with reference to the figures, in which:
When a fault occurs in an electric power transmission and distribution system, the fault may depress voltages throughout the load area “downstream” of the fault location. Modern electric power transmission and distribution systems employ a variety of types of equipment and techniques to identify faults and to de-energize affected areas of the system to clear the fault. Under normal conditions, once the fault is cleared load voltages return to normal values. Under certain conditions, however, the voltage in the load area may not recover promptly when the fault is cleared. Rather, the immediate increase in voltage when the fault is cleared may be smaller than expected and full recovery to normal voltage has been observed to take many seconds or even a few minutes. The occurrence of such events have been observed and documented by operators of electric power transmission and distribution systems. The present disclosure is addressed to systems and methods for identifying the occurrence of FIDVR events and to implementing control strategies to avoid or reduce the severity of the FIDVR event.
The embodiments of the disclosure will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. It will be readily understood that the components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the systems and methods of the disclosure is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments of the disclosure. In addition, the steps of a method do not necessarily need to be executed in any specific order, or even sequentially, nor need the steps be executed only once, unless otherwise specified.
In some cases, well-known features, structures or operations are not shown or described in detail. Furthermore, the described features, structures, or operations may be combined in any suitable manner in one or more embodiments. It will also be readily understood that the components of the embodiments as generally described and illustrated in the figures herein could be arranged and designed in a wide variety of different configurations.
Several aspects of the embodiments described may be implemented as software modules or components. As used herein, a software module or component may include any type of computer instruction or computer executable code located within a memory device and/or transmitted as electronic signals over a system bus or wired or wireless network. A software module or component may, for instance, comprise one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that performs one or more tasks or implements particular abstract data types.
In certain embodiments, a particular software module or component may comprise disparate instructions stored in different locations of a memory device, which together implement the described functionality of the module. Indeed, a module or component may comprise a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network. In a distributed computing environment, software modules or components may be located in local and/or remote memory storage devices. In addition, data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.
Embodiments may be provided as a computer program product including a non-transitory computer and/or machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic device) to perform processes described herein. For example, a non-transitory computer-readable medium may store instructions that, when executed by a processor of a computer system, cause the processor to perform certain methods disclosed herein. The non-transitory computer-readable medium may include, but is not limited to, hard drives, floppy diskettes, optical disks, CD-ROMs, DVD-ROMs, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, solid-state memory devices, or other types of machine-readable media suitable for storing electronic and/or processor executable instructions.
Substation 119 may include a generator 114, which may be a distributed generator, and which may be connected to bus 126 through step-up transformer 117. Bus 126 may be connected to a distribution bus 132 via a step-down transformer 130. Various distribution lines 136 and 134 may be connected to distribution bus 132. Distribution line 136 may lead to substation 141 where the line is monitored and/or controlled using IED 106, which may selectively open and close breaker 152. Load 140 may be fed from distribution line 136. Further step-down transformer 144 in communication with distribution bus 132 via distribution line 136 may be used to step down a voltage for consumption by load 140.
Distribution line 134 may lead to substation 151, and deliver electric power to bus 148. Bus 148 may also receive electric power from distributed generator 116 via transformer 150. Distribution line 158 may deliver electric power from bus 148 to load 138, and may include further step-down transformer 142. Circuit breaker 160 may be used to selectively connect bus 148 to distribution line 134. IED 108 may be used to monitor and/or control circuit breaker 160 as well as distribution line 158.
Electric power delivery system 100 may be monitored, controlled, automated, and/or protected using intelligent electronic devices (IEDs), such as IEDs 104, 106, 108, 115, and 170, and a central monitoring system 172. In general, IEDs in an electric power generation and transmission system may be used for protection, control, automation, and/or monitoring of equipment in the system. For example, IEDs may be used to monitor equipment of many types, including electric transmission lines, electric distribution lines, current transformers, busses, switches, circuit breakers, reclosers, transformers, autotransformers, tap changers, voltage regulators, capacitor banks, generators, motors, pumps, compressors, valves, and a variety of other types of monitored equipment.
As used herein, an IED (such as IEDs 104, 106, 108, 115, and 170) may refer to any microprocessor-based device that monitors, controls, automates, and/or protects monitored equipment within system 100. Such devices may include, for example, remote terminal units, differential relays, distance relays, directional relays, feeder relays, overcurrent relays, voltage regulator controls, voltage relays, breaker failure relays, generator relays, motor relays, automation controllers, bay controllers, meters, recloser controls, communications processors, computing platforms, programmable logic controllers (PLCs), programmable automation controllers, input and output modules, and the like. The term IED may be used to describe an individual IED or a system comprising multiple IEDs.
A common time signal may be distributed throughout system 100. Utilizing a common or universal time source may ensure that IEDs have a synchronized time signal that can be used to generate time synchronized data, such as synchrophasors. In various embodiments, IEDs 104, 106, 108, 115, and 170 may receive a common time signal 168. The time signal may be distributed in system 100 using a communications network 162 or using a common time source, such as a Global Navigation Satellite System (“GNSS”), or the like.
According to various embodiments, central monitoring system 172 may comprise one or more of a variety of types of systems. For example, central monitoring system 172 may include a supervisory control and data acquisition (SCADA) system and/or a wide area control and situational awareness (WACSA) system. A central IED 170 may be in communication with IEDs 104, 106, 108, and 115. IEDs 104, 106, 108 and 115 may be remote from the central IED 170, and may communicate over various media such as a direct communication from IED 106 or over a wide-area communications network 162. According to various embodiments, certain IEDs may be in direct communication with other IEDs (e.g., IED 104 is in direct communication with central IED 170) or may be in communication via a communication network 162 (e.g., IED 108 is in communication with central IED 170 via communication network 162).
Communication via network 162 may be facilitated by networking devices including, but not limited to, multiplexers, routers, hubs, gateways, firewalls, and switches. In some embodiments, IEDs and network devices may comprise physically distinct devices. In other embodiments, IEDs and network devices may be composite devices, or may be configured in a variety of ways to perform overlapping functions. IEDs and network devices may comprise multi-function hardware (e.g., processors, computer-readable storage media, communications interfaces, etc.) that can be utilized in order to perform a variety of tasks that pertain to network communications and/or to operation of equipment within system 100.
A fault in system 100 may result in an FIDVR event in certain conditions. For example, such conditions may include power factors reflecting a high ratio of inductive loads to resistive loads. Such a load profile may be created, for example by a large number of motors or other types of inductive loads. Residential air conditions may present such a load profile. The inertial constants of small motors are small (typically less than 40 milliseconds, and accordingly, may stall in response to relatively small voltage fluctuations. As such, it has been observed that faults cleared in as little as 50 milliseconds (3 cycles in a system with a nominal frequency of 60 Hz) can cause widespread stalling. Accordingly, various embodiments of the present disclosure may be configured to identify a fault that is likely to result in an FIDVR event and to implement a control strategy to avoid or reduce the severity of the FIDVR event within a control window of between 50 and 100 milliseconds after the fault and excluding a breaker operation time.
Once a motor is stalled, current flowing through the motor increases dramatically. The additional current flow may lead to a temperature increase until a thermal cutoff threshold is reached and further current flow is interrupted. After the thermal threshold is exceeded and additional current flow is cut off, the temperature of the device may begin to decrease. Once the device has cooled, the device may resume normal operation. As a result of the time needed for the individual air conditioning systems to reach the thermal threshold and to cool down after reaching the thermal threshold, the voltage of an electric distribution system may remain depressed for an extended period of time (e.g., on the order of minutes). While the voltage in the system is depressed, the system may face an increased risk of blackout.
With reference to
As discussed in greater detail below, systems and methods consistent with the present disclosure may be configured to identify such an event and may implement control strategies configured to avoid or minimize the severity of the FIDVR event. For example, in certain embodiments, after detecting an FIDVR event, reactive power support may be provided by selectively connecting a capacitor bank 174 to system 100 using a breaker 176. Connecting the capacitor bank 174 may provide reactive power support to avoid or mitigate the severity of an FIDVR event. Other control strategies may also be employed, such as controlling tap changes on transformers 130, 142, and 144 or selectively disconnecting loads 138 or 140 or to preserve the stability of system 100.
As discussed above, an FIDVR event may result from the combined stalling effect of a large number of motors in residential air conditioning systems. When the amplitude of the voltage at the terminals of a motor is reduced suddenly (e.g., when the fault occurs at time 202) or when the voltage is ramped at a moderate rate (e.g., at time 212), the motors are at risk of stalling. One factor influencing whether a particular motor will stall is the phase of the voltage at the instant that the step is applied. The greatest likelihood of the motor stalling may be when the voltage is at 0° because this phase corresponds to 90° of flux. Accordingly, various embodiments consistent with the present disclosure may determine the voltage phase at the time of the fault and may assess whether the voltage phase is likely to contribute to the occurrence of an FIDVR event.
Motors in air conditioning units deployed in an electric power transmission and distribution system have varying physical parameters (e.g., windings of the motor may have a different number of turns, may carry different currents, etc.). As a result, the torque developed by different motors may also vary from one air conditioning unit to another and over time. The average rotor speed is slower than synchronous with respect to the power system frequency, and the instantaneous rotor speed is not constant but varies in accordance with the variation of electromagnetic and load torques. The result of the non-synchronism of the driving and resisting torques is that the variation of rotor speed is not constant even in steady supply conditions. Instead, the variations of electromagnetic torque, load torque, and rotor speed may follow a pattern determined by the difference between synchronous and rotor speeds. The internal condition of the motor at the moment of inception of a fault may be a function of the operational history of the driven load because the wave of rotor-synchronized load torque constantly slips in phase with respect to the phase of the supply voltage. In a real population of motors the relative phase of electromagnetic torque and load torque at the moment a supply disturbance (e.g., a fault) would be largely random.
After the fault is cleared other control actions may be taken to stabilize the system; however, the fault may have caused a number of motors in air conditioning units to stall. These stalled motors may result in a large current draw and a corresponding large drop in the system's voltage following the fault. The stalled motors may continue to draw an abnormally large current until reaching a thermal cutoff point. Accordingly, the distribution voltage may remain substantially below the nominal voltage 210.
In some circumstances, control actions that are implemented slowly (e.g., implemented by operator action) may contribute to variations in the distribution voltage. For example, a capacitor bank may be connected to provide reactive power support to the system. Such an action may cause a voltage to rise. As the voltage rises above the nominal voltage 210, other actions may be taken to reduce the voltage. For example, at 206, a tap change may occur in a transformer. In the illustrated example, another tap change may be required at 208 before the voltage returns to an acceptable range near the nominal voltage. In the illustrated example, the fluctuations in voltage may leave the electric power distribution system more vulnerable to blackouts. Accordingly, detecting the circumstances in which an FIDVR event is likely to occur may aid in the development and timely execution of control strategies optimized to avoid or minimize the severity the FIDVR event.
The fault may occur at the time indicated by dashed line 302. The speed of the motors declines rapidly following the fault at time 302 because of the small inertial constants of the plurality of motors. As illustrated, each of the plurality of motors 304, 306, 308, and 310 may respond differently to the fault. Motors 306 and 308 stall in response to the fault; however, motor 308 stalls more rapidly than motor 306. In contrast, motors 304 and 310 recover after the fault, with motor 304 recovering more quickly than motor 310. The differing responses illustrated in
The conditions in which the fault occurs may also affect the responses of the plurality of motors 304, 306, 308, and 310. For example, the voltage drop caused by the fault and the duration of the fault may influence which motors stall, if any, and which motors recover following the fault. The response may also be affected by the phase of the voltage at the time the fault occurs. As described above, the sinusoidal function of the supply voltage results in an alternating flux in the motor, and accordingly, may affect the motors' responses to the fault.
As a result of fault 442, system 400 may experience an FIDVR event under certain conditions. A control system (not shown) associated with system 400 may evaluate various criteria to assess the likelihood of the occurrence of an FIDVR event. In some embodiments, such criteria may include the duration of the fault, a voltage drop due to the fault, and when the fault occurs with respect to a phase of the supply voltage, an ambient temperature, power factors of the feeders, etc.
System 400 may be configured to implement a control strategy dependent upon the type of load connected to each feeder. In some embodiments, the type of load connected to a feeder may be inferred from a power factor. For example, the loads 446 on feeder 436 may include a large number of small single phase motors used in connection with air conditioning systems. When the ambient temperature is high the air conditioners may be operating frequently. The large number of motors may result in a large inductive load component and a power factor that is significantly below 1 (e.g., a power factor between 0.79 and 0.85). A decrease in voltage associated with an FIDVR event may result in an increased current draw. The increased current draw may exacerbate the voltage decrease during the FIDVR. Accordingly, if load shedding is part of a control strategy for avoiding or reducing the severity of the FIDVR event, shedding the feeder with the largest inductive load would result in the greatest benefit.
In contrast, feeder 440 may have a power factor near 1, and accordingly may include largely resistive loads 444. A decrease in voltage results in a decrease in current drawn by a feeder 440. Accordingly, in response to a likely FIDVR event, a control strategy employed to avoid or reduce the severity of the FIDVR event that selectively disconnects a feeder with a large inductive component would be more effective than a control strategy that selectively disconnects a feeder with a primarily resistive component.
Still further, certain feeders may have only a minor impact on the occurrence or severity of an FIDVR event. In the illustrated embodiment, loads 448 reflect a mixture of inductive and resistive loads. A decrease in voltage may cause the resistive components to draw less current, while the inductive component draws more current. Overall, the change in current flow through feeder 434 as a result of a change in voltage may be relatively small, and accordingly, may have only a small impact on the severity and/or duration of an FIDVR event.
A control system associated with system 400 may monitor a power factor associated with feeders 434, 436, 438, and 440 to identify feeders having a large inductive component, such as feeder 436. Based on a power factor and other criteria, a control system may assess whether disconnection of one or more feeders may avoid or reduce the severity of the FIDVR event caused by a fault 442. Moreover, the selective disconnection of certain feeders may be prioritized by the likely impact on avoiding or reducing the severity of the FIDVR event.
In addition to assessing a load profile, a control system consistent with the present disclosure may also assess a priority of the loads supplied by a particular feeder when developing a control strategy to avoid or reduce the severity of the FIDVR event. Certain loads may have a higher priority than other loads, and accordingly, may only be disconnected as a last resort. In the illustrated embodiment, a hospital 450 is connected to feeder 438. The hospital 450 may represent a high priority load that should not be selectively disconnected regardless of its load profile.
After a fault has been detected, at 506, the fault may be analyzed. A variety of parameters may be evaluated in various embodiments consistent with the present disclosure, such as a duration of the fault, the voltage dip due to the fault at the head of a feeder, and the phase of the voltage at which the fault occurs (e.g., 0 degrees, 40 degrees, 85 degrees, etc.).
At 508, local environmental conditions may be determined in the area serviced by the electric power transmission and distribution system. As described above, an FIDVR event may be more likely to occur when a large number of air conditioning systems are operating.
At 510, load profiles may be estimated. In some embodiments, a load estimate may be generated for each of a plurality of feeders. The load estimate may be based, at least in part, on a power factor associated with various loads.
Based on the analysis that occurs at 506, 508, and/or 510, method 500 may determine at 512 whether the fault is likely to result in an FIDVR event. If the fault is unlikely to result in an FIDVR event, the fault may be cleared and method 500 may return to monitoring the power transmission and distribution system at 502. If the fault is likely to result in an FIDVR event, method 500 may progress to 514.
At 514, feeders with reactive components may be identified. The identification of such feeders may be useful for identifying a control strategy for avoiding or ameliorating the effects of an FIDVR event. In some situations, feeders having large high reactive power requirements may be targeted by certain embodiments consistent with the present disclosure for load shedding to avoid or reduce the severity of the FIDVR event.
At 516, a system implementing method 500 may determine reactive power requirements. Such a determination may be based, in various embodiments, on the estimated load profiles and the identification of feeders with reactive components. In some circumstances the fault may increase the reactive power because single phase motors may stall as a result of the fault. Accordingly, supplying additional reactive power support may avoid or mitigate the severity of the FIDVR event. As described above, a decrease in supply voltage to a load with a large reactive power component may result in increased current draw. The increase in current may strain an electric power transmission and distribution system.
At 518, feeders supplying critical loads may be identified so that such loads are avoided in the event that load shedding is part of a control strategy. In some embodiments, critical loads may be avoided regardless of the overall load profile associated with the feeder supplying the critical load.
At 520, feeders with low or moderate impact on the FIDVR event may be identified. Such feeders may include a load profile that is likely to remain substantially unchanged as a result of the fault. Such feeders may include a load profile that includes a mix of resistive and inductive loads, such that a decrease in the supply voltage may not substantially alter the current drawn by the feeder. The identification of such feeders may be useful to avoid overshedding by avoiding feeders that are unlikely to significantly affect the occurrence or severity of an FIDVR event.
At 522 a control strategy within a substation may be implemented consistent with certain embodiments. For example, a substation controller may selectively connect one or more capacitor banks in response to a determination that reactive power support may avoid or reduce the severity of the FIDVR event. In another example, a substation controller may identify and selectively disconnect one or more feeders that are likely to increase the likelihood of the occurrence or severity of an FIDVR event.
At 524, a control strategy may be implemented across multiple substations consistent with certain embodiments. Coordination of the control strategy across multiple substations may provide a mechanism to avoid overshedding and to implement the most effective strategy for addressing the FIDVR event. In various embodiments, coordination of the control strategy may be accomplished using distributed control or using central control. In a distributed control scenario, a plurality of substation controllers may be enabled to make certain control decisions independently and to communicate with peer devices regarding other control decisions. In a central control strategy, a central controller may receive input from a plurality of devices, may analyze the input, and may direct the devices to take certain control actions.
System 600 includes a communications interface 616 configured to communicate with other IEDs, controllers, and/or devices associated with an electric power transmission and distribution system. In certain embodiments, the communications interface 616 may facilitate direct communication with another IED or communicate with another IED over a communications network. Communications interface 616 may facilitate communications with multiple devices. System 600 may further include a time input 612, which may be used to receive a time signal (e.g., a common time reference) allowing system 600 to apply a time-stamp to the acquired instructions or data points. In certain embodiments, a common time reference may be received via communications interface 616, and accordingly, a separate time input may not be required for time-stamping and/or synchronization operations. One such embodiment may employ the IEEE 1588 protocol. A monitored equipment interface 608 may be configured to receive status information from, and issue control instructions to, a piece of monitored equipment (such as a circuit breaker, conductor, transformer, or the like).
Processor 624 may be configured to process communications received via communications interface 616, time input 612, and/or monitored equipment interface 608 and to coordinate the operation of the other components of system 600. Processor 624 may operate using any number of processing rates and architectures. Processor 624 may be configured to perform any of the various algorithms and calculations described herein. Processor 624 may be embodied as a general purpose integrated circuit, an application specific integrated circuit, a field-programmable gate array, and/or any other suitable programmable logic device.
In certain embodiments, system 600 may include a sensor component 610. In the illustrated embodiment, sensor component 610 is configured to gather data directly from equipment such as a conductor (not shown) and may use, for example, transformers 602 and 614 and A/D converters 618 that may sample and/or digitize filtered waveforms to form corresponding digitized current and voltage signals provided to data bus 642. Current (I) and voltage (V) inputs may be secondary inputs from instrument transformers such as, CTs and VTs. A/D converters 618 may include a single A/D converter or separate A/D converters for each incoming signal. A current signal may include separate current signals from each phase of a three-phase electric power system. A/D converters 618 may be connected to processor 624 by way of data bus 642, through which digitized representations of current and voltage signals may be transmitted to processor 624. In various embodiments, the digitized current and voltage signals may be used to assess various electrical parameters relevant to the systems and methods disclosed herein. The data bus 642 may link monitored equipment interface 608, time input 612, communications interface 616, and a plurality of additional subsystems.
A remote fault detection subsystem 634 may be configured to detect a fault or to receive an indication of the occurrence of a fault. In some embodiments, fault detection subsystem 634 may be configured to operate in conjunction with the sensor component 610 to detect the occurrence of a fault by monitoring the electrical characteristics associated with the current and voltage inputs. In other embodiments, an indication of a fault may be communicated to system 600 through communications interface 616 and/or monitored equipment interface 608. Still further, certain embodiments may be configured to both monitor sensor component 610 and to receive an indication of a fault from either monitored equipment interface 608 or communications interface 616.
A fault analysis subsystem 632 may be configured to determine various parameters of a fault. In some embodiments, the fault analysis subsystem 632 may be configured to determine a duration of a fault, a voltage decrease caused by a fault, a point on a waveform at which the fault occurs (e.g., 0 degrees, 40 degrees, 85 degrees, etc.) and other parameters. In some embodiments, measurements used by the fault analysis subsystem 632 may be obtained using sensor component 610. In other embodiments, data regarding the fault may be received via monitored equipment interface 608 or communications interface 616.
A temperature analysis subsystem 644 may be configured to determine an ambient temperature in a particular geographic region in which system 600 is in operation. The ambient temperature may provide an indication of whether residential air conditioning units are likely to be operating, and if so, may also provide an indication of what proportion of a load the air conditioning units represent. As noted above, when the ambient temperature is high, air conditioning units may be operating frequently and in large numbers. The large number of motors may result in a large inductive load component that trigger or exacerbate an FIDVR event.
A load profile analysis subsystem 646 may be configured to determine a load profile based on a variety of factors. One factor that may be used to assess a load profile is the ambient temperature; however, other factors may also be assessed. Additional factors may include various electrical parameters associated with a particular load or feeder, such as a power factor or the amount of current drawn, etc. In some embodiments, a specific type of load profile may be specified by an operator of an electric power transmission and distribution system in which system 600 is operating. In some embodiments, load profile analysis subsystem 646 may be configured to assess the impact of a control action before the action is taken in order to assess the impact of the control action on an FIDVR event. For example, selectively disconnecting a feeder that provides electrical energy primarily to a resistive load would not assist avoiding or reducing the severity of an FIDVR event. Accordingly, load profile analysis subsystem 646 may be configured to avoid such an action. In another example, selectively disconnecting a feeder having a power factor of approximately 0.8 may help to avoid or reduce the severity of the FIDVR event. As such, load profile analysis subsystem may, in conjunction with other subsystems in system 600, be configured to selectively disconnect such a feeder as a last resort to avoid or reduce the severity of an FIDVR event.
A control subsystem 648 may be configured to implement control actions configured to avoid or mitigate the severity of an FIDVR event. Such actions may include, selectively providing reactive power support, controlling tap changes, identifying selected feeders for disconnection, and the like. In some embodiments, control subsystem 648 may be configured to implement a plurality of control actions within a substation. In other embodiments, control subsystem 648 may be configured to implement control actions that are coordinated across multiple substations. In some embodiments, communications regarding such control actions may be sent or received via communications interface 616.
A load priority subsystem 652 may be configured to assess the priority of load associated with various feeders. Load priority analysis subsystem 652 may be configured to avoid shedding high priority loads. In some embodiments, disconnecting high priority loads may be avoided regardless of the impact of such loads on an FIDVR event.
A load analysis subsystem 650 may be configured to determine the types of loads supplied by an electric transmission and distribution system. Load analysis subsystem 650 may determine the types of loads using a variety of techniques. In some embodiments, load analysis subsystem 650 may monitor a power factor. The power factor may provide an indication of the resistive and inductive components of the load. Further, in some embodiments, an operator of the electric power transmission and distribution system may specify the types of loads. Still further, in some embodiments, the responses of the loads to changes in electrical parameters may be used to develop a load model using the techniques disclosed in U.S. Pat. No. 8,706,309, which is assigned to the assignee of the present application.
While specific embodiments and applications of the disclosure have been illustrated and described, it is to be understood that the disclosure is not limited to the precise configurations and components disclosed herein. For example, the systems and methods described herein may be applied to an industrial electric power delivery system or an electric power delivery system implemented in a boat or oil platform that may not include long-distance transmission of high-voltage power. Moreover, principles described herein may also be utilized for protecting an electric system from over-frequency conditions, wherein power generation would be shed rather than load to reduce effects on the system. Accordingly, many changes may be made to the details of the above-described embodiments without departing from the underlying principles of this disclosure. The scope of the present invention should, therefore, be determined only by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4349744 | Reuther | Sep 1982 | A |
4387336 | Joy | Jun 1983 | A |
4829298 | Fernandes | May 1989 | A |
4874961 | Henderson | Oct 1989 | A |
5006846 | Granville | Apr 1991 | A |
5224011 | Yalla | Jun 1993 | A |
5341265 | Westrom | Aug 1994 | A |
5446682 | Janke | Aug 1995 | A |
5498956 | Kinney | Mar 1996 | A |
5592393 | Yalla | Jan 1997 | A |
5596492 | Divan | Jan 1997 | A |
5693404 | Shiraishi et al. | Dec 1997 | A |
5694281 | Roberts | Dec 1997 | A |
5703745 | Roberts | Dec 1997 | A |
5731943 | Roberts | Mar 1998 | A |
6028754 | Guzman | Feb 2000 | A |
6236949 | Hart | May 2001 | B1 |
6265881 | Meliopoulos | Jul 2001 | B1 |
6285917 | Sekiguchi | Sep 2001 | B1 |
6341055 | Guzman | Jan 2002 | B1 |
6356421 | Guzman | Mar 2002 | B1 |
6356471 | Fang | Mar 2002 | B1 |
6411865 | Qin | Jun 2002 | B1 |
6442010 | Kasztenny | Aug 2002 | B1 |
6446682 | Viken | Sep 2002 | B1 |
6603298 | Guzman | Aug 2003 | B2 |
6608742 | Schweitzer | Aug 2003 | B2 |
6662124 | Schweitzer | Dec 2003 | B2 |
6694270 | Hart | Feb 2004 | B2 |
6757146 | Benmouyal | Jun 2004 | B2 |
6839210 | Roberts | Jan 2005 | B2 |
6845333 | Anderson | Jan 2005 | B2 |
6915186 | Patterson, Jr. | Jul 2005 | B2 |
6946753 | Kernahan | Sep 2005 | B2 |
7072744 | Kuwabara | Jul 2006 | B2 |
7116010 | Lasseter | Oct 2006 | B2 |
7196884 | Guzman | Mar 2007 | B2 |
7319576 | Thompson | Jan 2008 | B2 |
7356422 | Schweitzer | Apr 2008 | B2 |
7457688 | Szepek | Nov 2008 | B2 |
7480580 | Zweigle | Jan 2009 | B2 |
7570469 | Guzman | Aug 2009 | B2 |
7582986 | Folkers | Sep 2009 | B2 |
7630863 | Zweigle | Dec 2009 | B2 |
7635967 | Loucks | Dec 2009 | B2 |
7660088 | Benmouyal | Feb 2010 | B2 |
7710693 | Guzman | May 2010 | B2 |
7761910 | Ransom | Jul 2010 | B2 |
7856327 | Schweitzer | Dec 2010 | B2 |
7903381 | Fischer | Mar 2011 | B2 |
7930117 | Guzman-Casillas | Apr 2011 | B2 |
8082367 | Etheridge | Dec 2011 | B2 |
8405247 | Miller | Mar 2013 | B2 |
8410633 | Batzler | Apr 2013 | B2 |
8560255 | Elwarry | Oct 2013 | B2 |
8766479 | Dorn | Jul 2014 | B2 |
20020105231 | Koeppe | Aug 2002 | A1 |
20040021470 | Adams | Feb 2004 | A1 |
20040027748 | Kojovic | Feb 2004 | A1 |
20040059469 | Hart | Mar 2004 | A1 |
20040138834 | Blackett | Jul 2004 | A1 |
20040252525 | Aldridge | Dec 2004 | A1 |
20050144437 | Ransom | Jun 2005 | A1 |
20060077605 | Folkers | Apr 2006 | A1 |
20060224336 | Petras | Oct 2006 | A1 |
20060259255 | Anderson | Nov 2006 | A1 |
20070086134 | Zweigle | Apr 2007 | A1 |
20070100504 | Moxley | May 2007 | A1 |
20070103004 | Chou | May 2007 | A1 |
20070198985 | Yanagihashi | Aug 2007 | A1 |
20070219755 | Williams | Sep 2007 | A1 |
20070222294 | Tsukida | Sep 2007 | A1 |
20070239372 | Schweitzer | Oct 2007 | A1 |
20080040296 | Bridges | Feb 2008 | A1 |
20080204044 | Ponnaluri | Aug 2008 | A1 |
20080225452 | Stoupis | Sep 2008 | A1 |
20080232005 | Kuehnle | Sep 2008 | A1 |
20080281540 | Zweigle | Nov 2008 | A1 |
20090021082 | Loucks | Jan 2009 | A1 |
20090079266 | McNamara | Mar 2009 | A1 |
20090085407 | Venkatasubramanian | Apr 2009 | A1 |
20090088989 | Guzman | Apr 2009 | A1 |
20090088990 | Schweitzer | Apr 2009 | A1 |
20090089608 | Guzman | Apr 2009 | A1 |
20090091867 | Guzman | Apr 2009 | A1 |
20090099798 | Gong | Apr 2009 | A1 |
20090125158 | Schweitzer | May 2009 | A1 |
20090198383 | Gardner | Aug 2009 | A1 |
20090254655 | Kidwell | Oct 2009 | A1 |
20090276173 | Wang | Nov 2009 | A1 |
20100002348 | Donolo | Jan 2010 | A1 |
20100104847 | Ciavatta | Apr 2010 | A1 |
20100114390 | Stevenson | May 2010 | A1 |
20100145536 | Masters | Jun 2010 | A1 |
20100152910 | Taft | Jun 2010 | A1 |
20100198423 | Hirst | Aug 2010 | A1 |
20110004324 | Bickel | Jan 2011 | A1 |
20110022734 | Etheridge | Jan 2011 | A1 |
20110062708 | Prochaska | Mar 2011 | A1 |
20110068576 | Meier | Mar 2011 | A1 |
20110074215 | Vartanian | Mar 2011 | A1 |
20110077885 | Zweigle | Mar 2011 | A1 |
20110190958 | Hirst | Aug 2011 | A1 |
20110213606 | Seaman | Sep 2011 | A1 |
20110251732 | Schweitzer | Oct 2011 | A1 |
20110298286 | Batzler | Dec 2011 | A1 |
20120226386 | Kulathu | Sep 2012 | A1 |
20130096724 | Divan | Apr 2013 | A1 |
20130138260 | Divan | May 2013 | A1 |
20130173078 | Divan | Jul 2013 | A1 |
20140103888 | Divan | Apr 2014 | A1 |
20140250972 | Achanta | Sep 2014 | A1 |
20140301120 | Zhu | Oct 2014 | A1 |
20140319932 | Russell | Oct 2014 | A1 |
Entry |
---|
Greg Zweigle, Expand Synchrophasor Capabilities with the Substation Phasor Data Concentrator, Feb. 18, 2010. |
Andrew Swinghamer, Create a Synchrophasor Network with the SEL-3378 Synchrophasor Vector Processor, Aug. 6, 2009. |
Yanfeng Gong, Using Synchrophasor-Based Modal Analysis to Detect Unstable Power System Oscillations, Jun. 24, 2009. |
Schweitzer Engineering Laboratories, Inc., Case Study, Powergrid Corporation—India, Using Wide-Area Synchrophasor Measurements to Improve System Reliability, Sep. 10, 2010. |
Schweitzer Engineering Laboratories, Inc., SEL-3378 Instruction Manual, Apr. 4, 2008. |
Schweitzer Engineering Laboratories, Inc., SEL-3530 Real-Time Automation Controller RTAC Instruction Manual, Sep. 15, 2009. |
Terry L. Conrad, Distributed State Estimator at U.S. Virgin Islands Water and Power Authority St. Thomas and St. John, NASPI Working Group Meeting, Mar. 7, 2008. |
A.P. Sakis Meliopoulos, George J. Cokkinides, Floyd Galvan, Bruce Fardanesh, Distributed State Estimator-Advances and Demonstration, 41st Annual Hawaii International Conference on System Sciences, Jan. 2008. |
Pserc- Ali Abur andMLADEN Kezunovic, Sakis Meliopoulos, Enhanced State Estimation by Advanced Substation Monitoring, Power Systems Engineering Research Center, Nov. 2002. |
Saman A. Zonouz and William H. Sanders, A Kalman-based Coordination for Hierarchical State Estimation: Algorithm and Analysis, 41st Annual Hawaii International Conference on System Sciences, Jan. 2008. |
ABB: Improved Power System Performance through Wide Area Monitoring, Protection, and Control, Jan. 2004. |
ABB, Wide Area Measurement, Monitoring, Protection and Control Industrial It for Energy System Operation—Jan. 2003. |
Sasa Jakovljevic, Mladen Kezunovic, Software for Enhanced Monitoring in Integrated Substations, 2003 IEEE Bologna Power Tech Conference, Jun. 23-26, 2003. |
Y. Wu, M. Kezunovic, Automatic Simulation of IED Measurements for Substation Data Integration Studies, Power Engineering Society General Meeting, Jun. 12-16, 2005. |
Sasa Jakovljevic, Data Collecting and Processing for Substation Integration Enhancement, May 2003. |
M. Kezunovic, G. Latisko, Automated Monitoring Functions for Improved Power System Operation and Control, Power Engineering Society General Meeting, Jun. 12-16, 2005. |
PCT/US2011/046437 International Search Report and Written Opinion of the International Searching Authority, Patent Cooperation Treaty, Dec. 16, 2011. |
Arshad Saleem, Agent Services for Situation Aware Control of Power Systems with Distributed Generation, 2009 IEEE [retrieved on Jan. 28, 2013 from the internet <url:http://orbi.dtu.dk/fedora/objects/orbit:55496/datastreams/file—3761170/content> ]. |
Chanin Choniratisai, HVDC Stability Functions and Implementation in Thailand, CEPSI 2004. [retrieved on Jan. 28, 2013 from the internet <URL://http://www.researchgate.net/CEPSI2004> ]. |
PCT/US2012/0068962 International Search Report and Written Opinion of the International Searching Authority, Patent Cooperation Treaty, Feb. 25, 2013. |
G.T. Heydt, C.C. Liu, A.G. Phadke, V. Vittal, Solutions for the Crisis in Electric Power Supply, IEEE Computer Applications in Power, Jul. 2001. |
Luc Meysenc, M. Jylhakallio, Peter Barbosa, Power Electronics Cooling Effectiveness Versus Thermal Inertia, IEEE Transactions on Power Electronics, vol. 20, No. 3, May 2005. |
R.A. Walling, N.W. Miller, Distributed Generation Islanding-Implications on Power System Dynamic Performance, IEEE Power Enginnering Society Summer Meeting vol. 1, Jul. 25, 2002. |
M. Ezzt, M.I. Marei, M. Abdel-Rahman, M.M. Mansour, A Hybrid Strategy for Distributed Generators Islanding Detection, IEEE PES Power Africa 2007 Conference and Exposition Johannesburg, South Africa, May 16-20, 2007. |
Mats Larsson, Christian Rehtanz, Predictive Frequency Stability Control Based on Wide-Area Phasor Measurements, IEEE Power Engineering Society Summer Meeting vol. 1, Jul. 2002. |
Jun Yin, Liuchen Chang, Chris Diduch, Recent Developments in Islanding Detection for Distributed Power Generation, IEEE Power Engineering, Jul. 2004. |
Xiaoming Wang, Vijay Vittal, System Islanding Using Minimal Cutsets with Minimum Net Flow, IEEE Power Systems Conference and Exposition, Oct. 2004. |
Dongchen Hu, Vaithianathan Venkatasubramanian, New Wide Area Algorithms for Detection and Mitigation of Angle Instability Using Synchrophasors, IEEE Power Engineering Society General Meeting, Jun. 2007. |
Robert J. Best, D. John Morrow, David J. McGowan, Peter A. Crossley, Synchronous Islanded Operation of a Diesel Generator, IEEE Transactions on Power Systems, vol. 22, No. 4, Nov. 2007. |
Olof Samuelsson, Helga Johannsdottir, Nils Gustavsson, Thorhallur Hrafnsson, Daniel Karlsson, Mike Kockott, Johan Salj, Arve Sollie, Power System Damping in Iceland Based on Phasor Measurements, Jul. 2, 2006. |
Gabriel Benmouyal, E. O. Schweitzer, A. Guzman, Synchronized Phasor Measurement in Protective Relays for Protection, Control, and Analysis of Electric Power Systems, 29th Annual Western Protective Relay Conference, Oct. 22-24, 2002. |
A.G. Phadke, Synchronized Phasor Measurement in Power Systems, IEEE Comput. Appl., vol. 6, No. 2, pp. 10-15, Apr. 1993. |
Edmund O. Schweitzer, III, David Whitehead, Armando Guzman, Yanfeng Gong, Marcos Donolo, Advanced Real-Time Synchrophasor Applications, Western Protective Relay Conference, Oct. 2008. |
Dale Williston, Dale Finney, Consequences of Out-of-Phase Reclosing on Feeders with Distributed Generators, Dec. 3, 2010. |
Michael J. Thompson, Fundamentals and Advancements in Generator Synchronizing Systems, Dec. 9, 2010. |
Michael J. Thompson, New Developments in Generator Synchronizing Systems, Feb. 10, 2011. |
PCT/US2012/055107 Patent Cooperation Treaty, International Search Report and Written Opinion of the International Searching Authority, Nov. 23, 2012. |
Number | Date | Country | |
---|---|---|---|
20160246666 A1 | Aug 2016 | US |