Why is PJM Not Following Their Own Rules?

Benjamin Pennington, President of the Preserve Orange Alliance and, inconveniently for certain bureaucracies, a United States Marine, has written a scathing response to the grid overlord's (PJM) boiler plate response to his original letter to PJM on the scope, cost, and most importantly in-service date change for the Valley Link Joshua Falls to Yeat abomination. Mr. Pennington must have done a full autopsy of PJM's own bureaucratic rules and fished out the exact sections that PJM is ignoring (and likely hoping the peasants never notice).
How do you beat a glacial bureaucracy? You pound it over the head with it's own rules, and that is exactly what Mr. Pennington is doing. The term 'Designated Entity' below is referring to the company with "no employees" called Valley Link. A link to Mr. Pennington's full response letter is below. We've summed up the important points and have to wonder if PJM is going to ignore Mr. Pennington?
To wit:
Schedule 6, Section 1.5.8(k) of the PJM Operating Agreement is titled “Failure of Designated Entity to Meet Milestones.” It is part of the Regional Transmission Expansion Planning Protocol and governs what happens when a Designated Entity (the entity selected to develop a competitively awarded RTEP project) misses development milestones in a way that delays the project’s in-service date.
In substance, the provision states:
In the event the Designated Entity fails to comply with one or more of the requirements of the Operating Agreement, Schedule 6, section 1.5.8(j); or fails to meet a milestone in the development schedule set forth in the Designated Entity Agreement that causes a delay of the project’s in-service date, the Office of the Interconnection shall re-evaluate the need for the Short-term Project or Long-lead Project, and based on that re-evaluation may:
retain the Short-term Project or Long-lead Project in the Regional Transmission Expansion Plan;
remove the Short-term Project or Long-lead Project from the Regional Transmission Expansion Plan; or
include an alternative solution in the Regional Transmission Expansion Plan.
If PJM retains the project, it must determine whether the delay is beyond the Designated Entity’s control and whether to retain that Designated Entity or reassign the project to the Transmission Owner(s) in the zone(s) where it is located. If the Designated Entity is already the local Transmission Owner, PJM seeks recourse through the Consolidated Transmission Owners Agreement or FERC, as appropriate. Any resulting modifications to the RTEP must be presented to the Transmission Expansion Advisory Committee (TEAC) for review and comment and approved by the PJM Board.
FERC has cited and applied this exact subsection in orders addressing Designated Entity Agreements and milestone issues, confirming that a milestone failure causing an in-service date delay triggers the mandatory reevaluation and the binary choice (retain the entity or reassign, subject to the special rule when the entity is already the incumbent Transmission Owner).
Related Procedures
Section 1.5.8(j) (cross-referenced in (k)) addresses acceptance of designation, development schedules, and related requirements, including security.
Manual 14C implements these rules for projects under a Designated Entity Agreement (DEA). It includes a formal Upgrade Project Designated Entity Agreement Modification Process (typically for routing changes, terminal adjustments, electrical parameter changes, etc.). Material changes may require amending and refiling the DEA. Manual 14C also addresses breach, cure, reevaluation, and default, and explicitly points back to Operating Agreement Schedule 6, Section 1.5.8(k) when milestones are missed in a way that delays the in-service date.
Scope or configuration changes that are not “materially different” and still solve the original reliability needs have been treated by PJM as manageable through the Manual 14C modification process without reopening a full competitive proposal window. In-service date delays driven by missed DEA milestones are treated differently under the explicit “shall re-evaluate” language of 1.5.8(k).
The distinction matters: routine or non-material scope evolution can proceed under the DEA modification process, but a milestone-driven delay of the in-service date obligates PJM to reevaluate the need and decide among retaining the project (and the Designated Entity or reassigning it), removing it, or selecting an alternative, subject to TEAC review and Board approval.
Side Note: we actually made this argument at the TEAC meeting, why aren't they re-evaluating given the in-service date change?
Perhaps someone has a contact at FERC who is supposed to be overseeing PJM, and they might force the issue? Or, perhaps a formal complaint will need to be filed with FERC if PJM continues to ignore their own rules? Guess we'll find out at the next PJM board meeting on November 17th if the board chair, Paula Conboy, is going to follow their own rules.



Comments