Draft-SOW PDS ADN.pdf

Draft Statement of Work The Atmospheres Discipline Node of the Planetary Data System

March 2026

1.0 Background

The Planetary Data System (PDS) is one of the most important means by which the Planetary Science Division (PSD) ensures compliance with data-related Federal laws (such as Title II of H.R.4174 Foundations for Evidence-Based Policymaking Act of 2018, the “Open Government Data Act,” and the Federal Records Act), Executive Orders, and NASA directives and requirements. Specifically, the PDS is the NASA-funded system that achieves science data archival, long-term preservation, distribution, and search for PSD-funded planetary mission data and Exploration Science Strategy Integration Office (ESSIO)-funded lunar mission data. These efforts enable innovative science that aims to understand the solar system's history and the distribution of life within it, and to enable future human exploration.

The PDS is the principal means by which the PSD accomplishes the necessary planning, validating, peer-review, archiving, long-term preservation, and public distribution of data from PSD-funded missions, programs, and scientific investigations. The PDS maintains close coordination with NASA-funded mission instrument teams (funded by both PSD and ESSIO) throughout the mission lifecycle to ensure receipt of peer-reviewed and NASA-compliant data bundles and necessary ancillary information. Though the PDS does not lead the production of archive data from active missions, it works closely with project teams to ensure the design of well-engineered products that can be released quickly. PDS-curated products are freely available online, and the PDS provides teams of scientists to support users in selecting and understanding the data. PDS teams have traditionally existed as private organizations participating in a federated data system, and data are archived by scientist-led organizations- or Discipline Nodes.

The PDS as a system of Discipline Nodes ensures the long-term secure preservation of NASA planetary science data and maintains its usability. Discipline Node work includes performing the function of a Federal information system (40 USC 11331) including compliance with Federal cybersecurity laws (e.g., FISMA, FITARA) and related NASA cybersecurity directives and requirements. Though not an exhaustive list, at a high level this includes the requirements in (FIPS 200) and the security controls in NIST (SP 800-53 rev. 5 ) (See 44 USC 3554 (a)(1)(A)).

The PDS provides services that enable finding and accessing NASA planetary mission data, as well as developing, deploying, and maintaining software tools and models to aid in data discovery and analysis. The PDS system of Discipline Nodes engages in standards development and supports the NASA planetary community in the application and implementation of standards that ensure better access, interoperability, and usability of mission and instrument observations, models, software, and ancillary NASA planetary science data. This work accelerates the time to science and enables cutting-edge science in accordance with the 2022 NASA Authorization Act SEC. 10821 and 10822. In addition, this work helps maximize the investments of the US Government and the scientific return from the space missions consistent with the Planetary Science Decadal Survey Origins, Worlds, and Life and the strategy for planetary science exploration embodied in NASA’s Science Strategy. This work ensures US preeminence in space exploration and scientific excellence and is directly responsive to Executive Order 14369 Ensuring American Space Superiority.

CLIN 1

2.0 Scope and Requirements

The Discipline Nodes of the Planetary Data System (PDS) cooperate “To make planetary mission data available to the public and remain in compliance with Title II of H.R.4174 - Foundations for Evidence-Based Policymaking Act of 2018, the “Open Government Data Act.” The work to be performed under this contract continues, but further expands upon, the work that has been conducted by the Atmospheres Discipline Node (ATM) of the Planetary Data System (PDS) at New Mexico State University (NMSU).

2.1 The ATM Discipline Node of the PDS must continue to provide science data services:

2.1.1 Planetary Science Mission Support

• Ingest non-imaging atmospheric data from currently observing planetary missions (excluding Earth observations) and research scientists, supporting ground-based observations, and planetary analog laboratory and field measurements.

• Validate data submissions, organize and perform peer-reviews of new data archives, and designate DOIs (Digital Object Identifiers) for datasets.

• Provide expertise to guide and assist missions, instrument teams, programs, and individuals to organize and document digital data, and to help ensure high quality data submissions to the repository. Expertise activities include, but are not limited to providing:

o A letter of support from the PDS Discipline Node for NASA ROSES proposals for research data sets seeking to be archived in the PDS, as long as the proposed data set(s) intend to be developed to meet PDS archival standards.

o New spacecraft mission support, which will commence with a letter of support during the proposal process, including the identification of anticipated data product types, volumes, and a delivery schedule aligning to NASA’s Science Information Policy.

o Support by the PDS Discipline Node to any current spacecraft mission or approved research dataset, or once a new NASA spacecraft mission or research data set is approved, and PDS Node participation is directed and funded. This support by the PDS Node must continue throughout the mission lifecycle through close out as directed by NASA. Major activities include, but are not limited to:

Providing expertise and support aligned to existing mission legacy

Science Data Management Plans (SDMP);

Providing expertise and support for the development of new mission Open Science and Data Management Plans (OSDMP);

Providing expertise and support to data providers to meet PDS standards during Data Generation;

Providing interface expertise as needed to achieve ingest, archival, and preservation of mission data sets;

Providing stewardship, discovery, access, and distribution of mission data sets;

Conducting final archival activities at spacecraft mission close out per mission Program Level Requirements Appendix (PLRA) and SDMP or OSDMP.

2.1.2 Essential Data Archival, Preservation, Discovery, Distribution and Data Usage

Services

• Implement NASA PDS Level 3 and 4 requirements, tracing to higher-level NASA requirements provided in Attachment I.

• Ensure the long-term preservation of the planetary data archive by providing an authoritative copy of data holdings to the NASA Space Science Data Coordinated Archive (NSSDCA) for permanent deep archive.

o The Discipline Node must coordinate with the PDS Project Office, the Engineering Node, and the NSSDCA to maintain a list, updated quarterly, of all data holdings that have successfully completed deep archival with the NSSDCA.

o The Discipline Node must maintain a schedule of upcoming data for deep archival to the NSSDCA at minimum 6 months in advance of planned delivery to the NSSDCA.

• Ensure data are made publicly available.

o Enable data accessibility to users in a manner compliant with Section 508 of the Rehabilitation Act.

o Publicly available data must be secured against natural disasters, unauthorized access, and modification. This must be achieved either through migration to the NASA-managed cloud environment, or when data reside on on-premises systems, then such systems must achieve and maintain compliance with NASA SMD cybersecurity standards on the timeline outlined in Section 3.

o Interruptions to public data access on Discipline Node-managed systems must be actively minimized and must not exceed 14 calendar days per instance.

A quarterly report shall be submitted listing downtimes by issue and includes impacted data holdings, affected systems and hardware, and resolution actions taken.

• Maintain tools to assist data providers in assembling, validating, and submitting archival products. During the cloud migration process within this period of performance, these tools must be maintained both on-premises and in the NASA-managed cloud environment.

o A listing of Discipline Node-maintained tools must be provided to the PDS Project Office within 60 days from the contract effective date and updated annually.

• Maintain documentation, user guides, and training modules for data providers.

During the cloud migration process, this information must be maintained and developed both for on-premises and cloud data submission and access.

o A listing of Discipline Node documentation, user guides, and training modules must be provided to the PDS Project Office within 60 days of the contract effective date and updated annually.

• Maintain value-added services to aid in searching and discovering archive products. Such services include catalog search tools, data visualization tools, and Application Programming Interface (API) data access. During cloud migration, these services must be maintained both on-premises and in the NASA-managed cloud environment.

o A listing of Discipline Node search and discovery services must be provided to the PDS Project Office within 60 days of the contract effective date and updated annually.

2.1.3 Standards and Documentation

• Maintain archiving standards for PDS data and ensure interoperability with NASA, Science Mission Directorate (SMD), and PSD Data Services Program standards.

• Maintain PDS4 Local Language Dictionaries (LDD) and data system APIs.

2.1.4 Working Groups

• Support the NASA Science Mission Directorate and Planetary Science Division’s data management activities through active participation in PDS working groups, communities of practice, and the PDS Management Council, including but not limited to, discussion and adoption of data and metadata standards and best practices, data governance policies, cloud migration planning activities, enterprise-level software, tools, high-end computing, Artificial Intelligence implementation, and enterprise-level systems engineering deployments, as well as coordination and planning in support of planetary community meetings.

o Participation shall be reported quarterly.

o Active participation by at least one Discipline Node representative in the cloud community of practice is mandatory.

o Active participation is defined as attendance of at least 70% of meetings.

It is expected that attendees will contribute to discussions and provide responses to data calls as necessary to advance the aims of the group.

• Annual in-person attendance of at least one Discipline Node representative at a minimum of one SMD-sponsored data repository meeting, workshop, or working group meeting during the period of performance.

• Submission of responses to all SMD-mandated and PSD-mandated data calls.

2.1.4.1 PDS Management Council Participation Expectation

The PDS Management Council meets monthly. Approximately 10 meetings per year are anticipated to be virtual, and two are anticipated to be in-person with hybrid participation facilitated. Virtual monthly meetings average up to two hours in length. Longer meetings are held approximately quarterly and include opportunities for technical sessions and working group coordination. NASA may determine to hold a planned in-person meeting virtually, or to cancel outright, in the event circumstances surrounding meeting attendance violate NASA policies, safety guidelines, or federal law. Discipline Nodes are expected to actively participate in all meetings. Cadance:

o Annual participation in up to 8 monthly virtual PDS Management Council Meetings, approximately two hours in length.

o Annual participation in at least 2 multi-day virtual PDS Management Council Meetings.

o Annual participation by up to 5 node personnel in up to 2 multi-day in-person PDS Management Council Meetings.

2.1.4.2 Expectation to Host a PDS Management Council Meeting

o In coordination with the PDS Project Office, host one in-person PDS

Management Council meeting during the Period of Performance.

2.1.5 Adherence to the PDS Code of Conduct

• Any violations must be reported in writing within 5 business days to the PDS Project Office, the COR, and the Contracting Officer.

2.2 In support of PDS enterprise modernization for efficient operation the ATM Discipline Node of the PDS must:

2.2.1 Data Holding Registration in the PDS Registry

• Complete the PDS Registry with documentation of all datasets in the Discipline Node’s stewardship within one year of contract effective date.

• Update the PDS Registry as any new datasets are added to the Discipline Node’s stewardship.

• Report updates to the PDS Registry quarterly.

2.2.2 Data Holding Conversion to PDS4

• Complete conversion of all Discipline Node planetary data holdings as defined in the PDS Registry to the NASA-led international planetary data standard and data model (i.e., PDS4), so that all planetary data is discoverable and interoperable. The conversion schedule shall be coordinated with the PDS Project Office, applicable mission teams, and progress reported quarterly.

o Exceptions to PDS3 to PDS4 conversion may only be granted by written request with compelling justification, and approved as deemed necessary, by the NASA Planetary Science Division Data Services program.

2.2.3 Cloud Migration

• Complete the migration of all Discipline Node data holdings as defined in the PDS Registry from on-premises systems at external institution(s) to the NASA-managed cloud environment. This includes the migration of essential data archive, validation, delivery and discovery services and capabilities from on-premises systems to the NASA-managed cloud environment in an open-source manner.

o Collaborate with the NASA-provided services of the PDS Project Office and the PDS Engineering Node to identify mission and research data, derived products, Discipline Node-developed software, tools, models, necessary workflows, and processes that must be migrated to the NASA-managed cloud environment to facilitate cloud-based Discipline Node operations. This includes any work necessary to co-develop, implement, and deploy cloud migration technologies.

Collaboration specifically includes co-developing an approved cloud migration schedule against which progress must be reported quarterly.

o Migrate a singular authoritative copy of each dataset in its holdings, as well as any software, models, tools, or services created and maintained by the node for the use of these datasets, to the NASA-managed cloud environment.

o Maintain the authoritative copy of each dataset in its holdings, as well as any software, models, tools, or services created and maintained by the node for the use of these datasets, on the NASA-managed cloud environment.

o Migrate value-added services (per the listing in section 2.1.2.) to the NASA-managed cloud environment that aid in search and discovery of archive products. This includes, but is not limited to, catalog search tools, data visualization, and API data access.

o Exceptions to cloud migration of Discipline Node data holdings may only be granted by written request with compelling justification, and approved as deemed necessary, by the NASA Planetary Science Division Data Services program.

2.2.4 Mission Data Pipeline Evolution

• Support the PDS-enterprise development of mission data delivery and validation pipelines in the cloud, including enabling and instructing planetary missions currently in operation how to deliver data to the PDS in the NASA-managed cloud environment and in collaboration with NASA HQ, as mission resources permit.

o It is anticipated that the Discipline Node will facilitate mission adoption of any direct-to-cloud data delivery pipeline developed by the PDS enterprise that is ready for mission use. However, the Discipline Node may propose to co-develop such cloud delivery and validation pipelines but must rely on NASA-provided platforms, enterprise-level systems engineering, and enterprise deployment technologies and expertise.

2.2.5 PDS Sub-Nodes

• Develop and submit plans for approval to the PDS Project Office within 180 days of contract effective date, and report progress against approved plans quarterly, for the complete transition of any work being performed by any sub-nodes receiving PDS funding directly into the capabilities of the Discipline Node by the end of the Period of Performance.

o Discipline Node requests for limited sub-contracting will be considered on a case-by-case basis and may be permissible at the discretion of the Contracting Officer.

• Ensure any and all subcontractors adhere to the limitations on government-furnished equipment and government-furnished information in this contract.

2.2.6 Enterprise Efficiency and Training

• Collaborate with the NASA-provided services of the PDS Project Office, other

PDS Discipline Nodes, and the PDS Engineering Node to identify and document a list of software, tools, models, workflows, or processes that can be combined (internally or externally) or decommissioned to enable increased PDS enterprise efficiency for the benefit of the planetary science community. The list shall be submitted to the PDS Project Office within 1 year of the effective contract date and updated annually.

• Support the Discipline Node’s user community to transition to the use of newly available, updated, or combined PDS-provided software, tools, models, workflows, or services, including cloud enterprise offerings.

o The Discipline Node must provide training materials and provide in-person support for an annual PDS-led user community meeting, which will be coordinated by the PDS Project Office. Up to 5 Discipline Node personnel may attend in person.

o The Discipline Node must collaborate with the PDS Project Office and any NASA-provided service contractors to support the development of training materials for PDS-provided offerings relevant to the Discipline Node’s user community.

o Support for up to two in-person training events at community meetings per year is limited to support materials valued at up to $5,000 per meeting as well as domestic travel expenses for up to 5 node personnel, per meeting.

The Discipline Node must abide by the NASA policies for SMD-funded Science Events in the Science Information Policy.

• All developed training materials become the property of

NASA and must be delivered to the PDS Project Office to be made publicly available.

Within 30 days of the conclusion of a training event, a training report shall be submitted to the PDS Project Office which includes, at a minimum, the final agenda, the number and mode of participants, high-level summary of outcomes, and participant feedback.

2.2.7 Cybersecurity

• Accomplish cybersecurity compliance activities as required by SMD for any data, tools, or services that are accessed using on-premises systems.

o Utilize the services and leadership provided by the PDS Project Office, PDS Engineering Node, and the SMD Office of the Chief Science Data Officer’s Science Cloud Infrastructure Project (SCIP), to ensure Discipline Node holdings comply with the NASA-managed cybersecurity System Security Plans (SSPs) for both cloud holdings and any on-premises systems and holdings. This includes providing Discipline Node-specific cybersecurity support to annual cybersecurity self-audits, permitting access for external audits necessary to maintain Authorization To Operate (ATO), as well as completion of compliance activities and documentation to support SSP ATO reviews.

o Deliver a cybersecurity compliance plan for all cybersecurity requirement clauses of this contract to the PDS Project Office within 30 days of contract effective date.

Delivery must include a schedule.

Reporting against the plan must occur quarterly after approval.

o Maintain current Interconnectivity Security Agreements (ISA’s) for connections between on-premises systems and NASA-managed systems.

o As necessary, assist the PDS Project Office and the PDS Engineering Node with the timely migration of any PDS ISAs from the current SSP 3278 to another NASA-managed SSP.

o For on-premises systems, achieve full compliance with the SMD-identified initial list of minimum Federal and NASA cybersecurity controls by the end of the first year of this period of performance (see Appendix II.). Compliance activities shall be reported quarterly in year 1.

o For on-premises systems, achieve full compliance with the SMD-required FIPS199 “low” Federal and NASA cybersecurity controls by 90 days prior to the end of this period of performance (see Appendix III.). Compliance activities shall be reported quarterly in year 2 and year 3.

2.2.8 Online Presence

• Work with the NASA-provided PDS Project Office and the PDS Engineering Node or other contractors to develop and execute a plan to transition the Discipline Node web presence and dataset access from institution-managed websites, servers, and infrastructure to NASA-managed PDS websites, servers, and infrastructure.

o The Discipline Node must participate in planning the transition schedule and activities, must assist in executing the transition, and must manage the former website during the transition phase.

o The Discipline Node must submit the web presence and data access transition plan and schedule within 180 days of contract effective date.

Reporting against the plan must occur quarterly after approval.

o After NASA has declared the transition complete, the Discipline Node must maintain the former site and redirect the user to the new site for up to 1 year.

o Decommissioning activities must begin for any obsolete infrastructure at 180 days after the migration has completed, or no later than 30 days before the end of the period of performance, whichever occurs first.

Documentation of decommissioning activities performed, and a list of decommissioned hardware must be submitted to the PDS Project Office quarterly after transition plan approval.

2.2.9 Metrics and Reporting

• Provide quarterly reporting, metrics and artifacts for tracking progress against deliverables, including cloud migration progress, dataset conversion to PDS4, web presence transition to the NASA-provided website infrastructure. These definitions for each must be used in reporting progress.

• Metrics include, but are not limited to, the following:

o Total Number of NASA datasets under stewardship o Total Volume of NASA mission datasets under stewardship o Total Volume of NASA investigator datasets under stewardship o Total Non-NASA dataset volume o Total data volume on-premises o Total outside-facing data volume on-premises o Total number of bundles o Total number of collections: Updated version o Total number of collections: All versions o Total number of bundles not in the registry o Total number of collections not in the registry: Updated version o Total number of collections not in the registry: All versions o Total number of pre-PDS4 datasets o Total size of pre-PDS4 datasets o Letters of support provided o Help requests addressed o Peer reviews completed o Number of datasets in PDS3 format o Number of datasets in PDS4 format o Number of datasets with a DOI o Number of datasets migrated to the NASA-provided cloud o Number of datasets with API access o Number of unique user IPs accessing on-premises holdings o Data access volume o Data download volume

• Provide annual supporting budget information requested by the PDS Project Office and NASA HQ to the annual NASA Programming, Planning, Budget, and Execution (PPBE) process.

critical controls listed in Appendix II Report on cybersecurity compliance against critical controls listed in Appendix III

2.2.7 Quarterly in year 2 and

year 3

Discipline Node web presence and data access transition plan; status reporting

2.2.8 Within 180 days of

contract effective date;

quarterly updates after transition plan is approved

List of decommissioned PDS support on-premises hardware

2.2.8 Quarterly updates after

transition plan is approved

Metrics and Reporting 2.2.9 Quarterly Transition plan for any system not owned and maintained by NASA funding but that is necessary for the performance of work on the contract; status reporting

4.0 Within 180 days of

contract effective date;

quarterly updates after plan is approved

Identification of any purchased hardware, date of registration with NASA, and associated NASA asset tag number

4.0 Within 30 days of

purchase

4.0 Government-Furnished Equipment and Government-Furnished Information

• GFE: Personnel of the Atmospheres Discipline Node (ATM) of the Planetary Data System (PDS) will be provided with NASA computers, but only for full-time PDS Node staff. No other Government-furnished equipment (GPE) will be provided. ATM has used past NASA funding under prior cooperative agreements to purchase and maintain on-premises servers where NASA planetary science mission and research data currently reside.

• GFI: No specific Government-furnished information (GFI) is required at the outset of the contract to perform duties according to the tasks set forth in this statement of work. However, over the course of the performance of this work, the ATM Discipline Node is expected to receive new scientific data from NASA missions and NASA-sponsored research efforts, as well as generate its own data and metadata, ancillary and auxiliary products from that received data, and will be expected to perform tasks under this contract that facilitate the ingest, archival, permanent deep-archive, access, distribution, and use of such data and associated data products. The ATM Discipline Node may also receive and generate new software, models, tools, services, and other scientific information and will be expected to perform tasks under this contract to facilitate its use.

• Limitations: The ATM Discipline Node of the PDS may only purchase new equipment identified as necessary for the performance of the tasks in this statement of work and may only use NASA funding. Funding from any other source is prohibited for the acquisition of new equipment necessary to fulfill the requirements of this effort.

o Any equipment purchased with NASA funding provided under this effort is government property and must solely be used for the express purpose of performance of work on this contract.

o Such property must be registered as a NASA asset and must be maintained in compliance with NASA cybersecurity standards.

o Any system that is not owned and maintained by NASA funding but that is necessary to the performance of the work of the Discipline Node must be identified and a transition plan for such systems must be submitted to the PDS Project Office which identifies dates to sunset the equipment and transition any NASA-owned data, software, models, tools, information, or services from that hardware to identified NASA-owned systems.

CLIN 2

Indefinite Delivery, Indefinite Quantity (IDIQ)

The Atmospheres Discipline Node must provide, at the request of NASA, any major planetary science mission support outside of the normal routine support to currently operating and known or planned planetary mission activities, covered in the Core contract through dialogue with NASA and utilizing the Indefinite Delivery Indefinite Quantity (IDIQ) Task/Delivery Order Mechanism. This includes, but is not limited to, the ingest of non-imaging atmospheric data from new planetary missions and research scientists, validation of data submissions, conduct of peer-reviews of new data archives, and designation of DOIs, as well as the provision of expertise to guide and assist new missions, instrument teams, programs, and payloads to ensure high quality data submissions to the NASA repository.

The Atmospheres Discipline Node must provide, at the request of NASA, any non-imaging atmospheric data archival, preservation, discovery, distribution, and data usage services for any new missions, instrument teams, programs, or payloads outside of the normal routine support to currently operating and known or planned planetary mission activities, covered in the Core contract. This includes, but is not limited to, the migration of value-added services to the NASA-managed cloud environment, that are not supportable under the Core contract.

The Atmospheres Discipline Node must provide, at the request of NASA, any non-imaging atmospheric data management services outside of the normal routine data management services covered in the Core contract. This includes, but is not limited to, enhanced data archival, or data reduction pipeline activities not included in the baseline activities, such upgrades to archiving activities, upgrades to access management, or additions of or upgrades to data reduction pipelines.

The Atmospheres Discipline Node must provide, at the request of NASA, PDS-relevant new mission, instrument, program, or payload interface non-imaging atmospheric activities outside of the normal routine mission support interfaces covered in the Core contract. This includes, but is not limited to, materials, personnel, or travel to support new planetary mission needs for NASA.

Place of Performance

• New Mexico State University (NMSU) will be the physical location of the work to be performed by the Atmospheres Discipline Node (ATM) of the PDS.

Efficient numbers of ATM staff must also be expected to travel to the sites of other PDS Discipline or Engineering Nodes, NASA GSFC where the PDS Project Office resides, NASA HQ, or other locations as directed by the NASA HQ Data Service Program to participate in work planning, collaboration, and PDS-specific meetings and to participate in conferences and community meetings approved by the Planetary Science Division’s Data Services Program.

Period of Performance

• The period of performance for this effort must commence on December 1, 2026 and must end on November 30, 2029.