SSP-50803.doc

SSP 50803

Baseline

Generic NASA/ESA Bilateral Hardware and Software Exchange Agreements, Lists and Schedules

International Space Station Program

Baseline

June 2007

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

REVISION AND HISTORY PAGE

PREFACE

Generic NASA/ESA Bilateral hardware and software exchange agreements, lists and schedules This Bilateral Hardware and Software Exchange Agreement identifies the hardware and software that will be exchanged between the National Aeronautics and Space Administration (NASA) and European Space Agency (ESA). In addition, this agreement defines the technical support that will be provided for the hardware and software exchange.

This bilateral exchange agreement implements the NASA and ESA Joint Management Plan (JMP), Paragraph 3.11, Hardware and Software Exchange Process. In addition, this agreement complies with SSP 50223, International Space Station Export Control Plan. This document is developed and maintained by the International Integration Team. The initial baseline release is under the control of the Space Station Control Board (SSPCB/Space Station Control Board (SSCB). The SSPCB/SSCB delegates control and approval authority for future updates and/or revisions to the Mission Integration and Operations Control Board (MIOCB).

Both NASA and ESA 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).

This bilateral exchange agreement covers all ESA elements and hardware/software exchanges between NASA and ESA, with the exception of exchanges under SSP 50528, Node 3 Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules, for the Node 3 module and SSP 50280, Node 2 Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules, for the Node 2 module.

INTERNATIONAL SPACE STATION PROGRAM

exchange agreements, lists and schedules

CONCURRENCE

june 2007

INTERNATIONAL SPACE STATION PROGRAM

exchange agreements, lists and schedules

CONCURRENCE

june 2007

INTERNATIONAL SPACE STATION PROGRAM

Generic NASA/ESA 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)

July 2007

Baseline

All

TABLE OF CONTENTS

PARAGRAPH

PAGE

1-11.0

INTRODUCTION

1.1

PURPOSE

1-1 1.2

SCOPE

1-1 1.3 precedence

1-2 1.4

DELEGATION OF AUTHORITY

1-2 1.5

DEVIATION

1-2 1.6

DEVELOPMENT AND CONTROL OF THE BHSEALS DATABASE

1-2 1.7

PROCESS FOR ADDITIONS, DELETIONS, OR CHANGES TO THE

BHSEALS DATABASE

1-2 1.7.1 Technical protocol

1-3 1.8

PERIODIC RECONCILIATION OF THE BHSEALS DOCUMENT AND DATABASE

1-5 2.0

DOCUMENTATION

2-1 2.1 applicable documents

2-1 2.2 reference documents

2-1 3.0

REQUIREMENTS AND RESPONSIBILITIES

3-1 3.1

ASSIGNMENT OF RESPONSIBILITIES

3-1 3.2

RESPONSIBILITIES OF THE PROVIDING ORGANIZATION

3-1 3.3

RESPONSIBILITIES OF THE RECEIVING ORGANIZATION

3-1 4.0 SPECIAL CONDITIONs

4-1 4.1

COPYRIGHTS

4-1 4.2

USE OF EXCHANGED HARDWARE/SOFTWARE

4-1 4.3

CONFIDENTIALITY

4-1

APPENDIX

aa Acronyms and abbreviations

-1 b glossary of terms b-1 c open work c-1 d example of technical protocol d-1 e ESA Notice of document change form (E-NDC) e-1 f

APPROVED DATABASE CHANGES

f-1

FIGURE

1-41.7-1 Illustration of BHSEALS Process

1.0 INTRODUCTION

This document is one of a series of bilateral agreements to be accomplished in implementation of the joint National Aeronautics and Space Administration (NASA)/European Space Agency (ESA) development of the International Space Station (ISS). This bilateral agreement documents arrangements between NASA and ESA regarding hardware and software to be exchanged between NASA and ESA in carrying out their respective International Partner (IP) roles in the ISS. This agreement includes related hardware and software exchanges such as:

A.

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

Hardware and software spares This agreement is not intended to include:

A.

Flight hardware and software that will be delivered to Kennedy Space Center (KSC) for launch B.

Ground support hardware and software for launch processing C.

Flight hardware and software that will be exchanged on orbit D.

Hardware and software that was exchanged and have been already returned to providing organization E.

Node 3 module related hardware or software

1.1 PURPOSE

The purpose of SSP 50803 is:

A.

To identify and describe hardware and software to be exchanged between NASA and ESA, including their respective contractors in development of the ISS B.

To define the schedule for hardware and software exchanges between NASA and ESA C.

To identify the organizations responsible for providing and receiving this hardware and software D.

To define the requirements and responsibilities for the use and support 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 E.

To define the management process for maintaining and tracking this exchange activity, including the shipping process as referenced

1.2 SCOPE

The terms of this agreement apply whether custody of the exchanged item is retained by the Providing Organization or transferred to the Receiving Organization.

1.3 precedence This document is subordinate to SSP 50019, NASA/ESA Joint Management Plan.

This document supersedes the existing Columbus and Cupola Bilateral Hardware and Software Exchange Agreements, Lists and Schedules (BHSEALS). In the event that a piece of hardware of software is already in the old Columbus or Cupola BHSEALS, a Technical Protocol (TP) will be required, but a Notice of Document Change (E-NDC) (see Paragraph 1.7) will not.

1.4 DELEGATION OF AUTHORITY

The Mission Integration and Operations Control Board (MIOCB) has formal control and approval of this document. All changes to this document will be processed in accordance with the procedures as specified in SSP 50123, Configuration Management Handbook.

1.5 DEVIATION

Any request for deviation from this document shall be made to the MIOCB in accordance with the procedures as specified in SSP 41170, Configuration Management Requirements. NASA will maintain this document and process changes per these requirements. ESA should provide any recommended changes to the NASA BHSEALS Book Manager for processing.

1.6 DEVELOPMENT AND CONTROL OF THE BHSEALS DATABASE

The BHSEALS Database is the tool that is used to record and track all exchange items defined in this document. Development of the BHSEALS Database will be controlled and maintained by the NASA BHSEALS Book Manager, but made available for ESA to view at any time.

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

The NASA and ESA technical teams will produce a TP (See paragraph 1.7.1 below) signed by both sides.

The NASA technical team will produce an E-NDC (ESA Notice of Document Change) (see Appendix D) for all items to be exchanged, per the TP.

The NASA technical team will then submit the TP and E-NDC electronically to the NASA BHSEALS Book Manager. The NASA BHSEALS Book Manager will then assign a tracking number to the E-NDC.

The NASA BHSEALS Book Manager will then review these two documents and inform the NASA Technical Team of any discrepancies or corrections needing to be made.

Once the E-NDC is approved by the NASA BHSEALS Book Manager, the NASA and ESA technical teams will work closely together via phone calls, meetings, telecons, faxes, etc., to obtain all team level signatures on the E-NDC. The signed E-NDC will then be returned to the NASA BHSEALS Book Manager for approval by the management of the providing and receiving organizations. Upon approval of the E‑NDC, the NASA BHSEALS Book Manager will update the BHSEALS database with the confirmation of the ESA BHSEALS Book Manager.

The signed E-NDC will then be returned to the NASA BHSEALS Book Manager for approval by the management of the providing and receiving organizations. Upon approval of the E-NDC, the NASA BHSEALS Book Manager will update the BHSEALS database with the confirmation of the ESA BHSEALS Book Manager. The approved E‑NDC and Proforma will then be handed off to the ISS Shipping Coordinator. The NASA and ESA technical teams will then work closely with the ISS Shipping Coordinator to complete the shipment.

Shipments cannot take place prior to the approval of the TP or the E-NDC. The following table outlines the information typically required in the Technical Protocol and Notice of Document Change. Figure 1.7.1-1 illustrates the BHSEALS process.

1.7.1 Technical protocol

Acknowledgment that NASA and ESA have agreed to the exchange Item Description/Quantity

Configuration Control (if applicable)

Figure 1.7-1 Illustration of BHSEALS Process

1.8 PERIODIC RECONCILIATION OF THE BHSEALS DOCUMENT AND DATABASE

The NASA Book Manager will provide a copy of the BHSEALS database to ESA biannually. The NASA Book Manager and the ESA Book Manager will review the database to ensure its accuracy.

Biannually, Appendix F of this document will be updated with a printout of the database as concurred upon by the NASA BHSEALS Book Manager and the ESA Book Manager.

This database printout will include, at a minimum, the following columns:

A.

E-NDC number B.

Item Description C.

Shipped/Received Date D.

Status (Open or Closed)

2.0 DOCUMENTATION

2.1 applicable documents

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The documents listed in this paragraph are 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 REQUIREMENTS AND RESPONSIBILITIES

3.1 ASSIGNMENT OF RESPONSIBILITIES

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

3.2 RESPONSIBILITIES OF THE PROVIDING ORGANIZATION

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 TP to document this agreement.

B.

Providing the necessary documents to the BHSEALS Book Manager:

1.

TP

2.

BHSEALS E-NDC form C.

Resolving any discrepancies after notification by Book Manager.

3.3 RESPONSIBILITIES OF THE RECEIVING ORGANIZATION

The Receiving Organization is responsible for:

A.

Coordination with the Providing Organization to define the items to be exchanged and signing the TP to document this agreement and the E-NDC to track the items.

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, with records on the operation, as scheduled.

4.0 SPECIAL CONDITIONs

4.1 COPYRIGHTS

The Providing Organization keeps all property rights and copyrights in relation to the exchange items. Nothing in this agreement can be interpreted as a basis for reassignment of the property right and copyrights for these items or for issuing licenses related to these items.

4.2 USE OF EXCHANGED HARDWARE/SOFTWARE

The exchanged items may be used only by the Receiving Organization (ESA or NASA), Space Agencies of the ISS IP, and their contractors which are companies of the United States (U.S.), or the IP. 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 exchanged 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.

4.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 ESA, 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

Acceptance

Act of receiving a delivery with verification that the design meets the specification requirements. Acceptance requires delivery paper and accumulation of support data in an acceptance data pack. Acceptance provides assurance that an item was manufactured as designed and is free of manufacturing and workmanship defects.

Accepted

All responsible parties have agreed on a coordinated resolution to the issue of concern.

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 - example of technical protocol

Appendix e - ESA Notice of document change form (E-NDC)

APPENDIX f - APPROVED DATABASE CHANGES

Approved Database Changes to SSP - <TBD F-1>

Period covering:

To: