![[NASA Logo]](../Images/nasaball.gif)
| |
NASA Procedures and Guidelines |
This Document is Obsolete and Is No Longer Used.
|
|
P.1 Purpose
P.2 Applicability
P.3 Authority
P.4 Applicable Documents and Forms
P.5 Measurement/Verification
P.6 Cancellation
1.1 Overview
1.2 General Provisions Governing NASA Directives
1.3 Description and Hierarchy of NASA Directives
2.1 Administrator
2.2 Deputy Administrator
2.3 Associate Administrator for Mission Support Directorate
2.4 Deputy Associate Administrator for Mission Support Directorate
2.5 Officials-in-Charge of Headquarters Offices
2.6 Center Directors
2.7 General Counsel
2.8 Inspector General
2.9 Chief Financial Officer
2.10 Assistant Administrator for Human Capital Management
2.11 Assistant Administrator for Procurement
2.12 Chief Information Officer
2.13 Responsible Offices
2.14 Directives Managers
2.15 Headquarters Quality Control Liaison
2.16 Headquarters Executive Secretariat
2.17 Agency Records Officer
3.1 Requirement Statements in NASA Directives
3.2 Responsibility Statements in Agency-level Directives
3.3 Document Citations in NASA Directives
3.4 Administrative Elements of NASA Directives
3.5 Writing Style
3.6 Content and Structure of NASA Policy Directives (NPD) and Center Policy Directives (CPD)
3.7 Content and Structure of NASA Procedural Requirements (NPR) and Center Procedural Requirements (CPR)
3.8 Content and Structure of NASA Interim Directives (NID) and Center Interim Directives (CID)
3.9 Content and Structure of Agency-level Charters
4.1 Introduction
4.2 Requesting Relief from Agency-level Directives
4.3 Establishing New Directives
4.4 Cancelling, Revising, Revalidating, or Providing Administrative Corrections to Existing NPDs or NPRs
4.5 Creating NIDs or CIDs
4.6 Hyperlinking Other Documentation to the NASA Online Directives Information System (NODIS) Library or the Center-level Directive's Library Systems
4.7 Case Files
Chg# |
Approver |
Date Approved |
Description/Comments |
1 |
Associate Administrator |
2/8/2017 |
Given the new requirements of the Federal Information Technology Acquisition Reform Act (FITARA), the Office of the Chief Information Officer (OCIO) is a mandatory reviewing and concurrence office for agency-level directives. NASA Centers are requested to adopt the same practice for Center-level directives. Paragraphs 2.12 and was updated to include FITARA as part of OCIO's review, and paragraph 4.3.7.7 was updated to include a mandatory review by the Information Officer for Agency-level directives and Center Information Officer/Information Technology for Center-level directives. |
2 |
Mission Support Directorate |
6/1/2017 |
Administrative corrections made to restore "shall" statement in paragraph 2.4.1 for the Deputy Associate Administrator for the Mission Support Directorate, and to remove unnecessary characters in Chapter 3 | 3 |
Agency Council Staff |
10/2/2017 |
Administrative corrections made to include the Office of Agency Council Staff as a concurring office on Agency and subordinate governance body charters. |
a. This directive describes the responsibilities and requirements for creating, revising, reviewing, approving, publishing, and cancelling NASA directives and Agency-level charters.
b. This directive provides specific instructions pertaining to the development, content, processing, and waiving of Agency-level and Center-level directives.
a. This directive is applicable to NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers. This directive applies to the Jet Propulsion Laboratory (JPL) (a Federally Funded Research and Development Center (FFRDC)) and other contractors only to the extent specified or referenced in applicable contracts.
b. In this directive, all mandatory actions (i.e., requirements) are denoted by statements containing the term "shall." The terms: "may" or "can" denote discretionary privilege or permission, "should" denotes a good practice and is recommended, but not required, "will" denotes expected outcome, and "are/is" denotes descriptive material.
c. In this directive, "Agency-level directives" refers to directives with Agency-wide applicability (e.g., NPDs, NPRs, and NIDs).
d. In this directive, "Center-level directives" refers to directives with Center-specific applicability (e.g., CPDs, CPRs, and CIDs).
e. In this directive, "NASA directives" refers to both Agency-level and Center-level directives.
f. In this directive, "NASA Charters" refers to those charters that govern Agency-wide councils, boards, committees, panels, and working groups.
g. In this directive, "Center-level charters" refers to those charters that govern specific Center councils, boards, committees, panels, and working groups.
h. In this directive, all document citations are assumed to be the latest version unless otherwise noted.
i. This directive is applicable to NASA directives developed or revised after the effective date of this NPR.
NPD 1400.1, Documentation and Promulgation of Internal NASA Requirements and Charters.
a. Inspector General Act of 1978, 5 U.S.C. App. § 4(a)(2), as amended.
b. Creating Labor-Management Forums to Improve Delivery of Government Services, E.O. 13522, 74 Fed. Reg. 66,203 (Dec. 14, 2009).
c. NPD 1000.0, NASA Governance and Strategic Management Handbook.
d. NPD 1000.3, The NASA Organization.
e. NPD 1001.0, 2014 NASA Strategic Plan.
f. NPD 1280.1, NASA Integrated Management System Policy.
g. NPD 1420.1, NASA Forms Management.
h. NPD 9910.1, Government Accountability Office/NASA Office of Inspector General Audit Liaison, Resolution, and Followup Program.
i. NPR 1441.1, NASA Records Management Program Requirements.
j. NPR 1450.10, NASA Correspondence Management and Communications Standards and Style.
k. NC 1000.32, Integrated Functional Review Board.
l. NRRS 1441.1, NASA Records Retention Schedules.
m. NODIS Manual.
n. NHQ Form 117, Action Document Summary.
o. NHQ Form 184, NASA Directive Request Summary.
p. NHQ Form 279, Review Report/Additional Comments.
q. NHQ Form 280, Cancelled Directive(s).
r. NASA Form 422, Signature.
a. In order to determine if responsible offices follow the required processes specified in this NPR for Agency-level directives initiated or revised after the effective date of this NPR, the Mission Support Directorate (MSD) monitors the processing of each Agency-level directive through NODIS and the subsequent signature process to ensure that all process steps and requirements have been completed correctly by all of the process participants. See Verification Matrix Table A in Appendix C.
b. In order to determine if responsible offices prepare directives in accordance with the requirements for the content and structure of directives that are specified in this NPR for Agency-level directives initiated or revised after the effective date of this NPR, MSD reviews the contents of each Agency-level directive during the NODIS review and verifies that the content requirements have been satisfied. See Verification Matrix Tables B-1 and B-2 in Appendix C.
c. In order to determine if Centers are following the content and process requirements of this NPR that are applicable to Centers for Center-level directives initiated or revised after the effective date of this NPR, Center Directors, or designees, determine and document compliance by applying a verification approach that is tailored to meet the needs of the Center. MSD surveys the Centers and conducts spot-checks every five years to review Center documentation and implementation of Center-specific verification activity. See Verification Matrix Tables C-1 and C-2 in Appendix C.
d. In order to determine if MSD fulfills its responsibilities as specified within this NPR, internal and external auditors responsible for verifying Headquarters requirements and processes evaluate MSD's performance against the requirements contained within this NPR.
NPR 1400.1F, NASA Directives and Charters Procedural Requirements, dated January 24, 2014.
1.1.1 A NASA directive is a document that formally prescribes requirements derived from law, the President, Federal regulation, the NASA Administrator, or other senior NASA officials. NASA directives can apply to all NASA activities or to a single NASA Center. NASA directives: (1) Establish policies, procedural requirements, and organizations; (2) Define purpose; (3) Grant authority to accomplish a task; and (4) Assign responsibilities.
1.1.2 Responsible Offices develop, coordinate, and promulgate NASA directives in accordance with this NPR to ensure that NASA directives:
a. Are necessary for the fulfillment of NASA's mission.
b. Are evaluated by all impacted or interested parties in draft form before issuance and that feedback is provided for comments received.
c. Are reviewed in draft form to reduce the potential for unintended technical, financial, or legal risks.
d. Are available and easily accessible or retrievable by all affected or interested parties.
e. Include an explanation of how the requirements in the directive will be verified for compliance.
1.2.1 NASA Directives are published in the NODIS Library at http://nodis3.gsfc.nasa.gov/.
1.2.1.1 Agency-level directives include NPDs that state the Agency's policies, NPRs that provide detailed procedural requirements to implement policy, and NIDs that provide an immediate, short-term statement of the Agency's policies or procedural requirements.
1.2.1.2 The Administrator approves all NPDs. Center Directors, or designees, approve all Center directives (e.g., CPDs, CPRs, and CIDs).
1.2.1.3 The signatory authority for NPRs and NIDs is either the Official-in-Charge of the Headquarters organization originating the NPR/NID or the Administrator.
1.2.2 NASA directives may apply to JPL (an FFRDC), other contractors, recipients of grants or cooperative agreements, and parties to other agreements only to the extent specified or referenced in the applicable contract, grant, or agreement. When NASA directives are applied to JPL, other contractors, recipients of grants or cooperative agreements, or parties to other agreements, the contract, grant, or agreement should specify which specific requirements from directives apply. Conversely, requirements directed toward civil servants and contractors should be clearly delineated within directives so that contracts, grants, or agreements can appropriately identify which requirements apply. See notes under paragraphs 2.13.2 and 2.14.2f for delineating examples.
1.2.3 Approved NASA directives are in effect for a maximum of five years. However, revisions can be made whenever a change is warranted. Note: Updates to change sections of an NPR can be coordinated in NODIS if the entire directive does not need to be revised. These updates will be recorded in the NPR's Change Log. There will be an assignment of a new five-year expiration date upon the completion of the changes.
1.2.4 NASA Centers may issue directives when no Agency-level directive exists that provides the required policy or instruction, when an Agency-level directive does not provide adequate policy or instruction, or when a situation is unique to a particular Center.
Note: It is at the discretion of Center management to determine whether Agency-level directives are sufficient or if more specific requirements are needed by the Center.
1.2.5 Requests for Relief (e.g., waivers, deviations, and tailoring) to Agency-level directives may be requested. See requirements for waiver requests in paragraph 4.2.
1.2.6 NPDs and NPRs are coordinated in the NODIS Document Management System (DMS) in accordance with an established monthly directives review cycle schedule that is accessible in the DMS. The coordination time for NPDs is no more than 90 calendar days. The coordination time for NPRs is no more than 120 calendar days. See the Directives Coordination Cycle in Figure 1-1.
Note 1: The coordination timeline starts on the day the official review commences. The Responsible Office may request up to three 30-day extensions to the coordination cycle. If the third 30-day extension has lapsed, the Responsible Office may request a waiver to receive another extension.
Note 2: 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 NODIS review with no action taken to respond by the suspense date, may be withdrawn by MSD if extensions are not requested.
Figure 1-1, Directives Coordination Cycle
1.2.7 However, NPDs and NPRs may be coordinated any time during the month on an out-of-cycle schedule for an expedited review in the NODIS DMS as long as the changes are minor and/or small portions of the document are being changed. Timelines for coordination are provided by the Responsible Office. Responsible Offices requesting out-of-cycle expedited reviews of NPDs and NPRs shall include the following in the request:
a. Purpose/rationale.
b. Internal or external requirement driving the Agency to publish requirements.
c. Date by which NPD or NPR needs to be published.
c. Timeline for coordination to include the dates for review, disposition, legal review, quality review, and Administrator's office approval.
Note 1: The minimum timeline for coordination is no less than 50 calendar days. See the Out-of-cycle Coordination Cycle in Figure 1-2.
Note 2: Extensions may be requested directly with the responsible office who can determine if a NODIS extension is necessary in accordance with Note 1 under paragraph 1.2.6.
Figure 1-2, Out-of-Cycle Coordination Cycle
1.3.1 In the event of a conflict among the top-level directives, the information provided in the highest ranking directive takes precedence.
1.3.2 In the event of a conflict among the top-level directives and one or more NPDs and CPDs and/or NPRs and CPRs, the information provided in the top-level directive(s) takes precedence.
1.3.3 In the event of a conflict between an NID, NPD, and an NPR, the information provided in the NID takes precedence.
Note: NIDs are included in the hierarchy at the same level of the directive it is intended to replace (i.e., an NID that is published in place of an NPD or NPR is included in the hierarchy at the level of either directive type).
1.3.4 In the event of a conflict between an NPD and an NPR with a Center-level directive, the information provided in the NPD or NPR takes precedence.
1.3.5 In the event of a conflict between a CPD and a CPR, the information provided in the CPD takes precedence.
1.3.6 In the event of a conflict between two or more equally ranking documents, the directive assigned to the office that is responsible for the function or program takes precedence.
Note 1: Attachment D of NPD 1400.1 establishes the order of flow and precedence and displays the hierarchical relationship between directives and NASA internal requirement documents.
Note 2: Readers may report conflicts to the Directives Manager to initiate resolution. See paragraph 2.13.1f.
Only the Administrator signs NPDs.
The Deputy Administrator, or designee, serves as the Agency-level Directives Resolution Official to resolve impasses, such as nonconcurrences and other issues that cannot be resolved at the organizational level.
2.3.1 The Associate Administrator (AA) for the Mission Support Directorate (MSD):
a. Has overall responsibility for the NASA Directives System.
b. Is the chair of the Integrated Functional Review Board (IFRB) responsible for examining proposed unfunded mandates derived from Agency-level directives and elevating unresolved, unfunded mandates to the Mission Support Council and directing to the appropriate Agency council (e.g., Agency Program Management Council (APMC) and Executive Council (EC)) for resolution, in accordance with the Board's process described in Appendix G and NC 1000.32.
Note: Functions of the IFRB are described in the Board's charter accessible in the NODIS Document Library here: http://nodis3.gsfc.nasa.gov/OPD_docs/NC_1000_32_.pdf.
2.4.1 The Deputy AA for MSD implements and maintains the NASA Directives System and establishes and enforces the policies and requirements in NPD 1400.1 and this NPR. The Deputy AA for MSD, or designee, shall:
a. Verify compliance with the requirements contained in this NPR by:
(1) Monitoring the processing of each Agency-level directive through NODIS and the subsequent signature process to ensure that all process steps and requirements of this NPR have been completed correctly by the process participants. Verification Matrix Table A in Appendix C is used to verify compliance with process requirements.
(2) Reviewing the contents of each Agency-level directive during the NODIS review by:
(a) Verifying that the content and structure requirements have been met using Verification Matrix Tables B-1 and B-2 in Appendix C.
(b) Forwarding results to the Responsible Office for corrective action.
(c) Confirming that corrective actions are completed.
(3) Conducting spot checks to review Center-specific directives and implementation of Center-specific verification activity every five years. Verification Matrix Tables C-1 and C-2 in Appendix C are used to verify that Center-level directives comply with the requirements of this NPR.
b. Assist and support the Deputy Administrator in the role as Agency-level Directives Resolution Official.
c. Verify the completeness of the Agency-level directive signature package when it goes to the responsible NASA official for signature to ensure that:
(1) All comments received from reviewing organizations during the review and approval process for Agency-level directives are dispositioned and that the dispositions are provided to the reviewing organizations.
(2) An explanation for nonconcurrences is documented and available in the directive's signature package.
d. Concur on Agency-level directives when submitted for signature.
e. Track, monitor, and report activities associated with processing Agency-level directives.
f. Ensure that Agency-level directives are coordinated, approved, and published within established timelines, withdrawing directives from coordination if not submitted for approval by established suspense dates and approving requests for extensions on established suspense and expiration dates.
g. Notify Responsible Offices when Agency-level directives under their authority are approaching expiration and requests that directives be revalidated, revised, or cancelled as follows:
(1) Notifies Directives Managers (DM) six months prior to expiration.
(2) Notifies Officials-in-Charge two months prior to expiration if no action is taken.
h. Distributes notifications when new, revised, and revalidated directives are approved and when interim directives are issued.
i. Ensure document control for Agency-level directives through maintenance of the NODIS library, the NODIS database, and signed approval packages.
j. Train and assist DMs and directives writers in the performance of their duties.
k. Monitor identified conflicts among directives to ensure resolution.
l. Maintain and dispose of all official files associated with approved Agency-level directives, in accordance with NPR 1441.1 and NRRS 1441.1. See paragraphs 4.3.8.1 through 4.3.8.3 for a list of official files.
2.5.1 OICs of Headquarters Offices have overall responsibility for directives promulgated by offices within their respective organization and are responsible for:
a. Determining their organization's need for establishing new Agency-level directives.
b. Ensuring that staff responsibilities are assigned to create or revise directives.
c. Submitting directives for official review and secure concurrences through NODIS. The NODIS Manual provides instructions for electronically coordinating NPDs and NPRs for official review and concurrence. The NODIS Manual is accessible at: https://nodis-dms.gsfc.nasa.gov/DMS_only/dir_homepage/NODIS_Manual.pdf.
d. Ensuring that Agency-level directives under their responsibility are reviewed for continuing need, applicability, and accuracy at least once every five years.
e. Cancelling Agency-level directives under their responsibility when they are no longer needed.
f. Designating a DM to assist, guide, and monitor the organization's directives activities.
g. Determining which Agency-level directives their office should review during the official review and approval process.
h. Evaluating and dispositioning all waivers to Agency-level directives under their responsibility, in accordance with the process described in paragraph 4.2 of this NPR.
i. Ensuring compliance with Agency-level directives and ensuring that directives under their responsibility do not conflict with material provided in other Agency-level directives.
Note: The OIC of the Headquarters Office may delegate the Responsible Office designation and responsibilities. Directives considered as under their responsibility for OICs of Headquarters Offices include all directives for which the Responsible Office reports to the OIC of the Headquarters Office.
2.6.1 Center Directors, or designees, are responsible for:
a. Ensuring compliance with Agency-level directives and ensuring that Center-level directives do not conflict with material provided in Agency-level directives.
b. Designating a Center DM as a point of contact to assist, guide, and monitor directives activities.
c. Determining which Agency-level directives the Center should review during the official review and approval process.
d. Signing Center-level directives.
2.7.1 The General Counsel is responsible for:
a. Reviewing for compliance with the law and commenting on all Agency-level directives during the process for coordinating and approving new or revised Agency-level directives.
b. Confirming that authorities, applicable documents, and references cited in Agency-level directives are formatted correctly, per paragraph 3.3.2.
c. Concurring on Agency-level directives prior to signature by the approving NASA official.
The Inspector General, in accordance with 5 U.S.C. App. § 4(a)(2), as amended, is responsible for reviewing and commenting on each Agency-level directive during the official review and approval process to identify possible impacts on effectiveness of and efficiency in the administration and operations of NASA programs to prevent fraud, waste, and abuse in NASA programs.
2.9.1 The Chief Financial Officer is responsible for:
a. Reviewing to ensure proper financial, resource (including budget, strategic planning, and performance), and acquisition consideration and comment on all Agency-level directives during the process for coordinating and approving new or revised Agency-level directives.
b. Concurring on Agency-level directives prior to signature by the approving NASA official.
The Assistant Administrator for Human Capital Management is responsible for coordinating the review of all proposed Agency-level directives with the national offices of Federal labor organizations in addition to conducting its own review and submitting a concurrence on these documents.
The Assistant Administrator for Procurement is responsible for reviewing and concurring on all Agency-level directives to determine if there are acquisition law or regulation impact requirements.
The Chief Information Officer, or designee, is responsible for reviewing and concurring on all Agency-level directives to determine if there are any requirements related to information systems and information technology, information collections, forms, records, Federal Information Technology Acquisition Reform Act, Privacy Act, Paperwork Reduction Act, American with Disabilities Act (508 Compliance), IT Security, and Sensitive But Unclassified information that need to be addressed.
2.13.1 Responsible Offices, as subject matter experts, shall prepare NASA directives in accordance with the requirements in Chapters 3 of this NPR to include the following:
a. Consulting the Office of Procurement when drafting new or revised requirements directed toward contractors to determine acquisition law or regulation impacts requirements.
b. Submitting NPRs for formal review only when there is an approved NPD that provides the authority for the NPR. Responsible Offices at the Centers may issue a CPR if there is an approved NPD, NPR, or CPD that provides the authority for the CPR.
Note: There need not be a separate NPD for each NPR or CPD for each CPR. An NPD or CPD may provide the authority for more than one NPR or CPR, respectively.
c. Submitting, at the time of request for official review and approval of directives, cost/benefit impacts (e.g., financial, human resources, and technical) to implement new requirements to avoid the potential for unintended consequences (see paragraph 4.3.6.1f).
d. Mitigating and resolving unfunded mandates with Centers during the comment/disposition period of directives and presenting unresolved proposed unfunded mandates to the IFRB in accordance with the Board's process described in Appendix G.
e. Maintaining currency for the directives they publish.
f. Ensuring that compliance with the requirements contained in Agency-level directives under their responsibility are verified.
Note: Spot checks, checklists, internal/external audits, or self-assessments may be used to ensure compliance.
g. Ensuring that Agency-level directives under their responsibility meet the requirements of this NPR, including responding to corrective actions.
h. Submitting directives signature packages for the Office of the Administrator's approval by the established suspense dates.
i. Requesting extensions of a suspense date, ten calendar days prior to the suspense date to submit signature package in order to obtain more time to resolve and respond to substantive issues related to the directive.
2.13.2 The Responsible Offices at the Centers shall prepare Center-level directives in accordance with paragraphs 2.13.1a-d, 2.13.1g, and 2.13.1i, as well as Chapter 3 of this NPR.
Note: Policy or procedural requirement formulation is done by NASA civil servants.
2.14.1 DMs are the points of contact in each Headquarters organization and NASA Center for matters pertaining to NASA directives. They are responsible for supporting OICs of Headquarters Offices, Headquarters senior managers, and Center Directors with directives activities and issues. This includes ensuring that directives are prepared and coordinated in accordance with the requirements in this NPR. Specifically, DMs:
a. Manage the directives process at their location.
b. Provide assistance to employees at their location with accessing NODIS.
c. Coordinate the official review of directives at their location.
d. Determine who should review Agency-level directives and ensure that reviewers are provided with the directive and the corresponding NASA Headquarters form (NHQ Form184) that summarizes significant changes and contains cost/benefit impacts accessible from NODIS.
e. Consolidate the reviewers' comments into the official response.
f. Document and initiate resolution of conflicts among directives (Agency-level and Center-level) that are identified or reported.
Note: Conflict resolution for Agency-level directives is initiated by contacting the DM of the Responsible Office(s) for the directive(s) in conflict and notifying the MSD.
g. Coordinate quality reviews of their organization's Agency-level directives with the respective Headquarters Quality Control Liaison.
h. Coordinate with directives writers to ensure that their directives meet the requirements of this NPR and that cost/benefit impact information to implement new/revised requirements is provided prior to submitting Agency-level directives for review.
i. Coordinate their organization's interim directives and requirement waivers for approval and publication. See paragraph 4.2 for waiver requirements and paragraph 4.5 for interim directives requirements.
j. Participate in DM meetings to remain aware of changes in the NASA directives process and NODIS.
k. Coordinate with their organization's Audit Liaison Representative (ALR) in order to acquire information on any Government Accountability Office (GAO) and/or Office of Inspector General (OIG) audit recommendations that impact the revisions to directives so that this information can be captured on NHQ 184 forms prior to acceptance of directives in NODIS.
Note 1: Senior management makes the final determination on acceptance of OIG/GAO recommendations. Also, events may occur after the release of the audit report that change the management plan's actions to address the finding(s). The ALR performs an advisory role in the process.
Note 2: For Center-level directives, local instructions apply.
2.14.2 In addition to the responsibilities listed in paragraph 2.14.1, excluding paragraphs 2.14.1g-i, Center DMs:
a. Manage and maintain a current online repository of Center-level directives.
b. Maintain a master list of Center-level directives.
c. Ensure that Center-level directives are approved and published in accordance with established procedures.
d. Track and monitor activities associated with processing NASA directives.
e. Train and assist directives writers and reviewers in the performance of their duties.
f. Maintain and dispose of case files for all Center-level directives in accordance with NPR 1441.1 (see paragraph 4.7).
Note: Policy or procedural requirement coordination can be done by a NASA civil servant or a NASA contractor.
Quality Control Liaisons for Headquarters Responsible Offices are responsible for ensuring that Agency-level directives signature packages and the Action Document Summary (ADS) are properly prepared (e.g., grammar, formatting, and timeliness).
2.16.1 The Headquarters Executive Secretariat is responsible for:
a. Conducting final quality reviews of Agency-level directives prior to approval and signature by the Agency official.
b. Providing all editorial changes in conformance with NPR 1450.10 and ensuring incorporation by the Responsible Office.
The Agency Records Officer in the Office of the Chief Information Officer is responsible for coordinating with the MSD, the Executive Secretariat, and the Office of the General Counsel on decisions affecting the numbering of NASA directives in accordance with the ten subject categories defined in NPR 1441.1 and NRRS 1441.1.
Note: Center DMs should contact their respective Center Records Officer for assistance.
3.1.1 Criteria for writing requirements statements in NASA directives:
a. Identify all requirements statements by using the word "shall" to denote mandatory compliance.
b. Designate at least one official (by position title) or organization as responsible and accountable for development, implementation, maintenance, and verification of the requirement.
c. Identify what action should be accomplished or what product should be provided to demonstrate compliance with the requirement.
d. Specify specific requirements, not general responsibilities with broad application
e. Separately state each individual requirement statement (i.e., one "shall" statement per paragraph or sub-paragraph).
Note: Each requirement should state any applicable timing for performance, delivery of a product, or completion of the requirement. This designation could be a specific event or a general flow in a process.
3.1.2 Do not replicate existing internal or external policy statements or procedural requirements in directives. However, cross-referencing may be used to cite existing requirements. NASA directives may supplement, clarify, or make more stringent external requirements or designate who is responsible for implementation of external requirements.
3.1.3 Do not include technical requirements in NASA directives. Technical requirements may be included in NASA technical standards, which may then be cited in NASA directives.
Note 1: Technical requirements are those requirements that discuss the design, performance, operational parameters, and constraints of equipment and systems. These are requirements that would typically be contained within a system or equipment specifications.
Note 2: View NASA Technical Standards here: http://standards.nasa.gov/.
Use official position titles and office titles as identified in NPD 1000.3 for consistency when assigning or documenting responsibilities in Agency-level directives.
3.3.1 NASA directives have three types of document citations: authority documents, applicable documents and forms, and references. Cite these documents in accordance with their purpose as follows:
a. Authority document citations list the higher level document(s) that authorize establishing the policy or requirements contained in the directive.
b. Applicable document and form citations consist of documents and forms incorporated by reference in the text of the directive and contains provisions or other pertinent requirements directly related to and necessary for the performance of the activities specified by the directive. Use only controlled and current forms in accordance with NPD 1420.1.
(1) Cite all applicable documents and forms listed in paragraph 4 (for NPDs) or paragraph P.4 (for NPRs) at least once within the text of the directive. Use statements to introduce applicable documents and forms (e.g., as required by, in accordance with, according to, or per).
(2) Conversely, list all applicable documents and forms cited within the text of the directive in paragraph 4 for NPDs or paragraph P.4 for NPRs.
c. Reference documents are documents that are not incorporated by reference in the text of the directive. These documents may consist of internal and external requirements and other resources considered by the Responsible Office to be useful as background information for the reader (to help in understanding the subject matter), but do not constitute requirements of the directive. In NPDs and CPDs, reference document lists are contained in an Attachment. In NPRs and CPRs, reference document lists are contained in an Appendix.
3.3.2 Within each document citation list (authority documents, applicable documents and forms, and references):
a. List document citations in the following order: United States Code, Public Law, Executive Orders, Code of Federal Regulations, Federal Register Notices, Office of Management and Budget Circulars, NPDs, NPRs, CPDs, CPRs, NASA Technical Standards, Forms, non-NASA Government standards, and other documents.
b. Format document citations using the following examples when listing in the authority, applicable documents and forms, and references sections:
(1) United States Code (Statutes) - National Aeronautics and Space Act, 51 U.S.C. § 20113 (a).
Note: "§" is a legal symbol for "section." Whole numbers refer to a "part" of the CFR; sections (§) consist of a decimal number, e.g., "§1259.102."
(2) Public Laws (Official Session Laws, Laws made prior to codification in the U.S. Code) - White House Conference on the Arts Act of 1990, Pub. L. 101-509, 104 Stat. 1427 (1990).
Note: Only cite if not already codified in the U.S. Code.
(3) Executive Orders (Signed by the President) - Regulatory Planning and Review, E. O. 12866, 3 CFR. 638 (1993).
Note: Includes codification of the Executive order in the Code of Federal Regulations.
(4) Code of Federal Regulations (Agency Regulations) - National Space Grant College and Fellowship Program, 14 CFR pt. 1259.
Note 1: Whole numbers in the CFR refer to a "part" (e.g., pt. 1259) of the CFR; sections (§) consist of a decimal number which includes the part number and the section number within the part; e.g., §1259.102.
(5) Federal Register Notices (Published in the Federal Register) - Environmental statements or availability, 71 Fed. Reg. 67389 (Nov. 21, 2006).
Note 1: The name of the citation (e.g., The National Aeronautics and Space Act) appears first and the location (51 U.S.C. § 20113 (a)) second when listing document citations described in paragraphs 3.3.2b(1)-(5).
(6) Office of Management and Budget Circulars (Generated by OMB) - OMB Circular A-19, Legislative Coordination and Clearance (09/20/1979).
(7) NASA Policy Directive - NPD 1400.1, Documentation and Promulgation of NASA Internal Requirements.
(8) NASA Procedural Requirements - NPR 1400.1, NASA Directives and Charters Procedural Requirements.
(9) NASA Standards - NASA-STD-8709.2, NASA Safety and Mission Assurance Roles and Responsibilities for Expendable Launch Vehicle Services.
(10) NASA Forms - NHQ Form 184, NASA Directive Request Summary.
Note 1: The document type and number (e.g., NPR 1400.1) appears first and the name (e.g., NASA Directives and Charters Procedural Requirements) second when listing document citations described in paragraphs b(6)-(10).
c. Cite documents within the text of directives as follows:
(1) Use the document citation location and omit the name when citing within the text of directives for documents described in paragraphs 3.3.2b(1)-(5) (e.g., 51 U.S.C. § 20113 (a)).
(2) Use the document type and number and omit the name when citing within the text of directives for citations described in paragraphs b(6)-(10) (e.g., NPR 1400.1).
d. Within each category, list documents in numerical order or alphabetical order by title if documents are not numbered.
e. When citing or listing NASA directives within NASA directives, exclude the revision letter designation (see Figure 2).
Note: This requirement is applicable only when citing or listing NASA directives in NASA directives. (In NASA directives, the current published version is what is referred to when a NASA directive is cited.) For other types of documents, citing the revision letter of the directive may be appropriate. Refer to the writing instructions for the type of document you are preparing if more information is needed.
f. Ensure that documents cited in the directive are approved documents that are available to the reader.
g. If a cited document is not a Federal statute or regulation, a NASA directive, or is not available in the NASA Technical Standards System, include footnotes (or URLs that allow public access) to show readers precisely where to find the cited documents.
h. Refer to one or more of the following resources to ensure that citations are current and accurate:
(1) United States Code Citations:
(a) Office of Law Revision Counsel - http://uscode.house.gov/.
(b) Government Publishing Office (GPO) Access - http://www.gpoaccess.gov/uscode/index.html.
(2) Public Laws citations - http://uscode.house.gov/popularnames/popularnames.htm.
(3) Executive Order citations:
(a) Title 3 on GPO Access - http://www.gpo.gov/fdsys/.
(b) Office of the Federal Register - http://www.gpo.gov/fdsys/browse/collection.action?collectionCode=FR.
(4) Code of Federal Regulations citations - http://www.gpoaccess.gov/cfr/index.html.
(5) NASA Directives - http://nodis3.gsfc.nasa.gov/.
(6) NASA Standards - http://standards.nasa.gov/.
(7) NASA Forms - http://server-mpo.arc.nasa.gov/services/NEFS/.
i. Use the following abbreviations for citations described in paragraphs 3.3.2b(1)-(5):
(1) United States Code - U.S.C.
(2) Federal Register - FR.
(3) Code of Federal Regulations - CFR.
(4) Part - pt., Parts - pts.
(5) Subpart - subpt. , Subparts - subpts.
(6) Appendix - app.
(7) Chapter - ch.
(8) Section - §, Sections - §§
(9) Section - sec.
Note: The word "section" instead of the symbol is used when it is the first word in a sentence. The word is also used in the text of the body and footnotes of law reviews and other documents except when referring to the U.S. Code. Otherwise, the symbol is used. (e.g., The National Aeronautics and Space Act, 51 U.S.C. § 20113 (a).
(10) Executive Order - EO
(11) Public Law - Pub. L.
3.4.1 NASA Directives Numbering Scheme
3.4.1.1 The NASA directives numbering scheme is composed of six elements that create a unique identifier. The six elements are: one or two letters indicating Agency-level or NASA Center, two letters indicating the NASA directive type, four numbers indicating the subject category, a separator (period), the NASA directive serial number, and letter(s) indicating the revision level designation (see Figure 2).
Figure 2. NASA Directives Numbering Scheme
Note: Include the full directive number in the file name and masthead section of the draft and final documents.
3.4.1.2 The subject category numbers used to classify NASA directives are the same subject categories found in in NRRS 1441.1. The serial numbers are automatically generated when the directive is approved.
3.4.1.3 For Agency-level directives, the MSD works with the Responsible Office to ensure that directives numbers are assigned in accordance with NRRS 1441.1.
3.4.1.4 For Center-level Directives, the Center DM works with the Responsible Office to ensure that directives numbers are assigned in accordance with the NASA Directives Numbering Scheme.
3.4.2 Effective and Expiration Dates for NASA Directives
3.4.2.1 A NASA directive takes effect on the date that it is signed by the approving official.
3.4.2.2 NPDs, NPRs, CPDs, and CPRs expire within a maximum of five years after signature or revalidation.
3.4.2.3 NIDs and CIDs expire upon the effective date of the permanent directive or 12 months after the effective date of the interim directive, whichever is earlier.
3.4.2.4 NPDs and NPRs will automatically be removed from the NODIS Library upon expiration, unless (1) an NPD or NPR replacing the directive being removed has been submitted for revalidation or for review and approval, or (2) the Responsible Office has requested an extension with justification. The current NPD or NPR will be granted an extension and remain effective until its revision is approved. See paragraph 4.4.2 for provisions to allow Agency-level directives to remain effective.
3.4.2.5 NIDs will automatically be removed from the NODIS Library upon expiration, unless an NPD or NPR replacing the NID is submitted for review and approval through NODIS.
Note: A NID may be revised once, and the expiration date will be 12 months after the effective date of the revised NID. If an extension on a NID's expiration date is needed, a waiver request can be submitted.
3.4.2.6 CPDs and CPRs will automatically be removed from the Center Directives Library upon expiration, unless (1) a CPD or CPR replacing the directive being removed has been submitted for revalidation or for review and approval, in accordance with the Center's established process, or (2) the Responsible Office has requested an extension with justification. The current CPD or CPR may be granted an extension and remain effective until its revision is approved.
3.4.2.7 CIDs will automatically be removed from the Center Directives Library upon expiration, unless a CPD or CPR replacing the CID is submitted for review and approval, in accordance with the Center's established process.
Note: A CID may be revised once, and the expiration date will be 12 months after the effective date of the revised CID.
3.5.1 Apply the following writing style rules:
a. Use NPR 1450.10 to supplement the style requirements in this NPR.
b. Exclude caveat phrases (e.g., "as applicable," "as appropriate," "whenever possible," "etc.") within requirements statements.
c. Use page numbers (e.g., 1, 2, 3) in NPRs, but exclude indexed table of contents that correspond to page numbers.
d. Align all text along the left margin (i.e., left justify or flush left).
e. Indent and italicize notes.
f. Center figures and tables. Number all figures (e.g., Figure 1) and add the figure number and title at the bottom of the figure. Letter all tables (e.g., Table A) and add the table letter and title above the table.
g. Use the correct phrasing to denote mandatory action or other forms of action, per paragraph P.2b.
h. Number/letter all paragraphs. If there is not a second paragraph immediately following at the same level, do not number/letter the paragraph. Exclude periods behind numbered paragraphs (e.g., use 3.5.1, not 3.5.1.), but include periods behind lettered paragraphs (e.g., use i., not i).
3.5.2 Responsible Offices that write Center-level directives will adhere to the requirements in paragraphs 3.5.1a-b and 3.5.1g-h. Adherence to paragraphs 3.5.1c-f is under the discretion of the Center official responsible for the writing styles for Center-level directives.
3.6.1 NPDs and CPDs document Agency- and Center-level policy statements, assignment of responsibilities for policy implementation, delegations of authority, approach for verification of compliance with the NPD or CPD, and the official's approval.
3.6.2 NPDs and CPDs should be no more than five pages, excluding attachments. The NPDs and CPDs consist of the following elements:
a. Masthead: Directive Number, Effective Date, Expiration Date, Responsible Office, and Subject (Title).
b. Change Log that describes administrative changes to an NPD or CPD.
Note: A Change Log can be added when the NPD or CPD is developed or added after the NPD or CPD is revised.
c. Body consisting of 8 required paragraphs: 1. Policy; 2. Applicability; 3. Authority; 4. Applicable Documents and Forms; 5. Responsibility; 6. Delegation of Authority; 7 Measurement/Verification; and 8. Cancellation.
Note: Governing NPDs may request relief from content and structure requirements. See paragraph 4.2 for requirements to request relief from Agency-level Directives.
d. Signature Block.
e. Attachments.
f. Graphics.
g. Distribution statement (e.g., NODIS or another system).
Note: If the distribution of the NPD or CPD is restricted only to NASA, include a distribution statement to identify the restrictions for release of the NPD or CPD.
3.6.3 Include the following content requirements when developing NPDs or CPDs:
a. Change Log - Date and description of updates or administrative changes made to an NPD or CPD. Note: A change log can be added when the NPD or CPD is developed or added after the NPD or CPD is revised.
b. For Paragraph 1, Policy - General statement of the principles, fundamental values, and general direction of the Agency or Center that is used to determine present and future decisions. Therefore, use appropriate language to introduce the policy (e.g., "It is NASA Policy" or "This directive establishes policy forâ?¦") and do not include "shall" statements.
c. For Paragraph 2, Applicability - The statement of the scope of the required application of the NPD or CPD. Include the following applicability statement: "This NPD is applicable to NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers."
(1) If the NPD applies to JPL (an FFRDC), other contractors, recipients of grants or cooperative agreements, or parties to other agreements, add the following applicability statement in Paragraph 2, Applicability, in addition to the applicability statement in paragraph 3.6.3c. "This language applies to JPL (a Federally-Funded Research and Development Center), other contractors, recipients of grants, cooperative agreements, or other agreements only to the extent specified or referenced in the applicable contracts, grants, or agreements." However, only list the type of document (i.e., contract, grant, or agreement) to which the directive applies. For example, if the directive is not applicable to a "grant," only list "contract or agreement" to indicate the directive's applicability.
Note: This statement alone is not sufficient to stipulate requirements for the contractor or recipient of the grant. Requirements can be delineated by adding a note after the requirements' paragraph. See paragraph 2.13.2 or 2.14.2f for examples of delineating requirements between civil servants and contractors or recipients of grants.
(2) For CPDs, include a statement similar to 3.6.3c above to ensure applicability at the Center and associated facilities.
(3) For NPDs and CPDs, include a statement that describes terms that denote action. See paragraph P.2b.
(4) For NPDs and CPDs, include the following statement: "In this directive, all document citations are assumed to be the latest version unless otherwise noted." See paragraph P.2h.
d. For Paragraph 3, Authority - List the NPD or CPD and external authority(ies) or requirements that justify establishing the NPD or CPD. This latter category includes only those external sources that are the authority for the NPD. Place all other external sources in the Applicable Documents or References sections.
e. For Paragraph 4, Applicable Documents and Forms - A list of documents and forms cited in the body of the directive that contains provisions or other pertinent requirements directly related and necessary to the performance of the activities specified by the directive. Apply the requirements in paragraph 3.3 to document citations.
f. For Paragraph 5, Responsibility - An explanation of who (by position or organization) is responsible for implementing the policy stated in the NPD or CPD. Write responsibility statements for implementation by the highest organizational level possible. Use "shall" statements only to specify specific actions, not general responsibilities with broad application. Do not dictate how an organizational leader is to organize or assign responsibilities within the leader's organization.
g. For Paragraph 6, Delegation of Authority - Paragraph reserved for direct delegation from the Administrator, Official-in-Charge, or Center Director to a specific position (e.g., Agency Regulatory Policy Officer).
h. For Paragraph 7, Measurement/Verification - An explanation of how compliance will be measured. Specify the information that is needed to support senior management's evaluation of performance for compliance and implementation. Where quantitative evaluation is possible, identify what data is to be collected, who collects the data, and who receives the data for evaluation. Cross-reference measurement/verification data that responds to externally imposed requirements to provide traceability to those requirements, for example, Government Performance and Results Act reporting requirements.
Note: This information may be presented as text within the paragraph, as a verification matrix, as an attachment to the NPD or CPD that includes details of data and report of data; such as formats and timelines; or as a citation to an NPD, CPD, or another requirements document.
i. For Paragraph 8, Cancellation - A list of directives that will be cancelled upon issuance. If the issuance cancels one or more directives, cite the Directive Number(s), Title(s), and Effective Date(s). If the issuance does not cancel a directive, state "None."
j. Signature block for the approving official's signature.
k. Attachments for information related to the directive (i.e., definitions, acronyms).
l. Graphics to illustrate information related to the directive.
m. Numbered paragraphs in accordance with Figure 3.
Figure 3, NPD and CPD Paragraph Numbering/Lettering
n. If there is a need to include definitions or other material such as details regarding measurement/verification to support the NPD or CPD, document the supporting material as an attachment.
Note: NPD and CPD attachments may be text and/or graphics. Contact your local DM for instructions.
o. Number paragraphs in attachments using the letter of the attachment (e.g., A.1, A.2), excluding attachments containing acronyms and definitions.
p. Document any definitions for words and phrases used in the NPD or CPD in Attachment A.
(1) List the definitions in alphabetical order.
(2) Provide only definitions for terms used in the NPD or CPD and only if the definitions are different than those used in dictionaries or other standard usage.
q. Document any acronyms used in the NPD or CPD in Attachment B and list in alphabetical order.
Note: If there are no definitions placed in Attachment A, acronyms can be placed in the Attachment A only if there are no other attachments that can be placed before the acronyms.
3.6.4 Do not document procedural information or instructions in an NPD or CPD.
3.7.1 NPRs and CPRs document procedural direction for essential or otherwise mandated items only. This includes procedural requirements that are established for reasons of health, safety, security, efficiency, and effectiveness.
3.7.2 NPRs and CPRs consists of the following elements:
a. Cover that includes the masthead with the Directive Number, Effective Date, Expiration Date, Responsible Office, and Subject (Title).
b. Change Log that describes administrative changes made to an NPR or CPR.
Note: A change log can be added when the NPR or CPR is developed or added after the NPR or CPR is approved.
c. Table of contents consisting of the preface, chapter titles, second-level paragraph titles (only if the second-level paragraphs exist in the directive), and appendices. Refer to this NPR's table of contents for formatting instructions.
d. Distribution statement. (This statement is populated by NODIS or other respective Center-level systems.)
Note: If distribution of the NPR or CPR is to be restricted to only NASA, include a distribution statement to identify the restrictions for release of the NPR or CPR.
e. Preface consisting of six required paragraphs: P.1 Purpose; P.2 Applicability; P.3 Authority; P.4 Applicable Documents and Forms; P.5 Measurement/Verification; and P.6 Cancellation. See paragraph 3.7.3a-f for Preface content requirements.
f. Chapters - Divided sections separated by page breaks that describe the directive's requirements and responsibilities that can be subdivided into paragraphs.
g. Appendices - Supplementary material or contractor requirements that are attached at the end of the directive.
Note: Governing NPRs may request relief from content and structure requirements. See paragraph 4.2 for requirements to request relief from Agency-level directives.
3.7.3 Include the following content requirements when developing NPRs and CPRs:
a. For Paragraph P.1, Purpose - Describe the rationale for establishing the NPR or CPR and what will be accomplished by implementing it.
b. For Paragraph P.2, Applicability - State the scope of the required application of the NPR or CPR. Include the following applicability statement: "This NPR is applicable to NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers."
(1) If the NPR is to apply to JPL (an FFRDC), other contractors, recipients of grants or cooperative agreements, or parties to other agreements, add the following applicability statement in P.2, Applicability, in addition to the applicability statement in paragraph 3.7.3b. "This language applies to the Jet Propulsion Laboratory (a Federally-Funded Research and Development Center), other contractors, recipients of grants and cooperative agreements, and parties to other agreements only to the extent specified or referenced in the applicable contracts, grants, or agreements." However, only list the type of document (i.e., contract, grant, or agreement) to which the directive applies. For example, if the directive is not applicable to a "grant," only list the "contract or agreement" to indicate the directive's applicability.
Note: This statement alone is not sufficient to stipulate requirements for the contractor, recipient of the grant or cooperative agreement, and other agreements. See paragraph 2.12.1a for an example of delineating requirements for contractors or recipients of grants.
(2) For CPRs, include a statement similar to 3.7.3b above to ensure applicability to the Center and associated facilities.
(3) For NPRs and CPRs, include a statement that describes the terms that denote action. See paragraph P.2b.
(4) For NPRs and CPRs, include the following statement: "In this directive, all document citations are assumed to be the latest version, unless otherwise noted." See paragraph P.2h.
c. For Paragraph P.3, Authority - List the NPD or CPD and the higher level external authority(ies) or requirement(s) that justify establishing the NPR or CPR. For the latter category, include only those external sources that are the authority for the NPR or CPR. Place all other external sources in the Applicable Documents or Reference sections.
d. For Paragraph P.4, Applicable Documents and Forms - Refer to description in paragraph 3.6.3e.
e. For Paragraph P.5, Measurement/Verification - Refer to description in paragraph 3.6.3h.
f. For Paragraph P.6, Cancellation - Refer to the description in paragraph 3.6.3i.
g. Number NPR or CPR Preface paragraphs in accordance with Figure 4.
Figure 4, NPR or CPR Preface Paragraph Numbering/Lettering
h. Number NPR or CPR chapter paragraphs in accordance with Figure 5.
Figure 5, NPR or CPR Chapter Paragraph Numbering/Lettering
Note: Use Figure 3 if paragraphs go beyond the 4th level.
i. Ensure that appendices do not contain requirements for civil service employees, only supporting information for the NPR or CPR.
j. Number paragraphs in appendices using the letter of the appendix (e.g., A.1, A.2), excluding appendices containing acronyms and definitions.
k. Document any definitions for words and phrases used in the NPR or CPR in Appendix A.
(1) List the definitions in alphabetical order.
(2) Provide only definitions for terms used in the NPR and only if the definitions are different than those used in dictionaries or other standard usage.
l. Document any acronyms used in the NPR or CPR in Appendix B and list in alphabetical order.
Note: If there are no definitions placed in Appendix A, acronyms can be placed in Appendix A only if there are no other appendices that can be placed before the acronyms.
m. If a verification/measurement matrix appendix is included within the NPR or CPR, include it in Appendix C.
Note 1: If there are no definitions placed in Appendix A or acronyms placed in Appendix B, measurement/verification can be placed in either of these appendices only if there are no other appendices that can be placed before the measurement/verification.
Note 2: See Appendix C of this NPR for examples of verification/measurement matrices.
3.8.1 Document the following when developing NIDs and CIDs:
a. Interim policy statements.
b. Assignment of interim responsibilities for policy implementation.
c. Interim requirement statements.
d. Assignment of interim responsibilities for completing requirements.
e. Applicability (e.g., Agency-wide or Center-specific).
Note: For NIDs and CIDs, include the following statement: "In this directive, all document citations are assumed to be the latest version, unless otherwise noted." See paragraph P.2h.
3.8.2 NIDs and CIDs may include policy memos or any other issuances intended to impose policy or requirements at the Agency or Center level.
3.8.3 NIDs and CIDs are issued for immediate or short-term use (see paragraph 3.4.2.3).
3.8.4 Follow the procedures contained in paragraph 4.5 for issuing NIDs and CIDs.
3.8.5 Coordinate with MSD to ensure that NIDs are added to the NODIS Library.
3.8.6 Coordinate with the Center DM to ensure that CIDs are published in accordance with local processes.
Note: NIDs and CIDs may be formatted as memorandums, directives, paragraphs, or other templates. See your DM for guidance on the preferred format for your organization.
3.9.1 Charters establish councils, boards, committees, panels, and working groups mandated by statute, the NASA Administrator, or an OIC of a Headquarters Office. To the extent that a group is established by law, directive, or other authority, the charter cites specific authority. Councils, committees, boards, and panel chairs ensure meeting preparation, efficiency, and follow up on actions. Members are expected to attend and participate in scheduled meetings. Respective charters include provisions for duration and periodic critical assessments of performance.
a. The term "council" is reserved for entities responsible for overall governance of the Agency or an Agency program, the technology portfolio managed by the Space Technology Mission Directorate, the MSD, or a Center. Councils are comprised of senior management tasked to make decisions regarding policy, strategic direction and planning, goals, or resources. The charters for NASA's governing councils (i.e., Executive Council, Senior Management Council, Mission Support Council, and Program Management Council) are maintained in NPD 1000.3.
b. All other Agency-level charters required by regulation, statute, program control, policy, or directed by the Administrator are located in NODIS.
c. Boards are comprised of senior management tasked to make decisions regarding implementation of policy, strategic plans, goals, and resources. Boards shall only be established in areas of Agency-wide significance with supporting topics and responsibilities that cross several organizations, as directed by a council. Decisions made by boards will be consistent with guiding policy direction and programmatic guidelines provided by a council. To execute actions generated by a board, a committee, panel, or working group may be established.
d. Committees, panels, and working groups are established as advisory groups for councils and boards to address significant topics, as requested by Agency leadership, Mission Directorates, the Offices of the Chief Technologist and Scientist, the MSD, or Centers.
(1) Committees - A group of individuals that meet to advise, coordinate, research, or make recommendations. The lifespan of a committee is based on the completion of activities assigned by a council or board. Committee charters are established with the respective council's or board's approval.
(2) Panels - A group of individuals gathered to advise, judge, interview, or discuss topics supported by councils or boards. The lifespan of a panel is based on completion of activities assigned by the respective council or board. Panel charters are established with the respective council or board's approval.
(3) Working Groups - A group of individuals working together to create a document or to resolve problems. The lifespan of a working group is based on completion of activities assigned by the respective council or board. Charters are not required for working groups unless the working group is expected to operate indefinitely, includes members across the Agency, and is established to support and is expected to report out to a council or board.
3.9.2 To publish or revise charters for governing councils, refer to NPD 1000.3 for instructions. To publish charters for other councils, boards, committees, or panels, the responsible office shall:
a. Ensure that Agency-level charters contain standard paragraphs in accordance with Figure 6.
Figure 6, Agency-level Charter Standard Paragraphs
b. Submit a hard and electronic copy of the charter with the chair's approval, along with concurrences from the Office of the General Counsel and the Office of Agency Council Staff, to the MSD.
3.9.3 Center-level charters are applicable to the issuing Center. To establish and/or publish Center-level charters, contact the Center's DM.
4.1.1 The NODIS Document Management System (DMS) is NASA's primary tool for creating, revising, reviewing, approving, publishing, and cancelling Agency-level directives. The NODIS DMS provides an electronic means to create, review, and comment on draft documents, disposition comments, concur on the directives, approve the directives, control revisions, track document history, generate reports, and publish Agency-level directives. All Agency-level directives are developed through the NODIS DMS.
4.1.2 The NODIS DMS coordination process will not be used to impede the Agency's legal obligations with respect to mission accomplishment, protection of worker health and safety and protection of the public, protection of the environment, or national security.
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 relief (e.g., waiver, deviation, and tailoring) from requirements that are established by Agency-level directives. For Center-level directives, local instructions apply.
4.2.1 Approval Authorities
4.2.1.1 Only the Administrator or the OIC who is responsible for the Agency-level directive, or delegated authority, approves requests for relief from requirements contained in the Agency-level directive.
4.2.1.2 The responsible OIC for the directive may delegate this approval authority to a lower level.
Note: For complex waiver/deviation/tailoring approval procedures, the Responsible OIC may cite another document in the directive.
4.2.1.3 The approval authority shall approve/disapprove a request for relief 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.
c. Requirements are justified under the circumstances (see paragraph 4.2.2 for instructions on how to prepare a justification).
4.2.1.4 The approval authority shall only approve a request for relief 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).
4.2.1.5 The approval authority maintains a record of requests for relief granted against Agency-level directives under their responsibility.
4.2.2 Responsible offices requesting relief from requirements, shall document the following in the request:
a. Identification of the requirement (directive and specific requirement(s)) for which the relief is requested.
b. Scope (e.g., site, facility, operation, and/or activity) and duration of the request.
c. Justification, including:
(1) Purpose/Rationale.
(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 relief 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 relief sections of applicable NPRs and CPRs (e.g., NPR 7120.5).
Note: For Center Requirement Waivers, local instructions for creating requirements waivers apply.
4.3.1 Responsible Offices for Agency-level directives shall use the NODIS DMS to create, coordinate, and approve any new NPD or NPR within the timeline established in paragraph 1.2.6.
4.3.2 Responsible Offices at the Centers shall use local processes to create, coordinate, and approve any Center-level directives.
4.3.3 Responsible Offices shall ensure that their DM is notified prior to beginning the process to establish a new directive.
4.3.4 Prereview Process
4.3.4.1 The prereview process provides an opportunity for review and comment, prior to the formal review, in NODIS, to address substantive issues in order to facilitate the completion of NASA directives within the timeframe allotted. Should a Responsible Office choose to conduct a prereview, the following are standard steps in the prereview process:
a. The Responsible Office for the directive creates a draft of the new or revised directive and distributes it to those affected by the directive and to those offices that the Responsible Office believes should review the draft.
Note: Local processes for prereview may have an established distribution list for directives prereviews. Consult your Center DM.
b. The Responsible Office for the directive determines the methodology for conducting the prereview.
Note: The Open Review System (https://openreview.gsfc.nasa.gov/ORSHome.cfm) is a Web-based tool that may be used to coordinate a prereview.
c. The Responsible Office coordinates, consolidates, and dispositions comments in preparation for the official review of the directive.
Note: If a prereview is conducted, comments resolved during the prereview can be restricted by the Responsible Office during the official review.
4.3.5 Prior to Official Review and Approval
4.3.5.1 For Agency-level directives, the Responsible Office shall:
a. Submit directives (i.e., new or revised) to the Office of Human Capital Management, Labor Relations Officer, who will ensure the national union receives a 30-day consultation period, as appropriate, in order to satisfy the Agency's obligation to provide this consultation period. Confirmation that this coordination is completed will be required on NHQ 184 in order for MSD to accept the directive into the NODIS system. For Center-level directives, contact the Center DM.
b. Ensure that their respective DMs and Audit Liaison Representatives (ALR) coordinate so that any information related to Government Accountability Office (GAO) and/or Office of Inspector General (OIG) recommendations that require revisions be made to directives is appropriately captured on NHQ 184. Confirmation that this coordination has been completed will be required on the NHQ 184 in order for MSD to accept the directive into the NODIS system.
4.3.6 Official Review and Approval
4.3.6.1 The official review and approval processes for Agency- and Center-level directives may be different. Headquarters and Center Officials responsible for establishing an official review and approval process at their location shall ensure that the process includes, at a minimum, the following steps:
a. Release of the draft directive utilizing an approved method and/or forms for an official review.
b. Notification and request for review by specified organizations. This may include provisions to allow organizations an opportunity to request to be added or removed from the review.
Note: For Agency-level directives, the Inspector General is a mandatory reviewing office. The Responsible Office is responsible for completely dispositioning the Inspector General's comments.
c. Review by the legal office (General Counsel for Agency-level directives; Chief Counsel for Center-level directives).
d. Sufficient instructions to reviewers to ensure that the review adheres to the approved process and schedule.
e. A system to provide feedback to reviewers indicating how their comments were incorporated or a rationale for not incorporating the reviewer's comments.
f. For Agency-level directives, the Responsible Office shall:
(1) In the request for review, include cost/benefit impacts to implement new requirements; in terms of financial, human resources, and technical (e.g., associated costs to implement new requirements and what can be gained by implementing the new requirements); and potential for unintended consequences.
Note: Space for the cost/benefit impacts is provided on the NHQ 184 in NODIS. Appendix F outlines the cost/benefit impacts for implementing requirements added to NPR 1400.1. The Responsible Office may use this as an example of appropriate cost/benefit impacts to be included in all Agency-level directives.
(2) Disposition all comments on the directives' technical content and cost/benefit impacts provided by reviewing organizations and Centers.
(3) Present unresolved proposed unfunded mandates to the IFRB for resolution in accordance with the Board's process described in Appendix G.
4.3.7 The Concurrence Process
4.3.7.1 DMs shall enter comments and a concurrence decision (e.g., concur, concur with comments, concur dependent upon disposition of comments, or nonconcur) in NODIS for Agency-level directives.
Note: See Appendix A for concurrence decision definitions.
4.3.7.2 Reviewing Offices and Centers shall:
a. Review and submit comments and concurrence decision on Agency-level directives' cost/benefit impacts described in the NHQ Form184, as well as the directive's technical content, to their respective DM.
Note: Reviewing Offices and Centers are encouraged not to submit grammatical comments on Agency-level directives to prevent discrepancies in grammatical corrections done by the NASA Headquarters Executive Secretariat, in accordance with NPR 1450.10, prior to approval for issuance.
b. Notify Headquarters functional organizations when proposed requirements in directives prevent implementation in an effort to mitigate and resolve and elevate unresolved mandates to the IFRB in accordance with the Board's process in Appendix G.
4.3.7.3 The legal office shall record a concurrence decision on all directives (General Counsel for Agency-level directives; Chief Counsel for Center-level directives).
4.3.7.4 The financial office shall record a concurrence decision on all directives (Chief Financial Officer for Agency-level directives; Center Chief Financial Officer for Center-level directives).
4.3.7.5 The human resources office shall record a concurrence decision on all directives (Human Capital Management for Agency-level directives; Center Human Resources/Human Capital Management for Center-level directives).
4.3.7.6 The procurement office shall record a concurrence decision on all directives (Procurement for Agency-level directives; Center Procurement/Acquisition for Center-level directives).
4.3.7.7 The information officer office shall record a concurrence decision on all directives (Information Officer for Agency-level directives; Center Information Officer/Information Technology for Center-level directives).
4.3.7.8 If, during the concurrence process, a reviewing official's nonconcurrence cannot be resolved with the Responsible Office, the Responsible Office shall document the nature of the impasse in the signature package.
4.3.7.9 The Deputy Administrator shall be the decision authority for any impasse with a mandatory concurring office (Office of the General Counsel, Office of the Chief Financial Officer, Office of Human Capital Management, or Office of Procurement).
4.3.7.10 When OICs and Center Directors do not respond (concur/nonconcur) on Agency-level directives by established suspense dates, MSD will notify respective OICs and CDs that a response is past due and grant a one-day extension for a response.
4.3.7.11 Reviewing offices may request an extension in advance of the established suspense date directly with the responsible office. The responsible office determines the number of days for the extension.
4.3.8 Signature Package for Agency-level Directives
4.3.8.1 The Responsible Office shall prepare a final signature package that includes the following official files:
a. Action Document Summary (ADS) to include the following:
(1) Evidence of concurrences from reviewing organizations and the concurrence of the responsible OIC.
(2) Administrator's Headquarters Action Tracking (HATS) ID (e.g., A/2015-00344).
(3) HATS due date.
(4) Quality Control Liaison's (QCL) name, number, and date of QCL review.
(5) Special Instructions (if any).
(6) DM's name and number.
b. ADS' Executive Summary to include the following:
(1) Purpose and justification for new requirement(s).
(2) Summary of significant changes if directive is being revised.
(3) Summary of significant comments received during the review.
(4) Summary of nonconcurrence(s) and attempts toward resolution, per 4.3.8.2 and 4.3.8.3.
(5) Cost/benefit impacts for new resources that may be needed and a justification for why resources need to be expended to identify unfunded mandates.
Note: Unresolved proposed unfunded mandates are coordinated with the IFRB for resolution.
(6) Strategic impact (if any).
(7) Description of Presidential initiative/external action (if any).
c. The original of the proposed directive.
d. A copy of the directive's review report of all comments and dispositions.
e. Any additional documents that convey executive direction and supporting material (e.g., e-mails and/or verification matrices).
f. One copy of each directive to be cancelled by the proposed directive when it is approved.
Note: See package assembly instruction in Verification Matrix Table A in Appendix A.
4.3.8.2 If any reviewing official has nonconcurred on the directive, the Responsible Office shall document the disagreement as part of the Executive Summary of the signature package, including:
a. An explanation for the nonconcurrence.
b. A discussion of how the Responsible Office attempted to resolve the impasse and the outcome of those attempts.
c. The reason(s) the impasse remains unresolved.
d. The recommendation of the Responsible Office.
Note: Impasses related to costs/benefits information will be coordinated with the respective governing council.
4.3.8.3 If an impasse is reached between the Responsible Office and the Inspector General, the Responsible Office shall also document the impasse in the Executive Summary of the signature package.
4.3.8.4 The DM shall process the final package for signature according to approved local procedures.
4.3.9 Signature Packages for Center-level directives. Center Responsible Offices shall use established Center instructions to prepare signature packages for Center-level directives.
4.3.10 Final Approval
4.3.10.1 NPDs are signed by the NASA Administrator. NPRs are concurred on by the requesting OIC after review is complete and prior to receiving approvals by officials within the Administrator's office and the NASA Administrator to publish the NPR. CPDs and CPRs are signed by CDs or designees. After receiving all signatures (e.g., approvals and concurrences) a directive becomes an official NASA directive and is controlled in an electronic documentation library. Agency-level directives are controlled in NODIS. Center-level directives are controlled in electronic libraries established at each Center and are linked to NODIS.
4.4.1 Responsible Offices shall submit a written justification via email to MSD for the cancellation or expiration of a directive.
4.4.2 Responsible Offices that need to revise an existing directive to reflect changes in policy or procedural requirements shall submit the directive for review and approval in the same manner as a new directive (see paragraph 4.3).
Note 1: If the change to the directive only impacts limited, discrete portions (paragraphs) of the directive, the Responsible Office may elect to only submit the paragraph changes for formal review and approval, as opposed to the entire document. However, if MSD determines the changes are too extensive for a paragraph review, a review of the entire document may be required.
Note 2: The cost/benefit impacts (see paragraph 4.3.6.1f) for revised directives need only discuss the impact of the revisions, not existing requirements.
Note 3: NPRs do not cancel NPDs, and CPRs may not cancel CPDs.
4.4.3 If a directive is due to expire, but the directive is current, necessary, and requires no changes, or only minor administrative changes (e.g., updates to document citations, office or position titles, references to other established policy or externally mandated instructions that may not be altered or edited, or substantive administrative changes that do not add or change policy or requirement), the Responsible Office shall request a revalidation for a period not to exceed five years, using the following process:
Note 1: Cost/benefit impacts (see paragraph 4.3.6.1f) are not required for revalidations.
Note 2: Revalidations will not be allowed on any directive that does not meet the content requirements in this NPR.
a. The Responsible Office provides an e-mail request to MSD with a list of the changes (or an electronic version of the directive showing the administrative changes).
b. MSD reviews the directive for compliance with this NPR and coordinates corrections with the Responsible Office.
c. MSD provides e-mail notification of the intent to revalidate the directive to DMs on an exception-only basis.
d. If there are no objections, MSD revalidates the directive, summarizes the administrative changes in the directive's change log, and extends the expiration date for another five years.
e. If there are objections, MSD determines whether the objections are valid and either approves the revalidation or requests that the document be submitted for formal review and approval.
4.4.4 If the Responsible Office needs to make minor administrative corrections (e.g., fixing typographical errors) during the life cycle of the directive, the Responsible Office may submit a request for administrative changes, via e-mail to MSD.
Note: Only the review and concurrence of MSD is needed to make administrative corrections. Administrative corrections should not change requirements. However, if MSD determines that these corrections do change requirements, a limited review of the changes/corrections may be required.
4.4.5 For Center-level directives, Center instructions apply.
4.5.1 For NIDs, the Responsible Office shall:
a. Secure written approval from the OIC and other approvals, as established within the local process for the proposed interim directive (policy/requirement).
b. Document the urgent requirement for issuing an interim directive.
c. Submit the interim directive to the DM or designated organization for processing.
d. Obtain concurrence from the Office of the General Counsel for legal review.
e. Obtain concurrence from the Office of Human Capital Management to satisfy the Agency's obligation, in accordance with E.O. 13522, to provide the Agency's union representatives with a 30-day national consultation period.
f. Obtain concurrence from the Office of Procurement if the NID impacts NASA contracts, contractors, grants, or grantees.
g. Obtain concurrence from the Office of the Chief Financial Officer to ensure proper financial consideration.
Note: For Agency-level interim directives, responsible offices should consult MSD or the DM when preparing NIDs.
4.5.2 MSD shall include NIDs in the NODIS Library.
4.5.3 For CIDs, Responsible Offices shall follow Center instructions for coordinating and publishing, to include satisfying the requirements in accordance with E.O. 13522, to provide local union representatives with consultation period.
Note: Consult your Center DM when preparing CIDs.
4.6.1 When a Responsible Office determines that a NASA Plan, Manual, Technical Standard, Work Instruction, or Other Policy Document is useful, but not appropriate for inclusion as a directive, the Responsible Office may use hyperlinking to make the related documentation available through NODIS. See Appendix D for description of these document types.
a. For Agency-level directives, the Responsible Office shall coordinate this with MSD.
b. For Center-level directives, the Responsible Office shall coordinate this with the Center's DM.
4.7.1 MSD shall manage Agency-level directives case files that include all the material included in the Approving Official's Signature Package.
Note: See paragraph 4.3.8.1 for a list of materials that are included in a signature package and Appendix C Verification A for assembly of this material. 4.7.2 Center-level directives case files shall be managed according to the Center's process.
Agency-level directive. A NASA directive with Agency-wide applicability; i.e., NASA Policy Directives (NPDs), NASA Procedural Requirements (NPRs), and NASA Interim Directives (NIDs).
Audit Liaison Representative (ALR). An individual appointed by an Official-in-Charge (OIC) or a Center Director to implement and coordinate audit liaison, resolution, and followup activities within each organizational component and Center. ALRs are the primary point of contact to represent management for each specific GAO or OIG audit for which the OIC has principal program or funding responsibility. Detailed responsibilities of the ALR are described in NPD 9910.1.
Authority. The source from which a requirement is drawn; the responsible organization imposing the requirement.
Center-level directive. A NASA directive with Center-specific applicability; e.g., Center Policy Directives (CPDs); Center Procedural Requirements (CPRs); and Center Interim Directives (CIDs).
Center Interim Directive (CID). Documents an immediate, short-term statement of the Center's policies, requirements, and responsibilities for implementation.
Center Policy Directive (CPD). Documents Center-specific policy requirements and responsibilities.
Center Procedural Requirements (CPR). Documents/establishes Center-specific procedural requirements and responsibilities to implement the policies and procedural requirements defined in related NPDs, NPRs, or CPDs.
Concurrence Decisions:
Contextual information. Background information, such as history or rationale for a requirement, or other descriptive information or examples that help clarify the actual requirements statement.
Disposition of Comments. A documented response explaining how reviewers' comments will be applied to the draft directive.
Guidance. A statement of expectation that does not mandate compliance.
NASA Directive. A NASA document that transmits information required by law, the President, the NASA Administrator, or other senior NASA official that applies to all NASA activities or to a single NASA Center on how they initiate, govern, or control actions. NASA directives include: NASA Policy Directives (NPD), NASA Procedural Requirements (NPR), NASA Interim Directives (NID), Center Policy Directives (CPD), Center Procedural Requirements (CPR), and Center Interim Directives (CID).
NASA Directives System. The tools and processes used to create and promulgate NASA Agency-level directives.
NASA Interim Directives (NID). Documents an immediate, short-term statement of the Agency's policies, requirements, and identifies responsibilities for implementation.
NASA Online Directives Information System (NODIS). A full-function, Web-based document management system (DMS) with a separate library for the search and retrieval of approved directives and related policy documents. The NODIS DMS is used for the creation, review, revision, concurrence, approval, publication, and maintenance of Agency-level directives, and the generation of associated reports. The NODIS Library provides for full text searching of Agency- and Center-level directives. It also provides links to other policy documents governing the Agency, including: NASA Technical Standards, Code of Federal Regulations, Executive Orders, Federal Register, OMB Circulars, Congressional Records, the U.S. Code, Congressional Bills, and the Catalog of U.S. Government Publications.
NASA Policy Directive (NPD). Documents Agency policy statements that describe what is required by NASA management to achieve NASA's vision, mission, and external mandates and who is responsible for carrying out those requirements.
NASA Procedural Requirements (NPR). Documents Agency requirements to implement NASA's policy as delineated in an associated NPD.
Note. Describes supplemental information useful to the reader. In some cases, more than one note is provided if additional information is needed to either aid the reader or to point the reader to information that is available in more detail elsewhere.
Policy. Describes the philosophies, fundamental values, and general direction of the Agency or Center and are used to determine present and future decisions. Because established policies are general in nature, they may need more specific requirements established in procedural requirements for full implementation.
Requirement. A statement of mandatory instruction that an employee or organization has to perform or a statement of form or function that a piece of equipment or system has to meet.
Responsible Office. The office that has responsibility for the development, maintenance, and verification of a directive.
Revalidation. The process for renewing a NASA directive when the directive is current and necessary and requires no changes or only minor administrative changes (e.g., updates to document citations, office or position titles, or references to other established policy or externally mandated instruction that may not be altered/edited).
Unfunded Mandates.
Unresolved Unfunded Mandates. UFMs that cannot be successfully resolved between NASA Centers, HQ Functional Organizations, and the responsible office issuing the mandate.
Verification. The process of proving or demonstrating that requirements have been satisfactorily met.
Waiver. A written authorization to depart from a specific directive requirement.
| AA | Assistant Administrator, Associate Administrator |
| ALR | Audit Liaison Representative |
| APMC | Agency Program Management Council |
| CD | Center Director |
| CID | Center Interim Directive |
| CPD | Center Policy Directive |
| CPR | Center Procedural Requirements |
| COR | Contracting Officer Representative |
| DM | Directives Manager |
| DMS | Document Management System |
| EC | Executive Council |
| HATS | Headquarters Action Tracking System |
| IFRB | Integrated Functional Review Board (e.g., UFM) |
| JPL | Jet Propulsion Laboratory (an FFRDC) |
| MSD | Mission Support Directorate |
| NASA-STD | NASA Technical Standard |
| NHQ | NASA Headquarters |
| NID | NASA Interim Directive |
| NODIS | NASA Online Directives Information System |
| NPD | NASA Policy Directive |
| NPR | NASA Procedural Requirements |
| NRRS | NASA Records Retention Schedules |
| OCFO | Office of the Chief Financial Officer |
| OGC | Office of the General Counsel |
| OHCM | Office of Human Capital Management |
| OIC | Official-in-Charge |
| QCL | Quality Control Liaison |
| UFM | Unfunded Mandates |
| U.S.C. | United States Code |
D.1 NASA directives work in conjunction with other NASA documents, such as plans, manuals, NASA Technical Standards, work instructions, and other policy documents. NASA directives provide the overarching requirements which serve as the framework for lower-level NASA internal organizational and task requirements.
D.1.1 Relationship between NASA Directives and Plans
D.1.1.1 Planning documents, such as Mission Directorate implementation plans, the Mission Support Implementation Plan, and the Human Capital Plan (described in NPD 1000.0, Strategic Management and Governance Handbook), and program/project plans typically describe activities focused in a discrete area. Directives establish the master requirements applicable to all entities across NASA, while plans describe goals, objectives, and requirements applicable to very specifically defined elements of NASA.
D.1.1.2 Plans are typically developed, approved, and controlled outside of the NASA Directives System, except as follows:
a. NASA Plans (i.e., NASA Strategic Plan (NPD 1001.0), Continuity of Operations Plan, Emergency Preparedness Plan, Safety, Health, Environmental Plan, etc.), derived by law, have Agency-level and Center-specific applicability and are controlled in the NASA Directives System.
b. Plans with discrete functional or programmatic applicability (i.e., Implementation Plans, Program and Project Plans, Software Engineering Improvement Plan(s), and Software Training Plan(s)) are controlled at the appropriate organizational level by the respective responsible NASA Official.
D.1.2 Relationship between NASA Directives and Manuals
D.1.2.1 Manuals typically identify process requirements for employees within a single work unit or functional area.
D.1.2.2 Manuals may supplement NASA directives and provide more instruction about how the provisions of those directives are carried out within the work unit or functional area. Manuals may also provide supplemental information about acceptable methods for implementing requirements, including lessons learned, suggested practices, instructions, and suggested performance measures. Manuals typically are written to a greater level of detail than NASA directives.
D.1.2.3 Manuals are typically developed, approved, and controlled outside of the NASA Directives System.
D.1.2.4 Manuals that implement NASA directives are typically hyperlinked to their associated NASA directives.
D.1.3 Relationship between Directives and NASA Technical Standards
D.1.3.1 NASA Technical Standards may be applied to programs/projects executed internally or under contract. Tailoring of these standards is a program/project responsibility and is to be approved by the governing Technical Authority.
D.1.3.2 NASA Technical Standards may also be referenced as guidance on acceptable methods for meeting requirements of NASA directives, lessons learned, and recommended practices.
D.1.3.3 NASA Technical Standards are developed, approved, and controlled by NPR 7120.10, Technical Standards for NASA Programs and Projects, rather than by this directive (NPR 1400.1).
D.1.4 Relationship between Directives and Work Instructions
D.1.4.1 Work instructions typically document the instructional requirements applied to an individual organization that define the processes used to deliver products or services to customers or to meet the organization's mission requirements.
D.1.4.2 Work instructions represent the translation of the Agency's strategic requirements and NASA directives down to a level of detailed application to individual employees or work groups.
D.1.4.3 Work instructions are typically developed, approved, and controlled outside of the NASA Directives System. Typically, the requirements for work instructions fall under the scope of the NASA Management System, as defined in NPD 1280.1, NASA Integrated Management System Policy. These documents may be included in the directives system's documentation libraries.
D.1.5 Relationship between Directives and Other Policy Documents (i.e., NASA Policy Statements (NPS), NASA Policy Instructions (NPI), and NASA Advisory Implementing Instructions (NAII))
D.1.5.1 NPSs are statements that reiterate the Agency's commitment to its defined course or method of action for adhering to external requirements.
D.1.5.2 NPIs are instructions that describe how to perform a definite course or method of action that guide and determine present and future decisions.
D.1.5.3 NAIIs are Agency-level documents that consolidate sets of principles, guidance, and instructions applicable to a particular activity. An NAII should be used when the procedural requirements for conducting the activity are not specified at an Agency level (such as through an NPR), but there are principles, guidance, and instructions that are considered when developing processes at the Center or organization level. An NAII is also used to provide direction relating to the implementation of responsibilities under NPDs or NPRs.
View NPD 1400.1, Documentation and Promulgation of NASA Internal Requirements as a sample.
View this NPR as a sample.
F.1.1 HQ and Center Responsible Offices will need to omit requirements (i.e., shall statements) from the policy section of NPDs and CPDs and specify specific requirements, not general responsibilities, in NPRs and CPRs with broad application. There is no cost or burden associated with these requirements as applicability begins when these documents are revised. The benefit of omitting shall statements from policy provides clear Agency direction.
F.1.2 HQ and Center Responsible Offices will need to include the language, "a Federally Funded Research and Development Center (FFRDC)" in parenthesis wherever JPL appears in their respective directives when these documents are created or revised. Including this language clarifies that JPL is not a NASA Center, but an FFRDC.
MSD and Centers whose directives reference JPL will need to adjust the applicability language in all approved Agency-level and Center-level directives that apply to JPL to include the language, "a Federally Funded Research and Development Center" in parenthesis wherever JPL appears in the directive. Including this language in approved directives clarifies that JPL is not a NASA Center, but an FFRDC.
Agency DMs will need to ensure that directive originators adhere to the new changes in NPR 1400.1 as respective directives are up for revision. There are no costs associated with this requirement as processes are already in place to confirm that directives comply with NPR 1400.1. The benefit of implementing these revisions is that it provides improved clarification of requirements.
Figure 7, Integrated Function Review Board Process