# B.4.2.2 -- Space Science and Earth-Observing SODA FSA

## 1. Overview

This SODA FSA provides the requirements for LOE tasks to be performed
for GSFC. This SODA FSA will define the GSFC requirements in detail.

## 2. Scope

This SODA FSA for GSFC will provide for work performed by the CSOC
contractor for efforts that are part of a Government-led effort. Types
of work in this category include performing studies and analyses of
mission operations alternatives during early mission definition;
developing new technology for application to mission operations and
mission certification testing; providing skills and teaming in support
of government-led development projects; providing skills in support of
government-led operations activities; providing quick-reaction analyses
and solutions to problems such as special testing and technology
demonstration requirements and isolation and resolution of spacecraft
anomalies that affect mission safety; and providing quick-reaction
support for tracking, data acquisition, and command in the suborbital
projects area.

This FSA defines work that is dynamic in nature and typically performed
in a team arrangement with the government and sometimes other
contractors. The government defines the overall requirements of each
effort and decides the respective responsibilities of each organization
participating in the effort. Intermediate and final deliverable items
are defined, but the nature of this work under this FSA requires
frequent changes to these baselines.

The analysis, development, and operations work defined here includes the
disciplines of mission management, systems engineering, mission control,
flight software, flight operations, science data processing, technology
development, flight dynamics, test tool development, and networks. The
work to be performed is defined generically in the following sections.
The SODA FSA table is included at the back of this FSA. The table lists
efforts that begin before contract start and end well past FY98 but are
included for clarity of scope. The table represents GSFC current
projection of work.

Each effort shall be performed by the contractor under this FSA via a
task order. A synopsis of each effort is provided in Section 8 of this
FSA.

## 3. Description

This section provides a general description of the types of work defined
in this FSA. In addition, it provide a breakdown of skills and technical
areas. This is intended as a high-level overview, and the details are
contained in the documents referenced in the GSFC SODA FSA table.

The CSOC contractor shall perform studies and analyses of mission
operations alternatives during premission definition. This shall include
performing tradeoffs, defining requirements, investigating COTS hardware
and software, and defining high-level system architectures. This work is
typically performed in conjunction with a team consisting of the flight
project and project scientists. This work may be planned efforts in
support of a new spacecraft or unplanned in response to an ad-hoc
request by a flight project, project scientists, university, or
industry.

The CSOC contractor shall develop new technologies that will ultimately
lead to significantly reduced mission operations costs. The contractor
shall participate in the identification of technology areas, perform
studies to demonstrate the need and potential benefits, perform the
technology development, and investigate commercialization of developed
technologies. The technology areas span the disciplines of mission
operations but include specialized areas such as VLSI circuit and
antenna/RF systems development. These are government-led activities with
frequent interaction between the government and the contractor. The
amount and types of technology development performed is dependent on
Research and Development (R&D) funding from Research Technology
Objectives and Plans (RTOP) sources and mission, enterprise, or external
sources.

The CSOC contractor shall develop systems and facilities for the Service
Elements, as well as for new Service Elements yet to be defined. The
development of these systems and facilities would occur under the SODA
FSA and would transition to a mission service or data service FSA upon
completion for general operations.

## 3.1 Government-Led Efforts

The contractor shall provide support for government-led activities.
These activities are typically for development of one-of-a-kind or
next-generation mission operations capabilities. They range from
development of a mission operations capability for small,
university-operated missions in the 1 to 5 staff-level range to
development of high-rate data capture and level-0 processing system for
Landsat in the 10 to 50 staff-level range. These efforts have aggressive
schedules and requirements and thus entail a higher degree of risk than
missions that are comparable to previous missions. These efforts have
significant government involvement in the definition and implementation
of requirements. It may also include support for government-led
operation efforts such as the in-house TRACE Flight Operations Team. The
contractor shall provide skills to complement the government's skills,
including systems engineering, software development, hardware
development, and flight operations. The range of skills also span
functional areas, including mission control, data processing, flight
dynamics, networks, flight software, and test support.

## 3.2 Quick-Reaction Efforts

The CSOC contractor shall provide support for quick-reaction analyses
for a variety of applications. These efforts are typically unplanned
and/or are responding to events such as a spacecraft emergency or ad-hoc
requirements such as a short planning cycle sounding rocket launch,
short turnaround mission-related facility modification or support of
existing customers using new technology, or technical approaches. The
contractor shall work with the government to perform analysis, develop
alternatives, and implement solutions if needed.

## 3.3 Skills

-   Project and mission management

-   Systems engineering

-   Research and analysis

-   Software design and development

-   Data base design and development

-   Hardware design and development

-   Flight operations

-   Operations analysis.

## 3.4 Technical Areas {#technical-areas .unnumbered}

-   Mission planning

-   Spacecraft command and control

-   Flight software

-   Science and engineering data processing and distribution

-   Test systems/test tool development

-   RF engineering

-   Communications engineering

-   Computer networks

-   Tracking and data acquisition

-   Flight dynamics

-   Flight operations.

## 4. Performance Requirements

Development, Analysis, and Support Services

The CSOC contractor shall provide development, analysis, and support
services in accordance with mission requirements.

Required Service: Provide development, analysis, and support services.

Std of Excellence: Contractor shall adhere to the baseline schedules and
requirements and reduce baseline costs as outlined in the appropriate
task orders.

Expectation: Contractor shall adhere to the baseline schedules,
requirements, and costs.

## 5. Integrated Table

The staffing levels indicated in the integrated table B.4.2.2-5.0
represent the current known SODA requirements. It is estimated that the
actual requirement will average 400 Onboard Equivalent (OBEs) per year
for contract years 3 thru 10.

Table B.4.2.2-5.0 Space Science and Earth-Observing SODA Missions,
Functions, and Tasks

  -------------------------------------------------------------------------------------------------------------------------------------------------
  Mission/Function/       Task       Task       Service       SOW          Reference       SODA   Calendar                                     
                                                Element                                           Year                                         
  ----------------------- ---------- ---------- ------------- ------------ --------------- ------ ---------- ---- ---- --- --- --- --- --- --- ----
  Task                    Start      Complete   Reference     Reference    Documents       Type   1          2    3    4   5   6   7   8   9   10

  SMEX                                                                                                                                         

  SAMPEX Flight           Contract   9/30/01    N/A           2.4.1.1b,                    G-L    1          1    1                            
  Operations Support      Start                               2.4.1.2b,                                                                        
                                                              2.4.1.3b,                                                                        
                                                              2.4.1.4b,                                                                        
                                                              2.4.1.6b                                                                         

  WIRE GS Development     Contract   4/1/99     A.1.27,       2.4.1.8.a,   Similar to      G-L    3                                            
                          Start                 A.1.17,       2.4.2.9.a    TRACE DMR; WIRE                                                     
                                                GA010, GA040,              DMR (future)                                                        
                                                GA050, CS010                                                                                   

  Future SMEX Development Contract   Contract   N/A           2.4.1.8.a,   Future SMEX DMR G-L    2          2    2    2   2   2   2   2   2   2
                          Start      End                      2.4.2.9.a                                                                        

  Landsat-7                                                                                                                                    

  Image Assessment System Contract   4/1/99     A.1.43,       2.4.1.8c     Landsat-7 IAS   G-L    6                                            
  Development             Start                 GA050, CS010               Element                                                             
                                                                           Specification                                                       

  Landsat-7 Simulator     Contract   12/31/98   A.1.59, 60,   2.3.3,       Landsat-7 DMR   G-L    3                                            
  Sustaining Support      Start                 CS010         2.4.1.1-5                                                                        

  ISTP                                                                                                                                         

  ISTP Mission Operations Contract   9/30/01    A.1.22,       2.4.1.1b     SOHO DMR; WIND  G-L    24         24   24                           
                          Start                 A.1.23,       2.4.1.2b     SIRD; POLAR                                                         
                                                A.1.26,       2.4.1.3b     SIRD; GEOTAIL                                                       
                                                A.1.25,       2.4.1.4b     SIRD; IMP-8                                                         
                                                A.1.52,       2.4.1.6b     MRR; ISTP CDHF                                                      
                                                GA040, GA010,              Requirements                                                        
                                                CS010                      Specification                                                       

  MIDEX                                                                                                                                        

  IMAGE GS Development    Contract   3/1/00     GA010,CS010   2.4.1.8.a    IMAGE MRR       G-L    2          1                                 
                          Start                                                                                                                

  MAP GS Development      Contract   6/1/00     GA010,CS010   2.4.1.8.a    MAP MRR         G-L    2          2                                 
                          Start                                                                                                                

  Future MIDEX            11/99      Contract   GA010,CS010   2.4.1.8.a    Future MIDEX    G-L               3    5    5   5   5   5   5   5   5
  Development                        End                                   DMR                                                                 

  Technology              Contract   Contract   GA010,CS010   2.4.1.8.a    N/A             G-L    2          2    2    2   2   2   2   2   2   2
  Development/Insertion   Start      End                                                                                                       
  -------------------------------------------------------------------------------------------------------------------------------------------------

<table style="width:100%;">
<colgroup>
<col style="width: 15%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 11%" />
<col style="width: 10%" />
<col style="width: 16%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="17">Table B.4.2.2-5.0 (Cont’d)</th>
</tr>
<tr class="odd">
<th>Mission/Function/</th>
<th>Task</th>
<th>Task</th>
<th>Service Element</th>
<th>SOW</th>
<th>Reference</th>
<th>SODA</th>
<th colspan="10">Calendar Year</th>
</tr>
<tr class="header">
<th>Task</th>
<th>Start</th>
<th>Complete</th>
<th>Reference</th>
<th>Reference</th>
<th>Documents</th>
<th>Type</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4</th>
<th>5</th>
<th>6</th>
<th>7</th>
<th>8</th>
<th>9</th>
<th>10</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td colspan="17">Technology/Other Mission Support</td>
</tr>
<tr class="even">
<td>New Millennium EO-1</td>
<td>Contract Start</td>
<td>9/30/99</td>
<td>GA010,CS010</td>
<td>2.4.1.8.a</td>
<td>EO-1 MRR</td>
<td>G-L</td>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Future Missions</td>
<td>5/1/99</td>
<td>Contract End</td>
<td>GA010,CS010</td>
<td>TBD</td>
<td>Future DMR</td>
<td>G-L</td>
<td>1</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
</tr>
<tr class="even">
<td colspan="17">Tools Development</td>
</tr>
<tr class="odd">
<td>Adv. S/C Simulator</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.18, GA050, CS010</td>
<td>2.3.3</td>
<td>TPOCC Advanced Spacecraft Simulator Systems Requirements
Specification</td>
<td>G-L</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
</tr>
<tr class="even">
<td>Next-Generation Test Tool and Simulator Development</td>
<td>Contract Start</td>
<td>10/1/01</td>
<td>A.1.59, CS010</td>
<td>2.3.3, 2.4.1</td>
<td>Simulations and Compatibility Test Branch Functional Capabilities
Document</td>
<td>G-L</td>
<td>8</td>
<td>8</td>
<td>4</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>RFSOC Systems Development</td>
<td>Contract Start</td>
<td>10/1/01</td>
<td>A.1.60, CS010</td>
<td>2.3.3</td>
<td>SOC/RFSOC Summary</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Portable Telemetry Processor Technology</td>
<td>Contract Start</td>
<td>10/1/01</td>
<td>A.1.62, CS010</td>
<td>2.3.3</td>
<td>PTP Users Guide; PTP Functional Requirements Document</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Compatibility Test System Development</td>
<td>Contract Start</td>
<td>10/1/01</td>
<td>A.1.61, GA050, CS010</td>
<td>2.3.3</td>
<td>Functional and Performance Requirements for Compatibility Test
Van</td>
<td>G-L</td>
<td>3</td>
<td>3</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Mission Planning System Technology Development</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.17, A.1.18, GA050, CS010</td>
<td>2.3.3</td>
<td>MOPSS Requirements Document</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
</tr>
<tr class="odd">
<td colspan="17">Mission Operations Technology Development</td>
</tr>
<tr class="even">
<td>MOC Technology Integration</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.17, A.1.18, GA050, CS010</td>
<td>2.3.3</td>
<td>N/A</td>
<td>G-L</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
</tr>
<tr class="odd">
<td>MOC Reusable System Components</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.17, A.1.18, GA050, CS010</td>
<td>2.3.3</td>
<td>N/A</td>
<td>G-L</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
</tr>
<tr class="even">
<td>Data Processing and Distribution Technology</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.43, A.1.44, A.1.50, GA010,GA040, GA050, CS010</td>
<td>2.3.3, 2.4.1.6</td>
<td>N/A</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
</tr>
<tr class="odd">
<td colspan="17">Mission Operations Support</td>
</tr>
<tr class="even">
<td>Mission Operations Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.3 – A.1.63, GA010,GA030, GA040, GA050, CS010</td>
<td>2.3, 2.4</td>
<td>N/A</td>
<td>Q-R</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
<td>18</td>
</tr>
<tr class="odd">
<td colspan="17">Technology Initiatives</td>
</tr>
<tr class="even">
<td>VLSI R&amp;D</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.68, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering</td>
<td>G-L</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
<td>16.5</td>
</tr>
<tr class="odd">
<td>VLSI Technology Applications</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.67, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
</tr>
<tr class="even">
<td>Java GenSAA</td>
<td>Contract Start</td>
<td>9/30/99</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>http://groucho.gsfc.nasa.gov/Code_520/Code_<br />
522/Projects/GenSAA/</td>
<td>G-L</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>LOGOS</td>
<td>Contract Start</td>
<td>9/30/00</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>http://groucho.gsfc.nasa.gov/agents/documents/
code522/logos.pdf</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Agents/Hail</td>
<td>Contract Start</td>
<td>9/30/01</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>An Agent-Oriented Approach to Automated Mission Operations, Walt
Truszkowski/GSFC &amp; Jide Odubiyi/Loral Aerosys, SpaceOps 94
Conference; “Remote Agents, Engineering Directorate (700), Statement of
Work (SOW)”</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Knowledge Discovery and Data (KDD) Mining</td>
<td>Contract Start</td>
<td>9/30/02</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Email message from Dr. Jon Smid of Morgan State Univ. to Walt
Truszkowski/Code 522.2</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>WAVE</td>
<td>Contract Start</td>
<td>9/30/00</td>
<td>A.1.18, GA050, CS010</td>
<td><p>2.3.3, 2.4.1.8(b), 2.4.1.9</p>
<p>(2.1.6 services not required)</p></td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>AFPS</td>
<td>Contract Start</td>
<td>9/30/99</td>
<td>CS010</td>
<td><p>2.3.3, 2.4.1.8(b), 2.4.1.9</p>
<p>(2.1.6 services not required)</p></td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering</td>
<td>G-L</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Technical Support Office</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.66, 67, 68, 70, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering</td>
<td>G-L</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
<td>3.4</td>
</tr>
<tr class="odd">
<td>DSTL Lab Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering</td>
<td>G-L</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
<td>4.7</td>
</tr>
<tr class="even">
<td>IMDC</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.71, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b)</td>
<td><p>Operations Plan for the Integrated Mission Development
Center;</p>
<p>http://imdc.nasa.gov/</p></td>
<td>G-L</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
<td>4.5</td>
</tr>
<tr class="odd">
<td>NGST SEA</td>
<td>Contract Start</td>
<td>9/30/04</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Presentation: “Prototype Project for NGST Scientist’s Expert
Assistant”, June 10, 1997, by Julie Breed/ Code 520</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>IFMP</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td><p>Consolidated NMOS GSA E.3 Data Systems Engineering</p>
<p>http://booster.nasa.gov: 443</p></td>
<td>G-L</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
<td>2.5</td>
</tr>
<tr class="odd">
<td>Model-Based Reasoning</td>
<td>Contract Start</td>
<td>9/30/01</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>Knowledge-Based Trend Analysis – Trends –
http://groucho.gsfc.nasa.gov/ames/trends</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Enterprise Integration</td>
<td>Contract Start</td>
<td>9/30/02</td>
<td>A.1.66, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>(New start – no documents)</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Adaptive Science Data Processing</td>
<td>Contract Start</td>
<td>9/30/00</td>
<td>A.1.67-70, CS010, GA050</td>
<td>2.3.3</td>
<td>Consolidated NMOS GSA E.3 Data Systems Engineering; Email message
from Mark Stephens/521 to Nick Speciale/Code 521</td>
<td>G-L</td>
<td>4.3</td>
<td>4.3</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Technology Development and Analysis Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.66, 67, 68, 70, GA050, CS010</td>
<td>2.1.6(a), 2.3.3, 2.4.1.8(b), 2.4.1.9</td>
<td>N/A</td>
<td>Q-R</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
</tr>
<tr class="odd">
<td colspan="17">Networks Development</td>
</tr>
<tr class="even">
<td>CLASS Sustaining Engineering and Mission Analysis</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.79, CS010</td>
<td>2.4.2.9</td>
<td>CLASS ACRS/TLAS Operators Manual and Ref., CLASS Design Doc.,
Guidelines for Preparation of User/TDRS RF ICD</td>
<td>G-L</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
<td>12</td>
</tr>
<tr class="odd">
<td>NCC98</td>
<td>Contract Start</td>
<td>12/31/01</td>
<td>A.1.73, CD200, CS010</td>
<td>2.4.2.9</td>
<td>NCCDS System Requirements, 1998</td>
<td>G-L</td>
<td>30</td>
<td>20</td>
<td>10</td>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>NCC CCSR</td>
<td>Contract Start</td>
<td>12/31/02</td>
<td>A.1.73, CD200, CS010</td>
<td>2.4.2.9</td>
<td>NCC F&amp;PR, SPSR Ops Concept, NCCDS System Requirements, 1998</td>
<td>G-L</td>
<td>30</td>
<td>30</td>
<td>30</td>
<td>10</td>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>LSD CMORE</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.90, CS030, CS010</td>
<td>2.4.2.9</td>
<td>LSD Standard Practices, CMORE Toolbench Training Workbook</td>
<td>G-L</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
</tr>
<tr class="even">
<td>WSC – mods for TDRS H,I,J</td>
<td>Contract Start</td>
<td>12/31/02</td>
<td>A.1.74, CD200, CS010</td>
<td>2.4.2.9</td>
<td>SOW for TDRSS H,I,J</td>
<td>G-L</td>
<td>17</td>
<td>14</td>
<td>3</td>
<td>6</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>NPAS Sustaining Engineering and Network Analysis</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.80, CS010</td>
<td>2.4.2.9</td>
<td>NPAS User’s Guide</td>
<td>G-L</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
</tr>
<tr class="even">
<td>Transponder Characterization</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.83, GA050, CS010</td>
<td>2.4.2.9</td>
<td>Performance and Design Req. for the 4th Gen. TDRS Transponder</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
</tr>
<tr class="odd">
<td>Antenna Range Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.85, GA050, CS010</td>
<td>2.4.2.9</td>
<td>STDN Test and Simulation Support Plan</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
</tr>
<tr class="even">
<td>Lab Technician Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.82, CS010</td>
<td>2.4.2.9</td>
<td>MBR Operations Transition Plan</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
</tr>
<tr class="odd">
<td>Multifunction Receiver/Software Programmable Adv. Receiver
(MFR-R/SPAR)</td>
<td>Contract Start</td>
<td>12/31/02</td>
<td>A.1.91, CS030, CS010</td>
<td>2.4.2.9</td>
<td>GN RER Upgrade: Requirements, Architecture, and Design</td>
<td>G-L</td>
<td>4</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="17">Flight Dynamics</td>
</tr>
<tr class="odd">
<td>Software Engineering Lab</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>An Overview of the Software Engineering Laboratory; Manager’s
Handbook for Software Development; Recommended Approach to Software
Development</td>
<td>G-L</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
</tr>
<tr class="even">
<td>Systems Engineering and Technology Evaluation</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>GEODYN COTS Evaluation Results</td>
<td>G-L</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
</tr>
<tr class="odd">
<td>GPS-Base System Development</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>GPS Modular (GMOD) Software Feasibility Analysis Report</td>
<td>G-L</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
</tr>
<tr class="even">
<td>Advanced Mission Planning Software Development</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>Automated Maneuver Planning Tool Operations Concept and
Requirements; FDDS Generalized Support Software Specification
Concepts</td>
<td>G-L</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
<td>8</td>
</tr>
<tr class="odd">
<td>Advanced Navigation Software Development</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>FDDS Navigation Support Component Operations Concept</td>
<td>G-L</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
</tr>
<tr class="even">
<td>Advanced Reuse and Software Architecture Development</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>FDDS GSS Specification Concepts</td>
<td>G-L</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
</tr>
<tr class="odd">
<td>Attitude Ground Support System (4 missions/yr)</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA040</td>
<td>2.4.1.3</td>
<td>FAST Attitude Ground Support System Software Development
History</td>
<td>G-L</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
</tr>
<tr class="even">
<td>Orbit Determination and Acquisition Data Systems (4
missions/yr)</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>Trajectory Computation and Orbital Products System (TCOPS);
Mathematical Theory of the GTDS; GTDS User’s Guide</td>
<td>G-L</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
</tr>
<tr class="odd">
<td>Mission Specific and Institutional Systems Maintenance/Sustain­ing
Engineering (8 mission/yr)</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>Operational Software Maintenance Process</td>
<td>G-L</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
<td>10</td>
</tr>
<tr class="even">
<td>Flight Dynamics Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>N/A</td>
<td>Q-R</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
</tr>
<tr class="odd">
<td>Flight Dynamics Analysis Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.93, GA010, GA040, CS010</td>
<td>2.4.1.3</td>
<td>http://fdd.gsfc.nasa.gov/ fdd550.html</td>
<td>G-L</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
<td>9</td>
</tr>
<tr class="even">
<td colspan="17">Special Services for Mission Management</td>
</tr>
<tr class="odd">
<td>Mission Operations Procedure Analysis</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>Q-R</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
</tr>
<tr class="even">
<td>Interagency Tracking and Communications Operations Panel (ITCOP)
Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
</tr>
<tr class="odd">
<td>Frequency and Spectrum Management</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
</tr>
<tr class="even">
<td>Human Flight Mission Planning and Coordination</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
<td>10.0</td>
</tr>
<tr class="odd">
<td>Robotic Flight Mission Planning and Coordination</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
<td>7</td>
</tr>
<tr class="even">
<td>Mission Model Data Base Maintenance</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.1, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
</tr>
<tr class="odd">
<td>Mission Requirements Management</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.1, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
</tr>
<tr class="even">
<td>Agreements Management Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.1, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
<td>1</td>
</tr>
<tr class="odd">
<td>MO&amp;DSD Resident Office at JSC</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
<td>3</td>
</tr>
<tr class="even">
<td>Information Technology Maintenance and Support</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.1, CS010</td>
<td>2.4.1.9</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
<td>2.0</td>
</tr>
<tr class="odd">
<td>Mission Planning Tool Development</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.2, CS010</td>
<td>2.4.1.8.d</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
</tr>
<tr class="even">
<td colspan="17">Development for Mission Management</td>
</tr>
<tr class="odd">
<td>Development of Mission Management Data Base Systems</td>
<td>Contract Start</td>
<td>9/30/99</td>
<td>A.1.1, CS010</td>
<td>2.4.1.8.d</td>
<td>Mission Management Office Support Requirements Document</td>
<td>G-L</td>
<td>2.0</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Development of Mission Management Tools</td>
<td>Contract Start</td>
<td>9/30/99</td>
<td>A.1.2, CS010</td>
<td>2.4.1.8.d</td>
<td>Mission Management Office Support Requirements Document</td>
<td>Q-R</td>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Information Dissemination and Distribution Tools</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>A.1.1, CS010</td>
<td>2.4.1.8.d</td>
<td>Mission Management Office Support Requirements Document</td>
<td>Q-R</td>
<td>2.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
<td>1.0</td>
</tr>
<tr class="even">
<td colspan="17">Systems Engineering</td>
</tr>
<tr class="odd">
<td>500 Policy</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>CS010</td>
<td>2.3</td>
<td></td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
</tr>
<tr class="even">
<td>500 Configuration Management</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>CS010</td>
<td>2.3</td>
<td>MO&amp;DSD Configuration Management Plan</td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
</tr>
<tr class="odd">
<td colspan="17">Wallops Flight Facility</td>
</tr>
<tr class="even">
<td>Instrumentation Engineering Laboratory</td>
<td>Contract Start</td>
<td>9/30/02</td>
<td>A.1.113, CS010</td>
<td>2.4.2.9</td>
<td><p>Operations and Safety Directive for Red Tigress III, DRW-1632,
Aug 1996; Operations and Safety Directive for Pegasus Minisat Launch
Campaign,</p>
<p>ORO-2349, March 1997; EOS AM-1 Detailed Mission Requirements;
Landsat-7 Detailed Mission Requirements</p></td>
<td>G-L</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td>11</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="17">EOS Development</td>
</tr>
<tr class="even">
<td>EOSDIS Test System</td>
<td>Contract Start</td>
<td>10/1/04</td>
<td>A.1.118, CS010</td>
<td></td>
<td></td>
<td>G-L</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>1</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Level-1 Product Generation System</td>
<td>Contract Start</td>
<td>12/1/98</td>
<td>A.1.43, GA050, CS010</td>
<td>2.4.1.8c</td>
<td>Landsat-7 DMR, Landsat-7 System Specification, Landsat-7 Data Format
Control Book Volumes 1-4</td>
<td>G-L</td>
<td>8</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="17">Implementation Team</td>
</tr>
<tr class="odd">
<td>Implementation Team</td>
<td>Contract Start</td>
<td>Contract End</td>
<td>All</td>
<td>2.4.1.9</td>
<td>N/A</td>
<td>Q-R</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
<td>2</td>
</tr>
<tr class="even">
<td><strong>Totals – Current Requirements</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>419</strong></td>
<td><strong>376</strong></td>
<td><strong>340</strong></td>
<td><strong>280</strong></td>
<td><strong>250</strong></td>
<td><strong>244</strong></td>
<td><strong>242</strong></td>
<td><strong>242</strong></td>
<td><strong>242</strong></td>
<td><strong>242</strong></td>
</tr>
<tr class="odd">
<td><strong>Future Requirements</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>24</td>
<td>60</td>
<td>120</td>
<td>150</td>
<td>156</td>
<td>158</td>
<td>158</td>
<td>158</td>
<td>158</td>
</tr>
</tbody>
</table>

## 5.1 GSFC SODA FSA TABLE DESCRIPTION

Table B.4.2.2-5.0 contains information about the scope of effort
required to support GSFC for the SODA. This section describes the
elements of the table in detail. Each row of the table represents a
collection of work in a mission or functional area.

### 5.1.1 Mission/Function/Task

This column contains the names of the mission and/or functional area
(shaded) and the names of the individual efforts contained in this FSA.

### 5.1.2 Task Start

This column contains the start date of the particular effort under this
FSA. The earliest date shown is Contract Start. Most of these tasks
would have started earlier and the CSOC contractor will be assuming the
responsibility of those tasks.

### 5.1.3 Task Complete

This column contains the completion date of the particular effort under
this FSA.

### 5.1.4 Service Element Reference

This column contain reference(s) to Service Elements from which this
effort will require services. For example, the WIRE GS Development
effort will utilize the SMEX MOC Service Element (Service Element
A.1.17; NSE GA050) during integration of hardware and software developed
under this effort. It will be installed into the existing SMEX MOC
Service Element (Service Element A.1.27; NSE GA040) during the effort
for integration, mission readiness testing, and transition to
operations.

### 5.1.5 SOW Reference

This column contains references to the WBS in the CSOC SOW under which
these efforts are authorized. An example is 2.4.1.8.c, which represents
a mission services development activity that is an ongoing development
that will be transferred from the current development contractor to the
CSOC contractor for completing the development phase and for performing
the M&O of the developed system or facility.

### 5.1.6 Reference Documents

This column contains references to documents, if any, that further
describe the nature and scope of work under this effort. For those
efforts with later start dates, documentation may not be available.

### 5.1.7 SODA Type

This column contains a designation of either Quick Reaction (Q-R) or
Government-Led (G-L) task order, depending on the type of effort.

## 5.2 Facilities

The work defined under this FSA will use either existing facilities
defined in the Service Elements or will require new facilities. The
result of some of these efforts will be new Service Elements that will
require support under the mission services, data services, or center
unique services. This support may be required during performance of the
work under this FSA for services such as systems administration, library
support, hardware/software vendor maintenance, and training.

## 5.3 CSOC and HST Mission Contract(s) Interrelationship

The government will transition services supporting the operation of the
HST MOC from the Consolidated NMOS contract upon the inception of CSOC.
This transition shall encompass management of the HST MOC facilities and
equipment, along with related training, documentation, logistics, CM,
equipment scheduling, systems and network management, and institutional
support from GSFC's Flight Dynamics Facility, Sensor Data Processing
Facility, and other GSFC MO&DSD organizations.

GSFC's HST mission contractor(s) will retain responsibility for the
operation of the HST spacecraft, including planning and preparation for
HST servicing missions. The mission contractor(s) will perform
integrated real-time command and control, telemetry analysis and
attitude determination, and sensor calibration. The mission
contractor(s) will also retain responsibility for the development of the
HST Vision 2000 ground system, including integration and testing of the
system.

Operation and maintenance of the Vision 2000 systems will transition to
CSOC or an appropriate alternative vehicle only after the system is
declared fully operational in the HST MOC. This transition will affect
operation and maintenance of the Vision 2000 operational and test
equipment and facilities as well as software and hardware vendor
maintenance and licensing.

## 

## 5.4 Future Trends

The support requirements detailed in the SODA FSA integrated table
B.4.2.2-5.0 represents the current known set of work under this FSA.
Additional requirements for support, such as development of ground
systems capabilities for missions not yet adequately defined, will arise
before the start of CSOC and during execution of the contract. An
example would be a new spaceflight mission on which GSFC has teamed with
a science team in the development of a new ground system to support a
technology satellite. The exact support requirement, if any, for CSOC
will not be known until after the mission is selected as a new start.
The mission set contains those missions that are candidates for
requiring CSOC support. As the exact requirements are identified, this
FSA will be updated appropriately and new task orders will be generated.

## 6. SODA Task Synopses

This section provides a brief description of each group of tasks (e.g.,
SMEX) followed by the task names (e.g., TRACE GS Development, WIRE GS
Development, etc.) listed in the integrated table B.4.2.2-5.0. Each
description contains the scope of effort to be provided by the CSOC
contractor.

## 6.1 SMEX

The CSOC contractor will provide support for an in-house civil servant
team that is developing the WIRE and SMEX-lite ground data systems. This
task includes systems engineering, hardware and software development,
and integration and testing support. The contractor will not provide
support for flight software maintenance. The contractor will also
provide support during launch and early orbit and through in-orbit
checkout. These tasks will utilize the SMEX MOC facilities and the
services provided to those facilities under the mission and data
services FSAs. Civil servants will operate the ground system in support
of mission operations. The projected launch dates for WIRE and SMEX-lite
missions are no earlier than September 1998.

The CSOC contractor shall provide training to Bowie State University
personnel relative to SAMPEX operations. The contractor shall provide
other assistance as necessary.

The CSOC contractor shall provide training to the WIRE civil service
Flight Operations Team (FOT) in accordance with Mission Director
direction and the SMEX Training Plan. The contractor will provide
transition support to the WIRE FOT and a single point of contact to
coordinate and resolve ground system operations engineering/testing
issues for all missions operated from the SMEX MOC.

## 6.2 Landsat-7

**Image Assessment System (IAS) Development.** The IAS development will
provide a system that will support image processing and quality
assessment for Landsat-7 data. This development effort is a
collaborative government and CSOC contractor effort, with the contractor
providing support for systems engineering and software development. The
IAS will be installed at the Earth Resource Observation System (EROS)
Data Center in Sioux Falls, South Dakota, and will not be operated and
maintained under the CSOC contract. Development activities for the IAS
involve the design, implementation, integration, testing, and
installation of software and hardware. This development is being
currently performed under the Systems Engineering and Analysis Support
(SEAS) contract in conjunction with an in-house development team. The
CSOC contractor will be required to continue this development effort
until a yet to be specified number of days beyond the Landsat-7 launch,
currently scheduled for May 1998.

**Landsat-7 Simulator Sustaining Support.** The Landsat-7 simulator is
currently under development as a ground systems test tool, an aid to
flight software testing and verification, and as a potential FOT
training tool. The simulator incorporates flight software modules for
execution of critical functions and where accuracy of algorithmic
solutions is paramount. The basic platform is Virtual Memory Extension
(VME) based, with a MIL-STD-1750A (software emulator) embedded in the
architecture, to emulate the Landsat-7 flight systems functionality and
run flight software. This simulator is the only simulator being built
for the project and is considered launch critical. Use of the simulator
is scheduled at L--20 months for ground systems support and is required
later, in a portable version, to be available for GN station testing and
or launch site interface verification at the Western Range launch site
(VAFB). Launch is currently scheduled for early Summer of 1998.
Simulator operations and maintenance is required for at least 90
calendar days after Landsat-7 launch, unless extended. Handover to NOAA
is planned at Launch +91 (L+91) days. Requirements for support beyond
that time are TBD. Support under CSOC should be planned to extend
through September 30, 1998 (end of FY98), with a contingency of 3 months
(first quarter FY99). Support utilities (software) and systems M&O are a
requirement, in addition to development, acceptance testing, and
deployment of the simulator. The simulator development area is located
in Bldg. 25, Room N-155.

## 6.3 ISTP

**SOHO Science Operations Coordinator (SOC).** The CSOC contractor will
provide a SOC for SOHO operations. The SOC's duties include science
planning support, science activities coordination, and ECS operations.
The contractor-provided SOC is one of three SOCs. The European Space
Agency and the ISTP project each provide a SOC who works in conjunction
with the SOC provided by the contractor.

## 6.4 MIDEX

The CSOC contractor will support the in-house civil servant team in the
implementation of the IMAGE, MAP, and future MIDEX ground systems,
including developing and integrating systems for scheduling, command
management, real-time operations, flight dynamics, data processing,
engineering analysis, and science browse data production. The effort
includes systems engineering, prototyping, software development,
integration of COTS and other existing systems, and testing.

## 6.5 Technology Mission Support

The CSOC contractor will support the in-house civil servant team in the
implementation of the ground systems for missions such as New Millenium
EO-1, including developing and integrating systems for scheduling,
command management, real-time operations, flight dynamics, data
processing, engineering analysis, and science data production. The
effort includes systems engineering, prototyping, software development,
integration of COTS and other existing systems, and testing. The
projected launch date for EO-1 is 1999. Other missions, will be added to
this area as the need is identified for contractor support of
in-house-developed systems.

## 6.6 Continuing and Sustaining Development

**Adv. S/C Simulator.** The contractor shall support a civil service
team in the development of advanced test and simulations tools.

**Next-Generation Test Tool and Simulator Development.** The CSOC
contractor shall support development of new technology test tools and
simulators for future missions. The test tools and simulators (fixed and
portable) will provide short-term and dynamic requirements support to
ground systems developers, allow for fault isolation and interface
verification, and provide testing support, which is independent of
vendors, systems developers, and other support elements. These test
tools can be used for network interface verification, end-to-end
testing, and RF testing in conjunction with an RF front end (such as the
RFSOC) for launch site and other remote site supports.

**RFSOC Systems Development.** The CSOC contractor shall provide support
for development of new technology RFSOC systems that can support future
RF testing for the TDRS and other missions. RF testing comprises
communication experiments, end-to-end testing, RF compatibility testing,
and development of new testing systems that can support higher operating
frequencies and data rates. Advanced testing concepts, including
evaluation of COTS technology for integration/ insertion into the RF
testing process, shall be evaluated and developed.

**Portable Telemetry Processor System Development.** The CSOC contractor
shall support development of new technology and capabilities for the
portable telemetry processor.

**Compatibility Test Systems Development and Automation.** The CSOC
contractor shall support the development and automation of new
technology compatibility test systems test and analysis systems.
Examples include data (including telecommand) and telemetry
encoder/decoder design and implementation; high rate/wide bandwidth data
capture/data transmission/data generation systems for testing and
verification of telemetry data links for SN and ground-based network
users; fiber-optics interfaces and data links for digital data and RF
transmission, as applied to compatibility testing and mission prelaunch
support advanced testing concepts, evaluation of COTS technology for
integration/insertion into the compatibility test/mission readiness
certification process.

**Mission Planning Systems Development.** The CSOC contractor shall
support a civil service team in the development of mission planning
systems technology.

## 6.7 Mission Operations Support

The CSOC contractor shall support the Mission Director during preflight
and in-flight phases. This support will include quick-reaction analyses
for a variety of applications. These efforts are typically unplanned
and/or are responding to events such as a spacecraft emergency or ad-hoc
requirements such as support of existing customers using new technology
or technical approaches. The contractor shall work with the government
to perform analysis, develop alternatives, and implement solutions if
needed.

## 6.8 Mission Operations Technology Development

**MOC Technology Integration.** This effort evaluates commercial
products that have potential application into mission operations. The
contractor shall support a civil service team in the continued
development, evaluation, and integration of advanced technology.

**MOC Reusable System Components.** This task will involve the research,
technology evaluation, COTS evaluation, requirements definition, and
development of next-generation MOC reusable subsystems, components, etc.

**Data Processing and Distribution Technology.** Development activities
for the Data Distribution Systems involve the design, implementation,
integration, testing, and installation of software that performs data
storage and distribution of science data products. This development is
being currently performed under the SEAS contract. The CSOC contractor
will be required to continue this R&D effort. New missions that select
the DDS as part of their ground system architecture will require
development support for mission-specific requirements.

Development activities for the Data Processing Systems involve the
design, implementation, integration, testing, and installation of
software that performs Level-0 processing for the ACE, TRACE, and WIRE
missions. This development is being currently performed under the SEAS
contract in conjunction with an in-house development team. The CSOC
contractor will be required to continue this development effort for
these missions. New missions that select the DPS as part of their ground
system architecture will require development support for
mission-specific requirements.

## 6.9 Technology Initiatives

The CSOC contractor will provide advanced support in emerging technology
areas such as Artificial Intelligence (AI), autonomous systems,
Information Management Systems (IMS), parallel data processing, software
engineering, human factors, VLSI circuit design, and high data rate
systems. Such support will be required in the development of autonomous
ground control and mission operations systems, high performance data
capture, processing and archiving systems, intelligent information
systems, and cost-effective software development tools and systems.

**VLSI R&D.** This R&D includes new VLSI circuit technologies applicable
to space mission ground control and space communications systems.

**VLSI Technology Applications.** This includes
development/configuration/application of existing system components in
the short term for space mission ground control and space
communications.

**VLSI Long Term.** This includes development of advanced technology
prototypes of systems and system components for possible future space
mission ground control and space communications.

**Java GenSAA.** This includes development of control center monitoring
and control capabilities using Java and incorporating advanced
distributed computing concepts.

**Lights-Out Ground Operations System (LOGOS).** This includes research
into multiagent technologies for lights-out ground control systems.
Advanced concepts of autonomy and intelligence will be explored.

**Knowledge Discovery and Data (KDD) Mining.** This includes research on
intelligent agents to derive application domain knowledge from
domain-specific data bases and to derive new knowledge from existing
related knowledge bases.

**World Wide Web (WWW), Artificial Intelligence and Virtual Environments
Explorations (WAVE).** Wave includes R&D support for prototyping
applications of the Web, AI, and virtual environments to demonstrate
advanced concepts for intelligent ground and space systems. The CSOC
contractor also provides system administrative support. This is a R&D
activity managed by Code 511.

**Automated Forms Processing System (AFPS).** AFPS includes research
into the Web technologies and its use for forms-related applications.
The CSOC contractor also provides systems administrative support for
existing systems.

**Technical Support Office (TSO).** This includes R&D support provided
by the CSOC contractor to teams of civil servants and contractor
personnel working on government-led R&D projects.

**DSTL Support.** This includes R&D support provided by the CSOC
contractor to teams of civil servants and contractor personnel working
on government-led R&D projects.

**Integrated Mission Design Center (IMDC).** This includes research into
new Web-distributed system technologies, hardware-in-the-loop
simulations, and groupware tools and software development for discipline
engineers. The CSOC contractor also maintains the servers and data
bases.

**Next-Generation Space Telescope Scientist's Expert Assistant (NGST
SEA).** The NGST SEA provides R&D of AI applications to support NGST
scientists.

**Model-Based Reasoning.** Research on model-based reasoning is directed
at eventual applications in intelligent ground and space systems.
Model-based reasoning approaches are developed for trending capabilities
for the SAIL system at the U.S. Naval Academy.

**Enterprise Integration.** This includes research on concurrent
engineering approaches for development of complex systems.

**Adaptive Science Data Processing.** This includes research on ways to
apply reconfigurable processing technology techniques to processing of
mission science data.

**Technology Development and Analysis Support.** This includes
quick-reaction R&D support by CSOC contractor to teams of civil servants
and contractor personnel working on government-led R&D projects.

## 6.10 Networks Development

The contractor shall perform a wide range of development and analysis
tasks in support of the operations and maintenance activities outlined
in the Telemetry, Data, Acquisition, and Command (TDA&C) Data Services
FSA (B.2.A) and Network Management Data Services FSA (B.2.C) for the
GSFC Spaceflight Tracking and Data Network (STDN). STDN includes the
Space Network (SN) and the Ground Network (GN). Scheduling and the use
of these networks, along with other NASA and non-NASA networks are
coordinated through the Network Control Center (NCC). Development and
analysis efforts associated with the NCC, as well as those in support of
the Logistics Support Depot (LSD), are also included. The specific areas
are listed below. All work will be accomplished under functional
directives, engineering orders, and/or technical change notices.

**CLASS Development.** CLASS Development provides the development of new
software capabilities to support new analyses as required or enhance
current capabilities. Development will be done jointly by the contractor
and the civil servants. All CLASS analyses, CLASS software development
specifications, CLASS software development plans, CLASS software
validation results, CLASS data base developments, and other CLASS items
resulting from work under this task are the exclusive property of the
U.S. Government and must be submitted directly to the CLASS Project
Office for approval before removal from or installation in the CLASS
Facilities at NASA GSFC. Although, the new software will have to be
reviewed and validated by both parties, the CSOC contractor shall
maintain the CM of the CLASS software and tools.

**NCC CCSR.** The Configuration and Control Segment (CCS) of the Network
Control Center Data System (NCCDS) is responsible for most of the NCC's
SN service control requirements, including reconfiguration of ongoing
services and performance data dissemination. A development effort for
the CCS Replacement (CCSR) will occur in the 1999 to 2001 time frame.
CCSR development will be a collaborative effort with the civil servants
as technical leads. The requirements/design team will be approximately
50/50 (civil servants/contractor), and the implementation team will be
approximately 20/80 (civil servants/contractor).

**LSD CMORE.** LSD CMORE provides for the further development and
enhancement of the logistics IMS to eliminate prevailing deficiencies,
improve system performance, and increase system utility and
availability.

Major system development objectives shall include functional integration
of LSD work elements, availability of on-line operational information
utilizing open system standards, maximum use of COTS software, use of
open standard data base formats, and ease of hardware technology
replacement and software portability. The CSOC contractor shall provide
methodologies and tools used for project development, implementation,
and future use of software and hardware.

**WSC MODS for TDRS HIJ.** The CSOC contractor shall provide support for
the TDRS H,I,J development effort, which is the follow-on government
procurement NAS5-32900 with Hughes Space and Communications for the
acquisition of three additional TDRSs and associated modifications to
WSC. This support includes providing technical support at program design
reviews and technical exchange working group meetings, providing
training, supporting the integration and testing of the WSC
modifications, supporting government acceptance tests, and assuming
sustaining engineering and operational responsibility from the
development contractor after government acceptance. The projected
integration and test of the TDRS H,I,J modifications at WSC begin in
mid-1998. The launch of the first of the TDRS H,I,J satellites is
projected in mid-1999.

**NPAS Development.** This provides development of new report formats,
data bases, and analysis capabilities for generation of performance
loading studies. The contractor shall incorporate new interfaces and
modify existing system interfaces to comply with NASA selected standards
for mission models, characterization parameters, schedules, report
formats, graphical user interfaces, etc. The CSOC contractor shall
develop scripts, filters, and preprocessors for accepting the output of
other tools as an input to the system. The contractor shall develop
additional presentation capabilities as requested by NASA.

**Transponder Characterization.** This provides validation of equipment
functional operation and performance signature over anticipated data
rate, thermal, vacuum, acceleration, shock, vibration, Electromagnetic
Conductance (EMC), and humidity conditions. Tests performed include
phase noise calibration, interface tests, acquisition/deacquisition
time, signal dynamic range, tracking, Bit Error Rate (BER), ranging, RF
power output, frequency temperature stability, transmit power ratio, and
modulation sensitivity,

**Antenna Range/Testbed Support.** This support provides for the
operation and maintenance of the Goddard Antenna Range Facility (GARF).
Tasks include configuration of RF test equipment for antenna performance
testing. Antenna Range personnel also construct and test unique antenna
systems and components.

**Lab Technician Support.** These requirements include:

1.  Fabricating prototype and finished deliverable PC boards (analog and
    digital)

2.  Fabricating electrical and mechanical aspects of prototype systems

3.  Assembling of subsystems RF and digital

4.  Performing tests on component-level purchased modules and subsystems

5.  Performing tests on deliverable subsystems

6.  Maintaining RF systems lab, including:

```{=html}
<!-- -->
```
a.  Ensuring that components and tools are available to support lab
    activities

b.  Ensuring that test equipment is properly calibrated

c.  Maintaining documentation on (a) and (b).

```{=html}
<!-- -->
```
7.  Configuring test equipment, including automated controllers for
    unique tests

8.  Assisting in configuration and maintenance of lab network servers.

**MFR-R/SPAR.** The Multifunction Receiver/Software Programmable
Advanced Receiver provides development, maintenance, and calibration.
The CSOC contractor shall develop and integrate hardware systems,
subsystems, and components as may be required to maintain the capability
to adequately support spaceflight missions and test activities. This
includes but is not limited to RF and digital data handling systems for
the GN and SN, secure data handling devices, test/simulation hardware
for the RFSOC and JSC ESTL and video display and control/monitor
hardware for the NCC and WSC. The contractor shall provide hardware
systems design, integration and test engineers, and facilities to
evaluate potential tracking and data acquisition RF and digital data
handling systems. This activity shall also include the evaluation of
SN-compatible user communications systems elements such as antenna
systems and shuttle and High-Definition Television (HDTV) video systems.
This activity shall include but is not limited to design, evaluation,
testing, specification development, interface requirements development
and definition, and testbed fabrication.

**Network Analysis Support.** This support provides the routine
production of communications link analysis reports, network loading
studies, and RF ICDs as requested by NASA as well as special studies and
analysis reports related to mission planning, customer design reviews,
performance and compatibility, interference (self, mutual, RFI, etc.);
premission analysis, mission anomaly assessments, and postmission
evaluations. The CSOC contractor shall develop and review ICDs (RF ICDs
and ground interfaces) reflecting customer interface information. The
contractor shall review pertinent user mission planning communications
requirements \[Support Instrumentation Requirements Document (SIRD) and
Detailed Mission Requirements (DMR)\] and other tracking and data
acquisition support documents as well as requirements documents, users
guides, etc. The contractor shall maintain a current knowledge of the
tracking and data acquisition communications interfaces, capabilities,
and requirements as well as the analysis systems to be used in
evaluating the customer interface. The contractor shall perform special
engineering, systems software, and operations studies as directed by the
appropriate networks element. These activities are related to the
development of new system, hardware, and software tests that will define
or verify total system performance capabilities. In particular, the
contractor shall develop and modify software that has a data base
capability to store End-to-End Test (EET) and calibration data and
output statistical results to be used in periodic reports. The
contractor shall develop plans and procedures to perform
characterization tests on the TDRSS or its components. The contractor
shall evaluate and document the results of the tests.

## 6.11 Flight Dynamics

General information regarding flight dynamics can be accessed at the
following Uniform Resource Locator (URL):
http://fdd.gsfc.nasa.gov/fdd550.html

**Software Engineering Lab.** Software Engineering Lab efforts consist
of internal software process improvement initiatives (e.g., metric
collection, estimation model building, new development methodology
experiments, etc.) and software engineering research and development
activities. They also involve support for the NASA Software Working
Group, which is responsible for transferring this technology across the
agency.

**Systems Engineering and Technology Evaluation.** These efforts consist
of high-level system architecture studies and prototypes as well as COTS
product evaluations and Internet technology studies (e.g., Java applet
development, automation studies, etc.).

**GPS-Based System Development.** GPS-based system development
responsibility efforts consist of development of advanced flight
software that increases accuracy, ground support error analysis systems,
modular software and standards development, autonomous station keeping
capabilities, etc.

**Advanced Mission Planning Software Development.** These efforts
consist of the development of new interactive graphics capabilities, AI
(e.g., fuzzy logic, expert systems, etc.), advanced targeting
algorithms, etc., in an effort to decrease mission analysis costs.

**Advanced Navigation Software Development.** These efforts consist of
the development of real-time orbit determination systems, advanced orbit
determination algorithms, automation of ground operations, etc.

**Advanced Reuse and Software Architecture Development.** These efforts
consist of the advancement and application of leading-edge technologies
\[e.g., object-oriented technology, Common Object Request Broken
Architecture (CORBA), etc.\] to increase the level of reuse between
systems/projects and, therefore, decrease the cost, cycle time, and
error rates of new systems.

**Attitude Ground Support System (4 mission/yr).** These efforts consist
of the specification, development, configuration, integration, and
testing of an attitude determination system, real-time attitude
determination system, science planning aids, sensor calibration
utilities, other utilities, and associated telemetry simulators/test
tools as required for each mission. This includes custom-developed
and/or COTS software, depending on mission requirements.

**Orbit Determination and Acquisition Data Systems (4 mission/yr).**
These efforts consist of the specification, development, configuration,
integration, and testing of end-to-end navigation systems that receive
and process raw tracking data into ephemerides and include similar work
for acquisition data generation and transmission. They also include
custom-developed and/or COTS software, depending on mission
requirements.

**Mission-Specific Maintenance/Sustaining Engineering (8 mission/yr).**
These efforts consist of the specification, development, configuration,
integration and testing of enhancements, error corrections, upgrades due
to system software changes, external interface changes, etc., on an
as-needed basis. They include communication front-end as well as
flight-dynamics-related applications.

**Institutional Systems Maintenance/Sustaining Engineering.** These
efforts consist of the specification, development, configuration,
integration and testing of enhancements, error corrections, upgrades due
to system software changes, external interface changes, etc., on an
as-needed basis. They include communication front-end as well as
flight-dynamics-related applications.

**Flight Dynamics Support.** Flight dynamics support provides
quick-response analysis support involving research and technology
assessment in a variety of flight dynamics disciplines such as support
of mission design, navigation, and attitude determination and control.

**Flight Dynamics Analysis Support.** Analysis support involves research
and technology assessment in a variety of flight dynamics disciplines
such as support of mission design, navigation, and attitude
determination and control. The intent of these investigations is to
improve the flight dynamics techniques used in the operational scenarios
for future missions and includes mission feasibility studies; parameter
studies; anomaly resolution; technology trade studies; trending studies;
optimization and targeting; and advanced algorithm, technique, and
automation process development.

## 6.12 Special Services for Mission Management

Mission management services includes mission support planning, mission
model data base maintenance, mission requirements management,
interelement agreements management, customer interface coordination,
frequency and spectrum management, support for the GSFC resident office
at JSC, information technology maintenance, and support and mission
planning tool operation and maintenance.

## 6.13 Development for Mission Management

Development for mission management involves the development of tools for
functions such as managing support requirements, interfacing with user
projects, and managing ground system projects. The CSOC contractor shall
explore and develop improved tools and provide technological advancement
for missions management and requirements analysis.

## 6.14 Systems Engineering

**Support for the Development of Policy Documentation.** This effort
presently supports the development of a System Management Policy (SMP)
for MO&DSD. This effort represents only one of the multiple policy
documents that need to be developed as this Directorate evolves. The
CSOC contractor is required to support this and similar efforts.

**Configuration Management.** The CSOC contractor shall have a
Configuration Management Plan as required by DRD 2.1.7, which assures
the government that system configurations are maintained and that
changes shall not impact system performance. The government shall have
the authority to review major system changes and audit configurations.
CSOC support is required for the GSFC MO&DSD Configuration Control Board
(CCB). This includes the development and operational phases.

## 6.15 Wallops Flight Facility

**Instrumentation Engineering Laboratory.** The CSOC contractor shall
provide support in the development and application of advanced or
emerging software technologies for range safety applications. Such will
be required in the development of high-performance/reliability data
processing systems, real-time autonomous information management, and
advanced wind weighting development. The contractor shall provide
support in the evaluation and implementation of state-of-the-art
high-speed, high-reliability software data filter designs. The
contractor shall also provide support in the interpretation,
verification, and specification project scheduling requirements and
mapping of required functions onto designs of existing or possible
future systems.

The CSOC contractor shall provide support in the automation engineering
of ground instrumentation. This support will include design, definition,
interfacing, and checkout of various hardware and software components
within the ground stations with special emphasis on the
hardware-to-software interface.

The CSOC contractor shall provide support in technical documentation,
document coordination, and clerical functions required to document
Facilities and Instrumentation Systems at Wallops Flight Facility. The
contractor shall provide documentation, technical illustration, and word
processing services for various Wallops organizational elements. The
contractor shall generate Federal Information Resources Management
Regulation Documents in support of the applicable GSFC Code 800
procurements. The contractor shall provide support for the planning and
coordination of Wallops technical engineering meetings, workshops, and
seminars, including the generation of minutes and follow-up action items
and provide support in the implementation of the NASA Automated
Information System Security Program and policy outlined in NPG 2810.1
Security of Information Technology.

## 6.16 EOS Development

**Level-1 Product Generation System (LPGS).** The LPGS development will
provide a system that will support Level-1 data processing for Landsat-7
image data. This development effort is a collaborative government and
CSOC contractor effort, with the contractor providing support for
systems engineering and software development. The LPGS will be installed
at the EROS Data Center in Sioux Falls, South Dakota, and will not be
operated and maintained under CSOC. This development is being currently
performed under the SEAS contract in conjunction with an in-house
development team. The CSOC contractor will be required to continue this
development effort for a period beyond the Landsat-7 launch, currently
scheduled for May 1998.

## 6.17 Implementation Team

The CSOC contractor shall provide support for the planning, design, and
implementation of mission facility modifications as specified. These
unplanned activities will typically be in response to situations that
are time critical and are required to avoid a failure in mission
support. Normal planned facility support will be provided for in the
mission, data, or center unique FSA or will be provided by other
organizations.