Asteroids and Dust Subnode

Form / Attachment / Pricing Sheet

This document outlines the Level 1 and Level 2 requirements for the Planetary Data System (PDS). It details the functions and responsibilities of the PDS in supporting NASA's planetary science and solar system exploration goals through data archiving, management, and accessibility.

• Data Provision: Expertise to guide missions in organizing and documenting digital data.
• Single Point of Contact: Providing a central contact for data providers.
• Archiving Standards & Tools: Establishing and maintaining standards, and providing tools for data assembly, validation, and submission.
• Data Collection & Peer Review: Collecting, validating, and peer-reviewing data submissions.
• Accessibility & Preservation: Ensuring data is accessible to users and preserved for the long term, maintaining usability.
• Management: Managed as a NASA project subject to specific NPRs, including project management functions and cybersecurity compliance.
• Level 2 Requirements: Ownership and maintenance of Level 2 requirements.

This document is crucial for potential bidders to understand the operational and technical requirements of the Planetary Data System. It defines the standards, processes, and management structures that govern the archiving and accessibility of NASA's planetary science data. Bidders involved in data management, archiving, or related services for NASA should review these requirements to assess their alignment with the PDS's objectives and operational framework.

Form / Attachment / Pricing Sheet

This document appears to be a checklist or matrix detailing various security and privacy controls, their identifiers, statements, discussions, and related references. It is likely intended as a reference or compliance document for information systems.

• Control Identifier: Unique codes for each control (e.g., CA-05, IA-02).
• Control Name: A descriptive name for the control (e.g., PLAN OF ACTION AND MILESTONES, IDENTIFICATION AND AUTHENTICATION).
• Control Statement: The specific requirement or action mandated by the control.
• Discussion: Explanations and context for the control.
• Related Controls: Cross-references to other relevant controls.
• Privacy Baseline, Security Baseline (Low, Moderate, High): Indicates the applicability of the control to different security and privacy baselines.
• References: Citations to relevant NIST publications, OMB circulars, and other standards.

Bidders may need to refer to this document to understand the specific security and privacy requirements that will be applied to the systems or services they are expected to provide. It outlines the compliance landscape and the expected standards for information security and privacy within the context of the opportunity. Understanding these controls is crucial for developing compliant proposals and ensuring successful contract performance.

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. It outlines federally mandated critical controls, NASA critical controls for various system types (High-Value Asset, export-controlled data, AI components), and NASA baseline requirements.

• Scope: Defines the purpose, applicability, tailoring, and authority for the specification.
• Applicable Documents: Lists relevant government and NIST documents.
• Acronyms, Abbreviations, and Definitions: Provides definitions for terms used throughout the specification.
• Control Overlay Highlights: Details specific 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: Presents comprehensive lists of IT and OT control baselines, categorized by system type and FIPS 199 security categorization.
• Appendix A: Lists Federally Mandated Critical Controls and their supporting documents.

This specification is crucial for any bidder proposing to provide IT or OT systems, services, functions, or processes to NASA. It establishes the mandatory cybersecurity control baselines and requirements that must be adhered to. Understanding these controls is essential for developing compliant proposals and ensuring successful contract performance. Bidders must ensure their proposed solutions meet or exceed these security standards.

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

This Statement of Work (SOW) outlines the requirements for the Asteroids and Dust subnode (SBN_PSI) of the Planetary Data System (PDS) to provide science data services. The primary goal is to ensure the long-term preservation, accessibility, and usability of NASA planetary science data, supporting scientific discovery and enabling future exploration.

• Planetary Science Mission Support: Ingest, validate, and archive asteroid and dust data from planetary missions and research scientists. Provide expertise for data documentation, DOI designation, and support for new and ongoing missions. This includes providing letters of support for NASA ROSES proposals and assisting with data product planning and delivery schedules.

• Data Archival, Preservation, Discovery, and Distribution: Implement NASA PDS Level 3 and 4 requirements, ensuring long-term preservation by providing data to the NASA Space Science Data Coordinated Archive (NSSDCA). Ensure data is publicly available, accessible (Section 508 compliant), and secured against disasters and unauthorized access. Minimize interruptions to public data access.

• Standards and Documentation: Maintain archiving standards for PDS data, ensure interoperability with NASA standards, and 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, communities of practice, and the PDS Management Council. This includes attending meetings, contributing to discussions, and participating in SMD-sponsored data repository meetings.

• Cloud Migration: Migrate all subnode data holdings, software, tools, and services to the NASA-managed cloud environment. This includes developing and implementing cloud migration technologies and maintaining authoritative copies of data and services in the cloud.

• Mission Data Pipeline Evolution: Support the development of cloud-based mission data delivery and validation pipelines, enabling missions to deliver data to the PDS cloud environment.

• Enterprise Efficiency and Training: Identify and document software, tools, and processes for PDS enterprise efficiency. Support the user community in transitioning to new PDS offerings and develop training materials.

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

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

• Annual reporting of supporting budget information.

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

• Place of Performance: Planetary Science Institute (PSI) will be the physical location of work. Travel to other PDS sites, NASA GSFC, and NASA HQ may be required.

• Compliance with Federal cybersecurity laws (e.g., FISMA, FITARA) and NASA cybersecurity directives.

• Adherence to the PDS Code of Conduct.

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

• Government-Furnished Information (GFI): No specific GFI is required at the outset, but new scientific data and related products will be received and processed.

• Limitations on purchasing new equipment and use of NASA funding.

• All equipment purchased with NASA funding is government property.

• Transition of any non-NASA funded systems to NASA-owned systems.

• Indefinite Delivery, Indefinite Quantity (IDIQ) for major planetary science mission support outside of routine support.