| NODIS Library | Program Management(8000s) | Search |

NASA
Procedural
Requirements

NPR 8715.7B
Effective Date: April 27, 2020
Expiration Date: April 27, 2025

COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES

Printable Format (PDF)

Subject: Payload Safety Program

Responsible Office: Office of Safety and Mission Assurance

Chapter 3. Payload Safety Process

3.1 The Payload Safety Review and Approval Process

3.1.1 The Payload Safety Review and Approval Process described in this chapter consists of five key steps or milestones, and has been developed as an aspect of the NASA Payload Safety Program. The Payload Safety Review and Approval Process is designed to work alongside the project milestones, and Key Decision Points for projects, reference NPR 7120.5, NASA Space Flight Program and Project Management. With all NASA payloads across the entire Agency working off the same process (tailored to their circumstances), the NASA Payload Safety Manager and Agency Team are able to ensure consistent implementation and applicability of requirements that ensure payload safety.

3.2 Establishing the Payload Safety Working Group

3.2.1 Each NASA payload mission is unique, involving different combinations of organizations, both internal and external to NASA, including payload organizations, payload contractors, launch service providers, payload processing sites, launch sites, and regulators. A key aspect of the payload safety review process is the establishment by the payload project of a Payload Safety Working Group (PSWG) specific to the project. The PSWG is not an Agency-level working group. It is a project level working group that acts as an advisory group which is established by, directed by, and reports to the Payload Project Manager. The role of the PSWG is to coordinate across the multiple stakeholder organizations, advise the Payload Project Manager, and advise their respective organizations on strategies for early hazard abatement, mitigation, or resolution. The PSWG includes system safety engineers from the various organizations that support the project. The PSWG helps the payload project ensure that it complies with applicable safety requirements, and that the safety risks are identified, understood, and adequately controlled. The PSWG is not an independent Technical Authority. The group is typically assembled prior to launch vehicle selection and is in place up to commencement of Safety Review III.

3.2.2 The Payload Project Manager shall:

a. Establish a PSWG with concurrence from the appropriate SMA Technical Authority(s) (SMA TA) and identify one of the members as the PSWG Chairperson. For projects using Launch Service Program (LSP), the NASA LSP Safety and Mission Assurance Launch Services Division System Safety Engineer typically serves as the PSWG Chairperson.

b. Ensure the PSWG has the following technical representations:

(1) PSWG Chairperson.

(2) Payload Project System Safety Engineer.

(3) Launch site range safety organization representative.

(4) Launch service provider safety representative.

Note: The PSWG may start without the launch service provider safety representative, if a launch vehicle for the payload is not known or selected.

(5) Other subject matter experts.

(6) Payload processing and Integration facilities safety representative.

Note: The PSWG may start without the payload processing facility safety representative, if the launch site area payload processing facility for the payload is not initially known.

(7) Payload or sample-recovery organization safety representative.

Note: If there is a planned return-to-Earth payload or sample recovery, the recovery operations are often handled by a separate organization much later after payload processing and launch. It may or may not be beneficial for the recovery organization to have a safety representative on the PSWG, depending on the level of impact the recovery hardware and operations have on payload design and processing prior to launch.

3.2.3 The PSWG technical representation may also include:

a. Payload contractor safety representatives including cooperative partnership contractor safety representatives.

b. Other payload safety representatives for primary, secondary, and auxiliary payloads.

Note: The inclusion of primary, secondary, and auxiliary payload safety representatives is to facilitate identification of integrated hazards and potential processing conflicts.

3.2.4 The PSWG for primary payloads may be used to conduct the safety review process for auxiliary payloads. If the auxiliary payload project conducts their own PSWG, the auxiliary PSWG shall include representation from the primary payload PSWG.

3.3 Payload Safety Process and Standard Determination

3.3.1 The following requirements specify what processes and standards are used to ensure payload safety.

3.3.2 The Payload Project Manager shall follow the payload safety review process outlined in this NPR and implement NASA-STD-8719.24, NASA Expendable Launch Vehicle Payload Safety Requirements or an alternate process and standard accepted by the appropriate SMA TA(s) in consultation with the NASA Payload Safety Manager.

3.3.3 The Payload Project Manager, in consultation with the PSWG and with concurrence from the appropriate SMA TA(s), may tailor the safety review and approval process described in this NPR and in NASA-STD 8719.24.

3.3.4 If the PSWG determines, based on analysis, that a payload does not present hazards to people or assets during testing, processing, integration, launch, or planned recovery, the Payload Project Manager, with concurrence from the appropriate SMA TA(s), may designate the payload as non-hazardous. The Payload Project Manager shall document such a decision. The remainder of the requirements in this NPR do not apply for non-hazardous payloads.

3.3.5 The Payload Safety Engineer shall identify and document controls for hazardous payload in the Safety Data Package.

3.3.6 For auxiliary payloads not included in the primary payload PSWG, the Project Manager shall determine, with concurrence from the appropriate SMA TA(s), a tailored version of the process in section 3.4, and applicable tailored standards such that:

a. Processes and standards are sufficient for the type of operations and associated hazards.

b. The process includes the development of a system safety plan and a hazard analysis addressing the payload design, GSE design, and ground operations.

Note: Document hazards and controls on Payload Safety Hazard Report Forms (NF 1825, NASA Payload Safety Hazard Report or equivalent form).

c. Safety data products are independently reviewed by the PSWG.

3.3.7 For payloads flying on a foreign launch vehicle, the Payload Project Manager shall:

a. Tailor the safety review and approval process in section 3.4 to work in conjunction with the foreign launch vehicle provider's payload safety review and approval process.

b. Develop and follow a project-specific set of payload safety requirements from a tailored version of NASA-STD-8719.24, ANNEX to NASA-STD-8719.24 NASA Expendable Launch Vehicle Payload Safety Requirements: Requirements Table, that comply with the foreign launch vehicle provider's payload safety requirements.

c. Comply with foreign launch vehicle and launch site safety requirements.

3.4 Payload Safety Reviews, Implementation, and Processes

3.4.1 Safety Reviews (SR)

3.4.1.1 The Payload Project Manager shall coordinate with the PSWG to schedule the Payload Safety Introductory Briefing, and three Safety Reviews (SR I, II, and III) and provide the required deliverables according to Table 3 1.

3.4.1.2 The technical details of the submission are based on the system level technical design and payload processing information available at the time of the project's review.

3.4.1.3 A Payload Safety Introductory Briefing is typically the first meeting of the PSWG providing mission concept information and preliminary safety approaches to the payload safety community.

3.4.1.4 The purpose of SR I and II is to review the safety technical data submissions by the PSWG for approval in support of Preliminary Design Review (PDR) and Critical Design Review (CDR), respectively.

3.4.1.5 SR III is the final formal PSWG review ensuring all safety comments and issues from Safety Review II have been addressed and that the PSWG is ready to proceed with the Pre-ship Review, payload shipping, and launch site area payload processing.

Table 3 1. Overview of Deliverables for the Payload Safety Process and Approvals

Deliverable or Related Activity	Payload Safety Introductory Briefing	SR I	SR II	SR III*	NASA-STD-8719.24 Annex Reference
Dates Deliverables Due to PSWG	Early as possible, NLT midpoint of the Preliminary Design Phase (Phase B per NPR 7120.5)	NLT 30 days prior to PDR	NLT 30 days prior to CDR	NLT 90 days prior to payload shipment to the processing site
Payload Safety Introductory Briefing	Final				Vol 1, Attachment 5
Systems Safety Plan	Draft	Final			Vol 1 Attachment 2 and Vol 3, Chapter 4
Tailored payload safety requirements		Draft	Final
Safety Data Package I		Draft			Vol 3, Chapter 4 and Attachment 1
Safety Data Package II			Update		Vol 3, Chapter 4 and Attachment 1
Safety Data Package III				Final	Vol 3, Chapter 4 and Attachment 1
Ground Operations Plan			Draft	Final	Vol 6, Attachment 1
Safety Verification and Tracking Log (SVTL)				Completed, updated as needed for future issue tracking
Action / Approvals required		PSWG Approves System Safety Plan Resolves any comments for Safety Data Package 1	PSWG Approves Tailored Requirements PSWG Approves Safety Data Package II	PSWG Approves Safety Data Package III
PSWG Response to Payload Project Manager:		Assessment of the project's safety efforts and identification of any safety concerns	Assessment of the content submitted and identification of any safety concerns	Assessment, with all comments resolved	-
Dates response from PSWG to Payload Project Manager		NLT 60 days after PDR (in support of Key Decision Point C)	NLT 60 days after CDR (in support of Key Decision Point D)	NLT 30 days prior to payload shipment to processing site.	-

*Note: The PSWG verifies that all safety requirements have been or will be satisfied at the appropriate time and any associated waivers have been approved.

3.4.2 Certificate of Payload Safety Compliance

3.4.2.1 Upon completion of the safety review process, the Payload Project Manager shall submit a signed copy of NF 1851, Certificate of Payload Safety Compliance, with any attachments, to the NASA Payload Safety Manager.

3.4.2.2 The NASA Payload Safety Manager shall sign, and provide the completed NF 1851 with any attachments to the Payload Project Manager via a letter indicating the successful completion of the project's PSWG safety review and approval process.

Note: The NASA Payload Safety Manager uses the completion of the payload safety review and approval process and NF 1851 as input to the project's Safety and Missions Success Review.

3.4.3 Maintaining the Safety Verification Tracking Log (SVTL) after SRIII.

3.4.3.1 The Payload Project Manager shall:

a. After SRIII, update the SVTL at least weekly (or more frequently based on operational necessity, when open items will constrain the applicable operation(s)).

b. Make the current SVTL available to all safety authorities and other officials impacted by the safety activities and items on the SVTL.

3.4.4 Payload and Sample Recovery

3.4.4.1 The Payload Project Manager shall:

a. For missions involving payload and sample recovery operations, plan and implement a process to address hazards and safety requirements associated with payload and sample recovery operations.

b. Obtain concurrence from the appropriate SMA TA prior to the implementation of the payload and sample recovery plan.

3.5 Waiver Process

3.5.1 The Payload Project Manager shall:

a. Request a waiver when the PSWG determines that noncompliance with or changes to a requirement result in an increased safety risk.

b. Follow the request for relief process in accordance with NPR 8715.1, NASA Safety Health Programs to request relief from other Agency SMA requirements specified in other Agency directives and standards.

c. Obtain concurrence from the PSWG prior to submitting a waiver request to relevant authorities. Concurrence indicates a determination that:

(1) The waiver request and accompanying data are correct and complete.

(2) Safety risks and related schedule and performance considerations are properly characterized, and the increase in risk is identified.

(3) Effects the waiver might have on other projects, resources, or requirements are properly characterized.

3.5.2 The Payload Project Manager shall obtain concurrences and approvals from all NASA and non-NASA relevant authorities (see NF 1827, NASA Payload Safety Waiver Request, or equivalent). Relevant authorities may include but are not limited to:

a. Engineering, Safety and Mission Assurance, and Health and Medical Technical Authorities.

b. The NASA Center Director responsible for the payload project and any additional NASA Center Director responsible for people or property subject to additional risk due to the noncompliance.

c. The Payload Project Manager responsible for the Payload Project requesting the waiver.

d. Non-NASA officials responsible for ranges or facilities utilized by the project.

Note: The required NASA signatures are in addition to any local approvals required when utilizing a non-NASA range or facility, such as approval by the Air Force Range Commander for payload missions utilizing an Air Force range. Such local approvals may be documented on the same waiver document as the NASA signatures, or on a separate equivalent document depending on local agreements and procedures.

3.5.3 In the event that a relevant authority does not concur with or consent to tailoring of a requirement or a waiver, and the issue cannot be resolved through coordination with the PSWG, the Agency Team, or the SMA TA or other Authorities, the Payload Project Manager may raise disagreement using the Dissenting Opinion process in NPD 1000.0, NASA Governance and Strategic Management Handbook.