EP2225639A1 - System zur echtzeitüberprüfung und überwachung von schutzvorrichtungseinstellungen in einem stromverteilungsnetz - Google Patents

System zur echtzeitüberprüfung und überwachung von schutzvorrichtungseinstellungen in einem stromverteilungsnetz

Info

Publication number
EP2225639A1
EP2225639A1 EP08860852A EP08860852A EP2225639A1 EP 2225639 A1 EP2225639 A1 EP 2225639A1 EP 08860852 A EP08860852 A EP 08860852A EP 08860852 A EP08860852 A EP 08860852A EP 2225639 A1 EP2225639 A1 EP 2225639A1
Authority
EP
European Patent Office
Prior art keywords
protective device
real
time
configuration settings
monitored
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP08860852A
Other languages
English (en)
French (fr)
Other versions
EP2225639A4 (de
Inventor
Adib Nasle
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Power Analytics Corp
Original Assignee
Edsa Micro Corp
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 Edsa Micro Corp filed Critical Edsa Micro Corp
Publication of EP2225639A1 publication Critical patent/EP2225639A1/de
Publication of EP2225639A4 publication Critical patent/EP2225639A4/de
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
    • G01R19/00—Arrangements for measuring currents or voltages or for indicating presence or sign thereof
    • G01R19/25—Arrangements for measuring currents or voltages or for indicating presence or sign thereof using digital measurement techniques
    • G01R19/2513—Arrangements for monitoring electric power systems, e.g. power lines or loads; Logging
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
    • G05B23/0243—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults model based detection method, e.g. first-principles knowledge model
    • G05B23/0254—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults model based detection method, e.g. first-principles knowledge model based on a quantitative model, e.g. mathematical relationships between inputs and outputs; functions: observer, Kalman filter, residual calculation, Neural Networks
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B9/00—Safety arrangements
    • G05B9/02—Safety arrangements electric

Definitions

  • the present invention relates generally to computer modeling and management of systems and, more particularly, to computer simulation techniques with real-time system monitoring and prediction of electrical system performance.
  • Computer models of complex systems enable improved system design, development, and implementation through techniques for off-line simulation of the system operation. That is, system models can be created that computers can "operate” in a virtual environment to determine design parameters. All manner of systems can be modeled, designed, and operated in this way, including machinery, factories, electrical power and distribution systems, processing plants, devices, chemical processes, biological systems, and the like. Such simulation techniques have resulted in reduced development costs and superior operation.
  • mission critical electrical systems e.g., for data centers or nuclear power facilities
  • the systems must be as failure proof as possible, and many layers of redundancy must be designed in to ensure that there is always a backup in case of a failure.
  • Computer design and modeling programs allow for the design of such systems by allowing a designer to model the system and simulate its operation. Thus, the designer can ensure that the system will operate as intended before the facility is constructed.
  • the design is typically only referred to when there is a failure.
  • technicians may from time-to-time adjust the protective device settings without first taking into consideration the power facility's design coordination requirements. This can result in unplanned power black outs due to the uncoordinated tripping of protective devices due to the protection system's loss of coordination and security.
  • a system for real-time verification of protective device system configuration settings on a monitored system includes a data acquisition component, a virtual system model database, a protective device system verification engine.
  • the data acquisition component is communicatively connected to a sensor configured to real-time protective device configuration data output from a protective device that is part of the monitored system.
  • the virtual system model database is configured to update a virtual mode of the system based on the status of the protective devices and to store a virtual system model of the monitored system, including preset protective device configuration settings for the protective device.
  • the protective device system verification engine configured to monitor the real-time protective device configuration data and the preset protective device configuration settings and generate a warning when there is a difference between the real-time protective device configuration data and the preset protective device configuration settings.
  • a computer-implemented method for real-time verification of protective device system configuration settings on a monitored system is disclosed.
  • Realtime protective device configuration data output is received from a sensor interfaced to a protective device that is part of the monitored system.
  • the real-time protective device configuration data is compared to the preset protective device configuration settings stored in a virtual system model of the monitored system.
  • a warning is generated when there is a difference between the real-time protective device configuration data and the present protective device configuration settings.
  • Figure 1 is an illustration of a system for utilizing real-time data for predictive analysis of the performance of a monitored system, in accordance with one embodiment.
  • Figure 2 is a diagram illustrating a detailed view of an analytics server included in the system of figure 1.
  • Figure 3 is a diagram illustrating how the system of figure 1 operates to synchronize the operating parameters between a physical facility and a virtual system model of the facility.
  • Figure 4 is an illustration of the scalability of a system for utilizing real-time data for predictive analysis of the performance of a monitored system, in accordance with one embodiment.
  • Figure 5 is a block diagram that shows the configuration details of the system illustrated in Figure 1 , in accordance with one embodiment.
  • Figure 6 is an illustration of a flowchart describing a method for real-time monitoring and predictive analysis of a monitored system, in accordance with one embodiment.
  • Figure 7 is an illustration of a flowchart describing a method for managing realtime updates to a virtual system model of a monitored system, in accordance with one embodiment.
  • Figure 8 is an illustration of a flowchart describing a method for synchronizing real-time system data with a virtual system model of a monitored system, in accordance with one embodiment.
  • Figure 9 is a flow chart illustrating an example method for updating the virtual model in accordance with one embodiment.
  • Figure 10 is a diagram illustrating an example process for monitoring the status of protective devices in a monitored system and updating a virtual model based on monitored data.
  • Figure 11 is a flowchart illustrating an example process for determining the protective capabilities of the protective devices being monitored.
  • FIG 12 is a diagram illustrating an example process for determining the protective capabilities of a High Voltage Circuit Breaker (HVCB).
  • HVCB High Voltage Circuit Breaker
  • Figure 13 is a flowchart illustrating an example process for determining the protective capabilities of the protective devices being monitored in accordance with another embodiment.
  • Figure 14 is a diagram illustrating a process for evaluating the withstand capabilities of a MVCB in accordance with one embodiment
  • Figure 15 is a flow chart illustrating an example process for analyzing the reliability of an electrical power distribution and transmission system in accordance with one embodiment.
  • Figure 16 is a flow chart illustrating an example process for analyzing the reliability of an electrical power distribution and transmission system that takes weather information into account in accordance with one embodiment.
  • Figure 17 is a diagram illustrating an example process for predicting in real-time various parameters associated with an alternating current (AC) arc flash incident.
  • AC alternating current
  • Figure 18 is a diagram illustrating how the Protective Device System
  • Configuration Verification Engine works in conjunction with the other elements of the analytics system to verify and monitor protective device settings within an electrical power distribution network, in accordance with one embodiment.
  • Figure 19 is a flowchart illustrating an example process for verifying and monitoring protective device settings within an electrical power distribution network, in accordance with one embodiment.
  • a system denotes a set of components, real or abstract, comprising a whole where each component interacts with or is related to at least one other component within the whole.
  • systems include machinery, factories, electrical systems, processing plants, devices, chemical processes, biological systems, data centers, aircraft carriers, and the like.
  • An electrical system can designate a power generation and/or distribution system that is widely dispersed (i.e., power generation, transformers, and/or electrical distribution components distributed geographically throughout a large region) or bounded within a particular location (e.g., a power plant within a production facility, a bounded geographic area, on board a ship, etc.).
  • a network application is any application that is stored on an application server connected to a network (e.g., local area network, wide area network, etc.) in accordance with any contemporary client/server architecture model and can be accessed via the network.
  • the network application programming interface resides on the application server separate from the client machine.
  • the client interface would typically be a web browser (e.g. INTERNET EXPLORERTM, FIREFOXTM, NETSCAPETM, etc) that is in communication with the network application server via a network connection (e.g., HTTP, HTTPS, RSS, etc.).
  • FIG. 1 is an illustration of a system for utilizing real-time data for predictive analysis of the performance of a monitored system, in accordance with one embodiment.
  • the system 100 includes a series of sensors (i.e., Sensor A 104, Sensor B 106, Sensor C 108) interfaced with the various components of a monitored system 102, a data acquisition hub 112, an analytics server 116, and a thin-client device 128.
  • the monitored system 102 is an electrical power generation plant.
  • the monitored system 102 is an electrical power transmission infrastructure.
  • the monitored system 102 is an electrical power distribution system.
  • the monitored system 102 includes a combination of one or more electrical power generation plant(s), power transmission infrastructure(s), and/or an electrical power distribution system. It should be understood that the monitored system 102 can be any combination of components whose operations can be monitored with conventional sensors and where each component interacts with or is related to at least one other component within the combination. For a monitored system 102 that is an electrical power generation, transmission, or distribution system, the sensors can provide data such as voltage, frequency, current, load, power factor, and the like.
  • the sensors are configured to provide output values for system parameters that indicate the operational status and/or "health" of the monitored system 102.
  • the current output or voltage readings for the various components that comprise the power generation system is indicative of the overall health and/or operational condition of the system.
  • the sensors are configured to also measure additional data that can affect system operation.
  • the sensor output can include environmental information, e.g., temperature, humidity, etc., which can impact electrical power demand and can also affect the operation and efficiency of the power distribution system itself.
  • the sensors are configured to output data in an analog format.
  • electrical power sensor measurements are sometimes conveyed in an analog format as the measurements may be continuous in both time and amplitude.
  • the sensors are configured to output data in a digital format.
  • the same electrical power sensor measurements may be taken in discrete time increments that are not continuous in time or amplitude.
  • the sensors are configured to output data in either an analog or digital format depending on the sampling requirements of the monitored system 102.
  • the sensors can be configured to capture output data at split-second intervals to effectuate "real time" data capture.
  • the sensors can be configured to generate hundreds of thousands of data readings per second. It should be appreciated, however, that the number of data output readings taken by a sensor may be set to any value as long as the operational limits of the sensor and the data processing capabilities of the data acquisition hub 112 are not exceeded.
  • each sensor is communicatively connected to the data acquisition hub 112 via an analog or digital data connection 110.
  • the data acquisition hub 112 may be a standalone unit or integrated within the analytics server 116 and can be embodied as a piece of hardware, software, or some combination thereof.
  • the data connection 110 is a "hard wired" physical data connection (e.g., serial, network, etc.).
  • the data connection 110 is a wireless data connection.
  • RF radio frequency
  • BLUETOOTHTM infrared or equivalent connection between the sensor and the hub 112.
  • the data acquisition hub 112 is configured to communicate "real-time" data from the monitored system 102 to the analytics server 116 using a network connection 114.
  • the network connection 114 is a "hardwired" physical connection.
  • the data acquisition hub 112 may be communicatively connected (via Category 5 (CAT5), fiber optic or equivalent cabling) to a data server (not shown) that is communicatively connected (via CAT5, fiber optic or equivalent cabling) through the Internet and to the analytics server 116 server.
  • the analytics server 116 being also communicatively connected with the Internet (via CAT5, fiber optic, or equivalent cabling).
  • the network connection 114 is a wireless network connection (e.g., Wi-Fi, WLAN, etc.). For example, utilizing an 802.1 lb/g or equivalent transmission format.
  • the network connection utilized is dependent upon the particular requirements of the monitored system 102.
  • Data acquisition hub 112 can also be configured to supply warning and alarms signals as well as control signals to monitored system 102 and/or sensors 104, 106, and 108 as described in more detail below.
  • the analytics server 116 hosts an analytics engine 118, virtual system modeling engine 124 and several databases 126, 130, and 132.
  • the virtual system modeling engine can, e.g., be a computer modeling system, such as described above. In this context, however, the modeling engine can be used to precisely model and mirror the actual electrical system.
  • Analytics engine 124 can be configured to generate predicted data for the monitored system and analyze difference between the predicted data and the real-time data received from hub 112.
  • Figure 2 is a diagram illustrating a more detailed view of analytic server 116.
  • analytic server 116 is interfaced with a monitored facility 102 via sensors
  • Sensors 202 are configured to supply real-time data from within monitored facility 102.
  • the real-time data is communicated to analytic server
  • Hub 204 can be configure to provide real-time data to server 116 as well as alarming, sensing and control featured for facility 102.
  • the real-time data from hub 204 can be passed to a comparison engine 210, which can form part of analytics engine 118.
  • Comparison engine 210 can be configured to continuously compare the real-time data with predicted values generated by simulation engine 208. Based on the comparison, comparison engine 210 can be further configured to determine whether deviations between the real-time and the expected values exists, and if so to classify the deviation, e.g., high, marginal, low, etc. The deviation level can then be communicated to decision engine 212, which can also comprise part of analytics engine 118.
  • Decision engine 212 can be configured to look for significant deviations between the predicted values and real-time values as received from the comparison engine 210.
  • decision engine 212 can also be configured to determine whether an alarm condition exists, activate the alarm and communicate the alarm to Human-Machine Interface (HMI) 214 for display in real-time via, e.g., thin client 128.
  • HMI Human-Machine Interface
  • Decision engine 212 can also be configured to perform root cause analysis for significant deviations in order to determine the interdependencies and identify the parent-child failure relationships that may be occurring. In this manner, parent alarm conditions are not drowned out by multiple children alarm conditions, allowing the user/operator to focus on the main problem, at least at first.
  • HMI 214 can be displayed via HMI 214 along with an indication that processes and equipment dependent on the parent process or equipment are also in alarm condition.
  • server 116 can maintain a parent-child logical relationship between processes and equipment comprising facility 102.
  • the processes can be classified as critical, essential, non-essential, etc.
  • Decision engine 212 can also be configured to determine health and performance levels and indicate these levels for the various processes and equipment via HMI 214. All of which, when combined with the analytic capabilities of analytics engine 118 allows the operator to minimize the risk of catastrophic equipment failure by predicting future failures and providing prompt, informative information concerning potential/predicted failures before they occur. Avoiding catastrophic failures reduces risk and cost, and maximizes facility performance and up time.
  • Simulation engine 208 operates on complex logical models 206 of facility
  • models 102 are continuously and automatically synchronized with the actual facility status based on the real-time data provided by hub 204.
  • the models are updated based on current switch status, breaker status, e.g., open-closed, equipment on/off status, etc.
  • the models are automatically updated based on such status, which allows simulation engine to produce predicted data based on the current facility status. This in turn, allows accurate and meaningful comparisons of the real-time data to the predicted data.
  • Example models 206 that can be maintained and used by server 116 include power flow models used to calculate expected Kw, Kvar, power factor values, etc., short circuit models used to calculate maximum and minimum available fault currents, protection models used to determine proper protection schemes and ensure selective coordination of protective devices, power quality models used to determine voltage and current distortions at any point in the network, to name just a few. It will be understood that differnet models can be used depending on the system being modeled.
  • hub 204 is configured to supply equipment identification associated with the real-time data. This identification can be cross referenced with identifications provided in the models.
  • DDT Defined Difference Tolerance
  • the comparison performed by comparison engine 210 indicates that the differential between the real-time sensor output value and the expected value exceeds a Defined Difference Tolerance (DDT) value (i.e., the "real-time" output values of the sensor output do not indicate an alarm condition) but below an alarm condition (i.e., alarm threshold value)
  • DDT Defined Difference Tolerance
  • the analytics engine does nothing and continues to monitor the real-time data and expected data.
  • the alarm or notification message is sent directly to the client (i.e., user) 128, e.g., via HMI 214, for display in real-time on a web browser, pop-up message box, e-mail, or equivalent on the client 128 display panel.
  • the alarm or notification message is sent to a wireless mobile device (e.g., BLACKBERRYTM, laptop, pager, etc.) to be displayed for the user by way of a wireless router or equivalent device interfaced with the analytics server 116.
  • the alarm or notification message is sent to both the client 128 display and the wireless mobile device.
  • the alarm can be indicative of a need for a repair event or maintenance to be done on the monitored system. It should be noted, however, that calibration requests should not be allowed if an alarm condition exists to prevent the models form being calibrated to an abnormal state.
  • model(s) 206 can be updated or adjusted to reflect the actual facility configuration. This can include, but is not limited to, modifying the predicted data output from the simulation engine 208, adjusting the logic/processing parameters utilized by the model(s) 206, adding/subtracting functional elements from model(s) 206, etc. It should be understood, that any operational parameter of models 206 can be modified as long as the resulting modifications can be processed and registered by simulation engine 208. [0058] Referring back to figure 1, models 206 can be stored in the virtual system model database 126.
  • the virtual system model can include components for modeling reliability, modeling output voltage stability, and modeling power flow.
  • models 206 can include dynamic control logic that permits a user to configure the models 206 by specifying control algorithms and logic blocks in addition to combinations and interconnections of generators, governors, relays, breakers, transmission line, and the like.
  • the voltage stability parameters can indicate capacity in terms of size, supply, and distribution, and can indicate availability in terms of remaining capacity of the presently configured system.
  • the power flow model can specify voltage, frequency, and power factor, thus representing the "health" of the system.
  • All of models 206 can be referred to as a virtual system model.
  • virtual system model database can be configured to store the virtual system model.
  • a duplicate, but synchronized copy of the virtual system model can be stored in a virtual simulation model database 130.
  • This duplicate model can be used for what-if simulations.
  • this model can be used to allow a system designer to make hypothetical changes to the facility and test the resulting effect, without taking down the facility or costly and time consuming analysis. Such hypothetical can be used to learn failure patterns and signatures as well as to test proposed modifications, upgrades, additions, etc., for the facility.
  • the real-time data, as well as trending produced by analytics engine 118 can be stored in a real-time data acquisition database 132.
  • the virtual system model is periodically calibrated and synchronized with "real-time" sensor data outputs so that the virtual system model provides data output values that are consistent with the actual "real-time” values received from the sensor output signals.
  • the virtual system models described herein are updated and calibrated with the real-time system operational data to provide better predictive output values. A divergence between the real-time sensor output values and the predicted output values generate either an alarm condition for the values in question and/or a calibration request that is sent to the calibration engine 120.
  • the analytics engine 124 can be configured to implement pattern/sequence recognition into a real-time decision loop that, e.g., is enabled by a new type of machine learning called associative memory, or hierarchical temporal memory (HTM), which is a biological approach to learning and pattern recognition.
  • Associative memory allows storage, discovery, and retrieval of learned associations between extremely large numbers of attributes in real time.
  • an associative memory stores information about how attributes and their respective features occur together. The predictive power of the associative memory technology comes from its ability to interpret and analyze these co-occurrences and to produce various metrics.
  • Associative memory is built through "experiential" learning in which each newly observed state is accumulated in the associative memory as a basis for interpreting future events.
  • the associative memory is able to learn normal patterns as a basis for identifying non-normal behavior and appropriate responses, and to associate patterns with particular outcomes, contexts or responses.
  • the analytics engine 118 is also better able to understand component mean time to failure rates through observation and system availability characteristics. This technology in combination with the virtual system model can be characterized as a "neocortical" model of the system under management
  • This approach also presents a novel way to digest and comprehend alarms in a manageable and coherent way.
  • the neocortical model could assist in uncovering the patterns and sequencing of alarms to help pinpoint the location of the (impending) failure, its context, and even the cause.
  • responding to the alarms is done manually by experts who have gained familiarity with the system through years of experience. However, at times, the amount of information is so great that an individual cannot respond fast enough or does not have the necessary expertise.
  • An "intelligent" system like the neocortical system that observes and recommends possible responses could improve the alarm management process by either supporting the existing operator, or even managing the system autonomously.
  • the virtual system model database 126 can be configured to store one or more virtual system models, virtual simulation models, and real-time data values, each customized to a particular system being monitored by the analytics server 118.
  • the analytics server 118 can be utilized to monitor more than one system at a time.
  • the databases 126, 130, and 132 can be hosted on the analytics server 116 and communicatively interfaced with the analytics engine 118.
  • databases 126, 130, and 132 can be hosted on a separate database server (not shown) that is communicatively connected to the analytics server 116 in a manner that allows the virtual system modeling engine 124 and analytics engine 118 to access the databases as needed.
  • the client 128 can modify the virtual system model stored on the virtual system model database 126 by using a virtual system model development interface using well-known modeling tools that are separate from the other network interfaces. For example, dedicated software applications that run in conjunction with the network interface to allow a client 128 to create or modify the virtual system models.
  • the client 128 may utilize a variety of network interfaces (e.g., web browser,
  • sensors e.g., configuration files, etc.
  • analytics engine 118 e.g., configuration files, analytics logic, etc.
  • calibration parameters e.g., configuration files, calibration parameters, etc.
  • virtual system modeling engine 124 e.g., configuration files, simulation parameters, etc.
  • virtual system model of the system under management e.g., virtual system model operating parameters and configuration files.
  • data from those various components of the monitored system 102 can be displayed on a client 128 display panel for viewing by a system administrator or equivalent.
  • server 116 is configured to synchronize the physical world with the virtual and report, e.g., via visual, real-time display, deviations between the two as well as system health, alarm conditions, predicted failures, etc. This is illustrated with the aid of figure 3, in which the synchronization of the physical world (left side) and virtual world (right side) is illustrated.
  • sensors 202 produce real-time data 302 for the processes 312 and equipment 314 that make up facility 102.
  • simulations 304 of the virtual system model 206 provide predicted values 306, which are correlated and synchronized with the real-time data 302. The real-time data can then be compared to the predicted values so that differences 308 can be detected.
  • FIG. 4 is an illustration of the scalability of a system for utilizing real-time data for predictive analysis of the performance of a monitored system, in accordance with one embodiment.
  • an analytics central server 422 is communicatively connected with analytics server A 414, analytics server B 416, and analytics server n 418 (i.e., one or more other analytics servers) by way of one or more network connections 114.
  • Each of the analytics servers is communicatively connected with a respective data acquisition hub (i.e., Hub A 408, Hub B 410, Hub n 412) that communicates with one or more sensors that are interfaced with a system (i.e., Monitored System A 402, Monitored System B 404, Monitored System n 406) that the respective analytical server monitors.
  • a respective data acquisition hub i.e., Hub A 408, Hub B 410, Hub n 412
  • analytics server A 414 is communicative connected with data acquisition hub A 408, which communicates with one or more sensors interfaced with monitored system A 402.
  • Each analytics server i.e., analytics server A 414, analytics server B 416, analytics server n 418) is configured to monitor the sensor output data of its corresponding monitored system and feed that data to the central analytics server 422.
  • each of the analytics servers can function as a proxy agent of the central analytics server 422 during the modifying and/or adjusting of the operating parameters of the system sensors they monitor.
  • analytics server B 416 is configured to be utilized as a proxy to modify the operating parameters of the sensors interfaced with monitored system B 404.
  • the central analytics server 422, which is communicatively connected to one or more analytics server(s) can be used to enhance the scalability.
  • a central analytics server 422 can be used to monitor multiple electrical power generation facilities (i.e., monitored system A 402 can be a power generation facility located in city A while monitored system B 404 is a power generation facility located in city B) on an electrical power grid.
  • each of the analytics servers are configured to serve as proxies for the central analytics server 422 to enable a client 128 to modify and/or adjust the operating parameters of the sensors interfaced with the systems that they respectively monitor.
  • the client 128 can use the central analytics server 422, and vice versa, to modify and/or adjust the operating parameters of analytics server A 414 and utilize the same to modify and/or adjust the operating parameters of the sensors interfaced with monitored system A 402.
  • each of the analytics servers can be configured to allow a client 128 to modify the virtual system model through a virtual system model development interface using well-known modeling tools.
  • the central analytics server 4522 can function to monitor and control a monitored system when its corresponding analytics server is out of operation.
  • central analytics server 422 can take over the functionality of analytics server B 416 when the server 416 is out of operation. That is, the central analytics server 422 can monitor the data output from monitored system B 404 and modify and/or adjust the operating parameters of the sensors that are interfaced with the system 404.
  • the network connection 114 is established through a wide area network (WAN) such as the Internet. In another embodiment, the network connection is established through a local area network (LAN) such as the company intranet. In a separate embodiment, the network connection 114 is a "hardwired" physical connection.
  • the data acquisition hub 112 may be communicatively connected (via Category 5 (CAT5), fiber optic or equivalent cabling) to a data server that is communicatively connected (via CAT5, fiber optic or equivalent cabling) through the Internet and to the analytics server 116 server hosting the analytics engine 118.
  • the network connection 114 is a wireless network connection (e.g., Wi-Fi, WLAN, etc.). For example, utilizing an 802.1 lb/g or equivalent transmission format.
  • FIG. 5 is a block diagram that shows the configuration details of analytics server 116 illustrated in Figure 1 in more detail. It should be understood that the configuration details in Figure 5 are merely one embodiment of the items described for Figure 1, and it should be understood that alternate configurations and arrangements of components could also provide the functionality described herein.
  • the analytics server 116 includes a variety of components.
  • the analytics server 116 is implemented in a Web-based configuration, so that the analytics server 116 includes (or communicates with) a secure web server 530 for communication with the sensor systems 519 (e.g., data acquisition units, metering devices, sensors, etc.) and external communication entities 534 (e.g., web browser, "thin client” applications, etc.).
  • a variety of user views and functions 532 are available to the client 128 such as: alarm reports, Active X controls, equipment views, view editor tool, custom user interface page, and XML parser.
  • the analytics server 116 also includes an alarm engine 506 and messaging engine 504, for the aforementioned external communications.
  • the alarm engine 506 is configured to work in conjunction with the messaging engine 504 to generate alarm or notification messages 502 (in the form of text messages, e-mails, paging, etc.) in response to the alarm conditions previously described.
  • the analytics server 116 determines alarm conditions based on output data it receives from the various sensor systems 519 through a communications connection (e.g., wireless 516, TCP/IP 518, Serial 520, etc) and simulated output data from a virtual system model 512, of the monitored system, processed by the analytics engines 118.
  • a communications connection e.g., wireless 516, TCP/IP 518, Serial 520, etc
  • the virtual system model 512 is created by a user through interacting with an external communication entity 534 by specifying the components that comprise the monitored system and by specifying relationships between the components of the monitored system.
  • the virtual system model 512 is automatically generated by the analytics engines 118 as components of the monitored system are brought online and interfaced with the analytics server 508.
  • a virtual system model database 526 is communicatively connected with the analytics server 116 and is configured to store one or more virtual system models 512, each of which represents a particular monitored system.
  • the analytics server 116 can conceivably monitor multiple electrical power generation systems (e.g., system A, system B, system C, etc.) spread across a wide geographic area (e.g., City A, City B, City C, etc.). Therefore, the analytics server 116 will utilize a different virtual system model 512 for each of the electrical power generation systems that it monitors.
  • Virtual simulation model database 538 can be configured to store a synchronized, duplicate copy of the virtual system model 512, and real-time data acquisition database 540 can store the real-time and trending data for the system(s) being monitored.
  • analytics server 116 can receive real-time data for various sensors, i.e., components, through data acquisition system 202.
  • analytics server 116 can comprise various drivers configured to interface with the various types of sensors, etc., comprising data acquisition system 202.
  • This data represents the real-time operational data for the various components. For example, the data may indicate that a certain component is operating at a certain voltage level and drawing certain amount of current. This information can then be fed to a modeling engine to generate a virtual system model 612 that is based on the actual real-time operational data.
  • Analytics engine 118 can be configured to compare predicted data based on the virtual system model 512 with real-time data received from data acquisition system 202 and to identify any differences. In some instances, analytics engine can be configured to identify these differences and then update, i.e., calibrate, the virtual system model 512 for use in future comparisons. In this manner, more accurate comparisons and warnings can be generated.
  • the differences will indicate a failure, or the potential for a failure.
  • the operating parameters will begin to change. This change may be sudden or it may be a progressive change over time.
  • Analytics engine 118 can detect such changes and issue warnings that can allow the changes to be detected before a failure occurs.
  • the analytic engine 118 can be configured to generate warnings that can be communicated via interface 532.
  • a user can access information from server 116 using thin client
  • reports can be generate and served to thin client 534 via server 540. These reports can, for example, comprise schematic or symbolic illustrations of the system being monitored. Status information for each component can be illustrated or communicated for each component. This information can be numerical, i.e., the voltage or current level. Or it can be symbolic, i.e., green for normal, red for failure or warning. In certain embodiments, intermediate levels of failure can also be communicated, i.e., yellow can be used to indicate operational conditions that project the potential for future failure. It should be noted that this information can be accessed in real-time. Moreover, via thin client 534, the information can be accessed form anywhere and anytime.
  • FIG. 6 is an illustration of a flowchart describing a method for real-time monitoring and predictive analysis of a monitored system, in accordance with one embodiment.
  • Method 600 begins with operation 602 where real-time data indicative of the monitored system status is processed to enable a virtual model of the monitored system under management to be calibrated and synchronized with the real-time data.
  • the monitored system 102 is a mission critical electrical power system.
  • the monitored system 102 can include an electrical power transmission infrastructure.
  • the monitored system 102 includes a combination of thereof. It should be understood that the monitored system 102 can be any combination of components whose operations can be monitored with conventional sensors and where each component interacts with or is related to at least one other component within the combination.
  • Method 600 moves on to operation 604 where the virtual system model of the monitored system under management is updated in response to the real-time data. This may include, but is not limited to, modifying the simulated data output from the virtual system model, adjusting the logic/processing parameters utilized by the virtual system modeling engine to simulate the operation of the monitored system, adding/subtracting functional elements of the virtual system model, etc. It should be understood, that any operational parameter of the virtual system modeling engine and/or the virtual system model may be modified by the calibration engine as long as the resulting modifications can be processed and registered by the virtual system modeling engine.
  • Method 600 proceeds on to operation 606 where the simulated real-time data indicative of the monitored system status is compared with a corresponding virtual system model created at the design stage.
  • the design stage models which may be calibrated and updated based on real-time monitored data, are used as a basis for the predicted performance of the system.
  • the real-time monitored data can then provide the actual performance over time.
  • difference can be identified a tracked by, e.g., the analytics engine 118.
  • Analytics engines 118 can then track trends, determine alarm states, etc., and generate a real-time report of the system status in response to the comparison.
  • the analytics can be used to analyze the comparison and realtime data and determine of there is a problem that should be reported and what level the problem may be, e.g., low priority, high priority, critical, etc.
  • the analytics can also be used to predict future failures and time to failure, etc.
  • reports can be displayed on a conventional web browser (e.g. INTERNET EXPLORERTM, FIREFOXTM, NETSCAPETM, etc) that is rendered on a standard personal computing (PC) device.
  • the "real-time" report can be rendered on a "thin-client” computing device (e.g., CITRIXTM, WINDOWS TERMINAL SERVICESTM, telnet, or other equivalent thin-client terminal application).
  • the report can be displayed on a wireless mobile device (e.g., BLACKBERRYTM, laptop, pager, etc.).
  • the "real-time" report can include such information as the differential in a particular power parameter (i.e., current, voltage, etc.) between the real-time measurements and the virtual output data.
  • FIG. 7 is an illustration of a flowchart describing a method for managing real-time updates to a virtual system model of a monitored system, in accordance with one embodiment.
  • Method 700 begins with operation 702 where real-time data output from a sensor interfaced with the monitored system is received.
  • the sensor is configured to capture output data at split-second intervals to effectuate "real time" data capture.
  • the sensor is configured to generate hundreds of thousands of data readings per second. It should be appreciated, however, that the number of data output readings taken by the sensor may be set to any value as long as the operational limits of the sensor and the data processing capabilities of the data acquisition hub are not exceeded.
  • Method 700 moves to operation 704 where the real-time data is processed into a defined format.
  • the data is converted from an analog signal to a digital signal.
  • the data is converted from a digital signal to an analog signal. It should be understood, however, that the real-time data may be processed into any defined format as long as the analytics engine can utilize the resulting data in a comparison with simulated output data from a virtual system model of the monitored system.
  • Method 700 continues on to operation 706 where the predicted (i.e., simulated) data for the monitored system is generated using a virtual system model of the monitored system.
  • a virtual system modeling engine utilizes dynamic control logic stored in the virtual system model to generate the predicted output data.
  • the predicted data is supposed to be representative of data that should actually be generated and output from the monitored system.
  • Method 700 proceeds to operation 708 where a determination is made as to whether the difference between the real-time data output and the predicted system data falls between a set value and an alarm condition value, where if the difference falls between the set value and the alarm condition value a virtual system model calibration and a response can be generated. That is, if the comparison indicates that the differential between the "realtime" sensor output value and the corresponding "virtual" model data output value exceeds a Defined Difference Tolerance (DDT) value (i.e., the "real-time" output values of the sensor output do not indicate an alarm condition) but below an alarm condition (i.e., alarm threshold value), a response can be generated by the analytics engine.
  • DDT Defined Difference Tolerance
  • FIG. 8 is an illustration of a flowchart describing a method for synchronizing real-time system data with a virtual system model of a monitored system, in accordance with one embodiment.
  • Method 800 begins with operation 802 where a virtual system model calibration request is received.
  • a virtual model calibration request can be generated by an analytics engine whenever the difference between the real-time data output and the predicted system data falls between a set value and an alarm condition value.
  • Method 800 proceeds to operation 804 where the predicted system output value for the virtual system model is updated with a real-time output value for the monitored system. For example, if sensors interfaced with the monitored system outputs a real-time current value of A, then the predicted system output value for the virtual system model is adjusted to reflect a predicted current value of A.
  • Method 800 moves on to operation 806 where a difference between the realtime sensor value measurement from a sensor integrated with the monitored system and a predicted sensor value for the sensor is determined.
  • the analytics engine is configured to receive "real-time" data from sensors interfaced with the monitored system via the data acquisition hub (or, alternatively directly from the sensors) and "virtual" data from the virtual system modeling engine simulating the data output from a virtual system model of the monitored system.
  • the values are in units of electrical power output (i.e., current or voltage) from an electrical power generation or transmission system. It should be appreciated, however, that the values can essentially be any unit type as long as the sensors can be configured to output data in those units or the analytics engine can convert the output data received from the sensors into the desired unit type before performing the comparison.
  • Method 800 continues on to operation 808 where the operating parameters of the virtual system model are adjusted to minimize the difference.
  • the logic parameters of the virtual system model that a virtual system modeling engine uses to simulate the data output from actual sensors interfaced with the monitored system are adjusted so that the difference between the real-time data output and the simulated data output is minimized.
  • this operation will update and adjust any virtual system model output parameters that are functions of the virtual system model sensor values. For example, in a power distribution environment, output parameters of power load or demand factor might be a function of multiple sensor data values.
  • the operating parameters of the virtual system model that mimic the operation of the sensor will be adjusted to reflect the real-time data received from those sensors.
  • authorization from a system administrator is requested prior to the operating parameters of the virtual system model being adjusted. This is to ensure that the system administrator is aware of the changes that are being made to the virtual system model.
  • a report is generated to provide a summary of all the adjustments that have been made to the virtual system model.
  • virtual system modeling engine 124 can be configured to model various aspects of the system to produce predicted values for the operation of various components within monitored system 102. These predicted values can be compared to actual values being received via data acquisition hub 112. If the differences are greater than a certain threshold, e.g., the DTT, but not in an alarm condition, then a calibration instruction can be generated. The calibration instruction can cause a calibration engine 134 to update the virtual model being used by system modeling engine 124 to reflect the new operating information.
  • a certain threshold e.g., the DTT
  • step 902 data is collected from, e.g., sensors 104, 106, and 108.
  • the sensors can be configured to monitor protective devices within an electrical distribution system to determine and monitor the ability of the protective devices to withstand faults, which is describe in more detail below.
  • the data from the various sensors can be processed by analytics engine 118 in order to evaluate various parameters related to monitored system 102.
  • simulation engine 124 can be configured to generate predicted values for monitored system 102 using a virtual model of the system that can be compared to the parameters generated by analytics engine 118 in step 904. If there are differences between the actual values and the predicted values, then the virtual model can be updated to ensure that the virtual model ages with the actual system 102.
  • a logical model of a facilities electrical system can be integrated with a logic and methods based approach to the adjustment of key database parameters within a virtual model of the electrical system to evaluate the ability of protective devices within the electrical distribution system to withstand faults and also effectively "age" the virtual system with the actual system.
  • Figures 10-12 are flow charts presenting logical flows for determining the ability of protective devices within an electrical distribution system to withstand faults and also effectively "age” the virtual system with the actual system in accordance with one embodiment.
  • Figure 10 is a diagram illustrating an example process for monitoring the status of protective devices in a monitored system 102 and updating a virtual model based on monitored data.
  • the status of the protective devices can be monitored in real time.
  • protective devices can include fuses, switches, relays, and circuit breakers. Accordingly, the status of the fuses/switches, relays, and/or circuit breakers, e.g., the open/close status, source and load status, and on or off status, can be monitored in step 1002.
  • step 1004 It can be determined, in step 1004, if there is any change in the status of the monitored devices. If there is a change, then in step 1006, the virtual model can be updated to reflect the status change, i.e., the corresponding virtual components data can be updated to reflect the actual status of the various protective devices.
  • step 1008 predicted values for the various components of monitored system 102 can be generated. But it should be noted that these values are based on the current, realtime status of the monitored system.
  • step 1010 it can be determined which predicted voltages are for nodes within monitored system 102 and which are for loads within monitored system 102.
  • real time sensor data can be received in step 1012. This real time data can be used to monitor the status in step 1002 and it can also be compared with the predicted values in step 1014. As noted above, the difference between the predicted values and the real time data can also be determined in step 1014.
  • meaningful predicted values based on the actual condition of monitored system 102 can be generated in steps 1004 to 1010. These predicted values can then be used to determine if further action should be taken based on the comparison of step 1014. For example, if it is determined in step 1016 that the difference between the predicted values and the real time sensor data is less than or equal to a certain threshold, e.g., DTT, then no action can be taken e.g., an instruction not to perform calibration can be issued in step 1018. Alternatively, if it is determined in step 1020 that the real time data is actually indicative of an alarm situation, e.g., is above an alarm threshold, then a do not calibrate instruction can be generated in step 1018 and an alarm can be generated as described above.
  • a certain threshold e.g., DTT
  • step 1024 If the real time sensor data is not indicative of an alarm condition, and the difference between the real time sensor data and the predicted values is greater than the threshold, as determined in step 1022, then an initiate calibration command can be generated in step 1024.
  • a function call to calibration engine 134 can be generated in step 1026.
  • the function call will cause calibration engine 134 to update the virtual model in step 1028 based on the real time sensor data.
  • a comparison between the real time data and predicted data can then be generated in step 1030 and the differences between the two computed.
  • step 1032 a user can be prompted as to whether or not the virtual model should in fact be updated. In other embodiments, the update can be automatic, and step 1032 can be skipped.
  • step 1034 the virtual model could be updated.
  • the virtual model loads, buses, demand factor, and/or percent running information can be updated based on the information obtained in step 1030.
  • An initiate simulation instruction can then be generated in step 1036, which can cause new predicted values to be generated based on the update of virtual model.
  • the predicted values generated in step 1008 are not only updated to reflect the actual operational status of monitored system 102, but they are also updated to reflect natural changes in monitored system 102 such as aging. Accordingly, realistic predicted values can be generated in step 1008.
  • Figure 11 is a flowchart illustrating an example process for determining the protective capabilities of the protective devices being monitored in step 1002.
  • the protective devices can be evaluated in terms of the International Electrotechnical Commission (IEC) standards or in accordance with the European standards. It will be understood, that the process described in relation to Figure 11 is not dependent on a particular standard being used.
  • IEC International Electrotechnical Commission
  • a short circuit analysis can be performed for the protective device.
  • the protective device can be any one of a variety of protective device types.
  • the protective device can be a fuse or a switch, or some type of circuit breaker.
  • circuit breakers including Low Voltage Circuit Breakers (LVCBs), High Voltage Circuit Breakers (HVCBs), Mid Voltage Circuit Breakers (MVCBs), Miniature Circuit Breakers (MCBs), Molded Case Circuit Breakers (MCCBs), Vacuum Circuit Breakers, and Air Circuit Breakers, to name just a few. Any one of these various types of protective devices can be monitored and evaluated using the processes illustrated with respect to Figures 10-12.
  • the short circuit current, symmetric (I sym ) or asymmetric (I aS ym), and/or the peak current (I pea k) can be determined in step 1102.
  • the short circuit current at a delayed time I symde i ay
  • a first cycle short circuit current (I sym ) and/or Ipeak can be determined in step 1102.
  • the short circuit current, symmetric or asymmetric can be determined in step 1102.
  • the short circuit current interrupting time can be calculated.
  • the short circuit analysis is performed in step 1102
  • various steps can be carried out in order to determine the bracing capability of the protective device.
  • the protective device is a fuse or switch
  • the steps on the left hand side of Figure 11 can be carried out.
  • the fuse rating can first be determined in step 1104.
  • the fuse rating can be the current rating for the fuse.
  • the asymmetric short circuit current (I aS ym) for the fuse can be determined in step 1106 using equation 1.
  • the inductants/reactants (X/R) ratio can be calculated instep 1108 and compared to a fuse test X/R to determine if the calculated X/R is greater than the fuse test X/R.
  • the calculated X/R can be determined using the predicted values provided in step 1008.
  • Various standard tests X/R values can be used for the fuse test X/R values in step 1108.
  • standard test X/R values for a LVCB can be as follows:
  • equation 12 can be used to calculate an adjusted symmetrical short circuit current (I a djsym).
  • I adjSym can be set equal to I sym in step 1110.
  • the fuse rating step 1104 is greater than or equal to I adjsym - If it is, then it can determine in step 1118 that the protected device has passed and the percent rating can be calculated in step 1120 as follows:
  • step 1114 If it is determined in step 1114 that the device rating is not greater than or equal to l adjsym , then it can be determined that the device as failed in step 1116. The percent rating can still be calculating in step 1120.
  • step 1122 it can first be determined whether they are fused in step 1122. If it is determined that the LVCB is not fused, then in step 1124 can be determined if the LVCB is an instantaneous trip LVCB. If it is determined that the LVCB is an instantaneous trip LVCB, then in step 1130 the first cycle fault X/R can be calculated and compared to a circuit breaker test X/R (see example values above) to determine if the fault X/R is greater than the circuit breaker test X/R. If the fault X/R is not greater than the circuit breaker test X/R, then in step 1132 it can be determined if the LVCB is peak rated.
  • a circuit breaker test X/R see example values above
  • I sym can be used in step 1146 below. If it is determined that the LVCB is not peak rated in step 1132, then lad j sym can be set equal to I sym in step 1140. In step 1146, it can be determined if the device rating is greater or equal to Iad j sym, or to I sym as appropriate, for the LVCB. [00115] If it is determined that the device rating is greater than or equal to Iad j sym, then it can be determined that the LVCB has passed in step 1148. The percent rating can then be determined using the equations for I a d JS ym defined above (step 1120) in step 1152. If it is determined that the device rating is not greater than or equal to I adjsym , then it can be determined that the device has failed in step 1150. The percent rating can still be calculated in step 1152.
  • the calculated fault X/R is not greater than the circuit breaker test X/R as determined in step 1130, then it can be determined if the LVCB is peak rated in step 1134. If the LVCB is not peak rated, then the Iad j sym can be determined using equation 12. If the LVCB is not peak rated, then I pea k can be determined using equation 11.
  • a time delay calculation can be performed at step 1128 followed by calculation of the fault X/R and a determination of whether the fault X/R is greater than the circuit breaker test X/R. If it is not, then I a d JS ym can be set equal to I sym in step 1136. If the calculated fault at X/R is greater than the circuit breaker test X/R, then Iad j symdeky can be calculated in step 1138 using the following equation with, e.g., a 0.5 second maximum delay:
  • the fault X/R can be calculated in step 1126 and compared to the circuit breaker test X/R in order to determine if the calculated fault X/R is greater than the circuit breaker test X/R. If it is greater, then Iadjsym can be calculated in step 1154 using the following equation:
  • Iadjsym can be set equal to I sym in step 1156. It can then be determined if the device rating is greater than or equal to Iadjsym in step 1146. The pass/fail determinations can then be carried out in steps 1148 and 1150 respectively, and the percent rating can be determined in step 1152.
  • FIG. 12 is a diagram illustrating an example process for determining the protective capabilities of a HVCB.
  • a peak voltage I peak
  • step 1162 it can be determined whether the HVCB' s rating is greater than or equal to I peak as determined in step 1158. If the device rating is greater than or equal to I P eak, then the device has passed in step 1164. Otherwise, the device fails in step 1166. In either case, the percent rating can be determined in step 1168 using the following:
  • an interrupting time calculation can be made in step 1170.
  • a fault X/R can be calculated and then can be determined if the fault X/R is greater than or equal to a circuit breaker test X/R in step 1172.
  • the following circuit breaker test X/R can be used;
  • I a d ⁇ ntsym can be set equal to I sym in step 1174. If the calculated fault X/R is greater than the circuit breaker test X/R, then contact parting time for the circuit breaker can be determined in step 1176 and equation 15 can then be used to determine Iad ⁇ ntsym in step 1178.
  • step 1180 it can be determined whether the device rating is greater than or equal to I adj i ntsym - The pass/fail determinations can then be made in steps 1182 and 1184 respectively and the percent rating can be calculated in step 1186 using the following:
  • FIG. 13 is a flowchart illustrating an example process for determining the protective capabilities of the protective devices being monitored in step 1002 in accordance with another embodiment.
  • the process can start with a short circuit analysis in step 1302.
  • the protective device X/R can be modified as follows:
  • a selection can be made, as appropriate, between use of the symmetrical rating or asymmetrical rating for the device.
  • the Multiplying Factor (MF) for the device can then be calculated in step 1304.
  • the MF can then be used to determine I a djasym or I adjsym -
  • step 1314 it can first be determined whether the device is fused in step 1314. If the device is not fused, then in step 1315 it can be determined whether the X/R is known for the device. If it is known, then the LVF can be calculated for the device in step 1320. It should be noted that the LVF can vary depending on whether the LVCB is an instantaneous trip device or not. If the X/R is not known, then it can be determined in step 1317, e.g., using the following:
  • step 1316 it can again be determined whether the X/R is known. If it is known, then the LVF can be calculated in step 1319. If it is not known, then the X/R can be set equal to, e.g., 4.9.
  • step 1321 it can be determined of the LVF is less than 1 and if it is, then the LVF can be set equal to 1.
  • Iintadj can be determined using the following:
  • step 1323 it can be determined whether the device's symmetrical rating is greater than or equal to I intadj , and it can be determined based on this evaluation whether the device passed or failed in steps 1324 and 1325 respectively.
  • the percent rating can then be determined in step 1326 using the following:
  • % rating I intadj *100/device rating.
  • Figure 14 is a diagram illustrating a process for evaluating the withstand capabilities of a MVCB in accordance with one embodiment.
  • a determination can be made as to whether the following calculations will be based on all remote inputs, all local inputs or on a No AC Decay (NACD) ratio. (Adib is this right?)
  • NACD No AC Decay
  • a calculation can then be made of the total remote contribution, total local contribution, total contribution (I m trmssym), and NACD. If the calculated NACD is equal to zero, then it can be determined that all contributions are local. IfNACD is equal to 1, then it can be determined that all contributions are remote.
  • step 1332 the remote MF (MFr) can be calculated and I int can be calculated using the following:
  • T J ⁇ int . M lv ⁇ F ⁇ r L *Tln ⁇ trmssym-
  • MFl can be calculated and I int can be calculated using the following: lint JVl-T 1 lintrmssym-
  • NACD NACD
  • MFr MFr
  • MFl MFl
  • AMFl MFl
  • I int can then be calculated using the following:
  • I 1n , AMFl*I intrmssym /S.
  • step 1338 the 3-phase device duty cycle can be calculated and then it can be determined in step 1340, whether the device rating is greater than or equal to I int . Whether the device passed or failed can then be determined in steps 1342 and 1344, respectively.
  • the percent rating can be determined in step 1346 using the following:
  • % rating I int *100/3p device rating.
  • step 1348 it can be determined, in step 1348, whether the user has selected a fixed MF. If so, then in certain embodiments the peak duty (crest) can be determined in step 1349 and MFp can be set equal to 2.7 in step 1354. If a fixed MF has not been selected, then the peak duty (crest) can be calculated in step 1350 and MFp can be calculated in step 1358. In step 1362, the MFp can be used to calculate the following: lmompeak IVLr p Isymrms-
  • step 1366 it can be determined if the device peak rating (crest) is greater than or equal to I mompeak - It can then be determined whether the device passed or failed in steps 1368 and 1370 respectively, and the percent rating can be calculated as follows:
  • % rating Imompeak* 100/device peak (crest) rating.
  • MFm can be set equal to, e.g., 1.6. If a fixed MF has not been selected, then in step 1352 MFm can be calculated. MFm can then be used to determine the following:
  • step 1374 It can then be determined in step 1374 whether the device C&L, rms rating is greater than or equal to I momsym - Whether the device passed or failed can then be determined in steps 1376 and 1378 respectively, and the percent rating can be calculated as follows:
  • % rating I mO masym*100/device C&L, rms rating.
  • FIG. 15 is a flow chart illustrating an example process for analyzing the reliability of an electrical power distribution and transmission system in accordance with one embodiment. First, in step 1502, reliability data can be calculated and/or determined.
  • the inputs used in step 1502 can comprise power flow data, e.g., network connectivity, loads, generations, cables/transformer impedances, etc., which can be obtained from the predicted values generated in step 1008, reliability data associated with each power system component, lists of contingencies to be considered, which can vary by implementation including by region, site, etc., customer damage (load interruptions) costs, which can also vary by implementation, and load duration curve information.
  • Other inputs can include failure rates, repair rates, and required availability of the system and of the various components.
  • a list of possible outage conditions and contingencies can be evaluated including loss of utility power supply, generators, UPS, and/or distribution lines and infrastructure.
  • step 1506 a power flow analysis for monitored system 102 under the various contingencies can be performed. This analysis can include the resulting failure rates, repair rates, cost of interruption or downtime versus the required system availability, etc.
  • step 1510 it can be determined if the system is operating in a deficient state when confronted with a specific contingency. If it is, then is step 1512, the impact on the system, load interruptions, costs, failure duration, system unavailability, etc. can all be evaluated. [00145] After the evaluation of step 1512, or if it is determined that the system is not in a deficient state in step 1510, then it can be determined if further contingencies need to be evaluated.
  • a report can be generated in step 1514.
  • the report can include a system summary, total and detailed reliability indices, system availability, etc.
  • the report can also identify system bottlenecks are potential problem areas.
  • the reliability indices can be based on the results of credible system contingencies involving both generation and transmission outages.
  • the reliability indices can include load point reliability indices, branch Reliability indices, and system reliability indices.
  • load/bus reliability indices can be determined such as probability and frequency of failure, expected load curtailed, expected energy not supplied, frequency of voltage violations, reactive power required, and expected customer outage cost.
  • the load point indices can be evaluated for the major load buses in the system and can be used in system design for comparing alternate system configurations and modifications.
  • Overall system reliability indices can include power interruption index, power supply average MW curtailment, power supply disturbance index, power energy curtailment index, severity index, and system availability.
  • the individual load point indices can be aggregated to produce a set of system indices. These indices are indicators of the overall adequacy of the composite system to meet the total system load demand and energy requirements and can be extremely useful for the system planner and management, allowing more informed decisions to be made both in planning and in managing the system.
  • the various analysis and techniques can be broadly classified as being either Monte Carlo simulation or Contingency Enumeration.
  • the process can also use AC, DC and fast linear network power flow solutions techniques and can support multiple contingency modeling, multiple load levels, automatic or user-selected contingency enumeration, use a variety of remedial actions, and provides sophisticated report generation.
  • the analysis of step 1506 can include adequacy analysis of the power system being monitored based on a prescribed set of criteria by which the system must be judged as being in the success or failed state.
  • the system is considered to be in the failed state if the service at load buses is interrupted or its quality becomes unacceptable, i.e., if there are capacity deficiency, overloads, and/or under/over voltages
  • FIG. 15 is a flow chart illustrating an example process for analyzing the reliability of an electrical power distribution and transmission system that takes weather information into account in accordance with one embodiment.
  • step 1602 real-time weather data can be received, e.g., via a data feed such as an XML feed from National Oceanic and Atmosphere Administration (NOAA).
  • NOAA National Oceanic and Atmosphere Administration
  • this data can be converted into reliability data that can be used in step 1502.
  • NFPA National Fire Protection Association
  • OSHA Occupational Safety and Health Association
  • conventional approaches/systems for performing such studies do not provide a reliable means for the real-time prediction of the potential energy released (in calories per centimeter squared) for an arc flash event.
  • PPE personal protective equipment
  • a static model does not provide the real-time analysis that can be critical for accurate PPE level determination. This is because static systems cannot adjust to the many daily changes to the electrical system that occur at a facility, e.g., motors and pumps may be on or off, on-site generation status may have changed by having diesel generators on-line, utility electrical feed may also change, etc., nor can they age with the facility to accurately predict the required PPE levels.
  • a logical model of a facility electrical system can be integrated into a real-time environment, with a robust AC Arc Flash simulation engine (system modeling engine 124), a data acquisition system (data acquisition hub 112), and an automatic feedback system (calibration engine 134) that continuously synchronizes and calibrates the logical model to the actual operational conditions of the electrical system.
  • system modeling engine 124 system modeling engine 124
  • data acquisition system data acquisition hub 112
  • calibration engine 134 an automatic feedback system
  • FIG. 17 is a diagram illustrating an example process for predicting in real-time various parameters associated with an alternating current (AC) arc flash incident. These parameters can include for example, the arc flash incident energy, arc flash protection boundary, and required Personal Protective Equipment (PPE) levels, e.g., in order to comply with NFPA-70E and IEEE-1584.
  • updated virtual model data can be obtained for the system being model, e.g., the updated data of step 1006, and the operating modes for the system can be determined.
  • an AC 3-phase short circuit analysis can be performed in order to obtain bolted fault current values for the system.
  • step 1706 e.g., IEEE 1584 equations can be applied to the bolted fault values and any corresponding arcing currents can be calculated in step 1708.
  • the ratio of arc current to bolted current can then be used, in step 1710, to determine the arcing current in a specific protective device, such as a circuit breaker or fuse.
  • a coordinated time-current curve analysis can be performed for the protective device in step 1712.
  • the arcing current in the protective device and the time current analysis can be used to determine an associated fault clearing time, and in step 1716 a corresponding arc energy can be determined based on, e.g., IEEE 1584 equations applied to the fault clearing time and arcing current.
  • step 1718 the 100% arcing current can be calculated and for systems operating at less than IkV the 85% arcing current can also be calculated.
  • step 1720 the fault clearing time in the protective device can be determined at the 85% arcing current level.
  • step 1722 e.g., IEEE 1584 equations can be applied to the fault clearing time (determined in step 1720) and the arcing current to determine the 85% arc energy level, and in step 1724 the 100% arcing current can be compared with the 85% arcing current, with the higher of the two being selected. IEEE 1584 equations, for example, can then be applied to the selected arcing current in step 1726 and the PPE level and boundary distance can be determined in step 1728.
  • step 1730 these values can be output, e.g., in the form of a display or report.
  • the following evaluations can be made in real-time and based on an accurate, e.g., aged, model of the system:
  • Network-Based Arc Flash Exposure on AC Systems/Single Branch Case Network-Based Arc Flash Exposure on AC Systems/Multiple Branch Cases; Network Arc Flash Exposure on DC Networks;
  • Figure 18 is a diagram illustrating how the Protective Device System
  • the Protective Device System Configuration Verification Engine 1802 can be integrated within a power analytics server 116 that can be communicatively connected via a network connection 114 with a data acquisition hub 112, a client terminal 128 and a virtual system model database 526.
  • the virtual system model database 526 can be configured to store the virtual system model of the electrical (i.e., monitored) system.
  • the virtual system model can be constantly updated with real-time data from the data acquisition hub 112 to effectively account for any natural aging effects and/or configuration (e.g., device configuration settings, etc.) changes that are made to the hardware that comprise the total electrical power system, thus, mirroring the real-time operating conditions of the system.
  • any natural aging effects and/or configuration e.g., device configuration settings, etc.
  • the Protective Device System Configuration Verification Engine 1802 can be configured to continuously (i.e., in real-time) monitor the device configuration settings (e.g., protection coordination settings, etc.) of the protective devices that are inter-dispersed within a typical electrical power facility and compare them against the preset (pre-programmed) protective device configuration settings that are stored in the virtual system model of the facility to detect and/or warn of any inconsistencies. That is, through a continuous feedback system, the protective device configurations settings and their status (for each protective device) are continuously compared with the design specified protection coordination settings (i.e., preset configuration settings) to detect for any unexpected protective device configuration adjustments that may have been made by technicians/operators to the protective devices during the course of the system's operation.
  • the design specified protection coordination settings i.e., preset configuration settings
  • the user can be warned (through audio, graphical, and/or text based warnings) of any inconsistencies so that corrective action(s) can be taken in order to correct the settings and return the system back to its design parameters for selective coordination and proper protection of the equipment that comprise the electrical system.
  • the warning is presented by the client terminal 128 or on a display that is attached thereto.
  • the warning is provided in a system summary printout/report 1804 that is generated by a printing device that is interfaced with the client terminal.
  • the warning is broadcast on a speaker (or other equivalent audio device) that is operatively interfaced internally or externally to the client terminal 128.
  • the Protective Device In one embodiment, once a discrepancy is detected, the Protective Device
  • System Configuration Verification Engine 1802 is configured to automatically upload the preset protective device configuration settings (stored in the virtual system model) into each protective device on which a discrepancy is detected.
  • the Protective Device System Configuration Verification Engine 1802 is configured to automatically "reset" (into a default setting) any protective device whose configuration settings have been modified and is no longer comparing favorably (i.e., where a discrepancy is detected) with the preset protective device configuration settings stored in the virtual system model of the electrical power system.
  • the data acquisition hub 112 can be communicatively connected via data connections 110 to a plurality of sensors that can be embedded throughout the electrical system 102.
  • the data acquisition hub 112 can be a standalone unit or integrated within the analytics server 116 and can be embodied as a piece of hardware, software, or some combination thereof.
  • the data connections 110 are "hard wired" physical data connections (e.g., serial, network, etc.). For example, a serial or parallel cable connection between the sensors and the hub 112.
  • the data connections 110 are wireless data connections. For example, a radio frequency (RF), BLUETOOTHTM, infrared or equivalent connection between the sensor and the hub 112.
  • RF radio frequency
  • BLUETOOTHTM infrared or equivalent connection between the sensor and the hub 112.
  • the client 128 can be a conventional thin-client or thick-client computing device that can utilize a variety of network interfaces (e.g., web browser, CITRIXTM, WINDOWS TERMINAL SERVICESTM, telnet, or other equivalent thin-client terminal applications, etc.) to access, configure, and modify the sensors (e.g., configuration files, etc.), power analytics engine (e.g., configuration files, analytics logic, etc.), calibration parameters (e.g., configuration files, calibration parameters, etc.), virtual system modeling engine (e.g., configuration files, simulation parameters, choice of contingency event to simulate, etc.), Protective Device System Configuration Verification Engine 1802 (e.g., configuration files, protection coordination schemes, etc.) and virtual system model of the electrical system under management (e.g., virtual system model operating parameters and configuration files).
  • network interfaces e.g., web browser, CITRIXTM, WINDOWS TERMINAL SERVICESTM, telnet, or other equivalent thin-client terminal applications, etc.
  • FIG. 19 is a flowchart illustrating an example process for verifying and monitoring protective device settings within an electrical power distribution network, in accordance with one embodiment.
  • the method 1900 begins with operation 1902 where the Protective Device System Configuration Verification Engine receives real-time protective device configuration data output from one or more sensors that are interfaced to one or more protective devices that are part of the electrical power system (monitored system).
  • the Protective Device System Configuration Verification Engine compares the real-time protective device configuration data to the preset protective device configuration settings stored in a virtual system model of the electrical system.
  • the virtual system model can be stored in a virtual system model database that can be communicatively connected Protective Device System Configuration Verification Engine.
  • step 1906 if a difference between the real-time protective device configuration data and the preset protective device configuration settings is detected, the Protective Device System Configuration Verification Engine generates a warning message.
  • the user can be warned (through audio, graphical, and/or text based warnings) of any inconsistencies so that corrective action(s) can be taken in order to correct the settings and return the system back to its design parameters for selective coordination and proper protection of the equipment that comprise the electrical system.
  • the warning is presented by the client terminal or on a display that is attached thereto.
  • the warning is provided in a system summary printout/report that is generated by a printing device that is interfaced with the client terminal.
  • the warning is broadcast on a speaker (or other equivalent audio device) that is operatively interfaced internally or externally to the client terminal.
  • System Configuration Verification Engine is configured to automatically initiate a synchronization operation to upload the preset protective device configuration settings (stored in the virtual system model) into each protective device on which the discrepancy is detected.
  • the Protective Device System Configuration Verification Engine is configured to initiate a synchronization operation to automatically "reset" (into a default setting) any protective device whose configuration settings have been modified and is no longer comparing favorably (i.e., where the discrepancy is detected) with the preset protective device configuration settings stored in the virtual system model of the electrical power system.
  • the embodiments described herein can be practiced with other computer system configurations including hand-held devices, microprocessor systems, microprocessor- based or programmable consumer electronics, minicomputers, mainframe computers and the like.
  • the embodiments can also be practiced in distributing computing environments where tasks are performed by remote processing devices that are linked through a network.
  • the embodiments described herein can employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Further, the manipulations performed are often referred to in terms, such as producing, identifying, determining, or comparing.
  • any of the operations that form part of the embodiments described herein are useful machine operations.
  • the invention also relates to a device or an apparatus for performing these operations.
  • the systems and methods described herein can be specially constructed for the required purposes, such as the carrier network discussed above, or it may be a general purpose computer selectively activated or configured by a computer program stored in the computer.
  • various general purpose machines may be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
  • Certain embodiments can also be embodied as computer readable code on a computer readable medium.
  • the computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system.
  • Examples of the computer readable medium include hard drives, network attached storage (NAS), read-only memory, random-access memory, CD-ROMs, CD-Rs, CD-RWs, magnetic tapes, and other optical and non-optical data storage devices.
  • the computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Landscapes

  • Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Power Engineering (AREA)
  • Artificial Intelligence (AREA)
  • Evolutionary Computation (AREA)
  • Mathematical Physics (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Remote Monitoring And Control Of Power-Distribution Networks (AREA)
EP08860852A 2007-12-17 2008-12-12 System zur echtzeitüberprüfung und überwachung von schutzvorrichtungseinstellungen in einem stromverteilungsnetz Withdrawn EP2225639A4 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US1437107P 2007-12-17 2007-12-17
PCT/US2008/086656 WO2009079395A1 (en) 2007-12-17 2008-12-12 Real-time system verification and monitoring of protective device settings within an electrical power distribution network

Publications (2)

Publication Number Publication Date
EP2225639A1 true EP2225639A1 (de) 2010-09-08
EP2225639A4 EP2225639A4 (de) 2012-07-18

Family

ID=40795880

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08860852A Withdrawn EP2225639A4 (de) 2007-12-17 2008-12-12 System zur echtzeitüberprüfung und überwachung von schutzvorrichtungseinstellungen in einem stromverteilungsnetz

Country Status (4)

Country Link
EP (1) EP2225639A4 (de)
AU (1) AU2008338563A1 (de)
CA (1) CA2706713A1 (de)
WO (1) WO2009079395A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115719168A (zh) * 2023-01-10 2023-02-28 佰聆数据股份有限公司 基于多电力终端协同的发电设备运行风险分析方法及装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2498363B1 (de) * 2011-03-10 2013-10-09 Accenture Global Services Limited Verbesserung eines Stromverteilungsnetzes für Plug-In-Elektrofahrzeuge
WO2012142355A1 (en) * 2011-04-15 2012-10-18 Abb Technology Ag Dynamic assessment system for high-voltage electrical components
CN103149549B (zh) * 2013-02-05 2015-04-29 重庆市电力公司电力科学研究院 一种基于电能计量装置的数据处理方法和系统
US20160259869A1 (en) * 2015-03-02 2016-09-08 Ca, Inc. Self-learning simulation environments
CN104810926B (zh) * 2015-05-06 2016-09-28 杨启蓓 电网高压断路器多维度大数据分析智能专家系统
CN115549313B (zh) * 2022-11-09 2024-03-08 国网江苏省电力有限公司徐州供电分公司 基于人工智能的用电监测方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7747356B2 (en) * 2002-02-25 2010-06-29 General Electric Company Integrated protection, monitoring, and control system
US7840395B2 (en) * 2006-03-10 2010-11-23 Edsa Micro Corporation Systems and methods for predictive monitoring including real-time strength and security analysis in an electrical power distribution system
WO2007106430A2 (en) * 2006-03-10 2007-09-20 Edsa Micro Corporation Systems and methods for real- time protective device evaluation in an electrical power distribution system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
No further relevant documents disclosed *
See also references of WO2009079395A1 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115719168A (zh) * 2023-01-10 2023-02-28 佰聆数据股份有限公司 基于多电力终端协同的发电设备运行风险分析方法及装置
CN115719168B (zh) * 2023-01-10 2023-04-11 佰聆数据股份有限公司 基于多电力终端协同的发电设备运行风险分析方法及装置

Also Published As

Publication number Publication date
WO2009079395A1 (en) 2009-06-25
EP2225639A4 (de) 2012-07-18
CA2706713A1 (en) 2009-06-25
AU2008338563A1 (en) 2009-06-25

Similar Documents

Publication Publication Date Title
US8165723B2 (en) Real-time system for verification and monitoring of protective device settings within an electrical power distribution network and automatic correction of deviances found
US7844439B2 (en) Systems and methods for real-time protective device evaluation in an electrical power distribution system
US20180189662A1 (en) Systems and Methods for Automatic Real-Time Capacity Assessment for Use in Real-Time Power Analytics of an Electrical Power Distribution System
US7840395B2 (en) Systems and methods for predictive monitoring including real-time strength and security analysis in an electrical power distribution system
US9111057B2 (en) Method for predicting arc flash energy and PPE category within a real-time monitoring system
US8688429B2 (en) System for comparing real-time data and modeling engine data to predict arc flash events
US20190065971A1 (en) Method for Predicting Symmetric, Automated, Real-Time Arc Flash Energy Within a Real-Time Monitoring System
US11113434B2 (en) Method for predicting arc flash energy and PPE category within a real-time monitoring system
EP2225639A1 (de) System zur echtzeitüberprüfung und überwachung von schutzvorrichtungseinstellungen in einem stromverteilungsnetz
US20210326731A1 (en) Systems and Methods for Automatic Real-Time Capacity Assessment for Use in Real-Time Power Analytics of an Electrical Power Distribution System
AU2007264973B2 (en) Systems and methods for providing real-time predictions of arc flash incident energy, arc flash protection boundary, and required personal protective equipment ( PPE ) levels to comply with workplace safety standards
US20210397768A1 (en) Method For Predicting Arc Flash Energy And PPE Category Within A Real-Time Monitoring System
EP2195666A1 (de) Verfahren zur vorhersage einer lichtbogen-blitzenergie und einer ppe-kategorie in einem echtzeitüberwachungssystem
CA2880731A1 (en) Systems and methods for providing real-time predictions of arc flash incident energy, arc flash protection boundary, and required personal protective equipment (ppe) levels to comply with workplace safety standards
EP2047396A2 (de) Systeme und verfahren zum bestimmen der schutzvorrichtungs-löschzeiten, die zur bereitstellung von echtzeitvorhersagen über bogenflashereignisse benutzt werden

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20100526

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA MK RS

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20120620

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 11/30 20060101AFI20120614BHEP

Ipc: G05B 9/02 20060101ALN20120614BHEP

Ipc: G01R 21/00 20060101ALN20120614BHEP

Ipc: G05B 23/02 20060101ALN20120614BHEP

Ipc: G01R 19/25 20060101ALN20120614BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20140701