![[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 Technical Standards
2.1 The NASA Chief Engineer
2.2 NASA Headquarters Offices that Sponsor Development of Technical Standards
2.3 Mission Directorates and Program and Project Managers
2.4 Center Directors
3.1 Selection of Technical Standards
3.2 Tailoring of Technical Standards
3.3 Use of Technical Standards
3.4 Agency's Annual Report on Standards
4.1 NASA Participation in Standards Development with Voluntary Consensus Standards Bodies and Other Government Agencies
4.2 Development of NASA Technical Standards
4.3 Maintaining NASA Technical Standards
4.4 Processes for Developing and Maintaining Technical Standards
4.5 Designation of NASA-Endorsed Technical Standards
a. This directive supports the implementation of the technical standards aspects of the parent directive NPD 7120.4.
b. This directive establishes responsibilities, requirements, and processes for:
(1) Selecting, tailoring, and using technical standards as program and project requirements, encouraging commonality and conformity in use across NASA programs and projects, and mandating use of specific technical standards when warranted.
(2) Developing technical standards, complying with Federal requirements for participating in the development and revision of voluntary consensus standards, and designating NASA-endorsed technical standards.
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)), other contractors, recipients of grants and cooperative agreements, and parties to other agreements only to the extent specified or referenced in applicable contracts, grants, or agreements.
b. Technical standards and this directive are also applicable to programs and projects managed under NPR 7120.5, NPR 7120.7, and NPR 7120.8.
c. 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 or statement of fact.
d. In this directive, "standard or technical standard" is defined in Appendix A and refers to various means used to achieve and maintain the desired levels of compatibility, interchangeability, commonality, or conformity.
e. In this directive, "NASA technical standards" refer to technical standards, specifications, and handbooks developed and approved by NASA Headquarters offices for Agency-wide use, assigned a prefix of "NASA-STD-," "NASA-SPEC-," or "NASA-HDBK-," respectively, to the unique document number.
f. This directive is limited to NASA technical standards sponsored by Headquarters offices and does not apply to development of Center-specific and/or program- and project-specific technical standards.
g. In this directive, all document citations are assumed to be the latest version unless otherwise noted.
a. Functions of Secretary and Institute, 15 U.S.C. ยง 272(b), as amended.
b. OMB Circular No. A-119, Federal Participation in the Development and Use of Voluntary Consensus Standards and in Conformity Assessment Activities, as revised January 27, 2016, at Federal Register Vol. 81, No. 17, page 4673, accessible at https://www.whitehouse.gov/sites/default/files/omb/inforeg/revised_circular_a-119_as_of_1_22.pdf, with the revised Circular text beginning at page 12.
c. NPD 1000.0, NASA Governance and Strategic Management Handbook.
d. NPD 1000.3, The NASA Organization.
e. NPD 1400.1, Documentation and Promulgation of Internal NASA Requirements and Charters.
f. NPD 7120.4, NASA Engineering and Program/Project Management Policy.
a. NPR 1441.1, NASA Records Management Program Requirements.
b. NPR 7120.5, NASA Space Flight Program and Project Management Requirements.
c. NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements.
d. NPR 7120.8, NASA Research and Technology Program and Project Management Requirements.
e. NPR 8715.3, NASA General Safety Program Requirements.
f. NPR 8900.1, NASA Health and Medical Requirements for Human Space Exploration.
g. NASA-STD 8709.20, Management of Safety and Mission Assurance Technical Authority (SMA TA) Requirements.
Compliance with this directive is verified by submission to responsible NASA officials, as defined in Chapter 2, of the products identified in requirement statements in this directive and by internal and external controls. Internal controls are consistent with processes defined in NPD 1200.1. Internal controls include surveys, audits, and reviews conducted in accordance with NPD 1210.2. External controls may include external surveys, audits, and reporting requirements.
1.1.1Technical standards are important to the Agency for many reasons, including but not limited to:
a. Complying with legal and other requirements.
b. Citing technical requirements or specifications in contracts, grants, and other types of agreements to ensure contractors are held accountable for delivering the products or services to achieve program or project needs.
c. Capturing lessons learned to provide a rationale for recommendations and requirements or to share success factors and new technology.
d. Facilitating engineering excellence in development studies and operations.
e. Providing a common base for interoperability.
f. Preventing conflict and duplication of effort.
g. Fostering and supporting reuse and sharing.
1.2.1 A technical standard is not "self-imposing," i.e., it is not mandatory for use by a performing entity unless:
a. Required by U.S. law or NASA directive, or
b. Invoked by other NASA requirements documents (e.g., contracts, including but not limited to, the JPL (FFRDC) contract, program and project documents, grants, and agreements).
1.2.2 Requirements in technical standards and specifications are identified by using the word "shall" and denote mandatory compliance by programs and projects when selected and used as program and project requirements.
Note: When developing NASA technical standards, endorsing voluntary consensus standards, or invoking them as requirements, the following should be considered: the potential effect on the economy and of applicable Federal laws and policies, including laws and regulations relating to antitrust, national security, small business, product safety, environment, metrication, technology development, international trade, intellectual property and copyright, privacy and security, and conflicts of interest.
1.2.3 Approved NASA technical standards are reviewed at least once every 5 years or as the need arises and revised, revalidated, inactivated for new design, editorially or administratively changed, or cancelled.
1.2.4 In NASA technical standards, verifiable requirement statements are numbered and indicated by the word "shall." Rationale for why the requirement is necessary should be provided for the user. To facilitate requirements selection and verification by NASA programs and projects, a Requirements Compliance Matrix is provided as an appendix in each NASA technical standard and specification. The Requirements Compliance Matrix should be used in coordination with the explanatory and guidance text in the body of the NASA technical standard or specification.
1.2.5 Technical standards are accessible at https://standards.nasa.gov.
Note: This chapter defines the roles and responsibilities of key officials in the technical standards management process. The roles and responsibilities of senior NASA management, along with fundamental principles of governance, are defined in NPD 1000.0 and further described in NPD 1000.3.
2.1.1 The NASA Chief Engineer serves as NASA's Standards Executive. The NASA Standards Executive, or designee:
a. Provides external coordination of NASA technical standards activities.
b. Provides NASA representation on the Interagency Committee for Standards Policy (ICSP).
c. Issues a call for information and submits NASA's annual report on voluntary consensus standard and conformity assessment activities to the Office of Management and Budget (OMB) through the National Institute of Standards and Technology (NIST).
2.1.2 The NASA Chief Engineer evaluates the effectiveness of NASA technical standards activities.
2.1.3 The NASA Chief Engineer coordinates and assesses Agency implementation of policy, procedural requirements, and activities for technical standards with other NASA Headquarters offices, Center Directors, and Technical Authorities.
2.1.4 The NASA Chief Engineer provides access to technical standards at https://standards.nasa.gov.
2.2.1 NASA Headquarters offices consult with voluntary consensus standards bodies and provide:
a. Adequate priority in budgets to support participation of employees in voluntary consensus standards development activities.
b. Input to the NASA Chief Engineer to support NASA's annual report to NIST.
2.2.2 NASA Headquarters offices develop processes to manage and approve the development and maintenance of NASA technical standards and participation in voluntary consensus standard activities within their areas of responsibility consistent with the requirements of this directive.
2.2.3 NASA Headquarters offices designate NASA-endorsed technical standards.
2.2.4 The NASA Chief Engineer, the Chief, Safety and Mission Assurance, and the Chief Health and Medical Officer serve as or may delegate Technical Authority for technical standards within their areas of responsibility.
2.2.5 NASA Headquarters offices periodically review Agency compliance with technical standards within their areas of responsibility.
2.3.1 Mission Directorates and program and project managers support the Agency's established processes for reviewing technical standards for technical accuracy and adequacy and provide comments when necessary.
2.3.2 Mission Directorates and program and project managers:
a. Consult with associated Technical Authorities to define the minimum set of technical authority standards and requirements to apply to programs and projects.
b. Seek formal approval from delegated Technical Authorities when tailoring defined technical authority standards and requirements.
c. Use requirements from technical standards in accordance with NPR 7120.5, NPR 7120.7,
NPR 7120.8, or NASA-STD 8709.20, observing and protecting Intellectual Property Rights (IPR) and managing classified national security and Sensitive But Unclassified (SBU) information.
2.4.1 Center Directors, or designees, adhere to established processes, including observing and protecting IPR and classified national security and SBU information, to:
a. Promote and authorize Center representatives who, at Government expense, participate on behalf of the Agency in the development and revision of voluntary consensus standards and other Government agency technical standards;
b. Develop and maintain NASA technical standards for which they have assigned responsibility;
c. Recommend technical standards for NASA endorsement; and
d. Report annually on Center participation in voluntary consensus standards and conformity assessment activities to the NASA Chief Engineer to support NASA's annual report to NIST.
2.4.2 Center Directors, or delegated Technical Authorities, in consultation with program and project managers, specify the minimum required set of associated technical standards for programs and projects and approve deviations and waivers for those standards applied to programs and projects.
3.1.1 Program and project managers, with delegated Technical Authority concurrence, shall select technical standards for use in defining program and project requirements based on effectiveness, suitability, currency, and applicability for use as program and project requirements according to the following order of priority:
a. Technical standards mandated by law.
b. Technical standards designated as mandatory by NPDs and NPRs.
c. Technical standards necessary to promote mission success and engineering excellence. When all other factors are the same, select in the following order of precedence:
(1) Voluntary consensus standards unless inconsistent with applicable laws or NASA NPDs and NPRs, technically inadequate, or otherwise impractical.
(2) NASA technical standards or other Government agency technical standards (government-unique standards) when voluntary consensus standards do not exist or use would not be as effective as other standards in meeting NASA's needs.
Note: Information is continually exchanged to ensure proper balance and ensure issues and concerns are properly elevated up the authoritative chain for resolution. When technical decisions result in residual safety and/or mission success risk, formal concurrence by the responsible Technical Authorities (Engineering, Safety and Mission Assurance, and/or Health and Medical) is required; refer to NPR 7120.5, section 3.3, and to section 3.4 for the dissenting opinion process.
Note: Promote commonality in the use of technical standards across NASA. As a first order, consider NASA-endorsed technical standards, accessible after login at https://standards.nasa.gov, Endorsed Standards.
3.1.2 Program and project managers shall select current versions of technical standards except when justified as impractical or incompatible with requirements and concurred with by the delegated Technical Authority.
3.1.3 Program and project managers, or designees, shall review lessons learned, including but not limited to those in the NASA Lessons Learned Information System, for applicability to current technical standards applications.
3.1.4 Program and project managers, NASA Headquarters offices, and Center Directors shall give preference to performance standards over prescriptive standards. Note: It is understood that all of the requirements contained within a NASA technical standard may not be applicable to a specific program or project.
3.2.1 NASA Headquarters offices and program and project managers shall:
a. Tailor, when necessary, technical standards and document necessary changes to meet specific application needs and to avoid over- or under-specification of requirements for formal approval by the delegated Technical Authority.
b. When a technical authority requirement is invoked by OCE, OSMA, and OCHMO documents (e.g., a NASA directive, Center institutional document, or other NASA requirements document) (e.g., a contract, standards cited as program or project requirements), document the traceability of the tailored requirement to the original requirement and obtain formal approval from the delegated Technical Authority as required by NPR 7120.5, NPR 7120.7, NPR 7120.8, NPR 8900.1, and for Safety and Mission Assurance, by NPR 8715.3 and NASA-STD 8709.20.
Note: Tailoring of technical standards required by law or Federal regulation requires General Counsel and NASA Technical Authority involvement.
3.3.1 Program and project managers shall:
a. Register to receive notification of changes to technical standards invoked as program and project requirements at https://standards.nasa.gov.
b. Review changes to invoked technical standards to determine the need for revision of program and project requirements or tailoring of technical standards.
NASA Headquarters offices and Center Directors, or their designees, shall submit to the NASA Chief Engineer input for NASA's annual report to NIST as required by OMB Circular No. A-119 describing NASA's use of voluntary consensus standards, participation by NASA-authorized representatives in the development or revision of voluntary consensus standards, and conformity assessment activities based on guidance issued by NIST.
NASA Headquarters offices shall determine, when a need is identified, if voluntary consensus standards or other Government agency standards exist or are in development that meet or can be adapted to meet NASA's needs.
4.2.1 NASA Headquarters offices that sponsor NASA technical standards shall consider development of a new NASA technical standard when the following criteria are met:
a. A search and evaluation of similar technical standards has determined that established voluntary consensus standards or other Government agency technical standards do not exist, are not in development, or are not suitable for adapting (tailoring) to meet NASA technical needs;
b. All basic research and testing have been completed to facilitate the development of the NASA technical standard within a 12-month timeframe and within allocated funding;
c. A NASA technical standard is necessary to establish multi-Center practices and processes that have been identified, such as problem areas or areas contributing to past incidents, near misses, failures, or reduced mission capability; and
d. A NASA technical standard is necessary to capture NASA-unique best practices, needs, and lessons learned
4.2.2 NASA Headquarters offices that sponsor NASA technical standards shall provide the location or a link to the website of documents whose requirements are incorporated as applicable ("by reference" per OMB Circular No. A-119) documents.
4.2.3 NASA Headquarters offices shall conduct Agency-wide technical reviews for adequacy and accuracy of each proposed document.
4.2.4 NASA Headquarters offices shall document and disposition all comments received from reviewers and provide the dispositions to all reviewers.
4.2.5 NASA Headquarters offices shall ensure that unresolved comments relative to NASA technical standards are appealed to the next higher level of authority, leading up to the responsible NASA Headquarters office in accordance with the process for handling dissenting opinions in NPR 7120.5.
4.3.1 NASA Headquarters offices, or designees, shall:
a. Review their NASA technical standards and document the results at least once every 5 years for relevancy, currency, technical accuracy and adequacy, conflict with or duplication of other requirements, changes in scope, and feasibility of replacing the existing NASA technical standard with, or converting it to, a voluntary consensus standard and inactivating for new design or cancelling the NASA technical standard.
b. Establish, document, and implement a configurationally controlled process to control maintenance (e.g., revalidation, revision, inactivation, changes, cancellation) of NASA technical standards.
c. Maintain NASA technical standards in accordance with NPR 1441.1.
4.4.1 NASA technical standards development for Office of the Chief Engineer and the Office of the Chief Health and Medical Officer follows the direction provided by the NASA Chief Engineer.
Note: The current directions for engineering technical standards and health and medical program and project technical standards are provided at https://standards.nasa.gov/sites/default/files/NASA-NTSP-1.pdf.
4.4.2 NASA technical standards development for safety and mission assurance follows the direction provided by the NASA Chief, Safety and Mission Assurance.
Note: The current directions for safety and mission assurance standards are provided at http://nodis3.gsfc.nasa.gov/HQDQMS_Docs/QMS/HQ_OWI_1410_GA000_002_F_.pdf.
4.4.3 NASA technical standards development for information technology follows the direction provided by the NASA Chief Information Officer.
Note: The current directions for information technology standards are provided at http://nodis3.gsfc.nasa.gov/displayCA.cfm?t=NPD&c=2800&s=1.
4.5.1 NASA Headquarters offices shall identify and approve technical standards as NASA-endorsed technical standards based on the following criteria:
a. The technical standard is approved in accordance with a documented, approved process and is reviewed and updated if necessary on a periodic basis; b. The technical standard addresses common, high-level functions that are considered by projects across or within a given program or elements across or within a given project;
Note: Applicability of NASA-endorsed technical standards may be specified by NASA Headquarters offices.
c. The technical standard leverages sound engineering practices representative of the best, most current, available, and proven technical knowledge and testing;
d. The technical standard is suitable for wide acceptance by NASA, industry, and other government agencies to ensure proven, consistent, common practices in the discipline area are applied.
Note: NASA-endorsed technical standards do not include program- or project-specific or Center documents, Center-specific laboratory procedures or processes, or procurement specifications.
Note: The list of NASA-endorsed technical standards accessible after login at https://standards.nasa.gov, Endorsed Standards, will be updated as necessary using the above criteria.
Agency. The National Aeronautics and Space Administration (NASA).
Applicable Documents. Citations consisting of documents incorporated by reference in the text of the directive and contain provisions or other pertinent requirements directly related to and necessary for the performance of the activities specified by the directive. (Source: NPR 1400.1.)
Conformity Assessment. A demonstration, whether directly or indirectly, that specified requirements relating to a product, process, system, person, or body are fulfilled. Conformity assessment includes sampling and testing, inspection, supplier's declaration of conformity, certification, and management system assessment and registration. Conformity assessment also includes accreditation of the competence of those activities. (Source: OMB Circular No. A-119.)
Consensus. A general agreement, but not necessarily unanimity. During the development of consensus, comments and objections are considered using fair, impartial, open, and transparent processes. (Source: OMB Circular No. A-119.)
Government-Unique Standard. A standard developed by and for use by the Federal government in its regulations, procurements, or other program areas specifically for government use (i.e., it is not generally used by the private sector unless required by regulation, procurement, or program participation). The standard was not developed as a voluntary consensus standard. (Source: OMB Circular No. A-119.)
Handbook. A guidance document that provides engineering information; lessons learned; possible options to address technical issues; classification of similar item, materials, or processes; interpretative direction and techniques; and any other type of guidance information that may help the Government or its contractors in the design, construction, selection, management, support, or operation of systems, products, processes, or services. (Source: MIL-STD-967.) Also, a how-to document containing procedural, technical, engineering, or design information or data about materials, processes, practices, or methods. Although NASA handbooks may contain "shall" statements, they are not intended to be requirements documents. Handbooks, or portions thereof, containing procedural or process requirements may be cited in contract, program, and other Agency documents.
Impractical. Includes circumstances in which such use (as defined in this section) would fail to serve the Agency's regulatory, procurement, or program needs; be infeasible; be inadequate, ineffectual, inefficient, or inconsistent with the Agency's mission or the goals of using voluntary consensus standards; be inconsistent with a provision of law; or impose more burdens, or be less useful, than the use of another standard. (Source: OMB Circular No. A-119.)
NASA-Endorsed Technical Standards. Proven technical standards identified and recommended by NASA Headquarters offices for particular types of applications and should be considered first for use in developing technical requirements for current and future NASA programs and projects. NASA Technical Standards. Consist of technical standards, specifications, and handbooks developed and approved by NASA Headquarters offices for Agency-wide use. NASA technical standards are assigned a prefix of "NASA-STD-," "NASA-SPEC-," or "NASA-HDBK-," respectively, to the unique document number.
Other Government Agency Standards. Technical standards originated and published by Government agencies other than NASA (e.g., military (MIL), Federal (FED), Department of Defense (DoD)).
Performance Standard. A standard that states requirements in terms of required results, but without stating the methods for achieving required results; may define the functional requirements for an item, operational requirements, and/or interface and interchangeability characteristics; also may be viewed in juxtaposition to a prescriptive standard. (Source: OMB Circular No. A-119.)
Prescriptive Standard. A standard that may specify design requirements such as materials to be used, how a requirement is to be achieved, or how an item is to be fabricated or constructed. (Source: OMB Circular No. A-119.)
Reference Documents. 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. (Source: NPR 1400.1.)
Specification. A document that prescribes, in a complete, precise, verifiable manner, the requirements, design, behavior, or characteristics of a system or system component. (Source: NPR 7123.1.)
Standard or Technical Standard. Includes the following:
a. Common and repeated use of rules, conditions, guidelines, or characteristics for products or related processes and production methods, and related management systems practices;
b. The definition of terms; classification of components; delineation of procedures; specification of dimensions, materials, performance, designs, or operations; measurement of quality and quantity in describing materials, processes, products, systems, services, or practices; test methods and sampling procedures; formats for information and communication exchange; or descriptions of fit and measurements of size or strength; and
c. Terminology, symbols, packaging, marking, or labeling requirements as they apply to a product, process, or production method. (Source: OMB Circular No. A-119.)
Tailoring. The process used to adjust or seek relief from a prescribed requirement to accommodate the needs of a specific task or activity (e.g., program or project). The tailoring process may result in the generation of deviations and waivers depending on the timing of the request. (Source: NPR 7120.5.)
Technical Authority. Part of NASA's system of checks and balances that provides independent oversight of programs and projects in support of safety and mission success through the selection of individuals at delegated levels of authority. These individuals are the Technical Authorities. Technical Authority delegations are formal and traceable to the Administrator. Individuals with Technical Authority are funded independently of a program or project. (Source: NPR 7120.5.)
Technical Authority Requirements. Requirements invoked by OCE, OSMA, and OCHMO documents (e.g., NPRs or technical standards cited as program or project requirements) or contained in Center institutional documents. These requirements are the responsibility of the office or organization that established the requirement unless delegated elsewhere. (Source: NPR 7120.5.)
Technical Requirements. 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. (Source: NPR 1400.1.)
Use (as in Use of a standard). Incorporation of a standard in whole, in part, or by reference for procurement purposes; inclusion of a standard in whole, in part, or by reference in regulation(s); or inclusion of a standard in whole, in part, or by reference in other mission-related activities. (Source: OMB Circular No. A-119, Federal Participation in the Development and Use of Voluntary Consensus Standards and in Conformity Assessment Activities.) Refer to http://archives.gov/federal-register/write/handbook/chapter-6.pdf for information on incorporation by reference.
Voluntary Consensus Standard. A type of standard developed or adopted by voluntary consensus standards bodies, through the use of a voluntary consensus standards development process defined in the definition of voluntary consensus standards bodies in this section. These bodies often have intellectual property rights (IPR) policies that include provisions requiring that owners of relevant patented technology incorporated into a standard make that intellectual property available to implementers of the standard on a non-discriminatory and royalty-free or reasonable royalty terms (and to bind subsequent owners of standards essential patents to the same terms). A standard that includes patented technology needs to be governed by such policies, which should be easily accessible, set out clear rules governing the disclosure and licensing of the relevant intellectual property, and take into account the interests of all stakeholders, including the IPR holders and those seeking to implement the standard. (Source: OMB Circular No. A-119.)
Voluntary Consensus Standards Body. A type of association, organization, or technical society that plans, develops, establishes, or coordinates voluntary consensus standards using a voluntary consensus standards development process that includes the following attributes or elements:
a. Openness: The procedures or processes used are open to interested parties. Such parties are provided meaningful opportunities to participate in standards development on a non-discriminatory basis. The procedures or processes for participating in standards development and for developing the standard are transparent.
b. Balance: The standards development process should be balanced. Specifically, there should be meaningful involvement from a broad range of parties, with no single interest dominating the decision-making.
c. Due process: Due process shall include documented and publicly available policies and procedures, adequate notice of meetings and standards development, sufficient time to review drafts and prepare views and objections, access to views and objections of other participants, and a fair and impartial process for resolving conflicting views.
d. Appeals process: An appeals process shall be available for the impartial handling of procedural appeals.
e. Consensus: Consensus is defined as general agreement, but not necessarily unanimity. During the development of consensus, comments and objections are considered using fair, impartial, open, and transparent processes. (Source: OMB Circular No. A-119).
| DoD | Department of Defense |
| FED | Federal |
| FFRDC | Federally Funded Research and Development Center |
| HDBK | Handbook |
| IPR | Intellectual Property Rights |
| JPL | Jet Propulsion Laboratory (an FFRDC) |
| MIL | Military |
| NASA | National Aeronautics and Space Administration |
| NIST | National Institute of Standards and Technology |
| NPD | NASA Policy Directive |
| NPR | NASA Procedural Requirements |
| OMB | Office of Management and Budget |
| SBU | Sensitive But Unclassified |
| SMA | Safety and Mission Assurance |
| SPEC | Specification |
| STD | Standard |
| TA | Technical Authority |
| U.S.C | United States Code |
C.1 NPD 1200.1, NASA Internal Control.
C.2 NPD 1210.2, NASA Surveys, Audits, and Reviews Policy.
C.3 NPR 1400.1, NASA Directives and Charters Procedural Requirements.
C.4 NPR 7123.1, NASA Systems Engineering Processes and Requirements.
C.5 MIL-STD-967, Defense Handbooks Format and Content.