SSP_50911-Baseline.docx

PMM BILATERAL HARDWARE AND SOFTWARE EXCHANGE AGREEMENTS, LISTS, AND SCHEDULES

International Space Station Program

Baseline

April 2010

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract No.: NNJ09GA18B

SSP 50911

Baseline (Draft – January 2010)

SSP 50911

Baseline

1-1

SSP 50911

Baseline

PREFACE

NASA/ PMM BILATERAL HARDWARE AND SOFTWARE

EXCHANGE AGREEMENTS, LISTS, AND SCHEDULES

This Bilateral Hardware and Software Exchange Agreement defines the hardware and software that will be exchanged between the National Aeronautics and Space Administration (NASA) and the Agenzia Spaziale Italiana (ASI) for the modification of an Multipurpose Logistics Module (MPLM) Flight Unit into the Permanent Multipurpose Module (PMM) that will become a permanent element of the International Space Station (ISS). The MPLM was developed by ASI and delivered to NASA.

The PMM will provide:

· logistics re-supply and transportation of user passive cargo and payloads for use by the ISS, as per the Flight Utilization Logistics Flight (ULF)-5 upload manifest;

· additional pressurized volume for passive stowage of cargo when permanently docked to the ISS;

· potential capabilities for further future exploitation.

In addition, this agreement defines the technical support that will be provided for the hardware and software.

This bilateral exchange agreement implements the SSP 50908, NASA/ASI PMM Project Joint Implementation Plan. In addition, this agreement complies with NASA’s Space Station Program Implementation Guidelines for Technology Transfer, Annex A.

Both NASA and ASI herein mutually agree that the execution of this hardware and software exchange agreement is necessary for the effective and safe integration of the PMM into the International Space Station.

This document is developed and maintained by the NASA PMM Project Office. This document is under the control of the Space Station Control Board (SSCB).

The initial baseline release of this document is under the control of the SSCB. The SSCB delegates control and approval authority for future updates and/or revisions to the Multilateral Vehicle Control Board (MVCB).

INTERNATIONAL SPACE STATION PROGRAM

NASA/ PMM BILATERAL HARDWARE AND SOFTWARE

EXCHANGE AGREEMENTS, LISTS, AND SCHEDULES

CONCURRENCE

April 2010

INTERNATIONAL SPACE STATION PROGRAM

NASA/ PMM BILATERAL HARDWARE AND SOFTWARE

EXCHANGE AGREEMENTS, LISTS, AND SCHEDULES

CONCURRENCE

April 2010

INTERNATIONAL SPACE STATION PROGRAM

NASA/ PMM BILATERAL HARDWARE AND SOFTWARE

EXCHANGE AGREEMENTS, LISTS, AND SCHEDULES

LIST OF CHANGES

April 2010 All changes to paragraphs, tables, and figures in this document are shown below:

Board Name

Entry Date

Change

Paragraph(s)

August 2010

Baseline

All v

TABLE OF CONTENTS

APPENDIX

TABLE

introduction purpose The purpose of the Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules (BHSEALS) between the National Aeronautics and Space Administration (NASA) and the Agenzia Spaziale Italiana (ASI) is to facilitate the exchange of hardware and software for the Permanent Multipurpose Module (PMM) of the International Space Station (ISS) Program.

scope This document represents the single authoritative hardware and software exchange agreement between the NASA ISS Program Manager and the ASI Multipurpose Logistics Module (MPLM)/PMM Program Manager. It includes development hardware and software to be used in simulations and verification testing, including Simulation Models used for Flight Software validation. It includes flight hardware and software deployed as part of the operational Space Station and support equipment used in test, launch, operations and/or training. This document outlines the exchange procedures and the roles and responsibilities of the respective organizations. This document includes the lists and descriptions of the hardware and software that will be exchanged as well as the known dates for the exchanges.

objectives The objectives of this agreement are to:

· define the mutual commitments and obligations of both ASI and NASA for the exchange of hardware and software;

· identify all hardware and software to be exchanged between ASI and NASA in development of the PMM, as a modification of one flight unit of MPLM;

· identify the organization providing and receiving the hardware and software;

· define the responsibilities of the providing and receiving organization;

· define the requirements and responsibilities for use and support of hardware and software;

· define the requirements and responsibilities for shipping, notifications, technical support, acceptance data packages and configuration management;

· define the schedule for hardware and software exchanges between ASI and NASA;

· define the process for maintaining and tracking the transfers.

other considerations The providing organization keeps all property rights and copyrights in relation to the exchanged items. Nothing in this agreement can be interpreted as a basis for re-assignment of the property rights and copyrights for these items or for issuing licenses related to these items.

The exchange items may be used only by the receiving organization of the International Space Station International Partners/Participants and their contractors. These exchanges will be used only for performing work within the framework of the ISS Program. No third party transfers of hardware or software, i.e. to other contractors or other countries not part of the ISS, are authorized by the agreement without prior approval of both agencies.

Requirements and conditions under this agreement will remain in force until both parties that signed this agreement agree otherwise.

This bilateral agreement in no way precludes agencies, prime contractors or subcontractors from commercial arrangements or ventures with other agencies or contractors, as necessary.

All hardware and software will be handled in accordance with program requirements.

authority, control and maintenance authority This hardware and software exchange agreement implements the SSP 50908, NASA/ASI PMM Joint Implementation Plan (JIP). These agreements document the authority and necessity for hardware and software exchanges for the ISS Program.

ASI and NASA and their contractors are authorized to exchange the hardware and software listed herein in the most expeditious manner and without further approvals, and in accordance with the schedule documented in Section 5.0.

control This bilateral agreement provides a dynamic management tool in that changes can be negotiated or generated as a function of changing requirements, design definition, qualification and verification.

The control of this document is described in the Joint Implementation Plan (JIP). The NASA ISS Program Manager and the ASI MPLM/PMM Program Manager jointly approve this BHSEALS document through the ISS Program configuration management process. Changes and additions will be coordinated by the NASA PMM Project Manager, the ASI PMM Project Manager and Thales Alenia Space Italia (TAS-I), (ASI contractor) PMM Program Manager. The changes and additions coordinated by the NASA PMM Project, the ASI PMM Project and the TAS-I PMM Program may be signed as interim working agreements prior to submittal for ISS Program formal baseline update (see paragraph 3.1 concerning supplemental agreements). Changes and additions will be authorized by the NASA ISS Vehicle Managers and ASI MPLM/PMM Program Manager through the ISS Program configuration management process.

maintenance Following initial approval, NASA is responsible for the maintenance of this bilateral exchange agreement. Maintenance consists of collecting changes and additions, incorporating changes, obtaining coordination signatures, presenting changes and additions to the approval authority, updating the revision history, and releasing revisions or change pages as required.

precedence This agreement is subordinate to the NASA/ASI PMM JIP.

1-3 documents applicable documents The following documents of the revision or change, as defined in other bilaterally controlled documents, are applicable subject to any limitations as might be specified herein.

2-1 hardware and software agreements supplemental agreements The providing and receiving organizations may make supplemental agreements in order to facilitate the exchanges identified herein. These supplemental agreements must be within the scope of the agreements defined in this document, and may include such things as: unique identifiers, contact names and addresses, shipping addresses, detailed information for exchanged items, details on technical support, changes in delivery and return dates, export data.

These supplementary agreements will be documented and signed by responsible members of the providing and receiving organizations. NASA and ASI will review all supplemental agreements, have approval authority over these supplemental agreements, and attach any supplemental agreements to this document as appendices.

3-1 requirements and responsibilities assignment of responsibilities NASA and ASI will each be responsible for issuing direction to their respective contractors as necessary to meet the requirements of this agreement. The Providing Organization is the Agency or company that has physical possession of the hardware and desires to transfer that hardware to another organization. The Receiving Organization is the Agency to whom the hardware is transferred by any method, including commercial shipment, handcarry, etc. The responsibilities of NASA and ASI when they function as the “Providing Organization” are listed in paragraph 4.2. The responsibilities of NASA and ASI when they function as the “Receiving Organization” are listed in paragraph 4.3.

responsibilities of the providing organization The organization providing the flight or ground support hardware will perform the following:

· Coordinate with the Receiving Organization to define and document any supplemental agreements, as described in section 3, necessary to efficiently accomplish the exchange.

· Deliver the hardware and software in accordance with the schedule defined in section 5.0. Shipping costs will be the responsibility of the providing organization.

· Provide periodic schedule status on development and production of the item to be exchanged.

· Provide technical support for the exchanged items as per dedicated supplemental agreements, when needed, or as per documents to which this agreement is subordinated.

· Notify the Receiving Organization that the hardware and/or software have been sent.

· Provide configuration control of the exchanged items. For those items that are transferred permanently, configuration control shall be transferred to the receiving organization following hardware/software transfer and formal acceptance by the receiving organization.

· Arrange for appropriate export authorizations for temporary or permanent export.

· Arrange for prompt execution of export customs procedures and payment of any export fees applicable to temporary export items.

· Negotiate, document, and implement technical and product assurance requirements for the exchanged items.

Acceptance Data Packages provided with hardware will be in accordance with the SSP 50914, NASA/ASI Bilateral Data Exchange Agreements, Lists and Schedules (BDEALS) for PMM.

responsibilities of the receiving organization The Receiving Organization shall coordinate with the Providing Organization to define and document any supplemental agreements, as described in section 3.0, needed to efficiently accomplish the exchange. The Receiving Organization shall negotiate technical and product assurance requirements for the exchanged items.

Upon notification of shipment leaving the Providing Organization and receipt of shipment information, the Receiving Organization shall arrange for prompt execution of entry customs procedures and payment of any import fees applicable to received items. The Receiving Organization shall notify the Providing Organization of the receipt of the hardware and/or software. The Receiving Organization will, in coordination with on-site Quality Personnel from the Providing Organization, perform a receiving inspection to document the condition of the hardware, report results of the receiving inspection to the Providing Organization, and support resolution of discrepancies found during receiving inspection.

The Receiving Organization shall store, handle, integrate and operate the provided hardware in accordance with the agreements documented herein and supplemental agreements documented in accordance with paragraph 3.1. Configuration control of the items and complete records on the operation of exchanged items shall be maintained and provided to the providing organization. For those items that are transferred permanently, the receiving organization shall be responsible for the configuration control of the item following transfer and formal acceptance of the hardware/software item.

The Receiving Organization shall provide for timely return of all hardware and ground support equipment upon request. This includes excess flight or test hardware, damaged or failed hardware, and hardware recalled for calibration, maintenance, or repair. Returned hardware will be packaged using proper packaging and inspections, including coordination with on-site quality personnel from the original Providing Organization.

The Receiving Organization will return any re-useable shipping containers, as well as any other containers identified by the Providing Organization, within 30 days of the receipt of the hardware unless alternate arrangements have been agreed upon.

responsibilities for ground support equipment (gse) No GSE will be provided by ASI to NASA for PMM.

4-2 hardware and software exchange lists nata to asi hardware and software list Tables 5.1.1-1 to 5.1.3-2 contain the hardware and software that NASA will provide to ASI.

The need date indicated in the tables correspond to the on-dock date at the receiving organization site.

The NASA-to-ASI hardware and software will be delivered to the ASI Contractor for PMM, which is TAS-I., as follows:

· Hardware: at the PMM footprint in the Space Station Processing Facility (SSPF) at the Kennedy Space Center (KSC);

· FM3 Hardware: turned over to TAS-I at KSC and KSC will assist in shipping to TAS-I premises in Torino

· Software: at TAS-I premises in Torino (delivery via ftp site).

nasa to asi software Table 5.1.1-1 provides a list of software provided as Government Furnished Equipment by NASA to ASI.

table 5.1.1-1 gfe software to asi

Requesting verification of software version currently loaded in MPLM FM1 – move to BDEALS(?)

Jan 2010

nasa to asi test and ground support equipment There is no Test and Ground Support Equipment (TGSE) provided as Government Furnished Equipment by NASA to ASI.

The NASA TGSE to be provided by NASA to ASI for ASI operations at KSC will be documented in the Launch Site Support Plan.

nasa to asi flight hardware NASA will provide to ASI the fully integrated MPLM Flight Unit “Leonardo” in the configuration flown for 19A mission, to allow the ASI Contractor, TAS-I, to intervene on the flight hardware at the KSC for reworking and Analysis and Integration Team (AIT) activities, as regulated by the NASA/ASI JIP.

The status of MPLM post-19A mission verification activities shall be documented by NASA and provided to ASI.

NASA will provide upon ASI request the following components for integration and installation in the PMM flight unit at KSC:

· Spare parts (i.e. equipment, Line Replaceable Unit (LRUs), Orbital Replacement Unit (ORUs), components, materials, harness, etc.) delivered by ASI to NASA as part of the MPLM Baseline configuration;

· Parts (i.e. equipment, LRUs, ORUs, components, materials, harness, etc.) that can be obtained from the Donatello module.

Agreements between NASA and ASI will be reached on case-by-case bases as per the NASA/ASI JIP. That is, ASI will present to NASA the request of receiving specific parts as soon as the need is identified, then an agreement between NASA and ASI shall be established to accomplish the ASI request.

The items/parts that are received from ASI as flight hardware will be returned to NASA as part of the integrated PMM flight element, or separately with the flight element as loose parts.

Table 5.1.3-1 provides a list of all Flight Hardware provided as Government Furnished Equipment by NASA to ASI for integration in PMM. This hardware will be delivered to ASI for PMM at KSC.

5-5 table 5.1.3-1 gfe flight hardware to asi

NASA will provide to ASI a partially integrated MPLM Flight Unit “Donatello” (FM3) to allow the ASI Contractor, TAS-I, to remove a selected list of items/parts from it, for reworking and modification activities, as per the NASA/ASI JIP.

The hardware removed from MPLM FM3 will be documented in a data package to be provided by TAS-I with transfer of responsibility to ASI.

The following documents will be part of the TAS-I data Package:

asi to nasa hardware and software list asi to nasa software Table 5.2.1-1 provides a list of all software provided as developed product by ASI to NASA. Deliveries of software include electronic transmittals of the software and associated documentation as per relevant SSP 50914, BDEALS. For PMM flight software, the “Need Date” corresponds to the date the software must be physically delivered to NASA.

Detailed TMM issue will be determined as part of the joint ASI/NASA PMM Sustaining Engineering Plan.

table 5.2.1-1 software from asi to nasa

asi to nasa test and ground support equipment There is no TGSE provided by ASI to NASA.

asi to nasa flight hardware ASI will provide to NASA the flight hardware listed in Table 5.2.3-1. The PMM flight element will be delivered closed for flight in launch configuration without cargo.

The items/parts that are received from NASA as flight hardware and will not be used as part of the integrated PMM flight element will be returned to NASA separately with the flight element as loose parts.

All other hardware and software necessary to accommodate the PMM on-orbit at the ISS will be under NASA responsibility and no ASI and/or TAS-I involvement and responsibilities will be established (unless otherwise stated in the NASA/ASI JIP).

table 5.2.3-1 flight hardware provided by asi to nasa

The hardware removed from MPLM FM3 will be returned to NASA once integrated into the PMM Flight Module. The items/parts that are received from NASA as flight hardware and will not be used as part of the integrated PMM flight element will be returned to NASA separately with the flight element as loose parts.

5-7

Appendix A - Acronyms and abbreviations

A-1 Appendix B - glossary of terms <reserved>

B-1 Appendix C - open work Table C-1 lists the specific To Be Determined (TBD) items in the document that are not yet known. The TBD is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBD item is numbered based on the section where the first occurrence of the item is located as the first digit and a consecutive number as the second digit (i.e., <TBD 4-1> is the first undetermined item assigned in Section 4 of the document). As each TBD is solved, the updated text is inserted in each place that the TBD appears in the document and the item is removed from this table. As new TBD items are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBDs will not be renumbered.

Table C-1 to be determined items

Table C-2 lists the specific To Be Resolved (TBR) issues in the document that are not yet known. The TBR is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBR issue is numbered based on the section where the first occurrence of the issue is located as the first digit and a consecutive number as the second digit (i.e., <TBR 4-1> is the first unresolved issue assigned in Section 4 of the document). As each TBR is resolved, the updated text is inserted in each place that the TBR appears in the document and the issue is removed from this table. As new TBR issues are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBRs will not be renumbered.

table C-2 TO BE RESOLVED ISSUES

C-1 image2.emf image3.emf image4.emf image1.wmf