Simulator 16 User Guide - PowerWorld

Decrease in low bus voltage – This is the minimum amount that a bus voltage must decrease for
a bus low voltage violation to be reported even if the resulting voltage is higher than the bus low
voltage limit. For example, if this value is set to 0.05 pu, the low voltage limit at a bus is 0.90 pu,
the base case voltage at the bus is 1.0 pu, and the post-contingency voltage at the bus is 0.95 pu,
this bus will be reported as a low voltage violation.
Increase in high bus voltage – This is the minimum amount that a bus voltage must increase for
a bus high voltage violation to be reported even if the resulting voltage is lower than the bus high
voltage limit. For example, if this value is set to 0.05 pu, the high voltage limit at a bus is 1.10 pu,
the base case voltage at the bus is 1.0 pu, and the post-contingency voltage at the bus is 1.05 pu,
this bus will be reported as a high voltage violation.
Increase in interface flows – This is the minimum change in interface flow in percentage points
that the loading on an interface must increase so that the interface gets reported as a violation even
if the loading does not exceed the interface limit. For example, if this value is set to 2%, interface
limits are being monitored at 100%, and an interface has a base case loading of 75% and a postcontingency
loading of 77%, this interface will be reported as a violation even though the postcontingency
loading does not exceed the limit.
Caution should be used when using the Always report… options because this may result in a very
large number of reported violations.
Report changes in bus dV/dQ sensitivity
Check this option to enable reporting changes in voltage to reactive power sensitivity for buses in
the post-contingency solution. Set the sensitivity multiplier to the minimum change in sensitivity for
reporting the value(s) under contingency. Any sensitivity that changes by the given multiple will be
reported. You can also define an advanced bus filter using the Define Filter button, and choose
either the newly defined bus filter or a previously existing bus filter for reporting dV/dQ sensitivity
changes at only buses that meet the defined filter.
Also, regardless of the sensitivity multiple setting, any bus that meets the filter and has a negative
dV/dQ will be reported as a violation.
Caution should be used when selecting this option. Calculating the dV/dQ sensitivities requires more
computation time. Define a filter so that the dV/dQ sensitivities are only calculated for those buses
for which it is important to calculate these values.
Report as a violations if a bus becomes disconnected
When checked, buses that become disconnected from the system due to a contingency will be
reported as violations.
Re-reporting of base case violations
This section controls the reporting of Base Case violations. Because the concern of contingency
analysis often is to identify those limitations that result directly from a particular outage or event,
you may desire not to report all violations that were present in the Base Case with each
contingency-specific set of violations. These options allow you to specify just how much of the Base
Case violation information to report for each contingency. It gives you three options:
Do not report Base Case violations
When this option is checked, any element that was violated in the Base Case is omitted from the
set of violations listed for each contingency.
List all Base Case violations for all contingencies
When this option is checked, all elements that were violated in the Base Case and are still
violated post-contingency are included in the set of violations listed for each contingency.
Use these criteria
©2011 PowerWorld Corporation
1056