US20160285675A1 - Network management based on modeling of cascading effect of failure - Google Patents

Network management based on modeling of cascading effect of failure Download PDF

Info

Publication number
US20160285675A1
US20160285675A1 US14/745,727 US201514745727A US2016285675A1 US 20160285675 A1 US20160285675 A1 US 20160285675A1 US 201514745727 A US201514745727 A US 201514745727A US 2016285675 A1 US2016285675 A1 US 2016285675A1
Authority
US
United States
Prior art keywords
failure probability
node
network
assets
computing
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.)
Abandoned
Application number
US14/745,727
Inventor
Aanchal Aggarwal
Younghun Kim
Tarun Kumar
Mark A. Lavin
Giuliano Andrea Pagani
Abhishek Raman
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.)
Utopus Insights Inc
Original Assignee
International Business Machines 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 International Business Machines Corp filed Critical International Business Machines Corp
Priority to US14/745,727 priority Critical patent/US20160285675A1/en
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PAGANI, GIULIANO ANDREA, AGGARWAL, AANCHAL, KIM, YOUNGHUN, KUMAR, TARUN, LAVIN, MARK A., Raman, Abhishek
Publication of US20160285675A1 publication Critical patent/US20160285675A1/en
Assigned to UTOPUS INSIGHTS, INC. reassignment UTOPUS INSIGHTS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTERNATIONAL BUSINESS MACHINES CORPORATION
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • H04L41/145Network analysis or design involving simulating, designing, planning or modelling of a network
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N7/00Computing arrangements based on specific mathematical models
    • G06N7/01Probabilistic graphical models, e.g. probabilistic networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0631Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/0636Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis based on a decision tree analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0631Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • H04L41/065Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving logical or physical relationship, e.g. grouping and hierarchies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • H04L41/142Network analysis or design using statistical or mathematical methods
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00Machine learning
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04SSYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them

Definitions

  • the present invention relates to management of a network, and more specifically, to network management based on modeling of the cascading effect of failures.
  • exemplary networks with a number of interdependent assets include a power network (power grid), gas network, and a water network.
  • a power network includes electrical assets (e.g., transformers, switches, fuses) and non-electrical assets (e.g., support structures, poles), each of which can not only fail but also damage other assets within the network.
  • a method of managing a network with assets includes generating, using a processor, a directed graph with each of the assets represented as a node; determining individual failure probability of each node; computing, using the processor, downstream failure probability of each node according to an arrangement of the nodes in the directed graph; computing, using the processor, upstream failure probability of each node according to the arrangement of the nodes in the directed graph; computing network failure probability for each node based on the corresponding individual failure probability, the downstream failure probability, and the upstream failure probability; and managing the network based on the network failure probability of the assets.
  • a network management system to manage assets of the network includes a memory device configured to store instructions, and a processor configured to process the instructions to compute network failure probability associated with each asset based on determining individual failure probability, upstream failure probability, and downstream failure probability for each asset, and to manage the network based on the network failure probabilities of the assets.
  • a computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit to perform a method of managing a network with assets.
  • the method includes generating a directed graph with each of the assets represented as a node; determining individual failure probability of each node; computing downstream failure probability of each node according to an arrangement of the nodes in the directed graph; computing upstream failure probability of each node according to the arrangement of the nodes in the directed graph; computing network failure probability for each node based on the corresponding individual failure probability, the downstream failure probability, and the upstream failure probability; and managing the network based on the network failure probability of the assets.
  • FIG. 1 is a process flow of a method of managing a network according to embodiments of the invention
  • FIG. 2 is an exemplary graph used to identify nodes and connections for embodiments of the invention.
  • FIG. 3 shows processes involved in computing downstream failure probability at block 130 ( FIG. 1 ) for every node according to an embodiment
  • FIG. 4 shows the processes involved in computing upstream failure probability for a given node at block 140 ( FIG. 1 ) according to an embodiment
  • FIG. 5 shows the processes involved in computing physical failure probability for each node at block 150 ( FIG. 1 ) according to an embodiment
  • FIG. 6 shows the processes involved in computing network failure probability for each node at block 160 ( FIG. 1 ) according to an embodiment
  • FIG. 7 is a block diagram of a processing system to implement embodiments of the invention.
  • a network may include a number of assets whose failure affects the individual asset as well as other assets of the network.
  • An accurate assessment of failures and the cascading effect of failures in the network facilitate management of the network.
  • the areas of vulnerability may be identified and addressed.
  • Embodiments of the methods and systems discussed herein relate to modeling the cascading effect of failures in a network and managing the network accordingly. While a power network and associated (electrical and non-electrical) assets are discussed below for explanatory purposes, the embodiments detailed herein are not limited to any one particular type of network.
  • FIG. 1 is a process flow of a method of managing a network according to embodiments of the invention.
  • asset and node are used interchangeably because the representation of the assets in a directed graph is as nodes.
  • generating a directed graph including different node types refers to known techniques for graphing the nodes of the network in a way that shows their interconnections, as further discussed and illustrated below. Determining individual failure probability of every node in the graph at block 120 is independent of interrelationships among nodes, as discussed below. Computing downstream failure probability for every node in the graph, at block 130 , involves computing the probability of a failure downstream of a given node due to the given node, as detailed below.
  • Computing the upstream failure probability for a given node, at block 140 involves an iterative process starting at the first or root node of the graph, as detailed below.
  • the processes include computing physical failure probability for the given node at block 150 and computing network failure probability for the given node at block 160 .
  • managing the network at block 170 may include mitigating failures based on their probability.
  • FIG. 2 is an exemplary graph 200 used to identify nodes 210 and connections 220 for embodiments of the invention.
  • Several nodes 210 of electrical and non-electrical (physical) assets are shown with connections 220 indicating the physical topology of the network.
  • the nodes 210 include non-electrical or physical assets—poles p 1 , p 2 —and electrical assets—transformers t 1 , t 2 , cables c 1 , c 2 , source pp, and endpoint s 2 —as well as an electrical protective device (e.g., fuse) dpd 1 . Steps involved in the generation of the graph 200 are known and are not detailed here.
  • the physical topology is converted into a list of edges.
  • Each edge is an ordered pair of two assets, and it is assumed that electric power flows from the first asset to the second in the ordered pair.
  • the assets are represented by the nodes 210 and the connectivity 220 is defined by the edges.
  • Each of the nodes 210 is classified as a protective electrical asset (e.g., fuse, dynamic protective device) that is able to stop the propagation of a failure, a non-protective electrical asset (e.g., transformer) that does not have any inbuilt protective feature, or a physical asset (e.g., pole) that only has the purpose to house or support an electrical asset in some way.
  • the node 210 pp is the root node (first electrical asset) for purposes of determining upstream failure probability ( 140 , FIG.
  • the assets may be protective gas assets (e.g., check valves), gas assets (e.g., gas pipes, junctions, pumps), and physical assets (e.g., the pipe section supports).
  • protective gas assets e.g., check valves
  • gas assets e.g., gas pipes, junctions, pumps
  • physical assets e.g., the pipe section supports
  • the individual failure probability of each node is determined at block 120 as:
  • N is the set of all nodes of the graph (e.g., all nodes 210 of graph 200 , FIG. 2 ).
  • the reliability R(i) of a given node i may be computed from the failure probability as:
  • the processes involved in determining individual failure include investigating historical failures of each recorded asset failure incident over a specified time period and determining the relationship of the failure rate with attributes of the asset such as, for example, asset type, make, material, and age in order to generate a training model. Once the training model has been generated, failure rates for all nodes (i.e., assets with and without recorded failure histories) may be extrapolated from the training model.
  • FIG. 3 shows processes involved in computing downstream failure probability at block 130 ( FIG. 1 ) for every node according to an embodiment.
  • performing a breadth first search involves traversing the graph (e.g., 200 in FIG. 2 ) by beginning with the root node (e.g., pp in FIG. 2 ) and progressing through the nodes ( 210 , FIG. 2 ) one-at-a-time from the root to its neighbors.
  • identifying and populating two sets of (downstream) children nodes P and Q using depth first search (DFS) means that each branch from the root node to the last node of the branch is traversed before back-tracking to explore each node of the next branch all the way through.
  • DFS depth first search
  • P refers to all non-protective electrical assets that are downstream of the current node and which do not have a protective electrical asset in the path to the current node. If P is being calculated for a sub-node in a branch (in the recursive part of the DFS algorithm), then the P of the current node should not include elements from the P set of the main node of the branch (i.e., elements of the P set will not be repeated).
  • Q refers to all protective electrical assets that are downstream of the current node and do not have any other protective electrical assets in the path to the current node. As an example, if c 1 shown in FIG.
  • the P would be an empty set due to the protective electrical asset dpd 1 (every other downstream node would have dpd 1 in the path to c 1 , the current node), which is the next node after c 1 , and Q would include dpd 1 .
  • the current node may be thought of as being in series with every element in P. That is, because of the absence of a protective electrical asset between the current node and the elements of P, a failure at any node that is an element in P can trigger a failure in the current node. Further, the current node may be thought of as being in series with every element in Q. However, the failure propagation is less straight-forward in this case. Two sub-cases emerge in considering the failure in an element (node) of Q. In a first case, when the protective electrical asset that is an element of Q works as expected, then any downstream failure in a node downstream of the protective electrical device (element of Q) will not affect the current node.
  • Q the set of protective electrical assets downstream of the current node
  • Q the set of protective electrical assets downstream of the current node
  • each element of Q is made the current node, and, at block 320 , P and Q are identified for each current node.
  • Q is empty, then, at block 350 , computing downstream failure probability for the current node i is performed.
  • the probability of downstream failure (P df ) for the i th node is given by:
  • R df is the downstream reliability of the current node and, with R indicating reliability, is given by:
  • R df ⁇ ( i ) ⁇ j ⁇ P ⁇ R ⁇ ( j ) ⁇ ⁇ k ⁇ Q ⁇ [ R ⁇ ( k ) + ( 1 - R ⁇ ( k ) ) ⁇ R df ⁇ ⁇ ( k ) ] [ EQ . ⁇ 4 ]
  • FIG. 4 shows the processes involved in computing upstream failure probability for a given node at block 140 ( FIG. 1 ) according to an embodiment.
  • performing breadth-first searching (BFS) of the graph involves beginning at the root node and moving through the graph to consider each node the current node one-at-a-time, as noted above.
  • BFS breadth-first searching
  • the probability of a failure upstream of the root node is 0.
  • the process at block 150 ( FIG. 1 ) is performed at block 500 , as detailed below.
  • the set of inbound nodes of the current node i is performed.
  • the set of inbound nodes is the set of immediate parents of the current node i.
  • the network failure probability refers to the process completed at block 160 ( FIG. 1 ) for the parent nodes (using G′). That is, because a current node may have multiple nodes in the set Si (multiple immediate parents), the loop defined by blocks 450 , 460 , and 470 ensures that the process shown at FIGS. 4 through 6 is completed for every parent node before the child node is evaluated.
  • the nodes in Si that have not had network failure probability computed are added to an evaluation list.
  • the nodes in the evaluation list are added as nodes to visit (i.e., nodes to process according to the steps shown in FIG. 4 ).
  • upstream failure probability is computed for the current node i.
  • the computation of upstream failure probability P uf of node i is given by:
  • the computation at EQ. 5 requires consideration of a modified directed graph G′ in which the current node i is omitted.
  • the upstream failure probability of the current node i is based on the network failure probability of each immediate parent node of node i (each node in the set Si).
  • the failure probabilities of nodes downstream of i are not counted multiple times (once for each j).
  • FIG. 5 shows the processes 500 involved in computing physical failure probability for each node at block 150 ( FIG. 1 ) according to an embodiment.
  • the processes 500 to implement block 150 ( FIG. 1 ) are reached in multiple ways, each of which ensures that the physical failure probability is considered for each node as the current node.
  • determining the set of nodes Bi includes determining the set of physical assets connected to the current node i. In the exemplary graph 200 of FIG. 1 , if the current node were pp, then the set of Bi would be comprised of p 1 , the pole that is directly connected to pp. The pole p 2 is not part of Bi when the current node is pp.
  • iterating through each element j of Bi begins, at block 530 , with determining if the current node i is the first node among the nodes (electrical assets) that are connected to element j of the set Bi. That is, in the example discussed with reference to FIG. 2 , if pp were the current node i, then pp is the first node (according to the directed graph) among the electrical assets that are connected to p 1 when j is such that the element of Bi is p 1 . If the current node i is not the first node among the (electrical asset) nodes that are connected to the current j element of Bi, then processing returns to block 520 to select the next element in Bi.
  • the physical asset j is added to Ai, which is the set of physical assets that have node i as the first (electrical) asset in the group of assets the physical asset supports, at block 540 . From block 540 , the next physical asset j is selected at block 520 .
  • Ai is an empty set. That is, it is determined if there are no physical assets for which the current node i is the first electrical asset in the group of assets that the physical asset supports. In exemplary FIG. 2 , t 1 , for example, is not the first node supported by any physical asset. Thus, if the current node were t 1 , the resulting Ai would be an empty set.
  • the physical failure probability is set to 0 at block 560 .
  • Ai is not an empty set, then the physical failure probability is computed at block 570 . The computation of the physical failure probability is given by:
  • FIG. 6 shows the processes 600 involved in computing network failure probability for each node at block 160 ( FIG. 1 ) according to an embodiment.
  • network reliability for the current node i is computed as a product of downstream reliability, upstream reliability, individual reliability, and physical reliability. This network reliability is given by:
  • R nf ( i ) R ( i ) ⁇ R df ( i ) ⁇ R uf ( i ) ⁇ R pf ( i ) [EQ. 7]
  • EQ. 7 can also be written as:
  • network failure probability associated with the current node i may be computed as:
  • management of the network can take into account the information generated by the other processes.
  • a node (electrical asset) with a high P nf according to EQ. 9 may be scheduled for inspection and maintenance more frequently than a node with a relatively lower P nf .
  • a threshold may be set for the P nf of any node such that any node whose P nf exceeds the threshold will be maintained as a critical asset. That maintenance may entail more frequency inspection and testing or replacement, for example.
  • FIG. 7 is a processing system 700 configured to implement embodiments described herein.
  • the processes detailed herein may be implemented by one or more processors (processing circuits) 710 based on instructions stored in one or more memory devices 720 .
  • the memory devices 720 may additionally store the training model discussed with reference to block 120 ( FIG. 1 ), for example.
  • the instructions and one or more memory devices 720 represent a computer program product to implement the detailed processes.
  • the processing system 700 may additionally include an input interface 730 (e.g., keyboard, wired or wireless communication link) to receive commands or data, as well as an output interface 740 (e.g., display device, communication link) to send output.
  • the computer program product ( 720 ) and processor 710 may be stand-alone components or may be integrated with other components of the network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Mathematical Physics (AREA)
  • Pure & Applied Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Mathematical Analysis (AREA)
  • Mathematical Optimization (AREA)
  • Algebra (AREA)
  • Software Systems (AREA)
  • Artificial Intelligence (AREA)
  • Evolutionary Computation (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Computational Mathematics (AREA)
  • Medical Informatics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A system and method of managing a network with assets are described. The method includes generating a directed graph with each of the assets represented as a node, determining individual failure probability of each node, computing downstream failure probability of each node according to an arrangement of the nodes in the directed graph, computing upstream failure probability of each node according to the arrangement of the nodes in directed graph, and computing network failure probability for each node based on the corresponding individual failure probability, the downstream failure probability, and the upstream failure probability. Managing the network is based on the network failure probability of the assets.

Description

  • This application is a continuation of U.S. application Ser. No. 14/665,316 filed Mar. 23, 2015, the disclosure of which is incorporated by reference herein in its entirety.
  • BACKGROUND
  • The present invention relates to management of a network, and more specifically, to network management based on modeling of the cascading effect of failures.
  • There are many types of networks that include a number of assets that affect each other. Exemplary networks with a number of interdependent assets include a power network (power grid), gas network, and a water network. For example, a power network includes electrical assets (e.g., transformers, switches, fuses) and non-electrical assets (e.g., support structures, poles), each of which can not only fail but also damage other assets within the network.
  • SUMMARY
  • According to one embodiment of the present invention, a method of managing a network with assets includes generating, using a processor, a directed graph with each of the assets represented as a node; determining individual failure probability of each node; computing, using the processor, downstream failure probability of each node according to an arrangement of the nodes in the directed graph; computing, using the processor, upstream failure probability of each node according to the arrangement of the nodes in the directed graph; computing network failure probability for each node based on the corresponding individual failure probability, the downstream failure probability, and the upstream failure probability; and managing the network based on the network failure probability of the assets.
  • According to another embodiment, a network management system to manage assets of the network includes a memory device configured to store instructions, and a processor configured to process the instructions to compute network failure probability associated with each asset based on determining individual failure probability, upstream failure probability, and downstream failure probability for each asset, and to manage the network based on the network failure probabilities of the assets.
  • According to yet another embodiment, a computer program product includes a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit to perform a method of managing a network with assets. The method includes generating a directed graph with each of the assets represented as a node; determining individual failure probability of each node; computing downstream failure probability of each node according to an arrangement of the nodes in the directed graph; computing upstream failure probability of each node according to the arrangement of the nodes in the directed graph; computing network failure probability for each node based on the corresponding individual failure probability, the downstream failure probability, and the upstream failure probability; and managing the network based on the network failure probability of the assets.
  • Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with the advantages and the features, refer to the description and to the drawings.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The forgoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
  • FIG. 1 is a process flow of a method of managing a network according to embodiments of the invention;
  • FIG. 2 is an exemplary graph used to identify nodes and connections for embodiments of the invention;
  • FIG. 3 shows processes involved in computing downstream failure probability at block 130 (FIG. 1) for every node according to an embodiment;
  • FIG. 4 shows the processes involved in computing upstream failure probability for a given node at block 140 (FIG. 1) according to an embodiment;
  • FIG. 5 shows the processes involved in computing physical failure probability for each node at block 150 (FIG. 1) according to an embodiment;
  • FIG. 6 shows the processes involved in computing network failure probability for each node at block 160 (FIG. 1) according to an embodiment; and
  • FIG. 7 is a block diagram of a processing system to implement embodiments of the invention.
  • DETAILED DESCRIPTION
  • As noted above, a network may include a number of assets whose failure affects the individual asset as well as other assets of the network. An accurate assessment of failures and the cascading effect of failures in the network facilitate management of the network. The areas of vulnerability may be identified and addressed. Embodiments of the methods and systems discussed herein relate to modeling the cascading effect of failures in a network and managing the network accordingly. While a power network and associated (electrical and non-electrical) assets are discussed below for explanatory purposes, the embodiments detailed herein are not limited to any one particular type of network.
  • FIG. 1 is a process flow of a method of managing a network according to embodiments of the invention. Throughout the discussion herein, asset and node are used interchangeably because the representation of the assets in a directed graph is as nodes. At block 110, generating a directed graph including different node types refers to known techniques for graphing the nodes of the network in a way that shows their interconnections, as further discussed and illustrated below. Determining individual failure probability of every node in the graph at block 120 is independent of interrelationships among nodes, as discussed below. Computing downstream failure probability for every node in the graph, at block 130, involves computing the probability of a failure downstream of a given node due to the given node, as detailed below. Computing the upstream failure probability for a given node, at block 140, involves an iterative process starting at the first or root node of the graph, as detailed below. The processes include computing physical failure probability for the given node at block 150 and computing network failure probability for the given node at block 160. Based on the computations and determinations that are further discussed below, managing the network at block 170 may include mitigating failures based on their probability.
  • FIG. 2 is an exemplary graph 200 used to identify nodes 210 and connections 220 for embodiments of the invention. Several nodes 210 of electrical and non-electrical (physical) assets are shown with connections 220 indicating the physical topology of the network. In the exemplary graph 200, the nodes 210 include non-electrical or physical assets—poles p1, p2—and electrical assets—transformers t1, t2, cables c1, c2, source pp, and endpoint s2—as well as an electrical protective device (e.g., fuse) dpd1. Steps involved in the generation of the graph 200 are known and are not detailed here. Generally, the physical topology is converted into a list of edges. Each edge is an ordered pair of two assets, and it is assumed that electric power flows from the first asset to the second in the ordered pair. The assets are represented by the nodes 210 and the connectivity 220 is defined by the edges. Each of the nodes 210 is classified as a protective electrical asset (e.g., fuse, dynamic protective device) that is able to stop the propagation of a failure, a non-protective electrical asset (e.g., transformer) that does not have any inbuilt protective feature, or a physical asset (e.g., pole) that only has the purpose to house or support an electrical asset in some way. In the exemplary graph 200, the node 210 pp is the root node (first electrical asset) for purposes of determining upstream failure probability (140, FIG. 1), which is detailed further below. As noted above, the embodiments detailed herein are not limited to a power network. In a gas network, for example, the assets may be protective gas assets (e.g., check valves), gas assets (e.g., gas pipes, junctions, pumps), and physical assets (e.g., the pipe section supports).
  • The individual failure probability of each node is determined at block 120 as:

  • P f(i)∀i ∈N   [EQ. 1]
  • N is the set of all nodes of the graph (e.g., all nodes 210 of graph 200, FIG. 2). The reliability R(i) of a given node i may be computed from the failure probability as:

  • R(i)=1−P f(i)   [EQ. 2]
  • The processes involved in determining individual failure include investigating historical failures of each recorded asset failure incident over a specified time period and determining the relationship of the failure rate with attributes of the asset such as, for example, asset type, make, material, and age in order to generate a training model. Once the training model has been generated, failure rates for all nodes (i.e., assets with and without recorded failure histories) may be extrapolated from the training model.
  • FIG. 3 shows processes involved in computing downstream failure probability at block 130 (FIG. 1) for every node according to an embodiment. At block 310, performing a breadth first search (BFS) involves traversing the graph (e.g., 200 in FIG. 2) by beginning with the root node (e.g., pp in FIG. 2) and progressing through the nodes (210, FIG. 2) one-at-a-time from the root to its neighbors. At block 320, identifying and populating two sets of (downstream) children nodes P and Q using depth first search (DFS) means that each branch from the root node to the last node of the branch is traversed before back-tracking to explore each node of the next branch all the way through. P refers to all non-protective electrical assets that are downstream of the current node and which do not have a protective electrical asset in the path to the current node. If P is being calculated for a sub-node in a branch (in the recursive part of the DFS algorithm), then the P of the current node should not include elements from the P set of the main node of the branch (i.e., elements of the P set will not be repeated). Q refers to all protective electrical assets that are downstream of the current node and do not have any other protective electrical assets in the path to the current node. As an example, if c1 shown in FIG. 2 were the current node, the P would be an empty set due to the protective electrical asset dpd1 (every other downstream node would have dpd1 in the path to c1, the current node), which is the next node after c1, and Q would include dpd1.
  • Based on the definitions of P and Q, the current node may be thought of as being in series with every element in P. That is, because of the absence of a protective electrical asset between the current node and the elements of P, a failure at any node that is an element in P can trigger a failure in the current node. Further, the current node may be thought of as being in series with every element in Q. However, the failure propagation is less straight-forward in this case. Two sub-cases emerge in considering the failure in an element (node) of Q. In a first case, when the protective electrical asset that is an element of Q works as expected, then any downstream failure in a node downstream of the protective electrical device (element of Q) will not affect the current node. In the second case, however, when the protective electrical asset (element of Q) fails, then a failure in a node downstream of the protective electrical asset (and the current node) will propagate and cause the current node to fail, as well. Both of these cases must be considered.
  • At block 330, it is determined if Q (the set of protective electrical assets downstream of the current node) is empty. If Q is not empty, then, at block 340, each element of Q is made the current node, and, at block 320, P and Q are identified for each current node. If Q is empty, then, at block 350, computing downstream failure probability for the current node i is performed. The probability of downstream failure (Pdf) for the ith node is given by:

  • P df(i)=1−R df(i)   [EQ. 3]
  • Rdf is the downstream reliability of the current node and, with R indicating reliability, is given by:
  • R df ( i ) = j P R ( j ) k Q [ R ( k ) + ( 1 - R ( k ) ) R df ( k ) ] [ EQ . 4 ]
  • At block 360, following computation of the probability of downstream failure, setting the next node in the graph as the current node is per the BFS.
  • FIG. 4 shows the processes involved in computing upstream failure probability for a given node at block 140 (FIG. 1) according to an embodiment. At block 410, performing breadth-first searching (BFS) of the graph (e.g., 200, FIG. 2) involves beginning at the root node and moving through the graph to consider each node the current node one-at-a-time, as noted above. At block 420, it is determined whether the current node is the root node. If the current node is the root node, then the upstream failure probability of the current node is set to 0 at block 430. This is because the root node is the most upstream node in the graph (see e.g., p1 in FIG. 2). Thus, the probability of a failure upstream of the root node is 0. From block 430, the process at block 150 (FIG. 1) is performed at block 500, as detailed below. If the current node is not the root node, then, at block 440, determining Si, the set of inbound nodes of the current node i is performed. The set of inbound nodes is the set of immediate parents of the current node i. At block 450, it is determined whether the network failure probability has already been computed for every node that is an element of the set Si. As detailed below with reference to EQ. 5, the network failure probability of every node in the set Si is determined using a modified directed graph G′ that excludes the current node i. The network failure probability refers to the process completed at block 160 (FIG. 1) for the parent nodes (using G′). That is, because a current node may have multiple nodes in the set Si (multiple immediate parents), the loop defined by blocks 450, 460, and 470 ensures that the process shown at FIGS. 4 through 6 is completed for every parent node before the child node is evaluated.
  • If it is determined at block 450 that the network failure probability has not been computed for every node in the set Si of the current node, then, at block 460, the nodes in Si that have not had network failure probability computed are added to an evaluation list. At block 470, the nodes in the evaluation list are added as nodes to visit (i.e., nodes to process according to the steps shown in FIG. 4). If it is determined at block 450 that the network failure probability (Pnf) has been computed for every node in the set Si of the current node (every immediate parent of the current node), then, at block 480, upstream failure probability is computed for the current node i. The computation of upstream failure probability Puf of node i is given by:
  • P uf ( i ) = j S i P nfG ( j ) [ EQ . 5 ]
  • The computation at EQ. 5 requires consideration of a modified directed graph G′ in which the current node i is omitted. The upstream failure probability of the current node i is based on the network failure probability of each immediate parent node of node i (each node in the set Si). By determining the network failure probability of each node in the set Si based on the modified directed graph G′ (which does not include the current node i), the failure probabilities of nodes downstream of i (in the original directed graph) are not counted multiple times (once for each j). Once the upstream failure probability is computed at block 480, the node i is removed from the evaluation list at block 490 and the next node is considered at block 410. Additionally, once the upstream failure probability is computed at block 480, the process at block 150 (FIG. 1) is performed at block 500 as detailed below.
  • FIG. 5 shows the processes 500 involved in computing physical failure probability for each node at block 150 (FIG. 1) according to an embodiment. As FIG. 4 indicates and as discussed above, the processes 500 to implement block 150 (FIG. 1) are reached in multiple ways, each of which ensures that the physical failure probability is considered for each node as the current node. At block 510, determining the set of nodes Bi includes determining the set of physical assets connected to the current node i. In the exemplary graph 200 of FIG. 1, if the current node were pp, then the set of Bi would be comprised of p1, the pole that is directly connected to pp. The pole p2 is not part of Bi when the current node is pp. At block 520, iterating through each element j of Bi begins, at block 530, with determining if the current node i is the first node among the nodes (electrical assets) that are connected to element j of the set Bi. That is, in the example discussed with reference to FIG. 2, if pp were the current node i, then pp is the first node (according to the directed graph) among the electrical assets that are connected to p1 when j is such that the element of Bi is p1. If the current node i is not the first node among the (electrical asset) nodes that are connected to the current j element of Bi, then processing returns to block 520 to select the next element in Bi. If the current node i is the first node among the (electrical asset) nodes that are connected to the current j element of Bi, then the physical asset j is added to Ai, which is the set of physical assets that have node i as the first (electrical) asset in the group of assets the physical asset supports, at block 540. From block 540, the next physical asset j is selected at block 520.
  • When all the physical assets in Bi have been processed, then, at block 550, it is determined if Ai is an empty set. That is, it is determined if there are no physical assets for which the current node i is the first electrical asset in the group of assets that the physical asset supports. In exemplary FIG. 2, t1, for example, is not the first node supported by any physical asset. Thus, if the current node were t1, the resulting Ai would be an empty set. When Ai is an empty set, then the physical failure probability is set to 0 at block 560. When Ai is not an empty set, then the physical failure probability is computed at block 570. The computation of the physical failure probability is given by:
  • P pf ( i ) = j A i P f ( j ) [ EQ . 6 ]
  • Whether the physical failure probability is computed (at block 570) or set to 0 (at block 560), the process at block 160 (FIG. 1) is then performed as discussed with reference to FIG. 6.
  • FIG. 6 shows the processes 600 involved in computing network failure probability for each node at block 160 (FIG. 1) according to an embodiment. At block 610, network reliability for the current node i is computed as a product of downstream reliability, upstream reliability, individual reliability, and physical reliability. This network reliability is given by:

  • R nf(i)=R(iR df(iR uf(iR pf(i)   [EQ. 7]
  • EQ. 7 can also be written as:

  • R nf(i)=(1−P f(i))·(1−P df(i))·(1−P uf(i))·(1−P pf(i))   [EQ. 8]
  • Based on the computed network reliability, network failure probability associated with the current node i may be computed as:

  • P nf(i)=1−R nf(i)   [EQ. 9]
  • The processes detailed above provide information about the probability of network failure associated with each given electrical asset. As such, at block 170 (FIG. 1), management of the network can take into account the information generated by the other processes. For example, a node (electrical asset) with a high Pnf according to EQ. 9 may be scheduled for inspection and maintenance more frequently than a node with a relatively lower Pnf. As another example, a threshold may be set for the Pnf of any node such that any node whose Pnf exceeds the threshold will be maintained as a critical asset. That maintenance may entail more frequency inspection and testing or replacement, for example.
  • FIG. 7 is a processing system 700 configured to implement embodiments described herein. The processes detailed herein may be implemented by one or more processors (processing circuits) 710 based on instructions stored in one or more memory devices 720. The memory devices 720 may additionally store the training model discussed with reference to block 120 (FIG. 1), for example. The instructions and one or more memory devices 720 represent a computer program product to implement the detailed processes. The processing system 700 may additionally include an input interface 730 (e.g., keyboard, wired or wireless communication link) to receive commands or data, as well as an output interface 740 (e.g., display device, communication link) to send output. The computer program product (720) and processor 710 may be stand-alone components or may be integrated with other components of the network.
  • The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one more other features, integers, steps, operations, element components, and/or groups thereof.
  • The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated
  • The flow diagrams depicted herein are just one example. There may be many variations to this diagram or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order or steps may be added, deleted or modified. All of these variations are considered a part of the claimed invention. Further, as noted above, although an electrical network is predominantly discussed as an exemplary network, the flow diagrams herein and the discussion pertain to any network with assets in which failures may propagate in both directions from the perspective of a directed graph.
  • While the preferred embodiment to the invention had been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described.
  • The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (9)

What is claimed is:
1. A network management system to manage assets of the network, the management system comprising:
a memory device configured to store instructions; and
a processor configured to process the instructions to compute network failure probability associated with each asset based on determining individual failure probability, upstream failure probability, and downstream failure probability for each asset, and to manage the network based on the network failure probabilities of the assets.
2. A computer program product comprising:
a tangible storage medium readable by a processing circuit and storing instructions for execution by the processing circuit to perform a method of managing a network with assets, the method comprising:
generating a directed graph with each of the assets represented as a node;
determining individual failure probability of each node;
computing downstream failure probability of each node according to an arrangement of the nodes in the directed graph;
computing upstream failure probability of each node according to the arrangement of the nodes in directed graph;
computing network failure probability for each node based on the corresponding individual failure probability, the downstream failure probability, and the upstream failure probability; and
managing the network based on the network failure probability of the assets.
3. The computer program product according to claim 2, wherein the method further comprises classifying each node in the directed graph, wherein the network is an electric power network and the classifying each node includes classifying each node as a non-protective electrical asset, a protective electrical asset, or a physical asset.
4. The computer program product according to claim 2, wherein the determining the individual failure probability of each node includes extrapolating from a training model that is trained with historical data.
5. The computer program product according to claim 2, wherein the computing the downstream failure probability for each node is based on a classification of one or more assets downstream of the node.
6. The computer program product according to claim 2, wherein the computing the upstream failure probability for each node involves an iterative process.
7. The computer program product according to claim 6, wherein the computing the upstream failure probability for each node is based on the network failure probability of upstream nodes in a modified directed graph that omits the node.
8. The computer program product according to claim 2, wherein the managing the network based on the network failure probability of the assets includes modifying an inspection and maintenance schedule of the assets based on the network failure probability of the assets.
9. The computer program product according to claim 2, wherein the managing the network based on the network failure probability of the assets includes setting a threshold network failure probability and, when the network failure probability of one of the assets exceeds the threshold network failure probability, managing the one of the assets as a critical asset.
US14/745,727 2015-03-23 2015-06-22 Network management based on modeling of cascading effect of failure Abandoned US20160285675A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/745,727 US20160285675A1 (en) 2015-03-23 2015-06-22 Network management based on modeling of cascading effect of failure

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/665,316 US10389600B2 (en) 2015-03-23 2015-03-23 Network management based on modeling of cascading effect of failure
US14/745,727 US20160285675A1 (en) 2015-03-23 2015-06-22 Network management based on modeling of cascading effect of failure

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/665,316 Continuation US10389600B2 (en) 2015-03-23 2015-03-23 Network management based on modeling of cascading effect of failure

Publications (1)

Publication Number Publication Date
US20160285675A1 true US20160285675A1 (en) 2016-09-29

Family

ID=56975468

Family Applications (4)

Application Number Title Priority Date Filing Date
US14/665,316 Active 2036-12-20 US10389600B2 (en) 2015-03-23 2015-03-23 Network management based on modeling of cascading effect of failure
US14/745,727 Abandoned US20160285675A1 (en) 2015-03-23 2015-06-22 Network management based on modeling of cascading effect of failure
US16/546,276 Active 2037-08-05 US11683238B2 (en) 2015-03-23 2019-08-20 Network management based on modeling of cascading effect of failure
US18/314,628 Pending US20240007357A1 (en) 2015-03-23 2023-05-09 Network management based on modeling of cascading effect of failure

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US14/665,316 Active 2036-12-20 US10389600B2 (en) 2015-03-23 2015-03-23 Network management based on modeling of cascading effect of failure

Family Applications After (2)

Application Number Title Priority Date Filing Date
US16/546,276 Active 2037-08-05 US11683238B2 (en) 2015-03-23 2019-08-20 Network management based on modeling of cascading effect of failure
US18/314,628 Pending US20240007357A1 (en) 2015-03-23 2023-05-09 Network management based on modeling of cascading effect of failure

Country Status (1)

Country Link
US (4) US10389600B2 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160116527A1 (en) * 2014-10-27 2016-04-28 Qualcomm Incorporated Stochastic and topologically aware electromigration analysis methodology
US20160285691A1 (en) * 2015-03-23 2016-09-29 International Business Machines Corporation Network management based on assessment of topological robustness and criticality of assets
US11435880B1 (en) * 2018-09-11 2022-09-06 Palantir Technologies Inc. User interfaces for displaying discretized elements of logical flow systems
CN115442222A (en) * 2022-07-29 2022-12-06 北京云狐信息有限公司 Network fault positioning method based on machine learning
US11683238B2 (en) 2015-03-23 2023-06-20 Utopus Insights, Inc. Network management based on modeling of cascading effect of failure

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190324832A1 (en) * 2018-04-18 2019-10-24 Alberto Avritzer Metric for the assessment of distributed high-availability architectures using survivability modeling

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2003302883A1 (en) 2002-12-12 2004-06-30 Nitin S. Bhagat Optimal feeder design in distribution system planning
US20050034023A1 (en) 2002-12-16 2005-02-10 Maturana Francisco P. Energy management system
KR101102384B1 (en) * 2003-08-14 2012-01-05 엘지전자 주식회사 Optical disc and recording method, recording/reproducing apparatus and recording/reproducing system
US8401709B2 (en) 2009-11-03 2013-03-19 Spirae, Inc. Dynamic distributed power grid control system
US8504214B2 (en) 2010-06-18 2013-08-06 General Electric Company Self-healing power grid and method thereof
CN103154845A (en) 2010-07-16 2013-06-12 纽约市哥伦比亚大学托管会 Machine learning for power grids
US9043037B2 (en) 2011-11-10 2015-05-26 International Business Machines Corporation Monitoring and optimizing an electrical grid state
EP2791744A4 (en) * 2011-12-16 2015-06-10 Schneider Electric Usa Inc Co-location electrical architecture
US9520717B2 (en) 2012-04-18 2016-12-13 Abb Research Ltd. Distributed electrical power network model maintenance
US9166907B2 (en) 2013-01-17 2015-10-20 Purdue Research Foundation Failure repair sequence generation for nodal network
SG10201407299RA (en) * 2013-11-08 2015-06-29 Accenture Global Services Ltd Network node failure predictive system
US10389117B2 (en) * 2014-05-13 2019-08-20 Georgia Tech Research Corporation Dynamic modeling and resilience for power distribution
US9923778B2 (en) 2015-03-23 2018-03-20 Utopus Insights, Inc. Network management based on assessment of topological robustness and criticality of assets
US20160283874A1 (en) 2015-03-23 2016-09-29 International Business Machines Corporation Failure modeling by incorporation of terrestrial conditions
US10389600B2 (en) 2015-03-23 2019-08-20 Utopus Insights, Inc. Network management based on modeling of cascading effect of failure

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Steinder et al. "Probabilistic Fault Localization in Communication Systems Using Belief Networks", IEEE/ACM Trans. Networking, 2004, pp 809-822) *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160116527A1 (en) * 2014-10-27 2016-04-28 Qualcomm Incorporated Stochastic and topologically aware electromigration analysis methodology
US20160285691A1 (en) * 2015-03-23 2016-09-29 International Business Machines Corporation Network management based on assessment of topological robustness and criticality of assets
US20160285689A1 (en) * 2015-03-23 2016-09-29 International Business Machines Corporation Network management based on assessment of topological robustness and criticality of assets
US9923778B2 (en) * 2015-03-23 2018-03-20 Utopus Insights, Inc. Network management based on assessment of topological robustness and criticality of assets
US9992069B2 (en) * 2015-03-23 2018-06-05 Utopus Insights, Inc. Network management based on assessment of topological robustness and criticality of assets
US10778529B2 (en) * 2015-03-23 2020-09-15 Utopus Insights, Inc. Network management based on assessment of topological robustness and criticality of assets
US11552854B2 (en) 2015-03-23 2023-01-10 Utopus Insights, Inc. Network management based on assessment of topological robustness and criticality of assets
US11683238B2 (en) 2015-03-23 2023-06-20 Utopus Insights, Inc. Network management based on modeling of cascading effect of failure
US11435880B1 (en) * 2018-09-11 2022-09-06 Palantir Technologies Inc. User interfaces for displaying discretized elements of logical flow systems
US20230003565A1 (en) * 2018-09-11 2023-01-05 Palantir Technologies Inc. User interfaces for displaying discretized elements of logical flow systems
US11898890B2 (en) * 2018-09-11 2024-02-13 Palantir Technologies Inc. User interfaces for displaying discretized elements of logical flow systems
CN115442222A (en) * 2022-07-29 2022-12-06 北京云狐信息有限公司 Network fault positioning method based on machine learning

Also Published As

Publication number Publication date
US20240007357A1 (en) 2024-01-04
US11683238B2 (en) 2023-06-20
US20200112488A1 (en) 2020-04-09
US20160283850A1 (en) 2016-09-29
US10389600B2 (en) 2019-08-20

Similar Documents

Publication Publication Date Title
US11683238B2 (en) Network management based on modeling of cascading effect of failure
US11552854B2 (en) Network management based on assessment of topological robustness and criticality of assets
WO2020211356A1 (en) Relay protection system risk assessment and fault positioning method and apparatus, and device and medium
CN110995482B (en) Alarm analysis method and device, computer equipment and computer readable storage medium
Silva et al. An effective algorithm for computing all‐terminal reliability bounds
US9166907B2 (en) Failure repair sequence generation for nodal network
CN106643765A (en) Method for calculating collection abnormality maintenance time
CN105721207A (en) Method and device for determining importance of communication nodes in power communication network
Lee et al. Benders decomposition approach for the robust network design problem with flow bifurcations
Applegate et al. Framework for probabilistic vulnerability analysis of interdependent infrastructure systems
EP3072200B1 (en) Holistic optimization of distribution automation using survivability modeling to support storm hardening
CN104008455B (en) Forward-back substitution method for reliability assessment of complex radial power distribution networks
Faddoul et al. Incorporating Bayesian networks in Markov decision processes
CN113191074A (en) Machine room power supply parameter detection method for data center
Hu et al. Determination of optimal MR&R policies for retaining life-cycle connectivity of bridge networks
CN113922347B (en) Ground protection fixed value optimization method, system and storage medium based on mismatch evaluation index
CN113011664B (en) Logistics aging monitoring method and device, electronic equipment and storage medium
CN105656721A (en) Method and device for determining invulnerability entropy of electric power communication network
Bessani et al. A hierarchical framework for complex networks robustness analysis to errors
Sharda et al. Smart Grid Communication Network Reliability Assessment Using Graphical Computational Model
CN108964954B (en) Method and device for processing outage network element information
Rahman et al. A component level approach to the earthquake vulnerability of critical infrastructure facilities
Arshad et al. Development of transmission line failure rate model using polynomial regression
KR101763860B1 (en) Apparatus and Method for deleting all event having elapsed time in event queue
Juan-Pablo et al. An Importance Function to Generate Scenarios for Training a Grey-Box Model for the Computational Risk Assessment of Cyber-Physical Systems

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AGGARWAL, AANCHAL;KIM, YOUNGHUN;KUMAR, TARUN;AND OTHERS;SIGNING DATES FROM 20150313 TO 20150315;REEL/FRAME:035987/0070

AS Assignment

Owner name: UTOPUS INSIGHTS, INC., NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:042700/0530

Effective date: 20170313

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION