From the NVIDIA edition of October 12, 2026
OCP base specification: interface between hyperscalers and utility grid for disturbance performance (v1.0.0)
Open Compute Project (authors from Google, Microsoft, Meta, NVIDIA) · Industry standards body · North America focus (references ERCOT, MISO, EirGrid)
- Publisher
- Open Compute Project
- Original publication
- 2026-09-17 (effective date; publicly announced 2026-10-12)
- Source retrieved
- 2026-10-13
- Event date
- 2026-10-12
What happened
Version 1.0.0, effective Sept 17, 2026, with one NVIDIA author among seven, responds to a 1,500 MW load-loss event in August 2024 and a larger one in the Eastern Interconnection on July 22, 2026. It covers only voltage ride-through and post-fault active power recovery, for the computational load (~70-90% of site load), mirroring ERCOT NOGRR 282 and MISO. Cooling loads are exempted. It states true fault ride-through is not achievable with current OEM UPS and PSU architectures. Its implementation plan would exempt operating or contracted facilities for life, with voluntary best-effort compliance.
Why it matters
High for state utility commissions and grid operators drafting large-load interconnection rules; relevant to public universities and states siting AI computing.
Evidence and measured results
Industry specification with technical rationale and references (ESIG, IEEE, MISO, ERCOT); no field test data.
Limitations and uncertainty
Authored by the regulated parties; normative only for those adopting it; excludes cooling and auxiliary loads; no measured compliance results.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-13; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- State regulators and utilities need common, enforceable ride-through terms for AI data centers after large simultaneous load-loss events, while operators want one fleet-wide standard.
- Stakeholders
- State public utility commission staff
- Grid operator / ISO planning staff
- Transmission and distribution utilities
- State economic development office
- Universities and agencies hosting or buying AI compute
- Discovery questions
- Which large-load ride-through rule applies at this site today, and which is pending?
- Does the facility qualify for any legacy or grandfathering exemption?
- How will cooling and auxiliary loads behave during a voltage sag?
- Value hypothesis
- Interpretation: aligning AI data center designs with published ride-through requirements early can reduce interconnection rework; it cannot guarantee faster approval or grid stability.
- Potential engagement
- Bounded comparison of the OCP specification against a state's pending or adopted large-load rules, highlighting exemptions and gaps.
- Unsupported claims
- That the specification is a regulation or binding on any operator
- That existing facilities will ride through faults
- That firmware updates alone achieve compliance
Pre-sales engineering
Role takeaway
- Fit
- High relevance to state utility commissions and grid planning; indirect for agencies buying cloud AI.
- Architecture and integration
- Requirements apply at the point of interconnection; computational load only; HVRT/LVRT table with minimum ride-through times and 90% recovery within 2 seconds; cooling and auxiliary loads excluded.
- Prerequisites
- PSU or MV-UPS capability data from OEMs
- Protection coordination study with the utility
- Dynamic load models
- Constraints
- Cooling loads exempt; their restart can take minutes
- Existing and contracted facilities proposed as exempt for life
- Frequency ride-through, ramp rates and oscillations deferred to future versions
- Security
- Not a security document; protection settings and monitoring telemetry shared with utilities need access controls reviewed separately.
- Proof of value
- Obtain OEM evidence that installed PSUs meet Table 1
- Simulate recloser sequences against site protection settings
- Quantify the share of site load excluded as cooling
Delivery
Role takeaway
- Work
- Map the specification's commitments and exemptions against the utility's interconnection requirements during design.
- Dependencies
- Utility interconnection agreement
- OEM firmware roadmaps
- State rulemaking timeline
- Ownership
- Data center operator's electrical engineering team with the serving utility; state commission for any rule adoption.
- Skills and adoption
- Facility engineers and public-sector owners need power-system study skills (dynamic models, protection coordination) that AI program teams usually lack.
- Governance checkpoints
- Regulator decision on grandfathering scope
- Utility acceptance of POI measurement method
- Post-event reporting process
- Acceptance criteria
- Proposed: OEM-certified ride-through capability documented for each PSU model
- Proposed: cooling-load share and restart time disclosed in interconnection filings
- Risks
- Lifetime exemptions leave a growing installed base non-compliant
- Cooling exclusion understates load-loss risk
- Spec may be cited to weaken stricter state rules
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Ride-through depends on PSU stored energy, MV-UPS, or grid-side SVC/E-STATCOM support; retrofits judged often impractical.
Governance
Who approves, reviews and stays accountable for outcomes?
Proposes grandfathering terms regulators would have to accept or reject; defers frequency ride-through and ramp-rate limits.
Security and privacy
What data, permissions and controls need testing?
Not addressed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed.
Procurement
What should contracts, pricing and exit terms secure?
Buyers of colocation or new builds can cite the spec, but utility rules govern.
Operating model
Which teams own the service once it runs?
Shifts some stability burden to utility grid-side equipment and per-site coordination studies.
Publication history
- 2026-10-12NVIDIA · Issue 374 resources
Stable resource ID: ocp-grid-disturbance-performance-spec-v1-hyperscalers-nvidia