QA2 - FA480326Q00960001 - Weather Service Intelligence.docx

QUESTIONS AND ANSWERS (Q&A) #2

Solicitation FA480326Q00960001 Project Title: Commercial cloud-based Weather Intelligence Service

ADMINISTRATIVE UPDATE: SOLICITATION AMENDMENT

Q1: PWS Section 5.1.2 references a "Unified Precipitation product." To align with performance-based contracting standards, will the Government accept any functionally equivalent multi-sensor merged precipitation product that utilizes various satellite and Numerical Weather Prediction (NWP) inputs?

A1: Yes. The Government is not seeking a specific commercial brand name or proprietary trade name. PWS Section 5.1.2 has been amended to require a generic "unified, multi-sensor merged precipitation product." Any functionally equivalent product that successfully fuses the required satellite, radar, and NWP inputs meets the Government's requirement.

Q2: Regarding PWS Section 5.2 (High-Resolution Probabilistic Regional Modeling), does the requirement for a 15-minute update cadence necessitate a full model re-initialization every 15 minutes, or will the Government accept a 15-minute output temporal resolution?

A2: The Government requires a 15-minute output temporal resolution (i.e., new data payloads delivered every 15 minutes), not a full model re-initialization every 15 minutes. A convection-permitting 3km physical ensemble providing 15-minute outputs satisfies the Government's requirement. PWS Sections 5.2 and 5.2.1 have been amended to clarify this distinction.

Q3: Regarding the 14-day Initial Operational Capability (IOC) timeline in PWS Section 9.1, would the Government accept a phased implementation schedule to broaden the field of capable offerors? For example, delivering core global capabilities at IOC, and reaching full operational capability for custom regional modeling at a later date?

A3: Yes, the Government will accept a phased delivery schedule. To meet IOC within fourteen (14) days, the Contractor must provision NIPRNet platform access, activate global AI forecasts and the alerting engine, and deliver the initial API/CDS data schemas. The high-resolution (3km) regional modeling over the CENTCOM AOR must reach Full Operational Capability (FOC) within thirty (30) days of contract award. PWS Section 9.1 has been updated accordingly.

Q4: Please clarify the security pathway requirements outlined in PWS Section 5.5.2 and Part VI. Must the platform be hosted in a FedRAMP-authorized cloud environment at the time of award, and will the Government sponsor the Authority to Operate (ATO) process?

A4: To maximize competition and align with commercial best practices, the PWS has been amended to remove the strict FedRAMP hosting requirement. The platform may reside in a standard commercial cloud environment, provided it utilizes industry-standard commercial cybersecurity best practices. Because the data will be delivered via the commercial internet to a Government Cross-Domain Solution (CDS) drop point, the Government will handle the sponsorship and accreditation for the data ingestion pathway. The Contractor must provide the necessary data schemas and security artifacts to support this approval process. A pre-existing, transferable DoD ATO is not required to bid or receive the award.

Q5: According to the Evaluation Factors for Award, will the Phase II live technical capability demonstration be required to take place in person at Shaw AFB, SC?

A5: No. The solicitation instructions have been amended to clarify that any requested live technical demonstrations will be conducted virtually (e.g., via Microsoft Teams). No physical travel or on-site presence at Shaw AFB, SC is required.

Q6: What are the anticipated award date and Period of Performance (PoP) dates for this contract?

A6: The anticipated award date is 1 July 2026. The Period of Performance will consist of a 3-month Base Period commencing 5-10 days after contract award (to allow for a post-award conference), followed by one 3-month option period and one 6-month option period.