The Capitol LedgerEvery move in Congress, on the record
HomeBillsRecordsLedger AI

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

AboutFAQFeedbackTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

The projectAboutFAQFeedback
LegalTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

All bills
3 versions
Back to ENGROSSED IN SENATE
Comparev2REPORTED TO SENATEMay 11→v3ENGROSSED IN SENATEJun 18
SubstantiveREPORTED TO SENATE → ENGROSSED IN SENATE

What changed between these versions

A substantive refinement. v3 modifies the language around preventing inefficient use of broadband funds and introduces new procedural requirements for the FCC's notice of inquiry. It also expands the scope of both the FCC's inquiry and the GAO's study to include the consideration of incorporating third-party mapping data.

Overview

A handful of targeted changes across two sections. · v3 clarifies the objectives of the Broadband Funding Map modernization, adds a new procedural safeguard for the FCC's inquiry, and expands the scope of both the FCC's evaluation and the GAO's study to include new considerations.

The primary change in v3 is the introduction of a new procedural requirement in Section 3(b)(1) allowing any Commissioner to request a vote before initiating the FCC's notice of inquiry on the Broadband Funding Map. Additionally, both the FCC's evaluation considerations in Section 3(b)(2) and the GAO's study requirements in Section 4(b) are expanded to include the feasibility and benefits of incorporating third-party mapping data. Section 3(a) also refines the language regarding the prevention of inefficient use of federal funds. The core definitions and overall structure of the bill remain consistent.

~

Modifications

~
Section 3(a)
The language describing the prevention objective was broadened.

This change expands the scope of what the Commission and NTIA are tasked with preventing. Instead of solely focusing on 'redundant overbuilding,' the mandate now includes preventing 'inefficient use or fragmentation' of federal broadband funding, potentially leading to a wider range of considerations in funding allocation and project oversight.

Before

The Commission, in coordination with NTIA, shall collect data to promote efficient use of Federal funds and prevent redundant overbuilding of broadband infrastructure with Federal funding.

After

The Commission, in coordination with NTIA, shall collect data to promote efficient use of Federal funds and prevent inefficient use or fragmentation of Federal funding for broadband infrastructure.

~
Section 3(b)(1)
A new procedural requirement was added, introducing a potential hurdle for the initiation of the notice of inquiry.

This modification introduces a new procedural step that could delay or prevent the initiation of the FCC's notice of inquiry if a majority of Commissioners do not approve it. This grants individual Commissioners more power to influence the timing and commencement of this specific inquiry, potentially affecting the timeline for modernizing the Broadband Funding Map.

Before

The Commission shall initiate a notice of inquiry concerning the optimum functionality and transparency of the Broadband Funding Map within 270 days of enactment.

After

The Commission shall initiate a notice of inquiry concerning the optimum functionality and transparency of the Broadband Funding Map within 270 days of enactment, subject to a new provision allowing any Commissioner to request a vote at the Commission level. If a vote is requested, the inquiry cannot proceed unless a majority of Commissioners approve it.

~
Section 3(b)(2)
The scope of the FCC's inquiry was expanded to include a new specific consideration.

This change directs the FCC to explicitly consider the integration of third-party mapping data during its inquiry. This could lead to a more comprehensive and potentially more accurate Broadband Funding Map by leveraging external data sources, benefiting stakeholders who rely on the map for deployment planning and funding decisions.

Before

The FCC's inquiry into the Broadband Funding Map's functionality and transparency included evaluation of five specific considerations (A-E), such as data adequacy, usability, timeliness, scope expansion, and augmentation with existing FCC tools.

After

The FCC's inquiry now includes six evaluation considerations (A-F). A new consideration (E) has been added, specifically asking whether third-party mapping data should be incorporated to improve the map's functionality and transparency. The original item (E) is re-lettered to (F).

~
Section 4(b)
The scope of the GAO's study was expanded to include a new specific requirement.

This modification ensures that the GAO's comprehensive study will assess the practicalities and advantages of integrating third-party mapping data. This analysis will provide Congress and relevant agencies with valuable insights into potential improvements for the Broadband Funding Map, potentially leading to more informed policy decisions regarding data sources and map accuracy.

Before

The GAO study on Federal agencies' roles and progress in maintaining the Broadband Funding Map included six specific requirements (1-6), covering data submission adequacy, Commission management, authority, NTIA efforts, interagency coordination, and taxpayer savings.

After

The GAO study now includes seven specific requirements (1-7). A new requirement (7) has been added, directing the Comptroller General to review the feasibility and potential benefits of incorporating third-party mapping data into the Broadband Funding Map.

Scope

Meaningful expansion or narrowing — Changes are concentrated in specific subsections of Section 3 and Section 4, rather than being scattered throughout the entire bill. — v3 represents a refinement within the existing policy direction, aiming to enhance the accuracy, transparency, and efficiency of the Broadband Funding Map. The core purpose of the bill remains unchanged, but new procedural and evaluative elements are introduced. — The changes primarily expand the scope of inquiries and studies. The new procedural requirement in Section 3(b)(1) directly impacts the initiation process for the FCC's inquiry, while the additions to Section 3(b)(2) and 4(b) expand the topics to be covered in the respective evaluations without altering other existing provisions.

Impact analysis

Federal Communications Commission (FCC) Commissioners

Procedural change, potentially leading to delays or increased scrutiny for the inquiry's commencement.

Individual Commissioners now have the explicit power to request a vote on the initiation of the notice of inquiry, requiring majority approval for it to proceed.

Federal Communications Commission (FCC) and National Telecommunications and Information Administration (NTIA)

Expanded responsibility and scope of evaluation.

The mandate for preventing inefficient use of federal funds for broadband deployment is broadened from 'redundant overbuilding' to 'inefficient use or fragmentation.' Additionally, the FCC's inquiry must now explicitly evaluate the incorporation of third-party mapping data.

Government Accountability Office (GAO)

Expanded scope of study requirements.

The GAO's study on the Broadband Funding Map is expanded to include a new requirement to assess the feasibility and benefits of incorporating third-party mapping data.

Stakeholders relying on the Broadband Funding Map (e.g., broadband providers, state/local governments, researchers)

Potential for improved data and transparency, benefiting planning and resource allocation.

The expanded scope of inquiry and study into third-party mapping data could lead to a more accurate and comprehensive Broadband Funding Map in the future.

Ask Ledger AI about this