Representative Task 2

Upgrade the system to support a major new release of the IRIX operating
system

(Major COTS Software Upgrade)

### Task Description

Upgrade all ECS SDPS elements at the ECS DAACs needed to support a major
new release of the IRIX operating system, including dependent COTS
software and custom software.

In support of this task, the contractor shall analyze the impacts of
these upgrades on the ECS SDPS, and plan for and execute the
implementation, test, and deployment of the upgrades to the operational
ECS SDPS at the DAACs. The contractor shall provide all necessary
management and engineering to perform these activities. The contractor
shall coordinate deployment schedules and resources with the DAACs and
shall provide engineering support to the DAACs until the release has
transitioned into operations at all DAACs.

### Task Assumptions

The following assumptions should be made in your approach to this
representative task

-   The IRIX upgrade will require changes to 5,000 C++ SLOC and 500 SQL
    SLOC, spread evenly throughout the subsystems currently hosted on
    SGI hardware.

-   The IRIX upgrade will require upgrades to 20 other dependent COTS
    software products; none of which result in additional SLOC or COTS
    changes. However, 15 of these dependent COTS are used in day-to-day
    operations at the DAACs.

-   The operational systems at each DAAC cannot be down for more than 36
    hours for all upgrades combined.

-   The costs of all COTS software products are covered under EMD Task
    1.

-   Once upgraded, the DAAC systems should experience no degradation of
    performance or usability of the system.

-   Task 1 and Representative Tasks 3 and 4 are active.

### Task Deliverables

The contractor shall deliver the following items in support of this
task:

1.  Plan for upgrade implementation, test and deployment, including
    schedule with key milestones. Due 2 months after start of task.

2.  Task status presentations. Due at monthly status reviews.

3.  All custom code changes and COTS software upgrades, and accompanying
    system integration and test needed to support the upgrade. Due no
    later than 18 months after start of task. However, the contractor
    may define an earlier feasible date.

4.  Pre-Shipment Review(s), consistent with the definition of PSRs
    presented in Task 1, for all custom and COTS upgrades. Due no later
    than 18 months after start of task. However, the contractor may
    define an earlier feasible date.

5.  Operations and maintenance documentation updates needed for all
    changes. Due 1 month prior to PSR.

6.  Transition, operations and maintenance training for DAAC personnel.
    Due 1 month prior to PSR.

[Type of Task]{.underline}: Cost Plus Award Fee (CPAF) End Item Task
pursuant to Clause G.3 of the basic contract, entitled "Award Fee for
End Item Contracts", NFS 1852.216-77.

[Period of Performance:]{.underline}

Start Date: July 1, 2003

Completion, not later than: January 1, 2005

Representative Task 3

Add capacity to support 3X Aqua processing

(Hardware Capacity Increase)

### Task Description

-   Upgrade all ECS SDPS elements at the ECS DAACs needed to support 4X
    Aqua processing. The upgrade should provide additional distribution,
    processing, ingest, metadata inventory and archive capacity for
    those products processed using ECS resources, and it should provide
    additional distribution, ingest, metadata inventory and archive
    capacity for those products processed using SIPS resources.

In support of this task, the contractor shall analyze the impacts of
these upgrades on the ECS SDPS, and plan for and execute the
implementation, test, and deployment of the upgrades to the operational
ECS SDPS at the DAACs. The contractor shall provide all necessary
management and engineering to perform these activities. The contractor
shall coordinate deployment schedules and resources with the DAACs and
shall provide engineering support to each DAAC until the required
performance has been achieved at the DAAC.

### Background

#### The ECS supports Aqua processing using two different models. In the first model, which is used at the GSFC DAAC, all MODIS Level-1 and AIRS processing is performed using the GSFC DAAC's processing system, which is known as "S4P". The S4P system is executed on ECS SDPS hardware. S4P initiates processing in two ways. First, it can receive data from the ECS distribution elements as a result of a subscription triggering when new Level 0 data become available. This is typically used for initial data processing. Second, S4P may request distribution of particular Level 0 data using the Science Data Server Command-Line Interface or SCLI. This interface is typically used for data re-processing. As S4P produces new data granules, it submits the granules and associated production history and browse files for ingest into the ECS archive using the standard SIPS protocol. The granule, production history and browse files are recorded in the ECS metadata inventory as part of the ingest process.

The second Aqua processing model that ECS supports is the standard SIPS
model in which ECS simply distributes data to an external SIPS, and the
SIPS then processes the data and submits the results to ECS for ingest
and archive using the standard SIPS interface. This model is used for
MODIS higher level processing, which is performed by the MODIS SIPS
called MODAPS. There are two ways in which the SIPS may receive data
from ECS. First, the data may be sent as a result of a subscription
triggering when new or re-processed Level 1 data become available.
Second, the SIPS may request the distribution of particular Level 1 data
through the Machine-To-Machine Gateway (MTMGW). After the SIPS produces
new data granules, it submits the granules and associated production
history and browse files for ingest into the ECS archive using the
standard SIPS protocol. The granule, production history and browse files
are recorded in the ECS metadata inventory as part of the ingest
process. Some SIPS (e.g., MODAPS) interface with multiple DAACs to
archive their data.

### Task Assumptions

The following assumptions should be made in your approach to this
representative task

-   The ECS SDPS system at the DAACs prior to the upgrade can support 3X
    Level-1 and 3X Level-2 and above Aqua processing.

-   The 4X requirement consists of 1X processing and 3X reprocessing.

-   Processing and reprocessing for all instruments begins from Level-0
    data, and includes Level-1 and above processing.

-   Aqua products are supported by each of the DAACs as indicated in the
    ECS F&PRS Appendix C tables.

```{=html}
<!-- -->
```
-   All processing at the GSFC DAAC is done using the GSFC DAAC's
    processing system, (which is known as "S4P") and the
    ECS/EMD-provided capacity. No additional capacity is needed to
    support AMSR-E at the NSIDC DAAC.

-   50% of Level 1 processing at the GSFC DAAC uses subscription-based
    distribution to S4P and 50% uses SCLI-based distribution to S4P.

-   50% of Level 2 and above processing done by MODAPS uses
    subscription-based distribution to MODAPS and 50% uses MTMGW-based
    distribution to MODAPS.

-   Each science granule produced by the GSFC DAAC or MODAPS has an
    associated production history file, and 50% of the science granules
    have associated browse files.

-   All browse files are 500 kilobytes in size, and all production
    history files are 2 kilobytes in size.

-   All browse files are archived on tape in the ECS archives but are
    also cached on on-line disks for rapid access.

-   Old versions of data are only maintained in the ECS archives for 6
    months after a new version is produced.

```{=html}
<!-- -->
```
-   No custom or COTS software changes, other than possibly additional
    licenses, are needed to support this upgrade. However, custom and
    COTS performance tuning may be required.

-   Any facility changes needed to support the upgrade will be completed
    by the DAACs within 6 months from task start.

-   For simplification purposes, do not address any added
    hardware/software maintenance costs resulting from the upgrade.

```{=html}
<!-- -->
```
-   The operational systems at each DAAC cannot be down for more than 36
    hours for all upgrades combined.

-   Each DAAC should experience 4X performance within 1 month of initial
    upgrades at that DAAC.

-   Task 1 and Representative Tasks 2 and 4 are active.

### Task Deliverables

The contractor shall deliver the following items in support of this
task:

1.  Plan for upgrade implementation, test and deployment, including
    schedule with key milestones. Due 2 months after start of task.

2.  Task status presentations. Due at monthly status reviews.

3.  Upgrade plan briefing(s) with DAACs. Due within 3 months after start
    of task.

4.  Operations and maintenance training for DAAC personnel. Due one week
    prior to deployment of COTS hardware and software to each DAAC.

5.  COTS hardware and software needed to execute the required upgrades
    at each DAAC. Due no later than 12 months after start of task.
    However, the contractor may define an earlier feasible date.

[Type of Task]{.underline}: Cost Plus Award Fee (CPAF) End Item Task
pursuant to Clause G.3 of the basic contract, entitled "Award Fee for
End Item Contracts", NFS 1852.216-77.

[Period of Performance:]{.underline}

Start Date: June 1, 2003

Completion, not later than: June 1, 2004

Representative Task 4

Modify the system to support media distribution via a new 100 GB media
technology

(Software Development)

[Task Description]{.underline}

Modify the system to support media distribution via a new 100 GB media
technology. The modifications should include all changes needed to make
the new capability visible via the EOS Data Gateway (EDG), fulfill user
orders using the new media technology, and support operational
management of the order fulfillment process for orders using the new
technology, including quality assessment.

In support of this task, the contractor shall analyze the impacts of
these modifications on the ECS SDPS, and plan for and execute the
implementation, test, and deployment of the modifications to the
operational ECS SDPS at the DAACs. The contractor shall provide all
necessary management and engineering to perform these activities. The
contractor shall coordinate deployment schedules and resources with the
DAACs and shall provide engineering support to the DAACs until the
release has transitioned into operations at all DAACs.

### Task Assumptions

The following assumptions should be made in your approach to this
representative task:

-   The new media technology does not support hardware compression,
    i.e., its maximum capacity is 100 Gigabytes per tape.

-   The media technology is integrated into the system via the Product
    Distribution System (PDS) components

-   The integration of the new media technology requires 5,000 SLOC of
    new custom code and changes to 3,000 SLOC of existing custom code,
    spread evenly throughout the subsystems involved in supporting media
    distribution.

-   The integration of the new media technology requires integration of
    a new IRIX-based COTS device driver.

-   The only hardware changes required to support the new capability are
    10 new media technology tape drives (2 for NSIDC, 2 for LaRC, 4 for
    GSFC and 4 for EDC), each of which costs \$25K.

-   Task 1 and Representative Tasks 2 and 3 are active.

### Task Deliverables

The contractor shall deliver the following items in support of this
task:

1.  Plan for capability implementation, test and deployment. Due 2
    months after start of task.

2.  Task status presentations. Due at monthly status reviews.

3.  Requirement documentation updates to reflect new capability and
    corresponding verification plan, including performance verification.
    (Contractor to determine completion milestone.)

4.  All custom code changes, hardware, and accompanying system
    integration and test needed to support the capability. Due no later
    than 1 week prior to CSR.

5.  Consent to Ship Review (CSR) and Pre-Shipment Review (PSR),
    consistent with the definition of CSRs and PSRs presented in Task 1,
    for the new capability. PSR should occur no later than 12 months
    after start of task. However, the contractor may define an earlier
    feasible date.

6.  Design documentation updates needed to reflect all design changes
    made to support the capability. Due one week prior to CSR.

7.  Operations and maintenance documentation updates needed to support
    the capability. Due 1 month prior to PSR.

8.  Transition, operations and maintenance training for DAAC personnel.
    Completion due 2 weeks prior to PSR.

[Type of Task]{.underline}: Cost Plus Award Fee (CPAF) End Item Task
pursuant to Clause G.3 of the basic contract, entitled "Award Fee for
End Item Contracts", NFS 1852.216-77.

[Period of Performance:]{.underline}

Start Date: June 1, 2004

Completion, not later than: June 1, 2005