About this file

Statement of Work (draft version)

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

EOS PI-Led Instrument Algorithm Maintenance Team for Measurements of Pollution in the

Troposphere (MOPITT)

Statement of Work

1. Introduction

1.1 Purpose

This Statement of Work (SOW) covers the required activities for the continuation of algorithm development and maintenance described in existing Algorithm Theoretical Basis Documents

(ATBDs). This includes the work necessary to assure the continued successful use of current algorithms and data, periodic updating resulting from accrued experience, improvements to computing facilities, instrumental changes, and evolving external inputs. It also includes all related operational aspects, and the first order validation work associated with comparing sensor data to that from aircraft, other operational satellite and ground based systems.

1.2 Background

A Memorandum of Understanding (MOU) was executed on November 1994, which describes the cooperation of the flight of the Measurements of Pollution in the Troposphere (MOPITT) instrument on the NASA Polar orbiting platform Terra and related support for an international

Earth Observing System (EOS) between NASA and the Canadian Space Agency (CSA). The EOS program elements and participating scientists outlined in this MOU were solicited by an

Announcement of Opportunity (AO) (OSSA-1-88, Jan. 19, 1988) and a subsequent NASA Research

Announcement (NRA-95-MTPE-03) was released in 2003 to select science team leaders for the development and maintenance of algorithms for the NASA Terra Spacecraft instrument MOPITT.

The successful proposal from the NRA outlined a teaming arrangement between NASA, the CSA and the National Center for Atmospheric Research/University Corporation for Atmospheric

Research (NCAR/UCAR), for the development and maintenance of algorithms supporting the

MOPITT instrument. The CSA was responsible for the instrument development, operation and calibration, and the U.S. team, led by NCAR/UCAR with NASA, for the algorithm development and maintenance. On December, 2017, the NASA Senior Review provided programmatic direction to continue the Terra mission through FY 2023.

1.3 Period of Performance

The period of performance for the work defined in this SOW begins on the date of award and continues for two years with an optional one year period.

2. Scope

2.1 Activities

The services required include, but are not limited to, maintenance of data production software to produce EOS geophysical data products, ensuring accuracy and quality of data products and providing support for the operation of the instruments and to the Project

Science Office (PSO) during the elaboration of the Senior Review (SR).

The Contractor will monitor the status of team member and determine the team’s total schedules and budgets in conjunction with the NASA EOS Senior Project Scientist.

The Contractor provides the overall direction of EOS platform instrument product maintenance and distribution and manages the MOPITT Teams’ algorithm maintenance process.

The Contractor coordinates and directs the team member’s efforts that include, but are not limited to, reporting, algorithm maintenance and updates, and Science Computing Facility

(SCF) operation.

The Contractor shall develop budgets and schedules for the instrument Team and regularly reports the status of the team’s work to the Contracting Officer’s Representative (COR).

The Contractor shall ensure that team members prepare updated algorithm theoretical basis documents (ATBD) for the algorithms which are used to generate each standard data product.

The Contractor shall manage the maintenance activities of the Level 1, 2, and 3 algorithms as appropriate including quality control, validation support, error analysis, software maintenance, documentation, and on-orbit monitoring of sensor status.

The Contractor shall continuously maintain oversight of direct calibration and characterization activities including new understanding of pre-launch calibration data and post-launch collections.

The Contractor shall ensure that instrument characteristics and calibration parameters are updated and incorporated into the appropriate data production software and tables.

The Contractor will also support investigation of instrument anomalies and/or sensor degradation.

The Contractor shall determine what resources and manpower are required to maintain any current Science Computing Facility (SCF) operations.

The Contractor shall act as the interface between any foreign partners and facilitate the scheduling, ordering and expediting data acquisition with these foreign partners on behalf of

NASA.

The Contractor shall ensure the generation of data in formats approved by NASA for use by the EOS Data Information System (EOSDIS).

The Contractor shall provide Internet information to internal and external scientists concerning sensor/system characteristics, interpretation, algorithms, data quality, data availability, data accuracy, and research reports.

Communication of instrument operation status and science result highlight shall take place at least once monthly through teleconferences with the Senior Project Scientist and other scientists and instrument team leaders.

Further communication of these results by the Contractor using MOPITT instrument shall take place through attendance at professional conferences, in print or online publications, at working groups, and through training sessions.

It is anticipated that presentations to the Senior Project Scientist will be performed through teleconferences on a monthly basis.

The conferences anticipated to be supported and attended to by the Contractor in communication of these results using the MOPITT instrument at a minimum are as follows:

American Geophysical Union (AGU), once a year in San Francisco, California, USA; and the

European Geophysical Union (EGU), once a year, Vienna, Austria.

Working Groups and Training sessions may be held at NASA GSFC or at the Contractor’s facility, at the discretion of the EOS Project Science Office and are expected not to exceed 1 per year.

An appropriate citation identifying the NASA EOS Program shall accompany each publication resulting from the work supported under this contract.

All Software Applications and Operating systems developed in performance of this Statement of Work shall comply with Section 1194.21 (Software Applications and Operating Systems) of the EIT Accessibility Standards.

Any WWW development in performance of this Statement of Work shall comply with section

1194.22 (web-based Intranet and Internet Information and Applications) of the EIT

Accessibility Standards.

Desktop or portable computers utilized in performance of this Statement of Work should comply with Section 1194.26 (Desktop and Portable Computers) of the EIT Accessibility

Standards.

2.2 Deliverables

For each sensor data algorithm, the Contractor shall develop the following deliverables:

Updated ATBD documentation.

A product error analysis document for use by scientists, and others, requiring product accuracies. This document shall include and distinguish between all significant types of errors including spacecraft location and motions, scanning, spectral differences from the ideal algorithms, calibration factors, digitization limitations, time and space sampling insufficiencies, interferences, atmospheric effects removal, and other information as needed and as appropriate.

Semi-annual Progress Reports shall be delivered to the EOS Project Science Office

(EOSPSO) and NASA Headquarters. Notification of delivery shall be made to the COR.

Periodic briefing requests from EOSPSO and NASA Headquarters, not to exceed three per calendar year, may be made by the COR.

Periodic documentation reporting requests from EOSPSO and NASA Headquarters (such as Senior Review inputs, mission closeout document, etc.), not to exceed two per calendar year, may be made by the COR.

A brief (two pages or less) Final Technical Progress Report shall be delivered to the COR describing the accomplishments achieved through the entire performance period and address the current status of work in progress.

File details come from the government source that posted it.