**Exhibit 2**

**ISS Operations**

**Statement of Work**

# Introduction

The National Aeronautics and Space Administration (NASA) Microgravity
Science program advocates and coordinates an interdisciplinary research
program to conduct specified research and to disseminate the results of
that research. Research experiments selected for flight definition are
assigned to a vehicle (Space Shuttle, International Space Station,
Sounding Rocket) and/or a research facility (Fluids and Combustion
Facility, Glovebox, etc) best suited for that experiment.

NASA LeRC has a requirement for the integration and operation of
individual flight experiments and the Fluids and Combustion Facility on
the International Space Station to perform numerous microgravity
investigations in combustion science and fluid physics, as well as the
collection of acceleration measurement data. In addition, there will be
requirements for operations support of commercial payloads, and/or
International payloads. To ensure the microgravity experiments are
successfully integrated and operated, it is necessary for NASA LeRC to
develop a sustained operational capability for the Fluids and Combustion
Facility (FCF) and acceleration measurement systems and sustain the
necessary telescience operations capability to support these missions on
the International Space Station.

# Scope

This International Space Station (ISS) Operations statement of work
encompasses the planning for, integration of, and operations of a wide
range of LeRC space operations activities which are required to support
basic research, technology demonstration, commercial and international
research. This statement of work has been structured to address specific
requirements for ISS Mission Integration Planning, FCF Increment
Engineering and Execution, System Engineering and Sustaining
Engineering, Telescience Support Center Implementation, Telescience
Operations, FCF Upgrades, and Acceleration Measurement Operations. The
contractor shall, except as otherwise specified herein, furnish all
personnel, facilities, materials and services necessary to support the
contract efforts.

# Applicable Documents

The nature of flight hardware integration and operation is such that
conformance to various standards and codes shall be specified if
required. Those that are applicable will be specified in each Delivery
Order. Typical standards and codes, which may be required of the
contractor, are the following:

ASTM Standards

Mil-Specifications and Standards

ANSI codes as sponsored by ASME

Department of Transportation Regulations

NASA Standards and Handbooks

The contractor shall suggest alternatives to these standards if use of
alternatives can lead to a better or less costly product that satisfies
requirements and regulations. The contractor shall also prepare and/or
utilize other applicable documents, not explicitly called out herein, as
needed to produce, test, and deploy hardware and software meeting the
requirements. The contractor shall be responsible for identifying,
acquiring, and properly using such documents. The contractor is
encouraged to submit alternative standards to the use of any military
specification or standard. The contractor shall also utilize other
applicable documents and efforts, including the performance of tests and
analyses not otherwise explicitly stated herein or in other parts of the
SOW, needed to produce the required flight hardware, software, or
support documentation. The contractor shall ascertain the totality of
the applicable documents and shall use each in accordance with the
document's purpose. In the event of conflicting requirements, the
requirements stated in the Delivery Order shall take precedence over
requirements stated in the applicable documents and/or the SOW.

## APPLICABLE REQUIREMENTS

The appropriate applicable requirements shall be identified in each
Delivery Order based on the specific needs of the experiment and its
associated carrier for integration.

## REFERENCE

The following provides a subset list of key documents for each potential
carrier or product assurance requirements that provide the basis for
flight hardware and software integration for that particular carrier.
The contractor shall obtain the latest version and all applicable
carrier integration requirements from the appropriate carrier
integrator.

### Management & Product Assurance

*Standard Assurance Requirements and Guidelines for Experiments
(SARGE):* Defines safety, reliability, and quality assurance
requirements and guidelines by carrier for developers of space
experiments within the LeRC system.

*LeRC Product Assurance Manual (PAM):* Product assurance instructions
(PAIs) employed at LeRC to address specific assurance topics.

*NASA Procedures and Guidelines \[NPG 7120.5A\]:* Establishes the
management system for processes, requirements, and responsibilities for
implementing program/project management within NASA.

*Government Surveillance Plan:* Defines NASA's approach for contract
surveillance in-sight activities for product assurance.

### Glovebox

*Microgravity Glovebox Experiment User's Manual:* Describes the Glovebox
carrier capabilities and the mechanical and electrical interfaces to
which the experiments must be designed.

### International Space Station

*Station Program Implementation Plan \[SSP 50200\]:* Defines the
implementation structure for the International Space Station Program
functions and documents the flowdown of detailed implementation.

*Pressurized Payload Interface Requirements Document \[SSP 57000\]:*
This document defines the minimum Space Station Requirements for
Pressurized Payloads and provides requirements for incorporation in the
NASA Space Station hardware procurements and technical programs.

*Program Requirements for Payload Developers \[SSP 50431\]:* This
document defines the ISS programmatic requirements, documentation and
processes to be followed by all developers of payloads and experiments
to be flown onboard the ISS.

*Pressurized Payloads Payload Accommodations Handbook \[SSP 57020\]:*
This document provides sufficient information on interfaces,
accommodations, capabilities, performance characteristics, and
constraints specific to payloads located in the U.S. Lab.

*Payload Integration Agreement Blank Book for Pressurized Payloads \[SSP
52000-PIA-PRP\]:* This document documents agreements made between the
ISSP and the payload developer concerning ISS accommodations, resources,
capabilities, and services to, from, and onboard the ISS.

### Telescience

*International Ground Segment System Specification Document \[SSP-54500,
Appendix F, Paragraph 3.7.18\]:* Provides the system requirements for
the United States ground segment including Telescience Support Center.

*POIC Capabilities Document \[SSP-50304\]:* Provides descriptive
information regarding the POIC capabilities and interfaces both local
and remote users.

*POIC to Generic User Interface Definition Document \[SSP-50305\]:*
Describes the detailed interface and file format description for access
to telemetry and command interfaces and files.

# Performance Work Statements

The following describes the general work required of the contractor upon
receipt of a Delivery Order:

## MANAGEMENT

The contractor shall provide a management function for the monitoring,
control, and reporting of the specific Delivery Order effort. The
contractor's management function shall provide to NASA reporting and
real-time insight into status based on the contractor's Performance
Measurement Plan (DID# CD-01), as well as, technical and performance
measurement of all contractor responsibilities and activities performed
under the Delivery Order. The contractor shall be responsible for the
submission of all change order proposals as required by this contract.
The contractor shall implement appropriate management systems that
prevent the improper dissemination of Principal Investigator competition
sensitive information. All contractor and subcontractor internal data,
reviews, audits, meetings, and other activities pertinent to the
execution of a Delivery Order shall be open to NASA attendance to
provide NASA insight. To facilitate NASA attendance the contractor shall
provide to NASA reasonable and timely notification of events. The
following paragraphs describe detailed requirements for performance
measurement, configuration management, property management, and review
requirements that apply to all elements of the ISS Operations Exhibit.

### Performance Measurement System

The contractor shall provide NASA with the necessary information to
implement the Government Surveillance Plan to monitor product assurance,
identify significant problems, and implement corrective action as
applicable based on the contractor's Performance Measurement Plan (DID#
CD-01). The contractor shall generate Performance Measurement Reports
(DID# CD-02) for the basic contract and each exercised option in
accordance with this plan. Additional Delivery Order specific technical
performance measurement requirements may also be identified in the
Delivery Order. The contractor shall participate for each cost plus type
Delivery Order in a monthly progress review meeting with the identified
NASA Project Manager (Delivery Order technical manager) to review cost,
schedule technical status, issues, risks, and technical interchange to
assure understanding of all Delivery Order requirements. The contractor
shall participate for each fixed price type Delivery Order in a monthly
informal Technical Information Meeting, unless otherwise modified by the
individual Delivery Order, with the identified NASA Project Manager
(Delivery Order technical manager) to review technical, schedule, and
contractual issues, risks, and provide a forum for technical interchange
to assure understanding of all Delivery Order requirements. The
contractor is not required to develop information or deliver data beyond
what is normally produced by the contractor in the day-to-day management
of the Delivery Order.

### Configuration Management

The contractor shall establish a configuration management process to
control critical hardware, software, and documentation. The specific
process to be used during integration and operations of the specific
experiment hardware shall be defined in a Configuration Management Plan
(DID# PM-04), based on the level of hardware complexity and carrier
requirements. For Delivery Orders involving FCF, the FCF Configuration
Management Plan (developed in Exhibit 1) shall be adhered to during the
operation and integration of the ground segment and flight segment
hardware and software. The contractor shall also implement an
engineering control system that shall review and approve changes to
drawings, parts lists, test procedures and quality procedures once a
baseline has been established.

### Property Management

The contractor shall maintain an inventory of all Government Furnished
property and of items purchased for Contract Delivery Orders for both,
on-site and at contractor facilities per the Property Clauses of the
contract. The contractor shall provide NASA with a current inventory
list quarterly and be subject to annual audits. During the audits, the
contractor shall verify the accuracy of the inventory listing and verify
the existence and locations of listed items. All flight hardware shall
be identified and controlled based upon the configuration management
plan which shall include a bonded storage capability to control the
tracking of and physical access to flight hardware inventory.

### Reviews

The contractor shall provide engineering, management, documentation and
planning support for reviews as required by NASA to certify the
hardware, software, and operational readiness of the system. NASA
project reviews, which apply to the Operations Exhibit, typically
include but are not limited to System Requirements Review, System
Acceptance Review, Increment Requirements Review, Increment Acceptance
Review, and an Operational Readiness Review. General requirements for
these reviews are defined in section 5.0, Milestone Reviews, or will
provided in the Delivery Order. The contractor shall also participate in
other technical reviews as required by the individual Delivery Order.

Operational Readiness Reviews shall be held at NASA Lewis Research
Center. Safety reviews shall be conducted with NASA Johnson Space Center
either at JSC or via a telecon. All other reviews may be held at the
contractor's location unless modified by the individual Delivery Order.
The contractor shall ensure that appropriate personnel attend each
review. The baseline dates for each review and any modifications to the
review requirements shall be defined in the Delivery Order to meet
unique requirements of that Delivery Order.

Review presentation packages shall be developed in accordance with
DID# D-01, unless otherwise defined in the Delivery Order. Action Items
from the reviews generated by NASA and other review participants shall
be recorded and shall require written responses for closure from the
contractor. The contractor shall evaluate the scope and content of each
review and suggest modifications, per NASA approval, to the review
requirements for more value-added reviews and/or cost reductions.

## PRODUCT ASSURANCE

The contractor will be required to plan, implement and maintain a
product assurance system to support all Delivery Orders under this
Exhibit. The Product Assurance requirements are defined in the LeRC's
Standard Assurance Requirements and Guidelines for Experiments (SARGE)
based on carrier selection. The product assurance system of the
contractor is subject to periodic review by NASA LeRC or its designated
NASA representative(s) as defined in Government's Surveillance Plan.

The contractor will be required to prepare, implement and maintain
Product Assurance Plans (DID# PA-01) and other documentation or
procedures which assure compliance with product assurance requirements.
The contractor will need to develop specific plans per the Delivery
Order to show how applicable product assurance requirements for
individual experiments will be addressed. Product Assurance Plans shall
include system safety, materials and processes, quality assurance,
problem reporting and corrective action system (PRACA), reliability and
maintainability and software product assurance.

### Quality Management

The contractor shall be certified to ISO 9001, in the process of
becoming certified or as a minimum have an established proven effective
quality program that is in accordance with FAR 42.202-3 Higher-level
Contract Quality Requirements (e.g. MIL-Q-9858). The contractor's
Quality Management system shall be capable of meeting the quality
assurance requirements in SARGE and SSP 41173, "Space Station Quality
Assurance Requirements". The Quality Management system is subject to
review as defined in the Government Surveillance Plan by NASA LeRC or
its representative.

### System Safety

The contractor shall assure the overall system safety of the design,
which minimizes or reduces safety risk to an acceptable level. The
contractor shall develop a System Safety Plan (DID# PA-02) for each
payload or experiment per the Delivery Order. The contractor shall
deliver all safety documentation required by and in accordance with
NSTS/ISS 13830 for Shuttle or ISS experiments (DID# PA-05). The
contractor shall present and support all reviews of this safety
documentation including successful closure of all resulting actions. The
contractor shall meet the requirements of NSTS 1700.7, NSTS 1700.7
Addendum, NSTS/ISS 18798, and KHB 1700.7 where applicable (e.g.,
operations at Kennedy Space Center). In addition, for ISS experiments,
the design and operational requirements of NSTS 1700.7 Addendum shall be
met. Any activity conducted at NASA LeRC facilities shall be conducted
in accordance with NASA Lewis Safety Manual and the LeRC Environmental
Programs Manual. The contractor shall impose the above mentioned
applicable safety requirements on all subcontractors and suppliers.

The contractor shall provide a Safety and Health Plan based on DID#
PA-12. This plan shall address all hazards related to the work to be
performed at LeRC and the contractor's facilities, exposures to workers
and LeRC personnel and plans to mitigate these hazards.

### Materials and Processes

The contractor shall have a materials assurance process for documenting
the Materials and Processes associated with the final design hardware
using a Materials Identification and Usage List (MIUL). Materials Usage
Agreements (DID# PA-06) shall also be submitted for all materials on the
MIUL that are not rated "A" or better per MSFC-Handbook-527. Materials
not located in MSFC-Handbook-527 shall be tested per NSTS 22648 for
Flammability Configuration or NASA-STD-6001 for all testing. The
materials assurance process must provide for certification of all parts
and materials for composition and properties as defined by the design
criteria. Materials used in applications, such as, limited life, safety,
and fracture critical shall be traceable through all critical processing
procedures up to end-item application. The contractor shall assure that
the space flight materials used meets all relevant safety requirements
and can be flight certified by NASA.

For hardware developed under the contract, the contractor shall consider
materials used in the fabrication of space flight hardware to be
selected by considering the design and operational requirements. The
properties of the candidate materials can be obtained per Mil-Handbook-5
"Metallic Materials and Elements for Aerospace Vehicle Structures" and
Mil-Handbook-17, "Polymer Matrix Composites". Material properties that
shall be considered include, but not limited to, mechanical properties,
fracture toughness, flammability, off-gas characteristics, corrosion,
stress corrosion, thermal and mechanical fatigue properties, thermal
vacuum stability, and fluid compatibility. Material codes used for
evaluation shall be obtained from MSFC-Handbook-527 "Materials Selection
List for Space Hardware Systems". For International Space Station
payloads, refer to SSP 30233 "Space Station Material and Processes" for
the material assurance requirements.

### Reliability and Maintainability

The contractor shall assure the reliability, availability and
maintainability (RAM) of the hardware that meets the definitive
requirements defined in SARGE. The contractor shall be responsible for
imposing the RAM requirements on all subcontractors and suppliers and
integrate all subcontractor and supplier RAM products into a
comprehensive compliance package as specified in SARGE.

For some Delivery orders, the contractor shall be required to perform
RAM assessments. In addition, the contractor may be required to conduct
tests to demonstrate the ability of flight experiments to survive
mission simulation conditions, be reliable/maintainable in the space
environment, and offer a 90% probability or greater for the mission to
succeed.

### Software Product Assurance

The contractor will be required to assure the management, safety, and
control of all flight-related software/firmware (including that used for
ground support or mission operations) and the software development
process (reference: NASA Software Assurance Standard NASA-STD-2201-93).
The contractor will be expected to assess the control level of the
software and its safety related requirements and level (reference
NASA-STD-8719.13A & NASA-GB-1740.13-96). Based on software control level
(reference LeRC Software Development Manual) the contractor will be
expected to develop and utilize a Software Assurance Plan (DID# PA-11)
to assure the management, safety, and control of the software products
and the software development process (e.g., configuration management,
risk management, performance, functionality, safety, reliability,
verification & validation processes and non-conformance reporting).

### Risk Management

The contractor shall have a risk management process to control critical
flight hardware, software, and documentation. Specific attention shall
be given to the control of physical and functional interfaces. The
specific process to be used by the contractor shall be defined in the
Risk Management Plan (DID# PM-02) based on the level of hardware
complexity and carrier requirements. The contractor shall provide a
status of the critical risks identified at the Technical Information
Meetings or Progress Reviews as defined in the management section.

## MISSION INTEGRATION PLANNING

Utilization and operation of scientific payloads in the ISS environment
requires new process development consistent with finite budget and
shortened schedules necessary to optimize ISS science throughput and
return. Consistent requirements and deliverables to the ISS must be
facilitated through a standard method of doing business with the ISS
Program Office. This is required to ensure that all ISS integration and
operations requirements are obtained, understood and addressed by all
ISS payloads, regardless of the ISS science carrier. The contractor
shall perform specific tasks as defined in the Delivery Order to
facilitate the strategic and tactical planning of LeRC combustion
science experiments, fluid physics experiments, and acceleration
measurement systems on the ISS along with any commercial and/or
international experiments manifested on the Fluids and Combustion
Facility. The ISS mission planning shall facilitate efforts to maximize
the science return and research opportunities on the ISS. The mission
planning activities shall apply to all LeRC microgravity investigations
for ISS pressurized and unpressurized payloads.

The contractor shall develop and maintain a planning database to assist
in multi-increment planning for each ISS Planning Period that includes
PI resource requirements and potential resource allocations from ISS.
The contractor shall support the development of ISS Mission Evaluation
Request (MER) data (DID \# R-05) and shall be responsible for
documenting this information on the MER form. These preliminary payload
requirements will include but not be limited to the (1) outfitting mass
and volume, (2) steady-state per run resources/accommodations/services
required, and (3) payload operations concept. The contractor shall
develop and maintain an integrated LeRC traffic model to document the
current manifest based on MERs submitted to ISS.

The contractor shall support LeRC in the development of an end-to-end PI
integration process that includes provisions for the Fluids and
Combustion Facility. This development shall include all ancillary
process definition that supports the overall PI integration process. The
contractor, in conjunction with FCF Increment Engineering activities,
shall provide generic PI specific documentation required for integration
into the FCF and for facilitation of information to the ISS in the form
of "blank books\" and templates. The contractor shall maintain and
upgrade this generic documentation as required. The contractor shall
also develop any tools required to facilitate the PI integration process
and to be compatible with the ISS program. For completeness, the
contractor shall obtain, document and maintain current the PI
integration processes as defined by other ISS carriers for use by
non-FCF LeRC payloads.

## FCF INCREMENT ENGINEERING AND EXECUTION

The FCF engineering responsibilities of the contractor consist of FCF
integration with the ISS, PI hardware integration into the FCF, and FCF
operations on the ISS. The FCF to ISS integration process has been
defined by the ISS Payloads Office to ensure compatibility with the ISS
vehicle accommodations, safety, and resources. The contractor shall
provide both the engineering integration (physical, analytical, and
operational) of the PI specific experiments with the Fluids and
Combustion Facility (FCF) as well as engineering integration of the FCF
& PI with the ISS. This integration shall provide for continuous
operation of the FCF on an increment or multi-increment basis depending
on the grouping of operations activities defined in the Delivery Order.
The contractor shall work with ISS Program and the PI specific
experiment developers to develop and document increment specific
requirements. These requirements shall be certified through an Increment
Requirements Review.

The contractor shall perform the integration activities for FCF and PI
specific experiments such as analytical compatibility analysis, FCF/PI
checkout and verification, ISS/FCF checkout and verification, mission
planning, training, and simulations. The contractor shall perform
structural, thermal, power, operations, command & data management,
safety and diagnostics integration and engineering functions. In
addition, the contractor shall manage the PI specific and ISS data
products and documentation requirements, perform transportation options
(mass/volume) analysis and recommendations on FCF manifesting. The
contractor shall verify that all requirements for a specific increment
have been met through the successful completion of an Increment
Acceptance Review. Specific work elements for each integration function
and the FCF increment execution activities are defined in the following
sections:

### PI to FCF Integration

The contractor shall work with the PI hardware development teams in
developing PI specific hardware and software to be used within the FCF
system. The contractor shall develop with the PI specific experiment
developer an Integration Agreement (IA) (DID# R-03; Note: FCF IA \"blank
book\" developed under Exhibit 1) on the responsibilities, tasks,
technical requirements, and resource requirements that directly relate
to the assignment and integration of that payload into the FCF on the
ISS as defined in the Delivery Order. The contractor shall develop with
the PI specific experiment developer a specific Interface Control
Document (ICD) with FCF (similar to DID #R-02; Note: FCF ICD \"blank
book\" developed under Exhibit 1) for that payload that defines the
physical and functional interface requirements. The contractor shall
provide a liaison to the PI specific hardware teams to facilitate the
integration process. The contractor shall provide an updated FCF
Accommodations Handbook (DID# D-05) to the users in Phase A/B and will
facilitate the development of the ICD, Integration Agreements (IA), and
Payload Verification Plan (PVP) (DID# V-01), with the specific user in
Phase C/D based on generic "blank book" templates. The contractor shall
also develop with the PI specific experiment developer an integration
schedule including data set and engineering product deliverables for the
PI specific experiment based on a generic FCF integration template. The
contractor shall book manage all PI specific to FCF integration
documentation developed from the \"blank books\" and templates for a
specific PI experiment and/or increment.

### FCF to ISS Integration

The contractor shall integrate all relevant inputs from the PI hardware
development teams and maintain and update all required documents and
data deliverables for the ISS program on an increment basis per the
Delivery Order. The contractor shall maintain and update the FCF Payload
Integration Agreement (PIA) including the increment specific Addendum C
and the datasets for all PI specific experiment information along with
FCF information. The PIA is the FCF and ISS agreement on the
responsibilities, tasks, and requirements that directly relate to the
assignment and integration of the facility into the ISS. The contractor
shall also maintain and update the FCF Interface Control Documents
(ICDs) originally developed under Exhibit 1. The ICDs are facility
specific interface documents between the FCF and ISS based on the ISS
Pressurized Payload Interface Requirements Document (IRD) and the ICD
templates. The contractor shall maintain and update the FCF Payload
Verification Plan including all relevant PI specific experiment
information. The contractor shall maintain and update FCF Flight and
Ground Safety Packages in accordance with the JSC Payload Safety Review
Panel procedures. This includes collection of safety package inputs from
the PI specific experiments, checking for completeness, developing a
safety package, and assisting the PI Development team in presenting to
the ISS Safety Panel and other Safety Panels as required. The contractor
shall be responsible for providing engineering products required by ISS
including PI specific experiment information in accordance with the
integration schedule developed and negotiated with ISS.

### FCF Verification

The contractor shall develop and maintain the FCF test equipment for
both early development testing and final test and verification of the
flight hardware. The contractor shall provide sufficient access of FCF
hardware and software to PI development teams during the PI
hardware/software development cycle, to ensure successful operation of
the final integrated PI-FCF system. The contractor shall provide
sufficient personnel support, training, and training materials on the
use of FCF hardware to the PI teams.

The contractor shall be responsible for all interface and verification
tests between FCF and PI specific hardware. The contractor shall be
responsible for scheduling, installation, check-out and verification of
the PI experiment hardware and software into the FCF Ground Integration
Unit (GIU) which will be located in NASA LeRC's Building 333 (high-bay,
clean-room). The contractor shall provide the necessary support for
proper integration of the PI Hardware into the FCF GIU and the
performance of integrated FCF/PI verification and validation tests based
on the PI payload developers Verification Plan that includes FCF system
testing, mission simulations, and ground/flight end-to-end testing. The
contractor shall also be responsible for supporting the installation and
initial checkout of the PI experiment hardware and software into the FCF
Experiment Development Unit (EDU) which will also be located in NASA
LeRC's Building 333.

### FCF Training

The contractor shall develop and present, in conjunction with specific
users, all integrated (FCF w/ PI Hardware) training materials for the
use of the FCF, including the FCF Payload Training Center Unit (PTCU)
per the Delivery Order. The contractor shall support the installation of
the experiment\'s training unit in the FCF Payload Training Center (PTC)
at the Johnson Space Center. The contractor shall work with the PI
experiment teams, the ISS crew, and the ISS payload training
organization to develop the integrated requirements for crew training.
These requirements will serve as the basis for the design and
development for the experiment specific training materials. The
contractor shall implement the training requirements for the PTC
training sessions, for the computer-based training, for part-task
trainers, and for on-orbit training. The contractor shall provide
experiment hardware and software training for the PI(s) and associated
team, the Project Scientist, and Payload Specialist(s) in the
operational/functional limitations and capabilities of the FCF for
proper decision making and in the development of operational procedures.

### Increment Execution

The contractor shall be responsible for the real-time FCF operations,
along with any supporting activities in conjunction with ISS increment
operations per the Delivery Order. The FCF mission operations shall
include coordinating real-time operational requirements, acquiring and
processing real-time data according to mission requirements, supporting
the correlation of scientific data with FCF and ISS mission events,
preparing FCF performance summary reports, maintaining FCF performance
information databases, and participating in working group interchanges.

The contractor shall be responsible for the planning and scheduling of
all FCF on-orbit operations in coordination with the PI hardware
development teams. This shall include developing and consolidating PI
Specific and FCF mission timelines and maintaining the timelines,
obtaining or requesting all necessary ground and on-orbit resources, and
implementing the planned FCF/experiment operations. The contractor shall
also support post-launch PI hardware checkout on the ISS that includes
payload integration into FCF, activation and calibration, system
characterization, and verification of the experiment operational
procedures.

The contractor shall provide trained staff for console operations
located in the LeRC Telescience Support Center. Appropriate personnel
shall be on console when the FCF is active or other planned operations
are being performed. The contractor shall be prepared to respond to crew
and ground team communications, and off-nominal situations. The
contractor shall develop and follow standard procedures to resolve
on-orbit FCF problems or anomalies.

## SYSTEM/SUSTAINING ENGINEERING

The contractor shall provide comprehensive system/sustaining engineering
for long duration mission operations (FCF, acceleration measurement
systems, etc.) and associated ground infrastructure (TSC, GIU, etc.) as
defined in the Delivery Order. The engineering effort shall include both
the flight and ground segments of the facility or payloads and their
operations. The contractor shall be responsible for the sustaining
engineering required ensuring continuous successful operation of the
integrated ground and flight segments. This includes conducting
appropriate system analyses, data evaluations, appropriate testing,
maintenance, and modifications required of the ground and flight
hardware and software necessary to sustain on-going operations.

Specifically, the contractor shall implement the Integrated Logistics
and Maintenance Support Plan (DID #OP-01) for that facility or payload
to maintain the full operational capability of the flight and ground
system. The contractor is responsible for conducting appropriate
logistics support, reliability and maintenance analyses in order to
maintain the hardware and software in proper operational status. These
efforts shall incorporate, at a minimum: the tracking of limited life
items for safety and/or mission assurance reasons, the reporting of
on-orbit system performance, and the development of trend analyses using
on-orbit systems reports and other available data. The maintainability
analyses shall include, at a minimum, mean-time-between-failure (MTBF)
analysis of Orbital Replacement Units (ORU) and critical ground system
components to determine system maintenance schedules and the associated
maintenance documentation required. The contractor shall be responsible
for the repair of flight ORU's and ground system components, when
specified in the Delivery Order. The contractor will also be responsible
for the physical packaging, handling, storage, and transportation of all
flight and non-flight maintenance and ORU items.

The contractor is responsible for the on-going maintenance support of
all ground support hardware and software identified in the Delivery
Order. For FCF this would include items such as the FCF component
simulators, Ground Integration Units (GIU), Experiment Development Units
(EDU), and FCF Payload Training Center Unit (PTCU). This FCF equipment
will be used for purposes including, but not limited to PI integration
testing, science data acquisition, training of the crew, PI science and
hardware teams, as well as mission simulation support.

The contractor shall be responsible for providing software support for
the development or modification of ground and flight software, which may
be developed or modified to correct software faults, work around
hardware failures, or to provide additional system capabilities.
Software maintenance shall include keeping commercial software licenses
current.

## TSC DEVELOPMENT & IMPLEMENTATION

The contractor shall develop and implement a ground system for
telescience operations which meets the ISS programmatic design and
verification requirements defined in the International Ground Segment
Specification (IGSS) document (SSP-54500). Design and operational
constraints with which the ground system must comply are documented in
the IGSS, the POIC to Generic User Interface Definition Document
(SSP-50305), and the POIC Capabilities Document (SSP-50304). The NASA
LeRC telecommunications ground system shall be capable of supporting all
NASA LeRC space operations activities defined by individual Delivery
Orders. The contractor shall be responsible for the overall management
of the TSC project, requirements development, capability development,
and test and verification of the system. The Telescience Support Center,
as the central LeRC communications facility for space command and
communications, shall be located at NASA Lewis Research Center in
Building 333. In addition, the ground system shall include remote site
locations for science operations at the location selected by the
Principal Investigator for his/her science investigation. The TSC
development and implementation shall maximize the use of commercially
available hardware and software. Per the Memorandum of Understanding
between NASA MSFC and NASA LeRC, the contractor shall incorporate the
Telescience Resource Kit (TReK) and the Remote Copy of the Enhanced HOSC
System (EHS) into the design and development of the TSC.

## TELESCIENCE OPERATIONS

The contractor shall perform ground operations (defined by the
individual Delivery Orders) from the Telescience Support Center, located
in Building 333, at NASA LeRC, and from remote sites located where the
Principal Investigator, or other user, is located. The contractor shall
provide operational support systems or functions required to plan,
monitor and control on-orbit payloads; perform TSC facility operations;
coordinate real-time FCF & experiment commanding requirements; perform
payload timeline planning; and simulate on-orbit operations for ground
verification and ground operations training. The contractor shall
operate & maintain the TSC facility and support systems. The contractor
shall work with payload developers to develop and document
increment-specific telescience requirements. The contractor shall ensure
the storage, retrieval, and archival of telemetry data, maintain
performance records, and develop TSC performance reports and trend
analysis information. The contractor shall be responsible for the
physical and automated information systems security for the TSC
facility. Any TSC systems that are actively supporting customer
operations within the facility shall require TSC operations staff per
customer operating profiles.

The contractor shall provide the Principal Investigators with a remote
capability to control and monitor the operations of their on-orbit
payload and communicate with the LeRC TSC and other ground systems. The
contractor shall provide hardware and software support systems for all
phases of mission operations support. The contractor shall support
set-up and shutdown of remote site systems.

The contractor shall develop and offer training courses and conduct
simulations to demonstrate the use of Telescience Support Center
capabilities and assure the proficiency of console operations either at
the TSC or at a remote site. The contractor shall provide personnel for
all phases of operations as required that includes appropriate trained
personnel for on-console operations during all mission simulations and
real time operations. The contractor shall certify the Operational
Readiness of the system and operators.

## ACCELERATION MEASUREMENT OPERATIONS

The contractor shall be responsible for the real-time operations of the
microgravity acceleration measurement hardware and any supporting
activities in conjunction with ISS and STS operations per the Delivery
Order. The contractor shall provide mission operations support for
microgravity acceleration measurement including: coordinating real-time
operational requirements; acquiring, processing, and distributing to
PI's real-time acceleration data according to mission requirements;
supporting the correlation of scientific data with acceleration data and
ISS mission events; preparing acceleration hardware performance summary
reports, maintaining acceleration measurement hardware performance
information databases, and participating in working group interchanges.

The contractor shall be responsible for the planning and scheduling of
all microgravity acceleration measurement hardware on-orbit operations,
develop and maintain mission timelines, obtain or request all necessary
ground and on-orbit resources; and implement the planned operations. The
contractor shall provide trained staff for console operations located in
the LeRC Telescience Support Center. Appropriate monitoring shall be
performed when acceleration measurement hardware is active or other
planned operations are being performed. The contractor shall be prepared
to respond to crew and ground team communications, and off-nominal
situations. The contractor shall develop and follow standard procedures
to resolve on-orbit problems or anomalies.

## FCF UPGRADES

The contractor shall produce upgrades to FCF subsystem hardware (I/O
Processor, Image Processing and Storage Units, Electrical Power Control
Unit, Diagnostics, etc.) according to the specifications in the Delivery
Order. The contractor shall meet all design and development requirements
as outlined in the Delivery Order, as well as all integration
documentation outlined in section 4.4 above. Deliverables may include
standard design review materials, flight unit hardware and software,
ground units to be included in the FCF Ground Integration Unit and other
FCF simulators, appropriate flight spares, integration and verification
plans. As part of the integration of new FCF hardware the contractor
shall update all appropriate FCF documentation including the Payload
Accommodations Handbooks, the Interface Control Documents, all FCF
Configuration Documents, etc. as defined in the Delivery Order.

# Milestone Reviews

Successful completion of each review includes the following:

-   Delivery of a review presentation package no later than two (2)
    weeks prior to the review, (unless waived by the Delivery Order)

-   Delivery of supporting documents no later than six (6) weeks prior
    to the review, unless otherwise indicated in the Delivery Order

-   Delivery of all items listed below for each review, plus any
    additional items identified in the Delivery Order

-   Documented closure of any actions submitted at prior reviews

-   Review board determination of adequacy of all deliverables
    (documented in the review board's assessment report)

The review board's assessment report shall be issued within 4 weeks of
the review. Individual documents shall be reviewed by NASA and approved,
approved with modification, or disapproved. Any documents disapproved by
NASA will require re-submittal and re-review until approved by NASA.

The descriptions of the major milestone reviews anticipated for ISS and
TSC operations activities are provided in the following sections.

## Increment Requirements Review 

The requirements and implementation plan will be reviewed for
completeness and the ability to meet the science objectives for the
designated increment or increments. The purpose of the IRR is to:

-   Identify and document programmatic and customer requirements

-   Establish engineering design requirements in compliance with
    science/research requirements

-   Ensure implementation plan is consistent with the requirements

-   Identify and document external requirements

-   Define the top level implementation approach

-   Obtain NASA approval on the Increment Operations Plan (DID# OP-03)
    and review the methodology used to develop the cost estimate, and
    costs by work breakdown structure element.

-   Submit for review and NASA approval the project plan which includes
    the management approach, work breakdown structure, configuration
    management approach, hardware/software development and test
    philosophy, schedules, and costs. Review the methodology used to
    develop the cost estimate, and costs by work breakdown structure
    element.

    **IRR Minimum Deliverables required:**

-   Increment Project Plan

-   Increment Operations Plan

-   Engineering Compliance Matrix showing compliance with ISS
    requirements

-   Draft Verification Plan (ISS and PI Specific)

-   Preliminary Payload Integration Agreement (PIA) Main Volume (FCF to
    ISS)

-   Preliminary PIA Addendum(s) (FCF to ISS)

-   Preliminary ICD (PI to FCF)

-   Preliminary Integration Agreement (IA) (PI to FCF)

-   Training Plan

-   Identification of and plan for integrating FCF replacement/upgrade
    hardware and/or software

## Increment Acceptance Review 

The Increment Acceptance Review (IAR) is a technical review of the FCF
system and documentation. The IAR will demonstrate that the FCF system
including PI equipment, FCF upgrades and maintenance items will meet all
of the increment(s) specific requirements. In addition, the IAR will
confirm that the FCF capabilities are comprehensive, systematic,
efficient and represent acceptable risk. Completion of this review
baselines the increment configuration and documentation and provides
sufficient detail to support final verification testing of PI experiment
equipment.

The purpose of the IAR is to:

-   Validate the configuration of the FCF system against the
    requirements

-   Ensure that all interface requirements have been achieved

-   Document test and verification plans and test readiness of systems

-   Document training plan and schedule

-   Document CoFR plan and schedule

-   Review and approve the plan for operations and maintenance of the
    facility

-   Ensure compliance with the contractor\'s Increment Operations Plan

-   Document closure of PI specific experiment verifications

-   Evaluate changes to increment complement

-   Provide status of open work and evaluate ability for completion

**IAR Minimum Deliverables required:**

-   Requirements Compliance Matrix

-   PI Specific Verification Plan that includes Final Interface
    Verification Test Plans

-   Final Interface Documentation (ICDs ,IA, Data Sets, etc.)

-   CoFR Plan

-   Integrated Logistics Support Plan

-   PI Specific Experiment Verification Tracking Log

-   Phase III Safety Package

-   Status of Limited Life Components

-   Launch Site Operations and Test Procedures

-   Increment Specific Waivers/Deviations and Verification or Basis of
    approval

-   IRR RFA Close Out

-   PI Specific Experiment Integration On-Orbit C/O Plan

## Certification of Flight Readiness (CoFR)

The contractor shall certify the FCF and all associated H/W and S/W for
a specific increment(s) for flight in accordance with SSP52054 - ISSP
Payloads Certification of Flight Readiness Implementation Plan -
Generic.

## TSC System Requirements Review 

The Project Plan, system requirements, customer requirements,
operational concepts, and implementation plan will be reviewed for
completeness and ability to meet the program objectives for the
designated increment or increments. The TSC System Requirements Review
(TSRR) is required for each major development phase. Individual payload
requirements will be compiled for each increment and reviewed as part of
the TSRR or as a lower level review.

The purpose of the TSRR is to:

-   Ensure that programmatic and customer requirements are identified
    and documented

-   Ensure that the implementation plan is consistent with the
    requirements

-   Identify external requirements

-   Describe the implementation approach and operational scenarios

-   Submit for review and NASA approval the project plan which includes
    the management approach, work breakdown structure, configuration
    management approach, hardware/software development and test
    philosophy, schedules, and costs. Review the methodology used to
    develop the cost estimate, and costs by work breakdown structure
    element.

-   Document and submit for review the technical, schedule, and cost
    risks of the proposed implementation.

    TSRR Minimum Deliverables required:

-   Telescience Support Center System Requirements Document, per DID
    #R-06

-   TSC Implementation Plan, per DID# OP-07

-   TSC Operations Concept Document, per DID# OP-06

-   TSC Project Plan, per DID# PM-01

-   TSC Configuration Management Plan, per DID# PM-04

-   Increment Specific Customer Requirements, per payload dataset
    submittals

-   TSC Increment Specific Integrated Payload Datasets (draft), per DID#
    OP-09

-   Preliminary space and resource allocation assessment

The CDRLs referenced should be used as a guideline for developing the
required deliverables. Tailoring and annotation of the CDRL to further
define the content of an individual document can be accomplished by
mutual agreement of the contractor and government leads in this area.

## TSC System Acceptance Review 

The TSC System Acceptance Review (TSAR) is a technical review of the TSC
system architecture and documentation. The TSAR will demonstrate that
the system constructed for use will meet all of the requirements. In
addition, the TSAR will confirm that the capabilities are comprehensive,
systematic, efficient, and represent acceptable risk. Completion of this
review baselines the design and documentation and provides sufficient
detail to proceed with integration and testing of subsystems. The TSAR
is required for each major TSC development phase.

The purpose of the TSAR is to:

-   Validate the design of the system architecture against the system
    requirements

-   Assure that individual customer ground operational requirements are
    accommodated

-   Ensure that all interface requirements have been met

-   Document test and verification plans and test readiness of systems

-   Document training plan and schedule

-   Document ground support personnel certification plans and schedule

-   Assess security of information systems, system interfaces, the
    facility, and remote sites

-   Review and approve the plan for operations and maintenance of the
    facility

-   Ensure compliance with the Contractor Project Plan

-   Document nominal and off-nominal operations procedures

**TSAR Minimum Deliverables required:**

-   TSC Increment Specific Integrated Payload Datasets, per DID# OP-09

-   System Design Documentation, per DID# D-08

-   System Drawings, per DID# D-04

-   Requirements Compliance Matrix, per DID# D-07

-   Interface Control Document, per DID# R-02

-   Assembly, Integration & Test Plan, per DID# V-12

-   TSC Training & Certification Plan, per DID# V-14

-   Performance Verification Plan, per DID# V-05

-   Individual Item Performance Verification Plan, per DID# V-06

-   TSC Training Manual, per DID# OP-08

-   Training Products, per Training Manual

-   TSC Security Plan, per DID# OP-10

-   Integrated Logistics Support Plan, per DID# OP-01

-   TSC Operator's Manual (draft), per DID# OP-02

-   Space and resource allocation assignments

The CDRLs referenced should be used as a guideline for developing the
required deliverables. Tailoring and annotation of the CDRL to further
define the content of an individual document can be accomplished by
mutual agreement of the contractor and government leads in this area.

## TSC Operational Readiness Review

The TSC Operational Readiness Review (TORR) provides the final
verification that the operational elements of the facility and
supporting elements are ready to be certified for each increment or
mission operations. The TORR will be completed as a two step review
process as required to meet Certificate of Flight Readiness #1 and
Certificate of Flight Readiness #2 requirements. The first step will be
held as an internal TSC Operations Readiness Review #1 (TORR#1) at
launch date minus 4 months for each increment. The second step will
finalize the operational readiness of the facility. The TORR#2 shall be
required for each increment two-months prior to the start of the
increment.

The purpose of the TORR #1 is to:

-   Verify the operational status of all TSC systems and document
    resolution of any problems and/or non-conformances

-   Verify the operational status of all TSC external interfaces and
    document resolution of any problems and/or non-conformances

-   Verify the operational status of remote site capabilities and
    document resolution of any problems and/or non-conformances

-   Provide TSC endorsements required for the COFR #1 process defined in
    SSP52054 - ISSP Payloads Certification of Flight Readiness
    Implementation Plan

The purpose of the TORR #2 is to:

-   Ensure that all systems and ground support personnel meet the ISSPO
    Certification Requirements

-   Baseline increment specific requirements and accommodations for
    individual payload operations

-   Document that all systems have successfully completed test and
    verification

-   Ensure that all systems are ready for real time operations

-   Proceed with mission operations with minimal, known risks

-   Freeze the configuration of the facility for increment operations.

-   Provide TSC endorsements required for the COFR #2 process defined in
    SSP52054 - ISSP Payloads Certification of Flight Readiness
    Implementation Plan

TORR #1 Minimum Deliverables required:

-   Performance Verification Reports, per DID# V-07

-   Individual Item Performance Verification Report, per DID V-08

TORR#2 Minimum Deliverables required:

-   Ground support personnel certification documentation

-   Certification Matrix, per the TSC Certification Plan (DID \# V-14)

-   TSC Operator's Manual, per DID# OP-02

-   Increment specific space and resource allocations

The CDRLs referenced should be used as a guideline for developing the
required deliverables. Tailoring and annotation of the CDRL to further
define the content of an individual document can be accomplished by
mutual agreement of the contractor and government leads in this area.