The ANCHOR Act tasks the National Science Foundation with producing a comprehensive plan to upgrade telecommunications and cybersecurity across the U.S. Academic Research Fleet. The requirement covers technical needs tied to each vessel’s scientific mission, cost estimates, timelines under different funding scenarios, and options for shared solutions or centralized services.
For research institutions, vessel operators, funders, and program managers, the bill matters because it converts a diffuse set of operational and security shortfalls into a mandated, agency-led assessment — and it explicitly ties those findings to concrete cost and funding proposals that could change procurement, charter pricing, and the division of responsibility between federal and non-federal owners.
At a Glance
What It Does
Directs the NSF Director to consult with federal agencies and vessel owners and to submit a plan that assesses telecom and cybersecurity needs, estimates costs and timelines, and lays out funding options and opportunities for shared solutions or centralization across the fleet.
Who It Affects
The National Science Foundation, Office of Naval Research, universities and laboratories that own or operate research vessels, vessel crews and deployed researchers, cloud and satellite vendors, and organizations that charter or use fleet vessels.
Why It Matters
The plan will shape near-term investment decisions, set expectations for cybersecurity and data-handling standards aboard academic ships, and influence operational costs (including potential increases in charter rates) as well as long-term capacity for remote and real-time science at sea.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill requires the NSF Director, working with other federal agencies and the heads of universities or labs that operate fleet vessels, to produce a single plan that reconciles scientific mission needs with telecommunications and cybersecurity requirements. That plan must be tailored to vessel classes so it does not treat a coastal research vessel and an ocean-going ship as interchangeable, and it must include cost estimates and timelines that show what can be done under different funding scenarios.
The plan's technical work is twofold: first, a telecommunications and networking assessment that defines speed and bandwidth targets tied to operational uses like telemedicine, real-time data streaming, remote instrument control, and off-ship backups; second, a cybersecurity assessment that follows CISA and NIST guidance and draws on prior expert work (notably the JASON report on NSF major facilities). The bill asks the Director to consider both vendor/enterprise hardware and shipboard high-performance computing, and to identify training and personnel gaps.Beyond technical and cost assessments, the bill requires the plan to explore practical delivery models: consortial licensing, common technical stacks, and possible centralization of cybersecurity and data-management functions at a shore facility.
It also requires a spending plan that identifies how NSF, the Office of Naval Research, non-federal vessel owners, and fleet users could share costs. Finally, the Director is given authority to support upgrades consistent with the plan and must report back on implementation progress after the plan is delivered.
The Five Things You Need to Know
The Director of the National Science Foundation must submit the required plan within 18 months of enactment to the Senate Committee on Commerce, Science, and Transportation and the House Committee on Science, Space, and Technology.
The plan must include a cost assessment that separately identifies equipment costs above current spending (satellite comms, shipboard HPC, enterprise hardware), personnel/training/logistics costs above current spending, and the estimated impact of these costs on daily charter rates.
The bill lists specific network use cases the plan must address, including telemedicine and mental-health communications, real-time streaming for shore-based observers, remote scientific instrumentation and seafloor mapping, remote maintenance support, and K–12 outreach.
Cybersecurity recommendations must be informed by CISA and NIST guidance and explicitly consider the October 2021 JASON report on cybersecurity at NSF major facilities, plus the handling requirements for controlled unclassified or classified information.
After the plan is submitted, the Director may support upgrades consistent with it and must deliver a progress report to the same Congressional committees no later than two years after the plan’s submission.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Establishes the Act's short name: "Accelerating Networking, Cyberinfrastructure, and Hardware for Oceanic Research Act" or "ANCHOR Act." This is a formal naming clause with no operational effect, but it signals congressional intent to focus on both networking and hardware across ocean research assets.
Plan requirement and consultations
Mandates that the NSF Director, in consultation with relevant federal agency owners and heads of universities/labs that operate fleet vessels, produce and submit a plan. Practically, this requires NSF to assemble multi-stakeholder working groups and to coordinate with non-federal vessel owners early in the process — a logistic and governance task that will determine how candidly institutions share operational vulnerabilities and cost data.
Required elements of the plan
Specifies six core plan elements: a telecommunications and networking needs assessment; a cybersecurity assessment aligned with CISA/NIST; a detailed cost estimate (equipment, personnel/training, and charter-rate impacts); implementation timelines under varying budgets; an analysis of opportunities for shared solutions or centralization; and a spending plan outlining potential contributions from NSF, ONR, non-federal owners, and fleet users. Each element forces NSF to move beyond high-level recommendations into quantified, programmatic options suitable for budget requests.
Technical and standards considerations
Directs the Director to consider specific operational network capabilities (bandwidth/speed targets) tied to listed use cases such as telemedicine, real-time science streaming, remote instrumentation, and outreach. It also requires consultation with CISA and NIST and explicit consideration of the JASON report on NSF facilities. This provision anchors the plan to recognized federal cyber standards while recognizing maritime operational constraints.
Implementation authority and progress report
Authorizes NSF, in coordination with ONR and non-federal partners, to support upgrades consistent with the plan and requires a progress report to the same Congressional committees two years after plan submission. The authorization to 'support' upgrades is permissive, not mandatory, meaning actual implementation depends on subsequent funding decisions and interagency agreements.
Definitions and scope
Defines 'Director' as the NSF Director, adopts the statutory definition of 'oceanographic research vessel' from 46 U.S.C. 2101, and defines the 'U.S. Academic Research Fleet' by vessel-operator status, designation through the fleet evaluation process, and participation in the University-National Oceanographic Laboratory System. Those definitions set clear boundaries about which vessels and organizations are in scope for the plan and any subsequent funding.
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
- University and laboratory fleet operators — gain a roadmap and federal engagement that can unlock funding, reduce security gaps, and standardize procurement for communications and cyber equipment.
- Deployed researchers and technicians — get improved bandwidth and remote-support capabilities (real-time streaming, remote instrument control, shoreside data backups) that expand the kinds of science that can be done at sea.
- Ship crews and vessel passengers — benefit from mandated consideration of telemedicine, mental-health communications, and other personnel-support systems that can improve safety and wellbeing on long deployments.
- Federal funders and program managers (NSF, ONR) — receive a consolidated needs assessment and spending plan that can inform budget requests and reduce duplicated procurement across institutions.
- K–12 and outreach programs — stand to gain more reliable video communications and occasional remote classroom access that broaden educational use of research voyages.
Who Bears the Cost
- Non-federal vessel owners and universities — may be required to contribute funding or to absorb portions of upgrade and operating costs under the spending plan, particularly for shipboard hardware and personnel training.
- NSF and the Office of Naval Research — face new demands for constrained appropriations if they choose to support upgrades; the bill authorizes support but does not appropriate funds.
- Fleet users and charterers — could see higher daily charter rates if cost estimates translate into passed-through charges to cover equipment or personnel expenses.
- Smaller institutions and labs — risk disproportionate compliance and operational burdens if shared solutions still require local investments in hardware, training, or ship modifications.
- Vendors and systems integrators — will need to meet maritime-specific procurement requirements and interoperability expectations, potentially increasing upfront engineering and certification costs.
Key Issues
The Core Tension
The central dilemma is balancing the need to modernize and secure critical research infrastructure against the cost, operational complexity, and potential access impacts of doing so: invest to raise capability and resilience (which can increase charter costs and administrative burdens) or accept a patchwork of lower-cost configurations that leave cyber and communications vulnerabilities unaddressed.
The bill is procedural: it compels a plan but does not itself appropriate funds. That design creates an immediate implementation tension — a clear, prioritized set of needs without a guaranteed funding stream.
NSF’s ability to convert the plan into actual upgrades depends on future appropriations, interagency commitments (notably from ONR), and the willingness of non-federal owners to share costs. Expect the spending-plan element to be the locus of negotiations about who pays for what and when.
The Act also forces a choice between centralized, standardized solutions and ship-specific approaches. Centralization (shore-based cybersecurity platforms, consortial licensing) promises scale economies and easier maintenance, but it can clash with the heterogeneity of vessel missions, legacy systems, and operational constraints (satellite latency, intermittent connectivity, and limited physical space for hardware).
Similarly, applying terrestrial cyber standards at sea raises practical questions about encryption performance over low-bandwidth links, incident response where connectivity is intermittent, and the logistics of updating shipboard systems without extensive drydock time. Finally, the plan’s reliance on coordination among federal and non-federal actors creates governance challenges: data sharing, liability for breaches, and who controls classified or controlled unclassified information aboard university-operated vessels will require negotiated agreements that the bill does not itself resolve.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.