Substation & Transmission Ownership, Operations & NERC Compliance

How a data center affects the bulk power system depends on its connection voltage, its aggregate load and how that load behaves. No voltage threshold alone settles ownership or registration. On a distribution feeder, the tariff and asset boundary still allocate ownership and operating duties, and a large synchronized load can disturb upstream voltage and protection well beyond one recloser. Connect at transmission voltage and draw hundreds of megawatts that can move in milliseconds, and you become a node the rest of the interconnection has to plan around. Chapter 4.2 covered the interconnection and the substation as a physical asset. This chapter covers the second set of consequences that asset triggers: who owns it, who runs it, who is liable when it misbehaves, and, as of October 2026, the compliance regime forming around it. The CLO/CLOP registry criteria won NERC Board approval on 2026-10-08, and the matching standards then cleared their final ballot, a result NERC announced on 2026-10-15. Nothing in that package binds anyone until FERC approves NERC’s filing; the registration section below sets out the schedule.

Almost everything in this chapter is expensive to re-decide, because it is written into the host utility's load-service or interconnection agreement and tariff. A GIA/LGIA comes in only if the project includes a generating facility, and computational-load registration is a separate question again. Get ownership wrong and you have either surrendered control of your own front door or signed up for an HV-operations competency you did not want to build. Get the compliance posture wrong and you find out after energization, as an unregistered entity operating a Bulk Electric System asset, a finding no AI operator wants to explain to a regional entity auditor.

The customer substation that steps transmission voltage (115 / 138 / 230 / 345 kV) down to your medium-voltage distribution can be owned by the utility, by you, or split at a defined boundary inside the yard. Ownership drives capex, schedule and control, and it decides which entity must assess its registered functions and NERC obligations. Regulatory exposure follows the asset schedule and the functions actually performed, not ownership alone, so this decision constrains more downstream than any other in this chapter. It is rarely a free choice: the host utility's tariff, the state commission and the ISO interconnection rules narrow the menu. Where latitude exists, the tradeoff is sharp.

Utility-owned leaves title, and the utility's yard-operating responsibilities, with the utility. It does not settle who pays. The effective tariff and facilities agreement do that. Depending on them, you may pay a contribution in aid of construction (CIAC), an upfront facilities charge or a recurring one, and the total can reach the full cost your load caused. Dominion Virginia's terms (IV.E.2–3, effective 2026-01-01) show the pattern: company-installed equipment stays company property while the customer pays a monthly charge for it. Pennsylvania's 2026-04-30 model order is guidance for later utility filings, not an effective tariff. Large-load tariffs are also layering multi-year minimum-demand (take-or-pay) billing over the facilities charge: AEP Ohio's data-center tariff does it today, and Dominion will bill its GS-5 class this way from 2027 (Chapter 3.4). Compare ownership options on total committed payments rather than the facilities charge alone. The real cost of utility ownership is control of the schedule. You are in a queue behind every other interconnection the utility is building, your energization date moves when their transformer order slips, and any change to the yard runs at utility speed and process. The power transformer is already the schedule-dominating long pole: a Wood Mackenzie analyst put US substation-transformer lead times above 160 weeks in 2026 (Data Center Knowledge, 2026-05-04). GSUs are a separate category. In Wood Mackenzie's Q2 2025 survey the average wait was 128 weeks for power transformers and 143 for GSUs. By Q1 2026, Reuters reported on 2026-07-09, GSU waits had passed 160 weeks. A utility that batches and prioritizes orders across a portfolio can cost you the very months your time-to-power thesis depends on.

Customer-owned moves title, and the HV operating program that comes with it, to you. You carry the capex: a transmission-class substation costs tens of millions of dollars before the line. You also own procurement, so you can place the long-lead transformer order the day the design basis freezes. That order also carries country-of-origin risk: Executive Order 14421 (signed 2026-08-26) lets DOE prohibit, condition or unwind purchases of bulk-power equipment, transformers and breakers included, from covered foreign entities, with implementing rules due 2026-12-24. Before you commit to the order, establish where the transformer, breakers and controls are made and who owns each supplier (Chapter 2.3). Procurement and maintenance are yours to run, within the utility’s switching, interconnection and energization constraints. The price is an HV operating capability you must build or contract for, and TO/TOP registration is a separate question from the ownership label. The HV yard becomes your switching, maintenance, relay settings, spares and qualified-worker program (Chapter 6.9). Once the proposed CLO/CLOP criteria take effect, a Computational Load Site with ≥50 MW of connected load supplied at ≥100 kV registers its owner as CLO and its operator as CLOP (criteria approved by NERC’s Board on 2026-10-08, pending FERC), and owning transmission assets can add TO/TOP registration on top. Where you have a choice of ownership, compare actual utility and customer procurement dates, and price the HV O&M capability that customer ownership requires, whether you staff it or contract it. The competency is real, regulated and unforgiving. The hybrid, where the utility owns up to a defined fence inside the yard and the customer owns downstream, is common because it lets each side hold the assets it is best equipped to operate and be registered for.

Whoever owns the yard, the POI is a seam between two organizations, and seams are where coordination fails. The instrument is a switching-and-tagging (S&T) coordination agreement attached to the interconnection agreement. It names which party may operate which device, sets the notification and authorization sequence before any breaker or disconnect moves, defines the clearance and hold-off (lockout-tagout) protocol that protects crews on either side, and designates a single point of contact, typically the Transmission Operator's control center, to authorize operations that affect the bulk system. Skipping it has real consequences. An uncoordinated customer-side switching operation can back-feed a line a utility crew believes is dead, or drop hundreds of megawatts the balancing authority did not see coming.

The second failure mode is the one the July 2024 Northern Virginia event exposed and the 2026-07-22 Ashburn event repeated. If one AI campus's protection or controls shift its entire load onto backup power during a remote disturbance, the balancing authority watches several hundred megawatts of demand it could not anticipate leave the grid. When many campuses near one fault do the same, the losses add up: about 3.8 GW at Ashburn. Coordinated operations turn that unpredictable lump of load into a node the operator can dispatch around: telemetry to the TOP's control center, agreed switching sequences, and ride-through settings that keep the load connected through faults it should ride (Chapter 4.10). The O&M model has to make this explicit, with 24/7 HV operations coverage, an on-call switching authority and a documented interface with the utility's control room, whether you staff it or contract it.

Protection is where the ownership seam becomes an engineering problem with milliseconds of margin. A fault near the POI has to be cleared by the device or devices that isolate the faulted protection zone, and only those, with coordinated backup clearing if a relay or breaker fails. Take a line fault: breakers open at both ends. In the 2026-07-22 Ashburn event the nearer terminal tripped in Zone 1 and the remote one in Zone 2 (PJM/Dominion, 2026-08-06). That calls for a single, jointly owned protection study spanning both sides of the boundary. It covers line distance, transformer and bus differential, and breaker-failure schemes, plus the overcurrent grading that runs from the customer's MV feeders up through the main transformers to the utility's line protection. Time-current coordination curves apply to those overcurrent elements. Settings on each side must be coordinated against the other so that selectivity holds and neither side trips for a fault the other should clear.

The fork is who sets and owns the relays on each side. The answer follows ownership, but the coordination never does. Even with a clean ownership fence the settings are coupled: the customer cannot change a main-transformer differential or a feeder overcurrent setting without rechecking coordination with the utility's line relays, and the utility cannot retune its line protection without confirming the customer still grades selectively beneath it. Modern practice runs this as a jointly reviewed settings database with change management on both sides. The discipline matters because a mis-graded setting stays silent until a fault arrives, and then shows up as a needless wide-area trip or a failure to clear. NERC’s protection standards reach this seam only through a registered function. PRC-027 (protection-system coordination) binds Transmission Owners, Generator Owners and Distribution Providers that own protection on BES Elements. PRC-024 sets protection limits for generating resources, so it reaches you only if on-site generation makes you a Generator Owner. For the load itself, the duty is the proposed CLO-003 protection coordination (passed final ballot, not yet in effect). Once one of these applies, your relay program becomes auditable; the utility agreement governs the coordinated settings either way. Reactive/voltage and frequency behavior toward the POI is in Chapter 4.10; grounding and the protection earthing basis are in Chapter 4.11.

Large data centers affect the Bulk Electric System through their aggregate load and control response. NERC’s May 4, 2026 Level 3 alert, pp.1–3 addresses computational-load modeling, studies, protection and controls. It went to transmission planners, owners and operators, planning coordinators, balancing authorities and reliability coordinators, not to data centers. Those recipients must acknowledge it and report back, but its Essential Actions are not mandatory. On 2026-08-19 NERC posted second-round registry criteria (Rules of Procedure Appendices 2/5A/5B) for two proposed functions, Computational Load Owner (CLO) and Computational Load Operator (CLOP), alongside draft CLO-001/002/003 standards under Project 2026-02. Under those criteria, a Computational Load Site with at least 50 MW of total connected load supplied through equipment connected at 100 kV or above, from one or more points of connection, would register its owner as CLO and its operator as CLOP. FERC’s 2026-07-16 order in Docket RD26-7-000 directs NERC to file the standards by 2026-12-31, with the registry-criteria revisions expected by the same date, and a Phase II work plan by 2027-03-01. NERC's Board approved the CLO/CLOP registry criteria on 2026-10-08, and the standards (CLO-001-1, CLO-002-1 and CLO-003-1, with revised FAC-001-5 and FAC-002-5) passed their final ballot (NERC, 2026-10-15). The standards go to NERC's Board for adoption, planned for December, and then to FERC. Neither the standards nor the criteria take effect until FERC approves them. A site that clears the threshold should plan for registration now and assign obligations from the texts FERC approves.

Registration opens only the standards that apply to the functions the entity performs. CIP attaches through those registered functions and their in-scope BES Cyber Systems; CLO/CLOP registration alone does not activate it. Owning transmission assets can carry Transmission Owner/Operator obligations, and on-site generation that can serve the grid can carry Generator Owner/Operator obligations (Chapter 4.8). For a registered function with in-scope BES Cyber Systems, the cybersecurity weight lands through the CIP-002 → CIP-015 cluster. CIP-002 is the gateway (CIP-002-5.1a today; NERC’s June 8–14, 2026 bulletin, p.3, lists July 1, 2028 for CIP-002-8). CIP-002-5.1a, §A.4, R1 and Attachment 1 identifies the responsible entities, facilities and the high/medium/low-impact categorization method, so confirm which edition will be enforceable at your site on the day you energize. Keep the editions enforceable today apart from those with future dates in your applicability register; Appendix A lists the dated NERC references. Which CIP-002 impact category a system falls in decides how much of the remaining cyber family applies, and at what depth: CIP-003 through CIP-013 (governance, access, ports, patching, recovery, supply chain) and CIP-015, the newest, on internal network security monitoring. This chapter covers the CIP cluster as it applies to large loads; the broader security architecture lives in Part 11 (Chapter 11.11). The substation’s OT network gets its ISA/IEC 62443 zones, conduits and target security levels with the rest of the facility control systems in Chapter 11.10.

CIP-014 works differently. It covers the physical security of critical transmission substations and has its own Transmission Owner/Operator applicability, independent of cyber categorization. Qualifying transmission stations and substations must be assessed, and facilities found critical, with their associated primary control centers, move on to the security requirements. FERC approved CIP-014-4 on 2026-09-10, effective 2028-10-01. CIP-014-4 widens the assessment to nearby BES stations and substations within 1,500 ft (457 m), counted fence to fence whoever owns them, and puts reassessment on a 36-calendar-month cycle. Where a station contains BES Elements owned by more than one Transmission Owner, the owners must document who carries the R3 and R5 duties. A split yard that meets that scope should settle the division in the ownership agreement.

Cyber (CIP) is one half of the registration weight. The operations-and-planning (O&P) standards are the other, and for a load they are newer. Three families of deliverable exist, and it matters which family an obligation comes from, because different parties enforce them. Legacy NERC standards bind the functions they name. TPL-001 binds planning coordinators and transmission planners. PRC-024 is a generator standard, and MOD-026-2 (which replaced MOD-026-1 and MOD-027-1 on April 1, 2026) covers generators and dynamic reactive devices. MOD-032, EOP-004 and PRC-004 apply to their listed functions. A load inherits none of them by taking transmission service. They reach you only through a registered function the standard names (TO, TOP, GO, GOP or, for some standards such as PRC-004, Distribution Provider (DP)) that you perform or whose assets you own, although the site agreement can require a model even when no generator standard applies.

Contract deliverables come from the tariff and the load-service or interconnection agreement, and today they carry most of the weight. They set which party submits steady-state, dynamic and short-circuit models, how protection and trip settings are coordinated, what operational data and communications flow to the transmission operator, and which events are reported. They often mirror the legacy standards, and a utility will draft them that way, but the counterparty is the utility, not the regional entity. The proposed CLO/CLOP layer is the load-specific one. The final-ballot texts (October 2026) put interconnection studies and modeling on the owner under CLO-001, operational data and communications on owner and operator under CLO-002, and protection coordination and disturbance monitoring on the owner under CLO-003. CLO-003-1’s implementation plan gives sites already in service 36 months from the effective date to meet its disturbance-monitoring requirements. A site placed in service after the effective date must comply 15 months after that date or on its in-service date, whichever is later, so a new campus should design the recorders in from the start. Write those deliverables into the site agreement now: the same models, settings, communications and disturbance records the standards will require. Then the compliance program is already producing evidence when the standards take effect, and an agreed deliverable can be due under contract while the standard is still awaiting Board adoption and FERC approval. The grid-interface engineering is built out in Chapter 4.10; the interconnection-study front end in Chapter 3.2.

The chapter's three decisions chain. Ownership sets where the assets sit. Where the assets sit sets the operations and protection seam you coordinate across. The assets you own plus the load you draw set whether you clear the bright line into registration, and which functional obligations follow. Choose customer-owned for speed and, in the same stroke, you have chosen to own the HV-operations interface, to check now whether the Board-approved CLO/CLOP criteria reach your site, and to test separately whether the assets you own make you a TO/TOP as well. Price all three together rather than discovering them in sequence. Let the utility own the yard and you shed the HV operations and the asset-based obligations, but not site-based CLO/CLOP duties. You also inherit the utility's schedule, so you cannot fix protection or operations interfaces on your own timeline.

Against the rest of Part 4, 4.3 is the institutional layer over the physical one. The substation, transformer and MV distribution are engineered in Chapter 4.2 and Chapter 4.4; the grid-interactive behavior that the effective rules and your connection agreement require is in Chapter 4.10; the protection earthing and grounding basis is in Chapter 4.11; and the metering and electrical-operations layer that produces the evidence is in Chapter 4.12. What 4.3 adds is the recognition that none of that engineering is purely yours to decide. You share it, by agreement and by regulation, with the grid you have joined.