{"resourceId":"tri-city-herald-aws-west-richland-21-data-centers-20261102","versions":[{"version":"external-6b83a7120db03624c5a28e38a69f95cab71819921e7f90f06600a2694b0254ed","resource":{"id":"tri-city-herald-aws-west-richland-21-data-centers-20261102","title":"Tri-City Herald: AWS confirms it is behind a $264M West Richland, Wash., land deal for up to 21 data center buildings as the council weighs a moratorium","organization":"Tri-City Herald; Amazon Web Services; City of West Richland","sector":"Local government; land use and utilities infrastructure","geography":"West Richland, Washington, United States","publishedAt":"2026-11-02","publicationDate":"2026-11-02","eventDate":"2026-11-03","sourceName":"Tri-City Herald","sourceLabel":"Amazon will build up to 21 data centers on West Richland land it paid $264M for","sourceUrl":"https://www.tri-cityherald.com/news/business/article317886652.html","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["infrastructure","governance-procurement","operating-model"],"finding":"The Tri-City Herald reports (Nov 2) that AWS confirmed it is the buyer behind Trammell Crow's $264 million July purchase of nearly 1,000 acres at Lewis & Clark Ranch in West Richland, planning three buildings first and up to 21. AWS has not submitted a site plan; the project is subject to Washington SEPA review. Residents, including about 200 homes across Ruppert Road, have pushed back, and the council was to consider an interim moratorium on Nov 3. AWS's FAQ claims outside-air cooling 93% of the time, 10 million gallons of water a year for three buildings rising to 70 million at 21, and that its power needs won't affect local utility customers; those are AWS statements reported by the paper. The paper notes AWS previously used an alias for the Wallula Gap site.","sledRelevance":"Local governments, ports and utilities negotiating AI data center capacity face disclosure, land-use and utility questions; the alias purchase and moratorium push show how trust issues shape approvals. For SLED AI buyers it is context on regional capacity and community constraints, not a deployment.","evidence":"Independent local reporting with AWS's confirmation by phone and its FAQ figures; no independent verification of water or power claims.","architectureImplications":"Relevant to regional AWS capacity planning only indirectly; no technical detail.","governanceImplications":"Raises transparency questions for councils about undisclosed buyers, SEPA review and moratorium use.","securityPrivacyImplications":"No security implications reported.","caveats":"Water, power, emissions and jobs figures are AWS claims. Moratorium outcome on Nov 3 unknown at submission. Not an AI deployment.","streamIds":["aws"],"roles":{"sales":"This is not a sales opportunity in itself; it is context for any conversation with Pacific Northwest local governments about AI infrastructure. Councils are wary of undisclosed buyers and unverified utility claims. Advisory value lies in helping a city or port structure independent review of water, power and tax commitments, not in advocating for or against AWS. Keep a neutral posture and avoid repeating AWS's figures as facts.","engineering":"Engineering relevance is limited. For customers planning AI workloads, the item signals continued AWS capacity expansion in the region but no Region or service change. If advising a municipality or utility, the technical work would be checking AWS's claimed cooling, water and load figures against independent engineering estimates and utility interconnection studies.","delivery":"For a local-government client, delivery would mean supporting a structured review process: documenting SEPA milestones, independent checks of water and power claims, public engagement records and enforceable commitments in any development agreement. Ownership sits with the city planning and utilities functions. Track the Nov 3 moratorium decision and the Nov 19 open house as milestones."},"roleDetails":{"sales":{"customerProblem":"Cities facing hyperscale proposals need to evaluate company claims on water, power and taxes and respond to resident concerns.","stakeholders":["City manager and council","Planning director","Local utility","Port authority"],"discoveryQuestions":["What independent review of water and power claims is planned?","How will SEPA findings feed the development agreement?","What disclosure rules apply to buyers using intermediaries?"],"valueHypothesis":"Independent review may help councils make defensible decisions; no outcome is implied.","potentialEngagement":"A bounded advisory review of a development agreement's utility and disclosure terms for a local government.","unsupportedClaims":["AWS water and power figures as verified facts","Any project outcome","SLED AI deployment benefit"]},"engineering":{"fit":"Advisory relevance for municipalities and utilities; no product fit.","architectureIntegration":"Not applicable; no technical integration described.","prerequisites":["Site plan submission","SEPA documentation","Utility load studies"],"constraints":["Washington SEPA review","Possible interim moratorium","Company figures unverified"],"security":"No security content in source.","proofOfValue":["Compare claimed water use with independent estimates","Verify utility statement against provider studies"]},"delivery":{"work":"Support a local government's structured review of the proposal.","dependencies":["SEPA process","Council moratorium decision","Utility studies"],"ownership":"City planning department with council oversight.","skillsAdoption":"Staff need capacity to evaluate hyperscale technical claims.","governanceCheckpoints":["Nov 3 moratorium decision","Site plan submission","SEPA determination"],"acceptanceCriteria":["Proposed: every company utility claim has an independent check documented","Proposed: public engagement record published before approval"],"risks":["Unverified claims accepted","Community trust erosion","Legal challenge to moratorium"]}},"retrievedAt":"2026-11-03T04:02:54Z","enrichedAt":"2026-11-03T04:05:18Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"AWS says 120-150 jobs per initial phase and 1,000 at full scale per site (company statements).","procurementImplications":"Local tax and utility negotiations: AWS described future property taxes only as 'millions'.","operatingModelImplications":"Cities need a process for evaluating hyperscale proposals, including independent review of water and power claims.","sourceVerification":{"openedUrl":"https://www.tri-cityherald.com/news/business/article317886652.html","referenceExcerpt":"AWS has not yet submitted a site plan to the city of West Richland.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}