SSP-50220_RevC.doc

DOC document 357 KB Posted

Attached to
Human Space Flight Technical Integration Contract (HSFTIC) Federal contract opportunity
Solicitation number
80JSC019R0023
Issued by
National Aeronautics and Space Administration Johnson Space Center

About this file

This document contains a bilateral hardware and software exchange agreement between NASA and the Canadian Space Agency (CSA) as well as related protocols and forms. Key details include:

  • The agreement identifies hardware and software to be exchanged between NASA and CSA to support the International Space Station program and defines requirements and responsibilities for use, support, and shipping. Exchanges include development hardware, software for verification testing, and operations/test/training support equipment.

  • Additions or changes are proposed by technical teams through a Technical Protocol and CSA Notice of Document Change form, reviewed by NASA and CSA managers, and updated in the BHSEALS database tracked by NASA. Reconciliation occurs biannually.

  • Shipping plans specify coordination requirements between providers and coordinators for shipments from NASA to CSA and vice versa, including documentation, contacts, import/export processes, and tracking.

  • Three protocols are included as examples for equipment deliveries from NASA to CSA to upgrade ground support facilities, with the third delivery planned for a specified date. Related CSA forms will be updated to reflect the agreements.

SSP-50220 RevC

View the file

Other files for this federal contract opportunity

Other files attached to Human Space Flight Technical Integration Contract (HSFTIC), newest first.
File Type Posted
HSFTIC J-17 placeholder (FRFP).docx DOCX document
HSFTIC Interested Parties List - Rev. 1.pdf PDF
MD_1015_RA_FINAL.docx DOCX document
SSP41142P1_RF_CD_012044_.pdf PDF
42097P1_AE_RF_012968.pdf PDF
SSP41017p1rG.pdf PDF
SSP41143Pt1RevC.PDF PDF
6.0.zip ZIP file
N_PR_9501_002E_.pdf PDF
SSP_50316-Rev_C.docx DOCX document
SSP_57011_Rev_E.docx DOCX document
Applicable_5.zip ZIP file
ISS_Program_Flight_Rate.pptx PPTX presentation
MD_1040_FINAL_PSF_US_Charter.docx DOCX document
SSP_50578-RevC.docx DOCX document
42097P2RE_AE_RE_012967.pdf PDF
DSG-PLAN-004_Gateway_Configuration_and_Data_Management_Plan_Baseline.pdf PDF
SSP_50826.doc DOC document
SSP-50615_Baseline.doc DOC document
Subsystem_&_Mission_Functions_to_Modules.xlsx XLSX spreadsheet
Gateway_generic_org_chart.pptx PPTX presentation
SSP_50038.DOC DOC document
SSP_50190-RevF.docx DOCX document
SSP-50715_RevA.docx DOCX document
SSP_50273_Rev_J.docx DOCX document
50281.DOC DOC document
SSP_50469-RevD-Retired.docx DOCX document
Initial_Baseline_DSG-CONOP-001_06_2019.docx DOCX document
POH_Vol_2_2-2-18.pdf PDF
SSP_50200-01-ANXZ-RevB_SPIP_OZ.docx DOCX document
SSP_50744-Rev_A.docx DOCX document
ssp42097_p2_rd.pdf PDF
SSP_52055_Revision_D.doc DOC document
Work_Load_Indicators_Matrix_FRFP.xlsx XLSX spreadsheet
SSP_41140_P2_RD_111010.pdf PDF
SSP_42007-Rev_L-SSCD_15992.docx DOCX document
SSP_50420-HTV3-Baseline.docx DOCX document
Signed_Approved_Charter_31Aug08_IRT_Charter.doc DOC document
SSP_41147,_Part_1_Rev_C.pdf PDF
SSP_42121-Part_1-RevC.docx DOCX document
SSP_50754-RevA-DCN001-EAR99.docx DOCX document
SSP_50839-RevB-DCN001-Collated_Master.pdf PDF
SSP41148.pdf PDF
PALSTORE.PROD.O0073170.G0000001.IL TXT text file
SSP_30575-RevF.docx DOCX document
SSP_41165-RevN.docx DOCX document
SSP_50005_Rev_G.pdf PDF
SSP_50309_Part_2.pdf PDF
DRFP_Industry_Questions_and_Answers.pdf PDF
Draft_HSFTIC_Request_for_Proposal.pdf PDF
Show all 50

Human Space Flight Technical Integration Contract (HSFTIC) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Directive 009655R1 ATTA

REVISION and history page

Revision Letter
Description
Publication Date

A

B

C

Initial Release (Reference per SSCD 000456, EFF. 02/21/97)

Revision A

NOTE: Rev A was never approved and released to the ISS Program. This fact was not discovered until Rev B of the document and 2809R1directive had been officially approved by the Program and were being posted and released. Therefore, for purposes of the documentation audit trail, versions of this book were approved and released from an Initial Release of the basic document, bypassing Revision A and going directly to Revision B.

Revision B (Reference per SSCD 002809, EFF. 11/30/99)

Revision C (Reference per SSCD 009655R1, EFF. 06/14/06)

02-26-97

01-25-00

01-25-00

08-01-06

INTERNATIONAL SPACE STATION PROGRAM

NASA/CSA BILATERAL HARDWARE AND SOFTWARE EXCHANGE AGREEMENTS, LISTS AND SCHEDULES

March 2006

PREFACE

This Bilateral Hardware and Software Exchange Agreement defines the hardware and software that will be exchanged between the National Aeronautic and Space Administration (NASA) and the Canadian Space Agency (CSA) for the Space Station Program. In addition, this agreement defines the technical support that will be provided for the hardware and software.

This bilateral exchange agreement implements the NASA and CSA Joint Management Plan (SSP 50022), Paragraph 3.11, Hardware and Software Exchange Process. In addition, this agreement complies with NASA’s Space Station Export Control Plan (SSP 50223). The Space Station Program Control Board (SSPCB) delegates control and approval authority for future updates and revisions to the Program Integration Control Board (PICB).

Both NASA and CSA herein mutually agree that the execution of this hardware and software exchange agreement is necessary for the effective and safe integration of the CSA's Mobile Servicing System (MSS) into the Space Station Manned Base (SSMB).

INTERNATIONAL SPACE STATION PROGRAM

CONCURRENCE

INTERNATIONAL SPACE STATION PROGRAM

LIST OF CHANGES

March 2006 All changes to paragraphs, tables, and figures in this document are shown below:

SSCBD

ENTRY DATE

CHANGE

PARAGRAPH(S)

002809 10/19/99 Describe role of MSS Integration 1.5.1

Panel (MIP) Tier II schedule in tracking exchange status

TABLE(S)

002809 10/19/99 Revised Deliverables, Item 5-1 A

Numbers, and Delivery Dates

10/19/99 Revised Deliverables, Item 5-1 B

Numbers, and Delivery Dates

10/19/99 Revised Deliverable Item 5-1 C

Number

FIGURE(S)

APPENDIX(ES)

ADDENDA

TABLE OF CONTENTS

1.0

INTRODUCTION

1.1

BACKGROUND

1.2

PURPOSE

1.3

SCOPE

1.4

DEFINITIONS

1.5

DOCUMENT CONTROL

1.6

APPLICABLE DOCUMENTS

1.7

AUTHORITY

2.0

HARDWARE AND SOFTWARE AGREEMENTS

2.1

PROCESS FOR ADDITIONS, DELETIONS, OR CHANGES TO THE

BHSEALS DATABASE

2.2

PERIODIC RECONCILIATION OF THE BHSEALS DATABASE

3.0

NASA ORIGINATED SHIPMENTS

3.1

REQUIREMENTS AND RESPONSIBILITIES

3.2

PROVIDING ORGANIZATION - NASA

3.3

RECEIVING ORGANIZATION - CSA

4.0

CSA ORIGINATED SHIPMENTS

4.1

REQUIREMENTS AND RESPONSIBILITIES

4.2

PROVIDING ORGANIZATION - CSA

4.3

RECEIVING ORGANIZATION - NASA

5.0

FIDELITY DEFINITIONS FOR USE ON THE C-NDC

FIGURES

2.2-1

HARDWARE AND SOFTWARE EXCHANGE LISTS

APPENDICIES

A

ABBREVIATIONS AND ACRONYMS

B

C-NDC – CSA-NOTICE OF DOCUMENT CHANGE

C

TECHNICAL PROTOCOL

D

HARDWARE AND SOFTWARE EXCHANGE LISTS,

MSS EQUIPMENT

E

SHIPPING PLAN: CSA BHSEALS (SSP 50220)

1.0 INTRODUCTION

This bilateral agreement documents arrangements between the National Aeronautics and Space Administration (NASA) and the Canadian Space Agency (CSA) regarding hardware and software to be exchanged between NASA and CSA in carrying out their respective International Partner roles in the International Space Station (ISS). It includes development hardware and software to be used in verification testing and support equipment used in operations, test, or training. This agreement does not cover hardware and software shipped for the purpose of being launched to the International Space Station.

1.1 background This document is one of a series of bilateral agreements to be accomplished in implementation of the joint U.S. (United States)/CSA development of the International Space Station. 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 CSA flight systems by making authentic hardware and software available for interface development and verification by the other side.

1.2 purpose

1. Identify and describe hardware and software to be exchanged between CSA and NASA, including their respective contractors in development of the International Space Station.

2. Identify the organization responsible for providing this hardware and software.

3. 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.

4. Define the management process for maintaining and tracking this exchange activity, including the shipping process.

1.3 scope This document represents the authoritative agreement between NASA and CSA on hardware and software exchanges between NASA and the International Partners in carrying out their respective roles in the International Space Station Program.

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 3.0 and 4.0.

1.4 definitions BHSEALS - the approved abbreviation for the Bilateral Hardware and Software Exchange Agreements, Lists and Schedules.

EXCHANGE as defined in the BHSEALS process – any hardware or software item shipped under the provisions of this agreement to be used for ground support, training, testing, certification testing or other purpose. This definition excludes any hardware or software shipped for launch on the receiving organization's space vehicle.

CSA-NOTICE OF DOCUMENT CHANGE FORM (C-NDC) – a form to authorize a change, addition, or deletion to the BHSEALS Database, per paragraph 2.0. (See Appendix B)

BHSEALS DATABASE – the tool that is used to record and track all exchange items defined on the BHSEALS Notice of Document Change Form (C-NDC), per paragraph 2.0.

TECHNICAL PROTOCOL (TP) – An agreement generated at the technical level between NASA and CSA stating the exact reason as to why a particular hardware or software exchange needs to take place. (See Appendix C)

1.5 Document CONTROL

All changes to this document require the approval of the NASA International Space Station Program Manager and the equivalent CSA International Space Station Manager.

1.6 applicable documents

DOCUMENT NO.

TITLE

No Number Intergovernmental Agreement (IGA)

No Number Memorandum of Understanding (MOU) between the United States National Aeronautics and Space Administration and the Canadian Space Agency on Cooperation in the Detailed Design, Development, Operation and Utilization of the Permanently Manned Civil Space Station

SSP 29840

Guidelines for International Shipments of ISS Hardware and Software

SSP 30459

International Space Station Interface Control Plan

SSP 41167

MSS Segment Specification

SSP 41170

Space Station Configuration Management Requirements

SSP 50022

NASA/CSA Joint Management Plan

SSP 50033

NASA/CSA Bilateral Integration and Verification Plan

SSP 50062

Bilateral Safety & Mission Assurance Requirements

SSP 50123

Configuration Management Handbook

SSP 50223

International Space Station Export Control Plan

1.7 AUTHORITY

This hardware and software exchange agreement implements the Intergovernmental Agreement (IGA), the NASA/CSA Memorandum of Understanding (MOU), and the NASA/CSA Joint Management Plan (JMP). These agreements document the authority and necessity for hardware and software exchanges for the Space Station Program. This agreement is subordinate to the IGA, the NASA/CSA MOU and the NASA/CSA JMP. Exchanges of hardware and software will be controlled by the process outlined in this document (see Section 2.1) and under the jurisdiction of the MIP (MSS (Mobile Servicing System) Integration Panel).

2.0 DEVELOPMENT AND CONTROL OF BHSEALS DATABASE

Development of the BHSEALS Database will be controlled by the NASA BHSEALS Book Manager.

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

The following outlines the process in which additions, deletions or changes to the BHSEALS Database will be managed:

1.

The technical Teams of the Providing and Receiving Organizations will create a Technical Protocol that summarizes the purpose of the shipment, the hardware and/or software that will be exchanged, whether or not the hardware is to be returned, and if so, at what date, and other relevant details.

2.

The providing organization will complete a BHSEALS Notice of Document Change Form (C-NDC) (see Appendix B) for all items to be exchanged, per the Technical Protocol.

3.

The Technical Protocol and the C-NDC will be forwarded to the NASA BHSEALS Book Manager, who will assign a tracking number to the C-NDC.

The NASA BHSEALS Book Manager will review the documents and return them to the NASA technical team with comments, if necessary.

5.

The technical teams are responsible for obtaining team-level signatures.

6.

The NASA BHSEALS Book manager is responsible for obtaining management-level signatures.

7.

Upon approval of the Technical Protocol and C-NDC by the CSA Manager and the NASA Robotics Integration Manager, the NASA BHSEALS Book manager will update the BHSEALS database.

8.

The Technical Teams contact the ISS Shipping Coordinator to coordinate shipping per the Shipping Plan (Appendix E).

2.2 PERIODIC RECONCILIATION OF THE BHSEALS DATABASE

Biannually, the NASA Book Manager and the CSA Book Manager will reconcile their database records to ensure accuracy. At this time, if necessary, the database will be revised.

For current list of hardware and software exchanged go to http://iss-www.jsc.nasa.gov/ss/issapt/rait/rusship.html.

Contents of Technical Protocol
Contents of C-NDC
Purpose of shipment
Nomenclature and Quantity
Anticipated date of shipment
Baseline Ship Date
Return date, if applicable.
Providing Organization
Generalized list of hardware/software each side is to provide
Receiving Organization
Any handling restraints
Return date, if applicable
Information on Shipping Point of Contact (POC)
Authority (BHSEALS or other)
Signed and approved by both Partners
Signed and approved by both Partners

Fidelity Definition

The illustration of BHSEALS database updated process with document revision is shown in Figure 2.2-1.

Figure 2.2-1: Document Revision and Database Update Process for BHSEALS

3.0 NASA ORIGINATED SHIPMENTS

3.1 REQUIREMENTS AND RESPONSIBILITIES

3.2 PROVIDING ORGANIZATION - NASA

The Providing Organization (technical team/hardware provider) is responsible for:

1. Coordinating with the Receiving Organization to define the items to be exchanged and creating a Technical Protocol to document this agreement.

2. Providing the necessary documents to the BHSEALS Book Manager:

a. Technical Protocol

b. Notice of Document Change Form (C-NDC)

c. Proforma Invoice (Johnson Space Center (JSC) Form 1735)

3. Resolving any discrepancies after notification by Book Manager

4. Coordination of the shipment with the Shipping Coordinator:

a. Completing JSC Form 1724 (Export Control Worksheet) and obtaining any necessary export licenses (Depending on the item, this process may take as long as six months. No shipments can take place without Export Control authorization.)

b. Completing JSC-290 (Shipping Document)

5. The Providing Organization must allow 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.)

6. The Providing Organization will provide any technical information required to complete the shipment.

3.3 RECEIVING ORGANIZATION - CSA

The Receiving Organization is responsible for:

1. Coordination with the Providing Organization to define the items to be exchanged and signing the Technical Protocol to document this agreement.

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

3. Maintaining complete records on the exchanged item, to levels consistent with the standards of the Receiving Organization for that type of hardware or software.

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

5. Return of item, with records on the operation, as scheduled.

4.0 csa originated shipments

4.1 REQUIREMENTS AND RESPONSIBILITIES

4.2 PROVIDING ORGANIZATION - CSA

The Providing Organization (technical team/hardware provider) is responsible for:

1.

Coordinating with the Receiving Organization to define the items to be exchanged and creating a Technical Protocol to document this agreement;

2.

Obtaining from the Receiving Organization the International Programs Blanket Duty-Free Certification;

3. Providing the necessary documents to Logistics Officer:

a.

Proforma Invoice b.

C-NDC;

4. Resolving any discrepancies after notification by Logistics Officer;

5. Coordination of the shipment with the Logistics Officer a.

Completing the Transportation Request and obtaining any necessary export licenses (Depending on the item, this process may take as long as six months.)

b.

Completing Shipping Documents, and;

6.

The Providing Organization must allow sufficient lead time for the necessary logistic and shipping coordination to take place. (Note: please contact the Logistics Officer as soon as the need for a shipment is identified.)

4.3 RECEIVING ORGANIZATION - NASA

The Receiving Organization is responsible for:

1. Coordination with the Providing Organization to define the items to be exchanged and signing the Technical Protocol to document this agreement;

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

3. Maintaining complete records on the exchanged item, to levels consistent with the standards of the Receiving Organization for that type of hardware or software;

4. Timely documenting and reporting of discrepancies, and assistance to the Providing Organization in resolution of such discrepancies, and;

5. Return of item, with records on the operation, as scheduled.

5.0 Fidelity definitions for use on the C-NDC

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

APPENDIX A: ABBREVIATIONS AND ACRONYMS

ADP

Acceptance Data Package

BHSEALS

Bilateral Hardware and Software Exchange Agreements, Lists and Schedules

CM

Configuration Management

C-NDC

CSA Notice of Document Change

CSA

Canadian Space Agency

DDU

Delivered Duty Unpaid

DQA

Data Quality Assurance

EFF

Effective

GSE

Ground Support Equipment

IGA

Intergovernmental Agreement

ISS

International Space Station

JMP

Joint Management Plan

JSC

Johnson Space Center

MIP

MSS Integration Panel

MOU

Memorandum of Understanding

MSS

Mobile Servicing System

NASA

National Aeronautics and Space Administration

PICB

Program Integration Control Board

POC

Point of Contact

Rev Revision

SSCBD

Space Station Control Board Directive

SSCD

Space Station Change Directive

SSMB

Space Station Manned Base

SSP

Space Station Program

SSPCB

Space Station Program Control Board

APPENDIX A: ABBREVIATIONS AND ACRONYMS (continued)

TBD

To Be Determined

TIM

Technical Interchange Meeting

TP

Technical Protocol

U.S.

United States

APPENDIX B: C-NDC – CSA-Notice of Document change

CSA Notification of Document Change (NDC) No.:

SSP XXXXX-XXX

Document Number:

XXXXX

Date C-NDC Originated:

Page 1 of x

Name of Document:

NASA/xxx Bilateral Hardware and Software Exchange Agreement, Lists, and Schedules

Reason for Change:

Add item to BHSEALS Database

Content of Change:

C- NDC Title: XXX

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

Nomenclature: (a brief description of the item)

Quantity:

Fidelity: (i.e. Flight, Test, Protocol, etc) Baseline Ship Date: (month/day/year) Providing Organization: (example: NASA/JSC) Receiving Organization:

Item to be Returned?: (Yes or No) Return Date?

Comments: (optional additional comments if necessary)

Authority: :(Protocol, TIM or agreement source ("Technical Protocol") that authorizes this exchange. )

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

Nomenclature:

Quantity:

Fidelity:

Baseline Ship Date:

Providing Organization:

Receiving Organization:

Item to be Returned?: Return date:

Comments:

Authority:

Copy and paste item information on blank sheets for each additional item

Signatures:
NASA / Date
/ Date
/ Date
/ Date

Technical Team

Technical Team

Bilateral Document

Manager

Technical Mgt.

APPENDIX C: TECHNICAL PROTOCOL

APPENDIX D: HARDWARE AND SOFTWARE EXCHANGE LISTS, MSS EQUIPMENT

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/ss/issapt/rait/rusship.html.

APPENDIX E: Shipping Plan: CSA BHSEALS (SSP 50220)

The following summarizes the current plan used to ship hardware to and from Canada. Management of ISS Shipments is the responsibility of the ISS Shipping Coordinator

Extensive pre-coordination is to take place before the shipment leaves JSC or Canada to ensure that all required documentation is in place.

Shipments from NASA/JSC to Canada

· No later than two weeks prior to the anticipated shipment date, the ISS Shipping Coordinator provides the receiving organization in Canada with:

· A copy of the Proforma Invoice

· The name and contact information of the technical specialist at the receiving company.

· Any shipping constraints

· The Point of Contact (POC) at the receiving organization will request any additional information that may be needed for the Canadian import permissions.

· The POC at the receiving organization will advise the ISS Shipping Coordinator when all the required paperwork is in place.

· The Shipping Coordinator advises the hardware provider and the shipment takes place.

· The Shipping Coordinator advises the POC at the receiving organization of the tracking and routing of the shipment.

Shipments from Canada to NASA/JSC

· Approximately one week prior to the anticipated shipping date, the POC at the providing organization in Canada will provide the ISS Shipping Coordinator and JSC Inbound Transportation with a copy of the commercial invoice for the shipment, which needs to include the name and phone number of the appropriate technical specialist at NASA.

· When the shipment is made, the POC at the providing organization in Canada will provide the ISS Shipping Coordinator and JSC Inbound Transportation with the airway bill information, routing information, and other shipment details.

· For any ISS-related shipment to the U.S., whether to a NASA center or a contractor, please insert this statement: “HTSUSA 9808.00.8000; duty-free certificate is attached.” Please attach a copy of attached two page certificate, “Certification for Foreign Spacecraft and Related Equipment Supporting International Programs,” to the package. (TBD)

· If the item being shipped is a return of hardware owned by NASA or its contractor, please state this on the commercial invoice. Also include information on how and when it was originally shipped. Example statement: “Return of goods imported on air waybill #123456789 on 5/31/02, invoice number 563489”.

· All items placed into the shipping container must be listed. If each item is a piece of one larger item, please list each piece and its respective part/serial number, rather than just the top assembly name and part number. Any Acceptance Data Packages (ADP) or other documentation included in the shipment should also be listed. All items should have a monetary value in U.S. dollars.

· Any special handling requirements must be listed, especially if the items are of Flight Grade

· In the air waybill block for “Harmonized Code”, insert “9808.00.8000”

· Shipment to NASA/JSC are made “DDU – NASA Receiving Dock”

C-NDC

“D"

“C"

“B"

TP

“D”

“C”

“B”

Note: at this point shipments A, B, C, and D can take place (assuming all licenses and shipping issues have been resolved)

“A”

"A"

Biannual Reconciliation by NASA and CSA

Book Managers

Technical Protocols and C-NDCs are maintained on file by NASA BHSEALS Book Manager

NASA and CSA confirmation

Updated BHSEALS

Database

Start CM Process

NASA will update the database

Revised

CSA BHSEALS

C-NDC Forms with NASA and CSA approval

PAGE

i i

_1204712861.doc

SSP 50220, Rev. BC

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

International Space Station

Program

Canadian Space Agency

Agence Spatiale Canadienne

October 19, 1999March 2006

CSA

National Aeronautics and Space Administration

International Space Station Program

Johnson Space Center

Houston, Texas

Revision CB

_1197798559.doc

Protocol

Of the Engineering Meeting

Between NASA/CSA Representatives

Month DD, YYYY

NASA/CSA came to an agreement regarding deliveries of NASA equipment to Canada (CSA) 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 CSA. 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 50220 is the basis for these deliveries. Appropriate SSP 50220 changes will be made by BHSEALS CSA-Notification of Document Change Form (C-NDC) as agreed to and signed by NASA and CSA.

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

Concurred by:

Concurred by:

NASA Technical Lead

CSA Technical Lead

Concurred by:

Concurred by:

NASA Project Manager

CSA Project Manager

Approved by:

Approved by:

NASA Robotics Integration Manager

CSA Robotics Integration Manager

File details come from the government source that posted it. Updated .