Transmission - Security Constrained Unit Commitment and Dispatch

Then (using the fact that P̃_nm is set to δP_n):

Define a sensitivity factor δ as the ratio of the change in phase angle θ, anywhere in the system, to the original power P_nm flowing over the line nm before it was dropped. This is:

If neither n nor m is the system references bus, two injections, δP_n and δP_m, are imposed at buses n and m respectively. This gives a change in phase angle at bus i equal to:

δ θ_i = X_in P_n + X_im δP_m

Then using the relationship between δP_n and δP_m, the resulting δ factor is:

If either n or m is the reference bus, only one injection is made. The resulting factors are:

If bus i itself is the reference bus, then δ_i,nm=0 since the reference bus angle is constant. The expression for d_l,k is:

If neither i nor j is the reference bus:

3. Generator Contingencies

Generation Shift Factor Calculations for the Single Slack

The PTDF is calculated as follows:

δθ=[X]δP

Where line l connects from bus n to bus m. Let the power injection change at bus i be one MW, δP_i, and the slack bus will absorb same amount of power, δP_slack=-δP_i.

The power angle changes at bus n and bus m are

δ θ_n = X_n,i δP_i

δ θ_m = X_m,i δP_i

Then, the flow change at line l is

Then the generator shift factor from bus i to line l is

Generation Shift Factor Calculation for the Distributed Slack

In the distributed slack case, one MW injection at bus i will be absorbed by multiple slack buses.

where bus sj is one of the slack buses. In the form of vector, the bus injection at bus i and the slack buses is:

Then power angle changes at bus n and bus m are

The flow change at line l is:

Then the generator shift factor from bus i to line l is

From this equation, we notice that there is an extra term,
, in the generator shift factor for the distributed slack as opposed to the single slack bus. In the single slack bus case, δP_sj=0 and δP_sn=-δP_i , and also θ_sn=0 which results in
and α_l,i is reduced to PTDF_l,i as shown above.

Flow Constraint Changes due to the Generator Outage

In both cases of single or distributed slack, the flow constraint for the generator outage bus i is:

Where P_i⁰ is the pre-contingency generation from the generator at bus i.

4. N-x Contingency Analysis

The SCUC in PLEXOS can also support the "N-x" contingency analysis, a standard of North American Electric Reliability Corporation (NERC) that ensures "two or more simultaneous contingencies will not propagate into a cascading blackout".

Three kinds of transmission elements can be selected as contingency object, Line, Transformer and Generator. Multiple elements selected in one contingency object will automatically enable the N-x contingency analysis in PLEXOS.

There are two important principles for DC-OPF based N-x contingency analysis:

• All the contingency elements are coupled together. The post-contingency solution for N-x is not equal to the sum of all the N-1 conditions.
• The calculation sequence of the contingency elements will not affect the final post-contingency power flow solution.

The contingency shift factor derived in section 9.1 is still applicable as below.

However, the [X] matrix of the network has to be updated every time after an AC line or AC transformer outage. The impedance matrix, [X] matrix is updated by eliminating the susceptance contributions from the outaged element, i.e. line k (from n to m).

where e_k is the line k connection vector,


x_k is the susceptance of line k.

Each element of [X] is updated as below:

Example

If an N-2 contingency is defined as {k, w}, where AC line k and w are set as contingency objects. The post-contingency power flow after line k (from n to m) outage on line l will be calculated as

where f_l⁰ and f_k⁰ are the pre-contingency power flows;

d_l,k is the contingency shift factor calculated based on original network.

In order to further analysis the line w (from a to b) outage, the network topology and susceptance matrix have to be updated by taking line k out. The new [X] matrix is then expressed as [X]^-k.

Then the post-contingency power flow on line l will be finally calculated as

where -> f_l⁰, f_k⁰ and f_w⁰ are the pre-contingency power flows;

f'_l and f'_w are the power flows after line k outage;

d_l,k and d_l,w are the contingency shift factor calculated based on original network;

d_l,w'^-k is the contingency shift factor calculated based on the network after line k outage.

The generator outage in N-x contingency analysis is generally the same as in N-1 cases.

5. SCUC on Large-scale Networks

SCUC is a challenging problem to solve because the number of constraints implied is very large. For each contingency we are considering the limits on all lines by computing their post-contingency flow. Thus the number of flow limits imposed can be huge. To limit the number of limits considered in SCUC do the following:

• Set the Transmission SCUC Constraint Voltage Threshold attribute to set a voltage level at or above which line limits are monitored; and/or
• Limit the set of Line limits considered by adding specific Line objects into the Contingency Monitored Lines collection for each Contingency

Using the latter method it is possible to consider a large number of contingencies even on a large-scale network.

6. SCUC and Interfaces

Interface objects are normally defined with limits (Max Flow and Min Flow) that account for contingencies, thus the PLEXOS SCUC algorithm does not monitor post-contingency flows on Interface flows by default. You can however select Interface objects whose post-contingency flows should be monitored using the Contingency Monitored Interfaces collection i.e. for each Contingency add the set of Interface objects to be monitored into the collection.

7. Example

We illustrate the use of SCUC in PLEXOS using the 7-Node network described in Section 9.6. We solve three cases:

1. Economic dispatch and optimal power flow ignoring contingencies and losses which is shown in Figure 1.
2. Case 1 with a contingency defined on a single line.
3. Case 1 but with all lines as contingencies.

In all cases PLEXOS will compute the shift factors for the network based on single slack bus, however distributed slack would work similarly. The shift factors are shown in Table 17.

Contingency on single line

In this case we define a contingency on Line "2_5". This is done in PLEXOS by creating a Contingency object and placing the Line "2_5" in the Contingency Lines collection for that Contingency. The Contingency Is Enabled property is then set to "Yes". Finally the SCUC must be enabled in Transmission settings (see the "Security Constrained Unit Commitment (SCUC)" switch in Figure 6).

When this case is run in PLEXOS the contingency shift factors are computed for the case of Line "2_5" going out of service. These factors are shown in Table 7. For example, for the loss of one megawatt of flow from Node "2" to Node "5" the flow between Node "2" to Node "3" will increase by 0.1485.

Table 7: Contingency Shift Factors

The results for this case are illustrated in Figure 4. Compared to Figure 1 the total system cost has increased from 15113.45 to 15603.43. The generation pattern changes so that when if the flow on Line "2_5" is lost the post-contingency flows on the other lines will not exceed their thermal ratings. In the solution file PLEXOS reports the Contingency Shadow Price of 21.02. Thus, although no line is congested 'pre-contingency' there are still separations in nodal prices as in Table 8.

Table 8: Nodal pricing with single contingency

Contingencies on all Lines

We define contingencies on all lines by creating one Contingency object for each Line and adding that line to the contingency. The solution for this case is illustrated in Figure 5. The contingency shadow prices are shown in Table 9 and nodal prices in Table 10.

Table 9: Contingency Shadow Prices

Table 10: Nodal pricing with all lines as contingencies