Transmission Loading Relief is one of those topics that looks like trivia until you realize the exam is really testing whether you know the difference between managing congestion and relieving a violation. TLR is a coordinated, market-aware procedure for unloading a constrained facility using transmission service priority. It is not a substitute for the Reliability Coordinator's obligation to act when a limit is actually being exceeded.
The NERC standard behind this is IRO-006, Reliability Coordination — Transmission Loading Relief, with interconnection-specific companions: IRO-006-EAST for the Eastern Interconnection TLR procedure, and IRO-006-WEST for qualified transfer path unscheduled flow relief in the Western Interconnection. Expect the exam to test the ladder, the priority order, and the boundary where TLR stops being the right tool.
Test Tips
- Memorize the TLR ladder in order, and know what each level actually does. Level 1 = notify other Reliability Coordinators of a potential SOL or IROL violation. Level 2 = hold transfers at current level (no new transactions that would worsen the constraint). Level 3a = reallocate by curtailing non-firm service so higher-priority service can flow. Level 3b = curtail non-firm service to relieve the violation. Level 4 = reconfigure transmission. Level 5a = reallocate firm service pro rata. Level 5b = curtail firm service to relieve the violation. Level 6 = emergency action. Level 0 = TLR concluded. The "a" levels reallocate; the "b" levels relieve.
- The RC initiates TLR — not the TOP, BA, or Transmission Provider. Distractors love to hand this authority to the Transmission Operator or the merchant. Under the IRO family, the Reliability Coordinator holds the wide-area view and the authority to direct actions across its Area. The TOP's obligation, under TOP-001, is to comply with the Reliability Coordinator's directive.
- Curtailment follows transmission service priority, and non-firm goes first. Non-firm point-to-point service is curtailed ahead of firm service, generally shortest-duration non-firm first. Firm point-to-point service and Network Integration Transmission Service from designated network resources sit in the top priority tier and are only touched at Level 5. If a question asks "which transaction gets cut first," it is asking about service priority, not about who is physically closest to the flowgate.
- Only transactions that actually affect the constrained facility are eligible. TLR uses transfer distribution factors to decide which transactions matter, with a distribution-factor threshold (commonly 5%) below which a transaction is not curtailed. In the Eastern Interconnection, the Interchange Distribution Calculator is the tool that performs that impact calculation. A transaction with a trivial distribution factor on the flowgate does not get curtailed just because it is non-firm.
- Know where TLR stops. TLR is a relief procedure, not an emergency procedure — until Level 6. If an IROL is being exceeded and the clock is running, the RC's obligation under IRO-009 is to act to return the system within the limit inside the allowable time, using whatever is fast enough: redispatch, reconfiguration, or load shedding under EOP-011. "Initiate a TLR and wait" is almost always the wrong answer to an active IROL exceedance question.
- Markets change the tool, not the obligation. Inside an RTO footprint, congestion is normally managed first through market redispatch and market-to-market coordination under the RTO tariff. TLR is the interconnection-wide backstop for flows the market cannot reach, or when market tools are insufficient. Tariff-level congestion tools are not NERC requirements — don't confuse an RTO business practice with a Reliability Standard.
5 Practice Questions
-
A Reliability Coordinator determines that a flowgate is approaching its SOL and wants to prevent additional interchange from making the condition worse, without curtailing any existing transactions. Which TLR level is appropriate?
- A. TLR Level 1
- B. TLR Level 2
- C. TLR Level 3a
- D. TLR Level 5b
-
What is the essential difference between TLR Level 3a and TLR Level 3b?
- A. 3a applies to firm service; 3b applies to non-firm service
- B. 3a reallocates non-firm service so higher-priority service can flow; 3b curtails non-firm service to relieve an actual SOL or IROL violation
- C. 3a is used in the Eastern Interconnection; 3b is used in the Western Interconnection
- D. 3a is initiated by the Transmission Operator; 3b is initiated by the Reliability Coordinator
-
An IROL is being exceeded in real time and the allowable time to return within the limit is nearly expired. The Reliability Coordinator has already initiated a TLR, but relief is not arriving fast enough. What is the correct next action?
- A. Escalate to the next TLR level and continue waiting for relief
- B. Notify the neighboring Reliability Coordinators and document the exceedance
- C. Take direct action — including redispatch, reconfiguration, or load shedding — to return the system within the IROL inside the allowable time
- D. Suspend the TLR and refer the constraint to the Transmission Provider
-
Four transactions all have significant distribution factors on a constrained flowgate. Which is curtailed first under the TLR procedure?
- A. Firm point-to-point transmission service
- B. Network Integration Transmission Service from a designated network resource
- C. Hourly non-firm point-to-point transmission service
- D. Monthly non-firm point-to-point transmission service
-
A non-firm transaction has a transfer distribution factor of 1% on the constrained facility, well below the threshold used in the TLR procedure. What happens to that transaction?
- A. It is curtailed first, because it is non-firm
- B. It is not curtailed, because its impact on the constrained facility is below the distribution-factor threshold
- C. It is curtailed only at TLR Level 6
- D. It is automatically converted to firm service
Answer Key & Explanations
- B — TLR Level 2. Level 2 holds transfers at their current level to keep the constraint from worsening, without curtailing anything already flowing. Level 1 is notification only; the Level 3 and 5 families involve reallocation or curtailment. This ladder is set out in the TLR procedure referenced by IRO-006 and detailed in IRO-006-EAST for the Eastern Interconnection.
- B. The "a" levels reallocate transmission service so higher-priority service can flow; the "b" levels curtail service to relieve an actual SOL or IROL violation. Both Level 3a and 3b act on non-firm service — firm service is reached at Level 5. The initiating entity is the Reliability Coordinator at every level.
- C. TLR is a relief procedure, not a guarantee of timely relief. Under IRO-009, the Reliability Coordinator must act to prevent or mitigate an IROL exceedance within the allowable time, and IRO-001 gives the RC the authority to direct those actions. If load shedding is required, EOP-011 governs. Escalating the TLR and waiting is not an acceptable answer when the clock is expiring.
- C — hourly non-firm point-to-point service. Non-firm service is curtailed before firm service, and among non-firm, the shortest-duration products are curtailed first. Firm point-to-point service and network service from designated network resources are in the highest priority tier and are only affected at TLR Level 5.
- B. Eligibility for curtailment is driven by transfer distribution factors, not by service type alone. A transaction whose distribution factor on the constrained facility is below the procedure's threshold (commonly 5%) provides too little relief to justify curtailment, and is passed over. In the Eastern Interconnection, the Interchange Distribution Calculator performs this impact calculation.
Keep Going
If you missed more than one of these, the gap is usually the ladder — not the concept. Drill the levels until you can recite them cold, then work the priority order until it is automatic. EPG Solutions builds RC exam prep the way the control room actually runs: GridCert RC prep, the NERC RC practice test book, and the RC test lab exam simulator are all at epgsolutions.services.