3.1.1.1 Flight Unit. The flight unit will be produced according to NASA functional requirements and performance specifications, including those for provision of a video system, fully integrated into an ESA-provided flight rack that meets International Standard Payload Rack (ISPR) specifications and interface requirements. The fully integrated flight unit will be delivered no later than six months before the launch readiness date of December 2000.

3.1.1.2

3.1.1.3

Ground Unit. The ground unit will be a functional simulator dedicated to protocol development and experiment testing. It will be functionally equivalent to the flight unit and all of the experiment and crew interfaces to the ground unit shall be high-fidelity. The ground unit will be supported by sufficient configuration documentation to allow NASA configuration control and maintenance of the unit. The ground unit will be delivered no later than 18 months before launch readiness date.

Training Unit. The training unit will be a mock-up unit supporting whole Station training, including malfunction simulation and front panel crew interfaces. The training unit will be supported by sufficient configuration documentation to allow NASA configuration control and maintenance of the unit. The training unit will be delivered no later than 18 months before launch readiness date.

3.1.1.4 Engineering Unit. The engineering unit will be of sufficiently high fidelity to support sustaining engineering functions such as anomaly resolution (hardware and software) and verification of system operational changes during on-orbit operations. To achieve this objective all functions, interfaces and hardware configuration shall be flight identical. The engineering unit, will be delivered to NASA upon the onorbit acceptance and verification of the flight unit, unless otherwise agreed.

3.1.2 Freezers (Minus 80 Degree Celsius).

3.1.2.1 Flight Units. A total of three flight units will be produced according to NASA functional requirements and performance specifications, fully integrated into ESA-provided flight racks that meet ISPR specifications and interface requirements. The three flight units will be used for logistics purposes to transport thermally controlled items between the ground and the Space Station. Each flight unit will be delivered no later than six months before its respective launch readiness date:

Flight Unit

First Unit

Second Unit

Third Unit

Launch Readiness Date
August 1999
December 2000

September 2001

The capacity of each flight unit will be at least 0.3 cubic meters of refrigerated volume.

3.1.2.2 Ground Unit. The ground unit is to accurately represent the thermal conditioning characteristics of the flight unit for experiment ground testing, development and verification of science protocols and in-flight procedures. The unit will provide high fidelity crew interfaces limited to those required to meet these objectives. The ground unit will be delivered no later than 18 months before to the launch readiness date of the first flight unit.

3.1.2.3 Training Unit 1. The training unit will be a flight-like mockup unit of the front panel crew interfaces with simulation of all data displays, including malfunction simulation for crew and ground controllers. The software simulator must be able to interface with Space Station Training Facility. The first training unit will be delivered no later than 18 months before the launch readiness date of the first flight unit.

Training Unit 2. The training unit will be an operator-interface high fidelity mock-up unit to support hands on training including, in-flight maintenance procedure, repair due to malfunctions, safing, replacing Orbital Replacement Units (ORU's), and installation/deinstallation procedures of the freezer. The training unit will be supported by sufficient configuration documentation to allow NASA configuration control and maintenance of the unit. The second training unit

3.1.3

3.1.4

will be delivered no later than 18 months before the launch readiness date of the first flight unit.

Engineering Unit. The engineering unit will be of sufficiently high fidelity to support sustaining engineering functions such as anomaly resolution (hardware and software) and verification of system operational changes during on-orbit operations. The engineering unit will be delivered to NASA upon the on-orbit and ground acceptance and verification of the flight units, unless otherwise agreed.

Hexapod Pointing System.

3.1.3.1

3.1.3.2

3.1.3.3

Flight Unit. The flight unit will be produced according to NASA functional requirements and performance specifications and verified to meet NASA requirements for acceptance and flight. The flight unit will be delivered no later than 12 months before the launch readiness date for SAGE III, but not earlier than January 2000.

Simulators. ESA will provide the following simulators of the Hexapod: (a) a low-fidelity simulator with geometry and mass characteristics suitable to support neutral buoyancy testing and crew training at Johnson Space Center for installation and servicing activities involving the remote manipulator system and/or extravehicular activity; and (b) a high fidelity partial simulator to verify mechanical interface between hexapod and science instrument (e.g., SAGE III); and to verify data system interfaces. All simulators will be delivered no later than mid1998.

Engineering Unit. The engineering unit will be of sufficiently high fidelity to support sustaining engineering functions such as anomaly resolution (hardware and software) and verification of system operational changes during on-orbit operations. The engineering unit will be delivered to NASA upon the on-orbit acceptance and verification of the flight unit, unless otherwise agreed.

ESA Mission Data Base system.

3.1.4.1 Mission Data Base. ESA will deliver to NASA, for the sole purpose of International Space Station cooperation, the ESA Mission Data Base (MDB) software as developed by the ESA contractors as part of the ESA Columbus program, for use in the NASA Mission Build Facility. The software will include a number of agreed special extensions to meet specific NASA needs with respect to the use at the Mission Build Facility and will also include all necessary documentation and training, in support of use of the MDB software by NASA contractors. The MDB is a ground software tool which provides a central repository for all software and data products as well as the tools to perform configuration management, consistency testing and to maintain security of these products. The products which can be stored and managed by the MDB software include the flight element configuration definition, the flight software, flight procedures, displays, telemetry and command definition.

3.1.4.2

The MDB software is part of the Columbus Ground Software (CGS) and is produced according to the Columbus CGS Assembly Requirement Specification SPE 1214 597 Issue 1, of February 7, 1994. This original CGS specification is extended with the additional functional requirements as agreed for MDB utilization as part of the Mission Build Facility and is released as Issue 4, dated October 20, 1994.

3.1.4.3 The delivery to NASA of the MDB Software was in the form of incremental deliveries starting with V2.1 in December 1994 through the final version V3 in December 1995 and included training and technical support up to the end of 1995.

3.1.4.4

3.1.4.5

Columbus Ground Software. ESA will make available free of charge to NASA, for the sole purpose of International Space Station cooperation, the basic CGS as developed by ESA contractors as part of the ESA Columbus program as defined by the baseline CGS technical specification referred to in subparagraph 3.1.4.2.

ESA assisted NASA in the initial replan activities (end 1994/ early 1995) required to incorporate the CGS into the Software

Verification Facility (SVF) baseline. ESA will maintain the basic CGS product and will make available to NASA, for the sole purpose of International Space Station cooperation, a copy of each new version of the CGS free of charge.

3.2 Delivery Schedules. The delivery dates cited in subparagraphs 3.1.1, 3.1.2 and 3.1.3 are target dates consistent with the International Space Station Assembly Sequence Revision B, dated September 26, 1996. Delivery dates will be updated as necessary and controlled in the respective implementation plans for each of the applicable ESA-provided utilization enhancement items, as required in subparagraph 3.3.5.

3.3 Additional ESA Responsibilities.

3.3.1

3.3.2

3.3.3

Reliability and Maintainability. ESA will design and develop each utilization enhancement item, other than the hexapod, to achieve 10 years of useful operational life for flight units, through a strategy of reliability, maintenance, replacement, or some combination thereof. For the hexapod, ESA will design and develop for 5 years of useful operational life without scheduled maintenance or replacement.

Item-Specific GSE. ESA will make available item-specific GSE necessary to support ground operations as specified in the respective implementation plans.

Training, Operational Support, Maintenance, and Sustaining
Engineering.

For each utilization enhancement item which entails delivery of flight units, ESA will provide maintenance procedures and an initial set of spares, as agreed in the respective implementation plans.

ESA will provide, until the time of successful on-orbit acceptance and verification of the utilization enhancement items, as agreed in the respective implementation plans, the following: training support, post shipment check out and acceptance support in the United States, launch support as necessary, and sustaining engineering.