DC Contingency Analysis
Summary
Several main functions are provided
by the contingency analysis group:
- Fast and complete screening of contingency violations using
a DC load flow solution, including a summary/statistics analysis
on specified contingencies, and a parametric DC contingency
analysis, which performs contingency analysis at zero and maximum
specified study transfer levels simultaneously. This group has
more (pre-shift) capabilities than Activity DCCC in PSS™E
as it compares two transfer levels and can be combined with
other interactive contingency analysis functions.
- A detailed contingency analysis reports all violations for
selected contingencies, contingency elementary events, island
composition, and data error checks.
- A new explicit contingency input file can be generated from
the contingency file that uses single branch, double branch,
or generator outage specifications.
- Contingencies can be excluded/included "on the fly"
from further transfer limit analysis.
[top]
Statistics
on Specified Contingencies
Statistic functions summarize statistics
on all specified contingencies. This function classifies all contingencies
in several categories. This function also shows the number of
the currently excluded contingencies according to the used EXCLUDE
files and contingencies that were excluded "on the fly".
[top]
Contingency
Summary
Below are examples of two examples
of a violations summary report. The main difference between these
two reports is that the first report shown compares the initial
case and the final case with the study transfer at the specified
value. Also, the second report does not contain violations that
have response factors (OTDF) below 0.02 (a user-specified threshold).
[top]
Monitored
Element Violations
This function reports all monitored
elements that are violated in the selected contingencies. Branch
violations are always reported in percent of a rating applied.
Interface violations are shown in MW. LowViol means that a branch
is overloaded with flow coming from the second reported bus. It
is possible (though unlikely) that the same branch has LowViol
and UppViol, which means that the flow on the branch can have
a different direction for different contingencies.
In the case of a large number of
violations under different contingencies, this report allows fast
identification of multiple violations of the same constraints
under different contingencies. For example, if the same constraint
is violated under all contingencies, it is likely a base case
problem.
[top]
Contingency
Violations Summary
This function reports all contingencies
with violations among the user selected subset of contingencies.
Three reported columns contain contingency branch flow, total
number of violations caused by the reported contingency, and the
worst violation for the initial and final cases.
[top]
Contingency
List
The contingency summary list report
provides summary information (one line per contingency) for user-selected
contingencies. Also, this report provides contingency indices
that can be used by other contingency analysis functions. Reviewing
this report identifies potential data errors and provide a convenient
overview on selected contingencies.
[top]
Detailed
Contingency Report
A detailed contingency report provides
the following information on selected contingencies:
- Detailed contingency description including the listing of
all contingency events. For branch opening events, it will report
branch flow at initial and maximum study transfer levels. A
user has the option to suppress detailed reporting of dispatch
events, which can be quite numerous.
- List all the monitored elements with loading above user-specified
loading level threshold. Selecting 100% loading level causes
reporting overloads only.
- Island composition for contingencies that create buses not
connected to the swing bus.
[top]
|
