NOAA C_EOGSS RFI.pdf

Request For Information (RFI)

NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION (NOAA)

COMMERCIAL ENTERPRISE OPERATIONS AND GROUND SYSTEM

SERVICE

A.1 General Information

This Request for Information (RFI) is issued for planning purposes only. The National Oceanic and Atmospheric Administration (NOAA) is not at this time seeking proposals and will not accept unsolicited proposals. Only material suitable for internal government distribution shall be submitted. Any proprietary information should be marked accordingly. No classified information should be included in your response to this RFI. The U.S. Government will protect any information received from respondents that is marked proprietary, and distribution of any material will be based on a strict need-to-know basis. The Government reserves the right to use any non-proprietary information provided by respondents for any purpose deemed necessary and legally appropriate, including using technical information provided by respondents in any resultant solicitation. Note that the submissions may be subject to review by experts outside of the civil service such as NOAA contractors (e.g. The Aerospace Corporation), each of whom would sign non-disclosure agreements as required. This exchange of information must be consistent with procurement integrity requirements. See Federal Acquisition Regulation (FAR) 3.104. Respondents to this RFI may include potential offerors, end users, Government acquisition and supporting personnel, and others with an interest in the conduct or outcome of the potential acquisition.

RFI Release Date: September 2, 2025

Questions Due Date: September 12, 2025 at 2:00 PM Eastern Time

Response Due Date: October 3, 2025 at 2:00 PM Eastern Time

Set Aside: To Be Determined

Classification Code: D - Information Technology Services

NAICS Code(s): 541330 – Engineering Services

A.1.1 Purpose

NOAA is looking for information on opportunities to reduce operational costs through commercialization of satellite operations, as well as satellite command and control functions, via procurements under FAR Part 12, Acquisition of Commercial Products and Commercial Services. This RFI outlines the potential activities for transitioning the current on-orbit operations responsibilities for the Joint Polar Satellite System (JPSS) and Geostationary Operational Environmental Satellites (GOES)-R constellations, as well as Space Weather Follow On-Lagrange 1 (SWFO-L1) observatory, to a commercial satellite operations service. The Government also requests information on commercial services’ ability to support the launch, early orbit, and activation of future JPSS missions, including the new JPSS spacecraft planned to launch in Government Fiscal Year (FY) 2028 (NOAA-22) and FY2033 (NOAA-23). This RFI does not include scope for any other planned and/or forecasted NOAA Missions.

Additionally, the Government does not intend to prescribe or preclude specific technical solutions or combinations of solutions in response to this RFI. Furthermore, respondents may provide information on how they can facilitate commercial operations or ground system services for any subset of scoped missions. However, it is the Government's intent to gain market research on how commercial industry is capable of operating all current on-orbit constellations, specifically JPSS, GOES-R, and SWFO-L1, utilizing a single commercial satellite operations service.

A.1.2 Background

Joint Polar Satellite System NOAA’s JPSS satellite system is NOAA’s flagship Low Earth Orbit (LEO) mission and is the primary data source for NOAA LEO observations. The JPSS constellation offers the advantage of daily global coverage, by making polar orbits nearly 14 times per day approximately 520 miles above the surface of the Earth. The orbits are circular, with an altitude around 830km, an afternoon Mean Local Time of the Ascending Node (MLTAN) of 1330 and are sun synchronous. The Earth's rotation allows the satellite to see a different view with each orbit, and each satellite provides two complete views of weather around the world each day. Currently, NOAA operates three JPSS satellites - NOAA-21, NOAA-20, and Suomi National Polar-orbiting Partnership (SNPP), all of which are capable of performing propellant based maneuvers and require a controlled reentry into earth's atmosphere upon end of mission. S-NPP is slated for decommissioning in FY26, with JPSS 4 (NOAA-22) slated for launch in FY28, and JPSS 3 (NOAA-23) in FY33. Status on the current operations of the NOAA JPSS satellites as well as orbital characteristics can be further found at the following URL:

https://www.ospo.noaa.gov/operations/jpss/status.html

Current JPSS operations capabilities utilize a single northern hemisphere and a single southern hemisphere downlink per orbit. The Government ground stations are located at Svalbard, Norway, McMurdo Station, Antarctica and Fairbanks, Alaska, as well as commercial services from Kongsberg Satellite Services (KSAT) at Svalbard, Norway and Troll, Antarctica, all of which support communication with the observatories over X-Band (SNPP) or Ka-Band (JPSS) for the downlink of observatory science data and S-Band for command and control functions. The satellites support a secondary service with the transmission of real-time imager and sounder data to the international user community utilizing a single https://www.ospo.noaa.gov/operations/jpss/status.html

X-band transmitter. Further information on the JPSS High Rate Downlink (HRD) Services utilized by the JPSS Mission can be found at the following URL:https://noaasis.noaa.gov/POLAR/JPSS/jpss.html

Further information on the JPSS Constellation can be found at:

https://www.nesdis.noaa.gov/our-satellites/currently-flying/joint-polar-satellite-system

Geostationary Operational Environmental Satellites NOAA’s latest generation of Geostationary Operational Environmental Satellites, the GOES-R Series, is the Nation’s most advanced fleet of geostationary weather satellites. The GOES-R Series is a four-satellite program within the National Environmental Satellite, Data, and Information Service (NESDIS) that includes GOES-16, GOES-17, GOES-18 and GOES-19, each with an expected operational lifetime of 15 years. NESDIS’s Geostationary Earth Orbit (GEO) satellite Ground System is the infrastructure for managing the satellites as well as generating and distributing satellite products and services. The 24/7 global coverage provided by NESDIS generates an uninterrupted stream of information and products for the Western Hemisphere.

The GEO Ground System provides the infrastructure and common services to support the GOES-R Constellation, via the Antenna (ANT), Mission Management (MM) and Data Operations (DO) elements.

Commanding via the GEO Ground System’s MM element currently occurs out of the NOAA Satellite Operations Facility (NSOF) in Suitland, MD with uplink capability provided by the Antenna element at Wallops Command and Data Acquisition Station (WCDAS) in Wallops, VA (primary) and at the Consolidated BackUp facility (CBU) in Fairmont, West Virginia (backup). MM supports the GOES-R Constellation with mission planning, spacecraft control, observatory command and telemetry, observational data acquisition and data routing. GOES-R observational data received by MM at the NOAA WCDAS and CBU sites is transferred to the GEO Cloud Compute System (GCCS) where it is used by the DO element to create Level 0, Level 1b, and Level 2 weather products, as well as GOES Rebroadcast (GRB). The DO element performs all Level 1 and Level 2 product generation supporting ingest into National Weather Service Predictive Models utilizing real-time GOES-R observations.

Further information on the GOES-R Constellation can be found at:

https://www.nesdis.noaa.gov/our-satellites/currently-flying/geostationary-satellites

Further information on the GOES Unique Payload Services (UPS) can be found at:

https://www.noaasis.noaa.gov/GOES/GRB/grb.html https://www.noaasis.noaa.gov/GOES/HRIT/about_hrit.html https://www.noaasis.noaa.gov/GOES/GOES_DCS/goes_dcs.html https://www.sarsat.noaa.gov/search-and-rescue-satellites/

Space Weather Follow On (SWFO) The Space Weather Follow On (SWFO) Program sustains NOAA’s foundational set of space-based space weather observations and measurements collected by legacy missions, to ensure continuity of critical space weather data to the National Weather Service’s (NWS) Space Weather Prediction Center (SWPC).

To achieve these objectives, the SWFO program is preparing to launch the Space Weather Follow On – Lagrange 1 (SWFO-L1) Observatory to orbit at the first Sun-Earth Lagrange point (L1) with the goal of https://noaasis.noaa.gov/POLAR/JPSS/jpss.html https://www.nesdis.noaa.gov/our-satellites/currently-flying/joint-polar-satellite-system https://www.nesdis.noaa.gov/our-satellites/currently-flying/geostationary-satellites https://www.noaasis.noaa.gov/GOES/GRB/grb.html https://www.noaasis.noaa.gov/GOES/HRIT/about_hrit.html https://www.noaasis.noaa.gov/GOES/GOES_DCS/goes_dcs.html https://www.sarsat.noaa.gov/search-and-rescue-satellites/ providing continuous measurements of the space environment, including observations of the Sun’s outer atmosphere, and contributing to accurate forecasts of space weather disturbances.

The SWFO Ground Segment includes a SWFO Antenna Network (SAN) with ground antennas distributed globally for real-time 24/7 data collection of SWFO-L1 data, a mission operations element for Command and Control (C2) of the SWFO-L1 Observatory, and a Product Generation and Distribution (PGD) element for near-real time science data processing. Primary C2 operations for SWFO-L1 will be performed at the NSOF in Suitland, MD where SWFO C2 shares some infrastructure with the GEO Ground system, and will use the CBU as the backup operations facility. C2 supports the SWFO-L1 mission with mission planning, spacecraft control, observatory command and telemetry functions, trending and analysis, plus observational data consolidation, Level 0 processing, and routing. The SAN is a globally-distributed antenna network that will provide continuous coverage for SWFO-L1 data acquisition. Dual S- and X-band ground antennas are located at WCDAS in Wallops, VA and at CBU in Fairmont, WV. X-band receive-only antennas are located around the world to complete the global coverage enabling continuous downlink of space weather observational data. Data will be transmitted from the SAN to C2 for data consolidation and then forwarded to PGD.

Further information on the SWFO-L1 observatory can be found at:

https://www.nesdis.noaa.gov/our-satellites/future-programs/space-weather-follow-program

Information on the NOAA Command and Data Acquisition Stations (CDAS) can be found at:

https://www.nesdis.noaa.gov/about/our-offices/office-of-satellite-and-product-operations-ospo/fairbanks-c ommand-and-data-acquisition-station-fcdas https://www.nesdis.noaa.gov/about/our-offices/office-of-satellite-and-product-operations-ospo/wallops-co mmand-and-data-acquisition-station

A.1.3 Terms

● “Government” or “Government representatives” means federal Government personnel and Government support contractor personnel.

● “Vendor” means all Contractor, Subcontractor and/or Academia support utilized within the scope of this RFI.

● “Observatory” refers to the spacecraft bus fully or partially integrated with one or more flight instruments.

● “JPSS Constellation” refers to the current On-Orbit NOAA-21 and NOAA-20 observatories as well as any planned to be launched observatories, as required.

● “Multi-Constellation" refers to the existing GOES-R On-Orbit observatories, SWFO observatory, as well as the On-Orbit JPSS observatories including any planned to be launched, as required.

https://www.nesdis.noaa.gov/our-satellites/future-programs/space-weather-follow-program https://www.nesdis.noaa.gov/about/our-offices/office-of-satellite-and-product-operations-ospo/fairbanks-command-and-data-acquisition-station-fcdas https://www.nesdis.noaa.gov/about/our-offices/office-of-satellite-and-product-operations-ospo/fairbanks-command-and-data-acquisition-station-fcdas https://www.nesdis.noaa.gov/about/our-offices/office-of-satellite-and-product-operations-ospo/wallops-command-and-data-acquisition-station https://www.nesdis.noaa.gov/about/our-offices/office-of-satellite-and-product-operations-ospo/wallops-command-and-data-acquisition-station

A.2 Key Operational Performance and Latency Requirements

The Government wants to explore the ability for a commercial vendor to assume responsibility for operations for the JPSS constellation for the remainder of the mission lifecycle (through FY2038), in adherence to the core JPSS Level 1 Requirements. At minimum, a vendor would need to meet the following JPSS performance and latency requirements, but the Government would like to know how these requirements could be exceeded by vendors’ unique approaches; specifically:

a. Downlink of JPSS Stored Mission Data (SMD) with a latency of less than 87 Minutes for the Primary JPSS Observatory.

b. Operational Availability of each Observatory greater than or equal to 98% over any 30 day period for the mission lifetime.

c. Maintain each Observatory in a polar sun-synchronous orbit with the following characteristics: altitude of 824 +/- 17 kilometers, ground track repeat accuracy of 20 km at the Equator with a repeat cycle less than 20 days, and ascending equator crossing time of 1330 +/- 10 minutes.

d. On a 30-day basis, at least 99% of the data collected by each JPSS Observatories’ operational sensors shall be delivered to the Government’s data processing system.

e. Notify the Government of the execution of any JPSS Contingency procedures, On-Orbit Anomalies, and/or other irregular items (e.g. Limit Violations) within 30 Minutes of an identified event.

Together with the above, the Government wants to explore the ability for a commercial vendor to assume operations for the GOES-R constellation for the remainder of the mission lifecycle (through FY2040), in adherence to the core GOES-R Level 1 Requirements (410-R-LIRD-0137). At minimum, a vendor would need to meet the following GEO performance and latency requirement, but the Government would like to know how they could be exceeded by vendors’ unique approaches; specifically:

a. GOES East shall be centered in the Eastern operating zone at 75° W longitude and cover an area bounded by 68° North and South latitudes, 148° West to 2° West longitudes.

b. GOES West shall be centered in the Western operating zone at 137° W longitude and cover an area bounded by 68° North and South latitudes, 150° East to 64° West longitudes.

c. Maintain the spare GOES Spacecraft(s) in an on-orbit geosynchronous storage location of 105° W longitude capable of periodic check out in storage, as required.

d. Maintain a mission availability of 0.80 over the operational lifetime for the combination of the specified operational coverage areas.

e. In the event of a failure of a primary GOES East/West satellite, where an on-orbit spare GOES spacecraft is available to adequately replace the failed primary, the Maximum Time to Restore Service (MaxTTRS) shall not exceed three weeks.

f. Provide continuous (with outages less than 6 hours per year) sensor data for ground science products.

g. In the event of a failure of a ground site, the failover time to a backup site for those functions supporting the GOES constellation, the Maximum Time To Restore (MaxTTR) functionality related to system health and safety shall be no greater than 5 minutes.

h. Provide continuous (with outages less than 75 hours per year) sensor data for ground generation of coronal mass ejection L0 data.

i. Ensure the continuation of GOES Series unique payload services (UPS) as a Observatory Pass-Through capability, such as GOES Rebroadcast, High Rate Information Transmission (HRIT), Emergency Manager Weather Information Network (HRIT/EMWIN), Data Collection System (DCS) and GEO Search and Rescue

(GEOSAR).

Because the SWFO-L1 mission shares infrastructure with the GOES-R missions, the Government wants to explore the ability for a commercial vendor to assume operations for the SWFO-L1 Observatory for the remainder of the mission lifecycle (through FY2035), in adherence to the core SWFO Level 1 Requirements. At minimum, a vendor would need to meet the following SWFO-L1 performance and latency requirement, but the Government would like to know how they could be exceeded by vendors’ unique approaches; specifically:

a. Maintain spacecraft and instrument operations at the Sun-Earth Lagrange Point 1

b. Ensure all Coronal White Light Imagery data is delivered to the Government product processing interface within 16 seconds of ground antenna receipt.

c. Ensure all Solar Wind data available to the Government within 16 seconds of ground antenna receipt.

d. Maintain delivery to the Government of two Coronal White Light images, acquired no less than 5 minutes apart, for each observable CME traveling towards Earth.

e. During NWS-declared Critical Space Weather Days, ensure in situ Solar Wind data gaps do not exceed 5 minutes per day for planned spacecraft events.

f. During nominal operations, the SWFO Spacecraft shall deliver operational coronal White

Light Imagery data to the Government at least 96 percent of the time measured over each and every 30-day period.

g. During nominal operations, the SWFO Spacecraft shall deliver operational Solar Wind data to the Government at least 96 percent of the time measured over each and every 30-day period.

A.3 Commercial Operations and Ground System Services Scope

The Government is looking to gain understanding through market research on how industry could provide capabilities and services that partially or fully replace existing Government satellite operations capabilities in innovative ways while maintaining ongoing operations of each NOAA constellation with dramatically reduced life cycle costs, at best value. The following commercial services should be considered in response to this RFI’s identified scope.

Commercially-Provided Ground System Services

1. Command, Control and Communications Segment (C3S) capabilities to facilitate NOAA

Multi-Constellation observatory science collection, by existing commercial physical and/or FedRAMP-approved Cloud Services, in a Service Level Agreement (SLA)-like approach.

a. The primary functions included in C3S are Command and Control, Mission Planning and Scheduling, Trending and Analysis, retention of telemetry data for the life of the mission, Flight Dynamics, Conjunction Analysis, as well as (where appropriate) Ground Station Radio Frequency (RF) uplink/downlink space-ground communications functionality

i. Operations of each spacecraft(s) payloads could include Vendor support for one or more of the below items, as applicable:

1. Execution of Instrument Calibration Activities (e.g. ACS, Instruments)

2. Development and maintenance of Instrument Calibration Tables, with the

Government’s input

3. Perform planning and execution of Government Directed Special

Activities (e.g., Mesoscale Scan Requests, etc…)

4. Maintain the operations of Key Pass-Through Services, as applicable

(e.g., GEOSAR, GRB, Direct Broadcast, etc.)

b. Maintain the Commercial C3S Capabilities in a manner consistent with a FISMA High

Impact Level and with the appropriate NIST 800-53 IT Security Controls and/or commercial equivalents under NIST SP 800-171

c. Modularity of proposed C3S Services and their ability to allow for further enhancement, replacement and/or modification to support a 13 Year Ground System Operations Lifecycle

d. Capability to maintain Continuity of Operations in case of major or minor outages.

2. Maximize the use of Commercial Services for any Ground System functionality supporting

Multi-Constellation Operations

3. Ability to provide Science Mission Data back to the Government for Science Processing in a

Cloud Native location once downlinked at a Ground Station, while continuing to meet or exceed the earlier identified JPSS, GOES, or SWFO latency requirements and with minimal change to existing Government Cloud-based Data Processing Systems

Commercially-Provided Operations and Engineering Staff The Government is interested in understanding vendors' capabilities to support Multi-Constellation mission operations and requests information on commercially operated alternative approaches to provide satellite controllers and engineering support staff. It is expected Government shall only be notified and included in any contingency and/or anomaly activities that pertain to the Multi-Constellation Observatories.

a. Utilization of Commercial Operational Engineers and Controllers to support ongoing Multi-Constellation mission operations on the vendors C3S capabilities

b. Use of commercial operations staff to support pre-launch; launch, early orbit, and activation (LEO&A); and post-launch commissioning activities for future JPSS Spacecraft

c. Use of commercial operations staff to support the decommissioning of JPSS Spacecraft via controlled reentry at the end of their mission life and/or GOES-R orbit raising at the end of their mission life and/or the vacating of the SWFO observatory from L1.

d. Use of automation to facilitate operations in support of ongoing Multi-Constellation Mission operations, as well as maintaining ongoing science observations

A.3.1 Government Furnished Property The Government currently has existing functionality available and could provide specific capabilities to the Vendor as Government Furnished Property (GFP), as requested. Examples include, but are not limited too:

● Government Subject Matter Experts (SME)

● Spacecraft and Instrument Simulators

● Satellite and Payload Vendor reachback support, as applicable

● NOAA IT Security Tools or Security Technical Implementation Guides (STIGs)

● Communications Security (COMSEC) Encryptors and COMSEC Key Material

● Existing JPSS, GOES-R, and SWFO Ground System baseline, including hardware, software, scripts, operations products, databases, procedures, and associated documentation

● Conjunction Assessment and Risk Assessment (CARA) capabilities

● NASA Tracking and Data Relay Satellite (TDRS) and/or NASA Commercial Data Relay support for launch, early orbit, anomaly resolution, and decommissioning activities

● GSA FedRAMP-approved Cloud Services, https://www.fedramp.gov/, via the NOAA Enterprise

Cloud Contract

● Limited facilities space at the NSOF, WCDAS, and CBU NOAA facilities

A.3.1.1 Government Furnished Property - NOAA Ground Station Services

For purposes of providing a response, interested sources may consider the following Government Radio Frequency (RF) Ground Station resources as available for utilization in the scope of your proposed response, if deemed advantageous and cost effective to your proposed service implementation. The Government is interested in understanding vendors' interfaces and constraints in utilizing Government antennas across LEO, GEO and L1 Orbits. Where possible, please identify any impacts (Technical, Cost, etc.) when using Government antennas instead of Commercial Services. General antenna services that vendors can include in their response are as listed below:

Location Ownership Size Tx Bands Rx Bands

Svalbard, Norway NOAA 13m, 4m S S, L, X, Ka

Fairbanks, AK NOAA 13m, 5m, 4m S, L S, L, X, Ka

McMurdo, Antarctica NOAA 4m None S, Ka

Wallops, VA NOAA 26m, 18m, 16.4m, 14.2m, 13m, 9m, 8m, 7.2m S, L, X S, L, X

Fairmont, WV NOAA 16.4m, 13m S, X S, L, X https://www.fedramp.gov/

A.4 Request for Information

The Government would like to hear from both academia and industry on potential frameworks to best support maintaining NOAA’s Multi-Constellation extended science operations activities while meeting the above identified NOAA long-term objectives/priorities. Sources intending to respond to this RFI should thoroughly review the aforementioned and submit the following information:

● Reference Architecture and Concept of Operations for all, or part, of the Multi-Constellation Mission operations as described above, including details pertaining to software applications, network topologies, requested cloud services and/or physical equipment or facilities.

○ If or how the proposed solution meets, or has the potential to meet through modifications, the Federal Acquisition Regulation (FAR) 2.101 Definition of a "commercial item."

○ Describe if or how a solution can meet the FAR 2.101 definition of a commercial item if modifications are required, and discuss the time frame involved.

● Identification of any requested Government Furnished Property (GFP) or Government Furnished Information (GFI) and any expected modifications required to support the Vendor’s Reference Architecture and Concept of Operations

● Business models and cost structures for transitioning from Government-owned Ground Systems to commercially provided capabilities.

● Processes as well as assumptions for how to transition operations from the Government Ground Systems to a Vendor-provided solution if possible, within a single calendar year (365 Days).

● Any Potential Risks and/or Issues for the Government to consider, including but not limited to, Information Technology (IT) Security, schedule, or programmatic considerations

○ Recommended approaches to reduce or otherwise mitigate risk for the Government's consideration

● Rough Order of Magnitude (ROM) Cost Estimate to support on-orbit operations of NOAA’s Constellations, including new JPSS launches, through FY2040, Operations, and any required Ground System modifications necessary to maintain operations or IT Security compliance over that period. For streamlining purposes, you are highly encouraged to use the ROM template that is attached to this RFI.

○ The estimate should include any assumptions and should highlight major cost drivers and opportunities for cost savings such as trade-offs between development costs for automation and operations costs/staffing.

○ Provide any published catalog pricing, as applicable.

● Identification of potential Acquisition Strategies, Studies, Cost Sharing, Contract Types and/or service level agreements for data delivery to support the identified Scope of Work and provide best value to the Government

○ Identification of potential NAICS and PSC code(s) this work would fall under based on the Vendor/s Reference Architecture and Concept of Operations.

○ Estimation if the majority of the effort and cost will be for computing services and/or engineering services

● Identification of what data rights respondents would anticipate under a future contract(s), to the extent that they would deviate from the standard data rights clauses 52.227-14 Rights in Data-General, 52.227-17 Rights in Data-Special Works, and 52.227-19 Commercial Computer Software License.

● Any additional Special Considerations and/or Opportunities the Government should otherwise consider

A.5 RFI Submission Instructions

Responses are limited to no more than 30 pages (applicable document comments and cost ROM spreadsheets not included), and should be submitted via email by October 3, 2025, at 2:00 PM Eastern Time to the point of contact listed below. The subject line of the submission should be “RFI for Commercial Enterprise Operations and Ground System Service” and attachments should be in Word or searchable PDF format (except the applicable document comments spreadsheet). If your organization is interested in a potential opportunity to provide additional information via virtual one-on-one discussions in the October/November 2025 timeframe, please indicate your intent by contacting the point of contact listed below.

SOURCES SOUGHT: Responses from large and small businesses are encouraged; however, in accordance with FAR 19.5, set-asides for small business; the Government will review the information in this announcement to determine the type of set aside (if any) for this requirement. Please provide the size status of your company based on NAICS 541330 – Engineering Services, with a size standard of $15 million. All questions about the RFI shall be directed by email to the point of contact listed below prior to Friday, September 12, 2025 at 2:00 PM Eastern Time. Please include the following:

● Identification of your firm's business size and identification of your firm’s CAGE Code and Unique Entity Identifier (UEI). Note: The NAICS Code for this requirement is 541330 – Engineering Services.

● Your firm’s presence (if any) on Government-Wide Contract Vehicles (e.g. GSA MAS, NASA SEWP, GSA OASIS, etc…) that can support this effort. Include your firm’s presence (if any) on NOAA-awarded Indefinite Delivery Indefinite Quantity contracts or Blanket Purchase Agreements that can support this effort.

● Capability statements expressing your firm’s interest in this requirement, describing your company and its capability and experience to meet the minimum requirements stated in this RFI with a description of your proposed services and/or supplies that would meet the requirements.

Interested parties should provide sufficient detailed information which demonstrates the technical capability of the proposed solution. This shall include a discussion on your firm’s estimated timeframe for delivery or performance.

Responses shall be sent via electronic mail to:

Ms. Sarah McKim Contracting Officer sarah.mckim@noaa.gov

Ms. Keami Estep Contract Specialist (contractor) keami.estep@noaa.gov mailto:sarah.mckim@noaa.gov