The NOAA Data Preservation Act restricts the Department of Commerce’s ability to terminate cloud storage contracts that hold NOAA datasets unless two conditions are met: a written uninterrupted-storage plan that covers moving the dataset (and related reporting systems) to a different cloud provider, and collaboration with the NOAA Administrator to protect the dataset. The bill uses the federal definition of “cloud service provider” in 6 U.S.C. 650.
This is a targeted statutory check on contract churn for NOAA data. For agencies, contractors, and data users, the practical effect is to formalize transition planning and require program-level coordination before a contract storing NOAA data can be ended — a change with implications for procurement schedules, continuity-of-operations planning, and records-management practice across NOAA programs that rely on cloud hosting.
At a Glance
What It Does
The bill bars the Commerce Secretary from ending a cloud-storage contract for any NOAA dataset unless the Secretary has prepared a plan to keep the data accessible during a provider transition and has worked with the NOAA Administrator to protect that data. It borrows the statutory definition of 'cloud service provider' from 6 U.S.C. 650.
Who It Affects
The provision directly touches Department of Commerce procurement officials, NOAA program offices that operate or rely on cloud-hosted datasets (satellite, observational, modeling, and reporting systems), and cloud service providers that contract with Commerce or NOAA. Indirectly it affects researchers, state partners, and downstream system integrators that consume NOAA data feeds.
Why It Matters
The bill elevates continuity-of-access into statute rather than agency policy, forcing formal transition planning that can reduce data outages but also constrain procurement flexibility. Compliance officers and contract managers will need to incorporate transition and coordination steps into acquisition planning for NOAA data storage.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
At its core, the bill creates a statutory hurdle that procurement officials must clear before terminating a cloud-storage contract that contains NOAA datasets. Instead of ending a contract on schedule or for convenience without preparatory steps, the agency must first document how the data and any connected reporting systems will remain available during and after a move to another cloud provider.
That plan requirement shifts some operational responsibilities typically handled in acquisition transition work into a legal prerequisite.
Second, the statute requires active collaboration with the NOAA Administrator. Practically, that means program-level involvement: NOAA technical leads must be party to transition decisions, not merely notified.
The collaboration mandate is designed to make sure technical and scientific priorities — such as data integrity, metadata continuity, and timing with observational windows — shape any cancellation decision.The bill adopts the existing federal meaning of 'cloud service provider,' tying its scope to the DHS-derived definition at 6 U.S.C. 650. Because the text does not add thresholds based on dataset size, classification, or mission criticality, the rule appears broad: it applies to any NOAA dataset in cloud storage as defined by that cross-reference.
The lack of sequencing, deadlines, or explicit funding language, however, leaves many implementation choices to Commerce and NOAA: what a compliant plan must contain, who approves it, and how to resource simultaneous storage or data-transfer operations are not specified.Operationally, agencies will likely fold this requirement into acquisition planning documents and solicitations for cloud storage services: transition strategies, data egress arrangements, and runbooks for failover will become procurement artifacts. Cloud vendors and system integrators should prepare for more formalized requirements on portability and data-transfer support in future contracts with Commerce and NOAA.
Finally, because the statute speaks to uninterrupted storage and protection, program offices will need to reconcile this new requirement with existing Federal Records Act, National Archives, and classified-data handling obligations where applicable.
The Five Things You Need to Know
The bill prevents the Secretary of Commerce from ending a cloud-storage contract that holds any NOAA dataset unless two statutory prerequisites are met.
One prerequisite is a documented plan that ensures uninterrupted storage and specifically contemplates transition to a different cloud service provider and continuity for any linked reporting systems.
The other prerequisite is documented collaboration with the NOAA Administrator to protect the dataset during cancellation and transition.
The statute ties the phrase 'cloud service provider' to the definition in 6 U.S.C. 650 (Homeland Security Act section 2200), rather than creating a new federal definition.
The text contains no deadlines, enforcement penalties, funding authorization, or detailed content requirements for the required plan, leaving those choices to agency implementation.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This single-line provision names the measure the 'NOAA Data Preservation Act.' It contains no operative content but frames the bill’s purpose for statutory references and codification.
Limit on cancelling cloud-storage contracts for NOAA datasets
Subsection (a) creates the substantive constraint: the Secretary of Commerce 'may not cancel' a cloud-storage contract containing a NOAA dataset unless the statutory conditions in subsection (b) are satisfied. Technically this operates as a prohibition on unilateral contract termination tied to a legal prerequisite, rather than as a grant of affirmative authority. Contracting officers will need to assess whether their planned terminations meet those prerequisites before executing a cancellation.
Requirement to develop an uninterrupted-storage transition plan
Paragraph (1) requires a plan that ensures uninterrupted storage and explicitly contemplates transition to a different cloud provider, including any associated reporting systems. The provision does not define plan contents, approval authority, acceptable technical measures (e.g., dual-write, replication, or scheduled cutovers), or verification standards. Practically, agencies will need to decide whether to require cold/hot backups, egress bandwidth commitments from suppliers, and testing milestones to demonstrate continuity.
Collaboration with the NOAA Administrator
Paragraph (2) mandates collaboration with the NOAA Administrator 'to ensure the uninterrupted protection' of the dataset. That language elevates NOAA’s programmatic role in procurement decisions about storage continuity and data protection. Implementation will require procedures for how NOAA program managers review and sign off on transition plans, potentially creating a parallel approval stream outside standard contracting sign-off.
Definition of cloud service provider
Subsection (c) imports the definition of 'cloud service provider' from section 2200 of the Homeland Security Act (6 U.S.C. 650). By doing so, the bill adopts existing federal terminology and scope, which includes commercial and noncommercial providers as described in that statute and accompanying DHS guidance. That choice reduces definitional ambiguity but ties applicability to any future legal changes to that cross-referenced definition.
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 program offices and data stewards — They gain a statutory backstop preventing abrupt contract terminations that could interrupt data streams, giving them leverage to require thorough transition planning and continuity safeguards.
- Research institutions and downstream data users — The mandate for uninterrupted storage reduces the likelihood of service interruptions that can disrupt long-running climate analyses, model runs, and operational decision-making.
- Cloud service providers currently hosting NOAA data — The prohibition raises the bar for abrupt terminations, which can preserve existing revenue streams and create demand for professional services to execute planned transitions.
Who Bears the Cost
- Department of Commerce contracting offices — They must incorporate plan development and NOAA collaboration into termination procedures, increasing pre-termination administrative burden and potentially delaying contract actions.
- Taxpayers/federal budget — Ensuring uninterrupted access during transitions can require parallel hosting, data replication, or paid egress and migration services, which raise near-term costs that the bill does not separately fund.
- System integrators and new cloud vendors — The requirement to support documented transitions (including reporting systems continuity) imposes technical and contractual obligations — and potential liabilities — that may increase bid prices or complicate migrations.
Key Issues
The Core Tension
The central dilemma is continuity versus procurement agility: the bill protects scientific and operational users from data outages by legally enforcing transition planning, but that protection imposes cost, administrative delay, and reduced flexibility on contracting authorities — a trade-off between safeguarding mission-critical data and preserving the government's ability to reprocure services efficiently and cheaply.
The bill solves the narrow problem of abrupt data unavailability by making transition planning a legal prerequisite to contract cancellation, but it leaves crucial implementation details unspecified. There is no statutory content standard for the required plan — no checklist of minimum technical measures (replication, failover testing, egress bandwidth guarantees), no timeline for completing transitions, and no designated approver beyond the vague instruction to 'collaborate' with the NOAA Administrator.
That ambiguity hands significant discretion to Commerce and NOAA but also creates operational risk: inconsistent standards across programs could produce uneven protections for different datasets.
Another practical friction is the cost of continuity. The bill assumes agencies can ensure uninterrupted access during provider changes, but simultaneous hosting or expedited data egress often requires material funding and vendor cooperation.
Because the statute contains no funding authorization or direction to adjust acquisition budgets, offices will need to reallocate funds or accept slower procurement timelines. Finally, the statute relies on the DHS-derived definition of 'cloud service provider,' which secures definitional clarity but also subjects the provision to any future shifts in that cross-reference — for example, if DHS updates its guidance, the bill’s scope may expand or contract without congressional action.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.