From the NVIDIA edition of September 23, 2026
ts2 analysis: AEMA flexibility needs contracts; 100 GW is a scenario; 130 kW trials ≠ GW campuses
ts2.space (Marcin Frąckiewicz) · AI datacenter energy policy / independent analysis · U.S.-centric policy analysis (global transferable caution)
- Publisher
- ts2.space
- Original publication
- September 17, 2026
- Source retrieved
- 2026-09-24
- Event date
- 2026-09-16
What happened
Sep 17, 2026 analysis of AEMA (Emerald AI/Google/NVIDIA, launched Sep 16) argues flexible connections only work if curtailment is dependable under the conditions that blocked firm service. It frames AEMA as extending demand response, cites Google’s 1 GW contracted DR (not a single campus shed), and stresses AEMA’s 100 GW headline is a Duke University planning scenario (≈98 GW at 0.5% average curtailment across 22 balancing authorities)—not spare local electricity. Strongest technical evidence cited: Emerald/EPRI/National Grid/Nebius five-day 130 kW London trial (22 events, <1 min response, up to 40% reductions) — four orders of magnitude below 1 GW. Contracts need baselines, auditable telemetry, event limits, and penalties; Latitude Media is cited that AEMA repurposes a largely inactive 2014 alliance and is advocacy—not a regulator.
Why it matters
Independent policy/engineering diligence that pairs with Register’s walled-garden Flex critique and yesterday’s Utility Dive binding-agreement theme: SLED interconnect strategies need tariff language and witnessed MW/time/SLO evidence, not coalition membership or national GW scenarios.
Evidence and measured results
AEMA launch Sep 16; DR extension framing; Google 1 GW contracted DR across utilities; Duke ~98 GW @ 0.5% curtailment / 2.1h avg event; 130 kW Nebius London trial details; EPRI DCFlex ≥10 demos planned; contract elements (baseline/telemetry/limits/penalties); Latitude advocacy characterization; FERC large-load tariff review context.
Limitations and uncertainty
Secondary analysis synthesizing AEMA/Duke/Emerald/Latitude/FERC; not a utility tariff text; quantitative claims depend on cited studies’ assumptions.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Interconnect delays push buyers toward flexibility slogans without enforceable terms.
- Stakeholders
- utility liaison
- general counsel
- facilities
- AI platform
- Discovery questions
- What curtailment depth/duration is writable?
- What telemetry will the utility audit?
- What penalties apply on miss?
- Value hypothesis
- Contractible flexibility can trade for faster/larger interconnect if proven at site scale.
- Potential engagement
- Interconnect diligence memo mapping AEMA claims to local tariff options.
- Unsupported claims
- 100 GW spare capacity
- Coalition membership equals approval
- 130 kW trial proves GW shed
Pre-sales engineering
Role takeaway
- Fit
- Relevant wherever Flex/AEMA language enters site planning.
- Architecture and integration
- Workload priority + BESS/onsite gen + utility signal path with audited meters.
- Prerequisites
- Baseline methodology
- Protected-job taxonomy
- Event logging
- Constraints
- Scale gap from 130 kW trials
- Local transmission constraints
- Security
- Utility telemetry share needs OT segmentation and data minimization.
- Proof of value
- Witnessed dispatch compliance
- SLO hold docs
- Scale-up re-proof plan
Delivery
Role takeaway
- Work
- Pilot + parallel tariff/IA negotiation; do not energize on advocacy alone.
- Dependencies
- utility
- counsel
- metering vendor
- platform SRE
- Ownership
- Utility liaison owns contract; platform owns control-loop ops.
- Skills and adoption
- Teams need DR operations literacy.
- Governance checkpoints
- Advocacy≠approval
- Scale re-proof gates
- Penalty clauses reviewed
- Acceptance criteria
- Signed flexible terms
- Auditable telemetry
- Missed-dispatch playbook
- Risks
- Scenario GW in capacity plans
- Unpenalized misses
- Cooling/SLO surprises at scale
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?
Control loops that work at 130 kW face cooling, conversion, multi-tenant, and SLO complexity at campus scale.
Governance
Who approves, reviews and stays accountable for outcomes?
Advocacy ≠ interconnection rights; write flexibility into tariffs/agreements with auditability.
Security and privacy
What data, permissions and controls need testing?
Telemetry sharing with utilities creates OT/data-governance obligations.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None direct.
Procurement
What should contracts, pricing and exit terms secure?
Put baseline/telemetry/penalty clauses in interconnect-related agreements.
Operating model
Which teams own the service once it runs?
Treat flexibility as an operated, audited service—not a press coalition.
Publication history
- 2026-09-23NVIDIA · Issue 188 resources
Stable resource ID: ts2-aema-flex-contracts-scale-20260917