This bill amends the Integrated Coastal and Ocean Observation System Act of 2009 (33 U.S.C. 3601 et seq.) to refine governance language, expand the statutory scope of measurements, require regional data‑sharing processes, and reauthorize funding. Key textual changes include replacing the term "Council" with "Committee," renaming an interagency body to "Ocean Policy Committee," inserting an explicit duty to "conduct operational oceanography measurements and" and adding "and ocean" alongside "weather" in relevant statutory language.
Why this matters: the revisions formalize interagency coordination language, create a statutory expectation that federally funded programs and regional offices collaborate with regional coastal observing systems on data sharing, and secure multi‑year appropriations. The combination of governance tweaks, an operational measurement mandate, and a dedicated funding line will affect NOAA, other federal agencies that participate in the IOOS enterprise, regional observing networks, and downstream users who rely on coastal and ocean data for forecasting, navigation, and resource management.
At a Glance
What It Does
The bill amends the IOOS statute to replace "Council" with "Committee," changes a named interagency body to the "Ocean Policy Committee," inserts language requiring operational oceanography measurements, directs the interagency body to develop regional data‑sharing requirements, and authorizes $56,000,000 per year for FY2026–2030. These are textual amendments to 33 U.S.C. 3601 et seq., plus a funding authorization in the statute.
Who It Affects
Primary targets are NOAA and other federal agencies engaged in the IOOS enterprise, regional coastal observing systems that collect and serve coastal and ocean data, state and local coastal managers, academic researchers, and commercial users of marine observations and forecasts. Federally funded projects and regional offices will face new expectations to design collaboration and data‑sharing arrangements with regional systems.
Why It Matters
The statutory changes codify expectations about measurement responsibilities and interagency/regional data exchange that previously operated through policy and interagency agreements. By pairing a data‑sharing mandate with a multi‑year appropriation, the bill seeks to reduce data silos and improve access to coastal and ocean observations — with direct implications for forecasting, hazard response, and marine commercial services.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill is a focused, targeted reauthorization: it does not create a new program, but it updates the existing IOOS statute in several places to reflect operational realities and to push federal partners toward more formal regional collaboration. One standing change is terminological: the statute will use "Committee" where it previously used "Council." That rename is more than cosmetic for practitioners because it can signal a shift in how interagency decisions are framed and tracked; it also aligns statutory text with contemporary interagency bodies and their governance practices.
A consequential addition requires the program to "conduct operational oceanography measurements and" — language that makes explicit in statute what IOOS partners already do in practice. That phrasing strengthens the legal basis for sustaining in‑water and remote sensors (buoys, gliders, HF radar, coastal tide stations), their data streams, and the operational systems that ingest observations into forecasts and decision tools.
Translating that statutory duty into action will require agencies to clarify measurement standards, quality control, and responsibility for equipment and operations.The bill also inserts a new, concrete obligation: the interagency committee must develop requirements and processes so regional offices and federally funded agency projects collaborate with regional coastal observing systems for regional data sharing. Practically, this pushes federal projects to negotiate technical interfaces, metadata standards, and data access arrangements with existing regional networks.
For regional partners that aggregate observations, the change aims to reduce barriers to ingesting federal project data, but it also creates a need for explicit guidance on roles, data rights, and timelines.Finally, the bill sets an appropriations authorization of $56 million annually for fiscal years 2026 through 2030. That funding authorization provides statutory cover for multi‑year budgeting but does not itself appropriate funds; appropriations committees must still allocate the dollars.
Together, these changes endeavor to codify measurement responsibilities, standardize regional data sharing, and provide predictable funding to sustain the IOOS enterprise.
The Five Things You Need to Know
The bill replaces the word "Council" with "Committee" throughout the Integrated Coastal and Ocean Observation System Act (33 U.S.C. 3601 et seq.).
It changes the statutory name "National Ocean Research Leadership Council" to "Ocean Policy Committee" in 33 U.S.C. 3602(2).
Section 12303 is amended to add an explicit statutory duty that the program "conduct operational oceanography measurements and" — placing operational measurement activity directly in the Act's text.
Section 12304(c)(2)(B) is amended to require the Interagency Ocean Observation Committee to develop requirements and processes for regional offices and federally funded projects to collaborate with regional coastal observing systems on regional data sharing.
The bill authorizes $56,000,000 for each fiscal year 2026 through 2030 (added to the statute's authorization provisions).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Terminology and named‑body updates
This part instructs the statute to use "Committee" instead of "Council" wherever the term appears and renames the "National Ocean Research Leadership Council" as the "Ocean Policy Committee." Mechanically, the changes are textual, but they can matter for administrative alignment — statutory names inform which interagency body the law contemplates and how executive branch offices route coordination, reporting, and membership obligations.
Adds explicit operational oceanography duty
The amendment inserts the phrase "conduct operational oceanography measurements and" into the list of program objectives. That makes operational measurement an explicit statutory obligation rather than an implied activity, giving agencies a clearer legal basis to prioritize and sustain sensor networks, data acquisition, and the operational chains that feed forecasts and decision support tools. Practically, it will require agencies to reconcile responsibilities for procuring, operating, and maintaining measurement platforms and to adopt consistent QA/QC standards.
Expands 'weather' language and mandates regional data‑sharing requirements
This section inserts "and ocean" alongside existing references to "weather," broadening the statute's framing of environmental observing. It also adds a new clause in subsection (c)(2)(B) directing the Interagency Ocean Observation Committee to develop requirements and processes for regional offices and federally funded projects to collaborate with regional coastal observing systems for regional data sharing. The practical implication is that federal projects will need to coordinate technical and contractual data flows with regional networks, which raises questions about standards, metadata, access controls, and timelines for implementation.
Funding authorization for FY2026–2030
The statute's authorization language is amended to add $56,000,000 for each fiscal year from 2026 through 2030. This is an authorization, not an appropriation: it signals Congress's intent on funding levels and helps planning for multi‑year program activities, but actual disbursements depend on future appropriations actions and how funds are apportioned across NOAA, regional systems, and interagency activities.
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
- Regional Coastal Observing Systems — Gains stronger statutory leverage to obtain federal project data and clearer expectations that federal regional offices will collaborate on data sharing, improving completeness of regional datasets and operational products.
- NOAA and Interagency Partners — Receives a clearer statutory mandate for operational measurements and a multi‑year authorization that supports continuity planning and interagency program management.
- State and Local Coastal Managers — Better access to consolidated regional observational data can improve coastal planning, emergency response, and local forecasting services.
- Academic and Research Institutions — More consistent access to federal observational streams and clearer coordination processes reduce duplication and improve the value of long‑term data records used in research.
- Commercial Marine Service Providers — Improved and more consistent regional data feeds can enhance navigation, fisheries services, and private sector forecasting products, expanding marketable services.
Who Bears the Cost
- NOAA and Participating Federal Agencies — Must implement new collaboration processes, potentially fund operational measurement activities, and absorb administrative duties tied to the renamed committee and new requirements.
- Regional Observing Systems — May need to upgrade technical interfaces, absorb additional data ingestion tasks, or renegotiate data rights with federal projects to comply with the new collaboration requirements.
- Congress/Appropriations — Although the bill authorizes $56M per year, Congress must appropriate the funds; if appropriations fall short, agencies and regional partners may face unfunded mandates to meet new statutory expectations.
- Federally Funded Project Leads — Projects that receive federal funds will be expected to design and execute data‑sharing arrangements with regional systems, which may require extra project resources and contractual language.
- Private Data Providers and Contractors — Could face new expectations to conform to federal or regional data standards and to share data under terms aligned with regional systems, potentially affecting commercial data strategies.
Key Issues
The Core Tension
The central dilemma is between greater centralization and standardization versus regional flexibility and resource constraints: the bill pushes for uniform data‑sharing processes and an explicit operational measurement mandate to improve interoperability and service quality, but it provides limited detail and a single authorization level — forcing a choice between strict, centralized requirements that may overburden regional partners, or looser implementation that preserves flexibility but risks perpetuating data silos.
The bill’s changes are compact but raise several implementation questions. Renaming the statutory coordinating body to "Committee" and changing a named body to the "Ocean Policy Committee" is administratively lightweight on its face, but it could shift reporting lines, membership expectations, or the locus of decision‑making without specifying how.
The statute does not define the committee’s membership, voting rules, or dispute‑resolution mechanisms, so the practical governance outcomes will depend on interagency agreements and executive‑branch implementation documents.
The new requirement that the interagency committee develop "requirements and processes" for regional offices and federally funded projects to collaborate with regional coastal observing systems leaves a lot of detail unspecified. The bill does not set deadlines, nor does it specify standards for metadata, access controls, intellectual property, or commercial data licensing.
That creates a risk that regional systems will confront inconsistent expectations across agencies or projects unless the committee issues uniform guidance. Linked to that, the $56 million annual authorization is helpful but potentially insufficient: expanding operational measurement expectations and building interoperable regional data infrastructure can require significant capital and operating investments, and the authorization does not allocate how funds should be split between federal program management, regional system grants, or technology upgrades.
Finally, the statute codifies an expectation of increased regional collaboration but leaves unresolved how to reconcile federal legal constraints (e.g., on data sharing, privacy, or security) with regional needs and commercial sensitivities. Agencies will need to decide whether compliance is a condition of grant awards or a voluntary coordination principle, and stakeholders will watch whether the interagency committee produces binding procedures or advisory guidance.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.