Atmosphere Discipline Node

Statement of Work (SOW) / Performance Work Statement (PWS)

This Statement of Work (SOW) outlines the requirements for the Atmospheres Discipline Node (ATM) of the Planetary Data System (PDS) to provide science data services. The primary goal is to ensure compliance with data-related Federal laws and NASA directives, enabling innovative science and future human exploration by managing NASA-funded planetary mission data.

• Planetary Science Mission Support: Ingest, validate, and archive non-imaging atmospheric data from ongoing and new planetary missions and research scientists. This includes peer-reviews, designation of Digital Object Identifiers (DOIs), and providing expertise to missions and instrument teams for high-quality data submissions.

• Essential Data Archival, Preservation, Discovery, Distribution, and Data Usage Services: Ensure long-term preservation of planetary data by providing authoritative copies to the NASA Space Science Data Coordinated Archive (NSSDCA). This involves coordinating with PDS Project Office and NSSDCA, maintaining an upcoming data schedule, and ensuring public data accessibility in compliance with Section 508 of the Rehabilitation Act. Data must be secured against unauthorized access and modification.

• Standards and Documentation: Maintain archiving standards for PDS data and ensure interoperability with NASA standards. Maintain PDS4 Local Language Dictionaries (LDD) and data system APIs.

• Working Groups: Support NASA Science Mission Directorate and Planetary Science Division data management activities through active participation in PDS working groups and the PDS Management Council.

• Enterprise Modernization: Support PDS enterprise modernization by registering data holdings, converting data to PDS4 standard, migrating data and services to a NASA-managed cloud environment, and evolving mission data pipelines.

• Cybersecurity: Accomplish cybersecurity compliance activities as required by SMD for data, tools, and services, including developing and delivering cybersecurity compliance plans and maintaining Interconnectivity Security Agreements (ISAs).

• Online Presence: Transition the Discipline Node web presence and dataset access from institution-managed infrastructure to NASA-managed infrastructure.

• Quarterly reporting on deliverables, including cloud migration progress, dataset conversion to PDS4, and web presence transition.

• Metrics include total number of datasets, data volume, number of bundles/collections, datasets in PDS3/PDS4 format, datasets with DOI, datasets migrated to cloud, user access, and data download volume.

• Annual reporting of budget information for NASA Programming, Planning, Budget, and Execution (PPBE) process.

• Period of Performance: December 1, 2026, to November 30, 2029.

• Place of Performance: New Mexico State University (NMSU), with potential travel to other PDS nodes, NASA GSFC, and NASA HQ.

• Government-Furnished Equipment (GFE): NASA computers will be provided for full-time PDS Node staff.

• Government-Furnished Information (GFI): No specific GFI is required at the outset, but the node will receive and process new scientific data from NASA missions and research efforts.

• Limitations: Only NASA funding can be used for purchasing necessary new equipment, which becomes government property.

• Cloud Migration: All data holdings and services must be migrated to the NASA-managed cloud environment. Exceptions require written justification and approval.

• IDIQ Task/Delivery Order Mechanism: Support for major planetary science mission activities outside of normal routine support will be handled via this mechanism.

Statement of Work (SOW) / Performance Work Statement (PWS)

This document outlines the Level 1 and Level 2 requirements for the Planetary Data System (PDS), aiming to support NASA's goals in planetary science and solar system exploration by organizing, documenting, and archiving digital data.

• Data Provision and Support: Provide expertise to guide missions, programs, and individuals in organizing and documenting digital data for archival. This includes establishing a single point of contact, offering expert help in designing archival data sets, assisting with archive plans, interface documents, validation procedures, and delivery schedules.

• Archiving Standards and Tools: Establish and maintain archiving standards for NASA planetary science data, and provide tools for data producers to assemble, validate, and submit archival products.

• Data Collection and Management: Collect, validate, and peer review organized and well-documented data into archives. This involves soliciting comprehensive archives, receiving and tracking submissions, validating compliance with standards, conducting peer reviews for completeness and accuracy, accepting or rejecting data, and maintaining a catalog of accepted data sets.

• Storage and Architecture: Provide appropriate storage for the archive and maintain a distributed architecture based on scientific expertise.

• Accessibility and User Services: Make data accessible to users, supporting searches, facilitating data retrieval and distribution, and providing value-added services.

• Long-Term Preservation and Usability: Ensure the long-term preservation and usability of data by setting and implementing requirements.

• Project Management: Manage the PDS as a NASA project, adhering to NPR 7120.8A, ensuring core project management functions (technical, cost, schedule, risk, procurement, configuration management), and maintaining cybersecurity compliance.

• The PDS Project Office shall maintain standards for PDS Metrics and reporting.

• The PDS Project Office shall own and maintain the Level 2 requirements of the PDS.

Not explicitly stated in this document, but implies ongoing operations and management of NASA's planetary data.

• Adherence to applicable federal statutes, NASA policies, and Memoranda of Understanding.
• Following best practices in system and software engineering.
• Transition of the online presence to a NASA-managed web environment.
• Overseeing the selection or designation of a lead node for mission interaction.

Form / Attachment / Pricing Sheet

This document appears to be a detailed control catalog or matrix, likely used for compliance and security management within a federal agency. It outlines various security and privacy controls (e.g., CA-05, CA-06, IA-02, PL-04, RA-02, SC-08, SI-02) with their respective control statements, discussions, related controls, and references to NIST publications and other federal regulations.

• Control Identifier: Unique codes for each control (e.g., CA-05).
• Control Name: Descriptive name of the control (e.g., PLAN OF ACTION AND MILESTONES).
• Control Statement: The specific requirement or action mandated by the control.
• Discussion: Explanations and context for the control's implementation and importance.
• Related Controls: Cross-references to other controls that are linked or complementary.
• References: Citations to relevant NIST Special Publications (SP), Federal Information Processing Standards (FIPS), Office of Management and Budget (OMB) circulars, and other authoritative documents.

While not a solicitation or SOW, this document is highly relevant for bidders who are required to comply with specific government security and privacy standards. It provides insight into the expected security posture and compliance requirements that may be imposed on systems or services being offered. Bidders should review this document to understand the baseline security controls and regulatory frameworks that may apply to their proposed solutions, particularly if the opportunity involves IT systems, data handling, or cybersecurity services. Understanding these requirements can inform proposal development and ensure compliance with government mandates.

Form / Attachment / Pricing Sheet

This document, NASA-SPEC-2661.Controls v2.0, is a NASA Technical Specification that defines information technology (IT) and operational technology (OT) security control baselines for NASA information systems. It outlines federally mandated critical controls, NASA critical controls, and specific controls for High-Value Asset (HVA) systems, systems with export-controlled data, and systems with artificial intelligence (AI) components.

• Scope: Defines IT and OT security control baselines, including federally mandated controls, NASA critical controls, and controls for specialized systems (HVA, export-controlled data, AI).
• Applicability: Applies to all NASA systems, projects, programs, and activities, including contractors and recipients of grants/agreements.
• Tailoring: Requirements for control selection are detailed in ITS-HBK-AASTEP2, Step 2: Select Policy.
• Authority: Established by NASA CIO and SAISO via the Agency Security Configuration Standards (ASCS) initiative.
• Applicable Documents: Lists relevant government, NASA, and NIST documents that constitute requirements for this specification.
• Acronyms, Abbreviations, and Definitions: Provides definitions for terms used throughout the document.
• Control Overlay Highlights: Summarizes control categories including Federally Mandated Critical Controls, NASA Critical Controls, NASA Critical Controls for High-Value Asset Systems, NASA Critical Controls for Systems with Export-Controlled Data, and NASA Baseline Requirements and Critical Controls for Systems with AI Components.
• NASA Control Baselines: Details specific control baselines (e.g., CA-05, AC-01, RA-02) and their applicability across IT and OT, with different security categorization levels (Low, Moderate, High).
• Appendix A: Lists Federally Mandated Critical Controls Supporting Documents.

This document is crucial for bidders as it specifies the cybersecurity control baselines and requirements that NASA information systems must adhere to. Understanding these controls is essential for developing compliant proposals, designing secure systems, and ensuring successful contract performance, particularly for IT and OT security aspects. It provides a detailed framework for cybersecurity requirements that may be incorporated into solicitations and contracts.