Statement of Work_RODB-2 IDIQ.pdf

SECTION C

DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

C.1 INTRODUCTION

In order to respond to the demand for environmental information, NOAA strives for an observing enterprise that is flexible, responsive to evolving technologies and economically sustainable, while continuing to be a leader and member of the global meteorological community. To help meet these goals and satisfy observational requirements, NOAA uses satellite-based global navigation satellite system (GNSS) radio occultation (RO) data purchased from multiple commercial contractors to complement Government sponsored sources for use in weather models and other systems. NOAA is interested in continuing the purchase and ingest of these RO data and exploring additional capabilities available from these observations.

C.2 SCOPE

NOAA is soliciting commercial near-real-time satellite-based GNSS RO and ionospheric measurements that will be processed into neutral atmosphere and space weather products.

These derived products will be fed into NOAA’s operational data systems, including weather and space weather analysis and prediction systems, and used for weather, climate, and atmospheric research purposes. All data and products will be archived by NOAA.

C.3 DATA REQUIREMENTS

Contractors must have the capability to fulfill Delivery Orders for data meeting the requirements specified in Section C.3. Optionally, contractors may propose the capability to fulfill Delivery Orders for data meeting requirements specified in SectionC.4.

C.3.1 Definitions

1. An RO sounding is a time series of satellite-based RO open loop measurements made during a GNSS occultation event from which NOAA can produce a quasi-vertical series of bending angles.

2. An ionospheric track is a time series of satellite-based GNSS dual-frequency pseudorange, carrier phase, and SNR measurements from which NOAA can produce geolocated ionospheric products for space weather applications and research purposes.

3. The elevation angle of an observation is defined as the angle between the spacecraft local level and the ray from the spacecraft receiver antenna to the GNSS transmitter antenna.

4. The height of straight line (HSL) altitude of an observation with negative elevation angle is the height of the tangent point of a straight line between the GNSS transmitter and the receiver relative to the World Geodetic System 1984 (WGS84) reference ellipsoid.

5. The time of an RO sounding is defined as the GPS time of the zero HSL altitude point.

6. The time of an ionospheric track is defined by the GPS time of observations making up the track.

7. The latency of a data product is defined as the difference between the time of the observation and the receipt of the data at NESDIS Common Cloud Framework (NCCF).

8. The daily count of a data product is defined as the number of RO soundings or ionospheric tracks in a 24 hour period starting at 00:00:00 GPS time.

9. The location of an RO sounding is defined as the geographic location of the zero HSL altitude point; the location of an ionospheric track is defined as the geographic location of the 120 km HSL altitude point.

10. The latency of an ionospheric observation is defined as the difference between the time of the observation epoch and the receipt of the observation data by the NESDIS Common Cloud Framework (NCCF). The daily median latency for ionospheric data is computed from all epochs collected during the 24 hour period beginning at 00:00:00 GPS time.

11. The Carrier Phase Sampling Rate is the rate of data underlying an on-board calculation of a scintillation index. The Calculation Time Interval is the time period over which a single index calculation is made.

C.3.2 Neutral Atmosphere Data Requirements (Category 1)

Data from RO soundings will be used to produce bending angle profiles of the neutral atmosphere. Contractors proposing to deliver neutral atmosphere data must have the capabilities to provide data meeting the following requirements:

1. RO soundings shall be collected as continuous dual-frequency open-loop measurements at either 50 Hz or 100 Hz.

2. Data shall be provided only from instruments on satellites with an assigned World Meteorological Organization (WMO) satellite identifier.

3. If applicable, the signal-to-noise ratio (SNR) conversion factor from dB-Hz to Volts/Volt (V/V) in a 1 Hz band shall be provided.

4. The SNR of the stronger signal in a dual frequency signal pair, when averaged over HSL altitudes of 60 km to 80 km, shall be greater than 200 V/V in a 1 Hz band.

5. The HSL altitudes of occultations shall span at least -150 km to 90 km.

6. RO soundings shall be from GPS, GLONASS, Galileo, or BeiDou GNSS satellites.

7. RO soundings shall be provided with concurrent precise orbit determination (POD) tracking data.

8. RO soundings shall be provided with concurrent POD tracking data such that one or two POD tracks may serve as reference links for single difference processing of a RO sounding.

9. POD tracking data shall include dual-frequency pseudo range, carrier phase, and SNR, as collected on-orbit in real time.

10. POD tracking data shall include dual-frequency measurements recorded at 1 Hz or greater rate from a minimum of four GNSS satellites simultaneously for 95% of the POD data collection period.

11. Every other orbit of each RO satellite from which data are provided shall be covered by POD tracking data at no less than 50% duty cycle with continuous arc length of at least 50 minutes per orbit.

12. POD tracking data shall be from GPS satellites, plus optionally Galileo and/or GLONASS satellites.

13. Navigation solutions calculated onboard the spacecraft shall be provided, including receiver clock offsets and time-tagged Earth-Centered-Earth-Fixed position and velocity.

14. Navigation solution data shall be provided at intervals of 30 seconds or less.

15. RO satellite attitude quaternions shall be collected concurrently with all POD and RO data at intervals of 30 seconds or less.

16. All RO soundings shall have a latency of 140 minutes or less.

17. The time of RO soundings shall be nearly uniformly distributed in time of day such that the quantity delivered in any six-hour period of the day, when averaged over 30 consecutive days, shall vary by less than a factor of two from any other six-hour period.

18. At a minimum, the Contractor must have the capability to provide a daily count of at least 500 RO soundings, when averaged over any 30-day period, with no more than three days in any 30 day period falling beneath 400/day.

19. Unless otherwise specified in a Delivery Order, the daily count of compliant RO soundings delivered by the Contractor, when averaged over any thirty day period, shall meet or exceed the required target count, and shall not fall below 80% of the required target count for more than three days in any thirty day period.

20. Metadata shall include, at a minimum, for each satellite/instrument configuration:

1. Satellite mass, center of mass, external dimensions including any protruding appendages (e.g., solar array wings, antennae), satellite coordinate system geometry, POD and RO antenna reference point vectors relative to the center of mass and corresponding uncertainty estimates, antenna boresight vectors, and antenna fields of view.

2. RO and POD antenna phase center offset and phase center variation measurements and corresponding uncertainty estimates, in ANTEX format (https://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats).

C.3.3 Space Weather Data Requirements (Category 2)

Ionospheric measurements will be used to produce space weather products including total electron content and scintillation indices. Contractors proposing to deliver space weather data must have the capabilities to provide Level 0 data meeting the following requirements:

C.3.3.1 Requirements for Total Electron Content (TEC)

1. Track extent: Tracks must be at least 8 minutes in duration and span from 90 km HSL to the maximum possible elevation angle for the transmitter/receiver geometry, which must occur at a positive elevation angle.

2. Pseudorange, carrier phase sampling rate 1 Hz

3. Measurement range 0 to 2000 TECU

4. Maximum measurement uncertainty:

1. Relative 0.5 TECU RMS https://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats

2. Absolute 4 TECU RMS

5. Maximum daily median latency 30 min

6. At a minimum, the Contractor shall provide data meeting these TEC requirements from at least 500 ionospheric tracks per day, when averaged over any 30-day period, with no more than three days in any 30 day period falling beneath 400/day.

7. Unless otherwise specified in a Delivery Order, the daily count of compliant ionospheric tracks delivered by the Contractor, when averaged over any thirty day period, shall meet or exceed the required target count, and shall not fall below 80% of the required target count for more than three days in any thirty day period.

C.3.3.2 Requirements for Scintillation Indices

1. S4 shall be computed on-orbit and provided for all tracks. For tracks where S4 exceeds 0.3, high rate (50+ Hz) data from the entire observational altitude range shall be downloaded and provided. This provides raw observations for calculation of scintillation information in the strongest events.

2. Minimum carrier phase sampling rate 50 Hz

3. On-board calculation time interval 10 s

4. On-board calculation cadence 10 s

5. S4 Measurement range 0.1 to 1.5

6. σφ (Sigma phi) Measurement range 0.1 to 20 rad

7. Maximum daily median latency 30 min

8. At a minimum, the Contractor shall provide data meeting these scintillation requirements from at least 25% of the tracks having an on-orbit-calculated value of S4 exceeding 0.3.

C.4 Enhanced Data Requirements

C.4.1 Specific Geospatial Distributions

The required geographic distribution of RO soundings or ionospheric tracks for a Delivery will be specified in each Delivery Order RFP. Within the specified latitude and longitude ranges of the Delivery Order:

1. The number of RO soundings or ionospheric tracks provided each day shall not vary by more than a factor of four (4) between any 30-degree latitude band.

2. Within any 30-degree latitude band, the number of RO soundings or ionospheric tracks provided each day within a 30 degree longitude section shall not vary by more than a factor of four (4) from any other 30 degree longitude section.

C.4.2 Neutral Atmosphere Data with Enhanced Signal-To-Noise Ratio

Delivery Orders may be issued which require higher SNR data. When required by NOAA, the SNR of the stronger signal in a dual frequency signal pair, when averaged over HSL altitudes of 60 km to 80 km, shall be greater than 1200 V/V in a 1 Hz band.

C.4.3 Specific Local Time Sampling

NOAA may include specific requirements on the distribution of local times of the RO soundings or ionospheric tracks. When required in a Delivery Order, the local time of the delivered RO soundings or ionospheric tracks shall be within the specified local time range or group of ranges. The extent of any local time ranges specified in a Delivery Order will be at least 1 hour.

C.4.4 Designated Satellites, Instruments or Modes

NOAA may limit the data in a Delivery Order to come from a specific predesignated list of satellites, instruments, or modes (for example, rising vs. setting occultations). Such a restriction would allow NOAA to coordinate data purchases with other Agencies and partners to avoid duplication of shared observational data.

C.5 DELIVERY REQUIREMENTS

C.5.1 Data Quantity and Delivery Duration

The daily data quantity, volume and delivery period duration will be specified in each Delivery Order RFP. The minimum Delivery Order duration will be 30 days.

The processing level of the RO soundings or ionospheric tracks and associated data to be delivered, i.e. either Level 0 or Level 1a, will be specified in each Delivery Order RFP.

C.5.2 Data Formats

1. The Contractor shall deliver data as Level 0 files or both Level 0 and Level 1a files, as specified by each Delivery Order. If Level 1a, the contractor shall deliver RO observations and high rate observations for derivation of scintillation products in opnGns format (https://cdaac-www.cosmic.ucar.edu/cdaac/cgi_bin/fileFormats.cgi?type=opnGns).

2. The Contractor shall deliver POD tracking data as Level 0 files or both Level 0 and Level 1a files, as specified in each Delivery Order. If Level 1a, the contractor shall deliver POD tracking data in RINEX2.20 or above format (http://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats).

3. The Contractor shall deliver on-orbit computed navigation solution data as Level 0 files or both Level 0 and Level 1a files as specified in each Delivery Order. If Level 1a, the contractor shall deliver navigation data in SP3 format (https://kb.igs.org/hc/en-us/articles/201096516-IGS- Formats).

4. The Contractor shall deliver attitude quaternion data as Level 0 files or both Level 0 and Level 1a files, as specified in each Delivery Order. If Level 1a, the contractor shall deliver Level 1a attitude data in leoAtt format (https://cdaac-www.cosmic.ucar.edu/cdaac/cgi_bin/fileFormats.cgi?type=leoAtt).

5. The Contractor shall deliver a detailed Level 0 data decoding dictionary for each to-be-delivered Level 0 data type. If delivered in binary format, in addition to the dictionary, the Contractor shall deliver binary decoder software as source code.

6. The data descriptor files shall conform to the International Organization for Standardization (ISO) 19115-1:2014 (content) and ISO 19139 (XML schema) standards, in accordance with the NOAA Environmental Data Management Framework.

7. Data files shall be named according to the file naming conventions used by the University Corporation for Atmospheric Research (UCAR) COSMIC Data Analysis and Archive Center (CDAAC), as defined at https://cdaac-www.cosmic.ucar.edu/cdaac/doc/formats.html. Offerors who cannot comply with the file name convention used by the CDAAC shall propose an alternative naming convention. Acceptance of any alternative naming conventions is at the discretion of the Government.

8. The Contractor shall deliver data to NOAA batched as compressed TAR files, with each TAR file including concurrent POD and attitude data files. RO data files may be included https://cdaac-www.cosmic.ucar.edu/cdaac/cgi_bin/fileFormats.cgi?type=opnGns https://cdaac-www.cosmic.ucar.edu/cdaac/cgi_bin/fileFormats.cgi?type=opnGns http://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats http://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats https://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats https://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats https://kb.igs.org/hc/en-us/articles/201096516-IGS-Formats https://cdaac-www.cosmic.ucar.edu/cdaac/cgi_bin/fileFormats.cgi?type=leoAtt https://cdaac-www.cosmic.ucar.edu/cdaac/cgi_bin/fileFormats.cgi?type=leoAtt https://cdaac-www.cosmic.ucar.edu/cdaac/doc/formats.html https://cdaac-www.cosmic.ucar.edu/cdaac/doc/formats.html in the POD and attitude TAR files or delivered as separate TAR files with file names correlating file types.

9. When RO data at both Level 0 and Level 1a are to be delivered, the Contractor shall deliver Level 0 and Level 1a data in separate TAR files.

C.5.3 Data Delivery

The Contractor shall deliver all files to the NESDIS Common Cloud Framework (NCCF) in accordance with the NCCF Interface Control Document (latest version).

The Contractor shall, upon receipt of NCCF alert notification, resolve and (as needed) redeliver data files when data latency requirements can still be met. Re-delivered file names shall include a date or identifier unique to that delivery.

If the contractor has an agreement to provide RO data:

1. to other U.S. Government agencies, National Meteorological and Hydrological Services, WMO-designated Regional Specialized Meteorological Centers, members of the Coordination Group for Meteorological Satellites, including but not limited to the European Organization for the Exploitation of Meteorological Satellites (EUMETSAT);

2. with a latency equal to or less than the latency required by this contract; and

3. The terms of that provision permit the immediate distribution to and use by NOAA, the contractor is not permitted to provide the same RO soundings to NOAA to meet its delivery requirements.

C.5.4 Test Data

Within 7 days of contract award, the Contractor shall provide:

1. A list of the satellites, with their WMO identifiers, that are planned to be used for RO data collection during the contract. Updates for future satellites should be handled per Notification requirements.

2. File name protocols, file name examples, and satellite identifier location, as well as information requested in the NCCF Interface Control Document section 3 “Template for Data Provider Interfaces Information”.

3. A description of the onboard receiver clock steering methods, sufficient to enable NOAA to determine any needed processing adjustments on the ground, shall be provided.

4. If the POD and RO receiver clocks are not the same, the Contractor shall provide a description of how to align them for single difference RO data processing.

Approximately 14 days prior to the start of any Delivery Order that is not a continuation of a Delivery Order, the Contractor shall provide:

1. 24 hours of contiguous on-orbit data, representative of that to be provided under contract and compliant with the data requirements specified herein.

2. Metadata as necessary to prepare ground processing for the identified satellites.

NOAA may require the Contractor to provide, outside the scope of a Delivery Order, limited examples of the data described in this SOW in order to validate changes to NOAA systems. For test data, the requirements for latency and delivery to the secure ingest interface may not apply.

The Contractor shall provide test data, consisting of 24-96 hours of contiguous compliant data and associated metadata, to support NOAA system tests.

NOAA will require any Contractor having data or interfaces not yet tested and validated by NOAA to provide a 30 day period of like-operations data delivery to support NOAA implementation and testing. NOAA will use a Test Data Delivery Order for this purpose and will specify the data and delivery requirements in that Delivery Order.

Any Contractor determined to have a new NCCF interface shall participate in network connectivity testing with the NOAA NCCF secure ingest service.

As specified in a Test Data Delivery Order, the Contractor shall provide compliant data and associated metadata to enable high-fidelity NOAA system tests.

C.6 NOTIFICATIONS

The Contractor shall provide timely notification to NOAA designated points of contact of anomalies and events that impact or have the potential to impact data deliveries or data volumes. Within a month of the reported anomaly, the Contractor shall deliver an anomaly report to the Program Manager, CO, and the Contract Specialist whose framework should include these topics: 1) General information on the Delivery Order (DO), POP, Contractor name;

2) Date/time of anomaly; 3) Description of the anomaly; 4) Resolution Summary and Lessons Learned, as applicable; 5) Impact on Users, Performance, and Schedule, as applicable.

The Contractor shall notify the Program Manager, COR, and the Contracting Officer, in writing, of any contract administration issues, including, but not limited to, changes in anticipated data delivery timelines or data specifications, as soon as they become known.

For any platform, sensor, or ground processing change that may affect data delivery or data quality, including but not limited to spacecraft, instrument, software, configuration, or other change, the Contractor shall provide written notification to NOAA of pending change no less than fourteen (14) days in advance of its implementation and shall include a description of the planned change as well as any resulting changes to the operations concept, configuration, delivery, ground data processing, data content, or metadata. Notification is required under the contract and is not dependent upon having an active Delivery Order. Depending on the nature and extent of the change, the Government may request a delivery of no less than 24 hours of sample data, not to exceed 1 week of sample data, in order for the Government to implement and test any Government system modifications required to accommodate the change.

C.7 GENERAL REQUIREMENTS

The Contractor shall participate in a post-award kick-off meeting, no later than 2 weeks after award.

The Contractor shall be available to discuss deliveries, support initial data integration, discuss anomalies, and provide sustaining engineering information, if necessary, through the end of the contract Ordering Period.

The Contractor shall support mitigation of NOAA Supply Chain Risk Assessment findings as determined by the NOAA OCIO. The Contractor shall provide a point of contact that is available 24x7 and will respond within 60 minutes of notification by NOAA to investigate and resolve any data delivery or performance issues.

C.8 CONTRACTING OFFICER’S REPRESENTATIVE AND TASK MANAGER

In accordance with CAR Clause 1352.201-72, a Contracting Officer's Representative (COR) will be designated at award. The COR may provide technical direction and has the authority to accept delivery. The COR is not authorized to make any commitments or otherwise obligate the Government or authorize any changes which affect the contract price, terms, or conditions of the award. Any Contractor request for changes shall be referred to the Contracting Officer directly or through the COR. No such changes shall be made without the express written prior authorization of the Contracting Officer.

A Task Manager (TM) will be designated at award. The TM does not have delegated authority to represent the Contracting Officer or bind the Government. The TM cannot change, waive, add, or request any additional specifications or performance.

C.9 SECURITY REQUIREMENTS

The Contractor shall comply with CAR 1352.239-72, section (i). The Contractor may request COR approval of alternate security accreditation methodologies for compliance with section (i) including: information security assessment methodology promulgated by the U.S Federal Government (specifically, National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37 and NIST SP 800- 53), or internationally recognized private industry information technology (IT) security frameworks (such as International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 27033, 27001, 27006 and 27002, or

Control Objectives for Information and Related Technology (COBIT)). The Contractor will provide an analysis for alternative methodologies compared to SP 800-53 high impact baseline identifying any gaps.

The Contractor shall deliver files to NOAA ingest using either Hypertext Transfer Protocol Secure (HTTPS) (preferred) or Secure File Transfer Protocol (SFTP). The Contractor shall use a data integrity method compliant with the NCCF ICD and approved by NOAA.

C.10 DATA RIGHTS

Per this contract, the Contractor grants NOAA a perpetual, non-exclusive, irrevocable, worldwide license to use, reproduce, and create derived and value-added products with the RO data, in any manner and for any purpose, and to authorize others to do so on its behalf (including other contractors and recipients of financial assistance awards).

A derived product means a work that is created when data are manipulated to such a degree that it cannot be reverse engineered. Derived products created using RO data received under this contract are not subject to the data rights provisions in this section or any other contractual, licensing, or intellectual property claims by the Contractor, and therefore may be publicly distributed without use restrictions.

A value-added product means a work that is created when data are modified—through technical manipulation, addition of data, or both—where the principal features and characteristics of the source data are retained in the work and are extractable through technical means. Value-Added Products created using RO data received under this contract are subject to the data rights provisions in this section.

Level 1 and Level 2 products (excess phase, vertical profiles of bending angle, refractivity, temperature, and humidity) created by NOAA or its affiliates from Contractor-supplied RO data are considered to be value-added products. All other products created by NOAA or its affiliates from Contractor-supplied RO data, including but not limited to model output, are considered to be derived products.

Furthermore, the Contractor shall provide pricing for various external data sharing rights, including but not limited to the external distribution and use rights described in the options below.

Option 1: Right to distribute all RO data to any entity immediately after receipt at NOAA with no restrictions on their use or further distribution, under a Creative Commons Attribution 4.0 International license (CC BY 4.0).

Option 2: Right to distribute all RO data to U.S. Government agencies, International Partners, including but not limited to those responsible for national meteorological, space weather, or hydrological services, and National Meteorological and Hydrological Services, WMO-designated Regional Specialized Meteorological Centers, members of the Coordination Group for Meteorological Satellites, and non-profit entities and academic entities, immediately after receipt at NOAA, for non-commercial use but not for further distribution.

Option 2A: In addition to the rights under Option 2, Option 1 rights will apply to all RO data beginning at 24 hours after collection.

Option 3: Right to distribute all RO data to U.S. Government agencies, International Partners, including but not limited to those responsible for national meteorological, space weather, or hydrological services, and National Meteorological and Hydrological Services, WMO-designated Regional Specialized Meteorological Centers, and members of the Coordination Group for Meteorological Satellites, immediately after receipt at NOAA, for non- commercial use but not for further distribution.

Option 3A: In addition to the rights under Option 3, Option 1 rights will apply to all RO data beginning at 24 hours after collection.

NOAA will ensure that any non-NOAA entity receiving restricted data is made aware of the identified use and distribution restrictions associated with the data rights specified in the IDIQ contract and this Delivery Order. If NOAA becomes aware that an entity is not adhering to those restrictions, NOAA will seek to ensure compliance, and if unsuccessful, may terminate the entity’s access to the data. NOAA, however, has no additional obligations under the IDIQ contract or this Delivery Order related to data use by third parties. In no event is NOAA liable to the contractor for third party use or release of contractor data

(End of Section C)

[The remainder of this page left intentionally blank.]