{"resourceId":"ts2-aema-flex-contracts-scale-20260917","versions":[{"version":"external-5421a5faccf4f54e8dde003e296007004ca755b7f3adff42d67f9cd4aa238d74","resource":{"id":"ts2-aema-flex-contracts-scale-20260917","title":"ts2 analysis: AEMA flexibility needs contracts; 100 GW is a scenario; 130 kW trials ≠ GW campuses","organization":"ts2.space (Marcin Frąckiewicz)","sector":"AI datacenter energy policy / independent analysis","geography":"U.S.-centric policy analysis (global transferable caution)","publishedAt":"September 17, 2026","publicationDate":"2026-09-17","eventDate":"2026-09-16","sourceName":"ts2.space","sourceLabel":"Independent analysis","sourceUrl":"https://ts2.space/en/ai-data-center-flexibility/","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["infrastructure","governance-procurement","operating-model"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"Control loops that work at 130 kW face cooling, conversion, multi-tenant, and SLO complexity at campus scale.","governanceImplications":"Advocacy ≠ interconnection rights; write flexibility into tariffs/agreements with auditability.","securityPrivacyImplications":"Telemetry sharing with utilities creates OT/data-governance obligations.","caveats":"Secondary analysis synthesizing AEMA/Duke/Emerald/Latitude/FERC; not a utility tariff text; quantitative claims depend on cited studies’ assumptions.","streamIds":["nvidia"],"roles":{"sales":"When buyers cite AEMA or “100 GW unlock,” reframe to contractible curtailment at their POI. Use the 130 kW vs GW scale gap and advocacy-vs-regulator distinction. Bound: no promised fast lane from coalition membership.","engineering":"Design measurement: baseline, telemetry, response envelope, protected-job SLOs. Re-prove at each scale step beyond lab kW.","delivery":"Negotiation workstream with utility counsel alongside Flex software pilots. Acceptance = tariff/IA language + witnessed events. Risk: mistaking demos for deliverable MW."},"roleDetails":{"sales":{"customerProblem":"Interconnect delays push buyers toward flexibility slogans without enforceable terms.","stakeholders":["utility liaison","general counsel","facilities","AI platform"],"discoveryQuestions":["What curtailment depth/duration is writable?","What telemetry will the utility audit?","What penalties apply on miss?"],"valueHypothesis":"Contractible flexibility can trade for faster/larger interconnect if proven at site scale.","potentialEngagement":"Interconnect diligence memo mapping AEMA claims to local tariff options.","unsupportedClaims":["100 GW spare capacity","Coalition membership equals approval","130 kW trial proves GW shed"]},"engineering":{"fit":"Relevant wherever Flex/AEMA language enters site planning.","architectureIntegration":"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.","proofOfValue":["Witnessed dispatch compliance","SLO hold docs","Scale-up re-proof plan"]},"delivery":{"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.","skillsAdoption":"Teams need DR operations literacy.","governanceCheckpoints":["Advocacy≠approval","Scale re-proof gates","Penalty clauses reviewed"],"acceptanceCriteria":["Signed flexible terms","Auditable telemetry","Missed-dispatch playbook"],"risks":["Scenario GW in capacity plans","Unpenalized misses","Cooling/SLO surprises at scale"]}},"retrievedAt":"2026-09-24T03:05:00Z","enrichedAt":"2026-09-24T03:11:06Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"None direct.","procurementImplications":"Put baseline/telemetry/penalty clauses in interconnect-related agreements.","operatingModelImplications":"Treat flexibility as an operated, audited service—not a press coalition.","sourceVerification":{"openedUrl":"https://ts2.space/en/ai-data-center-flexibility/","referenceExcerpt":"A 130 kW cluster, however, is four orders of magnitude smaller than a 1 GW campus","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}