Evaluation of Openxda For Automatic Fault Analysis
Evaluation of Openxda For Automatic Fault Analysis
Evaluation of Openxda For Automatic Fault Analysis
Presented at the Georgia Tech Fault and Disturbance Analysis Conference, April 27-28, 2015.
Abstract
The high efficiency of fault location calculation is one of the most crucial techniques which has significant influence on the
reliability of power systems. Once an event occurs on a power transmission line, it is followed by a series of automatic device
activities: protections triggered, breakers tripped, load outage, etc. The most stringent mission for the utility is to pinpoint
the fault location, and then to clear the fault, and restore power. The sooner the power supply recovery, the less power
outage, and the better the power system’s reliability. Typically, manual analysis is required to calculate a reasonable and
acceptable fault location result, including faulted line, fault type, and fault location distance. Based on the result, line crews
are targeting to find fault trace in the field. The currently used traditional fault location calculation method is analyzed in this
paper, and several problems have been exposed within it. In order to improve fault location analysis efficiency in utility, GPA
(Grid Power Alliance Co.) proposed a novel application, openXDA (open-source Extensible Disturbance Analytics) to solve
these problems. This project mainly purposes to evaluate openXDA, which targets to realize highly efficient calculations for
saving time, and to obtain a reasonable result which could be close enough to the actual event location for line crews’ work.
It is expected to accomplish a series of analytical processes by automatic calculation, and improve accuracy by using multiple
advanced algorithms and plentiful samples for calculating. In this paper, we use several real fault cases on Dominion Virginia
Power’s transmission network to evaluate openXDA.
Key words: openXDA, power system reliability, automatic fault analysis, fault location
Fig. 4.1 openXDA Result for the Fault on Line 126 a. openXDA Result for the Fault on Line 40