SSP-50136_RevA.doc

SSP 50136

Revision A

NASA/Roscosmos Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

International Space Station Program

Revision A

June 2007

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract Number: NNJ04AA02C

REVISION AND HISTORY PAGE

PREFACE

NASA/ROSCOSMOS 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 Roscosmos. In addition, this agreement defines the technical support necessary for the shipment of the hardware and software. The Space Station Program Control Board (SSPCB) delegates control and approval for future updates and revisions to the Mission Integration and Operations Control Board (MIOCB).

This bilateral exchange agreement implements the NASA and Roscosmos Joint Management Plan, Paragraph 4.5.2, Hardware and Software Exchange Process. Both NASA and Roscosmos herein mutually agree that the execution of this hardware and software exchange agreement is necessary for the effective and safe integration of the International Space Station (ISS).

INTERNATIONAL SPACE STATION PROGRAM

NASA/ROSCOSMOS Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

CONCURRENCE

june 2007

INTERNATIONAL SPACE STATION PROGRAM

NASA/ROSCOSMOS Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

LIST OF CHANGES

june 2007 All changes to paragraphs, tables, and figures in this document are shown below:

SSCB

Entry Date

Change

Paragraph(s)

February 1998

Baseline

All

October 2007

Revision A

All

TABLE OF CONTENTS

PARAGRAPH

PAGE

1-11.0 introduction

1.1

PURPOSE

1-1 1.2

SCOPE

1-2 1.3 precedence

1-2 1.4 delegation of authority

1-2 1.5

BACKGROUND

1-2 1.6

DOCUMENT CONTROL

1-2 2.0 documents

2-1 2.1 applicable documents

2-1 2.2 reference documents

2-1 3.0

DEVELOPMENT AND CONTROL OF BHSEALS DATABASE

3-1 3.1

PROCESS FOR ADDITIONS, DELETIONS, OR CHANGES TO

THE BHSEALS DATABASE

3-1 3.2

PERIODIC RECONCILIATION OF THE BHSEALS DATABASE

3-1 4.0 Special shipments

4-1 5.0

REQUIREMENTS AND RESPONSIBILITIES

5-1 5.1

ASSIGNMENT OF RESPONSIBILITIES

5-1 5.2 responsibility of hardware owner

5-1 5.3

RESPONSIBILITIES OF THE PROVIDING ORGANIZATION

5-1 5.4

RESPONSIBILITIES OF THE RECEIVING ORGANIZATION

5-2 5.5 transfer of responsibilities in cases where the providing organization retains responsibility for the article to be exchanged

5-3 6.0

FIDELITY DEFINITIONS

6-1 7.0

SPECIAL CONDITIONS

7-1 7.1

COPYRIGHTS

7-1 7.2

USE OF EXCHANGED HARDWARE/SOFTWARE

7-1 7.3

CONFIDENTIALITY

7-1

APPENDIX

aa Acronyms and abbreviations

-1 b glossary of terms b-1 c open work c-1 d Notice of Document Change d-1 e technical protocol e-1 f Hardware and software exchange lists f-1

TABLE

cC-1 to be determined items

-1 C-2

TO BE RESOLVED ISSUES

c-1

1.0 introduction

This bilateral agreement documents arrangements between National Aeronautics and Space Administration (NASA) and Roscosmos regarding hardware and software to be exchanged between NASA and Roscosmos in carrying out their respective International Partner (IP) roles in the International Space Station (ISS).

This agreement includes NASA or Russian hardware and software exchanges such as, but not limited to:

A.

Development hardware and software to be used in interface simulations and verification testing

B.

Support equipment used in simulations, verification testing, training, and operations

C.

Flight hardware and software delivered for fit checks, certification, verification, testing or training that may be launched in the future.

This agreement is not intended to include:

A.

Cargo and Payloads to be manifested

B.

Flight hardware and software exchanged on orbit

It is recognized that this document must comply with the top-level ISS Program documents listed below, which take priority over this agreement, and any changes made to the top-level documents must be reflected in the subsequent modifications to this agreement:

A. The Agreement between the Governments of the United States of America and the Russian Federation concerning the Procedure for the Customs Documentation and Duty-Free Import of Goods Transported within the Framework of U.S.-Russian Cooperation in the Exploration and Use of Space for Peaceful Purposes, signed on December 16, 1994.

B. Memorandum of Understanding Between the National Aeronautics and Space Administration of the United States of America and the Russian Space Agency Concerning Cooperation on the Civil International Space Station (January 29, 1998).

1.1 PURPOSE

A.

Identify and describe hardware and software to be exchanged between Roscosmos and NASA, including their respective contractors in development of the ISS.

B.

Identify the responsible organization for providing this hardware and software.

C.

Define the requirements and responsibilities for the use and support of the delivery of this hardware and software, including technical support, acceptance data packages, configuration management, logistics, and maintenance. Define the processes for negotiating and documenting final details of these requirements. These processes will be tailored to the criticality of the intended application, and will utilize existing documentation where appropriate.

D.

Define the management process for maintaining and tracking this exchange activity.

1.2 SCOPE

This document represents the authoritative executive agreement between NASA and Roscosmos on hardware and software exchanges between the Russian and United States (U.S.) partners in carrying out their respective IP roles in the ISS.

The terms of this agreement apply whether custody of the exchanged item is retained by the providing organization or transferred to the receiving organization. Specific responsibilities for these two cases are identified in paragraph 5.0.

Hardware and software exchanges authorized under other contracts between NASA and any Roscosmos are not subject to this agreement.

1.3 precedence

This document is subordinate to the SSP 50107, NASA/RSA Joint Management Plan.

1.4 delegation of authority

This document will be revised, as needed, by the NASA Book Manager. The Roscosmos Book Manager will be informed of all revisions.

1.5 BACKGROUND

The Joint Management Protocol adopted by NASA and Roscosmos established this document as one of a series of bilateral agreements to be accomplished in implementation of the joint U.S./Russian development of the ISS. The exchange of appropriate hardware and software provides mutual benefits in this Program, including:

A.

Improves feasibility and performance of the Space Station by allowing use of the best available technology in each country’s segment.

B.

Assures compatibility of the U.S. and Russian flight systems by making authentic hardware and software available for interface development and verification by the other side.

1.6 DOCUMENT CONTROL

All changes to this document require the approval of the NASA Space Station Program Manager and the Roscosmos Deputy General Director.

2.0 documents

2.1 applicable documents

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The documents listed in this paragraph are directly applicable to the extent specified herein. Inclusion of applicable documents herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of this document.

2.2 reference documents

The following documents contain supplemental information to guide the user in the application of this document. These reference documents may or may not be specifically cited within the text of this document.

3.0 DEVELOPMENT AND CONTROL OF BHSEALS DATABASE

Development of the Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules (BHSEALS) database will be controlled by the NASA BHSEALS Book Manager.

3.1 PROCESS FOR ADDITIONS, DELETIONS, OR CHANGES TO THE BHSEALS DATABASE

Per the technical protocol, the technical teams will produce a Notice of Document Change (NDC) listing the items to be exchanged. The NASA Book Manager will assign the NDC number and any other tracking numbers to each NDC.

The U.S. and Russian technical teams are responsible for obtaining all technical team level signatures on the NDC. The U.S. technical team will then provide the NDC and a copy of the technical protocol to the NASA Book Manager. The NASA Book Manager will then submit the NDC for approval by the management of the providing and receiving organizations.

The BHSEALS database will be updated upon receipt of both the providing and receiving organizations’ management signatures. The database will be initiated by the NDC and finalized by the final ProForma Invoice.

For shipments to Russia, hardware cannot ship prior to receipt of all signatures on the NDC, the Technical Protocol and the Three-Way Protocol and customs paperwork has been finalized.

3.2 PERIODIC RECONCILIATION OF THE BHSEALS DATABASE

Twice a year, the NASA BHSEALS Book Manager will provide a copy of the BHSEALS database to the Book Managers of the Roscosmos contractors participating in BHSEALS. The Book Managers will review the database to ensure its accuracy.

4.0 Special shipments

This document also applies in the event that either party needs to ship hardware that is not manifested but has the potential of launching on a future flight. In this case special instructions will be outlined in the Technical Protocol such as photographs, or explicit details to serve flight hardware customs requirements. An example of this would be test hardware that could be used for spares or delivered on an as need basis and may be launched on the receiver’s vehicle at a later date.

5.0 REQUIREMENTS AND RESPONSIBILITIES

5.1 ASSIGNMENT OF RESPONSIBILITIES

NASA and Roscosmos will each be responsible for issuing direction to their respective contractors or subordinate agencies as necessary to meet the requirements of this agreement.

5.2 responsibility of hardware owner

Transportation of hardware to be exchanged is the responsibility of the side that owns the hardware.

5.3 RESPONSIBILITIES OF THE PROVIDING ORGANIZATION

The providing organization may select either of the following options:

A. Transfer the responsibility for the item being exchanged to the receiving organization for the duration of the exchange.

B. Retain the responsibility for the item being exchanged for the duration of exchange (provisions of section 5.5 apply).

The providing organization (technical team/hardware provider) is responsible for:

A.

Coordinating with the receiving organization to define the items to be exchanged and creating a Technical Protocol to document this agreement.

B.

Providing the necessary documents to the BHSEALS Book Manager:

1.

Technical Protocol

2.

NDC Form

3.

ProForma Invoice Note: Preferably, in order to expedite the process, the NDC and the preliminary ProForma Invoice are to be delivered to Roscosmos contractor in parallel.

C.

Resolve any discrepancies after notification from Book Manager.

D. Obtain and process all necessary export licenses and permits.

E.

Coordination of the shipment with the providing organization’s Shipping Coordinator:

1.

Completing internal export paperwork and shipping documents F. Ensure delivery is made according to the schedule and terms of delivery. Provide notice of delivery delays to the receiving side.

G. Maintenance and provision of spares for items to be exchanged. Maintenance may be performed at the location of operation or at locations determined by the providing organization. Maintenance details may be documented in applicable technical protocols. The providing organization and the receiving organization coordinate the scope of these activities. Maintenance costs and costs for the provision of spares shall be borne by the providing organization, unless the sides agree otherwise.

H. Ensuring the export tax exemption, if applicable.

I. Organizing completion of customs procedures and payment of all required taxes and duties for the item being transported on its own territory. For clear interpretation of the provisions of this paragraph, NASA territory shall be considered to be the territory of the U.S. and of the IPs other than Russia. The territory of Russia and territories of other Commonwealth of Independent States (CIS) states will be considered Roscosmos territory. Shipments that fall outside these guidelines will be handled on a case by case basis.

J. Compliance with technical requirements and the reliability, safety, and quality assurance requirements of items to be exchanged.

Note: for JSC originated shipments, JSC Form 1724, Export Control Request and Approval Worksheet, JSC Form 1735, ProForma Invoice and JSC Form 290, JSC Shipping Document are required.

K. The providing organization must provide sufficient lead time for the necessary BHSEALS and shipping coordination to take place. (Note: Please contact the BHSEALS team as soon as the need for a shipment is identified.)

L. The providing organization will provide any technical information required to complete the shipment.

5.4 RESPONSIBILITIES OF THE RECEIVING ORGANIZATION

The receiving organization is responsible for:

A.

Coordinating with the providing organization to define the items to be exchanged and signing the technical protocol to document this agreement B.

Ensuring that the import is made on a duty-free basis

C.

Maintaining complete records on the exchanged item, to levels consistent with the standards of the receiving organization for that type of hardware or software D.

Timely documenting and reporting of discrepancies and assistance to the Providing Organization in resolution of such discrepancies

E.

Return of item as scheduled.

F.

Organizing completion of customs procedures and payment of all required taxes and duties for the item being transported on its own territory. For clear interpretation of the provisions of this paragraph, NASA territory shall be considered to be the territory of the U.S. and of the IPs other than Russia. The territory of Russia and territories of other CIS states will be considered Roscosmos territory. Shipments that fall outside these guidelines will be handled on a case by case basis.

G. Compliance with technical requirements and the reliability, safety, and quality assurance requirements of items to be exchanged.

5.5 transfer of responsibilities in cases where the providing organization retains responsibility for the article to be exchanged

<TBD 5-1>

6.0 FIDELITY DEFINITIONS

Fidelity of the hardware and software exchanged under this agreement will be shown on the appropriate Technical Protocol and also on the NDC for each item.

7.0 SPECIAL CONDITIONS

7.1 COPYRIGHTS

The Providing Organization shall keep all property rights and copyrights on the exchanged items. Nothing in this agreement is interpreted as a basis for reassignment of the property rights and copyrights for these items or for issuing licenses related to these items.

7.2 USE OF EXCHANGED HARDWARE/SOFTWARE

Items exchanged under the BHSEALS Agreement shall be used only by the receiving organization (Roscosmos or NASA), space agencies of the ISS IPs, and their contractors which are companies of the U.S., the IPs, or the CIS. These exchanges will be used only for performing work in the framework of the ISS Program. Without prior written approval by the providing organization, the receiving organization will not transfer exchange hardware or software to any party outside the above mentioned organizations, will not introduce any changes to the items, and will not duplicate the item or use it for any goals other than mentioned above.

Upon request of the providing organization, the receiving organization will provide a written statement confirming its obligation to adhere to these requirements. This will be submitted in the form of an appropriate certificate.

7.3 CONFIDENTIALITY

It is understood, that in the course of the ISS Program implementation process, the exchange of confidential hardware and software items which are the property of Roscosmos, NASA, or their contractors, may become necessary.

The hardware and software provided in accordance with this agreement are intended for the use exclusively within the ISS Program implementation activities. Consequently, only the personnel of the receiving party directly dealing with the ISS Program activities may have access to such hardware and software. Any other use, commercial or non-commercial, of such hardware and software will require written approval by the providing party.

The party providing confidential hardware and software will attach the appropriate notification on the use rights restrictions. The party receiving such hardware and software is obligated to use them strictly in compliance with the requirements indicated in the notification on the use rights restrictions, as well as to take the appropriate measures ensuring confidentiality, which includes the appropriate instructing of the user personnel who have access to such hardware and software.

In cases when a deliverable, accompanied by the notification on the use rights restrictions, will be handed over to contractors or third parties, the requirements indicated herein shall be applicable to such contractors and third parties, and shall be documented in writing in the respective agreements or included in the terms of the respective contract.

Providing of hardware and software is not, and may not be interpreted as ownership rights transfer, yielding of copyrights, or granting of license to use.

Appendix a - Acronyms and abbreviations

Appendix b - glossary of terms bhseals database

Database to be used to record and track all exchange items defined on the NDC and the final JSC Form 1735.

Exchange Any hardware or software provided to an IP or their subcontractor for fit checks, testing, training, certification, verification, or other purpose and is not:

A.

Being shipped for the sole purpose of launch (i.e., on the Manifest) on the receiving organization’s space vehicle; and

B.

Being shipped under the jurisdiction of an existing contract between NASA and any other Roscosmos contractor.

notice of document change This completed and approved form will be used to authorize a change, addition, or deletion to the BHSEALS database. (See Appendix D for an example).

technical protocol

An agreement generated at the technical level between NASA and Roscosmos (and Roscosmos contractor) stating the exact reason as to why a particular hardware or software exchange needs to take place. (See Appendix E for an example).

Transportation protocol (Three-way protocol)

A trilateral document signed by NASA, Roscosmos and a Roscosmos subcontractor, determining the terms and the items list for a particular shipment of hardware and/or software. This is the basis for Russian Customs authorization of duty-free importation into Russia.

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

Appendix d - Notice of Document Change

NASA/Roscosmos Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

Add item BHSEALS Database

Content of Change:

NDC Title: Create a short title that gives a top-level description of segment, etc. of this hardware/software exchange. Use as few words as possible.

1. Add a row to BHSEALS Database, to include the following information:

Item Number: (to be assigned by Book Manager)

Nomenclature: (name description of hardware or software to be exchanged - include part number)

Quantity:

Baseline Ship Date: (Month/Day/Year)

Providing Organization: (example: NASA/JSC)

Receiving Organization: (example: RSC-ENERGIA)

Item to be Returned?: Yes or No. (If yes, include return date)

Comments:

Authority: (Example: Technical Protocol dated xx/xx/xxxx)

2. Add a row to BHSEALS Database, to include the following information:

Item Number: (to be assigned by Book Manager)

Nomenclature: (name description of hardware or software to be exchanged - include part number)

Quantity:

Baseline Ship Date: (Month/Day/Year)

Providing Organization: (example: NASA/JSC)

Receiving Organization: (example: RSC-ENERGIA)

Item to be Returned?: Yes or No. (If yes, include return date)

Comments:

Authority: (Example: Technical Protocol dated xx/xx/xxxx)

/Date RSC-Energia /Date KhSC /Date

GCTC

/Date

Technical Team

Technical Team

Bilateral Document Manager

Program Mgt./ Technical Mgt.

(Team 0)

Appendix e - technical protocol

Appendix f - Hardware and software exchange lists

To view the history as well as a current list of hardware and software exchanged under this document see http://iss-www.jsc.nasa.gov/nwo/mio/iit/shipments/ web/RSA_BHSEALS.shtml.

PAGE

_1211869164.doc

Protocol

Of the Engineering Meeting

Between NASA/RSA Representatives

Month DD, YYYY

NASA and the Roscosmos representative, RSC-Energia, came to an agreement regarding deliveries of NASA equipment to Russia (RSC-Energia) that are needed to support development and maintenance of ISS Simulation Software for NASA. The items listed in the attachment are to be delivered to upgrade the functionality of the Ground Support Equipment (GSE) facility at RSC-Energia. The first delivery is in progress in accordance with the previous protocol dated Month DD, YYYY. The second delivery is in process in accordance with the previous protocol dated Month DD, YYYY. This is the third such delivery of equipment – there will be other deliveries with separate protocols as the specifics of the GSE equipment are defined.

Bilateral Document SSP 50136 is the basis for these deliveries. Appropriate SSP 50136 changes will be made by Notice of Document Change (NDC) as agreed to and signed by NASA and RSC-Energia.

The planned delivery date for the equipment in the attachment is DD Month YYYY.

Prepared by:

NASA Book Manager Roscosmos Book Manager

Concurred by:

NASA Technical Lead

Concurred by:

NASA RSA Project MGR

Roscosmos Project Team

Approved by:

NASA/RSA Integrations MGR

Roscosmos Project MGR