WO2020162937A1 - Système de validation automatisée de modèle pour réseau électrique - Google Patents

Système de validation automatisée de modèle pour réseau électrique Download PDF

Info

Publication number
WO2020162937A1
WO2020162937A1 PCT/US2019/017008 US2019017008W WO2020162937A1 WO 2020162937 A1 WO2020162937 A1 WO 2020162937A1 US 2019017008 W US2019017008 W US 2019017008W WO 2020162937 A1 WO2020162937 A1 WO 2020162937A1
Authority
WO
WIPO (PCT)
Prior art keywords
pmu
power system
power
event
data
Prior art date
Application number
PCT/US2019/017008
Other languages
English (en)
Inventor
Honggang Wang
Weizhong Yan
Manu PARASHAR
Radhakrishnan Srinivasan
Original Assignee
General Electric Company
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by General Electric Company filed Critical General Electric Company
Priority to PCT/US2019/017008 priority Critical patent/WO2020162937A1/fr
Publication of WO2020162937A1 publication Critical patent/WO2020162937A1/fr

Links

Classifications

    • HELECTRICITY
    • H02GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02JCIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J3/00Circuit arrangements for ac mains or ac distribution networks
    • HELECTRICITY
    • H02GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02JCIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J13/00Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network
    • H02J13/00006Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network characterised by information or instructions transport means between the monitoring, controlling or managing units and monitored, controlled or operated power network element or electrical equipment
    • HELECTRICITY
    • H02GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02JCIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J2203/00Indexing scheme relating to details of circuit arrangements for AC mains or AC distribution networks
    • H02J2203/20Simulating, e g planning, reliability check, modelling or computer assisted design [CAD]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02EREDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
    • Y02E40/00Technologies for an efficient electrical power generation, transmission or distribution
    • Y02E40/70Smart grids as climate change mitigation technology in the energy generation sector
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02EREDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
    • Y02E60/00Enabling technologies; Technologies with a potential or indirect contribution to GHG emissions mitigation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04SSYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S10/00Systems supporting electrical power generation, transmission or distribution
    • Y04S10/22Flexible AC transmission systems [FACTS] or power factor or reactive power compensating or correcting units
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04SSYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
    • Y04S40/12Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them characterised by data transport means between the monitoring, controlling or managing units and monitored, controlled or operated electrical equipment
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04SSYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
    • Y04S40/20Information technology specific aspects, e.g. CAD, simulation, modelling, system security

Definitions

  • Grid planning and operating decisions are often based on the results of power system simulations. These simulations rely on power system models to predict system performance during anticipated disturbance events. Both technical and commercial segments of the industry must be confident that the dynamic simulation models, including all of their data, are accurate and up-to-date. Optimistic models can result in grid undcr-investment or unsafe operating conditions and ultimately widespread power outages. On the other hand, pessimistic models and assumptions can result in overly' conservative grid operation and under-utilization of network capacity. Pessimistic models can also lead to unnecessary capital investment, thereby' increasing the cost of electric power. Therefore, realistic models arc needed for ensuring reliable and economic power system operation.
  • Power system models are the foundation of virtually all power system studies. Calculation of operating limits, planning for assessment of new generation and load growth, performance assessments of system integrity protection schemes (SIPS), and the like, depend on an approximate mathematical representation of the transmission, generation, and load of an electrical grid. Disturbances in the electrical grid provide an excellent opportunity to validate a power system model. In order to validate the power system model, disturbance data must be collected from appropriate systems on the grid, network topology information of tiie electrical grid must be collected, dynamic models at the time of the event must be collected, and sensor data must somehow be correlated to power system data on the grid. However, these processes arc typically performed by an operator (human) and often require significant amounts of time and cost. As a result, validation of power system models is not regularly performed.
  • the example embodiments describe a system which improves upon the prior art by auto-detecting a disturbance on the electrical grid, identifying phasor measurement units (PMUs) associated with the disturbance, and triggering an automated power system model validation based on disturbance data captured by the identified PMUs.
  • the system may identify one or more PMUs diat have relevant data associated with the disturbance based on a disturbance impact factor generated for the PMU.
  • the system may also automatically correlate the identified PMUs to one or more power generation systems on the electrical grid (e.g., substations, transmission lines, etc.) that are associated with the disturbance. The correlation may involve an automated tag-mapping process between PMU name tags and energy management system (EMS) name tags.
  • EMS energy management system
  • the system may automatically validate a power system model of the power generation systems based on the PMU data that is captured of the event.
  • a computing system may include a storage configured to store information about an event on an electrical grid, and a processor configured to, in response to the event on the electrical grid being detected, identify a PMU of the electrical grid based on a geographical location of the event, map the identified PMU to a power generation system on the electrical grid based on a tag of the identified PMU and a tag of the power generation system, and retrieve a power system model of the power generation system from a repositoiy. Furthermore, the processor may trigger a validation determination of the power system model based on event data sensed by the identified PMU.
  • a method may include, in response to an event on an electrical grid, identifying a PMU ofthe electrical grid based on a geographical location of the event, mapping the identified PMU to a power generation system onthe electrical grid based on a tag of the identified PMU and a tag of the power generation system, retrieving a power system model of the power generation system, and triggering a validation determination of the power system model of the power generation system based on event data sensed bythe identified PMU.
  • FIG. I is a diagram illustrating a system for delivering electricity to a customer in accordance with an example embodiment.
  • FIG. 2 is a diagram illustrating a network topology of an electrical grid in accordance with an example embodiment.
  • FIG. 3 is a diagram illustrating a system including an enhanced disturbance management (EDM) module in accordance with an example embodiment.
  • EDM enhanced disturbance management
  • FIG. 4 is a diagram illustrating a framework for validating power system models in accordance with an example embodiment.
  • FIG. 5 is a diagram illustrating an automated model validation system in accordance with an example embodiment.
  • FIG. 6 is a method for triggering validation of a power system model in accordance with an example embodiment.
  • FIG. 7 is a diagram illustrating a computing system for use in th me ethods and processed described herein.
  • FIG. 8 A is a diagram illustrating a process of tag-mapping in accordance with an example embodiment.
  • FIG. 8B is a diagram illustrating a human machine interface for automatic model validation in accordance with an example embodiment.
  • FIG. 9 is a diagram illustrating a human machine interface displaying calibration information in accordance whh an example embodiment.
  • FIG. 10 is a diagram illustrating table data stored in an AMV expert system in accordance with an example embodiment.
  • FIG. 11 is a diagram illustrating a system that includes an automatic model validation system in accordance with an example embodiment.
  • the example embodiments provide a framework for an automated model validation system which can detect a disturbance event and identify affected PMU locations based on disturbance information. For example, the system may select PMUs that have adequate responses to the event. The system may correlate (e.g., map) the selected PMUs to generator systems on the electrical grid using an automated tag-mapping operation which resolves differences between PMU names and EMS names for power generating systems on the grid. Based on the mapping, the system can carve out the subsystem(s) on the electrical grid that are affected by the disturbance and which should be validated.
  • the framework may include a data collection system which establishes a communication channel between existing EMS, PMU, and Enhanced Disturbance Monitoring (EDM) systems and automatically retrieves power system models of the subsystems affected by the disturbance.
  • EDM Enhanced Disturbance Monitoring
  • an automated model validation (AMV) system may validate the power system models based on the PMU data. When the AMV system determines a power system model is not valid, the AMV system may notify an operator thereof. As another option, the system may determine updated parameters for the invalid model which improve the model, and provide the results to the operator via a user interface, etc.
  • the behavior of power plants and electrical grids may change over time and should be checked and updated to assure that they remain accurate.
  • Engineers use the processes of validation and calibration to make sure that a power system model can accurately predict tire behavior of the modeled object (e.g., transmission system, generating unit, load, etc.)
  • Validation assures that the model accurately represents the operation of the real system including model structure, correct assumptions, and that th oeutput matches actual events.
  • a calibration process may be used to make minor adjustments to the model and its parameters so that the model continues to provide accurate outputs.
  • High-speed, time -synchronized data, collected using PMUs may facilitate model validation of the dynamic response to grid events. Grid operators may use, for example,
  • the transmission operators can use this calibrated generator or power system model for power system stability study based on N-k contingencies, in every 5 to 10 minutes. If there is a stability' issue (transient stability') for some specific contingency, the power flow may be redirected to relieve t shteress-limiting factors. For example, the output of some power generators will be adjusted to redirect the power flow. Alternatively, adding more capacity (more power lines) to the existing system can be used to increase the transmission capacity'.
  • the gnd operator can also diagnose the causes of operating events, such as wind-driven oscillations, and identify appropriate corrective measures before those oscillations spread to harm other assets or cause a loss of load.
  • devices may exchange information via any communication network which may be one or more of a Local Area Network (“LAN”), a Metropolitan Area Network (“MAN”), a Wide Area Network (“WAN”), a proprietary network, a Public Switched Telephone Network (“PSTN”), a Wireless Application Protocol (“WAP”) network, a Bluetooth network, a wireless LAN network, and/or an Internet Protocol (“IP”) network such as the Internet, an intranet, or an extranet.
  • LAN Local Area Network
  • MAN Metropolitan Area Network
  • WAN Wide Area Network
  • PSTN Public Switched Telephone Network
  • WAP Wireless Application Protocol
  • Bluetooth a Bluetooth network
  • wireless LAN network a wireless LAN network
  • IP Internet Protocol
  • any devices described herein may communicate via one or more such communication networks.
  • FIG. 1 is a diagram illustrating example embodiments of a power delivery- process 100 showing components that can facilitate the generation of power and the process of delivering power (e.g., delivering energy, electricity) to customer premises.
  • Electric power can be generated at a power generation facility, and then carried by transmission power lines to substations having transformers. A local distribution system of smaller, lower-voltage transmission lines and substations carry' power to the customer premises.
  • a power generation facility' 105 generates electricity to meet the power demands of customers.
  • a variety of facilities can generate electricity'.
  • power generation facilities 105 can include power plants that bum coal, oil, or natural gas.
  • Power generation facilities 105 can also comprise nuclear power plants, renewable sources of energy' such as hydroelectric dams, wind turbines, and solar panels, and the like. The location of these electricity' generators, and their distance from end users, can vary' widely.
  • the electricity' that is generated by the pow'er generation facility- 105 may be stepped up or stepped down by transformers (e.g., transformer 110) which may be located at power plant substations adjacent to (and connected via power lines to) the power plant.
  • transformers e.g., transformer 110
  • the transformer 110 is a step-up transformer that will "step up" the voltage of the electricity.
  • power lines e.g., metallic wires that conduct electricity
  • the power loss is proportional to the amount of current being carried. Power companies keep the current low and compensate by stepping up the voltage.
  • the electricity is typically carried over long distances by high voltage power transmission lines, typically supported and elevated by transmission towers (e.g., transmission towers 115) that can be of various dimensions, materials, and heights.
  • transmission towers e.g., transmission towers 115
  • the voltage may be gradually reduced by step-down transformers as the electricity approaches customer premises.
  • Transmission substations contain step-down transformers (e.g., transmission substation step-down transformer 120) that reduce the voltage of the electricity'.
  • the electricity can then be distributed on lower- voltage power lines.
  • a typical transmission substation can serve tens of thousands of customers.
  • the electricity' leaving transmission substations can travel through power lines to distribution substations.
  • Distribution substations contain step-down transformers (e.g., distribution substation step-down transformer 125) that further reduce the voltage of electricity and distribute the power to cities and towns through main power lines, which can serve hundreds of customers. Distribution lines car lower voltage power to clusters of homes and businesses, and are typically supported by wooden poles. Of note, power lines can also be buried under the ground. Of note, substations can contain a variety of other equipment, including switches, breakers, regulators, batteries, etc.
  • the voltage from a branch line can further be reduced by transformers that are mounted on poles (e.g., step-down transformer on pole 130) that connect customer premises (e.g., customer premises 135) through a service drop power line.
  • Customer premises 135 can be of any type and variety.
  • Customer premises can be a residential customer premises, such as residential houses.
  • Customer premises can be an industrial customer premises, such as factories.
  • Customer premises can be commercial customer premises, such as an office building. If a particular customer premises has a heavier load (e.g., has a higher demand for power), then a larger transformer, instead of a pole transformer, might service that particular customer premises.
  • FIG. 2 depicts an illustration of a power grid system 200 (e.g., an electrical grid) comprising multitudes of nodes 201-210.
  • a node may represent a power generation facility ' , transmission substation, a distribution substation, and t lhikee, and is intended to convey that such facilities and substations can be interconnected.
  • a node may be referred to as a“power system node.”
  • the power grid system 200 can follow a structural topology, influenced by factors such as budget, system reliability, load demand (demand for power), land, and geology.
  • the structural topology' in many cities and towns, for example many of those in North America, tends to follow a classic radial topology.
  • a substation receives its power from a power generation facility, and the power may be stepped down with a transformer and sent through lines that spread out in all directions across the countryside. These feeders carr three-phase power and tend to follow major streets near the substation. As the distance from the substation grows, the fanout continues as smaller laterals spread out to cover areas missed by the feeders. This tree-like structure grows outward from the substation, but a single power failure can render inoperable entire branches of the tree. For reliability reasons, there are often unused backup connections from one substation to a nearby substation.
  • This backup connection can be enabled in case of an emergency, such that a part of a substation's service area can be fed by another substation in case of any pow’er failure events. Redundancy allows line failures to occur and pow er to be rerouted w r hile workmen restore to sendee damaged or deactivated components. Neighboring pow'er utilities also typically link their grids, thereby assisting one another to maintain a balance between power generation supply and loads (e.g., customer demand). Other topologies can be mesh topologies, looped systems (mostly found in Europe) and ring networks.
  • the result can be an interconnected power grid system 200 that can form complex networks of pow er plants and transformers connected by hundreds of thousands of miles of high-voltage transmission lines. While these interconnections can be useful in situations, the danger or risk can comprise the possibility' that a shutdow n in one sector could rapidly spread to other sectors, leading to massive power failures in a wide area.
  • measurement devices 220A-220E disposed within the power grid system 200 .
  • a variety of sensors, monitoring devices and measurement devices collectively referred to herein as
  • measurement devices can be located at one or more nodes (e.g., nodes 201-210), in between nodes on lines, and the like, and can be used to provide monitoring data related to pow er flow measurements, or monitor the condition of one or more aspects of a power grid system.
  • the measurement devices 220A-220E may be deployed within, or adjacent to, power transmission components (e.g., generating units, transformers, circuit breakers), including at substations. In some examples, the measurement devices 220A-220E can also be deployed along distribution lines.
  • the measurement devices 220A-220E may include sensors that measure a range of parameters such as magnitude and phase angle of voltage, current, harmonic distortion, real and reactive power, power factor, and fault current.
  • sensors include, but are not limited to, voltage and current sensors, PMUs, transformer-Metal Insulated Semiconducting (MIS) gas in oil sensors, circuit breaker sulfur hexafluoride density sensors, conductor temperature and current sensors that record overhead transmission conductor temperatures and current magnitudes, overhead insulator leakage current sensors, Transmission Line Surge Arrester (TLSA) sensors, and the like.
  • MIS transformer-Metal Insulated Semiconducting
  • the power grid system 200 may include the measurement devices 220A-220E located in various parts (e.g., such as nodes) throughout the grid.
  • the measurement devices 220A-220E can be coupled via a network of transmission lines, as well as through wireless and wired communications mediums (e.g., cellular, ethemet, etc.).
  • a measurement device 220E can be coupled via a transmission line 222 from a network of transmission lines associated with the nodes 201-210.
  • a subset of the measurement devices can be associated with a sector of the power grid system 200.
  • a measurement device may include a phasor measurement unit (PMU) which can capture data of a disturbance event.
  • PMUs typically have a naming convention based on PMU information which is defined by a regional transmission authority.
  • power system nodes 201- 210 have a naming convention based on utility companies.
  • the measurement devices 220A-220E may have names that are not identical to or correlated with the names of the power system nodes 201-210.
  • the system can perform automated tag mapping to correlate the measurement devices 220A-220E with corresponding power system nodes 201-210.
  • an Enhanced Disturbance Management (EDM) component e.g., module
  • read e.g., obtain
  • monitoring data for example, Supervisory Control and Data Acquisition (SCADA) system data, PMU-based data, topology' data, and the like
  • SCADA Supervisory Control and Data Acquisition
  • the monitoring data can comprise alarm data indicative of an electrical disturbance within the electrical power system, and topology data indicative of a topology of the electrical power system.
  • the EDM component can be operable to correlate the alarm data, which can relate to, for example, an angle disturbance alarm, or, for example, a frequency disturbance alarm, with a change in the topology data.
  • FIG. 3 illustrates a system 300 including an EDM module 316 in accordance with an example embodiment.
  • the EDM module 316 can determine a characterization (e.g., classification, causation) of the electrical disturbance in the pow'er grid system based on the correlating of the alarm data with th teopology' data, determining a coherency level representative of the degree of correlation between t ahlearm data and the topology data, determining a Disturbance Impact Factor (DIF) indicative of an impact of the electrical disturbance on a location in the pow'er grid system, and identify one or more sensors (PMUs) that have captured data of the disturbance.
  • DIF Disturbance Impact Factor
  • the EDM module 316 can further auto-map PMUs to one or more pow'er system nodes on the grid, retrieve power model information of the power system nodes, and validate the retrieved power model based on the PMU information of the disturbance.
  • the EMD module 316 can also store and display disturbance history', event history', and a variety of other statistical information related to disturbances and events, including on a graphical user interface, or in a generated report.
  • Measurement device 220 in FIG. 3 can obtain, monitor or facilitate the determination of electrical characteristics associated wtith the power grid system (e.g., the electrical pow'er system), w'hich can comprise, for example, power flow's, voltage current, harmonic distortion, frequency, real and reactive power, power factor, fault current, and phase angles. Measurement device 220 can also be associated with a protection relay, a Global Positioning System (GPS), a Phasor Data Concentrator (PDC), communication capabilities, or other functionalities.
  • GPS Global Positioning System
  • PDC Phasor Data Concentrator
  • Measurement devices 220 can provide real-time measurements of electrical characteristics or electrical parameters associated with the power grid system (e.g., the electrical power system).
  • the measurement device 220 can, for example, repeatedly obtain measurements from the power grid system (e.g., the electrical pow'er system) that can be used by the EDM module 316.
  • the data generated or obtained by the measurement device 220 can be coded data (e.g., encoded data) associated with the power grid system that can input (or be fed into) a traditional SCADA/EMS system.
  • the measurement device 220 can also be a PMU that repeatedly obtains subs-second measurements (e.g.. 30 times per second).
  • the PMU data can be fed into, or input into, applications (e.g., Wide Area Monitoring System (WAMS) and WAMS-related applications) that can utilize th meore dynamic PMU data (explained further below).
  • WAMS Wide Area Monitoring System
  • WAMS-related applications can utilize th meore dynamic PMU data (explained
  • the measurement device 220 includes a voltage sensor 302 and a current sensor 304 that feed data typically via other components, to, for example, a Supervisor ⁇ ' Control and Data Acquisition (SCADA) system (e.g., SCADA component 310). Voltage and current magnitudes can be measured and reported to a system operator every' few seconds by the SCADA component 310.
  • SCADA component 310 can provide functions such as data acquisition, control of power plants, and alarm display.
  • the SCADA component can also allow operators at a central control center to perform or facilitate management of energy flow in the power grid system. For example, operators can use a SCADA component (for example using a computer such as a laptop or desktop) to facilitate performance of certain tasks such opening or closing circuit breakers, or other switching operations that might divert the flow of electricity.
  • the SCADA component 310 can receive measurement data from Remote Terminal Units (RTUs) connected to sensors in the power grid system, Programmable Logic Controllers (PLCs) connected to sensors in the power grid system, or a communication system (e.g., a telemetry' system) associated with the power grid system.
  • RTUs Remote Terminal Units
  • PLCs Programmable Logic Controllers
  • a communication system e.g., a telemetry' system
  • PLCs and RTUs can be installed at power plants, substations, and the intersections of transmission and distribution lines, and can be connected to various sensors, including the voltage sensor 302 and the current sensor 304.
  • the PLCs and RTUs receive its data from the voltage and current sensors to which they are connected.
  • the PLCs and RTUs can convert the measured information to digital fonn for transmission of the data to the SCADA component.
  • the SCADA component 310 can also comprise central host server or servers called master terminal units (MTUs), sometimes also referred to as a SCADA center.
  • MTU master terminal units
  • the MTU can also send signals to PLCs and RTUs to control equipment through actuators and switchboxes.
  • the MTU can perform controlling, alarming, and networking with other nodes, etc.
  • the SCADA component 310 can monitor the PLCs and RTUs, and can send information or alarms back to operators over telecommunications channels.
  • the SCADA component 310 can also be associated with a system for monitoring or controlling devices in the power grid system, such as an Energy Management System (EMS).
  • EMS Energy Management System
  • An EMS can comprise one or more systems of computer-aided tools used by operators of the electric power grid systems to monitor, control, and optimize the performance ofthe generation or transmission system.
  • an EMS is also referred to as SCADA/EMS or EMS/SCADA.
  • SCADA/EMS or EMS/SCADA can also perform the functions of a SCADA.
  • a SCADA can be operable to send data (e.g., SCADA data) to the EMS, which can in turn provide the data to the EDM module 316.
  • EDM module 316 can be associated with other systems with which the EDM module 316 can be associated can comprise a situational awnreness system for the power grid system, a visualization system for t phoewer grid system, a monitoring system for the power grid system or a stability assessment system for the power grid system.
  • the SCADA component 310 can generate or provide SCADA data (e.g., SCADA DATA shown in FIG. 3) comprising, for example, real-time information (e.g., real time information associated with the devices in the power grid system) or sensor information (e.g., sensor information associated with the devices in the power grid system) that can be used by the EDM module 316.
  • SCADA data can be stored, for example, in a repository 314 (described further below ).
  • data determined or generated by the SCADA component 310 can be employed to facilitate generation of topology data (topology data is further described below) that can be employed by the EDM module 316 for enhanced disturbance management, which is further described below .
  • the measurement device 220 also includes one or more PMUs 306.
  • a PMU 306 can be a standalone device or may be integrated into another piece of equipment such as a protective relay. PMUs 306 can be employed at substations, and can provide input into one or more software tools (e.g., WAMS, SCADA, EMS, and other applications).
  • a PMU 306 can use voltage and current sensors (e.g., voltage sensors 302, current sensors 304) that can measure voltages and currents at principal intersecting locations (e.g., substations) on a power grid using a common time source for synchronization, and can output accurately time- stamped voltage and current phasors.
  • synchrophasor refers to the synchronized phasor measurements taken by the PMU 306, some have also used the term to describe the device itself. Because these phasors are truly synchronized, synchronized comparison of two quantities is possible in real time, and tins time synchronization allows synchronized realtime measurements of multiple remote measurement points on the grid.
  • the high sampling rates (e.g., 30 times a second) provides "sub-second" resolution in contrast with SCADA-based measurements.
  • SCADA-based measurements can be used to assess system conditions-such as: frequency changes, power in megawatts (MW), reactive power in mega volt ampere reactive (MVARs), voltage in kilovolts (KV), etc.
  • MW power in megawatts
  • MVARs reactive power in mega volt ampere reactive
  • KV voltage in kilovolts
  • PMU measurements can provide improved visibility into dynamic grid conditions and can allow for real-time wide area monitoring of power system dynamics.
  • synchrophasors account for the actual frequency of the power delivery system at the time of measurement.
  • phase angle differences between two distant PMUs can indicate the relative stress across the grid, even if the PMUs are not directly connected to each other by a single transmission line. This phase angle difference can be used to identify power grid instability', and a PMU can be used to generate an angle disturbance alarm (e.g., angle difference alarm) when it detects a phase angle difference.
  • an angle disturbance alarm e.g., angle difference alarm
  • Examples of disturbances that might cause the generation of an angle disturbance alarm can comprise, for example, a line out or line in disturbance (e.g., a line out disturbance in which a line that was in sendee has now gone out of sendee, or in th cease of a line in disturbance, in which case a line that was out of sendee has been brought back into sendee).
  • PMUs 306 can also be used to measure and detect frequency differences, resulting in frequency alarms being generated.
  • unit out and unit in disturbances can result in the generation of a frequency alarm (e.g., a generating unit was in sendee, but might have gone out of sendee, or a unit that was out of sendee has come back in to sendee-both can cause frequency disturbances in the system that can result in the generation of a frequency alarm.).
  • PMUs 306 can also be used to detect oscillation disturbances (e.g., oscillation in the voltage, frequency, real pow'er— any kind of oscillation), which can result in the generation of an alarm (e.g., oscillation alarm).
  • oscillation disturbances e.g., oscillation in the voltage, frequency, real pow'er— any kind of oscillation
  • oscillation alarm e.g., oscillation alarm
  • Several other types of alarms can be generated based on PMU data from PMU based measurements.
  • an angle or frequency disturbance alarm might not necessarily mean that a particular type of disturbance occurred, only that it is indicative of that ty pe of disturbance.
  • a frequency disturbance alarm if it is detected, it might not necessarily be a unit in or unit out disturbance, but may be a load in or load out disturbance.
  • IEEE Institute of Electrical and Electronics Engineers
  • PDCs 312 can comprise local PDCs at a substation.
  • PDCs 312 can be used to receive and time-synchronized PMU data from multiple PMUs 306 to produce a real-time, time-aligned output data stream.
  • a PDC can exchange phasor data with PDCs at other locations.
  • Multiple PDCs can also feed phasor data to a central PDC, which can be located at a control center.
  • multiple layers of concentration can be implemented within an individual synchrophasor data system.
  • the PMU data collected by the PDC 312 can feed into other systems, for example, a central PDC, corporate PDC, regional PDC, the SC ADA component 310 (optionally indicated by a dashed connector), energy- management system (EMS), synchrophasor applications software systems, a WAMS, the EDM module 316, or some other control center software system.
  • a central PDC corporate PDC, regional PDC, the SC ADA component 310 (optionally indicated by a dashed connector), energy- management system (EMS), synchrophasor applications software systems, a WAMS, the EDM module 316, or some other control center software system.
  • EMS energy- management system
  • synchrophasor applications software systems e.g., synchrophasor applications software systems
  • WAMS gigabytes
  • the measurement device 220, the SCADA component 310. and PDCs/Central PDCs 312, can provide data (e.g., real-time data associated with devices, meters, sensors or other equipment in the power grid system) (including SCADA data and topology data), that can be used by the EDM module 316 for enhanced disturbance management.
  • SCADA data and PMU data can be stored in one or more repositories 3014.
  • the SCADA data and PMU data can be stored into the repository' 314 by the SCADA component 310, or by the PDC 412
  • the EDM module 316 can have one or more components or modules that are operable to receive SCADA data and PMU data and store the data into the repository' 314 (indicated by dashed lines).
  • the repository' can comprise a local repository ⁇ , or a networked repository'.
  • the data on the repository 314 can be accessed by SCADA component 310, the PDCs 312, others systems (not shown), and optionally by example embodiments of the EDM module 316.
  • the EDM module 316 can be operable to send instructions to one or more other systems (e.g., SCADA component 310, PDCs 312) to retrieve data stored on the repository' 314 and provide it to the EDM module 316.
  • the EDM module 316 can facilitate retrieval of the data stored in repository ⁇ 314, directly.
  • the data stored in the repository 314 can be associated SCADA data and PMU data.
  • the data can be indicative of measurements by measurement device 220 that are repeatedly obtained from a power grid system.
  • the data in repository 314 can comprise PMU/SCADA -based equipment data, such as, for example, data associated with a particular unit, line, transformer, or load within a power grid system (e.g., power grid system 200).
  • the data can comprise voltage
  • the data can be location-tagged. For example, it can comprise a station identification of a particular station in which a power delivery device being measured is located (e.g., "CANADA8").
  • the data can comprise a particular node number designated for a location.
  • the data can comprise the identity' of the measure equipment (e.g., the identification number of a circuit breaker associated with an equipment).
  • the data can also be time-tagged, indicating the time at which the data was measured by a measurement device.
  • the PMU/SCADA-based equipment data can also contain, for example, information regarding a particular measurement device (e.g., a PMU ID identifying the PMU from which measurements were taken).
  • the data stored in repository 314 can comprise not only collected and measured data from various measurement devices 220, the data can also comprise data derived from that collected and measured data.
  • the data derived can comprise topology data (e.g., PMU/SCADA-based topology data), event data, and event analysis data, and EDM data (data generated by EDM module 316).
  • the repository 314 can contain topology data (e.g., PMU/SCADA-based topology data) indicative of a topology for the power grid system 200.
  • the topology of a power grid system can relate to the interconnections among power system components, such as generators, transformers, busbars, transmission lines, and loads. This topology can be obtained by determining the status of the switching components responsible for maintaining the connectivity status within the network.
  • the switching components can be circuit breakers that are used to connect (or disconnect) any power system component (e.g., unit, line, transformer, etc.) to or from the rest of th peower system network.
  • Typical ways of determining topology can be by monitoring of th DCrcuit breaker status, which can be done using measurement devices and components associated with those devices (e.g., RTUs,
  • the topology' data can be indicative of an arrangement (e.g., structural topology', such as radial, tree, etc.) or a power status of devices in the power grid system.
  • Connectivity information or switching operation information originating from one or more measurement devices 220 can be used to generate the topology data.
  • the topology data can be based on a location of devices in the power grid system, a connection status of devices in the power grid system or a connectivity state of devices in the power grid system (e.g., devices that receive or process power distributed in throughout the power grid system, such as transformers and breakers).
  • the topology data can indicate where devices are located, and which devices in the power grid system are connected to other devices in the power grid system (e.g., where devices in the power grid system are connected, etc.) or which devices in the power grid system are associated with a powered grid connection.
  • the topology data can further comprise the connection status of devices (e.g., a transformer, etc.) that facilitate power delivery in the power grid system, and th setatuses for switching operations associated with devices in the power grid system (e.g., an operation to interrupt, energize or de-energize or connect or disconnect) a portion of the power grid system by connecting or disconnecting one or more devices in the power grid system (e.g., open or close one or more switches associated with a device in the power grid system, connect or disconnect one or more transmission lines associated with a device in the power grid system etc.).
  • the topology data can provide connectivity states of the devices in the power grid system (e.g., based on connection points, based on busses, etc.).
  • the repository 314 can contain a variety of event and event analysis data, which can be derived based on PMU data, and in some embodiments, other data as well (e.g., SCADA data, other measurement data, etc.).
  • the data can comprise information regarding events related to the power grid system 200.
  • An event can comprise, for example, one or more disturbances to the power grid system.
  • a disturbance can comprise, for example, a line disturbance (e.g., line in, or line out), a unit disturbance (e.g., unit in or unit out), or load disturbance (load in or load out).
  • the event and event analysis data can also comprise EDM data, which can be data related to events.
  • the various data stored in the repositorz 314, including equipment data, topology data, event data, event analysis data, EDM data, and other data, can be inputs into the various functionalities and operations that can be performed by the EDM module 316.
  • FIG. 4 illustrates an Automatic Model Validation (AMV)framework 400 for validating power system models in accordance with an example embodiment.
  • the framework 400 may be a ffamew ' ork that implements or otherwise includes an EDM component such as EDM module 316 shown in FIG. 3.
  • the AMV framew ork includes a disturbance event detection module 410, a PMU selection module 411, a tag mapping module 412, a data file collection module 413, a subsystem definition module 414, a model validation module 415, and a reporting module 416.
  • the disturbance event detection module 410 of the EDM can respond to the alarm by correlating the alarm with the change in topology (e.g., topology data such as equipment energization status, equipment connection status, etc.) of the system that potentially gave rise to that alarm.
  • topology e.g., topology data such as equipment energization status, equipment connection status, etc.
  • This correlation of PMU, equipment data, and topology’ data can provide context to an alarm, and can be used to associate information with the event that comprises the following: a disturbance epicenter; a disturbance magnitude; a disturbance impact; and an event spread.
  • the disturbance epicenter comprises information about the detection time of an event along with the epicenter of the event, including the exact cause (e.g., characterization) and location (e.g., localization) of the event, wherein an event can be comprised of one or more disturbances.
  • an event can be comprised of one or more disturbances.
  • a disturbance at one location can lead to a disturbance at another location, and so on.
  • the disturbance event detection module 410 can attempt to determine a cause and categorize tire disturbance as a line in/out, unit in/out, or load in/out, and also provide a coherency indicator that indicates how likely the disturbance is of a particular characterization.
  • PMU data can be correlated with other data, such as SCADA data, winch includes topology data.
  • PMUs are monitoring tire effect of something that happened on the grid (e.g., an angle disturbance alarm or a frequency disturbance alarm).
  • SCADA data can provide infomration on the topology (e.g., topology data, e.g., where the unit, line, or a transformer, and what circuit breaker is connected or involved), and how the topology reacted to a disturbance (e.g., what are the topological changes that have taken place).
  • the disturbance event monitoring module 410 can also provide a coherency indicator that indicates how likely the disturbance is of a particular characterization.
  • PMU-based data can result in the generation an angle disturbance alarm, and can also generate a frequency disturbance alarm.
  • a frequency disturbance alarm is generated, and the disturbance event monitoring module 410 correlates the PMU alarm with a change in topology that indicated that a unit has come out of service, this correlation is high because generating unit trips can cause a frequency alarm.
  • the coherency is thus indicated as high for frequency because the PMU alarm and the topology change both match well with a cause (unit out) and effect (frequency alarm).
  • the disturbance event monitoring module 410 can account for multiple scenarios.
  • An event can also comprise more than one disturbances, in which all the disturbances are part of one event.
  • PMU detections e.g., measurements
  • the disturbance event monitoring module 410 of the EDM can utilize the topology data (e.g., the equipment status, the breaker status, the topology exchanged etc.) to determine if the disturbances are part of the same event. If in the subsequent cycles the topology’ does not change any more, despite still receiving new alarms, then that might be an indication that the same disturbances that are resulting the continuous generation of the alarms (e.g., as opposed to different disturbances associated with a different event impacting other locations).
  • Overlapping e.g., correlating, overlaying
  • the topology changes on top of the PMU based alarms can thus be a way to validate the alarms that are coming from the PMUs; PMU based alarms would still be generated, when there really are no more disturbances after a period of time.
  • the information about the disturbance epicenter can be at a granularity level that comprises information regarding the epicenter of an event, for example, the disturbance type, the equipment, the circuit breaker, the name or designation of the station, the voltage level associated with the station (e.g., 500 kV), and the name or designation of the node.
  • Die information can be derived from using, for example, PMU data, SCADA Data, and topology' data.
  • differences in, for example, angle, frequency, etc. can inform as to whether there is a disturbance event, which might be a line in/out, unit in/out, or load in/out, each of which can lead to an impact on certain electrical parameters, comprising, for example, change in real power, reactive power, frequency, and voltage per unit.
  • Time synchronized information reported by the measurement devices can be used to determine which equipment w'as impacted first in time.
  • Topology' information can be used to determine whether other equipment (including at other stations or nodes) connected with the equipment that w'as impacted first in time also experienced a disturbance.
  • An event can comprise one or more disturbances.
  • the disturbance event monitoring module 410 can use topology information and time synchronized information, to detennine that several equipment all comiected together experienced a disturbance, and that one equipment was impacted first, and then a second equipment connected to the first one experienced a disturbance next, then a diird equipment connected to the second. By making these determinations, an epicenter— the source of the event-can be determined.
  • the disturbance event monitoring module 410 can also be operable to provide a disturbance magnitude for each disturbance.
  • disturbance magnitude information comprising information about the change in electrical parameters (e.g. change in real power, change in reactive power, and change in voltage) can be determined by the disturbance event monitoring module 410.
  • the magnitude information can be for the disturbance epicenter, for example.
  • the magnitude information can also be for the most impacted PMU location, for example.
  • the disturbance event monitoring module 410 can also be operable to determine disturbance impact information, which can comprise information about the impact of the disturbance event at pre-specified and measured key locations in the system using a disturbance impact factor (DIF) metric, which can be a function of the change in power, voltage, real power, reactive power, and voltage, or some other parameter (e.g., electrical parameter, custom-designed parameter, etc.) with reference to the point of disturbance.
  • DIF disturbance impact factor
  • the DIF reflects the impact of each disturbance in an event on a PMU location (based on user defined weights and steady-state changes in the power system parameters dining the
  • the DIF PMU BUS i is the disturbance impact factor associate with a particular PMU. It is calculated, for example, by multiplying weighting factor W 1 multiplied against the change in real power of the PMU over the change in real power of the disturbance location, added to a weighting factor W2 multiplied against a change in quality Q at the PMU over the change in quality at the disturbance location, added to a weighting factor W3 multiplied against a change in voltage at the PMU over the change in voltage of the disturbance location.
  • Each of the weighting factors Wl, W2, and W3 can be set (e.g., set by a power systems operator). Again, other factors can be accounted for when calculating a disturbance impact factor, which can depend on customer or user choice or design.
  • the disturbance event monitoring module 410 can also be operable to determine event spread information.
  • Event spread information can comprise information about the spread or scope of the event (e.g., whether the event is a local event or a wide area event).
  • a local event can be an event wherein only one location (e.g., one substation) is impacted, whereas a wide-spread event can be an event in which multiple locations have been impacted.
  • Event spread information can also include information as to whether the event involves different types of equipment (e.g., a line and a load simultaneously, etc.).
  • each new disturbance may be appended to an event history archive in a chronological maimer, which can enable a post-event analysis to be performed.
  • the information archived for each disturbance can be as follows: event detection time; correlation of system topological disturbances in the event with PMU-based alarms; disturbance type, location, and magnitude; most impacted location (amongst the pre-specified list of key locations) due to the disturbance.
  • the PMU selection module 411 may select or otherwise identify PMUs on the electrical grid which are affected by a disturbance event. For example, the PMU selection module 411 may identify PMUs that see adequate disturbance information which can be used for performing model validation of a device (generator, transmission system, load, etc.) which is associated with the PMU. For each of the selected PMUs, the PMU selection module 411 may determine whether there is a need to proceed to model validation. For example, the PMU selection module 411 may compare a disturbance impact factor of a selected PMU to a predefined threshold.
  • the PMU selection module 411 may select the PMU (and its related device(s) as a candidate for model validation.
  • the PMU selection module 411 may execute a machine learning algorithm to compare the features of the event and the associated network topology with features of existing events in a database.
  • the tag mapping module 412 may correlate a tag of an identified PMUs with a tag of one or more power system nodes on the electrical grid.
  • a unique generator may be uniquely defined by both the generator name and the name of the station it is directly tied to. The needs for a tag mapping function arises from the potentially different naming conventions from three different entities.
  • th neames of power system nodes such as generators, substations, etc., are defined by a generator owner (GO), while their
  • EMS corresponding names in the EMS are defined by the utilities.
  • the names of the PMU and related substation/generators are defined by a third party -regional transmission owner (RTO), which is more recently dian the previous two.
  • RTO third party -regional transmission owner
  • the name convention for power system node tags in EMS is typically limited in size (e.g., 8 bits, etc.), while the names in the RTO s PMU database tends to have more flexibility allowing for larger-sized tag names.
  • the PMU tags must be mapped to power system node tags to associate the event disturbance data captured by the PMU with one or more elements on the pow'cr grid (generator, substation, etc.).
  • the tag mapping module 412 of the example embodiments performs an automated tag-mapping process to automatically associated the selected PMUs with corresponding subsystems on the electrical grid.
  • the auto tag mapping process from EMS system to RTO’s PMU database is described here after the identification of grid event and selection of PMU and the affected station from EMS (as described in step 410 and 411 in Fig. 4), Substation names may be retrieved for the EMS system, and PMU names may be retrieved from a RTO’s PMU database.
  • Name variants of the generator and the station may be generated for pairs by the tag mapping module 412 based on a database or predefined location dictionary. The name variants are also called name augmentation. The augmented name may then be correlated to the names in the ROT’s PMU database based on the word, term and contextual association between word and terms.
  • the similarity-based metrics such as cosine similarity- between the word and terms can be used.
  • a correlation vector may be used for each pair of PMU and EMS system, and the highest correlated matched pair is the mapping result.
  • Other approaches like rule-based inference, fuzzy logic can also be used to facilitate the mapping decision.
  • Results of the tag mapping may be output to the user interface 430 to enable a user to review and correct mapping results.
  • mapped pairs may be added to a database (e.g., AMV database 420) for future use.
  • the data file collection module 413 may establish connections with existing databases and retrieve naming information, power system model information, network topology information, and the like, w'hich can be used by the different components of the EDM shown in FIG. 4.
  • FIG. 5 shows an example of an architecture of a file collection system (AMV module 536) which further includes elements from the EDM incorporated therein for performing automated power system model validation.
  • the AMV module 536 may include or otherwise be connected to the file collection system 413 shown in FIG. 4.
  • current and voltage sensors 510 may acquire voltage data, current data, and the like, from the electrical grid.
  • the data may be based on RTUs 512, PMUs 514, SCADA 516, PDC 518, and the like.
  • the AMV module 536 may identify and retrieve PMU data for a period of time associated with the detected disturbance. The onset and clearing of disturbances may be performed on a regular basis. Once a disturbance time period is identified, the AMV module 536.
  • the AMV module 536 may retrieve
  • synchrophasor data from the synchrophasor repository' 526 to identify only pow'er system nodes where disturbances are observed and whose dynamic model can be validated.
  • a network topology model may be retrieved by th AeMV 536 in this example.
  • the AMV 536 may include the data file collection module 413 shown in FIG. 4.
  • disturbance information from disturbance monitoring 524 may be retrieved by the AMV 536.
  • the AMV 536 interconnects widi existing storage modules of a pow'er system.
  • the EDM may export a time-stamped, topology solved model (power system model) from the EMS topology-solved network model repository 530.
  • the network model may be in a standard format (CIM, PSS/e, etc.) and may be a format of the network at the time the disturbance is detected. Meanwhile, a dynamic model may be retrieved as well.
  • an EMS that is armed to run real-time transient stability’ may have a dynamic model repository ' 534 which can be configured to pick dynamic models from a preconfigured network location.
  • the model validation module 415, the reporting module 416, or the like, from the system 400 may provide subscription services for other entities such as GOs, TSOs, RTOs, and the like.
  • the subscription services may provide calibration information tag-mapping information, PMU information, and the like, to the other systems that operate and have interest in the electrical power grid.
  • the subsystem definition module 414 may carve out which subsystems (generators, substations, etc.) should have power system models validated.
  • the subsystem module 414 may carve out and identify the subsystems based on PMU selection and tag mapping that is performed by the PMU selection module 411 and the lag mapping module 412.
  • the power system models collected by the file collection unit 413 may associated with the subsy stems for validation and calibration.
  • the model validation module 415 may automatically determine whether a power sy stem model of a subsystem (power system node) is valid.
  • the model validation module 415 may receive disturbance data monitored by one or more PMUs coupled to an electrical power distribution grid may be received.
  • the disturbance data can include voltage (“V”), frequency (“/“), and/or active and nonactivc reactive (“P” and“Q”) power measurements from one or more points of interest (POl) on the electrical power grid.
  • a playback simulation using default model parameters and existing transient simulation software can be performed. Those default parameters can be the current parameters incorporated in the power system model.
  • the current parameters can be stored in a model parameter record.
  • the simulation can be done by a power system simulation engine, including GE PSLF, Pow er Tech TSAT and Siemens PIT PSS/E, to perform a real-time power system simulation scenario.
  • the model v alidation module 415 may also comprise of the model calibration unit with three functionalities.
  • the first functionality is an event screening tool to select characteristics of disturbance event from a library of recorded event data. This functionality clusters similar events and determines the set of most representative events from the available measurements.
  • the second functionality is a preconditioning tool for the parameter identifiabilify study. When implementing this functionality, a global quantification of parameter sensitivity magnitude and dependency will be achieved.
  • the third functionality is a tool for simultaneous tuning of models using an augmented event comprised of multiple events.
  • event screening can be implemented during the simulation to provide computational efficiency. If hundreds of events are stitched together and fed into the calibration algorithm unsclcctivcly, the algorithm may not be able to converge. To maintain the number of events manageable and still keep an acceptable representation of all the events, a screening procedure may be performed to select the most characteristic events among all. Depending on the type of events, the measurement data could have different characteristics. For example, if an event is a local oscillation, the oscillation frequency in the measurement data would be much faster as compared to an inter- area oscillation event. In some implementations, a K-medoids clustering algorithm can be utilized to group events with similar characteristic together, thus reducing the number of events to be calibrated.
  • the results of the simulated default model performance can be compared by the model validation module 415 to actual disturbance data measured on the power system.
  • the model validation module 415 can end parameter conditioning and wait for disturbance data Grom a subsequent event.
  • a predetermined threshold of accuracy e.g., specified by, for example, power system operators, designers, etc.
  • a parameter identifiabitity algorithm may be performed.
  • the parameter identifiability analysis can determine the differing effects that various parameters can have on power system model.
  • each parameter can represent a factor/coefficient in a term of a polynomial expression representing the power system model.
  • a parameter sensitivity study may be performed. The sensitivity study can vary ⁇ the value of the parameter, compare the power system model result to monitored data, and then determine the perturbation’s magnitude caused by the variation in parameter value.
  • playback simulation is conducted with the value of that parameter perturbed upward and downward. The difference in the model’s performance i.e., when compared to the measured disturbance data) between the up. and the down perturbation yields the trajectory sensitivity matrix.
  • the parameter identifiability analysis addresses two aspects: (a) magnitude of sensitivity' of output to parameter change; and (b) dependencies among different parameter sensitivities. For example, if the sensitivity' magnitude of a particular parameter is low, the parameter would appear in a row being close to zero in the parameter estimation problem’s Jacobian matrix Also, if some of the parameter sensitivities have dependencies, it reflects that there is a linear dependence among the corresponding rows of the Jacobian. Both these scenarios lead to singularity of the Jacobian matrix, making the estimation problem infeasible. Therefore, it may be important to select parameters which are highly sensitive as well as result in no dependencies among parameter sensitivities.
  • parameter values in the active power system model may be updated, and the system may generate a report and/or display of the estimated parameter values(s), confidence metrics, and the model error response as compared to the measured data.
  • the reporting module 416 may notify a user (via user interface 430) of the validity of a power system model that is determined by the EDM system. For example, the reporting module 416 may notify that a power system model is valid, invalid, and the like.
  • the reporting module 416 can provide additional information about a power system model.
  • the reporting module 416 may provide an update (to one or more parameters) of the power system model to be accepted by the user via the user interface 430.
  • the reporting module 416 can retrieve updated parameter information from the model validation module 415 and provide those to the user interface 430 to efficiently update a power system model on behalf of a user.
  • the model validation module 415, the reporting module 416, or the like, from the system 400 may provide subscription sendees for other entities such as GOs, TSOs, RTOs, and the like.
  • the subscription services may provide calibration information, tag-mapping information, PMU information, and the like, to the other systems that operate and have interest in the electrical power grid.
  • the system shown in FIG. 4 further includes an expert system 420 which includes an automated model validation (AMV) database 421 and an inference engine 422.
  • AMV database 421 may store information that is collected by the EDM such as disturbance information (DIF, PMU selection, tag dictionaries, etc.). Furthermore, reports and results generated by the model validation module 415 may be stored there as well.
  • the inference engine 422 may query a calibrated case and reuse a subsystem, which are stored in the AMV database 421.
  • the inference engine 422 may analyze a parameter change for a mapped power system node and adjust a threshold for the power system node to thereby update a power system model associated therewith. The update may be determined based on a DIF of a PMU associated with the power system node.
  • the inference engine 422 may provide rules, a knowledge base, and a learning algorithm for tag mapping between selected PMU tags and power system node tags.
  • the inference engine 422 may provide an initial value and other information to accelerate the model validation and calibration.
  • the inference engine 422 may extract event (disturbance) features, cluster events using similarity with previously detected events, and update clusters based on newly received event information.
  • FIG. 6 illustrates a method 600 for determining a predictive CFD flow in accordance with an example embodiment.
  • the method 600 may be perfonned by a database, a cloud platform, a server, a user device, a combination of devices, and the like.
  • the method may include, in response to an event on an electrical grid, identifying one or more PMUs of the electrical grid based on a geographical location of the event.
  • the one or more PMUs may be identified from a larger group of PMUs based on disturbance impact factor information at each of the PMUs.
  • PMUs having a DIF greater than a predetermined threshold may be identified/selected as having captured information associated with tire disturbance event based on the geographical proximity or location with respect to a location of the event.
  • the method may include mapping the identified PMU to a power system node on the electrical grid based on a tag of the identified PMU and a tag of the power system node.
  • the mapping may include determining a similarity' between a name of the identified PMU and respective names of a plurality of power system nodes on the electrical grid, and mapping the identified PMU to a power system node having a name that is most similar to the name of the identified PMU.
  • the mapping may include automated tag mapping a name of the identified PMU to a name of the power system node defined by an energy' management system (EMS).
  • EMS energy' management system
  • the method may include retrieving a power system model of the power system node, and in 640, the method may include triggering a validation determination of the power system model of the power system node based on event data sensed by the identified PMU. In some embodiments, the method may further include, in response to the triggering, determining whether the power system model of the power system node is to be calibrated based on a simulation of a default parameters of the pow'er system model with respect to the event data sensed by the identified PMU. In some embodiments, the method may further include in response to determining the power system model should be calibrated, identifying changes in values to one or more parameters of the power system model and outputting the identified changes in values for display via a user interface. For example, the power system model of the power system node may include one or more of a representation of transmission system components on the electrical grid, a representation of power generating components on the electrical grid, and a load representation at various locations on the electrical grid
  • FIG. 7 illustrates a computing system 700 that may be used in any of the methods and processes described herein, in accordance wdth an example embodiment.
  • the computing system 700 may be a database node, a server, a cloud platform, or the like.
  • the computing system 700 may be distributed across multiple computing devices such as multiple database nodes.
  • the computing system 700 includes a network interface 710, a processor 720, an input / output 730, and a storage device 740 such as an in -memory storage, and the like.
  • the computing system 700 may also include or be electronically connected to other components such as a display, an input unit(s), a receiver, a transmitter, a persistent disk, and the like.
  • the processor 720 may control the other components of the computing system 700.
  • the network interface 710 may transmit and receive data over a network such as the Internet, a private network, a public network, an enterprise network, and the like.
  • the network interface 710 may be a wireless interface, a wired interface, or a combination thereof.
  • the processor 720 may include one or more processing devices each including one or more processing cores. In some examples, the processor 720 is a multicore processor or a plurality of multicore processors. Also, the processor 720 may be fixed or it may be reconfigurable.
  • the input / output 730 may include an interface, a port, a cable, a bus, a board, a wire, and the like, for inputting and outputting data to and from the computing system 700.
  • data may be output to an embedded display of the computing system 700, an externally connected display, a display connected to the cloud, another device, and the like.
  • the network interface 710, the input / output 730, the storage 740, or a combination thereof, may interact with applications executing on other devices.
  • the storage device 740 is not limited to a particular storage device and may include any known memory’ device such as RAM, ROM, hard disk, and the like, and may or may not be included within a database system, a cloud environment, a web server, or the like.
  • the storage 740 may store software modules or other instructions which can be executed by the processor 720 to perform the method shown in FIG. 6. According to various embodiments,
  • the storage 740 may include a data store having a plurality of tables, partitions and sub-partitions.
  • the storage 740 may be used to store database records, items, entries, and the like.
  • the storage 740 may store information about an event on an electrical grid.
  • the event may be detected by the processor 720 based on a disturbance in one or more of power, voltage, and current on the electrical grid.
  • the processor 720 may, in response to the event being detected, identify one or more PMUs of the electrical grid which have data of the event based on a geographical location of the event.
  • the processor 720 may map the identified PMU to a power system node on the electrical grid based on a tag of the identified PMU and a tag of the power system node, and retrieve a power system model of the power system node from a repository.
  • the processor 720 may trigger a validation determination of the power system model based on event data sensed by the identified PMU.
  • the processor 720 may identify one or more PMUs affected by the event based on a disturbance impact factor at the one or more PMUs being greater than a predetermined threshold. In some embodiments, the processor 720 may determine a similarity between a name of the identified PMU and respective names of a plurality of power system nodes on the electrical grid, and map the identified PMU to a power system node having a name that is most similar to the name of the identified PMU.
  • the processor 720 may auto-tag map a name of the identified PMU to a name of the power system node defined by an energy management system (EMS).
  • EMS energy management system
  • the processor 720 may execute an automated power system model validation. For example, the processor 720 may determine whether the power system model of the power system node is to be calibrated based oil a simulation of a default parameters of the power system model with respect to the event data sensed by the identified PMU. In some embodiments, in response to determining the povrer system model should be calibrated, the processor 720 may identify changes in values to one or more parameters of the power system model and output the identified changes in values for display via a user interface.
  • the power system model of the power system may include a representation of transmission system components on the electrical grid, a representation of power generating components on the electrical grid, and a load representation at various locations on the electrical grid.
  • FIG. BA illustrates a process 800 of tag-mapping in accordance with an example embodiment.
  • three tables are shown that correspond to three separately stored and managed data stores (802, 804, and 806) which store generator information and its connected station information.
  • each row in EMS data table 802, PMU point of interest data table 804, and general information data table 806, characterizes a unique generator device name and its station name.
  • the first row in EMS data table 802 represents the generator device named with“ABCD” directly tied to Station“W SHORE .
  • the second row in EMS data table 802 represents the generator device named with“EFGH” directly tied to the same Station“W_SHORE”. Note that the name is shorter than 8 character due to historical naming convention reason; also note that by sampling using station name or device could not uniquely identify one single device. They have to be used collectively to uniquely characterize one generator device.
  • a PMU name and PMU ID may be able to link with different voltage and current sensors. This is because one PMU may have multiple channels, and each channel may measure one power line connecting to one generator device. As an example, one PMU name“ ELECTRICRD_A” consists three measurement channels: G345_U1_VP, G345_U2_VP, G345_U3_VP.
  • the general information data table 806 may be stored in the host computer managed by the RTO who also is responsible to define and manage the POI PMU s Information.
  • the goal of tag mapping is to match the identified row (or Station Device) with a certain row in the POI PMU Information.
  • Table 808 show's the mapping result corresponding to the illustrated example from data tables 802, 804, and 806.
  • the first row of 808 show's that the matched result from device named with“ABCD” linking to a station named with“W_SHORE” have been matched to a PMU Name of
  • the result of the tag mapping shown in FIG. 8A is that the three data tables 802, 804, and 806, from three differently owmed data stores may be mapped together and stored together as a single table 808.
  • the three tables 802, 804, and 806 become one table 808 that correspond to the mapping.
  • the order of the entries in the tables 802, 804, and/or 806 may change to align the entries together as a result of the tag mapping. For example, in the first row in 808, the device ABCD has been mapped from each of the tables into a same common row .
  • the system may perform a similarity analysis to identify most likely matches between the tags in the different tables 802, 804, and 806, for example.
  • the similarity- analysis may be based on term and contextual information of terms which describe the name of a PMU, a generator and a substation.
  • The“term” here may be a keyword, partial name, full name or an abbreviation of the name of a PMU, a generator and a substation.
  • the tag mapping process may have a function that leams from user inputs.
  • the automatic tag matching may have a mechanism of learning from user input and learning from historical data to help perform the tag mapping and identify similar tags.
  • FIG. 8B illustrates a human machine interface 850 for automatic model validation in accordance with an example embodiment.
  • the interface 850 may be output by a system described herein such as AMV module 536 described in FIG. 5.
  • the interface 850 may include tabs or pages for viewing and / or modifying disturbance information, PMU selection information, tag mapping information, file collection
  • the interface 850 may also include options for validating a power system model and calibrating the power system model in a case the power system model is not valid.
  • FIG. 9 illustrates a human machine interface 900 displaying calibration information in accordance with an example embodiment.
  • the interface 900 includes user-selectable options of validation, identifiability, and calibration options 910.
  • a customization area 920 allows for selection of a data file (e.g., associated with single or multiple events), a simulation, a calibration algorithm, etc. Selection of option (e.g., via touchscreen or computer mouse pointer 940) may result in the optimization criteria (e.g., a baseline approach, a smart weight, a faster solver, an enhanced version, etc.).
  • the display may further include graphical charts 940, 950 that show a model response result figure according to the user selected options (e.g., with a percent improvement in accuracy and time marked on the charts 940, 950).
  • the display 900 may also include a table 960 that shows performance in terms of deviation against measurement data, according to the user selected options, with a percentage improvement in accuracy and time included in th taeble 960.
  • The may also be user-selectable graphical icons allowing a user to visualize parameters 970 and/or export 980 the data.
  • FIG. 10 illustrates table data stored in an AMV expert system in accordance with an example embodiment.
  • the AMY expert system may be the AMV module 536 shown in FIG. 5.
  • a table is shown that represents the data store 1000 that may be stored according to some embodiments.
  • the table may include, for example, entries identifying industrial assets or other systems to be protected.
  • the table may also define fields 1002, 1004, 1006, 1008, 1010, 1012, 1014, 1016, 1018, 1020, 1022,1024 for each of the entries.
  • the fields 1002, 1004, 1006, 1008, 1010, 1012, 1014, 1016, 1018, 1020, 1022,1024 may, according to some embodiments, specify: an Event Identifier 1002, an event type 1004, etc.
  • the data store 1000 may be created and updated, for example, when a new physical system is monitored or modeled, a component is to be calibrated, measurement data is received from a measurement unit, etc.
  • the data types are as listed herein.
  • Event ID 1002 includes a unique identifier for a grid event stored in the EMS system, which links to a unique start time and time duration.
  • Event Type 1004 associates with one type of event including unit in, unit out, line in and line out.
  • PMU Location 1006 specifies the name of the station, the voltage level (in unit of Kilovolts) and the Nodes Number (ND).
  • PMU ID 1008 includes a unique identifier for the PMU identified and evaluated in the EMS system.
  • DIF 1010 is a Disturbance Impact Factor which may be determined as described herein.
  • PMU Selection 1012 is determined based on the DIF value and the DIF threshold value.
  • the DIF threshold is 30%. So the top three rows are selected for model validation while the last row is not selected because its DIF value is lower than the threshold (30%).
  • Mapped Generator 1014 is used to indicate th geenerator name identified according to the auto-tag mapping method.
  • Network Model File 1016 is used to indicate the power network model file name identified by the automatic file collection 413 in FIG. 4. It is one input for Model Validation 1022.
  • Dynamic Model File 1018 indicates the dynamic model file name (consisting generator model name and parameter value inside) identified by the automatic file collection 413 in FIG. 4. It is one input for Model Validation 1022.
  • PMU event File 1020 indicates the PMU event file name identified by the automatic file collection 413 in FIG. 4. It is one input for Model Validation 1022.
  • Model Validation 1022 shows the model validation result: either continue to conduct model calibration or no need to conduct model calibration.
  • Model Calibration 1024 show the calibrated model file, which should replace the Dynamic model File 1018 after the user’s confirmation
  • FIG. 11 illustrates a system 1100 that includes an automatic model validation system in accordance with an example embodiment.
  • Embodying approaches can account for non-linearity in the power system model; account for multiple differing disturbance events; and calibration results can be localized around assumed default parameter values. Physical constraints of parameters may be enforced during model calibration, and an embodying calibration algorithm avoids tuning model parameters that might already be set at their true (e.g. , optimal) values.
  • a system 1100 may include a power generation system 1110 in accordance with some embodiments.
  • an embodying AMV system 1120 can include an AMV server 1130 in communication with a server data store 1140.
  • the server 1130 can include a server control processor 1131 that communicates with other components of the AMV system 1120.
  • a server control processor 1131 accesses computer executable program instructions, which in some implementations can be stored in the server data store 1140.
  • the server control processor 1131 can support embodying power system model validation for disturbance-based model validation and or calibration by executing executable instructions.
  • Dedicated hardware, software modules, and/or firmware can implement embodying approaches disclosed herein.
  • the server 1130 can be in communication with the server data store 1140 directly and/or across an electronic communication network 1118.
  • the electronic communication network 1118 can be, can comprise, or can be part of, an IP network, the Internet, an ISDN, frame relay connections, a modem connected to a phone line, a PSTN, a public or private data network, a LAN, a MAN, a WAN, a wireline or wireless network, a local, regional, or global communication network, an enterprise intranet, any combination of the preceding, and/or any other suitable communication means. It should be recognized that techniques and systems disclosed herein are not limited by the nature of electronic communication network 1118.
  • a power system can include a power generation system 1110, which provides electrical power to an electrical power distribution grid 1112.
  • a PMU 1115 can be coupled to the electrical power distribution grid to monitor signal characteristics (e.g., voltage (V) , frequency (f), active reactive power (P) and nonactive reactive power ( Q )).
  • the data obtained by the PMU 1115 can be provided to the AMV system 1120 across the electronic communication network 1118. This data can be stored in data records PMU monitored data 1143.
  • a power system is not limited to a single power generation system; that an electrical power grid can be a vast, interconnected network of multiple producers (power generation systems), transmission lines, substations, transformers, and loads (power consumers); and that multiple PMUs can be coupled to the power grid at multiple locations.
  • a power system model is tuned (“calibrated”) for one event (e.g., treating each disturbance event separately). This conventional approach results in severely limiting that model’s performance to satisfactorily predict a power system s performance in response to a subsequent event. Because some embodiments described herein simultaneously perform power system parameter tuning across multiple events, these system parameters can be provided to a power system model 1146. By incorporating the tuned parameters into the power system model 1146, the model 1146 can more accurately predict power system performance than conventionally-calibrated (“tuned”) models.
  • the parameter conditioning tool 1020 generates trajectory' sensitivity matrices for all the selected disturbances. These matrices are generated by perturbing each model parameter and feeding the perturbed parameter values to model simulation unit 1133. Depending on the number of disturbances being considered, model calibration algorithm 1144 can follow two options.
  • an embodying model calibration algorithm 1144 can solve an optimization problem to find a solution that has the minimum total distance to all the null spaces. Die solution reflects the parameter set that has dependencies in one or more of these disturbances.
  • a second option can be implemented by model calibration algorithm 1144. This second option evaluates the identifiability of parameters for each disturbance, then calculates the average identifiability ranking across disturbances. Since the sensitivity studies are conducted at the parameters’ default values, the parameter conditioning tool can also perform a global sensitivity consistency study when the parameters’ values deviate far away from their default values. Such study can portray the geometry of the parameter sensitivity in the entire parameter space.
  • the server 1130 may include an AMV module 1135 which can conduct the key modules (PMU selection, tag mapping, subsystem definition, model validation). Furthermore, the server data store 1140 may also store a knowledge base for PMU selection 1141 (DIF threshold for each equipment), a knowledge base for tag mapping 1142 such as naming convention rules, naming convention special cases, geographic names repositories, and the like. Meanwhile, the PMU monitored data record 1143 can further include the newly added table record from data store 1000 in FIG. 10, model calibration algorithms 1144, model parameter record 1145, and power system models 1146.
  • the above- described examples of the disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or any combination or subset thereof. Any such resulting program, having computer-readable code, may be embodied or provided within one or more non-transitory computer-readable media, thereby making a computer program product, i.e., an article of manufacture, according to the discussed examples of the disclosure.
  • the non-transitory computer-readable media may be, but is not limited to, a fixed drive, diskette, optical disk, magnetic tape, flash memory, semiconductor memory such as read-only memory (ROM), and/or any
  • the article of manufacture containing the computer code may be made and/or used by executing the code directly from one medium, by copying the code from one medium to another medium, or by transmitting the code over a network.
  • the computer programs may include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language.
  • the terms “machine-readable medium” and“computer-readable medium” refer to any computer program product, apparatus, cloud storage, internet of things, and/or device (e.g., magnetic discs, optical disks, memory, programmable logic devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal.
  • The“machine-readable medium” and“computer-readable medium,” however, do not include transitory signals.
  • the term“machine-readable signal” refers to any signal that may be used to provide machine instructions and/or any other kind of data to a programmable processor.

Abstract

La présente invention concerne un système et un procédé pour une validation automatisée de modèle de système d'alimentation. Le système permet de détecter une perturbation sur un réseau électrique, d'identifier des capteurs qui sont proches de la perturbation, de corréler les capteurs à un sous-système sur le réseau, et d'effectuer une validation de modèle de système d'alimentation pour le sous-système. Dans un exemple, le procédé peut comprendre les étapes consistant à, en réponse à un événement sur un réseau électrique, identifier une PMU du réseau électrique sur la base d'un emplacement géographique de l'événement, mapper la PMU identifiée à un système de production d'énergie sur le réseau électrique sur la base d'une étiquette de la PMU identifiée et d'une étiquette du système de production d'énergie, récupérer un modèle de système d'alimentation du système de production d'énergie, et déclencher une détermination de validation du modèle de système d'alimentation du système de production d'énergie sur la base de données d'événement détectées par la PMU identifiée.
PCT/US2019/017008 2019-02-07 2019-02-07 Système de validation automatisée de modèle pour réseau électrique WO2020162937A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2019/017008 WO2020162937A1 (fr) 2019-02-07 2019-02-07 Système de validation automatisée de modèle pour réseau électrique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2019/017008 WO2020162937A1 (fr) 2019-02-07 2019-02-07 Système de validation automatisée de modèle pour réseau électrique

Publications (1)

Publication Number Publication Date
WO2020162937A1 true WO2020162937A1 (fr) 2020-08-13

Family

ID=65576678

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/017008 WO2020162937A1 (fr) 2019-02-07 2019-02-07 Système de validation automatisée de modèle pour réseau électrique

Country Status (1)

Country Link
WO (1) WO2020162937A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111999583A (zh) * 2020-08-24 2020-11-27 南京工程学院 适应交流电网的安全稳定控制装置故障跳闸判别方法
CN112508447A (zh) * 2020-12-18 2021-03-16 国网河南省电力公司电力科学研究院 基于云平台的整定计算系统电网模型协同维护和共享方法
CN113098021A (zh) * 2021-04-20 2021-07-09 山东科技职业学院 电力系统自动电压控制方法
CN114189049A (zh) * 2021-12-06 2022-03-15 国网福建省电力有限公司经济技术研究院 电力电网数据采集系统
CN114397815A (zh) * 2021-12-14 2022-04-26 国网江苏省电力工程咨询有限公司 一种基于电力管廊及运维监控系统的精准甄控方法
CN115051363A (zh) * 2022-08-17 2022-09-13 广东电网有限责任公司佛山供电局 一种配网台区户变关系辨识方法、装置及计算机存储介质
CN117610980A (zh) * 2023-10-18 2024-02-27 国家电网有限公司华东分部 一种电力系统量测质量的辅助分析方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012035433A2 (fr) * 2010-09-17 2012-03-22 Nexans Système et procédé de gestion de réseau électrique
WO2013158813A1 (fr) * 2012-04-18 2013-10-24 Abb Research Ltd. Entretien d'un modèle de réseau électrique distribué
US20140244065A1 (en) * 2013-02-26 2014-08-28 Washington State University Voltage stability monitoring in power systems
US9362746B2 (en) * 2011-10-07 2016-06-07 Cisco Technology, Inc. Communication network topology management based on an associated electric grid topology
EP3301774A1 (fr) * 2016-10-03 2018-04-04 General Electric Technology GmbH Dispositif de simulation pour formation de répartiteur dynamique
US20180095123A1 (en) * 2016-10-03 2018-04-05 General Electric Technology Gmbh Enhanced distrubance management of a power grid system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012035433A2 (fr) * 2010-09-17 2012-03-22 Nexans Système et procédé de gestion de réseau électrique
US9362746B2 (en) * 2011-10-07 2016-06-07 Cisco Technology, Inc. Communication network topology management based on an associated electric grid topology
WO2013158813A1 (fr) * 2012-04-18 2013-10-24 Abb Research Ltd. Entretien d'un modèle de réseau électrique distribué
US20140244065A1 (en) * 2013-02-26 2014-08-28 Washington State University Voltage stability monitoring in power systems
EP3301774A1 (fr) * 2016-10-03 2018-04-04 General Electric Technology GmbH Dispositif de simulation pour formation de répartiteur dynamique
US20180095123A1 (en) * 2016-10-03 2018-04-05 General Electric Technology Gmbh Enhanced distrubance management of a power grid system

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111999583A (zh) * 2020-08-24 2020-11-27 南京工程学院 适应交流电网的安全稳定控制装置故障跳闸判别方法
CN111999583B (zh) * 2020-08-24 2023-03-28 南京工程学院 适应交流电网的安全稳定控制装置故障跳闸判别方法
CN112508447A (zh) * 2020-12-18 2021-03-16 国网河南省电力公司电力科学研究院 基于云平台的整定计算系统电网模型协同维护和共享方法
CN113098021A (zh) * 2021-04-20 2021-07-09 山东科技职业学院 电力系统自动电压控制方法
CN114189049A (zh) * 2021-12-06 2022-03-15 国网福建省电力有限公司经济技术研究院 电力电网数据采集系统
CN114397815A (zh) * 2021-12-14 2022-04-26 国网江苏省电力工程咨询有限公司 一种基于电力管廊及运维监控系统的精准甄控方法
CN114397815B (zh) * 2021-12-14 2023-08-01 国网江苏省电力工程咨询有限公司 一种基于电力管廊及运维监控系统的精准甄控方法
CN115051363A (zh) * 2022-08-17 2022-09-13 广东电网有限责任公司佛山供电局 一种配网台区户变关系辨识方法、装置及计算机存储介质
CN115051363B (zh) * 2022-08-17 2023-01-13 广东电网有限责任公司佛山供电局 一种配网台区户变关系辨识方法、装置及计算机存储介质
CN117610980A (zh) * 2023-10-18 2024-02-27 国家电网有限公司华东分部 一种电力系统量测质量的辅助分析方法及装置
CN117610980B (zh) * 2023-10-18 2024-04-26 国家电网有限公司华东分部 一种电力系统量测质量的辅助分析方法及装置

Similar Documents

Publication Publication Date Title
US10739396B2 (en) Enhanced disturbance management of a power grid system
WO2020162937A1 (fr) Système de validation automatisée de modèle pour réseau électrique
US10733901B2 (en) Dynamic dispatcher training simulator
Bose Smart transmission grid applications and their supporting infrastructure
WO2020171814A1 (fr) Sélection d'événement pour perturbation de réseau électrique
US10958101B2 (en) Methods and apparatus incorporating topology error estimation for management of an electric power system
KR102625403B1 (ko) 지역 단위 재생 에너지 통합 관제 시스템
CN116451876B (zh) 一种基于人工智能的配电网故障预测和主动检修系统
Arghandeh Micro-synchrophasors for power distribution monitoring, a technology review
GB2586435A (en) Electrical grid monitoring system
US20220284156A1 (en) Real-time update of power system models for dynamic security assessment
Mohamed et al. A multi-agent system for fault location and service restoration in power distribution systems
US20230082184A1 (en) Two-step oscillation source locator
US11860213B2 (en) Method, system and software product to identify installations likely to exhibit an electrical non-conformity
Gomathi et al. Optimal location of PMUs for complete observability of power system network
Zolin et al. Wide Area Monitoring System (WAMS) application in smart grids
Gomez et al. Web services framework for power quality monitoring
Wu et al. Monitoring power system transient stability using synchrophasor data
Rocha-Doria et al. Synchrophasor applications in distribution systems: real-life experience
Arghandeh et al. Synchronized measurements and their applications in distribution systems: An update
US20230327438A1 (en) Scalable state estimation for power distribution grid
Haidar et al. A framework for placement assessment of synchrophasor measurement in practical power grid: a case study from Borneo
Yao et al. Research on topology generation and fault prediction technology of low voltage distribution network based on state perception
Hao et al. Data-driven lean management for distribution network
Hälvä Development of Process Data Utilization in Proactive Network Management

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19707940

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19707940

Country of ref document: EP

Kind code of ref document: A1