NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION (NOAA)

Commercial Weather Data Pilot (CWDP) Program – Wildfire Imagery Pilot Study

SYNOPSIS/SOLICITATION

(i) This is a combined synopsis/solicitation for commercial products or commercial services prepared in accordance with part 12. This announcement constitutes the only solicitation. Offers are being requested and a separate written solicitation will not be issued.

Solicitation number 1332KP26R0016 is issued as a request for proposal (RFP) to acquire available commercial multi-spectral imagery observations and investigate the utility of radiometric data developed by commercial vendors to aid in wildfire detection and characterization, monitoring, and mapping.

This acquisition is a Total Small Business Set-Aside. This solicitation incorporates provisions and clauses by reference. The full text of provisions and clauses may be accessed electronically at www.acquisition.gov.

Defense Priorities and Allocations System (DPAS) and assigned ratings do not apply.

(ii) Contract Line Item Numbers (CLINs) are to be determined based on the awarded quantities.

(iii) Description of requirements for the items to be acquired is included in Section 2 and Attachment 1, "Statement of Work."

(iv) Place of Delivery: Data shall be submitted as set forth in Section 2 and Attachment 1, "Statement of Work."

(v) The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular FAC 2026-01, effective March 13, 2026.

(vi) The Government intends to award one or more FIRM-FIXED PRICE (FFP) contracts. The associated NAICS code is 518210-- Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services with a corresponding small business size standard of $40.0 million.

(vii) RFO 52.212-1, Instructions to Offerors-Commercial Products and Commercial Services (SEP 2023) (Deviation RFO JAN 2026) applies to this acquisition. Addenda to 52.212-1, Instructions to Offerors - Commercial Products and Commercial Services, are included in Section 4.

(viii) RFO 52.212-2, Evaluation-Commercial Products and Commercial Services (NOV 2021) (Deviation RFO JAN 2026) applies to this acquisition as set forth in Section 4.

http://www.acquisition.gov/

(ix) The clause at RFO 52.212-4, Terms and Conditions - Commercial Products and Commercial Services (NOV 2023) (Deviation RFO JAN 2026) applies to this acquisition.

These terms and conditions will be incorporated by reference in any resulting award.

(x) Additional contract requirements, terms, and conditions can be found in Attachment 1, "Statement of Work," and Section 2.

(xi) Proposals are required to be received in the contracting office no later than 2:00 P.M., Eastern Time on April 30, 2026. Questions related to this RFP is due no later than 2:00 P.M. Eastern Time on April 20, 2026.

(xii) All proposals must be emailed to the attention of Suzanna Espinoza, Contracting Officer at: suzanna.espinoza@noaa.gov and Cherron E. Bennett-Pettus, Contract Specialist at:

cherron.bennett-pettus@noaa.gov. For information regarding the solicitation, the Contracting Officer and Contract Specialist may be contacted via email at suzanna.espinoza@noaa.gov and cherron.bennett-pettus@noaa.gov. Telephone calls will not be accepted. Instructions for the submissions of proposals are presented in Section 4. Offerors are responsible for ensuring timely submission of proposals. Multiple emails may be sent in order to accommodate large file sizes.

This solicitation does not commit the Government to pay any cost for the preparation and submission of a proposal in response to this RFP.

Attachments:

Attachment 1: Statement of Work Attachment 2: Price / Availability Schedule mailto:suzanna.espinoza@noaa.gov

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3.AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN 29. AWARD OF CONTRACT: REFERENCE

. YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4.

FAR 52.212-3 AND 52.212-5 ARE ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED.

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

DATED.

OFFER

ADDENDA

ADDENDA

1332KP26R0016

NOAA/NESDIS/OSAAP

1335 EAST WEST HWY

SSMC1, ROOM 5300

SILVER SPRING MD 20910

SIAD-RED

1325 EAST WEST HWY

SSMC2, 11th FLOOR

SILVER SPRING MD 20910

SIAD-RED

1325 EAST WEST HWY

SSMC2, 11th FLOOR

SILVER SPRING MD 20910

04/30/2026 1400 ED

CHERRON BENNETT-PETTUS

SIAD-RED 100.00

SIAD-RED

SUZANNA ESPINOZA

518210

$40

04/07/2026

NEEA0002

Period of Performance: 06/01/2026 to

04/01/2027

0001 Phase 1: Preparation - 1 month

In this initial phase, the Contractor shall

Continued...

STOCK RECORD (S/R)

STANDARD FORM 1449 (REV. 11/2021) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE RECEIVED (MM/DD/YYYY) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

32g. EMAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

ACCEPTED,

supply the necessary technical documentation which may include format specifications, calibration data, and any other information that will be needed to ingest and process the data. Delivery mechanisms and data handling processes will be communicated to the

Contractor. The Contractor will provide engineering support as needed to the Government to enable the acquisition and processing of the supplied datasets. A delivery of 24-hours of sample data may be required during this phase and used to test and adjust the delivery and data flow process as needed.

Product/Service Code: DF10

Delivery: 06/01/2026

0002 Phase 2: Data Delivery - 6 months

During this phase, the Contractor shall provide a series of data deliveries over a period of 6 months, in accordance with the requirements specified in this document. The start and end date/time of this delivery period will be coordinated with the Contracting Officer (CO) and Contracting Officer’s Representative

(COR).

Product/Service Code: DF10

Delivery: 07/01/2026

Continued...

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGES

NAME OF OFFEROR OR CONTRACTOR

SUPPLIES/SERVICES

(B)

UNIT

(D)

UNIT PRICE

(E)

AMOUNT

(F)

OPTIONAL FORM 336 (4-86)

Sponsored by GSA FAR (48 CFR) 53.110

ITEM NO.

(A)

QUANTITY

(C)

NSN 7540-01-152-8067

1332KP26R0016

0003 Phase 3: Evaluation - 3 months

In this final phase, the Contractor will be available for limited reachback engineering/technical support as needed for problem resolution and technical assistance, as the Government evaluates the supplied dataset.

Product/Service Code: DF10

Delivery: 01/01/2027

1332KP26R0016 BASE

Section 1 - SCHEDULE OF SUPPLIES/SERVICES Section 2 - STATEMENT OF WORK Section 3 - CONTRACT CLAUSES (TERMS AND CONDITIONS) Section 4 - SOLICITATION PROVISIONS (INSTRUCTIONS TO OFFERORS) Section 5 - REPRESENTATIONS AND CERTIFICATIONS

Section 1 - SCHEDULE OF SUPPLIES/SERVICES

Item Number Description Quantity Unit Unit Price Amount

Phase 1: Preparation - 1 month In this initial phase, the Contractor shall supply the necessary technical documentation which may include format specifications, calibration data, and any other information that will be needed to ingest and process the data. Delivery mechanisms and data handling processes will be communicated to the Contractor. The Contractor will provide engineering support as needed to the Government to enable the acquisition and processing of the supplied datasets. A delivery of 24-hours of sample data may be required during this phase and used to test and adjust the delivery and data flow process as needed.

Product/Service Code: DF10

Phase 2: Data Delivery - 6 months During this phase, the Contractor shall provide a series of data deliveries over a period of 6 months, in accordance with the requirements specified in this document. The start and end date/time of this delivery period will be coordinated with the Contracting Officer (CO) and Contracting Officer’s Representative (COR).

Product/Service Code: DF10

Phase 3: Evaluation - 3 months In this final phase, the Contractor will be available for limited reachback engineering/technical support as needed for problem resolution and technical assistance, as the Government evaluates the supplied dataset.

Product/Service Code: DF10

Attachment Number Title Date

1 Attachment 1 - Statement of Work 04/07/2026 2 Attachment 2 - Price - Availability Schedule 04/07/2026

Section 2 - STATEMENT OF WORK

2 STATEMENT OF WORK

ATTACHMENT 1

Wildfire Imagery Pilot–Statement of Work

I. INTRODUCTION

The National Oceanic and Atmospheric Administration’s (NOAA) mission is to understand and predict changes in climate, weather, oceans, and coasts, to share that knowledge and information with others as the Nation’s authoritative environmental intelligence agency. NOAA is committed to improving public predictions to protect life and property.

Wildfires pose a significant threat to communities across the United States, and NOAA's observations are crucial for both fire mitigation and response efforts. In particular, early fire detection and monitoring of fire intensity and progression are critical for first response and wildfire incident management, both of which the National Weather Service supports. NOAA seeks to augment its remote sensing fire detection and monitoring capabilities with commercial space-based multispectral capabilities. These commercial observations will aid in modernizing fire warnings and synthesizing data from multiple sources to support time-critical decision-making.

The NESDIS Commercial Data Program (CDP) pursues demonstration projects on behalf of NOAA and assesses the viability of assimilating commercially provided satellite data and products to diversify NOAA’s portfolio of data collection capabilities. Through the NESDIS CDP, NOAA intends to conduct a commercial data Pilot Study that may help NOAA meet its terrestrial environment mission objectives.

For this Pilot Study, NOAA will use Pilot Study data to assess the quality and impact of available commercial multispectral imagery, including infrared capabilities, and to investigate the utility of radiometric data developed by commercial vendors to aid in wildfire detection, monitoring, and mapping. NOAA will assess thermal-based fire detection performance compared to NOAA’s Advanced Baseline Imager (ABI) and Visible Infrared Imaging Radiometer Suite (VIIRS) instruments. NOAA will use these observations to generate fire detection and characterization intelligence and to assess their value within an integrated data and application framework. NOAA will focus these efforts on use cases related to protecting life and property.

II. DATA SPECIFICATION REQUIREMENTS

The Contractor for this Pilot Study shall supply multi-spectral observation data that, preferably, includes visible, near infrared, short-wave infrared, mid-wave infrared, and long-wave infrared channels collected on-orbit from one or more satellites. The observation data will primarily be used to evaluate commercial multispectral imagery for wildfire detection, characterization, monitoring, and mapping.

1. The requirements set forth below constitute the specific operational measurement requirements for the Pilot Study. Requirements are categorized as threshold values, representing minimum acceptable levels, and objective values, representing desired levels of performance with increased utility. Threshold and objective requirements specified in this document are not necessarily indicative of requirements that may be developed for future contracts or solicitations.

2. The threshold requirements define the minimum acceptable performance levels; failure to meet them may result in no contract award.

3. For the objective requirements, it is understood that contractors may not be able to meet all objective requirements. Contractors proposing to deliver data that do not meet one or more objective requirements during the data delivery period shall clearly identify:

1. the requirement(s) not met,

2. the reason(s) for not meeting the requirement(s), and

3. the expected impact on data quality, operational usability, and evaluation outcomes.

4. Due to the nature of this Pilot Study, it is understood that contractors may not be able to meet all requirements presented. Contractors proposing to deliver data that does not meet a requirement during the Pilot Study data delivery period should indicate the nature of the discrepancy, the reason for not meeting the requirement, and the expected impact.

II.A. DEFINITIONS

1.

1. NOAA Data Processing Level Definitions include:

2. Table 1. NOAA Data Processing Level

Data Level Description Multispectral Imagery Examples

Level 0

Reconstructed, unprocessed instrument and payload data at full resolution, with any and all communications artifacts (e.g., synchronization frames, communications headers, duplicate data) removed.

Raw detector counts from each channel, time stamps for each scan line, scan geometry and sensor view angles, instrument telemetry.

Level 1A (L1A) Level-1A (L1A) data are reconstructed and time-ordered instrument measurements that have been de-packetized and quality-checked but remain uncalibrated.

Uncalibrated digital counts from each channel with time, scan angle, and instrument telemetry.

Level 1B (L1B)

Level-1B (L1B) data contain radiometrically calibrated and geolocated radiance measurements for each spectral band.

Processing includes: conversion from raw counts to physical radiance units; application of calibration coefficients;

assignment of Earth-location coordinates (geolocation) and quality flags and metadata. L1B data are the primary input for generating geophysical products.

Calibrated, geolocated radiances or reflectances for each spectral band and spatial pixel.

Level 1C (L1C) Resampled and geolocated brightness temperature data projected onto a standard Earth grid, enabling multi-sensor analysis and model ingestion.

Brightness temperatures gridded to a fixed Earth coordinate system (e.g., EASE-Grid).

Level 2 (L2)

Level-2 (L2) data are derived geophysical products — such as cloud properties, sea-surface temperature, aerosol optical depth, fire detections and fire radiative power, and vegetation indices — computed from Level-1B radiances and ready for scientific and operational use.

Cloud properties, sea-surface temperature, aerosol optical depth, fire detections and fire radiative power

2. Metadata is structured, descriptive information that documents the characteristics of a dataset. They provide essential context about the data's content, origin, purpose, quality, format, spatial and temporal coverage, processing history, and usage constraints. Metadata enables effective data discovery, interpretation, integration, management, and reuse by both humans and machines. High-quality metadata are critical for ensuring transparency, traceability, and interoperability within NOAA’s data enterprise and across the broader scientific community.

3. For additional guidance on metadata standards and practices, see NOAA’s National Centers for Environmental Information (NCEI):https://www.ncei.noaa.gov/resources/metadata/introduction-to-metadata-at-ncei

3. Latency of a data product is defined as the difference between the time the instrument acquires data in orbit and the time the data are received into the NESDIS Common Cloud Framework (NCCF) or alternate NESDIS cloud environment.

4. Satellite data availability is the percentage of satellite-generated data that, during a given time period, is accessible, usable, and delivered as expected to users. It reflects the overall capability of the satellite system—including onboard sensors, communication links, ground stations, and processing infrastructure—to provide data continuously and without interruption.

II.B. OBSERVATION CAPABILITY AND REQUIREMENTS

1.

1. The Contractor shall supply multispectral observation data. The requirements set forth below constitute the measurement requirements.

2. Spectral acquisitions must remain within the Earth exploration satellite service (EESS) allocations, as specified in the FCC Online Table of Frequency Allocations, to avoid compromising system performance or violating regulatory constraints.

3. Table 2, summarized below, lists the spectral guidance and acceptable capabilities for multispectral radiance observations for Fire Imagery. The Contractor shall provide radiance observations that, at a minimum, include at least one channel in each of the specified spectral ranges. Additional spectral observations, if available, shall also be provided.

2. Table 2. Spectral Guidance for Multispectral Radiance Observations for Fire Detection Imagery

Spectral Band Spectral Channel Ranges (¿¿m) Primary Use

Visible / Near Infrared 0.6 - 0.9 False Alarm Screening

Shortwave / Midwave Infrared 3.5 - 4.2 Active Fire Detection and Characterization

Longwave Infrared 8.0 - 12.5 Active Fire Detection and False Alarm Screening https://www.ncei.noaa.gov/resources/metadata/introduction-to-metadata-at-ncei https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-2/subpart-B/section-2.106

5. Table 3, summarized below, presents the observational requirements for multispectral imagery for fire imagery detection. The Contractor shall adhere to these requirements and meet or exceed the stated thresholds in Table 3.

The contractor shall deliver at least 80% of the constellation-level data (full-swath data) over a 3-9 month period during peak wildfire season (June - November), when any part of the full satellite swath intersects a predefined region of interest, with a primary focus on the western United States. The contractor may provide two pricing options: one for a region of interest that is 1900 km in the north/south direction and 1000 km in the east/west direction, and another for a 950 km (N/S) x 500 km (E/W) region. The location of the region of interest will be based on wildfire activity during the 3-9 month pilot period.

Table 3. Multispectral Radiance Data Requirements for Fire Detection Imagery

Performance Level Threshold Requirement

Horizontal Spatial Resolution (at nadir) Threshold: 200 m, Objective: 50 m

Geolocation Accuracy Threshold: 100% of Horizontal spatial resolution, Objective: 50% of Horizontal spatial resolution

L1B product Latency Threshold: 3 hours, Objective: 60 minutes

III. DELIVERY REQUIREMENTS

Contractors shall supply data that meets the following requirements:

1. Provide Level 1 data products consistent with or improving upon the spatial and radiometric data characteristics of NOAA’s Visible Infrared Imaging Radiometer Suite (VIIRS) sensor. VIIRS serves as references for spatial resolution, radiometric performance, and geolocation accuracy.

As defined in Section II.A, data products shall include, at a minimum:

a. Level 1B: Calibrated and geolocated radiances in Wm-2sr-1µm-1 units along with Lookup Tables (LUTs) or band-specific information to convert them to reflectance (unitless) and brightness temperatures (Kelvin). These radiometrically calibrated measurements shall be traceable to onboard blackbody references or other high-fidelity validation references and reported at the sensor’s native resolution. Level 1B products shall be formatted as NetCDF, HDF5, or geotiff files.

b. Level 1C: Level 1B data resampled onto an orthomosaic using a fixed Earth grid. Level 1C products shall be formatted as NetCDF, HDF5, or geotiff files.

2. The Contractor shall ensure continuous and contiguous data coverage over geographic regions and periods of interest, and deliver all collected data without interruptions, providing a complete record of observations in near real-time.

1. At a minimum, the Contractor must have the capability to provide contiguous data, without temporal or spatial gaps, along-track for one satellite. Cross-track coverage shall https://www.nesdis.noaa.gov/our-satellites/currently-flying/joint-polar-satellite-system/visible-infrared-imaging-radiometer-suite-viirs be sufficient to meet the spatial and temporal coverage requirements as specified in this

SOW.

3. To ensure consistent delivery of supplementary commercial multispectral radiometric data, overall constellation-level data availability shall serve as the primary performance metric. The Contractor shall maintain at least 80% operational availability. This availability accounts for routine maintenance, calibration activities, and orbital dynamics, and ensures that the spacecraft are capable of supporting NOAA’s data acquisition needs. This constellation-level approach ensures sufficient data continuity to support NOAA mission needs while allowing flexibility in individual satellite performance.

4. The product latency of multispectral radiometric observations delivered by the Contractor, when averaged over any continuous thirty-day period, shall meet or exceed the required latency as specified in Table 3.

5. The Contractor shall ensure cross-platform data consistency across their constellation of commercial multispectral instruments. All instruments shall support "mix-and-match" interoperability, enabling seamless integration of radiance data regardless of satellite platform.

1. All instruments must have consistent calibration algorithms and gain models post-launch, with updates synchronized across the constellation.

2. Data products must be traceable to recognized reference standards, with VIIRS designated as the primary external reference instrument.

3. Timestamps associated with all mission data—including metadata, telemetry, and science observations—must maintain consistency across satellites to within ±1 second to ensure compatibility in time-sensitive processing workflows.

4. The Contractor shall maintain all technical documentation, including calibration history and consistency reports, and ensure it is accessible to the Government in accordance with applicable data access provisions.

6. In the event of data anomalies or as requested by the Government, the Contractor shall provide Level 0 data to support diagnostic analysis and root cause investigation and/or to perform independent calibration/validation by the Government or its designated representatives.

7. All satellite or instrument configuration changes that may impact the quality, calibration, or continuity of science data shall be documented in a change log. Notifications of such changes shall be provided to the designated Government point of contact within 24 hours.

8. The Contractor shall provide all necessary technical documentation to support data understanding, usage, and validation. At a minimum, this shall include:

1. Algorithm Theoretical Basis Documents (ATBDs) – Describing the scientific rationale, processing methodology, and assumptions underlying data generation algorithms.

2. Documentation and data files to support characterization, quality control, and calibration/validation activities, including but not limited to:

1. Spectral response functions.

2. Calibration coefficients to convert pixel-based digital values into radiance, and the reflectance and brightness temperature equivalents.

3. Pixel-based geolocation information, including terrain correction.

3. Pre-launch and on-orbit calibration reports.

4. Documentation of quality control flags and calibration/validation indicators.

5. User guides and detailed data specification documents.

9. Data delivery shall follow the following processes:

1. The data delivery process along with file naming conventions, data formats, and metadata formats shall follow standard NESDIS methods and protocols. The Contractor shall deliver all files for secure ingest to the NESDIS Common Cloud Framework (NCCF) in accordance with the NCCF Interface Control Document (ICD) or alternative secure ingest methods such as the NESDIS Innovation Hub cloud services.

The Contractor shall, upon receipt of alert notifications, 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.

2. The data descriptor files shall conform to theInternational Organization for Standardization (ISO) 19115-1:2014 and applicable amendments (content) and ISO 19139-1:2019 and applicable amendments (XML schema) standards.

3. Data shall be provided only from instruments on satellites with an assigned World Meteorological Organization (WMO) satellite identifier or a unique, internationally recognized identifier such as the COSPAR ID.

4. The data delivery process shall follow NOAA security requirements (see Section VI.

SECURITY REQUIREMENTS).

IIIA. OPTIONAL DELIVERY REQUIREMENTS

Contractors should consider supplying optional data that meets the following requirements:

1. Provide Level 2 (if available) data products consistent with or improving upon the spatial and radiometric data characteristics of NOAA’s Visible Infrared Imaging Radiometer Suite (VIIRS) mission.

VIIRS serves as references for spatial resolution, radiometric performance, and geolocation accuracy.

As defined in Section II.A, data products shall include:

a. Level 2 (if available): Sparse data array(s) containing pixel-based active fire detection information, including essential attributes such as date and time of observation in UTC, center latitude/longitude coordinates, satellite and solar zenith and azimuth angles, effective pixel area, and fire radiative power (FRP) of fire-affected pixels. Optimally provide complementary 2D fire masks describing primary pixel classes (e.g., active fire, clear land, cloud, water), preferably in NetCDF, HDF5, or geotiff format.

IV. CONTRACTING OFFICER’S REPRESENTATIVE

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.

https://www.nesdis.noaa.gov/s3/2024-01/474-00001-01_JPSS-CDFCB-X-Vol-I_F.pdf https://www.iso.org/home.html https://www.iso.org/home.html https://www.nesdis.noaa.gov/our-satellites/currently-flying/joint-polar-satellite-system/visible-infrared-imaging-radiometer-suite-viirs

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 manages the contract cost, schedule, performance and risks. 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.

V. PERFORMANCE SCHEDULE

The Pilot study will be conducted with the following schedule:

Post-Award:

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

Additionally, NOAA/NESDIS CDP may require the Contractor to deliver 48-72 hours of on-orbit data to facilitate Government preparation of data ingestion and conversion.

Phase 1: Preparation - 1 month In this initial phase, the Contractor shall supply the necessary technical documentation which may include format specifications, calibration data, and any other information that will be needed to ingest and process the data. Delivery mechanisms and data handling processes will be communicated to the Contractor. The Contractor will provide engineering support as needed to the Government to enable the acquisition and processing of the supplied datasets. A delivery of 24-hours of sample data may be required during this phase and used to test and adjust the delivery and data flow process as needed.

Phase 2: Data Delivery - 6 months In this phase, the Contractor shall supply a series of data deliveries for a period of 6 months meeting the requirements specified in this document (see Sections II, III, IV, V, VIII). All proposals must include detailed cost and performance breakdowns for each monthly increment within this range to facilitate a scalable evaluation of the service requirements. The start and end date/time of this data delivery period will be coordinated with the CO and COR.

Phase 3: Evaluation - 3 months In this final phase, the Contractor will be available for limited reachback engineering/technical support as needed for problem resolution and technical assistance, as the Government evaluates the supplied dataset.

VI. 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, NIST SP 800- 53, and NIST SP 800-171), 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 NESDIS Cloud System Data Ingest and Data Distribution Services Interface Control Document (ICD) and approved by NOAA.

VII. DATA RIGHTS

Per this contract, the Contractor grants NOAA a perpetual, non-exclusive, irrevocable, worldwide license to use, reproduce, and create NOAA-derived and value-added products with the 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). NOAA Level-2 data products can be shared with unlimited distribution after 24 hours.

Furthermore, the Contractor shall provide NOAA the right to distribute all data to all U.S. Government agencies and foreign government or intergovernmental entities, including National Meteorological and Hydrological Services, WMO-designated Regional Specialized Meteorological Centers, members of the Coordination Group for Meteorological Satellites, university research centers, and other entities responsible for national meteorological, space weather, emergency response, or hydrological services, immediately after receipt at NOAA, for non-commercial use but not for further distribution.

In addition to data deliveries, the Government requests specific documentation to support understanding, usage, and validation of the data. Contractors shall define the distribution rights for the documentation required. All documentation provided that is marked as 'Proprietary' or 'Confidential'— including detailed instrument specifications and satellite engineering data—shall be treated as vendor-proprietary. NOAA agrees to protect such documentation from unauthorized disclosure and will not share, publish, or distribute it to non-NOAA entities or third parties without the express written consent of the Contractor.

NOAA will ensure that any non-NOAA entity receiving restricted data, including documentation, is made aware of the identified use and distribution restrictions associated with the data sharing rights specified in this contract. 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 this contract 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.

Section 3 - CONTRACT CLAUSES (TERMS AND CONDITIONS)

FAR 52.202-1 Definitions. (JUN 2020)

FAR 52.203-5 Covenant Against Contingent Fees. (MAY 2014)

FAR 52.203-7 Anti-Kickback Procedures. (JUN 2020)

FAR 52.203-12 Limitation on Payments to Influence Certain Federal Transactions. (JUN 2020)

FAR 52.203-17 Contractor Employee Whistleblower Rights. (NOV 2023)

FAR 52.204-19 Incorporation by Reference of Representations and Certifications. (DEC 2014)

FAR 52.226-8 Encouraging Contractor Policies To Ban Text Messaging While Driving. (MAY 2024)

FAR 52.227-14 Rights in Data-General. (MAY 2014) - Alternate II (DEC 2007)

(a) Definitions. As used in this clause-

Computer database or database means a collection of recorded information in a form capable of, and for the purpose of, being stored in, processed, and operated on by a computer. The term does not include computer software.

Computer software- (1) Means (i) Computer programs that comprise a series of instructions, rules, routines, or statements, regardless of the media in which recorded, that allow or cause a computer to perform a specific operation or series of operations; and

(ii) Recorded information comprising source code listings, design details, algorithms, processes, flow charts, formulas, and related material that would enable the computer program to be produced, created, or compiled.

(2) Does not include computer databases or computer software documentation.

Computer software documentation means owner's manuals, user's manuals, installation instructions, operating instructions, and other similar items, regardless of storage medium, that explain the capabilities of the computer software or provide instructions for using the software.

Data means recorded information, regardless of form or the media on which it may be recorded. The term includes technical data and computer software. The term does not include information incidental to contract administration, such as financial, administrative, cost or pricing, or management information.

Form, fit, and function data means data relating to items, components, or processes that are sufficient to enable physical and functional interchangeability, and data identifying source, size, configuration, mating and attachment characteristics, functional characteristics, and performance requirements. For computer software it means data identifying source, functional characteristics, and performance requirements but specifically excludes the source code, algorithms, processes, formulas, and flow charts of the software.

Limited rights means the rights of the Government in limited rights data as set forth in the Limited Rights Notice of paragraph (g)(3) if included in this clause.

Limited rights data means data, other than computer software, that embody trade secrets or are commercial or financial and confidential or privileged, to the extent that such data pertain to items, components, or processes developed at private expense, including minor modifications.

Restricted computer software means computer software developed at private expense and that is a trade secret, is commercial or financial and confidential or privileged, or is copyrighted computer software, including minor modifications of the computer software.

Restricted rights, as used in this clause, means the rights of the Government in restricted computer software, as set forth in a Restricted Rights Notice of paragraph (g) if included in this clause, or as otherwise may be provided in a collateral agreement incorporated in and made part of this contract, including minor modifications of such computer software.

Technical data, means recorded information (regardless of the form or method of the recording) of a scientific or technical nature (including computer databases and computer software documentation). This term does not include computer software or financial, administrative, cost or pricing, or management data or other information incidental to contract administration. The term includes recorded information of a scientific or technical nature that is included in computer databases. (See 41 U.S.C. 116).

Unlimited rights means the rights of the Government to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

(b) Allocation of rights. (1) Except as provided in paragraph (c) of this clause, the Government shall have unlimited rights in-

(i) Data first produced in the performance of this contract;

(ii) Form, fit, and function data delivered under this contract;

(iii) Data delivered under this contract (except for restricted computer software) that constitute manuals or instructional and training material for installation, operation, or routine maintenance and repair of items, components, or processes delivered or furnished for use under this contract; and

(iv) All other data delivered under this contract unless provided otherwise for limited rights data or restricted computer software in accordance with paragraph (g) of this clause.

(2) The Contractor shall have the right to-

(i) Assert copyright in data first produced in the performance of this contract to the extent provided in paragraph (c)(1) of this clause;

(ii) Use, release to others, reproduce, distribute, or publish any data first produced or specifically used by the Contractor in the performance of this contract, unless provided otherwise in paragraph (d) of this clause;

(iii) Substantiate the use of, add, or correct limited rights, restricted rights, or copyright notices and to take other appropriate action, in accordance with paragraphs (e) and (f) of this clause; and

(iv) Protect from unauthorized disclosure and use those data that are limited rights data or restricted computer software to the extent provided in paragraph

(g) of this clause.

(c) Copyright- (1) Data first produced in the performance of this contract. (i) Unless provided otherwise in paragraph (d) of this clause, the Contractor may, without prior approval of the Contracting Officer, assert copyright in scientific and technical articles based on or containing data first produced in the performance of this contract and published in academic, technical or professional journals, symposia proceedings, or similar works. The prior, express written permission of the Contracting Officer is required to assert copyright in all other data first produced in the performance of this contract.

(ii) When authorized to assert copyright to the data, the Contractor shall affix the applicable copyright notices of 17 U.S.C. 401 or 402, and an acknowledgment of Government sponsorship (including contract number).

(iii) For data other than computer software, the Contractor grants to the Government, and others acting on its behalf, a paid-up, nonexclusive, irrevocable, worldwide license in such copyrighted data to reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly by or on behalf of the Government. For computer software, the Contractor grants to the Government, and others acting on its behalf, a paid-up, nonexclusive, irrevocable, worldwide license in such copyrighted computer software to reproduce, prepare derivative works, and perform publicly and display publicly (but not to distribute copies to the public) by or on behalf of the Government.

(2) Data not first produced in the performance of this contract. The Contractor shall not, without the prior written permission of the Contracting Officer, incorporate in data delivered under this contract any data not first produced in the performance of this contract unless the Contractor-

(i) Identifies the data; and

(ii) Grants to the Government, or acquires on its behalf, a license of the same scope as set forth in paragraph (c)(1) of this clause or, if such data are restricted computer software, the Government shall acquire a copyright license as set forth in paragraph (g)(4) of this clause (if included in this contract) or as otherwise provided in a collateral agreement incorporated in or made part of this contract.

(3) Removal of copyright notices. The Government will not remove any authorized copyright notices placed on data pursuant to this paragraph (c), and will include such notices on all reproductions of the data.

(d) Release, publication, and use of data. The Contractor shall have the right to use, release to others, reproduce, distribute, or publish any data first produced or specifically used by the Contractor in the performance of this contract, except-

(1) As prohibited by Federal law or regulation (e.g., export control or national security laws or regulations);

(2) As expressly set forth in this contract; or

(3) If the Contractor receives or is given access to data necessary for the performance of this contract that contain restrictive markings, the Contractor shall treat the data in accordance with such markings unless specifically authorized otherwise in writing by the Contracting Officer.

(e) Unauthorized marking of data. (1) Notwithstanding any other provisions of this contract concerning inspection or acceptance, if any data delivered under this contract are marked with the notices specified in paragraph (g)(3) or (g) (4) if included in this clause, and use of the notices is not authorized by this clause, or if the data bears any other restrictive or limiting markings not authorized by this contract, the Contracting Officer may at any time either return the data to the Contractor, or cancel or ignore the markings. However, pursuant to 41 U.S.C.

4703, the following procedures shall apply prior to canceling or ignoring the markings.

(i) The Contracting Officer will make written inquiry to the Contractor affording the Contractor 60 days from receipt of the inquiry to provide written justification to substantiate the propriety of the markings;

(ii) If the Contractor fails to respond or fails to provide written justification to substantiate the propriety of the markings within the 60-day period (or a longer time approved in writing by the Contracting Officer for good cause shown), the Government shall have the right to cancel or ignore the markings at any time after said period and the data will no longer be made subject to any disclosure prohibitions.

(iii) If the Contractor provides written justification to substantiate the propriety of the markings within the period set in paragraph (e)(1)(i) of this clause, the Contracting Officer will consider such written justification and determine whether or not the markings are to be cancelled or ignored. If the Contracting Officer determines that the markings are authorized, the Contractor will be so notified in writing. If the Contracting Officer determines, with concurrence of the head of the contracting activity, that the markings are not authorized, the Contracting Officer will furnish the Contractor a written determination, which determination will become the final agency decision regarding the appropriateness of the markings unless the Contractor files suit in a court of competent jurisdiction within 90 days of receipt of the Contracting Officer's decision. The Government will continue to abide by the markings under this paragraph (e)(1)(iii) until final resolution of the matter either by the Contracting Officer's determination becoming final (in which instance the Government will thereafter have the right to cancel or ignore the markings at any time and the data will no longer be made subject to any disclosure prohibitions), or by final disposition of the matter by court decision if suit is filed.

(2) The time limits in the procedures set forth in paragraph (e)(1) of this clause may be modified in accordance with agency regulations implementing the Freedom of Information Act (5 U.S.C. 552) if necessary to respond to a request thereunder.

(3) Except to the extent the Government's action occurs as the result of final disposition of the matter by a court of competent jurisdiction, the Contractor is not precluded by paragraph (e) of the clause from bringing a claim, in accordance with the Disputes clause of this contract, that may arise as the result of the Government removing or ignoring authorized markings on data delivered under this contract.

(f) Omitted or incorrect markings. (1) Data delivered to the Government without any restrictive markings shall be deemed to have been furnished with unlimited rights. The Government is not liable for the disclosure, use, or reproduction of such data.

(2) If the unmarked data has not been disclosed without restriction outside the Government, the Contractor may request, within 6 months (or a longer time approved by the Contracting Officer in writing for good cause shown) after delivery of the data, permission to have authorized notices placed on the data at the Contractor's expense.

The Contracting Officer may agree to do so if the Contractor-

(i) Identifies the data to which the omitted notice is to be applied;

(ii) Demonstrates that the omission of the notice was inadvertent;

(iii) Establishes that the proposed notice is authorized; and

(iv) Acknowledges that the Government has no liability for the disclosure, use, or reproduction of any data made prior to the addition of the notice or resulting from the omission of the notice.

(3) If data has been marked with an incorrect notice, the Contracting Officer may-

(i) Permit correction of the notice at the Contractor's expense if the Contractor identifies the data and demonstrates that the correct notice is authorized; or

(ii) Correct any incorrect notices.

(g) Protection of limited rights data and restricted computer software. (1) The Contractor may withhold from delivery qualifying limited rights data or restricted computer software that are not data identified in paragraphs (b)(1)(i), (ii), and (iii) of this clause. As a condition to this withholding, the Contractor shall-

(i) Identify the data being withheld; and

(ii) Furnish form, fit, and function data instead.

(2) Limited rights data that are formatted as a computer database for delivery to the Government shall be treated as limited rights data and not restricted computer software.

(3) Notwithstanding paragraph (g)(1) of this clause, the contract may identify and specify the delivery of limited rights data, or the Contracting Officer may require by written request the delivery of limited rights data that has been withheld or would otherwise be entitled to be withheld. If delivery of that data is required, the Contractor shall affix the following "Limited Rights Notice" to the data and the Government will treat the data, subject to the provisions of paragraphs (e) and (f) of this clause, in accordance with the notice:

LIMITED RIGHTS NOTICE (DEC 2007)

(a) These data are submitted with limited rights under Government Contract No.

[______________] (and subcontract [_______________], if appropriate). These data may be reproduced and used by the Government with the express limitation that they will not, without written permission of the Contractor, be used for purposes of manufacture nor disclosed outside the Government;

except that the Government may disclose these data outside the Government for the following purposes, if any; provided that the Government makes such disclosure subject to prohibition against further use and disclosure: [ ](Agencies may list…