Directs the National Oceanic and Atmospheric Administration to develop AI-based weather models, improve forecasts, and analyze fire environments. Encourages public-private partnerships for AI innovation and workforce development. Ensures open access to non-sensitive data and models.
Analysis summaries, actor details, and coverage mappings were LLM-classified and may contain errors.
This is a Congressional bill that, if enacted, would create binding legal obligations on the Under Secretary of Commerce for Oceans and Atmosphere (NOAA) to develop AI-based weather forecasting systems and programs. The document uses mandatory language throughout ('shall') and establishes specific requirements with reporting obligations to Congressional committees.
The document has minimal coverage of AI risk domains, with limited focus on environmental harm (6.6) through best practices for minimizing environmental impacts of AI use. There is implicit minimal coverage of system safety (7.3) through requirements for model testing and evaluation. The document primarily focuses on AI applications for weather forecasting rather than AI risk mitigation.
This document primarily governs AI use in Public Administration (excluding National Security) through NOAA's weather forecasting activities, with significant coverage of Scientific Research and Development Services through research partnerships and AI model development. It also has minimal coverage of Information sector through data processing and telecommunications aspects of weather information delivery.
The document covers multiple AI lifecycle stages with primary focus on Build and Use Model (developing AI weather models and training datasets), Verify and Validate (testing models, reforecast analysis, assessment frameworks), Deploy (making models operational), and Operate and Monitor (ongoing evaluation, technical assistance, workforce development). There is also coverage of Plan and Design through partnership structures and Collect and Process Data through comprehensive dataset curation requirements.
The document explicitly mentions AI models (specifically 'artificial intelligence weather models') and AI systems throughout. It does not explicitly reference frontier AI, general purpose AI, task-specific AI, foundation models, or compute thresholds. The focus is on domain-specific AI applications for weather forecasting. The document does not explicitly distinguish between generative and predictive AI, though the weather forecasting applications described are inherently predictive. There is no explicit mention of open-weight or open-source models, though open data access is addressed.
United States Congress (Senate and House of Representatives)
The document is a Congressional bill proposed by the legislative branch of the United States government, as indicated by the enactment clause and the legislative format.
Committee on Commerce, Science, and Transportation of the Senate and Committee on Science, Space, and Technology of the House of Representatives
Congressional committees are designated to receive mandatory reports and provide oversight of the Under Secretary's implementation of the Act's requirements.
Committee on Commerce, Science, and Transportation of the Senate, Committee on Science, Space, and Technology of the House of Representatives, National Academy of Sciences (potential independent assessor)
The Congressional committees monitor implementation through mandatory annual reporting requirements. The document also provides for independent assessment by the National Academy of Sciences or similar entities to evaluate impacts of AI weather models.
Under Secretary of Commerce for Oceans and Atmosphere (National Oceanic and Atmospheric Administration - NOAA), private entities and academic entities in partnerships, weather enterprise
The primary target is NOAA (through the Under Secretary) which is directed to develop AI weather models and programs. The document also targets private and academic entities through partnership provisions and the broader 'weather enterprise' for technical assistance and best practices.
2 subdomains (2 Minimal)