Codify — Article

Bill directs DOE–NOAA collaboration to accelerate AI and HPC for weather and climate models

Creates centers of excellence, mandates a 10-year NOAA computing strategy, and orders reports and briefings to scale high‑resolution forecasting capabilities.

The Brief

The Advanced Weather Model Computing Development Act directs closer collaboration between the Department of Energy and the National Oceanic and Atmospheric Administration to upgrade computing, data, and algorithm capabilities used for numerical weather and climate prediction. It amends the Weather Research and Forecasting Innovation Act to emphasize artificial intelligence and machine learning, authorize centers of excellence, permit multi‑year HPC and cloud contracts, and require a congressionally delivered evaluation of computing needs and forecast value.

The bill matters to agencies that run operational forecasts, researchers who need computing capacity, private cloud and HPC vendors, and emergency managers who depend on high‑resolution probabilistic guidance. It creates a planning and reporting framework—timelines, performance measures, and public input—to translate emerging technologies (including AI and exploratory quantum efforts) into operational forecasting improvements while creating new procurement and governance requirements for NOAA and its partners.

At a Glance

What It Does

Mandates DOE–NOAA collaboration on advanced computing for weather and climate, directs NOAA to expand or establish centers focused on AI/ML-enabled HPC, allows multi‑year contracts for computing infrastructure, and requires a congressional report and a public 10‑year strategic plan with recurring updates.

Who It Affects

NOAA line offices (forecasting, fisheries, oceanography), DOE research and computing facilities, commercial cloud and HPC providers, academic weather and climate modeling groups, and state/local emergency managers relying on forecast products.

Why It Matters

It formalizes computing and AI as central levers for improving forecast resolution and probabilistic guidance, sets concrete planning and oversight timelines, and signals federal willingness to use public‑private partnerships and longer contracts to secure large computing capacity.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill rewrites part of the Weather Research and Forecasting Innovation Act to put advanced computing and AI at the center of NOAA’s strategy for better weather and climate prediction. It instructs the Under Secretary to invest in artificial intelligence and machine learning tools that can be used together with high‑performance and cloud computing to improve model performance, post‑processing, visualization, and dissemination.

To operationalize that direction, the bill authorizes NOAA to expand existing centers of excellence or create new ones. Those centers are expected to work with public and private partners to provide training and workforce development, build and optimize libraries and algorithms for HPC systems, and apply modern machine‑learning methods to mission problems.

The centers are also explicitly allowed to explore quantum computing partnerships where practicable, positioning NOAA to experiment with nascent architectures without mandating production deployments.On procurement and program structure, the bill permits multi‑year contracts for operations, research, and development related to HPC and cloud infrastructure, subject to statutory procurement rules in title 41 and with language that contemplates an unfunded contingent liability if a contract is cancelled. It also creates deliverables and oversight: a report due within two years that evaluates the value of high‑resolution probabilistic forecasts and the computing needs (including cloud, quantum, visualization, and dissemination), and a public 10‑year strategic plan on NOAA’s computing and data management needs that must be produced within one year and updated every five years until 2035.Finally, the bill builds in congressional touchpoints and public input: specific congressional committees receive the report; the strategic plan must invite public comment during its development; and NOAA must provide annual briefings on progress for several years.

Together these elements create both a roadmap for upgrading forecasting capabilities and recurring accountability on whether computing investments translate into improved operational products.

The Five Things You Need to Know

1

The bill requires the Under Secretary to submit a report within two years assessing the value of high‑resolution probabilistic forecast guidance and the computing, cloud, and quantum resources needed to deliver it.

2

NOAA must publish a 10‑year strategic plan on high‑performance computing and data management within one year and update that plan every five years through 2035, with annual congressional briefings through 2030.

3

Centers of excellence may be expanded or established to develop HPC‑optimized software, train personnel, foster public‑private partnerships, and explore quantum computing applications.

4

The Under Secretary may enter multi‑year contracts under 41 U.S.C. 3903 to secure HPC and cloud infrastructure, and those contracts may include unfunded contingent liabilities if cancelled.

5

The bill defines ‘hazardous weather or water events’ for the report’s valuation to include severe storms, winter storms, extreme heat or cold, wildfire, drought, dense fog, and coastal or river flooding.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Provides the Act’s name: the Advanced Weather Model Computing Development Act. This is purely nominal but signals Congressional intent to focus on computing and model development for weather and climate prediction.

Section 2(a) (amendment to Section 108)

AI and machine‑learning investments for NOAA missions

Replaces prior language in Section 108 to require the Under Secretary to leverage AI and machine learning to enhance NOAA’s critical missions. Practically, this authorizes directed investments in algorithms, model post‑processing, and data analysis workflows that run on HPC and cloud platforms and positions AI/ML as an explicit part of NOAA’s computing strategy.

Section 2(c)

Centers of excellence to accelerate adoption of next‑gen computing

Authorizes expansion or establishment of centers that will develop software stacks, optimize algorithms for HPC architectures, provide workforce and training pathways, and facilitate public‑private partnerships. The provision encourages centers to create reusable tools and act as hubs for cross‑sector collaboration, reducing the need for each NOAA office to independently develop similar capabilities.

4 more sections
Section 2(d)

Authority for multi‑year contracts with contingent liabilities

Grants the Under Secretary the ability to use multi‑year contracting under 41 U.S.C. 3903 for HPC and cloud systems, with an explicit requirement to include the statutory contract clauses and to recognize possible unfunded contingent liabilities if a contract is cancelled. That makes long‑term supplier commitments feasible but also triggers budget and cancellation‑cost considerations.

Section 2(e)

Two‑year report on forecast value and computing needs

Requires a report, delivered to specified House and Senate committees, that (A) estimates the value of high‑resolution probabilistic forecasts for hazardous weather or water events, (B) catalogs needs for cloud, quantum, and HPC plus visualization and dissemination collaboration between DOE and NOAA, and (C) provides timelines and implementation guidance for high‑resolution models and the supporting compute and data ecosystems. The statute supplies a definition of hazardous events to guide valuation.

Section 2(b) (Strategic plan)

10‑year strategic plan on HPC and data management

Mandates a publicly available 10‑year strategic plan within one year that details computing resource needs disaggregated by NOAA line office, inventory of current facilities and contracts, cloud and emerging tech usage (AI/ML, quantum), workforce needs, and products currently constrained by compute limits. The plan must include timelines, performance measures, and a life‑cycle analysis for hardware and facilities; updates are required every five years until 2035.

Section 2(b)(3)–(4)

Public input and annual briefings

Requires solicitation of public comments during plan development and annual briefings to Congress on progress and updates to the strategy through 2030. These provisions create repeated oversight checkpoints and a formal role for external stakeholders in shaping NOAA’s computing roadmap.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Science across all five countries.

Explore Science in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • NOAA operational forecast offices — gain a coordinated plan, targeted investments in compute and AI tools, and access to centers that will accelerate model improvements and product delivery.
  • Emergency managers and state/local forecast users — could receive higher‑resolution, probabilistic forecast guidance for hazardous events if investments translate into operational models and faster dissemination.
  • Research universities and modeling centers — benefit from public‑private centers of excellence and potential access to shared HPC resources, optimized libraries, and training opportunities.
  • DOE computational facilities and national labs — receive a formal collaborative role, channeling DOE expertise and infrastructure toward weather and climate modeling problems.
  • Commercial cloud and HPC vendors — stand to win longer, multi‑year contracts and partnership opportunities to host and manage NOAA workloads and to co‑develop software stacks.

Who Bears the Cost

  • NOAA budget authorities — will need to allocate funds to implement multi‑year contracts, staff and sustain centers, and execute the strategic plan; these are new resource demands that must fit within agency budgets.
  • Procurement and financial offices — must manage multi‑year contracting and unfunded contingent liabilities, increasing complexity for budget planning and potential exposure to cancellation costs.
  • Smaller vendors and in‑house teams — may face competitive pressure from large cloud/HPC contractors and centralized centers of excellence, which could centralize tools and reduce smaller vendors’ roles.
  • Congressional appropriations committees — will inherit the responsibility to fund longer‑term computing commitments and may face tradeoffs between capital computing investments and other NOAA programs.
  • IT and workforce units within NOAA — will need to scale hiring and training (software engineers, data scientists, HPC specialists) to use new technologies effectively; shortfalls could delay the plan’s benefits.

Key Issues

The Core Tension

The central dilemma is whether to pursue rapid gains in forecast skill by contracting large, sustained computing capacity and partnering with private actors—thereby accelerating delivery but increasing procurement, budget, and governance risks—or to proceed more cautiously and incrementally, which limits exposure but may postpone the operational improvements that higher‑resolution, AI‑enhanced models could provide.

The bill pushes NOAA toward a computing‑centric modernization path but leaves several implementation questions open. It requires a strategic plan and report with concrete timelines, yet it does not appropriate funds; delivering on multi‑year contracts and building centers will depend on future appropriations and interagency resource allocations.

The multi‑year contracting authority makes it easier to secure large‑scale compute capacity but also raises the risk of long‑term financial exposure through unfunded contingent liabilities if funding lapses or programs are cancelled.

Reliance on public‑private partnerships and commercial cloud providers accelerates access to capacity but creates governance issues: data stewardship, security, model reproducibility, and cost escalation are real concerns. The bill permits exploratory quantum partnerships, which signals forward thinking but risks diverting scarce implementation effort toward technologies that remain experimental.

Finally, valuing the operational benefits of higher‑resolution probabilistic guidance—required by the report—is analytically difficult and context dependent; robust cost‑benefit estimates will require assumptions about adoption by emergency managers, communication of probabilistic products, and how improved forecasts change behavior and outcomes.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.