Substation & Transmission Ownership, Operations & NERC Compliance

Connection voltage, aggregate load and operating behavior determine how a data center affects the bulk power system; 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 affect upstream voltage and protection beyond one recloser. At the other scale — connected at transmission voltage, drawing hundreds of megawatts that can move in milliseconds — you are a node the rest of the interconnection has to plan around. Chapter 4.2 got you the interconnection and the substation as a physical asset. What follows is the second set of consequences that asset triggers: who owns it, who runs it, who is liable when it misbehaves, and, as of August 2026, the compliance regime taking shape around them: FERC Order RD26-7-000 (2026-07-16) requires NERC to file computational-load standards and registry criteria by 2026-12-31 with a Phase II work plan by 2027-03-01, and NERC’s CLO/CLOP criteria (posted 2026-08-19) remain a proposal until that filing is approved — read the operative order and appendices before treating a deadline as yours.

Everything 4.3 turns on is unusually expensive to re-decide, because most of it is written into the host utility's actual load-service/interconnection agreement and tariff; a separate GIA/LGIA applies only if a generating facility is in scope. Proposed computational-load registration remains a separate status question. 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. A wrong compliance posture surfaces only after energization, when you find you are an unregistered entity operating a Bulk Electric System asset — a finding no AI operator wants in front of 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 propagates into capex, schedule, control, and — critically — which entity must assess its registered functions and applicable NERC obligations; the asset schedule and actual function, not ownership alone, decide that exposure, which is why it is the decision in 4.3 that constrains the most downstream. It is rarely a free choice: the host utility's tariff, the state commission, and the ISO interconnection rules narrow what is even on the menu. Where latitude exists, the tradeoff is sharp.

Utility-owned keeps the substation capital off your books and inside the utility's rate base, hands the HV-operations competency and the lion's share of the NERC exposure to an entity that already has it, and — its real cost — surrenders control of the schedule and the asset. You are now 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 utility process. In a market where the power transformer is already the schedule-dominating long pole (≈128 weeks standard, ≈144–208 weeks for a GSU, and up to ~60 months in constrained markets), handing the procurement to a utility that batches and prioritizes across a portfolio can cost you the very months your time-to-power thesis depends on.

Customer-owned inverts every term. You carry the capex (a transmission-class substation is tens of millions of dollars before the line), you own the procurement and can place the long-lead transformer order the day the design basis freezes, and you control its procurement and maintenance schedule within the utility’s switching, interconnection and energization constraints. The price is an HV operating capability you must build or contract for; determine TO/TOP registration separately from the ownership label. The HV yard is now your switching, your maintenance, your relay settings, your spares, and your qualified-worker program (Chapter 6.9); and 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 (NERC proposal of 2026-08-19; verify the approved appendices), while owning transmission assets can add TO/TOP registration on top. Most large self-build operators land on customer-owned for speed and control, then immediately sub-contract the O&M to a specialist because the competency is real, regulated, and unforgiving. The hybrid — utility owns up to a defined fence inside the yard, customer owns downstream — is common precisely because it lets each side hold the assets it is best equipped to operate and be registered for.

The applicability register must distinguish the currently enforceable CIP version from future enforcement dates; Appendix A holds the dated NERC reference and ISA/IEC 62443 identity rows. For each OT zone/conduit, name its risk assessment, security requirements and owner; a VLAN name does not establish a security level.

Whoever owns the yard, the POI is a seam two organizations operate across, and seams are where coordination failures live. The governing instrument is a switching-and-tagging (S&T) coordination agreement bolted onto the interconnection agreement: it names which party may operate which device, the notification and authorization sequence before any breaker or disconnect is moved, the clearance/hold-off (lockout-tagout) protocol that protects crews on either side, and the single point of contact (typically the Transmission Operator's control center) that authorizes operations affecting the bulk system. The consequence of skipping it is not theoretical — 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 NoVA event exposed: when an AI campus's protection or controls trip the whole load offline on a remote disturbance, the balancing authority experiences an instantaneous, multi-hundred-megawatt loss it could not anticipate. Coordinated operations — 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) — are what turn an unpredictable lump of load into a node the operator can actually dispatch around. The O&M model has to make this explicit: 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 anywhere near the POI has to be cleared by the right device — the one closest to the fault — without cascading trips that take out the interconnection or strand the load. That requires a single, jointly-owned protection study that spans both sides of the boundary: relay coordination curves that selectively grade from the customer's MV feeders up through the main transformers to the utility's transmission line protection, with the customer's settings explicitly coordinated against the utility's 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, and the answer follows ownership — but the coordination never does. Even with a clean ownership fence, the relay settings are coupled: the customer cannot change a main-transformer differential or a feeder overcurrent setting without re-checking 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 controlled, jointly-reviewed settings database with change-management on both sides; the discipline matters because a mis-graded setting does not announce itself until a fault arrives, and then it announces itself as either a needless wide-area trip or a failure to clear. This is also where the protection standards bite — PRC-024/PRC-027 for the functions you register for, and the draft load-side CLO-003 protection-coordination duty — and where a transmission-connected entity’s relay program becomes auditable; the utility agreement separately governs coordinated relay settings. → reactive/voltage and frequency behavior toward the POI in Chapter 4.10; grounding and the protection earthing basis 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; its recipient acknowledgment/reporting duties are distinct from the nonmandatory Essential Actions. 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: 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 Order RD26-7-000 (2026-07-16) directs NERC to file the standards and registry-criteria revisions by 2026-12-31 and a Phase II work plan by 2027-03-01; the comment window on the August proposals runs to 2026-09-18, and adoption and approval remain pending. Until the approved appendices name the entity and the site aggregation rule, the registration allocation stays a watch item — read the filed text, not this summary, before assigning obligations.

Registration opens only the standards applicable to the functions the entity performs; CIP attaches through applicable registered functions and in-scope BES Cyber Systems — CLO/CLOP registration alone does not activate it. Owning transmission assets can carry Transmission Owner/Operator obligations, while on-site generation that can serve the grid can carry Generator Owner/Operator obligations (Chapter 4.8). For an applicable registered function with in-scope BES Cyber Systems, the cybersecurity weight lands through the CIP-002 → CIP-015 cluster: CIP-002 (CIP-002-5.1a today; NERC’s June 8–14, 2026 bulletin, p.3, lists July 1, 2028 for CIP-002-8) is the gateway. CIP-002-5.1a, §A.4, R1 and Attachment 1 identifies the responsible entities, facilities and high/medium/low-impact categorization method, so confirm the edition enforceable at your site on your energization date. That categorization determines how much of the rest of the family (CIP-003 through CIP-013 governance, access, ports, patching, recovery, supply chain; CIP-014 physical security of critical substations; and the newest, CIP-015 internal network security monitoring) applies and at what depth. This is the canonical home for the CIP cluster as it applies to large loads; the broader security architecture lives in Part 11 (Chapter 11.11).

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 each obligation comes from, because they are enforced by different people. Legacy NERC standards bind the functions they name: TPL-001 binds planning coordinators and transmission planners; PRC-024 and MOD-026/027 are generator standards; 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 if you separately register as a TO, TOP, GO or GOP because of 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: 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; 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: NERC’s August 2026 drafts 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. Write those deliverables into the site agreement now — the same models, settings, communications and disturbance records the drafts will require — so the compliance program is already producing the evidence when the standards take effect; an agreed deliverable can be due under contract while a draft standard is still pending. 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 are not independent; they chain. Ownership sets where the assets sit; where the assets sit sets the operations and protection seam you coordinate across; and 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 you have, in the same stroke, chosen to own the HV-operations interface, to assess CLO/CLOP applicability against the final effective criteria when available, 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 buy down the obligation but inherit its schedule, losing the ability to fix protection or operations interfaces on your own timeline.

Set 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 required by the applicable effective rule and connection agreement is engineered in Chapter 4.10; the protection earthing and grounding basis in Chapter 4.11; and the metering and electrical-operations layer that produces the evidence 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.