Effective Date: March 29, 2019
Expiration Date: March 29, 2024
|| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | ALL ||
5.1.1 A NASA directive or charter can be cancelled when the Responsible Office or Chair determines that it served its purpose or is no longer needed. To cancel a directive or charter, the DM, with input from the Responsible Offices shall:
a. Submit a written justification via e-mail to the DMT to request cancellation of an Agency-level directive.
b. Submit a written justification via e-mail to the DMT, with concurrence from the Chair and the Agency Council Staff, to request cancellation of a NASA charter.
Note: To cancel Center-level directives or charters, Responsible Offices should contact the Center DM for instructions.
5.2.1 The DMT notifies Responsible Offices when Agency-level directives under their authority are approaching expiration as follows:
a. Notifies DMs six months prior to expiration.
b. Notifies OICs two months prior to expiration, if no action is taken.
5.2.2 In response to this notification, DMs, with input from the Responsible Office, shall:
a. Request an extension via e-mail to the DMT if more time is needed for revisions with an explanation of when revisions are expected.
b. Revalidate or revise directives according to the requirements described in Chapters 3 and 4.
5.2.3 For directives in coordination in the NODIS DMS, Responsible Offices may request up to three 30-day extensions on suspense dates. If the third 30-day extension has lapsed, the Responsible Office may request another extension for the amount of time that is realistically needed to publish the directive by submitting a completed Request for Waiver (Table B). Directives in coordination are tracked in the Headquarters Action Tracking System (HATS) and will appear overdue if submitted after the suspense date. Directives that languish in coordination with no action taken, may be withdrawn by the DMT if extensions are not requested. To request extensions on suspense dates, DMs, with input from the Responsible Office, shall submit:
a. A memo requesting a 30-day extension from the requesting Official-in-Charge to the Director for Mission Support Operations through the DMT ten days prior to the suspense date. Only three 30-day extensions can be requested.
b. A request for Waiver (Table B) to receive additional time if the third 30-day extension has lapsed.
5.3.1 Responsible Offices for Agency-level directives shall initiate resolution of impasses by:
a. Meeting at least twice with reviewing organizations that oppose new proposed requirements in an effort to come to an agreement.
b. Forwarding responses to reviewing organizations' opposing arguments, as well as the updated directive to the DMT for mediation if meetings do not yield a resolution.
c. Attending the meeting with the DRO, along with the reviewing organizations if a resolution cannot be mediated. At a minimum, the OIC (or designee), directive's originator, and directives manager attends the meeting with the DRO.
d. Updating directives according to the DRO's decision on how the Agency's will govern the requirement.
5.3.2 Reviewing Offices shall:
a. Notify the Responsible Office when there are oppositions to new proposed requirements.
b. Forward opposing arguments to the DMT for mediation.
c. Participate in all meetings, as designated, to resolve impasses on requirements they oppose in order to provide opposing arguments to the Responsible Office, as well as the DRO, if impasses cannot be resolved. At a minimum, the OIC (or designee), directive's originator, and directives manager attend the meeting with the DRO.
5.3.3 Director for Mission Support Operations shall assist and support the Deputy Administrator (or designee), Agency-level DRO, by:
a. Verifying that responsible and reviewing organizations meet at least twice in an effort to resolve impasses and nonconcurrences.
b. Reviewing Offices' opposing arguments and Responsible Offices' responses in an effort to mediate a resolution, if meetings do not yield one.
c. Scheduling and facilitating the meeting with the DRO, Reviewing Offices, and the Responsible Offices if a resolution cannot be mediated.
d. Informing the Reviewing Offices and the Responsible Office of the meeting day, time, and location.
e. Forwarding the Reviewing Offices' opposing arguments, the Responsible Offices' response to those arguments, as well as the updated directive to the DRO prior to the meeting.
Note: For impasses on Center-level directives, local instructions apply.
5.4.1 A directive may be transferred from one organization to another when functions described in the directive are also transferred. To transfer Agency-level directives, the DM, with input from the Responsible Office, shall send a memo from the OIC, with concurrence from the accepting organization's OIC, to the Director for Mission Support Operations.
5.4.2 The DMT will change the Responsible Office's information in NODIS once the Director for Mission Support Operations approves the transfer and notify the Responsible Office.
Note: NPD 1000.0 outlines the principles for establishing the proper set of requirements and for tailoring requirements, as needed. This paragraph discusses the implementation of these principles when requesting waivers from requirements described in Agency-level directives. For Center-level directives, local instructions apply.
5.5.1 Approval Authorities
22.214.171.124 Only the OIC who is responsible for the Agency-level directive or requirement is the approval authority for waiver requests.
Note: For complex waiver approval procedures, the Responsible OIC may cite another document in the directive.
126.96.36.199 The approval authority shall approve/disapprove a request for waiver from requirements based on the following criteria:
a. Requirements are not prohibited by external requirements.
b. Requirements do not present an undue risk to public health, safety, the environment, or personnel.
Note: If requirements present an undue risk, additional review and concurrence by other OICs is needed before approval.
c. Requirements are justified under the circumstances.
188.8.131.52 The approval authority shall only approve a request for waiver from requirements for a specific period or duration.
Note: The specific period or duration may be defined by calendar dates (i.e., From March 2006 to March 2008) or by project milestones (e.g., This waiver is in effect until disposal for XYZ Project).
184.108.40.206 The approval authority maintains a record of requests for waiver granted against Agency-level directives under their responsibility and should periodically review waivers to determine continued need.
5.5.2 NASA Headquarters organizations and NASA Centers requesting a waiver from requirements in Agency-level directives, shall document the following and submit it to the Responsible Office's DM for processing:
a. Identification of the requirement (directive and specific requirement(s)) for which the waiver is requested.
b. Scope (e.g., site, facility, operation, and/or activity) and duration of the request.
c. Justification, including:
(2) Whether application of the requirement in a particular circumstance described would conflict with another requirement.
(3) Whether application of the requirement in a particular circumstance would not achieve, or is not necessary to achieve, the underlying purpose of the requirement.
(4) Any other pertinent data or information related to the request (e.g., cost or schedule considerations).
(5) Identification and justification of the acceptance of any additional risk that will be incurred if the request is granted.
d. Address the following for request for waiver from environment, safety, health, and security requirements:
(1) A description of any special circumstances that warrant granting of the request, including whether:
(a) Application of the requirement in a particular circumstance would not be justified by any safety and health reason.
(b) Approving the request would result in a health and safety improvement that compensates for any detriment that would result from granting the request.
(c) There exists any other material circumstances not considered when the requirement was adopted for which it is in the public interest to grant the request.
(2) A description of any alternative or mitigating action that will be taken to ensure adequate safety and health and protection of the public, the workers, and the environment for the period the request will be effective.
e. Specific information called for in the requirements waiver sections of applicable NPRs and CPRs (e.g., NPR 7120.5).
5.5.3 To request a waiver from requirements contained in this directive, DMs, on behalf of their OIC or CD, shall complete the Request for Waiver (Table B) below and submit it to the DMT. Table B may be tailored to request waivers from requirements described in other Agency-level or Center-level directives, only if these directives do not already have an established waiver process.
5.5.4 Requests for waivers from requirements in this directive will be reviewed by the DMT periodically to determine continued need.
Download Fillable/Printable Table
| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | ALL |
|| NODIS Library | Organization and Administration(1000s) | 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.