Section J, Attachment A

**RAPID SPACECRAFT PROCUREMENT**

**STATEMENT OF WORK**

**June 6, 1997**

1\.
Introduction\...\...\...\...\...\...\...\...\...\...\...\...\...\.....

2\.
Scope\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...

3\. Applicable and Reference Documentation\...\...\...\...\...\...

4\. Work to be Performed by the Contractor\...\...\...\...\...\...

4.1 System Implementation

4.1.1 Core System(s)

4.1.2 Core System Option(s)

4.1.3 Mission-Specific Modifications

4.2 Non-Standard Services

4.2.1 Non-Mission-Specific Non-Standard Services

4.2.2 Mission Specific Non-Standard Services

4.3 Standard Services

4.3.1 Program Management

4.3.1.1 Quality Management System

4.3.1.1.1 Quality Assurance Management Requirements

4.3.1.1.2 Pre-Launch Reports

4.3.1.1.3 Post Launch Reports

4.3.1.2 Documentation

4.3.1.3 Reviews

4.3.1.3.1 Mission Design Review Requirements

4.3.1.3.2 Instrument Integration Readiness Review

4.3.1.3.3 Pre-Environmental Review

4.3.1.3.4 Pre-Ship Review

4.3.1.3.5 Program Status Reviews

4.3.1.4 Audits

4.3.1.5 Government Insight

4.3.2 Systems Engineering

4.3.2.1 Requirements Analyses and Allocations

4.3.2.2 Interface Definition, Verification and Control

4.3.2.3 Observatory/Launch Vehicle Interface

4.3.2.4 Design and Performance Verification Analyses

4.3.3 Spacecraft Bus

4.3.4 Implementation

4.3.4.1 Spacecraft Bus Integration and Test (I&T)

4.3.4.2 Observatory Integration and Test (I&T)

4.3.4.3 Spacecraft Bus/Observatory Storage

4.3.4.4 Spacecraft Bus, Observatory and Ground Support Equipment
Shipment

4.3.5 Launch & Operations

4.3.5.1 Launch Support

4.3.5.2 Flight Operations Interfaces and Support

4.3.5.2.1 Ground System Interface Definition

4.3.5.2.2 Ground System Training and Flight Operations Support

4.3.5.3 On-Orbit Performance Verification

4.3.5.4 Support to On-Orbit Operations

4.3.6 Flight Software

4.3.6.1 Software Maintenance

4.3.6.2 Software Documentation 15

# 

# 

# 1. Introduction

This statement of work (SOW) defines the contractor's efforts required
to provide a spacecraft bus and associated services that meet the needs
of the National Aeronautics and Space Administration's (NASA) flight
science and technology missions. Other United States Government
Departments and Agencies may also utilize this contract. Particular
mission requirements and tailoring of this SOW shall be as defined in
the delivery order issued for each specific mission.

# 2. Scope

The scope of the work encompasses all necessary effort from receipt of
an Indefinite Delivery Indefinite Quantity (IDIQ) contract through the
delivery and on-orbit check out of specific missions. A mission-specific
delivery order will be issued by the Government in accordance with the
ordering procedures contained in the contract schedule. Delivery orders
for non-standard services may be issued by the Government.

# 3. Applicable and Reference Documentation

Reserved for mission specific use.

# 4. Work to be Performed by the Contractor

## 

## 4.1 System Implementation

For this contract, the effort to produce a specified core system, the
selected options, and the mission-unique modifications required in the
delivery order in accordance with the mission implementation
specification, results in a product called the "Spacecraft Bus" or
"Spacecraft". The effort to integrate a payload (or instrument), and
qualify the combined payload and spacecraft bus in accordance with the
mission implementation specification, results in a system called an
"Observatory".

An order for a specific core system placed via delivery order may be a
combination of a core system and options as contained in the contract
schedule, as well as mission-specific modifications to the applicable
core system and options. The complete set of technical requirements as
contained in the delivery order shall be applicable to the core system,
the options and the mission-specific modifications.

### 4.1.1 Core System(s)

The contractor shall develop, implement, test, and qualify a spacecraft
bus ready for payload integration, called the "core system." , integrate
the payload with the core system, qualify the resulting observatory, and
provide launch and operations support, as well as satisfy all
requirements of section 4.3 of the sow. The core system shall conform
with the applicable performance specification and mission implementation
specification provided by the contractor with the proposal.

### 4.1.2 Core System Option(s)

The contractor shall develop, implement, test, and qualify performance
option(s) to the core system such that the combined options and core
system are ready for payload integration, and satisfy all of the
requirements of section 4.3 of this SOW. The option(s) to the core
system shall conform with the applicable performance specification and
mission implementation specification.

### 4.1.3 Mission-Specific Modifications

In order to meet the unique requirements of a specific mission a
contractor may modify their core systems and options. These
modifications are to be implemented as necessary for the adaptation of
the core system, options and implementation effort under the contract to
meet the delivery order requirements. The extent of the modifications
may include, but are not limited to, the addition of performance
parameters; changes to any performance parameter; changes to mission
implementation specifications; the addition of new specifications,
requirements, analyses, reports, hardware, software or support;
adaptation of baseline hardware or software configurations; changes to
baseline schedules, reviews, funding profiles, and milestones; and the
modification of contract deliverable item lists, contents or formats. It
is expected that in some cases the extent of modifications required to
meet the specific mission requirements may be extensive.

## 

## 4.2 Non-Standard Services

The contractor shall provide all personnel, facilities, materials, and
other necessary resources for the performance of non-standard services
as ordered under this contract.

### 4.2.1 Non-Mission-Specific Non-Standard Services

The Government may, from time to time within the period of performance
of this contract, issue non-standard service delivery orders. Delivery
orders issued under this section shall not be specific to any delivery
order previously issued, but may address issues associated with possible
future missions.

These delivery orders may be issued for the following types of efforts:

a\. Analyses related to a particular core system, which includes, but is
not limited to, performance capability analyses, modeling parameters,
potential core system modification analyses, launch vehicle
compatibility analyses, instrument interface analyses, integration
analyses, launch support and on-orbit check out analyses.

b\. Tasks, including but not limited to, core system design envelope
enhancement, core system modifications, verification testing, core
system technology update feasibility, process definitions, reviews, and
updates.

### 4.2.2 Mission Specific Non-Standard Services

The purpose of non-standard services ordered under this section of the
statement of work shall be directly related to a specific mission under
delivery order.

Non-standard services ordered may be for the following types of efforts:
Special studies, analysis, mission specific hardware fabrication and/or
core system modification in support of a specific mission delivery
order.

## 4.3 Standard Services

This section describes the effort required of the contractor upon
receipt of a delivery order. At a minimum the contractor shall provide
all facilities, services, and personnel necessary for the successful and
on-time implementation of all of the efforts necessary to meet the
mission-specific delivery order requirements.

### 4.3.1 Program Management

The contractor shall provide a Program Management function that is
responsible for the control of the specific mission effort. The
contractor's Program Management function shall provide to the Government
reporting and real-time insight into program status, as well as,
technical and programmatic performance of all of the contractor's
responsibilities and activities performed under the delivery order.

The contractor shall perform various design, study, trade-off and
analysis tasks relating to the development, implementation,
characterization and operation of the specific mission as necessary.

The contractor shall be responsible for the submission of all change
order proposals as required by this contract.

The items and services acquired under this contract are required to
include accurate processing of the date and date-related data (including
but not limited to calculating, comparing, and sequencing) by all
hardware and software products delivered under this contract,
individually and in combination, upon installation. This also includes
the manipulation of data with dates prior to, through, and beyond
January 1, 2000, and shall be transparent to the user. Hardware and
software products provided under this contract shall, individually, and
in combination, successfully transition into the Year 2000 with the
correct system data, without human intervention, including leap year
calculations. Such products shall also provide correct results when
moving forward or backward in time across the Year 2000 or subsequent
years.

All systems delivered under this contract shall be Year 2000 compliant.

The contractor shall implement appropriate management systems which
prevent the improper dissemination of Principal Investigator competition
sensitive information.

#### 4.3.1.1 Quality Management System

The contractor will maintain and adhere to a Quality Management System
in accordance with ANSI/ASQC Q9001-1994.

The Government reserves the right to impose other quality standards as
mission-specific requirements to meet the needs of a specific mission.
These unique requirements shall be documented in the mission-specific
delivery order.

ANSI/ASQC Q9001-1994, Paragraph 4.13.2 shall be augmented to include the
following subparagraphs.

##### 4.3.1.1.1 Quality Assurance Management Requirements

Once the mission specific core system begins comprehensive performance
test in demonstration of readiness for mission payload integration, a
system of written problem/failure reports (PFR's) will be used through
launch. The PFR's will be written for any departure from design,
performance, testing, or handling requirements which affect the function
of the flight system, or ground support system which interfaces with the
flight system, or that could compromise mission objectives.

##### 4.3.1.1.2 Pre-Launch Reports

Failure reports are to be reported in accordance with the CDRL.
Contractor format, generation, review, disposition and/or approval of
failure reports will be described in applicable procedure(s) included or
referenced in the contractor's Quality Manual.

##### 4.3.1.1.3 Post Launch Reports

Following launch, flight hardware and software anomalies, problems
and/or failures will be reported using the Spacecraft Orbital Anomaly
Report (SOAR) in accordance with GMI 5310.1B, GSFC Problem/Failure
Anomaly Reporting.

#### 4.3.1.2 Documentation

The contractor shall develop, produce, deliver, and maintain all
documentation required by the Contract Data Requirements List (CDRL) and
necessary to implement the mission-specific delivery order. All efforts
including the performance of tests and analyses not otherwise explicitly
stated in other parts of this SOW, but needed to produce the required
documentation, shall be performed and documented by the contractor. All
documentation, data and analyses generated for, or applicable to, the
effort, whether formal or informal, shall be made available to the
Government upon request at the contractor's facility.

#### 4.3.1.3 Reviews

The contractor shall conduct usual and customary internal reviews and
provide for timely reporting of program status to the Government with
discussions on problem areas, and a timely transfer of technical
information to the Government, of major program milestones. The
contractor shall provide technical and management support to certify
spacecraft bus or observatory readiness at the following program
reviews:

  ------------------------------ ------------------- ----------------------------
  [Review]{.underline}           [\# of              [Personnel
                                 Days]{.underline}   Required]{.underline}

  Mission Design Review (MDR)    3                   Operation, Systems &
                                                     Subsystems Design

  Integration Readiness Review   2                   Systems, Quality & Test
  (IRR)                                              

  Mission Operations Review      2                   Systems & Operations
  (MOR)                                              

  Pre-Environmental Review (PER) 2                   Systems, Quality & Test

  Pre-Ship Review (PSR)          3                   Systems, Quality & Test

  Flight Operations Review (FOR) 2                   Systems & Operations

  Launch Readiness Review (LRR)  1                   Systems, Quality & Test
  ------------------------------ ------------------- ----------------------------

The MOR and FOR shall be held at NASA's Goddard Space Flight Center and
the LRR shall be held at the launch site, all other reviews shall be
held at the contractor's location. The contractor shall ensure that
appropriate personnel attend each review.

The baseline dates for each review shall be defined in Section J,
attachment B of the contract and may be modified by the delivery order
to meet unique mission requirements.

##### 4.3.1.3.1 Mission Design Review Requirements

The contractor shall host and provide data for the Mission Design Review
where mission requirements and subsystem requirements flow-down will be
confirmed, based on the mini-proposal design offered. Interface
documents will have been prepared and reviewed for understanding and
ready for signature. Mission-specific core system modifications will be
confirmed and understood sufficiently to proceed with manufacture.

The contractor shall provide, at a minimum, the following data and
information.

[System Level:]{.underline}

1.  Mission Design overview showing a mature understanding of the
    mission objectives and the approaches that will be used to carry out
    the mission together with definition of roles and responsibilities.

2.  Mission performance requirements allocation and subsystem flow-down

3.  Resource allocations and margins (telemetry, commands, power,
    weight, data storage, processor capability, etc.)

4.  ICDs (instrument, ground system) ready for signature

5.  Performance verification approach and rationale

6.  Spacecraft bus integration and test sequence rationale

7.  Observatory integration and test sequence and rationale

8.  QA program applications, status, issues

9.  Orbit, orbit maintenance, and flight dynamics analysis

10. Flight operations overview and status

11. Mission ground support equipment (GSE)

12. Approach for the next milestone review

13. I&T software requirements, description, status, verification

14. Flight software requirements, description, development and
    verification plan, status

[Subsystem level (including flight software)]{.underline}

1.  Requirements flow-down specifications to each subsystem

2.  Performance verification and validation

3.  Design details of mission-specific elements

4.  GSE

[Specific Analysis and Margins]{.underline}

1.  Stress and dynamics

2.  Loads determination

3.  Communication links

4.  Thermal flight predictions

5.  Power balance (end-of-life and battery DOD)

6.  Worse case

7.  Data flow, Storage and loading

8.  Pointing budgets including attitude control simulation results

9.  Flight dynamics, orbit insertion, maintenance, disposal

10. Radiation, EMC, ESD, magnetics

11. Failure mode and effects update

##### 4.3.1.3.2 Instrument Integration Readiness Review

The contractor shall present at the IIRR:

1.  The results of the latest spacecraft bus Comprehensive Performance
    Test

2.  A resolution plan for all failures, anomalies, and malfunctions
    encountered during system testing

3.  Any remaining open integration issues and their proposed resolution

4.  The readiness to perform Instrument integration (e.g. staffing,
    facilities, GSE, procedures, resources, etc.)

5.  Plans to proceed to Pre-Environmental Review (tests, activities,
    facilities, resources, schedule, flow)

6.  I&T software readiness and verification status

7.  Flight software development and verification status

##### 4.3.1.3.3 Pre-Environmental Review

The contractor shall present at the PER:

1.  The results of Instrument Integration and the status of the
    Observatory

2.  A resolution plan for all failures, anomalies, and malfunctions
    encountered during Instrument integration

3.  Review of all environmental test plans and procedures

4.  Present detailed thermal vacuum and thermal balance test plans
    showing the observatory in the chamber, the hot and cold plates and
    shrouds, optical or thermal targets, RF coupling, star camera and
    sun sensor stimulators, QCMs, cold finger, planned test profile,
    cleaning and outgassing plan.

5.  The structural qualification/acceptance plan, showing the final
    modal analyses and coupled loads analyses results

6.  Define the predicted test limits for the components of the core
    system and instrument payload for:

    -Vibration

    -Thermal-Vacuum, Balance

7.  Justify that the planned test environments adequately demonstrate
    the Observatory Performance requirements without presenting a
    hazard, and without degrading Observatory performance and lifetime

8.  Present the plans to proceed to PSR (e.g. tests, activities,
    facilities, staffing, resources, schedule, flow)

##### 4.3.1.3.4 Pre-Ship Review

The contractor shall present at the PSR:

1.  Results of all the environmental tests and the latest Observatory
    Comprehensive Performance Test

2.  A resolution plan for all failures, anomalies, and malfunctions
    remaining open from the implementation

3.  Flight software verification status

4.  Any remaining open issues under the contract and their proposed
    resolution

5.  Shipping documentation status (e.g. shipping lists, manifests,
    containers, handling, transport, etc.)

6.  Observatory documentation status (e.g. final configuration lists,
    trend data, test reports, mass properties, system safety plan,
    life-limited items, equipment logs, cleanliness certification, and
    any other necessary documents)

7.  Receiving point plans - arrival time and place, storage, handling,
    points-of-contact, mechanical and electrical test plans and
    procedures

8.  An overview of the launch support plans (e.g. activities,
    facilities, staffing, resources, schedule, flow)

##### 4.3.1.3.5 Program Status Reviews

Program Status Reviews shall be conducted bi-monthly at the contractor's
facility. The contractor shall present the following information at the
Program Status Reviews:

1.  Status of work being performed including appropriate metrics.

2.  Milestone Monitoring - The contractor shall report on the status of
    progress made toward accomplishing each of his major milestones.
    Each report shall include a listing of major accomplishments and a
    discussion of any problems associated with each milestone as well as
    their resolution.

3.  Status of technical issues

4.  Changes to design parameters such as weight, power profile,
    communications, system performance, etc.

5.  Descriptions and status of technical problems and the resolutions.

6.  Subcontract technical performance

7.  Performance assurance status including non-conformance and failure
    report dispositions.

#### 4.3.1.4 Audits

The contractor shall support both formal and informal Government audits,
as ordererd through non-standard services, of the contractor's
activities, processes, products, documentation and data in order to
provide assurance to the Government that the program is being
implemented according to all requirements and specifications.

#### 4.3.1.5 Government Insight

All contractor and subcontractor internal data, reviews, audits,
meetings and other activities pertinent to the execution of a delivery
order shall be open to Government attendance. The contractor shall
provide the Government with reasonable and timely notification, to
facilitate Government attendance. Government support contractors may
also attend these reviews, audits, and meetings at the Government's
discretion.

### 4.3.2 Systems Engineering

The contractor shall perform the necessary systems engineering required
to ensure that the core system, options, and modifications meet all of
the performance, interface, and implementation requirements of the
mission-specific delivery order. The systems engineering effort shall
comprise the analyses of technical requirements, allocation of derived
system, core system, ground terminal and lower level requirements,
definition and maintenance of interfaces, and verification of all
defined and derived requirements.

#### 4.3.2.1 Requirements Analyses and Allocations

The contractor shall conduct complete analyses of the mission
requirements which fully establish, define, maintain and control
allocations. An appropriately updated index of analyses and allocations
shall be maintained by the contractor. The results of all analyses shall
be made available by the contractor for Government review at each
subsequent major program review.

#### 4.3.2.2 Interface Definition, Verification and Control

Using the results of the analyses and allocations of technical
parameters performed under the efforts described in Section 4.3.2.1, the
contractor shall specify all interfaces not explicitly defined by
Government specifications. These interfaces shall then be defined,
documented, verified and controlled for the duration of the delivery
order, by the contractor.

#### 4.3.2.3 Observatory/Launch Vehicle Interface

The contractor shall define and maintain all design interface
information between the observatory and the Government provided launch
vehicle. The contractor shall participate in the preparation and
maintenance of the Observatory-to-launch vehicle Interface Control
Documents (ICD). The responsibility for writing, maintaining, and
gaining approval of the ICD shall reside with the Government.

A flight ready mechanical fit check and an electrical interface
verification test of the spacecraft bus (or observatory) to the launch
vehicle interface shall be performed by the contractor prior to the
final flight mate to the launch vehicle interfaces. The mechanical fit
check and electrical interface verification test shall be performed at
the contractor's location prior to shipment to the launch site. The
Government shall supply a test payload attach fitting which simulates
the launch vehicle side of the interface.

The contractor shall provide the analytical models and shall perform all
analyses and tests required to ensure proper electrical, mechanical,
thermal, and operational compatibility between the observatory and the
Government provided launch vehicle and launch vehicle environments. The
contractor shall develop, maintain and provide all technical and
programmatic documentation required to ensure a successful launch
activity. This includes all observatory level safety-related
documentation as required by the launch site and launch range
organizations.

#### 4.3.2.4 Design and Performance Verification Analyses

The contractor shall perform and document all analyses of the data and
information from the design, qualification testing, acceptance testing,
compatibility testing and on-orbit testing of the contractor's hardware
and software which are required to ensure that the program will meet its
specifications and objectives.

### 4.3.3 Spacecraft Bus

The contractor shall produce and verify a spacecraft bus which meets all
of the requirements, specifications, and interfaces in accordance with
the mission-specific delivery order. The design shall be verified by a
combination of analyses and test on engineering models, prototype or
proto-flight hardware and software.

Prior to instrument integration the spacecraft bus shall under go a
comprehensive performance test to demonstrate readiness for observatory
level integration.

The contractor shall provide a spacecraft bus interface simulator for
use by the mission for interface verification. This item need not be
mission-specific but may be adaptable by the contractor to meet the
requirements of the mission-specific delivery order.

### 4.3.4 Implementation

#### 4.3.4.1 Spacecraft Bus Integration and Test (I&T)

The contractor shall integrate and test all spacecraft bus and payload
interface hardware and software. The spacecraft bus shall be tested with
calibrated and maintained Ground Support Equipment and shall be
compatibility tested with the ground control system as defined in the
delivery order.

#### 4.3.4.2 Observatory Integration and Test (I&T)

To the extent defined in the mission specific delivery order, the
contractor shall plan and conduct integration of the spacecraft bus and
payload to form an observatory. The contractor shall then plan, manage
and execute observatory level interface verification, system test,
environmental test program, and support mission payload specific tests
as defined in the delivery order.

#### 4.3.4.3 Spacecraft Bus/Observatory Storage

When required by the delivery order, the contractor shall provide
appropriate ground storage for the spacecraft bus or observatory prior
to launch. This activity shall encompass storage, storage maintenance,
and post-storage activities necessary to bring the spacecraft bus to
integration readiness or observatory to launch status. This shall
include, but not be limited to, the storage and maintenance of spare
parts as well as ground support equipment.

#### 4.3.4.3 Spacecraft Bus, Observatory and Ground Support Equipment Shipment

The contractor shall be responsible for the shipment of the spacecraft
bus and observatory between the places of manufacture, and integration
and test, and storage and launch in appropriate shipment containers. The
contractor shall provide for the shipment of necessary ground support
equipment required to support the spacecraft bus/observatory during each
phase of test, integration and launch preparation.

### 4.3.5 Launch & Operations

#### 4.3.5.1 Launch Support

The contractor shall provide launch support of the completed
observatory. This shall include launch vehicle interface definition,
design verification and management, observatory launch preparation and
launch support. The Government will make the final go/no-go decision for
launch. The launch support activity shall include, but not necessarily
be limited to, the following efforts:

1.  Launch Operations Planning - This effort requires the development
    and maintenance of interfaces with all entities that play a role in
    observatory launch. This involves coordinating, planning and
    performing all tasks which are necessary to implement a successful
    launch. The contractor shall provide technical and management
    support of meetings required to define launch related interfaces.

2.  Launch Simulations - This effort encompasses the conduct, analyses
    and evaluation of pre-launch training and simulations of the launch
    (through orbit insertion). Two training simulations plus one launch
    rehearsal are to be conducted.

3.  Pre-launch Integration and Test - The contractor shall perform all
    tasks necessary to integrate, test and prepare the observatory for
    launch at the launch site.

4.  Launch Operations - The contractor shall provide all required
    integration, safety, and engineering support to process the
    observatory through the ground processing facilities, launch
    facility and the launch vehicle. In addition, this effort shall
    encompass the contractor's efforts necessary to support the actual
    launch, post-launch orbit insertion, perform observatory
    initialization, deployments and preparation for on-orbit performance
    verification testing. This activity will be under Government
    direction from launch through separation of the observatory from the
    launch vehicle.

#### 4.3.5.2 Flight Operations Interfaces and Support

##### 4.3.5.2.1 Ground System Interface Definition

The contractor shall provide observatory compatibility with at least one
of NASA's available command and control systems (e.g. Space
Network/TDRSS, Deep Space Network, Ground Stations, or EOS Ground
Network), unless otherwise specified in the mission specific delivery
order.

The contractor shall work closely with NASA mission engineers to perform
communications, command, control and operational requirements trade
analyses.

The contractor shall provide all necessary interfaces to the ground
command, control and data system defined in the documents describing the
observatory requirements contained in the delivery order. This is to
include all necessary system documentation, interface control documents,
databases and test efforts.

##### 4.3.5.2.2 Ground System Training and Flight Operations Support

The contractor shall provide support to the mission operations team for
training and on-orbit initialization, checkout, performance verification
and anomaly resolution.

The contractor shall provide descriptions of flight software
functionality and spacecraft bus operation adequate to be used by the
flight operations team for flight operations.

The contractor shall provide a means to integrate Integration & Test
activities with the mission operations teams.

#### 4.3.5.3 On-Orbit Performance Verification

The contractor shall perform an on-orbit performance verification
program which will confirm that the spacecraft bus performance is in
accordance with the mission requirements, specifications, and
interfaces. As a minimum this shall include:

1.  Spacecraft Bus On-Orbit Check-Out - This effort shall be performed
    by the contractor to verify the post-launch performance and
    state-of-health of the spacecraft bus. All systems must be verified
    for proper function and performance.

2.  Spacecraft Bus/Ground Control and Data Systems Interface
    Verification - This effort shall be performed by the contractor
    after the spacecraft bus on-orbit performance and state-of-health
    have been confirmed. The purpose of this test is to verify proper
    operations of the spacecraft bus to ground system interfaces and to
    provide the necessary calibrations.

3.  30-Day On-Orbit Performance Report - The contractor shall prepare a
    brief report which summarizes the on-orbit performance of the
    spacecraft bus compared to its predicted performance for the mission
    after launch. Each subsystem is to be addressed and the performance
    of launch and flight operations crews are to be included. All
    pertinent issues affecting mission success shall be addressed. The
    extent of performance explanation required depends on the
    seriousness of the impacts that any problems identified may have on
    mission success. This report summarizes the spacecraft bus
    performance on-orbit after launch and check-out to determine initial
    mission success and completion payment milestone status.

#### 4.3.5.4 Support to On-Orbit Operations

The contractor shall provide support to resolve all on-orbit observatory
anomalies. This responsibility shall remain in place until the end of
the baseline mission life as defined in the delivery order.

### 4.3.6 Flight Software

#### 4.3.6.1 Software Maintenance

The contractor shall maintain the flight software along with the
environments and emulators necessary to develop and verify these systems
until the end of the program's baseline mission life as defined in the
delivery order. The delivery order may modify this requirement for
transfer of this responsibility to an alternate organization, in which
case the contractor shall support the transition with the necessary
ground based hardware, software, documentation and labor as required in
the delivery order. The contractor shall provide a description of how
ground and flight operational software will be maintained, supported,
verified, and managed to the end of the mission, and also describe the
use of personnel, what role others play, how others are to be trained
and by whom. In addition, the contractor shall describe configuration
control methods and safeguards, how emulators are accessed or dedicated,
how software corrections or changes are verified before uploading to the
spacecraft bus on-orbit. The contractor shall also describe the
documentation system, source code generation and use, and the methods of
maintaining equipment.

#### 4.3.6.2 Software Documentation

The contractor shall provide Flight Software Documentation for the
complete software lifecycle development to ensure reliability,
maintainability, and operability. This documentation will also be used
for maintenance of the system. Therefore, it shall also describe the
hardware aspects of the system which are necessary for operations and
maintenance of the emulator and its interface to external systems.