Appendix I - L1 and L2 Requirements of the PDS.pdf
PDF 35 KB Posted
- Attached to
- Atmosphere Discipline Node
- Solicitation number
- 80GSFC27PDSADN
About this file
This document is an appendix containing Level 1 and Level 2 requirements for the Planetary Data System (PDS), a NASA project responsible for organizing, archiving, and providing access to planetary science and solar system exploration data.
The PDS requirements are organized into five primary functional areas. First, PDS must provide expertise and guidance to missions, programs, and individuals submitting archival data, including designating a single point of contact, offering expert leadership in dataset design, assisting with archive planning and documentation, establishing archiving standards, and providing tools for data assembly and validation. Second, PDS must collect, validate, peer review, and maintain well-organized, scientifically credible data archives through solicitation, receipt, validation, peer review, acceptance or rejection decisions, cataloging, appropriate storage, and distributed architecture based on scientific expertise. Third, PDS must make archived data accessible through search and discovery capabilities, data retrieval and distribution services, and value-added user services. Fourth, PDS must ensure long-term preservation of data and maintain their usability through established preservation requirements and long-term usability procedures. Finally, PDS operations must comply with NASA Procedural Requirements (NPR) 7120.8A, with the PDS Project Office responsible for core project management functions including technical, cost, schedule, risk, procurement, and configuration management; NASA cybersecurity compliance; transition of PDS online presence to NASA-managed web environment; maintenance of PDS Metrics standards; ownership and maintenance of Level 2 requirements; and oversight of lead node selection to serve as a single point of contact for missions.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
APPENDIX 1
LEVEL 1 AND LEVEL 2 REQUIREMENTS OF THE PLANETARY DATA SYSTEM
1. PDS will provide expertise to guide and assist missions, programs, and individuals to organize and document digital data supporting NASA's goals in planetary science and solar system exploration.
1.1 Single Point of Contact: PDS will provide a single point of contact to each mission, program, agency, or individual (i.e., data providers) wishing to submit archival data.
1.2 Expert Help: PDS will provide expert leadership in designing archival data sets.
1.3 Plans and Documents: PDS will assist data providers in developing archive plans, interface documents, validation procedures, and delivery schedules for PDS approval.
1.4 Archiving Standards: PDS will establish and maintain archiving standards for NASA planetary science data.
1.5 Archiving Tools: PDS will have tools to assist data producers in assembling, validating, and submitting archival products.
2. PDS will collect suitably organized and well-documented data into archives that are peer reviewed and maintained by members of the scientific community.
2.1 Solicit: PDS will seek complete and comprehensive archives from data providers consistent with interests and resources available.
2.2 Receive: PDS will receive, acknowledge and track data submissions.
2.3 Validation: PDS will validate data submissions to ensure compliance with standards.
2.4 Peer Review: PDS will conduct peer reviews of all submissions of archival data to ensure completeness, accuracy, and scientific usability of content.
2.5 Acceptance: PDS will accept or reject submitted data.
2.6 Catalog: PDS will maintain a catalog of accepted archival data sets.
2.7 Storage: PDS will provide appropriate storage for its archive.
2.8 Architecture: PDS will maintain a distributed architecture based on scientific expertise.
2.9 External Controls: PDS will adhere to applicable federal statutes, NASA policies and Memoranda of Understanding with other organizations.
2.10 System Development and Operations: PDS will follow best practices in system and software engineering for developing and operating the system.
3. PDS will make these data accessible to users seeking to achieve NASA's goals for exploration and science.
3.1 Search and Discovery: PDS will allow and support searches of its archival holdings.
3.2 Data Retrieval and Distribution: PDS will facilitate transfers of its data to users.
3.3 User Services: PDS will provide value-added services to aid in using archive products.
4. PDS will ensure the long-term preservation of the data and maintain their usability.
4.1 Long-Term Preservation: PDS will set requirements for and ensure long-term preservation of the data.
4.2 Long-Term Usability: PDS will establish long-term usability requirements and implement procedures for meeting them.
5. The PDS shall be managed as a NASA project subject to NASA Procedural Requirements (NPR) 7120.8A, NASA Research and Technology Program and Project Management Requirements.
5.1 The PDS Project Office shall ensure core project management functions including but not limited to technical management, cost management, schedule management, risk management, procurement and configuration management, are performed consistent with NPR 7120.8 and other applicable NASA standards.
5.2 The PDS Project Office shall be responsible for ensuring NASA cybersecurity compliance of the PDS system.
5.3 The PDS Project Office shall ensure the transition of the online presence of the PDS to the NASA-managed web environment.
5.4 The PDS Project Office shall maintain the standards for PDS Metrics and reporting.
5.5 The PDS Project Office shall own and maintain the Level 2 requirements of the PDS.
5.6 The PDS Project Office shall oversee the process of selecting or designating a lead node to serve as a single point of contact for missions to interact with the PDS.
File details come from the government source that posted it. Updated .