{"document":{"slug":"request-er26-3515-pjmicc-clarification","title":"Industrial customers ask FERC to clarify or rehear its Large Load registry order","issued":"2026-11-09","accession":"20261109-5238","docket":"ER26-3515-001","group":"PJM filings","filer":"PJM Industrial Customer Coalition and Steel Producers","kind":"request","file":"sources/originals/20261109-5238_01.pdf","url":"https://elibrary.ferc.gov/eLibrary/filelist?accession_Number=20261109-5238","sha256":"35fce070392d809071a42835587143c1f8de3db7c4aca2d1441bfa5d50587d29","pages":17,"tokens":4879,"emptyPages":[]},"pages":[{"page":1,"startToken":0,"endToken":265,"text":"UNITED STATES OF AMERICA \nFEDERAL ENERGY REGULATORY COMMISSION \n \n \n \n \n \n \n \n \n: \nPJM Interconnection, L.L.C.  \n \n \n: \n \nDocket No. ER26-3515-000 \n \n \n \n \n \n \n \n: \n \nREQUEST FOR CLARIFICATION  \nOR, IN THE ALTERNATIVE, REHEARING  \nOF THE PJM INDUSTRIAL CUSTOMER COALITION AND STEEL PRODUCERS \n \nPursuant to Rule 713 of the Federal Energy Regulatory Commission’s (“Commission” or \n“FERC”) Rules of Practice and Procedure,1 the PJM Industrial Customer Coalition (“PJMICC”) \nand Steel Producers respectfully request clarification or, in the alternative, rehearing of portions \nof the Commission’s October 9, 2026, Order Accepting Tariff Revisions in Part and Rejecting \nTariff Revisions in Part (“October 9 Order” or “Order”) pertaining to the applicability of the Large \nLoad Registry (“Registry”) to industrial and manufacturing loads and the Registry’s confidentiality \nrules.2 PJMICC is authorized to state that the Industrial Energy Consumers of America (“IECA”) \nstrongly supports this Request.3    \nI. \nINTRODUCTION \nThe October 9 Order rejected PJM’s proposed Interim Resource Adequacy Service \n(“IRAS”) and Bring Your Own New Capacity (“BYONC”) frameworks, which were the core of \nPJM’s Section 205 filing on August 13, 2026.4 However, the Commission accepted PJM’s \nproposal to create a Registry and accepted PJM’s proposed definition of Large Load.  \n \n1 See 18 C.F.R. § 385.713. \n2 PJM Interconnection, L.L.C., 197 FERC ¶ 61,019 (Order issued Oct. 9, 2026) (“October 9 Order”). \n3 IECA filed out-of-time Comments in this docket, which the Commission accepted in its October 9 Order. October \n9 Order at P 10. However, IECA did not intervene or seek party status in this proceeding and does not seek such \nstatus by this Request. \n4 October 9 Order at PP 2, 13-14."},{"page":2,"startToken":265,"endToken":546,"text":"2 \n \nPJMICC and Steel Producers appreciate the Commission’s statements affirming that \nexisting protections in the PJM Operating Agreement (“OA”) will apply to retail customers listed \nin the Registry.5 However, the Registry will compile some of the most commercially sensitive \ninformation that energy-intensive manufacturers and institutions possess—data concerning who \nthey are, where they operate, how much power they use, how they back up their operations, and \nwith whom they contract for supply and at what rates. Without certain clarifications regarding who \nmay see that information and for what purpose, the Registry risks becoming a source of \ncompetitive intelligence rather than a reliability tool.  Absent the clarifications requested herein, \nthe October 9 Order would be arbitrary and capricious because it does not address how Registry \ndata will be protected from uses that could confer market power in PJM’s electric markets or \nundermine competition in critical American industries.   \nClarification is necessary because OA protections must be applied to retail customers, \nincluding to customers who are not signatories to the OA and do not have the privileges of PJM \nMembership. PJMICC and Steel Producers therefore respectfully request that the Commission \nclarify the scope of Registry data and the scope of access to Registry data in order to ensure \nprotection of competitively sensitive retail customer information while enabling targeted access to \nthe information necessary to support reliable operations and planning. PJMICC and Steel \nProducers also submit an alternative Request for Rehearing, in the event the Commission does not \ngrant the requested clarifications. \nII. \nEXECUTIVE SUMMARY \nPJMICC is a coalition of energy-intensive industrial and institutional customers in the PJM \nregion, including manufacturers of paper, cement, chemicals, metals, pharmaceutical products, and \n \n5 Id. at PP 49-50."},{"page":3,"startToken":546,"endToken":874,"text":"3 \n \nconsumer goods, as well as hospitals and universities.6 Steel Producers consists of the steel mills \nowned by (i) Steel Dynamics, Inc., and (ii) Nucor Corporation that are located in the PJM footprint. \nIECA is a nonpartisan association of leading manufacturing companies with $1.3 trillion in annual \nsales, over 12,000 facilities nationwide, and with more than 1.9 million employees—many of them \nin PJM’s territory. Together, PJMICC, Steel Producers, and IECA represent many retail customers \nwhose competitiveness is largely determined by the cost and reliability of natural gas and \nelectricity. These retail customers have traditionally been thought of as “large” users but are, in \nmost cases, much smaller than the large data center projects that are being added to the grid. \nThe October 9 Order accepts PJM’s Registry, which will gather into a single location, for \neach Large Load of 50 MW or more, information such as the customer’s identity, location, in-\nservice dates, peak load and ramp schedule, telemetry specifications, backup generation (including \nfuel type and permitting limitations), and contracts or service agreements with its Load Serving \nEntity (“LSE”), which may include power supply rate information.7 Because the Commission \nrejected IRAS, all retail customers that satisfy the definition of Large Load, including some \nexisting PJMICC and Steel Producers members, will be included in the Registry for “informational \npurposes” only.8 \nThe Order finds that PJM’s existing confidentiality rules under section 18.17 of the PJM \nOperating Agreement (“OA”) will adequately safeguard Registry data.9 This holding is significant, \nbut section 18.17 of the OA was not expressly designed for retail end-use customer data, and the \nOrder does not specify how access will be limited among the many entities eligible to receive it. \n \n6 Comments of the PJM Industrial Customer Coalition, Docket No. ER26-3515-000, at 1, 3 (Sept. 3, 2026) \n(“PJMICC Comments”). \n7 October 9 Order at PP 16, 33. \n8 Id. at P 50. \n9 October 9 Order at P 49."},{"page":4,"startToken":874,"endToken":1238,"text":"4 \n \nThe October 9 Order therefore fails “to consider an important aspect of the problem”10 and does \nnot address the significant competitive and security implications of disclosure. Accordingly, \nPJMICC and Steel Producers request that the Commission clarify that: \n1. PJM must segment access to Registry data on a “need-to-know” basis, so that each \nrecipient receives only the data relevant to its own planning and operational \nresponsibilities, consistent with the scope limits in OA section 18.17.7, which provides \nfor Transmission Owners to receive only confidential generator data that impacts that \nTransmission Owner’s planning. \n \n2. Confidentiality protections for retail customer data in the Registry will be no less \nrestrictive than those for generator data, including limiting access to operational \nemployees and prohibiting disclosure to marketing employees. \n \n3. An LSE may access Registry data only for the Large Loads that it serves, not as a broad-\nbased access to potential customers, consistent with OA Section 18.17.7. \n \n4. Retail customers listed in the Registry will have the same rights as PJM Members under \nOA section 18.17 to designate data as confidential and prevent it from being disclosed \nto other PJM Members or others. \n \n5. Information on retail customer rates or pricing will be excluded from the Registry and \nredacted from contracts that are added to the Registry. \n \nThese clarifications are consistent with the Commission’s October 9 Order, with PJM’s \ncommitment to limit Registry access to “as small a universe of entities as possible,” and with the \nprotections the OA already affords generator data.11  \nHowever, if the Commission does not grant the requested clarifications, PJMICC and Steel \nProducers respectfully request rehearing, as set forth below. \nIII. \nSTATEMENT OF ISSUES/ERRORS FOR ALTERNATIVE REHEARING \nREQUEST \nIf the Commission grants all of the above requested clarifications in full, the issues and \nerrors raised in PJMICC’s and Steel Producers’ alternative request for rehearing will be resolved. \n \n10 Motor Vehicle Mfrs. Ass’n v. State Farm Mut. Auto. Ins. Co., 463 U.S. 29, 43 (1983) (“an agency rule would be \narbitrary and capricious if the agency . . . failed to consider an important aspect of the problem”). \n11 October 9 Order at P 42; OA § 18.17.7."},{"page":5,"startToken":1238,"endToken":1713,"text":"5 \n \nHowever, if the Commission does not grant the requested clarifications in full, PJMICC and Steel \nProducers seek rehearing on the following issues: \n1. The October 9 Order errs because it does not provide substantial evidence to support \nthe inclusion of existing Large Loads, including industrial customers, in the Registry, \neven for “informational purposes.” 5 U.S.C. § 706(2)(A); Vistra Corp. v. FERC, 80 \nF.4th at 312; South Carolina Pub. Serv. Auth. v. FERC, 762 F.3d 41, 55 (D.C. Cir. \n2014); Sacramento Mun. Util. Dist. v. FERC, 616 F.3d 520, 528 (D.C. Cir. 2010).  \n2. The October 9 Order is arbitrary and capricious because it does not sufficiently \naccount for the critical nature of the information the Registry will collect and the need \nto protect that information consistent with governing rules. 5 U.S.C. § 706(2)(A); \nVistra Corp. v. FERC, 80 F.4th at 312; South Carolina Pub. Serv. Auth. v. FERC, 762 \nF.3d 41, 55 (D.C. Cir. 2014); Sacramento Mun. Util. Dist. v. FERC, 616 F.3d 520, \n528 (D.C. Cir. 2010).   \n \n3. The October 9 Order is unjust, unreasonable, and unduly discriminatory or preferential \nbecause it affords retail customer data less protection than the Operating Agreement \naffords generator data. 16 U.S. Code § 824d-824e; California Indep. Sys. Operator \nCorp. v. FERC, 372 F.3d 395, 400 (D.C. Cir. 2004); S.C. Pub. Serv. Auth. v. FERC, \n762 F.3d 41 (D.C. Cir. 2014).  \n4. The October 9 Order errs by permitting access to undefined “other entities” and to LSEs \nand other entities who have marketing functions without clearly defined limitation, \ncontrary to the Commission’s duty to protect consumers and competitive markets. \nNAACP v. FPC, 425 U.S. 662, (1976); Pub. Util. Dist. No. 1 of Snohomish Cnty., Wash. \nv. FERC, 272 F.3d 607 (D.C. Cir. 2001). See also 18 C.F.R. § 35.34(k)(6). \n5. The October 9 Order errs by approving the Registry despite rejection of the IRAS \nproposal that the Registry was designed to support, without substantial evidence that \nthe Registry is properly designed for non-IRAS purposes. 5 U.S.C. § 706(2)(A); Vistra \nCorp. v. FERC, 80 F.4th at 312; South Carolina Pub. Serv. Auth. v. FERC, 762 F.3d \n41, 55 (D.C. Cir. 2014); Sacramento Mun. Util. Dist. v. FERC, 616 F.3d 520, 528 (D.C. \nCir. 2010). \nIV. \nPROCEDURAL HISTORY \nOn August 13, 2026, PJM filed, pursuant to section 205 of the Federal Power Act \n(“FPA”)12, proposed revisions to its Open Access Transmission Tariff (“Tariff”) and Reliability \nAssurance Agreement (“RAA”) to establish: (1) a definition of Large Load; (2) a Large Load \nRegistry; (3) a new service known as IRAS, which was proposed as a program to require New \n \n12 16 U.S. Code § 824d."},{"page":6,"startToken":1713,"endToken":2039,"text":"6 \n \nLarge Loads to bring their own sources of power or to be curtailed earlier than other load during a \ngrid emergency; (4) a requirement for LSEs serving New Large Load (as defined in PJM’s Tariff \nproposal) to designate new capacity resources; (5) rules for BYONC arrangements; and (6) rules \nto exclude Eligible New Large Load from the Variable Resource Requirement (“VRR”) curve \n(collectively, “IRAS Filing”).13 Notice of the filing was published in the Federal Register, with \ninterventions and protests due on or before September 3, 2026.14 PJMICC filed a doc-less Motion \nto Intervene on August 14, 2026, and filed Comments (“PJMICC Comments”) on September 3, \n2026, urging, among other things, that existing Large Loads be excluded from the Registry or, if \nincluded, be afforded due process and robust confidentiality protections.15 On September 3, 2026, \nSteel Producers filed a doc-less Motion to Intervene. On September 15, IECA filed out-of-time \nComments (“IECA Comments”), which the Commission accepted in its October 9 Order.16 \nOn October 9, 2026, the Commission issued the October 9 Order, accepting PJM’s \nproposal to establish the Registry and approving PJM’s definition of Large Load, while rejecting \nthe remainder of PJM’s proposal, and directing PJM to submit a compliance filing within 30 \ndays.17  While the Commission addressed some of PJMICC’s Comments, it did not address certain \nconcerns in sufficient detail to explain how retail customer data will be meaningfully protected. \nConsequently, PJMICC and Steel Producers timely submit this Request for Clarification or, in the \nAlternative, Rehearing in response to the October 9 Order.18 \n \n13 October 9 Order at P 1. \n14 Id. at P 5 (citing 91 Fed. Reg. 53407 (Aug. 18, 2026)). \n15 PJMICC Comments at 5-8. \n16 The Commission accepted IECA’s out-of-time comments in its October 9 Order. See October 9 Order at P 10. \n17 October 9 Order at PP 2, 13, 48. \n18 16 U.S.C. § 825l(a); 18 C.F.R. § 385.713."},{"page":7,"startToken":2039,"endToken":2294,"text":"7 \n \nV. \nREQUEST FOR CLARIFICATION \nPJMICC and Steel Producers respectfully request clarification regarding five issues: (1) \nsegmentation of Registry data on a “need-to-know” basis; (2) confidentiality protections for retail \ncustomer data that are no less restrictive than those for generator data; (3) limitation of each LSE’s \naccess to data for its own customers; (4) confirmation that retail customers listed in the Registry \nwill have the same rights as PJM Members under OA section 18.17; and (5) exclusion or redaction \nof information on retail customers’ rates or pricing. \nAs a threshold point, competition is the foundation of PJM markets. The emphasis in this \nRequest for Clarification on the need for specific confidentiality clarifications is directly related to \nthe importance confidentiality plays in competitive markets—both electric markets and the \nindustries in which Large Load customers serve. Without confidentiality regarding key terms such \nas supplier relationships, contracts, load information, and more, competition will be undermined, \nand the risks of market power and antitrust concerns will increase.  Further, there is a direct line \nfrom confidentiality to competition and from competition to affordability: competitive markets \ndiscipline prices only when market participants cannot exploit non-public information about their \ncustomers and rivals. \nAdditionally, in restructured states, a customer’s supplier relationship is typically \nconfidential, and disclosure of retail customers’ LSEs could affect the functioning of retail \nmarkets.19 Further, confidentiality has antitrust considerations: Customer-specific load, contract, \nand supplier data shared among LSEs and competitive suppliers could facilitate coordination, \ntargeting, or segmenting of customers or customer bases.  \n \n19 PJMICC Comments, at 6."},{"page":8,"startToken":2294,"endToken":2606,"text":"8 \n \nThe Commission and PJM both recognize that PJM’s existing rules contemplate these \nconcerns. The rules already mask resource names, load identity, and submitter identity to protect \nmarket-sensitive information.20 The rules also provide for data segmentation on a “need-to-know” \nbasis. Registry data warrants at least equivalent protection. The FERC should affirm that these \nprotections apply on an equivalent basis to load, as set forth below. \nA. The Commission should clarify that PJM must collect and segment access to \nRegistry data on a “need-to-know” basis. \n \nThe Order accepts PJM’s proposal to make Registry information available to Authorized \nCommissions, Transmission Owners, Electric Distributors, LSEs, the Independent Market \nMonitor (“IMM”), the Commission, and other entities, “subject to appropriate confidentiality and \ndata protection safeguards.”21 PJM itself acknowledged that the Registry “is expected to collect \ninformation that may be confidential or commercially sensitive, or that may implicate \ninfrastructure security concerns,” and that it therefore must permit access to “as small a universe \nof entities as possible.”22 In rejecting requests for broader access, the Commission explained that \n“the Large Load Registry will be available only to entities that already have access to this sort of \ninformation and consistent with existing confidentiality rules,” rules “that currently do not allow \nstate consumer advocates or similar entities to have access to this type of information.”23 However, \nbeyond this, the Order does not specify how that universe will be limited in practice, or whether \neach recipient will receive the entire Registry or only the portion relevant to its responsibilities. \nThe OA already provides a model. When PJM shares confidential generator information \nwith Transmission Owners, it does so only for generators that are or will be “modeled within the \n \n20 OA § 18.17.1(e)(i). \n21 October 9 Order at P 49. See also id. at P 34. \n22 Id. at P 42. \n23 Id. at P 49."},{"page":9,"startToken":2606,"endToken":2906,"text":"9 \n \nTransmission Owner’s energy management system” or “identified in a Transmission Owner’s \nrestoration plan.”24 The same principle should govern the Registry: a Transmission Owner or \nElectric Distributor should receive data only for Large Loads located on or directly affecting its \nown system, and no recipient should receive Registry data beyond what it needs to perform its \nplanning and operational responsibilities. The Commission should clarify that this principle of the \nOA applies to retail customers’ data and that PJM must implement this need-to-know segmentation \nin its compliance filing or the PJM Manuals. \nFurther, because the Commission rejected IRAS, the core reason for developing the \nRegistry is no longer present. The Commission did affirm in the October 9 Order that the Registry \nwill “provide PJM with the information necessary to address operational impacts” of Large Loads \nand “enable PJM to better forecast load growth and to plan and manage its transmission system.”25 \nIn addition to segmenting data PJM does collect, the Commission should clarify that PJM’s data \ncollection must be limited to data that relates to the operational and planning purposes set forth in \nthe Order. \nB. The Commission should clarify that confidentiality protections for retail \ncustomer data in the Registry will be no less restrictive than the protections for \ngenerator data. \n \nGenerator data is provided substantial protection in the OA, and for good reason: in PJM, \ngenerators operate in a competitive marketplace. Per the OA, confidential generator data provided \nto Transmission Owners may be provided “only to transmission function employees,” may be used \nonly for the Transmission Owner’s reliability and transmission functions, and may not be disclosed \n“to any person, including marketing function employees,” except as expressly permitted.26 \n \n24 OA § 18.17.7(a). \n25 October 9 Order at P 48. \n26 OA § 18.17.7(c)-(d)."},{"page":10,"startToken":2906,"endToken":3195,"text":"10 \n \nSimilarly, data available on PJM’s Energy Management System (“EMS”) terminals must be held \nin the Transmission Owner’s secure control room and may not be disclosed to “marketing \norganizations, energy affiliates or independent third parties.”27 \nRetail customer data in the Registry has similar competitive and security sensitivities as \ngenerator data. PJM may not know or understand retail customers’ competitive sensitivities, as \nretail customers operate within particular industries. As PJMICC explained in its Comments, \nhowever, knowledge of a manufacturer’s load size, location, demand response participation, and \nLSE relationships enables competitors, including international competitors, to infer critical \noperational intelligence.28 The Registry will also contain backup generation details, permitting \nlimitations, and contracts or service agreements between the Large Load and its LSE, which may \ninclude power supply rate information.29 A large manufacturer’s load profile and supply contracts \nshould be viewed as at least as sensitive as a generator’s real-time output. The Commission should \nclarify that Registry data will be disclosed only to transmission function (or equivalent planning \nand operations) personnel and will not be disclosed to marketing function employees, consistent \nwith the separation of transmission and marketing functions under the Commission’s Standards of \nConduct, 18 C.F.R. Part 358. \nC. The Commission should clarify that an LSE may access Registry data only for \nthe Large Loads that it serves. \n \nThe Order confirms that the LSE serving a Large Load is obligated to provide the Registry \ninformation for that customer.30 It does not follow that every LSE should have access to the \nRegistry information of every other LSE’s customers. Many LSEs, particularly competitive retail \n \n27 OA § 18.17.6(c). \n28 PJMICC Comments at 6. \n29 October 9 Order at P 33. \n30 Id. at PP 43, 50."},{"page":11,"startToken":3195,"endToken":3510,"text":"11 \n \nsuppliers, have marketing functions and compete to serve Large Loads. In restructured states, a \ncustomer’s supplier relationship is typically confidential, and disclosure of that relationship could \naffect the functioning of retail markets.31 A competitive supplier seeking to serve a Large Load \nshould not have access to information that is confidential between that customer and its current \nLSE.32 The Commission should clarify that an LSE’s access to Registry data is limited to its own \ncustomers and that Registry data may not be used as a marketing tool. \nD. The Commission should clarify that retail customers listed in the Registry will \nhave the same rights as PJM Members under OA section 18.17 to designate data \nas confidential and prevent it from being disclosed. \n \nUnder the OA, Members are provided with specific rights and protections, such as the right \nto designate information as confidential and to prevent its disclosure to other PJM Members. As \nexplained above, many retail customers are not PJM Members. Consequently, to ensure that the \nOA protections apply to retail customers in the Registry, PJMICC and Steel Producers respectfully \nrequest that the Commission clarify that retail customers’ data is automatically deemed \nconfidential upon entry into the Registry or, at a minimum, that retail customers have sufficient \nopportunity to designate their own data in the Registry as confidential. \nThese clarifications matter because confidentiality is necessary to support competition in \nthe energy industry and key industries that support the nation’s economic growth. Additionally, \nconfidentiality protection is needed for retail customers, particularly manufacturers, who must \ncompete globally and for whom information in the Registry could be used as competitive \nintelligence by competitors. \n \n \n31 PJMICC Comments at 6. \n32 Broad access to customer utility account numbers in the Registry could also create security concerns, such as the \npossibility of unauthorized switching of a customer’s supplier, or of demand response aggregators erroneously \nenrolling assets in programs."},{"page":12,"startToken":3510,"endToken":3828,"text":"12 \n \nE. The Commission should clarify that information on rates will be excluded from \nthe Registry and redacted from contracts that are added to the Registry. \n \nA Large Load retail customer’s electric rate or pricing information is one of the most \nsensitive pieces of competitive intelligence in its possession. It is closely guarded by many retail \ncustomers and is a core component of those customers’ relationships with their respective LSEs. \nAs mentioned above, many Large Load retail customers must compete globally in their respective \nindustries. Their rates and contract terms are central to these customers’ competitiveness. \nA Large Load retail customer’s rate or pricing information is not necessary for \nTransmission Owners, EDCs, LSEs, or PJM to perform planning or operational responsibilities. \nBecause rate and pricing information is highly confidential and central to a retail customer’s \ncompetitiveness, it should not be included in the Registry or, if it is included in contracts on file \nwith the Registry, should be redacted for all recipients. \nVI. \nALTERNATIVE REQUEST FOR REHEARING \nIf the Commission does not grant the clarifications requested above, PJMICC and Steel \nProducers respectfully request rehearing on the issues identified in Section III. First, the October \n9 Order does not provide substantial evidence to support the inclusion of existing Large Load, \nincluding industrial customers and other energy-intensive customers, in the Registry.33 The \nCommission recognized that, because IRAS was rejected, industrial customers will be included in \nthe Registry only for informational purposes.34 The October 9 Order’s sole stated basis for \nincluding them is that PJM must have visibility into the full spectrum of Large Loads in its \nfootprint.35 The Order identifies no record evidence explaining why that visibility requires \ncollecting existing customers’ contracts, power supply rate information, supplier relationships, \n \n33 See 16 U.S.C. § 825l(b); 5 U.S.C. § 706(2)(A), (E). \n34 October 9 Order at P 50. \n35 Id. at PP 44, 50."},{"page":13,"startToken":3828,"endToken":4206,"text":"13 \n \nbackup generation and permitting limits, and other site-specific data, much of which state-\nregulated utilities already hold subject to state confidentiality rules. \nSecond, the Order arbitrarily and capriciously fails to account for the critical nature of the \ninformation the Registry will collect and the need to protect that information in a manner consistent \nwith governing rules. The Registry will compile site-level data on location, telemetry, backup \ngeneration, and contracts for each Large Load, which may include power supply rate \ninformation.36 PJM itself acknowledged that the Registry may implicate infrastructure security \nconcerns.37 The Commission’s own regulations protect Critical Energy/Electric Infrastructure \nInformation (“CEII”),38 and PJM’s Operating Agreement recognizes that real-time grid and \ngenerator data may constitute CEII and strictly limits their use and disclosure.39 Yet the Order \naccepts the Registry’s safeguards solely by reference to PJM’s existing confidentiality rules,40 \nwithout addressing the fact that those rules expressly attach to Member data designated as \nconfidential,41 but do not expressly attach to retail customers listed in the Registry who are not \nPJM Members and cannot themselves designate their data as confidential. An agency’s failure to \nappreciate the practical consequences of its legal determinations is arbitrary and capricious.42 \nThird, the Order affords retail customer data less protection than the OA affords generator \ndata.43 Generator data is provided substantial protection in the OA, but without an affirmative \n \n36 Id. at P 33. \n37 Id. at P 42. \n38 See 18 C.F.R. § 388.113. \n39 See OA § 18.17.6(b)-(c) (stating, in part, “The data and information produced by the EMS or other situational \nawareness tool, are confidential and/or commercially sensitive because they will display the real-time status of \nelectric transmission lines and generation facilities, the disclosure of which could impact the market and the \ncommercial interests of its participants. In addition, the responsive information will contain detailed information \nabout real-time grid conditions, transmission lines, power flows, and outages, which may fall within the definition of \nCritical Energy Infrastructure Information (CEII) as set forth in 18 CFR § 388.113.”). \n40 October 9 Order at P 49. \n41 OA § 18.17.1(a)-(b). \n42 See State Farm, 463 U.S. at 43.  \n43 See OA § 18.17.7(c)-(d)."},{"page":14,"startToken":4206,"endToken":4527,"text":"14 \n \nstatement by the Commission that retail customer data must be protected on an equal basis to \ngenerator data, there remains uncertainty around whether retail customers will be adequately \nprotected. This is unduly discriminatory. Both retail customers and generators operate in \ncompetitive contexts. Both are price-sensitive. Both rely on protection of strategic information. As \na result, it would be unduly discriminatory to afford generators greater protection since retail \ncustomers and generators are similarly situated with respect to the need to protect competitive \nintelligence.  \nFourth, the Order does not reconcile its acceptance of the Registry with the Commission’s \nresponsibility to protect consumers and competitive markets.44 The Commission’s stated mission \nis to “[a]ssist consumers in obtaining reliable, safe, secure, and economically efficient energy \nservices at a reasonable cost through appropriate regulatory and market means, and collaborative \neffort.”45 Customer-specific load, contract, rate, and supplier data shared among LSEs and \ncompetitive suppliers could facilitate coordination, targeting, or segmenting of customers or \ncustomer bases, increasing the risk of market power abuse and antitrust concerns. By permitting \naccess to undefined “other entities,”46 and without limiting LSEs and other entities with marketing \nfunctions to non-marketing purposes, the Order is unjust, unreasonable, and unduly discriminatory \nor preferential. \nFinally, the October 9 Order errs in approving the Registry while rejecting IRAS because \nthe Registry was designed to support IRAS. While PJM consented to severance of the Registry \nfrom other parts of the filing, its justification for the Registry without IRAS was general, stating \n \n44 See 16 U.S. Code §§ 824d, 824e; see also NAACP v. FPC, 425 U.S. 662, 670 (1976) (explaining that the “public \ninterest” phrasing of the Federal Power Act and Natural Gas Act as a directive to “promote the orderly production of \nplentiful supplies of electric energy and natural gas at just and reasonable rates”). \n45 FERC, What FERC Does, https://www.ferc.gov/what-ferc. \n46 October 9 Order at P 49."},{"page":15,"startToken":4527,"endToken":4685,"text":"15 \n \nin part, “The registry will enable PJM to better forecast load growth, plan and manage the \ntransmission system, and study and provide the anticipated new transmission services for co-\nlocated loads and Large Loads.”47 However, if the objective is to increase forecasting accuracy, \nthe record does not explain how collecting such an extensive set of data into the Registry would \nimprove upon the large load data that EDCs already compile, such as peak load contributions \n(“PLC”) in their service territories. Neither PJM nor the Commission has provided sufficient \njustification for such an extensive collection of data on retail customers.  \nAccordingly, if the requested clarifications are not granted, the Commission should grant \nrehearing and either (1) exclude existing Large Loads from the Registry absent substantial record \nevidence supporting their inclusion, or (2) direct PJM to apply to Registry data the access \nlimitations and protections described above, consistent with OA section 18.17. \n \n \n47 IRAS Filing at 22."},{"page":16,"startToken":4685,"endToken":4812,"text":"16 \n \nVII. \nCONCLUSION \nPJMICC and Steel Producers respectfully request that the Commission grant the \nclarifications set forth above, consistent with its holding in the October 9 Order, or, in the \nalternative, grant rehearing as set forth in Section VI. \nRespectfully submitted, \n \nBy: \n/s/ Susan E. Bruce \n \n \nSusan E. Bruce \nKenneth R. Stark \nMatthew L. Garber \nMcNees Wallace & Nurick LLC  \n100 Pine Street \nHarrisburg, PA  17101 \nTel:  717-232-8000 \nE-mail: sbruce@mcneeslaw.com \n \n kstark@mcneeslaw.com \n \n mgarber@mcneeslaw.com \n \nCounsel to the PJM Industrial Customer \nCoalition \n/s/ Damon E. Xenopoulos \n \n \nDamon E. Xenopoulos \nJoseph R. Briscar \nStone Mattheis Xenopoulos & Brew, PC \n1025 Thomas Jefferson Street, N.W. \nSuite E-3400 \nWashington, DC 20007 \nTel:  202-342-0800 \nE-mail: dex@smxblaw.com \njrb@smxblaw.com \n \nCounsel to Steel Producers \n \nDated: November 9, 2026"},{"page":17,"startToken":4812,"endToken":4879,"text":"CERTIFICATE OF SERVICE \n \nI hereby certify that I have this day served, via first-class mail, electronic transmission, or \nhand-delivery, the foregoing upon each person designated on the official service list compiled by \nthe Secretary in this proceeding. \n \nDated this 9th day of November, 2026. \n \n/s/ Susan E. Bruce \n \n \n \nSusan E. Bruce \nMcNees Wallace & Nurick LLC  \n100 Pine Street \nHarrisburg, PA  17101 \nTel:  717-232-8000 \nE-mail: sbruce@mcneeslaw.com"}],"sections":[{"p":1,"at":0,"title":"Opening text","method":"opening text","endPage":1,"endAt":1003,"startToken":0,"endToken":133},{"p":1,"at":1003,"title":"I. INTRODUCTION","method":"printed heading","endPage":1,"endAt":1007,"startToken":133,"endToken":134},{"p":1,"at":1007,"title":"INTRODUCTION","method":"printed heading","endPage":2,"endAt":1703,"startToken":134,"endToken":514},{"p":2,"at":1703,"title":"II. EXECUTIVE SUMMARY","method":"printed heading","endPage":2,"endAt":1708,"startToken":514,"endToken":515},{"p":2,"at":1708,"title":"EXECUTIVE SUMMARY","method":"printed heading","endPage":4,"endAt":1807,"startToken":515,"endToken":1151},{"p":4,"at":1807,"title":"III. STATEMENT OF ISSUES/ERRORS FOR ALTERNATIVE REHEARING","method":"printed heading","endPage":5,"endAt":2270,"startToken":1151,"endToken":1644},{"p":5,"at":2270,"title":"IV. PROCEDURAL HISTORY","method":"printed heading","endPage":7,"endAt":5,"startToken":1644,"endToken":2040},{"p":7,"at":5,"title":"V. REQUEST FOR CLARIFICATION","method":"printed heading","endPage":8,"endAt":453,"startToken":2040,"endToken":2360},{"p":8,"at":453,"title":"A. The Commission should clarify that PJM must collect and segment access to","method":"printed heading","endPage":9,"endAt":1215,"startToken":2360,"endToken":2792},{"p":9,"at":1215,"title":"B. The Commission should clarify that confidentiality protections for retail","method":"printed heading","endPage":10,"endAt":1442,"startToken":2792,"endToken":3106},{"p":10,"at":1442,"title":"C. The Commission should clarify that an LSE may access Registry data only for","method":"printed heading","endPage":11,"endAt":571,"startToken":3106,"endToken":3284},{"p":11,"at":571,"title":"D. The Commission should clarify that retail customers listed in the Registry will","method":"printed heading","endPage":12,"endAt":6,"startToken":3284,"endToken":3511},{"p":12,"at":6,"title":"E. The Commission should clarify that information on rates will be excluded from","method":"printed heading","endPage":12,"endAt":1073,"startToken":3511,"endToken":3672},{"p":12,"at":1073,"title":"VI. ALTERNATIVE REQUEST FOR REHEARING","method":"printed heading","endPage":16,"endAt":6,"startToken":3672,"endToken":4686},{"p":16,"at":6,"title":"VII. CONCLUSION","method":"printed heading","endPage":16,"endAt":12,"startToken":4686,"endToken":4687},{"p":16,"at":12,"title":"CONCLUSION","method":"printed heading","endPage":17,"endAt":0,"startToken":4687,"endToken":4812},{"p":17,"at":0,"title":"CERTIFICATE OF SERVICE","method":"printed heading","endPage":17,"endAt":460,"startToken":4812,"endToken":4879}]}
