Assessing Thermal and Voltage Impacts of an N-1 Contingency

Good to see you again. Your solved IEEE 9-bus base case is now the reference condition for a security assessment. In the previous lesson, you verified that it converges, that generation and losses are credible, and that its voltage and reactive-power behavior agrees materially with the benchmark.

This lesson applies one carefully chosen N-1 contingency: the loss of a single in-service transmission element. You will take the outage of a line that leaves the 9-bus system connected, solve the new steady state without “helping” the system through unrecorded changes, and compare its branch loading and bus-voltage results with the validated base case. The same comparison discipline later scales to SPP, ERCOT, WECC, and utility-provided cluster cases.

---

What an N-1 result means

An N-1 contingency evaluates whether the modeled system remains within the applicable performance criteria after losing one credible element, such as one transmission line, transformer, generator, or shunt device. For this lesson, “N” means the intact, solved base network; “N-1” means that same network with exactly one selected element out of service.

The crucial idea is that an N-1 outcome is always conditional on a stated operating scenario:

• load level and location;
• generation dispatch and voltage schedules;
• branch and transformer ratings;
• automatic controls permitted to act;
• planned outages already present in the base case;
• the particular component selected for outage.

A line can be acceptable in a low-load base case yet become limiting under high solar output, BESS charging, peak data-center demand, or a different generation-dispatch pattern. Therefore, do not describe a component as simply “N-1 compliant” without naming the scenario and criteria.

A deterministic contingency study proceeds from a credible base case, through a selected credible contingency set, to identification and reporting of limiting conditions.

For a future production study, the utility, ISO/RTO, planning criteria, and project agreement determine which outages are credible and which post-contingency voltage and emergency thermal limits apply. In this 9-bus practice case, your purpose is narrower: demonstrate a traceable AC N-1 comparison.

---

Define the comparison before changing the case

Select the outage of the transmission line between Bus 4 and Bus 5, using its actual circuit identifier in your case, commonly "1" in published IEEE 9-bus data. This is a useful teaching contingency because an alternate electrical route remains available. It should not island the system.

Before opening the branch record, create a short study contract in your workspace notes:

Study: IEEE 9-bus manual N-1 contingency
Base case: IEEE9_SOLVED_BASE_R01.sav
Contingency: outage of line Bus 4 – Bus 5, circuit [ID]
Operating condition: benchmark base dispatch and load
Solution method: full Newton-Raphson
Redispatch or manual corrective action: none
Automatic controls: [state the control settings retained from the base solve]
Voltage criteria: [reference or teaching screen used]
Thermal criterion: [applicable rating field and source]

This looks formal for a nine-bus case, but it prevents a common professional failure: changing the outage, dispatch, or rating assumption and later being unable to reconstruct why results differ.

Establish the base-case measurements

From IEEE9_SOLVED_BASE_R01.sav, record:

• voltage magnitude at all buses, with particular attention to load buses 5, 6, and 8;
• the MVA flow and applicable rating on all in-service branches;
• branch loading percentage only where a defensible rating is populated;
• generator MW and Mvar output;
• the solved swing-machine output;
• convergence status, iterations, and largest mismatch.

For the Bus 4–Bus 5 outage, likely alternate paths include the connected route through Buses 4, 6, 9, 8, 7, and 5. You may reasonably expect some flows along that route to rise after the outage. Do not assume every branch on that path must increase: AC power flow redistributes both real and reactive power through a meshed network, and voltage changes alter the result.

Use the same terminal when comparing branch MVA between cases. For a branch $k$, define the loading change as:

$$\Delta S_k=S_{k,\mathrm{N}-1}-S_{k,\mathrm{base}}$$

For thermal assessment, use the higher apparent-power magnitude reported at either terminal and the rating that is applicable to the contingency category:

$$\%{\mathrm{Loading}}_k=100\frac{\max \left(\left|S_{ij}\right|,\left|S_{ji}\right|\right)}{R_{\mathrm{applicable}}}$$

Do not automatically assume that RATE B is always the correct post-contingency rating. It is often used that way in planning models, but the model’s data conventions and the governing criteria must confirm it. If the teaching case has blank, zero, or provisional ratings, report the MVA flow change but do not make an unsupported thermal-adequacy claim.

For each bus $i$, calculate:

$$\Delta V_i=V_{i,\mathrm{N}-1}-V_{i,\mathrm{base}}$$

An absolute post-contingency voltage and the change from base answer different questions:

• Absolute voltage: Is the voltage inside the applicable allowable range?
• Voltage change: How strongly did this outage disturb the local electrical condition?

A bus may stay above its minimum criterion yet experience a meaningful negative voltage change. Conversely, a bus can violate an absolute limit even if its change from base is modest, because its base voltage was already weak.

---

Perform the selected line outage in PSS®E

For this first N-1 analysis, use a manual outage rather than ACCC. ACCC will become important for large contingency sets, but manually changing one element makes the physical meaning, data status, and result comparison visible.

1. Open the solved base case and immediately save a working copy.
   Use a revision name such as:

   IEEE9_N1_L45_R00.sav
   

   Preserve IEEE9_SOLVED_BASE_R01.sav unchanged. It is your comparison reference and must remain recoverable.

2. Locate the branch record.
   In PSS®E network data, find the branch whose terminal buses are 4 and 5. Confirm:

   • both bus numbers;
   • circuit ID;
   • line status is currently in service;
   • its impedance, charging, and ratings match your intended benchmark data.

   Do not out-age an identically numbered but different-circuit record.

3. Change only the branch status to out of service.
   Set the selected line’s status from in service to out of service. Do not delete the record. Retaining it with an out-of-service status preserves the network data and makes the outage explicit.

4. Solve the post-contingency power flow.
   Use the same full Newton-Raphson approach and solution settings used to validate the base case. Do not manually change generator dispatch, transformer taps, shunts, or loads merely to make the case look better.

   If your base-case settings permit automatic transformer or shunt controls to operate, retain those settings for the contingency solve and record any movements. Those actions are part of the modeled post-contingency state. Unrecorded manual intervention is not.

5. Record numerical and topology status before interpreting limits.
   Confirm:

   • the post-contingency case converged;
   • there are no unintended islands;
   • all intended loads and generators remain connected;
   • no generator unexpectedly reaches a reactive limit;
   • the outaged branch remains out of service.

6. Save the solved contingency state.

   IEEE9_N1_L45_SOLVED_R01.sav
   

If the case does not converge, do not report “no violations.” Non-convergence is itself a material result requiring investigation. Check the progress output, the element status, and islanding reports before considering any corrective action.

---

Monitor thermal and voltage changes

The following ACCC demonstration is useful as a preview of how PSS®E later formalizes monitoring for many contingencies. For today, treat it as orientation; your actual analysis remains the manual one-line outage above.

Read the voltage result correctly

Produce a bus-voltage comparison for at least Buses 4 through 9, and include Buses 1 through 3 if their reactive outputs or voltage-control status changed.

Bus	Base voltage, p.u.	N-1 voltage, p.u.	$\Delta V$, p.u.	Assessment
5	[record]	[record]	[calculate]	[within limit / low / changed materially]
6	[record]	[record]	[calculate]	[assessment]
8	[record]	[record]	[calculate]	[assessment]
4, 7, 9	[record]	[record]	[calculate]	[assessment]

Interpret the results in this order:

1. Identify the lowest post-contingency voltage and its bus.
2. State whether it meets the voltage criterion actually selected for the exercise.
3. Identify the largest voltage decrease, which may occur at a different bus.
4. Check whether any PV generator has reached $Q_{\max }$ or $Q_{\min }$. A reactive-limit transition can explain a voltage decrease.
5. Relate the change to the new transfer route created by the Bus 4–Bus 5 line outage.

Avoid treating a voltage of, for example, 0.96 p.u. as automatically good or bad. It may be acceptable under one approved post-contingency criterion and unacceptable under another. The applicable criterion belongs in the study contract.

Read the thermal result correctly

For each remaining branch or transformer with a credible rating, compare base and post-contingency flow. Prioritize the branches with the greatest post-contingency loading and those with the largest positive change in loading.

In-service element	Base MVA	N-1 MVA	Applicable rating, MVA	N-1 loading	Change and interpretation
Line 4–6	[record]	[record]	[record]	[calculate]	[record]
Line 5–7	[record]	[record]	[record]	[calculate]	[record]
Line 6–9	[record]	[record]	[record]	[calculate]	[record]
Line 7–8	[record]	[record]	[record]	[calculate]	[record]
Line 8–9	[record]	[record]	[record]	[calculate]	[record]

The outaged 4–5 line should show zero flow because it is out of service. That is not a “relief” finding; it is simply the definition of the contingency. The engineering finding concerns the remaining in-service network and whether it can carry the redistributed power within applicable limits.

A concise result statement should distinguish three possible outcomes:

• No identified violation: the case converged, remained connected, and monitored quantities were inside the stated criteria.
• Thermal violation: an in-service element exceeded its applicable post-contingency rating.
• Voltage violation: a bus exceeded the stated upper limit or fell below the stated lower limit.

You may also have a non-violation but noteworthy sensitivity, such as a large loading increase, a substantial voltage decrease, or a generator reaching its reactive limit. Such behavior may become limiting when the system is stressed by higher project output or higher load.

---

If you select a transformer instead

The procedure is identical: create a new case copy, set the correct transformer circuit or winding record out of service, solve, check convergence and islanding, then compare voltages and in-service-element flows.

The interpretation deserves extra caution:

• A transformer outage can remove a source, load pocket, or voltage-control path.
• Outaging a generator step-up transformer in the basic IEEE 9-bus topology can isolate its generator bus from the transmission network.
• A post-contingency island is not a normal thermal-loading result. Record it explicitly, identify the isolated buses and equipment, and stop before drawing ordinary voltage or branch-overload conclusions for that island.

This is why the Bus 4–Bus 5 line is the better initial teaching contingency: it illustrates power redistribution without turning the exercise into an islanding investigation.

---

Document one defensible N-1 result

Add a result record to your workspace manifest:

Case: IEEE9_N1_L45_SOLVED_R01.sav
Base reference: IEEE9_SOLVED_BASE_R01.sav
Contingency: line Bus 4 – Bus 5, circuit [ID], status set out of service
Solution status: [converged / did not converge]
Islanding: [none / describe]
Lowest post-contingency voltage: [bus, p.u.]
Largest voltage change from base: [bus, p.u.]
Highest post-contingency thermal loading: [element, percentage, rating basis]
Largest branch-flow increase: [element, base MVA, N-1 MVA]
Generator reactive limits reached: [none / list]
Automatic control movements: [none / list]
Conclusion: [no identified violation / thermal violation / voltage violation / non-convergence]
Limit basis and source: [record]

A one-paragraph engineering conclusion can then be written in a disciplined form:

With the Bus 4–Bus 5 line out of service, the IEEE 9-bus case [converged/did not converge] without [islanding/describe islanding]. The lowest monitored voltage was [value] p.u. at Bus [number], compared with [criterion]. The highest in-service loading was [value]% on [element], evaluated against [rating basis]. The limiting observed change was [brief physical explanation of redistributed flow or reactive response].

---

Key takeaways

An N-1 study is a controlled comparison between a validated base case and a case with one credible component removed.

• Preserve the solved base case and make the outage in a separately named working revision.
• For the first manual exercise, outage Line 4–5 rather than a generator step-up transformer, because the line outage should leave an alternate network path.
• Solve with the same assumptions as the base case and do not hide a result through undocumented redispatch, tap changes, shunt changes, or topology changes.
• Check convergence and islanding before assessing thermal or voltage limits.
• Compare both absolute post-contingency voltage and voltage change from base.
• Assess thermal loading only against a rating that is demonstrably applicable to the contingency category.
• Report the scenario, outage identity, criteria, result, and any control or reactive-limit behavior so another engineer can reproduce the conclusion.

Next, you will validate the completed IEEE 9-bus model against a published reference solution and document any remaining material differences before moving to larger, more realistic contingency-study cases.