| Traceability of Constellation (CxP) Document: CxP 70059 to SMARTS Requirements | ||||||||||
| Filter Settings: Tech Authority: Any | OSMA Opinion: Any | CxP Implementation: Any | ||||||||||
| CxP Doc | CxP Doc Para | CxP Doc Req | Parent Doc Num | Parent Doc Para | Parent Req ID | Parent Req Text | Tech Auth | OSMA Opinion | CxP Impl'n | CxP Discipline |
| CxP 70059 | ||||||||||
| CxP 70059 | 0 | MGT-132 | NPD 8720.1B | 5.d.(4) | 13039 | Program and project managers are responsible for: Identifying the organization(s) that will maintain the Reliability and Maintainability data for the lifetime of the system and coordinating with the Center SMA functional manager to ensure that Reliability and Maintainability data is available for use as heritage data. (Requirement 13039) | S | Y | Y | RMS |
| RMS-117 | NPR 8735.1B | 1.2.4.a | 57144 | General Requirements: Responsibilities: Program, Project, and Operations/Institutional Managers shall: Review all contracts to ensure incorporation of GIDEP participation requirements to evaluate GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories (Requirement 57144). | S | Y | Y | RMS | ||
| SWA-128 | NASA-STD-8739.8 | 6.2.6 | 33249 | The software assurance manager shall assure that problems and risks are reported, recorded, addressed, and tracked to closure. (Requirement 33249) | S | Y | Y | SWA | ||
| SWA-129 | NASA-STD-8739.8 | 6.2.6 | 33249 | The software assurance manager shall assure that problems and risks are reported, recorded, addressed, and tracked to closure. (Requirement 33249) | S | Y | Y | SWA | ||
| CxP 70059 | 1.1 | MGT-1 | NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.1 | 33655 | The requirements of this Standard shall continue to be applicable after the safety-critical software has been released for operations. (Requirement 33655) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2 | 33656 | The software safety requirements to specify, develop, analyze, and test safety-critical software, shall apply to all changes made to the software or routine operational updates (e.g., mission specific database updates). (Requirement 33656) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.a | 1003 | POLICY: It is NASA policy to-- Protect the public, Astronauts and pilots, NASA workforce, and high-value equipment and property from potential harm as a result of NASA activities and operations by providing safe programs, technologies, operations, and facilities; and protect the environment. (Requirement 1003) | S | Y | Y | Mgmt | |||
| NPD 8700.1C | 5.e.1 | 1039 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Implement Agency SMA and Risk Management policies, guidelines, and standards and establish safety and mission-success requirements within their programs and projects. (Requirement 1039) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.02.1.a | 45566 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that their safety planning and direction; the development of safety requirements, safety policies, safety methodology, and safety procedures; and the implementation and evaluation of their safety programs achieve the safety requirements in this NPR (Requirement 45566). | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.02.1.d | 45569 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that employees are informed of any risk acceptance when the employees are the ones at risk. (Requirement 45569) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.03.1.a(1) | 45581 | Institutional and Programmatic Safety Requirements: Public Safety: Center Directors, project managers, supervisors and NASA employees shall: Eliminate risk or the adverse effect of NASA operations on the public, or provide public protection by exclusion or other protective measures where the risk or the adverse effect of NASA operations on the public cannot be eliminated. (Requirement 45581) | S | Y | Y | Mgmt | |||
| CxP 70059 | 1.1 | MGT-50 | NPD 8700.1C | 5.e.5 | 1086 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Designate an individual with specific responsibilities for coordinating/executing SMA efforts within the program/project. (Requirement 1086) | S | Y | Y | Quality |
| CxP 70059 | 1.13 | MGT-31 | NASA STD 8719.13B | 6.3.2.1 | 33609 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33609) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 5.8.1.2 | 33234 | Ensure that the retirement plan includes archival and eventual disposal of software assurance records and documents created over the life of the program/project in accordance with the requirements of NPR 1441.1, NASA Records Retention Schedules. (Requirement 33234) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.1(1) | 33251 | Each software provider shall establish and maintain a software assurance plan that addresses all software development and maintenance activities. (Requirement 33251) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.1 | 33254 | Conform to IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans. (Requirement 33254) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.3 | 33256 | If there is any conflict between Section 6.0 or Section 7.0 of this Standard and IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans, this Standard shall take precedence. (Requirement 33256) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.4.1 | 33258 | The provider shall submit any proposed deviations from or modification to the baselined software assurance plan to the acquirer as a formal change request. (Requirement 33258) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.6.1 | 33262 | Software assurance records shall be prepared, maintained, placed under configuration management, and contain the descriptions and results of software assurance activities, (e.g, audit reports, classification evaluations, milestone review, software assurance briefings, problem reporting tracking). (Requirement 33262) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.6.2 | 33263 | Software assurance records shall include recommended preventive measures, corrective actions, and lessons learned. (Requirement 33263) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.4.5 | 33314 | Software assurance shall collect and maintain software assurance records showing the participation of software assurance staff in verification and validation efforts, such as minutes, records, artifacts, and signature on test reports. (Requirement 33314) | S | Y | Y | SWA | |||
| NPR 8715.3C | 01.05.2.a | 45652 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: Addresses life-cycle, safety relevant functions and activities. (Requirement 45652) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.b | 45653 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project Managers shall ensure the the SMA Plan: Graphically represents project organizational relationships and assurance roles and responsibilities employing a Mission Assurance Process Map as described in NPR 8705.6, Safety and Mission Assurance Audits, Reviews, and Assessments. (Requirement 45653) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.c | 45654 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: Reflects a life-cycle SMA process perspective, addressing areas including: procurement, management, design and engineering, design verification and test, software design, software verification and test, manufacturing ,manufacturing verification and test, operations, and preflight verification and test, disassembly, and disposal. (Requirement 45654) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.d | 45655 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: Contains data and information to support each section of the SMA Plan for each major milestone review to include the Safety and Mission Success Review (formerly SMA Readiness Review). (Requirement 45655) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.e | 45656 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Paln: Contains trending and metrics utilized to display progress and to predict growth towards SMA goals and requirements. (Requirement 45656) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.01 | 45658 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Safety per this NPR. (Requirement 45658) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.02 | 45659 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Reliability and maintainability per NPD 8720.1, NASA Reliability and Maintainability (R&M) Program Policy. (Requirement 45659) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.03 | 45660 | Institution:Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Risk assessment per NPR 8705.5, Probabilistic Risk Assessment (PRA) Procedures for NASA Programs and Projects. (Requirement 45660) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.04 | 45661 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Quality assurance per NPD 8730.5, NASA Quality Assurance Program Policy. (Requirement 45661) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.05 | 45662 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Software safety and assurance per NASA-STD-88719.13, Software Safety Standard, and NASA-STD-8739.8, Software Assurance Standard. (Requirement 45662) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.06 | 45663 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Occupational safety and health per NPR 8715.1, NASA Occupational Safety and Health Programs. (Requirement 45663) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.07 | 45664 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Range safety per NPR 8715.5, Range Safety Program. (Requirement 45664) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.08 | 45665 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Human-rating per NPR 8705.2, Human-Rating Requirements for Space Systems. (Requirement 45665) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.09 | 45666 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Mishap reporting per NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping. (Requirement 45666) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.10 | 45667 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Compliance verification, audit, SMA reviews, and SMA process mpas per NPR 8705.6, Safety and Mission Assurance Audits, Reviews and Assessments. (Requirement 45667) | S | Y | Y | Mgmt | |||
| MGT-32 | NASA STD 8719.13B | 5.05.1 | 33480 | The integration of software safety with the chosen software life cycle shall be documented in the project Software Safety Plan. (Requirement 33480) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.06.1 | 33484 | The documents to be prepared as part of the software safety program, and their contents, shall be specified in the Software Safety Plan. (Requirement 33484) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.1 | 33594 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33594) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.1 | 33609 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33609) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.8.1.2 | 33234 | Ensure that the retirement plan includes archival and eventual disposal of software assurance records and documents created over the life of the program/project in accordance with the requirements of NPR 1441.1, NASA Records Retention Schedules. (Requirement 33234) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.1(1) | 33251 | Each software provider shall establish and maintain a software assurance plan that addresses all software development and maintenance activities. (Requirement 33251) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.1 | 33254 | Conform to IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans. (Requirement 33254) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.3 | 33256 | If there is any conflict between Section 6.0 or Section 7.0 of this Standard and IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans, this Standard shall take precedence. (Requirement 33256) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.4.1 | 33258 | The provider shall submit any proposed deviations from or modification to the baselined software assurance plan to the acquirer as a formal change request. (Requirement 33258) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.6.1 | 33262 | Software assurance records shall be prepared, maintained, placed under configuration management, and contain the descriptions and results of software assurance activities, (e.g, audit reports, classification evaluations, milestone review, software assurance briefings, problem reporting tracking). (Requirement 33262) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.6.2 | 33263 | Software assurance records shall include recommended preventive measures, corrective actions, and lessons learned. (Requirement 33263) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.4.5 | 33314 | Software assurance shall collect and maintain software assurance records showing the participation of software assurance staff in verification and validation efforts, such as minutes, records, artifacts, and signature on test reports. (Requirement 33314) | S | Y | Y | SWA | |||
| NPR 8715.3C | 01.05.2.a | 45652 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: Addresses life-cycle, safety relevant functions and activities. (Requirement 45652) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.b | 45653 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project Managers shall ensure the the SMA Plan: Graphically represents project organizational relationships and assurance roles and responsibilities employing a Mission Assurance Process Map as described in NPR 8705.6, Safety and Mission Assurance Audits, Reviews, and Assessments. (Requirement 45653) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.c | 45654 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: Reflects a life-cycle SMA process perspective, addressing areas including: procurement, management, design and engineering, design verification and test, software design, software verification and test, manufacturing ,manufacturing verification and test, operations, and preflight verification and test, disassembly, and disposal. (Requirement 45654) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.d | 45655 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: Contains data and information to support each section of the SMA Plan for each major milestone review to include the Safety and Mission Success Review (formerly SMA Readiness Review). (Requirement 45655) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.e | 45656 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Paln: Contains trending and metrics utilized to display progress and to predict growth towards SMA goals and requirements. (Requirement 45656) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.01 | 45658 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Safety per this NPR. (Requirement 45658) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.02 | 45659 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Reliability and maintainability per NPD 8720.1, NASA Reliability and Maintainability (R&M) Program Policy. (Requirement 45659) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.03 | 45660 | Institution:Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Risk assessment per NPR 8705.5, Probabilistic Risk Assessment (PRA) Procedures for NASA Programs and Projects. (Requirement 45660) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.04 | 45661 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Quality assurance per NPD 8730.5, NASA Quality Assurance Program Policy. (Requirement 45661) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.05 | 45662 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Software safety and assurance per NASA-STD-88719.13, Software Safety Standard, and NASA-STD-8739.8, Software Assurance Standard. (Requirement 45662) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.06 | 45663 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Occupational safety and health per NPR 8715.1, NASA Occupational Safety and Health Programs. (Requirement 45663) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.07 | 45664 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Range safety per NPR 8715.5, Range Safety Program. (Requirement 45664) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.08 | 45665 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Human-rating per NPR 8705.2, Human-Rating Requirements for Space Systems. (Requirement 45665) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.09 | 45666 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Mishap reporting per NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping. (Requirement 45666) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.05.2.f.10 | 45667 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project managers shall ensure that the SMA Plan: As a minimum, addresses the following topics and associated requirements: Compliance verification, audit, SMA reviews, and SMA process mpas per NPR 8705.6, Safety and Mission Assurance Audits, Reviews and Assessments. (Requirement 45667) | S | Y | Y | Mgmt | |||
| CxP 70059 | 1.14 | MGT-35 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA |
| NPR 8715.3C | 09.3.1.b | 46671 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that the application of the requirements in Chapter 2 of this NPR are specified in related contracts, memoranda of understanding, and other documents for joint ventures between NASA and other parties including commercial services, interagency efforts, and international partnerships. (Requirement 46671) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.1.c | 46672 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that NASA responsibilities are specified in contracts, memoranda of understanding, and other documents for joint ventures between NASA and other parties including commercial services, interagency efforts, and international partnerships. (Requirement 46672) | S | Y | Y | Safety | |||
| MGT-36 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| NPR 8715.3C | 09.3.4.b | 46690 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in applying any special safety provisions to grants or cooperative agreements (see paragraph 2.7). (Requirement 46690) | S | Y | Y | Mgmt | |||
| MGT-37 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| NPR 8715.3C | 09.3.4.a | 46689 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in evaluating the prospective contractor's safety record and safety program. (Requirement 46689) | S | Y | Y | Mgmt | |||
| MGT-38 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| NPR 8715.3C | 09.3.2.b | 46680 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Establish safety performance as an element to be evaluated in contracts with fee plans. (Requirement 46680) | U | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.4.c | 46691 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: During the pre-award phase of acquisition, develop, document and provide to the CO criteria for the safety performance elements to be evaluated in contracts with fee plans in a timely manner to ensure inclusion in the solicitation. (Requirement 46691) | S | Y | Y | Mgmt | |||
| CxP 70059 | 1.15 | MGT-13 | NPD 8730.5 | 5.d.3 | 42199 | Responsibility: Program/project managers shall: Identify safety/mission critical attributes and associated Government mandatory inspection points. (Requirement 42199) | S | Y | Y | Quality |
| NPD 8730.5 | 5.e.2 | 42203 | Responsibility: Procurement officials shall: Ensure that prospective contractors meet contract qualification requirements (quality system, product, process, personnel). (Requirement 42203) | S | Y | Y | Quality | |||
| CxP 70059 | 1.16 | MGT-106 | NPR 8705.6 | 3.2.07.1 | 42384 | Program/Project Managers shall: Incorporate PA&R process activities into program/project plans, including a program/project-unique mission assurance process map and matrix developed and maintained by the program/project with appropriate support and guidance of the Headquarters and/or Center SMA organization. Program/project management and responsible Center SMA organization use these products to actively manage the SMA function and to develop and support required inputs to the SMARR. (Requirement 42384) | S | Y | Y | Mgmt |
| NPR 8705.6 | 3.2.07.2 | 42385 | Program/Project Managers shall: Support the PA&R process (either Headquaters-led or Center-led) by providing logistic and resource support required for successful execution of and response to PA&R process activities. (Requirement 42385) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.3 | 42386 | Program/Project Managers shall: Coordinate with Center SMA and Center procurement to ensure that contracts provide for adequate contractor support of Headquarters-led and Center-led PA&R activities. (Requirement 42386) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.4 | 42387 | Program/Project Managers shall: Provide the PA&R Audit/Review Lead with the applicable programmatic BRS and OQE to facilitate PA&R process activities. (Requirement 42387) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.5 | 42388 | Program/Project Managers shall: Provide authorization for the program/project contractors to support PA&R process activities. (Requirement 42388) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.6 | 42389 | Program/Project Managers shall: In concert with the Center Director, Center SMA Director, and Program/Project SMA Manager, provide a Corrective Action Plan to the OSMA for resolution of Headquarters-led PA&R findings within 60 calendar days of the audit/review. (Requirement 42389) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.7 | 42390 | Program/Project Managers shall: In concert with the Program/Project SMA Manager, provide a Corrective Action Plan to the Center Director for resolution of Center-led PA&R findings. (Requirement 42390) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.08.1 | 42392 | SMA Managers Reporting (matrixed or direct) to the Program/Project Manager shall: Support the program/project manager in the development and maintenance of the program Assurance Process Map and Matrix. (Requirement 42392) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.08.2 | 42393 | SMA Managers Reporting (matrixed or direct) to the Program/Project Manager shall: Develop and maintain a program-specific Mission Assurance Portfolio which contains the OQE necessary to support the PA&R audits, reviews, and assessments. (Requirement 42393) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.08.3 | 42394 | SMA Managers Reporting (matrixed or direct) to the Program/Project Manager shall: Identify to the PA&R Audit/Review Lead (either Headquarters-led or Center-led) other audits, reviews, or assessments that may have previously verified compliance with the applicable programmatic BRS. (Requirement 42394) | S | Y | Y | Mgmt | |||
| MGT-28 | NPR 8705.6 | 3.2.07.1 | 42384 | Program/Project Managers shall: Incorporate PA&R process activities into program/project plans, including a program/project-unique mission assurance process map and matrix developed and maintained by the program/project with appropriate support and guidance of the Headquarters and/or Center SMA organization. Program/project management and responsible Center SMA organization use these products to actively manage the SMA function and to develop and support required inputs to the SMARR. (Requirement 42384) | S | Y | Y | Mgmt | ||
| NPR 8705.6 | 3.2.07.2 | 42385 | Program/Project Managers shall: Support the PA&R process (either Headquaters-led or Center-led) by providing logistic and resource support required for successful execution of and response to PA&R process activities. (Requirement 42385) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.3 | 42386 | Program/Project Managers shall: Coordinate with Center SMA and Center procurement to ensure that contracts provide for adequate contractor support of Headquarters-led and Center-led PA&R activities. (Requirement 42386) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.4 | 42387 | Program/Project Managers shall: Provide the PA&R Audit/Review Lead with the applicable programmatic BRS and OQE to facilitate PA&R process activities. (Requirement 42387) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.5 | 42388 | Program/Project Managers shall: Provide authorization for the program/project contractors to support PA&R process activities. (Requirement 42388) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.6 | 42389 | Program/Project Managers shall: In concert with the Center Director, Center SMA Director, and Program/Project SMA Manager, provide a Corrective Action Plan to the OSMA for resolution of Headquarters-led PA&R findings within 60 calendar days of the audit/review. (Requirement 42389) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.07.7 | 42390 | Program/Project Managers shall: In concert with the Program/Project SMA Manager, provide a Corrective Action Plan to the Center Director for resolution of Center-led PA&R findings. (Requirement 42390) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.08.1 | 42392 | SMA Managers Reporting (matrixed or direct) to the Program/Project Manager shall: Support the program/project manager in the development and maintenance of the program Assurance Process Map and Matrix. (Requirement 42392) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.08.2 | 42393 | SMA Managers Reporting (matrixed or direct) to the Program/Project Manager shall: Develop and maintain a program-specific Mission Assurance Portfolio which contains the OQE necessary to support the PA&R audits, reviews, and assessments. (Requirement 42393) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 3.2.08.3 | 42394 | SMA Managers Reporting (matrixed or direct) to the Program/Project Manager shall: Identify to the PA&R Audit/Review Lead (either Headquarters-led or Center-led) other audits, reviews, or assessments that may have previously verified compliance with the applicable programmatic BRS. (Requirement 42394) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.6.1 | 42441 | Program/Project Managers shall: Provide the necessary logistics and resources required to support the preparation and conduct of Headquarters-led or Center-led SMARRs. (Requirement 42441) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.6.2 | 42442 | Program/Project Managers shall: Coordinate with Center SMA and Center procurement to ensure that contracts provide for adequate contractor support of Headquarters-led and Center-led SMARR activities. (Requirement 42442) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.1 | 42444 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Help to identify all independent organizations which have assessed portions of the program or project. (Requirement 42444) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.2 | 42445 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Compile the program/project SMARR material, including the program's assessment of residual safety and mission success risk related to the upcoming milestone, identifying risk consequence and likelihood with supporting rationale and uncertainty associated with estimated likelihood. (Requirement 42445) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.3 | 42446 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Coordinate the presentation of the Center and program/project SMARR material to the Chief Safety and Mission Assurance Officer. (Requirement 42446) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.4 | 42447 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Coordinate within the program/project and support Headquarters-led and Center-led SMARR preparation meetings, as required. (Requirement 42447) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.5 | 42448 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Participate in SMARR polling as described in paragraphs 4.2.3.2. and 4.2.6.3. (Requirement 42448) | S | Y | Y | Mgmt | |||
| MGT-33 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| MGT-34 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| NPD 8700.1C | 1.e | 1063 | POLICY: It is NASA policy to-- Verify and validate life-cycle implementation of SMA, RM, and mission- success requirements through ongoing surveillance of program, project, and contractor processes. (Requirement 1063) | S | Y | Y | Mgmt | |||
| NPD 8700.1C | 1.f | 1064 | POLICY: It is NASA policy to-- Certify the safety and operational readiness of flight hardware/software, mission-critical support equipment, hazardous facilities/operations, and high-energy, ground-based systems through formal review processes. (Requirement 1064) | S | Y | Y | Mgmt | |||
| MGT-39 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| NPR 8715.3C | 02.6.1.a | 45952 | System Safety: System Safety Reviews: The program/project manager shall: Conduct periodic system safety and mission success reviews of their program/project depending on the complexity of the system. Note: The greater the risks, complexity of systems, or visibility of the programs, the greater the independence and formality of the reviews. (Requirement 45952) | S | Y | Y | Mgmt | |||
| MGT-40 | NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | ||
| MGT-41 | NASA-STD-8739.8 | 5.6.1.1 | 33222 | Ensure that software assurance processes are in place for operation of the software developed or acquired by NASA. (Requirement 33222) A separate Software Assurance Plan may be necessary as a new contract may cover the operational phase. | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 7.4.6 | 33315 | Software assurance shall provide objective evidence to the project and NASA SMA of the software's readiness for operational release. (Requirement 33315) | S | Y | Y | SWA | |||
| NPD 8700.1C | 5.e.4 | 1085 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Use and distribute lessons learned to enhance the probability of mission success and establish recurrence control through a closed-loop corrective/preventative action system. (Requirement 1085) | S | Y | Y | Quality | |||
| SAF-78 | NPR 8705.6 | 4.2.6.1 | 42441 | Program/Project Managers shall: Provide the necessary logistics and resources required to support the preparation and conduct of Headquarters-led or Center-led SMARRs. (Requirement 42441) | S | Y | Y | Mgmt | ||
| NPR 8705.6 | 4.2.6.2 | 42442 | Program/Project Managers shall: Coordinate with Center SMA and Center procurement to ensure that contracts provide for adequate contractor support of Headquarters-led and Center-led SMARR activities. (Requirement 42442) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.1 | 42444 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Help to identify all independent organizations which have assessed portions of the program or project. (Requirement 42444) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.2 | 42445 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Compile the program/project SMARR material, including the program's assessment of residual safety and mission success risk related to the upcoming milestone, identifying risk consequence and likelihood with supporting rationale and uncertainty associated with estimated likelihood. (Requirement 42445) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.3 | 42446 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Coordinate the presentation of the Center and program/project SMARR material to the Chief Safety and Mission Assurance Officer. (Requirement 42446) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.4 | 42447 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Coordinate within the program/project and support Headquarters-led and Center-led SMARR preparation meetings, as required. (Requirement 42447) | S | Y | Y | Mgmt | |||
| NPR 8705.6 | 4.2.7.5 | 42448 | SMA Managers reporting (matrix or direct) to the Program/Project Manager shall: Participate in SMARR polling as described in paragraphs 4.2.3.2. and 4.2.6.3. (Requirement 42448) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.02.1.f | 45571 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that technical reviews of the safety of development efforts and operations are conducted in accordance with sound system safety engineering principles. (Requirement 45571) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.3.1.d | 45931 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that decisions to accept risk are coordinated with the governing SMA organization and communicated to the next higher level of management for review. (See paragraph 1.6.2 of this NPR.) (Requirement 45931) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.3.2.a | 45935 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Ensure that the system safety models are constructed to support the implementation of the risk-informed decision framework. (Requirement 45935) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.6.1.a | 45952 | System Safety: System Safety Reviews: The program/project manager shall: Conduct periodic system safety and mission success reviews of their program/project depending on the complexity of the system. Note: The greater the risks, complexity of systems, or visibility of the programs, the greater the independence and formality of the reviews. (Requirement 45952) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 02.6.1.c | 45954 | System Safety: System Safety Reviews: The program/project manager shall: Ensure that the System Safety and Mission Success Program Reviews focus on the evaluation of management and technical documentation, hazard closure, and the safety residual risks remaining in the program at that stage of development. (Requirement 45954) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.8.2.b | 45974 | System Safety: Documentation: The System Safety Manager shall: Ensure that each submitted revision to the system safety analysis report lists the risks that have been addressed, the risks that have yet to be addressed, and expected residual risks that will remain following the implementation of risk reduction strategies. (Requirement 45974) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.8.2.c | 45975 | System Safety: Documentation: The System Safety Manager shall: Ensure that the system safety analysis report documents management and technical changes that affect the established safety baseline (by changes in the planned approach, design, requirements, and implementation) and is revised when required. (Requirement 45975) | S | Y | Y | Safety | |||
| CxP 70059 | 1.17 | MGT-43 | NPD 8730.5 | 1.b.06 | 42135 | Policy: NASA quality assurance programs shall: Continually be improved through: advocacy; awareness training; teaming and sharing of quality assurance tools, techniques and data; integration of quality assurance processes to prevent duplication of effort; and dissemination/implementation of lessons learned and best practices. (Requirement 42135) | S | Y | Y | Quality |
| CxP 70059 | 1.2 | MGT-2 | NASA STD 8719.13B | 5.05.2 | 33481 | Software safety activities shall be performed throughout all phases of the software development life cycle. Activities which may be completed within or dependent upon a particular phase, or may need to be updated within successive phases, are documented as such. (Requirement 33481) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.05.3 | 33482 | Software safety activities shall continue to be performed at a needed level once the system is operational. Section 7 provides requirements for the operational phase of the system. (Requirement 33482) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.1 | 33655 | The requirements of this Standard shall continue to be applicable after the safety-critical software has been released for operations. (Requirement 33655) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2 | 33656 | The software safety requirements to specify, develop, analyze, and test safety-critical software, shall apply to all changes made to the software or routine operational updates (e.g., mission specific database updates). (Requirement 33656) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.d(1) | 1062 | POLICY: It is NASA policy to-- Define and document both SMA requirements and safety and mission- success criteria in NASA programs and projects as a foundation for the design and development of safe and reliable program hardware and software. (Requirement 1062) | S | Y | Y | Mgmt | |||
| NPD 8700.1C | 1.d(2) | 30884 | POLICY: It is NASA policy to-- All solicitation instruments (announcements of opportunity, cooperative agreements, requests for proposals, or other) will require prospective providers to identify and describe SMA and Risk Management (RM) approaches (where appropriate) and how the risk factors will be managed. (Requirement 30884) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.02.1.a | 45566 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that their safety planning and direction; the development of safety requirements, safety policies, safety methodology, and safety procedures; and the implementation and evaluation of their safety programs achieve the safety requirements in this NPR (Requirement 45566). | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.02.1.d | 45569 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that employees are informed of any risk acceptance when the employees are the ones at risk. (Requirement 45569) | S | Y | Y | Mgmt | |||
| CxP 70059 | 1.3 | MGT-3 | NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.1 | 33655 | The requirements of this Standard shall continue to be applicable after the safety-critical software has been released for operations. (Requirement 33655) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2 | 33656 | The software safety requirements to specify, develop, analyze, and test safety-critical software, shall apply to all changes made to the software or routine operational updates (e.g., mission specific database updates). (Requirement 33656) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.d(1) | 1062 | POLICY: It is NASA policy to-- Define and document both SMA requirements and safety and mission- success criteria in NASA programs and projects as a foundation for the design and development of safe and reliable program hardware and software. (Requirement 1062) | S | Y | Y | Mgmt | |||
| NPD 8700.1C | 1.d(2) | 30884 | POLICY: It is NASA policy to-- All solicitation instruments (announcements of opportunity, cooperative agreements, requests for proposals, or other) will require prospective providers to identify and describe SMA and Risk Management (RM) approaches (where appropriate) and how the risk factors will be managed. (Requirement 30884) | S | Y | Y | Mgmt | |||
| MGT-4 | NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.1 | 33655 | The requirements of this Standard shall continue to be applicable after the safety-critical software has been released for operations. (Requirement 33655) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2 | 33656 | The software safety requirements to specify, develop, analyze, and test safety-critical software, shall apply to all changes made to the software or routine operational updates (e.g., mission specific database updates). (Requirement 33656) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.d(1) | 1062 | POLICY: It is NASA policy to-- Define and document both SMA requirements and safety and mission- success criteria in NASA programs and projects as a foundation for the design and development of safe and reliable program hardware and software. (Requirement 1062) | S | Y | Y | Mgmt | |||
| MGT-5 | NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.1 | 33655 | The requirements of this Standard shall continue to be applicable after the safety-critical software has been released for operations. (Requirement 33655) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2 | 33656 | The software safety requirements to specify, develop, analyze, and test safety-critical software, shall apply to all changes made to the software or routine operational updates (e.g., mission specific database updates). (Requirement 33656) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.d(1) | 1062 | POLICY: It is NASA policy to-- Define and document both SMA requirements and safety and mission- success criteria in NASA programs and projects as a foundation for the design and development of safe and reliable program hardware and software. (Requirement 1062) | S | Y | Y | Mgmt | |||
| MGT-6 | NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| CxP 70059 | 1.5 | MGT-14 | NPR 8715.3C | 01.13.4.a | 45793 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Establish and implement Center/program/project-level processes and requirements as needed to satisfy the SMA variance policy and associated requirements provided in this NPR to include processes for preparation, review, and approval of variance requests. (Requirement 45793) | S | Y | Y | Mgmt |
| NPR 8715.3C | 01.13.4.b | 45794 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure that all variance requests include (but are not limited to) documentation as to why the requirement cannot be met, alternative means to reduce the hazard or risk, the type of variance, the duration of the variance if temporary, and comments from any affected workers or their representatives if the variance affects personnel safety. (Requirement 45794) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.c | 45795 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure all variance requests include a risk assessment that determines whether there is an increase in risk because the requirement is not satisfied or that the intent of the requirement is met through alternate means that provide an equivalent or lower level of risk. (Requirement 45795) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.d | 45796 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure all requests for deviations or waivers include a plan for correcting the associated deficiency and identify a date or development milestone for bringing the project into compliance with the associated requirement. (Requirement 45796) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.e | 45797 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure variance requests are approved in accordance with the policy in paragraph 1.13.3 of this NPR. (Requirement 45797) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.f | 45798 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Provide copies of all approved safety variances to the OSMA. (Requirement 45798) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.g | 45799 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Forward any request for variance to Federal, State, or local regulations to the OSMA for review prior to submittal to the appropriate Federal/State/local agency. (Requirement 45799) | S | Y | Y | Mgmt | |||
| MGT-47 | NPR 8705.2A | 1.5.11.7 | 34331 | The Program Manager shall track the status of compliance with the provisions of all waivers (Requirement 34331). | S | Y | Y | Safety | ||
| NPR 8715.3C | 01.13.4.a | 45793 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Establish and implement Center/program/project-level processes and requirements as needed to satisfy the SMA variance policy and associated requirements provided in this NPR to include processes for preparation, review, and approval of variance requests. (Requirement 45793) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.b | 45794 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure that all variance requests include (but are not limited to) documentation as to why the requirement cannot be met, alternative means to reduce the hazard or risk, the type of variance, the duration of the variance if temporary, and comments from any affected workers or their representatives if the variance affects personnel safety. (Requirement 45794) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.c | 45795 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure all variance requests include a risk assessment that determines whether there is an increase in risk because the requirement is not satisfied or that the intent of the requirement is met through alternate means that provide an equivalent or lower level of risk. (Requirement 45795) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.d | 45796 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure all requests for deviations or waivers include a plan for correcting the associated deficiency and identify a date or development milestone for bringing the project into compliance with the associated requirement. (Requirement 45796) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.e | 45797 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Ensure variance requests are approved in accordance with the policy in paragraph 1.13.3 of this NPR. (Requirement 45797) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.f | 45798 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Provide copies of all approved safety variances to the OSMA. (Requirement 45798) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 01.13.4.g | 45799 | Institutional and Programmatic Safety Requirements: Safety Variances: Center Directors (or designees) and project managers shall: Forward any request for variance to Federal, State, or local regulations to the OSMA for review prior to submittal to the appropriate Federal/State/local agency. (Requirement 45799) | S | Y | Y | Mgmt | |||
| CxP 70059 | 1.8 | MGT-18 | NASA STD 8719.13B | 5.01.2.1.5 | 33429 | Program/project/facility management shall work with SMA management to provide a means to resolve conflicts related to software safety requirements or processes. (Requirement 33429) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.3.2.1 | 33442 | Software safety personnel shall have the organizational freedom and authority to analyze and report software safety non-conformances. (Requirement 33442) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.2.3 | 33246 | The software assurance manager shall have a reporting channel to provider management that is independent of the provider's project management and software development function. (Requirement 33246) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.c | 1006 | POLICY: It is NASA policy to-- Establish and maintain independent lines of communications for unrestricted flow of information concerning Safety and Mission Assurance (SMA), risks, or other matters affecting the ability to meet the mission-success criteria. (Requirement 1006) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 02.5.1.3.j | 45910 | System Safety: Core Requirements for System Safety Processes: System Safety Technical Plan (SSTP): The assigned System Safety Manager shall: Establish an independent safety reporting channel to keep the Center SMA Director apprised of the system safety status (including tests and operations), particularly regarding problem areas that may require assistance from the Center, the NASA Engineering and Safety Center, or Headquarters. (Requirement 45910) | S | Y | Y | Mgmt | |||
| MGT-19 | NASA STD 8719.13B | 5.01.2.1.5 | 33429 | Program/project/facility management shall work with SMA management to provide a means to resolve conflicts related to software safety requirements or processes. (Requirement 33429) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.01.3.2.1 | 33442 | Software safety personnel shall have the organizational freedom and authority to analyze and report software safety non-conformances. (Requirement 33442) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.2.3 | 33246 | The software assurance manager shall have a reporting channel to provider management that is independent of the provider's project management and software development function. (Requirement 33246) | S | Y | Y | SWA | |||
| NPD 8700.1C | 1.c | 1006 | POLICY: It is NASA policy to-- Establish and maintain independent lines of communications for unrestricted flow of information concerning Safety and Mission Assurance (SMA), risks, or other matters affecting the ability to meet the mission-success criteria. (Requirement 1006) | S | Y | Y | Mgmt | |||
| MGT-20 | NASA STD 8719.13B | 5.01.2.1.5 | 33429 | Program/project/facility management shall work with SMA management to provide a means to resolve conflicts related to software safety requirements or processes. (Requirement 33429) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.3.1.3 | 33203 | Ensure that acquirer software assurance personnel are trained and qualified to accomplish their tasks. (Requirement 33203) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.3.1.4 | 33204 | Assure that provider software assurance personnel are trained and qualified to accomplish their tasks. (Requirement 33204) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.8.1 | 33267 | Personnel managing, developing, and implementing the software assurance process shall be trained and/or experienced in software assurance. (Requirement 33267) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.8.2 | 33268 | Software assurance training shall be obtained and/or originated and maintained for management, engineering, and assurance personnel. (Requirement 33268) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.8.3 | 33269 | Software assurance personnel shall be trained in relevant software engineering design methods and languages, processes, development environments, tools, test techniques, and other software engineering and assurance methods needed to stay current with the engineering environment and products they must assure. (Requirement 33269) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.8.4 | 33270 | Software assurance personnel shall be trained for the environment and operational particulars of the program/project to which they are assigned. (Requirement 33270) This may include on-the-job training as well as orientation and specific engineering training. | S | Y | Y | SWA | |||
| NPD 8700.1C | 5.a | 1013 | RESPONSIBILITY: Each NASA organizational element shall allocate and maintain appropriate levels of authority, funding, and training necessary to achieve compliance with the policies set forth above. (Requirement 1013) | S | Y | Y | Mgmt | |||
| NPD 8730.5 | 5.d.1 | 42197 | Responsibility: Program/project managers shall: Provide necessary program dollars for costs associated with Government and contractor implementation of the requirements prescribed by this NPD and NPR 8735.2. (Requirement 42197) | S | Y | Y | Quality | |||
| NPR 8705.5 | 1.4.4 | 33016 | Center Directors, Center SMA Directors, and program/project SMA Directors shall assist Center-based programs/projects in conducting required PRAs; i.e., provide required resources, training, tools, technical advice, or assistance in obtaining competent support services (Requirement 33016). | S | Y | Y | PRA | |||
| CxP 70059 | 1.9 | MGT-21 | NASA STD 8719.13B | 5.01.2.1.5 | 33429 | Program/project/facility management shall work with SMA management to provide a means to resolve conflicts related to software safety requirements or processes. (Requirement 33429) | S | Y | Y | SWA |
| MGT-22 | NPD 8700.1C | 1.f | 1064 | POLICY: It is NASA policy to-- Certify the safety and operational readiness of flight hardware/software, mission-critical support equipment, hazardous facilities/operations, and high-energy, ground-based systems through formal review processes. (Requirement 1064) | S | Y | Y | Mgmt | ||
| NPD 8700.1C | 1.g | 1065 | POLICY: It is NASA policy to-- Fully address safety and mission success concerns, risks and risk acceptance, and appropriate lessons learned at all management committee reviews, other major milestone review activities, and operational readiness reviews. (Requirement 1065) | S | Y | Y | Mgmt | |||
| MGT-23 | NPD 8700.1C | 5.e.5 | 1086 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Designate an individual with specific responsibilities for coordinating/executing SMA efforts within the program/project. (Requirement 1086) | S | Y | Y | Quality | ||
| MGT-25 | NPR 8715.3C | 01.02.1.e | 45570 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that safety surveillance and periodic inspections are conducted to assure compliance with NASA safety policies and to assess the effectiveness of NASA safety activities as required by Federal, State, and local regulations, NASA policy, and national consensus standards. (Requirement 45570) | S | Y | Y | Mgmt | ||
| MGT-26 | NPR 8715.3C | 09.3.4.b | 46690 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in applying any special safety provisions to grants or cooperative agreements (see paragraph 2.7). (Requirement 46690) | S | Y | Y | Mgmt | ||
| MGT-27 | NASA-STD-8739.8 | 5.6.1.2 | 33223 | Depending upon the operational environment and the criticality of operation, ensure that software assurance processes include a periodic audit of the operations to ensure any changes to the software or software induced operational workarounds have been reviewed and approved. (Requirement 33223) | S | Y | Y | SWA | ||
| NPR 8715.3C | 02.5.1.3.k | 45911 | System Safety: Core Requirements for System Safety Processes: System Safety Technical Plan (SSTP): The assigned System Safety Manager shall: Support OSMA requirements for audits, assessments, and reviews. (Requirement 45911) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 02.6.1.a | 45952 | System Safety: System Safety Reviews: The program/project manager shall: Conduct periodic system safety and mission success reviews of their program/project depending on the complexity of the system. Note: The greater the risks, complexity of systems, or visibility of the programs, the greater the independence and formality of the reviews. (Requirement 45952) | S | Y | Y | Mgmt | |||
| CxP 70059 | 2.1.10 | SAF-26 | NPR 8715.3C | 09.7.1.a | 46715 | Safety and Risk Management for NASA Contracts: Grants: Project managers that select research projects that could contain possible safety issues shall: Identify the need for special safety conditions to be included in grants or cooperative agreement award documents. Note: A "special safety condition" addressing safety should be included in grants and cooperative agreements when contract performance involves NASA facilities, Government-Furnished Equipment, or hazardous or energetic materials or chemicals that may pose a significant safety or health risk to the public, NASA employees, and contractor employees when used. (Requirement 46715) | S | Y | Y | Safety |
| SAF-27 | NPR 8715.3C | 09.7.1.b | 46716 | Safety and Risk Management for NASA Contracts: Grants: Project managers that select research projects that could contain possible safety issues shall: Identify special safety conditions that include provisions for applicable OSHA requirements and host institution and general industry-accepted practices to be followed during research to eliminate or control risks associated with implementing the grant or cooperative agreement. (Requirement 46716) | S | Y | Y | Safety | ||
| CxP 70059 | 2.1.11 | SAF-154 | NPR 8621.1B | 0.P.1.a | 44011 | PREFACE: PURPOSE: The purpose of this NASA Procedural Requirements (NPR) is to provide requirements to report, investigate, and document mishaps, close calls, and previously unidentified serious workplace hazards to prevent recurrence of similar accidents. This NPR does not apply to investigative procedures concerning civil, criminal, or administrative culpability or legal liability. Furthermore, the safety investigation outlined in this NPR shall not be used to direct or justify disciplinary action for mishaps or close calls. (Requirement 44011) | S | Y | Y | Safety |
| NPR 8621.1B | 1.02.2.6(1) | 44065 | GENERAL INFORMATION: Description of NASA Mishaps and Close Calls: The following are not considered NASA mishaps: When an event is not considered a mishap because the initiating event (proximate cause) is natural phenomenon or weather, the cognizant Center safety office shall enter the event and a description of the damage in IRIS. (Requirement 44065) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.02.2.7 | 44070 | GENERAL INFORMATION: Description of NASA Mishaps and Close Calls: The following are not considered NASA mishaps: When an event is not considered a mishap because the initiating event (proximate cause) is natural phenomenon or weather, the organization incurring the damage shall perform a technical assessment to evaluate design and construction aspects, contingency planning, and emergency response and provide facts, findings, and recommendations to the Center Director through the Center SMA Director (or equivalent office with responsibilities for the Center?s facility safety program). (Requirement 44070) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.03.1 | 44074 | GENERAL INFORMATION: Determining the Classification Level and Type of Investigation to be Conducted: The severity of the personnel injury and the direct cost of the mishap or close call (property damage and/or mission failure) shall determine the classification level of the mishap or close call (see Figure 1) and the corresponding type of investigation to be conducted. (Requirement 44074) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.03.3.1 | 44077 | GENERAL INFORMATION: Determining the Classification Level and Type of Investigation to be Conducted: Determining the direct cost of the mishap or close call: The responsible manager, with review and concurrence by the Center safety office, shall calculate the direct cost of a mishap or close call by adding all the actual costs (or the estimate of the cost) (the greater value of actual or fair market value) of damaged property, destroyed property, or mission failure, actual cost of repair or replacement, labor (actual value of replacement or repair hours for internal and external/contracted labor), cost of the lost commodity (e.g., the cost of the fluid that was lost from a ruptured pressure vessel), as well as resultant costs such as environmental decontamination, property cleanup, and restoration. (Requirement 44077) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.03.3.2 | 44078 | GENERAL INFORMATION: Determining the Classification Level and Type of Investigation to be Conducted: Determining the direct cost of the mishap or close call: In cases where replacement parts are available from salvaged or excess equipment at little or no cost to NASA, the direct cost of the mishap or close call shall include the actual costs of replacement parts (if they were purchased new) plus labor calculated as if the salvage/excess parts were unavailable. (Requirement 44078) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.03.3.3 | 44079 | GENERAL INFORMATION: Determining the Classification Level and Type of Investigation to be Conducted: Determining the direct cost of the mishap or close call: In cases where insurance compensation, contractor compensation, or other compensation is available or provided, the direct cost of the mishap or close call shall include the direct cost (or estimate of the cost) as if this compensation were not available or provided. (Requirement 44079) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.03.3.4 | 44080 | GENERAL INFORMATION: Determining the Classification Level and Type of Investigation to be Conducted: Determining the direct cost of the mishap or close call: The cost of the safety mishap investigation shall not be included in the direct cost. (Requirement 44080) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.01.a | 44083 | GENERAL INFORMATION: Roles and Responsibilities: Administrator. The Administrator: May elect to be the appointing official for Type A mishaps or delegate to the AA. (If the Administrator elects not to be the appointing official, the MDAA, CD, or another designee will serve as the appointing official.) (Requirement 44083) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.01.b | 44084 | GENERAL INFORMATION: Roles and Responsibilities: Administrator. The Administrator: Shall serve as appointing official for NASA joint participation on a MIB with the Department of Defense (DoD) and other agencies unless authority is delegated by existing agreements. (Requirement 44084) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.02.a | 44087 | GENERAL INFORMATION: Roles and Responsibilities: Chief/OSMA. The Chief/OSMA or designee shall: Ensure the proper reporting, investigating, and recordkeeping for mishaps and close calls by defining the mishap reporting and investigating process, updating this NPR, verifying its implementation, developing mishap investigation training, and identifying candidate mishap investigation tools. (Requirement 44087) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.02.b | 44088 | GENERAL INFORMATION: Roles and Responsibilities: Chief/OSMA. The Chief/OSMA or designee shall: Concur with the mishap classification level, investigation approach, and the MIB membership and serve as an endorsing official for the mishap report for Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls. (Requirement 44088) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.02.c | 44089 | GENERAL INFORMATION: Roles and Responsibilities: Chief/OSMA. The Chief/OSMA or designee shall: Provide a qualified NASA person to support NTSB investigations of NASA aircraft mishaps. (Requirement 44089) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.02.d | 44090 | GENERAL INFORMATION: Roles and Responsibilities: Chief/OSMA. The Chief/OSMA or designee shall: Archive NASA Headquarters-approved NASA mishap investigation board reports and related documents per NPR 1441.1. (Requirement 44090) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.03 | 44091 | GENERAL INFORMATION: Roles and Responsibilities: Inspector General. The Inspector General shall investigate criminal activity associated with mishaps and close calls. (Requirement 44091) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.04.a | 44093 | GENERAL INFORMATION: Roles and Responsibilities: AA. The AA shall: Serve as the appointing official for Type A mishaps if designated by the Administrator. (Requirement 44093) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.04.b | 44094 | GENERAL INFORMATION: Roles and Responsibilities: AA. The AA shall: Obtain concurrence from the Chief/OSMA and the Chief Engineer on the MIB membership of mishaps in which he/she is the appointing official. (Requirement 44094) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.04.c | 44095 | GENERAL INFORMATION: Roles and Responsibilities: AA. The AA shall: Serve as an endorsing official for all mishaps in which he/she is the appointing official. (Requirement 44095) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.a | 44097 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Implement the mishap and close call reporting, investigating, and recordkeeping requirements for their assigned Mission Directorates for mishaps and close calls that occur outside the Center?s gates, during in-space flight, or at a program/project contractor site that is not managed by a Center. (Requirement 44097) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.b(1) | 44098 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Approve via signature all his/her program and project (as defined in NPR 7120.5) Program/Project Mishap Preparedness and Contingency Plans. (These plans will be developed by the cognizant Center safety offices, and will include procedures to notify, report, investigate, and record mishaps and close calls that involve Mission Directorate programs/projects/activities whether onsite or offsite, and whether on the ground or in flight.) (Requirement 44098) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.c | 44100 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Determine the mishap classification level (or assign a designee to determine the classification level) for all mishaps for which he/she has reporting responsibility and obtain concurrence on this classification level from the Chief/OSMA for Type A and B mishaps, high-visibility mishaps, and high-visibility close calls. (Requirement 44100) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.d(1) | 44102 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Serve as the appointing official for Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls that involve Mission Directorate programs/projects/activities that occur outside the Center?s gates, during in-space flight, or at a program/project contractor site that is not managed by a Center. (Requirement 44102) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.e | 44104 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Serve as the appointing official or document the designee in the Program Mishap Preparedness and Contingency Plan for Type C mishaps, Type D mishaps, and close calls that occur outside the Center?s gates, during in-space flight, or at a program/project contractor site that is not managed by a Center. (Requirement 44104) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.f | 44105 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Provide funding and support for investigations within their programs and involving their hardware, facilities, or enabling activities. (Requirement 44105) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.05.g | 44106 | GENERAL INFORMATION: Roles and Responsibilities: MDAA. The MDAA shall: Ensure that agreements for joint programs with international partners and other Federal agencies incorporate elements of this NPR to ensure that joint mishap investigating and reporting complies with NASA requirements. (Requirement 44106) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.06.a | 44108 | GENERAL INFORMATION: Roles and Responsibilities: Assistant Administrator, Office of Public Affairs (AA/OPA): The AA/OPA shall establish guidelines for the public release of mishap reports and related information. (Requirement 44108) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.06.c(1) | 44110 | GENERAL INFORMATION: Roles and Responsibilities: Assistant Administrator, Office of Public Affairs (AA/OPA): For Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls, the AA/OPA (or designee) shall appoint a Headquarters public affairs advisor. (Requirement 44110) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.1 | 44113 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: The AA/OIA shall provide funding and support for investigations of mishaps that occur at NASA Headquarters. (Requirement 44113) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.a | 44114 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Develop Center and Program Mishap Preparedness and Contingency Plans to support this NPR (this includes procedures to notify, report, investigate, and record mishaps and close calls that involve programs, projects, and activities that fall under their responsibility). (Requirement 44114) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.b | 44115 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Implement the mishap reporting, investigating, and recordkeeping requirements for all projects, programs, and activities that fall under their SMA responsibility. (Requirement 44115) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.c | 44116 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Provide funding and support for investigations at their Centers, within their projects and programs, and involving their hardware, facilities, or enabling activities. (Requirement 44116) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.d | 44117 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Determine the mishap classification level (or assign a designee to determine the classification level) for all mishaps for which the Center has reporting responsibility and obtain concurrence on this classification level from the Chief/OSMA for Type A and B mishaps, high-visibility mishaps, and high-visibility close calls. (Requirement 44117) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.e(1) | 44118 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Serve as the appointing official for Type A mishaps and Type B mishaps occurring at, or managed by, his/her Center and involving offsite Center support contractors. (Requirement 44118) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.f | 44120 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Serve as or designate the appointing official and document the designee(s) in the Mishap Preparedness and Contingency Plan for Type C mishaps, Type D mishaps, and close calls. (Requirement 44120) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.g | 44121 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: In the event that there is a mishap involving injury of a human research subject at a NASA Center, request the Chief Health and Medical Officer (CHMO) concurrence on the investigating authority's membership. (Requirement 44121) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.h | 44122 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Personally report, by telephone or e-mail, to the Administrator within 24 hours of learning the instance of any NASA Type A mishap, any NASA Type B mishap, and a NASA Type C mishap only if it involves a lost-time injury or illness. (Requirement 44122) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.i | 44123 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Personally report, by telephone or e-mail, to the Administrator within 24 hours of any nonoccupational fatality, such as sudden cardiac arrest of a NASA civil service employee or a resident contractor that occurred on site (a resident contractor is a NASA contractor whose primary place of business is on or near a NASA Center or NASA-owned facility). (Requirement 44123) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.j | 44124 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Personally report, by telephone or e-mail, to the Administrator when it becomes known that there is any off-the-job fatality or serious injury/illness of a NASA civil service employee or resident contractor. (Requirement 44124) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.k.1 | 44126 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Ensure that local procedures for dealing with the needs of the NASA workforce (civil service employees and contractor employees) when they are experiencing a crisis situation (e.g., serious injury, illness, or fatality of workforce member or family member) are: Reviewed annually. (Requirement 44126) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.k.2 | 44127 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Ensure that local procedures for dealing with the needs of the NASA workforce (civil service employees and contractor employees) when they are experiencing a crisis situation (e.g., serious injury, illness, or fatality of workforce member or family member) are: Include a process for immediately notifying the next of kin for mishaps and on site nonoccupational medical events resulting in fatality or serious injury. (Requirement 44127) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.k.3 | 44128 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Ensure that local procedures for dealing with the needs of the NASA workforce (civil service employees and contractor employees) when they are experiencing a crisis situation (e.g., serious injury, illness, or fatality of workforce member or family member) are: Provide information to the person or family (when the person is unable to receive such information due to the injury or illness) concerning benefits, such as extended sick-leave and disability. (Requirement 44128) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.L | 44129 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Ensure that the NASA civil service employees designated to communicate with the family of an injured, ill, or deceased individual have received training in NASA policy concerning benefits and crisis intervention. (Requirement 44129) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.m(1) | 44130 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Initiate the use of the NASA Family Assistance Fund (NFAF), upon the NASA civil service employee family?s agreement or request. (Requirement 44130) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.n | 44132 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Obtain concurrence from the Chief/OSMA and the Chief Engineer on the MIB membership of Type A, Type B, high-visibility mishaps, and high-visibility close calls in which he/she is the appointing official. (Requirement 44132) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.o | 44133 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Provide administrative and logistical support for the investigating authority working on the Center and distribute the authorized mishap report per this NPR. (Requirement 44133) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.p | 44134 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Verify that NASA contractors and grantees conduct mishap investigations and provide mishap reports as specified in their contracts and in NFS 1852.223-70. (Requirement 44134) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.07.q | 44135 | GENERAL INFORMATION: Roles and Responsibilities: CD and AA/OIA. The CD and the AA/OIA shall: Serve as an endorsing official for mishaps and close calls in which he/she is the appointing official. (Requirement 44135) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.08.a | 44137 | GENERAL INFORMATION: Roles and Responsibilities: Program and Project Managers. Program and project managers shall: Concur on the Program/Project Mishap Preparedness and Contingency Plan. (Requirement 44137) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.08.b | 44138 | GENERAL INFORMATION: Roles and Responsibilities: Program and Project Managers. Program and project managers shall: In the event of a mishap or close call at the Center, activate the Program Mishap Preparedness and Contingency Plan. (Requirement 44138) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.08.c | 44139 | GENERAL INFORMATION: Roles and Responsibilities: Program and Project Managers. Program and project managers shall: Provide funding and support for investigations within their program jurisdiction or involving their hardware and facilities. (Requirement 44139) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.08.d | 44140 | GENERAL INFORMATION: Roles and Responsibilities: Program and Project Managers. Program and project managers shall: Assist the investigating authority as requested. (Requirement 44140) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.08.e | 44141 | GENERAL INFORMATION: Roles and Responsibilities: Program and Project Managers. Program and project managers shall: When tasked by the appointing official, develop the Corrective Action Plan (CAP), implement the CAP, support the Center safety office personnel as they verify that the CAP has been completed, and generate the lessons learned. (Requirement 44141) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.09.a | 44143 | GENERAL INFORMATION: Roles and Responsibilities: Responsible Organization. The responsible organization shall: Assist the investigating authority as requested. (Requirement 44143) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.b | 44147 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Determine the level of NASA involvement, if any, when a mishap resulted from the actions of an outside source that was not involved in NASA operations. (Requirement 44147) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.c | 44148 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Initiate a NASA investigation pursuant to this NPR, when the appointing official believes that a NASA contractor's/grantee's mishap report is not adequate because it failed to reach root cause(s), failed to provide recommendations that prevent recurrence, is not suitably independent, or is in some other way deficient. (Requirement 44148) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.d(1) | 44149 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Generate a formal memorandum for Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls that communicates the appointment of the investigating authority members, the chairperson, the ex officio, and the advisors. (Requirement 44149) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.e | 44151 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Serve as an endorsing official for mishaps and close calls in which he/she is the appointing official. (Requirement 44151) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.f | 44152 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Assign the responsible organization(s)/program(s)/project(s) to develop the CAP, implement the CAP, and generate the lessons learned. (Requirement 44152) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.g | 44153 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Ensure that the mishap investigation process for the assigned mishap or close call is properly completed. (Requirement 44153) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.h | 44154 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Verify that the mishap report is reviewed, endorsed, and authorized for public release. (Requirement 44154) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.i | 44155 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Ensure that the CAP is developed and implemented. (Requirement 44155) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.j | 44156 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Ensure that the lessons learned are developed, reviewed, and authorized for public release. (Requirement 44156) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.k | 44157 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Release the investigating authority from duty. (Requirement 44157) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.L | 44158 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Generate the CAP closure statement and the mishap activities completion statement. (Requirement 44158) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.m | 44159 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: Assist the investigating authority as requested. (Requirement 44159) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.n.1 | 44161 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: If the NTSB performs an investigation, the appointing official shall: Initiate a NASA mishap investigation per this NPR. (Requirement 44161) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.10.n.2 | 44162 | GENERAL INFORMATION: Roles and Responsibilities: Appointing Official. The appointing official shall: If the NTSB performs an investigation, the appointing official shall: Request that a NASA representative be a party to the NTSB's investigation. (Requirement 44162) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.12.a | 44167 | GENERAL INFORMATION: Roles and Responsibilities: Ex Officio. The ex officio shall: Serve as the authorized representative of the Chief/OSMA. (Requirement 44167) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.12.b | 44168 | GENERAL INFORMATION: Roles and Responsibilities: Ex Officio. The ex officio shall: Be a nonvoting participant in all investigation deliberations. (Requirement 44168) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.12.e | 44171 | GENERAL INFORMATION: Roles and Responsibilities: Ex Officio. The ex officio shall: Assure that the mishap report contains the proper elements including proximate cause(s), root cause(s), failed barrier(s), and observation(s); sufficient facts/data to support the finding(s) and recommendation(s); and a mishap investigation summary. (Requirement 44171) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.13.a | 44175 | GENERAL INFORMATION: Roles and Responsibilities: Chairperson. The chairperson of the investigating authority shall: Manage and coordinate all aspects of the mishap investigation, including, but not limited to, the following tasks: assign group leaders; interview witnesses; reconstruct the mishap or close call; identify facts; identify proximate cause(s) and root cause(s); generate recommendation(s); and complete the mishap report. (Requirement 44175) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.13.e | 44181 | GENERAL INFORMATION: Roles and Responsibilities: Chairperson. The chairperson of the investigating authority shall: Define the roles and/or areas of investigative responsibility for each group or subgroup on the MIB or MIT, as needed. (Requirement 44181) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.13.g(1) | 44183 | GENERAL INFORMATION: Roles and Responsibilities: Chairperson. The chairperson of the investigating authority shall: Report only to the appointing official (or designee) during the investigation. (Requirement 44183) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.13.h(1) | 44185 | GENERAL INFORMATION: Roles and Responsibilities: Chairperson. The chairperson of the investigating authority shall: Refer allegations and evidence of criminal activity that are identified in the course of an investigation to the Office of Inspector General. (Requirement 44185) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.14 | 44187 | GENERAL INFORMATION: Roles and Responsibilities: Investigating Authority. The investigating authority shall conduct a comprehensive investigation within the defined scope of the appointment letter or appointment orders, generate the products indicated in paragraph 1.7 and Figure 5 of this NPR, prepare a mishap report, and sign the report. (Requirement 44187) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.15.a(1) | 44189 | GENERAL INFORMATION: Roles and Responsibilities: Investigating Authority's Advisors. The advisors shall: Attend meetings as needed, travel with the investigating authority as requested, and have access to all investigative material with the exception of witness statements and testimony. (Requirement 44189) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.15.b | 44191 | GENERAL INFORMATION: Roles and Responsibilities: Investigating Authority's Advisors. The advisors shall: Provide advice to the investigating authority. (Requirement 44191) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.15.c | 44192 | GENERAL INFORMATION: Roles and Responsibilities: Investigating Authority's Advisors. The advisors shall: Sign the mishap report stating that he/she has reviewed the mishap report and that it meets NASA policies and procedures in his/her functional area. (Requirement 44192) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.16.a | 44194 | GENERAL INFORMATION: Roles and Responsibilities: Legal Advisor. The legal advisor shall: Develop nondisclosure agreements if the investigating authority uses a contractor as administrative support. (Requirement 44194) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.16.b | 44195 | GENERAL INFORMATION: Roles and Responsibilities: Legal Advisor. The legal advisor shall: Develop nondisclosure agreements if the investigating authority uses a contractor to analyze interview data or participate in interviews. (Requirement 44195) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.16.c | 44196 | GENERAL INFORMATION: Roles and Responsibilities: Legal Advisor. The legal advisor shall: Provide legal advice and counsel as requested by the board chair. (Requirement 44196) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.17.1(1) | 44199 | GENERAL INFORMATION: Roles and Responsibilities: The advisors may be included or excluded from listening to any deliberations at the discretion of the chairperson: The chairperson may exclude advisors (with the exception of the legal advisor) from participating in deliberations that discuss privileged witness testimony. (Requirement 44199) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.19.a | 44206 | GENERAL INFORMATION: Roles and Responsibilities: The consultants shall not: Participate in deliberations (vote on findings). (Requirement 44206) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.19.b | 44207 | GENERAL INFORMATION: Roles and Responsibilities: The consultants shall not: Sign the mishap report. (Requirement 44207) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.19.c(1) | 44208 | GENERAL INFORMATION: Roles and Responsibilities: The consultants shall not: Read, listen to, or participate in witness interviews unless they are tasked to analyze interviews, and they have signed a nondisclosure agreement prepared by NASA Office of the General Counsel or Center Chief Counsel. (Requirement 44208) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.20(1) | 44214 | GENERAL INFORMATION: Roles and Responsibilities: If the Chair of the Investigating Authority chooses to use a person that is not a Federal employee as administrative support, that person shall sign a nondisclosure agreement prior to having access to any mishap data or International Traffic Arms Regulations (ITAR), Export Administration Regulations (EAR), proprietary, or privileged information. (Requirement 44214) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.21.a | 44217 | GENERAL INFORMATION: Roles and Responsibilities: Interim Response Team (IRT). The IRT shall: Notify the Center PAO about casualties, damages, and any potential hazards to the public, and notify legal advisors (as appropriate) (Requirement 44217) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.21.b | 44218 | GENERAL INFORMATION: Roles and Responsibilities: Interim Response Team (IRT). The IRT shall: Assist the incident commander, as requested. (Requirement 44218) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.21.d | 44220 | GENERAL INFORMATION: Roles and Responsibilities: Interim Response Team (IRT). The IRT shall: Only Federal employees on the IRT shall support the Center safety office in impounding data and collecting witness statements (written statements when possible) (Requirement 44220) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.21.f(1) | 44223 | GENERAL INFORMATION: Roles and Responsibilities: Interim Response Team (IRT). The IRT shall: Advise the supervisor if drug testing should be requested per the NPR 3792.1, Plan for a Drug-Free Workplace. (Requirement 44223) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.21.g | 44225 | GENERAL INFORMATION: Roles and Responsibilities: Interim Response Team (IRT). The IRT shall: Provide all available mishap data and evidence to the investigating authority. (Requirement 44225) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.21.h | 44226 | GENERAL INFORMATION: Roles and Responsibilities: Interim Response Team (IRT). The IRT shall: Support the AA/OPA (or designee), Center safety office, IRT, and CD or AA/OIA in the release of information to the press and media to alert Center personnel and the public of any known hazards and their potential effects, and provide instructions that will mitigate the risk and harm. (Requirement 44226) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.22 | 44227 | GENERAL INFORMATION: Roles and Responsibilities: Incident Commander. The incident commander shall implement the procedures outlined in the Center Mishap Preparedness and Contingency Plan to coordinate rescue activities, mitigate hazards, and safe and secure the mishap site. (Requirement 44227) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.a | 44229 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Support the development of the Center Mishap Preparedness and Contingency Plan, Program Mishap Preparedness and Contingency Plan(s), contract clauses, mishap investigation training, and a mishap investigation tool repository (that makes tools readily accessible to investigating authorities). (Requirement 44229) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.b | 44230 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Develop the Program/Project Mishap Preparedness and Contingency Plans for Programs/Projects as defined by NPR 7120.5 and that their Center manages. Programs with aircraft in the developmental, qualification, or certification phases of the program shall have a Program Mishap Preparedness and Contingency Plan that is tailored for the particular phase of the program. (Requirement 44230) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.c | 44231 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Ensure that their Center's employees are familiar with the roles and responsibilities as documented within the Center Mishap Preparedness and Contingency Plan and this NPR. (Requirement 44231) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.e | 44233 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Report the mishap to Headquarters per the reporting requirements defined in this NPR and to OSHA (when applicable). (Requirement 44233) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.f | 44234 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Support the incident commander as he/she safes and secures the mishap site. (Requirement 44234) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.g | 44235 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Impound data, records, equipment, and facilities. (Requirement 44235) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.h | 44236 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Advise the supervisor that drug testing should be initiated. (Requirement 44236) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.j(1) | 44238 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Ensure that mishap and close call information is entered in the Incident Reporting Information System (IRIS) per the requirements outline in this NPR. (Requirement 44238) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.k | 44240 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Verify the CAP is complete and all elements of the investigation have been completed. (Requirement 44240) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.L | 44241 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Retain mishap investigation records per NPR 1441.1 and physical evidence (debris) as necessary. (Requirement 44241) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.m | 44242 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Keep an updated list of all Center personnel that have training and experience in mishap investigation including information such as relevant training courses, date of training, recent participation in a mishap investigation, and security clearances. (Requirement 44242) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.23.n | 44243 | GENERAL INFORMATION: Roles and Responsibilities: Center Safety Office. The Center safety office shall: Establish a Center-specific process to disseminate to other Centers the final mishap report and to rapidly disseminate preliminary mishap and close call precautionary information that meets the PAO guidelines for release. (Requirement 44243) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.24.a | 44245 | GENERAL INFORMATION: Roles and Responsibilities: The Office of Security and Program Protection (OSPP) shall: Upon request from the appointing official, perform a classification review of the endorsed mishap report to determine if any section of the report (or the whole report) needs to be classified or if it may be authorized for public release. (Requirement 44245) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.25.a | 44247 | GENERAL INFORMATION: Roles and Responsibilities: The Center security office shall: Support the Incident Commander, Center safety office, and IRT in securing the mishap site and impounding data, records, equipment, and facilities. (Requirement 44247) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.26.a | 44249 | GENERAL INFORMATION: Roles and Responsibilities: Supervisors. Supervisors shall: Notify the Center safety office when a mishap or close call occurs. (Requirement 44249) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.26.b | 44250 | GENERAL INFORMATION: Roles and Responsibilities: Supervisors. Supervisors shall: Support the incident commander as he/she secures and safes the mishap site. (Requirement 44250) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.26.c | 44251 | GENERAL INFORMATION: Roles and Responsibilities: Supervisors. Supervisors shall: Initiate drug testing after a mishap if the mishap results in a fatality or personal injury requiring immediate hospitalization or in damage estimated to be in excess of $10,000 to government or private property. (Requirement 44251) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.26.d | 44252 | GENERAL INFORMATION: Roles and Responsibilities: Supervisors. Supervisors shall: Assist the investigating authority, as requested. (Requirement 44252) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.26.e | 44253 | GENERAL INFORMATION: Roles and Responsibilities: Supervisors. Supervisors shall: Complete the initial mishap or close call report in accordance with the Center Mishap Preparedness and Contingency Plan. (Requirement 44253) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.27.a | 44255 | GENERAL INFORMATION: Roles and Responsibilities: All Employees. All employees shall: If witness to, or involved in, a NASA mishap or close call, immediately notify both emergency response (e.g., 911, fire, ambulance, Center security office) of the need for assistance and a supervisor, management official, or a safety/health staff member of the circumstance of the mishap or close call. (Requirement 44255) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.27.b | 44256 | GENERAL INFORMATION: Roles and Responsibilities: All Employees. All employees shall: Complete witness statements prior to leaving the mishap investigation site, to the extent possible. (Requirement 44256) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.27.c | 44257 | GENERAL INFORMATION: Roles and Responsibilities: All Employees. All employees shall: Provide as much information as possible to the investigating authority. (Requirement 44257) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.28 | 44258 | GENERAL INFORMATION: Roles and Responsibilities: Center's Chief of Aircraft Operations. The Chief of Aircraft Operations shall notify the NTSB of a mishap involving aircraft per paragraph 1.6.6 of this NPR and complete NTSB Form 6120 per paragraph 1.6.8 of this NPR and NTSB requirements. (Requirement 44258) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.29.a | 44260 | GENERAL INFORMATION: Roles and Responsibilities: Contracting Officers. Contracting officers shall: Involve the Center safety office in the acquisition strategy planning activities for proposed contracts as detailed in NASA NFS Part 1807, "Acquisition Planning". (Requirement 44260) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.29.b | 44261 | GENERAL INFORMATION: Roles and Responsibilities: Contracting Officers. Contracting officers shall: Incorporate applicable mishap and close call reporting and investigating procedures and corrective action requirements detailed in the NFS into contracts and grants covering NASA programs and operations. (Requirement 44261) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.29.c | 44262 | GENERAL INFORMATION: Roles and Responsibilities: Contracting Officers. Contracting officers shall: Coordinate with the contractor and subcontractor sites to assist the investigating authority in gaining contractor site access, impound contractor data, and interview contractor personnel as permitted by the contract. (Requirement 44262) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.30.a(1) | 44264 | GENERAL INFORMATION: Roles and Responsibilities: CHMO. The CHMO shall: Serve as the appointing official for a mishap involving a human research subject participating in NASA-funded research at a grantee site, or at another offsite location, and obtain the concurrence from the Chief/OSMA on the investigating authority?s membership. (Requirement 44264) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.30.b | 44267 | GENERAL INFORMATION: Roles and Responsibilities: CHMO. The CHMO shall: Serve as an endorsing official for Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls involving an injury or fatality. (Requirement 44267) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.31 | 44268 | GENERAL INFORMATION: Roles and Responsibilities: Office of Institutions and Management, Office of Infrastructure and Administration, Aircraft Management Division (AMD). For Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls involving aircraft AMD shall serve as an endorsing official. (Requirement 44268) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.32.a | 44270 | GENERAL INFORMATION: Roles and Responsibilities: Office of the General Counsel. The Office of the General Counsel shall: Develop and implement procedures for collateral investigations that will be performed for mishaps and close calls that do not involve criminal activity. (Requirement 44270) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.04.32.b | 44271 | GENERAL INFORMATION: Roles and Responsibilities: Office of the General Counsel. The Office of the General Counsel shall: Assist the AA/OPA (or designee) in the review of the approved mishap report as it is being prepared for public release. (Requirement 44271) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.1 | 44277 | GENERAL INFORMATION: Notification and Reporting Requirements: Immediately after a mishap or close call, NASA employees shall notify the appropriate authorities in the manner specified in paragraph 1.4.27 of this NPR and the Center Mishap Preparedness and Contingency Plan. (Requirement 44277) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.2 | 44278 | GENERAL INFORMATION: Notification and Reporting Requirements: The Center safety office shall collect employee safety concerns, mishap reports, and close call reports through a Center process, review the employee reports, verify that they meet the definitions of mishap or close call found in Appendix A and Figure 1, and report those that are consistent with the NPR. (Requirement 44278) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.3 | 44279 | GENERAL INFORMATION: Notification and Reporting Requirements: Notify Office of Safety and Mission Assurance, Safety and Assurance Requirements Division (OSMA/SARD). After emergency response has been initiated, within one hour of the occurrence of a Type A mishap, Type B mishap, high-visibility mishap, or high-visibility close call, the Center safety office shall notify OSMA/SARD by calling 1.202.358.0006, or, if no answer, by calling the NASA Headquarters After Hours Contact Center at 1.866.230.6272. (Requirement 44279) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.3.1 | 44280 | GENERAL INFORMATION: Notification and Reporting Requirements: During this notification, the Center safety office shall provide the following information: the Center name, location of incident, time of incident, number of fatalities (if known), number of hospitalized employees (if known), type of injury (if known), type of damage (if known), contact person, contact person's phone number, and a brief description of the mishap. (Requirement 44280) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.3.a | 44281 | GENERAL INFORMATION: Notification and Reporting Requirements: Mishap notification must be acknowledged (verbally, e-mailed, or faxed) to meet the intent of this requirement. (Requirement 44281) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.3.b | 44282 | GENERAL INFORMATION: Notification and Reporting Requirements: Per NPR 7100.1, paragraph 11.4.1, this includes immediately reporting a human test subject injury or fatality that resulted in a loss of life, a permanent disability, hospitalization, extensive first aid, or lost workday[s]. (Requirement 44282) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.4 | 44283 | GENERAL INFORMATION: Notification and Reporting Requirements: Notify OSHA. Within 8 hours of a work-related mishap involving death of a Federal employee, or the hospitalization for inpatient care of three or more employees (provided at least one is a Federal employee), the Center safety office shall notify OSHA by calling the area office nearest the site of the mishap or OSHA's toll-free number, 1.800.321.6742. (Requirement 44283) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.4.1 | 44284 | GENERAL INFORMATION: Notification and Reporting Requirements: OSHA notification is required for any fatality or three or more hospitalizations that occur up to 30 workdays after the respective mishap. (Requirement 44284) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.4.2 | 44285 | GENERAL INFORMATION: Notification and Reporting Requirements: The Center safety office shall persist in making contact with OSHA to provide this report until OSHA has acknowledged receipt of the report. (Requirement 44285) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.4.3 | 44286 | GENERAL INFORMATION: Notification and Reporting Requirements: In notifying OSHA, the Center safety office shall provide OSHA with the following information: the establishment name, location of incident, time of incident, number of fatalities (if known), number of hospitalized employees (if known), contact person, contact person's phone number, and a brief description of the mishap. (Requirement 44286) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.4.4 | 44287 | GENERAL INFORMATION: Notification and Reporting Requirements: After notifying OSHA, the Center safety office shall inform OSMA/SARD that an oral report has been provided to OSHA. (Requirement 44287) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.5 | 44288 | GENERAL INFORMATION: Notification and Reporting Requirements: Within 24 hours of a Type A mishap, Type B mishap, high-visibility mishap, or high visibility close call, the Center safety office shall follow up the initial phone notification by sending an electronic notification to OSMA/SARD that includes the following information: Center submitting report; author of report; author's phone number and mail code; date report submitted; time report submitted; incident date; incident time; incident general location; exact location (if known); responsible organization; organization's point of contact; point of contact's phone number and mail code; mission affected; program impact (if known); number and type of injuries or fatalities (if known); type of damage to equipment, flight hardware, flight software, or facilities; estimate of direct cost of damage; and a brief description of the mishap or close call. (Requirement 44288) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.05.6.1 | 44290 | GENERAL INFORMATION: Notification and Reporting Requirements: The OIG and the Center's Office of the Chief Counsel or the NASA Office of the General Counsel shall be notified if it is suspected that a mishap resulted from criminal activity. (Requirement 44290) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.06.1 | 44294 | GENERAL INFORMATION: Additional Notification and Reporting Requirements for Aircraft Investigations: NASA employees shall report immediately to the Center safety office any of the aircraft mishaps or anomalies described in Figure 3, paragraph 1.2, and paragraph 1.6.2 of this NPR. (Requirement 44294) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.06.2(1) | 44295 | GENERAL INFORMATION: Additional Notification and Reporting Requirements for Aircraft Investigations: Employees shall report unexpected aircraft departure from controlled flight for all aircraft except the following high performance jet/test aircraft which can experience departure from controlled flight when engaged in flight test activities: F-15, F-16, F/A-18, T-38, OV-10, and T-34. (Requirement 44295) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.06.3 | 44297 | GENERAL INFORMATION: Additional Notification and Reporting Requirements for Aircraft Investigations: Immediately after the occurrence of an aviation mishap or NTSB-defined mishap or close call, the Center aircraft operator shall provide all the information listed in Figure 4 to the Center safety office and the Center Chief of Aircraft Operations. (Requirement 44297) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.06.7 | 44303 | GENERAL INFORMATION: Additional Notification and Reporting Requirements for Aircraft Investigations: In the event that the NTSB exercises its authority to investigate a NASA aircraft mishap, NASA shall conduct a separate investigation in accordance with this NPR. (Requirement 44303) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.06.8 | 44304 | GENERAL INFORMATION: Additional Notification and Reporting Requirements for Aircraft Investigations: Within 10 workdays of an aircraft mishap or close call that meets the reporting requirements as defined in Figure 3 and paragraph 1.6.2 of this NPR, the Center Chief of Aircraft Operations shall submit an NTSB Form 6120 to the NTSB regional office nearest to the location of the mishap or close call. (Requirement 44304) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.06.9 | 44305 | GENERAL INFORMATION: Additional Notification and Reporting Requirements for Aircraft Investigations: An unmanned aerial vehicle (UAV) is not currently considered an aircraft by the NTSB, consequently NTSB reporting requirements are not applicable to a UAV unless personnel are injured or the UAV comes down in a populated area outside a Center's gates. | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.a | 44308 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Investigating authority and ex officio signatures demonstrating their approval of the mishap report. (Requirement 44308) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.b | 44309 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Advisor(s) signatures demonstrating that he/she has reviewed the mishap report; that it meets NASA policies and procedures in his/her functional area; that any privileged or proprietary information, ITAR information, EAR information, or material subject to the Privacy Act has been identified and marked as nonreleasable to the public; and that sections that are releasable to the public are marked releasable and, to the best of his/her knowledge, are ready for public release (pending endorsements and Headquarters and Center public affairs authorization) (Requirement 44309) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.c | 44310 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: List of the investigating authority's consultants. (Requirement 44310) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.d | 44311 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: An executive summary that does not contain privileged or proprietary information, material subject to the Privacy Act, ITAR information, or EAR information. (Requirement 44311) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.e | 44312 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: The OSHA Final Mishap Summary (OSHA 301 Form: Injury and Illness Incident Report, or an equivalent form), if the mishap is an OSHA recordable incident. (Requirement 44312) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.f | 44313 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Description of the type of data gathered and evaluated during the investigation. (Requirement 44313) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.g | 44314 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Narrative description of the facts including what, when, and where. (Requirement 44314) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.h | 44315 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Timeline. (Requirement 44315) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.i | 44316 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Description of all structured analysis techniques used and how they contributed to determining the findings. (Requirement 44316) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.j | 44317 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Event and causal factor tree or similar graphical representation of the mishap. (Requirement 44317) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.k | 44318 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Description explaining why the mishap/close call occurred including all finding(s) such as proximate cause(s), root cause(s), contributing factor(s), failed barrier(s), observation(s), and the evidence upon which the findings are based. (Requirement 44318) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.L | 44319 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Conclusions and recommendations. (Requirement 44319) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.1.m | 44320 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The investigating authority shall conduct an investigation and include the following products in the mishap report according to the requirements listed in Figure 5: Minority report, if there is one. (Requirement 44320) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.2 | 44321 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: For close calls, where the potential for a Type A mishap or Type B mishap is significant, the Center Safety and Mission Assurance (SMA) director may consider application of a MIB or MIT investigation and their associated products. Serious workplace hazards previously unidentified and discovered as a result of inspections, audits, surveys, or concerns shall be investigated in the same manner as close calls. (Requirement 44321) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.07.4 | 44324 | GENERAL INFORMATION: Investigation Products for each Classification Level/Type of Investigation: The CD or AA/OIA shall elevate the level of investigation and required products of any mishap or close call upon the request of a higher authority, such as the Administrator, an Associate or Assistant Administrator, or upon his/her discretion. (Requirement 44324) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.08.1(1) | 44326 | GENERAL INFORMATION: Recording Requirements: Within 24 hours, the Center safety office shall ensure that all NASA mishaps and close calls are recorded in IRIS and include the following information: Center submitting report; author of report; author's phone number and mail code; date report submitted; time report submitted; incident date; incident time; incident general location; exact location (if known); responsible organization; organization's point of contact; point of contact's phone number and mail code; mission affected; program impact (if known); number and type of injuries or fatalities (if known); type of damage to equipment, flight hardware, flight software, or facilities; estimate of direct cost of damage; and a brief description of the mishap or close call. (Requirement 44326) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.08.2 | 44328 | GENERAL INFORMATION: Recording Requirements: For mishaps or close calls involving injury, the occupational health representative or other medical person shall provide the appropriate medical information regarding the person(s) injured and the nature of the injury(s) to the Center safety office for inclusion in IRIS. (Requirement 44328) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.08.3 | 44329 | GENERAL INFORMATION: Recording Requirements: The Center safety office shall record mishaps involving injury or illness to NASA civil service employees on the OSHA 300 Log as required by 29 CFR Part 1904.7. (Requirement 44329) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.08.4 | 44330 | GENERAL INFORMATION: Recording Requirements: The Center safety office shall ensure that the information recorded in IRIS is updated as new information becomes available and, at a minimum, verify information is up to date once every 30 days until the investigation is complete and the corrective actions are complete. (Requirement 44330) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.09.1 | 44332 | GENERAL INFORMATION: Collateral Investigations: The NASA investigating authority performing the safety investigation per this NPR shall have primacy over other Agency collateral investigations, with the exception of OIG criminal investigations. (Requirement 44332) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.09.2 | 44333 | GENERAL INFORMATION: Collateral Investigations: The investigating authority shall not distribute witness statements, notes, or transcripts of witness testimony taken during interviews, or medical records to the collateral investigation board or any other Agency, unless ordered in a court of law. (Requirement 44333) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.09.5 | 44337 | GENERAL INFORMATION: Collateral Investigations: Members of the investigating authority shall not participate in both collateral investigations or contractor and safety investigations for the same mishap or at the same time. (Requirement 44337) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.10.1 | 44339 | GENERAL INFORMATION: Investigations by Outside Authorities: NASA shall support investigations of NASA mishaps by other Federal agencies authorized to investigate NASA mishaps. (Requirement 44339) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.10.2 | 44340 | GENERAL INFORMATION: Investigations by Outside Authorities: NASA shall support investigations of mishaps experienced by other Federal agencies, foreign participants, and private industry in accordance with agreements. (Requirement 44340) | S | Y | Y | Safety | |||
| NPR 8621.1B | 1.10.5.1 | 44348 | GENERAL INFORMATION: Investigations by Outside Authorities: A contractor onsite injury or illness that is classified as a Type C mishap, Type D mishap, or Close Call may be investigated by the contractor per their contract. The mishap report must be delivered to NASA, and NASA has the option of completing the endorsement process. (Requirement 44348) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.a | 44358 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: The local mishap and close call notification, reporting, investigating, recording, and prevention policies and procedures. (Requirement 44358) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.b | 44359 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: The relationship between the emergency preparedness plan, the Center Mishap Preparedness and Contingency Plan, and Program Mishap Preparedness and Contingency Plans and which plan takes precedence given specific conditions. (Requirement 44359) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.c | 44360 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Management responsibilities for establishing mishap investigations. (Requirement 44360) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.d | 44361 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Procedures to appoint an IRT for those mishaps and close calls that are not covered by a program/project Mishap Preparedness and Contingency Plan (i.e., facility mishaps and close calls) (Requirement 44361) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.e | 44362 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Procedures to appoint a MIT or MI for Type C mishaps, Type D mishaps, and close calls that occur at the Center or involve programs/projects/activities managed by the Center. (Requirement 44362) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.f | 44363 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Roles and responsibilities of the incident commander (or the location in the emergency preparedness plan where these can be found) (Requirement 44363) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.g | 44364 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Procedures to impound appropriate records and equipment that may be involved in the mishap to prevent unauthorized use or modification. (Requirement 44364) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.h | 44365 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: List of responsible organizations, along with Center safety office personnel, that shall take immediate action to safeguard (or impound) appropriate records, equipment, and facilities and secure the mishap site. (Requirement 44365) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.i | 44366 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Identification of the location or space where impounded data, records, and equipment shall be stored and secured during an investigation. (Requirement 44366) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.j | 44367 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Procedures for release of impounded data, records, equipment, facilities, and the mishap site. (Requirement 44367) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.k | 44368 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Mishap report approval process for Type C mishaps, Type D mishaps, and close calls that occur at the Center or involve programs/projects/activities managed by the Center. (Requirement 44368) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.L | 44369 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: List of potential contractor support and onsite experts that can facilitate the immediate acquisition or purchase of products needed by the investigation board or team (e.g., high resolution cameras, recording devices, software, and others) (Requirement 44369) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.n | 44371 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: The information technology plan to provide computer data retrieval and data archive support to the investigating authority. (Requirement 44371) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.o | 44372 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Requisite security clearances, if any, for investigating authority members, chair, and ex officio. (Requirement 44372) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.p(1) | 44373 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: Description of the ?chain of custody process? that will be used to secure and safeguard personnel effects and sensitive information related to injured or deceased individuals. (Requirement 44373) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.1.1.q(1) | 44375 | READINESS TO CONDUCT INVESTIGATIONS: Headquarters Operations and Center Mishap Preparedness and Contingency Plan: The AA/OIA and each CD shall develop a Center Mishap Preparedness and Contingency Plan that describes the following: The expiration date. (Requirement 44375) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.b | 44380 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Is consistent with the Centers' Mishap Preparedness and Contingency Plans, for all Centers in which the program operates. (Requirement 44380) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.c | 44381 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Covers any information and procedures required specifically by the program that are not covered in the Centers' Mishap Preparedness and Contingency Plans (i.e., special procedures for safing, handling, or containing hazardous chemicals present in the program's/project's hardware). (Requirement 44381) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.d | 44382 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the procedures to comply with NPR 8621.1 notification, reporting, investigating, and recording requirements for all program/project activities not located at a Center or managed by a Center (e.g., program/project activities managed by Headquarters and located at a University, contractor site, or other off-Center location). (Requirement 44382) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.e | 44383 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the training requirements and the IRT's membership for mishaps and close calls that occur offsite, at offsite program/project (as defined by NPR 7120.5) contractor sites, or in flight. (Requirement 44383) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.f | 44384 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes any special procedures for the emergency response personnel, the IRT, and the incident commander that are not covered in the Center Mishap Preparedness and Contingency Plan or the emergency response plan (e.g., identification and handling of hazardous commodities specific to the program). (Requirement 44384) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.g | 44385 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the procedures to impound data, records, equipment, facilities, and property not located at a NASA facility. (Requirement 44385) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.h | 44386 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Identifies existing memoranda of agreement with national, state, and local organizations and agencies that may be utilized during a mishap investigation. (Requirement 44386) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.i | 44387 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes how offsite debris shall be collected, transported, and stored. (Requirement 44387) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.j | 44388 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the investigation and debris collection process required for any mishap or close call occurring in a foreign country. (Requirement 44388) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.k | 44389 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Requires that, for NASA-investigated mishaps, NASA personnel shall perform and control the impounding process. (Requirement 44389) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.L(1) | 44390 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Lists the personnel who will assist in performing the procedures to impound data, records, equipment, facilities, and other property. (Requirement 44390) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.m | 44392 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Identifies the national, state, and local (and, where applicable, international) organizations and agencies which are most likely to take part in debris collection; identifies the roles and responsibilities of each organization; and identifies a point of contact. (Requirement 44392) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.n | 44393 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Addresses the responsibilities and procedures for mishap investigation in the bilateral or multilateral agreements when the program involves international partners, program managers, and project managers. (Requirement 44393) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.o | 44394 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the resources that may be needed from other government agencies (e.g., Federal Emergency Management Agency, NTSB, DoD, Department of Justice) during a Type A mishap or Type B mishap investigation; identifies the point of contact and contact information for each of these Agencies; describes the procedures to acquire their assistance; and identifies the potential roles and responsibilities of each Agency. (Requirement 44394) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.p | 44395 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Includes a list of information such as databases, Web sites, documentation (including hardware history), drawings, basic system operation, and procedures that may be scrutinized in a Type A mishap involving loss of a vehicle and/or major facility damage and frequently updates this information so that it is easily deliverable to a mishap investigation board, and includes points of contact for the information. (Requirement 44395) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.q | 44396 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the information technology plan to provide computer data retrieval and data archive support to the investigating authority. (Requirement 44396) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.r | 44397 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the requisite security clearances, if any, for investigating authority members, chair, and ex officio participating in program/project investigations. (Requirement 44397) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.s(1) | 44398 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Describes the ?chain of custody process? that will be used to secure and safeguard personal effects and sensitive information related to injured or deceased individuals. (Requirement 44398) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.t | 44400 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: Names of key personnel from the Agency Public Affairs Office and Office of External Relations (OER) that should be notified for all Type A and Type B mishaps. (Requirement 44400) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.1.u(1) | 44401 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall concur in a Program/Project Mishap Preparedness and Contingency Plan that: States the expiration date. (Requirement 44401) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.2 | 44403 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program/project manager shall have the appropriate NASA Offices, at a minimum, General Counsel, OPA, OER, OSMA, and Centers (all Centers at which the program/project has activities) review and comment on the Mishap Preparedness and Contingency Plan prior to its approval. (Requirement 44403) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.2.5 | 44406 | READINESS TO CONDUCT INVESTIGATIONS: Program and Project Mishap Preparedness and Contingency Plans: The program or project (as defined per NPR 7120.5) Safety and Mission Assurance representative shall review and approve the Mishap Preparedness and Contingency Plan, verifying that it has the content required per this NPR (NPR 8621.1), prior to submittal for signature. (Requirement 44406) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.3.1(1) | 44408 | READINESS TO CONDUCT INVESTIGATIONS: Mishap Preparedness and Contingency Plan Practice: The Program and Center Mishap Preparedness and Contingency Plans, including emergency response where appropriate, shall be practiced during contingency simulations that occur prior to a major test, launch, or space activity. (Requirement 44408) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.5.1 | 44417 | READINESS TO CONDUCT INVESTIGATIONS: Contract Clauses: Contracting officers shall include appropriate mishap and close call notification, reporting, recording, and investigation procedures in NASA contracts. (Requirement 44417) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.5.2 | 44418 | READINESS TO CONDUCT INVESTIGATIONS: Contract Clauses: The Center safety office shall involve itself in acquisition strategy meetings per NFS Part 1807, Acquisition Planning, to assure that the appropriate mishap and close call reporting, investigating, and evaluation criteria are incorporated into contracts. (Requirement 44418) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.6.1.a(1) | 44421 | READINESS TO CONDUCT INVESTIGATIONS: Training: The Chief/OSMA with the support of the Center safety office shall provide the necessary training to ensure that at least one member of each investigating authority and the ex officio has, at a minimum, the following: Knowledge of the NASA mishap investigation policy and process as demonstrated via test. (Requirement 44421) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.6.1.b | 44423 | READINESS TO CONDUCT INVESTIGATIONS: Training: The Chief/OSMA with the support of the Center safety office shall provide the necessary training to ensure that at least one member of each investigating authority and the ex officio has, at a minimum, the following: Knowledge and skills to secure the site; preserve the mishap scene; interview witnesses; collect and impound data, records, equipment and facilities; create time lines; document facts; generate fault trees; perform barrier analysis; perform change analysis; create event and causal factor trees; obtain forensic analysis; integrate evidence; draw conclusions; generate recommendations; and generate mishap reports. (Requirement 44423) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.6.2.a | 44425 | READINESS TO CONDUCT INVESTIGATIONS: Training: The Chief/OSMA, with the support of the Center safety office, shall provide the necessary training to ensure that the human factors mishap investigator has the following: At a minimum, knowledge (as demonstrated via test or on-the-job training) of the method to identify unsafe acts and errors, identify types of errors, identify causal and contributing factors for errors, identify performance shaping factors, interview witnesses, analyze data, create timelines, perform fault tree analysis, perform barrier analysis, create event and causal factor trees, draw conclusions, and generate recommendations that will reduce human error or mitigate the negative consequence of human actions. (Requirement 44425) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.6.2.b | 44426 | READINESS TO CONDUCT INVESTIGATIONS: Training: The Chief/OSMA, with the support of the Center safety office, shall provide the necessary training to ensure that the human factors mishap investigator has the following: Basic knowledge of physical and psychological processes, capabilities, skill levels, and limitations of humans, such as the science and practical application of cognitive psychology, human reliability, anthropometrics, biomechanics, and human factors engineering applications to design. (Requirement 44426) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.6.3 | 44427 | READINESS TO CONDUCT INVESTIGATIONS: Training: The Center safety office shall develop and maintain NASA mishap investigation introductory training (onsite orientation training) that can be provided to the investigating authority and advisors upon their assignment to the investigation. (Requirement 44427) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.6.3.a | 44428 | READINESS TO CONDUCT INVESTIGATIONS: Training: The Center safety office shall develop and maintain NASA mishap investigation introductory training (onsite orientation training) that can be provided to the investigating authority and advisors upon their assignment to the investigation: The NASA mishap investigation introductory training shall include (at a minimum) a brief familiarization of the investigating authority's roles and responsibilities, NASA policy and procedures, and a description of root cause analysis. (Requirement 44428) | S | Y | Y | Safety | |||
| NPR 8621.1B | 2.7 | 44429 | READINESS TO CONDUCT INVESTIGATIONS: Tools: The Chief/OSMA supported by the Center safety offices shall identify candidate mishap investigation tools that can be implemented quickly and maintain a tool repository that makes these tools readily available to investigating authorities. (Requirement 44429) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.1 | 44432 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): After the initial notifications are made, the supervisor shall provide any necessary assistance to safe the mishap site until the emergency response and/or personnel from the Center safety office arrive. (Requirement 44432) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.2 | 44433 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): Upon notification of a mishap, the Center safety office shall initiate the Center Mishap Preparedness and Contingency Plan. (Requirement 44433) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.4 | 44435 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): In accordance with the Center Mishap Preparedness and Contingency Plan, the incident commander, with support from the responsible organization, IRT, Center safety office, Center security office, emergency response personnel, and supervisor, shall take immediate action to prevent further injury to personnel and/or damage to any property and secure the site. (Requirement 44435) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.5 | 44436 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): The incident commander and emergency response personnel shall have the authority to take action to mitigate dangerous conditions, direct emergency response actions, and/or clean up a hazardous materials release. (Requirement 44436) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.6 | 44437 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): The Center safety office and incident commander shall ensure protection of personnel from residual hazardous material prior to entry into the mishap site. (Requirement 44437) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.7 | 44438 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): The Center safety office and/or incident commander shall stipulate the type of personal protective equipment (PPE) required. (Requirement 44438) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.01.8 | 44439 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Safe the Mishap Site and Initiate Mishap Preparedness and Contingency Plan(s): Every professional supporting the investigation, including the IRT and investigating authority, shall adhere to the PPE requirements as defined by the Center safety office personnel or incident commander. (Requirement 44439) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.02 | 44440 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Notify Headquarters Office of Safety and Mission Assurance Within 1 Hour of Type A Mishap, Type B Mishap, High-Visibility Mishap, or High-Visibility Close Call: After emergency response has been initiated, within 1 hour of the occurrence of a Type A mishap, Type B mishap, high-visibility mishap, or high-visibility close call, the Center safety office shall notify Headquarters as described in paragraph 1.5.3 and NPR 7100.1, paragraph 11.4.1 (Per NPR 7100.1, paragraph 11.4.1, this includes immediately reporting a human test subject injury or fatality that resulted in a loss of life, a permanent disability, hospitalization, extensive first aid, or lost workday(s)). (Requirement 44440) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.03 | 44441 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Deploy IRT: In accordance with the Center or program/project Mishap Preparedness and Contingency Plan, the Center safety office or other designee shall deploy the IRT to initiate and support the investigation until a determination can be made as to the need for, and selection of, an investigating authority. (Requirement 44441) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.04 | 44442 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Notify Personnel and the Public of Potential Hazards: The AA/OPA (or designee), with the assistance of the Center safety office, IRT, and CD or AA/OIA shall immediately release information to the press and media to alert Center personnel and the public of any known hazards and their potential effects and provide instructions that will mitigate the risk and harm. (Requirement 44442) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.05.1 | 44444 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Secure the Site and Preserve Evidence: The incident commander, with support from the responsible organization, IRT, Center safety office, Center security office, emergency response personnel, and supervisor, shall take immediate action to prevent further injury to personnel and/or damage to any property, secure the site, limit unnecessary access, and preserve evidence. (Requirement 44444) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.05.2 | 44445 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Secure the Site and Preserve Evidence: Evidence preservation actions shall not hamper essential rescue operations. (Requirement 44445) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.06.1 | 44448 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Impound Data: The Center safety office, with the support of the IRT, Center security office personnel, and supervisor, shall impound all appropriate data, records, equipment, and facilities that may be involved in the mishap to prevent their unauthorized use or modification. (Requirement 44448) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.06.2 | 44449 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Impound Data: The Center safety office shall control access to all impounded items until they are released by the investigating authority per the procedures in the Center Mishap Preparedness and Contingency Plan. (Requirement 44449) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.06.4 | 44451 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Impound Data: For NASA mishaps occurring on international programs and/or involving program participants, autopsies shall be conducted in accordance with the bilateral/multilateral agreements. (Requirement 44451) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.06.5 | 44452 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Impound Data: For NASA mishaps occurring on international programs and/or involving international program participants, data, records, equipment, and facilities shall be impounded in accordance with the bilateral/multilateral agreements. (Requirement 44452) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.07 | 44453 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Initiate Drug Testing: If the mishap results in a fatality or personal injury requiring immediate hospitalization, or in damage estimated to be in excess of $10,000 to government or private property, the supervisor shall initiate post-accident/unsafe practice testing per NPR 3792.1, NASA Plan for a Drug-Free Workplace. (Requirement 44453) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.a(1) | 44455 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: All written witness statements obtained within the first 24 hours of the occurrence of a mishap or close call shall be considered privileged and protected. (Requirement 44455) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.b | 44457 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: All verbal witness statements and written statements given after 24 hours as part of a NASA mishap investigation, where the witness was explicitly informed that his/her account will not be released, shall be considered privileged and protected. (Requirement 44457) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.c(1) | 44458 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: When privilege has been granted by the IRT, Center safety office, or investigating authority, NASA shall make every effort to keep witness testimony (both written and verbal) confidential and privileged to the greatest extent permitted by law. (Requirement 44458) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.d(1) | 44460 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: The witness shall not be given a copy of the privileged written statement or transcripts of verbal witness statements given in the course of a NASA mishap investigation. (Requirement 44460) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.e | 44462 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: The Center safety office, with the support of the IRT, shall either request initial written statements from all persons who were involved in or witness to the mishap or document verbal accounts from such persons. (Requirement 44462) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.f(1) | 44463 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: Before a verbal witness statement is taken or an interview begins, the IRT, Center safety office, or investigating authority shall tell the witness whether the information gathered during the interview is confidential and privileged or not confidential and not privileged. (Requirement 44463) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.g | 44465 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: When conducting privileged witness interviews, the NASA investigating authority shall only have Federal employees present at the interview (with the exception of the interviewee), unless a contractor has been hired specifically to support interviews or provide technical guidance to the Board during the interviews and has signed a nondisclosure agreement prepared by General Counsel prior to participating in the interviews. (Requirement 44465) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.h(1) | 44466 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: When it is expected that an external investigating body will be the sole mishap investigation authority (e.g., for catastrophic vehicle failure such as Space Shuttle or International Space Station loss, or airplane loss), NASA shall not grant privilege to witnesses for either written witness statements or verbal witness statements, even when those statements are taken within the first 24 hours after the mishap. (Requirement 44466) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.i.1 | 44469 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: When the IRT, Center safety office, or investigating authority decides to take a verbal statement or interview a witness and keep that witness interview confidential, the interviewer shall read the statement in Figure 6 of this NPR and inform the witness that: The oral statement (taken during interview) and/or written statement will be retained as part of the investigation report background files but will not be released as part of the mishap report. (Requirement 44469) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.08.i.2 | 44470 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Collect Witness Statements: When the IRT, Center safety office, or investigating authority decides to take a verbal statement or interview a witness and keep that witness interview confidential, the interviewer shall read the statement in Figure 6 of this NPR and inform the witness that: NASA will make every effort to keep the testimony privileged to the greatest extent permitted by law. (Requirement 44470) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.1.1 | 44473 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information Concerning Casualties and Extensive Property Damage: The NASA Headquarters OPA must approve the release of all information related to NASA Type A mishaps and Type B mishaps, prior to its release to the press or public. (Requirement 44473) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.1.2 | 44474 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information Concerning Casualties and Extensive Property Damage: The CD or AA/OIA shall coordinate release of all information to the press and the public via the Center PAO. (Requirement 44474) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.1.3 | 44475 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information Concerning Casualties and Extensive Property Damage: The Center PAO shall, as appropriate, disseminate any preliminary information, video, and imagery to the public relating to the mishap. (Requirement 44475) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.2.1 | 44477 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information Concerning NASA-Owned Property Damage on Other Than Government-Owned Facilities, Overseas Tracking Stations, and Contractor-Owned Plants: When a mishap involving extensive damage to, or destruction of, NASA property occurs at other than government-owned facilities, overseas tracking stations, or contractor-owned plants, the contractor, tracking station manager, base commander, or other authority shall inform their point of contact at NASA. (Requirement 44477) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.2.2 | 44478 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information Concerning NASA-Owned Property Damage on Other Than Government-Owned Facilities, Overseas Tracking Stations, and Contractor-Owned Plants: The Center safety office cognizant of the mishap shall confirm that the mishap occurred to the NASA-owned property on other than government-owned facilities. (Requirement 44478) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.1 | 44480 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: NASA Employee Casualties. When a NASA employee is killed or receives a permanent disability within the confines of a Center, the Center PAO shall promptly announce to the public that a mishap has taken place and injuries or fatalities have occurred. (Requirement 44480) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.1.a | 44481 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: NASA Employee Casualties. When a NASA employee is killed or receives a permanent disability within the confines of a Center, the Center PAO shall promptly announce to the public that a mishap has taken place and injuries or fatalities have occurred: In the case of a fatality, the CD or AA/OIA or appropriate Headquarters Official-in-Charge, shall ensure that notification of the family has been made prior to release of the victim's name. (Requirement 44481) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.1.b | 44482 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: NASA Employee Casualties. When a NASA employee is killed or receives a permanent disability within the confines of a Center, the Center PAO shall promptly announce to the public that a mishap has taken place and injuries or fatalities have occurred: All initial announcements shall include what is known at the time, including the injuries or fatalities that have occurred and when additional information is expected to be available. (Requirement 44482) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.1.c | 44483 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: NASA Employee Casualties. When a NASA employee is killed or receives a permanent disability within the confines of a Center, the Center PAO shall promptly announce to the public that a mishap has taken place and injuries or fatalities have occurred: In the case of fatalities, release of the victim's name(s) shall be made as soon as possible after the notification of the next of kin. (Requirement 44483) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.2.a | 44485 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Military and Other Agency Personnel Casualties: The procedures for public announcements of mishaps involving military and other Federal personnel (including astronauts) detailed to NASA shall be the same as for NASA employees, with these additional requirements: The CD or AA/OIA shall inform the appropriate military service headquarters or other Federal agency of the mishap. (Requirement 44485) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.2.b | 44486 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Military and Other Agency Personnel Casualties: The procedures for public announcements of mishaps involving military and other Federal personnel (including astronauts) detailed to NASA shall be the same as for NASA employees, with these additional requirements: The CD or AA/OIA shall inform the Center PAO that the military service organization or other Federal agency has been notified of the mishap. (Requirement 44486) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.2.c | 44487 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Military and Other Agency Personnel Casualties: The procedures for public announcements of mishaps involving military and other Federal personnel (including astronauts) detailed to NASA shall be the same as for NASA employees, with these additional requirements: When the Center is on a military base, release of a victim's name shall be made according to procedures previously agreed upon by the base commander and CD or AA/OIA. (Requirement 44487) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.3.a | 44489 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Contractor and Grantee Employee Casualties. NASA does not assume responsibility for the release of information concerning mishaps involving contractor or grantee employees, except as follows: When a Type A mishap or Type B mishap occurs on a Center or at Headquarters or involves a NASA-managed program managed by that Center, the CD or AA/OIA, in coordination with the Center PAO/Headquarters PAO, shall announce as soon as possible that a mishap has occurred, as well as the number of known fatalities and/or injured. (Requirement 44489) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.3.b | 44490 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Contractor and Grantee Employee Casualties. NASA does not assume responsibility for the release of information concerning mishaps involving contractor or grantee employees, except as follows: The CD or AA/OIA shall not announce the identity of contractor or grantee personnel involved. (Requirement 44490) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.3.c | 44491 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Contractor and Grantee Employee Casualties. NASA does not assume responsibility for the release of information concerning mishaps involving contractor or grantee employees, except as follows: When a mishap occurs at a contractor's/grantee's plant engaged in NASA work, NASA has no responsibility to release information concerning the mishap and shall not issue statements as to the cause and extent of injury or damage. (Requirement 44491) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.4 | 44492 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Center Visitor Casualties. When a Type A mishap or Type B mishap occurs which involves visitors on a Center or at Headquarters, the CD or AA/OIA, in coordination with the Center PAO or Headquarters PAO, shall announce as soon as possible that a mishap occurred and the number of known fatalities and/or injured. (Requirement 44492) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.5 | 44493 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Overseas Mishaps. When a Type A mishap or Type B mishap occurs overseas, for example, at a tracking station or during an overseas rocket or balloon campaign involving NASA personnel, the Official-in-Charge shall release mishap information through the U.S. consular office in accordance with policies and procedures established by that office. (Requirement 44493) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.5.a | 44494 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Overseas Mishaps. When a Type A mishap or Type B mishap occurs overseas, for example, at a tracking station or during an overseas rocket or balloon campaign involving NASA personnel, the Official-in-Charge shall release mishap information through the U.S. consular office in accordance with policies and procedures established by that office: If the program involves foreign participation, the release of information shall be coordinated with the foreign entities sponsoring and participating in the program. (Requirement 44494) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.5.b | 44495 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Overseas Mishaps. When a Type A mishap or Type B mishap occurs overseas, for example, at a tracking station or during an overseas rocket or balloon campaign involving NASA personnel, the Official-in-Charge shall release mishap information through the U.S. consular office in accordance with policies and procedures established by that office: The Official-in-Charge shall notify, by the most expeditious means, the Chief/OSMA and the appropriate MDAA that a mishap has occurred overseas. (Requirement 44495) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.09.3.5.c | 44496 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Coordinate Release of Information: Release of Information to the Press and Public Concerning Casualties: Overseas Mishaps. When a Type A mishap or Type B mishap occurs overseas, for example, at a tracking station or during an overseas rocket or balloon campaign involving NASA personnel, the Official-in-Charge shall release mishap information through the U.S. consular office in accordance with policies and procedures established by that office: The MDAA shall notify, by the most expeditious means, the AA that a mishap has occurred overseas. (Requirement 44496) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.10.1 | 44499 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Notify OSHA: Within 8 hours of a work-related mishap involving death of a Federal employee, or the hospitalization for inpatient care of three or more employees (provided at least one is a Federal employee), the Center safety office shall notify OSHA per paragraph 1.5.4 of this NPR. (Requirement 44499) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.10.2 | 44500 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Notify OSHA: OSHA notification is required for any fatality and for three or more hospitalizations for inpatient care that occur up to 30 workdays after the respective mishap. (Requirement 44500) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.11.1 | 44502 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Record the Mishap: For Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls, the Center safety office shall send an electronic notification to OSMA/SARD containing information found in paragraph 1.5.3.2 of this NPR. (Requirement 44502) | S | Y | Y | Safety | |||
| NPR 8621.1B | 3.11.2(1) | 44503 | INITIAL RESPONSE TO A MISHAP OR CLOSE CALL: Record the Mishap: Within 24 hours, the Center safety office shall ensure that all NASA mishaps and close calls are recorded in IRIS in accordance with paragraph 1.8.1 of this NPR. (Requirement 44503) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.1.1 | 44507 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Determine the Appointing Official for Mishap and Close Call Investigation: The Chief/OSMA or the AA shall contact the Administrator within 1 hour of the initial notification of the Type A mishap to determine if the Administrator wishes to exercise appointment authority. (Requirement 44507) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.1.2 | 44508 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Determine the Appointing Official for Mishap and Close Call Investigation: Within 48 hours of a mishap or close call, the appointing official, as specified in Figure 5, shall appoint the investigating authority. (Requirement 44508) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.1.3 | 44509 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Determine the Appointing Official for Mishap and Close Call Investigation: The Administrator shall serve as appointing official for NASA joint participation on a MIB with the DoD and other agencies unless authority is delegated by existing agreements. (Requirement 44509) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.1 | 44511 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall select the members of the investigating authority, the chairperson, the executive secretary (when needed), and the support staff. (Requirement 44511) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.2 | 44512 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The MDAA shall request concurrence from the Chief/OSMA and the Chief Engineer on the proposed MIB membership for Type A mishaps, high-visibility mishaps, and high-visibility close calls in which he/she is the appointing official. (Requirement 44512) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.3 | 44513 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): For Type A mishaps and Type B mishaps, the investigating authority membership shall be determined with the advice of the Office of the General Counsel or the Office of the Chief Counsel, as appropriate. (Requirement 44513) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.4 | 44514 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): For Type A mishaps and Type B mishaps, high-visibility mishaps, and high-visibility close calls involving aircraft, the investigating authority membership shall be determined with the advice of the AMD. (Requirement 44514) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.6 | 44516 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): For Type C mishaps, Type D mishaps, and close calls, the CD or AA/OIA, or designee, shall seek advice concerning investigating authority membership from the Center safety office. (Requirement 44516) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.6.a | 44517 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): For Type C mishaps, Type D mishaps, and close calls, the CD or AA/OIA, or designee, shall seek advice concerning investigating authority membership from the Center safety office: The MDAA [or designee] shall seek advice concerning investigating authority membership from OSMA/SARD for NASA Type C mishaps, Type D mishaps, and close calls that involve Mission Directorate programs/projects/activities where the mishaps or close calls have occurred outside the Center's gates and are not managed by a Center, program, or project. (Requirement 44517) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.a | 44519 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: All members of the investigating authority (including the chairperson) and the executive secretary must be Federal personnel. (Requirement 44519) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.b | 44520 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The severity and complexity of the mishap to be investigated shall dictate the total number of members. (Requirement 44520) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.c | 44521 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The investigating authority shall consist of an odd number of voting members (including the chairperson). (Requirement 44521) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.d(1) | 44522 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The majority of the members of the investigating authority shall be independent from (have no responsibilities for) the operation or activity. (Requirement 44522) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.e | 44524 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: Members and the chairperson shall have the requisite security clearances as identified in the Center and/or program/project Mishap Preparedness and Contingency Plans. (Requirement 44524) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.f(1) | 44525 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The chairperson for the investigating authority shall be independent of the program or facility that experienced the mishap or close call. (Requirement 44525) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.g | 44527 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The members shall not be from the direct chain of authority responsible for day-to-day or line management oversight of the facility, area, or activity involved in the mishap or have a vested interest in the outcome of the investigation. (Requirement 44527) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.h | 44528 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The MIB and MIT shall be composed of a chairperson, members, and an ex officio. (Requirement 44528) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.i | 44529 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The MIB shall have at least five members for a Type A mishap and at least three members for a Type B mishap. (Requirement 44529) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.i.1 | 44530 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The MIB shall have at least five members for a Type A mishap and at least three members for a Type B mishap: The number of MIB members for high-visibility mishaps and high-visibility close calls shall be determined by the appointing official. (Requirement 44530) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.j(1) | 44531 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: For all Type A mishaps involving injury, illness, or fatality, the MIB shall include an occupational health physician as a member. (Requirement 44531) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.k(1) | 44534 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: For all Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls involving aircraft, the MIB shall have a member knowledgeable in aircraft operations, a member knowledgeable in aircraft maintenance, and a member knowledgeable in aviation safety. (Requirement 44534) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.L | 44536 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The MIB and MIT shall include a safety officer and a human factors mishap investigator as members. (Requirement 44536) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.n | 44538 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: The investigating authority shall have at least one member that has completed all the NASA mishap investigation training listed in paragraph 2.6.1.a in the last 1 year and paragraph 2.6.1.b in the last three years. (Requirement 44538) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.p | 44540 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: Members shall have sufficient experience and technical expertise to understand the technology and management interfaces related to the mishap. (Requirement 44540) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.2.7.r | 44542 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Members of the Investigating Authority (MIB, MIT, or MI): The appointing official shall use the following requirements to determine the composition of the investigating authority: For international programs, members shall be selected as described in bilateral/multilateral or international agreements. (Requirement 44542) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.3.1 | 44549 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Ex Officio: For any mishap or close call, the Chief/OSMA may serve as the ex officio or appoint, at his/her discretion, the ex officio; otherwise that selection shall be made by the senior SMA official in the appointing official's organization. (Requirement 44549) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.3.2(1) | 44550 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Ex Officio: For Type C mishaps, Type D mishaps, and close call investigations, the ex officio shall be at a level consistent with the authority level of the MIT chair. (Requirement 44550) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.3.3 | 44552 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Ex Officio: The ex officio shall be a Federal employee selected from personnel who have completed the NASA mishap investigation training or equivalent and have received refresher training in the last 3 years (if training was acquired more than 3 years ago) (Requirement 44552) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.3.5 | 44554 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select the Ex Officio: Only one ex officio shall be appointed to an investigating authority. (Requirement 44554) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.4.1 | 44556 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select Investigating Authority's Advisors: For all mishaps, the appointing official shall request that the appropriate mission support office appoint advisors to the investigating authority. (Requirement 44556) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.4.2 | 44557 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select Investigating Authority's Advisors: For Type A, Type B, and Type C mishaps, the investigating authority shall have a legal advisor, a public affairs advisor, an import/export control advisor, and (where appropriate) an external relations advisor. (Requirement 44557) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.4.3 | 44558 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Select Investigating Authority's Advisors: The advisors shall be NASA civil service employees selected from the respective mission support offices and be authorized to represent their mission support office's interests in the investigation. (Requirement 44558) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.6.1(1) | 44565 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Provide Support to Investigating Authority: The appointing official shall arrange for administrative, logistical, and information technology support to the investigating authority via the appointment letter or by contacting the appropriate CD or the AA/OIA, as appropriate. (Requirement 44565) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.6.2 | 44567 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Provide Support to Investigating Authority: The responsible organization, the Center safety office, and the CD or AA/OIA shall provide support as deemed necessary by the investigating authority. (Requirement 44567) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.7.1(1) | 44569 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Contents of the Appointment Letter or Appointment Orders: For Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls, the appointing official shall prepare an appointment letter to communicate the selection of the investigating authority members, the chairperson, the ex officio, and the advisors. (Requirement 44569) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.7.2 | 44571 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Contents of the Appointment Letter or Appointment Orders: The appointment letter shall identify the chairperson, membership (including ex officio), the legal advisor, the Headquarters public affairs advisor, import/export control advisor, the external relations advisor (where appropriate), the scope of the investigation, and the projected completion date. (Requirement 44571) | S | Y | Y | Safety | |||
| NPR 8621.1B | 4.7.3 | 44572 | SELECTING THE INVESTIGATING AUTHORITY AND SUPPORT: Contents of the Appointment Letter or Appointment Orders: The appointment letter/appointment orders shall relieve the investigating authority chairperson and members from other duties while they are engaged in investigation activities. (Requirement 44572) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.01.1 | 44575 | MISHAP INVESTIGATION PROCESS. Overview of the Mishap Investigation Process: The investigating authority shall use a structured technique to collect and review all available data, construct a timeline of events, conduct witness interviews, reconstruct the mishap or close call, and analyze the mishap occurrence to determine what happened, when it happened, and why it happened. (Requirement 44575) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.01.2 | 44576 | MISHAP INVESTIGATION PROCESS. Overview of the Mishap Investigation Process: Figure 7 illustrates the typical steps that the investigating authority shall perform during the mishap investigation. (Requirement 44576) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.02.a | 44578 | MISHAP INVESTIGATION PROCESS: Prepare for the Investigation: The investigating authority shall perform the following activities prior to arrival at the mishap site or shortly thereafter: Mishap investigation overview training. (Requirement 44578) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.02.a.1(1) | 44579 | MISHAP INVESTIGATION PROCESS: Prepare for the Investigation: The investigating authority shall perform the following activities prior to arrival at the mishap site or shortly thereafter: Mishap investigation overview training: The Investigating Authority members and advisors shall take the NASA ?Introduction to Mishap Investigation Training? upon their assignment to the investigation to familiarize themselves with NASA mishap investigation policies and procedures and root cause analysis. (Requirement 44579) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.02.b(1) | 44581 | MISHAP INVESTIGATION PROCESS: Prepare for the Investigation: The investigating authority shall perform the following activities prior to arrival at the mishap site or shortly thereafter: Assessment of personnel resources. (Requirement 44581) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.02.b.1 | 44583 | MISHAP INVESTIGATION PROCESS: Prepare for the Investigation: The investigating authority shall perform the following activities prior to arrival at the mishap site or shortly thereafter: Assessment of personnel resources: For Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close call investigation boards, the Chief/OSMA and Chief Engineer shall concur on membership changes prior to any MIB member additions or deletions. (Requirement 44583) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.02.c | 44584 | MISHAP INVESTIGATION PROCESS: Prepare for the Investigation: The investigating authority shall perform the following activities prior to arrival at the mishap site or shortly thereafter: Identification and selection of consultants as necessary. (Requirement 44584) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.02.d | 44585 | MISHAP INVESTIGATION PROCESS: Prepare for the Investigation: The investigating authority shall perform the following activities prior to arrival at the mishap site or shortly thereafter: Establishment of member duties, meeting times, and investigation schedules. (Requirement 44585) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.1.1 | 44588 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Verify that the Mishap Site is Safe and Secured: Upon arrival, the chairperson shall verify the site is safe and secured. (Requirement 44588) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.1.2 | 44589 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Verify that the Mishap Site is Safe and Secured: Neither the investigating authority nor the IRT has the authority to direct emergency response actions or activities to clean up a hazardous materials release. (Requirement 44589) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.1.2.1 | 44590 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Verify that the Mishap Site is Safe and Secured: Neither the investigating authority nor the IRT has the authority to direct emergency response actions or activities to clean up a hazardous materials release: These actions shall be directed by the incident commander. (Requirement 44590) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.2.1 | 44592 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Ensure that Evidence is Preserved and Impounded: The chairperson shall ensure that all the appropriate perishable evidence has been collected, photographed, documented, and/or impounded. (Requirement 44592) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.2.2 | 44593 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Ensure that Evidence is Preserved and Impounded: The chairperson shall ensure that all the necessary data, records, and equipment have been impounded and are being stored in a secure site. (Requirement 44593) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.2.3 | 44594 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Ensure that Evidence is Preserved and Impounded: The IRT, Center safety office personnel, emergency response personnel, and Center security office personnel shall provide the investigating authority with all evidence gathered at the scene; all data pertaining to the investigation, including impounded records; a status of impounded records/equipment; and a description of the actions taken. (Requirement 44594) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.03.2.4 | 44595 | MISHAP INVESTIGATION PROCESS: Verify that the Site is Safe and Secured and Ensure Evidence is Preserved/Impounded: Ensure that Evidence is Preserved and Impounded: When there is a mishap involving an injury or a fatality, the chairperson shall appoint a Federal employee to serve as an evidence custodian(s) who will implement the ?chain of custody process? documented in the Program Mishap Preparedness and Contingency Plan to provide physical security over and controlled access to the injured/deceased personal effects and related sensitive material. (Requirement 44595) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.04.3 | 44599 | MISHAP INVESTIGATION PROCESS: Gather Physical Evidence and Facts: Lack of physical evidence: If there is no recoverable physical evidence available, the investigating authority shall use existing program and/or mission documentation, any collected mission data, and applicable analytical techniques to determine the probable proximate cause(s) and probable root cause(s) of the mishap. (Requirement 44599) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.05.1 | 44601 | MISHAP INVESTIGATION PROCESS: Interview Witnesses: It is NASA's philosophy to interview witnesses rather than interrogate them. "Interview" connotes a cooperative meeting where the interviewer approaches the interviewee as an equal. The cooperation of the interviewee is sought; encouragement is given to tell the story freely without interruption or intimidation. An interview is usually conducted informally with a voluntary or cooperative answering of questions. However, the investigating authority may also conduct more formal interviews. Even in those cases, witnesses shall not be sworn in. (Requirement 44601) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.05.2.a | 44603 | MISHAP INVESTIGATION PROCESS: Interview Witnesses: The investigating authority shall interview mishap witnesses with two basic objectives in mind: To find out what the witness observed or did. (Requirement 44603) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.05.2.b | 44604 | MISHAP INVESTIGATION PROCESS: Interview Witnesses: The investigating authority shall interview mishap witnesses with two basic objectives in mind: To find out the witness's opinion of potential cause(s) of the mishap. (Requirement 44604) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.05.3 | 44605 | MISHAP INVESTIGATION PROCESS: Interview Witnesses: The investigating authority conducting the witness interviews shall perform all steps as listed in paragraph 3.8 of this NPR. (Requirement 44605) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.06.1 | 44607 | MISHAP INVESTIGATION PROCESS: Review and Analyze Data: The investigating authority shall determine the sequence of events and document them in a timeline. (Requirement 44607) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.06.2(1) | 44608 | MISHAP INVESTIGATION PROCESS: Review and Analyze Data: The investigating authority shall create a fault tree, or perform an equivalent analysis, to identify all potential cause(s) and contributing factor(s) to the mishap and the relationships among them. (Requirement 44608) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.06.3 | 44610 | MISHAP INVESTIGATION PROCESS: Review and Analyze Data: The investigating authority shall analyze all potential cause(s), including both technical and human cause(s) (Requirement 44610) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.07.1 | 44612 | MISHAP INVESTIGATION PROCESS: Draw Conclusions and Document Findings: The investigating authority shall evaluate all information collected during the course of the investigation, including, but not limited to, physical evidence, witness statements and testimony, and analytical results from testing and analysis; draw conclusions concerning what happened and why it happened; and document these as investigation findings. (Requirement 44612) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.07.2 | 44613 | MISHAP INVESTIGATION PROCESS: Draw Conclusions and Document Findings: All findings shall be supported by facts. (Requirement 44613) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.08.1 | 44615 | MISHAP INVESTIGATION PROCESS: Generate Recommendations: At a minimum, the investigating authority shall develop recommendations that address both the proximate cause(s) and the root cause(s) to prevent recurrence of the mishap or close call or similar mishaps and close calls. (Requirement 44615) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.08.2 | 44616 | MISHAP INVESTIGATION PROCESS: Generate Recommendations: The investigating authority shall verify that the recommendations are practical, feasible, and achievable. (Requirement 44616) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.08.3 | 44617 | MISHAP INVESTIGATION PROCESS: Generate Recommendations: The investigating authority shall prioritize the recommendations. (Requirement 44617) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.08.5 | 44619 | MISHAP INVESTIGATION PROCESS: Generate Recommendations: Upon receipt of a safety critical recommendation, the appointing official shall evaluate the recommendation and communicate the recommendation to the responsible program, project, organization, or external body to initiate implementation of corrective measures. (Requirement 44619) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.09(1) | 44620 | MISHAP INVESTIGATION PROCESS: When and How to Turn Over for Criminal Investigation: If it is reasonably suspected that a mishap resulted from criminal activity, the investigating authority shall halt the investigation; notify immediately the OIG and the Office of the General Counsel or the Office of the Chief Counsel, as appropriate; notify the appointing official; and wait for further direction. (Requirement 44620) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.10.1 | 44623 | MISHAP INVESTIGATION PROCESS: Release the Mishap Site and Restore Site Operations: Only the investigating authority shall release the mishap site for post-investigation cleanup or other activities. (Requirement 44623) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.10.2 | 44624 | MISHAP INVESTIGATION PROCESS: Release the Mishap Site and Restore Site Operations: Only the investigating authority shall release impounded data, records, equipment, or facilities. (Requirement 44624) | S | Y | Y | Safety | |||
| NPR 8621.1B | 5.10.3 | 44625 | MISHAP INVESTIGATION PROCESS: Release the Mishap Site and Restore Site Operations: The investigating authority shall not release data and records unless copies of the documents are made and retained with mishap investigation records. (Requirement 44625) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.01 | 44628 | The investigating authority shall develop a mishap report that contains the information as specified in paragraph 1.7 and Figure 5 in this NPR. (Requirement 44628) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.02 | 44629 | MISHAP REPORT: Develop the Mishap Report: Witness statements, witness names, and names of those involved in the mishap or related activities shall not be included as a part of the mishap report. (Requirement 44629) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.03.a | 44631 | MISHAP REPORT: Develop the Mishap Report: The mishap report shall be technically accurate; properly documented; easily understood; have traceability between facts, findings, and recommendations; and include the products required in Figure 5 in this NPR, in the following order: Section 1: Signature page(s), list of consultants, executive summary, and OSHA summary (when applicable) (Requirement 44631) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.03.b | 44632 | MISHAP REPORT: Develop the Mishap Report: The mishap report shall be technically accurate; properly documented; easily understood; have traceability between facts, findings, and recommendations; and include the products required in Figure 5 in this NPR, in the following order: Section 2: Narrative description and facts (what, when, where, how) (Requirement 44632) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.03.c | 44633 | MISHAP REPORT: Develop the Mishap Report: The mishap report shall be technically accurate; properly documented; easily understood; have traceability between facts, findings, and recommendations; and include the products required in Figure 5 in this NPR, in the following order: Section 3: Type of data gathered and data analysis (level of detail and products dependent upon Figure 5 in this NPR) (Requirement 44633) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.03.d | 44634 | MISHAP REPORT: Develop the Mishap Report: The mishap report shall be technically accurate; properly documented; easily understood; have traceability between facts, findings, and recommendations; and include the products required in Figure 5 in this NPR, in the following order: Section 4: Finding(s) (Requirement 44634) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.03.e | 44635 | MISHAP REPORT: Develop the Mishap Report: The mishap report shall be technically accurate; properly documented; easily understood; have traceability between facts, findings, and recommendations; and include the products required in Figure 5 in this NPR, in the following order: Section 5: Recommendation(s) (Requirement 44635) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.03.f | 44636 | MISHAP REPORT: Develop the Mishap Report: The mishap report shall be technically accurate; properly documented; easily understood; have traceability between facts, findings, and recommendations; and include the products required in Figure 5 in this NPR, in the following order: Section 6: Minority Report(s) (Requirement 44636) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.04 | 44637 | MISHAP REPORT: Develop the Mishap Report: The investigating authority shall include the mishap classification level (e.g., Type A, Type B, Type C, Type D, or close call) and the IRIS/NAARS case number in the mishap report title page and the report executive summary. (Requirement 44637) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.05 | 44638 | MISHAP REPORT: Develop the Mishap Report: The investigating authority shall describe, in the mishap report, the type of property damage, type of the mission failure, and/or describe the personal injury(ies)/illness/(es) (Requirement 44638) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.06 | 44639 | MISHAP REPORT: Develop the Mishap Report: The investigating authority shall describe, in the mishap report, the actual direct cost of the mishap or if the actual direct cost is not available, the estimate of the direct cost of the mishap. (Requirement 44639) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.08.a | 44642 | MISHAP REPORT: Develop the Mishap Report: If the investigating authority would like to receive a preliminary review of the mishap report and feedback concerning the adequacy of the report, they may provide a draft mishap report to the appointing official and request a preliminary review: This preliminary review must occur within the time allocated for the completion of the mishap report. (Requirement 44642) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.08.b | 44643 | MISHAP REPORT: Develop the Mishap Report: If the investigating authority would like to receive a preliminary review of the mishap report and feedback concerning the adequacy of the report, they may provide a draft mishap report to the appointing official and request a preliminary review: Upon receipt of a draft mishap report, the appointing official shall determine the appropriate preliminary review process and reviewing offices that should participate in the preliminary review, have them review the draft mishap report, and provide feedback to the investigating authority within 15 workdays. (Requirement 44643) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.08.c | 44644 | MISHAP REPORT: Develop the Mishap Report: If the investigating authority would like to receive a preliminary review of the mishap report and feedback concerning the adequacy of the report, they may provide a draft mishap report to the appointing official and request a preliminary review: The Center safety office or OSMA (dependent on level of investigation) shall participate in all preliminary reviews. (Requirement 44644) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.08.e | 44646 | MISHAP REPORT: Develop the Mishap Report: If the investigating authority would like to receive a preliminary review of the mishap report and feedback concerning the adequacy of the report, they may provide a draft mishap report to the appointing official and request a preliminary review: The chairperson and/or investigating authority is not required to make any changes to the mishap report with which he or she does not agree. (Requirement 44646) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.09 | 44647 | MISHAP REPORT: Develop the Mishap Report: All investigating authority members shall sign the completed mishap report. (Requirement 44647) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.a | 44649 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: The investigation was conducted in conformance with NASA policy and this NPR. (Requirement 44649) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.b | 44650 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: The investigation process was fair, independent, and nonpunitive. (Requirement 44650) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.c | 44651 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: The mishap report contains all the required elements. (Requirement 44651) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.d | 44652 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: The mishap report accurately identifies the proximate cause(s), root cause(s), and contributing factor(s) (Requirement 44652) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.e | 44653 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: Adequate facts have been gathered and analyzed to substantiate the findings. (Requirement 44653) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.f | 44654 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: The recommendations reasonably address the causes and findings. (Requirement 44654) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.g | 44655 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: The recommendations track one-to-one to each significant finding. (Requirement 44655) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.10.h | 44656 | MISHAP REPORT: Develop the Mishap Report: The ex officio shall sign the completed mishap report attesting to the following: If these conditions have not been met, the ex officio shall describe the mishap report's deficiencies in writing and sign and attach this description to the mishap report in lieu of signing the report. (Requirement 44656) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.11 | 44657 | MISHAP REPORT: Develop the Mishap Report: Each NASA advisor shall sign the mishap report stating that he/she has reviewed the mishap report, that it meets NASA policies and procedures in his/her functional area, and: (Requirement 44657) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.12 | 44662 | MISHAP REPORT: Develop the Mishap Report: The names of the consultants may be listed in the mishap report; however, the consultants shall not sign the mishap report. (Requirement 44662) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.1.13(1) | 44663 | MISHAP REPORT: Develop the Mishap Report: Within 75 workdays of the mishap or close call, the investigating authority shall submit the completed and signed mishap report to the appointing official. (Requirement 44663) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.2 | 44666 | MISHAP REPORT: Release Investigating Authority: Upon receiving the signed mishap report, the appointing official shall inform the investigating authority that the mishap report fulfills the requirements of the appointment letter and that they are released from duty. (Requirement 44666) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.1 | 44668 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: Upon receipt of the signed mishap report, the appointing official shall request the appropriate officials to review and endorse the mishap report (see Figure 5 of this NPR for endorsing officials) (Requirement 44668) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.a | 44670 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: The mishap report content is technically accurate and complete. (Requirement 44670) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.b | 44671 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: Proper analysis techniques were selected and completed correctly. (Requirement 44671) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.c | 44672 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: The mishap report adequately describes proximate cause(s), root cause(s), and contributing factor(s) (Requirement 44672) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.d | 44673 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: There are adequate facts to substantiate the findings. (Requirement 44673) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.e | 44674 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: Recommendations track one-to-one to each finding. (Requirement 44674) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.f | 44675 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: Recommendations are practical, feasible, achievable, and will, in the opinion of the reviewer, prevent recurrence of similar mishaps or close calls. (Requirement 44675) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.2.g | 44676 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: The review and endorsement process should verify, at a minimum, the following: Proprietary information, ITAR information, EAR information, material subject to the Privacy Act, or privileged information that should not be released has been identified. (Requirement 44676) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.3 | 44677 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: For those mishap or close call reports where the Chief/OSMA is an endorsing official, all endorsements shall be forwarded to OSMA for review prior to completion of the Chief/OSMA endorsement. (Requirement 44677) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.4 | 44678 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: Within 30 workdays, the endorsing officials will provide their signed endorsement, recommendation for mishap report approval or rejection, and (when applicable) comments related to amplification or disagreement with elements of the report to the appointing official. (These endorsements and comments (when applicable) shall be attached to the mishap report and become part of the permanent record). (Requirement 44678) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.5 | 44679 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: Within 5 workdays, the appointing official shall attach all endorsements and comments (including his/her own) to the mishap report, review the comments, and determine if the report is approved or rejected based on the review and comments/direction from endorsing officials. (Requirement 44679) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.3.6 | 44680 | MISHAP REPORT: Review, Endorse, and Approve Mishap Report: If the appointing official rejects the mishap report, he/she must provide a written description of the deficiencies that warrant this rejection, attach this to the mishap report, send the report to the Center safety office (or OSMA for Type A mishaps, Type B mishaps, high visibility mishaps, and high-visibility close calls) for records retention, and charter a new investigation. (Requirement 44680) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.4.1(1) | 44682 | MISHAP REPORT: Authorize Mishap Report for Public Release: If the mishap report is approved, the appointing official shall immediately send the approved report with endorsements/comments to the Export Administrator, the Center PAO, Office of Security and Program Protection, and then to OPA, Procurement, and legal counsel for review. (Requirement 44682) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.4.2(1) | 44684 | MISHAP REPORT: Authorize Mishap Report for Public Release: Within 10 workdays of the request, the Export Administrator, OPA, Office of Security and Program Protection, Procurement, and legal counsel shall review the mishap report and specify in writing which sections of the mishap report are authorized for public release. (Requirement 44684) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.5.1 | 44687 | MISHAP REPORT: Distribute Mishap Report: Upon receipt of notification that the mishap report is authorized for public release, the appointing official shall send the approved mishap report with authorization comments to OSMA/SARD and the Center safety office (dependent upon level of investigation). (Requirement 44687) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.5.2 | 44688 | MISHAP REPORT: Distribute Mishap Report: Within 10 workdays, the MDAA or the Center safety office shall distribute the mishap report to the appropriate NASA programs and organizations including, but not limited to, the responsible organization and/or program, all Center safety offices, the CHMO (when an injury or fatality has occurred), and AMD (when the mishap involved an aircraft). (Requirement 44688) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.5.3 | 44689 | MISHAP REPORT: Distribute Mishap Report: Within 15 workdays, the Center safety office shall distribute information about the Type A mishap or Type B mishap via "weekly safety highlights" (or equivalent) to Center personnel, including a brief description of what caused the mishap and how it can be prevented. (Requirement 44689) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.5.4 | 44690 | MISHAP REPORT: Distribute Mishap Report: The AA/OPA shall determine whether a mishap report, whatever its origin, shall be issued from Headquarters or the Center. (Requirement 44690) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.5.5 | 44691 | MISHAP REPORT: Distribute Mishap Report: Generally, the appropriate public affairs officer shall make the news release on the mishap report available simultaneously at Headquarters and the appropriate Center. (Requirement 44691) | S | Y | Y | Safety | |||
| NPR 8621.1B | 6.5.6 | 44692 | MISHAP REPORT: Distribute Mishap Report: The appropriate public affairs officer shall make the mishap report available to the public at the same time. (Requirement 44692) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.1.1 | 44698 | POST-INVESTIGATION ACTIVITIES: Develop CAP: Immediately after the mishap report has been authorized for public release, the appointing official shall direct the responsible organization or program/project to develop a CAP for those recommendations approved by the endorsing officials. (Requirement 44698) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.2.1.a | 44703 | POST-INVESTIGATION ACTIVITIES: CAP Contents: The CAP shall include the following: A description of the corrective actions along with a designation of the organization(s) responsible for implementing the corrective actions and a completion date for each corrective action. (Requirement 44703) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.2.1.b | 44704 | POST-INVESTIGATION ACTIVITIES: CAP Contents: The CAP shall include the following: Which NASA organization, contractor organization, or grantee organization (to the lowest level) is responsible for ensuring the corrective action is completed. (Requirement 44704) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.2.1.c | 44705 | POST-INVESTIGATION ACTIVITIES: CAP Contents: The CAP shall include the following: A matrix or other means of matching corrective actions to all findings and recommendations. (Requirement 44705) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.2.1.d | 44706 | POST-INVESTIGATION ACTIVITIES: CAP Contents: The CAP shall include the following: A review of any process changes required based on corrective actions. (Requirement 44706) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.3.2 | 44709 | POST-INVESTIGATION ACTIVITIES: Review and Approve CAP: Based on the results of these reviews and his/her own review, the appointing official shall either accept or reject the CAP. (Requirement 44709) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.3.3 | 44710 | POST-INVESTIGATION ACTIVITIES: Review and Approve CAP: If the plan is rejected, the appointing official shall return the CAP, with comments, to the responsible organization or program/project for revision and resubmission. (Requirement 44710) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.3.4 | 44711 | POST-INVESTIGATION ACTIVITIES: Review and Approve CAP: The appointing official shall determine the timeframe for resubmission of the CAP. (Requirement 44711) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.4.1 | 44713 | POST-INVESTIGATION ACTIVITIES: Implement CAP: The responsible organization shall implement the corrective actions as directed by the appointing official and as documented in the approved CAP. (Requirement 44713) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.4.2 | 44714 | POST-INVESTIGATION ACTIVITIES: Implement CAP: The responsible organization shall track the corrective action performance and completion in IRIS and inform the appointing official of the status of the actions at intervals determined by the appointing official. (Requirement 44714) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.4.4 | 44716 | POST-INVESTIGATION ACTIVITIES: Implement CAP: The Center safety office shall assist the responsible organization, if needed, to enter updates into IRIS, as described in the Center Mishap Preparedness and Contingency Plan. (Requirement 44716) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.4.5 | 44717 | POST-INVESTIGATION ACTIVITIES: Implement CAP: The Center safety office shall enter into IRIS the actual direct cost of the mishap or if the actual direct cost is not available, the estimate of the direct cost of the mishap. (Requirement 44717) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.4.7 | 44719 | POST-INVESTIGATION ACTIVITIES: Implement CAP: The appointing official shall assess and, if warranted and desired, approve any changes to the CAP. (Requirement 44719) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.4.8 | 44720 | POST-INVESTIGATION ACTIVITIES: Implement CAP: The appointing official shall send approved changes to the responsible organization and the Center safety office. (Requirement 44720) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.5.1 | 44722 | POST-INVESTIGATION ACTIVITIES: Monitor and Closeout CAP: The applicable Center safety office shall monitor corrective action activities to determine if they were carried out according to the plan and report noncompliance to the appointing official. (Requirement 44722) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.1 | 44726 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: Following the authorization of the mishap report for public release, the appointing official shall designate a person or team of persons to develop the lessons learned identified in the mishap report. (Requirement 44726) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.2 | 44727 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: The individual or team shall develop lessons learned that, at a minimum, include the executive summary, findings, and recommendations from the mishap report that are authorized for public release. (Requirement 44727) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.3 | 44728 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: Program and/or project managers that have mission failures or NASA mishaps for long-duration missions shall develop lessons learned for possible application to existing or future programs. (Requirement 44728) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.4 | 44729 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: Within 10 workdays of being tasked, the person or team assigned to develop lessons learned shall submit the prepared lessons learned to the appointing official. (Requirement 44729) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.5.a | 44731 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: Prior to submission into NASA Lessons Learned Information System (LLIS), NASA program and policy officials, including, but not limited to, legal, import/export control, and public affairs, shall: Review the proposed lessons learned to ensure they are consistent with NASA policy and do not contain any privileged or proprietary information, ITAR information, EAR information, or material subject to the Privacy Act. (Requirement 44731) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.6 | 44733 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: Based on the results of the review of the lessons learned, the appointing official shall either accept or reject the lessons learned and forward accepted lessons learned to the NASA LLIS. (Requirement 44733) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.6.7 | 44734 | POST-INVESTIGATION ACTIVITIES: Develop, Disposition, Submit, and Approve Lessons Learned: OCE and program managers shall review the LLIS quarterly to determine if any mishap lessons learned should be translated into programmatic or Agency requirements. (Requirement 44734) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.7.1 | 44736 | POST-INVESTIGATION ACTIVITIES: Conclude Mishap Activities: The appointing official shall submit the mishap activities completion statement to the responsible organization, OSMA/SARD (For Type A mishaps, Type B mishaps, high-visibility mishaps, and high-visibility close calls), the Center safety office, and other appropriate organizations indicating that the investigation was performed; the CAP was developed, implemented, and closed; and the lessons learned have been entered into the NASA LLIS. (Requirement 44736) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.8.1 | 44739 | POST-INVESTIGATION ACTIVITIES: Record and Retain Evidence: The final CAP and approved lessons learned shall be filed with the official approved mishap report in a location specified in the Center Mishap Preparedness and Contingency Plan. (Requirement 44739) | S | Y | Y | Safety | |||
| NPR 8621.1B | 7.8.3(1) | 44741 | POST-INVESTIGATION ACTIVITIES: Record and Retain Evidence: The CAP, lessons learned, and witness statements, plus other records documenting the investigation, shall be managed and dispositioned by the Center safety office in accordance with NPR 1441.1, NASA Records Retention Schedule. (Requirement 44741) | S | Y | Y | Safety | |||
| SAF-159 | NPR 8715.3C | 09.3.4.b | 46690 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in applying any special safety provisions to grants or cooperative agreements (see paragraph 2.7). (Requirement 46690) | S | Y | Y | Mgmt | ||
| SAF-160 | NPD 8700.1C | 1.i | 1067 | POLICY: It is NASA policy to-- Report and track to resolution all corrective actions resulting from investigations of mishaps, incidents, nonconformances, and anomalies; and distribute and use lessons learned to improve activities and operations. (Requirement 1067) | S | Y | Y | Quality | ||
| NPD 8700.1C | 5.e.4 | 1085 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Use and distribute lessons learned to enhance the probability of mission success and establish recurrence control through a closed-loop corrective/preventative action system. (Requirement 1085) | S | Y | Y | Quality | |||
| CxP 70059 | 2.1.12 | SAF-1009 | NASA-STD-8739.8 | 6.8.5 | 33271 | Records shall be maintained and readily available for review (e.g, training, testing, and certification/recertification status of personnel). (Requirement 33271) | S | Y | Y | SWA |
| NPR 8715.3C | 01.02.1.g | 45572 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that trained individual(s) determine the corrective actions needed for mitigating or controlling safety risk for all activities. (Requirement 45572) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 07.4.1.a | 46557 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: Personnel who perform or control hazardous operations or use or transport hazardous material have been trained and certified with the necessary knowledge, skill, judgement, and physical ablitiy (if specified in the job classification) to do the job safely. (Requirement 46557) Note: Many NASA operations involve hazardous materials or chemicals, technology, or systems with potential hazards to life, the environment, or property. | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.b | 46558 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: Personnel obtain hazardous operation safety certification for those tasks that potentially have an immediate danger to the individual (death/injury to self) if not done correctly, or could create a danger to other individuals in the immediate area (death or injury), or are a danger to the environment. (Requirement 46558) Note: Detailed training and certification requirements may be found in specific NASA Standards; e.g., NASA-STD-8719.9, Standard for Lifting Devices and Equipment, or NSS 1740.12, Safety Standard for Explosives, Propellants and Pyrotechnics. | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.c | 46559 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: All contractor personnel engaged in potentially hazardous operations or hazardous material handling are certified via a process similar to that for NASA personnel. (Requirement 46559) | S | Y | Y | Safety | |||
| SAF-1010 | NPR 8715.3C | 01.02.1.g | 45572 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that trained individual(s) determine the corrective actions needed for mitigating or controlling safety risk for all activities. (Requirement 45572) | S | Y | Y | Mgmt | ||
| NPR 8715.3C | 03.15.4.a | 46232 | Operational Safety: Non-Ionizing Radiation: Center Directors and project managers shall ensure that: Only trained and certified employees are assigned to install, adjust, and operate laser equipment. (Requirement 46232) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.15.4.b | 46233 | Operational Safety: Non-Ionizing Radiation: Center Directors and project managers shall ensure that: Personnel operating lasers are trained and certified in accordance with Chapter 7 of this NPR. (Requirement 46233) | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.a | 46557 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: Personnel who perform or control hazardous operations or use or transport hazardous material have been trained and certified with the necessary knowledge, skill, judgement, and physical ablitiy (if specified in the job classification) to do the job safely. (Requirement 46557) Note: Many NASA operations involve hazardous materials or chemicals, technology, or systems with potential hazards to life, the environment, or property. | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.b | 46558 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: Personnel obtain hazardous operation safety certification for those tasks that potentially have an immediate danger to the individual (death/injury to self) if not done correctly, or could create a danger to other individuals in the immediate area (death or injury), or are a danger to the environment. (Requirement 46558) Note: Detailed training and certification requirements may be found in specific NASA Standards; e.g., NASA-STD-8719.9, Standard for Lifting Devices and Equipment, or NSS 1740.12, Safety Standard for Explosives, Propellants and Pyrotechnics. | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.c | 46559 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: All contractor personnel engaged in potentially hazardous operations or hazardous material handling are certified via a process similar to that for NASA personnel. (Requirement 46559) | S | Y | Y | Safety | |||
| SAF-87 | NPR 8715.3C | 01.02.1.g | 45572 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that trained individual(s) determine the corrective actions needed for mitigating or controlling safety risk for all activities. (Requirement 45572) | S | Y | Y | Mgmt | ||
| NPR 8715.3C | 07.4.1.a | 46557 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: Personnel who perform or control hazardous operations or use or transport hazardous material have been trained and certified with the necessary knowledge, skill, judgement, and physical ablitiy (if specified in the job classification) to do the job safely. (Requirement 46557) Note: Many NASA operations involve hazardous materials or chemicals, technology, or systems with potential hazards to life, the environment, or property. | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.b | 46558 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: Personnel obtain hazardous operation safety certification for those tasks that potentially have an immediate danger to the individual (death/injury to self) if not done correctly, or could create a danger to other individuals in the immediate area (death or injury), or are a danger to the environment. (Requirement 46558) Note: Detailed training and certification requirements may be found in specific NASA Standards; e.g., NASA-STD-8719.9, Standard for Lifting Devices and Equipment, or NSS 1740.12, Safety Standard for Explosives, Propellants and Pyrotechnics. | S | Y | Y | Safety | |||
| NPR 8715.3C | 07.4.1.c | 46559 | Safety Training and Personnel Certification: Personnel Safety Certification Programs for Potentially Hazardous Operations and Materials: Mission Directorate Associate Administrators, Center Directors, project managers, and line managers shall ensure that: All contractor personnel engaged in potentially hazardous operations or hazardous material handling are certified via a process similar to that for NASA personnel. (Requirement 46559) | S | Y | Y | Safety | |||
| CxP 70059 | 2.1.13 | SAF-1011 | NPR 8715.3C | 03.08.2.a | 46070 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Identify, assess, analyze, and develop adequate safety controls for all hazardous operations. (Requirement 46070) | S | Y | Y | Safety |
| NPR 8715.3C | 03.08.2.b | 46071 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all hazardous operations have a Hazardous Operating Procedure or a Hazardous Operating Permit (HOP). (Requirement 46071) Note: HOPs consist of a detailed plan listing step-by-step functions or tasks to be performed on a system or equipment to ensure safe and efficient operations. HOPs list special precautions, start and stop time of the operation, and the approving supervisor(s). Certain operations (e.g., rigging, high voltage) depend on adherence to overall standards and general guidelines and specific training as opposed to HOPs for each specific operation. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.c | 46072 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all HOPs developed at NASA sites or for NASA operations have concurrence from the responsible fire protection or safety office. (Requirement 46072) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.d | 46073 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all HOPs are approved by the NASA Center safety office or the contractor safety office to assure that a review has been performed. (Requirement 46073) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.e | 46074 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that deviations or changes to HOPs are also approved by the cognizant NASA Center safety office or contractor safety office to assure that a review has been preformed. (Requirement 46074) Note: If deviations or changes to HOPs are approved by the contractor's safety office, a copy should be forwarded to the local NASA safety office for informational purposes. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.f | 46075 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure facility operating instructions and changes are developed based on the facility mission and operational requirements. (Requirement 46075) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.g | 46076 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all procedures include sufficient detail to identify residual hazards and cautions to NASA personnel. (Requirement 46076) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.h | 46077 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that hazardous procedures are marked conspicuously on the title page; e.g., "THIS DOCUMENT CONTAINS HAZARDOUS OPERATIONS PROCEDURES," to alert operators that strict adherence to the procedural steps and safety and health precautions contained therein is required to ensure the safety and health of personnel and equipment. (Requirement 46077) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.k | 46080 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that personnel use the buddy system whereby an adjacent or nearby person not directly exposed to the hazard serves as an observer to render assistance where the risk of injury is high. (Requirement 46080) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.09.2.d | 46088 | Operational Safety: Laboratory Hazards: Center Directors and project managers shall ensure that: The design, fabrication, or modification of laboratories used for experimentation, testing, or analyses performed on human or animal subjects are coordinated in advance with the OCHMO at (202) 358-2390. (Requirement 46088) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.2 | 46195 | Operational Safety: Test Operations Safety: Center Directors and project managers shall ensure that test plans are developed and evaluated to assure test performance within safe operating limits. (Requirement 46195) Note: Evaluations will address the test article, test facility, testing procedures, test conditions, operator involvement, and potential risk to adjoining facilities and personnel. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.3.2 | 46198 | Operational Safety: Test Operations Safety: Safety Documentation: Center Directors and project managers shall ensure that established test controls are clearly identified in test drawings, facility drawings, and test procedures. (Requirement 46198) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.a | 46201 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Design test systems such that test personnel or critical test hardware are not subject to a test environment wherein a credible single-point failure (e.g., power loss) could result in injury, illness, or loss to the critical test hardware. (Requirement 46201) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.b | 46202 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Construct all systems (electrical, mechanical, pneumatic, and/or hydraulic) so that no single failure could cause a critical condition. (Requirement 46202) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.d | 46204 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Calibrate and certify safety-critical instrumentation before test operations and as required by test documentation or the test organization's internal procedures. (Requirement 46204) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.e | 46205 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure all personnel involved in test are informed of potential hazards, safety procedures, and protective measures. (Requirement 46205) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.f | 46206 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure the availability of appropriate emergency medical treatment facilities. (Requirement 46206) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.g | 46207 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Conduct formal reviews of engineering designs that are complicated or potentially hazardous to facilities. (Requirement 46207) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.h | 46208 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure test results report include anomalies, safety implications, and lessons learned. (Requirement 46208) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.6.1 | 46214 | Operational Safety: Test Operations Safety: Pre-test Meeting: Center Directors and project managers shall ensure that a pre-test meeting is conducted with all involved personnel to discuss the facility, design, instrumentation, safety, and operator training and certification. (Requirement 46214) Note: The meeting should also establish the test plan, identify test constraints to ensure facility safety, and determine test article readiness, ground support equipment readiness, and procedural readiness. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.a | 46218 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Tests involving hazardous substances, where human test subjects or test team personnel may be exposed, are reviewed for adequacy of test team safeguards, including direct communication between the test subjects and the test conductors. (Requirement 46218) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.b | 46219 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A facility environmental control system failure or failure in the distribution system affecting one pressure-suited occupant shall not affect any other pressure-suited occupant for test requiring crew participation in a pressure suit. (Requirement 46219) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.c | 46220 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A means exists for immediately detecting an incipient fire or other hazardous condition in each crew compartment of any test area. (Requirement 46220) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.d | 46221 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Automatic fire detection is provided for critical areas not suitable for visual monitoring. (Requirement 46221) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.e | 46222 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed for timely and unencumbered rescue of incapacitated crew members. (Requirement 46222) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.f | 46223 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Software controlling crewed test systems are thoroughly analyzed to ensure that no command results in death or injury to the test subjects (Requirement 46223) Note: Policies and requirements for software are given in NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA Software Engineering Requirements. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.g | 46224 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed to provide for manual overrides of critical software commands to ensure the safety of test subjects during any system event or test scenario (normal operation, malfunction, emergency). (Requirement 46224) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.h | 46225 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Manual overrides of critical software commands support safe test termination and egress of test subjects. (Requirement 46225) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.i | 46226 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Medical resources and facilities needed for response are alerted, on-call, and immediately available as needed. (Requirement 46226) | S | Y | Y | Safety | |||
| SAF-1012 | NPR 8715.3C | 03.08.2.a | 46070 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Identify, assess, analyze, and develop adequate safety controls for all hazardous operations. (Requirement 46070) | S | Y | Y | Safety | ||
| NPR 8715.3C | 03.08.2.b | 46071 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all hazardous operations have a Hazardous Operating Procedure or a Hazardous Operating Permit (HOP). (Requirement 46071) Note: HOPs consist of a detailed plan listing step-by-step functions or tasks to be performed on a system or equipment to ensure safe and efficient operations. HOPs list special precautions, start and stop time of the operation, and the approving supervisor(s). Certain operations (e.g., rigging, high voltage) depend on adherence to overall standards and general guidelines and specific training as opposed to HOPs for each specific operation. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.c | 46072 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all HOPs developed at NASA sites or for NASA operations have concurrence from the responsible fire protection or safety office. (Requirement 46072) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.d | 46073 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all HOPs are approved by the NASA Center safety office or the contractor safety office to assure that a review has been performed. (Requirement 46073) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.e | 46074 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that deviations or changes to HOPs are also approved by the cognizant NASA Center safety office or contractor safety office to assure that a review has been preformed. (Requirement 46074) Note: If deviations or changes to HOPs are approved by the contractor's safety office, a copy should be forwarded to the local NASA safety office for informational purposes. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.f | 46075 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure facility operating instructions and changes are developed based on the facility mission and operational requirements. (Requirement 46075) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.g | 46076 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that all procedures include sufficient detail to identify residual hazards and cautions to NASA personnel. (Requirement 46076) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.h | 46077 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that hazardous procedures are marked conspicuously on the title page; e.g., "THIS DOCUMENT CONTAINS HAZARDOUS OPERATIONS PROCEDURES," to alert operators that strict adherence to the procedural steps and safety and health precautions contained therein is required to ensure the safety and health of personnel and equipment. (Requirement 46077) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.08.2.k | 46080 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that personnel use the buddy system whereby an adjacent or nearby person not directly exposed to the hazard serves as an observer to render assistance where the risk of injury is high. (Requirement 46080) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.09.2.d | 46088 | Operational Safety: Laboratory Hazards: Center Directors and project managers shall ensure that: The design, fabrication, or modification of laboratories used for experimentation, testing, or analyses performed on human or animal subjects are coordinated in advance with the OCHMO at (202) 358-2390. (Requirement 46088) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.3.2 | 46198 | Operational Safety: Test Operations Safety: Safety Documentation: Center Directors and project managers shall ensure that established test controls are clearly identified in test drawings, facility drawings, and test procedures. (Requirement 46198) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.a | 46201 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Design test systems such that test personnel or critical test hardware are not subject to a test environment wherein a credible single-point failure (e.g., power loss) could result in injury, illness, or loss to the critical test hardware. (Requirement 46201) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.b | 46202 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Construct all systems (electrical, mechanical, pneumatic, and/or hydraulic) so that no single failure could cause a critical condition. (Requirement 46202) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.d | 46204 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Calibrate and certify safety-critical instrumentation before test operations and as required by test documentation or the test organization's internal procedures. (Requirement 46204) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.e | 46205 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure all personnel involved in test are informed of potential hazards, safety procedures, and protective measures. (Requirement 46205) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.f | 46206 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure the availability of appropriate emergency medical treatment facilities. (Requirement 46206) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.g | 46207 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Conduct formal reviews of engineering designs that are complicated or potentially hazardous to facilities. (Requirement 46207) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.4.1.h | 46208 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure test results report include anomalies, safety implications, and lessons learned. (Requirement 46208) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.b | 46219 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A facility environmental control system failure or failure in the distribution system affecting one pressure-suited occupant shall not affect any other pressure-suited occupant for test requiring crew participation in a pressure suit. (Requirement 46219) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.c | 46220 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A means exists for immediately detecting an incipient fire or other hazardous condition in each crew compartment of any test area. (Requirement 46220) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.d | 46221 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Automatic fire detection is provided for critical areas not suitable for visual monitoring. (Requirement 46221) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.e | 46222 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed for timely and unencumbered rescue of incapacitated crew members. (Requirement 46222) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.f | 46223 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Software controlling crewed test systems are thoroughly analyzed to ensure that no command results in death or injury to the test subjects (Requirement 46223) Note: Policies and requirements for software are given in NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA Software Engineering Requirements. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.g | 46224 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed to provide for manual overrides of critical software commands to ensure the safety of test subjects during any system event or test scenario (normal operation, malfunction, emergency). (Requirement 46224) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.h | 46225 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Manual overrides of critical software commands support safe test termination and egress of test subjects. (Requirement 46225) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.i | 46226 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Medical resources and facilities needed for response are alerted, on-call, and immediately available as needed. (Requirement 46226) | S | Y | Y | Safety | |||
| SAF-1013 | NPR 8715.3C | 03.14.5.1.a | 46211 | Operational Safety: Test Operations Safety: Test Readiness Review: Center Directors and project managers shall ensure that Test Readiness Reviews: Are conducted for tests involving new or modified hardware and/or procedures. (Requirement 46211) | S | Y | Y | Safety | ||
| NPR 8715.3C | 03.14.5.1.b | 46212 | Operational Safety: Test Operations Safety: Test Readiness Review: Center Directors and project managers shall ensure that Test Readiness Reviews: Determine and document the safety, technical, and operational readiness of the test. (Requirement 46212) | S | Y | Y | Safety | |||
| SAF-90 | NPR 8715.3C | 03.14.5.1.b | 46212 | Operational Safety: Test Operations Safety: Test Readiness Review: Center Directors and project managers shall ensure that Test Readiness Reviews: Determine and document the safety, technical, and operational readiness of the test. (Requirement 46212) | S | Y | Y | Safety | ||
| NPR 8715.3C | 03.14.7.2.b | 46219 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A facility environmental control system failure or failure in the distribution system affecting one pressure-suited occupant shall not affect any other pressure-suited occupant for test requiring crew participation in a pressure suit. (Requirement 46219) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.c | 46220 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A means exists for immediately detecting an incipient fire or other hazardous condition in each crew compartment of any test area. (Requirement 46220) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.d | 46221 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Automatic fire detection is provided for critical areas not suitable for visual monitoring. (Requirement 46221) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.e | 46222 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed for timely and unencumbered rescue of incapacitated crew members. (Requirement 46222) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.f | 46223 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Software controlling crewed test systems are thoroughly analyzed to ensure that no command results in death or injury to the test subjects (Requirement 46223) Note: Policies and requirements for software are given in NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA Software Engineering Requirements. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.g | 46224 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed to provide for manual overrides of critical software commands to ensure the safety of test subjects during any system event or test scenario (normal operation, malfunction, emergency). (Requirement 46224) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.h | 46225 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Manual overrides of critical software commands support safe test termination and egress of test subjects. (Requirement 46225) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.i | 46226 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Medical resources and facilities needed for response are alerted, on-call, and immediately available as needed. (Requirement 46226) | S | Y | Y | Safety | |||
| CxP 70059 | 2.1.2 | SAF-1001 | NPR 8715.3C | 02.5.3.1.f | 45933 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that the requirements of this chapter are specified in related contracts, memoranda of understanding, and other agreement documents. (See Chapter 9 of this NPR.) (Requirement 45933) | S | Y | Y | Safety |
| NPR 8715.3C | 09.3.1.d | 46673 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that contracts contain safety, mission success, and risk management requirements for design, development, fabrication, test, and the operations of systems, equipment, and facilities in consultation with Center SMA Directors. (Requirement 46673) | S | Y | Y | Safety | |||
| CxP 70059 | 2.1.6 | SAF-175 | NPR 8715.3C | 01.02.1.e | 45570 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that safety surveillance and periodic inspections are conducted to assure compliance with NASA safety policies and to assess the effectiveness of NASA safety activities as required by Federal, State, and local regulations, NASA policy, and national consensus standards. (Requirement 45570) | S | Y | Y | Mgmt |
| NPR 8715.3C | 02.5.1.3.k | 45911 | System Safety: Core Requirements for System Safety Processes: System Safety Technical Plan (SSTP): The assigned System Safety Manager shall: Support OSMA requirements for audits, assessments, and reviews. (Requirement 45911) | S | Y | Y | Mgmt | |||
| CxP 70059 | 2.1.9 | SAF-1003 | NPR 8715.3C | 07.5.3 | 46609 | Safety Training and Personnel Certification: Mission Critical Personnel Reliability Program (PRP): Mission Directorate Associate Administrators, Center Directors, project managers, supervisors, Cos, and COTRs shall ensure that contracts cover mission-critical operations or areas referenced by 48 CFR Part 1852.246-70, NASA FAR Supplement, Mission Critical Space System Personnel Reliability Program. (Requirement 46609) | S | Y | Y | Safety |
| NPR 8715.3C | 09.3.2.c | 46681 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Require copies of MSDS for new hazardous materials as requested by the local NASA safety office. (Requirement 46681) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.d | 46682 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Participate in onsite visits and pre-bid conferences to ensure potential bidders understand safety provisions. (Requirement 46682) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.e | 46683 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Review, comment, and approve (or disapprove) the contractors' safety risk assessment, submitted in response to paragraph 9.3.3, before the start of any hazardous deliverable work or support operations. (Requirement 46683) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.f | 46684 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Coordinate any matter regarding proposed deviations to safety requirements of 48 CFR Part 1823.70, Safety and Health, with the OSMA, or designated representative. (Requirement 46684) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.g | 46685 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement NPR 5100.4, Federal Acquisition Regulation Supplement (NASA FAR Supplement). (Requirement 46685) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.h | 46686 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement 48 CFR Parts 1807, Acquisition Planning; 1823, Environment, Energy and Water Efficiency, Renewable Energy Technologies, Occupational Safety, and Drug-Free Workplace; 1842, Contract Administration and Audit Services; and 1846, Quality Assurance. (Requirement 46686) | S | Y | Y | Safety | |||
| SAF-179 | NPR 8715.3C | 02.5.3.1.f | 45933 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that the requirements of this chapter are specified in related contracts, memoranda of understanding, and other agreement documents. (See Chapter 9 of this NPR.) (Requirement 45933) | S | Y | Y | Safety | ||
| NPR 8715.3C | 09.3.1.d | 46673 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that contracts contain safety, mission success, and risk management requirements for design, development, fabrication, test, and the operations of systems, equipment, and facilities in consultation with Center SMA Directors. (Requirement 46673) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.c | 46681 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Require copies of MSDS for new hazardous materials as requested by the local NASA safety office. (Requirement 46681) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.d | 46682 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Participate in onsite visits and pre-bid conferences to ensure potential bidders understand safety provisions. (Requirement 46682) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.e | 46683 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Review, comment, and approve (or disapprove) the contractors' safety risk assessment, submitted in response to paragraph 9.3.3, before the start of any hazardous deliverable work or support operations. (Requirement 46683) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.f | 46684 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Coordinate any matter regarding proposed deviations to safety requirements of 48 CFR Part 1823.70, Safety and Health, with the OSMA, or designated representative. (Requirement 46684) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.g | 46685 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement NPR 5100.4, Federal Acquisition Regulation Supplement (NASA FAR Supplement). (Requirement 46685) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.h | 46686 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement 48 CFR Parts 1807, Acquisition Planning; 1823, Environment, Energy and Water Efficiency, Renewable Energy Technologies, Occupational Safety, and Drug-Free Workplace; 1842, Contract Administration and Audit Services; and 1846, Quality Assurance. (Requirement 46686) | S | Y | Y | Safety | |||
| SAF-23 | NPR 8715.3C | 02.5.3.1.f | 45933 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that the requirements of this chapter are specified in related contracts, memoranda of understanding, and other agreement documents. (See Chapter 9 of this NPR.) (Requirement 45933) | S | Y | Y | Safety | ||
| NPR 8715.3C | 03.15.3 | 46230 | Operational Safety: Non-Ionizing Radiation Center Directors and project managers shall comply with these regulations unless a specific exemption is obtained from the U.S. Department of Health and Human Services, Food and Drug Administration. (Requirement 46230) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.1.d | 46673 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that contracts contain safety, mission success, and risk management requirements for design, development, fabrication, test, and the operations of systems, equipment, and facilities in consultation with Center SMA Directors. (Requirement 46673) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.c | 46681 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Require copies of MSDS for new hazardous materials as requested by the local NASA safety office. (Requirement 46681) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.d | 46682 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Participate in onsite visits and pre-bid conferences to ensure potential bidders understand safety provisions. (Requirement 46682) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.e | 46683 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Review, comment, and approve (or disapprove) the contractors' safety risk assessment, submitted in response to paragraph 9.3.3, before the start of any hazardous deliverable work or support operations. (Requirement 46683) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.g | 46685 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement NPR 5100.4, Federal Acquisition Regulation Supplement (NASA FAR Supplement). (Requirement 46685) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.h | 46686 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement 48 CFR Parts 1807, Acquisition Planning; 1823, Environment, Energy and Water Efficiency, Renewable Energy Technologies, Occupational Safety, and Drug-Free Workplace; 1842, Contract Administration and Audit Services; and 1846, Quality Assurance. (Requirement 46686) | S | Y | Y | Safety | |||
| SAF-24 | NPR 8715.3C | 09.3.2.c | 46681 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Require copies of MSDS for new hazardous materials as requested by the local NASA safety office. (Requirement 46681) | S | Y | Y | Safety | ||
| NPR 8715.3C | 09.3.2.d | 46682 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Participate in onsite visits and pre-bid conferences to ensure potential bidders understand safety provisions. (Requirement 46682) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.e | 46683 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Review, comment, and approve (or disapprove) the contractors' safety risk assessment, submitted in response to paragraph 9.3.3, before the start of any hazardous deliverable work or support operations. (Requirement 46683) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.g | 46685 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement NPR 5100.4, Federal Acquisition Regulation Supplement (NASA FAR Supplement). (Requirement 46685) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.h | 46686 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Implement 48 CFR Parts 1807, Acquisition Planning; 1823, Environment, Energy and Water Efficiency, Renewable Energy Technologies, Occupational Safety, and Drug-Free Workplace; 1842, Contract Administration and Audit Services; and 1846, Quality Assurance. (Requirement 46686) | S | Y | Y | Safety | |||
| CxP 70059 | 2.2.1 | SAF-1014 | NPR 8715.3C | 01.02.1.c | 45568 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that safety assessments of all system changes are conducted, prior to changes to these systems being implemented, so as to preclude an unknown increase in risk to personnel or equipment. (Requirement 45568) | S | Y | Y | Safety |
| NPR 8715.3C | 02.7.1.d | 45966 | System Safety: Change Review: The project manager and the System Safety Manager shall: Ensure that the safety impact for every change that is proposed to a program baseline (even if the statement is "No Impact") is documented. (Requirement 45966) | S | Y | Y | Safety | |||
| SAF-1015 | NPR 8715.3C | 01.06.2.1.c(1) | 45678 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Reduce the risk to an acceptable level using the technical safety requirements provided in Paragraph 1.7 of this NPR. (Requirement 45678) | S | Y | Y | Safety | ||
| SAF-181 | NASA STD 8719.13B | 5.01.3.2.5 | 33446 | Software safety personnel shall participate in project reviews. These include any NASA-specific reviews, e.g., Preliminary and Critical Design Reviews (PDR, CDR), Design Certification Review (DCR), FACI (First Article Configuration Inspection), Test Readiness Review (TRR), Certification of Flight Readiness (CoFR), Preflight Acceptance Review (PAR), Flight Acceptance Review (FAR), facility reviews, etc. (Requirement 33446) | S | Y | Y | SWA | ||
| NPR 8715.3C | 01.06.2.1.c(1) | 45678 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Reduce the risk to an acceptable level using the technical safety requirements provided in Paragraph 1.7 of this NPR. (Requirement 45678) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.2.2.a | 45917 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Ensure that system safety models use systematic, replicable, and scenario-based techniques to identify hazards, to characterize the risk of accidents, to identify risk control measures, and to identify key uncertainties. (Requirement 45917) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.2.2.b | 45918 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Initially conduct system safety analyses during project formulation and design concept phases (prior to the Preliminary Design Review) and maintain and update these analyses continuously throughout the project life cycle. (Requirement 45918) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.2.2.f | 45922 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Use system-specific and all relevant data including failure histories, mishap investigation findings, and the NASA LLIS in system safety analysis. (Requirement 45922) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.2.2.h | 45924 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Document the bases for the system safety analyses including key assumptions, accident scenarios, probabilities, consequence severities, and uncertainties such that they are traceable. (Requirement 45924) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.7.1.a | 45963 | System Safety: Change Review: The project manager and the System Safety Manager shall: Update the system safety analyses to identify any change in risk. (Requirement 45963) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.7.1.b | 45964 | System Safety: Change Review: The project manager and the System Safety Manager shall: Ensure that safety personnel assess the potential safety impact of the proposed change and any changes to the baseline risk and previously closed hazards. (Requirement 45964) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.7.1.c | 45965 | System Safety: Change Review: The project manager and the System Safety Manager shall: Ensure that proposed changes to correct a safety problem are analyzed to determine the amount of safety improvement (or detriment) that would result from incorporation of the change. (Requirement 45965) | S | Y | Y | Safety | |||
| SAF-6 | NPR 8715.3C | 01.02.1.c | 45568 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that safety assessments of all system changes are conducted, prior to changes to these systems being implemented, so as to preclude an unknown increase in risk to personnel or equipment. (Requirement 45568) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.2.2.b | 45918 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Initially conduct system safety analyses during project formulation and design concept phases (prior to the Preliminary Design Review) and maintain and update these analyses continuously throughout the project life cycle. (Requirement 45918) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.8.1.a | 45970 | System Safety: Documentation: The project manager (or designated agent) and the System Safety Manager shall: Ensure that all pertinent details of the system safety analysis and review are traceable from the initial identification of the risks through their resolution and any updates in the SSTP. (Requirement 45970) | S | Y | Y | Safety | |||
| CxP 70059 | 2.2.1.1 | SAF-1041 | NPR 8715.3C | 01.07.1.1.a | 45689 | Institutional and Programmatic Safety Requirements: Technical Safety Requirements for NASA-Unique Designs and Operations: Risk Reduction Protocol: Project managers shall ensure that hazards are mitigated according to the following stated order of precedence: Eliminate hazards. (Requirement 45689) | S | Y | Y | Safety |
| NPR 8715.3C | 01.07.1.1.b | 45690 | Institutional and Programmatic Safety Requirements: Technical Safety Requirements for NASA-Unique Designs and Operations: Risk Reduction Protocol: Project managers shall ensure that hazards are mitigated according to the following stated order of precedence: Minimize the hazard risk through design/operation. (Requirement 45690) | S | Y | Y | Safety | |||
| NPR 8715.3C | 01.07.1.1.c | 45691 | Institutional and Programmatic Safety Requirements: Technical Safety Requirements for NASA-Unique Designs and Operations: Risk Reduction Protocol: Project managers shall ensure that hazards are mitigated according to the following stated order of precedence: Incorporate safety devices. (Requirement 45691) | S | Y | Y | Safety | |||
| NPR 8715.3C | 01.07.1.1.d | 45692 | Institutional and Programmatic Safety Requirements: Technical Safety Requirements for NASA-Unique Designs and Operations: Risk Reduction Protocol: Project managers shall ensure that hazards are mitigated according to the following stated order of precedence: Provide cautions and warning devices. (Requirement 45692) | S | Y | Y | Safety | |||
| NPR 8715.3C | 01.07.1.1.e(1) | 45693 | Institutional and Programmatic Safety Requirements: Technical Safety Requirements for NASA-Unique Designs and Operations: Risk Reduction Protocol: Project managers shall ensure that hazards are mitigated according to the following stated order of precedence: Develop administrative procedures and training. (Requirement 45693) | S | Y | Y | Safety | |||
| CxP 70059 | 2.2.1.2 | SAF-1018 | NPR 8715.3C | 01.06.2.1.d | 45680 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Only accept residual risk consistent with NASA requirements and, in all cases, ensure the acceptance of risk to NASA employees and/or equipment does not endanger the public or NASA employees. (Requirement 45680) | S | Y | Y | Safety |
| NPR 8715.3C | 02.5.3.1.c | 45930 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure acceptable residual risks^19 are accepted in writing. (See paragraph 1.6 of this NPR.) (Requirement 45930) ^19 Residual risk is the level of risk that remains present after the applicable safety-related requirements have been satisfied. In a risk-informed context, such requirements may include measures and provisions intended to reduce risk from above to below a defined acceptable level. | S | Y | Y | Safety | |||
| SAF-1019 | NPR 8715.3C | 01.06.2.1.d | 45680 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Only accept residual risk consistent with NASA requirements and, in all cases, ensure the acceptance of risk to NASA employees and/or equipment does not endanger the public or NASA employees. (Requirement 45680) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.3.1.c | 45930 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure acceptable residual risks^19 are accepted in writing. (See paragraph 1.6 of this NPR.) (Requirement 45930) ^19 Residual risk is the level of risk that remains present after the applicable safety-related requirements have been satisfied. In a risk-informed context, such requirements may include measures and provisions intended to reduce risk from above to below a defined acceptable level. | S | Y | Y | Safety | |||
| SAF-12 | NPR 8715.3C | 01.02.1.b | 45567 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure the conduct of assessments of quantitative and/or qualitative safety risks to people, property, or equipment, and include recommendations to either reduce the risks or accept them. (Requirement 45567) | S | Y | Y | Safety | ||
| NPR 8715.3C | 01.06.1.1.a(1) | 45672 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Assessment: Project managers for flight systems and line managers for institutional systems shall: Use a process for risk assessment that supports decisions regarding safety and mission success as well as other decisions such as the development of surveillance plans and information security (see Chapter 2). (Requirement 45672) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.2.2.c | 45919 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Ensure, for Category I and II programs/projects, probabilistic risk assessment techniques are used for system safety analysis. (Requirement 45919) | S | Y | Y | Safety | |||
| SAF-182 | NPR 8715.3C | 01.02.1.b | 45567 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure the conduct of assessments of quantitative and/or qualitative safety risks to people, property, or equipment, and include recommendations to either reduce the risks or accept them. (Requirement 45567) | S | Y | Y | Safety | ||
| NPR 8715.3C | 01.06.1.1.a(1) | 45672 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Assessment: Project managers for flight systems and line managers for institutional systems shall: Use a process for risk assessment that supports decisions regarding safety and mission success as well as other decisions such as the development of surveillance plans and information security (see Chapter 2). (Requirement 45672) | S | Y | Y | Safety | |||
| SAF-44 | NPR 8715.3C | 01.06.2.1.d | 45680 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Only accept residual risk consistent with NASA requirements and, in all cases, ensure the acceptance of risk to NASA employees and/or equipment does not endanger the public or NASA employees. (Requirement 45680) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.3.1.c | 45930 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure acceptable residual risks^19 are accepted in writing. (See paragraph 1.6 of this NPR.) (Requirement 45930) ^19 Residual risk is the level of risk that remains present after the applicable safety-related requirements have been satisfied. In a risk-informed context, such requirements may include measures and provisions intended to reduce risk from above to below a defined acceptable level. | S | Y | Y | Safety | |||
| CxP 70059 | 2.2.1.2.1 | SAF-20 | NPR 8715.3C | 01.02.1.g | 45572 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that trained individual(s) determine the corrective actions needed for mitigating or controlling safety risk for all activities. (Requirement 45572) | S | Y | Y | Mgmt |
| CxP 70059 | 2.2.2.2 | SAF-1020 | NPR 8715.3C | 02.5.3.1.a | 45928 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that a framework is constructed for systematically incorporating system safety analysis results into the evaluation of decision alternatives. (Requirement 45928) | S | Y | Y | Safety |
| SAF-1021 | NPR 8715.3C | 02.5.4.1 | 45942 | System Safety: Core Requirements for System Safety Processes: Performance Monitoring: Project managers shall ensure that the performance attributes and precursors that are identified as being important indicators of system safety are monitored. (Requirement 45942) | S | Y | Y | Safety | ||
| SAF-32 | NPR 8715.3C | 02.5.1.1.b | 45893 | System Safety: Core Requirements for System Safety Processes: System Safety Technical Plan (SSTP): Project managers shall: Ensure that the System Safety Manager and the prime contractor (for out-of-house projects) have the resources to implement the SSTP. (Requirement 45893) | S | Y | Y | Safety | ||
| SAF-35 | NPR 8715.3C | 02.6.1.b | 45953 | System Safety: System Safety Reviews: The program/project manager shall: Document the periodicity of the System Safety and Mission Success Program Reviews in the SSTP. (Requirement 45953) | S | Y | Y | Safety | ||
| SAF-36 | NASA STD 8719.13B | 5.08.1 | 33507 | There shall be a system for closed-loop tracking of discrepancies, problems, and failures in the baselined safety-critical software products and processes. (Requirement 33507) | S | Y | Y | Safety | ||
| NASA STD 8719.13B | 6.4.3.4 | 33648 | Improperly implemented safety features shall be input into the problem reporting system for project-level resolution. (Requirement 33648) | S | Y | Y | SWA | |||
| NPR 8715.3C | 01.06.2.1.a | 45676 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Establish and document a formal, closed loop, transparent decision-making process for accpeting residual risk for their assigned activities, personnel, and/or property. (Requirement 45676) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.3.1.b | 45929 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Establish and document a formal and transparent decision-making process for hazard closure^18 and formally accepting residual risk that has been determined to be acceptable by the cognizant technical authority. (Requirement 45929) ^18 Closure of a hazard condition or other safety issue is the demonstration that all safety requirements expressly formulated to address the condition or issue have been satisfied. | S | Y | Y | Safety | |||
| SAF-37 | NPR 8715.3C | 09.3.1.a | 46670 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Work with cognizant safety officals to develop and approve safety requirements and objectives for efforts to be contracted, and advise COs and COTRS of specific safety concerns or issues related to contract performance. (Requirement 46670) | S | Y | Y | Safety | ||
| NPR 8715.3C | 09.3.4.a | 46689 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in evaluating the prospective contractor's safety record and safety program. (Requirement 46689) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.4.b | 46690 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in applying any special safety provisions to grants or cooperative agreements (see paragraph 2.7). (Requirement 46690) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.4.c | 46691 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: During the pre-award phase of acquisition, develop, document and provide to the CO criteria for the safety performance elements to be evaluated in contracts with fee plans in a timely manner to ensure inclusion in the solicitation. (Requirement 46691) | S | Y | Y | Mgmt | |||
| SAF-38 | NPR 8715.3C | 02.5.3.1.f | 45933 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that the requirements of this chapter are specified in related contracts, memoranda of understanding, and other agreement documents. (See Chapter 9 of this NPR.) (Requirement 45933) | S | Y | Y | Safety | ||
| NPR 8715.3C | 09.3.1.d | 46673 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that contracts contain safety, mission success, and risk management requirements for design, development, fabrication, test, and the operations of systems, equipment, and facilities in consultation with Center SMA Directors. (Requirement 46673) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.2.a | 46679 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Develop safety requirements and objectives that are clearly delineated in contract specifications in conjunction with project officials. (Requirement 46679) | S | Y | Y | Safety | |||
| SAF-39 | NPR 8715.3C | 02.5.3.1.f | 45933 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure that the requirements of this chapter are specified in related contracts, memoranda of understanding, and other agreement documents. (See Chapter 9 of this NPR.) (Requirement 45933) | S | Y | Y | Safety | ||
| NPR 8715.3C | 09.3.1.d | 46673 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that contracts contain safety, mission success, and risk management requirements for design, development, fabrication, test, and the operations of systems, equipment, and facilities in consultation with Center SMA Directors. (Requirement 46673) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.1.f | 46675 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Provide specific safety tasks to the CO for incorporation into contracts. (Requirement 46675) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.4.a | 46689 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in evaluating the prospective contractor's safety record and safety program. (Requirement 46689) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.4.b | 46690 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in applying any special safety provisions to grants or cooperative agreements (see paragraph 2.7). (Requirement 46690) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.4.c | 46691 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: During the pre-award phase of acquisition, develop, document and provide to the CO criteria for the safety performance elements to be evaluated in contracts with fee plans in a timely manner to ensure inclusion in the solicitation. (Requirement 46691) | S | Y | Y | Mgmt | |||
| SAF-40 | NPR 8715.3C | 01.02.1.e | 45570 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that safety surveillance and periodic inspections are conducted to assure compliance with NASA safety policies and to assess the effectiveness of NASA safety activities as required by Federal, State, and local regulations, NASA policy, and national consensus standards. (Requirement 45570) | S | Y | Y | Mgmt | ||
| NPR 8715.3C | 09.3.1.g | 46676 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Define the surveillance of contractor safety matters with respect to the nature of the procurement. (Requirement 46676) | S | Y | Y | Safety | |||
| NPR 8715.3C | 09.3.1.h | 46677 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Ensure that performance-based contracts have a surveillance plan. (Requirement 46677) | S | Y | Y | Safety | |||
| SAF-42 | NPR 8715.3C | 02.5.2.1 | 45915 | System Safety: Core Requirements for System Safety Processes:System Safety Modeling: System Safety Managers shall ensure that the system safety modeling activities are fully integrated into system engineering and are supported by domain, systems and specialty engineers. (Requirement 45915) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.3.2.b | 45936 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Ensure that the system safety models incorporate all the safety attributes important to risk-informed decision making by working with the project manager and other decision makers as deemed appropriate. (Requirement 45936) | S | Y | Y | Safety | |||
| SAF-43 | NPR 8715.3C | 01.06.2.1.b | 45677 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Meet Federal safety and health standards when making risk-informed decisions to accept residual risk. (Requirement 45677) | S | Y | Y | Safety | ||
| NPR 8715.3C | 01.06.2.1.e | 45681 | Institutional and Programmatic Safety Requirements: Risk Assessment and Risk Acceptance: Risk Acceptance: Center Directors and project managers shall: Document the basis for any risk-informed decisions. (Requirement 45681) | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.3.1.b | 45929 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Establish and document a formal and transparent decision-making process for hazard closure^18 and formally accepting residual risk that has been determined to be acceptable by the cognizant technical authority. (Requirement 45929) ^18 Closure of a hazard condition or other safety issue is the demonstration that all safety requirements expressly formulated to address the condition or issue have been satisfied. | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.5.3.1.c | 45930 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Ensure acceptable residual risks^19 are accepted in writing. (See paragraph 1.6 of this NPR.) (Requirement 45930) ^19 Residual risk is the level of risk that remains present after the applicable safety-related requirements have been satisfied. In a risk-informed context, such requirements may include measures and provisions intended to reduce risk from above to below a defined acceptable level. | S | Y | Y | Safety | |||
| NPR 8715.3C | 02.8.2.d | 45976 | System Safety: Documentation: The System Safety Manager shall: Ensure that a final approved system safety analysis report is produced that contains a verification of the resolution of the risks and a written acceptance of the residual risks from the program/project manager to complete the audit trail (Requirement 45976) | S | Y | Y | Safety | |||
| SAF-45 | NPR 8715.3C | 01.02.1.h | 45573 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that NASA employees and safety professionals are trained for their roles and responsbilities associated with specific safety functions. (Requirement 45573) | S | Y | Y | Safety | ||
| NPR 8715.3C | 03.08.2.i | 46078 | Operational Safety: Hazardous Operations: Center Directors and project managers shall: Ensure that specific personnel certificaiton requirements are established, as listed in Chapter 7, in cases where hazardous operations (e.g., rigging, high voltage) depend on adherence to specific standards, guidelines, and training. (Requirement 46078) | S | Y | Y | Safety | |||
| CxP 70059 | 2.2.2.2.e | SAF-1035 | NPR 8715.3C | 03.14.7.2.b | 46219 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A facility environmental control system failure or failure in the distribution system affecting one pressure-suited occupant shall not affect any other pressure-suited occupant for test requiring crew participation in a pressure suit. (Requirement 46219) | S | Y | Y | Safety |
| NPR 8715.3C | 03.14.7.2.c | 46220 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A means exists for immediately detecting an incipient fire or other hazardous condition in each crew compartment of any test area. (Requirement 46220) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.d | 46221 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Automatic fire detection is provided for critical areas not suitable for visual monitoring. (Requirement 46221) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.e | 46222 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed for timely and unencumbered rescue of incapacitated crew members. (Requirement 46222) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.f | 46223 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Software controlling crewed test systems are thoroughly analyzed to ensure that no command results in death or injury to the test subjects (Requirement 46223) Note: Policies and requirements for software are given in NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA Software Engineering Requirements. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.g | 46224 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed to provide for manual overrides of critical software commands to ensure the safety of test subjects during any system event or test scenario (normal operation, malfunction, emergency). (Requirement 46224) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.h | 46225 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Manual overrides of critical software commands support safe test termination and egress of test subjects. (Requirement 46225) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.i | 46226 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Medical resources and facilities needed for response are alerted, on-call, and immediately available as needed. (Requirement 46226) | S | Y | Y | Safety | |||
| CxP 70059 | 2.2.2.3 | SAF-1022 | NPR 8715.3C | 02.5.3.2.c | 45937 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Establish the methods and tools that are used in the risk-informed framework. (Requirement 45937) | S | Y | Y | Safety |
| NPR 8715.3C | 02.5.4.2.a | 45944 | System Safety: Core Requirements for System Safety Processes: Performance Monitoring: The System Safety Manager shall: Establish the methods and tools that are used in the performance monitoring and precursor assessments. (Requirement 45944) | S | Y | Y | Safety | |||
| SAF-1023 | NPR 8715.3C | 02.5.3.2.d | 45938 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Check and validate the methods and tools before implementation and obtain concurrence from the project manager. (Requirement 45938) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.4.2.b | 45945 | System Safety: Core Requirements for System Safety Processes: Performance Monitoring: The System Safety Manager shall: Check and validate the methods and tools used for performance monitoring and precursor assessments before implementation. (Requirement 45945) | S | Y | Y | Safety | |||
| SAF-1024 | NPR 8715.3C | 02.5.2.2.g | 45923 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Maintain an up-to-date database of identified hazards, accident scenarios, probabilities and consequences, and key uncertainties throughout the life of the program. (Requirement 45923) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.4.2.c | 45946 | System Safety: Core Requirements for System Safety Processes: Performance Monitoring: The System Safety Manager shall: Maintain an up-to-date databse of the performance monitoring results and precursor results. (Requirement 45946) | S | Y | Y | Safety | |||
| SAF-1025 | NPR 8715.3C | 02.5.4.2.d | 45947 | System Safety: Core Requirements for System Safety Processes: Performance Monitoring: The System Safety Manager shall: Ensure that the performance monitoring and precursor data are fed back into system safety analyses and the results updated. (Requirement 45947) | S | Y | Y | Safety | ||
| SAF-1026 | NPR 8715.3C | 02.5.3.2.e | 45939 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Document the bases for the methods and tools used and analytical results. (Requirement 45939) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.5.4.2.e | 45948 | System Safety: Core Requirements for System Safety Processes: Performance Monitoring: The System Safety Manager shall: Document the bases for the methods and tools that are used in the performance monitoring and precursor assessments. (Requirement 45948) | S | Y | Y | Safety | |||
| SAF-54 | NPR 8715.3C | 02.6.2.a | 45957 | System Safety: System Safety Reviews: The System Safety Manager shall: Conduct periodic independent reviews of the system safety tasks keyed to project milestones (Requirement 45957) | S | Y | Y | Safety | ||
| SAF-55 | NPR 8715.3C | 02.6.1.d | 45955 | System Safety: System Safety Reviews: The program/project manager shall: Establish and maintain dedicated independent assessment activities for Priority I programs and projects, such as the Constellation Program. (Requirement 45955) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.6.2.b | 45958 | System Safety: System Safety Reviews: The System Safety Manager shall: Assist and support independent review groups established to provide independent assessments of the program. (Requirement 45958) | S | Y | Y | Safety | |||
| SAF-56 | NPR 8715.3C | 02.5.2.2.g | 45923 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Maintain an up-to-date database of identified hazards, accident scenarios, probabilities and consequences, and key uncertainties throughout the life of the program. (Requirement 45923) | S | Y | Y | Safety | ||
| SAF-57 | NPR 8715.3C | 02.5.1.3.i | 45909 | System Safety: Core Requirements for System Safety Processes: System Safety Technical Plan (SSTP): The assigned System Safety Manager shall: Maintain appropriate safety participation in the program design, tests, operations, failures and mishaps, and contractor system safety activities at a level consistent with mishap potential for the life of the program. (Requirement 45909) | S | Y | Y | Safety | ||
| SAF-59 | NPR 8715.3C | 02.6.2.c | 45959 | System Safety: System Safety Reviews: The System Safety Manager shall: Support the OSMA independent safety assessment process to determine readiness to conduct tests and operations having significant levels of safety risks. (Requirement 45959) | S | Y | Y | Safety | ||
| SAF-60 | NPR 8715.3C | 02.5.3.2.a | 45935 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Ensure that the system safety models are constructed to support the implementation of the risk-informed decision framework. (Requirement 45935) | S | Y | Y | Safety | ||
| NPR 8715.3C | 02.8.2.a | 45973 | System Safety: Documentation: The System Safety Manager shall: Submit a system safety analysis report to the program/project manager at each milestone (formulation, evaluation, implementation, or other equivalent milestones [e.g., Safety Requirements Review^20, Preliminary Design Review, Critical Design Review, and Flight Readiness Review]) detailing the results of the system safety analyses completed to date to document the status of system safety tasks. (Requirement 45973) ^20 Safety requirements include both deterministic and risk-informed requirements. A deterministic safety requirement is the qualitative or quantitative definition of a threshold of action or performance that must be met by a mission-related design item, system, or activity in order for that item, system, or activity to be acceptably safe. A risk-informed requirement is a safety requirement that has been established, at least in part, on the basis of the consideration of a safety-related risk metric and its associated uncertainty. | S | Y | Y | Safety | |||
| SAF-61 | NPR 8715.3C | 09.3.4.a | 46689 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in evaluating the prospective contractor's safety record and safety program. (Requirement 46689) | S | Y | Y | Mgmt | ||
| NPR 8715.3C | 09.3.4.b | 46690 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: Assist the CO and COTR in applying any special safety provisions to grants or cooperative agreements (see paragraph 2.7). (Requirement 46690) | S | Y | Y | Mgmt | |||
| NPR 8715.3C | 09.3.4.c | 46691 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers shall: During the pre-award phase of acquisition, develop, document and provide to the CO criteria for the safety performance elements to be evaluated in contracts with fee plans in a timely manner to ensure inclusion in the solicitation. (Requirement 46691) | S | Y | Y | Mgmt | |||
| SAF-64 | NPR 8715.3C | 02.7.1.d | 45966 | System Safety: Change Review: The project manager and the System Safety Manager shall: Ensure that the safety impact for every change that is proposed to a program baseline (even if the statement is "No Impact") is documented. (Requirement 45966) | S | Y | Y | Safety | ||
| SAF-65 | NPR 8715.3C | 02.5.3.2.c | 45937 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: The System Safety Manager shall: Establish the methods and tools that are used in the risk-informed framework. (Requirement 45937) | S | Y | Y | Safety | ||
| SAF-66 | NPR 8715.3C | 02.5.2.2.d | 45920 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Ensure that the system safety models are developed in an iterative process to allow model expansion, model updating, and model integration as the design evolves and operational experience is acquired. (Requirement 45920) | S | Y | Y | Safety | ||
| CxP 70059 | 2.2.2.4 | SAF-1027 | NPR 8715.3C | 02.5.3.1.e | 45932 | System Safety: Core Requirements for System Safety Processes: Application of System Safety Models for Risk-informed Decisions: Program/project managers shall: Where residual risks have been determined by either the cognizant technical authority or the cognizant SMA authority as "unacceptable," initiate risk mitigation/control activities, as appropriate, to reduce the risk to an acceptable level. (Requirement 45932) | S | Y | Y | Safety |
| CxP 70059 | 2.2.3 | SAF-183 | NPR 8715.3C | 01.02.1.i(1) | 45574 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that software safety is included in their safety programs (Requirement 45574). | S | Y | Y | Safety |
| SAF-70 | NPR 8715.3C | 01.02.1.i(1) | 45574 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that software safety is included in their safety programs (Requirement 45574). | S | Y | Y | Safety | ||
| SAF-71 | NPR 8715.3C | 01.02.1.i(1) | 45574 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that software safety is included in their safety programs (Requirement 45574). | S | Y | Y | Safety | ||
| SAF-72 | NPR 8715.3C | 01.02.1.i(1) | 45574 | Institutional and Programmatic Safety Requirements: NASA General Safety Program Roles and Responsibilities: Ensure that software safety is included in their safety programs (Requirement 45574). | S | Y | Y | Safety | ||
| CxP 70059 | 2.2.4 | SAF-73 | NPR 8715.3C | 02.7.1.d | 45966 | System Safety: Change Review: The project manager and the System Safety Manager shall: Ensure that the safety impact for every change that is proposed to a program baseline (even if the statement is "No Impact") is documented. (Requirement 45966) | S | Y | Y | Safety |
| CxP 70059 | 2.3 | SAF-1030 | NPR 8715.5 | 1.3.4.1.d | 42648 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: The Center Director or NASA designee shall: Ensure that each program's timeline includes provisions for any necessary tailoring of range safety requirements and the apporval process to take place (Requirement 42648). | S | Y | Y | Safety |
| NPR 8715.5 | 1.3.4.1.e | 42649 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: The Center Director or NASA designee shall: Accept the risk associated with any waiver to a requirement of this NPR when people or property for which the Center is responsible are exposed to the range operation per paragraph 1.4 of this NPR (Requirement 42649). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.a | 42651 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Establish the processes and associated Center-level requirements needed to ensure the requirements of this NPR are satisfied, including the risk management process of paragraph 3.2.4 of this NPR (Requirement 42651). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.b | 42652 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Ensure all employees and visitors are informed of potential hazards associated with a range operation and the actions to take in the event of an emergency (Requirement 42652). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.c | 42653 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site. When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Follow the variance process described in paragraph 1.4 of this NPR (Requirement 42653). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.d | 42654 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Support range safety independent assessments and respond to all findings and recommendations for which the Center is accountable (Requirement 42654). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.e | 42655 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Support and ensure that the Certificate of Flight Readiness or equivalent review process includes range safety considerations (Reuirement 90101). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.f | 42656 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Coordinate with the appropriate emergency response agencies on Center activities and potential effects on outside communities (Requirement 42656). Note: NPD 8710.1, NASA Emergency Preparedness Program, and NPR 8715.2, NASA Emergency Preparedness Plan Procedural Requirements, apply with regard to emergency preparedness. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.h | 42657 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: When responsible for range facilities, ensure range safety systems provide for safe and reliable operations (Requirement 42657). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.i | 42658 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Develop emergency response plans to prevent or mitigate the exposure of the public or employees to any hazard associated with a range operation (Requirement 42658). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.j | 42659 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Approve the categorization of people located on NASA property as mission essential, Center essential, or public/visitors for the purposes of risk management (Requirement 42659). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.2.k | 42660 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, launch site (fixed or mobile), or landing site (including any airfield used for range operations); or when onsite personnel are affected by range operations, the Center Director or NASA designee shall: Review and approve each vehicle program's RSRMP (including any updates) per paragraphs 1.3.7.p and 3.2.4.4 of this NPR (Requirement 42660). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.4.3 | 42661 | Roles and Responsibilities: Center Directors. A NASA Center may become involved in range safety activities through its assigned programs in a number of ways: such as a range, launch site, or landing site operator; range user; or as a range safety technology research and development site: When functioning as the authority for a range, the Center Director or NASA designee shall establish a Center range safety organization (direct or delegated) that is independent of all vehicle programs and has safety responsibility for all range operations that use the Center's range facilities (see paragraph 1.3.5 of this NPR) (Requirement 42661). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.a | 42663 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Implement or oversee the implementation of this NPR and associated Center-level processes and requirements including the risk management process of paragraph 3.2.4 of this NPR (Requirement 42663). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.b | 42664 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Identify program data requirements, perform or evaluate and approve required range safety analysis (Requirement 42664). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.c | 42665 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Evaluate and approve all range safety systems (Requirement 42665). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.d | 42666 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Designate a qualified Range Safety Officer (RSO) to support each NASA mission that involves range operations (see paragraph 1.3.8 of this NPR for RSO responsibilities) (Requirement 42666). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.e | 42667 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Establish a qualification and training program that satisfies paragraph 3.5 of this NPR for range safety personnel (including RSOs and personnel responsible for range safety systems and range safety analysis) appropriate to the types of vehicles and operations at the range (Requirement 42667). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.f | 42668 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Set operational performance requirements and standards for all range safety systems (Requirement 42668). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.g | 42669 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Ensure the readiness of the range safety systems to support each operation (Requirement 42669). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.h | 42670 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Coordinate with maritime, aviation, and other authorities to ensure all range safety requirements are satisfied for all range operations (Requirement 42670). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.i | 42671 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Evaluate requests for tailoring, deviations, or waivers to this NPR and coordinate with the approval authorities per paragraph 1.4 of this NPR (Requirement 42671) | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.5.j | 42672 | Roles and Responsibilities: Center Range Safety Organization. For all range operations that use a Center's range facilities, the Center range safety organization lead or NASA designee shall: Evaluate each vehicle program's RSRMP (including any updates) per paragraphs 1.3.7.p and 3.2.4.4 of this NPR and coordinate with the approval authorities (Requirement 42672). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.1.a | 42675 | Roles and Responsibilities: Range Safety Representative. The Range Safety Representative for a Center or a vehicle program shall: Monitor implementation of this NPR (Requirement 42675). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.1.b | 42676 | Roles and Responsibilities: Range Safety Representative. The Range Safety Representative for a Center or a vehicle program shall: Keep the NASA Range Safety Manager advised of activities related to range safety (Requirement 42676). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.1.c | 42677 | Roles and Responsibilities: Range Safety Representative. The Range Safety Representative for a Center or a vehicle program shall: Provide the NASA Range Safety Manager with an annual summary of all range safety activities associated with each program where applicable (Requirement 42677). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.1.d | 42678 | Roles and Responsibilities: Range Safety Representative. The Range Safety Representative for a Center or a vehicle program shall: Lead and/or participate in range safety activities as designated by the Center Director or vehicle program manager (Requirement 42678). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.1.e | 42679 | Roles and Responsibilities: Range Safety Representative. The Range Safety Representative for a Center or a vehicle program shall: Coordinate any requests for variance to a requirement of this NPR per paragraph 1.4 of this NPR. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.2 | 42680 | Roles and Responsibilities: Range Safety Representative. A Center Range Safety Representative shall satisfy paragraph 1.3.6.1 for all programs managed by the Center and may also perform as the Range Safety Representative for a vehicle program (Requirement 42680). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.6.3 | 42681 | Roles and Responsibilities: Range Safety Representative. The Range Safety Representative for a vehicle program shall satisfy paragraph 1.3.6.1 for the program and may also perform as a Center Range Safety Representative (Requirement 42681). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.a | 42683 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Establish the processes and associated program-level requirements needed to ensure the requirements of this NPR are satisfied, including the risk management process of paragraph 3.2.4 of this NPR (Requirement 42683). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.b | 42684 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Coordinate all risk management related efforts with the range safety organization(s) and authority for any range, launch site, or landing site that support the range operation (Requirement 42684). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.c | 42685 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Coordinate with the range safety organization(s), including the RSO or equivalent, to develop and implement operational range safety requirements, plans, procedures, and checklists, icluding mission rules and flight commit criteria (see paragraph 3.4 of this NPR for operational requirements) (Requirement 42685). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.d | 42686 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Designate a Range Safety Representative for the vehicle program (see paragraph 1.3.6) (Requirement 42686). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.e | 42687 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Involve range safety personnel and begin the tailoring process by the Systems Requirement Review (SRR), continuing throughout all pertinent vehicle and payload reviews and during operations (Requirement 42687). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.f | 42688 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Ensure adequate resources and data are available to support all range safety requirements and activities, including the design, test, and implementation of vehicle range safety systems required to support range safety requirements, the range safety organization/authority supporting the review, and approval process and operational support (Requirement 42688). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.g | 42689 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Incorporate the requirements of this document in all launch service provider contracts and flight or other range operation contracts or agreements (Requirement 42689). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.h | 42690 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Coordinate any additional tailoring (not accounted for during the tailoring process), deviation, or waiver request to this NPR with the Center Range Safety Manager responsible for the range operation or the NASA Range Safety Manager prior to submittal for final approval (Requirement 42690). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.i | 42691 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Submit any request for tailoring, deviation, or waiver in accordance with the requirements and processes of the Independent Technical Authority per NPD 1240.4, NASA Technical Authority, paragraph 1.4 of this NPR, and any local range policies (Requirement 42691). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.j | 42692 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: In coordination with the range safety organization(s), generate a contingency action plan that describes roles and responsibilities in the event of a mishap and provides procedures to secure all data relevant to an investigation (Requirement 42692). Note: NPR 8621.1, NASA Procedural Requirements for Mishap Reporting, Investigating, and Recordkeeping, contains the applicable policy and procedural requirements for mishap reporting and investigating. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.k | 42693 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and coordinate emergency response planning actions with the emergency planning community (including but not limited to, Center or local safety office, emergency responders, local jurisdictions, and the cognizant NASA environmental management organization) and the range safety organization(s) (Requirement 42693). Note: NPD 8710.1, NASA Emergency Preparedness Program, and NPR 8715.2, NASA Emergency Preparedness Plan Procedural Requirements, apply with regard to emergency preparedness. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.L | 42694 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: In coordination with any Center that supports the range operation, ensure all employees and visitors are informed of potential hazards associated with a range operation and the actions to take in the event of an emergency (Requirement 42694). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.m | 42695 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Ensure that employees whose duties involve the potential for exposure to hazardous materials are educated regarding hazardous materials in accordance with 29 CFR 1910.1200, Hazardous Communications (Requirement 42695). This includes toxic plume awareness training for the types of hazardous materials associated with range operations. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.n | 42696 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Provide the range safety organization(s) with all data pertinent to the range safety review and approval process (Requirement 42696). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.o | 42697 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Engage the Center range safety organization regarding, and establish a plan for, monitoring of vehicle and range processes during launches, entries, and other range operations and to ensure timely identification and resolution of any violation that might affect launch, entry, or other operational approval. Engage with the NASA Range Safety Manager to perform this function for range operations not supported by a Center range safety organization (Requirement 42697). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.p | 42698 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and approve a RSRMP for the vehicle program per paragraph 3.2.4.4 of this NPR (Requirement 42698). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.p.1 | 42699 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and approve a RSRMP for the vehicle program per paragraph 3.2.4.4 of this NPR: Maintain the RSRMP to ensure its validity for each operation (Requirement 42699). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.p.2 | 42700 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and approve a RSRMP for the vehicle program per paragraph 3.2.4.4 of this NPR: Perform a documented review and update of the RSRMP at least once every 2 years to reflect current operations and risk levels (Requirement 42700). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.p.3 | 42701 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and approve a RSRMP for the vehicle program per paragraph 3.2.4.4 of this NPR: Coordinate the RSRMP and any updates with the responsible NASA range safety organization or the NASA Range Safety Manager prior to submittal for final approval (Requirement 42701). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.p.4 | 42702 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and approve a RSRMP for the vehicle program per paragraph 3.2.4.4 of this NPR: Obtain approval of the RSRMP (including any updates) by the NASA Center Director responsible for the range, launch site or landing site (Requirement 42702). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.p.5 | 42703 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Develop and approve a RSRMP for the vehicle program per paragraph 3.2.4.4 of this NPR: If the vehicle program is not supported by a NASA Center range safety organization, obtain approval of the RSRMP (including any updates) by the NASA Chief Safety and Mission Assurance Officer or NASA designee (Requirement 42703) | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.q | 42704 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: With regard to range safety, implement or participate in the payload safety review process required by NASA and any other responsible entity (Requirement 42704). Note: NASA STD 8719.8, Expendable Launch Vehicle Payload Safety Review Process Standard, defines NASA's ELV payload safety review process. Space Shuttle Program safety policies and requirements for Space Shuttle payloads are specified in NSTS 1700.7B, Safety Policy and Requirements for Payloads Using the Space Transportation System, and KHB 1700.7, Space Shuttle Payload Ground Safety Handbook. The International Space Station (ISS) safety policies and requirements for ISS payloads are specified in NSTS 1700.7B ISS Addendum - Safety Policy Requirements for Payloads Using the International Space Station (ISS Addendum). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.7.r | 42705 | Roles and Responsibilities: Vehicle Program Manager. For each range operation, the vehicle program manager or NASA designee shall: Ensure that any vehicle program personnel who performs a range safety function are qualified and trained in accordance with paragraph 3.5 of this NPR. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.1 | 42707 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): The RSO or equivalent for each NASA range operation shall be a qualified NASA or DoD employee or a person operating under an FAA license (see paragraph 3.5 of this NPR for applicable personnel qualification requirements) (Requirement 42707). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.2.a | 42709 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For each range operation, the RSO or equivalent shall: Undergo simulation scenarios that exercise hands-on operations of range safety system, safety decision-making tools or processes in conjunction with vehicle systems (Requirement 42709). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.2.b | 42710 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For each range operation, the RSO or equivalent shall: Coordinate with the program to develop and implement operational range safety requirements, plans, procedures, and checklists, including mission rules and flight commit criteria (see paragraph 3.4 of this NPR for operational requirements (Requirement 42710). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.2.c | 42711 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For each range operation, the RSO or equivalent shall: Coordinate with the program and responsible approval authorities on any tailoring or variance to range safety requirements (Requirement 42711). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.2.d | 42712 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For each range operation, the RSO or equivalent shall: Provide an independent safety assessment and ensure that all range safety flight commit criteria are satisfied prior to flight initiation (Requirement 42712). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.3.a | 42714 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For any vehicle that has a Flight Termination System (FTS), the RSO or equivalent shall: Coordinate with the program to develop flight termination activation criteria (Requirement 42714). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.3.b | 42715 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For any vehicle that has a Flight Termination System (FTS), the RSO or equivalent shall: Perform real-time monitoring of the vehicle flight path/trajectory, vehicle systems, range safety systems, and the performance of the FTS (Requirement 42715). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.3.8.3.c | 42716 | Roles and Responsibilities: Range Safety Officer (RSO) (or equivalent): For any vehicle that has a Flight Termination System (FTS), the RSO or equivalent shall: Make a flight termination decision when performance of the vehicle violates preplanned termination criteria or presents an unplanned, unacceptable hazard to the public, personnel, or property and activate the FTS (Requirement 42716). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.1 | 42718 | Variance Process: A range user shall use this variance process when requesting tailoring, deviation, or waiver of the requirements of this NPR to support program objectives. See Appendix A for definitions for variance, tailoring, deviation, and waiver. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.2 | 42719 | Variance Process: For all requirements contained in this NPR, the approval of any tailoring, deviation, or waiver requests shall satisfy the processes and requirements of the Independent Technical Authority per NPD 1240.4, NASA Technical Authority. | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.3 | 42720 | Variance Process: The Center or Vehicle Program Range Safety Representative shall coordinate variance requests with the range safety organization(s) and the approval authorities (Requirement 42720). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.4.a | 42722 | Variance Process: The variance approval process shall incorporate the following: The Center Range Safety Organization that supports the range operation shall evaluate all variance requests and provide input to the approval authorities. The NASA Range Safety Manager shall perform this function for each NASA range operation that is not supported by a Center Range Safety Organization (Requirement 42722). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.4.b | 42723 | Variance Process: The variance approval process shall incorporate the following: One of the three Independent Technical Authority-sponsored range safety technical warrant holders (Space Flight Range Safety, Atmospheric Flight Range Safety, or Suborbital Range Safety) shall approve any variance to a requirement of this NPR (Requirement 42723). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.4.c | 42724 | Variance Process: The variance approval process shall incorporate the following: The accountable technical warrant holder (per paragraph 1.4.4.b of this NPR) shall notify the Agency Chief Engineer and the Chief Safety and Mission Assurance Officer of any approved waivers to this NPR (Requirement 42724). | S | Y | Y | Safety | |||
| NPR 8715.5 | 1.4.4.d | 42725 | Variance Process: The variance approval process shall incorporate the following: The vehicle program manager and each Center Director (or NASA designee) responsible for people or property exposed to the associated range operation shall cosign each waiver to this NPR (indicating acceptance of the risk associated with the waiver) (Requirement 42725). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.2.2.a | 42731 | Commercial Launch and Entry: A NASA launch or entry does not require an FAA license if the activity is conducted by or for NASA and NASA is so substantially involved that it effectively directs or controls the activity. For such a launch or entry, NASA shall: Supervise the activities of each contractor providing a launch or entry service by approval of requirements and ongoing insight into the contractor's operations (Requirement 42731). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.2.2.b | 42732 | Commercial Launch and Entry: A NASA launch or entry does not require an FAA license if the activity is conducted by or for NASA and NASA is so substantially involved that it effectively directs or controls the activity. For such a launch or entry, NASA shall: Ensure that a government organization directly oversees and performs the range safety function during the activity (Requirement 42732). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.2.3 | 42733 | Commercial Launch and Entry: A NASA program may require FAA licensing for commercial ventures funded by NASA or a commercial launch or entry carrying a NASA payload (as a primary customer) through a contract. | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.2.4 | 42734 | Commercial Launch and Entry: A NASA program shall require FAA licensing for any launch or entry where there is no government organization directly overseeing and performing the range safety function during the activity (Requirement 42734). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.3.1 | 42736 | National Airspace System: This paragraph applies to each NASA program that uses the National Airspace System during conduct of a range operation: A NASA program shall coordinate with the FAA on each range operation that uses the National Airspace System, including each launch and entry (Requirement 42736). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.3.2 | 42737 | National Airspace System: This paragraph applies to each NASA program that uses the National Airspace System during conduct of a range operation: A NASA program shall obtain a Certificate of Authorization or equivalent written agreement from the FAA for each UAV operation within the National Airspace System (Requirement 42737). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.3.3 | 42738 | National Airspace System: This paragraph applies to each NASA program that uses the National Airspace System during conduct of a range operation: A NASA program shall coordinate the required information with range safety personnel prior to submitting the request to the FAA center(s) with authority over the planned areas of operation (Requirement 42738). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.4.1 | 42740 | Foreign Participation in Range Operations Involving NASA: Foreign participation in any range operation involving NASA shall require prior coordination with the NASA Office of External Relations and be conducted in accordance with this NPR; NPD 1360.2, Initiation and Development of International Cooperation in Space and Aeronautics Programs; and NPD 1050.1, Authority To Enter Into Space Act Agreements (Requirement 42740). | S | Y | Y | Safety | |||
| NPR 8715.5 | 2.4.2 | 42741 | Foreign Participation in Range Operations Involving NASA: Foreign participation in any Range Operation involving NASA, which requires access to NASA Installations or Facilities, shall also be conducted in accordance with paragraph 2.4.1 of this NPR; NPR 1371.2, Procedural Requirements for Processing Requests for Access to NASA Installations or Facilities by Foreign Nationals or U.S. Citizens Who are Representatives of Foreign Entities; and/or NPD 1371.5, Coordination and Authorization of Access by Foreign Nationals and Foreign Representatives to NASA (Requirement 42741). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.01 | 42745 | Range Safety Analysis: Each range operation shall undergo a range safety analysis to establish any design or operational constraints needed to control risk to persons and property (Requirement 42745). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.02 | 42746 | Range Safety Analysis: A range safety organization that is independent of the vehicle program shall review and approve the range safety analysis (Requirement 42746). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.03 | 42747 | Range Safety Analysis: A range safety analysis shall incorporate the elements of risk management, risk assessment, containment, and risk mitigation (Requirement 42747). Note: Containment for the purpose of range safety is defined in Appendix A and related requirements are in paragraph 3.2.9 of this NPR. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.1 | 42749 | Range Safety Analysis: Risk Management Process: A Center's or vehicle program's risk management process shall include assessment of the risk to the public, workforce, and property in accordance with paragraph 3.2.5 of this NPR (Requirement 42749) | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.2 | 42750 | Range Safety Analysis: Risk Management Process: A vehicle program's risk management process shall incorporate the applicable requirements of any range, launch site, or landing site that supports the program's range operations (Requirement 42750). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.a | 42752 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Mitigate the risk to members of the public and the workforce (Requirement 42752). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.b | 42753 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Identify any property in the vicinity of the flight that requires protection from potential debris impact, identify the potential damage of concern, and mitigate the associated risk (Requirement 42753). Note: In general, the requirements for managing risk to the public and workforce (i.e., people) also provide appropriate protection for property. However, local authorities may have risk management requirements that apply to certain property, or there may be specifice property for which the program requires risk management due to its proximity to the flight and the consequences associated with a potential debris impact. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.c | 42754 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Quantify and document any risk through the conduct of a formal risk assessment (Requirement 42754). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.d | 42755 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Make risk acceptance/disposition decisions that integrate concerns for public risk, workforce risk, risk to any property identified under paragraph 3.2.4.3.b, mission risk, including the risk to the safety of any flight crew, and mission constraints (Requirement 42755). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.e | 42756 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Make operational decisions needed to control risk prior to initiation of flight or each phase of flight (Requirement 42756). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.f | 42762 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Document decisions concerning approval of operations, acceptance/disposition of safety risk including justification, and the application of any additional safety controls or constraints based on safety evaluations (Requirement 42762). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.g | 42763 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Inform operational personnel of the hazards and safety risk associated with the conduct of any range operation (Requirement 42763). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.3.h | 42764 | Range Safety Analysis: Risk Management Process: Within the risk management process, the vehicle program, the range safety organization(s), and the authority responsible for the range, launch site, or landing site shall coordinate to: Inform on-site public/visitors of hazards and safety risk associated with viewing a range operation from NASA-controlled property (Requirement 42764). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.4(1) | 42765 | Range Safety Analysis: Risk Management Process. Range Safety Risk Management Plan (RSRMP): The RSRMP shall be a formal written document that details a vehicle program's risk management process (Requirement 42765). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.4(2) | 42766 | Range Safety Analysis: Risk Management Process. Range Safety Risk Management Plan (RSRMP): The RSRMP shall be a formal written document that details a vehicle program's risk management process: The RSRMP shall demonstrate how the vehicle program satisfies the risk criteria of paragraph 3.2.4.5 (Requirement 42766). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.4(3) | 42767 | Range Safety Analysis: Risk Management Process. Range Safety Risk Management Plan (RSRMP): The RSRMP shall be a formal written document that details a vehicle program's risk management process: The RSRMP shall incorporate any acceptance of risk that exceeds the criteria of paragraph 3.2.4.5 (Requirement 42767). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.4(4) | 42768 | Range Safety Analysis: Risk Management Process. Range Safety Risk Management Plan (RSRMP): The RSRMP shall be a formal written document that details a vehicle program's risk management process: The RSRMP shall incorporate the risk management requirements and processes of any other organization that supports the program, such as the range, launch site, or landing site (Requirement 42768). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.4(5) | 42769 | Range Safety Analysis: Risk Management Process. Range Safety Risk Management Plan (RSRMP): The RSRMP shall be a formal written document that details a vehicle program's risk management process: Note: Approval of the RSRMP constitutes NASA acceptance of any range safety risks documented in the RSRMP. Paragraph 1.3.7.p of this NPR identifies the approval authorities. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5 | 42770 | Range Safety Analysis: Risk Management Process: Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation (Requirement 42770). Note: These criteria are consistent with those used throughout the government and commercial range community and consistent with other industries' standards addressing operations that are potentially hazardous to the public and workforce. In general, these criteria define a level of assessed risk to the public, workforce, and property that the Agency accepts for all range operations without higher management review. If a range operation is to exceed any of these criteria, the variance process and associated requirements outlined in section 1.4 of this NPR apply. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.a.1 | 42772 | Range Safety Analysis: Risk Management Process: Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Individual Risk: Probability of casualty (Pc)<=1 less than or equal to 10^-6 for individual people who are not mission essential, applied separately for each hazard, each flight (Requirement 42772). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.a.2 | 42773 | Range Safety Analysis: Risk Management Process. Risk Criteria: Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Individual Risk: Pc <=10 less than or equal to 10^-6 for mission essential personnel, applied separately for each hazard, each flight (Requirement 42773). Note: For purposes of consistency with DoD and FAA range safety policy, the specific hazards considered in a range safety risk assessment are defined in paragraph 3.2.5.6 of this NPR. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.b | 42774 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Property Impact Probability. Probability of debris impact <= 1 less than or equal to 10^-3 for any property identified under paragraph 3.2.4.3.b that could result in the damage of concern identified under paragraph 3.2.4.3.b, applied for each flight (Requirement 42774). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.1 | 42776 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Risk Criterion for Center Essential Personnel. Expectation of Casualty (Ec) <= 300 less than or equal to 10^-6 casualties per flight, applied separately for each hazard, each flight (Requirement 42776). Note: Center essential personnel include mission essential personnel. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.2 | 42777 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for all Flights other than Controlled Entry (Requirement 42777): | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.2.b | 42779 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for all Flights other than Controlled Entry: Ec<= 1 less than or equal to 10^-3 casualties per year, applied separately for each hazard, for each individual range or launch site. Note: The 1 less than or equal to 10^-3 per year (i.e., one casualty in a thousand years) public risk criterion as a historical basis for the widely accepted 30 in a million launch risk criterion. (1 less than or equal to 10^-3 per year divided by an average of 33 launches per year from a given launch site yields the risk criterion of 30 casualties in a million launches.) NASA has adopted the per-year criterion as an acceptable option for both launch and entry. This approach allows some flexibility for addressing the operation of new or unique vehicles while remaining consistent with widely recognized criteria for acceptable risk to the public. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.2.b.i | 42780 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for all Flights other than Controlled Entry: Ec<= 1 less than or equal to 10^-3 casualties per year, applied separately for each hazard, for each individual range or launch site: Each vehicle program shall coordinate with the official(s) responsible for the range/site to establish the flight specific risk criteria and any other constraints needed to ensure that the range/site satisfies the annual criterion (Requirement 42780). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.2.b.i | 42781 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for all Flights other than Controlled Entry: Ec<= 1 less than or equal to 10^-3 casualties per year, applied separately for each hazard, for each individual range or launch site: When applying this option, the flight rate shall be no less than one flight per year (Requirement 42781). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.2.b.ii | 42782 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for all Flights other than Controlled Entry: Ec<= 1 less than or equal to 10^-3 casualties per year, applied separately for each hazard, for each individual range or launch site: When applying this option, the Ec for public outside NASA-controlled property shall not exceed 30 less than or equal to 10^-6 casualties per flight, applied separately for each hazard (Requirement 42782). Note: The per-flight risk to public outside NASA-controlled property shall be accounted for as part of the annual public risk; not in addition to the annual risk. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.2.b.ii | 42783 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for all Flights other than Controlled Entry: Ec<= 1 less than or equal to 10^-3 casualties per year, applied separately for each hazard, for each individual range or launch site: Each vehicle program's RSRMP shall document all associated criteria and constraints, including justification for the flight rate (Requirement 42783). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.3 | 42784 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for Controlled Entry (Requirement 42784): [For Space Shuttle entry operations, see paragraph 3.2.4.5.c.(4)]: | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.3.2.i | 42786 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for Controlled Entry: [For Space Shuttle entry operations, see paragraph 3.2.4.5.c.(4)]: Ec<= 1 less than or equal to 10^-3 casualties per year, applied for a combination of all hazards, for each individual landing site: When applying this option, the entry rate shall be no less than one entry per year (Requirement 42786). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.3.2.ii | 42787 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for Controlled Entry: [For Space Shuttle entry operations, see paragraph 3.2.4.5.c.(4)]: Ec<= 1 less than or equal to 10^-3 casualties per year, applied for a combination of all hazards, for each individual landing site: Each entry vehicle program shall coordinate with the official(s) responsible for the landing site to establish the entry specific risk criteria and any other constraints needed to ensure that the site satisfies the annual criterion (Requirement 42787). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.3.2.iii | 42788 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for Controlled Entry: [For Space Shuttle entry operations, see paragraph 3.2.4.5.c.(4)]: Ec<= 1 less than or equal to 10^-3 casualties per year, applied for a combination of all hazards, for each individual landing site: Each vehicle program's RSRMP shall document all associated criteria and constraints, including justification for the flight rate (Requirement 42788). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.3.a | 42789 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk Criteria for Controlled Entry: [For Space Shuttle entry operations, see paragraph 3.2.4.5.c.(4)]: Ec <= 100 less than or equal to 10^-6 casualties per controlled entry, applied for a combination of all hazards; OR Note: Ec <= 100 less than or equal to 10^-6 casualties per entry is NASA's established and internationally accepted public risk criterion for uncontrolled entry of space hardware and is now adopted as an acceptable criterion for controlled entry operations. This criterion represents a total Ec for all hazards, unlike the Ec <= 30 less than or equal to 10^-6 launch criterion, which applies per hazard. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.4.a | 42791 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk for Space Shuttle Entry: The assessed collective public risk for Space Shuttle entries shall not exceed the highest risk associated with the ascending entry trajectories into Kennedy Space Center (KSC) from the International Space Station orbit inclination of 51.6 degrees except as described in paragraph 3.2.4.5.c(4)(b) (Requirement 42791). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.04.5.c.4.b | 42792 | Range Safety Analysis: Risk Management Process. Risk Criteria. Each range operation shall satisfy the following criteria for assessed risk unless higher risk levels are specifically authorized for the operation: Collective Risk: Collective Public Risk for Space Shuttle Entry: If an entry must take place under off-nominal conditions or when critical crew safety factors (e.g. landing site weather, Orbiter consumables, crew health and duty day) require the consideration of alternate landing site opportunities, the Space Shuttle Program shall balance the mitigation of public and crew risk in selecting the entry opportunity and landing site (Requirement 42792). Note: This provision is necessary due to the Space Shuttle's established design and operational constraints. Any significant alterations to Space Shuttle entry operations would have the potential for negative effects on crew and mission. This provision allows the Space Shuttle Program to continue to use KSC as its primary landing site, with Edwards Air Force Base and White Sands Missile Range as backups. The Shuttle Program, in coordination with NASA Headquarters, has quantified and thoroughly evaluated the risks associated with this provision. The public collective risk associated with this provision is acceptable for the remaining Space Shuttle missions. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.1 | 42794 | Range Safety Analysis: Range Safety Risk Assessment: A range safety risk assessment shall be a formal documented analysis that identifies and quantifies risk for input to the risk management process (Requirement 42794). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.2 | 42795 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall provide a best estimate of the risks and include an evaluation of uncertainty bounds or sensitivities to inputs (Requirement 42795). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.3 | 42796 | Range Safety Analysis: Range Safety Risk Assessment: The assessment documentation shall identify all assumptions made (Requirement 42796). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.4.a | 42798 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall account for variability associated with the following: Each source of hazard, including any associated with a payload, during flight (Requirement 42798). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.4.b | 42799 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall account for variability associated with the following: Normal flight and each appropriate foreseeable failure response mode of the vehicle for each flight phase (Requirement 42799). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.4.c | 42800 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall account for variability associated with the following: Each appropriate foreseeable external and internal vehicle flight environment (Requirement 42800). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.4.d | 42801 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall account for variability associated with the following: Public and worker population potentially exposed to the flight (Requirement 42801). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.4.e | 42802 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall account for variability associated with the following: Population growth rates in order to remain valid if a risk assessment will apply to a number of flights over a number of years (Requirement 42802). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.4.f | 42803 | Range Safety Analysis: Range Safety Risk Assessment: The risk assessment shall account for variability associated with the following: The performance of any range safety system, control, or constraint including all associated time delays (Requirement 42803). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.a | 42805 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Quantitative assessment of vehicle reliability unless the vehicle will operate under full containment where any associated hazard cannot reach persons and property (Requirement 42805). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.b | 42806 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Proposed trajectories (nominal, preplanned contingency, abort, and malfunction trajectories) (Requirement 42806). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.c | 42807 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Description of any landing sites and/or flight paths (Requirement 42807). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.d | 42808 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Description of credible failure modes and their probability of occurrence resulting in a hazard to public safety (Requirement 42808). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.e | 42809 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Reliability of any range safety system (Requirement 42809). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.f | 42810 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: All hazard controls and mitigation stategies (Requirement 42810). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.g | 42811 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Pertinent vehicle information, such as size, weight, propellant types and amounts, and any explosives, toxic materials, or radionuclides (Requirement 42811). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.5.h | 42812 | Range Safety Analysis: Range Safety Risk Assessment: Input data used for the range safety risk assessment shall include: Other relevant data required for analysis in support of specific mission objectives, including related payload information (Requirement 42812). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.6 | 42813 | Range Safety Analysis: Range Safety Risk Assessment: There are typically three types of hazards considered in a range safety risk assessment. These include debris, far-field blast overpressure, and toxic material release (see paragraphs 3.2.6, 3.2.7, and 3.2.8 respectively of this NPR). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.6.a | 42814 | Range Safety Analysis: Range Safety Risk Assessment: There are typically three types of hazards considered in a range safety risk assessment. These include debris, far-field blast overpressure, and toxic material release (see paragraphs 3.2.6, 3.2.7, and 3.2.8 respectively of this NPR): A risk assessment shall account for the risk due to each hazard where applicable for each flight unless the hazard is fully contained (Requirement 42814). Note: Containment for the purposes of range safety is defined in Appendix A and related requirements are in paragraph 3.2.9 of this NPR. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.05.6.b | 42815 | Range Safety Analysis: Range Safety Risk Assessment: There are typically three types of hazards considered in a range safety risk assessment. These include debris, far-field blast overpressure, and toxic material release (see paragraphs 3.2.6, 3.2.7, and 3.2.8 respectively of this NPR): Other hazards may exist based on specific mission requirements, and these hazards shall be included in the assessment on a case-by-case basis (Requirement 42815). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.1 | 42817 | Range Safety Analysis: Debris Risk Assessment: A range safety analysis shall assess any risk due to debris for input to the risk management process (Requirement 42817). For a launch, these requirements apply to any debris that does not achieve orbit. For an entry operation, these requirements apply to any debris that might be generated, intentionally or not, after the deorbit burn or sample return capsule release. Any orbital debris is subject to the requirements of NPD 8710.3, NASA Policy for Limiting Orbital Debris Generation. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.a | 42819 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: All potential debris, generated intentionally or not, that could cause a casualty, including debris that could affect someone on the ground or on a waterborne vessel, or cause an aircraft accident (Requirement 42819). Note: Casualty models used in range safety risk assessments typically evaluate certain impact parameters, such as kinetic energy, and incorporate thresholds on those paramenters that define when a debris impact has the potential to cause a casualty or down an aircraft. These thresholds may change as our knowledge of human vulnerability/aircraft vulnerability evolves. Sources of the latest casualty and aircraft impact thresholds developed for use by the range safety community include RCC 321, Common Risk Criteria for National Test Ranges: Inert Debris, and AFSPCMAN 91-710, Range Safety User Requirements Manual. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.b | 42820 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: All populated areas in the overflight area that could be impacted by the debris (Requirement 42820). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.c | 42821 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: The probability of the debris impacting each populated area, which accounts for the probability of vehicle failure (Requirement 42821). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.d | 42822 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: The effective casualty area of the impacting debris, which accounts for the cross-sectional area of the debris, average size of a person, and the effects of any overpressure due to any explosive debris (debris that would explode on or after impact) (Requirement 42822). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.e | 42823 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: The population density of each populated area (Requirement 42823). The assessment should consider any risk mitigation factors associated with each population, such as sheltering and time of day of the flight. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.f | 42824 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: Debris variability, including size, shape, aerodynamic properties, weight, and potential to survive to impact (Requirement 42824). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.g | 42825 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: The sources of debris variability, including breakup conditions (Requirement 42825). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.h | 42826 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: The uncertainties in the state vector at the instant of jettison or destruct and any correlations used (Requirement 42826). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.i | 42827 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: Any velocity imparted to the debris fragments during jettison, destruct or breakup (Requirement 42827). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.2.j | 42828 | Range Safety Analysis: Debris Risk Assessment: An assessment of risk to the public and workforce due to debris shall account for each of the following as a function of flight-time or loss-of-control-time: The influence of atmospheric variability, including winds (Requirement 42828). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.a | 42830 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: All potential debris (intentionally or unintentionally generated) that could cause property damage, which accounts for the specific nature of the property (Requirement 42830). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.b | 42831 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: The cross-sectional area of the debris and the effects of any overpressure due to any explosive debris (debris that would explode on or after impact)(Requirement 42831). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.c | 42832 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: Debris variability, including size, shape, aerodynamic properties, weight, and potential to survive to impact (Requirement 42832). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.d | 42833 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: The sources of debris variability, including breakup conditions (Requirement 42833). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.e | 42834 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: The uncertainties in the state vector at the instant of jettison or destruct and any correlations used (Requirement 42834). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.f | 42835 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: Any velocity imparted to the debirs fragments during jettison, destruct, or breakup (Requirement 42835). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.g | 42836 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: The influence of atmospheric variablity, including winds (Requirement 42836). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.3.h | 42837 | Range Safety Analysis: Debris Risk Assessment: A debris risk assessment for any property identified under paragraph 3.2.4.3.b shall account for: The probability of the debris impacting the property, which accounts for the probability of vehicle failure and the location, size, and shape of the property (Requirement 42837). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.4 | 42838 | Range Safety Analysis: Debris Risk Assessment: A range safety analysis shall establish flight commit criteria and operational constraints, such as hazard areas and impact limit lines, needed to control any risk due to debris impacts (Requirement 42838). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.06.5 | 42839 | Range Safety Analysis: Debris Risk Assessment. A range safety analysis shall establish hazard areas needed to control risk due to debris including aircraft and ship hazard areas for notices to mariners and notices to airmen (Requirement 42839). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.1 | 42841 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A range safety analysis shall characterize the risk to the public and the workforce due to any far-field blast overpressure from potential explosions during vehicle operations for input to the risk management process (Requirement 42841). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.2 | 42842 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: The analysis shall establish flight commit criteria to control risk due to potential distance focus overpressure effects (Requirement 42842). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.3 | 42843 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A far-field blast overpressure analysis shall account for: The potential for distance focus overpressure or overpressure enhancement given current meteorological conditions and terrain characteristics (Requirement 42843). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.3.a | 42844 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A far-field blast opverpressure analysis shall account for: The potential for broken windows and related casualties (Requirement 42844). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.3.b | 42845 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A far-field blast opverpressure analysis shall account for: Characteristics of the potentially affected windows, including their size, location, orientation, glazing material, and condition (Requirement 42845). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.3.c | 42846 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A far-field blast opverpressure analysis shall account for: The hazard characteristics of the potential glass shards, such as falling from upper building stories or being propelled into or out of a shelter toward potentially occupied spaces (Requirement 42846). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.3.d | 42847 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A far-field blast opverpressure analysis shall account for: The explosive capability of the vehicle at or after impact and at altitude and potential explosions resulting from debris impacts, including the potential for mixing of liquid propellants (Requirement 42847). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.07.3.e | 42848 | Range Safety Analysis: Far-Field Blast Overpressure Effects Risk Assessment: A far-field blast opverpressure analysis shall account for: Characteristics of the vehicle flight and the surroundings that would affect the population's susceptibility to injury, for example, shelter types and time of day of the proposed activity (Requirement 42848). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.1 | 42850 | Range Safety Analysis: Toxic Hazard Risk Assessment: In the case of a catastrophic failure of a vehicle in flight, rocket fuel and oxidizer residues (e.g., aerozine-50, nitrogen tetroxide, hydrogen chloride from solid rocket motors, and their combustion products) may be present. Under certain meteorological conditions, high concentrations of these materials may drift over populated areas at levels greater than emergency health standards permit. As a result, NASA shall protect the public and workforce from toxic hazards using either hazard containment or a risk mitigation approach (Requirement 42850). This paragraph does not apply to any potential release of radioactive materials. (See paragraph 3.3.7.3). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.2 | 42851 | Range Safety Analysis: Toxic Hazard Risk Assessment: A range safety analysis shall establish flight commit criteria to control any risk due to potential toxic material release (Requirement 42851). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.2.a | 42852 | Range Safety Analysis: Toxic Hazard Risk Assessment: A range safety analysis shall establish flight commit criteria to control any risk due to potential toxic material release: The analysis shall assess any residual risk due to potential toxic material release not fully contained or mitigated for input to the program's risk management process (Requirement 42852). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.2.b.1 | 42854 | Range Safety Analysis: Toxic Hazard Risk Assessment: A range safety analysis shall establish flight commit criteria to control any risk due to potential toxic material release: The analysis shall account for: Any foreseeable toxic material release during the proposed flight or in the event of a mishap (Requirement 42854). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.2.b.2 | 42855 | Range Safety Analysis: Toxic Hazard Risk Assessment: A range safety analysis shall establish flight commit criteria to control any risk due to potential toxic material release: The analysis shall account for: Any operational constraints and emergency procedures that provide protection from toxic material release (Requirement 42855). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.2.b.3 | 42856 | Range Safety Analysis: Toxic Hazard Risk Assessment: A range safety analysis shall establish flight commit criteria to control any risk due to potential toxic material release: The analysis shall account for: All populations potentially exposed to any toxic material release, including all members of the public and workforce on land and on any waterborne vessels and aircraft (Requirement 42856). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.2.b.4 | 42857 | Range Safety Analysis: Toxic Hazard Risk Assessment: A range safety analysis shall establish flight commit criteria to control any risk due to potential toxic material release: The analysis shall account for: Potential emissions from both nominal range operations and catastrophic events to ensure response actions are designed to prevent or mitigate possible exposures (Requirement 42857). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.08.3 | 42858 | Range Safety Analysis: Toxic Hazard Risk Assessment: The American Industrial Hygiene Association - Emergency Response Planning Guidelines (ERPG) - shall be used for determining the need and requirements for emergency response action plans (Requirement 42858). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.09.1 | 42860 | Range Safety Analysis: Containment: When controlling risk through containment, the range safety analysis shall provide the basis for establishing the geographical areas from which people and any property identified under paragraph 3.2.4.3.b shall be excluded during flight (Requirement 42860). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.09.2 | 42861 | Range Safety Analysis: Containment: The analysis shall determine any operational controls needed to isolate each hazard and prevent/mitigate the risk due to hazard (Requirement 42861). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.09.3 | 42862 | Range Safety Analysis: Containment: The cognizant range safety organization, in conjunction with the program, shall establish the containment criteria for normal and malfunctioning vehilcle flight (Requirement 42862). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.09.4 | 42863 | Range Safety Analysis: Containment: Any residual risk due to any hazard not fully contained shall undergo the risk management process of paragraph 3.2.4 (Requirement 42863). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.10.1 | 42865 | Range Safety Analysis: Risk Mitigation: When controlling risk through mitigation, a range safety analysis shall establish the operational constraints that negate the risk or reduce it to a level that is acceptable with appropriate management approval (Requirement 42865). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.2.10.2 | 42866 | Range Safety Analysis: Risk Mitigation: Any residual risk not fully mitigated shall undergo the risk management process of paragraph 3.2.4 (Requirement 42866). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1 | 42868 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.1 | 42869 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: Any vehicle, stage, or payload with propulsive capability that poses elevated risk to the public shall have an FTS as needed to satisfy the range safety analysis requirements of paragraph 3.2 of this NPR (Requirement 42869). Note: Based on a case-by-case assessment, an inhabited vehicle might incorporate an FTS only on certain components and not on the inhabited portion of the vehicle. NPR 8705.2, Human-Rating Requirements for Space Systems, contains requirements that apply when an FTS is used on any component of an inhabited vehicle. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.2 | 42870 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: When designing future inhabited aerospace vehicles, NASA shall consider designs that provide controllability and high reliability, fuels and materials of low toxicity, and trajectories for launch and entry that limit exposure of hazards to populations to negate the need for an FTS (Requirement 42870). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.3 | 42871 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: When an FTS is used, the termination action shall inhibit further deviation in the instantaneous impact point of the vehicle, including any payload, and disperse any hazardous propellant in a predictable manner (Requirement 42871). This serves to limit further exposure of population to hazards associated with an errant vehicle. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.4 | 42872 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: The FTS shall satisfy the design and test requirements of AFSPCMAN 91-710, Range Safety User Requirements Manual, RCC 313, Test Standards for Flight Termination Receiver/Decoders, or RCC 319, Flight Termination Systems-Commonality Standard (Requirement 42872). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.5 | 42873 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: When an FTS is used for a NASA or NASA-sponsored vehicle, the vehicle program shall implement a secure FTS in accordance with NPR 2810.1, Security of Information Technology (Requirement 42873). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.6 | 42874 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: The configuration of an installed, approved FTS shall be controlled using a standard configuration control management process (Requirement 42874). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.7.a | 42876 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: Criteria for activiation of the FTS for uninhabited vehicles shall include conditions for when: Valid data shows the vehicle violating a flight termination boundary, unless other documented mitigations are in effect (Requirement 42876). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.7.b | 42877 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: Criteria for activiation of the FTS for uninhabited vehicles shall include conditions for when: Vehicle performance or location is unknown, the vehicle is capable of violating a flight termination boundary, and terminating flight would mitigate the risk (Requirement 42877). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.7.c | 42878 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: Criteria for activiation of the FTS for uninhabited vehicles shall include conditions for when: There is a gross trajectory deviation or obvious erratic flight rendering the vehicle uncontrollable (Requirement 42878). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.7.d | 42879 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: Criteria for activiation of the FTS for uninhabited vehicles shall include conditions for when: Other mission-specific conditions present rationale for additional criteria (Requirement 42879). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.1.8 | 42880 | Range Safety: Range Safety Systems: Flight Termination System (FTS). An FTS provides for hazard mitigation during vehicle flight and may be a major component of a vehicle program's risk management approach: When an inhabited vehicle or its launch system require an FTS, the range safety organization and the program shall coordinate to develop the flight terminaiton activation criteria (Requirement 42880). NPR 8705.2, Human-Rating Requirements for Space Systems, applies. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.2.1 | 42882 | Range Safety: Range Safety Systems: Recovery Systems: Recovery systems intended to save or preseve the flight vehicle in the event of a malfunction shall not be considered an FTS (Requirement 42882). A recovery system may be considered as risk mitigation and factor into the range safety risk assessment for the range operation where applicable. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.2.2 | 42883 | Range Safety: Range Safety Systems: Recovery Systems: Activation of a recovery system shall not increase the risk to people or property (Requirement 42883). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.3.2 | 42886 | Range Safety: Range Safety Systems: Contingency Management System (CMS): A CMS shall not be considered an FTS (Requirement 42886). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.3.3 | 42887 | Range Safety: Range Safety Systems: Contingency Management System (CMS): Activation of a CMS shall not increase the risk to people or property (Requirement 42887). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.3.4 | 42888 | Range Safety: Range Safety Systems: Contingency Management System (CMS): A CMS may be considered as risk mitigation and factor into the range safety risk assessment for the range operation where applicable. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.4.1.a | 42891 | Range Safety: Range Safety Systems: Vehicle Tracking: For a vehicle that is flown with an FTS: The range safety systems used to support a flight termination decision shall include at least two sources of vehicle tracking data; where the two sources are independent of each other and one of the sources is independent of the vehicle guidance system (Requirement 42891). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.4.1.b | 42892 | Range Safety: Range Safety Systems: Vehicle Tracking: For a vehicle that is flown with an FTS: The tracking data shall be of sufficient quality to determine the vehicle's real time position and instantaneous impact point throughout the entire period of time that the FTS is used to contain the hazard and make range safety decisions (Requirement 42892). Note: This tracking time period includes launch through orbital insertion for orbital vehicles, throughout the mission for suborbital or aeronautical vehicles, and upon entry through landing for entry vehicles. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.4.2 | 42893 | Range Safety: Range Safety Systems: Vehicle Tracking: For the flight of an uninhabited vehicle that is flown without an FTS, the range safety system shall include tracking or other data sources sufficient to determine the impact footprint of all vehicle components (Requirement 42893). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.5.1 | 42895 | Range Safety: Range Safety Systems: Telemetry: All data systems that provide information used to evaluate range safety requirements shall undergo validation to ensure operational readiness prior to initiating any phase of flight such as launch or entry (Requirement 42895). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.5.2 | 42896 | Range Safety: Range Safety Systems: Telemetry: The range safety telemetry system shall provide continuous, accurate data during preflight operations and during flight (Requirement 42896). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.5.3 | 42897 | Range Safety: Range Safety Systems: Telemetry: The vehicle program shall coordinate with responsible range safety organization to identify the safety data required for each flight (Requirement 42897). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.5.4 | 42898 | Range Safety: Range Safety Systems: Telemetry: For a vehicle that uses an FTS, the telemetry data shall include parameters that describe the health and status of the FTS and the vehicle needed to support a flight termination decision (Requirement 42898). These parameters may include: | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.6.1 | 42911 | Range Safety: Range Safety Systems: FTS Command System: An FTS command system used to support missions that require an FTS shall incorporate fully redundant and independent command paths (Requirement 42911). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.6.2 | 42912 | Range Safety: Range Safety Systems: FTS Command System: An FTS command system shall undergo validation to ensure operational readiness prior to every mission (Requirement 42912). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.6.3 | 42913 | Range Safety: Range Safety Systems: FTS Command System: FTS command systems shall be under configuration control (Requirement 42913). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.1 | 42915 | Range Safety: Range Safety Systems: Radiation Systems: NASA programs shall control radiation sources during all operational phases to ensure the protection of people, environment, facilities, and equipment and compliance with applicable Federal, State, and local regulations and NASA requirements (Requirement 42915). Note: Such radiation sources include radio-frequency/microwave emitters, radioactive materials, X-ray devices, lasers, and optical emitters. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.2 | 42916 | Range Safety: Range Safety Systems: Radiation Systems: Nonionizing Radio Frequency (RF) Radiation Controls - All operations involving the use of RF transmitters (including FTS) shall be licensed, scheduled, and coordinated through the range and conform to the standards and regulations specified in IEEE C95.1-1991, American National Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 30 KHz to 100 GHz., and regulations of the range involved in the operation (Requirement 42916). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.3 | 42917 | Range Safety: Range Safety Systems: Radiation Systems: Ionizing Radiation Controls - All operations involving the use of radioactive sources shall conform to the standards and regulations of the Nuclear Regulatory Comission and regulations of the range involved in the operation (Requirement 42917). Note: Policies and guidance for handling, use, and storage of radioactive material, including the approvals required, are contained in directives under the purview of NASA occupational health organizations (see NPD 1800.2, NASA Occupational Health Program). NPR 8715.3, NASA Safety Manual, Chapter 5, contains requirements and guidance applicable to launch of any radioactive materials. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.4.1 | 42919 | Range Safety: Range Safety Systems: Radiation Systems: Laser Hazard Controls: All operations involving the use of lasers shall comply with ANSI Z136.1, American National Standard for the Safe Use of Lasers (Requirement 42919). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.4.2 | 42920 | Range Safety: Range Safety Systems: Radiation Systems: Laser Hazard Controls: All operations involving the use of lasers outdoors shall comply with ANSI Z136.6-2000, American National Standard for the Safe Use of Lasers Outdoors (Requirement 42920), which includes the following: | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.4.2.a | 42921 | Range Safety: Range Safety Systems: Radiation Systems: Laser Hazard Controls: All operations involving the use of lasers outdoors shall comply with ANSI Z136.6-2000, American National Standard for the Safe Use of Lasers Outdoors, which includes the following: Lasers entering the National Airspace shall have an FAA letter of nonobjection (Requirement 42921). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.7.4.2.b | 42922 | Range Safety: Range Safety Systems: Radiation Systems: Laser Hazard Controls: All operations involving the use of lasers outdoors shall comply with ANSI Z136.6-2000, American National Standard for the Safe Use of Lasers Outdoors, which includes the following: Programs that use a laser with the potential to strike orbiting satellites shall coordinate its operations with the DoD Laser Safety Clearinghouse (Requirement 42922). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.8.1 | 42924 | Range Safety: Range Safety Systems: Safety Critical Software: Range safety systems that incorporate safety critical software that are used to support NASA missions shall have an independent verification and validation plan in accordance with the NPD 8730.4, Software Independent Verificaiton and Validation (IV&V) Policy (Requirement 42924). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.3.8.2 | 42925 | Range Safety: Range Safety Systems: Safety Critical Software: NASA safety-critical software shall be developed in accordance with NPR 7150.2, NASA Software Engineering Requirements, and NASA STD 8719.13, Software Safety (Requirement 42925). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.1.1 | 42928 | Range Safety: Operational Requirements: Flight Commit Criteria: The flight commit criteria for a range operation shall identify the conditions that must be met to initiate each flight or phase of flight (see paragraph 3.2.4.e.1 for requirements that apply to phases of flight) (Requirement 42928). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.1.2.a | 42930 | Range Safety: Operational Requirements: Flight Commit Criteria: The flight commit criteria shall provide for: Assurance that the collision avoidance requirements of paragraph 3.4.3 are satisfied for any launch or entry (Requirement 42930). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.1.2.b | 42931 | Range Safety: Operational Requirements: Flight Commit Criteria: The flight commit criteria shall provide for: Surveillance of any established hazard areas (Requirement 42931). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.1.2.c | 42932 | Range Safety: Operational Requirements: Flight Commit Criteria: The flight commit criteria shall provide for: Verification that all range safety systems are available and operational (Requirement 42932). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.1.2.d | 42933 | Range Safety: Operational Requirements: Flight Commit Criteria: The flight commit criteria shall provide for: Verification that the meteorological conditions, such as wind, lightning, and visibility, are within the limits defined by the range safety analysis (Requirement 42933). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.1.3 | 42934 | Range Safety: Operational Requirements: Flight Commit Criteria: Implementation of the flight commit criteria shall include documenting the actual conditions at the time of flight or time of each phase of flight where applicable to verify that the flight commit criteria have been met (Requirement 42934). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.2.1 | 42936 | Range Safety: Operational Requirements: Entry Operations. For an entry operation, the vehicle program and the receiving landing site have responsibility for range safety risk management. In this regime, range safety responsibility begins with concurrence with the decision to send the final command that initiates the entry and landing sequence: Commit to entry and landing shall be initiated (enabled) by vehicle operator control (Requirement 42936). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.2.2 | 42937 | Range Safety: Operational Requirements: Entry Operations. For an entry operation, the vehicle program and the receiving landing site have responsibility for range safety risk management. In this regime, range safety responsibility begins with concurrence with the decision to send the final command that initiates the entry and landing sequence: Entry and landing shall not be initiated until all conditions critical to safety have been confirmed (Requirement 42937). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.2.3 | 42938 | Range Safety: Operational Requirements: Entry Operations. For an entry operation, the vehicle program and the receiving landing site have responsibility for range safety risk management. In this regime, range safety responsibility begins with concurrence with the decision to send the final command that initiates the entry and landing sequence: The reliability of the vehicle to achieve controlled entry to the targeted landing site or debris footprint shall be at least 0.99 with 50 percent confidence (Requirement 42938). Note: The intent is to provide appropriate assurance that the vehicle will be deorbited in a predictable manner (i.e., avoid skip out) and allow for appropriate risk management during the entry operation in accordance with paragraph 3.2.4. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.3.1 | 42940 | Range Safety: Operational Requirements: Collision Avoidance (COLA): A space vehicle program, in coordination with the responsible range safety organization, shall ensure that the vehicle, any jettisoned component, or payload does not pass closer than 200 kilometers to an orbiting inhabited on inhabitable spacecraft (Requirement 42940). Note: This applies throughout suborbital flight to landing and final impact. For orbital flight, this applies during ascent to initital orbital insertion and through at least one complete orbit. For any entry operation, this applies from the point that the commit to deorbit is initiated through landing or final impact. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.3.2.a | 42942 | Range Safety: Operational Requirements: Collision Avoidance (COLA). The vehicle program or responsible range safety organization shall: Inform the United States Strategic Command of an upcoming launch or entry operation at least 15 days before the operation (Requirement 42942). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.3.2.b | 42943 | Range Safety: Operational Requirements: Collision Avoidance (COLA). The vehicle program or responsible range safety organization shall: Notify the United States Strategic Command immediately of an change in the planned launch or entry operations that occurs after the initial notification (Requirement 42943). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.3.2.c | 42944 | Range Safety: Operational Requirements: Collision Avoidance (COLA). The vehicle program or responsible range safety organization shall: Obtain a COLA analysis from the United States Strategic Command or perform an equivalent analysis needed to satisfy paragraph 3.4.3.1 of this NPR (Requirement 42944). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.3.2.d | 42945 | Range Safety: Operational Requirements: Collision Avoidance (COLA). The vehicle program or responsible range safety organization shall: Implement any constraints needed to satisfy paragraph 3.4.3.1 of this NPR (Requirement 42945). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.4.1 | 42947 | Range Safety: Operational Requirements: Uninhabited Aerial Vehicles Operations: The RCC 323, Range Safety Criteria for Unmanned Air Vehicles, shall be used for guidance when operating, hosting, or sponsoring a UAV operation (Requirement 42947). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.4.4.2 | 42948 | Range Safety: Operational Requirements: Uninhabited Aerial Vehicles Operations: Lead range safety responsibility for a UAV flight shall default to the initiating Center or range (where takeoff occurs) (Requirement 42948). Note: Each takeoff initiates a distinct range operation. Unless other agreements are made between the ranges involved, if a UAV lands at a site that has a different authority than the original takeoff site, lead range safety responsibility for future takeoff and subsequent flight from the new site transfers to the new range authority. | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.1.a | 42951 | Range Safety: Range Safety Personnel Qualifications and Training: Qualifications for personnel who perform a range safety function (including RSOs and personnel responsible for range safety systems and range safety analysis) shall include: Successful completion of knowledge-based training (self-study and/or classroom) applicable to the range safety function (Requirement 42951). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.1.b | 42952 | Range Safety: Range Safety Personnel Qualifications and Training: Qualifications for personnel who perform a range safety function (including RSOs and personnel responsible for range safety systems and range safety analysis) shall include: Successful completion of instructor-led, hands-on training on how to perform the range safety function followed by satisfactory on-the-job performance as a trainee, as applicable (Requirement 42952). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.1.c | 42953 | Range Safety: Range Safety Personnel Qualifications and Training: Qualifications for personnel who perform a range safety function (including RSOs and personnel responsible for range safety systems and range safety analysis) shall include: Proficiency demonstrated to a qualified range safety professional during simulation scenarios that exercise hands-on operations of range safety systems and use of safety decision-making tools or processes, as applicable (Requirement 42953). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.1.d | 42954 | Range Safety: Range Safety Personnel Qualifications and Training: Qualifications for personnel who perform a range safety function (including RSOs and personnel responsible for range safety systems and range safety analysis) shall include: Proficiency demonstrated to a qualified range safety professional during exercises of nominal and contingency actions, as applicable (Requirement 42954). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.2.a | 42956 | Range Safety: Range Safety Personnel Qualifications and Training: The training program for range safety personnel shall: Provide qualified personnel to support nominal and contingency range operations (Requirement 42956). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.2.b | 42957 | Range Safety: Range Safety Personnel Qualifications and Training: The training program for range safety personnel shall: Include a recurring training process to ensure personnel retain their qualifications (Requirement 42957) | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.2.c | 42958 | Range Safety: Range Safety Personnel Qualifications and Training: The training program for range safety personnel shall: Include a requalification process for personnel who lose qualification status, such as, someone who exhibits substandard performance or has temporary health problems (Requirement 42958). | S | Y | Y | Safety | |||
| NPR 8715.5 | 3.5.2.d | 42959 | Range Safety: Range Safety Personnel Qualifications and Training: The training program for range safety personnel shall: Include a documentation process that captures the qualification, recurring training, and requalification status of all range safety personnel (Requirement 42959). | S | Y | Y | Safety | |||
| CxP 70059 | 2.4 | SAF-191 | NASA STD 8719.14 | 1.1.3 | 56244 | SCOPE: Purpose: This document, along with the associated Debris Assessment Software (DAS) [version 2.0 or higher] provided by the NASA Orbital Debris Program Office (NASA ODPO) located at Johnson Space Center (JSC), shall be used by the program or project manager as the primary reference in conducting orbital debris assessments (Requirement 56244). | S | Y | Y | Safety |
| NASA STD 8719.14 | 1.2.e | 56255 | SCOPE: Applicability: NASA spacecraft, launch vehicles, and instruments that passed Preliminary Design Review prior to August 1995 (release of NASA Safety Standard (NSS) 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris) are not required to perform an ODA unless a large change in design or changes in space object capability or risk affect the ability to achieve compliance with the requirements. If one or more of these conditions occur, an ODA Report (ODAR) shall be performed (Requirement 56255). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.2.1.e | 56372 | Requirements: Conducting Debris Assessments: An Overview: ODA and ODARs: ODAs being performed on components or portions of a spacecraft shall document the assessment in the abbreviated ODAR using Appendix A.3 (Requirement 56372). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.2.1.i | 56376 | Requirements: Conducting Debris Assessments: An Overview: ODA and ODARs: NASA programs/projects that are flying as Space Shuttle, International Space Station (ISS), and Constellation Program payloads that remain encapsulated by the Space Shuttle/ISS (i.e., not exposed to outer space environment) are exempted from performing orbital debris assessments. Space Shuttle/ISS/Constellation payloads which are temorarily deployed and retreived into the ISS or on the same Space Shuttle or Constellation flight shall provide an abbreviated Orbital Debris Assessment (ODA) Report (ODAR) per this standard (Requirement 56376). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.2.2.b | 56380 | Requirements: Conducting Debris Assessments: An Overview: The EOMP shall be organized using Appendix B, Section B.1 (Requirement 56380). The NASA ODPO reviews the EOMPs using the Section B.1 criteria and reports findings back to the program via the OSMA using the evaluation sheet in Appendix B, Section B.2. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.2.2.c | 56381 | Requirements: Conducting Debris Assessments: An Overview: The EOMP shall contain a statement covering what actions must be undertaken in the event of reductions of capabilities or consumables which may significantly and predictably threaten the ability to carry out the EOMP (Requirement 56381). This includes reduction of system capability to "single string" unless expressly agreed otherwise. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.3.2 | 56396 | Requirements: Assessment of Debris Released During Normal Operations: Requirements for the Control of Debris Released During Normal Operations: NASA programs and projects shall assess and limit the amount of debris released (Requirement 56396). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.3.2.1 | 56397 | Requirements: Assessment of Debris Released During Normal Operations: Requirements for the Control of Debris Released During Normal Operations: Requirement 4.3-1: Debris passing through LEO: For missions leaving debris in orbits passing through LEO, released debris with diameters of 1 mm or larger shall satisfy both Requirement 4.3-1a and Requirement 4.3-1b (Requirement 56397). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.3.2.1.a | 56398 | Requirements: Assessment of Debris Released During Normal Operations: Requirements for the Control of Debris Released During Normal Operations: Requirement 4.3-1a: All debris released during the deployment, operation, and disposal phases shall be limited to a maximum orbital lifetime of 25 years from date of release (Requirement 56398). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.3.2.1.b | 56399 | Requirements: Assessment of Debris Released During Normal Operations: Requirements for the Control of Debris Released During Normal Operations: Requirement 4.3-1b: The total object-time product shall be no larger than 100 object-years per mission (Requirement 56399). The object-time product is the sum of all debris of the total time spent below 2000 km altitude during the orbital lifetime of each object. (See section 4.3.4.2 for methods to calculate the object-time product). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.3.2.2 | 56400 | Requirements: Assessment of Debris Released During Normal Operations: Requirements for the Control of Debris Released During Normal Operations: Requirement 4.3-2: Debris passing near GEO: For missions leaving debris in orbits with the potential of traversing GEO (GEO altitude +/- 15 degrees latitude), released debris with diameters of 5 cm or greater shall be left in orbits which will ensure that within 25 years after release the apogee will no longer exceed GEO - 200 km (Requirement 56400). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.3.4 | 56407 | Requirements: Assessment of Debris Released During Normal Operations: Methods to Assess Compliance: Compliance to section 4.3 requirements shall be documented in the ODAR and EOMP for all items/objects larger than 1 mm in LEO and 5 cm in GEO planned for release during all phases of flight (Requirement 56407). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4(1) | 56433 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Orbital debris analyses assess accidental explosion probability and intentional breakups during and after completion of mission operations. Requirement area 4.4 is required for all space structures in Earth and lunar orbits (Requirement 56433). Requirement 4.4-3 is recommended for Earth-Sun Lagrange Points, Earth-Moon Lagrange points, and Mars operations. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4.2.1.1 | 56449 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Requirements for the Area: Accidental Explosions: Requirement 4.4-1: Limiting the risk to other space systems from accidental explosions during deployment and mission operations while in orbit about Earth or the Moon: For each spacecraft and launch vehicle orbital stage employed for a mission, the program or project shall demonstrate, via failure mode and effects analyses or equivalent analyses, that the integrated probability of explosion for all credible failure modes of each spacecraft and launch vehicle is less than 0.001 (excluding small particle impacts) (Requirement 56449). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4.2.1.2 | 56450 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Requirements for the Area: Accidental Explosions: Requirement 4.4-2: Design for passivation after completion of mission operations while in orbit about Earth or the Moon: Design of all spacecraft and launch vehicle orbital stages shall include the ability to deplete all onboard sources of stored energy and disconnect all energy generation sources when they are no longer required for mission operations or postmission disposal or control (Requirement 56450). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4.2.2.1.a | 56453 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Requirements for the Area: Intentional Breakups: Be conducted at an altitude such that for orbital debris fragments larger than 10 cm the object-time product does not exceed 100 object-years (Requirement 56453). For example, if the debris fragments greater than 10cm decay in the maximum allowed 1 year, a maximum of 100 such fragments can be generated by the breakup. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4.2.2.1.b | 56454 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Requirements for the Area: Intentional Breakups: Requirement 4.4-3. Limiting the long-term risk to other space systems from planned breakups: Planned explosions or intentional collisions shall: Not generate debris larger than 1 mm that shall remain in Earth orbit longer than one year (Requirement 56454). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4.2.2.2 | 56455 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Requirements for the Area: Intentional Breakups: Requirement 4.4-4: Limiting the short-term risk to other space systems from planned breakups: Immediately before a planned explosion or intentional collision, the probability of debris, orbital or ballistic, larger than 1 mm colliding with any operating spacecraft within 24 hours of the breakup shall be verified to not exceed 10^6 (Requirement 56455). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.4.4 | 56465 | Requirements: Assessment of Debris Generated by Explosions and Intentional Breakups: Methods to Assess Compliance: Compliance to section 4.4 requirements shall be documented in the ODAR and EOMP for all phases of flight (Requirement 56465). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5 | 56500 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Orbital debris analyses assess the ability of the design and mission profile of a space system to limit the probability of accidental collision with known resident space objects during the system's orbital lifetime. Requirement area 4.5 shall apply for all space structures in Earth and lunar orbits (Requirement 56500). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5.2 | 56505 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Requirements for the Collision-induced Risk to Disposal Area: NASA programs and projects shall assess and limit the probability that the operating space system becomes a source of debris if it collides with orbital debris or meteoroids (Requirement 56505). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5.2.1 | 56506 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Requirements for the Collision-induced Risk to Disposal Area: Requirement 4.5-1. Limiting debris generated by collisions with large objects when operating in Earth or lunar orbit: For each spacecraft and launch vehicle orbital stage in or passing through LEO, the program or project shall demonstrate that, during the orbital lifetime of each spacecraft and orbital stage, the probability of accidental collision with space objects larger than 10 cm in diameter is less than 0.001 (Requirement 56506). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5.2.2 | 56507 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Requirements for the Collision-induced Risk to Disposal Area: Requirement 4.5-2. Limiting debris generated by collisions with small objects when operating in Earth or lunar orbit: For each spacecraft, the program or project shall demonstrate that, during the mission of the spacecraft, the probability of accidental collision with orbital debris and meteoroids is sufficient to prevent postmission disposal is less than 0.01 (Requirement 56507). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5.4(1) | 56511 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Methods to Assess Compliance: Compliance to section 4.5 requirements shall be documented in the ODAR and EOMP for all phases of flight including the launch phase per applicability in Section 4.5 introduction (Requirement 56511). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5.4.2.e(1) | 56523 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Methods to Assess Compliance: Collisions with Small Debris During Mission Operations (Requirement 4.5-2): For operations in Earth orbit, DAS shall be used to determine whether damaging impacts by small particles could reasonably prevent successful postmission disposal operations (Requirement 56523). The software estimates the probability that meteoroid or orbital debris impacts will cause components critical to postmission disposal to fail. If this estimate shows that there is a significant probability of failure, a higher-fidelity analysis shall be used to guide any redesign and to validate any sheilding design (Requirement 56523). DAS is not intended to be used to design shielding. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.5.4.2.e(2) | 56524 | Requirements: Assessment of Debris Generated by On-orbit Collisions: Methods to Assess Compliance: Collisions with Small Debris During Mission Operations (Requirement 4.5-2): The software estimates the probability that meteoroid or orbital debris impacts will cause components critical to postmission disposal to fail. If this estimate shows that there is a significant probability of failure, a higher-fidelity analysis shall be used to guide any redesign and to validate any sheilding design (Requirement 56524). DAS is not intended to be used to design shielding. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6(5).a | 56545 | Requirements: Postmission Disposal of Space Structures: Spacecraft disposal can be accomplished by one of three methods: Requirement area 4.6 applies as follows: Requirements 4.6-1, 4.6-2, and 4.6-3 are required for all space structures when in Earth orbit (Requirement 56545). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6(5).b | 56546 | Requirements: Postmission Disposal of Space Structures: Spacecraft disposal can be accomplished by one of three methods: Requirement area 4.6 applies as follows: Requirement 4.6-4 is required for all space structure in orbit about the Earth (Requirement 56546). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6(5).c | 56547 | Requirements: Postmission Disposal of Space Structures: Spacecraft disposal can be accomplished by one of three methods: Requirement area 4.6 applies as follows: Requirement 4.6-5 is required for all space structures in orbit about the Earth and the Moon (Requirement 56547). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.1 | 56557 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-1. Disposal for space structures passing through LEO: A spacecraft or orbital stage with a perigee altitude below 2000 km shall be disposed of by one of three methods: (Requirement 56557) | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.2 | 56563 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-2. Disposal for space structures near GEO: A spacecraft or orbital stage in an orbit near GEO shall be maneuvered at EOM to a disposal orbit above GEO with a predicted minimum altitude of GEO +200 km (35,986 km) for a period of at least 100 years after disposal (Requirement 56563). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.3.a | 56565 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-3. Disposal for space structures between LEO and GEO: A spacecraft or orbital stage may be left in any orbit between 2000 km above the Earth's surface and 500 km below GEO (Requirement 56565). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.3.b | 56566 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-3. Disposal for space structures between LEO and GEO: A spacecraft or orbital stage shall not use nearly circular disposal orbits near regions of high value operational space structures, such as between 19,100 km and 20,200 km (Requirement 56566). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.4 | 56567 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-3. Disposal for space structures between LEO and GEO: Requirement 4.6-4. Reliability of postmission disposal operations in Earth orbit: NASA space programs and projects shall ensure that all postmission disposal operations are designed for a probability of success as follows: (Requirement 56567) | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.5.a | 56571 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-5. Operational design for EOM passivation: All NASA spacecraft and launch vehicles in Earth and lunar orbit shall be totally passivated at EOM to prevent breakup or further generation of orbital debris (Requirement 56571). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.5.b | 56572 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-5. Operational design for EOM passivation: The timing, order, procedures, and verification methods for performing all depletions identified for Requirement 4.4-2 shall have been developed prior to launch (Requirement 56572). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.5.c | 56573 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-5. Operational design for EOM passivation: Requirement 4.6-5 shall be updated prior to implementation of the EOMP (Requirement 56573). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.2.5.d | 56574 | Requirements: Postmission Disposal of Space Structures: Requirements for the Area: Requirement 4.6-5. Operational design for EOM passivation: Depletion Passivation shall occur as soon as this operation does not pose an unacceptable risk to the payload (Requirement 56574). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.3.d | 56580 | Requirements: Postmission Disposal of Space Structures: Rationale for the Area Requirements: If disposal by controlled reentry into the atmosphere is chosen, the trajectory must be designed to ensure that the space structure does not skip in the upper regions of the atmosphere. Therefore, the effective perigee of the reentry trajectory shall be no higher than 50 km (Requirement 56580). See section 4.7 for additional guidance on controlled reentries. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.3.f | 56582 | Requirements: Postmission Disposal of Space Structures: Rationale for the Area Requirements: Spacecraft that have terminated their mission shall be maneuvered far enough away from GEO so as not to cause interference with space systems still in geostationary orbit (Requirement 56582). The minimum increase in perigee altitude at the end of re-orbiting shall ensure that the space structure does not come within GEO + 200 km for the next 100 years. A selected perigee of GEO +235 km + (1000*CR*A/m) and an eccentricity of less than 0.005 (e<g]<0.005) will ensure that the space structure does not come within 200 km of GEO altitude (35,786 km) for at least 100 years (figure 4.6-1). [CR= solar radiation pressure coefficient, typical values: 1-2, A=area in m.^2, abd m=Mass in /> | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.3.g | 56583 | Requirements: Postmission Disposal of Space Structures: Rationale for the Area Requirements: The propulsion system for a GEO spacecraft should be designed not to be separated from the spacecraft. If there are unavoidable reasons that require separation, the propulsion system shall remain outside of the protected geosynchronous region (GEO altitude plus or minus 200 km) (Requirement 56583). Regardless of whether it is separated or not, a propulsion system shall be designed for passivation. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.3.j | 56586 | Requirements: Postmission Disposal of Space Structures: Rationale for the Area Requirements: Due to the relatively (compared with LEO) small amount of propellants needed to perform disposal maneuvers near GEO, propellant gauging issues can be important. An adequate amount of propellant shall be held in reserve to ensure that the desired disposal orbit is reached, usually through a series of maneuvers (Requirement 56586). This is even more important when orbits of very low eccentricity are needed. In accordance with Requirement 4.4-2, all propellants remaining after achieving the proper disposal orbit needs to be vented or burned in a way that does not upset the disposal orbit. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.3.m | 56589 | Requirements: Postmission Disposal of Space Structures: Rationale for the Area Requirements: When selecting a disposal orbit between LEO and GEO, a long-term (at least 100-year) orbital perturbation analysis shall be conducted (and documented in the ODAR/EOMP) to enure that the disposal orbit is not altered, particularly by solar and lunar gravitational forces, in such a way that the disposed space structure will later penetrate LEO or GEO (Requirement 56589). Even nearly circular orbits in MEO can, under certain initial conditions, later experience severe changes in eccentricity, resulting in perigees within LEO or apogees within GEO. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.6.3.o | 56591 | Requirements: Postmission Disposal of Space Structures: Rationale for the Area Requirements: All planned postmission maneuvers, including large, discrete maneuvers and continuous low-thrust maneuvers, shall be evaluated for potential collision risks with other resident space objects tracked by the U.S. Space Surveillance Network (Requirement 56591). Contact the NASA ODPO at JSC for assistance in requesting DoD support in maneuver planning. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.7.1 | 56623 | Requirements: Survival of Debris From the Postmission Disposal Earth Atmospheric Reentry Option: Definition of the Reentry Debris Casualty Risk Technical Area: The use of atmospheric reentry to limit the orbital lifetime of space structures in conformance with Requirement 4.6-1 results in the transfer of an orbital environment risk to a potential human casualty risk. This section presents the requirement that defines the maximum human casualty risk permitted for either a controlled or uncontrolled reentry. An uncontrolled reentry is defined as the atmospheric reentry of a space structure in which the surviving debris impact cannot be guaranteed to avoid landmasses. Requirement area 4.7 applies to all space structures in Earth orbital area (Requirement 56623). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.7.2(2).a | 56626 | Requirements: Survival of Debris From the Postmission Disposal Earth Atmospheric Reentry Option: Requirements for the Area: Requirement 4.7-1. Limit the risk of human casualty: The potential for human casualty is assumed for any object with an impacting kinetic energy in excess of 15 joules: Requirements for the Area: For uncontrolled reentry, the risk of human casualty from surviving debris shall not exceed 0.0001 (1:10,000) (Requirement 56626). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.7.2(2)b | 56627 | Requirements: Survival of Debris From the Postmission Disposal Earth Atmospheric Reentry Option: Requirements for the Area: Requirement 4.7-1. Limit the risk of human casualty: The potential for human casualty is assumed for any object with an impacting kinetic energy in excess of 15 joules: For controlled reentry, the selected trajectory shall ensure that no surviving debris impact with a kinetic energy greater than 15 joules, is closer than 370 km from foreign landmasses, or is within 50 km from the continental U.S., territories of the U.S., and the permanent ice pack of Antarctica (Requirement 56627). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.7.2(2)c | 56628 | Requirements: Survival of Debris From the Postmission Disposal Earth Atmospheric Reentry Option: Requirements for the Area: Requirement 4.7-1. Limit the risk of human casualty: The potential for human casualty is assumed for any object with an impacting kinetic energy in excess of 15 joules: Requirements for the Area: For controlled reentries, the product of the probability of failure of the reentry burn (from Requirement 4.6-4.b) and the risk of human casualty assuming uncontrolled reentry shall not exceed 0.0001 (1:10,000) (Requirement 56628). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.7.4.d | 56639 | Requirements: Survival of Debris From the Postmission Disposal Earth Atmospheric Reentry Option: Methods to Assess Compliance: Due to the complexity of satellite reentry physics and material responses, NASA programs and projects shall employ either DAS or a higher fidelity model called ORSAT (Object Reentry Survival Analysis Tool) to determine compliance with Requirement 4.7-1 (Requirement 56639). The reentry risk assessment portion of DAS contains a simplified model which does not require expert knowledge in satellite reentry analyses. Due to the need to make some simplifications, the model is designed to be somewhat conservative. The degree of conservatism is actually a function of the vehicle and the materials under evaluation. | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.7.4.g | 56642 | Requirements: Survival of Debris From the Postmission Disposal Earth Atmospheric Reentry Option: Methods to Assess Compliance: In the DAS or ORSAT risk assessment, the assumptions used to model the reentry shall be documented in the ODAR and include the explanation of which items are assemblies and their sub assemblies and which items, resulting in >15J impacts have been included (Requirement 56642). | S | Y | Y | Safety | |||
| NASA STD 8719.14 | 4.8 | 56648 | Requirements: Additional Assessment Requirement for Tether Missions: Orbital debris analyses assess the potential hazard of tethered systems considering both an intact and severed system. Tethers are flexible long and narrow space structures with two of the dimensions much smaller than the third. The potential to damage operating spacecraft can be larger than would be expected solely from the tether mass and cross-sectional area. Requirement area 4.8 applies to all space structures with tethers in Earth and lunar orbits (Requirement 56648). | S | Y | Y | Safety | |||
| NPR 7120.5D | 4.4.2.b.5 | 55724 | Program and Project Requirements by Phase: Projects - Phase A: Requirements: During Phase A, the Project Manager and project team shall: Perform technical activities: Develop an initial orbital debris assessment in accordance with NASA Safety Standard 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris. (Requirement 55724) | E | N | N | Mgmt | |||
| NPR 7120.5D | 4.5.2.b.10 | 55768 | Program and Project Requirements by Phase: Projects - Phase B: Requirements: During Phase B, the Project Manager and the project team shall: Perform technical activities: Develop a preliminary orbital debris assessment in accordance with NASA Safety Standard 1740.14. (Requirement 55768) | E | N | N | Mgmt | |||
| NPR 7120.5D | 4.6.2.a.08 | 55803 | Program and Project Requirements by Phase: Projects - Phase C: Requirements: During Phase C, the Project Manager and the project team shall: Perform technical activities: Develop a baseline orbital debris assessment prior to the project CDR in accordance with NASA Safety and Standard 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris. (Requirement 55803) | E | N | N | Mgmt | |||
| NPR 8715.6A | 0.P.2.4.a | 57283 | Preface: APPLICABILITY: The following subparagraphs (a-d below) limit the scope of this NPR: NASA spacecraft, launch vehicles, and instruments that passed the Preliminary Design Review (PDR) prior to August 1995 (release of NSS 1740.14, Guidelines and Assessment Procedures for Limiting Orbital Debris) are not required to perform an ODA unless a large change in design, as determined by the SMA Technical Authority for Orbital Debris, or changes in space object capability or risk affect the ability to achieve compliance with the requirements. If one or more of these conditions occur, an ODA Report (ODAR) shall be performed (Requirement 57283) | S | Y | Y | Safety | |||
| NPR 8715.6A | 0.P.2.4.e | 57290 | Preface: APPLICABILITY: The following subparagraphs (a-d below) limit the scope of this NPR: All applicable programs not listed in paragraphs P.2.4.a through P.2.4.d shall use NASA-STD 8719.14 (Requirement 57290). | S | Y | Y | Safety | |||
| NPR 8715.6A | 1.3.13.1 | 56786 | General Information: Roles and Responsibilities: NASA Program/Project Manager: The NASA Program/Project Manager shall establish an orbital debris mitigation activity as a part of every spaceflight program/project as defined by paragraph P.2.2. (Requirement 56786) | S | Y | Y | Safety | |||
| NPR 8715.6A | 1.3.13.2 | 56787 | General Information: Roles and Responsibilities: NASA Program/Project Manager: The NASA Program/Project Manager shall provide copies of any plans describing generation of orbital debris to the SMA Technical Authority for Orbital Debris for review. (Requirement 56787) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.1 | 56793 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: The NASA Program/Project Manager shall implement orbital debris requirements for those portions of a spaceflight program/project over which NASA has control as defined by paragraph P.2.2. (Requirement 56793) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.2 | 56794 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: The NASA Program/Project Manager shall include the applicable design requirements stated in NSS 1740.14 in the program/project requirements unless a variance to the requirements has been granted per NPR 8715.3, paragraph 1.13. (Requirement 56794) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.3 | 56795 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: The NASA Program/Project Manager and the contracting officer for the program/project shall include requirements in this NPR in agreements and contracts necessary to ensure compliance with this NPR unless a variance to the requirements has been granted per NPR 8715.3, paragraph 1.13. (Requirement 56795) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.4 | 57300 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: When a spacecraft is jointly developed/built/managed by multiple NASA Centers/facilities using NASA-STD 8719.14, the Program/Project Manager at each NASA Center/facility shall deliver an abbreviated ODAR per NASA-STD 8719.14, Appendix A, Section A.3, as a part of the hardware delivery to the program/project integrator covering those spacecraft portions under their control (Requirement 57300). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.4.a | 57301 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: When a spacecraft is jointly developed/built/managed by multiple NASA Centers/facilities using NASA-STD 8719.14, the Program/Project Manager at each NASA Center/facility shall deliver an abbreviated ODAR per NASA-STD 8719.14, Appendix A, Section A.3, as a part of the hardware delivery to the program/project integrator covering those spacecraft portions under their control: When a spacecraft is jointly developed/built/managed by multiple NASA Centers/facilities using NSS 1740.14, the Program/Project Manager at each NASA Center/facility shall deliver either a full ODAR per NSS 1740.14, Chapter 8, or an abbreviated ODAR per NASA-STD 8719.14, Appendix A, Section A.3, as a part of the hardware delivery to the program/project integrator covering those spacecraft portions under their control (Requirement 57301). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.5 | 57302 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: When a spacecraft is jointly developed/built by multiple organizations where NASA is using NASA-STD 8719.14, and NASA is not the launching or lead Agency, the NASA Program/Project Manager shall provide an abbreviated ODAR to the non-NASA launching or lead Agency per NASA-STD 8719.14, Appendix A, Section A.3, as part of the delivery of the hardware data package covering only those spacecraft portions being developed/integrated by the NASA organization as permitted by International Traffic in Arms (ITAR) and other data restrictions (Requirement 57302). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.5.a(1) | 57303 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: When a spacecraft is jointly developed/built by multiple organizations where NASA is using NASA-STD 8719.14, and NASA is not the launching or lead Agency, the NASA Program/Project Manager shall provide an abbreviated ODAR to the non-NASA launching or lead Agency per NASA-STD 8719.14, Appendix A, Section A.3, as part of the delivery of the hardware data package covering only those spacecraft portions being developed/integrated by the NASA organization as permitted by International Traffic in Arms (ITAR) and other data restrictions: When a spacecraft is jointly developed/built by multiple organizations where NASA is using NSS 1740.14, and NASA is not the launching or lead Agency, the NASA Program/Project Manager shall provide either a full ODAR per NSS 1740.14 Chapter 8 or an abbreviated ODAR per NASA-STD 8719.14, Appendix A, Section A.3, to the non-NASA launching or lead Agency as a part of the delivery of the hardware data package covering only those spacecraft portions being developed/integrated by the NASA organization as permitted by International Traffic in Arms Regulations (ITAR) and other data restrictions (Requirement 57303). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.1.7 | 57306 | Program/Project Development and Prelaunch Preparations: Orbital Debris Program Setup and Control: The NASA Program/Project Manager shall include a review of the orbital debris requirements derived from this NPR and NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4, as a part of the program/project System Requirements Review (or equivalent early review) (Requirement 57306). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.1.01 | 57307 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: Orbital Debris Assessment Report (ODAR): The NASA Program/Project Managers shall assess the mission for compliance with this NPR and NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4, for generation of orbital debris during all mission phases (Requirement 57307). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.1.02 | 57308 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: Orbital Debris Assessment Report (ODAR): The NASA Program/Project Managers shall prepare and deliver the mission orbital debris assessments to the MDAA in an ODAR per the format and content defined in NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4, for all objects being launched as defined in paragraph P.2.2 (Requirement 57308). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.1.07 | 56810 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: Orbital Debris Assessment Report (ODAR): The Program/Project Manager shall submit the initial mission ODAR prior to the spacecraft PDR or equivalent NASA Program/Project or project milestone. (Requirement 56810) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.1.08 | 56811 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: Orbital Debris Assessment Report (ODAR): The Program/Project Manager shall submit the updated mission ODAR no later than 45 days prior to the spacecraft CDR or equivalent NASA program or project milestone. (Requirement 56811) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.1.09 | 56812 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: Orbital Debris Assessment Report (ODAR): The Program/Project Manager shall submit the final mission ODAR no later than 30 days prior to the opening of the launch window or 30 days prior to the NASA SMA readiness review described in NPR 8705.6, whichever comes first. (Requirement 56812) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.2.01 | 56815 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: End-of-Mission Plan (EOMP): Program/Project Managers shall assess the mission for compliance with this NPR and NSS 1740.14 for proper disposal of the spacecraft and the launch vehicle for the portion of the program/project funded, managed, or operated by NASA. (Requirement 56815) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.2.02 | 57309 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: End-of-Mission Plan (EOMP): Program/Project Managers shall prepare, update, and deliver an EOMP per the format and content defined in NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4, for the configuration of the space vehicles anticipated at EOM for all objects as defined in paragraph P.2.2 (Requirement 57309). | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.2.03 | 56817 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: End-of-Mission Plan (EOMP): The Program/Project Manager shall submit each draft EOMP to the Chief/OSMA, the AA/SOMD (for missions that could pose a risk to humans in space), and the cognizant MDAA for review. (Requirement 56817) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.2.08 | 56822 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: End-of-Mission Plan (EOMP): The Program/Project Manager shall submit the initial draft EOMP no later than 45 days prior to the spacecraft CDR or equivalent program or project milestone. (Requirement 56822) | S | Y | Y | Safety | |||
| NPR 8715.6A | 2.2.2.09 | 56823 | Program/Project Development and Prelaunch Preparations: Orbital Debris Risk Assessments: End-of-Mission Plan (EOMP): The Program/Project Manager shall submit the Prelaunch EOMP no later than 30 days prior to the opening of the launch window or 30 days prior to the SMA readiness review described in NPR 8705.6, whichever comes first. (Requirement 56823) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.1.1 | 56843 | Program/Project Operations: Design: The NASA Program/Project Manager shall ensure that all NASA and NASA-funded or NASA-controlled spacecraft and launch vehicles are designed to be disposed of in accordance with the remainder of this Chapter. (Requirement 56843) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.1.3(1) | 57314 | Program/Project Operations: Design: The NASA Program/Project Manager shall ensure that all spacecraft and launch vehicles placed in orbit about Earth or the Moon are designed to prevent/preclude, to the extent possible/feasibile, a self-initiated unintentional orbit breakup from launch through reentry (Requirement 57314). | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.01 | 56848 | Program/Project Operations: Monitoring During Spaceflight: The NASA Program/Project Manager shall monitor their spacecraft and launch vehicle stages, to the extent possible/feasible, to detect intended or unintended operations that generate orbital debris around Earth, the Moon, or Mars, or at an Earth-Sun Lagrange point. (Requirement 56848) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.02 | 56849 | Program/Project Operations: Monitoring During Spaceflight: If the NASA Program/Project Manager has determined that a spacecraft in orbit around Earth or the Moon has (or may have) generated intended or unintended orbital debris which is outside of the ODAR or EOMP analyses, then the following offices shall be notified within 48 hours of identifying the release by the identifying party: MDAA, OSMA, and NASA ODPO and SOMD for debris generated in LEO. (Requirement 56849) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.03(1) | 56850 | Program/Project Operations: Monitoring During Spaceflight: The NASA Program/Project Manager shall ensure that all generated orbital debris in Earth orbit (planned and unplanned) is analyzed by the program/project to determine if within 3-months the orbital debris may either pose a risk to another spacecraft in a similar or crossing orbit or will return to Earth. (Requirement 56850) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.05 | 56853 | Program/Project Operations: Monitoring During Spaceflight: The NASA Program/Project Manager shall, for orbits about the Earth or the Moon, monitor spacecraft and launch vehicle stage items defined as critical in the ODAR or EOMP which may lead to a breakup or loss of control function or any items which may affect the planned maneuvers, passivation, or disposal at EOM. (Requirement 56853) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.06 | 56854 | Program/Project Operations: Monitoring During Spaceflight: For orbits about the Earth or the Moon, when an event is detected that may affect the generation of orbital debris or implementation of the EOMP, the NASA Program/Project Manager shall ensure that appropriate measures are taken to limit further generation of orbital debris that may preculded intended passivation and disposal of the spacecraft and launch vehicle stages. (Requirement 56854) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.07 | 56855 | Program/Project Operations: Monitoring During Spaceflight: The Program/Project Manager shall notify the Program's MDAA, who in turn, shall notify the Chief/OSMA and the NASA Chief Engineer, and SOMD (for missions that could pose a risk to humans in space) for events in LEO, within 96 hours of identifying the event when any of the following conditions occur: (Requirement 56855) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.2.09 | 56861 | Program/Project Operations: Monitoring During Spaceflight: The NASA Program/Project Manager shall provide copies of all actions per NPD 8010.3, Notification of Intent to Decommission or Terminate Operating Space Systems and Terminate Missions, to the OSMA with EOMP updates. (Requirement 56861) | S | Y | Y | Mgmt | |||
| NPR 8715.6A | 3.2.10 | 56862 | Program/Project Operations: Monitoring During Spaceflight: The NASA Program/Project Manager shall inform the Department of Defense's Space Surveillance Network in the Cheyenne Mountain Operations Center prior to spacecraft and launch vehicle EOM maneuvers that result in a change of Earth orbit altitutde of greater than 1 km. (Requirement 56862) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.1 | 56865 | Program/Project Operations: EOM Actions: EOM Planning: The MDAA and the NASA Program/Project Manager shall periodically review and update the EOMP as a part of the Mission Directorate senior management review process. (Requirement 56865) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.2 | 56866 | Program/Project Operations: EOM Actions: EOM Planning: All spacecraft planned for reentry into Earth's atmosphere or remaining in orbit about the Earth or the Moon shall be passivated as part of the disposal. (Requirement 56866) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.3 | 56867 | Program/Project Operations: EOM Actions: EOM Planning: When significant capabilities affecting the spacecraft's planned ability to passivate, maneuver, or reenter at end-of-life change either through graceful degradation, malfunction, or via command, the EOMP shall be updated/annotated by the NASA Program/Project Manager. (Requirement 56867) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.5(1) | 57317 | Program/Project Operations: EOM Actions: EOM Planning: The following systems shall be analyzed when passivation is required (Requirement 57317). (for further information on passivation, see NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4): | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.5(1).a | 57318 | Program/Project Operations: EOM Actions: EOM Planning: The following systems shall be analyzed when passivation is required. (for further information on passivation, see NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4): Electrical Systems: Batteries and charging circuits. | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.5(1).b | 57319 | Program/Project Operations: EOM Actions: EOM Planning: The following systems shall be analyzed when passivation is required. (for further information on passivation, see NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4): Mechanical Pressure Systems: Propulsion, fluid loop, gas-pressurized batteries, and cryogenics. | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.5(1).c | 57320 | Program/Project Operations: EOM Actions: EOM Planning: The following systems shall be analyzed when passivation is required. (for further information on passivation, see NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4): Chemical Systems: Propulsion and solid motors. | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.1.5(1).d | 57321 | Program/Project Operations: EOM Actions: EOM Planning: The following systems shall be analyzed when passivation is required. (for further information on passivation, see NSS 1740.14 or NASA-STD 8719.14, as applicable per paragraph P.2.4): Mechanical Systems: Rotating machinery and springs. | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.2.1(1) | 56876 | Program/Project Operations: EOM Actions: EOM Requirements for Spacecraft and Launch Vehicles Planned for Reentry Into Earth's Atmosphere or Remaining in Orbit About the Earth or the Moon: Maneuverable spacecraft that are terminating their operationsal phases at altitudes of less than 2000 km above the Earth shall be maneuvered to reduce their orbital lifetime, commensurate with 25-year low Earth orbit lifetime limitations, or relocated, when feasible, if analysis shows the probability of collision with alrge objects exceeds criteria for objects in these highly utilized orbit regions. (Requirement 56876) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.2.3 | 56880 | Program/Project Operations: EOM Actions: EOM Requirements for Spacecraft and Launch Vehicles Planned for Reentry Into Earth's Atmosphere or Remaining in Orbit About the Earth or the Moon: All spacecraft and launch vehicles shall be passivated as a part of EOM disposal/decommissioning to a level where the remaining internal stored energy is insufficient to cause breakup. (Requirement 56880) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.2.4 | 56881 | Program/Project Operations: EOM Actions: EOM Requirements for Spacecraft and Launch Vehicles Planned for Reentry Into Earth's Atmosphere or Remaining in Orbit About the Earth or the Moon: The Program/Project Manager shall include evaluation of the long-term perturbations on, and the future trajectories of, orbital spacecraft and launch vehicle stages in the EOMP. (Requirement 56881) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.2.5 | 56882 | Program/Project Operations: EOM Actions: EOM Requirements for Spacecraft and Launch Vehicles Planned for Reentry Into Earth's Atmosphere or Remaining in Orbit About the Earth or the Moon: The NASA Program/Project Manager shall ensure that all spacecraft and launch vehicles designed to be operated in GEO are designed to be able to maneuver at least 300 km above GEO altitude (closest approach to GEO greater than 300 km above GEO altitude). (Requirement 56882) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.3.3.1 | 56884 | Program/Project Operations: EOM Actions: EOM Requirements While in Orbit About the Moon: The NASA Program/Project Manager shall not plan to leave objects in lunar orbit unless a documented need is stated in the ODAR. (Requirement 56884) | S | Y | Y | Mgmt | |||
| NPR 8715.6A | 3.3.3.2 | 56885 | Program/Project Operations: EOM Actions: EOM Requirements While in Orbit About the Moon: The NASA Program/Project Manager shall document the orbital parameters of all objects intended to be left in lunar orbit in the EOMP. (Requirement 56885) | S | Y | Y | Mgmt | |||
| NPR 8715.6A | 3.3.3.3 | 56886 | Program/Project Operations: EOM Actions: EOM Requirements While in Orbit About the Moon: For disposal of spacecraft left in lunar orbit, the NASA Program/Project Manager shall document consideration of a change to the orbital parameters of the spacecraft such that it is not in an orbit where it may interfere with another active spacecraft and include this analysis in the EOMP. (Requirement 56886) | S | Y | Y | Mgmt | |||
| NPR 8715.6A | 3.3.3.4 | 56887 | Program/Project Operations: EOM Actions: EOM Requirements While in Orbit About the Moon: The plan for disposal of a spacecraft on the lunar surface shall be concurred in by the Chief/OSMA. (Requirement 56887) | S | Y | Y | Mgmt | |||
| NPR 8715.6A | 3.3.3.5 | 56888 | Program/Project Operations: EOM Actions: EOM Requirements While in Orbit About the Moon: All spacecraft landing sites on the Moon, planned or anticipated after EOM, shall be chosen (or precluded) with due regard to the planned usage of those sites in future exploration or scientific study and the interests of other spacefaring nations, subject to NPR 8020.12. (Requirement 56888) | S | Y | Y | Mgmt | |||
| NPR 8715.6A | 3.4.1 | 56891 | Program/Project Operations: Conjunction Assessments during Mission Operations (for Earth Orbiting spacecraft): The NASA Program/Project Manager shall have conjunction assessment analyses performed routinely for all maneuverable Earth orbiting spacecraft with a perigee height of less than 2000 km in altitude or within 200 km of GEO. (Requirement 56891) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.4.2 | 56892 | Program/Project Operations: Conjunction Assessments during Mission Operations (for Earth Orbiting spacecraft): Conjunction assessment analyses shall be performed using the USSTRATCOM high accuracy catalog as a minimum. (Requirement 56892) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.4.3 | 56893 | Program/Project Operations: Conjunction Assessments during Mission Operations (for Earth Orbiting spacecraft): The NASA Program/Project Manager shall have a collision risk assessment and risk mitigation process in place for all maneuverable Earth orbiting spacecraft that are performing routine conjunction assessment analyses. (Requirement 56893) | S | Y | Y | Safety | |||
| NPR 8715.6A | 3.5.2 | 56896 | Program/Project Operations: Special Requirements for Spacecraft Carrying Humans: The Program/Project Manager shall notify the Chief/OSMA 48 hours in advance of a planned jettison of an object(s). (Requirement 56896) | S | Y | Y | Safety | |||
| NPR 8735.1A | 2.2.b | 24001 | GENERAL REQUIREMENTS: NASA shall: b.) Develop, document, and implement a process (or processes) for: (1) The identification, documentation, control and correction of problems and nonconforming items. (2) The exchange of significant problem and nonconforming item data among NASA activities and with GIDEP. (3) The evaluation and disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories. (Requirement 24001 - Part (3) only)) | S | Y | Y | Safety | |||
| NPR 8735.1A | 2.3.b | 24003 | Each NASA E/AA is responsible for maintaining continuous oversight of their Center's processing of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories. (Requirement 24003) | S | Y | Y | Safety | |||
| CxP 70059 | 2.5 | SAF-1033 | NPR 8715.3C | 03.05.1 | 46031 | Operational Safety: Pressure System Safety: Center Directors and Project Managers shall use NPD 8710.5, NASA Safety Policy for Pressure Vessels and Pressurized Systems, to protect personnel and property from hazards posed by pressure vessels and pressurized systems. Note: This document assigns responsibility for the various aspects of a NASA pressure vessel and pressurized systems program, references the codes, standards, guides, and Federal regulations that must be followed, and establishes unique NASA requirements. (Requirement 46031) | S | Y | Y | Safety |
| NPR 8715.3C | 03.14.7.2.b | 46219 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A facility environmental control system failure or failure in the distribution system affecting one pressure-suited occupant shall not affect any other pressure-suited occupant for test requiring crew participation in a pressure suit. (Requirement 46219) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.c | 46220 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: A means exists for immediately detecting an incipient fire or other hazardous condition in each crew compartment of any test area. (Requirement 46220) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.d | 46221 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Automatic fire detection is provided for critical areas not suitable for visual monitoring. (Requirement 46221) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.e | 46222 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed for timely and unencumbered rescue of incapacitated crew members. (Requirement 46222) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.f | 46223 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Software controlling crewed test systems are thoroughly analyzed to ensure that no command results in death or injury to the test subjects (Requirement 46223) Note: Policies and requirements for software are given in NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA Software Engineering Requirements. | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.g | 46224 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Crewed test systems are designed to provide for manual overrides of critical software commands to ensure the safety of test subjects during any system event or test scenario (normal operation, malfunction, emergency). (Requirement 46224) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.h | 46225 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Manual overrides of critical software commands support safe test termination and egress of test subjects. (Requirement 46225) | S | Y | Y | Safety | |||
| NPR 8715.3C | 03.14.7.2.i | 46226 | Operational Safety: Test Operations Safety: Human Research Subjects: Center Directors and project managers shall ensure that: Medical resources and facilities needed for response are alerted, on-call, and immediately available as needed. (Requirement 46226) | S | Y | Y | Safety | |||
| SAF-1045 | NASA STD 8719.10 | 0 | 46813 | NASA Standard 8719.10 is represented by this single entry. If this entry is being viewed from a filter, list, or traceability report, then the metadata applies to the document as a whole and the document should be reviewed at http://www.hq.nasa.gov/office/codeq/doctree/871910.htm | S | S | S | Safety | ||
| NASA STD 8719.11 | 0 | 46814 | NASA Standard 8719.11 is represented by this single entry. If this entry is being viewed from a filter, list, or traceability report, then the metadata applies to the document as a whole. | S | S | S | Safety | |||
| NASA STD 8719.17 | 0 | 46815 | NASA Standard 8719.17 is represented by this single entry. If this entry is being viewed from a filter, list, or traceability report, then the metadata applies to the document as a whole. | S | S | S | Safety | |||
| NASA STD 8719.7 | 0 | 46811 | NASA Standard 8719.7 is represented by this single entry. If this entry is being viewed from a filter, list, or traceability report, then the metadata applies to the document as a whole. | S | S | S | Safety | |||
| NASA STD 8719.9 | 1.3 | 40357 | Applicability: Compliance with this standard is mandatory for all NASA-owned and NASA contractor-supplied equipment used in support of NASA operations at NASA installations and NASA operations in host countries. The individual installation Lifting Devices and Equipment Manager (LDEM) and safety organizations are responsible for implementation and enforcement. This document establishes minimum requirements; NASA installations should assess their individual programs and develop additional requirements as needed. The need for compliance with this standard at contractor installations performing NASA work should be evaluated and made a contractual requirement where deemed necessary by the contracting officer and the responsible NASA installation/program safety office. Rented or leased LDE is exempt from this standard only by the decision of the contracting officer, the responsible NASA installation/program safety office, and the LDEM. If determined that rented or leased LDE will be used for a critical lift, this standard applies. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.3.2 | 40359 | Applicability: The design/hardware requirements contained in this document are applicable to new lifting devices/equipment purchased after 6 months from the issue date of this document. Existing equipment and that purchased during the first 6 months from issue of this document shall be reviewed for compliance with all design/hardware aspects of this standard within 12 months of its issue and the need to update such equipment shall be evaluated. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.3.3 | 40360 | Applicability: Deviations/waivers from the requirements of this document (including design/hardware requirements for both new and existing equipment) shall be approved as outlined in paragraph 1.7. The deviation/waiver documentation shall include any alternate or special criteria or procedures that will be imposed to ensure safe design and operations for those devices that do not meet the applicable requirements. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.3.4 | 40361 | Applicability: Portions of this standard refer to various national consensus codes/standards for equipment design/hardware requirements (e.g., ASME, CMAA, etc.). Lifting devices and equipment purchased after the initial review required in paragraph 1.3.2 shall comply with the specified codes/standards in effect at the time of manufacture. Each installation shall periodically review subsequent codes/standards and evaluate the need to update existing equipment. Based on an evaluation of NASA's overall safe lifting program and any significant changes in the consensus codes/standards, the NASA Safety and Risk Management Division with concurrence from the field installations shall decide when the next complete review (as described in paragraph 1.3.2) is warranted. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 1.4 | 40362 | Relation to Occupational and Safety Health Administration (OSHA) Requirements: This document is not a substitute for OSHA requirements. OSHA requirements apply to all NASA operations. This document meets or exceeds Federal OSHA requirements. Some States have their own OSHA programs that must comply with Federal OSHA and may be stricter. All NASA installations are responsible for keeping up to date with the Federal and State OSHA requirements that apply to their operations. This standard contains some OSHA requirements where deemed necessary to stress the importance of the requirement, clarify the requirement, document interpretaion of the requirement, and/or define NASA's program for meeting the requirement. The NASA Safety and Risk Management Division, with assistance from the field installations, shall monitor subsequent OSHA requirements for any impact on NASA's safe lifting program. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.5.1 | 40364 | Critical and Noncritical Lifting Operations: Critical lifts are lifts where failure/loss of control could result in loss of life, loss of or damage to flight hardware, or a lift involving special high dollar items, such as spacecraft, one-of-a-kind articles, or major facility components, whose loss would have serious programmatic or institutional impact. Critical lifts also include the lifting of personnel with a crane, lifts where personnel are required to work under a suspended load, and operations with special personnel and equipment safety concerns beyond normal lifting hazards. Personnel shall not be located under suspended or moving loads unless the operation adheres to the OSHA-approved NASA Alternate Standard for Suspended Load Operations (see Appendix A). Lifting of personnel with a crane shall be in accordance with 29 CFR 1926.550 (see Appendix C). | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.5.1.a | 40365 | Critical and Noncritical Lifting Operations: Each installation or program shall develop a process to identify critical lifting operations and lifting devices/equipment that must meet critical lift requirements. Input shall be gathered from facility, program, user, and assurance personnel. The results of the process shall be documented and approved, as a minimum, by the installation LDEM. (Requirement 40365) | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.5.1.b | 40366 | Critical and Noncritical Lifting Operations: It is NASA policy that the comprehensive safeguards outlined in this standard be provided for critical lifting operations. This includes special design features, maintenance, inspection, and test intervals for the lifting devices/equipment used to make critical lifts. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.5.1.c | 40367 | Critical and Noncritical Lifting Operations: Specific written procedures shall be prepared and followed for all critical lifts. (Requirement 40367) | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.5.1.d | 40368 | Critical and Noncritical Lifting Operations: During critical lifts there shall be one person present (NASA or contractor) that is designated as responsible for the safety of the operations. That person may be a safety professional, a supervisor, an engineer, or a task leader. (Requirement 40368) | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.5.3 | 40370 | Critical and Noncritical Lifting Operations: The requirements for critical and noncritical lifts outlined in this standard shall be followed unless a specific deviation/waiver is approved as outlined in paragraph 1.7. Different levels of risks associated shall be evaluated using the risk determination criteria in NPG 8715.3. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 1.6 | 40371 | Recordkeeping and Trend Analysis: A data collection system shall be established at each installation or location to support NASA-wide lifting device trend and data analysis. Data entered locally would typically be associated with type and manufacturer of the equipment, age, maintenance history, operational problems and their corrective actions, lifting mishaps, safety notices, inspection discrepancies, waivers, and proof and load test results. (Requirement 40371) | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.7.1 | 40373 | Safety Variances: If a mandatory requirement cannot be met, a safety variance shall be prepared in accordance with NPG 8715.3. (Requirement 40373) | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.7.2 | 40374 | Safety Variances: The NASA variance process does not apply to Federal and applicable State/local regulations (e.g., OSHA, Cal OSHA). Any variance of a Federal or State/local regulation must be approved by the appropriate Federal/State/local agency (e.g., NASA Alternate Safety Standard for Suspended Load Operations approved by OSHA). The NASA Safety and Risk Management Division shall review all proposed safety variances of Federal regulations before submittal for approval. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.7.3 | 40375 | Safety Variances: Example: A variance request to a requirement in this standard that uses the word shall would be routed through the Center Safety Director for concurrence and approved or denied by the Center Director. A copy would then be sent to the NASA Safety and Risk Management Division within 14 days along with detailed rationale for its approval and other documentation. | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.8.1 | 40377 | Lifting Devices and Equipment Committee: NASA LDE Committee. Each installation Director shall designate in writing at least one person and an alternate, with appropriate background in lifting devices, lifting operations, lifting equipment industry standards and an understanding of lifting safety, as the installation LDEM, to participate as a member of the NASA LDE Committee. The committee is chaired by the Director, Safety and Risk Management Division, or designee, and is responsible for reviewing proposed changes to this standard and addressing general LDE safety issues. The LDEM is responsible for overall management of the installation LDE program, coordinating with appropriate personnel at their installation on lifting issues and providing the NASA LDE Committee with their installation's position on LDE issues. (Requirement 40377) | S | S | S | Mgmt | |||
| NASA STD 8719.9 | 01.8.2 | 40378 | Lifting Devices and Equipment Committee: Installation LDE Committee. Each installation shall establish a LDE Committee, to ensure this standard is understood and applied across other organizations at the installation and to resolve any issues and provide a forum to exchange information. The Installation LDE Committee shall be chaired by the LDEM, with representation from all organizations at the installation that are responsible for and/or involved with LDE. (Requirement 40378) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.a | 4001 | The Chief Health and Medical Officer (CHMO) serves as the Chairperson of the NASA Health Council and is responsible for the overall NASA Occupational Health Program. (Requirement 4001) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.a.(1) | 4002 | The CHMO will ensure the following: Establishing and coordinating Agency Occupational Health policy. (Requirement 4002) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.a.(2) | 4003 | The CHMO will ensure the following: Approving occupational health standards, procedures, and guidelines. (Requirement 4003) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.a.(3) | 4004 | The CHMO will ensure the following: Advocating and supporting funding for the NASA Occupational Health Program. (Requirement 4004) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.a.(4) | 4005 | The CHMO will ensure the following: Appropriate communication and coordination on Agencywide occupational health issues with Headquarters functional offices. (Requirement 4005) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b | 4006 | The Director, Occupational Health Programs, is responsible for the oversight of the Occupational Health Program and for ensuring compliance with programmatic, statutory, and regulatory guidelines and policy implementation, including. (Requirement 4006) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(1) | 4007 | The Director, Occupational Health Programs, is responsible for the following: Providing program operations, policy implementation, and management. (Requirement 4007) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(2) | 4008 | The Director, Occupational Health Programs, is responsible for the following: Providing regular onsite review and assessment of Center Occupational Health operations to facilitate medical quality assurance and reporting the results of these reviews to the Director of Occupational Health programs and the NASA Health Council, as appropriate. (Requirement 4008) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(3) | 4009 | The Director, Occupational Health Programs, is responsible for the following: Coordinating and developing occupational health policy, procedures, guidelines, and health standards for approval. (Requirement 4009) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(4) | 4010 | The Director, Occupational Health Programs, is responsible for the following: Coordinating with the CHMO. (Requirement 4010) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(5) | 4011 | Reserved. | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(6) | 4012 | The Director, Occupational Health Programs, is responsible for the following: Coordinating Agencywide occupational health initiatives. (Requirement 4012) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(7) | 4013 | Reserved. | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(8) | 4014 | The Director, Occupational Health Programs, is responsible for the following: Coordinating all issues affecting worker safety with the appropriate Headquarters functional organization(s). (Requirement 4014) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.b.(9) | 4015 | Reserved. | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.d | 4021 | The Senior Environmental Health Officer, located at the Principal Center, functions as the Radiological Protection Officer, ensuring compliance with 10 CFR Part 20, 29 CFR 1910.97, and other Federal standards. (Requirement 4021) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.e | 4016 | E/AAs/Institutional Program Officers shall provide support for critical occupational health programs at the NASA Centers they oversee. (Requirement 4016) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.f | 4031 | NASA Center Directors and the Assistant Administrator for Institutional and Corporate Management have the responsibility to ensure that the NASA Occupational Health Program is effectively implemented and operated at their respective Center and Component Facilities. (Requirement 4031) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.g | 4017 | Other Officials-in-Charge of Headquarters Offices shall ensure that their organizations support the NASA Occupational Health Program. (Requirement 4017) | S | S | S | Mgmt | |||
| NPD 1800.2B | 5.h | 4018 | NASA supervisors shall support the constituent occupational health programs and facilitate employee participation to the maximum extent possible. (Requirement 4018) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.a | 4022 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: Achievement of NASA Occupational Health target indicators as indicated in NASA's Performance Plan. (Requirement 4022) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.b | 4023 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: Compliance with medical quality assurance standards. (Requirement 4023) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.c | 4024 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: The number of chronic occupationally related harmful employee exposures. (Requirement 4024) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.d | 4025 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: The number of emergency responses to accidental, acute exposure. (Requirement 4025) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.e | 4026 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: The number of hazard-control measures initiated. (Requirement 4026) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.f | 4027 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: Reduction in the number of occupational illness claims. (Requirement 4027) | S | S | S | Mgmt | |||
| NPD 1800.2B | 7.g | 4028 | MEASUREMENTS: Compliance with this policy and the overall success of this program shall be measured through the evaluation of the Agency's performance in the following areas: The number of life-threatening health risk factors (e.g., high blood pressure and high cholesterol) identified and controlled from voluntary Health Maintenance Examinations. (Requirement 4028) | S | S | S | Mgmt | |||
| NPD 8700.1C | 5.h | 1101 | RESPONSIBILITY: Supervisors and managers are responsible for educating their employees on the hazards of their job, establishing and promoting safe work practices, instilling in employees the importance of safety and mission success, and implementing safety and mission success regulations. (Requirement 1101) | S | S | S | Safety | |||
| NPD 8700.1C | 5.i | 1102 | RESPONSIBILITY: Employees are responsible for understanding the safety and mission-success requirements of their organization, performing their tasks in accordance with established safety procedures, and using prescribed personal protective equipment. (Requirement 1102) | S | S | S | Safety | |||
| NPD 8710.2D | 1.b | 8032 | It is NASA policy to -- Meet the most protective requriements in the event of conflicting standards or regulatory issuance until a resolution of the conflicts can be accomplished. (Requirement 8032) | S | S | S | Safety | |||
| NPD 8710.2D | 1.c | 8033 | It is NASA policy to -- Instill an awareness of the need for safety, health, and resource conservation in all NASA employees and require NASA contractors to emphasize safety, health, and resource conservation to their employees. (Requirement 8033) | S | S | S | Safety | |||
| NPD 8710.2D | 1.d | 8034 | It is NASA policy to -- Establish overall safety and health objectives to ensure employee safety, health, and resource conservation during all operations. (Requirement 8034) | S | S | S | Safety | |||
| NPD 8710.2D | 1.e | 8035 | It is NASA policy to -- Establish safety and health management performance indicators to measure progress toward meeting safety and health objectives. (Requirement 8035) | S | S | S | Safety | |||
| NPD 8710.2D | 1.f | 8036 | It is NASA policy to -- Periodically review and evaluate plans, systems, programs, facilities, equipment, processes, and activities to ensure that objectives will be achieved in a safe and healthful manner. (Requirement 8036) | S | S | S | Safety | |||
| NPD 8710.2D | 1.g | 8037 | It is NASA policy to -- Develop and maintain a management information system(s) for tracking and advancing goals of the safety and health programs. (Requirement 8037) | S | S | S | Safety | |||
| NPD 8710.2D | 1.h | 8038 | It is NASA policy to -- Ensure that all alleged hazardous conditions are investigated, all identified safety and health risks are properly assessed and controlled, and pertinent close-call and lessons-learned situations are promptly publicized to prevent reoccurrences. (Requirement 8038) | S | S | S | Safety | |||
| NPD 8710.2D | 1.i | 8039 | It is NASA policy to -- Encourage employees to report workplace hazards and to ensure that no employee is subject to restraint, interference, coercion, discrimination, or reprisal for exercising his/her rights to report unsafe or unhealthful conditions. (Requirement 8039) | S | S | S | Safety | |||
| NPD 8710.2D | 1.j | 8040 | It is NASA policy to -- Reinforce NASA's commitment to safety and health, and highlight details of the Agency's safety and health programs, by periodically preparing and distributing NASA safety and health information to all NASA facilities and locations. (Requirement 8040) | S | S | S | Safety | |||
| NPD 8710.2D | 1.k | 8041 | It is NASA policy to -- Establish space flight awareness motivation programs within NASA and the supporting NASA contractor/partner workforce for the purpose of instilling in employees the need to prevent human errors and mistakes that could impact the safety and mission success of human space flight activities. (Requirement 8041) | S | S | S | Safety | |||
| NPD 8710.2D | 5.c | 8004 | The Enterprise Associate Administrators, Institutional Program Officers, and the Director for Headquarters Operations are responsible for providing the necessary management oversight, resources, and emphasis to ensure and maintain proper safety and health programs within their institutions/programs. (Requirement 8004) | S | S | S | Safety | |||
| NPD 8710.2D | 5.d(1) | 8005 | The Director, NASA Safety and Assurance Requirements Division, is responsible for the following: Establishing, developing, and directing the overall NASA safety program and priorities. (Requirement 8005) | S | S | S | Safety | |||
| NPD 8710.2D | 5.d(2) | 8006 | The Director, NASA Safety and Assurance Requirements Division, is responsible for the following: Serving as the senior safety official for the Agency and exercising functional management authority over all NASA safety and risk management activities. (Requirement 8006) | S | S | S | Safety | |||
| NPD 8710.2D | 5.d(4) | 8008 | The Director, NASA Safety and Assurance Requirements Division, is responsible for the following: Reviewing and evaluating NASA activities for conformance with prescribed safety policies, standards, and procedures and recommending or pursuing necessary corrective action to obtain conformance when discrepancies are identified. (Requirement 8008) | S | S | S | Safety | |||
| NPD 8710.2D | 5.d(5) | 8009 | The Director, NASA Safety and Assurance Requirements Division, is responsible for the following: The Director, Safety and Assurance Requirements Division, is empowered, on behalf of the Associate Administrator for Safety and Mission Assurance, to terminate any operation that presents an immediate and unacceptable risk to personnel, property, or mission operations. When this occurs, immediate notification will be made to the affected Center and Institutional Program Office officials. | S | S | S | Safety | |||
| NPD 8710.2D | 5.d(7) | 8011 | The Director, NASA Safety and Assurance Requirements Division, is responsible for the following: Preparation and distribution of NASA Safety Program information. | S | S | S | Safety | |||
| NPD 8710.2D | 5.e(5) | 8017 | The CHMO is responsible for the following: The CHMO shall terminate any NASA operation considered an immediate health hazard. When this occurs, immediate notification will be made to the affected Center and Institutional Program Officer. | S | S | S | Safety | |||
| NPD 8710.2D | 5.f(1) | 8021 | Director, Headquarters Operations, and Center Directors are responsible for the following: Designating a senior manager as the Center safety and health official. (Requirement 8021) | S | S | S | Safety | |||
| NPD 8710.2D | 5.f(2) | 8022 | Director, Headquarters Operations, and Center Directors are responsible for the following: Developing, implementing, and maintaining an effective safety and health program consistent with NASA, State, and Federal requirements. (Requirement 8022) | S | S | S | Safety | |||
| NPD 8710.2D | 5.f(3) | 8023 | Director, Headquarters Operations, and Center Directors are responsible for the following: Utilizing the NASA Lessons Learned Information System for documenting, investigating, and applying safety lessons learned, as applicable, for all programs and projects. (Requirement 8023) | S | S | S | Safety | |||
| NPD 8720.1B | 5.e.(1) | 13042 | The Center SMA functional manager is responsible for: Ensuring that Reliability and Maintainability data is available for use as heritage data both to support current programs/projects at other Centers and to establish Reliability and Maintainability goals and requirements for follow-on or new programs/projects. (Requirement 13042) | S | S | S | RMS | |||
| NPR 1800.1B | 4.02.2.c.1 | 54570 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Establish and direct the exposure assessment program. (Requirement 54570) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.2 | 54571 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Assure key competencies. (Requirement 54571) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.3 | 54572 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Review assessment conducted by other staff. (Requirement 54572) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.4 | 54573 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Direct follow up effort. (Requirement 54573) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.5 | 54574 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Manage the regular monitoring program. (Requirement 54574) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.6 | 54575 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Develop a Management of Change system. (Requirement 54575) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.7 | 54576 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Use other knowledgeable personnel and additional experts when required. (Requirement 54576) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.8 | 54577 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Evaluate the background systems. (Requirement 54577) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.c.9 | 54578 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Environmental Health personnel shall perform the following: Identify personnel requiring surveillance. (Requirement 54578) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.d.1 | 54580 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Occupational Medicine personnel shall perform the following: Provide health surveillance screening to identify any workers or worker groups who may be at an elevated occupational health risk (Requirement 54580) | S | S | S | Safety | |||
| NPR 1800.1B | 4.02.2.d.2 | 54581 | Environmental Health: Occupational Exposure Assessment and Management: Responsibilities: NASA Center Occupational Medicine personnel shall perform the following: Work with other functions to assure such workers' exposures have been assessed and control measure decisions made and adopted, as necessary. (Requirement 54581) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.1 | 54741 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Facility sanitation. (Requirement 54741) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.2 | 54742 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Disease vector surveillance. (Requirement 54742) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.3 | 54743 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Potable water compliance monitoring. (Requirement 54743) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.4 | 54744 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Food service sanitation compliance inspections. (Requirement 54744) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.5 | 54745 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Monitoring of chemical toilets. (Requirement 54745) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.6 | 54746 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Launch/landing support. (Requirement 54746) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.a.7 | 54747 | Environmental Health: Environmental Sanitation: Process Description: The Sanitation Program activities shall be centered around formal design/operational document reviews and both periodic and special surveys. The focus of these activities shall be, but are not limited to the following: Zoogenic problems. (Requirement 54747) | S | S | S | Safety | |||
| NPR 1800.1B | 4.07.3.b | 54748 | Environmental Health: Environmental Sanitation: Process Description: NASA Centers shall maintain awareness of any developing local public health concern (e.g., West Nile fever from local birds, rodent-borne viruses.) and report any possible concerns to the OHP PCO. Flow Diagram: The flow diagram for this process is shown in Figure 4.7 at the end of this section | S | S | S | Safety | |||
| NPR 1800.1B | 4.08.3.b.5 | 54776 | Environmental Health: Balancing Work-Rest Cycles: Process Description: Definitions and Determinations: The calendar year, the week, and the calendar day (which changes at midnight) shall be used for worktime evaluation and maintenance of records. Accurate time records are mandatory in all work considerations. (Requirement 54776) | S | S | S | Safety | |||
| NPR 1800.1B | 4.08.3.c.4 | 54789 | Environmental Health: Balancing Work-Rest Cycles: Process Description: Worktimes: The following is based upon worktimes used at KSC and Langley Research Center (LaRC), and Commission recommendations for the Nuclear Regulatory Commission policy on shift scheduling and overtime at nuclear power plants: Overtime may be required because of a problem during operation or because of an extended work process. In either case, overtime shall not exceed the stated guidelines. Unusual circumstances may arise that require deviation from the guidelines. Such deviations shall be authorized by the first-level director. (This authorization must be documented and made available for NASA management inspection.) An extended work process shall not be considered unusual circumstances. (Requirement 54789) | S | S | S | Safety | |||
| NPR 1800.1B | 4.08.3.d | 54795 | Environmental Health: Balancing Work-Rest Cycles: Process Description: Variances: Management and unions work together to approve variances to stated guidelines, though advanced written approval is required. In unusual circumstances, a NASA review may be indicated. Managers, supervisors, and other specialists (e.g., Contracting Officer/Contract Technical Monitor, medical representative, Employee Assistance Program counselor, union representative) may participate in such reviews. The objective is to guard against arbitrary interpretation and possible excesses leading to maximum worktime violations. Any violations to maximal worktime requirements shall be reported immediately to the director of the primary organization. Resolution shall be sought at the lowest management level. Final arbitration lies with the Medical Policy Board. (Requirement 54795) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.b | 54829 | Environmental Health: Hearing Conservation: Introduction: The requirements of the latest revision of 29 CFR 1910.95, Occupational Noise Exposure Hearing Conservation Amendment Final Rule and appendices, and the requirements of the latest revision of 29 CFR 1904.10, Occupational Injury and Illness Recordkeeping and Reporting Requirements, for cases involving occupational hearing loss are incorporated herein by reference and shall be followed unless otherwise specified in this section. (Requirement 54829) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.c | 54830 | Environmental Health: Hearing Conservation: Introduction: Where conflicts exist between other NASA health and safety requirements, 29 CFR 1910.95, Occupational Noise Exposure Hearing Conservation Amendment Final Rule and appendices, 29 CFR Part 1904.10, Occupational Injury and Illness Recordkeeping and Rerporting Requirements, and this section, the most protective requirements shall apply. (Requirement 54830) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.d | 54831 | Environmental Health: Hearing Conservation: Introduction: Centers shall take steps to inform and protect all personnel from potential risks to their hearing that may be encountered in, or derived from, the workplace. (Requirement 54831) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.e | 54832 | Environmental Health: Hearing Conservation: Introduction: Centers shall have a written Hearing Conservation Program (HCP), which, at a minimum, addresses the requirements and provisions of this section and requires their contractors to have HCPs in accordance with the NASA FAR Supplement 1852.223-70, Safety and Health. (Requirement 54832) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.f | 54833 | Environmental Health: Hearing Conservation: Introduction: Occupational health personnel, trained in sound analysis, noise exposure assessment, hearing protection, audiometric testing, and noise abatement strategies, shall review their Center's HCP, including the hazardous noise training program, for adequacy at least every 3 years and more frequently if program requirements change. (Requirement 54833) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.g | 54834 | Environmental Health: Hearing Conservation: Introduction: Centers shall implement a "Buy Quiet and Quiet by Design" program and a system to effectively prioritize noise surveys and noise remediation efforts as part of their HCP and in accordance with the provisions of this section. (Requirement 54834) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.h | 54835 | Environmental Health: Hearing Conservation: Introduction: Communication and coordination between and among Center managers, supervisors, employees, engineers, environmental health personnel, and the Medical Director shall be implemented to properly identify, evaluate, and control hazardous noise and to prevent hearing loss caused by exposure to hazardous noise. (Requirement 54835) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.1.i | 54836 | Environmental Health: Hearing Conservation: Introduction: Center Directors and affected Program and Project Managers shall be notified of all operations and equipment not conforming to this section or the Center's HCP. (Requirement 54836) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.a | 54838 | Environmental Health: Hearing Conservation: Responsibilities: The Designated Agency Safety and Health Official (DASHO) shall provide resources for the development and review of the Agency's Hearing Conservation Policy and for implementation of the Office of the Chief Health and Medical Officer (OCHMO) responsibilities contained therein. (Requirement 54838) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.b | 54839 | Environmental Health: Hearing Conservation: Responsibilities: The Director, Agency Occupational Health Program, shall provide direction for, and approval of, the Agency's Hearing Conservation Policy. (Requirement 54839) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.c.1 | 54841 | Environmental Health: Hearing Conservation: Responsibilities: The Senior Environmental Officer shall: Make recommendations and provide advice concerning hearing conservation to the Director, Agency Occupational Health Program, and the DASHO, when requested. (Requirement 54841) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.c.2 | 54842 | Environmental Health: Hearing Conservation: Responsibilities: The Senior Environmental Officer shall: Biannually review the adequacy of HCPs at each Center. (Requirement 54842) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.d | 54843 | Environmental Health: Hearing Conservation: Responsibilities: The Chief Engineer and the Assistant Administrator for Infrastructure and Administration shall ensure that "Buy Quiet and Quiet by Design" provisions are integral to the site selection and design of new or modified facilities and equipment. (Requirement 54843) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.e | 54844 | Environmental Health: Hearing Conservation: Responsibilities: The Assistant Administrator for Procurement shall ensure that "Buy Quiet and Quiet by Design" provisions are included in all contracts and in the purchase of new equipment, as appropriate. (Requirement 54844) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.f.1 | 54846 | Environmental Health: Hearing Conservation: Responsibilities: Center Directors, Component Facility Directors, and the Assistant Administrator for Infrastructure and Administration shall ensure the following: Adequate resources are provided to implement Center HCPs. (Requirement 54846) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.f.2 | 54847 | Environmental Health: Hearing Conservation: Responsibilities: Center Directors, Component Facility Directors, and the Assistant Administrator for Infrastructure and Administration shall ensure the following: Approved HCPs are implemented at their Centers. (Requirement 54847) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.g | 54848 | Environmental Health: Hearing Conservation: Responsibilities: Facility Managers, design engineers, occupational health personnel, and employers of affected employees shall implement the provisions of their Center's HCP. (Requirement 54848) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.2.h | 54849 | Environmental Health: Hearing Conservation: Responsibilities: Contracting Officers shall ensure that Center contract requirments incl , ude provisio , ns for writt , en HCPs in a , ccordance wi , th the NASA, FAR Supplement 1852.223-70, Safety and Health. (Requirement 54849) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.1 | 54890 | Environmental Health: Hearing Conservation: Process Description: Written HCP: All Centers shall develop and maintain a written HCP to implement the requirements of this section. (Requirement 54890) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0i | 54892 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Specifying the individual responsibilities for Facilities Managers, Design Engineers, Occupational Health Personnel, Supervisors, and Employees. (Requirement 54892) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0ii | 54893 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Assuring the noisy areas are surveyed to determine if they are hazardous noise areas. (Requirement 54893) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0iii | 54894 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Affirming the criterion sound level and exchange rate. (Requirement 54894) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0iv | 54895 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Evaluating and maintaining the HCP's effectiveness. (Requirement 54895) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0v | 54896 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Implementing "Buy Quiet and Quiet by Design" Programs. (Requirement 54896) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0vi | 54897 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Exposure monitoring. (Requirement 54897) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0vii | 54898 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Medical surveillance (audiometric monitoring). (Requirement 54898) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.0viii | 54899 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Notification and coordination between employees, management and occupational health personnel of noise exposure and dosimetry monitoring and survey results, operational and design plan review results, the addition of new equipment or new operations, and any work-related STS. (Requirement 54899) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.ix | 54900 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Audiometric testing, review, and medical follow-up. (Requirement 54900) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.x | 54901 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Selection, use, cleaning, and inspection of hearing protectors. (Requirement 54901) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xi | 54902 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Training and certification for employees and supervisors exposed at or above the action level. (Requirement 54902) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xii | 54903 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Certification of occupational hearing conservationists. (Requirement 54903) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xiii | 54904 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Recordkeeping and access to infromation. (Requirement 54904) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xiv | 54905 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Policy documentation. (Requirement 54905) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xv | 54906 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Noise control requirements and strategies. (Requirement 54906) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xvi | 54907 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Effective implementation of engineering, operational, and administrative controls. (Requirement 54907) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.b.2.xvii | 54908 | Environmental Health: Hearing Conservation: Process Description: Written HCP: At a minimum, the HCPs shall include provisions for: Appropriate corrective actions for employees who violate requirements of this section, the Center's HCP requirements, or 29 CFR 1910.95, "Occupational Noise Exposure Hearing Conservation Amendment Final Rule," and appendices. (Requirement 54908) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.c | 54909 | Environmental Health: Hearing Conservation: Process Description: HCP Participation: Whenever an employee is occupationally exposed to noise equal to or exceeding the action level (an 8-hour time-weighted average sound level [TWA] of 82 decibels measured on the A scale [slow response] or, equivalently, a dose of 50 percent for 30 days or more per year), the Center or Facility shall administer a continuing, effective hearing conservation program in conformance with the requirements of this section and the affected employees included in the program. Exposures shall be computed without regard to any attenuation provided by the use of personal protective equipment. (Requirement 54909) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.d.1 | 54911 | Environmental Health: Hearing Conservation: Process Description: Noise Exposure Limits: NASA's allowable noise exposure limit is the equivalent to an 85 dBA, 8-hour TWA exposure using a 3 dB exchange rate. Table 1 contains noise exposure levels and durations that are equivalent to this limit as calculated by the following formula where L stands for exposure level and T for duration: T (min) = 480/2 (L-85)/3 Exposures exceeding equivalent exposures in Table 1 shall be controlled, reduced, or eliminated through a hierarchical combination of engineering controls, administrative controls, and hearing protection devices. (Requirement 54911) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.d.2 | 54912 | Environmental Health: Hearing Conservation: Process Description: Noise Exposure Limits: Noise dose shall include all impact/impulse noise measured up to and including 140 dB peak. (Requirement 54912) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.d.4 | 54914 | Environmental Health: Hearing Conservation: Process Description: Noise Exposure Limits: All personnel who enter designated areas or who perform tasks where exposure to noise is greater than or equal to 82 dBA regardless of the duration of exposure shall be provided with personal hearing protection. All personnel who enter designated areas or who perform tasks where exposure to noise is greater than or equal 85 dBA or 140 dB peak, regardless of the duration of exposure or number of impulses, shall be provided with and shall be required to wear personal hearing protection. (Requirement 54914) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.i | 54916 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Meet realistic and achievable baseline noise criteria and optimize noise emission criteria based on individual and specific operational and site conditions. (Requirement 54916) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.ii | 54917 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Encompass design and development, or selection and purchase, of a broad variety of fixed and portable equipment purchased for use by Centers, including equipment purchased by contractors, to minimize noise-exposure hazards to personnel. (Requirement 54917) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.iii | 54918 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Encompass equipment expected to produce noise which is approaching hearing conservation levels of 80 dBA and higher under a variety of site and operational considerations. (Requirement 54918) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.iv | 54919 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Identify noise emission and control requirements for equipment procurement specifications and design. (Requirement 54919) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.v | 54920 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Contain provisions for "Buy Quiet and Quiet By Design" program support, promotion, training, and management sponsorship. (Requirement 54920) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.vi | 54921 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Be individualized to meet the Center's specific needs, configuration, and other relevant factors. (Requirement 54921) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.e.vii | 54922 | Environmental Health: Hearing Conservation: Process Description: "Buy Quiet and Quiet by Design" Programs shall: Not apply to specialized research project items or flight hardware, which may be expected to produce large amounts of noise. (Requirement 54922) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.f.1 | 54924 | Environmental Health: Hearing Conservation: Process Description: Engineering Controls: Engineering controls shall be the first and primary means of controlling hazardous noise. The feasibility and cost of engineering controls may be considered when making decisions about these controls. (Requirement 54924) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.f.3 | 54926 | Environmental Health: Hearing Conservation: Process Description: Engineering Controls: Facility plans shall be reviewed to assess the adequacy of precautions that are planned and/or undertaken to control noise exposures. (Requirement 54926) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.f.4 | 54927 | Environmental Health: Hearing Conservation: Process Description: Engineering Controls: Engineering projects, drawings, and operational plans, including noise control measures, shall be coordinated with affected management organizations and occupational health personnel in the early stages of the design and/or planning process and prior to contract award and/or authority to proceed. (Requirement 54927) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.f.5.i | 54929 | Environmental Health: Hearing Conservation: Process Description: Engineering Controls: Organizations responsible for introducing changes to facilities, operations, or procedures shall notify occupational health personnel of: Any changes in operations or equipment that increase noise levels. (Requirement 54929) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.f.5.ii | 54930 | Environmental Health: Hearing Conservation: Process Description: Engineering Controls: Organizations responsible for introducing changes to facilities, operations, or procedures shall notify occupational health personnel of: Any new, uncontrolled, or previously unidentified areas, operations, or equipment that may produce hazardous noise or may not comply with the requirements of this section. (Requirement 54930) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.g.1 | 54932 | Environmental Health: Hearing Conservation: Process Description: Administrative Controls: If engineering controls fail to reduce sound levels within the requirements specified in this section, administrative controls shall be utilized. Examples of administrative controls include access restrictions and time limitations in the hazardous noise levels. (Requirement 54932) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.g.2 | 54933 | Environmental Health: Hearing Conservation: Process Description: Administrative Controls: The distance between the employee and the hazardous noise source shall be maximized to the extent practical. (Requirement 54933) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.g.3.i | 54935 | Environmental Health: Hearing Conservation: Process Description: Administrative Controls: Hazardous Noise Area Identification shall be implemented as follows: Areas determined to be hazardous noise areas shall be identified by posting with signs that conform to 29 CFR 1910.145 - Specifications for accident prevention signs and tags requirements. (Requirement 54935) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.g.3.ii | 54936 | Environmental Health: Hearing Conservation: Process Description: Administrative Controls: Hazardous Noise Area Identification shall be implemented as follows: Signs shall clearly indicate the presence of hazardous noise and state the requirements to wearing hearing protection. The signs shall be posted at the entrance(s) to or the periphery of hazardous noise area(s). (Requirement 54936) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.g.3.iii | 54937 | Environmental Health: Hearing Conservation: Process Description: Administrative Controls: Hazardous Noise Area Identification shall be implemented as follows: Decals or placards with similar statements shall be affixed to power tools and machines that produce hazardous noise levels, and cautions signs shall be posted in areas where hazardous noise-producing tools and machines are used. (Requirement 54937) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.1 | 54939 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): If both engineering and administrative controls fail to reduce sound levels to 85 dBA TWA or below, p ersonal hearing protection shall be used to bring exposure levels to acceptable levels. (Requirement 54939) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.2 | 54940 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): HPDs shall be made available for use in sound levels at or above 82 dBA. HPDs shall be worn by employees when they are exposed to noise levels in excess of 85 dBA, independent of duration of exposure. (Requirement 54940) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.3 | 54941 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): Earplugs shall be for the exclusive use of each employee and shall not be traded or shared. (Requirement 54941) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.4 | 54942 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): HPDs shall attenuate employee noise exposure to an 8-hour TWA of 85 dBA or less. For those with STS, HPDs shall attenuate exposure to an 8-hour TWA of the 82 dBA or less. (Requirement 54942) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.5 | 54943 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): The following derating criteria shall apply for all types of HPDs, where "NRR" is the manufacturer's Noise Reduction Rating: Required NRR = [(LA - 85) x 2] + 7, where LA is the measured ambient sound level to which the employee is exposed. (Requirement 54943) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.6 | 54944 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): The adequacy of HPD attenuation shall be reevaluated whenever employee noise exposures increase. (Requirement 54944) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.7 | 54945 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): Special hearing-protective equipment, such as sound-suppression or noise-cancellation communicated headsets, shall be regularly inspected if they are used in hazardous noise areas. (Requirement 54945) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.8 | 54946 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): Sound- suppression and noise-cancellation headsets that have been damaged, altered, or modified in any way that affect the attenuation characteristics shall not be used. (Requirement 54946) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.h.9 | 54947 | Environmental Health: Hearing Conservation: Process Description: Personal Hearing Protection Devices (HPDs): Where sound-suppression and noise-cancellation headsets are not permanently issued to individuals, such equipment shall be cleaned and sanitized before re-issuance. (Requirement 54947) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.01 | 54949 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Noisy areas shall be surveyed to determine if they are hazardous noise areas. (Requirement 54949) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.02 | 54950 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Measurement of potentially hazardous sound levels shall be conducted when any information, observation, or calculation indicates that an employee may be exposed to noise at or above the action level. This includes, but it not limited to, times where there is a need to document representative noise, exposures, where employees complain of excessive noise, or where it is difficult to understand a normal conversation when the speaker and listener face each other at a distance of 3 feet. (Requirement 54950) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.03 | 54951 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: In determining TWA exposures, all continuous, intermittent, and impulsive sound levels, from 80 dBA to 140 dBA, shall be integrated into the noise measurements. (Requirement 54951) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.04 | 54952 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Octave band analysis shall be conducted, when required, to establish the characteristics of the noise source and to help determine appropriate abatement techniques. (Requirement 54952) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.05 | 54953 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: When a noise survey is performed, it shall determine the presence of compounding hearing-related circumstances present in the environment (e.g., certain solvents, heavy metals, carbon monoxide, heat, and vibration) to ensure proper mitigation. (Requirement 54953) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.06 | 54954 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Noise surveys shall also be conducted whenever any changes to facilities, equipment, work practices, procedures, or noise-control measures alter potential noise-exposures. A review of hazardous noise sources and controls, employee exposures, and work practices and procedures shall be conducted for changing conditions whenever an employee experiences an STS. (Requirement 54954) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.07 | 54955 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: When a noise survey shows that any employee or group of employees may be exposed to noise at or above 82 dBA 8-hr TWA, noise dosimetry monitoring will be conducted to determine the noise dose of the exposed employee and the representative exposure of similarly exposed employees and to determine appropriate noise abatement techniques. (Requirement 54955) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.08 | 54956 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: All noise surveys and personal noise dosimetry monitoring conducted shall be consistent with 29 CFR 1910.95 requirements, unless otherwise specified in this section. (Requirement 54956) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.09 | 54957 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Operational plans shall be reviewed to assess the adequacy of precautions that are planned and/or implemented to control noise exposures. (Requirement 54957) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.10 | 54958 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Baseline surveys of each new or changed operation, job, or procedure, having the potential of creating hazardous noise, shall be conducted. (Requirement 54958) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.11 | 54959 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: New equipment, operations, jobs, or procedures, with the potential for creating hazardous noise, shall be evaluated with regard to noise emissions prior to operational start-up. (Requirement 54959) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.12 | 54960 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Employees and/or their representatives shall be provided an opportunity to observe noise dosimetry and area monitoring activites. (Requirement 54960) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.13 | 54961 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Affected employees shall be notified in writing of the results of noise dosimetry monitoring. (Requirement 54961) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.14 | 54962 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Employers of affected employees and the appropriate occupational health program managers shall be notified when noise measurement data indicate that noise exposures equal or exceed the limitations of Table 1 and the action level. Written reports of the hazardous noise surveys that identify all survey observations, findings, and conclusions shall also be provided to affected employees. (Requirement 54962) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.i.15 | 54963 | Environmental Health: Hearing Conservation: Process Description: Exposure Monitoring: Randomly selected hazardous noise areas shall be surveyed and documented each year to assure program effectiveness. (Requirement 54963) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.j.1 | 54965 | Environmental Health: Hearing Conservation: Process Description: Sound-Measuring Equipment: An instrument used to measure workers' noise exposure shall be field-calibrated prior to each use and shall be checked periodically, at least annually, by its manufacturer, a representative of its manufacturer, or an approved laboratory. (Requirement 54965) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.j.2 | 54966 | Environmental Health: Hearing Conservation: Process Description: Sound-Measuring Equipment: Sound-level meters used to measure workers' noise exposures shall be set at "slow" response and A-weighting. (Requirement 54966) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.k.1 | 54968 | Environmental Health: Hearing Conservation: Process Description: Audiometric Test Equipment: Audiometric test equipment shall be calibrated to meet requirements specified in the latest revision of ANSI S3.6, Specification for Audiometers. (Requirement 54968) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.k.2 | 54969 | Environmental Health: Hearing Conservation: Process Description: Audiometric Test Equipment: Ambient noise levels in audiometric test rooms and booths shall meet the specifications in the latest version of ANSI S3.1, Maximum Permissible Ambient Noise Levels for Audiometric Test Rooms. (Requirement 54969) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0i | 54972 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: Employees enrolled in an HCP shall receive medical surveillance as part of the HCP. (Requirement 54972) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0ii | 54973 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: Employees receiving medical surveillance shall undergo a baseline audiometric examination before beginning work assignments in hazardous noise areas. If it is not possible to obtain the baseline prior to noise assignment, then employees shall undergo a baseline audiometric examination within 30 days of initial exposure to hazardous noise. During this 30-day period, employees shall wear personal HPDs, which reduce their exposure to 82 dBA TWA or below. When it is discovered that personnel have already been assigned to a position that may expose them to hazardous noise but have not yet had an audiometric examination, audiometry shall be conducted within 30 days of discovery, and employees shall wear personal hearing protection that reduces their exposure to 82 dBA TWA or below. (Requirement 54973) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0iii | 54974 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: Audiometric examinations shall include an audiogram, an otoscopic examination by an audiologist, physician, or Council on Accreditation for Occupational Hearing Conservation (CAOHC)-certified occupational hearing conservationist, unless otherwise appropriately trained, to determine any existing medical pathology of the ear, and an update to their medical history (occupational and personal) to document past noise exposure and other otopathological factors. (Requirement 54974) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0iv | 54975 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: The employee shall have no apparent or suspected ear, nose, or throat problems that might compromise the validity of the audiogram. When an employee has an acute disease that may compromise the validity of the test, the audiogram shall be delayed until the condition has abated. (Requirement 54975) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0v | 54976 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: At the time ,of the audiometric examination, exposure history shall be collected to include ototoxic medications and exposure, to ototoxic substances. (Requirement 54976) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0vi | 54977 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: If during a medical evaluation the employee is identified as potentially unable to perform the job safely, the employee and employer shall receive a written notification of the requirement to perform an Ability and Risk Evaluation. The written notification shall include the results of the medical and work history with special emphasis on the association of any health conditions that may impair ability to safely perform the work expected in the position held (hear commands or signals) or the ability to wear appropriate personal hearing protection equipment in a hazardous noise area. (Requirement 54977) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0vii | 54978 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: Personnel suffering from an acute disease of the ear shall not be placed in hazardous noise areas until the condition has abated, particularly if such diseases preclude the wearing of hearing protectors. (Requirement 54978) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.0viii | 54979 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: Centers shall take all possible measures to assure that employees who have participated in the HCP medical surveillance program receive a final audiometric examination prior to termination of employment, transfer to duties not involving noise exposures, transfer to another installation, or retirement. An annual audiogram, if completed within 6 months of the termination, transfer, or retirement date, may be substituted for the final audiogram. (Requirement 54979) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.1.ix | 54980 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric Examination: When employees at a Center retain their "work role position" but change employers due to contract award to new employer, all medical records applicable to hearing conservation shall follow them to their new employer, including their current baseline threshold. (Requirement 54980) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.i | 54982 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: Audiometric testing shall be performed upon initial assignment, and annually thereafter, in accordance with 29 CFR 1910.95 Sections (g) and (h). (Requirement 54982) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.ii | 54983 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: Audiometric testing shall be performed by, or overseen by, an audiologist or a physician knowledgeable in hearing conservation. (Requirement 54983) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.iii | 54984 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: Personnel who conduct audiometric testing shall be familiar with the provisions of this section, and shall be certified by the CAOHC, or be an audiologist. (Requirement 54984) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.iv | 54985 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: All baseline audiograms shall be preceded by a period of at least 14 hours during which there is no known exposure to noise above 82 dBA TWA, on or off the job. Hearing protectors that lower workplace noise to the equivalent of 82 dBA TWA, using the appropriate noise-reduction rating, may be used as a substitute for the requirement that baseline audiograms be preceded by 14 hours without exposure to workplace noise. (Requirement 54985) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.v | 54986 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: If the answer to ALL of the questions below is "yes," the STS shall be logged as an OSHA-recordable event in accordance with 29 CFR 1904.10: (Requirement 54986) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.v.a | 54987 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: If the answer to ALL of the questions below is "yes," the STS shall be logged as an OSHA-recordable event in accordance with 29 CFR 1904.10: Did an annual age-corrected audiogram reveal STS (10 dB shift or greater, averaging 2k, 3k, and 4k, Hz) relative to the baseline audiogram in one or both ears? (Age correction permitted.) (Requirement 54987) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.v.b | 54988 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: If the answer to ALL of the questions below is "yes," the STS shall be logged as an OSHA-recordable event in accordance with 29 CFR 1904.10: Is the employee's uncorrected hearing level (averaging 2k, 3k, and 4k Hz) 25 dB or greater above audiometric zero in the same ear as the STS? (Age correction NOT permitted.) (Requirement 54988) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.v.c | 54989 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: If the answer to ALL of the questions below is "yes," the STS shall be logged as an OSHA-recordable event in accordance with 29 CFR 1904.10: is the hearing work related in the opinion of the medical and supervisory personnel? (Requirement 54989) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.2.vi | 54990 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Audiometric testing: if during a baseline audiogram the employee has a hearing profile equal to or worse than that listed in Table 2 below, the employee and employer shall receive a written notification of the requirement to perform an Ability and Risk Evaluation. The written notification shall include results of the medical and work history with special emphasis on the association of any health conditions that may impair ability to safely perform the work expected in the position held (hear commands or signals) or the ability to wear appropriate personal hearing protection equipment in a hazardous noise area. (Requirement 54990) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0ii | 54993 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Each employee's annual audiogram shall be compared to his/her baseline audiogram to determine if the audiogram is valid and to determine if an STS has occurred. (Requirement 54993) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0iii | 54994 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: The baseline of each ear shall be separately tracked. (Requirement 54994) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0iv | 54995 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: A physician, audiologist, or CAOHC-certified occupational hearing conservationist shall perform the hearing test and the comparison. (Requirement 54995) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0v | 54996 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: If an STS is identified and a confirmation audiogram is not performed within 30 days, the STS shall become a confirmed STS by default. (Requirement 54996) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0vi | 54997 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: If the identified STS is followed by a confirmation audiogram and the confirmation audiogram does not confirm the STS, this second audiogram reaplces the first one that suggested the STS. (Requirement 54997) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0vii | 54998 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: If the identified STS is followed by a positive confirmation audiogram, the better of the two shall become the confirmed STS. (Requirement 54998) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.0viii | 54999 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: A physician or audiologist with hearing conservation experience shall review problem audiograms, including those showing an STS (either by confirmation with 30 days or by default) and shall determine whether there is a need for further evaluation. During the confirmation audiogram, the employee shall be examined by a physician, audiologist, or CAOHC-certified occupational health nurse for proper HPD fit. (Requirement 54999) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.ix | 55000 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: When further evaluation is warranted, the employee shall be referred to an otolaryngologist or other qualified physician, or to an audiologist for further medical evaluation. See Section 4.9.3.1.(4), Referrals. (Requirement 55000) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.x | 55001 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: A new baseline reference audiogram shall replace the original or previous baseline audiogram (in separate ears and not both ears, unless both ears meet criteria listed below) when: (Requirement 55001) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.x.a | 55002 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: A new baseline reference audiogram shall replace the original or previous baseline audiogram (in separate ears and not both ears, unless both ears meet criteria listed below) when: The reviewing CAOHC-certified hearing conservationist determines that an STS is persistent on a retest (conducted no sooner than 6 months later). Unless an audiologist or physician determines and documents reasons for not revising the baseline, the baseline shall be revised to the lower (more sensitive) value for the average. Employees assigned a new baseline audiogram, as a result of an STS, shall receive an audiometric re-evaluation 6 months after this assignment to determine if a further STS has occurred. (Requirement 55002) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.x.b | 55003 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: A new baseline reference audiogram shall replace the original or previous baseline audiogram (in separate ears and not both ears, unless both ears meet criteria listed below) when: A "significant improvement" is shown if the average of thresholds at 2000, 3000, and 4000 Hz for either ear shows an improvement of 5 dB or more from the baseline and the improvement is persistent in the next test. The baseline shall be revised to the lower (more sensitive) value for the average unless a physician or audiologist determines and documents reasons for not revising. Age corrections shall not be used when determining "improvement." (Requirement 55003) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xi | 55004 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: The employee, employer, and environmental health staff shall be notified of an STS in writing within 21 days of the determination of the STS. (Requirement 55004) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xii | 55005 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Based on the best available information, the employer of an employee with an STS shall determine, in coordination with the physician or physician representative and the employer's health and safety representative, if the noise-induced STS is the result of occupational noise exposure. (Requirement 55005) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii | 55006 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: (Requirement 55006) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.a | 55007 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: The employee shall be examined by a physician or an audiologist for proper HPD fit. (Requirement 55007) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.b | 55008 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: HPDs shall be reevaluated for effectiveness and the employee shall be refitted as necessary with HPDs offering a greater sound attenuation. (Requirement 55008) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.c | 55009 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: The work environment(s) shall be investigated to determine if work practices or changes in equipment or procedures have increased the noise hazard and abatement actions shall be instituted, as necessary. (Requirement 55009) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.d | 55010 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: The work-related hearing loss shall be reported to the Center's mishap reporting system. (Requirement 55010) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.e | 55011 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: The employee shall be trained or retrained on the hazardous effects of noise and the need to use hearing protection. (Requirement 55011) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.f | 55012 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: Engineering controls shall be employed to reduce the potential for exposure to action level. (Requirement 55012) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.g | 55013 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: Administrative and work practices shall be reevaluated for effectiveness. (Requirement 55013) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.h | 55014 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: The employee shall be rechecked or refitted with hearing protectors, offering greater sound attenuation, if needed. (Requirement 55014) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiii.i | 55015 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where it has been determined that an employee has experienced an STS as a result of an occupational noise exposure: The employee's management and responsible safety and health office will be notified of the occurance of an STS or other work-related hearing loss. (Requirement 55015) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xiv | 55016 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: When an OSHA-recordable STS has occurred, the employer shall record the condition as a hearing loss on the OSHA 300 Log and maintain the record in accordance with 29 CFR 1904, Recording and Reporting Occupational Injuries and Illnesses. (Requirement 55016) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xv | 55017 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: The Medical Director shall determine if reassignment to work in a low noise area is indicated to prevent further hearing impairment and shall advise the employer accordingly. (Requirement 55017) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xvi | 55018 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: The employer shall have ultimate authority and responsibility for employee reassignment. (Requirement 55018) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.3.xvii | 55019 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Theshold Shifts: Where the same employee experiences any subsequent work-related STS as a result of occupational noise exposure, the work environment(s) shall be reevaluated. If the employee continues to work in the hazardous noise area(s), engineering and/or administrative controls shall be employed that reduce that employee's noise exposure to no more than 50 percent of what was previously allowed for that employee. (Requirement 55019) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.i | 55021 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: Employees shall be referred to an otolaryngologist or other physician knowledgeable in hearing conservation or to an audiologist based on criteria in this section. (Requirement 55021) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.ii | 55022 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: Where further medical testing or referrals are needed, the employee shall be notified of the reason for the testing or need for referral. (Requirement 55022) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iii | 55023 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: When the examining physician refers an employee to a specialist, communication of relevant medical data shall be provided to the specialist. (Requirement 55023) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv | 55024 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: (Requirement 55024) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.a | 55025 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: Average hearing level at 500, 1000, 2000, and 3000 Hz greater than 25 dB HTL in either ear (Baseline Audiogram). (Requirement 55025) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.b | 55026 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: Difference in average hearing threshold level between the better and poorer ears of more than 15 dB HTL at 500, 1000, and 2000 Hz (Baseline Audiogram). (Requirement 55026) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.c | 55027 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: Change for the worse in average hearing level in either ear compared to the baseline audiogram of more than 15 dB at 500, 1000, and 2000 Hz or more than 20 dB at 3000, 4000, and 6000 hz (Periodic Audiograms). (Requirement 55027) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.d | 55028 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: Variable or inconsistent responses or unusual hearing loss curves (Periodic Audiograms). (Requirement 55028) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.e | 55029 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: History of ear pain; drainage; dizziness; severe, persistent tinnitus, sudden, fluctuating or rapidly progressive hearing loss; or a feeling of fullness or discomfort in one or both ears within the preceding 12 months (Any Audiogram). (Requirement 55029) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.f | 55030 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: Earwax accumulation sufficient to completely obstruct the view of the eardrum with otoscopy or foreign body in the ear canal. (Requirement 55030) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.g | 55031 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: The employee has failed any of the above criteria and has ear pain; drainage; dizziness; or severe, persistent tinnitus (Any Audiogram). (Requirement 55031) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.L.4.iv.h | 55032 | Environmental Health: Hearing Conservation: Process Description: Medical Surveillance: Referrals: The following criteria are based upon the American Academy of Otolaryngology-Head and Neck Surgery referral criteria and shall be used for referral to a qualified physician or otolaryngologist for more comprehensive testing and/or treatment: When an employee suspects that a medical pathology of the ear is caused or aggravated by the wearing of hearing protectors (Any Audiogram). (Requirement 55032) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.m | 55033 | Environmental Health: Hearing Conservation: Process Description: Impairment: The latest edition of the American Medical Association Guides to the Evaluation of Permanent Impairment shall by used as a guideline in determining hearing impairment. (Requirement 55033) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.1 | 55035 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Each occupational hearing conservationist shall receive CAOHC certification training. A CAOHC refresher course shall be taken every 5 years, at a minimum. (Requirement 55035) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.2 | 55036 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Occupational health personnel who conduct assessments shall receive initial training in their Center's hearing conservation program and in noise exposure hazard training. (Requirement 55036) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.3 | 55037 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Employees enrolled in an HCP and their supervisors shall receive annual training in the hazards of noise exposure. (Requirement 55037) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4 | 55038 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: (Requirement 55038) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0i | 55039 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: An overview or review of this section. (Requirement 55039) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0ii | 55040 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: An overview or review of the 29 CFR 1910.95, their Center's and employer's HCP, and this section. (Requirement 55040) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0iii | 55041 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: The effects of hazardous noise and ototoxic substances on hearing (including permanent hearing loss). (Requirement 55041) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0iv | 55042 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: Identification of the hazardous noise sources in the employee's work areas. (Requirement 55042) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0v | 55043 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: Factors that may contribute to hearing loss. (Requirement 55043) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0vi | 55044 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: Noise-control principles. (Requirement 55044) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0vii | 55045 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: An explanation of the audiometric testing procedure and the purpose of audiometric testing. (Requirement 55045) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.0viii | 55046 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: The employee's role and responsibilities in the HCP. (Requirement 55046) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.ix | 55047 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: The purpose of HPDs including: (Requirement 55047) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.ix.a | 55048 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: The purpose of HPDs including: The advantages, disadvantages, and attenuation characteristics of various types of HPDs. (Requirement 55048) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.ix.b | 55049 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: The purpose of HPDs including: Instructions on selection, fitting, use and care of HPDs. (Requirement 55049) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.n.4.ix.c | 55050 | Environmental Health: Hearing Conservation: Process Description: HCP/Hazardous Noise Training: Annual training in the hazards of noise exposure shall include, at a minimum: The purpose of HPDs including: The recommendation that employees use hearing protection whenever they are exposed to hazardous noise during off-duty activities (e.g., lawn mowing, use of firearms). (Requirement 55050) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i | 55053 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: (Requirement 55053) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.a | 55054 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: The Center's written HCP and subsequent revisions. (Requirement 55054) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.b | 55055 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: A comprehensive registry of all personnel placed in the HCP. * (Requirement 55055) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.c | 55056 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Audiometric tests and records.* (Requirement 55056) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.d | 55057 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Background sound pressure levels of audiometric test rooms. (Requirement 55057) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.e | 55058 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Data and information concerning repair of audiometers. (Requirement 55058) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.f | 55059 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Hazardous noise areas and noise levels recorded in those areas. (Requirement 55059) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.g | 55060 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Survey and dosimetry results and recommendations.* (Requirement 55060) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.h | 55061 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Data and information concerning calibration and repair of sound-measuring equipment. (Requirement 55061) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.i | 55062 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: The employee's most recent noise-exposure assessment. (Requirement 55062) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.j | 55063 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Special noise studies. (Requirement 55063) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.k | 55064 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Remedial actions recommended/taken. (Requirement 55064) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.L | 55065 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Engineering controls installed. (Requirement 55065) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.m | 55066 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Design operational and review results. (Requirement 55066) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.n | 55067 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Training. (Requirement 55067) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.o | 55068 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Hearing protector selection. (Requirement 55068) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.i.p | 55069 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Accurate HCP records shall be maintained as specified in the applicable records retention schedules in NPR 1441.1 and 29 CFR 1910.95 (m), Recordkeeping, Records kept shall include: Documentation of other official HCP-related activities. (Requirement 55069) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.ii | 55070 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Items above marked with an asterisk (*) shall be maintained for at least 30 years. (Requirement 55070) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii | 55071 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: (Requirement 55071) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii.a | 55072 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: Hearing threshold levels at 500, 1000, 2000, 3000, 4000, 6000, and 8000 Hz. (Requirement 55072) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii.b | 55073 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: The audiometric level to which the audiometer was calibrated at the time of testing. (Requirement 55073) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii.c | 55074 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: The date of the audiogram. (Requirement 55074) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii.d | 55075 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: The name, employee number, and job classification of the employee tested. (Requirement 55075) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii.e | 55076 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: The examiner's name and position. (Requirement 55076) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iii.f | 55077 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiometric test records shall include, as a minimum: The date of the last calibration of the audiometer. (Requirement 55077) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iv | 55078 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Consistent with the requirements of the Privacy Act and the restrictions in the "Annual Notice and Amendment to Systems of Records," published in the Federal Register, copies of this section, 29 CFR 1910.95, "Occupational Noise Exposure Hearing Conservation Amendment Final Rule" and appendices, and any other records required by this section, shall be provided upon request to: (Requirement 55078) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iv.a | 55079 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Consistent with the requirements of the Privacy Act and the restrictions in the "Annual Notice and Amendment to Systems of Records," published in the Federal Register, copies of this section, 29 CFR 1910.95, "Occupational Noise Exposure Hearing Conservation Amendment Final Rule" and appendices, and any other records required by this section, shall be provided upon request to: Employees and former employees and their representatives. (Requirement 55079) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iv.b | 55080 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Consistent with the requirements of the Privacy Act and the restrictions in the "Annual Notice and Amendment to Systems of Records," published in the Federal Register, copies of this section, 29 CFR 1910.95, "Occupational Noise Exposure Hearing Conservation Amendment Final Rule" and appendices, and any other records required by this section, shall be provided upon request to: Representatives of the U.S. Department of Labor. (Requirement 55080) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iv.c | 55081 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Consistent with the requirements of the Privacy Act and the restrictions in the "Annual Notice and Amendment to Systems of Records," published in the Federal Register, copies of this section, 29 CFR 1910.95, "Occupational Noise Exposure Hearing Conservation Amendment Final Rule" and appendices, and any other records required by this section, shall be provided upon request to: The National Institute for Occupational Safety and Health (NIOSH). (Requirement 55081) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.iv.d | 55082 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Consistent with the requirements of the Privacy Act and the restrictions in the "Annual Notice and Amendment to Systems of Records," published in the Federal Register, copies of this section, 29 CFR 1910.95, "Occupational Noise Exposure Hearing Conservation Amendment Final Rule" and appendices, and any other records required by this section, shall be provided upon request to: Occupational Health Program personnel. (Requirement 55082) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.v | 55083 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: Audiograms and noise-exposure records shall be maintained as a permanent part of an employee's medical records. (Requirement 55083) | S | S | S | Safety | |||
| NPR 1800.1B | 4.09.3.o.1.vi | 55084 | Environmental Health: Hearing Conservation: Process Description: Other Considerations: Recordkeeping: When noise-exposure-measurement records are representative of the exposures of other individuals participating in the Hearing Conservation Program, and to the extent allowable by the Privacy Act, the range of noise levels and the average noise doses shall be made a permanent part of the medical records of those other individuals. (Requirement 55084) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.1 | 55117 | Environmental Health: Food Safety: Introduction: This program establishes a preventive approach to food safety. It encompasses planning and reviews of all proposed projects, processes, and procedures to mitigate potential food safety hazards. The primary objectives of this section are to adopt the Food and Drug Administration (FDA) Food Code as the minimum standard for food service operations at NASA facilities and to provide a NASA policy that promotes good retail food practices and active managerial control of the risk factors most commonly associated with foodborne illness. This shall be accomplished through the implementation of Hazard Analysis Critical Control Point (HACCP) principles, risk-based inspections and controls, and FDA-recommended program standards. Where conflicts between the latest FDA Food Code, this section of NPR 1800.1, and any additional state or local "food code" requirements exist, whichever is most stringent shall be applied. Centers shall coordinate questionable conflicts between the latest FDA Food Code and this section of NPR 1800.1 with the Senior Environmental Health Officer (SEHO) and shall coordinate questionable conflicts between either the FDA Food Code or this section of the NPR with the state and local ?food code? With the local authorities. This section does not apply to spacecraft operations. (Requirement 55117) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.1.a | 55121 | Environmental Health: Food Safety: Responsibilities: The NASA SEHO shall be responsible for managing, evaluating, and reviewing the NASA Food Safety Program to ensure compliance with regulatory and Agency requirements. Specifically, the SEHO shall be responsible for: Acting as the functional representative of the Director of Occupational Health on food safety matters. (Requirement 55121) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.1.b | 55122 | Environmental Health: Food Safety: Responsibilities: The NASA SEHO shall be responsible for managing, evaluating, and reviewing the NASA Food Safety Program to ensure compliance with regulatory and Agency requirements. Specifically, the SEHO shall be responsible for: Providing technical guidance to Center's food service organizations on related safety matters/concerns. (Requirement 55122) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.1.c | 55123 | Environmental Health: Food Safety: Responsibilities: The NASA SEHO shall be responsible for managing, evaluating, and reviewing the NASA Food Safety Program to ensure compliance with regulatory and Agency requirements. Specifically, the SEHO shall be responsible for: Periodically conducting surveys/inspections of each Center's food services for compliance with NASA requirements and applicable local, State, and Federal regulations. (Requirement 55123) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.1.d | 55124 | Environmental Health: Food Safety: Responsibilities: The NASA SEHO shall be responsible for managing, evaluating, and reviewing the NASA Food Safety Program to ensure compliance with regulatory and Agency requirements. Specifically, the SEHO shall be responsible for: Investigating Agency-level complaints associated with food safety concerns. (Requirement 55124) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.1.e | 55125 | Environmental Health: Food Safety: Responsibilities: The NASA SEHO shall be responsible for managing, evaluating, and reviewing the NASA Food Safety Program to ensure compliance with regulatory and Agency requirements. Specifically, the SEHO shall be responsible for: Coordinating with outside agencies, as applicable, on food safety and related environmental health matters. (Requirement 55125) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.1.f | 55126 | Environmental Health: Food Safety: Responsibilities: The NASA SEHO shall be responsible for managing, evaluating, and reviewing the NASA Food Safety Program to ensure compliance with regulatory and Agency requirements. Specifically, the SEHO shall be responsible for: Notifiying, by the most expeditious means, the Agency Director of Occupational Health of food-related incidents as they are reported by the Centers. (Requirement 55126) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.2.a | 55128 | Environmental Health: Food Safety: Responsibilities: Center Directors, including Headquarters and Component Facility Directors shall be responsible for: Ensuring compliance with the provisions in this section. (Requirement 55128) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.2.b | 55129 | Environmental Health: Food Safety: Responsibilities: Center Directors, including Headquarters and Component Facility Directors shall be responsible for: Ensuring all Center Food Safety Program elements are implemented and maintained. (Requirement 55129) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.a | 55131 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Providing for design/procedure reviews, technical assistance, and consultation with all Center organizations on matters concerning food sanitation. (Requirement 55131) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.b | 55132 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Performing, at least quarterly, on-site, risk-based, food safety audits of food establishments; identifying and assessing the hazards and associated risks; determining and implementing critical controls and procedures necessary to reduce risk of foodborne illness; and providing a program of active managerial control. (Requirement 55132) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.c | 55133 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Maintaining accurate and complete survey and inspection data records for the last three months or last three inspections, whichever time span is greater. (Requirement 55133) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.d | 55134 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Providing consultation in the preparation of State and/or local permit applications for food service activities and maintaining copies of those documents and permits, with associated records, to ensure compliance monitoring and reporting is carried out in a timely manner. (Requirement 55134) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.e | 55135 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Identifying and providing support concerning certification and training requirements for food managers and food service workers in order to promote a comprehensive awareness and active managerial control of risk factors most commonly associated with foodborne illnesses. (Requirement 55135) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.f | 55136 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Notifying, by the most expeditious means, the SEHO of major food-related incidents as they are reported. (Requirement 55136) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.g | 55137 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Correcting all inspection violations in a reasonable length of time. (Requirement 55137) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.3.3.h | 55138 | Environmental Health: Food Safety: Responsibilities: Centers shall be responsible for: Notifying their local and State health departments, the Centers for Disease Control and Prevention (CDC), and/or the Department of Homeland Security, as applicable, of foodborne disease outbreaks. (Requirement 55138) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.1.a | 55158 | Environmental Health: Food Safety: Process Description: Provisions: General: All food served or vended for human consumption shall be stored, handled, prepared, and dispensed in a manner which ensures food safety. (Requirement 55158) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.1.b | 55159 | Environmental Health: Food Safety: Process Description: Provisions: General: Vermin shall be controlled to prevent the creation of a health hazard to humans. (Requirement 55159) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.2 | 55160 | Environmental Health: Food Safety: Process Description: Provisions: Constraints/Controls: Constraints/controls imposed upon substances/operations subject to the provisions of this section shall be no less than those required by applicable regulatory authorities and shall include any additional special constraints deemed necessary by the NASA SEHO as a result of unique or operational characteristics. (Requirement 55160) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.3 | 55161 | Environmental Health: Food Safety: Process Description: Provisions: Records: All records generated by following these procedural requirements, including but not limited to those required by local, State, or Federal statute or regulation, and the most recent edition of the FDA Food Code, shall be maintained in accordance with NPR 1441.1, NASA Records Retention Schedules. All records shall be available for review by the NASA SEHO or designee and Federal, State, and/or loca, l food safety inspectors. Examples of records include applicable training records, inspection records, temperature logs, food receiving logs, maintenance logs, and dishwasher logs. (Requirement 55161) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.4 | 55162 | Environmental Health: Food Safety: Process Description: Provisions: Waivers: Waivers from some or all NASA Food Safety Program requirements described in this section shall be determined on a case-by-case basis by the NASA SEHO. Requests for waivers shall be submitted to the NASA SEHO in writing for approval by the Chief Health and Medical Officer (CHMO) prior to their initiation. Authorization may be withdrawn at any time for violations of the granted waiver or other regulatory non-compliance. Centers shall provide copies of requests for waivers to the Office of Safety and Mission Assurance if they are deemed to affect the NASA workforce, and the appropriate union, as applicable. (Requirement 55162) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.5 | 55163 | Environmental Health: Food Safety: Process Description: Provisions: Non-Compliances: Where Agency surveys or inspections indicate non-compliance with NASA-approved procedures and controls, the responsible organization for that activity shall correct discrepancies and notify the NASA SEHO and the Center Occupational Health Office when remediation has been completed. (Requirement 55163) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.4.2.6 | 55164 | Environmental Health: Food Safety: Process Description: Provisions: Acidents, Incidents, and Emergencies: The NASA SEHO and the Center Occupational Health Office shall be immediately advised of major accidents, incidents, or emergencies involving food safety. (Requirement 55164) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.1 | 55166 | Environmental Health: Food Safety: Safety: General: This section outlines the basic methods to prevent outbreaks of foodborne illness by assuring all food served or vended at NASA Centers and Component Facilities shall be clean and free of pathogenic organisms, contamination, and organic or inorganic toxins (including those of bacterial origin). This applies to transporting, storing, preparing, serving, and vending of food provided/available at NASA Centers and Component Facilities. This applies equally to all appropriated funded, non-appropriated funded, organizational, contractor, and/or private association food activities held on NASA Centers and Component Facilities. Centers and Component Facilities shall comply with HACCP principles and the United States Department of Health and Human Services, FDA Food Code. (Requirement 55166) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.a | 55169 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that requirements and provisions of this section are included in all food and beverage services contracts, subcontracts, and other applicable contracts. (Requirement 55169) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.b | 55170 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Conduct a continuing program of inspection and surveillance of all food establishments by individuals who are qualified by certification or standardization to conduct inspection and surveillance to ensure that all food service establishments shall meet or exceed the minimum acceptable requirements established by NASA directives, as well as applicable Federal, State, and local regulations. (Requirement 55170) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.c | 55171 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Remove from service or sale all food items suspected to be contaminated, unwholesome, or otherwise deemed unfit for consumption. (Requirement 55171) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.d | 55172 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure design reviews are conducted for new or redesigned food establishments, as well as for facilities that intend to make significant changes to the existing menu or theme. Facility plans shall consider menu plans and include equipment specifications and food establishment facility layouts. (Requirement 55172) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.e | 55173 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Review prepared food establishment design review packages that include proposed menu, equipment specifications, and equipment layout for any food facility to be newly constructed, remodeled, or reopened. (Requirement 55173) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.f | 55174 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Review plans for temporary events and provide recommendations concerning food safety provisions. (Requirement 55174) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.g | 55175 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that Center policy requires prompt notification of a responsible individual in the event of an emergency such as a fire, flood, power outage, or similar event which might result in the contamination of food or that might prevent potentially hazardous food from being held at safe temperatures. (Requirement 55175) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.h | 55176 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that training is provided to maintain certification requirements for all food service employees. (Requirement 55176) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.i | 55177 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Maintain the most recent copy of the inspection form and have it available for review by inspection personnel and food installation customers. (Requirement 55177) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.j | 55178 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure all food handlers report to their designated medical clinic or designated medical care provider when any symptoms of infections and/or communicable disease are present. (Requirement 55178) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.k.i | 55180 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that all food handlers returning to work after an illness-related absence associated with any of the conditions below are cleared by an appropriate medical care provider: A diagnosed illness of Norovirus, typhoid fever (Salmonella typhia), shigellosis (Shigella spp.), E. Coli O157:H7 infection (or other EHEC/STEC (enterohemorrhagic or Shiga toxin-producing E. Coli)), or hepatitis A virus (hepatitis A)). (Requirement 55180) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.k.ii | 55181 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that all food handlers returning to work after an illness-related absence associated with any of the conditions below are cleared by an appropriate medical care provider: Symptoms of gastrointestinal illness such as diarrhea, fever, vomiting, jaundice, or sore throat with fever. (Requirement 55181) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.k.iii | 55182 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that all food handlers returning to work after an illness-related absence associated with any of the conditions below are cleared by an appropriate medical care provider: A lesion, boil, or wound containing pus that is open or draining and is on the hands, wrists, or exposed portions of the arms. (Requirement 55182) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.k.iv | 55183 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that all food handlers returning to work after an illness-related absence associated with any of the conditions below are cleared by an appropriate medical care provider: Illness from consuming food that was implicated in or caused an outbreak. (Requirement 55183) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.1.L | 55184 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall: Ensure that organizations operating vending machines that dispense food or beverages provide the Center Occupational Health Office with a list of on-site vending machines and their locations, where potentially hazardous food items are dispensed. (Requirement 55184) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.2.2 | 55185 | Environmental Health: Food Safety: Safety: Organizational Functions: Centers shall have a written food safety policy that requires them to ensure that an HACCP or equivalent management system includes and implements a process of self-inspection and continuous improvement. The management system shall provide for active managerial control and the purposeful incorporation of specific actions or procedures into the safety plans. A generic plan is not acceptable. The food safety plan shall identify potential hazards of significance and include preventive measures to ensure and improve food safety. Critical Control Points shall be effectively controlled. (Requirement 55185) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.3.1 | 55187 | Environmental Health: Food Safety: Safety: Equipment/Facility Design Features: New and redesigned facilities shall be reviewed by the Center Occupational Health Office. The design of a food establishment shall meet the principles outlined in State and local codes and the FDA Food Code, unless they cannot be technically accomplished. All design deviations shall be approved by the Center's Occupational Health representative prior to implementation. (Requirement 55187) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.5.3.2 | 55188 | Environmental Health: Food Safety: Safety: Equipment/Facility Design Features: Changes that may affect the Center's Food Safety Program requirements shall be coordinated with appropriate Center personnel and approved in advance by the Center's Occupational Health representative. (Requirement 55188) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.6.2.a | 55192 | Environmental Health: Food Safety: Bottled Water for Water Dispensers: Organizational Functions: The Center shall maintain a continuing surveillance of all bottled water dispensers. Under no circumstances shall empty bottles be refilled by anyone other than the processor. All organizations procuring bottled water shall ensure that: No bottled water dispensers are allowed or bottles of water stored, in areas where general hazards or contamination of any kind pose a threat to users under normal operations. (Requirement 55192) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.6.2.b | 55193 | Environmental Health: Food Safety: Bottled Water for Water Dispensers: Organizational Functions: The Center shall maintain a continuing surveillance of all bottled water dispensers. Under no circumstances shall empty bottles be refilled by anyone other than the processor. All organizations procuring bottled water shall ensure that: Contractors and subcontractors furnishing bottled water shall provide routine chemical and microbiological laboratory analysis reports for bottled water delivered to the Center. (Requirement 55193) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.6.2.c | 55194 | Environmental Health: Food Safety: Bottled Water for Water Dispensers: Organizational Functions: The Center shall maintain a continuing surveillance of all bottled water dispensers. Under no circumstances shall empty bottles be refilled by anyone other than the processor. All organizations procuring bottled water shall ensure that: Bottled water dispensers are maintained in a sanitary condition. (Requirement 55194) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.6.2.d | 55195 | Environmental Health: Food Safety: Bottled Water for Water Dispensers: Organizational Functions: The Center shall maintain a continuing surveillance of all bottled water dispensers. Under no circumstances shall empty bottles be refilled by anyone other than the processor. All organizations procuring bottled water shall ensure that: All dispensers have equipment numbers. (Requirement 55195) | S | S | S | Safety | |||
| NPR 1800.1B | 4.10.6.2.e | 55196 | Environmental Health: Food Safety: Bottled Water for Water Dispensers: Organizational Functions: The Center shall maintain a continuing surveillance of all bottled water dispensers. Under no circumstances shall empty bottles be refilled by anyone other than the processor. All organizations procuring bottled water shall ensure that: There is prompt recall of the suspect bottled water and/or appropriate action when notified of contamination detection. (Requirement 55196) | S | S | S | Safety | |||
| NPR 1800.1B | 7.1 | 55338 | Occupational Health Review Process: Introduction: This chapter establishes a method for performing and documenting the results of Agency Occupational Health reviews and delineates requirements for biennial evaluations of major NASA HQ and field locations that occur on NASA property. For purposes of the audit element of the review process, the OCHMO defines a requirement as a mandatory element for a program or function. Requirements shall include NASA Policy Directives (NPDs), NASA Procedures and Requirements (NPRs) and other external regulations and consensus standards applicable to NASA. The review process shall be comprehensive enough to provide Center Senior Management with a status of the effectiveness of their Center's programs. By definition this must include the provision of sufficient resources commensurate with the Center's size, population, and mission to achieve and maintain desired effectiveness. (Requirement 55338) | S | S | S | Safety | |||
| NPR 1800.1B | 7.2(1) | 55339 | Occupational Health Review Process: Purpose: Regular reviews of medical and occupational health services are required to assure protection of the health of the NASA workforce. Biennial OCHMO review shall be designed to help the Agency identify and mitigate risk, provide a consistent, high level of health care to participants across the Agency and identify best practices and innovative solutions that provide greater opperational effectiveness and efficiency. (Requirement 55339) | S | S | S | Safety | |||
| NPR 1800.1B | 7.2(2) | 55340 | Occupational Health Review Process: Purpose: Occupational health (OH) reviews include a compliance audit component. They also provide an opportunity for open dialogue with Center personnel and are used as a forum to advocate for appropriate support for health-related services. The Review Team provides technical help, guidance on best practices, support on Agency occupational health initiatives, and facilitates specialized training for emerging health threats or new requirements as needed to enhance the competency of health discipline employees. (Requirement 55340) | S | S | S | Safety | |||
| NPR 1800.1B | 7.2(3) | 55341 | Occupational Health Review Process: Purpose: The OH components assessed shall include medical care provided at each Center's Occupational Medicine Clinic (including emergency care capability and coordination with other departments, medical quality assurance, and health clinic environment of care); preventive health activities; the employee assistance program; federal workers' compensation; fitness facilities; industrial hygiene; health physics; sanitation and food safety programs; and medical aspects of other programs such as emergency preparedness and childcare facilities. (Requirement 55341) | S | S | S | Safety | |||
| NPR 1800.1B | 7.2(4) | 55342 | Occupational Health Review Process: Purpose: During the alternate years, when a review is not conducted at a Center, the Center shall perform a self evaluation using criteria provided in the most recent occupational health review conducted at the Center, or some other approved equivalent methodology. A record of areas reviewed, names individual(s) conducting evaluations, dates and locations shall be retained on file at the host center. Each Center shall provide a self-evaluation to the OCHMO in the same month of the alternate year in which they are normally audited. The Center report shall delineate areas of substantial improvement and/or degradation of their occupational health program. (Requirement 55342) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(01) | 55343 | Occupational Health Review Process: Occupational health reviews shall compare Center policies, procedures, and practices to regulatory and other compliance requirements, agency policy requirements and consensus standards. A written report shall be produced from the review findings and provided to the Center for response. The appropriate Mission Associate Administrator, Institutional Corporate Management, and Safety and Mission Assurance Directorate shall be appropriately copied for their reference of findings associated with health, environmental compliance and/or safety, respectively. (Requirement 55343) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(02) | 55344 | Occupational Health Review Process: Occupational health reviews shall begin with scheduling review dates with the Centers' occupational health Contracting Officer Technical Representative(s) (COTR) or their appointed representative. The COTR or their representative shall act as the Center's primary point of contact for the review process. The schedule for the program surveys is as follows: (Requirement 55344) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(03) | 55345 | Occupational Health Review Process: A letter shall be sent to the Center Director or Facility Manager, at least 60 days ahead of the review dates, announcing the upcoming review and requesting the associated support. This shall be followed with an e-mail to the COTR containing the review questionnaires and a request for specific Center documentation. The COTR shall distribute the requests to the Centers' occupational health representatives. The Centers' occupational health representative shall answer the questions. The primary point of contact shall return the questionnaires to the OCHMO Review Team Leader via e-mail. The requested Center-specific documentation shall be returned to the OCHMO Review Team Leader, who will distribute it to the Review Team for their assessment prior to the Center review. (Requirement 55345) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(04) | 55346 | Occupational Health Review Process: The review shall begin with an in-briefing of the principals involved in the review process. The Center shall provide multi-disciplinary coverage for the entire review period. The in-briefing shall provide a forum for an exchange of information and details regarding the review. It shall also provide the Centers with current OHMS information that may affect them and provide feedback on previous review process improvements. The in-briefing shall be an opportunity for the OHMS Review Team to offer expert information and advocacy while on site. The Centers shall present their top occupational health concerns and a status of any open or unresolved nonconformance findings from previous occupational health reviews at the in-briefing. (Requirement 55346) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(05) | 55347 | Occupational Health Review Process: After the in-briefing, each reviewer shall meet with their subject matter counterpart to clarify questionnaire answers, discuss Center occupational health programs and process and plan area visits. Information shall be collected and verified through interviews, tours of work areas, observation of activities and the surrounding work environment and conditions, documentation of reviews, and record inspections. (Requirement 55347) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(06) | 55348 | Occupational Health Review Process: The out-briefing shall be presented to the Center Director or the Deputy as a verbal executive summary. It shall focus on the strengths and weaknesses found during the review. A written report shall be preapred within 45 days of out-briefing. (Requirement 55348) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(07) | 55349 | Occupational Health Review Process: The written report shall be a reiteration of the same issues expressed in the verbal executive summary, plus a detailed report of all review findings. Centers shall have 45 days after receipt of the written report to reply to the OHMS Review Team Leader with a corrective action plan that addresses remedial actions for the non-conformance findings associated with the review process. (Requirement 55349) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(08) | 55350 | Occupational Health Review Process: Nonconformance findings shall be closed within 6 months or as negotiated. The Center shall keep the OHMS Review Team Leader informed of the status of corrective action activities particularly if a delay is anticipated. Corrective actions shall only be "closed" when the anomalous condition associated with the non-conformance findings associated with the review process. Nonconformance findings shall be closed within 6 months or as negotiated. The Center shall keep the OHMS Review Team Leader informed of the status of corrective action activities particularly if a delay is anticipated. Corrective actions shall only be "closed" when the anomalous condition associated with the non-conformance no longer exists. (Requirement 55350) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(09) | 55351 | Occupational Health Review Process: A re-visit to a Center to review the occupational health program, or portion thereof, shall be performed when important program elements are non-conforming or incomplete or of, in the opinion of the discipline reviewer and team leader, the program or a portion thereof, shall be performed when important program elements are non-conforming or incomplete or if, in the opinion of the discipline reviewer and team leader, the program or a portion thereof, is sufficiently weak or degraded as to require a review before the next biennial review. Follow-up review elements shall concentrate only on the deficient areas. (Requirement 55351) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(10) | 55352 | Occupational Health Review Process: Working documents, reports, and results shall be retained on file or in the Agency Health Electronic Database (AHED) for use and future examination. (Requirement 55352) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(11) | 55353 | Occupational Health Review Process: Findings shall be categorized as follows: (Requirement 55353) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(12) | 55354 | Occupational Health Review Process: Commendation: Best practices that far exceed requirements or are ingenious time or cost-saving solution to problems. (Requirement 55354) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(13) | 55355 | Occupational Health Review Process: Recognition: Acknowledgement of significant improvements or progress toward Center occupational health program goals. (Requirement 55355) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(14) | 55356 | Occupational Health Review Process: Observation: A noteworthy comment such as notation of a significant difference compared with other Centers' practices. Such comments are neither positive nor negative in nature. (Requirement 55356) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(15) | 55357 | Occupational Health Review Process: Opportunity for Improvement: A condition that meets compliance requirements, but could be improved. Opportunities for Improvement will be accompanied by "Recommendations" in the written report but are not required to be addressed in the Center's corrective action plan. (Requirement 55357) | S | S | S | Safety | |||
| NPR 1800.1B | 7.3(16) | 55358 | Occupational Health Review Process: Nonconformance: A divergence from a compliance rrequirement (Federal, State, local, NASA Agency, NASA Center, etc.) or consensus standard (ANSI, HACCP, NIOSH, NFPA, etc.). (Requirement 55358) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.1.a | 55361 | Occupational Health Review Process: Responsibilities: The Chief Health and Medical Officer shall be responsible for: Ensuring that planned program evaluations of NASA facilities are conducted to determine the value and adequacy of Center occupational health programs and that program resources are appropriately provided (Requirement 55361) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.1.b | 55362 | Occupational Health Review Process: Responsibilities: The Chief Health and Medical Officer shall be responsible for: Reviewing Flight Medicine aspects of NASA's occupational health processes (Requirement 55362) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.1.c | 55363 | Occupational Health Review Process: Responsibilities: The Chief Health and Medical Officer shall be responsible for: Determining the need for more frequent specialized surveys on aspects of, or the entire, occupational health program. (Requirement 55363) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.2.a | 55365 | Occupational Health Review Process: Responsibilities: The Director of Occupational Health shall be responsible for the following: Assuring overall occupational health review process efficacy (Requirement 55365) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.2.b | 55366 | Occupational Health Review Process: Responsibilities: The Director of Occupational Health shall be responsible for the following: Appointing the team lead for Center reviews (Requirement 55366) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.2.c | 55367 | Occupational Health Review Process: Responsibilities: The Director of Occupational Health shall be responsible for the following: Reviewing and releasing occupational health review reports (Requirement 55367) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.2.d | 55368 | Occupational Health Review Process: Responsibilities: The Director of Occupational Health shall be responsible for the following: Approving or disapproving lessons learned suggestions prior to their implementation (Requirement 55368) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.a | 55370 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: The overall effective implementation of the Agency's occupational health review (Requirement 55370) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.b | 55371 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Initiating contact with each Center prior to review (Requirement 55371) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.c | 55372 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Providing Review Team members with discipline-specific point of contact information for each Center, inculding names, e-mail addresses, and phone numbers (Requirement 55372) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.d | 55373 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Coordinating and exchanging information with each Center primary point of contact (Requirement 55373) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.e | 55374 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Establishing each Center's review schedule and associated meetings (Requirement 55374) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.f | 55375 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Representing the OHMS at each Center's review in-briefing meeting (Requirement 55375) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.g | 55376 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Overseeing all aspects of the review on site (Requirement 55376) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.h | 55377 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Coordinating real-time issues and problems, as they arise, during the review process (Requirement 55377) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.i | 55378 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Consulting with the Agency's Director of Occupational Health, as needed during the review, regarding nonconformance findings (Requirement 55378) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.j | 55379 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Representing the OHMS at each Center's out briefing meetings (Requirement 55379) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.k | 55380 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Coordinating and preparing review reports (Requirement 55380) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.L | 55381 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Conducting "lessons-learned" meetings with Review Team Members as soon as feasible after each occupational health review (Requirement 55381) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.m | 55382 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Compiling strength and weakness summaries for inclusion into each Center's written report summary (Requirement 55382) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.n | 55383 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Ensuring that the written report is consistent with the verbal out briefing, and is released within 45 days. (Requirement 55383) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.o | 55384 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Tracking Centers' nonconformance findings to closure (Requirement 55384) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.3.p | 55385 | Occupational Health Review Process: Responsibilities: The OHMS Review Team Leader shall be the Agency's primary representative for the review and shall be responsible for the following: Continually improving the occupational health review process based on lessons-learned (Requirement 55385) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.a | 55387 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Appointing a Center point of contact, with sufficient authority for reviews, to coordinate Center on-site reviews with the OHMS, and to provide ready access to facilities, and other logistical support (Requirement 55387) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.b | 55388 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Supporting the review effort with adequate resources and personnel (Requirement 55388) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.c | 55389 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Attending the out-briefing or designating the Deputy Center Director to attend if he/she is unavailable (Requirement 55389) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.d | 55390 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Assuring the corrective action plan addresses all nonconformance findings (Requirement 55390) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.e | 55391 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Providing the corrective action plan to the Agency (Requirement 55391) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.f | 55392 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Providing the adequate resources to resolve corrective actions (Requirement 55392) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.g | 55393 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Ensuring implementation of the requests for action designated in the review (Requirement 55393) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.4.h | 55394 | Occupational Health Review Process: Responsibilities: Center Directors shall be responsible for the following: Assuring notification of the OHMS for Center reviews, audits and visits from outside regulatory bodies, such as the Occupational Safety and Health Administration (OSHA), the Nuclear Regulatory Commission (NRC), etc. (Requirement 55394) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.a | 55396 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Being the subject matter points of contact for their Center counterparts (Requirement 55396) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.b | 55397 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Reviewing returned Center questionnaires, and previous audit/assessment information prior to the review (Requirement 55397) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.c | 55398 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Coordinating and exchaning information with each Centers' subject matter points of contact (Requirement 55398) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.d | 55399 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Establishing individual review times and coordinating meetings with Center counterparts (Requirement 55399) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.e | 55400 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Performing their discipline-specific review of the Center's occupational health program (Requirement 55400) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.f | 55401 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Reporting real-time issues and problems to the Review Team Leader, as they arise, during the review process (Requirement 55401) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.g | 55402 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Representing the OHMS at the review out-briefing or coordinating with other Review Team members who will attend the out-briefing meetings, as applicable (Requirement 55402) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.h | 55403 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Coordinating, preparing and entering data into the AHED (Requirement 55403) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.i | 55404 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Providing the team lead with a summary of strengths and weaknesses of the Center pertinent to their disciplines for the summary report (Requirement 55404) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.j | 55405 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Attending "lessons-learned" meetings as they are scheduled (Requirement 55405) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.k | 55406 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Reviewing draft occupational health review reports (Requirement 55406) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.L | 55407 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Reviewing, and either accepting or rejecting, nonconformance closure rationale (Requirement 55407) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.m | 55408 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Updating the status of nonconformance findings in the AHED (Requirement 55408) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.5.n | 55409 | Occupational Health Review Process: Responsibilities: Individual Agency Review Team members shall be responsible for the following: Coordinating nonconformance findings with the team leader in support of chain-of-command reporting (Requirement 55409) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.a | 55411 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Coordinating and exchanging information with each review Team Member counterpart (Requirement 55411) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.b | 55412 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Providing a discipline-specific point of contact list to the Review Team Leader, including names, mail, and e-mail addresses, and phone numbers (Requirement 55412) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.c | 55413 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Distributing review questionnaires from the Review Team Leader to Center personnel (Requirement 55413) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.d | 55414 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: E-mailing completed questionnaires to the Agency Review Team Leader on time (Requirement 55414) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.e | 55415 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Providing other requested documentation via e-mail, fax, etc. to the Agency Review Team Leader (Requirement 55415) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.f | 55416 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Arranging for badging and escort of the Review Team (Requirement 55416) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.g | 55417 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Coordinating requirements for bringing review equipment onto the Center, including any forms that must be completed and submitted for equipment use at the Center (e.g., laptop PCs, cameras, PDAs, etc.) (Requirement 55417) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.h | 55418 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Arranging for a private work area and logistic support for the Agency Review Team (Requirement 55418) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.i | 55419 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Arranging in-briefings and out-briefings and associated meeting rooms (Requirement 55419) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.j | 55420 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Supporting the review schedule and associated meetings (Requirement 55420) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.k | 55421 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Providing access to Center internal locations subject to the scope of the review (Requirement 55421) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.L | 55422 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Providing on-site access to additional Center documentation as needed (Requirement 55422) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.m | 55423 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Overseeing the review for the Center (Requirement 55423) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.n | 55424 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Coordinating real-time issues and problems, as they arise, during the review process (Requirement 55424) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.o | 55425 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Coordinating nonconformance findings as needed with Center Management (Requirement 55425) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.p | 55426 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Representing the Center at the review out-briefing meetings (Requirement 55426) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.q | 55427 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Overseeing preparation of the corrective action plan (Requirement 55427) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.6.r | 55428 | Occupational Health Review Process: Responsibilities: The Center primary point of contact shall be responsible for the following: Tracking Centers' nonconformance findings to closure (Requirement 55428) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.a | 55430 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Being the subject matter points of contact for the Agency Review Team counterparts (Requirement 55430) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.b | 55431 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Emailing completed questionnaires to the Center primary point of contact on time (Requirement 55431) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.c | 55432 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Coordinating and exchanging occupational health discipline information with the appropriate Review Team counterpart (Requirement 55432) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.d | 55433 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Being available to support their Agency Review Team counterpart with the review process (Requirement 55433) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.e | 55434 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Supporting the review in-briefing meetings (Requirement 55434) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.f | 55435 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Coordinating individual review times and meetings with Agency Review Team counterparts (Requirement 55435) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.g | 55436 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Providing objective evidence of implementation of requirements (e.g., documentation, records, licenses, etc.). (Requirement 55436) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.h | 55437 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Escorting Agency Review Team personnel (Requirement 55437) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.i | 55438 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Reporting real-time issues and problems to the Center primary point of contact, as they arise, during the review process (Requirement 55438) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.j | 55439 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Coordinating with the Agency Review Team on specific discipline findings prior to the out briefing (Requirement 55439) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.7.k | 55440 | Occupational Health Review Process: Responsibilities: Center Discipline-specific points of contact shall be responsible for the following: Representing the Center at the review out-briefing meetings as applicable (Requirement 55440) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.a | 55442 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Maintaing an overall schedule of each review to assure that critical milestones are met, such as review announcement letter, pre-review meetings, review letters, six-month status reports, lessons learned meetings and responses to corrective action plans (Requirement 55442) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.b | 55443 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Assuring review announcement letters are initiated in sufficient time to allow for OHMS and Center actions questionnaires and document requests (Requirement 55443) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.c | 55444 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Scheduling in-house pre-review meetings (Requirement 55444) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.d | 55445 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Preparing the final report from AHED data (Requirement 55445) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.e | 55446 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Preparing the executive summary and detailed report for distribution to the Center within 45 days of completing the review (Requirement 55446) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.f | 55447 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Scheduling lessons learned meetings after reviews (Requirement 55447) | S | S | S | Safety | |||
| NPR 1800.1B | 7.4.8.g | 55448 | Occupational Health Review Process: Responsibilities: The OHMS Administrative Assistant to the Director shall be responsible for: Providing a lessons learned report (Requirement 55448) | S | S | S | Safety | |||
| NPR 8715.1 | 2.01.1 | 22003 | The NASA Administrator is the senior person responsible for Agency wide safety and health. (Requirement 22003) | S | S | S | Safety | |||
| NPR 8715.1 | 2.01.2(1) | 22004 | OSHA requires that each agency head designate an official with sufficient authority and responsibility to represent effectively the interest and support the agency head in the management and administration of the agency occupational safety and health program. (Requirement 22004) | S | S | S | Safety | |||
| NPR 8715.1 | 2.01.2(2) | 31542 | The current Designated Agency Safety and Health Official (DASHO) for NASA is the Associate Administrator for the Office of Life and Microgravity Sciences and Applications. The DASHO holds responsibility for assuring that all OSHA regulatory requirements at the Agency level are fulfilled or implemented. (Requirement 31542) | S | S | S | Safety | |||
| NPR 8715.1 | 2.01.2(3) | 31775 | The DASHO holds responsibility for assuring that all OSHA regulatory requirements at the Agency level are fulfilled or implemented. The DASHO is responsible for assuring that safety and health officials are appointed at appropriate levels with adequate budgets and staffs to implement occupational safety and health programs at all operational levels as required by CFR 1960.6, paragraph (c). (Requirement 31775) | S | S | S | Safety | |||
| NPR 8715.1 | 2.02.1 | 22156 | NASA Center Directors and the Assistant Administrator for Institutional and Corporate Management have the responsibility to ensure that the NASA occupational Health and safety programs are effectively implemented and operated at their Centers and Component Facilities. (Requirement 22156) | S | S | S | Safety | |||
| NPR 8715.1 | 2.02.2 | 22006 | Other Officials-in-Charge of Headquarters Offices shall ensure that their organizations support the NASA Occupational Health and Safety Program. (Requirement 22006) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1 | 22007 | Supervisors are responsible for ensuring a safe and healthful workplace. (Requirement 22007) This responsibility extends to any place where their employee(s) is engaged in work related to his/her job including international and extraterrestrial locations. Responsibilities include: | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.1(1) | 22090 | Furnishing a safe and healthful place of employment and ensuring that identified hazards are eliminated or controlled through a rigorous proactive inspection and abatement process. (Requirement 22090) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.2 | 22091 | Ensuring that employees are informed of NASA safety and health programs and of the protection afforded employees through these programs. (Requirement 22091) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.3 | 22092 | Informing employees of the location of the nearest medical treatment facility, procedures for obtaining treatment, and methods for reporting occupational injuries or illnesses. (Requirement 22092) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.4 | 22093 | Instructing employees to report hazardous conditions to their immediate supervisor or to their Center or Component Facility safety and health official. (Requirement 22093) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.5 | 22094 | Taking appropriate action to protect employees in imminent danger situations. (Requirement 22094) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.6 | 22095 | Informing employees of specific hazards associated with their workplace and duties and ensuring use of appropriate personal protective equipment. (Requirement 22095) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.7(1) | 22008 | Ensuring that NASA employees are provided safety and health training as applicable to the work environment (see paragraph 2.5.2.6). (Requirement 22008) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.7(2) | 31544 | Ensuring that employees are informed of their specific responsibilities and rights under the Act, Executive Order l2l96, and 29 CFR Part 1960, and how they may participate in the safety and health program. (Requirement 31544) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.8 | 22097 | Cooperating with and assisting safety and health personnel while they are performing their duties as specified in the NASA Occupational Safety and Health (OSH) program. (Requirement 22097) | S | S | S | Safety | |||
| NPR 8715.1 | 2.03.1.9 | 22098 | Ensuring timely reporting of mishaps and close calls and timely follow up of any corrective actions. (Requirement 22098) | S | S | S | Safety | |||
| NPR 8715.1 | 2.04.1 | 22100 | Complying with safety and health standards, rules, and regulations, issued by NASA, Federal, State, and local authorities. (Requirement 22100) | S | S | S | Safety | |||
| NPR 8715.1 | 2.04.2 | 22101 | Using established procedures to report suspected safety or health hazards. (Requirement 22101) | S | S | S | Safety | |||
| NPR 8715.1 | 2.04.3 | 22102 | Promptly obtaining necessary emergency medical care as the result of an occupational injury or illness. (Requirement 22102) | S | S | S | Safety | |||
| NPR 8715.1 | 2.04.4 | 22103 | Promptly reporting occupational injuries, illnesses, mishaps, and close calls in accordance with established procedures. (Requirement 22103) | S | S | S | Safety | |||
| NPR 8715.1 | 2.04.5 | 22104 | Cooperating with safety and health personnel during inspections, surveys, and investigations. (Requirement 22104) | S | S | S | Safety | |||
| NPR 8715.1 | 2.04.6 | 22105 | Utilizing protective equipment when prescribed and/or required by safety or health standards, good work practices, or when directed by supervisors. (Requirement 22105) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.1.1 | 22107 | Access to documents describing NASA's occupational safety and health programs including the Act, applicable Executive orders, Federal, State, and local regulations, and standards. (Requirement 22107) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.1.2. | 22108 | Access to the log and summary of occupational injuries and illnesses, including OSHA Form 100F or its equivalent, subject to the Privacy Act of 1974, as amended, 5 U.SC. 552a. (Requirement 22108) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.1.3. | 22109 | Access to proposed NASA occupational safety and health standards and encouraged to provide comments to their appropriate representatives or committees. (Requirement 22109) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.1.4. | 22110 | Access to inspection reports, job hazard analyses of the work site, associated job safety and health documentation, and accident investigations. (Requirement 22110) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.2.1. | 22111 | NASA-sponsored medical examinations at no cost when the Center or Component Facility occupational health or safety representative identifies significant exposure or significant potential for exposure to a chemical, physical, or biological agent in the work environment. (Requirement 22111) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.2.2. | 22112 | Safety and health training, appropriate for the degree of hazard associated with their occupation or workplace. (Requirement 22112) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.3 | 22011 | Employees shall be represented on Center or Component Facility safety and health committees or their subcommittees. (Requirement 2201) | S | S | S | Safety | |||
| NPR 8715.1 | 2.05.6 | 22013 | Employees shall be authorized official time to participate in the Agency safety and health programs and in the activities provided for in Section 19 of the Act, Executive Order 12196, and 29 CFR 1960. (Requirement 22013) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.1(1) | 22014 | Dissemination of Program Information: Employees must be made aware of the Center or Component Facility safety and health programs. (Requirement 22014) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.1(2) | 31545 | Dissemination of Program Information: Copies of Executive Order 12196, 29 CFR Part 1960, details of NASAs Occupational Safety and Health programs, and applicable safety and health standards shall be made available, upon request, to employees or employee representatives for review. (Requirement 31545) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.2 | 22015 | A copy of the Center or Component Facility written safety and health program information shall be made available to each supervisor, safety and health committee member, and employee representatives. (Requirement 22015) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.3 | 22016 | The Center or Component Facility safety and health official(s) shall assure that a poster (NASA Form 1613, "NASA Occupational Safety and Health Protection For Federal Employees") is conspicuously posted in each major facility informing employees of the provisions of the Act, Executive Order 12196, and NASAs Occupational Safety and Health programs. (Requirement 22016) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.3.1 | 31546 | Individual NASA Centers or Component Facilities shall augment such posters with site specific information, which includes the following: Details of the Center or Component Facility procedure for responding to employee reports of potential unsafe or unhealthful conditions. (Requirement 31546) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.3.2 | 31547 | Individual NASA Centers or Component Facilities shall augment such posters with site specific information, which includes the following: Details of NASAs procedure for filing allegations of discrimination or reprisal for participating in the safety or health program or for reporting potential unsafe or unhealthful conditions. (Requirement 31547) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.3.3 | 31548 | Individual NASA Centers or Component Facilities shall augment such posters with site specific information, which includes the following: Locations where employees may obtain information regarding the Center or Component Facility safety and health programs. (Requirement 31548) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.3.4 | 31549 | Individual NASA Centers or Component Facilities shall augment such posters with site specific information, which includes the following: Relevant information about the Centers safety and health committee. (Requirement 31549) | S | S | S | Safety | |||
| NPR 8715.1 | 2.06.4 | 22017 | An annual summary of occupational injuries and illnesses shall be posted no later than 45 calendar days after the close of the fiscal year or otherwise disseminated in written form to all employees of the workplace. (Requirement 22017) | S | S | S | Safety | |||
| NPR 8715.1 | 2.07 | 22018 | Freedom From Reprisal: No employee shall be subject to restraint, interference, coercion, discrimination, or reprisal for filing a report of an unsafe or unhealthful working condition, participation in the activities of the Agency's occupational safety and health programs, or the exercise of any right or privilege afforded by Section 19 of the Act, Executive Order 12196, or 29 CFR Part 1960. (Requirement 22018) | S | S | S | Safety | |||
| NPR 8715.1 | 2.09.5(1) | 22120 | Abatement of unsafe and unhealthful conditions is the primary responsibility of the Center Directors with assistance provided by the Center or Component Facility Safety and Health Office(s). (Requirement 22120) | S | S | S | Safety | |||
| NPR 8715.1 | 2.09.5(2) | 31550 | In the event the Center or Component Facility funding is inadequate to address and abate the hazard, it is the responsibility of the Associate Administrator to resolve any funding issue. (Requirement 31550) | S | S | S | Safety | |||
| NPR 8715.1 | 2.09.6(1) | 22024 | The safety and health inspections required by Subpart D, 29 CFR Part 1960, coupled with action in response to safety complaints and reports of deficiencies are intended to identify conditions requiring corrective action. Cost estimates are required for all projects. (Requirement 22024) | S | S | S | Safety | |||
| NPR 8715.1 | 2.09.6(2) | 31551 | The safety and health inspections required by Subpart D, 29 CFR Part 1960: In addition, the appropriate fund source type and a justification for action must be given. (Requirement 31551) | S | S | S | Safety | |||
| NPR 8715.1 | 2.10.2 | 22027 | To ensure such compliance, Centers or Component Facilities shall: (.1) Provide Material Safety Data Sheets (MSDS) for hazardous materials which meet the content requirements of 29 CFR 1910.1200. (Requirement 22027) (.2) Meet requirements for system safety as outlined in NPR 8715.3, "NASA Safety Manual," for major hardware and software product development. | S | S | S | Safety | |||
| NPR 8715.1 | 3.1.1 | 22029 | NASA will comply with safety and health standards promulgated under Section 6 of the Act, except where alternate/supplemental standards have been approved by the Secretary of Labor and NASA Headquarters. (Requirement 22123) | S | S | S | Safety | |||
| NPR 8715.1 | 3.2.2.1 | 31552 | In developing and submitting alternate standards, NASA shall provide the following information: A statement of why NASA cannot comply with the OSHA standard or wants to adopt an alternate standard. (Requirement 31552) | S | S | S | Safety | |||
| NPR 8715.1 | 3.2.2.2 | 31553 | In developing and submitting alternate standards, NASA shall provide the following information: The proposed alternate standard. (Requirement 31553) | S | S | S | Safety | |||
| NPR 8715.1 | 3.2.2.3 | 31554 | In developing and submitting alternate standards, NASA shall provide the following information: An explanation of how the alternate standard provides equivalent or greater protection for the affected employees. (Requirement 31554) | S | S | S | Safety | |||
| NPR 8715.1 | 3.2.2.4 | 31555 | In developing and submitting alternate standards, NASA shall provide the following information: A description of interim protective measures employed pending approval of the standard. (Requirement 31555) | S | S | S | Safety | |||
| NPR 8715.1 | 3.2.2.5 | 31556 | In developing and submitting alternate standards, NASA shall provide the following information: A written summary of comments, if any, from interested employees, their representatives, or the applicable safety and health committee. (Requirement 31556) | S | S | S | Safety | |||
| NPR 8715.1 | 3.3.2.1 | 31557 | In developing and submitting supplemental standards, NASA shall provide the following information: A statement of why NASA requires the development of the supplemental standard. (Requirement 31557) | S | S | S | Safety | |||
| NPR 8715.1 | 3.3.2.2 | 31558 | In developing and submitting supplemental standards, NASA shall provide the following information: The proposed supplemental standard. (Requirement 31558) | S | S | S | Safety | |||
| NPR 8715.1 | 3.3.2.3 | 31559 | In developing and submitting supplemental standards, NASA shall provide the following information: An explanation of how the supplemental standard provides protection for the affected employees. (Requirement 31559) | S | S | S | Safety | |||
| NPR 8715.1 | 3.3.2.4 | 31560 | In developing and submitting supplemental standards, NASA shall provide the following information: A description of interim protective measures employed pending approval of the standard. (Requirement 31560) | S | S | S | Safety | |||
| NPR 8715.1 | 3.3.2.5 | 31561 | In developing and submitting supplemental standards, NASA shall provide the following information: A written summary of comments, if any, from interested employees, their representatives, or the applicable safety and health committee. (Requirement 31561) | S | S | S | Safety | |||
| NPR 8715.1 | 3.6(1) | 22035 | When it is determined by the Center or program official approving the procurement request, in conjunction with the Center or Component Facility safety and/or health office(s), that NASA safety and/or health standards are required in statements of work, solicitations, and contracts, such standards will be identified and cited for all places where NASA employees work. (Requirement 22160) | S | S | S | Safety | |||
| NPR 8715.1 | 4.1.1(1) | 22037 | Frequency of Inspection: NASA Centers or Component Facilities will establish a formal schedule of inspections for all operations/facilities. All active areas and operations of each establishment shall be inspected at least annually. (Requirement 22037) | S | S | S | Safety | |||
| NPR 8715.1 | 4.1.1(2) | 31562 | Frequency of Inspection: More frequent inspections shall be conducted in all establishments where there is an increased risk of accident, injury, or illness due to the nature of the workplace. (Requirement 31562) | S | S | S | Safety | |||
| NPR 8715.1 | 4.1.2(1) | 22038 | Any facility, structure, operation, vehicle, or equipment that is in an inactive status must be inspected at least annually. (Requirement 22038) | S | S | S | Safety | |||
| NPR 8715.1 | 4.1.2(2) | 31563 | Prior to reactivation, the facility, structure, vehicle, operation, or equipment shall undergo a thorough inspection to identify potential hazards. (Requirement 31563) | S | S | S | Safety | |||
| NPR 8715.1 | 4.1.3 | 22039 | Sufficient unannounced inspections and unannounced follow-up inspections shall be conducted to ensure the identification and abatement of hazardous conditions. (Requirement 22039) | S | S | S | Safety | |||
| NPR 8715.1 | 4.2.1 | 22041 | Qualified inspectors shall conduct inspections. (Requirement 22041) | S | S | S | Safety | |||
| NPR 8715.1 | 4.2.2(1) | 22042 | Safety and health specialists must meet the qualifications as defined in 29 CFR 1960.2 and paragraph 1.2.9 of this NPR. (Requirement 22042) | S | S | S | Safety | |||
| NPR 8715.1 | 4.2.2(2) | 31564 | The Center or Component Facility safety and/or health official(s) shall be responsible for the determination and certification of qualified personnel including those stated in paragraph 1.2.9 of this NPR. (Requirement 31564) | S | S | S | Safety | |||
| NPR 8715.1 | 4.2.3 | 22043 | Inspectors shall have sufficient documented training and experience in safety and health necessary for the recognition, evaluation, and general abatement suggestions/procedures of health and safety hazards. (Requirement 22043) | S | S | S | Safety | |||
| NPR 8715.1 | 4.3.2(1) | 22045 | The supervisor in charge of the establishment, or a person empowered to act for that official, shall undertake immediate abatement, or cease operations and withdraw exposed personnel who are not necessary for abating an imminent danger condition. (Requirement 22045) | S | S | S | Safety | |||
| NPR 8715.1 | 4.3.2(2) | 31565 | In the event the supervisor in charge of the establishment needs assistance to undertake full abatement, that official shall promptly contact the responsible Center officials, who shall assist in the abatement effort. (Requirement 31565) | S | S | S | Safety | |||
| NPR 8715.1 | 4.3.3 | 22046 | Inspection personnel shall be provided the proper support equipment necessary to conduct a thorough inspection of the establishment involved. (Requirement 22046) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.1 | 22048 | Employees are encouraged to report alleged unsafe or unhealthful conditions to the Center or Component Facility safety and/or health official(s). Upon request of the employee, his or her name shall not be disclosed except to the safety and/or health official(s) in connection with the report of a suspected unsafe or unhealthful condition. (Requirement 22048) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.2.a | 31566 | As a minimum the unhealthful conditions file shall contain the following: Date and time received. (Requirement 31566) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.2.b | 31567 | As a minimum the unhealthful conditions file shall contain the following: File number assigned. (Requirement 31567) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.2.c | 31568 | As a minimum the unhealthful conditions file shall contain the following: Location of condition. (Requirement 31568) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.2.d | 31569 | As a minimum the unhealthful conditions file shall contain the following: Description of condition reported. (Requirement 31569) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.2.e | 31570 | As a minimum the unhealthful conditions file shall contain the following: Hazard Classification. (Requirement 31570) | S | S | S | Safety | |||
| NPR 8715.1 | 4.4.2.f | 31571 | As a minimum the unhealthful conditions file shall contain the following: Action taken. (Requirement 31571) | S | S | S | Safety | |||
| NPR 8715.1 | 4.5.1(1) | 22050 | Notice of Unsafe or Unhealthful Conditions: Notice of Unsafe or Unhealthful Condition (NF 1390) or equivalent (any equivalent form must be approved by the DASHO or designee), hereinafter referred to as the notice (See Appendix A for sample), shall be issued not later than 15 days after completion of the inspection for safety violations or not later than 30 days for health violations. (Requirement 22050) | S | S | S | Safety | |||
| NPR 8715.1 | 4.5.1(2) | 31572 | Notice of Unsafe or Unhealthful Conditions: If the notice cannot be issued within the prescribed time period, reasons for the delay must be documented. The hazard will be posted if deemed necessary by the local safety and/or health official(s). (Requirement 31572) | S | S | S | Safety | |||
| NPR 8715.1 | 4.5.2 | 22051 | The notice shall be sent to the supervisor in charge of the establishment for correction (and posting if directed by the safety or health office). (Requirement 22051) Local safety and health office(s) will establish closed-loop procedures to ensure necessary follow-up and correction. | S | S | S | Safety | |||
| NPR 8715.1 | 4.5.3 | 22052 | The supervisor in charge of the establishment shall ensure that a copy of the notice is filed and retained for a period of 5 years after abatement and made available to OSHA or NIOSH officials upon request. (Requirement 22052) (Electronic versions are acceptable for recordkeeping purposes.) | S | S | S | Safety | |||
| NPR 8715.1 | 4.5.4(1) | 22053 | The notice shall indicate the risk assessment for the condition described. (Requirement 22053) | S | S | S | Safety | |||
| NPR 8715.1 | 4.5.4(2) | 31573 | A risk assessment process should be used to analyze and status overall risk potential. The risk assessment/analysis must be accomplished using two elements: Severity and Probability. (Requirement 31573). | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.1.1 | 31575 | Abatement of Unsafe or Unhealthful Conditions: In response to reports of suspected unsafe or unhealthful conditions: For reported imminent danger conditions, immediate notification to their supervisor will be made and employees removed from exposure to the alleged imminent danger condition until an inspection has been made (within 24 hours as required by 29 CFR 1960). (Requirement 31575) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.1.2 | 31576 | Abatement of Unsafe or Unhealthful Conditions: In response to reports of suspected unsafe or unhealthful conditions: Serious conditions - 3 working days. (Requirement 31576) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.1.3 | 31577 | Abatement of Unsafe or Unhealthful Conditions: In response to reports of suspected unsafe or unhealthful conditions: Less than serious conditions (all others) - 20 working days. (Requirement 31577) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.2 | 22055 | Where unsafe or unhealthful conditions are abated immediately upon discovery, the notice shall be noted to that affect and be filed and maintained in accordance with paragraph 4.5 of this NPR. (Requirement 22055) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.3 | 22056 | Where conditions will be abated within 30 calendar days, the notice will so indicate. (Requirement 22056) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.4(1) | 22057 | Where conditions will require more than 30 calendar days to abate, the supervisor in charge of the establishment shall promptly prepare an abatement plan with the appropriate consultation of the establishment`s safety and/or health official(s). (Requirement 22057) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.4(2) | 31578 | The NASA Safety and Health Hazard Abatement Form (NF 1584), or equivalent (any equivalent form must be approved by the DASHO or designee), may be used by NASA Centers or Component Facilities for this purpose. The plan shall contain an explanation of the circumstances of the delay in abatement, a proposed timetable for the abatement, and a summary of steps being taken in the interim to protect employees from being adversely exposed to the unsafe or unhealthful working condition. (Requirement 31578) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.4(3) | 31579 | The NASA Safety and Health Hazard Abatement Form (NF 1584): A copy of the plan shall be sent to the Center safety and health committee and to representatives of the employees. (Requirement 31579) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.4(4) | 31580 | The NASA Safety and Health Hazard Abatement Form (NF 1584): Any changes in an abatement plan will require the preparation of a new plan in accordance with the provisions of this paragraph. (Requirement 31580) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.5(1) | 22058 | When a hazard cannot be abated with the authority and resources of the supervisor in charge of the establishment, that official shall request assistance from the Center Director. (Requirement 22058) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.5(2) | 31582 | When a hazard cannot be abated: The local safety/health official, any established committee and/or employee representatives, and all personnel subject to the hazard shall be advised of this action and of interim protective measures in effect and shall be kept informed of subsequent progress on the abatement plan. (Requirement 31582) | S | S | S | Safety | |||
| NPR 8715.1 | 4.6.7 | 22060 | For those deficiencies that can be rectified within 30 days, written notification by the supervisor in charge of the establishment indicating the corrective action and associated cost, along with verification of proper abatement by the safety and health office(s), is required. (Requirement 22060) (Use NASA Form 1390, "Notice of Unsafe or Unhealthful Conditions," or equivalent (any equivalent form must be approved by the DASHO or designee).) | S | S | S | Safety | |||
| NPR 8715.1 | 4.7(1) | 22061 | Access for OSHA and NIOSH representatives: Official representatives of OSHA and the National Institute of Occupational Safety and Health (NIOSH) are authorized to enter NASA establishments for purposes of inspection and/or evaluation of conditions therein. The NASA DASHO or designee must be notified immediately of any OSHA inspection or visit. (Requirement 22061) | S | S | S | Safety | |||
| NPR 8715.1 | 4.7(2) | 31584 | Access for OSHA and NIOSH representatives: Access to security controlled areas will be coordinated with the Center security officer. Such representatives shall be required to present appropriate identification, receive necessary security clearance, and be escorted during their visits. (Requirement 31584) | S | S | S | Safety | |||
| NPR 8715.1 | 4.7(3) | 31585 | OSHA and NIOSH representatives shall, upon request, be provided available safety and health information on the Center or Component Facility to be visited. (Requirement 31585) | S | S | S | Safety | |||
| NPR 8715.1 | 4.7(4) | 31586 | Upon request, they should also be provided photographic support, if available. Arrangements shall be made for such officials to interview and be accompanied by employees or representatives of employees during their visit. (Requirement 31586) Within 10 working days following written notification of findings of an inspection by OSHA or an evaluation by NIOSH, NASA Centers or Component Facilities will provide a summary of any findings and corrective action necessary to the DASHO. | S | S | S | Safety | |||
| NPR 8715.1 | 5.3(1) | 22065 | Center Executive Safety and Health Board or Equivalent: This committee will be established at each Center. The NASA Center Director or a designee will be the chairperson. Meetings will be scheduled at least semiannually and more often where conditions indicate a need. The purpose of this committee is to provide a forum for meaningful discussion of, and a channel for input to, managements decisions relative to occupational safety and health matters. For these reasons, membership should be broad based and will include representatives of both management and employees. Safety and health, as well as other technical personnel, should be either full members or advisors to the committee and should attend meetings. Agendas shall be prepared in advance and minutes kept and distributed to participants. (Requirement 22065) | S | S | S | Safety | |||
| NPR 8715.1 | 5.3(2) | 31587 | Each committee recommendation shall receive a formal response from management, within 30 days of receipt, as to the disposition of the recommendations and be incorporated in the minutes of subsequent meetings. (Requirement 31587) | S | S | S | Safety | |||
| NPR 8715.1 | 5.3(3) | 31588 | Copies of minutes shall be kept on file for review by Headquarters safety and health offices. (Requirement 31588) | S | S | S | Safety | |||
| NPR 8715.1 | 5.4(1) | 22066 | Subordinate Safety and Health Committees: Special safety and health committees may be formed on an ad hoc or continuing basis in accordance with 29 CFR 1960.38 to assist the NASA Center or Component Facility safety and health officials in dealing with particular programs, projects, geographical areas, or special operations. Committee members chosen for this assignment must receive safety or health training as required. (Requirement 22066) | S | S | S | Safety | |||
| NPR 8715.1 | 5.4(2) | 31589 | Subordinate Safety and Health Committees: NASA Centers or Component Facilities are also encouraged to form supervisor- and employee level safety committees to assist in the implementation of the safety and health programs. Written minutes of each committee meeting shall be maintained and distributed per 29 CFR 1960.37. (Requirement 31589) | S | S | S | Safety | |||
| NPR 8715.1 | 6.2 | 22067 | Center Director Responsibility: The Center Director has the ultimate responsibility to assure that adequate training is provided to personnel in accordance with Federal and NASA requirements. (Requirement 22067) In performance of this responsibility, the Center Director shall: | S | S | S | Safety | |||
| NPR 8715.1 | 6.2.1 | 22142 | Identify safety and health training needs. (Requirement 22142) | S | S | S | Safety | |||
| NPR 8715.1 | 6.2.2 | 22143 | Budget for safety and health training requirements. (Requirement 22144) | S | S | S | Safety | |||
| NPR 8715.1 | 6.2.3 | 22144 | Develop safety and health training courses. (Requirement 22144) | S | S | S | Safety | |||
| NPR 8715.1 | 6.2.4 | 22145 | Maintain training records to reflect employee safety and health training. (Requirement 22145) | S | S | S | Safety | |||
| NPR 8715.1 | 6.3 | 22068 | DASHO Responsibility: The DASHO shall assure that safety and health officials are designated at each appropriate level with sufficient authority and responsibility to plan for and assure funds for safety and health staff, equipment, materials, and training required to ensure implementation of an effective occupational safety and health program. (Requirement 22068) | S | S | S | Safety | |||
| NPR 8715.1 | 6.4.1 | 31590 | Agency Safety and Health Managers: Establishing safety and health training policies and accessing Center or Component Facility performance with OSHA and NASA requirements. (Requirement 31590) | S | S | S | Safety | |||
| NPR 8715.1 | 6.4.2 | 31591 | Agency Safety and Health Managers: Advocating additional training budget needs with the DASHO and OSHEB, based on Center or Component Facility performance evaluations, and/or budget communications. (Requirement 31591) | S | S | S | Safety | |||
| NPR 8715.1 | 6.4.3 | 31592 | Agency Safety and Health Managers: Sponsoring training course development and maintaining a catalog of available training courses to augment Center or Component Facility training programs. (Requirement 31592) | S | S | S | Safety | |||
| NPR 8715.1 | 6.4.4 | 31593 | Agency Safety and Health Managers: Maintaining liaisons with other government and industry training organizations for the purposes of cross fertilization and lessons learned. (Requirement 31593) | S | S | S | Safety | |||
| NPR 8715.1 | 6.5.1 | 31594 | Personnel to be Trained: Appropriate instruction and job-related safety and health training are required for the following employees: Top management officials including program/project managers. (Requirement 31594) | S | S | S | Safety | |||
| NPR 8715.1 | 6.5.2 | 31595 | Personnel to be Trained: Appropriate instruction and job-related safety and health training are required for the following employees: Supervisors. (Requirement 31595) | S | S | S | Safety | |||
| NPR 8715.1 | 6.5.3 | 31596 | Personnel to be Trained: Appropriate instruction and job-related safety and health training are required for the following employees: Safety and health professionals. (Requirement 31596) | S | S | S | Safety | |||
| NPR 8715.1 | 6.5.4 | 31597 | Personnel to be Trained: Appropriate instruction and job-related safety and health training are required for the following employees: Collateral duty safety and health personnel and safety and health committee members. (Requirement 31597) | S | S | S | Safety | |||
| NPR 8715.1 | 6.5.5 | 31598 | Personnel to be Trained: Appropriate instruction and job-related safety and health training are required for the following employees: Employees and employee representatives. (Requirement 31598) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.1 | 31599 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Essential features of the Occupational Safety and Health Act. (Requirement 31599) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.2 | 31600 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Content of Executive Order No. 12196. (Requirement 31600) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.3 | 31601 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: The requirements of 29 CFR Part 1960, "Basic Program Elements for Federal Employee Occupational Safety and Health Programs," and related matters. (Requirement 31601) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.4 | 31602 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: NASAs occupational safety and health policies and program requirements. (Requirement 31602) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.1 | 31604 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Hazards of the job task.(Requirement 31604) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.2 | 31605 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Safe and healthful work practices.(Requirement 31605) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.3 | 31606 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Hazards of the work environment. (Requirement 31606) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.4 | 31607 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Necessity for and proper use and care of personal protective equipment. (Requirement 31607) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.5 | 31608 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Pertinent emergency procedures. (Requirement 31608) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.6 | 31609 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Methods for reporting of mishaps, occupational injuries, illnesses, and hazardous conditions.(Requirement 31609) | S | S | S | Safety | |||
| NPR 8715.1 | 6.6.5.7 | 31610 | Training Course Content: The training program should be structured so as to ensure that the following information be provided to civil servants, as required, for their specific jobs as reflected in paragraph 6.3: Specific job-related information such as: Safety and health standards applicable to the work environment.(Requirement 31610) | S | S | S | Safety | |||
| NPR 8715.1 | 7.2.1 | 22072 | Annual Summary - Occupational Injuries/Illnesses (OSHA Form 102F and 102FF) summarizing the calendar year information will be forwarded to the DASHO or their designee within 30 days following the end of the calendar year. (Requirement 22072) A summary of all open abatement plans and a listing of those closed during the reporting period will also be provided to the DASHO or designee as part of the input to the annual report. | S | S | S | Safety | |||
| NPR 8715.1 | 8.1.1 | 22075 | Institutional/Facility/Operational Safety Audits and Biennial Occupational Health Audits of NASA Center or Component Facility safety and health programs by responsible Headquarters offices will be conducted on a frequency stipulated in their respective policy documents. These audits should provide some basis for input into the NASA self-evaluation review process (see paragram 8.2 of this NPR). (Requirement 22075) | S | S | S | Safety | |||
| NPR 8715.1 | 8.1.2.1 | 31611 | Surveys will include qualitative assessments of the extent to which the Center or Component Facility safety and health programs are: Compliant with NASA policy and procedures. (Requirement 31611) | S | S | S | Safety | |||
| NPR 8715.1 | 8.1.2.2 | 31612 | Surveys will include qualitative assessments of the extent to which the Center or Component Facility safety and health programs are: Compliant with Executive Order 12196 and provisions of 29 CFR Part 1960. (Requirement 31612) | S | S | S | Safety | |||
| NPR 8715.1 | 8.1.2.3 | 31613 | Surveys will include qualitative assessments of the extent to which the Center or Component Facility safety and health programs are: Implemented effectively by the Center or Component Facility. (Requirement 31613) | S | S | S | Safety | |||
| NPR 8715.1 | 8.1.2.4 | 31614 | Surveys will include qualitative assessments of the extent to which the Center or Component Facility safety and health programs are: Consistent with recognized good practice. (Requirement 31614) | S | S | S | Safety | |||
| NPR 8715.1 | 8.2(1) | 22077 | Center Self-Evaluations: Centers or Component Facilities will perform self surveys of their safety and health programs and submit the reports in conjunction with the annual OSHA report (see paragraph 7.2.1 of this NPR). (Requirement 22077) | S | S | S | Safety | |||
| NPR 8715.1 | 8.2(2) | 31615 | Center Self-Evaluations: Centers or Component Faculties shall use the OSHA baseline questionnaire, which is based on 29 CFR 1960 requirements, to perform the self evaluations. (Requirement 31615) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(2) | 31616 | NASA will establish emergency response plans and be prepared to: Protect lives. (Requirement 31616) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(3) | 31617 | NASA will establish emergency response plans and be prepared to: Protect the environment. (Requirement 31617) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(4) | 31618 | NASA will establish emergency response plans and be prepared to: Minimize the loss of, or damage to, NASA resources. (Requirement 31618) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(5) | 31619 | NASA will establish emergency response plans and be prepared to: Provide for the continuous operation or timely resumption of critical services and missions. (Requirement 31619) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(6) | 31620 | NASA will establish emergency response plans and be prepared to: Aid in the recovery and timely resumption of normal operations. (Requirement 31620) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(7) | 31621 | NASA will establish emergency response plans and be prepared to: Assist in mitigating hazards and minimizing the effects of a natural or technological emergency or disaster. (Requirement 31621) | S | S | S | Safety | |||
| NPR 8715.2 | 1.0(8) | 31622 | NASA will establish emergency response plans and be prepared to: Support local, State, and Federal agencies and appropriate emergency response authorities. (Requirement 31622) | S | S | S | Safety | |||
| NPR 8715.2 | 2.1.1 | 23073 | NASA activities take place at different locations, and consequently, potential emergencies may be varied. Site plans for NASA Centers and details on the types of emergencies that each Center within NASA could expect to face are contained in the individual Center Emergency Preparedness Plans. Copies of these plans are on file with the Safety and Assurance Requirements Division and are available for review upon request. (Requirement 23073) | S | S | S | Safety | |||
| NPR 8715.2 | 2.1.2.1 | 23002 | This NPR constitutes the Agency Emergency Preparedness Program Plan and uses the DHS/FEMA format to address unique NASA emergency preparedness concerns. This NPR should be reviewed at least annually and updated as required. (Requirement 23002) | S | S | S | Safety | |||
| NPR 8715.2 | 2.1.2.2(1) | 23003 | NASA Centers (including Component Facilities) shall develop multihazard functional emergency preparedness program plans using the FEMA format. (Requirement 23003) | S | S | S | Safety | |||
| NPR 8715.2 | 2.1.2.2(2) | 31623 | Centers will review plans annually and update them as required. (Requirement 31623) | S | S | S | Safety | |||
| NPR 8715.2 | 2.1.2.2(3) | 31624 | Centers will forward a copy of the emergency preparedness plans, including site maps, to the Office of Security and Program Protection. (Requirement 31624) | S | S | S | Safety | |||
| NPR 8715.2 | 3.1 | 23006 | Office of Security and Program Protection: The Office of Security and Program Protection, NASA Headquarters, will respond to national emergencies and major natural or technological disasters, as requested by NRP. (Requirement 23006) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2 | 23007 | NASA Centers: Each NASA Center shall be prepared to respond to local emergencies and major natural or technological disasters within their confines or at other NASA Centers and to support the appropriate tasking per the NRP. (Requirement 23007) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.1.1(1) | 23008 | The NASA Emergency Preparedness Program Planning Group is responsible for recommending modifications to the NASA emergency preparedness plan. (Requirement 23008) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.1.1(2) | 31625 | The NASA Emergency Preparedness Program Planning Group: This group, chaired by the Office of Safety and Mission Assurance, consists of NASA Emergency Preparedness Coordinators and representatives from Headquarters Codes and Centers. Each NASA Center is responsible for its own emergency plan(s). (Requirement 31625) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.1.2 | 23009 | The Office of Security and Program Protection will coordinate planning and support between NASA Centers. (Requirement 23009) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.2.1 | 31626 | The minimum requirements for exercising emergency plans are as follows: Annual tabletop exercise at the Center level. (Requirement 31626) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.2.2 | 31627 | The minimum requirements for exercising emergency plans are as follows: Annual functional exercise (single scenario) at the Center level. (Requirement 31627) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.2.3 | 31628 | The minimum requirements for exercising emergency plans are as follows: Biennial functional Agencywide exercises (in conjunction with a Center exercise or a Federal emergency exercise as required by the NRP). (Requirement 31628) In the event of an actual emergency, the response may be counted as a fulfillment of the required annual functional exercise. | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.3.1(1) | 23010 | The Assistant Administrator for Security and Program Protection is responsible for the overall management of the NASA Emergency Preparedness Program. (Requirement 23010) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.3.1(2) | 31629 | The Assistant Administrator for Security and Program Protection is responsible for: Each NASA Center Director shall ensure development of that portion of the plan applicable to the mission and needs of the Center and its Component Facilities. (Requirement 31629) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.3.2 | 23011 | When notified of a NASA Center emergency, the Office of Security and Program Protection will activate and operate the NASA Emergency Operations Center (EOC) from the Office of Security and Program Protection , Washington, DC, 20546. (Requirement 23011) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.3.3 | 23012 | When support is requested by DHS/FEMA under the NRP, the Assistant Administrator for Security and Program Protection, or designee, who serves as NASA's representative to the CDRG, will report to the DHS/FEMA Emergency Information and Coordination Center (EICC). The representative shall be the focal point for coordination with the appropriate NASA management to facilitate decisions, problem resolution, and policy issue clarification as required. (Requirement 23012) | S | S | S | Safety | |||
| NPR 8715.2 | 3.2.3.4 | 23013 | Requests for NASA resources beyond the capability of the local NASA Center shall be directed through the NASA EOC for action by the appropriate NASA Mission Directorate Associate Administrators/Headquarters Center Executives (AA/HCEs) . (Requirement 23013) | S | S | S | Safety | |||
| NPR 8715.2 | 3.3 | 23016 | State of Emergency Declaration: After a major natural or technological disaster, the affected Center Director, or designee, shall declare a state of emergency, coordinate with local, State, and Federal agencies, and notify NASA Headquarters, Office of Security and Program Protection during other than normal work hours. (Requirement 23016) The Office of Security and Program Protection will notify the NASA Administrator and appropriate Mission Support and Mission Directorate offices and activate the Headquarters EOC to request and coordinate, as appropriate, assistance from other NASA organizations and Federal agencies. | S | S | S | Safety | |||
| NPR 8715.2 | 4.2 | 23018 | Planning: Each NASA Center shall establish preparedness activities, programs, plans, and systems to ensure readiness and to enhance response to an emergency or disaster. (Requirement 23018) To achieve this goal, each NASA Facility shall develop an emergency plan and procedures that include, but are not limited to, the following: | S | S | S | Safety | |||
| NPR 8715.2 | 4.2.a | 31630 | Planning: Each NASA Center shall establish preparedness activities for the following: Designation of a Center Emergency Preparedness Coordinator. (Requirement 31630) | S | S | S | Safety | |||
| NPR 8715.2 | 4.2.b(1) | 31631 | Planning: Each NASA Center shall establish preparedness activities for the following: Hazard/threat identification and analysis (see Table 4-1). (Requirement 31631) | S | S | S | Safety | |||
| NPR 8715.2 | 4.2.b(2) | 31632 | Planning: Each NASA Center shall establish preparedness activities for the following: NASA Centers will conduct a thorough vulnerability analysis to identify potential hazards/threats. (Requirement 31632) | S | S | S | Safety | |||
| NPR 8715.2 | 4.2.b(3) | 31633 | Planning: Each NASA Center shall establish preparedness activities for the following: Center emergency preparedness programs will include a mitigation component to reduce or eliminate identified risks based on their vulnerability analysis. (Requirement 31633) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3 | 23019 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. (Requirement 23019) These should include, but not be limited to, the following: | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.a | 31634 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Activation of Center emergency response teams. (Requirement 31634) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.b | 31635 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Activation of the Center Emergency Operations Center (EOC) and alternate EOC, if required. (Requirement 31635) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.c | 31636 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Exercises and drills. (Requirement 31636) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.d | 31637 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Use of Incident Command System (ICS) including telecommunications support resources. (Requirement 31637) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.e | 31638 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Coordination with local, State, and Federal agencies. (Requirement 31638) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.f | 31639 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Recall and notification of essential personnel. (Requirement 31639) | S | S | S | Safety | |||
| NPR 8715.2 | 4.3.g | 31640 | Response: Certain emergency response procedures require unique and specialized plans and actions that can be anticipated and preplanned to support the overall response effort. In this regard, each NASA Center Emergency Preparedness Program Plan shall contain procedures and checklists to support specific emergency response activities. These should include, but not be limited to, the following: Damage assessment. (Requirement 31640) | S | S | S | Safety | |||
| NPR 8715.2 | 5 | 23021 | Continuity of Agency Operations: All NASA Center Emergency Preparedness Program Plans shall identify the management succession structure to support the necessary decision making and emergency response activities associated with the Emergency Preparedness Program. (Requirement 23021) Refer to NASA Policy Directive 1000.3, "The NASA Organization," for the Agency management succession during emergencies. | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.01.1 | 23078 | Support Executive Orders 12148 and 12656 and coordinate with the Department of Defense (DoD) to prepare for the use, maintenance, and development of technologically advanced aerospace and aeronautical-related systems, equipment, and methodologies applicable to national security emergencies. (Requirement 23078) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.01.2 | 23023 | Appoint a senior policy official responsible for maintaining an Agency Emergency Preparedness Program that includes objectives, plans, and budgetary requirements. (Requirement 23023) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.01.3 | 23080 | Provide management with the means and the staffing to make the Emergency Preparedness Program Plan operative (i.e., place priority and responsibilities on Headquarters Offices, NASA Centers, and operating locations) to ensure ability to respond to local, national, and international emergencies. (Requirement 23080) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.01.4 | 23081 | Support the Federal Response Plan and maintain a worldwide contingency system through established national and international agreements. (Requirement 23081) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.01.5 | 23082 | Ensure that data/archives records preservation plans are managed in accordance with NPR 1441.1, "NASA Records Retention Schedules," (e.g., collect and store all important records, such as personnel, pay, mission program data, facility engineering design plans/drawings) and provide for assistance to NASA Centers in post disaster recovery of vital records. This activity will be managed by the Chief Information Officer. (Requirement 23082) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.02 | 23024 | The Office of the Chief Financial Officer/Comptroller shall perform the following: (Requirement 23024) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.02.a | 31641 | The Office of the Chief Financial Officer/Comptroller shall perform the following: Provide funding as approved in support of a viable Emergency Preparedness Program. (Requirement 31641) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.02.b | 31642 | The Office of the Chief Financial Officer/Comptroller shall perform the following: Assist and advise on Emergency Preparedness Program budget development. (Requirement 31642) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.02.c | 31643 | The Office of the Chief Financial Officer/Comptroller shall perform the following: Provide interagency funding for supporting exercises and requirements under the Robert T. Stafford Disaster Relief and Emergency Assistance Act. (Requirement 31643) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.02.d | 31644 | The Office of the Chief Financial Officer/Comptroller shall perform the following: Provide systems that will account for emergency preparedness expenditures. (Requirement 31644) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.05.a | 31645 | The Office of Human Capital Management shall perform the following: Establish response procedures for Center Directors to determine personnel leave or personnel pay policies in the event of Center loss or closure. (Requirement 31645) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.05.b | 31646 | The Office of Human Capital Management shall perform the following: Provide the training and education budget for NASA emergency preparedness personnel. (Requirement 31646) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.06.a | 31647 | The Office of the General Counsel shall perform the following: Provide legal advice on compliance with Federal, State, and local laws as applicable to emergency preparedness. (Requirement 31647) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.06.b | 31648 | The Office of the General Counsel shall perform the following: Provide legal advice on NASA interagency agreements, Memoranda of Agreement (MOAs) , and Memoranda of Understanding (MOUs) , with Federal, State, or local agencies. (Requirement 31648) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.06.c | 31649 | The Office of the General Counsel shall perform the following: Provide legal liaison with other Federal agencies assigned NRP responsibilities. (Requirement 31649) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.06.d | 31650 | The Office of the General Counsel shall perform the following: Provide legal review of emergency preparedness program plans and documents, including the NSEP Plan. (Requirement 31650) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.07 | 23029 | The Office of Procurement shall authorize and make available all lawful and otherwise permissible procurement techniques appropriate to the emergency. (Requirement 23029) For example, waiver to the requirements for synopsis, competition, solicitation review, etc., may be used when warranted. | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.a | 31651 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Support the Assistant Administrator for Security and Program Protection, who is designated as the responsible official for national security emergency preparedness program planning and coordination in support of E.O. 12656 and for writing NASAs NSEP Plan (Appendix E). (Requirement 31651) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.b | 31652 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Provide resource management advice and guidance. (Requirement 31652) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.c | 31653 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Coordinate emergency relocation of affected Centers, as required. (Requirement 31653) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.d | 31654 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Review surveys and perform staff-assistance visits. (Requirement 31654) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.e | 31655 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Assist the Office of Security and Program Protection in the identification of Office of Infrastructure, Management, and Headquarters Operations emergency response and recovery capabilities. (Requirement 31655) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.f | 31656 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following:Provide Agency management of physical security assets. (Requirement 31656) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.g | 31657 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Participate, when called upon to support the CDRG, in emergency conditions and exercises. (Requirement 31657) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.h | 31658 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Coordinate postevent Facility recovery and assessment. (Requirement 31658) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.i | 31659 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Manage the Continuity of Government (COG) effort for National security (See Appendix E). (Requirement 31659) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.j(1) | 31660 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Support the NASA Emergency Preparedness Program with respect to environmental regulatory compliance issues. (Requirement 31660) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.j(2) | 31661 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following:Advise and keep NASA Headquarters and Centers aware of current and pending environmental regulations regarding emergency preparedness. (Requirement 31661) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.k | 31662 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following:Maintain the viability of the critical infrastructure in the event of an emergency, as prescribed by Presidential Decision Directive (PDD) 63 using the NASA Critical Infrastructure Protection Plan. (Requirement 31662) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.L | 31663 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Coordinate the planning and implementation of the Critical Infrastructure Protection Plan with the Office of Security and Program Protection and all NASA Center Emergency Preparedness Coordinators. (Requirement 31663) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.m | 31664 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Support the plan, maintaining the viability of the infrastructure in the event of an emergency, as part of the role of the Chief Infrastructure Assurance Officer. (Requirement 31664) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.o | 31665 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Suport the NASA Emergency Preparedness Program and the NRP by responsing to specific tasks as assigned, including requests from DHS/FEMA. (Requirement 31665) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.p | 31666 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Interface with the General Services Administration and idenify the minimum emergency preparedness requirements for Headquarters Offices. (Requirement 31666) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.q | 31667 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Author the Headquarters Center Emergency Preparedness Program Plan. (Requirement 31667) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.r | 31668 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Design and implement the plan for notification and alert of NASA officials during other than normal work hours (See Appendix C). (Requirement 31668) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.s | 31669 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Design and implement the Headquarters Contingency Replcation Plan to provide for the relocation of selected portions of NASA Headquarters in the event that Headquarters facilities are no longer useable (See Appendix D). (Requirement 31669) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.08.t | 31670 | The Office of Infrastructure, Management, and Headquarters Operations shall perform the following: Exercise the NASA Headquarters relocation activity portion of the NASA Security Emergency Preparedness (NSEP) Plan. (Requirement 31670) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.09 | 23031 | The Office of Small and Disadvantaged Business Utilization shall provide assistance in the award of emergency procurement contracts through the use of small and disadvantaged business entities. (Requirement 23031) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.10.a | 31674 | The Office of Legislative Affairs shall perform the following: Support the NASA Emergency Preparedness Program at the appropriate legislative level. (Requirement 31674) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.10.b | 31675 | The Office of Legislative Affairs shall perform the following: Advise and keep NASA Headquarters and Centers aware of current and pending legislation regarding emergency preparedness. (Requirement 31675) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.a | 31676 | The Space Operations Mission Directorate shall perform the following: Support each NASA Center in emergency preparedness when called upon for special resource capabilities. (Requirement 31676) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.b | 31677 | The Space Operations Mission Directorate shall perform the following: Update annually and report status of the resources available to support the NASA Emergency Preparedness Program. This is to specifically address NASAs mission-critical operational flight programs and communications. (Requirement 31677) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.c | 31678 | The Space Operations Mission Directorate shall perform the following: In coordination with the NASA Administrator, respond to appropriate Executive Branch Secretary requests levied on NASA programs for NSEP technical or flight program support resources when national security situations develop beyond the scope of the NASA Emergency Preparedness Program Plan. In such cases, the Space Operations Mission Directorate-managed resources may be handled outside the provisions of the Plan. (Requirement 31678) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.d | 31679 | The Space Operations Mission Directorate shall perform the following: Fund the Emergency Preparedness Program at Johnson Space Center, Kennedy Space Center, Marshall Space Flight Center, and Stennis Space Center, including Component Facilities. (Requirement 31679) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.e | 31680 | The Space Operations Mission Directorate shall perform the following: Appoint an emergency preparedness representative to serve as a liaison to the Office of Security and Program Protection EOC as dictated by the magnitude of the emergency. (Requirement 31680) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.f | 31681 | The Space Operations Mission Directorate shall perform the following: Respond to requests from DHS/FEMA, with Office of Security and Program Protection coordination. (Requirement 31681) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.g | 31682 | The Space Operations Mission Directorate shall perform the following: Support reconnaissance and damage assessment and reporting to the Office of Security and Program Protection. (Requirement 31682) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.h | 31683 | The Space Operations Mission Directorate shall perform the following: Identify NSEP assets and response capabilities for the Office of Security and Program Protection. (Requirement 31683) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.i | 31684 | The Space Operations Mission Directorate shall perform the following: Appoint a senior NASA official to coordinate telecommunications policy with the Office of the Manager, National Communications System, in accordance with E.O. 12472 and the NASA MOU. (Requirement 31684) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.j | 31685 | The Space Operations Mission Directorate shall perform the following: Support Federal and Agency NSEP telecommunications mobilization under national emergency conditions declared by the President or other competent Federal authority, e.g., pursuant to E.O. 12656 and National Security Decision Directives 47 and 97. (Requirement 31685) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.k | 31686 | The Space Operations Mission Directorate shall perform the following: Ensure that NASAs terrestrial and space-borne spectrum-dependent telecommunications systems are properly licensed under national and international radio frequency rules and regulations. (Requirement 31686) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.L | 31687 | The Space Operations Mission Directorate shall perform the following: Authorize controlled-access interfaces to automated information systems, i.e., those telecommunications and computing networks or systems under the Space Operations Mission Directorate's cognizance, during national or regional emergencies. (Requirement 31687) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.m | 31688 | The Space Operations Mission Directorate shall perform the following: Provide technical assistance and consultation to the Office of Security and Program Protection and others on contingency or emergency administrative telecommunications requirements that may be required and approved to support the NASA Emergency Preparedness Program. (Requirement 31688) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.n | 31689 | The Space Operations Mission Directorate shall perform the following: Fund national or NASAs NSEP telecommunications services or initiatives. According to E.O. 12472, Office of Management and Budget (OMB) guidance, this is to include special procurements or other arrangements between the Space Operations Mission Directorate, the Office of Security and Program Protection, and other appropriate NASA Headquarters Offices having institutional responsibilities. (Requirement 31689) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.o | 31690 | The Space Operations Mission Directorate shall perform the following: Identify, for the Office of Security and Program Protection, all NSEP telecommunications assets funded and managed by the Space Operations Mission Directorate. As appropriate and available, participate in NASA and national-level (sponsored by the DoD/National Communications System/FEMA) exercises to respond to an actual emergency or disaster. (Requirement 31690) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.p | 31691 | The Space Operations Mission Directorate shall perform the following: Provide, where appropriate and compatible, controlled-access interface with Space Operations Mission Directorate-managed telecommunications, tracking, and computing resources during national, international, and/or regional NSEP emergencies declared by the President. (Requirement 31691) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.q | 31692 | The Space Operations Mission Directorate shall perform the following: Support NASAs mission-critical flight (including aeronautics) programs and NASA's emergency essential functions in accordance with the Space Operations Mission Directorate charter and agreements and/or MOUs with other Federal agencies. (Requirement 31692) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.r | 31693 | The Space Operations Mission Directorate shall perform the following: Provide support to each continental United States-based space flight tracking installation. (Requirement 31693) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.s | 31694 | The Space Operations Mission Directorate shall perform the following: Provide support to foreign space flight tracking installations pursuant to provisions of MOAs with host countries. (Requirement 31694) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.11.t | 31695 | The Space Operations Mission Directorate shall perform the following: Support Emergency Preparedness Program funding for nationally and internationally located facilities or sites. (Requirement 31695) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.a | 31696 | The Office of Public Affairs shall perform the following: Function as the single Agency spokesperson to all external resources/personnel. (Requirement 31696) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.b.1) | 31698 | The Office of Public Affairs shall perform the following: Act as liaison with the media to accomplish the following: Provide pre-event coordination, if possible., (Requirement 31698) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.b.2) | 31699 | The Office of Public Affairs shall perform the following: Act as liaison with the media to accomplish the following: Establish and operate an emergency news center, (Requirement 31699) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.b.3) | 31700 | The Office of Public Affairs shall perform the following: Act as liaison with the media to accomplish the following: Provide timely and accurate information to the news media. (Requirement 31700) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.b.4) | 31701 | The Office of Public Affairs shall perform the following: Act as liaison with the media to accomplish the following: Provide escort as required; coordinate press releases with Headquarters and Centers., (Requirement 31701) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.b.5) | 31702 | The Office of Public Affairs shall perform the following: Act as liaison with the media to accomplish the following: Coordinate procedures for contact to national media agencies, (Requirement 31702) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.b.6) | 31703 | The Office of Public Affairs shall perform the following: Prrepare postevent articles and press releases. | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.c | 31704 | The Office of Public Affairs shall perform the following: Provide coordination for the utilization of the Emergency Broadcast System. (Requirement 31704) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.d | 31705 | The Office of Public Affairs shall perform the following: Provide public affairs support for emergency preparedness awareness. (Requirement 31705) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.e | 31706 | The Office of Public Affairs shall perform the following: Provide public affairs support to the CDRG. (Requirement 31706) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.12.f | 31707 | The Office of Public Affairs shall perform the following: Appoint a public affairs representative to serve as a liaison to the Office of Security and Program Protection EOC as dictated by the magnitude of emergency. (Requirement 31707) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.a | 23037 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Define emergency preparedness management structure, i.e., Center to Headquarters (flow chart). (Requirement 23037) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.b | 31708 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Identify minimal Center emergency response capability. (Requirement 31708) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.c | 31709 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Coordinate support with Federal agencies. (Requirement 31709) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.d | 31710 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Provide support to CDRG. (Requirement 31710) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.e | 31711 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Endorse the use of the Incident Command System (ICS) for emergency responses throughout NASA. (Requirement 31711) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.f | 31712 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Activate the EOC as needed. Generally, the EOC is activated any time two or more emergency response elements are employed. (Requirement 31712) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.g | 31713 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Monitor NASA Center agreements and plans as related to emergency preparedness. (Requirement 31713) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.h | 31714 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Develop an Agency top-level Emergency Preparedness Program, that complies with Federal requirements, for NASA Center use. (Requirement 31714) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.i | 31715 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Provide emergency preparedness and response advice to the NASA Administrator. (Requirement 31715) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.j | 31716 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Provide guidance to all NASA offices for operation of the Emergency Preparedness Program. (Requirement 31716) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.k | 31717 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Provide guidance for tasks received by NASA offices and Centers from DHS/FEMA and other Federal agencies. (Requirement 31717) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.L | 31718 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Provide advocacy for budget items. (Requirement 31718) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.m | 31719 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Determine the need for, and if necessary advocate, the acquisition of specialized computer software to develop Emergency Preparedness Program Plans, annexes, and exercises. (Requirement 31719) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.n | 31720 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Conduct reviews of each Center and its Emergency Preparedness Program Plan at least biennially. (Requirement 31720) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.o | 31721 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Conduct an emergency preparedness coordinators meeting at least annually (rotated among all NASA Centers). (Requirement 31721) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.p | 31722 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Provide or recommend training for assigned emergency preparedness coordinators. (Requirement 31722) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.q | 31723 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Review after-action Agency investigative reports and lessons learned. (Requirement 31723) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.r | 31724 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Review damage assessment and prioritization of recovery actions. (Requirement 31724) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.13.2.s | 31725 | Assistant Administrator for Security and Program Protection: The NASA Emergency Preparedness Coordinator shall perform the following: Serve as the NASA point of contact to DHS/FEMA at the Headquarters level for the National Response Plan and all related FEMA matters. (Requirement 31725) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.a | 31726 | Aeronautics research Mission Directorate shall perform the following: Respond to requests from the Office of Security and Program Protection in support of the NASA Emergency Preparedness Program. (Requirement 31726) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.b | 31727 | Aeronautics research Mission Directorate shall perform the following: Provide support to each NASA Center in performing emergency preparedness. (Requirement 31727) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.c | 31728 | Aeronautics research Mission Directorate shall perform the following: Provide the Office of Security and Program Protection an annual status report on the resources available to support the NASA Emergency Preparedness Program. (Requirement 31728) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.d | 31729 | Aeronautics research Mission Directorate shall perform the following: Provide resources for the Emergency Preparedness Program at Ames Research Center, Langley Research Center, and Glenn Research Center, including all Component Facilities. (Requirement 31729) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.e | 31730 | Aeronautics research Mission Directorate shall perform the following: Respond, through the Agency emergency management structure, to requests from DHS/FEMA. (Requirement 31730) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.f | 31731 | Aeronautics research Mission Directorate shall perform the following: Support the NASA Emergency Preparedness Program with resources (reconnaissance and research). (Requirement 31731) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.g | 31732 | Aeronautics research Mission Directorate shall perform the following: Identify, for the Office of Security and Program Protection, all NSEP assets and response capabilities. (Requirement 31732) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.14.h | 31733 | Aeronautics research Mission Directorate shall perform the following: Appoint an emergency preparedness person to serve as a liaison to the Office of Security and Program Protection EOC as dictated by the scope of emergency. (Requirement 31733) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.a | 31734 | The Science Mission Directorate shall perform the following: Support emergency planning efforts, including preservation of mission essential resources. (Requirement 31734) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.b | 31735 | The Science Mission Directorate shall perform the following: Establish minimum levels for the effective operation of sensitive NASA systems during emergency operations or contingencies. (Requirement 31735) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.c | 31736 | The Science Mission Directorate shall perform the following: Provide support to each NASA Center in performing emergency preparedness. (Requirement 31736) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.d | 31737 | The Science Mission Directorate shall perform the following: Provide to the Office of Security and Program Protection an annual status report on the resources available to support the NASA Emergency Preparedness Program. (Requirement 31737) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.e | 31738 | The Science Mission Directorate shall perform the following: Provide resources for the Emergency Preparedness Program at Ames Research Center, Goddard Space Flight Center, and JPL and Component Facilities. (Requirement 31738) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.f | 31739 | The Science Mission Directorate shall perform the following: Respond, through the Agency emergency management structure, to requests from DHS/FEMA. (Requirement 31739) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.g | 31740 | The Science Mission Directorate shall perform the following: Serve as the focal point for all Science Mission Directorate programs responsible for consolidating and coordinating technical reconnaissance requests. (Requirement 31740) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.h | 31741 | The Science Mission Directorate shall perform the following: Advise the Office of Security and Program Protection and update annually the technical reconnaissance resources available to support the Emergency Preparedness Program. (Requirement 31741) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.i | 31742 | The Science Mission Directorate shall perform the following: Identify for the Office of Security and Program Protection all NSEP assets and response capabilities. (Requirement 31742) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.j | 31743 | The Science Mission Directorate shall perform the following: Appoint an emergency preparedness person to serve as a liaison to the Office of Security and Program Protection EOC as dictated by the magnitude of emergency. (Requirement 31743) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.15.k | 34526 | Upon activation of the Office of Security and Program Protection EOC, apply available Earth observing assets to provide technical reconnaissance to NASA Centers in Need of Damage Assessment. (Requirement 90000) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.a | 31744 | The Chief Health and Medical Officer shall perform the following: Provide support to Centers in emergency preparation matters. (Requirement 31744) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.b | 31745 | The Chief Health and Medical Officer shall perform the following: Respond to requests from the Agency emergency management structure in support of the NASA Emergency Response Program. (Requirement 31745) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.c | 31746 | The Chief Health and Medical Officer shall perform the following: Participate as a member of the Headquarters EOC as warranted. (Requirement 31746) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.d | 31747 | The Chief Health and Medical Officer shall perform the following: Provide support as needed to the CDRG in emergency conditions and exercises. (Requirement 31747) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.e | 31748 | The Chief Health and Medical Officer shall perform the following: Provide training as needed in medical and environmental health topics pertinent to emergency response. (Requirement 31748) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.f | 31749 | The Chief Health and Medical Officer shall perform the following: Review investigative reports and lessons learned relative to emergencies with medical/health implications. (Requirement 31749) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.g | 31750 | The Chief Health and Medical Officer shall perform the following: Respond to DHS/FEMA requests for support via the NASA emergency management structure. (Requirement 31750) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.h | 31751 | The Chief Health and Medical Officer shall perform the following: Provide medical response, follow-up surveillance, and support to recognize, evaluate, and control potential health hazards. (Requirement 31751) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.i | 31752 | The Chief Health and Medical Officer shall perform the following: Coordinate emergency support using NASA telemedicine, informatics, and other appropriate technological capabilities. (Requirement 31752) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j | 31753 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. (Requirement 31753) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.1) | 31754 | The Chief Health and Medical Officer: Provide emergency response-related support through occupational health programs. This includes the following: Hazard communication; (Requirement 31754) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.2) | 31755 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Respiratory protection; (Requirement 31755) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.3) | 31756 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Provision of toxicological and medical information; (Requirement 31756) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.4) | 31757 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Material Safety Data Sheets (MSDS); (Requirement 31757) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.5) | 31758 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Medical response/follow-up surveillance of exposed personnel; (Requirement 31758) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.6) | 31759 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Recognition, evaluation, and control of potential health hazards; (Requirement 31759) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.7) | 31760 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Provision of training in pertinent topics (respiratory protection, lead mitigation, ventilation, bloodborne pathogens, emergency medical care, indoor air quality, etc.); (Requirement 31760) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.8) | 31761 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Distribution of alerts regarding disasters and preventive/remedial measures; (Requirement 31761) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.16.j.9) | 31762 | The Chief Health and Medical Officer shall perform the following: Provide emergency response-related support through occupational health programs. This includes the following: Critical incident stress syndrome and other emotional/mental health training and counseling for disaster workers and victims as required. (Requirement 31762) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.17.a | 31763 | Office of Earth Science shall perform the following: Support the NASA Emergency Preparedness Program and the NRP by responding to specific tasks from DHS/FEMA through the NASA emergency management structure. (Requirement 31763) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.17.b | 31764 | Office of Earth Science shall perform the following: Appoint an emergency preparedness representative to serve as a liaison to the Office of Safety and Mission Assurance EOC as dictated by the magnitude of emergency. (Requirement 31764) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.17.c | 31765 | Office of Earth Science shall perform the following: Provide resources for the Emergency Preparedness Program at Office of Earth Science Centers. (Requirement 31765) | S | S | S | Safety | |||
| NPR 8715.2 | 6.1.17.d | 31766 | Office of Earth Science shall perform the following: Upon activation of the Office of Safety and Mission Assurance EOC, apply available earth observing assets to provide technical reconnaissance to NASA Centers in need of damage assessment. (Requirement 31766) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.a(1) | 31767 | Center Directors or designees shall perform the following: Manage the program to - Ensure that all applicable individuals are properly trained to meet Federal regulatory requirements related to the emergency preparedness authorities and directives listed in Appendix A and subsequent Presidential Executive Orders or Directives. (Requirement 31767) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.a(2) | 31768 | Center Directors or designees shall perform the following: Manage the program to - Centers may use on-line systems for training and documenting training but not for the actual plan or checklists unless the systems are protected by firewalls. Plans and checklists are to be considered "For Official Use Only" and not placed on open systems. (Requirement 31768) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.b | 31769 | Center Directors or designees shall perform the following: Manage the program to - Ensure the program is visible within the organization. (Requirement 31769) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.c | 31770 | Center Directors or designees shall perform the following: Manage the program to - Provide a single point of contact for emergency preparedness to develop and coordinate the Center Emergency Preparedness Program Plan and conduct exercises. (Requirement 31770) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.d | 31771 | Center Directors or designees shall perform the following: Manage the program to - Establish an EOC and an alternate EOC. (Requirement 31771) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.e | 31772 | Center Directors or designees shall perform the following: Manage the program to - Establish a Center Emergency Preparedness Program Planning Group to assist in Center emergency preparedness program planning and in developing EOC operational procedures. (Requirement 31772) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.f | 31773 | Center Directors or designees shall perform the following: Manage the program to - Ensure that an emergency response capability exists. (Requirement 31773) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.1.g | 31774 | Center Directors or designees shall perform the following: Manage the program to - Ensure the Center Emergency Preparedness Program Plan addresses required reporting of hazardous material releases to regulating authorities. (Requirement 31774) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.a | 31776 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Establish separate checklists and plans to cope with each known contingency. (Requirement 31776) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.b | 31777 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Establish checklists and plans to support emergency response activities. (Requirement 31777) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.c | 31778 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Identify parameters and levels for emergency response contingencies. (Requirement 31778) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.d | 31779 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Establish and maintain environmental contact lists for various types of hazardous materials and waste spills. (Requirement 31779) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.e | 31780 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Establish and maintain resource lists including local data and telecommunications networks. (Requirement 31780) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.f | 31781 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Assess potential hazardous materials exposures and potential health effects of facility operations that have a potential for a significant emergency situation. (Requirement 31781) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.2.g | 31782 | Center Directors or designees shall perform the following: Provide program planning and response capability to - Correct/abate controllable threats/hazards that could result in an emergency situation. (Requirement 31782) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.a | 31783 | Center Directors or designees shall perform the following: Conduct program reviews to - Ensure all offices are involved in Center emergency preparedness program development: (Requirement 31783) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.a.(1) | 31784 | Center Directors or designees shall perform the following: Conduct program reviews to - Ensure all offices are involved in Center emergency preparedness program development: It is the responsibility of NASA Centers to ensure the operability of critical telecommunications and/or information system assets under emergency conditions, including the provision of backup power generation and other utility services; (Requirement 31784) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.a.(2) | 31785 | Center Directors or designees shall perform the following: Conduct program reviews to - Ensure all offices are involved in Center emergency preparedness program development: NASA Headquarters Mission Directorates/Headquarters Center Executives will verify the adequacy of alternative Center Utility Plan(s). (Requirement 31785) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.b | 31786 | Center Directors or designees shall perform the following: Conduct program reviews to - Ensure local hazards/threat analyses specific to the Center are reviewed annually and updated as appropriate. (Requirement 31786) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.c | 31787 | Center Directors or designees shall perform the following: Conduct program reviews to - Ensure annual reviews of emergency preparedness and emergency response procedures are current and provide copies to the Office of Security and Program Protection. The format for this report is provided annually by the Office of Security and Program Protection. (Requirement 31787) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.d | 31788 | Center Directors or designees shall perform the following: Conduct program reviews to - Provide annual Center emergency preparedness program status reports to the Office of Security and Program Protection. (Requirement 31788) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.3.e | 31789 | Center Directors or designees shall perform the following: Conduct program reviews to - Ensure all elements of the Center emergency preparedness program (personnel, facilities, equipment, response teams, etc.) are capable of performing assigned tasks. (Requirement 31789) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.4.a | 31790 | Center Directors or designees shall perform the following: Oversee the emergency preparedness program budget to - Define budget requirements for Center programs. (Requirement 31790) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.4.b | 31791 | Center Directors or designees shall perform the following: Oversee the emergency preparedness program budget to - Ensure that appropriate resources, personnel, and funding are sufficient for the Center emergency preparedness program. (Requirement 31791) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5 | 23047 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. (Requirement 23047) This includes the following: | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.a | 31792 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Provide funding to conduct ongoing training for all personnel involved in the Center emergency preparedness program. (Requirement 31792) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.b | 31793 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Identify training requirements and develop a training plan to support contingencies. (Requirement 31793) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.c(1) | 31794 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Identify and train essential personnel and response teams. (Requirement 31794) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.c(2) | 31795 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Keep a list of essential personnel as a vital record. (Requirement 31795) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.d | 31796 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Establish an exercise design/evaluation group and conduct exercise and post-exercise critiques. (Requirement 31796) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.e | 31797 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Conduct and document drills and exercises. (Requirement 31797) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.5.f | 31798 | Center Directors or designees shall perform the following: Monitor the emergency preparedness training. This includes the following: Participate in practice drills with local governments and agencies on an as-requested basis. (Requirement 31798) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.a | 31799 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Adopt and implement the Incident Command System at the Center. (Requirement 31799) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.b | 31800 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Provide public address and emergency warning systems/alerts per 29 CFR 1910.165. (Requirement 31800) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.c | 31801 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Ensure an effective communications capability exists in the EOC. (Requirement 31801) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.d | 31802 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Respond to medical emergencies and provide medical surveillance. (Requirement 31802) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.e | 31803 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Develop and maintain 24-hour communications capability: (1) During Normal Work Hours - 0730 - 1630 (Eastern Time) , Centers will notify the Office of Security and Program Protection; (2) During Other Than Normal Work Hours -1630 - 0730 (Eastern Time) , all day weekends and holidays, calls are to be made to the NASA Headquarters Security Console at phone: 202-358-0541 (nonemergency) , 1-866-230-NASA (1-866-230-6272) (emergency) , or fax: 202-358-3382. (Requirement 31803) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.f | 31804 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Secure vital and classified records in accordance with the appropriate NASA policies. (Requirement 31804) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.6.g | 31805 | Center Directors or designees shall perform the following: Review emergency response capability. This includes the following: Provide organization chart and current rosters of essential points of contact to the Office of Security and Program Protection. (Requirement 31805) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.a | 31806 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Coordinate development of contingency/recovery plans for critical services and missions. (Requirement 31806) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.b | 31807 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Establish criteria for reporting damage assessments and forward assessment to the Office of Security and Program Protection, the Office of Infrastructure, Management, and Headquarters Operations, and appropriate Mission Directorate and Mission Support Assistant/Associate Administrators. (Requirement 31807) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.c | 31808 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Establish criteria for obtaining the resources necessary to recover from an emergency situation. (Requirement 31808) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.d | 31809 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Develop and implement mutual aid procedures with DoD, local, State, and Federal agencies and the appropriate emergency response authorities. (Requirement 31809) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.e | 31810 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Prioritize post event damage assessment and immediate facility dispositions (i.e. restore, shutdown or vacate, or ignore) (Requirement 31810). | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.f | 31811 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Establish a damage assessment team. (Requirement 31811) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.g | 31812 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Provide preincident preparations and post incident critiques and after-actions reports. (Requirement 31812) | S | S | S | Safety | |||
| NPR 8715.2 | 6.2.7.h | 31813 | Center Directors or designees shall perform the following: Perform damage assessment and recovery. This includes the following: Comply with OMB requirements for reports and accounting. (Requirement 31813) See OMB Circular A-12. | S | S | S | Safety | |||
| NPR 8715.2 | 7 | 23050 | Center Emergency Preparedness Program Plans: The following standardized functional annexes shall be included in NASA Center Emergency Preparedness Program Plans: (Requirement 23050) a.) Annex A - Direction and Control; (b.) Annex B - Communications; (c.) Annex C - Warning/Alerting; (d.) Annex D - Emergency Public Affairs; (e.) Annex E - Evacuation; (f.) Annex F - Reception and Care; (g.) Annex G - Sheltering; (h.) Annex H - Health and Medical; (i.) Annex I - Security; (j.) Annex J - Facilities; (k.) Annex K - Fire and Rescue; (l.) Annex L - Radiological Defense; (m.) Annex M - Human Services; (n.) Annex N - Transportation; (o.) Annex O - Damage Assessment; (p.) Annex P - Search and Rescue; (q.) Annex Q - Hazardous Materials Response; (r.) Annex R - Emergency Operations Center; (s.) Annex S - Utilities Control; (t.) Annex T - MOU's, MOA's, and Joint Operating Procedures; (u.) Annex U - National Security Emergency Preparedness Plan. (This annex is applicable to all NASA Facilities when activated by the NASA Administrator or designee.) Each NASA Center will expand requirements of the NASA National Security Emergency Preparedness Plan (Appendix E of this NPR) to meet the Center's NSEP requirements. | S | S | S | Safety | |||
| NPR 8715.3C | 02.2.1 | 45818 | System Safety: Institutional Roles and Responsibilities: Mission Directorate Associated Administrators, Center Directors, program and project managers, and line managers shall ensure that system safety activities are conducted for all programs and projects including system acquisistions, in-house developments (research and technology), design, construction, fabrication and manufacture, experimentation and test, packaging and transportation, storage, checkout, launch, flight, reentry, retrieval and disassembly, maintenance and refurbishment, modification, and disposal. (Requirement 45818) | S | S | S | Mgmt | |||
| NPR 8715.3C | 03.10.1 | 46107 | Operational Safety: Lifting Safety: Center Directors and project managers shall comply with NASA-STD-8719.9, Standard for Lifting Devices and Equipment, for protecting persons and property during lifting operations. (Requirement 46107) Note: This standard established minimum safety requirements for the design, testing, inspection, personnel certification, maintenance, and use of overhead and gantry cranes, mobile cranes, derricks, hoists, special hoist-supported personnel lifting devices, hydrasets, hooks, mobile aerial platforms, power industrial trucks, jacks, and slings for NASA-owned and NASA contractor-supplied equipment used in support of NASA operations at NASA Centers. | S | S | S | Safety | |||
| NPR 8715.3C | 03.11.1 | 46109 | Operational Safety: Explosive, Propellant, and Pyrotechnic Safety: Center Directors and project managers shall use NSS 1740.12, Safety Standard for Explosives, Propellants, and Pyrotechnics, for protecting personnel and property from hazards of explosives and explosive materials, including all types of explosives, propellants (liquid and solid), oxidizers, and pyrotechnics. (Requirement 46109) Note: ASTM Manual 36, Safe Use of Oxygen and Oxygen Systems, addresses the requirements for working with explosive, propellant, and pyrotechnic substances. | S | S | S | Safety | |||
| NPR 8715.3C | 03.11.2 | 46110 | Operational Safety: Explosive, Propellant, and Pyrotechnic Safety: Center Directors and project managers shall ensure that explosive, propellant, and pyrotechnic operations are conducted in a manner that exposes the minimum number of people to the smallest quantity of explosives for the shortest period consistent with the operation being conducted. (Requirement 46110) | S | S | S | Safety | |||
| NPR 8715.3C | 03.12.2 | 46130 | Operational Safety: Underwater Operations Safety: Center Directors and project managers shall use NSS/WS 1740.10, NASA Safety Standard for Underwater Facility and Non-Open Water Operations, as the minimum standard to establish the safety requirements for all NASA neutral buoyancy facilities, equipment, personnel, and operations involving underwater activities including the simulation of a weightless environment. (Requirement 46130) Note: This standard also applies to NASA personnel participating in underwater operations at non-NASA facilities. | S | S | S | Safety | |||
| NPR 8715.3C | 03.15.4.c | 46234 | Operational Safety: Non-Ionizing Radiation: Center Directors and project managers shall ensure that: Laser operations during any open-air laser scenario conducted on DoD-controlled ranges or test facilities or by DoD personnel use the Range Commanders Council Document 316-91, Laser Range Safety. (Requirement 46234) | S | S | S | Safety | |||
| NPR 8715.3C | 03.15.4.g | 46238 | Operational Safety: Non-Ionizing Radiation: Center Directors and project managers shall ensure that: Any laser that can cause injury or damage has a Center-approved safety documentation, test plan, and test procedure review. (Requirement 46238) | S | S | S | Safety | |||
| NPR 8715.3C | 03.17.5 | 46280 | Operational Safety: Confined Spaces: Supervisor shall have the overall responsibility for entry and work in condined spaces and ensure compliance with ANSI Z117.1, Safety Requirements for Confined Space, and the NIOSH Publication No. 87-113, A Guide to Safety in Confined Space. (Requirement 46280) Note: Permit requirements for confined spaces are given in 29 CFR 1910.146, Permit-Required Confined Spaces. | S | S | S | Safety | |||
| NPR 8715.3C | 09.2.1 | 46666 | Safety and Risk Management for NASA Contracts: Applicability and Scope: When NASA activities include contractor involvement, Center Directors and project managers shall include contractors in the NASA Safety Program. (Requirement 46666) | S | S | S | Safety | |||
| NPR 8715.3C | 09.2.2 | 46667 | Safety and Risk Management for NASA Contracts: Applicability and Scope: Center SMA Directors, project managers, COs, and COTRs shall ensure that NASA contracts are written to hold contractors accountable for the safety of their employees, their services, their products, and for complying with NASA and Center safety requirements. (Requirement 46667) | S | S | S | Safety | |||
| NSS-1740.12 | 0 | 57093 | NASA Safety Standard 1740.12 is represented by this single entry. If this entry is being viewed from a filter, list, or traceability report, then the metadata applies to the document as a whole. | S | S | S | Safety | |||
| CxP 70059 | 2.6 | SAF-1034 | NPR 7120.5D | 4.4.2.c.09 | 55742 | Program and Project Requirements by Phase: Projects - Phase A: Requirements: During Phase A, the Project Manager and project team shall: Perform project planning, costing, and scheduling activities: Develop a Nuclear Safety Launch Approval Plan (for mission with nuclear materials) in accordance with NPR 8715.3, NASA General Safety Program Requirements. (Requirement 55742) | E | N | N | Mgmt |
| NPR 8715.3C | 06.2.4.a | 46409 | Nuclear Safety for Launching of Radioactive Materials: Responsibilities: Mission Directorate Associate Administrators and program executives shall: Designate an individual responsible for ensuring the implementation of the requirements for nuclear launch safety approval in accordance with paragraph 9 of PD/NSC-25. (Requirement 46409) | S | Y | Y | Safety | |||
| NPR 8715.3C | 06.2.4.b | 46410 | Nuclear Safety for Launching of Radioactive Materials: Responsibilities: Mission Directorate Associate Administrators and program executives shall: Notify the NASA Headquarters NFSAM, in writing, as soon as radioactive sources are identified for potential use on NASA spacecraft to schedule nuclear launch safety approval activities. (Requirement 46410) | S | Y | Y | Safety | |||
| CxP 70059 | 3.1 | RMS-1 | NPD 8720.1B | 1.a.(3) | 13015 | It is NASA policy for: Plan, establish, document, and implement-- Requirements and tasks for Reliability and Maintainability engineering, analysis, and testing (including hardware, software, firmware, and human elements). (Requirement 13015) | S | Y | Y | RMS |
| NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS | |||
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| CxP 70059 | 3.1.1 | RMS-2 | NPD 8720.1B | 1.a.(1) | 13014 | It is NASA policy for: Plan, establish, document, and implement-- System Reliability and Maintainability design and operational performance requirements (qualitative and quantitative). (Requirement 13014) | S | Y | Y | RMS |
| CxP 70059 | 3.1.2 | RMS-118 | NPD 8720.1B | 1.a.(4) | 13016 | It is NASA policy for: Plan, establish, document, and implement-- Timely and continuous assessment of the progress toward achieving the Reliability and Maintainability requirements, including identification of areas for improvement. (Requirement 13016) | S | Y | Y | RMS |
| RMS-3 | NPD 8720.1B | 1.a.(1) | 13014 | It is NASA policy for: Plan, establish, document, and implement-- System Reliability and Maintainability design and operational performance requirements (qualitative and quantitative). (Requirement 13014) | S | Y | Y | RMS | ||
| NPD 8720.1B | 1.a.(3) | 13015 | It is NASA policy for: Plan, establish, document, and implement-- Requirements and tasks for Reliability and Maintainability engineering, analysis, and testing (including hardware, software, firmware, and human elements). (Requirement 13015) | S | Y | Y | RMS | |||
| CxP 70059 | 3.1.3 | RMS-6 | NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS |
| CxP 70059 | 3.1.4 | RMS-10 | NPD 8720.1B | 1.a.(4) | 13016 | It is NASA policy for: Plan, establish, document, and implement-- Timely and continuous assessment of the progress toward achieving the Reliability and Maintainability requirements, including identification of areas for improvement. (Requirement 13016) | S | Y | Y | RMS |
| RMS-5 | NPD 8720.1B | 1.a.(4) | 13016 | It is NASA policy for: Plan, establish, document, and implement-- Timely and continuous assessment of the progress toward achieving the Reliability and Maintainability requirements, including identification of areas for improvement. (Requirement 13016) | S | Y | Y | RMS | ||
| CxP 70059 | 3.2 | RMS-18 | NPD 8720.1B | 1.a.(3) | 13015 | It is NASA policy for: Plan, establish, document, and implement-- Requirements and tasks for Reliability and Maintainability engineering, analysis, and testing (including hardware, software, firmware, and human elements). (Requirement 13015) | S | Y | Y | RMS |
| CxP 70059 | 3.2.1.4 | RMS-113 | NPD 8720.1B | 1.a.(3) | 13015 | It is NASA policy for: Plan, establish, document, and implement-- Requirements and tasks for Reliability and Maintainability engineering, analysis, and testing (including hardware, software, firmware, and human elements). (Requirement 13015) | S | Y | Y | RMS |
| CxP 70059 | 3.2.2 | RMS-23 | NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS |
| CxP 70059 | 3.2.5.1 | RMS-32 | NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS |
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| CxP 70059 | 3.2.6 | RMS-34 | NPD 8730.2B | 1 | 10013 | POLICY: It is NASA policy to control risk and enhance reliability in NASA spaceflight and critical ground support systems, in part, by managing the selection, acquisition, traceability, testing, handling, packaging, storage, and application of Electrical, Electronic, and Electromechanical (EEE) parts; advanced packaging and interconnect systems; and mechanical parts (including fasteners, bearings, studs, pins, rings, shims, valves, springs, brackets, clamps, and spacers). (Requirement 10013) | S | Y | Y | RMS |
| NPD 8730.2B | 1.a | 10014 | To carry out this policy, NASA shall accomplish the following: Select parts and packaging technology based on their intended use considering, but not limited to, performance, environmental, criticality, and lifetime requirements. (Requirement 10014) | S | Y | Y | RMS | |||
| NPD 8730.2B | 1.b | 10025 | To carry out this policy, NASA shall accomplish the following: Document the derating criteria for parts. (Requirement 10025) | S | Y | Y | RMS | |||
| NPD 8730.2B | 1.c(1) | 10026 | To carry out this policy, NASA shall accomplish the following: Utilize the results of surveys/audits as a means to determine capability and qualification of sources. (Requirement 10026) | S | Y | Y | Quality | |||
| NPD 8730.2B | 1.c(2) | 30896 | To carry out this policy, NASA shall accomplish the following: NASA Centers may utilize the results of surveys/audits performed by other Centers or third-party auditors. The process used by third-party auditors/surveyors (including those performed by other Government agencies or commercial third-party auditors) must be reviewed prior to use to determine that the process meets minimum NASA requirements. (Requirement 30896) | S | Y | Y | Quality | |||
| CxP 70059 | 3.3.1.1 | RMS-57 | NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS |
| CxP 70059 | 3.4.1.1 | RMS-62 | NPR 8735.1A | 2.3.d.(2) | 31836 | Program, Project, and Functional Managers are responsible for: Ensuring that all applicable GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories are reviewed and dispositioned. (Requirement 31836) | S | Y | Y | RMS |
| NPR 8735.1A | 2.3.d.(3) | 31837 | Program, Project, and Functional Managers are responsible for: Ensuring that all significant parts, material and safety problems of a general concern are identified and corresponding data exchanged via GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories. (Requirement 31837) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.a | 31847 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Determining its relevance and impact to programs and projects. (Requirement 31847) | S | Y | Y | Safety | |||
| NPR 8735.1A | 5.1.b | 31848 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Identifying actions to be taken to reduce or eliminate any detrimental effects on programs and projects or identifying other disposition actions to be taken (e.g., risk accepted after assessment, parts replaced, parts placed in segregated stores, additional testing performed, etc.). (Requirement 31848) | S | Y | Y | RMS | |||
| NPR 8735.1B | 1.2.4.a | 57144 | General Requirements: Responsibilities: Program, Project, and Operations/Institutional Managers shall: Review all contracts to ensure incorporation of GIDEP participation requirements to evaluate GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories (Requirement 57144). | S | Y | Y | RMS | |||
| NPR 8735.1B | 1.2.4.c | 57146 | General Requirements: Responsibilities: Program, Project, and Operations/Institutional Managers shall: Ensure that all significant parts, material, and safety problems of a general concern are identified and corresponding data exchanged via GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories (Requirement 57146). | S | Y | Y | RMS | |||
| CxP 70059 | 3.4.1.2 | RMS-63 | NPR 8735.1B | 4.1.c | 57195 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Preparing and providing a response to the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory in the form of a Parts, Materials, and Safety Problem Impact Statement (NASA Form 1544 (see Appendix C)) or Center-designated form (Requirement 57195). | S | Y | Y | RMS |
| NPR 8735.1B | 4.1.c(01) | 57196 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: For GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, or NASA Advisories that do not apply to a program, project, or institution, the Program, Project, or Operations/Institutional Manager shall provide a "no impact" response on the form (Requirement 57196). | S | Y | Y | RMS | |||
| CxP 70059 | 3.4.1.3 | RMS-61 | NPR 8735.1A | 5.1.a | 31847 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Determining its relevance and impact to programs and projects. (Requirement 31847) | S | Y | Y | Safety |
| NPR 8735.1A | 5.1.b | 31848 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Identifying actions to be taken to reduce or eliminate any detrimental effects on programs and projects or identifying other disposition actions to be taken (e.g., risk accepted after assessment, parts replaced, parts placed in segregated stores, additional testing performed, etc.). (Requirement 31848) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(1) | 31849 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Preparing and providing a response to the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory in the form of a Parts, Materials and Safety Problem Impact Statement (NASA Form 1544 (Refer to Appendix 3)) or Center designated form. (Requirement 31849) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.d | 31853 | Collecting additional information as requested by the NASA Advisory initiator. (Requirement 31853) For example, NASA Advisories that deal with fraud will generally require additional information on the NASA Form 1544 to assist the NASA Office of the Inspector General in the preparation of any legal casework and to assist in cost recovery action. Such additional information may include: (1) Programs and Projects Impacted (Block 7): In addition to the list of programs/projects affected, the costs incurred in investigation of the impact to the programs/projects should be indicated. If there is no impact, the costs incurred to make that determination should be indicated. (2) Impact on Programs and Projects (Block 8): In addition to the required impact summary, the number of parts involved and their estimated cost should be indicated (e.g., 10 lots of fasteners totaling 135 fasteners with an estimated cost of $10,000). (3) Action Taken (Block 9): In addition to the summary of actions taken to eliminate or minimize the impact, any additional testing or inspection should be indicated. The results of those inspections or tests should be provided (e.g., Particle Impact Noise Detection test performed on 40 items with 3 failures). If a scrap decision is made, the number of items scrapped and their value should be indicated. | S | Y | Y | Mgmt | |||
| NPR 8735.1A | 5.1.e | 31854 | Preparing Lessons Learned reports if appropriate. (Requirement 31854) | S | Y | Y | Mgmt | |||
| NPR 8735.1B | 1.2.4.d | 57147 | General Requirements: Responsibilities: Program, Project, and Operations/Institutional Managers shall: Ensure that the status of all applicable GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories are reviewed at program milestones and readiness reviews (Requirement 57147). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.1.b | 57194 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Identifying actions to be taken to reduce or eliminate any detrimental effects on programs, projects, and institutions or identifying other disposition actions to be taken (e.g., risk accepted after assessment, parts replaced, parts placed in segregated stores, additional testing performed) (Requirement 57194). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.1.c | 57195 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Preparing and providing a response to the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory in the form of a Parts, Materials, and Safety Problem Impact Statement (NASA Form 1544 (see Appendix C)) or Center-designated form (Requirement 57195). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.1.c(01) | 57196 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: For GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, or NASA Advisories that do not apply to a program, project, or institution, the Program, Project, or Operations/Institutional Manager shall provide a "no impact" response on the form (Requirement 57196). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.4(1) | 57206 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: For human flight operations and safety critical systems, Program, Project, and Operations/Institutional Managers shall continue closed-loop GIDEP processing throughout the entire program/project life until disposal (Requirement 57206). | S | Y | Y | Safety | |||
| CxP 70059 | 3.4.1.4 | RMS-60 | NPR 8735.1A | 5.1.b | 31848 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Identifying actions to be taken to reduce or eliminate any detrimental effects on programs and projects or identifying other disposition actions to be taken (e.g., risk accepted after assessment, parts replaced, parts placed in segregated stores, additional testing performed, etc.). (Requirement 31848) | S | Y | Y | RMS |
| NPR 8735.1A | 5.1.c(2) | 31850 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: For GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, or NASA Advisories that do not apply to a program or project, a "no impact" response shall be provided on the form. (Requirement 31850) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(3) | 31851 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Center-generated processes shall identify how these documents are to be processed and retained. (Requirement 31851) | S | Y | Y | Safety | |||
| NPR 8735.1A | 5.1.c(4) | 31852 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: These documents shall be maintained for a minimum of 5 years following completion of the program. (Requirement 31852) | S | Y | Y | Mgmt | |||
| NPR 8735.1A | 5.1.e | 31854 | Preparing Lessons Learned reports if appropriate. (Requirement 31854) | S | Y | Y | Mgmt | |||
| NPR 8735.1B | 1.2.4.b | 57145 | General Requirements: Responsibilities: Program, Project, and Operations/Institutional Managers shall: Ensure that all applicable GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories are reveiwed and dispositioned for impact to all levels under their purview (Requirement 57145). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.1.a | 57193 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Determining its relevance and impact to programs, projects, and institutions (Requirement 57193). (See paragraph 4.2 and 4.3 for exceptions to Program and Project Managers' requirements for closed-loop GIDEP reporting). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.3 | 57205 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Program and Project Managers shall ensure that the baselining of the parts list includes a check of historical GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories (Requirement 57205). | S | Y | Y | RMS | |||
| CxP 70059 | 3.4.1.5 | RMS-58 | NPR 8735.1A | 2.3.d.(3) | 31837 | Program, Project, and Functional Managers are responsible for: Ensuring that all significant parts, material and safety problems of a general concern are identified and corresponding data exchanged via GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories. (Requirement 31837) | S | Y | Y | RMS |
| NPR 8735.1A | 3.1(1) | 24007 | Significant problem and non-conforming item data shall be documented for exchange among NASA Centers and GIDEP. (Requirement 24007) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.b | 31848 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Identifying actions to be taken to reduce or eliminate any detrimental effects on programs and projects or identifying other disposition actions to be taken (e.g., risk accepted after assessment, parts replaced, parts placed in segregated stores, additional testing performed, etc.). (Requirement 31848) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(1) | 31849 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Preparing and providing a response to the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory in the form of a Parts, Materials and Safety Problem Impact Statement (NASA Form 1544 (Refer to Appendix 3)) or Center designated form. (Requirement 31849) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(2) | 31850 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: For GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, or NASA Advisories that do not apply to a program or project, a "no impact" response shall be provided on the form. (Requirement 31850) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(3) | 31851 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Center-generated processes shall identify how these documents are to be processed and retained. (Requirement 31851) | S | Y | Y | Safety | |||
| NPR 8735.1A | 5.1.c(4) | 31852 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: These documents shall be maintained for a minimum of 5 years following completion of the program. (Requirement 31852) | S | Y | Y | Mgmt | |||
| NPR 8735.1B | 1.2.4.c | 57146 | General Requirements: Responsibilities: Program, Project, and Operations/Institutional Managers shall: Ensure that all significant parts, material, and safety problems of a general concern are identified and corresponding data exchanged via GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories (Requirement 57146). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.1.d(1) | 57199 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Collecting additional information as requested by the NASA Advisory initiator (Requirement 57199). | S | Y | Y | RMS | |||
| CxP 70059 | 3.4.1.6 | RMS-59 | NPR 8735.1A | 2.3.d.(4) | 31838 | Program, Project, and Functional Managers are responsible for: Ensuring that the status of all applicable GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories are reviewed at program milestones and readiness reviews. (Requirement 31838) | S | Y | Y | Mgmt |
| NPR 8735.1A | 3.1(1) | 24007 | Significant problem and non-conforming item data shall be documented for exchange among NASA Centers and GIDEP. (Requirement 24007) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.b | 31848 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Identifying actions to be taken to reduce or eliminate any detrimental effects on programs and projects or identifying other disposition actions to be taken (e.g., risk accepted after assessment, parts replaced, parts placed in segregated stores, additional testing performed, etc.). (Requirement 31848) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(1) | 31849 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Preparing and providing a response to the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory in the form of a Parts, Materials and Safety Problem Impact Statement (NASA Form 1544 (Refer to Appendix 3)) or Center designated form. (Requirement 31849) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(2) | 31850 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: For GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, or NASA Advisories that do not apply to a program or project, a "no impact" response shall be provided on the form. (Requirement 31850) | S | Y | Y | RMS | |||
| NPR 8735.1A | 5.1.c(3) | 31851 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Center-generated processes shall identify how these documents are to be processed and retained. (Requirement 31851) | S | Y | Y | Safety | |||
| NPR 8735.1A | 5.1.c(4) | 31852 | Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, Program/Project/Functional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: These documents shall be maintained for a minimum of 5 years following completion of the program. (Requirement 31852) | S | Y | Y | Mgmt | |||
| NPR 8735.1B | 4.1.c | 57195 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: Preparing and providing a response to the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory in the form of a Parts, Materials, and Safety Problem Impact Statement (NASA Form 1544 (see Appendix C)) or Center-designated form (Requirement 57195). | S | Y | Y | RMS | |||
| NPR 8735.1B | 4.1.c(01) | 57196 | Evaluation and Disposition of GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories: Upon receipt of a GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory, all Program, Project, and Operations/Institutional Managers shall evaluate and disposition the GIDEP ALERT, GIDEP SAFE-ALERT, GIDEP Problem Advisory, GIDEP Agency Action Notice, or NASA Advisory by: For GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency Action Notices, or NASA Advisories that do not apply to a program, project, or institution, the Program, Project, or Operations/Institutional Manager shall provide a "no impact" response on the form (Requirement 57196). | S | Y | Y | RMS | |||
| CxP 70059 | 4.1 | RMS-65 | NPD 8720.1B | 1.a.(1) | 13014 | It is NASA policy for: Plan, establish, document, and implement-- System Reliability and Maintainability design and operational performance requirements (qualitative and quantitative). (Requirement 13014) | S | Y | Y | RMS |
| CxP 70059 | 4.1.1 | RMS-66 | NPD 8720.1B | 1.a.(1) | 13014 | It is NASA policy for: Plan, establish, document, and implement-- System Reliability and Maintainability design and operational performance requirements (qualitative and quantitative). (Requirement 13014) | S | Y | Y | RMS |
| NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS | |||
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| CxP 70059 | 4.1.2 | RMS-67 | NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS |
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| RMS-68 | NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS | ||
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| CxP 70059 | 4.1.3 | RMS-70 | NPD 8720.1B | 1.a.(3) | 13015 | It is NASA policy for: Plan, establish, document, and implement-- Requirements and tasks for Reliability and Maintainability engineering, analysis, and testing (including hardware, software, firmware, and human elements). (Requirement 13015) | S | Y | Y | RMS |
| CxP 70059 | 4.1.5 | RMS-75 | NPD 8720.1B | 1.a.(4) | 13016 | It is NASA policy for: Plan, establish, document, and implement-- Timely and continuous assessment of the progress toward achieving the Reliability and Maintainability requirements, including identification of areas for improvement. (Requirement 13016) | S | Y | Y | RMS |
| CxP 70059 | 4.1.8 | RMS-79 | NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS |
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| CxP 70059 | 4.2.1 | RMS-82 | NPD 8720.1B | 1.a.(2) | 13032 | It is NASA policy for: Plan, establish, document, and implement-- System maintenance concepts. (Requirement 13032) | S | Y | Y | RMS |
| NPD 8720.1B | 5.d.(2) | 13010 | Program and project managers are responsible for: Establishing a maintenance concept early in the system development and ensuring that compatibility is sustained among system design, maintenance planning, and logistics support activities. (Requirement 13010) | S | Y | Y | RMS | |||
| CxP 70059 | 4.2.1.2 | RMS-84 | NPD 8720.1B | 5.d.(2) | 13010 | Program and project managers are responsible for: Establishing a maintenance concept early in the system development and ensuring that compatibility is sustained among system design, maintenance planning, and logistics support activities. (Requirement 13010) | S | Y | Y | RMS |
| CxP 70059 | 4.2.2 | RMS-87 | NPD 8720.1B | 5.d.(3) | 13011 | Program and project managers are responsible for: Establishing and maintaining a data collection system that provides a basis for generating the information to evaluate Reliability and Maintainability performance throughout the system's life cycle. (Requirement 13011) | S | Y | Y | RMS |
| NPD 8720.1B | 5.d.(4) | 13039 | Program and project managers are responsible for: Identifying the organization(s) that will maintain the Reliability and Maintainability data for the lifetime of the system and coordinating with the Center SMA functional manager to ensure that Reliability and Maintainability data is available for use as heritage data. (Requirement 13039) | S | Y | Y | RMS | |||
| CxP 70059 | 4.2.7 | RMS-97 | NPD 8720.1B | 1.a.(5) | 13033 | It is NASA policy for: Plan, establish, document, and implement-- Integration of Reliability and Maintainability processes, analytical activities, and data with systems engineering, risk management, and other processes, assessments, and analyses including, but not limited to, safety, security, quality, logistics, availability, probabilistic risk assessment, life-cycle cost, configuration management, and maintenance. (Requirement 13033) | S | Y | Y | RMS |
| NPD 8720.1B | 5.d.(1) | 13009 | Program and project managers are responsible for: Integrating all Reliability and Maintainability activities with the associated design and operation functions and associated program/project safety, quality assurance, risk management (including probabilistic risk assessment), and logistics (including maintenance) activities. (Requirement 13009) | S | Y | Y | RMS | |||
| CxP 70059 | 5.1.3 | QAS-1 | NPD 8700.1C | 1.i | 1067 | POLICY: It is NASA policy to-- Report and track to resolution all corrective actions resulting from investigations of mishaps, incidents, nonconformances, and anomalies; and distribute and use lessons learned to improve activities and operations. (Requirement 1067) | S | Y | Y | Quality |
| NPD 8730.5 | 1.a | 42126 | Policy: It is NASA policy to comply with prescribed requirements for performance of work and to provide for independent assurance of compliance through implementation of a quality assurance program. | S | Y | Y | Quality | |||
| NPD 8730.5 | 1.b.14 | 42147 | Policy: NASA quality assurance programs shall: Be performed in accordance with a documented quality system that follows the criteria specified in Attachment A. (Requirement 42147) | S | Y | Y | Quality | |||
| NPD 8730.5 | 1.c | 42148 | Policy: Government quality assurance organizations are to ensure that contractors implement quality system requirements and deliver conforming product in accordance with Federal Acquisition Regulations (FAR), the NASA FAR Supplement, and NPR 8735.2, Management of Government Safety and Mission Assurance Functions for NASA Contracts, Chapters 1 and 2. | S | Y | Y | Quality | |||
| NPD 8730.5 | 5.d.2 | 42198 | Responsibility: Program/project managers shall: Ensure program planning and acquisition documents incorporate applicable requirements of this NPD, including specification of applicable quality system requirements identified in Attachment A of this NPD. (Requirement 42198) | S | Y | Y | Quality | |||
| QAS-70 | NPD 8730.5 | 1.a | 42126 | Policy: It is NASA policy to comply with prescribed requirements for performance of work and to provide for independent assurance of compliance through implementation of a quality assurance program. | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.14 | 42147 | Policy: NASA quality assurance programs shall: Be performed in accordance with a documented quality system that follows the criteria specified in Attachment A. (Requirement 42147) | S | Y | Y | Quality | |||
| NPD 8730.5 | 1.c | 42148 | Policy: Government quality assurance organizations are to ensure that contractors implement quality system requirements and deliver conforming product in accordance with Federal Acquisition Regulations (FAR), the NASA FAR Supplement, and NPR 8735.2, Management of Government Safety and Mission Assurance Functions for NASA Contracts, Chapters 1 and 2. | S | Y | Y | Quality | |||
| NPD 8730.5 | 5.d.2 | 42198 | Responsibility: Program/project managers shall: Ensure program planning and acquisition documents incorporate applicable requirements of this NPD, including specification of applicable quality system requirements identified in Attachment A of this NPD. (Requirement 42198) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.4 | QAS-3 | NPD 8730.5 | 1.b.10.a | 42142 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Demonstrated knowledge, skills, and experience related to quality assurance principles and practices, and related to the specific product, process, or attribute for which assurance is being provided. (Requirement 42142) | S | Y | Y | Quality |
| NPD 8730.5 | 1.b.10.b | 42143 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Meeting formal certification or qualification requirements where prescribed in required/invoked documents or where deemed necessary to ensure personnel competency to perform specialized quality assurance functions. (Requirement 42143) | S | Y | Y | Quality | |||
| QAS-4 | NPD 8730.5 | 1.b.10.a | 42142 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Demonstrated knowledge, skills, and experience related to quality assurance principles and practices, and related to the specific product, process, or attribute for which assurance is being provided. (Requirement 42142) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.10.b | 42143 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Meeting formal certification or qualification requirements where prescribed in required/invoked documents or where deemed necessary to ensure personnel competency to perform specialized quality assurance functions. (Requirement 42143) | S | Y | Y | Quality | |||
| QAS-5 | NPD 8730.5 | 1.b.10.a | 42142 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Demonstrated knowledge, skills, and experience related to quality assurance principles and practices, and related to the specific product, process, or attribute for which assurance is being provided. (Requirement 42142) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.10.b | 42143 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Meeting formal certification or qualification requirements where prescribed in required/invoked documents or where deemed necessary to ensure personnel competency to perform specialized quality assurance functions. (Requirement 42143) | S | Y | Y | Quality | |||
| QAS-6 | NPD 8730.5 | 1.b.10.a | 42142 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Demonstrated knowledge, skills, and experience related to quality assurance principles and practices, and related to the specific product, process, or attribute for which assurance is being provided. (Requirement 42142) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.10.b | 42143 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Meeting formal certification or qualification requirements where prescribed in required/invoked documents or where deemed necessary to ensure personnel competency to perform specialized quality assurance functions. (Requirement 42143) | S | Y | Y | Quality | |||
| QAS-7 | NPD 8730.5 | 1.b.10.a | 42142 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Demonstrated knowledge, skills, and experience related to quality assurance principles and practices, and related to the specific product, process, or attribute for which assurance is being provided. (Requirement 42142) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.10.b | 42143 | Policy: NASA quality assurance programs shall: Be performed by persons that are competent on the basis of: Meeting formal certification or qualification requirements where prescribed in required/invoked documents or where deemed necessary to ensure personnel competency to perform specialized quality assurance functions. (Requirement 42143) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.6.1 | QAS-71 | NPD 8730.5 | 1.b.02 | 42129 | Policy: NASA quality assurance programs shall: Attain confidence levels for requirement compliance that are commensurate with the severity of consequences that would be incurred in the event of noncompliance. (Requirement 42129) | S | Y | Y | Quality |
| NPR 8735.2A | 1.2.07.c | 43062 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Provide detailed information concerning the resource(s) required to perform required quality assurance activities, including preparation of the NASA Center estimate of required delegated agency or surveillance support contract support (Requirement 43062) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.d | 43063 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure clear and mutual understanding of delegated/assigned quality assurance functions between NASA, the delegated agency, and quality assurance support contractors. (Requirement 43063) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.g | 43066 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Coordinate and integrate quality assurance functions performed by different parties to ensure that all of the requirements of Chapter 2 of this NPR are satisfied and to avoid duplication of effort. (Requirement 43066) | S | Y | Y | Quality | |||
| QAS-TBD | NASA STD 8719.13B | 6.3.2.1 | 33609 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33609) | S | Y | Y | SWA | ||
| CxP 70059 | 5.2.6.2.a | QAS-72 | NPR 8735.2A | 1.2.07.c | 43062 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Provide detailed information concerning the resource(s) required to perform required quality assurance activities, including preparation of the NASA Center estimate of required delegated agency or surveillance support contract support (Requirement 43062) | S | Y | Y | Quality |
| NPR 8735.2A | 1.2.07.d | 43063 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure clear and mutual understanding of delegated/assigned quality assurance functions between NASA, the delegated agency, and quality assurance support contractors. (Requirement 43063) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.g | 43066 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Coordinate and integrate quality assurance functions performed by different parties to ensure that all of the requirements of Chapter 2 of this NPR are satisfied and to avoid duplication of effort. (Requirement 43066) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.2 | 43224 | Performance of Quality Assurance Functions by Non-NASA Organizations: NASA Technical Direction: The NASA SMA Lead shall act as a liaison for providing technical direction and recommendations to delegated agencies and support contractors on matters related to the following, as applicable: (Requirement 43224) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.4.2 | 43240 | Performance of Quality Assurance Functions by Non-NASA Organizations: Selection of Organizations Performing Quality Assurance Functions: The following factors shall be evaluated in the selection of an organization to perform quality assurance functions (Requirement 43240): | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.7.1 | 43276 | Performance of Quality Assurance Functions by Non-NASA Organizations: Monitoring of Delegated Agency and Support Contractor Performance: NASA SMA Leads shall establish management controls to ensure adequate performance of delegated/tasked quality assurance functions. (Requirement 43276) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.6.3 | QAS-73 | NPD 8730.5 | 1.b.14 | 42147 | Policy: NASA quality assurance programs shall: Be performed in accordance with a documented quality system that follows the criteria specified in Attachment A. (Requirement 42147) | S | Y | Y | Quality |
| NPD 8730.5 | 1.c | 42148 | Policy: Government quality assurance organizations are to ensure that contractors implement quality system requirements and deliver conforming product in accordance with Federal Acquisition Regulations (FAR), the NASA FAR Supplement, and NPR 8735.2, Management of Government Safety and Mission Assurance Functions for NASA Contracts, Chapters 1 and 2. | S | Y | Y | Quality | |||
| NPR 8715.3C | 01.05.3 | 45668 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project Managers shall ensure that contractor operations and designs are evaluated for consistency and compliance with the safety and health provisions provided in their contractual agreements. (Requirement 45668) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.05.a | 43047 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Make contract awards which ensure that the Government is not assuming unacceptable quality risk, and which take into consideration SMA office input regarding contractor past performance in meeting contract requirements related to safety, quality, and product configuration. (Requirement 43047) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.05.b | 43048 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Take inputs from the program/project manager and/or the NASA SMA Lead to establish quality assurance requirements to be delegated to a non-NASA Federal agency via a Letter of Delegation (LOD) and/or to be performed under contract by a quality assurance support contractor. (Requirement 43048) | S | Y | Y | Quality | |||
| QAS-74 | NPD 8730.5 | 1.c | 42148 | Policy: Government quality assurance organizations are to ensure that contractors implement quality system requirements and deliver conforming product in accordance with Federal Acquisition Regulations (FAR), the NASA FAR Supplement, and NPR 8735.2, Management of Government Safety and Mission Assurance Functions for NASA Contracts, Chapters 1 and 2. | S | Y | Y | Quality | ||
| NPR 8735.2A | 3.2.1.c(1) | 43180 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Incorporate applicable requirements from FAR Part 46, NFS Part 1846, NPD 8730.5, Chapter 2 of this NPR, and other related documents (e.g., Program/Project Plan, Risk Management Plan, contract, GMIP schedule). (Requirement 43180) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.7 | QAS-11 | NPD 8730.5 | 1.b.02.b | 42131 | Policy: NASA quality assurance programs shall: For circumstances where noncompliance can result in loss of life or loss of mission, Government Mandatory Inspection Points (GMIP) shall be performed to ensure 100 percent compliance with safety/mission critical attributes. Safety/mission critical attributes include hardware characteristics, manufacturing process requirements, operating conditions, and functional performance criteria that, if not met, can result in loss of life or loss of mission. (Requirement 42131) | S | Y | Y | Quality |
| NPR 8735.2A | 1.2.04.a | 43042 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Plan and budget for implementation of Government contract quality assurance functions. (Requirement 43042) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.04.b | 43043 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Identify high-risk and low-risk item acquisitions using input/support provided by the Center SMA office. (Requirement 43043) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.04.c | 43044 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Develop Program/Project Quality Assurance Surveillance Plans (PQASP) per Chapter 3 of this NPR using input/support provided by the Center SMA office. (Requirement 43044) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.04.d | 43045 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Appoint a program/project SMA Lead, or request SMA Director assignment/provision of a NASA SMA Lead, in accordance with local Center organizational governance procedures. (Requirement 43045) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.05.a | 43047 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Make contract awards which ensure that the Government is not assuming unacceptable quality risk, and which take into consideration SMA office input regarding contractor past performance in meeting contract requirements related to safety, quality, and product configuration. (Requirement 43047) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.05.b | 43048 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Take inputs from the program/project manager and/or the NASA SMA Lead to establish quality assurance requirements to be delegated to a non-NASA Federal agency via a Letter of Delegation (LOD) and/or to be performed under contract by a quality assurance support contractor. (Requirement 43048) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.05.c(1) | 43049 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Incorporate appropriate clauses or provisions into the prime contract that allow NASA, delegated Federal agency personnel, and/or quality assurance support contractors timely access to contractor and subcontractor facilities to perform quality assurance functions required by this NPR. (Requirement 43049) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.a | 43060 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Identify key processes, products, documents, records, and performance characteristics requiring Government assurance actions and determine the appropriate level and type of Government contract quality assurance actions to be applied. (Requirement 43060) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.b | 43061 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Support the program/project manager and contracting officer in the development of the PQASP, LODs, and/or quality assurance support contracts. (Requirement 43061) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.c | 43062 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Provide detailed information concerning the resource(s) required to perform required quality assurance activities, including preparation of the NASA Center estimate of required delegated agency or surveillance support contract support (Requirement 43062) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.d | 43063 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure clear and mutual understanding of delegated/assigned quality assurance functions between NASA, the delegated agency, and quality assurance support contractors. (Requirement 43063) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.g | 43066 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Coordinate and integrate quality assurance functions performed by different parties to ensure that all of the requirements of Chapter 2 of this NPR are satisfied and to avoid duplication of effort. (Requirement 43066) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.1.1 | 43074 | Government Contract Quality Assurance Requirements: Low-Risk Items: Program/project managers shall identify low-risk item acquisitions in accordance with the criteria specified in paragraph 2.1.3 below. (Requirement 43074) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.1.2.b | 43077 | Government Contract Quality Assurance Requirements: Low-Risk Items: Government contract quality assurance for acquisitions involving the supply of low-risk items shall be performed in accordance with: Procurement quality assurance requirements provided in the procuring organization?s quality standard (e.g., AS9100 or ISO 9001 Section 7.4.3, Verification of Purchased Product). | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.1.2.c | 43078 | Government Contract Quality Assurance Requirements: Low-Risk Items: Government contract quality assurance for acquisitions involving the supply of low-risk items shall be performed in accordance with: Government Mandatory Inspection Point (GMIP) requirements per Chapter 8 of this NPR. | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.2.1(1) | 43090 | Government Contract Quality Assurance Requirements: High-Risk Items: Program/project managers shall identify high-risk item acquisitions. (Requirement 43090) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.1.1 | 43100 | Government Contract Quality Assurance Requirements: Product Assurance: Contractor hardware products shall be assured by product examination, process evaluation, and record review as follows: Product Examination: Supplier products shall be physically inspected, measured, and/or tested to ensure conformity to contract requirements. (Requirement 43100) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.1.2(1) | 43101 | Government Contract Quality Assurance Requirements: Product Assurance: Contractor hardware products shall be assured by product examination, process evaluation, and record review as follows: Process Witnessing: Supplier work processes shall be personally witnessed to ensure compliance with prescribed work instructions and contract requirements. (Requirement 43101) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.1.3(1) | 43103 | Government Contract Quality Assurance Requirements: Product Assurance: Contractor hardware products shall be assured by product examination, process evaluation, and record review as follows: Record Review: Recorded evidence demonstrating conformance to contract requirements shall be reviewed to ensure product and process conformance to contract requirements. (Requirement 43103) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.2 | 43105 | Government Contract Quality Assurance Requirements: Product Assurance: The selection of product assurance actions and the sample size/frequency of attribute selection shall be based on the following risk factors: 1) the criticality, complexity, cost, and importance of product supplied, 2) the complexity and maturity of the process performed, 3) personnel safety considerations, and 4) the supplier?s past quality performance related to the product supplied or process performed. (Requirement 43105) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.4 | 43107 | Government Contract Quality Assurance Requirements: Product Assurance: Product assurance attributes shall be pre-identified on checklists or by other documented methodology. (Requirement 43107) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5(1) | 43108 | Government Contract Quality Assurance Requirements: Product Assurance: Accomplishment of product assurance actions shall be attested to by signature, legible printed name, and date or by an inspection control system such as inspection stamps or electronic medium. (Requirement 43108) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5.1(1) | 43110 | Government Contract Quality Assurance Requirements: Product Assurance: Signatures, stamps, and data entries shall identify the discrete item examined (including any unique product identification/traceability information), process witnessed, or record verified. (Requirement 43110) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5.2.a | 43113 | Government Contract Quality Assurance Requirements: Product Assurance: Where stamps or an electronic medium is used, the inspection control system shall: Indicate the date of acceptance. (Requirement 43113) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5.2.b | 43114 | Government Contract Quality Assurance Requirements: Product Assurance: Where stamps or an electronic medium is used, the inspection control system shall: Ensure the legibility and durability of stamp impressions and ensure that stamps do not interlock with other stamps. (Requirement 43114) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5.2.c | 43115 | Government Contract Quality Assurance Requirements: Product Assurance: Where stamps or an electronic medium is used, the inspection control system shall: Ensure that only properly authorized and qualified persons are permitted to apply stamps or make data entries and that individuals who are authorized to use stamps maintain control of their assigned stamp at all times. (Requirement 43115) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5.2.d | 43116 | Government Contract Quality Assurance Requirements: Product Assurance: Where stamps or an electronic medium is used, the inspection control system shall: Ensure that data entries and/or stamp impressions provide direct traceability to the individual applying the stamp or making the data entry. (Requirement 43116) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.5.3 | 43117 | Government Contract Quality Assurance Requirements: Product Assurance: Where product assurance accomplishment is attested by application of stamps to inspected supplies, the stamp shall not be applied in a manner prohibited by drawings or specifications or which may degrade the quality of the product. (Requirement 43117) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.6 | 43118 | Government Contract Quality Assurance Requirements: Product Assurance: Product assurance actions shall be performed at subcontractor locations only where necessary to ensure that the contracted organization maintains effective oversight of subcontractors or to ensure compliance with critical product attributes (see paragraph 8.3.f). (Requirement 43118) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.7 | 43119 | Government Contract Quality Assurance Requirements: Product Assurance: Product assurance actions shall be performed by persons properly qualified and trained concerning the quality assurance technique being practiced and the specific product or processes for which assurance is being provided. (Requirement 43119) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.8 | 43120 | Government Contract Quality Assurance Requirements: Product Assurance: The control of monitoring and measuring devices used to perform product assurance actions shall comply with the same/applicable requirements invoked upon the contractor. (Requirement 43120) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.4.9 | 43121 | Government Contract Quality Assurance Requirements: Product Assurance: Product assurance actions performed on a sampling basis, for which there is a measurable population of items, shall be performed using statistically valid sampling plans to achieve prescribed confidence level objectives. (Requirement 43121) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.1(1) | 43123 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The contractor?s quality system shall be reviewed to ensure compliance with invoked quality program requirements, including internally developed procedures. (Requirement 43123) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.2 | 43125 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The frequency of quality system audits shall be based on the contracted organization?s quality history, but no less than once every two years. (Requirement 43125) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.3 | 43126 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The following quality system elements shall be reviewed where applicable and where invoked upon the contractor (Requirement 43126): | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.3.p | 43142 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The following quality system elements shall be reviewed where applicable and where invoked upon the contractor: Other quality program elements considered to represent unacceptable risk. | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.4 | 43143 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Quality system audits shall be performed and documented following written audit attributes, such as provided in AS9101, Quality Management Systems Assessment. (Requirement 43143) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.5 | 43144 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Quality system audit attribute selection shall be based on the importance of the attribute toward achieving product conformity. (Requirement 43144) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.6 | 43145 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Quality system auditing shall include product sampling, where applicable, to validate quality system effectiveness. (Requirement 43145) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.6.1 | 43146 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Product sampling shall be based on the criticality, complexity, and maturity of the product, personnel safety considerations, and the supplier?s past quality performance related to the product. (Requirement 43146) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.6.1 | 43148 | Government Contract Quality Assurance Requirements: Quality Data Analysis: Contractor quality data shall be collected and analyzed to identify problem areas (e.g., projects, products, processes, operations, organizations), common deficiency causes, quality trends, defect anomalies, and process variations. (Requirement 43148) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.6.2 | 43149 | Government Contract Quality Assurance Requirements: Quality Data Analysis: Sources of data shall include contractor-generated metrics, NASA-identified nonconformances, post-delivery quality escapes, and quality data reported by delegated parties (e.g., DCMA, quality assurance support contractors, and accredited quality system registrars). (Requirement 43149) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.6.3.a | 43151 | Government Contract Quality Assurance Requirements: Quality Data Analysis: Data shall be evaluated at established periodic intervals for the purpose of: Adjusting the frequency and content of customer oversight actions, including allocation of quality assurance personnel resources. (Requirement 43151) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.6.3.b | 43152 | Government Contract Quality Assurance Requirements: Quality Data Analysis: Data shall be evaluated at established periodic intervals for the purpose of: Providing supporting rationale for acceptance/rejection of the contractor?s quality system and/or written procedures. (Requirement 43152) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.6.3.c | 43153 | Government Contract Quality Assurance Requirements: Quality Data Analysis: Data shall be evaluated at established periodic intervals for the purpose of: Initiating corrective action based on identification of systemic problems and trends. (Requirement 43153) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.7.3.d | 43162 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Corrective action requests shall require identification of: Measures taken/planned to prevent recurrence of the nonconformity. | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.7.5 | 43165 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Government identified nonconformances and corrective action reports shall be entered into an electronic nonconformance reporting and corrective action tracking system and, as appropriate for source evaluation/selection purposes, a past performance information management system. (Requirement 43165) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.8.1.a | 43168 | Government Contract Quality Assurance Requirements: Final Acceptance: Final acceptance constitutes acknowledgement that the supplies or services conform with applicable contract quality and quantity requirements, except where acceptance of nonconforming supplies is determined to be in the Government?s interest (see FAR Section 46.407 and Subpart 46.5) or where provided for by other terms and conditions of the contract. The Government shall formally accept delivery of product or services based on performance of the following actions: Final product inspection. (Requirement 43168) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.8.1.b | 43169 | Government Contract Quality Assurance Requirements: Final Acceptance: Final acceptance constitutes acknowledgement that the supplies or services conform with applicable contract quality and quantity requirements, except where acceptance of nonconforming supplies is determined to be in the Government?s interest (see FAR Section 46.407 and Subpart 46.5) or where provided for by other terms and conditions of the contract. The Government shall formally accept delivery of product or services based on performance of the following actions: Validation that there are no outstanding corrective actions resulting from contracting activity or contractor-identified nonconformances affecting acceptability of product. (Requirement 43169) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.8.1.c | 43170 | Government Contract Quality Assurance Requirements: Final Acceptance: Final acceptance constitutes acknowledgement that the supplies or services conform with applicable contract quality and quantity requirements, except where acceptance of nonconforming supplies is determined to be in the Government?s interest (see FAR Section 46.407 and Subpart 46.5) or where provided for by other terms and conditions of the contract. The Government shall formally accept delivery of product or services based on performance of the following actions: Validation that there are no outstanding engineering departures/waivers/deviations impacting acceptability of product and that all applicable engineering departures/waivers/deviations have been approved by the proper technical authority. (Requirement 43170) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.8.1.d | 43171 | Government Contract Quality Assurance Requirements: Final Acceptance: Final acceptance constitutes acknowledgement that the supplies or services conform with applicable contract quality and quantity requirements, except where acceptance of nonconforming supplies is determined to be in the Government?s interest (see FAR Section 46.407 and Subpart 46.5) or where provided for by other terms and conditions of the contract. The Government shall formally accept delivery of product or services based on performance of the following actions: Validation that all required GMIPs have been accomplished. (Requirement 43171) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.8.2 | 43172 | Government Contract Quality Assurance Requirements: Final Acceptance: Performance of final acceptance is an inherently Governmental function which is the responsibility of the NASA contracting officer or his/her Government delegate. Performance of final acceptance shall not be delegated to a non-Governmental entity. (Requirement 43172) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.b(2) | 43179 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: The PQASP may be a part of a larger program/project safety and mission assurance plan or may be a stand-alone document. | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.c(1) | 43180 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Incorporate applicable requirements from FAR Part 46, NFS Part 1846, NPD 8730.5, Chapter 2 of this NPR, and other related documents (e.g., Program/Project Plan, Risk Management Plan, contract, GMIP schedule). (Requirement 43180) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.d(1) | 43182 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Be initially prepared in conjunction with preparation of the Statement of Work and periodically adjusted thereafter based on changing risk factors as the program/project progresses through pre-award activities, Request for Proposal responses, and post-award activities. (Requirement 43182) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.4 | 43188 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Surveillance Functions. Identify the quality assurance surveillance functions to be performed for the program/project in accordance with Chapter 2 of this NPR and the following (Requirement 43188): | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.2 | 43224 | Performance of Quality Assurance Functions by Non-NASA Organizations: NASA Technical Direction: The NASA SMA Lead shall act as a liaison for providing technical direction and recommendations to delegated agencies and support contractors on matters related to the following, as applicable: (Requirement 43224) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.3.a | 43235 | Performance of Quality Assurance Functions by Non-NASA Organizations: Coordination of NASA Quality Assurance Functions: When there are multiple NASA delegations and/or tasks at a contractor's facility, duplication of effort and inconsistent surveillance methodologies are to be avoided. Prior to providing a new delegation and/or quality assurance support contractor tasking, NASA SMA Leads shall coordinate their efforts to: Establish agreement among the delegating activities for interpretation of common requirements. (Requirement 43235) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.3.b | 43236 | Performance of Quality Assurance Functions by Non-NASA Organizations: Coordination of NASA Quality Assurance Functions: When there are multiple NASA delegations and/or tasks at a contractor's facility, duplication of effort and inconsistent surveillance methodologies are to be avoided. Prior to providing a new delegation and/or quality assurance support contractor tasking, NASA SMA Leads shall coordinate their efforts to: Establish agreement among the delegating activities for acceptance or rejection of delegated agency or surveillance support contractor operational methods. (Requirement 43236) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.3.c | 43237 | Performance of Quality Assurance Functions by Non-NASA Organizations: Coordination of NASA Quality Assurance Functions: When there are multiple NASA delegations and/or tasks at a contractor's facility, duplication of effort and inconsistent surveillance methodologies are to be avoided. Prior to providing a new delegation and/or quality assurance support contractor tasking, NASA SMA Leads shall coordinate their efforts to: Place common requirements on the delegated agency or surveillance support contractor for similar supplies and services. (Requirement 43237) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.4.1 | 43239 | Performance of Quality Assurance Functions by Non-NASA Organizations: Selection of Organizations Performing Quality Assurance Functions: Program/project offices or the Center SMA office, as delegated by the Center Director, shall select/assign the organization that will be responsible for performing Government contract quality assurance functions (NASA civil servants, a delegated agency, quality assurance support contractor, or an authorized third party) based on the qualifications and abilities of the organization in relation to the needs and objectives of the quality assurance function(s). (Requirement 43239) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.4.2 | 43240 | Performance of Quality Assurance Functions by Non-NASA Organizations: Selection of Organizations Performing Quality Assurance Functions: The following factors shall be evaluated in the selection of an organization to perform quality assurance functions (Requirement 43240): | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.2 | 43254 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead, in coordination with the contracting office technical representative and other interested/authorized contracting office attendees, shall conduct the planning conference prior to the post-contract award conference. (Requirement 43254) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.a | 43256 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Contract and subcontract quality requirements. (Requirement 43256) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.b | 43257 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: End-use and criticality of supplies and services. (Requirement 43257) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.c | 43258 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Current procedures and general operations, particularly those applicable to supplies and services similar to those being procured. (Requirement 43258) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.d | 43259 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Technical direction to be given to the contractor. (Requirement 43259) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.e | 43260 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Functions to be delegated or tasked and the performance desired. (Requirement 43260) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.f | 43261 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Special skills, knowledge, qualifications, training, and certifications required. (Requirement 43261) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.g | 43262 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Quality assurance functions to be performed at the contractor's facility by NASA personnel. (Requirement 43262) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.h | 43263 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Channels of communication. (Requirement 43263) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.i | 43264 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Past quality assurance history of the contractor, known contractor deficiencies, and the contractor's progress in correcting deficiencies. (Requirement 43264) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.j | 43265 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: MRB authority. (Requirement 43265) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.k | 43266 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Redelegation and flowdown of requirements. (Requirement 43266) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.L | 43267 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Interface situations arising from partial delegations, Department of Defense delegations, or other NASA delegations in the same facility. (Requirement 43267) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.m | 43268 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: Response time for mandatory inspections. (Requirement 43268) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.5.3.n | 43269 | Performance of Quality Assurance Functions by Non-NASA Organizations: Planning Conference: The NASA SMA Lead shall ensure that the planning conference includes discussions of the following: NASA, delegated agency, and contractor responsibilities related to the reporting, tracking, corrective action resolution, and closure of contract nonconformances. (Requirement 43269) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.7.1 | 43276 | Performance of Quality Assurance Functions by Non-NASA Organizations: Monitoring of Delegated Agency and Support Contractor Performance: NASA SMA Leads shall establish management controls to ensure adequate performance of delegated/tasked quality assurance functions. (Requirement 43276) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.7.3 | 43279 | Performance of Quality Assurance Functions by Non-NASA Organizations: Monitoring of Delegated Agency and Support Contractor Performance: NASA SMA Leads shall provide evaluation results to the delegated agency/quality assurance support contractor. (Requirement 43279) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.7.4 | 43280 | Performance of Quality Assurance Functions by Non-NASA Organizations: Monitoring of Delegated Agency and Support Contractor Performance: Contracting officers shall incorporate requirements into LODs and support contracts for delegated agencies and quality assurance support contractors to monitor their own performance and resource utilization and provide performance measurement data to NASA on a specified periodic basis. (Requirement 43280) | S | Y | Y | Quality | |||
| NPR 8735.2A | 4.8.1 | 43282 | Performance of Quality Assurance Functions by Non-NASA Organizations: Inadequate Quality Assurance Support: Upon discovery that the delegated agency or the quality assurance support contractor is providing inadequate quality assurance support that does not comply with the LOD or support contract, as applicable, the contracting officer, in coordination with the NASA SMA Lead, shall formally request corrective action from the delegated agency or support contractor. (Requirement 43282) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.2.2.1 | 43298 | NASA Letters of Delegation: Planning Delegations: Contracting officers shall: Issue delegations within 10 calendar days of contract award. (Requirement 43298) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.2.2.2 | 43299 | NASA Letters of Delegation: Planning Delegations: Contracting officers shall: Request that delegated agencies provide notification of LOD acceptance within 30 calendar days of receipt. (Requirement 43299) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.2.2.3(1) | 43300 | NASA Letters of Delegation: Planning Delegations: Contracting officers shall: Specify that authorized redelegations be issued within 15 calendar days of acceptance of the original delegation. (Requirement 43300) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.1 | 43303 | NASA Letters of Delegation: LOD Content: Contracting officers shall incorporate the applicable requirements and text from the template provided in Appendix C of this NPR into their LODs. (Requirement 43303) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.a | 43305 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Name, location, and telephone number of the designated SMA Point of Contact (POC) who serves as NASA?s principal POC and technical/contractual authority liaison for matters pertaining to the delegation and a request for the delegated agency to include this information in letters of redelegation. (Requirement 43305) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.b | 43306 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: The identification of any quality assurance decisions which require review by the NASA SMA Lead prior to, and after acceptance for, the Government. (Requirement 43306) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.c | 43307 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Point of contact for obtaining assistance with locating any NASA-unique documents. (Requirement 43307) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.d | 43308 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Dates, frequency, and distribution for submittal of required delegated agency reports. (Requirement 43308) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.e | 43309 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Information concerning assignment of NASA technical representatives at the contractor's facility, including names and functions to be performed. (Requirement 43309) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.f | 43310 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Request for the name of the delegated agency representative to serve as the principal point of contact for the facility where the delegated functions are to be performed. (Requirement 43310) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.g | 43311 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Extent of redelegation authority. (Requirement 43311) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.h | 43312 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Identification of surveillance functions to be performed by the delegated agency utilizing the template provided in Appendix C of this NPR. (Requirement 43312) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.i | 43313 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Criteria for delegated agency selection of mandatory actions, if applicable. (Requirement 43313) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.j | 43314 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Special instructions on preparation and distribution of shipping and acceptance documents. (Requirement 43314) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.k | 43315 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Identification of the delegated agency?s responsibility for interim acceptance and for support at the remote site where final acceptance is to occur (for circumstances where final acceptance of supplies and services is not to occur at the contractor's facility). (Requirement 43315) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.L | 43316 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Instructions regarding the respective responsibilities and authority of the delegated agency and NASA personnel (for circumstances where the delegated activities involve interface with NASA personnel (e.g., end item test and inspection)). (Requirement 43316) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.2.m | 43317 | NASA Letters of Delegation: LOD Content: Contracting officers shall include the following in their LODs: Identification of special training and qualification requirements for personnel performing delegated functions, including special process certifications (e.g., nondestructive testing, workmanship) and job classifications or competencies of personnel needed (e.g., safety engineer). (Requirement 43317) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.3.3 | 43318 | NASA Letters of Delegation: LOD Content: Contracting officers shall maintain a central file of LODs for their Center. (Requirement 43318) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.5.1 | 43321 | NASA Letters of Delegation: Action upon Completion of Delegated Functions: The contracting officer shall maintain delegations at all tiers for the same period of time as required for records to be maintained in the contract/subcontract under surveillance. (Requirement 43321) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.5.3 | 43323 | NASA Letters of Delegation: Action upon Completion of Delegated Functions: Delegations may be reopened within one year after contract completion and shall be retained for easy retrieval. (Requirement 43323) | S | Y | Y | Quality | |||
| NPR 8735.2A | 5.5.4 | 43324 | NASA Letters of Delegation: Action upon Completion of Delegated Functions: The contracting officer shall advise the delegated agency to hold the delegation open when conditions exist or are expected that would justify extension of the contract period of performance. (Requirement 43324) | S | Y | Y | Quality | |||
| NPR 8735.2A | 6.2 | 43327 | Quality Assurance Support Contracts: Planning Quality Assurance Support Contracts: Contracting officers shall issue quality assurance support contracts in sufficient time to permit accomplishment of assigned quality assurance functions coincident with the commencement of contractor work operations (Requirement 43327). | S | Y | Y | Quality | |||
| NPR 8735.2A | 6.3.1.a | 43330 | Quality Assurance Support Contracts: Quality Assurance Support Contract Contents: Contracting officers shall include the following contents in quality assurance support contracts: Applicable requirements and text from the template provided in Appendix C of this NPR. (Requirement 43330) | S | Y | Y | Quality | |||
| NPR 8735.2A | 6.3.1.b | 43331 | Quality Assurance Support Contracts: Quality Assurance Support Contract Contents: Contracting officers shall include the following contents in quality assurance support contracts: Identification of quality assurance surveillance functions to be performed by the support contractor utilizing the template provided in Appendix C of this NPR. (Requirement 43331) | S | Y | Y | Quality | |||
| NPR 8735.2A | 6.3.2(1) | 43332 | Quality Assurance Support Contracts: Quality Assurance Support Contract Contents: Quality assurance support contracts are not to include performance of inherently Governmental functions as defined in 48 CFR 7, Subpart 7.5. (Requirement 43332) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.2.1 | 43342 | Government Mandatory Inspection Points (GMIPs): Selection and Assignment of GMIPs: Program/project Offices, with NASA SMA Lead and SMA office support, shall define GMIPs based on an analysis of risks related to contract noncompliance. This includes the following: (Requirement 43342) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.2.1.a | 43343 | Government Mandatory Inspection Points (GMIPs): Selection and Assignment of GMIPs: Program/project Offices, with NASA SMA Lead and SMA office support, shall define GMIPs based on an analysis of risks related to contract noncompliance. This includes the following: Safety-critical GMIPs are defined in order to assure conformance to hardware characteristics, manufacturing process requirements, operating conditions, and functional performance criteria that, if not met, can result in loss of life. A safety-critical GMIP shall be assigned for every (i.e., 100 percent) attribute/requirement where noncompliance could credibly result in loss of life. (Requirement 43343) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.2.1.b(1) | 43344 | Government Mandatory Inspection Points (GMIPs): Selection and Assignment of GMIPs: Program/project Offices, with NASA SMA Lead and SMA office support, shall define GMIPs based on an analysis of risks related to contract noncompliance. This includes the following: For circumstances where noncompliance could not credibly result in loss of life, but could result in serious injury, loss of mission, or loss of a significant mission resource, GMIPs shall be assigned to attain heightened confidence of contract compliance. (Requirement 43344) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.2.1.c(1) | 43346 | Government Mandatory Inspection Points (GMIPs): Selection and Assignment of GMIPs: Program/project Offices, with NASA SMA Lead and SMA office support, shall define GMIPs based on an analysis of risks related to contract noncompliance. This includes the following: Where analysis indicates an unacceptable likelihood of conformance with a key product attribute or process requirement, GMIPs shall be assigned to attain satisfactory confidence of contract compliance. (Requirement 43346) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.2.1.d | 43348 | Government Mandatory Inspection Points (GMIPs): Selection and Assignment of GMIPs: Program/project Offices, with NASA SMA Lead and SMA office support, shall define GMIPs based on an analysis of risks related to contract noncompliance. This includes the following: Program/project offices shall consider the following sources of information during the GMIP definition process: (Requirement 43348) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.2.1.e | 43360 | Government Mandatory Inspection Points (GMIPs): Selection and Assignment of GMIPs: Program/project Offices, with NASA SMA Lead and SMA office support, shall define GMIPs based on an analysis of risks related to contract noncompliance. This includes the following: Program/project offices shall consider the following conditions, operations, and quality assurance functions during the GMIP definition process: (Requirement 43360) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.a | 43374 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Perform 100 percent of all assigned GMIPs in strict accordance with the prescribed technical criteria. (Requirement 43374) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.b(1) | 43375 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Request formal disposition/authorization for GMIP omissions, waivers, or deviations from the designated NASA technical authority. (Requirement 43375) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.c | 43377 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Indicate as acceptable only those characteristics that have been personally examined, witnessed, or verified. (Requirement 43377) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.d | 43378 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Perform GMIPs after contractor personnel have made their acceptance decisions, except in those cases where concurrent inspections/tests are necessary to avoid the need for destructive testing or to prevent excessive costs or potential time delays. (Requirement 43378) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.e | 43379 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Perform GMIPs as late as practicable in the material fabrication/installation/delivery cycle for circumstances where GMIP attributes can be altered (e.g., contamination). (Requirement 43379) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.f | 43380 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Perform GMIPs at subcontractor facilities only when required in the Government?s interest, as specified in FAR Section 46.405. (Requirement 43380) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.g | 43381 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Attest to the completion of GMIPs in accordance with the requirements of paragraph 2.4.5 of this NPR. (Requirement 43381) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.h | 43382 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Periodically sign a statement indicating that they understand that their signature, application of a stamp, or data entry is a professional, individual warranty (guarantee) that they personally examined the product, witnessed the process, or verified the record as literally stated for the GMIP acceptance criteria. (Requirement 43382) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.i | 43383 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Maintain positive controls which assure that all assigned GMIPs are incorporated into planning documents, where applicable, and accomplished. (Requirement 43383) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.j | 43384 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Report, track, and ensure proper resolution of nonconformances identified during the conduct of GMIPs in accordance with section 2.7 of this NPR. (Requirement 43384) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.3.k | 43385 | Government Mandatory Inspection Points (GMIPs): Performance of GMIPs: Personnel responsible for the administration and performance of GMIPs shall: Where GMIP accomplishment is attested to by stamps/signatures on contractor developed/maintained planning records or data, ensure that such records are readily retrievable. (Requirement 43385) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.4.a | 43387 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: Safety-critical GMIPs shall be performed by Government personnel or under the direction and supervision of Government personnel. (Requirement 43387) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.4.b | 43388 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: When safety-critical GMIPs are assigned to non-Governmental personnel, NASA supervision shall include periodic/random spot checks of GMIP performance, and other measures as necessary, to ensure that such persons are properly trained and qualified and are carrying out these inspections in an objective and competent manner. (Requirement 43388) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.4.c | 43389 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: Safety-critical GMIPs shall include product examination or process witnessing versus record review whenever practicable. (Requirement 43389) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.4.d | 43390 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: Contracting officers shall include in contracts a statement expressly prohibiting the contractor from continuing work operations planned subsequent to the performance of designated safety-critical GMIPs until Government accomplishment of the mandatory inspection point. (Requirement 43390) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.4.e | 43391 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: For circumstances where destructive testing would be necessary to assure compliance with a safety-critical attribute, contractor assurance actions and associated GMIPs shall involve, wherever possible, the testing of a product sample that is determined to reliably/accurately represent the final product attribute. (Requirement 43391) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.5.a | 43393 | Government Mandatory Inspection Points (GMIPs): Contractor Interface for Performance of GMIPs: The onsite Government representatives (i.e., NASA, delegated agency, or support contractors) shall work with the contractor to: Incorporate GMIPs as hold points on contractor work planning documents. (Requirement 43393) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.5.b | 43394 | Government Mandatory Inspection Points (GMIPs): Contractor Interface for Performance of GMIPs: The onsite Government representatives (i.e., NASA, delegated agency, or support contractors) shall work with the contractor to: Develop a GMIP notification process that assures sufficiently advance Government notification of work operations involving GMIPs, that results in timely performance of GMIPs, and that results in minimal disruption to contractor work operations. (Requirement 43394) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.5.c | 43395 | Government Mandatory Inspection Points (GMIPs): Contractor Interface for Performance of GMIPs: The onsite Government representatives (i.e., NASA, delegated agency, or support contractors) shall work with the contractor to: Establish specific guidelines and requirements regarding contractor continuance of work operations in the event that the Government does not arrive within a specified agreed-to time frame to perform an assigned GMIP. (Requirement 43395) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.7.2.1 | QAS-16 | NPR 8735.2A | 4.7.2(1) | 43277 | Performance of Quality Assurance Functions by Non-NASA Organizations: Monitoring of Delegated Agency and Support Contractor Performance: NASA SMA Leads shall evaluate performance on a continuing basis to ensure that LOD and support contract requirements are complied with and remain current. (Requirement 43277) | S | Y | Y | Quality |
| QAS-17 | NASA-STD-8739.8 | 6.6.2 | 33263 | Software assurance records shall include recommended preventive measures, corrective actions, and lessons learned. (Requirement 33263) | S | Y | Y | SWA | ||
| CxP 70059 | 5.2.7.2.2 | QAS-18 | NPD 8730.5 | 5.e.2 | 42203 | Responsibility: Procurement officials shall: Ensure that prospective contractors meet contract qualification requirements (quality system, product, process, personnel). (Requirement 42203) | S | Y | Y | Quality |
| NPR 8735.2A | 2.3.1 | 43094 | Government Contract Quality Assurance Requirements: Document Review: Contractor quality system procedures, technical products (e.g., data, drawings), and manufacturing process instructions shall be reviewed to ensure compliance with contract requirements. (Requirement 43094) | S | Y | Y | Quality | |||
| QAS-19 | NPR 8735.2A | 2.3.1.1 | 43095 | Government Contract Quality Assurance Requirements: Document Review: Document review shall be performed on a periodic basis and whenever document changes are made that affect quality system processes or product attributes. (Requirement 43095) | S | Y | Y | Quality | ||
| QAS-20 | NPD 8730.5 | 1.b.02 | 42129 | Policy: NASA quality assurance programs shall: Attain confidence levels for requirement compliance that are commensurate with the severity of consequences that would be incurred in the event of noncompliance. (Requirement 42129) | S | Y | Y | Quality | ||
| NPR 8735.2A | 2.3.1.2 | 43096 | Government Contract Quality Assurance Requirements: Document Review: Selection of documents for review shall be based on the criticality, complexity, cost and importance of the product or process that is documented, and past product/process performance. (Requirement 43096) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.7.4 | QAS-22 | NPR 8735.2A | 4.4.1 | 43239 | Performance of Quality Assurance Functions by Non-NASA Organizations: Selection of Organizations Performing Quality Assurance Functions: Program/project offices or the Center SMA office, as delegated by the Center Director, shall select/assign the organization that will be responsible for performing Government contract quality assurance functions (NASA civil servants, a delegated agency, quality assurance support contractor, or an authorized third party) based on the qualifications and abilities of the organization in relation to the needs and objectives of the quality assurance function(s). (Requirement 43239) | S | Y | Y | Quality |
| NPR 8735.2A | 8.4.a | 43387 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: Safety-critical GMIPs shall be performed by Government personnel or under the direction and supervision of Government personnel. (Requirement 43387) | S | Y | Y | Quality | |||
| NPR 8735.2A | 8.4.b | 43388 | Government Mandatory Inspection Points (GMIPs): Special Requirements for Safety-Critical GMIPs: When safety-critical GMIPs are assigned to non-Governmental personnel, NASA supervision shall include periodic/random spot checks of GMIP performance, and other measures as necessary, to ensure that such persons are properly trained and qualified and are carrying out these inspections in an objective and competent manner. (Requirement 43388) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.7.5.1 | QAS-23 | NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality |
| NPR 8735.2A | 2.5.1(1) | 43123 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The contractor?s quality system shall be reviewed to ensure compliance with invoked quality program requirements, including internally developed procedures. (Requirement 43123) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.2 | 43125 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The frequency of quality system audits shall be based on the contracted organization?s quality history, but no less than once every two years. (Requirement 43125) | S | Y | Y | Quality | |||
| QAS-24 | NPD 8730.5 | 1.b.02 | 42129 | Policy: NASA quality assurance programs shall: Attain confidence levels for requirement compliance that are commensurate with the severity of consequences that would be incurred in the event of noncompliance. (Requirement 42129) | S | Y | Y | Quality | ||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.1(1) | 43123 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The contractor?s quality system shall be reviewed to ensure compliance with invoked quality program requirements, including internally developed procedures. (Requirement 43123) | S | Y | Y | Quality | |||
| QAS-25 | NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | ||
| CxP 70059 | 5.2.7.5.1.d | QAS-77 | NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality |
| NPR 8735.2A | 2.5.6 | 43145 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Quality system auditing shall include product sampling, where applicable, to validate quality system effectiveness. (Requirement 43145) | S | Y | Y | Quality | |||
| QAS-78 | NPR 8735.2A | 2.5.6.1 | 43146 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Product sampling shall be based on the criticality, complexity, and maturity of the product, personnel safety considerations, and the supplier?s past quality performance related to the product. (Requirement 43146) | S | Y | Y | Quality | ||
| CxP 70059 | 5.2.7.5.3 | QAS-27 | NASA-STD-8739.8 | 5.6.1.2 | 33223 | Depending upon the operational environment and the criticality of operation, ensure that software assurance processes include a periodic audit of the operations to ensure any changes to the software or software induced operational workarounds have been reviewed and approved. (Requirement 33223) | S | Y | Y | SWA |
| NPD 8730.5 | 5.e.2 | 42203 | Responsibility: Procurement officials shall: Ensure that prospective contractors meet contract qualification requirements (quality system, product, process, personnel). (Requirement 42203) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.3 | 43126 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The following quality system elements shall be reviewed where applicable and where invoked upon the contractor (Requirement 43126): | S | Y | Y | Quality | |||
| QAS-28 | NPR 8735.2A | 2.5.3 | 43126 | Government Contract Quality Assurance Requirements: Quality System Evaluation: The following quality system elements shall be reviewed where applicable and where invoked upon the contractor (Requirement 43126): | S | Y | Y | Quality | ||
| CxP 70059 | 5.2.7.5.4.1 | QAS-79 | NPD 8730.5 | 1.b.01 | 42128 | Policy: NASA quality assurance programs shall: Be designed and implemented in a manner that mitigates risks associated with noncompliance. Determination of risk considers the likelihood of noncompliance and the consequences associated with noncompliance, including the maturity, complexity, criticality, and value of work performed, as well as demonstrated experience with past quality system or program performance. (Requirement 42128) | S | Y | Y | Quality |
| NPD 8730.5 | 1.b.03 | 42132 | Policy: NASA quality assurance programs shall: Be reevaluated and adjusted based on changes to risk factors. (Requirement 42132) | S | Y | Y | Quality | |||
| NPD 8730.5 | 1.b.04 | 42133 | Policy: NASA quality assurance programs shall: Include prework assurance measures that provide increased confidence for meeting prescribed requirements (e.g., preaward surveys, qualified source selection, training), concurrent assurance measures to ensure that work is being performed in accordance with requirements (e.g., process control, process witnessing), and postwork assurance measures to ensure that work was properly performed (e.g., inspections, tests, record review, configuration control). (Requirement 42133) | S | Y | Y | Quality | |||
| NPD 8730.5 | 1.b.09 | 42140 | Policy: NASA quality assurance programs shall: Ensure clear and mutual understanding of prescribed quality requirements among organizations responsible for contracting or assigning work, performing work, and assuring conformity of work. (Requirement 42140) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.4 | 43143 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Quality system audits shall be performed and documented following written audit attributes, such as provided in AS9101, Quality Management Systems Assessment. (Requirement 43143) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.5.5 | 43144 | Government Contract Quality Assurance Requirements: Quality System Evaluation: Quality system audit attribute selection shall be based on the importance of the attribute toward achieving product conformity. (Requirement 43144) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.7.5.4.2 | QAS-29 | NASA-STD-8739.8 | 5.6.1.2 | 33223 | Depending upon the operational environment and the criticality of operation, ensure that software assurance processes include a periodic audit of the operations to ensure any changes to the software or software induced operational workarounds have been reviewed and approved. (Requirement 33223) | S | Y | Y | SWA |
| NPD 8730.5 | 1.b.03 | 42132 | Policy: NASA quality assurance programs shall: Be reevaluated and adjusted based on changes to risk factors. (Requirement 42132) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.7.7.1.a | QAS-131 | NPD 8730.5 | 5.d.4 | 42200 | Responsibility: Program/project managers shall: Initiate corrective actions upon discovery or notification of noncompliance. (Requirement 42200) | S | Y | Y | Quality |
| CxP 70059 | 5.2.7.7.2 | QAS-34 | NPD 8730.5 | 1.b.08 | 42137 | Policy: NASA quality assurance programs shall: Provide for investigative and corrective actions upon discovery or notification of noncompliance. (Requirement 42137) | S | Y | Y | Quality |
| NPD 8730.5 | 5.d.4 | 42200 | Responsibility: Program/project managers shall: Initiate corrective actions upon discovery or notification of noncompliance. (Requirement 42200) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.7.1 | 43156 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Government-identified nonconformances shall be documented and reported to the contractor for performance of corrective and preventive actions. (Requirement 43156) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.7.3 | 43158 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Corrective action requests shall require identification of: (Requirement 43158) | S | Y | Y | Quality | |||
| QAS-35 | NPR 8735.2A | 2.7.2 | 43157 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Corrective action requests shall be elevated to the appropriate level of contractor management based on problem criticality, recurrence, and/or nonresponsiveness. (Requirement 43157) | S | Y | Y | Quality | ||
| QAS-36 | NPD 8730.5 | 1.b.08.b | 42139 | Policy: NASA quality assurance programs shall: Corrective actions shall include the correction, replacement, repair, or authorized disposition of noncompliant items/conditions, implementation of preventive measures to eliminate the causes of noncompliance, and validation that implemented preventive measures have effectively eliminated recurrence of the noncompliant condition (recurrence control). (Requirement 42139) | S | Y | Y | Quality | ||
| NPR 8735.2A | 2.7.4(1) | 43163 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Government follow-up shall be performed to ensure effective accomplishment of contractor corrective/preventive actions. (Requirement 43163) | S | Y | Y | Quality | |||
| QAS-37 | NPD 8730.5 | 1.b.08.a | 42138 | Policy: NASA quality assurance programs shall: Investigative actions shall identify the proximate and root cause(s) of noncompliance and the scope/population of noncompliant items. (Requirement 42138) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.08.b | 42139 | Policy: NASA quality assurance programs shall: Corrective actions shall include the correction, replacement, repair, or authorized disposition of noncompliant items/conditions, implementation of preventive measures to eliminate the causes of noncompliance, and validation that implemented preventive measures have effectively eliminated recurrence of the noncompliant condition (recurrence control). (Requirement 42139) | S | Y | Y | Quality | |||
| NPR 8715.3C | 01.05.3 | 45668 | Institutional and Programmatic Safety Requirements: Program Management Roles and Responsibilities in the NASA Safety Program: Project Managers shall ensure that contractor operations and designs are evaluated for consistency and compliance with the safety and health provisions provided in their contractual agreements. (Requirement 45668) | S | Y | Y | Quality | |||
| NPR 8735.2A | 2.7.4(1) | 43163 | Government Contract Quality Assurance Requirements: Nonconformance Reporting and Corrective/Preventive Action: Government follow-up shall be performed to ensure effective accomplishment of contractor corrective/preventive actions. (Requirement 43163) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.9.1 | QAS-133 | NPR 8735.2A | 1.2.07.g | 43066 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Coordinate and integrate quality assurance functions performed by different parties to ensure that all of the requirements of Chapter 2 of this NPR are satisfied and to avoid duplication of effort. (Requirement 43066) | S | Y | Y | Quality |
| QAS-134 | NPR 8735.2A | 1.2.07.g | 43066 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Coordinate and integrate quality assurance functions performed by different parties to ensure that all of the requirements of Chapter 2 of this NPR are satisfied and to avoid duplication of effort. (Requirement 43066) | S | Y | Y | Quality | ||
| CxP 70059 | 5.2.9.2 | QAS-135 | NPD 8730.5 | 1.b.01 | 42128 | Policy: NASA quality assurance programs shall: Be designed and implemented in a manner that mitigates risks associated with noncompliance. Determination of risk considers the likelihood of noncompliance and the consequences associated with noncompliance, including the maturity, complexity, criticality, and value of work performed, as well as demonstrated experience with past quality system or program performance. (Requirement 42128) | S | Y | Y | Quality |
| NPR 8735.2A | 1.2.04.c | 43044 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Develop Program/Project Quality Assurance Surveillance Plans (PQASP) per Chapter 3 of this NPR using input/support provided by the Center SMA office. (Requirement 43044) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.a | 43060 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Identify key processes, products, documents, records, and performance characteristics requiring Government assurance actions and determine the appropriate level and type of Government contract quality assurance actions to be applied. (Requirement 43060) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.b | 43061 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Support the program/project manager and contracting officer in the development of the PQASP, LODs, and/or quality assurance support contracts. (Requirement 43061) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.f | 43065 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Continuously evaluate the adequacy of the PQASP, LOD, and/or support contract based on contractor performance and other changing risk factors. (Requirement 43065) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.d(1) | 43182 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Be initially prepared in conjunction with preparation of the Statement of Work and periodically adjusted thereafter based on changing risk factors as the program/project progresses through pre-award activities, Request for Proposal responses, and post-award activities. (Requirement 43182) | S | Y | Y | Quality | |||
| QAS-48 | NPD 8730.5 | 1.b.01 | 42128 | Policy: NASA quality assurance programs shall: Be designed and implemented in a manner that mitigates risks associated with noncompliance. Determination of risk considers the likelihood of noncompliance and the consequences associated with noncompliance, including the maturity, complexity, criticality, and value of work performed, as well as demonstrated experience with past quality system or program performance. (Requirement 42128) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.04 | 42133 | Policy: NASA quality assurance programs shall: Include prework assurance measures that provide increased confidence for meeting prescribed requirements (e.g., preaward surveys, qualified source selection, training), concurrent assurance measures to ensure that work is being performed in accordance with requirements (e.g., process control, process witnessing), and postwork assurance measures to ensure that work was properly performed (e.g., inspections, tests, record review, configuration control). (Requirement 42133) | S | Y | Y | Quality | |||
| NPD 8730.5 | 1.b.09 | 42140 | Policy: NASA quality assurance programs shall: Ensure clear and mutual understanding of prescribed quality requirements among organizations responsible for contracting or assigning work, performing work, and assuring conformity of work. (Requirement 42140) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.04.c | 43044 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Develop Program/Project Quality Assurance Surveillance Plans (PQASP) per Chapter 3 of this NPR using input/support provided by the Center SMA office. (Requirement 43044) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.a | 43060 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Identify key processes, products, documents, records, and performance characteristics requiring Government assurance actions and determine the appropriate level and type of Government contract quality assurance actions to be applied. (Requirement 43060) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.b | 43061 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Support the program/project manager and contracting officer in the development of the PQASP, LODs, and/or quality assurance support contracts. (Requirement 43061) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.c | 43062 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Provide detailed information concerning the resource(s) required to perform required quality assurance activities, including preparation of the NASA Center estimate of required delegated agency or surveillance support contract support (Requirement 43062) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.d | 43063 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure clear and mutual understanding of delegated/assigned quality assurance functions between NASA, the delegated agency, and quality assurance support contractors. (Requirement 43063) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.f | 43065 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Continuously evaluate the adequacy of the PQASP, LOD, and/or support contract based on contractor performance and other changing risk factors. (Requirement 43065) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.c(1) | 43180 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Incorporate applicable requirements from FAR Part 46, NFS Part 1846, NPD 8730.5, Chapter 2 of this NPR, and other related documents (e.g., Program/Project Plan, Risk Management Plan, contract, GMIP schedule). (Requirement 43180) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.d(1) | 43182 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Be initially prepared in conjunction with preparation of the Statement of Work and periodically adjusted thereafter based on changing risk factors as the program/project progresses through pre-award activities, Request for Proposal responses, and post-award activities. (Requirement 43182) | S | Y | Y | Quality | |||
| QAS-49 | NPD 8730.5 | 1.b.09 | 42140 | Policy: NASA quality assurance programs shall: Ensure clear and mutual understanding of prescribed quality requirements among organizations responsible for contracting or assigning work, performing work, and assuring conformity of work. (Requirement 42140) | S | Y | Y | Quality | ||
| NPR 8735.2A | 1.2.04.c | 43044 | Introduction: Roles and Responsibilities: Program and/or project managers are responsible for the quality of their assigned products and services. To that end, they shall: Develop Program/Project Quality Assurance Surveillance Plans (PQASP) per Chapter 3 of this NPR using input/support provided by the Center SMA office. (Requirement 43044) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.a | 43060 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Identify key processes, products, documents, records, and performance characteristics requiring Government assurance actions and determine the appropriate level and type of Government contract quality assurance actions to be applied. (Requirement 43060) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.b | 43061 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Support the program/project manager and contracting officer in the development of the PQASP, LODs, and/or quality assurance support contracts. (Requirement 43061) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.c | 43062 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Provide detailed information concerning the resource(s) required to perform required quality assurance activities, including preparation of the NASA Center estimate of required delegated agency or surveillance support contract support (Requirement 43062) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.d | 43063 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure clear and mutual understanding of delegated/assigned quality assurance functions between NASA, the delegated agency, and quality assurance support contractors. (Requirement 43063) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.a | 43177 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Describe the activities, metrics, control mechanisms, and organizations that will be conducting quality assurance functions for the program/project. (Requirement 43177) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.b(1) | 43178 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Be a consolidated and integrated document (i.e., not divided among various/separate documents). (Requirement 43178) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.c(1) | 43180 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Incorporate applicable requirements from FAR Part 46, NFS Part 1846, NPD 8730.5, Chapter 2 of this NPR, and other related documents (e.g., Program/Project Plan, Risk Management Plan, contract, GMIP schedule). (Requirement 43180) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.1.d(1) | 43182 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: The PQASP shall: Be initially prepared in conjunction with preparation of the Statement of Work and periodically adjusted thereafter based on changing risk factors as the program/project progresses through pre-award activities, Request for Proposal responses, and post-award activities. (Requirement 43182) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.1 | 43185 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Introduction. Identify the program/project under surveillance; summarize the program/project objectives; and summarize the contents of the applicable contract(s). (Requirement 43185) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.2 | 43186 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Objectives. Identify the specific outcomes of quality assurance actions in terms that are quantifiable and measurable. (Requirement 43186) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.3 | 43187 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Reference Documents. Identify documents related to performance of quality assurance functions (e.g., NASA Directives, the Program/Project Plan, the Risk Management Plan, program/project requirements documents, the contract, invoked quality system requirements). (Requirement 43187) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.4 | 43188 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Surveillance Functions. Identify the quality assurance surveillance functions to be performed for the program/project in accordance with Chapter 2 of this NPR and the following (Requirement 43188): | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.6 | 43218 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Surveillance Organization. Identify the organizational entities of the program/project that will be performing surveillance (i.e., NASA, the delegated agency, and/or quality assurance support contractors), their assigned responsibilities, and their authority to act. (Requirement 43218) | S | Y | Y | Quality | |||
| NPR 8735.2A | 3.2.2.7 | 43219 | Program/Project Quality Assurance Surveillance Plan (PQASP): PQASP Preparation and Content: PQASPs shall contain the following: Quality Assurance Resources. Identify the personnel, funding, and material resources to be applied to the program/project quality assurance effort. (Requirement 43219) | S | Y | Y | Quality | |||
| CxP 70059 | 5.2.9.3 | QAS-136 | NPR 8735.2A | 1.2.07.g | 43066 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Coordinate and integrate quality assurance functions performed by different parties to ensure that all of the requirements of Chapter 2 of this NPR are satisfied and to avoid duplication of effort. (Requirement 43066) | S | Y | Y | Quality |
| QAS-50 | NPD 8700.1C | 5.e.4 | 1085 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Use and distribute lessons learned to enhance the probability of mission success and establish recurrence control through a closed-loop corrective/preventative action system. (Requirement 1085) | S | Y | Y | Quality | ||
| CxP 70059 | 6 | PRA-1 | NPR 8705.5 | 0.P.2.b | 32944 | This NPR shall be used specifically for programs/projects that provide aerospace products or capabilities; i.e., space and aeronautics systems, flight and ground systems, technology demonstration/validation, and operations (Requirement 32944). | S | Y | Y | PRA |
| NPR 8705.5 | 1.1.4 | 32960 | All PRAs shall be conducted in accordance with this NPR (Requirement 32960). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.2.1 | 32964 | NASA program and project managers shall use the criteria in paragraph 1.2.3, Table 1, and paragraph 1.2.4 to determine when a PRA must be conducted and the scope to be implemented (Requirement 32964). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.2.2 | 32965 | The PRA approach for each project shall be described in the projects risk management plan and submitted for Governing Program Management Committee (GPMC) review and approval at the project formulation decision milestone (Requirement 32965). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.2.3.1.1(2) | 32969 | Decision-making for projects involving complex systems in high-stakes programmatic contexts shall be supported by a full-scope PRA with consideration of uncertainty (Requirement 32969). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.2.3.1.3(2) | 32972 | Uncertainty analysis shall be performed to provide the decision-maker with a full appreciation of the overall degree of uncertainty about the PRA results and an understanding of which sources of uncertainty are critical to the results that guide decisions (Requirement 32972). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.2.3.2.3 | 32976 | Similar to a full-scope PRA, sources of uncertainties that have a strong effect on the limited-scope PRA results and insights shall be identified and quantified (Requirement 32976). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.2.3.3.2 | 32979 | In a simplified PRA, the sources of uncertainties that have the strongest effects on the PRA results shall be identified and, in cases where they affect the management decision process, shall be quantified (Requirement 32979). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.3.1 | 32984 | After determining the level at which the PRA shall be conducted, the program or project manager shall document the PRA decision and its basis in the program/project risk plan (Requirement 32984). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5 | 33017 | Program/project managers and other decision-makers shall conduct and use PRA with the best state-of-practice methods and data to support management decisions to improve safety and performance (Requirement 33017). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 7 and 12.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.1 | 33018 | Program/project managers shall document PRA decisions, justifications and plans for implementing and conducting PRAs in program/project risk management plans (Requirement 33018). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.5.1 | 33023 | If the residual risk, as shown through the use of PRA, is deemed unacceptable as defined by program requirements, the program/project manager shall consider modifying the project through design, operation, upgrade, and maintenance, and implement management decisions to reduce risk to an acceptable level as defined at the appropriate level of the Agency; i.e., Headquarters, Center, Enterprise, program, or project, as appropriate (Requirement 33023). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.01.3(1) | 33031 | The process and techniques provided in the Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners shall be used for conducting PRAs in accordance with this NPR (Requirement 33031). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.02.1(2) | 33035 | The objective of the risk assessment shall be well defined and, associated with it, the appropriate undesirable consequences of interest (called end states ) that are consistent with the stated study objective(s) must be identified and selected (Requirement 33035). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.02.2(1) | 33037 | Depending on the scope of the PRA, applicable configuration, time frame, and rules for considering initiators (i.e., whether to include external events such as micrometeoroids) shall be defined (Requirement 33037). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.03(2) | 33040 | If the PRA is performed on an existing system that has been operated for some time, the engineering information shall be on an as-built and as-operated basis; if the PRA is conducted on a new or proposed system, then the as-designed system shall be used as the basis (Requirement 33040). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.04.1 | 33043 | The complete set of initiating events (see Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, sections 15.1.7/8 and 15.2.5) shall be identified (Requirement 33043). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.04.1.2(1) | 33045 | The initiating events shall be identified, analyzed, and screened to ensure that they have the potential to initiate accident scenarios leading to the defined end states (Requirement 33045). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.04.1.3(2) | 33048 | When initiating events are treated as a group, their frequencies shall be logically summed up to derive the group initiator frequency (Requirement 33048). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 4, 5, and 15.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.05(1) | 33050 | Scenario Modeling. The PRA shall identify and evaluate potential scenarios leading to undesired consequences (Requirement 33050). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.06(1) | 33052 | Failure Modeling. The PRA shall evaluate the failure (type and probability) of each event in the scenarios identified above (Requirement 33052). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.07(1) | 33054 | Quantification. The PRA shall quantify the scenarios (Requirement 33054). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.08(2) | 33057 | Any PRA insights reported to decision-makers shall include an appreciation of the overall degree of uncertainty about the results and an understanding of which sources of uncertainty are critical (Requirement 33057). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.11(1) | 33061 | Data Analysis. The PRA shall conduct data analyses to support quantification (Requirement 33061). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.1.2(1) | 33068 | The PRA team shall include a PRA expert who has had training and extensive experience in the application and conduct of PRAs, preferably for several different types of systems. The PRA expert shall serve as the PRA Technical Authority, with technical decision-making authority for the PRA (Requirement 33068). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.2(2) | 33075 | Terminology shall also be consistent with what is used in the program/project in order to facilitate risk communication (Requirement 33075). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.3(2) | 33077 | Contributors to undesired events shall be quantified on the basis of existing data (Requirement 33077). This requires that some analyses of previous mission failures be performed. (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.4.1(1) | 33085 | A PRA shall follow quality assurance principles and practices that are analogous to those in other engineering fields and practices (Requirement 33085). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.5.1 | 33101 | In order to enhance the quality and credibility of a PRA study, an independent peer review of the work shall be conducted for all full-scope PRAs (Requirement 33101) and should also be conducted for all other PRAs. | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.5.1.1 | 33102 | This review shall be carried out by independent peers, that is, recognized PRA experts who are not involved in the study and have no stake in it (Requirement 33102). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.5.1.3 | 33104 | In general, this review shall concentrate on the appropriateness of methods, information, sources, judgments, and assumptions as well as their application to the program/project/system being evaluated and its objective(s) (Requirement 33104). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1 | 33108 | A PRA shall be comprehensive, balanced, and tailored (Requirement 33108). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.1 | 33109 | A comprehensive PRA shall consider the complete environment and all factors that pertain to the system being assessed, including, as appropriate to satisfy its stated objective(s), the safety of the public, astronauts, pilots, and the NASA workforce; protection of high-value equipment and property; adverse impacts on the environment; national interests; and security (Requirement 33109). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.2 | 33110 | A balanced PRA shall ensure that the scope considers issues of safety, operation, and mission assurance; is conducted at a level commensurate with the level of risk; and is timely to assist program/project management in limiting risk (Requirement 33110). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.3 | 33111 | A tailored PRA shall ensure that the level of detail is commensurate with the complexity of the hazards, scope, and objective(s) of the mission/project being evaluated (Requirement 33111). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2.a | 33113 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33113), including: Identification of the elements of risk (initiators, hazards, scenarios, probabilities, and consequences) (Requirement 33113). | S | Y | Y | PRA | |||
| NPR 8715.3C | 02.5.2.2.c | 45919 | System Safety: Core Requirements for System Safety Processes: System Safety Modeling: System safety engineers shall: Ensure, for Category I and II programs/projects, probabilistic risk assessment techniques are used for system safety analysis. (Requirement 45919) | S | Y | Y | Safety | |||
| PRA-10 | NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.06(1) | 33052 | Failure Modeling. The PRA shall evaluate the failure (type and probability) of each event in the scenarios identified above (Requirement 33052). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.2(2) | 33075 | Terminology shall also be consistent with what is used in the program/project in order to facilitate risk communication (Requirement 33075). | S | Y | Y | PRA | |||
| PRA-11 | NPR 8705.5 | 1.2.3.1.3(2) | 32972 | Uncertainty analysis shall be performed to provide the decision-maker with a full appreciation of the overall degree of uncertainty about the PRA results and an understanding of which sources of uncertainty are critical to the results that guide decisions (Requirement 32972). | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.02.2(1) | 33037 | Depending on the scope of the PRA, applicable configuration, time frame, and rules for considering initiators (i.e., whether to include external events such as micrometeoroids) shall be defined (Requirement 33037). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.2(2) | 33075 | Terminology shall also be consistent with what is used in the program/project in order to facilitate risk communication (Requirement 33075). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.1 | 33109 | A comprehensive PRA shall consider the complete environment and all factors that pertain to the system being assessed, including, as appropriate to satisfy its stated objective(s), the safety of the public, astronauts, pilots, and the NASA workforce; protection of high-value equipment and property; adverse impacts on the environment; national interests; and security (Requirement 33109). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.2 | 33110 | A balanced PRA shall ensure that the scope considers issues of safety, operation, and mission assurance; is conducted at a level commensurate with the level of risk; and is timely to assist program/project management in limiting risk (Requirement 33110). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.3 | 33111 | A tailored PRA shall ensure that the level of detail is commensurate with the complexity of the hazards, scope, and objective(s) of the mission/project being evaluated (Requirement 33111). | S | Y | Y | PRA | |||
| PRA-12 | NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.2(2) | 33075 | Terminology shall also be consistent with what is used in the program/project in order to facilitate risk communication (Requirement 33075). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1 | 33108 | A PRA shall be comprehensive, balanced, and tailored (Requirement 33108). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.1 | 33109 | A comprehensive PRA shall consider the complete environment and all factors that pertain to the system being assessed, including, as appropriate to satisfy its stated objective(s), the safety of the public, astronauts, pilots, and the NASA workforce; protection of high-value equipment and property; adverse impacts on the environment; national interests; and security (Requirement 33109). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.2 | 33110 | A balanced PRA shall ensure that the scope considers issues of safety, operation, and mission assurance; is conducted at a level commensurate with the level of risk; and is timely to assist program/project management in limiting risk (Requirement 33110). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.3 | 33111 | A tailored PRA shall ensure that the level of detail is commensurate with the complexity of the hazards, scope, and objective(s) of the mission/project being evaluated (Requirement 33111). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2 | 33112 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33112), including: | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2.a | 33113 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33113), including: Identification of the elements of risk (initiators, hazards, scenarios, probabilities, and consequences) (Requirement 33113). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2.b | 33114 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33114), including: Recommended controls (preventive and mitigating features, compensatory measures) needed to reduce and manage risks (Requirement 33114). | S | Y | Y | PRA | |||
| PRA-13 | NPR 8705.5 | 2.04.1 | 33043 | The complete set of initiating events (see Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, sections 15.1.7/8 and 15.2.5) shall be identified (Requirement 33043). | S | Y | Y | PRA | ||
| NPR 8705.5 | 2.04.1.2(1) | 33045 | The initiating events shall be identified, analyzed, and screened to ensure that they have the potential to initiate accident scenarios leading to the defined end states (Requirement 33045). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.1 | 33109 | A comprehensive PRA shall consider the complete environment and all factors that pertain to the system being assessed, including, as appropriate to satisfy its stated objective(s), the safety of the public, astronauts, pilots, and the NASA workforce; protection of high-value equipment and property; adverse impacts on the environment; national interests; and security (Requirement 33109). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.2 | 33110 | A balanced PRA shall ensure that the scope considers issues of safety, operation, and mission assurance; is conducted at a level commensurate with the level of risk; and is timely to assist program/project management in limiting risk (Requirement 33110). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.3 | 33111 | A tailored PRA shall ensure that the level of detail is commensurate with the complexity of the hazards, scope, and objective(s) of the mission/project being evaluated (Requirement 33111). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2 | 33112 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33112), including: | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2.a | 33113 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33113), including: Identification of the elements of risk (initiators, hazards, scenarios, probabilities, and consequences) (Requirement 33113). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2.b | 33114 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33114), including: Recommended controls (preventive and mitigating features, compensatory measures) needed to reduce and manage risks (Requirement 33114). | S | Y | Y | PRA | |||
| PRA-14 | NPR 8705.5 | 1.3.2 | 32985 | The program or project manager shall brief the GPMC on the PRA decision and the rationale during the formulation phase of the program or project (Requirement 32985). (See NPR 1000.3, The NASA Organization, paragraph 6.6.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.3.3 | 32986 | Any disputes concerning the PRA decision and level of implementation shall be elevated to the next level of Program Management Committee (Requirement 32986). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.2 | 33019 | The program or project manager shall brief the GPMC on the PRA decision and the rationale during the formulation phase of the program or project (Requirement 33019). | S | Y | Y | PRA | |||
| PRA-2 | NPR 8705.5 | 1.2.3.1.1(2) | 32969 | Decision-making for projects involving complex systems in high-stakes programmatic contexts shall be supported by a full-scope PRA with consideration of uncertainty (Requirement 32969). | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.5.1 | 33023 | If the residual risk, as shown through the use of PRA, is deemed unacceptable as defined by program requirements, the program/project manager shall consider modifying the project through design, operation, upgrade, and maintenance, and implement management decisions to reduce risk to an acceptable level as defined at the appropriate level of the Agency; i.e., Headquarters, Center, Enterprise, program, or project, as appropriate (Requirement 33023). | S | Y | Y | PRA | |||
| PRA-3 | NPR 8705.5 | 1.4.5 | 33017 | Program/project managers and other decision-makers shall conduct and use PRA with the best state-of-practice methods and data to support management decisions to improve safety and performance (Requirement 33017). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 7 and 12.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.3 | 33020 | Program/project managers shall maintain and safeguard records resulting from PRAs in accordance with the guidelines in NPR 1441.1, NASA Records Retention Schedule (Requirement 33020). | S | Y | Y | PRA | |||
| PRA-4 | NPR 8705.5 | 1.4.5.1 | 33018 | Program/project managers shall document PRA decisions, justifications and plans for implementing and conducting PRAs in program/project risk management plans (Requirement 33018). | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.1.2(1) | 33068 | The PRA team shall include a PRA expert who has had training and extensive experience in the application and conduct of PRAs, preferably for several different types of systems. The PRA expert shall serve as the PRA Technical Authority, with technical decision-making authority for the PRA (Requirement 33068). | S | Y | Y | PRA | |||
| PRA-5 | NPR 8705.5 | 1.4.5.1 | 33018 | Program/project managers shall document PRA decisions, justifications and plans for implementing and conducting PRAs in program/project risk management plans (Requirement 33018). | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| PRA-6 | NPR 8705.5 | 1.4.5 | 33017 | Program/project managers and other decision-makers shall conduct and use PRA with the best state-of-practice methods and data to support management decisions to improve safety and performance (Requirement 33017). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 7 and 12.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.5 | 33022 | Program/project managers shall update design, operating, and implementation plans to reflect insights from PRA and use the insights gathered from PRA to reinforce or modify existing relevant management decisions or to generate new management decisions (Requirement 33022). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.03(2) | 33040 | If the PRA is performed on an existing system that has been operated for some time, the engineering information shall be on an as-built and as-operated basis; if the PRA is conducted on a new or proposed system, then the as-designed system shall be used as the basis (Requirement 33040). | S | Y | Y | PRA | |||
| PRA-7 | NPR 8705.5 | 1.4.5 | 33017 | Program/project managers and other decision-makers shall conduct and use PRA with the best state-of-practice methods and data to support management decisions to improve safety and performance (Requirement 33017). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 7 and 12.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.3 | 33020 | Program/project managers shall maintain and safeguard records resulting from PRAs in accordance with the guidelines in NPR 1441.1, NASA Records Retention Schedule (Requirement 33020). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.02.1(2) | 33035 | The objective of the risk assessment shall be well defined and, associated with it, the appropriate undesirable consequences of interest (called end states ) that are consistent with the stated study objective(s) must be identified and selected (Requirement 33035). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.02.2(1) | 33037 | Depending on the scope of the PRA, applicable configuration, time frame, and rules for considering initiators (i.e., whether to include external events such as micrometeoroids) shall be defined (Requirement 33037). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.04.1 | 33043 | The complete set of initiating events (see Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, sections 15.1.7/8 and 15.2.5) shall be identified (Requirement 33043). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.04.1.2(1) | 33045 | The initiating events shall be identified, analyzed, and screened to ensure that they have the potential to initiate accident scenarios leading to the defined end states (Requirement 33045). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.05(1) | 33050 | Scenario Modeling. The PRA shall identify and evaluate potential scenarios leading to undesired consequences (Requirement 33050). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.06(1) | 33052 | Failure Modeling. The PRA shall evaluate the failure (type and probability) of each event in the scenarios identified above (Requirement 33052). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.07(1) | 33054 | Quantification. The PRA shall quantify the scenarios (Requirement 33054). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.08(2) | 33057 | Any PRA insights reported to decision-makers shall include an appreciation of the overall degree of uncertainty about the results and an understanding of which sources of uncertainty are critical (Requirement 33057). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.11(1) | 33061 | Data Analysis. The PRA shall conduct data analyses to support quantification (Requirement 33061). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.2(2) | 33075 | Terminology shall also be consistent with what is used in the program/project in order to facilitate risk communication (Requirement 33075). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.3(2) | 33077 | Contributors to undesired events shall be quantified on the basis of existing data (Requirement 33077). This requires that some analyses of previous mission failures be performed. (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1 | 33108 | A PRA shall be comprehensive, balanced, and tailored (Requirement 33108). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.1 | 33109 | A comprehensive PRA shall consider the complete environment and all factors that pertain to the system being assessed, including, as appropriate to satisfy its stated objective(s), the safety of the public, astronauts, pilots, and the NASA workforce; protection of high-value equipment and property; adverse impacts on the environment; national interests; and security (Requirement 33109). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.2 | 33110 | A balanced PRA shall ensure that the scope considers issues of safety, operation, and mission assurance; is conducted at a level commensurate with the level of risk; and is timely to assist program/project management in limiting risk (Requirement 33110). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.1.3 | 33111 | A tailored PRA shall ensure that the level of detail is commensurate with the complexity of the hazards, scope, and objective(s) of the mission/project being evaluated (Requirement 33111). | S | Y | Y | PRA | |||
| NPR 8705.5 | 4.1.2.a | 33113 | PRA implementation procedures shall reflect and incorporate the results of project risk analysis (Requirement 33113), including: Identification of the elements of risk (initiators, hazards, scenarios, probabilities, and consequences) (Requirement 33113). | S | Y | Y | PRA | |||
| PRA-8 | NPR 8705.5 | 1.4.5 | 33017 | Program/project managers and other decision-makers shall conduct and use PRA with the best state-of-practice methods and data to support management decisions to improve safety and performance (Requirement 33017). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 7 and 12.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.06(1) | 33052 | Failure Modeling. The PRA shall evaluate the failure (type and probability) of each event in the scenarios identified above (Requirement 33052). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.2(2) | 33075 | Terminology shall also be consistent with what is used in the program/project in order to facilitate risk communication (Requirement 33075). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.3(2) | 33077 | Contributors to undesired events shall be quantified on the basis of existing data (Requirement 33077). This requires that some analyses of previous mission failures be performed. (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| PRA-9 | NPR 8705.5 | 1.4.5 | 33017 | Program/project managers and other decision-makers shall conduct and use PRA with the best state-of-practice methods and data to support management decisions to improve safety and performance (Requirement 33017). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapters 7 and 12.) | S | Y | Y | PRA | ||
| NPR 8705.5 | 1.4.5.1 | 33018 | Program/project managers shall document PRA decisions, justifications and plans for implementing and conducting PRAs in program/project risk management plans (Requirement 33018). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.3 | 33020 | Program/project managers shall maintain and safeguard records resulting from PRAs in accordance with the guidelines in NPR 1441.1, NASA Records Retention Schedule (Requirement 33020). | S | Y | Y | PRA | |||
| NPR 8705.5 | 1.4.5.4 | 33021 | Program/project managers shall adequately and clearly communicate PRA results and insights that explicitly include initial assumptions, residual uncertainties, and significant risk drivers to all involved program/project staff and management, and ensure that the PRA results and insights, as well as their implications regarding systems design, operation, and upgrade, are reviewed, analyzed, properly interpreted, and understood (Requirement 33021). (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.01.2(1) | 33029 | The process that shall be used for conducting a typical scenario-based PRA involves objective definition, system familiarization, identification of initiating events, scenario modeling, failure modeling, quantification, uncertainty analysis, sensitivity analysis, importance ranking, and data analysis (Requirement 33029). | S | Y | Y | PRA | |||
| NPR 8705.5 | 2.06(1) | 33052 | Failure Modeling. The PRA shall evaluate the failure (type and probability) of each event in the scenarios identified above (Requirement 33052). | S | Y | Y | PRA | |||
| NPR 8705.5 | 3.2.3(2) | 33077 | Contributors to undesired events shall be quantified on the basis of existing data (Requirement 33077). This requires that some analyses of previous mission failures be performed. (See Probabilistic Risk Assessment Procedures Guide for NASA Managers and Practitioners, chapter 13.) | S | Y | Y | PRA | |||
| CxP 70059 | 7.1 | SWA-1 | NASA STD 8719.13B | 4.1.2 | 33394 | The requirements of this Standard shall apply to all safety-critical software elements regardless of the presence of non-software hazard controls or mitigations (e.g., operator intervention, hardware overrides). (Requirement 33394) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.1 | 33655 | The requirements of this Standard shall continue to be applicable after the safety-critical software has been released for operations. (Requirement 33655) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2 | 33656 | The software safety requirements to specify, develop, analyze, and test safety-critical software, shall apply to all changes made to the software or routine operational updates (e.g., mission specific database updates). (Requirement 33656) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.1.2 | 33238 | The software assurance program shall include processes for assurance of COTS, MOTS, and GOTS software addressing both the basic acquired software and any modifications or applications written to adopt them into the intended system. (Requirement 33238) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.1.3 | 33239 | The software assurance program shall include the disciplines of Software Quality, Software Safety, Software Reliability, and Software V&V. (Requirement 33239) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.2.2 | 33245 | The software assurance manager shall establish and maintain the interfaces with project management and ensure the working relationship between software assurance personnel and that of the project. (Requirement 33245) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.2.1 | 33299 | The requirements for NASA-STD-8719.13, NASA Software Safety Standard, shall be implemented. (Requirement 33299) | S | Y | Y | SWA | |||
| NPR 8715.3C | 03.14.4.1.c | 46203 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure that software may interface with test systems meets the requirements stated in Chapter 1 of this NPR. (Requirement 46203) Note: Software by itself is not hazardous; however, when interfaced with test hardware, software could command a hazardous condition in the hardware. See NASA-STD-8719.13, Software Safety Standard, for further information. | S | Y | Y | SWA | |||
| NPR 8715.3C | 03.15.8.1.a | 46267 | Operational Safety: Non-Ionizing Radiation: Laser Software: Project managers shall ensure that: Laser software provides safety precautions for fast-moving lasers and prevents misdirected laser operation. (Requirement 46267) | S | Y | Y | SWA | |||
| NPR 8715.3C | 03.15.8.1.b | 46268 | Operational Safety: Non-Ionizing Radiation: Laser Software: Project managers shall ensure that: Laser software development is subjected to a software safety analysis per Chapter 1 of this NPR. (Requirement 46268) | S | Y | Y | SWA | |||
| CxP 70059 | 7.2 | SWA-3 | NASA STD 8719.13B | 5.01.2.1.4 | 33428 | Program/project/facility management shall designate personnel to be responsible for the software safety program (e.g., software safety manager) of the project, program, or facility. (Requirement 33428) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.3.1 | 33434 | A software safety manager shall be assigned to each project, program or facility, with the responsibility to develop and implement the software safety processes and plans. (Requirement 33434) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.3.2 | 33441 | One or more personnel shall be assigned the responsibility for performing software safety analyses (or assuring it is properly conducted and documented). This person or persons shall be referred to in this document as the software safety personnel. (Requirement 33441) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1 | 33448 | At least one software assurance engineer shall be assigned responsibility for assuring that software safety is planned, approved, and implemented. (Requirement 33448) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.1 | 33449 | The software assurance engineer shall assure that software safety processes, product standards and procedures are followed. (Requirement 33449) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.2 | 33450 | The software assurance engineer shall be assigned responsibility for performing software safety assurance audits. (Requirement 33450) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1 | 33457 | Software safety assessment and planning shall be performed for each software acquisition, development, and maintenance activity, and for changes to legacy systems. (Requirement 33457) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1.1 | 33458 | Safety program reviews shall be planned and conducted to ensure proper implementation of the software safety program. (Requirement 33458) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.2 | 33459 | Software safety planning shall be implemented at a point in time sufficient to provide direction to personnel performing the software development and assurance activities. Ideally, software safety planning will begin at project conception or formulation. Legacy systems and projects already in development should determine, with input from Center or program SMA, how this Standard should be applied. (Requirement 33459) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.3 | 33460 | The software safety manager shall document software safety planning information in a Software Safety Plan. (Requirement 33460) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.4. | 33463 | The Software Safety Plan shall describe how the requirements specified by this Standard will be implemented. For example, this can be done by means of a matrix showing the relationship between requirements of this Standard and the activities specified in the plan. (Requirement 33463) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.5 | 33464 | The Software Safety Plan shall specify the activities to be carried out, the schedule on which they will be implemented, the personnel who will carry out the activities, the methodologies used, and the products that will result. (Requirement 33464) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6 | 33465 | The Software Safety Plan shall address the interrelationships among system safety, software assurance, software development efforts, and the Center or Program SMA organization. (Requirement 33465) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.1 | 33466 | If this project is a candidate for IV&V, the Software Safety Plan shall address, either specifically or by reference to the IV&V MOA, the role of IV&V for the safety-critical software and detail how IV&V will work with the software safety program and personnel. (Requirement 33466) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.2 | 33467 | The Software Safety Plan shall specifically address the mechanism by which safety-critical requirements are generated, implemented, tracked, and verified. (Requirement 33467) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.3 | 33468 | The Software Safety Plan shall specify procedures for ensuring prompt follow-up and satisfactory resolution of software safety concerns and recommendations. (Requirement 33468) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.4 | 33469 | The Software Safety Plan shall specify how the software safety activity schedule will be synchronized with related program/project activities. (Requirement 33469) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.05.1 | 33480 | The integration of software safety with the chosen software life cycle shall be documented in the project Software Safety Plan. (Requirement 33480) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.10.2 | 33525 | Software safety tasks shall be coordinated with the overall software assurance disciplines to eliminate duplication of effort. (Requirement 33525) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.11.2 | 33532 | The software safety manager shall approve the approach. (Requirement 33532) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.3 | 33631 | Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs, FTAs, shall be used to determine which failures to test for, and the level of failure combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33631) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.4 | 33632 | System testing shall verify the correct and safe operation of the system under system load, stress, and off-nominal conditions. (Requirement 33632) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.5 | 33633 | System testing shall verify correct and safe operations in all anticipated operational and off-nominal configurations. (Requirement 33633) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.1(1) | 33174 | The acquirer shall identify a person with responsibility for software assurance, e.g, a software assurance manager. (Requirement 33174) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.02 | 33178 | Ensure that projects with safety-critical software comply with the requirements in NASA STD-8719.13 and the software assurance requirements and activities for the assessed Class of software. (Requirement 33178) | S | Y | Y | SWA | |||
| CxP 70059 | 7.3.1 | SWA-10 | NASA-STD-8739.8 | 5.1.2.03(1) | 33179 | Ensure that Class A and B projects, which require the most software assurance, follow all the requirements of Sections 5, 6, and 7. (Requirement 33179) See Table 1 for requirements and implementation of those requirements by Software Class. While the implementation of requirements for Class B will be tailored to some degree, the actual requirements are not. Class C software may address tailoring the requirements based on what is applicable for the software engineering requirements of NPR 7150.2 and according to any potential risks specific to the planned operational or development environment. Class D software may have the most requirements tailoring, matching the assurance activities to the less formal development activities. An experienced software assurance engineer must work closely with the project to assess the software for the project and tailor the software assurance activities accordingly. (See Table 1) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | |||
| SWA-11 | NASA-STD-8739.8 | 5.1.2.04 | 33184 | Assure all classifications of software are compared and agreed upon with the project. (Requirement 33184) As some projects may have multiple software tasks, each may need to be assessed separately. The assurance and engineering ITAs will need to settle any disagreements in classification. | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | |||
| SWA-12 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.1.2.07 | 33187 | Assure contractual statements include appropriate oversight/insight requirements, including needed deliverables (e.g, records, documents, reports). (Requirement 33187) | S | Y | Y | SWA | |||
| SWA-13 | NASA STD 8719.13B | 5.01.3.1.6 | 33440 | The software safety manager shall provide inputs to management regarding requirements to be imposed on a contractor(s) for development of safety-critical software. These requirements include, at a minimum, documentation, process definition, quality assurance and verification and validation requirements as they relate to assuring safety of the system. (Requirement 33440) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.01.4.1 | 33448 | At least one software assurance engineer shall be assigned responsibility for assuring that software safety is planned, approved, and implemented. (Requirement 33448) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.1 | 33449 | The software assurance engineer shall assure that software safety processes, product standards and procedures are followed. (Requirement 33449) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.2 | 33450 | The software assurance engineer shall be assigned responsibility for performing software safety assurance audits. (Requirement 33450) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.3 | 33451 | The software assurance engineer shall report software safety process non conformances to software and system safety personnel, to project/program/facility management. (Requirement 33451) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1 | 33457 | Software safety assessment and planning shall be performed for each software acquisition, development, and maintenance activity, and for changes to legacy systems. (Requirement 33457) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1.1 | 33458 | Safety program reviews shall be planned and conducted to ensure proper implementation of the software safety program. (Requirement 33458) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.2 | 33459 | Software safety planning shall be implemented at a point in time sufficient to provide direction to personnel performing the software development and assurance activities. Ideally, software safety planning will begin at project conception or formulation. Legacy systems and projects already in development should determine, with input from Center or program SMA, how this Standard should be applied. (Requirement 33459) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.3 | 33460 | The software safety manager shall document software safety planning information in a Software Safety Plan. (Requirement 33460) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.4. | 33463 | The Software Safety Plan shall describe how the requirements specified by this Standard will be implemented. For example, this can be done by means of a matrix showing the relationship between requirements of this Standard and the activities specified in the plan. (Requirement 33463) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.5 | 33464 | The Software Safety Plan shall specify the activities to be carried out, the schedule on which they will be implemented, the personnel who will carry out the activities, the methodologies used, and the products that will result. (Requirement 33464) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6 | 33465 | The Software Safety Plan shall address the interrelationships among system safety, software assurance, software development efforts, and the Center or Program SMA organization. (Requirement 33465) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.1 | 33466 | If this project is a candidate for IV&V, the Software Safety Plan shall address, either specifically or by reference to the IV&V MOA, the role of IV&V for the safety-critical software and detail how IV&V will work with the software safety program and personnel. (Requirement 33466) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.2 | 33467 | The Software Safety Plan shall specifically address the mechanism by which safety-critical requirements are generated, implemented, tracked, and verified. (Requirement 33467) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.3 | 33468 | The Software Safety Plan shall specify procedures for ensuring prompt follow-up and satisfactory resolution of software safety concerns and recommendations. (Requirement 33468) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.4 | 33469 | The Software Safety Plan shall specify how the software safety activity schedule will be synchronized with related program/project activities. (Requirement 33469) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.05.1 | 33480 | The integration of software safety with the chosen software life cycle shall be documented in the project Software Safety Plan. (Requirement 33480) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.10.2 | 33525 | Software safety tasks shall be coordinated with the overall software assurance disciplines to eliminate duplication of effort. (Requirement 33525) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.1 | 33594 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33594) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.1 | 33609 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33609) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.3 | 33631 | Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs, FTAs, shall be used to determine which failures to test for, and the level of failure combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33631) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.4 | 33632 | System testing shall verify the correct and safe operation of the system under system load, stress, and off-nominal conditions. (Requirement 33632) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.5 | 33633 | System testing shall verify correct and safe operations in all anticipated operational and off-nominal configurations. (Requirement 33633) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.08 | 33188 | Prepare a preliminary acquirer program/project software assurance plan documenting the planned level of software assurance effort and activities required and the necessary resources using the template provided in Appendix B. (Requirement 33188) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.8.1.2 | 33234 | Ensure that the retirement plan includes archival and eventual disposal of software assurance records and documents created over the life of the program/project in accordance with the requirements of NPR 1441.1, NASA Records Retention Schedules. (Requirement 33234) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.1.4 | 33240 | When IV&V has been selected for a project, the provider shall coordinate with IV&V personnel to share data and information. (Requirement 33240) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.1(1) | 33251 | Each software provider shall establish and maintain a software assurance plan that addresses all software development and maintenance activities. (Requirement 33251) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.1 | 33254 | Conform to IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans. (Requirement 33254) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.3 | 33256 | If there is any conflict between Section 6.0 or Section 7.0 of this Standard and IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans, this Standard shall take precedence. (Requirement 33256) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.4.1 | 33258 | The provider shall submit any proposed deviations from or modification to the baselined software assurance plan to the acquirer as a formal change request. (Requirement 33258) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.03 | 33282 | Software products and related documentation have been evaluated, according to the software assurance plan. (Requirement 33282) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.1 | 33292 | Those software life cycle processes employed for the project adhere to the applicable plans. (Requirement 33292) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.5 | 33296 | All management, engineering, and assurance processes are audited for compliance with applicable plans. (Requirement 33296) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.2.4 | 33302 | Periodic reviews and/or audits shall be conducted for compliance with the defined software safety process for acquisition, development, and assurance of safety-critical software. (Requirement 33302) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.5.3 | 33321 | When the IV&V function is required, the provider shall provide all required information to NASA IV&V Facility personnel. (Requirement 33321) (This requirement includes specifying on the contracts and subcontracts, IV&V's access to system and software products and personnel.) | S | Y | Y | SWA | |||
| SWA-14 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.1.2.09 | 33189 | Verify that the RFP/MOU/MOA address software quality metrics (see definition in Section 3.1 of the Standard). (Requirement 33189) | S | Y | Y | SWA | |||
| SWA-15 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.1.2.10 | 33190 | Participate in the process to identify, analyze, track, and control procurement/development risks. (Requirement 33190) | S | Y | Y | SWA | |||
| SWA-9 | NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.01 | 33177 | Ensure completion of the Software Assurance Classification Assessment in Appendix A, for each project, including software management agreement on the results. (Requirement 33177) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.3 | 33209 | Ensure that acquirer software assurance staff performs tasks to provide insight into whether the provider is adhering to approved software assurance, management, and development plans and procedures and that these plans and procedures are effectively fulfilling their purpose. (Requirement 33209) These tasks may include activities such as audits, reviews, analyses, and assessments. | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.4 | 33210 | Ensure that acquirer software assurance staff performs tasks to provide oversight of the provider's management, assurance, and engineering processes. Specifically, reviews, audits, and evaluations may be performed to ensure adherence to and effectiveness of approved plans and procedures. (Requirement 33210) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.5 | 33211 | Assure that both deliverable and any designated non-deliverable software development products have proper configuration management. (Requirement 33211) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.9.1 | 33273 | The provider shall flow down the requirements of this Standard to any subcontractor who develops, tests, maintains, operates, or provides services for the software. (Requirement 33273) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.9.2 | 33274 | The provider shall assure that the subcontractors satisfy the requirements of this Standard. (Requirement 33274) | S | Y | Y | SWA | |||
| CxP 70059 | 7.3.2 | SWA-16 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 5.2.1.1 | 33193 | Evaluate the proposals to verify that the software assurance requirements in the RFP have been addressed. (Requirement 33193) | S | Y | Y | SWA | |||
| SWA-17 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.2.1.2 | 33194 | Participate in pre-award surveys when such surveys are requested. (Requirement 33194) | S | Y | Y | SWA | |||
| SWA-18 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.2.1.3 | 33195 | Participate in contract negotiation to ensure that all software engineering, software assurance, management, and development requirements have been addressed and, where appropriate, are included in any resulting contracts. (Requirement 33195) | S | Y | Y | SWA | |||
| NPR 8715.3C | 09.3.1.e | 46674 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: Project managers shall: Use the software safety requirements in NASA-STD-8719.13, Software Safety Standard, and NASA-STD-8739.8, Software Assurance Standard, as the basis for contracts, memoranda of understanding, and other documents related to software. (Requirement 46674) | S | Y | Y | Safety | |||
| SWA-19 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.2.1.4 | 33196 | Coordinate with project management to perform an updated Software Assurance Classification Assessment with the accepted proposal information and defined software assurance development approach. (Requirement 33196) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.2.1.5 | 33197 | Apply the updated Software Assurance Classification Assessment results to update the software assurance requirements. (Requirement 33197) | S | Y | Y | SWA | |||
| SWA-21 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.2.1.6 | 33198 | Ensure that each Software Assurance Classification Assessment Report is maintained and made available to the SMA director, SMA office, SMO, project management, and/or Center Director upon request. (Requirement 33198) | S | Y | Y | SWA | |||
| CxP 70059 | 7.3.3 | SWA-22 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 5.3.1.1 | 33201 | Verify that the provider's software assurance plan meets contractual requirements. (Requirement 33201) | S | Y | Y | SWA | |||
| SWA-23 | NASA-STD-8739.8 | 5.1.2.05 | 33185 | Apply software assurance requirements in Section 5 for the acquirer software assurance activities, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33185) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.3.1.2 | 33202 | Verify that the acquirer's software assurance plan and the provider's software assurance plan are consistent, compatible, and are baselined. (Requirement 33202) | S | Y | Y | SWA | |||
| NPR 8715.3C | 09.3.2.f | 46684 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Coordinate any matter regarding proposed deviations to safety requirements of 48 CFR Part 1823.70, Safety and Health, with the OSMA, or designated representative. (Requirement 46684) | S | Y | Y | Safety | |||
| CxP 70059 | 7.3.4 | SWA-119 | NASA-STD-8739.8 | 5.4.1.1 | 33207 | Provide surveillance to assure that both the acquirer and provider software assurance functions are performed according to their specific software assurance plans and the contract. (Requirement 33207) | S | Y | Y | SWA |
| SWA-120 | NASA-STD-8739.8 | 5.4.1.2 | 33208 | Verify that the provider has developed and maintained processes for assurance of COTS, MOTS, and GOTS software addressing both the basic acquired software and any modifications or applications written to adopt them into the intended system. (Requirement 33208) | S | Y | Y | SWA | ||
| CxP 70059 | 7.3.5 | SWA-24 | NASA-STD-8739.8 | 5.5.1.2 | 33217 | Ensure that any acquirer facilities (e.g, buildings, hardware) are prepared to receive and install the software. (Requirement 33217) | S | Y | Y | SWA |
| NPR 8715.3C | 09.3.2.f | 46684 | Safety and Risk Management for NASA Contracts: Authority and Responsibility: System Safety Managers, COs, and COTRs shall: Coordinate any matter regarding proposed deviations to safety requirements of 48 CFR Part 1823.70, Safety and Health, with the OSMA, or designated representative. (Requirement 46684) | S | Y | Y | Safety | |||
| SWA-25 | NASA-STD-8739.8 | 5.5.1.4 | 33219 | Assure that all acquisition lessons learned are recorded and entered into the NASA lessons learned database. (Requirement 33219) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 6.6.2 | 33263 | Software assurance records shall include recommended preventive measures, corrective actions, and lessons learned. (Requirement 33263) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.4.5 | 33314 | Software assurance shall collect and maintain software assurance records showing the participation of software assurance staff in verification and validation efforts, such as minutes, records, artifacts, and signature on test reports. (Requirement 33314) | S | Y | Y | SWA | |||
| NPD 8700.1C | 5.e.4 | 1085 | RESPONSIBILITY: Program and project managers are responsible for the safety and mission success of their program/projects. Program and project managers shall-- Use and distribute lessons learned to enhance the probability of mission success and establish recurrence control through a closed-loop corrective/preventative action system. (Requirement 1085) | S | Y | Y | Quality | |||
| CxP 70059 | 7.3.6 | SWA-28 | NASA STD 8719.13B | 5.09.2 | 33519 | All changes, modifications, and patches made to safety-critical requirements, design, code, systems, equipment, test plans, procedures, simulators, models, test suites, or criteria shall be evaluated to determine the effect of the proposed change on system safety. (Requirement 33519) | S | Y | Y | SWA |
| NASA STD 8719.13B | 7.2.1.2 | 33659 | Software safety personnel shall concur on any changes to basic, as built, or approved upgrades of the operational software. (Requirement 33659) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.6.1.2 | 33223 | Depending upon the operational environment and the criticality of operation, ensure that software assurance processes include a periodic audit of the operations to ensure any changes to the software or software induced operational workarounds have been reviewed and approved. (Requirement 33223) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.6.2(1) | 33224 | Software assurance staff shall perform periodic operational assessments to ensure baseline management of software requirements, design, code, and documentation and to ensure review and approval of software changes or software induced operational workarounds. (Requirement 33224) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.5 | 33296 | All management, engineering, and assurance processes are audited for compliance with applicable plans. (Requirement 33296) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.2.4 | 33302 | Periodic reviews and/or audits shall be conducted for compliance with the defined software safety process for acquisition, development, and assurance of safety-critical software. (Requirement 33302) | S | Y | Y | SWA | |||
| CxP 70059 | 7.3.7 | SWA-122 | NASA-STD-8739.8 | 5.7.1.1 | 33228 | Ensure that software assurance processes are in place for software maintenance. (Requirement 33228) | S | Y | Y | SWA |
| SWA-29 | NASA-STD-8739.8 | 5.7.1.2 | 33229 | Assure the transfer and maintenance of any licenses, simulators, models, and test suites from the developer to NASA, or the designated maintenance contractor. (Requirement 33229) | S | Y | Y | SWA | ||
| SWA-30 | NASA-STD-8739.8 | 5.7.1.3 | 33230 | Assure that any metrics collected on the software, along with any trending and reliability data, are transferred to the maintenance organization and maintained in order to better understand and predict problem areas in the software. (Requirement 33230) | S | Y | Y | SWA | ||
| CxP 70059 | 7.3.8 | SWA-31 | NASA-STD-8739.8 | 5.8.1.1 | 33233 | Assure that software engineering and management prepare, approve, and execute a retirement plan. (Requirement 33233) | S | Y | Y | SWA |
| SWA-32 | NASA STD 8719.13B | 7.4 | 33663 | The requirements of this Standard expire for a particular facility or system only upon the retirement of that facility or system. (Requirement 33663) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 7.4.1 | 33664 | When the facility or system is retired, there shall be a retirement plan which addresses the safe termination of operations, decommissioning, and retirement of that system or facility. (Requirement 33664) | S | Y | Y | SWA | |||
| CxP 70059 | 7.4.1 | SWA-35 | NASA STD 8719.13B | 5.01.2.2 | 33430 | Program/project/facility management shall ensure that the software safety program is planned and executed throughout the entire software life cycle. (Requirement 33430) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.3.1.6 | 33440 | The software safety manager shall provide inputs to management regarding requirements to be imposed on a contractor(s) for development of safety-critical software. These requirements include, at a minimum, documentation, process definition, quality assurance and verification and validation requirements as they relate to assuring safety of the system. (Requirement 33440) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1 | 33448 | At least one software assurance engineer shall be assigned responsibility for assuring that software safety is planned, approved, and implemented. (Requirement 33448) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.1 | 33449 | The software assurance engineer shall assure that software safety processes, product standards and procedures are followed. (Requirement 33449) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.2 | 33450 | The software assurance engineer shall be assigned responsibility for performing software safety assurance audits. (Requirement 33450) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1 | 33457 | Software safety assessment and planning shall be performed for each software acquisition, development, and maintenance activity, and for changes to legacy systems. (Requirement 33457) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1.1 | 33458 | Safety program reviews shall be planned and conducted to ensure proper implementation of the software safety program. (Requirement 33458) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.2 | 33459 | Software safety planning shall be implemented at a point in time sufficient to provide direction to personnel performing the software development and assurance activities. Ideally, software safety planning will begin at project conception or formulation. Legacy systems and projects already in development should determine, with input from Center or program SMA, how this Standard should be applied. (Requirement 33459) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.3 | 33460 | The software safety manager shall document software safety planning information in a Software Safety Plan. (Requirement 33460) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.4. | 33463 | The Software Safety Plan shall describe how the requirements specified by this Standard will be implemented. For example, this can be done by means of a matrix showing the relationship between requirements of this Standard and the activities specified in the plan. (Requirement 33463) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.5 | 33464 | The Software Safety Plan shall specify the activities to be carried out, the schedule on which they will be implemented, the personnel who will carry out the activities, the methodologies used, and the products that will result. (Requirement 33464) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6 | 33465 | The Software Safety Plan shall address the interrelationships among system safety, software assurance, software development efforts, and the Center or Program SMA organization. (Requirement 33465) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.1 | 33466 | If this project is a candidate for IV&V, the Software Safety Plan shall address, either specifically or by reference to the IV&V MOA, the role of IV&V for the safety-critical software and detail how IV&V will work with the software safety program and personnel. (Requirement 33466) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.2 | 33467 | The Software Safety Plan shall specifically address the mechanism by which safety-critical requirements are generated, implemented, tracked, and verified. (Requirement 33467) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.3 | 33468 | The Software Safety Plan shall specify procedures for ensuring prompt follow-up and satisfactory resolution of software safety concerns and recommendations. (Requirement 33468) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.4 | 33469 | The Software Safety Plan shall specify how the software safety activity schedule will be synchronized with related program/project activities. (Requirement 33469) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.05.1 | 33480 | The integration of software safety with the chosen software life cycle shall be documented in the project Software Safety Plan. (Requirement 33480) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.1 | 33594 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33594) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.1 | 33609 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33609) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.3 | 33631 | Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs, FTAs, shall be used to determine which failures to test for, and the level of failure combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33631) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.4 | 33632 | System testing shall verify the correct and safe operation of the system under system load, stress, and off-nominal conditions. (Requirement 33632) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.5 | 33633 | System testing shall verify correct and safe operations in all anticipated operational and off-nominal configurations. (Requirement 33633) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.8.1.2 | 33234 | Ensure that the retirement plan includes archival and eventual disposal of software assurance records and documents created over the life of the program/project in accordance with the requirements of NPR 1441.1, NASA Records Retention Schedules. (Requirement 33234) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.1.1 | 33237 | The provider shall plan, document, and implement a software assurance program for software development, operation, and maintenance activities. (Requirement 33237) This includes documentation of software assurance procedures, processes, tools, techniques, and methods to be used. | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.1.4 | 33240 | When IV&V has been selected for a project, the provider shall coordinate with IV&V personnel to share data and information. (Requirement 33240) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.1(1) | 33251 | Each software provider shall establish and maintain a software assurance plan that addresses all software development and maintenance activities. (Requirement 33251) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.1 | 33254 | Conform to IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans. (Requirement 33254) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.3 | 33256 | If there is any conflict between Section 6.0 or Section 7.0 of this Standard and IEEE 730-2002, IEEE Standard for Software Quality Assurance Plans, this Standard shall take precedence. (Requirement 33256) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.03 | 33282 | Software products and related documentation have been evaluated, according to the software assurance plan. (Requirement 33282) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.1 | 33292 | Those software life cycle processes employed for the project adhere to the applicable plans. (Requirement 33292) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.5 | 33296 | All management, engineering, and assurance processes are audited for compliance with applicable plans. (Requirement 33296) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.2.4 | 33302 | Periodic reviews and/or audits shall be conducted for compliance with the defined software safety process for acquisition, development, and assurance of safety-critical software. (Requirement 33302) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.5.3 | 33321 | When the IV&V function is required, the provider shall provide all required information to NASA IV&V Facility personnel. (Requirement 33321) (This requirement includes specifying on the contracts and subcontracts, IV&V's access to system and software products and personnel.) | S | Y | Y | SWA | |||
| SWA-37 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 6.1.5 | 33241 | The software assurance program shall describe what metrics will be collected and reported in regards to the software assurance program activities. (Requirement 33241) | S | Y | Y | SWA | |||
| CxP 70059 | 7.4.2 | SWA-38 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 6.2.1(1) | 33243 | The provider shall identify the person responsible for directing and managing the software assurance program; e.g, a software assurance manager. (Requirement 33243) | S | Y | Y | SWA | |||
| SWA-39 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 6.2.4 | 33247 | The software assurance manager shall conduct and document periodic reviews of the software assurance process. (Requirement 33247) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.1 | 33292 | Those software life cycle processes employed for the project adhere to the applicable plans. (Requirement 33292) | S | Y | Y | SWA | |||
| CxP 70059 | 7.4.3 | SWA-40 | NASA STD 8719.13B | 7.2.1.2 | 33659 | Software safety personnel shall concur on any changes to basic, as built, or approved upgrades of the operational software. (Requirement 33659) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.5 | 33260 | Software Assurance Approval Authority. The software assurance manager shall have approval authority on the establishment and composition of all software baselines and any changes to the baselines before submission to the acquirer. (Requirement 33260) This includes changes to software plans, procedures, verification approaches, requirements, design, and code. | S | Y | Y | SWA | |||
| CxP 70059 | 7.4.4 | SWA-41 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 6.7.1 | 33265 | The provider shall prepare software assurance status reports that include: a. Highlights of organization and key personnel changes. b. Assurance accomplishments and resulting software assurance program metrics for activities such as inspection and test, reviews, contractor/subcontractor surveys, audits. c. Subcontractor assurance accomplishments, including items listed above, plus summaries of acceptance and certification reports. d. Significant problems, their status, solutions, and remedial and preventive actions. e. Trends in software quality metric data (e.g, defect types, location, priority/criticality). f. Plans for upcoming software assurance activities. g. Recommendations and lessons learned. (Requirement 33265) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.1 | SWA-42 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA |
| CxP 70059 | 7.5.2.1 | SWA-43 | NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.3 | 33584 | Improperly decomposed requirements shall be documented for project level resolution. (Requirement 33584) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1 | 33587 | All functional software safety requirements shall be incorporated into the software design. (Requirement 33587) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.b | 33643 | The analysis methodology shall include the following steps, at a minimum: Verify that the requirements verification evaluation, inspection, or demonstration data meet the requirements of section 6.4.2 and sub-sections (Requirement 33643) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.5.1.1 | 33216 | Ensure that an audit (e.g, Functional Configuration Audit, Physical Configuration Audit) is performed prior to delivery to assure that all delivered products are complete, contain the proper versions, and that all discrepancies, open work, and deviations and waivers are properly documented and approved. (Requirement 33216) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.5.1.3 | 33218 | Assure that all acceptance documentation is present, including signed certifications. (Requirement 33218) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.2.5 | 33248 | The software assurance manager shall conduct and document periodic reviews, audits, and assessments of the development process and products. (Requirement 33248) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.2 | 33255 | In addition, address how the provider will implement the requirements of Sections 6.0 and 7.0 of this Standard. (Requirement 33255) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.01 | 33280 | All of the required plans (e.g, configuration management, risk management, provider's assurance plan, software management plan) are documented, adhere to applicable standards and procedures, are mutually consistent, and are being executed. (Requirement 33280) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.02 | 33281 | All software requirements are defined, traceable from one life cycle phase to another, and analyzed in a manner that is measurable or otherwise verifiable. (Requirement 33281) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.03 | 33282 | Software products and related documentation have been evaluated, according to the software assurance plan. (Requirement 33282) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.04 | 33283 | Project documentation, including plans, procedures, requirements, design, verification documentation, reports, schedules, and records and any changes to them are reviewed for impact to the quality of the product. (Requirement 33283) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.05 | 33284 | Formal and acceptance software testing are witnessed by software assurance personnel to verify satisfactory completion and outcome. (Requirement 33284) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.06 | 33285 | Lower level testing results and software development folders are updated, audited, and/or reviewed for completeness. (Requirement 33285) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.07 | 33286 | Software quality metrics are in place and are used to ensure the quality and safety of the software products being delivered. (Requirement 33286) Trends in software quality metrics are reported to assist in risk mitigation. | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.08 | 33287 | The software development plans specify the standards and procedures for management, acquisition, engineering, and assurance activities. (Requirement 33287) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.09 | 33288 | The software is verified (e.g, tested, analyzed, measured) for compliance with functional and performance requirements. (Requirement 33288) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.10 | 33289 | The status and quality of the software are presented at formal reviews. (Requirement 33289) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.11 | 33290 | Problems with products are reported during participation in formal and informal reviews (e.g, inspections, peer reviews, test readiness reviews, requirements reviews) along with regular reporting to project management and engineering during team meetings. (Requirement 33290) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.2 | 33293 | Problems found with implementation of the software life cycle processes, including management, engineering, and assurance, are documented, tracked, and resolved through the problem reporting and corrective action process and through discussions with the project manager. (Requirement 33293) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.2.2 | SWA-44 | NASA STD 2202-93 | 0 | 57095 | NASA Standard 2202-93 is represented by this single entry. If this entry is being viewed from a filter, list, or traceability report, then the metadata applies to the document as a whole. | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.b | 33643 | The analysis methodology shall include the following steps, at a minimum: Verify that the requirements verification evaluation, inspection, or demonstration data meet the requirements of section 6.4.2 and sub-sections (Requirement 33643) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.2.5 | 33248 | The software assurance manager shall conduct and document periodic reviews, audits, and assessments of the development process and products. (Requirement 33248) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.2 | 33255 | In addition, address how the provider will implement the requirements of Sections 6.0 and 7.0 of this Standard. (Requirement 33255) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.1 | 33292 | Those software life cycle processes employed for the project adhere to the applicable plans. (Requirement 33292) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.2 | 33293 | Problems found with implementation of the software life cycle processes, including management, engineering, and assurance, are documented, tracked, and resolved through the problem reporting and corrective action process and through discussions with the project manager. (Requirement 33293) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.3 | 33294 | The software engineering practices, development environment, test environment, and libraries employed for the project adhere to applicable standards and procedures. (Requirement 33294) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.4 | 33295 | Formal reviews and inspections are monitored and address software quality issues. (Requirement 33295) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.5 | 33296 | All management, engineering, and assurance processes are audited for compliance with applicable plans. (Requirement 33296) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.6 | 33297 | The software quality metrics process is assessed for compliance to appropriate documentation or requirements. (Requirement 33297) Trending is accomplished following the defined software quality metrics process. | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.3.3 | 33306 | Collection and classification of defects found during/from software assurance and programmatic/project formal and informal reviews shall be maintained. (Requirement 33306) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.3 | SWA-45 | NASA STD 8719.13B | 5.01.2.4 | 33432 | Program/project/facility management shall implement a process or mechanism to document, trace, communicate, and close software safety concerns that result from safety analyses or design reviews, with concurrence of the safety personnel. (Requirement 33432) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.4.1.3 | 33451 | The software assurance engineer shall report software safety process non conformances to software and system safety personnel, to project/program/facility management. (Requirement 33451) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.08.1.2 | 33509 | Software safety personnel shall approve safety-critical discrepancy report closures. (Requirement 33509) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.4 | 33648 | Improperly implemented safety features shall be input into the problem reporting system for project-level resolution. (Requirement 33648) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.6 | 33212 | Assure that problem reports, discrepancies from reviews, and test anomalies are documented, addressed, analyzed, and tracked to resolution. (Requirement 33212) | S | Y | Y | SWA | |||
| SWA-46 | NASA STD 8719.13B | 5.01.2.4 | 33432 | Program/project/facility management shall implement a process or mechanism to document, trace, communicate, and close software safety concerns that result from safety analyses or design reviews, with concurrence of the safety personnel. (Requirement 33432) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.01.4.1.3 | 33451 | The software assurance engineer shall report software safety process non conformances to software and system safety personnel, to project/program/facility management. (Requirement 33451) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.08.2 | 33510 | All discrepancy reports shall be reviewed regularly for safety impacts by software safety personnel. (Requirement 33510) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.4 | 33648 | Improperly implemented safety features shall be input into the problem reporting system for project-level resolution. (Requirement 33648) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.6 | 33212 | Assure that problem reports, discrepancies from reviews, and test anomalies are documented, addressed, analyzed, and tracked to resolution. (Requirement 33212) | S | Y | Y | SWA | |||
| SWA-47 | NASA STD 8719.13B | 5.01.2.4 | 33432 | Program/project/facility management shall implement a process or mechanism to document, trace, communicate, and close software safety concerns that result from safety analyses or design reviews, with concurrence of the safety personnel. (Requirement 33432) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.01.4.1.3 | 33451 | The software assurance engineer shall report software safety process non conformances to software and system safety personnel, to project/program/facility management. (Requirement 33451) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.08.3 | 33511 | All software changes including those that result from problem or discrepancy resolution shall be evaluated for potential safety impact, including the creation of new hazard contributions and impacts, modification of existing hazard controls or mitigations, or detrimental effect on safety-critical software or hardware. (Requirement 33511) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.4 | 33648 | Improperly implemented safety features shall be input into the problem reporting system for project-level resolution. (Requirement 33648) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1.2 | 33659 | Software safety personnel shall concur on any changes to basic, as built, or approved upgrades of the operational software. (Requirement 33659) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.6 | 33212 | Assure that problem reports, discrepancies from reviews, and test anomalies are documented, addressed, analyzed, and tracked to resolution. (Requirement 33212) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.4 | SWA-49 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 7.3.1 | 33304 | Software assurance shall assure that fault tolerance and redundancy have been specified, implemented correctly, and verified by testing. (Requirement 33304) | S | Y | Y | SWA | |||
| SWA-50 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 7.3.2 | 33305 | Software reliability analyses and measurements, including trends and metric data, shall be included in appropriate status reports to the software assurance manager and project management. This data is to be used to trace and recommend actions on specific modules which may have less than desired reliability. (Requirement 33305) | S | Y | Y | SWA | |||
| SWA-51 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 7.3.4 | 33307 | The use of software quality metrics shall be documented, monitored, analyzed and tracked during each stage of development and across development and operational phases. (Requirement 33307) Examples include fault counts by severity levels, time between discovery and removal of faults, and number of faults found in a time period per lines of code or number of function points. | S | Y | Y | SWA | |||
| SWA-52 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 7.3.5 | 33308 | Trend analyses shall be performed on the software quality metrics and made available for lessons learned or root cause analyses. (Requirement 33308) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.5 | SWA-53 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 7.4.1 | 33310 | Software assurance shall assure that software V&V activities occur according to established plans, policies, procedures, and standards. (Requirement 33310) | S | Y | Y | SWA | |||
| SWA-54 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 7.4.2 | 33311 | Software assurance shall participate in the formal and informal reviews. (Requirement 33311) Such activities include peer reviews, inspections, and milestone reviews (e.g, software requirements review, design reviews, test readiness reviews, certification readiness reviews). | S | Y | Y | SWA | |||
| SWA-55 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 7.4.3 | 33312 | Software assurance shall witness or review/audit results of software testing and demonstration. (Requirement 33312) | S | Y | Y | SWA | |||
| SWA-56 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA | ||
| NASA-STD-8739.8 | 5.4.1.7 | 33213 | Assure that software products (e.g, software requirements, preliminary design, detailed design, use cases, code, models, simulators, test data, inspection results, flow diagrams) are reviewed and software quality metrics (e.g, defect metrics) are collected, analyzed, trended, and documented. (Requirement 33213) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.07 | 33286 | Software quality metrics are in place and are used to ensure the quality and safety of the software products being delivered. (Requirement 33286) Trends in software quality metrics are reported to assist in risk mitigation. | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.4.4 | 33313 | Software assurance shall use defect data collected by the project to analyze software quality metrics. (Requirement 33313) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.6 | SWA-66 | NASA-STD-8739.8 | 5.1.2.06 | 33186 | Apply software assurance requirements in Sections 6 and 7 for the provider software assurance activities for each RFP/MOU/MOA, based on both the results of the Software Assurance Classification Assessment and Table 1 for guidance. (Requirement 33186) | S | Y | Y | SWA |
| CxP 70059 | 7.5.7.1 | SWA-68 | NASA STD 8719.13B | 4.1.1.1 | 33383 | Until proven otherwise, based on the following evaluation criteria, all software within a safety critical system shall be assumed to be safety critical. (Requirement 33383) | S | Y | Y | SWA |
| NASA STD 8719.13B | 4.1.1.3(1) | 33390 | The software evaluation shall occur during the concept or formulation phase, prior to the acquisition or planning for the given software for all new projects. (Requirement 33390) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.1 | 33424 | Program/project/facility management shall be responsible for software safety planning within the project. (Requirement 33424) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.1.2 | 33426 | Program/project/facility management shall ensure that the acquired or developed system is periodically evaluated for the use of software in safety-critical functions. (Requirement 33426) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.1.1 | 33571 | Software safety requirements shall be derived from the system safety requirements, environmental requirements, standards, program specification, vehicle or facility requirements, interface requirements, system hazard reports, and system hazard analyses [ref. section 4.2]. (Requirement 33571) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.2 | SWA-124 | NASA STD 8719.13B | 4.1.1.5 | 33393 | The Center or responsible Program Safety and Mission Assurance (SMA) organization shall approve the evaluation conclusions. (Requirement 33393) | S | Y | Y | SWA |
| SWA-69 | NASA STD 8719.13B | 4.1.1 | 33382 | When the system is determined to be safety-critical, the software shall be evaluated for its contribution to the safety of the system. (Requirement 33382) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 4.1.1.1 | 33383 | Until proven otherwise, based on the following evaluation criteria, all software within a safety critical system shall be assumed to be safety critical. (Requirement 33383) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.2.b | 33386 | Software shall be classified as safety-critical if it meets at least one of the following criteria: Processes data or analyzes trends that lead directly to safety decisions (e.g., determining when to turn power off to a wind tunnel to prevent system destruction). (Requirement 33386) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.2.c | 33387 | Software shall be classified as safety-critical if it meets at least one of the following criteria: Provides full or partial verification or validation of safety-critical systems, including hardware or software subsystems. (Requirement 33387) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.2.Note 4-1: | 33388 | If data is used to make safety decisions (either by a human or the system), then the data is safety-critical, as is all the software that acquires, processes, and transmits the data. However, data that may provide safety information but is not required for safety or hazard control (such as engineering telemetry) is not safety-critical. (Requirement 33388) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.3(1) | 33390 | The software evaluation shall occur during the concept or formulation phase, prior to the acquisition or planning for the given software for all new projects. (Requirement 33390) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.1 | 33424 | Program/project/facility management shall be responsible for software safety planning within the project. (Requirement 33424) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.1.2 | 33426 | Program/project/facility management shall ensure that the acquired or developed system is periodically evaluated for the use of software in safety-critical functions. (Requirement 33426) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.1.1 | 33571 | Software safety requirements shall be derived from the system safety requirements, environmental requirements, standards, program specification, vehicle or facility requirements, interface requirements, system hazard reports, and system hazard analyses [ref. section 4.2]. (Requirement 33571) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| SWA-70 | NASA STD 8719.13B | 4.1.1.1 | 33383 | Until proven otherwise, based on the following evaluation criteria, all software within a safety critical system shall be assumed to be safety critical. (Requirement 33383) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 4.1.1.2.a | 33385 | Software shall be classified as safety-critical if it meets at least one of the following criteria: Resides in a safety-critical system (as determined by a hazard analysis) AND at least one of the following apply: 1) Causes or contributes to a hazard. 2) Provides control or mitigation for hazards. 3) Controls safety-critical functions. 4) Processes safety-critical commands or data (see note 4-1 below). 5) Detects and reports, or takes corrective action, if the system reaches a specific hazardous state. 6) Mitigates damage if a hazard occurs. 7) Resides on the same system (processor) as safety-critical software (see note 4-2 below). (Requirement 33385) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.2.b | 33386 | Software shall be classified as safety-critical if it meets at least one of the following criteria: Processes data or analyzes trends that lead directly to safety decisions (e.g., determining when to turn power off to a wind tunnel to prevent system destruction). (Requirement 33386) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.2.c | 33387 | Software shall be classified as safety-critical if it meets at least one of the following criteria: Provides full or partial verification or validation of safety-critical systems, including hardware or software subsystems. (Requirement 33387) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.2.Note 4-1: | 33388 | If data is used to make safety decisions (either by a human or the system), then the data is safety-critical, as is all the software that acquires, processes, and transmits the data. However, data that may provide safety information but is not required for safety or hazard control (such as engineering telemetry) is not safety-critical. (Requirement 33388) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.1.3(1) | 33390 | The software evaluation shall occur during the concept or formulation phase, prior to the acquisition or planning for the given software for all new projects. (Requirement 33390) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.1.2 | 33394 | The requirements of this Standard shall apply to all safety-critical software elements regardless of the presence of non-software hazard controls or mitigations (e.g., operator intervention, hardware overrides). (Requirement 33394) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.1.2 | 33426 | Program/project/facility management shall ensure that the acquired or developed system is periodically evaluated for the use of software in safety-critical functions. (Requirement 33426) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1 | 33541 | The contract or MOA/MOU shall include provisions sufficient to assure that the contracted safety-critical software is developed according to this Standard. (Requirement 33541) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.1 | 33542 | The contract or MOA/MOU shall include all software safety deliverables, including the software safety plan, preliminary and subsequent hazard analyses, safety-critical software development audit reports, and verification reports. (Requirement 33542) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.2 | 33543 | The contract or MOA/MOU shall specify how the customer (i.e., the NASA program/project) will determine if the contractor is performing the software safety activities properly. (Requirement 33543) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.4 | 33545 | The contract or MOA/MOU shall specify that customer agreement is required for changes to baselined safety-critical software elements. (Requirement 33545) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.3 | SWA-127 | NASA STD 8719.13B | 5.01.2.1.1 | 33425 | Program/project/facility management shall consult with software safety personnel regarding the acquisition of safety-critical software and its applicability to this Standard. (Requirement 33425) | S | Y | Y | SWA |
| NASA-STD-8739.8 | 6.2.6 | 33249 | The software assurance manager shall assure that problems and risks are reported, recorded, addressed, and tracked to closure. (Requirement 33249) | S | Y | Y | SWA | |||
| SWA-75 | NASA STD 8719.13B | 4.2.1 | 33399 | Software safety personnel shall participate in system safety analyses, including the PHA, which is usually conducted during the concept or formulation phase. (Requirement 33399) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 4.2.1.1 | 33400 | Identified hazards associated with a specific requirement, design concept and/or operation shall be evaluated for softwares contribution to hazard causes, controls, or mitigations. (Requirement 33400) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.2.1.2 | 33401 | Software safety analyses shall be conducted in conjunction with the overall system safety analyses. System safety analyses provide input into software safety analyses, and results of the software analyses are provided back to the system safety program for use in updating and refining their analyses. These analyses, and the feedback loop, will continue throughout the system life cycle as more detail becomes available, including the design and verification of software safety features. (Requirement 33401) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.2.2.1 | 33403 | Identified software safety requirements and software hazard causes, contributors, and controls shall be recorded in an appropriate document and referenced in a safety plan. The requirements are usually documented in a section of the software requirements specification. The safety plan can be part of a system safety plan, a software management/development plan, a software or system assurance plan, or when warranted, in a standalone software safety plan. (Requirement 33403) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.3 | 33431 | Program/project/facility management shall ensure that software safety is an integral part of the overall system safety and software development efforts. (Requirement 33431) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.3.2.2 | 33443 | Software safety personnel shall review system hazard analyses for changes that impact the software subsystem. (Requirement 33443) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.3.2.3 | 33444 | Software safety personnel shall provide information on changes in safety-critical software to system safety personnel for evaluation and incorporation into system safety documents. (Requirement 33444) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.3.2.4 | 33445 | Software safety personnel shall support the system safety review process. (Requirement 33445) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.10.1 | 33524 | Acceptance or closure of any system-level hazards related to software shall be dependent on the successful conclusion of all assurance activities linked to its associated software safety requirements. (Requirement 33524) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.2 | 33583 | The documented results of the analysis, including any newly identified hazards, hazard causes, and improperly decomposed requirements, shall be provided to the responsible system safety personnel. (Requirement 33583) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.b | 33597 | The analysis methodology shall include the following steps, at a minimum: Verify that the design does not compromise any safety controls or processes, that any additional hazard, hazard cause, or hazard contribution is documented, and that the design maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider: timing constraints, hardware failures, common-mode failures, fault migration, communications, interrupts, concurrency, event sequence, fault tolerance, FDIR design, adverse environments, invalid inputs, off-the-shelf or reused software, design assumptions, information flow, (Requirement 33597) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.c | 33598 | The analysis methodology shall include the following steps, at a minimum: Verify that safety features incorporated in the design are adequate for their function. (Requirement 33598) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.d | 33599 | The analysis methodology shall include the following steps, at a minimum: Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs (Failure Modes and Effects Analysis), FTAs (Fault Tree Analysis), shall be used to help determine design features to prevent, mitigate or control failures and faults, and the level of failure/fault combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33599) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.e | 33600 | The analysis methodology shall include the following steps, at a minimum: Verify that any partitioning or isolation methods used in the design adequately isolate the safety-critical design elements from those that are non-safety-critical. This is particularly important with the incorporation of COTS. (Requirement 33600) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.3 | 33602 | The documented results of the analysis including any newly identified hazards, shall be provided to the responsible system safety personnel. (Requirement 33602) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.c | 33613 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the code implementation does not compromise any safety controls or processes, does not create any additional hazards, and maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider the elements detailed in 6.2.2.2.b. (Requirement 33613) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.3 | 33616 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33616) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| SWA-76 | NASA STD 8719.13B | 4.1.1.4 | 33392 | The evaluation results shall be recorded in an appropriate document. (Requirement 33392) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 4.2.1 | 33399 | Software safety personnel shall participate in system safety analyses, including the PHA, which is usually conducted during the concept or formulation phase. (Requirement 33399) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.2.1.1 | 33400 | Identified hazards associated with a specific requirement, design concept and/or operation shall be evaluated for softwares contribution to hazard causes, controls, or mitigations. (Requirement 33400) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.2.1.2 | 33401 | Software safety analyses shall be conducted in conjunction with the overall system safety analyses. System safety analyses provide input into software safety analyses, and results of the software analyses are provided back to the system safety program for use in updating and refining their analyses. These analyses, and the feedback loop, will continue throughout the system life cycle as more detail becomes available, including the design and verification of software safety features. (Requirement 33401) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 4.2.2.1 | 33403 | Identified software safety requirements and software hazard causes, contributors, and controls shall be recorded in an appropriate document and referenced in a safety plan. The requirements are usually documented in a section of the software requirements specification. The safety plan can be part of a system safety plan, a software management/development plan, a software or system assurance plan, or when warranted, in a standalone software safety plan. (Requirement 33403) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.2.3 | 33431 | Program/project/facility management shall ensure that software safety is an integral part of the overall system safety and software development efforts. (Requirement 33431) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.3.2.3 | 33444 | Software safety personnel shall provide information on changes in safety-critical software to system safety personnel for evaluation and incorporation into system safety documents. (Requirement 33444) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.3.2.4 | 33445 | Software safety personnel shall support the system safety review process. (Requirement 33445) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.10.1 | 33524 | Acceptance or closure of any system-level hazards related to software shall be dependent on the successful conclusion of all assurance activities linked to its associated software safety requirements. (Requirement 33524) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.10.2 | 33525 | Software safety tasks shall be coordinated with the overall software assurance disciplines to eliminate duplication of effort. (Requirement 33525) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.2 | 33583 | The documented results of the analysis, including any newly identified hazards, hazard causes, and improperly decomposed requirements, shall be provided to the responsible system safety personnel. (Requirement 33583) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.b | 33597 | The analysis methodology shall include the following steps, at a minimum: Verify that the design does not compromise any safety controls or processes, that any additional hazard, hazard cause, or hazard contribution is documented, and that the design maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider: timing constraints, hardware failures, common-mode failures, fault migration, communications, interrupts, concurrency, event sequence, fault tolerance, FDIR design, adverse environments, invalid inputs, off-the-shelf or reused software, design assumptions, information flow, (Requirement 33597) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.c | 33598 | The analysis methodology shall include the following steps, at a minimum: Verify that safety features incorporated in the design are adequate for their function. (Requirement 33598) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.d | 33599 | The analysis methodology shall include the following steps, at a minimum: Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs (Failure Modes and Effects Analysis), FTAs (Fault Tree Analysis), shall be used to help determine design features to prevent, mitigate or control failures and faults, and the level of failure/fault combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33599) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.e | 33600 | The analysis methodology shall include the following steps, at a minimum: Verify that any partitioning or isolation methods used in the design adequately isolate the safety-critical design elements from those that are non-safety-critical. This is particularly important with the incorporation of COTS. (Requirement 33600) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.3 | 33602 | The documented results of the analysis including any newly identified hazards, shall be provided to the responsible system safety personnel. (Requirement 33602) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.c | 33613 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the code implementation does not compromise any safety controls or processes, does not create any additional hazards, and maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider the elements detailed in 6.2.2.2.b. (Requirement 33613) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.3 | 33616 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33616) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.2.2 | 33300 | Software safety tasks shall be coordinated between system safety program, software development, and software assurance to ensure completion of required tasks and elimination of duplicate efforts. (Requirement 33300) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.4.1 | SWA-100 | NASA STD 8719.13B | 5.01.2.1.3 | 33427 | Program/project/facility management shall provide adequate resources, including trained software safety personnel (trained per NASA policy), schedule time, tools, and budget, to the software safety program. (Requirement 33427) | S | Y | Y | SWA |
| SWA-101 | NASA STD 8719.13B | 5.01.3.1.3 | 33437 | The software safety manager shall assure that risks affecting software safety are captured, addressed, and managed as part of program, project, and facility risk management processes, and those risks which could impose a system hazard are captured in the system hazard analyses. (Requirement 33437) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.01.3.2.1 | 33442 | Software safety personnel shall have the organizational freedom and authority to analyze and report software safety non-conformances. (Requirement 33442) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.13.1.3 | 33544 | The contract or MOA/MOU shall define a method for problem reporting and corrective action between the contractor and the customer. (Requirement 33544) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.2.6 | 33249 | The software assurance manager shall assure that problems and risks are reported, recorded, addressed, and tracked to closure. (Requirement 33249) | S | Y | Y | SWA | |||
| SWA-6 | NASA STD 8719.13B | 5.01.3.1.1 | 33435 | The software safety manager shall communicate software safety concerns directly to the project manager for resolution within the project. (Requirement 33435) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.01.3.1.2 | 33436 | The software safety manager shall follow the approved method to elevate software safety concerns that cannot be resolved within the project. (Requirement 33436) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.11.2 | 33532 | The software safety manager shall approve the approach. (Requirement 33532) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.4.2 | SWA-125 | NASA STD 8719.13B | 5.01.2.1 | 33424 | Program/project/facility management shall be responsible for software safety planning within the project. (Requirement 33424) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.4.1.1 | 33449 | The software assurance engineer shall assure that software safety processes, product standards and procedures are followed. (Requirement 33449) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.2 | 33450 | The software assurance engineer shall be assigned responsibility for performing software safety assurance audits. (Requirement 33450) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.4.3 | SWA-7 | NASA STD 8719.13B | 5.01.3.1.4 | 33438 | The software safety manager (or designee) shall be a part of any change control board that approves software modifications affecting safety-critical systems. (Requirement 33438) | S | Y | Y | SWA |
| NASA STD 8719.13B | 7.2.1.2 | 33659 | Software safety personnel shall concur on any changes to basic, as built, or approved upgrades of the operational software. (Requirement 33659) | S | Y | Y | SWA | |||
| SWA-72 | NASA STD 8719.13B | 5.01.2.2 | 33430 | Program/project/facility management shall ensure that the software safety program is planned and executed throughout the entire software life cycle. (Requirement 33430) | S | Y | Y | SWA | ||
| NPR 8715.3C | 03.14.4.1.c | 46203 | Operational Safety: Test Operations Safety: Test System Requirements: Project managers responsible for developing test systems shall: Ensure that software may interface with test systems meets the requirements stated in Chapter 1 of this NPR. (Requirement 46203) Note: Software by itself is not hazardous; however, when interfaced with test hardware, software could command a hazardous condition in the hardware. See NASA-STD-8719.13, Software Safety Standard, for further information. | S | Y | Y | SWA | |||
| NPR 8715.3C | 03.15.8.1.a | 46267 | Operational Safety: Non-Ionizing Radiation: Laser Software: Project managers shall ensure that: Laser software provides safety precautions for fast-moving lasers and prevents misdirected laser operation. (Requirement 46267) | S | Y | Y | SWA | |||
| NPR 8715.3C | 03.15.8.1.b | 46268 | Operational Safety: Non-Ionizing Radiation: Laser Software: Project managers shall ensure that: Laser software development is subjected to a software safety analysis per Chapter 1 of this NPR. (Requirement 46268) | S | Y | Y | SWA | |||
| SWA-73 | NASA STD 8719.13B | 5.09(1) | 33513 | Safety-critical software is managed in accordance with a software configuration management process that is approved by the software configuration manager. (Requirement 33513) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.09(2) | 33514 | Software configuration management is practiced during all phases of the software life cycle, from initiation of development through software maintenance, and is responsible for ensuring that any changes during the development and maintenance processes are made in a controlled and complete manner. (Requirement 33514) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.09.1 | 33516 | Software and documentation shall be placed under strict configuration control, including source code, executables, test plans and procedures, and associated data, prior to verification of the safety requirements. (Requirement 33516) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.09.1.1 | 33517 | All baselined safety-critical software and associated documentation, simulators, models, test suites, data, etc. shall be maintained in a controlled configuration management system. (Requirement 33517) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.09.1.2 | 33518 | The organization responsible for Software Configuration Management shall formally provide and document the release of safety-critical software. (Requirement 33518) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.2.1 | 33625 | Any simulators, test drivers and stubs, along with any test data, used for testing at the unit level shall be configuration controlled and documented. (Requirement 33625) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.2.2 | 33626 | Any simulators, test drivers and stubs, along with any test data, used for testing at the component level shall be configuration controlled and documented. (Requirement 33626) | S | Y | Y | SWA | |||
| SWA-74 | NASA STD 8719.13B | 5.09.2.1 | 33520 | Software safety personnel shall approve changes to baselined safety-critical software. (Requirement 33520) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 7.2.1.2 | 33659 | Software safety personnel shall concur on any changes to basic, as built, or approved upgrades of the operational software. (Requirement 33659) | S | Y | Y | SWA | |||
| SWA-77 | NASA STD 8719.13B | 5.01.2.3 | 33431 | Program/project/facility management shall ensure that software safety is an integral part of the overall system safety and software development efforts. (Requirement 33431) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.10.1 | 33524 | Acceptance or closure of any system-level hazards related to software shall be dependent on the successful conclusion of all assurance activities linked to its associated software safety requirements. (Requirement 33524) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.2 | 33583 | The documented results of the analysis, including any newly identified hazards, hazard causes, and improperly decomposed requirements, shall be provided to the responsible system safety personnel. (Requirement 33583) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.b | 33597 | The analysis methodology shall include the following steps, at a minimum: Verify that the design does not compromise any safety controls or processes, that any additional hazard, hazard cause, or hazard contribution is documented, and that the design maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider: timing constraints, hardware failures, common-mode failures, fault migration, communications, interrupts, concurrency, event sequence, fault tolerance, FDIR design, adverse environments, invalid inputs, off-the-shelf or reused software, design assumptions, information flow, (Requirement 33597) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.c | 33598 | The analysis methodology shall include the following steps, at a minimum: Verify that safety features incorporated in the design are adequate for their function. (Requirement 33598) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.d | 33599 | The analysis methodology shall include the following steps, at a minimum: Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs (Failure Modes and Effects Analysis), FTAs (Fault Tree Analysis), shall be used to help determine design features to prevent, mitigate or control failures and faults, and the level of failure/fault combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33599) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.e | 33600 | The analysis methodology shall include the following steps, at a minimum: Verify that any partitioning or isolation methods used in the design adequately isolate the safety-critical design elements from those that are non-safety-critical. This is particularly important with the incorporation of COTS. (Requirement 33600) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.c | 33613 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the code implementation does not compromise any safety controls or processes, does not create any additional hazards, and maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider the elements detailed in 6.2.2.2.b. (Requirement 33613) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.3 | 33616 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33616) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.b | 33643 | The analysis methodology shall include the following steps, at a minimum: Verify that the requirements verification evaluation, inspection, or demonstration data meet the requirements of section 6.4.2 and sub-sections (Requirement 33643) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.2 | 33255 | In addition, address how the provider will implement the requirements of Sections 6.0 and 7.0 of this Standard. (Requirement 33255) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5 | SWA-86 | NASA STD 8719.13B | 5.01.3.2.3 | 33444 | Software safety personnel shall provide information on changes in safety-critical software to system safety personnel for evaluation and incorporation into system safety documents. (Requirement 33444) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.3.2.4 | 33445 | Software safety personnel shall support the system safety review process. (Requirement 33445) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.06.3(08) | 33494 | The following documentation shall address safety-critical software: Safety Analyses and Reports (Requirement 33494) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.4 | 33585 | The software safety requirements analysis results shall be presented at project formal reviews and system-level safety reviews by the responsible safety organization. (Requirement 33585) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.4 | 33603 | The software safety design analysis results shall be presented at project formal reviews and system-level safety reviews. (Requirement 33603) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.4 | 33617 | The software safety code analysis results shall be presented at project formal reviews and system-level safety reviews. (Requirement 33617) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.10 | 33289 | The status and quality of the software are presented at formal reviews. (Requirement 33289) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5.1 | SWA-71 | NASA STD 8719.13B | 6.1.1.5 | 33575 | Any safety related constraints between the hardware and software shall be included in the software requirements documentation. That is, when the software and hardware work together to perform a safety critical function, their roles, precedence, and failure modes, are documented and understood. (Requirement 33575) | S | Y | Y | SWA |
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1.3.1 | 33591 | Software design documentation shall clearly identify all safety-critical design elements. (Requirement 33591) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| SWA-78 | NASA STD 8719.13B | 6.1.1.4 | 33574 | Software safety requirements shall include the modes or states of operation under which they are valid, and any modes or states in which they are not applicable. Note: These requirements are also referred to as must work and must not work functions. For example, the safety critical commands and checks which initiate a robotic arm movement must not work during system initiation or perhaps when in maintenance mode. (Requirement 33574) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| SWA-80 | NASA STD 8719.13B | 4.2.2 | 33402 | System safety analyses, including the PHA, subsequent system hazard analyses, and software safety analyses shall be used to create new, or identify existing, software requirements necessary to mitigate or resolve any hazards where software is a potential cause or contributor, or enable software to be used as a hazard control. Such requirements are designated as software safety requirements. (Requirement 33402) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 4.2.2.1 | 33403 | Identified software safety requirements and software hazard causes, contributors, and controls shall be recorded in an appropriate document and referenced in a safety plan. The requirements are usually documented in a section of the software requirements specification. The safety plan can be part of a system safety plan, a software management/development plan, a software or system assurance plan, or when warranted, in a standalone software safety plan. (Requirement 33403) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.1 | 33570 | Software safety requirements shall be developed and included in the software requirements specification. (Requirement 33570) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.1.1 | 33571 | Software safety requirements shall be derived from the system safety requirements, environmental requirements, standards, program specification, vehicle or facility requirements, interface requirements, system hazard reports, and system hazard analyses [ref. section 4.2]. (Requirement 33571) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.1.2 | 33572 | Software safety requirements, both generic and specific, shall be clearly identified as such in the software requirements specification. (Requirement 33572) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5.2 | SWA-126 | NASA STD 8719.13B | 5.01.3.1.6 | 33440 | The software safety manager shall provide inputs to management regarding requirements to be imposed on a contractor(s) for development of safety-critical software. These requirements include, at a minimum, documentation, process definition, quality assurance and verification and validation requirements as they relate to assuring safety of the system. (Requirement 33440) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.01.4.1 | 33448 | At least one software assurance engineer shall be assigned responsibility for assuring that software safety is planned, approved, and implemented. (Requirement 33448) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.1 | 33449 | The software assurance engineer shall assure that software safety processes, product standards and procedures are followed. (Requirement 33449) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.2 | 33450 | The software assurance engineer shall be assigned responsibility for performing software safety assurance audits. (Requirement 33450) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.01.4.1.3 | 33451 | The software assurance engineer shall report software safety process non conformances to software and system safety personnel, to project/program/facility management. (Requirement 33451) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1 | 33457 | Software safety assessment and planning shall be performed for each software acquisition, development, and maintenance activity, and for changes to legacy systems. (Requirement 33457) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.1.1 | 33458 | Safety program reviews shall be planned and conducted to ensure proper implementation of the software safety program. (Requirement 33458) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.2 | 33459 | Software safety planning shall be implemented at a point in time sufficient to provide direction to personnel performing the software development and assurance activities. Ideally, software safety planning will begin at project conception or formulation. Legacy systems and projects already in development should determine, with input from Center or program SMA, how this Standard should be applied. (Requirement 33459) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.3 | 33460 | The software safety manager shall document software safety planning information in a Software Safety Plan. (Requirement 33460) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.4. | 33463 | The Software Safety Plan shall describe how the requirements specified by this Standard will be implemented. For example, this can be done by means of a matrix showing the relationship between requirements of this Standard and the activities specified in the plan. (Requirement 33463) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.5 | 33464 | The Software Safety Plan shall specify the activities to be carried out, the schedule on which they will be implemented, the personnel who will carry out the activities, the methodologies used, and the products that will result. (Requirement 33464) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6 | 33465 | The Software Safety Plan shall address the interrelationships among system safety, software assurance, software development efforts, and the Center or Program SMA organization. (Requirement 33465) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.1 | 33466 | If this project is a candidate for IV&V, the Software Safety Plan shall address, either specifically or by reference to the IV&V MOA, the role of IV&V for the safety-critical software and detail how IV&V will work with the software safety program and personnel. (Requirement 33466) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.2 | 33467 | The Software Safety Plan shall specifically address the mechanism by which safety-critical requirements are generated, implemented, tracked, and verified. (Requirement 33467) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.3 | 33468 | The Software Safety Plan shall specify procedures for ensuring prompt follow-up and satisfactory resolution of software safety concerns and recommendations. (Requirement 33468) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.02.6.4 | 33469 | The Software Safety Plan shall specify how the software safety activity schedule will be synchronized with related program/project activities. (Requirement 33469) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.05.1 | 33480 | The integration of software safety with the chosen software life cycle shall be documented in the project Software Safety Plan. (Requirement 33480) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.10.2 | 33525 | Software safety tasks shall be coordinated with the overall software assurance disciplines to eliminate duplication of effort. (Requirement 33525) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1 | 33587 | All functional software safety requirements shall be incorporated into the software design. (Requirement 33587) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2 | 33593 | Software safety personnel shall analyze the software design. (Requirement 33593) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.1 | 33594 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33594) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.1 | 33609 | The analysis methodology shall be recorded in an appropriate document (e.g., software safety plan or software assurance plan). (Requirement 33609) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.3 | 33631 | Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs, FTAs, shall be used to determine which failures to test for, and the level of failure combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33631) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.4 | 33632 | System testing shall verify the correct and safe operation of the system under system load, stress, and off-nominal conditions. (Requirement 33632) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.5 | 33633 | System testing shall verify correct and safe operations in all anticipated operational and off-nominal configurations. (Requirement 33633) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.2.1 | 33292 | Those software life cycle processes employed for the project adhere to the applicable plans. (Requirement 33292) | S | Y | Y | SWA | |||
| SWA-83 | NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1.1 | 33588 | The software design shall identify safety design features and methods (e.g., inhibits, failure detection and recovery, interlocks, assertions, and partitions) that will be used to implement the software safety requirements. (Requirement 33588) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2 | 33593 | Software safety personnel shall analyze the software design. (Requirement 33593) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| SWA-85 | NASA STD 8719.13B | 5.01.3.1.5 | 33439 | The software safety manager shall provide input to management on the selection of off-the-shelf or previously created (reused) software for incorporation into safety-critical systems. (Requirement 33439) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.06.3(06) | 33492 | The following documentation shall address safety-critical software: Software Design Documentation (Requirement 33492) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1 | 33534 | All off-the-shelf and reused software shall be evaluated for the potential to impact safety-critical functions within the current system. (Requirement 33534) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.1 | 33535 | Safety-critical OTS and reused software shall undergo safety analysis that considers its ability to meet required safety functions, extra functionality, even if not planned for use that may be present, the impact on safety, and interfaces to developed code. (Requirement 33535) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.2 | 33536 | Software safety analysis shall consider the interactions of COTS software components with the developed software and any other COTS software that is part of the system. (Requirement 33536) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.b | 33579 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Examine the software safety requirements for ambiguities, inconsistencies, omissions, and undefined conditions. (Requirement 33579) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1.3 | 33590 | Design elements that implement safety-critical requirements or can potentially affect the safety-critical elements through failure or other mechanisms, shall be designated as safety-critical. (Requirement 33590) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2 | 33593 | Software safety personnel shall analyze the software design. (Requirement 33593) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5.3 | SWA-87 | NASA STD 8719.13B | 6.3.1 | 33605 | All software safety design features and methods shall be implemented in the software code. (Requirement 33605) | S | Y | Y | SWA |
| NASA STD 8719.13B | 6.3.1.1 | 33606 | The software coding standards shall incorporate requirements for clearly identifying safety-critical code and data within source code comments, and strongly discouraging unsafe language features such as pointers or memcopy, requiring these features to also be clearly identified and documented whenever used [ref. checklist in NASA GB 8719.13, NASA Software Safety Guidebook]. (Requirement 33606) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.1.2 | 33607 | The software coding standard shall be used in the development of software code. (Requirement 33607) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5.4 | SWA-90 | NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1.2 | 33589 | The software design shall allow software safety features and requirements to be thoroughly tested. (Requirement 33589) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1 | 33622 | All functional software safety requirements and safety-critical software elements shall be verified by testing. (Requirement 33622) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3 | 33628 | System and acceptance tests shall include software safety testing. (Requirement 33628) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2 | 33635 | Requirements that cannot be verified by test shall be verified by evaluation, inspection, or demonstration. (Requirement 33635) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2.1 | 33636 | The rationale for selecting evaluation, inspection, or demonstration shall be recorded in an appropriate document (e.g., system safety report, hazard analysis). (Requirement 33636) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2.3 | 33638 | The software safety personnel shall concur with both the rationale for not performing a test and the selected evaluation, inspection, or demonstration methodology used to verify the requirement. (Requirement 33638) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.09 | 33288 | The software is verified (e.g, tested, analyzed, measured) for compliance with functional and performance requirements. (Requirement 33288) | S | Y | Y | SWA | |||
| SWA-91 | NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.1.2 | 33589 | The software design shall allow software safety features and requirements to be thoroughly tested. (Requirement 33589) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.1 | 33623 | Testing shall verify that system hazards related to software have been eliminated or controlled to an acceptable level of risk. (Requirement 33623) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.2 | 33624 | Unit level tests and component level tests shall include software safety testing. (Requirement 33624) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3 | 33628 | System and acceptance tests shall include software safety testing. (Requirement 33628) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2 | 33635 | Requirements that cannot be verified by test shall be verified by evaluation, inspection, or demonstration. (Requirement 33635) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2.1 | 33636 | The rationale for selecting evaluation, inspection, or demonstration shall be recorded in an appropriate document (e.g., system safety report, hazard analysis). (Requirement 33636) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2.3 | 33638 | The software safety personnel shall concur with both the rationale for not performing a test and the selected evaluation, inspection, or demonstration methodology used to verify the requirement. (Requirement 33638) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| SWA-93 | NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| SWA-94 | NASA STD 8719.13B | 5.06.3(07) | 33493 | The following documentation shall address safety-critical software: Verification and Validation Plan (Requirement 33493) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.b | 33597 | The analysis methodology shall include the following steps, at a minimum: Verify that the design does not compromise any safety controls or processes, that any additional hazard, hazard cause, or hazard contribution is documented, and that the design maintains the system in a safe state during all modes of operation. The analysis should, at a minimum, consider: timing constraints, hardware failures, common-mode failures, fault migration, communications, interrupts, concurrency, event sequence, fault tolerance, FDIR design, adverse environments, invalid inputs, off-the-shelf or reused software, design assumptions, information flow, (Requirement 33597) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.c | 33598 | The analysis methodology shall include the following steps, at a minimum: Verify that safety features incorporated in the design are adequate for their function. (Requirement 33598) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.e | 33600 | The analysis methodology shall include the following steps, at a minimum: Verify that any partitioning or isolation methods used in the design adequately isolate the safety-critical design elements from those that are non-safety-critical. This is particularly important with the incorporation of COTS. (Requirement 33600) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.1 | 33629 | Correct and safe operation of the software in conjunction with system hardware and operator inputs shall be verified prior to system acceptance. (Requirement 33629) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3.2 | 33630 | System testing shall verify the correct and safe operation of the system in the presence of failures and faults including software, hardware, input, timing, memory corruption, communication, and other failures. (Requirement 33630) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| SWA-95 | NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.d | 33599 | The analysis methodology shall include the following steps, at a minimum: Safety analyses, such as PHAs, sub-system hazard analyses, FMEAs (Failure Modes and Effects Analysis), FTAs (Fault Tree Analysis), shall be used to help determine design features to prevent, mitigate or control failures and faults, and the level of failure/fault combinations to include (e.g., both a software and a hardware failure, or multiple concurrent hardware failures). (Requirement 33599) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.2.3 | 33627 | The results of unit level and component level tests and the test procedures, simulators, test suites, drivers, stubs and data shall be documented. (Requirement 33627) Note: When changes occur within software units or components containing safety-critical requirements, these test articles (simulator, test drivers, and stubs) may be used to conduct regression tests. | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.3 | 33628 | System and acceptance tests shall include software safety testing. (Requirement 33628) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2 | 33635 | Requirements that cannot be verified by test shall be verified by evaluation, inspection, or demonstration. (Requirement 33635) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2.1 | 33636 | The rationale for selecting evaluation, inspection, or demonstration shall be recorded in an appropriate document (e.g., system safety report, hazard analysis). (Requirement 33636) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.2.3 | 33638 | The software safety personnel shall concur with both the rationale for not performing a test and the selected evaluation, inspection, or demonstration methodology used to verify the requirement. (Requirement 33638) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.5 | 33649 | The software safety test analysis results shall be presented at project formal reviews and system-level safety reviews. (Requirement 33649) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5.5 | SWA-96 | NASA STD 8719.13B | 5.06.3(05) | 33491 | The following documentation shall address safety-critical software: Software Requirements Specification (Requirement 33491) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.07.1 | 33502 | A tracing system shall map the relationships between software safety requirements and system hazards, as well as trace the flow down of software safety requirements to design, implementation, and test. (Requirement 33502) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.07.1.1 | 33503 | The software tracing system shall include, or link to, the system-level hazard tracking system to allow tracking of software-related hazard controls and mitigations, and to verify closure of system hazards. (Requirement 33503) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.07.2 | 33504 | The tracing system shall be under configuration control. (Requirement 33504) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.07.3 | 33505 | The tracing system reports shall be reviewed by software safety personnel. These reports are, at a minimum, available for project formal reviews. (Requirement 33505) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.08.1.1 | 33508 | This system shall trace identified safety-critical software problems back to the system-level hazard involved. (Requirement 33508) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.a | 33578 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements meet the requirements of section 6.1.1 and sub-sections. (Requirement 33578) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.c | 33580 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements are traceable to system safety requirements, environmental requirements, standards, program specification, vehicle or facility requirements, interface requirements, and system hazard reports. (Requirement 33580) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.d | 33581 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements provide adequate response to potential failures. Areas to consider should include, but are not limited to, limit ranges, relationship logic for interdependent limits, out-of-sequence event protection, timing problems, sensor or actuator failures, voting logic, hazardous command processing requirements, Fault Detection, Isolation, and Recovery (FDIR), switchover logic for failure tolerance, and the ability to reach and maintain a safe state if so required. (Requirement 33581) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.e | 33582 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that the software safety requirements include positive measures to prevent potential problems and implement required "must work" functions. (Requirement 33582) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.f | 33601 | The analysis methodology shall include the following steps, at a minimum: Verify all safety-critical design elements are traceable to software safety requirements, and vice versa. (Requirement 33601) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.e | 33615 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify all safety-critical code units are traceable to safety-critical design elements. (Requirement 33615) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 7.2.1 | 33657 | Software safety change analysis shall evaluate whether the proposed change could invoke a hazardous state, affect a hazard control, increase the likelihood of a hazardous state, adversely affect safety-critical software, or change the safety-criticality of an existing software element. (Requirement 33657) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 7.1.1.02 | 33281 | All software requirements are defined, traceable from one life cycle phase to another, and analyzed in a manner that is measurable or otherwise verifiable. (Requirement 33281) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.5.6 | SWA-99 | NASA STD 8719.13B | 5.14.3.d | 33553 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All software safety requirements and elements have been successfully validated, or waivers/deviations have been approved. (Requirement 33553) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.14.3.e | 33554 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All software safety requirements and elements have been properly verified, or waivers/deviations have been approved. (Requirement 33554) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.15.1 | 33560 | If one or more requirements (i.e., a numbered shall statement) contained within this Standard cannot be met by any safety-critical software project, a waiver/deviation package shall be prepared by a software safety expert and approved according to NPR 8715.3. (Requirement 33560) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.15.2 | 33561 | The project shall submit a written request for a waiver/deviation, detailing the justification to support the waiver/deviation. (Requirement 33561) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.6 | SWA-108 | NASA STD 8719.13B | 5.11.1.2.2 | 33531 | The software safety manager shall ensure sufficient safety testing and analysis is performed to verify that any changes in the use of project tools does not influence known hazards or adversely affect the residual risk of the software. (Requirement 33531) | S | Y | Y | SWA |
| NASA STD 8719.13B | 5.12.1.3 | 33537 | Additional analysis, testing, or a combination thereof shall be performed to verify safety-critical OTS or reused software to the same level required of in-house developed software to the extent possible via black box testing. (Requirement 33537) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.14.1 | 33547 | There shall be an official certification process established, documented, and conducted prior to the release of any safety-critical software for its intended operational use. (Requirement 33547) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2 | 33576 | Software safety personnel shall analyze the software safety requirements, both technical and procedural. (Requirement 33576) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.1.2.1.c | 33580 | The analysis methodology shall be recorded in an appropriate document and include the following steps, at a minimum: Verify that all software safety requirements are traceable to system safety requirements, environmental requirements, standards, program specification, vehicle or facility requirements, interface requirements, and system hazard reports. (Requirement 33580) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.2.2.2.a | 33596 | The analysis methodology shall include the following steps, at a minimum: Verify that the software design meets the requirements of section 6.2.1 and sub-sections. (Requirement 33596) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2 | 33608 | Software safety personnel shall analyze the software implementation (e.g., code). (Requirement 33608) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.a | 33611 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that the safety-critical software code and data meets the requirements of section 6.3.1 and sub-sections. (Requirement 33611) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.b | 33612 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Verify that design safety features and methods are correctly implemented in the software code. (Requirement 33612) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.3.2.2.d | 33614 | The analysis methodology shall include the following steps, at a minimum, and can include source code reviews and inspections: Ensure that code and data verification activities adequately substantiate all software safety requirements, to the extent that a requirement can be verified at a component or unit level. (Requirement 33614) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.1.4 | 33634 | Additional hazardous states or contributors identified during testing shall undergo complete analysis prior to software delivery or use. (Requirement 33634) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3 | 33639 | The results from the software and system test process, or the requirements verification evaluation, inspection, or demonstration process, shall be analyzed. (Requirement 33639) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.a | 33642 | The analysis methodology shall include the following steps, at a minimum: Verify that the software and system tests data meet the requirements of section 6.4.1 and sub-sections. (Requirement 33642) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.b | 33643 | The analysis methodology shall include the following steps, at a minimum: Verify that the requirements verification evaluation, inspection, or demonstration data meet the requirements of section 6.4.2 and sub-sections (Requirement 33643) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.c | 33644 | The analysis methodology shall include the following steps, at a minimum: Verify via test coverage analysis that all safety requirements, functions, controls, and processes have been completely covered within the unit, component, system, and acceptance level tests. (Requirement 33644) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.d | 33645 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety requirements have been tested, or evaluated, inspected, or demonstrated. (Requirement 33645) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.e | 33646 | The analysis methodology shall include the following steps, at a minimum: Verify that all software safety functions are correctly performed and that the software system does not perform unintended functions. (Requirement 33646) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.3 | 33647 | The documented results of the analysis, including any newly identified hazards and improperly implemented safety features, shall be provided to the responsible system safety personnel. (Requirement 33647) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.5.1.3 | 33218 | Assure that all acceptance documentation is present, including signed certifications. (Requirement 33218) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.2 | 33255 | In addition, address how the provider will implement the requirements of Sections 6.0 and 7.0 of this Standard. (Requirement 33255) | S | Y | Y | SWA | |||
| SWA-109 | NASA STD 8719.13B | 5.14.3.a | 33550 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All software hazards have been identified. (Requirement 33550) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.14.3.b | 33551 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All hazard controls that require software implementation have been identified. (Requirement 33551) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.14.3.c | 33552 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All software safety requirements and elements have been identified and tracked. (Requirement 33552) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.14.3.d | 33553 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All software safety requirements and elements have been successfully validated, or waivers/deviations have been approved. (Requirement 33553) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.14.3.e | 33554 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All software safety requirements and elements have been properly verified, or waivers/deviations have been approved. (Requirement 33554) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.14.3.f | 33555 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All discrepancies in safety-critical software have been dispositioned with the safety organization's concurrence, per the certification process. (Requirement 33555) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 5.14.3.g | 33556 | The software safety organization shall participate in evaluation of the following areas as part of their certification process: All operational workarounds associated with discrepancies in safety-critical software have the concurrence of the Center or Program safety organization, per the certification process. (Requirement 33556) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.2.b | 33643 | The analysis methodology shall include the following steps, at a minimum: Verify that the requirements verification evaluation, inspection, or demonstration data meet the requirements of section 6.4.2 and sub-sections (Requirement 33643) | S | Y | Y | SWA | |||
| NASA STD 8719.13B | 6.4.3.4 | 33648 | Improperly implemented safety features shall be input into the problem reporting system for project-level resolution. (Requirement 33648) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.4.1.6 | 33212 | Assure that problem reports, discrepancies from reviews, and test anomalies are documented, addressed, analyzed, and tracked to resolution. (Requirement 33212) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 5.5.1.3 | 33218 | Assure that all acceptance documentation is present, including signed certifications. (Requirement 33218) | S | Y | Y | SWA | |||
| NASA-STD-8739.8 | 6.3.2.2 | 33255 | In addition, address how the provider will implement the requirements of Sections 6.0 and 7.0 of this Standard. (Requirement 33255) | S | Y | Y | SWA | |||
| SWA-110 | NASA STD 8719.13B | 5.14.5 | 33558 | The organization providing the safety engineering shall approve the results and reports prior to acceptance of the software and the system. The Center SMA organization reviews the results and provides final certification or approval for operation of safety-critical products and facilities. (Requirement 33558) | S | Y | Y | SWA | ||
| SWA-111 | NASA STD 8719.13B | 5.14.4 | 33557 | Personnel conducting software safety functions shall be prepared to represent the software to an appropriate safety panel for certification. (Requirement 33557) | S | Y | Y | SWA | ||
| SWA-112 | NASA STD 8719.13B | 4.1.1.5 | 33393 | The Center or responsible Program Safety and Mission Assurance (SMA) organization shall approve the evaluation conclusions. (Requirement 33393) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 5.14.5 | 33558 | The organization providing the safety engineering shall approve the results and reports prior to acceptance of the software and the system. The Center SMA organization reviews the results and provides final certification or approval for operation of safety-critical products and facilities. (Requirement 33558) | S | Y | Y | SWA | |||
| CxP 70059 | 7.5.7.7 | SWA-113 | NASA STD 8719.13B | 7.2.1.1 | 33658 | The analysis activity shall include an assessment of the amount of regression testing needed to verify that the implementation of new software requirements has not affected the implementation of existing safety-critical software. (Requirement 33658) | S | Y | Y | SWA |
| SWA-115 | NASA STD 8719.13B | 5.06.3(11) | 33497 | The following documentation shall address safety-critical software: Operations and Maintenance Plan (Requirement 33497) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 7.3 | 33660 | Operational documentation, including user manuals and procedures, shall describe all safety related commands, data, input sequences, options, and other items necessary for the safe operation of the system. (Requirement 33660) | S | Y | Y | SWA | |||
| SWA-116 | NASA STD 8719.13B | 7.3.1 | 33661 | All error message descriptions and corrective actions shall be included in operational documentation. (Requirement 33661) | S | Y | Y | SWA | ||
| SWA-117 | NASA STD 8719.13B | 5.06.3(10) | 33496 | The following documentation shall address safety-critical software: User documentation and procedures (Requirement 33496) | S | Y | Y | SWA | ||
| NASA STD 8719.13B | 7.3.2 | 33662 | Software safety personnel shall review any updates to user manuals and procedures for safety impacts, and to ensure that any software-related hazard closures that depend on operational workarounds are properly documented. (Requirement 33662) | S | Y | Y | SWA | |||
| CxP 70059 | A | QAS-51 | NPD 8730.5 | 1.b.05 | 42134 | Policy: NASA quality assurance programs shall: Flow applicable quality assurance requirements down to successive levels of the supply chain to ensure control of subtier suppliers and verificaiton of safety/mission critical attributes at all levels of the supply chain. (Requirement 42134) | S | Y | Y | Quality |
| CxP 70059 | A.1.1.1 | QAS-52 | NPD 8730.5 | 1.b.05 | 42134 | Policy: NASA quality assurance programs shall: Flow applicable quality assurance requirements down to successive levels of the supply chain to ensure control of subtier suppliers and verificaiton of safety/mission critical attributes at all levels of the supply chain. (Requirement 42134) | S | Y | Y | Quality |
| NPD 8730.5 | 5.d.2 | 42198 | Responsibility: Program/project managers shall: Ensure program planning and acquisition documents incorporate applicable requirements of this NPD, including specification of applicable quality system requirements identified in Attachment A of this NPD. (Requirement 42198) | S | Y | Y | Quality | |||
| NPD 8730.5 | 5.e.1 | 42202 | Responsibility: Procurement officials shall: Incorporate quality assurance requirements identified in Attachment A of this NPD into procurement contracts utilizing input provided by the program/project and Center SMA office. (Requirement 42202) | S | Y | Y | Quality | |||
| QAS-53 | NPD 8730.5 | 1.b.05 | 42134 | Policy: NASA quality assurance programs shall: Flow applicable quality assurance requirements down to successive levels of the supply chain to ensure control of subtier suppliers and verificaiton of safety/mission critical attributes at all levels of the supply chain. (Requirement 42134) | S | Y | Y | Quality | ||
| NPD 8730.5 | 5.d.2 | 42198 | Responsibility: Program/project managers shall: Ensure program planning and acquisition documents incorporate applicable requirements of this NPD, including specification of applicable quality system requirements identified in Attachment A of this NPD. (Requirement 42198) | S | Y | Y | Quality | |||
| NPD 8730.5 | 5.e.1 | 42202 | Responsibility: Procurement officials shall: Incorporate quality assurance requirements identified in Attachment A of this NPD into procurement contracts utilizing input provided by the program/project and Center SMA office. (Requirement 42202) | S | Y | Y | Quality | |||
| NPD 8730.5 | 5.e.2 | 42203 | Responsibility: Procurement officials shall: Ensure that prospective contractors meet contract qualification requirements (quality system, product, process, personnel). (Requirement 42203) | S | Y | Y | Quality | |||
| CxP 70059 | A.1.1.3 | QAS-58 | NPD 8730.5 | 5.e.2 | 42203 | Responsibility: Procurement officials shall: Ensure that prospective contractors meet contract qualification requirements (quality system, product, process, personnel). (Requirement 42203) | S | Y | Y | Quality |
| CxP 70059 | A.1.4.2.4 | QAS-61 | NPD 8730.5 | 1.b.12 | 42145 | Policy: NASA quality assurance programs shall: Be supported by records demonstrating compliance with technical/quality requirements. Records shall be legible, traceable to the applicable product, identifiable to the applicable requirement, and readily retrievable for requirement verification. (Requirement 42145) | S | Y | Y | Quality |
| NPD 8730.5 | 1.b.13 | 42146 | Policy: NASA quality assurance programs shall: Include the collection and analysis of quality data for the purpose of identifying and initiating resolution of problem areas (e.g., projects, products, processes, operations, organizations), common deficiency causes, nonconformance trends, defect anomalies, and process variations. (Requirement 42146) | S | Y | Y | Quality | |||
| NPR 8715.3C | 02.8.1.b | 45971 | System Safety: Documentation: The project manager (or designated agent) and the System Safety Manager shall: Ensure that records are maintained per NPR 1411.1, NASA Records Retention Schedules. (Requirement 45971) | S | Y | Y | PP&C | |||
| QAS-62 | NPD 8730.5 | 1.b.12 | 42145 | Policy: NASA quality assurance programs shall: Be supported by records demonstrating compliance with technical/quality requirements. Records shall be legible, traceable to the applicable product, identifiable to the applicable requirement, and readily retrievable for requirement verification. (Requirement 42145) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.13 | 42146 | Policy: NASA quality assurance programs shall: Include the collection and analysis of quality data for the purpose of identifying and initiating resolution of problem areas (e.g., projects, products, processes, operations, organizations), common deficiency causes, nonconformance trends, defect anomalies, and process variations. (Requirement 42146) | S | Y | Y | Quality | |||
| CxP 70059 | A.1.7.4.1 | QAS-100 | NPR 8735.2A | 1.2.05.c(1) | 43049 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Incorporate appropriate clauses or provisions into the prime contract that allow NASA, delegated Federal agency personnel, and/or quality assurance support contractors timely access to contractor and subcontractor facilities to perform quality assurance functions required by this NPR. (Requirement 43049) | S | Y | Y | Quality |
| QAS-101 | NPD 8730.5 | 5.e.2 | 42203 | Responsibility: Procurement officials shall: Ensure that prospective contractors meet contract qualification requirements (quality system, product, process, personnel). (Requirement 42203) | S | Y | Y | Quality | ||
| NPR 8735.2A | 1.2.05.c(1) | 43049 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Incorporate appropriate clauses or provisions into the prime contract that allow NASA, delegated Federal agency personnel, and/or quality assurance support contractors timely access to contractor and subcontractor facilities to perform quality assurance functions required by this NPR. (Requirement 43049) | S | Y | Y | Quality | |||
| CxP 70059 | A.1.7.4.2.b | QAS-170 | NPD 8730.5 | 5.d.3 | 42199 | Responsibility: Program/project managers shall: Identify safety/mission critical attributes and associated Government mandatory inspection points. (Requirement 42199) | S | Y | Y | Quality |
| NPR 8735.2A | 1.2.05.c(1) | 43049 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Incorporate appropriate clauses or provisions into the prime contract that allow NASA, delegated Federal agency personnel, and/or quality assurance support contractors timely access to contractor and subcontractor facilities to perform quality assurance functions required by this NPR. (Requirement 43049) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.b | 43061 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Support the program/project manager and contracting officer in the development of the PQASP, LODs, and/or quality assurance support contracts. (Requirement 43061) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.c | 43062 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Provide detailed information concerning the resource(s) required to perform required quality assurance activities, including preparation of the NASA Center estimate of required delegated agency or surveillance support contract support (Requirement 43062) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.d | 43063 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure clear and mutual understanding of delegated/assigned quality assurance functions between NASA, the delegated agency, and quality assurance support contractors. (Requirement 43063) | S | Y | Y | Quality | |||
| NPR 8735.2A | 1.2.07.e | 43064 | Introduction: Roles and Responsibilities: The NASA SMA Lead appointed by the program/project manager or the Center SMA Director shall: Ensure that delegated/assigned quality assurance functions are properly and effectively performed over the life of the program/project in accordance with the LOD or support contract. (Requirement 43064) | S | Y | Y | Quality | |||
| CxP 70059 | A.1.7.4.3.a | QAS-171 | NPD 8730.5 | 1.b.02.a | 42130 | Policy: NASA quality assurance programs shall: For circumstances where noncompliance cannot result in loss of life or loss of mission, statistically-based sampling plans or 100 percent inspection shall be employed based on determination of risk. (Requirement 9005) | S | Y | Y | Quality |
| CxP 70059 | A.1.7.5.1 | QAS-173 | NPD 8730.5 | 1.b.11 | 42144 | Policy: NASA quality assurance programs shall: Be performed by persons that are not assigned direct responsibility for ensuring that cost or schedule objectives are met. (Requirement 42144) | S | Y | Y | Quality |
| QAS-179 | NPD 8730.5 | 1.b.11 | 42144 | Policy: NASA quality assurance programs shall: Be performed by persons that are not assigned direct responsibility for ensuring that cost or schedule objectives are met. (Requirement 42144) | S | Y | Y | Quality | ||
| CxP 70059 | A.1.7.6 | QAS-120 | NPD 8730.1B | 1.a | 11010 | It is NASA policy to accomplish the following: Require that suppliers of calibration laboratory services to NASA be compliant with the calibration laboratory competency requirements identified in ANSI/NCSL Z540.1-1994 (R2002). (Requirement 11010) | S | Y | Y | Quality |
| NPD 8730.1B | 1.b | 11021 | It is NASA policy to accomplish the following: Require that suppliers of calibration laboratory services be accredited to ANSI/ISO/IEC 17025:2000, where it is appropriate and beneficial to NASA to require independent accreditation, and be compliant with the calibration laboratory competency requirements identified in ANSI/NCSL Z540.1-1994 (R2002). (Requirement 11021) | S | Y | Y | Quality | |||
| NPD 8730.1B | 1.c(1-5) | 11011 | It is NASA policy to accomplish the following: Maintain calibration on all test and measuring equipment and safety instruments used to perform measurements associated with the following functions: (1) Acceptance testing (determining that a part, component, or system meets specifications). (2) Inspection, maintenance, or calibration. (3) Flight hardware qualification. (4) Measurement of processes where test equipment accuracy is essential for the safety of personnel or the public. (5) Telecommunication, transmission, and test equipment where exact signal interfaces and circuit confirmations are essential to mission success. (Requirement 11022) | S | Y | Y | Quality | |||
| NPD 8730.1B | 1.c(6) | 30895 | It is NASA policy to accomplish the following: Maintain calibration on all test and measuring equipment and safety instruments used to perform measurements associated with the following functions: (6) Development, testing, and special applications where the specifications, end products, or data are accuracy sensitive, including instruments used in hazardous and critical applications. (Requirement 30895) | S | Y | Y | Quality | |||
| NPD 8730.1B | 1.d | 11022 | It is NASA policy to accomplish the following: Limit use of noncalibrated instruments to only applications where substantiated accuracy is not required, or for "indication only" purposes in nonhazardous, noncritical applications. (Requirement 11022) | S | Y | Y | Quality | |||
| CxP 70059 | A.1.7.6.i | QAS-221 | NPD 8730.5 | 1.b.12 | 42145 | Policy: NASA quality assurance programs shall: Be supported by records demonstrating compliance with technical/quality requirements. Records shall be legible, traceable to the applicable product, identifiable to the applicable requirement, and readily retrievable for requirement verification. (Requirement 42145) | S | Y | Y | Quality |
| NPD 8730.5 | 1.b.13 | 42146 | Policy: NASA quality assurance programs shall: Include the collection and analysis of quality data for the purpose of identifying and initiating resolution of problem areas (e.g., projects, products, processes, operations, organizations), common deficiency causes, nonconformance trends, defect anomalies, and process variations. (Requirement 42146) | S | Y | Y | Quality | |||
| QAS-222 | NPD 8730.5 | 1.b.12 | 42145 | Policy: NASA quality assurance programs shall: Be supported by records demonstrating compliance with technical/quality requirements. Records shall be legible, traceable to the applicable product, identifiable to the applicable requirement, and readily retrievable for requirement verification. (Requirement 42145) | S | Y | Y | Quality | ||
| NPD 8730.5 | 1.b.13 | 42146 | Policy: NASA quality assurance programs shall: Include the collection and analysis of quality data for the purpose of identifying and initiating resolution of problem areas (e.g., projects, products, processes, operations, organizations), common deficiency causes, nonconformance trends, defect anomalies, and process variations. (Requirement 42146) | S | Y | Y | Quality | |||
| CxP 70059 | A.1.8.2.2 | QAS-122 | NPR 8735.2A | 1.2.05.c(1) | 43049 | Introduction: Roles and Responsibilities: Contracting officers ensure performance of all necessary actions for effective contracting and safeguard the interests of the United States in its contractual relationships. To implement requirements of this NPR, contracting officers shall: Incorporate appropriate clauses or provisions into the prime contract that allow NASA, delegated Federal agency personnel, and/or quality assurance support contractors timely access to contractor and subcontractor facilities to perform quality assurance functions required by this NPR. (Requirement 43049) | S | Y | Y | Quality |
| CxP 70059 | A.1.8.2.4.1 | QAS-124 | NPD 8730.5 | 5.d.4 | 42200 | Responsibility: Program/project managers shall: Initiate corrective actions upon discovery or notification of noncompliance. (Requirement 42200) | S | Y | Y | Quality |
| CxP 70059 | A.1.8.3 | QAS-229 | NPD 8730.5 | 1.b.06 | 42135 | Policy: NASA quality assurance programs shall: Continually be improved through: advocacy; awareness training; teaming and sharing of quality assurance tools, techniques and data; integration of quality assurance processes to prevent duplication of effort; and dissemination/implementation of lessons learned and best practices. (Requirement 42135) | S | Y | Y | Quality |
| CxP 70059 | A.1.8.3.3.a | QAS-238 | NPD 8730.5 | 1.b.07 | 42136 | Policy: NASA quality assurance programs shall: Ensure that customers and Government authorities are quickly notified concerning noncompliant products or failure experiences potentially affecting product safety, reliability, or functionality. Customers and Government authorities include: contracting officers, Government contract management agents, authorities responsible for assigning, managing, or overseeing work, and, where noncompliant conditions might constitute evidence of possible fraud, malpractice, or other serious misconduct, the NASA Office of Inspector General. (Requirement 42136) | S | Y | Y | Quality |
| CxP 70059 | A.1.8.3.3.d | QAS-241 | NPD 8730.5 | 1.b.07 | 42136 | Policy: NASA quality assurance programs shall: Ensure that customers and Government authorities are quickly notified concerning noncompliant products or failure experiences potentially affecting product safety, reliability, or functionality. Customers and Government authorities include: contracting officers, Government contract management agents, authorities responsible for assigning, managing, or overseeing work, and, where noncompliant conditions might constitute evidence of possible fraud, malpractice, or other serious misconduct, the NASA Office of Inspector General. (Requirement 42136) | S | Y | Y | Quality |
| CxP 70059 | A.1.8.3.5 | QAS-267 | NPD 8730.5 | 1.b.07 | 42136 | Policy: NASA quality assurance programs shall: Ensure that customers and Government authorities are quickly notified concerning noncompliant products or failure experiences potentially affecting product safety, reliability, or functionality. Customers and Government authorities include: contracting officers, Government contract management agents, authorities responsible for assigning, managing, or overseeing work, and, where noncompliant conditions might constitute evidence of possible fraud, malpractice, or other serious misconduct, the NASA Office of Inspector General. (Requirement 42136) | S | Y | Y | Quality |
| CxP 70059 | A.1.8.3.5.d | QAS-283 | NPD 8730.5 | 1.b.07 | 42136 | Policy: NASA quality assurance programs shall: Ensure that customers and Government authorities are quickly notified concerning noncompliant products or failure experiences potentially affecting product safety, reliability, or functionality. Customers and Government authorities include: contracting officers, Government contract management agents, authorities responsible for assigning, managing, or overseeing work, and, where noncompliant conditions might constitute evidence of possible fraud, malpractice, or other serious misconduct, the NASA Office of Inspector General. (Requirement 42136) | S | Y | Y | Quality |
| Opinion/Impl'n Key: Y = Yes, N = No, U = Unassigned, F = Future, C = Conditional, O = Other, D = Program Disagrees, I = Institutional, X = Not SMA Requirement, R = Resolve, P = Partial Implementation, V = Variance Approved | ||||||||||
| Tech Auth Key: S = SMA, E = Engineering, A = Adminstrator, H = Heath, I = Informaton, P = Planet Protection, F = Facility Admin, U = Unassigned | ||||||||||