AGREEMENT FOR {PAYLOAD NAME} Appendix D of the SLS Secondary Payload User’s is to implement a co-signed Payload Integration Agreement (PIA) between the Secondary Payload Customer and the FP30/Exploration and Space Transportation Development Office as the binding agreement for meeting and implementing the latest technical integration requirements and management processes required to fly a secondary payload on the Space Launch System (SLS) vehicle. This PIA is applicable to all secondary payloads that will be integrated into the SLS stack. The PIA defines the management agreements by both parties and results in: (1) a co-signed PIA that will address management agreements; (2) the PIA becomes a separate standalone document; and (3) the PIA provides direction to applicable documentation so that the Secondary Payload Customer shall be in compliance with the latest requirements. The sections are preliminary and require further definition but aim to initially introduce and address potential sections of the PIA. PURPOSE The Payload Integration Agreement (PIA) documents the agreements to manage and execute the roles and responsibilities of the technical integration requirements, processes, services, and resources between the Secondary Payload Customer and the FP30/Exploration and Space Transportation Development Office for transportation services via the SLS vehicle. The effectivity of this co-signed PIA commences upon the last required signature of this document and continues through payload deployment from the SLS vehicle. REQUIREMENTS It is the responsibility of the Secondary Payload Customer or the FP30/Exploration and Space Transportation Development Office to verify compatibility of secondary payload/deployer physical and functional interfaces with the applicable SLS interface agreements and documents. FP30, on behalf of the SLS Program, however, intends to provide maximum flexibility in determining the manner or method to be used to accomplish this verification. All secondary payload/deployer physical and functional compliance shall be accomplished prior to installation for flight. DESCRIPTION The Secondary Payload Customer provides a top-level description that describes the basic function(s) and research objectives of the secondary payload. UNIQUE AGREEMENTS, CONSTRAINTS, OR SERVICES The Secondary Payload Customer or FP30, on behalf of the SLS Program, provides any unique deviations required from the management responsibilities or technical agreements.
AGREEMENT FOR {PAYLOAD NAME} Appendix D of the SLS Secondary Payload User’s is to implement a co-signed Payload Integration Agreement (PIA) between the Secondary Payload Customer and the FP30/Exploration and Space Transportation Development Office as the binding agreement for meeting and implementing the latest technical integration requirements and management processes required to fly a secondary payload on the Space Launch System (SLS) vehicle. This PIA is applicable to all secondary payloads that will be integrated into the SLS stack. The PIA defines the management agreements by both parties and results in: (1) a co-signed PIA that will address management agreements; (2) the PIA becomes a separate standalone document; and (3) the PIA provides direction to applicable documentation so that the Secondary Payload Customer shall be in compliance with the latest requirements. The sections are preliminary and require further definition but aim to initially introduce and address potential sections of the PIA. PURPOSE The Payload Integration Agreement (PIA) documents the agreements to manage and execute the roles and responsibilities of the technical integration requirements, processes, services, and resources between the Secondary Payload Customer and the FP30/Exploration and Space Transportation Development Office for transportation services via the SLS vehicle. The effectivity of this co-signed PIA commences upon the last required signature of this document and continues through payload deployment from the SLS vehicle. REQUIREMENTS It is the responsibility of the Secondary Payload Customer or the FP30/Exploration and Space Transportation Development Office to verify compatibility of secondary payload/deployer physical and functional interfaces with the applicable SLS interface agreements and documents. FP30, on behalf of the SLS Program, however, intends to provide maximum flexibility in determining the manner or method to be used to accomplish this verification. All secondary payload/deployer physical and functional compliance shall be accomplished prior to installation for flight. DESCRIPTION The Secondary Payload Customer provides a top-level description that describes the basic function(s) and research objectives of the secondary payload. UNIQUE AGREEMENTS, CONSTRAINTS, OR SERVICES The Secondary Payload Customer or FP30, on behalf of the SLS Program, provides any unique deviations required from the management responsibilities or technical agreements.
sls-secondary_payload_users_guide.docx