Effective Date: April 20, 2011
Expiration Date: January 20, 2022
|| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppdendixA | AppendixB | AppendixC | AppendixD | ALL ||
C.1.1 NASA's formal Planetary Protection Policy and requirements documents, NPD 8020.7 and NPR 8020.12, detail overall planetary protection policy and requirements; assign and describe responsibilities; and provide specifications for key parameters involved in the implementation of requirements. These guidelines supplement those documents by describing a model process, consistent with NPD 8020.7 and NPR 8020.12, for the flow of communications between flight projects and the NASA Planetary Protection Officer and her/his staff and consultants at NASA Headquarters (hereinafter, "the PPO"). The purpose of these guidelines is to provide flight projects useful information to facilitate their implementation of planetary protection requirements, enable effective and timely communications, and contribute to the success of their missions.
C.2.1 Projects can benefit from communication with the PPO at NASA Headquarters even during preproject activities. Although not formally a part of planetary protection requirements, it is suggested that a project request a preliminary planetary protection categorization of the mission during the early stages of mission planning. A preliminary planetary protection categorization may be required by specific language in an Announcement of Opportunity. Prior to submitting a written request, the project is encouraged to communicate informally with the PPO.
C.3.1 During the early stages of the project, and no later than the end of Phase A, the project manager (may be the Principal Investigator on competitive missions) should request from the PPO, in writing, the formal planetary protection categorization of the mission. Again, informal communication with the PPO is encouraged prior to submittal of this request letter to ensure that the request is comprehensive and phrased appropriately.
C.3.2 After receipt of a PP Categorization Letter from the PPO, the Project should submit a Planetary Protection Plan, unless the project received a PP Category I categorization, which exempts it from any subsequent requirements. A Project-approved draft of the Planetary Protection Plan is due no later than the end of Phase B (conceptual study phase), with the formal release of the plan due no later than the Project's Preliminary Design Review (PDR). For PP Category II missions, as well as PP Category V-unrestricted Earth return, the Planetary Protection Plan is a fairly straightforward undertaking and may require only limited interaction with the PPO. To address any questions or issues that may arise, direct communication with the PPO is encouraged.
C.3.3 For missions assigned PP Categories III, IV, and V-restricted Earth return, preparation of the Project's Planetary Protection Plan is significantly more involved and complex. Development of such a Planetary Protection Plan requires frequent interaction with the PPO, the extent of which will depend on the PP category and degree of mission complexity. During the evaluation of alternative implementation strategies, communication with the PPO is necessary to ensure that the strategies are consistent with NASA's Planetary Protection Policy and requirements and, therefore, acceptable. The Planetary Protection Plan is subject to approval by the Project and concurrence by the relevant Program Office and through established Program Management channels (e.g., Program Executive), as appropriate, prior to its formal submission to the PPO for approval.
C.4.1 Following approval of the Planetary Protection Plan by the PPO, the Project embarks on the preparation of subsidiary plans and documentation as detailed in NPR 8020.12, and the implementation of planetary protection requirements consistent with the strategy outlined in the Planetary Protection Plan. Subsidiary plans do not generally require formal approval by the PPO (except all "inbound" subsidiary plans for PP Category V-restricted Earth return missions), but projects are encouraged to develop these plans in consultation with the PPO. Subsidiary plans should be forwarded to the PPO for information and review to ensure consistency with planetary protection requirements and the approved implementation strategy.
C.4.2 The process of implementing planetary protection requirements is subject to monitoring by the PPO. Monitoring activities include informal and formal reviews; witnessing of important implementation activities; reviews of ad hoc analyses; verification assays; and frequent communication. When needed, the project may seek clarification on parameter specifications, negotiate trade-offs, and, if absolutely necessary, request a deviation (with justification) from a particular requirement. It should be noted that approval of such a request does not represent a "waiver" of planetary protection requirements -- rather, the project is granted approval to deviate from the formal requirements by demonstrating that the goals of planetary protection will still be met.
C.4.3 The Project documents implementation activities in the Project's Planetary Protection Pre-Launch Report. This report is to be approved by the Project, with concurrence by the Program Office as appropriate, and submitted to the PPO no later than 90 days before launch. Again, it is strongly encouraged to maintain good communications with the PPO as the report is prepared; to provide a draft to the PPO to ensure the report's adequacy; and to address comments from the PPO before submitting the report for formal approval. Critical events and data collection taking place after the release of the Pre-Launch Report should be communicated to the PPO immediately and included in the informal and formal planetary protection prelaunch reviews that precede the certification by the PPO that the mission has met planetary protection requirements and has PPO approval to launch.
C.5.1 Activities occurring subsequent to submission of the Pre-Launch Report, along with launch and postlaunch updates, are to be documented in the Project's Planetary Protection Post-Launch Report, submitted to the PPO no later than 60 days after launch. The process for formal approval of this document is the same as that followed for the Planetary Protection Plan and Planetary Protection Pre-Launch Report.
C.5.2 Communications with the PPO continue postlaunch, as necessary, to report on mission operations involved in compliance with planetary protection requirements, including but not limited to the execution of trajectory correction maneuvers, orbit insertion, aerocapture or aerobraking, entry descent and landing, ground operations, etc. Any anomalies or off-nominal events that could affect planetary protection compliance should be reported immediately to the PPO, and an assessment of their impact on the project's compliance with planetary protection requirements should be provided in a timely fashion. Should compliance be jeopardized, the Project must take appropriate steps, negotiated with the PPO, to ensure that planetary protection requirements are not violated.
C.5.3 For PP Category V-Restricted Earth return missions, added to the outbound requirements are the certifications and documentation detailed in NPR 8020.12, particularly approval of all "inbound" subsidiary plans for PP Category V-restricted Earth return missions. The process of interaction with the PPO for sample return missions otherwise should follow the steps outlined in these guidelines.
C.6.1 If the project plans to extend its mission, a letter requesting approval for the extension as well as an Extended Mission Planetary Protection Report should be submitted to the PPO no later than 60 days prior to the end of the nominal mission. Communication with the PPO is necessary to assure that the appropriate information is included in the extension request. The same process must be repeated for each extended mission.
C.7.1 The final report the Project is required to submit to the PPO, per NPR 8020.12, is the End-of-Mission Planetary Protection Report. Consultation with the PPO may be appropriate to address issues identified during preparation of this report, and it is due no later than 60 days after the formally declared end of mission.
C.7.2 In the unfortunate event of a mission failure, the project is required to submit to the PPO an End of Mission report that includes a comprehensive analysis and assessment of the failure's contribution to the potential contamination of any impacted planet(s).
| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppdendixA | AppendixB | AppendixC | AppendixD | ALL |
|| NODIS Library | Program Management(8000s) | Search ||
This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.