The Advanced Weather Model Computing Development Act requires the Secretary of Energy and the NOAA Administrator to carry out joint research and development using advanced computing techniques to improve ‘‘advanced weather models’’ across weather-to-climate time scales. The bill mandates an interagency agreement (MOU or similar), a competitive merit-reviewed process for proposals, pilot proof-of-concept work comparing new approaches to current operational models, and periodic reporting to designated congressional committees.
The legislation also authorizes up to three centers of excellence at DOE National Laboratories, directs workforce and infrastructure support, allows multi-year contracts under existing procurement rules, and ties all activity to statutory research-security requirements. For practitioners, the measure channels DOE HPC/AI capabilities into operational modeling, imposes new coordination and compliance steps on participating institutions, and creates a time-limited initiative with explicit deliverables and reporting milestones.
At a Glance
What It Does
Directs DOE and NOAA to execute collaborative R&D using high-performance computing, AI, data assimilation, and related methods to improve weather and climate models. Establishes a competitive, merit-reviewed Initiative for proof-of-concept comparisons, authorizes up to three National Laboratory centers of excellence, and requires two-year reports to Congress.
Who It Affects
National Laboratories hosting DOE HPC systems, NOAA research labs and the National Weather Service, universities and nonprofit modeling groups that apply for awards, private-sector partners in modeling and cloud/HPC services, and state/local emergency managers who rely on forecasts.
Why It Matters
Brings DOE computational resources and AI expertise directly into forecasting research, potentially improving forecast accuracy and resolution and changing how operational models are developed and ported across architectures. It also sets a model for coordinated federal use of HPC for mission-driven environmental modeling while layering in research-security constraints.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates a formal bridge between DOE computing capabilities and NOAA’s modeling mission. It instructs the two agencies to sign an MOU or interagency agreement and use a competitive, merit-reviewed process to fund collaborative projects.
That process is open to federal labs, universities, nonprofits, and consortia and is intended to prevent duplicative work while targeting improvements in model codes, data handling, and computational methods.
A central feature is an Initiative to test models developed with advanced computing techniques against current National Weather Service operational outputs. The Initiative explicitly includes archival capacity for model output, an agile framework for computing decisions, workforce development programs, and mechanisms for community sharing of modeling innovations (including Unified Forecast System–compatible work).
The Initiative is designed as a proof-of-concept vehicle rather than a permanent program and is subject to a five-year sunset for the authorities created in that section.To concentrate technical work, the bill permits DOE to host up to three centers of excellence at National Laboratories. Those centers are expected to partner with NOAA research labs, build public-private pathways for training and infrastructure access, and optimize software and algorithms for high-performance systems.
DOE and NOAA may use reimbursable agreements and enter multi-year contracts under existing procurement authorities to support ongoing operational research.Finally, every activity must comply with federal research-security rules found in subtitle D of title VI of the Research and Development, Competition, and Innovation Act. Both agencies must report to specified congressional committees within two years, documenting coordination, technical gains, opportunities to expand capabilities, and plans for continued collaboration.
The Five Things You Need to Know
Section 3 requires DOE and NOAA to formalize collaboration through an MOU or interagency agreement and to use a competitive, merit-reviewed process for selecting projects.
Section 4 creates an Initiative to run proof-of-concept comparisons between models developed with advanced computing techniques and current National Weather Service operational models.
The bill authorizes up to three centers of excellence at DOE National Laboratories, prioritizing labs with existing NOAA partnerships, AI-enabled HPC, weather-modeling experience, and geographic proximity to NOAA research labs.
Both the Initiative and the broader program require two-year reports to designated congressional committees; the authority for Section 4 activities sunsets five years after enactment.
All activities must comply with subtitle D of title VI of the RD&CIA (research security), and DOE/NOAA may use multi-year contracts under 41 U.S.C. 3903 for operational R&D support.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions that frame scope and tools
Section 2 sets the terms the bill uses: ‘‘advanced computing techniques’’ (explicitly listing AI, HPC, cloud, data assimilation, and quantum computing) and ‘‘advanced weather model’’ (models spanning weather to climate scales). These definitions constrain the program’s remit: the work must target modeling systems and the computational methods that support them, not unrelated environmental programs.
Interagency coordination, competitive awards, and a two-year report
Section 3 directs DOE and NOAA to run collaborative R&D focused on improving advanced weather models, and it requires an MOU or equivalent interagency agreement to implement those activities. The agreement must establish a competitive, merit-reviewed process open to federal agencies, National Labs, higher-education institutions, nonprofits, and consortia. The section authorizes reimbursable agreements between agencies and mandates a congressional report after two years detailing coordination, technical opportunities, achievements, and plans to continue collaboration — a mechanism to force early transparency and to surface gaps in capability or governance.
Initiative for proof-of-concept modeling and program mechanics
Section 4 creates the Initiative, to be run by NOAA in collaboration with DOE, which will fund pilots that leverage DOE computing and expertise to develop advanced-model workflows and compare them against operational NWS forecasts. The section lists operational mechanics — archival capacity for model output, an agile requirements approach to computing choices, workforce recruitment and retention measures, and expectations for community-based sharing. It explicitly allows comparative research between new models and operational forecasts and requires an evaluative report to Congress after two years. The authority for these activities is time-limited: it terminates five years after enactment.
Centers of excellence at National Laboratories
DOE, working with NOAA, may establish no more than three centers of excellence at National Laboratories to research, develop, and deploy advanced computing for weather models. The centers are meant to create public-private partnership pathways, optimize libraries and algorithms for HPC, and support workforce and infrastructure development. Selection criteria prioritize labs with NOAA partnerships, AI-enabled HPC systems, weather-modeling expertise, and proximity to NOAA research facilities — signaling a lean toward labs already embedded in weather research ecosystems.
Procurement authority and contracting flexibility
The bill authorizes DOE and NOAA to enter multi-year contracts under 41 U.S.C. 3903 and requires compliance with that statute. That provision gives program managers procurement flexibility for multi-year operational R&D while preserving statutory safeguards for multi-year agreements. Practically, it reduces the need to re-compete short-term operational research annually and facilitates longer development cycles.
Mandatory research-security compliance
All authorized work must be carried out in compliance with subtitle D of title VI of the Research and Development, Competition, and Innovation Act. That ties program activities to existing federal research-security standards — affecting data-sharing arrangements, foreign collaboration, personnel vetting, and controlled-access computing environments.
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 research labs and the National Weather Service — gain access to DOE HPC resources, AI expertise, and center-level partnerships that can accelerate model development and potentially improve forecast skill and resolution.
- DOE National Laboratories that host AI-enabled HPC systems — receive designated roles (up to three centers of excellence), additional mission-driven funding opportunities, and stronger ties to operational environmental missions.
- Academic modeling groups and nonprofit research consortia — become eligible for competitive awards and benefit from improved archival access to model output and community-based software sharing.
- State, local, and tribal emergency managers and infrastructure planners — stand to gain more accurate, higher-resolution forecasts and research outputs that could improve decision-making if the Initiative's pilots translate into operational gains.
- Private-sector weather-tech firms and HPC/cloud vendors — can partner through public-private models, provide specialized services, and commercialize performance-portability and optimization tools developed under the program.
Who Bears the Cost
- DOE and NOAA program offices — must provide staff time for interagency coordination, administer competitions and reports, and potentially reallocate budget lines to support centers, pilots, and archival capacity.
- National Laboratories selected as centers — will face onboarding, partnership-management, and infrastructure commitments that require in-kind resources and internal coordination; smaller labs may be disadvantaged if not selected.
- Universities and nonprofits applying for awards — must compete under a merit-reviewed process and may need to invest own resources to meet proposal requirements, data-security standards, and compute access commitments.
- Private partners and vendors — will need to comply with research-security requirements and possibly operate in controlled-access environments, which can raise costs and slow collaboration.
- Operational units within NOAA (e.g., NWS) — may incur integration costs if pilot models require certification, validation, or re-tooling before adoption into operational pipelines.
Key Issues
The Core Tension
The bill balances two legitimate priorities that point in different directions: it seeks rapid, open community innovation in modeling by encouraging sharing and multi‑partner research, while also imposing strict research-security controls and concentrating work at a small number of DOE labs — forcing a trade-off between openness (which accelerates adoption and broad participation) and controlled access (which protects sensitive research and infrastructure).
The bill threads an ambitious technical agenda through a set of administrative constraints that will shape outcomes. First, the requirement to use a competitive, merit-reviewed process opens the program to a broad research base but also creates administrative overhead and the potential for uneven funding distribution — institutions with proposal-writing capacity and existing DOE ties will be advantaged.
Second, the legislation promotes open, community-based software and data sharing ‘‘to the maximum extent practicable’’ while simultaneously requiring compliance with research-security rules; reconciling openness with controlled access for sensitive computing or data will require detailed policy work and likely technical gating (segmented archives, vetted user access) that could blunt some benefits of community sharing.
Implementation hinges on practical issues that the text leaves to agency execution. ‘‘Performance portability’’ between DOE HPC architectures and NOAA operational systems is a technical challenge that depends on funding for code refactoring, standards adoption, and sustained engineering support — none of which are fully funded by the statutory text. The five-year sunset on the Initiative authorities creates a compressed timeline for demonstrating operational value; if measurable benefits require longer development cycles, the program may struggle to show sufficient return before authorities lapse.
Lastly, centers of excellence concentrate resources and expertise but risk leaving other capable institutions with fewer opportunities unless the agencies use the competitive process to seed broader collaboration.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.