**Exhibit 3**

**IDIQ Development of PI Specific Experiments, Instruments and
Diagnostics**

**Statement of Work**

# Introduction

The National Aeronautics and Space Administration (NASA) Microgravity
Science program advocates and coordinates an interdisciplinary research
community to conduct specified research and to disseminate the results
of that research. Research selected for flight definition is assigned to
a carrier or a research facility best suited for that experiment (Space
Shuttle, Sounding Rocket, International Space Station, Glovebox, etc.).
NASA has a requirement for the development and operation of these
individual flight experiments to perform microgravity investigations in
combustion and fluid science research.

This statement of work (SOW) defines the contractor's efforts required
to provide performance-based activities in the design, development,
fabrication, assembly, test, delivery, and operation of Microgravity
Science payloads. The contractor will perform the tasks for the
Microgravity Science program managed by the NASA Lewis Research Center
(LeRC). Particular requirements and tailoring of this SOW shall be
defined in the Delivery Order issued for each specific Principal
Investigator's mission. The statement of work is structured by
historical NASA development phases (NHB 7120.5), see Figure 1, with the
anticipation that the Delivery Order requirements and end-item
deliverables will be defined within that life-cycle phase. The
development approach shall be tailored as appropriate to most
effectively meet the requirements of the experiment.

![](media/image1.wmf)Figure 1 - Typical Project Management Process

(Note: Phase A activities are nominally performed by the Government)

# Scope

The contract encompasses the design, development, testing, engineering,
production, delivery, and operations of Microgravity Science flight
payloads. The flight experiments are designed to accommodate basic
research, commercial applications, and studies of phenomena in fluid
physics, combustion science, acceleration measurements, and other
microgravity investigations. The contractor shall, except as otherwise
specified herein, furnish all personnel, facilities, materials and
services necessary to support the contract efforts. The contractor shall
work from Delivery Orders describing required deliverables and
specifications required to satisfactorily complete each order.

# Applicable Documents

The nature of flight hardware development 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.

## REFERENCE

The following provides a subset list of key documents for each potential
carrier or product assurance that provide the basis for flight hardware
and software development for that particular carrier. The contractor
shall obtain the latest version and all applicable carrier 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.

### Get Away Special (GAS)

*Get Away Special (GAS) Small Self-Contained Payloads Experimenter
Handbook:* Handbook includes all interface requirements, all carrier
capabilities, selected materials requirements and recommendations,
selected safety requirements, and selected test and verification
requirements.

### Hitchhiker (HH)

*Customer Accommodations and Requirements Specification (CARS)
\[HHG-730-1503-07\]:* Includes all interface requirements, all carrier
capabilities, selected materials requirements and recommendations,
selected safety requirements, and selected test and verification
requirements.

### Sounding Rocket

*Sounding Rocket User's Handbook:* Describes sounding rocket
capabilities, hardware design considerations, payload development
process, integration, testing, safety, etc.

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

### Spacehab/STS

*Spacehab User's Handbook \[MDC-SH-0002\]:* Includes all carrier
capabilities, selected materials requirements and recommendations,
selected safety requirements, and selected test and verification
requirements.

*Spacehab Experiment Requirement Questionnaire \[MDC-94-W5718\]:*
Establishes the format and content of information about experimenter
requirements to be used during the manifesting process and subsequent
formal definition process.

*Spacehab Payload Processing Facility Experimenter's Handbook
\[MDC-94-W5719A\]:* Defines the generic capabilities of the Spacehab
Payload Processing Facility (SPPF) for the experiment user.

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

*Space Station Program Requirements for Payloads \[SSP 50431\]:* This
document provides a consolidation of all International Space Station
Program (ISSP) programmatic requirements, documentation and processes to
be used by all ISSP funded and barter agreement Payload Developers (PDs)
and processors.

# Performance Work Statements

The following describes the functional performance work required of the
contractor upon receipt of a Delivery Order necessary for the successful
and on-time implementation to meet the mission-specific Delivery Order
requirements.

## 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 (DID# PM-05) 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 Exhibit 3.

### Performance Measurement

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, 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, 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 development 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. 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. Any modifications to requirements or deviations shall be in
accordance with DID# PM-05.

### 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 NASA design reviews required by NASA Headquarters,
other NASA field centers and the program offices to certify hardware and
software maturity readiness. NASA design reviews typically include but
are not limited to the Science Concept Review (SCR), Requirements
Definition Review (RDR), Preliminary Design Review (PDR), Critical
Design Review (CDR), Verification and Test Review (VTR), Pre-Ship Review
(PSR), and Flight Readiness Review (FRR) as defined in section 5.0
Milestone Reviews. The contractor shall also participate in other
technical reviews based on the individual Delivery Order, such as
Verification and Safety Reviews.

The SCR, RDR, and PSR shall be held at NASA's Lewis Research Center and
the Safety reviews shall be held at NASA Johnson Space Center, all other
reviews shall be held at the contractor's location or 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 mission requirements.

Review presentation packages shall be developed in accordance with
DID# D-01, unless otherwise defined in the Delivery Order. Action Items
from the reviews shall be generated by NASA 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 tasks under the Contract. 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 MRDOC Surveillance Plan by NASA LeRC or its
representative.

### System Safety

The contractor shall assure the overall system safety of the design that
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
support all reviews of this safety documentation. 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. The
contractor shall meet the requirements of GHB 1771.1, Range Safety, GMI
1771.1, Range Safety Policies & Criteria for GSFC/Wallops Flight
Facility and White Sands Users Handbook for sounding rocket payloads.
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), see DID# PA-06.
Materials Usage Agreements 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 NASA 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 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-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
LeR-P-2.10.2 and the 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), per 7120.5A Section 4.3, 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.

## EXPERIMENT DEFINITION

The Government shall nominally provide initial system level experiment
concept(s) for the Science Concept Review (SCR) to meet science
requirements as defined by the Principal Investigator (PI), identify any
engineering feasibility issues and perform key tests that demonstrate
the proposed science requirements can be satisfied. The Government will
support the PI's identification and refinement of the science
requirements by designing and developing bench-top hardware
(breadboards) and rigs for laboratory and/or low-gravity ground-based
testing. The outcome of the Experiment Definition phase is to establish,
through science peer-review, that the scope and feasibility of the
experiment have been adequately addressed to propose a definitive flight
experiment. The completion of this phase occurs upon peer-review
approval at the Science Concept Review. Typical activities performed
during the Experiment Definition phase are described in the following
sections (provided for information purposes only):

### Requirements Definition

Top-level engineering requirements that address the Principal
Investigator's science requirements are defined. The NASA hardware
development team works with the experiment\'s Project Scientist through
a structured process to interpret the PI's experiment needs and
determine the top-level technical requirements.

### Concept Feasibility

The system design and mission analysis are conducted to produce feasible
concept(s) that address the science requirements and to evaluate
potential mission carrier options. The concepts identify possible
subsystems that address the science objectives and the key high-risk
development areas. The mission analysis may include: technology
alternatives, operations scenarios, risks identification, and
infrastructure evaluations.

Engineering feasibility issues are identified based on the science
requirements to determine a resolution approach and perform initial
breadboard level testing as required. Engineering feasibility issues
include: fundamental capabilities required to meet science objectives,
reduce life-cycle costs, assess technical viability based on current
industry capabilities, and assess the diagnostic methods utilized in the
PI's research.

### Project Formulation

The Government will formulate a preliminary engineering plan for
development of the experiment concept. Schedule and budget information
is developed to meet the requirements of the Science Concept Review with
a rough order of magnitude estimate for the overall budget and schedule
that includes key milestones and an overall implementation approach to
flight.

## REQUIREMENTS DEFINITION

The contractor shall thoroughly define project requirements and provide
sufficient detailed definition of the project technical, management,
budget, and institutional support plans needed to enable a firm NASA
commitment to accomplish the science objectives on schedule and within
budget. The outcome of the Experiment Definition phase is to establish,
through science and engineering peer-review, that the engineering
concept of the experiment will be sufficient to meet the detailed
science requirements in the Principal Investigator's Science
Requirements Document (SRD), the engineering requirements derived from
the science requirements have been determined, major feasibility issues
have been resolved or feasibility resolution plans established, and the
project plan and initial costs have been developed to enable NASA to
assess the readiness of the project to enter the preliminary design
phase. The performance standard for successful completion of this work
element occurs upon peer-review approval to NASA at a Requirements
Definition Review (RDR). In the performance of Experiment Definition
efforts, the contractor shall accomplish the following:

### System Requirements Analysis

The contractor shall define the fundamental system requirements per DID#
R-01 (Draft) based on science, potential carrier, operations, and safety
and quality requirements. A requirement compliance matrix based on these
system requirements shall also be developed for the Requirements
Definition Review that shows compatibility between engineering
implementation and the science requirements.

### Concept Feasibility

The contractor shall determine the overall feasibility of the candidate
experiment concept(s) that consider affordability, technology readiness,
operations, infrastructure, content, risk, and potential procurement
strategies. The technology readiness assessment shall evaluate the
fundamental technology requirements of the experiment concept to ensure
that specified science objectives will be met, project cost or risk will
be minimized and identifies where significant technology gaps exist,
such that it would be difficult for a concept to be realized.

### Breadboards

The contractor shall minimize development risk based on identified
engineering feasibility issues through the design and development of
breadboards, as appropriate, to evaluate functional performance.
Breadboard testing should be focused on determining whether the
engineering experiment concept will meet the science requirements
defined in the PI's SRD. Any concept limitations should be identified
and alternate concepts and technologies should be tested in areas where
meeting a science requirement may be challenging. This may require the
use of ground-based low-g test facilities (drop towers, KC-135, etc.),
the contractor shall identify and schedule with NASA the use of such
facilities. The results of the breadboard testing shall be made
available for NASA review. Any requirement for additional hardware
breadboarding of high risk subsystem function(s) or special equipment
that are necessary to be performed during the Preliminary Design phase
shall be identified and documented in the RDR presentation package (DID#
D-01).

### Integrated Concept

The contractor shall develop an initial integrated concept of the
selected experiment that includes the design constraints and interfaces
of the recommended carrier (ISS, sounding rocket, NSTS, etc.). This
initial concept shall provide sufficient detail to show the overall
feasibility, compliance to the SRD requirements, carrier integration
compatibility, and subsystem level packaging. The integrated concept may
require the use of the carriers ground integration unit or simulators to
determine overall feasibility; this need shall be identified to NASA for
proper availability for testing. The selected experimental concept shall
be documented in a draft Baseline Concept Description (DID# D-03)
document and presented at the RDR.

### Project Planning

The contractor shall formulate an overall engineering plan which defines
and details the approach, schedule, hardware classification, and
resource requirements, so that programmatic commitments can be made
based on a recommended flight carrier. The contractor shall also provide
a life cycle costing analysis necessary to produce the selected concept.
Schedule and budget information shall be developed and presented as part
of the RDR review package that meets the requirements of the
Requirements Definition Review with a rough order of magnitude estimate
for the life cycle costs and overall schedule that includes key
milestones and an implementation approach to flight.

## PRELIMINARY DESIGN

The contractor shall develop a preliminary design that can demonstrate
at the system, subsystem and component level compliance to the system
and science requirements with acceptable risk. The outcome of the
Preliminary Design phase is to establish, through independent
engineering-review, that the proposed engineering design solution for
the experiment is expected to meet the performance and functional
requirements at the configuration item level, the design is verifiable
and does not pose major problems which may cause schedule delays or cost
overruns, all interfaces and verification methodologies have been
identified, and all system requirements have been allocated to the
subsystem and component level and the flow down is adequate to verify
system performance. The design activities may include the design of
diagnostic packages (illumination, imaging, optical diagnostic
techniques, microscopy, interferometry, etc.), avionics packages
(command, control, data handling, image processors, communication,
etc.), power distribution packages (monitoring, switching, power
isolation, conditioning, V/A regulation, EMI suppression, electrical
fault protection, etc.), instrumentation (temperature sensors, pressure
sensors, flow rate sensors, thermal imaging, leak detection, etc.),
structural hardware, associated interfaces, environmental control
(collection, transportation, and rejection of thermal, precision
temperature and flow control), gas distribution (storage, mixing,
valving, composition , containment, etc.), capture and containment of
contamination sources, design of experiment test cells, and the design
of an integrated system. The performance standard for successful
completion of this work element occurs upon engineering-review approval
by NASA at a Preliminary Design Review (PDR). In the performance of
Preliminary Design efforts, the contractor shall accomplish the
following:

### Requirements

The contractor shall develop preliminary design-to specifications (DID#
R-01) that incorporates the PI experiment requirements, carrier
requirements and determine all interface requirements, including
software interfaces, shall be documented. Also, if required by the
Delivery Order, a preliminary Interface Control Document (DID# R-02)
shall be developed with the carrier based on the appropriate carrier
integration template. All experiment functional requirements shall be
allocated to either hardware or software with a flow-down of
requirements to the subsystems and components, if applicable. The
estimated resources required of the carrier shall also be determined
that includes resource allocations and appropriate margins. Compliance
with experiment requirements shall be determined based on the
preliminary design and documented in a Requirements Compliance Matrix
(DID# D-07).

### Design

The contractor shall develop a preliminary hardware and software design
that complies with the experiment's system requirements based on the
science, carrier, interface, and product assurance requirements. These
requirements are defined in the specific project Science Requirements
Document and System Requirements Document or as identified in the
Delivery Order. The preliminary design shall establish the overall
system architecture, identify all the external interfaces, develop an
operations concept, develop experiment layouts, detailed drawings, mass
properties, interface schematics, and preliminary materials & parts
lists. The contractor shall perform engineering analyses (thermal,
dynamic, vibration, optics, etc.) as appropriate in the design of the
mechanical, electrical, and system hardware.

The contractor shall submit and present design progress for review at
various times and locations as specified in the Delivery Order. The
contractor shall develop a Preliminary Design Review package (DID# D-01)
that shows a mature understanding of the mission objectives and
requirements (Packaging, Structural, Thermal, Testing of components,
electrical EMI) and preliminary drawings according to DID# D-04. The
preliminary design may also be documented in a Baseline Concept
Descripiton document (DID# D-03).

The contractor shall develop a software design and initial programming
in parallel with the hardware design. The design shall clearly define
the hardware/software interfaces and identify software requirements,
documented in a preliminary Software Requirements Document (DID# V-04).

The contractor shall also identify, design and develop/procure any
required ground support equipment necessary for the development and/or
implementation of the experiment hardware. This shall include
identifying any transportation and handling considerations that will
impose requirements on the flight hardware or support equipment.

### Prototype/Breadboard Development

The contractor shall minimize system and/or subsystem development risk
based on identified engineering feasibility issues through the design,
development and fabrication of system and/or subsystem-level mockups,
breadboards, brassboards and prototype hardware, as specified by the
Delivery Order. The hardware may be required to evaluate form, fit
and/or functional performance, as well as manufacturing techniques, to
determine overall performance and compliance to the system requirements.
Risk reduction hardware development and testing should be focused on the
details of the engineering experiment design in meeting all of the
requirements defined in the experiment's system requirements. Any
hardware limitations should be identified and alternate design
prototypes should be built and tested in areas where meeting a system
and/or subsystem requirement may be challenging. The results of the
prototype testing shall be made available for NASA review and
incorporated into the final design and if appropriate, the engineering
model.

### Verification & Safety

The contractor shall provide assurance that the preliminary design will
meet all carrier safety and verification requirements. The contractor
shall perform safety hazard analysis to identify hazards and mitigation
methods to assure that the proposed preliminary design does not violate
any safety requirements which will endanger human life or mission
success. These analyses shall be documented in Safety Hazard Reports
(DID# PA-03) and a Phase 0/1 Safety Compliance Data Package (DID#
PA-05), unless otherwise defined in the Delivery Order. The contractor
shall also participate in the Phase 0/1 Safety Review at the site
designated per the Delivery Order. The safety critical structures shall
also be identified through analysis and documented in a Safety Critical
Structures Data Package (Preliminary) and a Fracture Control Plan (DID#
PA-04).

The contractor shall develop preliminary verification plans (DID# V-01
and DID# V-02) that identify clearly where, how, and when each function
and performance requirement is verified in the verification program
before launch and, if applicable, how these requirements are again going
to be verified on-orbit.

The contractor shall assure that all the chosen materials for the
experiment design are properly safety and meet material requirements for
corrosion resistance, stress corrosion cracking susceptibility,
outgassing, flammability, fluid compatibility, and offgassing in
habitable areas (SOW 4.2.3). The contractor shall identify material
usage in a preliminary Materials Identification and Usage List (DID#
PA-06) document or justify the use of non-A-rated materials (MUA) in
space flight hardware if required.

### Integration and Operations Planning

The contractor shall develop preliminary versions of the Payload
Integration Agreement (DID# R-03) main volume and the Interface Control
Document (DID# R-02) or equivalents, based on the carrier's integration
template. These integration planning and requirements documents shall
include evaluations based on the preliminary design that include:
payload configuration, payload training requirements, payload command
and data handling requirements, ground data services requirements,
payload operations requirements, and payload ground
integration/deintegration requirements.

The contractor shall identify and design any simulators required for
training, integration, and operations to support the experiment mission.
The identified simulators and concepts for each shall be provided as
part of the PDR presentation package. For ISS FCF sub-payloads, the
contractor shall work with the FCF engineering team to determine the
training requirements to support the formulation of an integrated FCF
training plan.

### Project Planning

The contractor shall develop a detailed engineering plan, or
modification of the existing Contractor Project Plan (DID# PM-01) that
defines the structure, approach, and processes required to complete the
final design, development, fabrication, assembly, and test of the
required hardware, software, and associated infrastructure. The
contractor shall also develop a Software Management and Development Plan
(Preliminary), per DID# PM-03, that provides the overall approach for
development of the project software. The life cycle costs of the project
may also be requested in the Delivery Order that include: the direct,
indirect, recurring, nonrecurring, and other related costs in the
design, development, production, operation, maintenance, support, and
retirement of the experiment. The contractor shall also identify key
risks based on the contractor's Risk Management Plan (DID# PM-02) that
requires on-going monitoring to assure compliance to requirements,
schedule or costs. The key risks shall be identified and provided to
NASA along with evidence that the preliminary design will meet
performance, cost, and schedule as planned as part of the PDR
presentation package that includes any long lead items which may
threaten schedule compliance are identified and/or procured.

### Product Assurance Plan

The contractor shall provide a Product Assurance Plan (DID# PA-01) that
defines the tailored approach to assure the safety, quality and
reliability of Delivery Order's space experiment systems and components.
The contractor shall also develop a Software Assurance Plan in
accordance with DID# PA-11 which describes the software management
procedures, policies, and controls to be used in developing the flight
software.

The contractor shall perform reliability and maintainability analysis
where appropriate to assure that the experiment's preliminary design
will meet the mission requirements through reliable
subsystems/components and/or through maintenance. Reliability analysis
is based on sound methodology and presents realistic predictions for
logistics planning and life cycle cost analysis. The results of this
analysis shall be part of the PDR presentation package.

## DESIGN AND DEVELOPMENT

The contractor shall develop a final design that can demonstrate at the
system, subsystem and component level compliance to the system, carrier,
product assurance, and science requirements, as well as other applicable
requirements identified in the Delivery Order. The outcome of the Design
and Development phase is to complete the design of the experiment
hardware and software that meets all performance and functional
requirements as demonstrated through test and analysis with all
technical problems and design anomalies resolved without compromising
system performance, reliability, and safety. The performance standard
for successful completion of this work element occurs upon NASA approval
at a Critical Design Review (CDR) or a Verification and Test Review
(VTR). In the performance of Design and Development efforts, the
contractor shall accomplish the following:

### Specifications and Analyses

The contractor shall generate complete system build-to specifications
that includes hardware and software. This activity shall include
preparation of specifications for systems, subsystems, and, if
appropriate, components which meet the requirements of DID# R-01.
Requirement traceability establishing the linkage of all derived
requirements shall be performed to ensure verification and validation of
the overall system. All requirements allocated to software shall be
documented in a Software Design Document (DID# D-06) as defined in the
Delivery Order.

The contractor shall perform, where required, system level analyses and
trade studies to optimize the operating design conditions; support the
development of the final design; demonstrate overall compliance with
requirements; support the verification activities; establish system
performance; evaluate thermal, environmental and structural behavior
(vibration, loads, etc.); determine reliability and maintainability; and
support the integration of developed components.

### Flight Design

The contractor shall develop an overall detailed reference design such
that all requirements are achieved, unless specifically waived by NASA.
The contractor shall develop a comprehensive description of the flight
design describing the resultant final design and documented per the
Delivery Order, such as a Baseline System Document (DID# D-03). As part
of this final design effort, the contractor shall develop overall system
schematics, layouts, interface requirements and drawings, mass
properties, volumetric characteristics, resupply requirements, and
resource requirements. The contractor shall develop a system layout
showing the relationship of each component or subsystem, the system
structure, harnessing, mounts and assembly requirements. Fabrication and
assembly drawings of the design shall be in accordance with drawing
standards defined in DID# D-04.

The contractor shall develop a software design and code development
based on the hardware design and requirements that may also include
simulator software, training software and ground support software, based
on carrier requirements, hardware requirements, and NASA software
development requirements. The contractor shall also develop the software
design that includes software simulations and prototyping to eliminate
any potential risks, which may hamper software coding, and integration.
The software design shall be documented in a Software Design Document
(DID# D-06) that describes the interface design, data requirements and
architectural design of the software.

Upon request of the Delivery Order, the flight hardware and software
design may be subjected to external design audits by NASA involving
specialty engineering groups, manufacturing, safety, quality, operations
and utilization and test organizations to ensure the integrity and
validity of the final design.

### Engineering Model Development

If defined in the Delivery Order, the contractor shall minimize
development risk through the design, development and fabrication of an
engineering model. The contractor shall perform the testing and
integration activities associated with the engineering model and/or
component, subsystem, and system development required to validate the
final design. The results of the testing and integration activities
shall be made available for NASA review and incorporated into the final
design.

### Verification and Safety

The contractor shall develop a final, comprehensive Verification Plan
(DID# V-01) and associated Individual Item Verification Plans (DID#
V-02) to assure that the payload hardware and associated software will
meet all defined requirements. The Verification Plan(s) shall identify
clearly where, how, and when each function and performance requirement
is verified in the verification program before launch and, if
applicable, how these requirements are again going to be verified
on-orbit.

The contractor shall assure that all the chosen materials for the
experiment design are properly safety and meet material requirements for
corrosion resistance, stress corrosion cracking susceptibility,
outgassing, flammability, fluid compatibility, and offgassing in
habitable areas (SOW 4.2.3). The contractor shall identify material
usage in a final Materials Identification and Usage List (DID# PA-06)
document or justify the use of non-A-rated materials (MUA) in space
flight hardware if required.

The contractor shall provide assurance that the final design will meet
all carrier safety and verification requirements. The contractor shall
perform an integrated safety analysis of the final design that shows
that there are no outstanding hazards, which cannot be controlled or are
within an acceptable risk level if waivers are required. These analyses
shall be documented in Safety Hazard Reports (DID# PA-03) and a Phase 2
Safety Compliance Data Package (DID# PA-05), unless otherwise defined in
the Delivery Order. The contractor shall also participate in the Phase 2
Safety Review at the site designated per the Delivery Order. The safety
critical structures shall also be identified through analysis and
documented in a final Safety Critical Structures Data Package .

### Carrier Integration, Operations & Training Planning

The contractor shall perform the analysis and implementation planning
necessary to define, prepare for and execute the operation of the
experiment, including design or development of any equipment required
for operations. The contractor shall prepare the experiment's
operational requirements and plans, operations concepts, mission
profiles, mission rules, crew procedures and timelines, and contingency
plans. The operations requirements with the carrier shall be documented
in a preliminary Payload Operations Requirements Data Set (DID# R-03)
based on the carrier's integration template unless otherwise directed by
the Delivery Order.

The contractor shall document the experiment's with the carrier in a
preliminary Payload Configuration Data Set (DID# R-03) based on the
carrier's integration template unless otherwise directed by the Delivery
Order.

The contractor shall prepare training requirements and plans, training
aids, models, simulators, software, and other training necessary for
ground and flight operations. The Training Requirements with the carrier
shall be documented in a Payload Training Requirements Data Set (DID#
R-03) based on the carrier's integration template unless otherwise
directed by the Delivery Order.

The contractor shall prepare ground data services requirements and plans
necessary for ground and flight operations on the specified carrier. The
ground data service requirements with the carrier shall be documented in
a Ground Data Services Data Set (DID# R-03) based on the carrier's
integration template unless otherwise directed by the Delivery Order.

The contractor shall perform the integrated logistic analyses required
to formulate optimum spares provisioning and maintenance strategies for
the life of the experiment. The transportation and handling of the
experiment hardware and associated ground support equipment shall be
identified. If requested in the Delivery Order, the results of these
analyses shall be incorporated and maintained in an Integrated Logistics
Support Plan per DID# OP-01. The contractor shall also determine the
predicted reliability of the system hardware.

### Project Planning

The contractor shall develop a detailed Assembly, Integration, and Test
Plan (DID# V-12) for the required activities that includes carrier
integration activities as part of CDR or VTR. The schedule shall
indicate parts procurement, fabrication, and the acquisition of required
special tooling or fixtures, if required. The closeout of all PDR
actions shall also be documented as part of the CDR or VTR review
presentation.

## FABRICATION, ASSEMBLY AND TEST

The contractor shall fabricate, assemble, test, verify, and deliver the
required hardware, software, and documentation specified in the Delivery
Order. The outcome of the Fabrication, Assembly and Test phase is to
provide an operational system that satisfies the ultimate user. This
involves the development of a certified flight system, unless otherwise
specified in the Delivery Order, all-necessary development and
qualification hardware and software; ground/flight/logistics support
equipment, spare parts required to sustain the system and required
integration documentation. The performance standard for successful
completion of this work element occurs upon engineering-review approval
by NASA at a Pre-Ship Review (PSR) and approval of a Certification for
Flight Readiness. In performance of fabrication, assembly and test
effort, the contractor shall accomplish the following:

### Mission Integration

The contractor shall perform mission and technical integration efforts
necessary to assure delivery of a fully functional system (flight and
ground unit) which satisfies all applicable carrier requirements. The
contractor shall ensure compatibility of the major subsystems with each
other and shall assure compatibility of the total system with all
required test facilities, the selected carrier (ISS, FCF, EXPRESS,
etc.), and the associated transportation system. This effort shall also
include development and/or support of the appropriate integration
documentation and its annexes (DID \# R-03) in accordance with
development and delivery of required interface and operational data in
the appropriate carrier integration format; support of all carrier
integration working groups and panels; and development of required
safety, operation, and training documentation. Functional, thermal,
fracture control, and fatigue analyses shall be performed as required in
accordance with the selected carrier requirements documents to
demonstrate that the hardware design satisfies system requirements.

### Flight Unit/Ground Unit

The contractor shall fabricate, assemble, and test a flight unit that
meets the specifications, quality and product assurance requirements
identified in the Delivery Order and SARGE for the experiment
classification and flight carrier. The Flight Unit shall be subjected to
acceptance test levels and durations with its intended use to be
operational in space as defined in the Verification Plan.

The contractor may be required to fabricate, assemble, and test a
Qualification Unit to determine flight acceptance verification and
compliance with specifications. The Qualification Unit shall consist of
the same systems and subsystems as the Flight Unit and shall be verified
to be physically and functionally identical to the Flight Unit. The
primary function of the Qualification Unit is to demonstrate through
testing to qualification levels that the Flight Unit design meets all
requirements. The Qualification Unit is not intended for flight unless
otherwise specified in the Delivery Order. The Qualification unit shall
be refurbished by the contractor to flight level specifications if
intended for flight. The Qualification Unit shall be maintained under
the same quality control and configuration management procedures as the
Flight Unit.

A Ground Unit may also be required (per the Delivery Order) to be used
for ground integration activities, trouble shooting of the on-orbit
hardware, and/or the checkout of proposed upgrades to the on-orbit
hardware. This unit is typically identical to the Flight Unit, but will
not receive full flight qualification testing.

The contractor shall design, fabricate/procure, assemble and verify the
hardware necessary for handling, transporting, storing, and qualifying
the flight unit, ground unit and trainer (hardware and software) in
accordance with the applicable carrier ground support design
requirements identified in the Delivery Order. The contractor shall
supply and maintain the spare parts required supporting the flight and
ground-based hardware and related equipment as specified in the Delivery
Order and the experiment's Integrated Logistics Support Plan. All
fabrication, inspection, checkout, acceptance test, and preparation for
delivery requirements, applicable to deliverable hardware and software,
shall also apply to the spare items furnished.

The contractor shall develop, verify, validate, and maintain all
software necessary to control and utilize the hardware deliverables
developed to Delivery Order specifications. The contractor shall install
and verify/validate all software necessary for the operation of all
developed hardware per the Delivery Order such as the Ground Unit,
Qualification Unit, Flight Unit, Trainers, interface verification,
ground support equipment, and simulators.

### Installation, Assembly & Checkout (IACO)

The Contract shall conduct all necessary activities as defined in the
Assembly, Integration, and Test Plan to ensure the successful
integration of all hardware and software with the selected carrier.
These activities shall be in accordance with applicable carrier
interface documentation to ensure that hardware and software comply with
all carrier payload certification requirements, as well as to ensure
that all operational, safety, and reliability requirements are met.
Results of this task shall be reported in accordance with the
experiment's Verification Plan (Certification Certificates). The
contractor shall provide calibration, proof testing, dynamic balancing
and integrated operation of the experiment system and functional
checkout of fabricated systems and components as specified in the
Delivery Order. Specific Delivery Orders may require assembly,
installation and system checkout in NASA facilities. The contractor
shall inspect all work prior to delivery to insure compliance to
requirements. A written inspection report shall be delivered with the
completed hardware (DID# V-11).

### Verification and Safety

The contractor shall conduct qualification, acceptance and verification
activities (test, analysis, etc.) on components, subsystems and combined
assemblies. These activities shall be in accordance with the
Verification Plan (DID# V-01) to assure that the payload hardware and
associated software meets all defined requirements. The contractor shall
verify integrated performance, assembly interactions, and interfaces, as
appropriate. Unless furnished by NASA, the contractor shall provide all
test support equipment, test fixtures, ground support equipment, and
simulators, required in the performance of the verification tests. The
contractor shall generate and maintain a requirements management and
traceability and close-out system to ensure and document that all design
and performance requirements requiring verification are addressed by the
verification program and all verification requirements are closed-out.
The closeout system shall maintain verification and assessment reports,
certification statements, and comprehensive verification reports (DID \#
V-04 & DID# V-08). The experiment system verification tests shall
include science verification & validation tests that includes an
assessment of the system performance by the Principal Investigator to
ensure that the hardware can successful perform the functions required
to meet the science requirements of the experiment. The software shall
also be verified and validated based on a Software Verification and
Validation Plan (DID# V-09) with the results documented in a Software
Verification and Validation Report (DID# V-10).

The contractor shall provide assurance that the experiment system meets
all carrier safety and verification requirements. The contractor shall
perform an integrated safety analysis and test of the flight hardware
that shows that there all hazards are controlled or approved waivers
have been approved detailing acceptable risk level. These analyses and
verification tests shall be documented in Safety Hazard Reports (DID#
PA-03) and a Phase 3 Safety Compliance Data Package (DID# PA-05), unless
otherwise defined in the Delivery Order. The contractor shall also
participate in the Phase 3 Safety Review at the site designated per the
Delivery Order.

The contractor shall facilitate the pre-mission operations with the PI
to characterize the hardware and obtain ground-based data in preparation
for flight. This activity shall include providing availability of the
hardware and software, set-up of operational parameters, and supporting
the operation of the experiment.

### Operations Capability Development

The contractor shall develop procedures for crew tended, untended, and
off-nominal operations with the input and approval of experiment, PI,
and carrier representatives, including Flight Safety. The contractor
shall deliver any hardware or software required for operations
capability as identified in the Delivery Order, such as simulators or
data processing equipment to support the mission.

The contractor shall conduct logistics support analyses to determine the
support required for pre-flight, flight, on-orbit, return, and
post-flight operations of hardware and software integrated in an ISS
experiment. Based on the logistics support analyses and other inputs,
the contractor shall provide adequate flight and non-flight spares. The
analyses shall include plans for the most efficient physical transfer of
flight and non-flight items required supporting the experiment
operations. The contractor shall provide the physical packaging,
handling, storage, and transportation of all flight and non-flight
items. A final Integrated Logistics Support Plan (DID# OP-01) shall be
provided that documents the experiment's ILS approach.

### Training

The contractor shall develop, in conjunction with specific users, all
training materials for the experiment, including experiment specific
training unit development as defined in the Delivery Order. The
contractor shall develop and support the installation of the
experiment-training unit at the appropriate site for the carrier, if
applicable. The contractor shall work with the PI teams, the flight
crew, and the carrier training organization to develop the requirements
for crew training, if applicable. These requirements will drive the
design and development for the experiment training materials. The
contractor shall implement the training requirements for the training
sessions, for any 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 instrumentation for proper decision
making and development of experiment procedures.

### Carrier Integration

The contractor shall be responsible for all ground servicing at the
launch site (e.g. KSC) to ensure the successful integration of all
experiment hardware with the carrier or transportation system (i.e. MPLM
for ISS). The contractor personnel shall actively participate in the
launch processing team activities and shall add/modify requirements,
concur on procedures, analyze data, make engineering recommendations and
decisions required by conditions not within specifications. The
contractor's launch site activities shall be in support of the payload
ground operations effort provided by NASA's launch site personnel.
Specifically the contractor shall: develop and implement Launch Site
Operations and Test Procedures (DID# OP-04) for the experiment hardware,
support the development of the requirements for testing, servicing, and
facility services required to process the experiment hardware through
pre-launch activities, monitor tests, evaluate test data, maintain
records of the tests, and provide engineering expertise to resolve
hardware/software problems, and ensure the experiment hardware has been
properly tested, support Launch Readiness Reviews (LRRs) and Flight
Readiness Reviews (FRRs) with engineering and management data to ensure
the experiment hardware is ready for flight. Following verification of
flight readiness, the flight hardware and associated documentation shall
be provided to the launch element manager for pre-flight processing and
launch.

### Product Assurance

The contractor shall implement the experiment specific Product Assurance
Plan (DID# PA-01) in the performance of the hardware and software
development, test, and verification. The contractor shall maintain and
provide to NASA the failure history of the hardware and software along
with remedial and preventive actions taken. The contractor shall provide
identification of any specification waivers and deviations required
along with the basis for approval. The contractor shall also maintain
the status of limited life components of the experiment system.

## OPERATIONS

The contractor shall support on-orbit integration activities, flight and
data reduction, experiment real-time operations, and data reduction for
PI analysis. The outcome of the Operations phase is to operate the
experiment to acquire the required scientific data for the PI. The
operational activities commence with delivery of the experiment to the
ultimate operator for use in its intended environment. The performance
standard for successful completion of this work element occurs upon
achieving the full success criteria for the experiment as described in
the Science Requirements Document. In performance of operations effort,
the contractor shall accomplish the following:

### On-orbit Operations

The contractor shall be responsible for the real-time operations and any
supporting activities of the PI's experiment in conjunction with the
carrier operations per the Delivery Order. The contractor shall provide
trained staff for console operations. Appropriate personnel shall be on
console when the experiment is active or other planned operations are
being performed. The contractor shall be responsible for on-console
support of on-orbit installation & set-up, check-out and verification of
the experiment hardware and software, if applicable; the planning and
scheduling of all experiment on-orbit operations; obtaining or
requesting all necessary ground and on-orbit resources; and implementing
and following the planned experiment operations. The contractor shall be
prepared to respond to crew and ground team communications, and
off-nominal situations. The contractor shall develop standard procedures
to resolve on-orbit problems or anomalies.

The contractor shall provide PI mission operations support including
coordination of real-time experiment requirements with the PI, the
carrier, and other appropriate entities; acquire and process scientific
real-time data according to pre-determined requirements; support the
correlation of scientific data with mission events; provide appropriate
personnel to support on-console mission operations and scientific data
analysis at the carrier's control center (LeRC TSC for FCF, White Sands
for Sounding Rockets, etc.); preparation of data products for data
dissemination including general and PI-specific mission summary reports;
preparation of unique data analysis reports for the PI; maintain
scientific information databases; and participate in working group
interchanges as defined in the Delivery Order.

### Post Mission Operations

The contractor shall be responsible for the post mission operations of
the PI's experiment to obtain baseline scientific data per the Delivery
Order. The contractor shall be responsible for ground installation &
set-up, check-out and verification of the experiment hardware and
software, if applicable; the planning and scheduling of all experiment
ground operations; and implementing and following the planned experiment
operations that duplicates PI experiment data points per the Delivery
Order. The contractor shall acquire and process scientific real-time
data according to past flight timelines; support the correlation of the
scientific data; preparation of data products for data dissemination;
preparation of unique data analysis reports for the PI; maintain
scientific information databases; and participate in working group
interchanges as defined in the Delivery Order.

### Sustaining Engineering & Maintenance

The contractor shall conduct appropriate analyses, data evaluations, and
ground tests to maintain the on-orbit system. This includes the tracking
of limited life items for safety and/or mission assurance reasons;
incorporating small upgrades as required; standard reporting of the
on-orbit experiment performance; developing trend analyses using
on-orbit systems reports and other available data; and implementing the
experiment maintenance plan designed to maintain the full operational
capability of the experiment.

# 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

-   Formal review presentation (unless waived by 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 the
Development of PI Specific Experiments, Instruments and Diagnostics
activities are provided in the following sections.

## Science Concept Review (SCR)

The purpose of the SCR (to be conducted by the Government, the
contractor may be asked to attend for information purposes) is to
establish, through peer-review, that the scope and feasibility of the
experiment have been adequately addressed to propose a definitive flight
experiment. The primary objectives of the SCR are to:

-   Affirm the merit of and need for the experiment (value to the
    scientific community), establish the detailed scientific objectives,
    confirm the rationale for a microgravity experiment, justify the use
    of space-based laboratories for the microgravity environment, and
    review the proposed scope and experimental approach. In addition,
    assess maturity, priority, and completeness of the preliminary
    science requirements to meet the objectives, and confirm that
    scientific feasibility has been completely demonstrated. The PI
    presents the information for the review panel to make these
    judgments.

-   Identify the PI's plan of activity with specific milestones between
    SCR and the Requirements Definition Review (RDR) with the goals of
    finalizing science requirements, improving models or theories,
    conducting additional ground-based experiments and completing
    technology development. (Often the plan proposed at SCR needs
    modification based on the panel's input provided at this review).
    The PI presents this information.

-   Evaluate proposed space-based experiment concept (block diagram
    level) with emphasis on compatibility with science requirements and
    identify engineering feasibility issues.

-   Define engineering plans (emphasizing the most critical, costly and
    difficult tasks) to develop the experiment concept into flight
    hardware (cartoon flight concept may be presented). Prepare the
    schedule and budget to reach RDR in reasonable detail, and provide
    rough order of magnitude budget and schedule estimates to flight.

## Requirements Definition Review (RDR)

The purpose of the Requirements Definition Review (RDR) is to evaluate,
through peer-review, the maturity of the engineering requirements of the
project. Successful completion of this review will be based upon the
following success criteria (some items provided are overall review
requirements and are not the responsibility of the contractor):

-   Science requirements document (SRD) is finalized (PI
    Responsibility).

-   Relevance of the science objectives and the requirement to conduct a
    flight experiment are confirmed (PI Responsibility).

-   Feasibility of the experiment has been demonstrated with the
    presentation of results of the ground-based science or laboratory
    testing.

-   Engineering design requirements are documented and reviewed by the
    panel and demonstrate compliance with the science requirements.

-   Experiment design is documented, as a minimum at the system level
    and reviewed by a NASA selected engineering and science panel.

-   The payload carrier accommodations and interfaces are defined and
    documented.

-   The development issues identified at the SCR have been resolved or
    plan in place to resolve by PDR.

-   Review the disposition of any SCR action items provided to the
    contractor.

-   Submit for review and NASA approval the Contractor's Project Plan
    which includes the approach, work breakdown structure, configuration
    management approach, hardware/software development and test
    philosophy, schedules, and costs.

-   Methodology used to develop the cost estimate, and costs by work
    breakdown structure is reviewed.

-   Document and submit for review the technical, schedule, and cost
    risks of the proposed experiment in accordance with the Risk
    Management Plan.

    **RDR Minimum Deliverables:**

-   Documented results of ground based science or laboratory testing

-   System Requirements (draft)

-   Requirements Compliance Matrix showing compliance with the science
    requirements

-   Baseline Concept Descripiton document that describes the concept and
    anticipated performance and operation

-   Disposition of SCR action items

-   Identification of flight hardware development risks that includes
    schedule and cost risks of the proposed experiment

-   Payload/Carrier interface requirements (can be part of the System
    Requirements)

-   Contractor's Project Plan that includes a software development
    approach

-   RDR Presentation Package

### Preliminary Design Review

The Preliminary Design Review is a formal technical review of the system
design and development approach. The PDR is conducted after the
completion of the preliminary design synthesis and before the detailed
design process. This review shall be conducted prior to the fabrication
of an engineering model of the flight experiment or prior to completion
of the breadboard testing if an engineering model is not being
fabricated. Successful completion of this review will be based upon the
following success criteria (some items provided are overall review
requirements and are not the responsibility of the contractor):

-   Principal Investigator's operations plan and data analysis plan is
    reviewed (PI responsibility).

-   Compliance of the system design with the science and carrier
    requirements is documented or demonstrated.

-   Functional and performance requirements of the entire system are
    documented and shown to be appropriate.

-   Breadboard level testing directed at resolving feasibility issues is
    presented and reviewed.

-   Compliance with appropriate design guides and standards, including
    safety and quality are shown.

-   Existence and compatibility of the physical and functional
    interfaces, including software is established.

-   Special test equipment or tooling requirements is determined.

-   Long lead part procurements and associated risks are determined.

-   Review the disposition of any RDR action items provided to the
    contractor.

-   Submit for review and NASA approval the Contractor's Project Plan
    (DID# PM-01) which includes the approach, work breakdown structure,
    configuration management approach, hardware/software development and
    test philosophy, schedules, and costs.

-   Methodology used to develop the cost estimate, and costs by work
    breakdown structure is reviewed.

-   Document and submit for review the technical, schedule, and cost
    risks of the proposed experiment in accordance with the Risk
    Management Plan.

A NASA appointed review board shall assess the status of the project in
regard to the above items, recommend whether or not to proceed with the
project into the software and engineering model development and test and
the flight design phase, identify any concerns that exist, and recommend
any actions to be taken to enhance the success of the next phase of the
project.

**PDR Minimum Deliverables required:**

-   Design-to Specifications

-   PDR Presentation Package

-   Preliminary Structure Design & Analysis

-   Preliminary Thermal Analysis

-   Preliminary Reliability Analysis

-   Preliminary Environmental Testing Requirements

-   Draft Payload Integration Agreement (w/carrier organization)

-   Safety, Flight & Ground, Phase 0/ 1 Data Package and associated
    Safety Hazard Reports

-   Preliminary Baseline Concept Descripiton document, or equivalent

-   Preliminary Requirements (Engineering and Science) Compliance
    Matrices

-   Preliminary Verification Plan

-   Product Assurance Plan

-   Software Assurance Plan

-   Interface Control Document (Preliminary), if required, with the
    carrier

-   Software Management and Development Plan

-   Draft Software Requirements Document

-   Software Design Document (Preliminary)

-   Documented results of software prototypes

-   Packaging Layouts

-   Breadboard/Brassboard/Prototype Test Results

-   Ground Support Equipment and Flight Support Equipment Requirements

-   Revised Contractor Project Plan

### Critical Design Review

The Critical Design Review is a formal technical review conducted after
the design has reached the degree of completion needed to permit a
comprehensive and detailed examination and data analysis. Typically,
this review shall be conducted after the review of engineering model
system testing (if an engineering model is being built) and/or prior to
release of drawings for fabrication of the end item hardware. The goal
is to have 90 percent of the flight hardware drawings released at the
time of the CDR. Successful completion of the CDR and close out of all
action items provides the technical definition for the end item
baseline. Successful completion of this review will be based upon the
following success criteria:

-   The detailed design satisfies the design requirements established in
    the governing specification unless waivers or exceptions have been
    approved.

-   Results of the engineering model system tests and any impact on the
    flight hardware specifications or design have been incorporated into
    the design.

-   Interface relationships that must exist between the end item and the
    payload carrier (e.g. ISS, FCF, SpaceHab, Sounding Rocket etc.) have
    been documented.

-   Predicted performance of the hardware including reliability has been
    completed.

-   Compliance with all requirements including safety and quality
    requirements.

-   Controls of safety hazards have been identified and reviewed.

-   Adequacy of the packaging of all subsystems.

-   Effectiveness of the design for fabrication and test has been
    determined.

-   Fabrication plans and the progress in the identification and
    acquisition of required special tooling or fixtures is reviewed.

-   Test plans, including preparation of any special test equipment, and
    software test plans and procedures are documented.

-   Document and submit for review the technical, schedule, and cost
    risks of the proposed experiment in accordance with the Risk
    Management Plan.

A NASA appointed review board shall assess the status of the project
with respect to the above items, recommend whether or not the project
should proceed to the flight hardware fabrication, integration, and test
phase, identify any concerns that should be addressed, and recommend any
actions that should be taken to enhance the success of the next phase of
the project.

**CDR Minimum Deliverables required:**

-   90% of Drawings

-   Software Design Document

-   Software Verification and Validation Plan

-   Thermal & Structural Analysis

-   Reliability Analysis

-   Phase 2 Safety Package with Preliminary Verification Analysis

-   Baseline System Descripiton document

-   Science and Engineering Compliance Matrices

-   Preliminary Data Delivery Plan

-   Verification Plan

-   Preliminary Integration Documentation required of the carrier

-   Engineering Model Test Results

-   PDR RFA Closeout

-   GSE Design

-   Assembly, Integration and Test Plan

### Verification and Test Review

A Verification and Test Review shall be conducted prior to the assembly
of the experiment (subassemblies may be assembled). The overall purpose
of the review is to present the overall test plan for the hardware and
software and obtain approval of project management to commence
environmental and verification testing. The specific purposes of the
review are to:

-   Assess the process in which the science, engineering and safety
    requirements shall be verified through the testing of the hardware
    and software. The process shall include the rationale for testing
    (i.e. testing high risk subsystems before system assembly etc.) and
    have direct traceability to the science, engineering and safety
    requirements.

-   Assess the verification & test plan which shall include test levels
    (i.e. thermal, vibratory, EMI, and radiation etc.) and test
    durations (i.e. number of thermal cycles, vibration duration, etc.)
    of the hardware and software subsystem/systems. The environmental
    test plan shall include the expected carrier vibration,
    EMI/susceptibility, thermal and radiation levels.

-   Review assembly procedures to assess the link with the test plans.

-   Assess the risk mitigation plan for compliance with all science,
    engineering and safety verifications.

-   Review the definition of the work to be accomplished during
    verification and environmental testing. The results of all testing
    shall be formally reported at the Pre-ship review.

NASA appointed review board shall assess the status of the flight
experiment test plan and recommend whether to proceed with the presented
test plan or to modify the presented test plan. NASA appointed review
board shall also make an independent judgment of the risks involved in
any areas, and identify any concerns which would affect the success of
the flight experiment.

**V&TR Minimum Deliverables:**

-   Science and Engineering Compliance Matrix

-   Verification Plan (Science & Engineering)

-   Software Verification and Validation Plan

-   Reliability Analysis

-   Complete Phase 2 Safety Package with Verification
    Test/Analysis/Inspection Plan

-   Environmental, Verification and Safety Test Risk Assessment Plan

-   Assembly, Integration and Test Plan

### Pre-Ship Review

A preship review is a formal review conducted prior to shipment of the
flight experiment hardware to the launch site for integration. The
overall purpose of the review is to obtain approval of the Center
management that the flight experiment meets all requirements and is
ready to be shipped. Successful completion of this review will be based
upon the following success criteria:

-   The flight worthiness and readiness of the flight experiment
    hardware and software; ground support hardware and software; and
    science operations plans will be reviewed.

-   Results of the verification testing including any specifications
    that were waived because of non-compliance and any significant
    modifications made to the flight experiment will be reviewed for
    completeness and meeting specifications.

-   All significant non-conformances and functional failures are
    provided to assess for corrective action and closeout.

-   The plans are completed and appropriate following shipment of the
    hardware for integration.

-   Flight hardware, along with associated GSE and software, is ready to
    ship to the launch site

NASA appointed review board shall assess the status of the flight
experiment and recommend whether or not to ship the flight experiment to
the launch site, make an independent judgment of the risks involved in
any areas, and identify any concerns which would affect the success of
the flight experiment.

**PSR Minimum Deliverables:**

-   100% of As-Built Drawings

-   Thermal & Structural Analysis (final)

-   Launch Site Operations and Test Procedures (final)

-   Reliability Analysis (final)

-   Phase 3 Safety Package with Final Verification Analysis

-   Software Code

-   Software Verification and Validation Reports

-   Baseline System Descripiton document (final)

-   Science and Engineering Compliance Matrices (final)

-   Integration Documentation required of the Carrier

-   Integrated Logistics Support Plan (final), if required by Delivery
    Order

-   Integration Data Package that including non-conformances, failure
    reports, etc.

-   CDR RFA Closeout

-   PSR Presentation Package

-   GSE Drawings

### Flight Readiness Review

A Flight Readiness Review is a formal review conducted after carrier
installation, integration and initial checkout. The overall purpose of
the review is to obtain NASA approval and final acceptance of the flight
hardware and associated ground support infrastructure. Successful
completion of this review will be based upon the following success
criteria:

-   The readiness of the flight experiment hardware will be reviewed
    based on the results of initial checkout of the hardware and/or
    software

-   Results of the verification (and calibration, if appropriate)
    testing including any specifications that were waived because of
    non-compliance and any significant modifications made to the flight
    configuration will be reviewed for completeness and meeting
    specifications.

-   All significant non-conformances and functional failures are
    provided to assess for corrective action and closeout.