Attachment 1_Statement of Need-04.01.2026.pdf

FA4600-XX-X-XXXX

Section J, Attachment 1

WEATHER APPLICATION PROTOTYPING,

CONTINUITY OF OPERATIONS,

AND

WEB PRESENCE PLATFORM

Overarching Statement of Need

01 April 2026

Statement of Objectives (SoN)

Applications

Vision Statement

To deliver to the Air Force Weather warfighter, combatant forces, and decision makers a web presence for rapid prototype numerical weather products, including Artificial Intelligence based Severe Weather

Decision tools and a platform for continued, collaborative sharing of the application of numerical weather products, and weather forecast techniques.

1 Introduction

This Statement of Need specifies the 16th Weather Squadron’s (16 WS) requirements for a new, sustainable cloud computing platform. To meet the ever-changing information environment, 16 WS must innovate and rapidly deploy capabilities to match the needs of the warfighter and be equipped to communicate the best practices and uses of provided numerical weather products. Additionally, Continuity of Operations (COOP) provided by cloud-based computing is critical in meeting the previously stated objectives. The requirement is the delivery of access to Amazon Web Services (AWS), a Cloud Service Provider (CSP) as defined by the DoD Cloud Computing Security Requirements Guide

(SRG) in the form of credits, where a credit relates to a dollar of CSP services as purchased by the

Government. The Contractor shall ensure the CSP is compliant with Federal Risk and Authorization

Management Program (FedRAMP) and the DoD Cloud Computing SRG. The CSP services/features shall comply with the Government’s requirements stated in this document.

This Statement of Need establishes the parameters for the BPA as well as overall goals, objectives, expectations, responsibilities, and nature of CSP credit delivery orders. The requirements identified within this Statement of Need are described in general terms. Each delivery order shall specifically address individual project requirements, project schedules, and other related performance criteria.

2 General Requirements

This section describes the general requirements for this BPA (Blanket Purchase Agreement). The following sub-sections provide details of various considerations concerning performance other than desired outcomes.

2.1 Business Relations

The Contractor shall coordinate all activity needed to deliver the required capabilities. The Contractor shall manage the timeliness, completeness, and quality of the overall contract, as well as the individual orders. The Contractor shall be transparent and provide timely notice of any real or perceived problems that affect the cost, schedule or performance of orders. The Contractor shall seek to ensure customer satisfaction and will ensure the ethical behavior of all Contractor personnel.

2.2 Closeout

For all orders, the Contractor shall complete all closeout actions and provide a final release of claims to the contracting officer within 180 calendar days after the delivery order is physically complete, as defined by FAR 4.804-4.

For the BPA contract, the Contractor shall complete all necessary closeout actions within one (1) calendar year after the BPA is physically complete, as defined by FAR 4.804-4.

2.3 Data Rights

Contractor will not have access to the data supplied to the CSP for the Government’s use of the Cloud.

Government retains all rights to data that it places into the Cloud. With respect to the CSP, the

Government shall have only the rights specified in the license under which the commercial computer software or commercial computer software documentation was obtained IWS R-DFARS 227.7202-3, Rights in commercial computer or commercial computer software documentation.

3 Requirements

The following section specifies the overall technological performance required under the BPA and Call

Orders.

3.1 Account Management

The Contractor shall provide the Government root credentials to any and all CSP accounts. The

Contractor will provide the Government, a Two-Factor Authentication (2FA) hardware token for each root account. The Contractor shall be responsible to maintain the payor account for all accounts provisioned with the CSP. At the conclusion of the BPA and Call Orders, the Government shall maintain all rights to the accounts and credentials as provided.

3.2 Usage Monitoring/Alerts

The Contractor shall provide the Government with a 24/7 real-time monitoring capability of credit usage.

Cautionary Levels of Usage shall be defined as 75% of credits expended. Critical Levels of Usage shall be defined as 85% of credits expended. The Contractor shall define what methodology they will utilize to notify the Government of cautionary and critical levels of usage. These levels specifically relate to usage that, if not changed, may cause the government to run out of credits before having the ability to order more. The Contractor shall notify the Government when credit usage reaches 75% (Cautionary Levels of

Usage) and 85% (Critical Levels of Usage) and may notify the Government more often at Contractor discretion. The Contractor shall coordinate with the Government means and time frames as required.

3.3 Qualifying Characteristics of CSP Environment and Services

The following section details specific Government requirements for CSP Environment and Services.

3.3.1 Available CSP Services/Features

The Contractor shall not prevent nor inhibit the use of any services/features (including AWS

Marketplace) which are made available to Commercial and/or Government users by the CSP.

3.3.2 AWS Well-Architected Framework

Contractor shall support the Government in provisioning an environment that is in line with AWS’s Well-

Architected Framework. For example, if the Government wishes to implement a multi-account solution, the Contractor shall make sure the Government has the ability to do so.

3.3.3 Deployment Locations/Regions

CSPs shall have the ability to deploy commercial and government CSP services to any and all available geographically-independent locations and/or regions offered by the CSP.

3.3.4 DoD Information Security Impact Level

CSPs shall have deployment locations or regions with authorization to operate at Impact Level 6 as defined by Department of Defense (DoD) Cloud Computing SRG. CSPs must be authorized to offer CSP capabilities in those US Government only regions up to IL4. Note: This Statement of Need is not explicitly soliciting classified computing, however this requirement ensures compatibility should future requirements require the need of classified computing resources. Although the ability to meet the DoD

SRG's Impact Level security guidelines is a military-specific requirement, CSP credits are a commercially-available item. CSP credits are available for sale to the public, and are considered a commercial item.

3.4 Expenditures

The Contractor shall hold Amazon Partner Status for Resale before contract award. The Contractor will make CSP services/features available to the Government in the form of credits and must be capable of providing payment services (credits) on behalf of wholly government operated accounts. Credits will have an equivalency of $1.00 USD of AWS commercial list price per credit. The unit price established in the award of the BPA shall include any discounts or mark-ups passed on to the Government by the CSP provider. Credits will be valid from date of purchase for a period not to exceed 12 months. Each TO will remain active during this 12-month period and the Contractor will be allowed to invoice each month for the credits used during that month. Any credits remaining at the end of the 12-month period will be de-scoped at the original value and all remaining funds will be de-obligated to zero out the balance on the TO for close out purposes. The contractor shall not invoice or be compensated for any credits the

Government does not use. Although the CSP credits themselves do not require a long lead time, there is an anticipated 45 day lead time from contract award to initial delivery. The reason for this lead time is the

16WS requires 45 days to establish a new account, due to security checks and agreements that must be put into place.

3.4.1 Utilization of Credits

Billing rates for the Government’s credits shall be at a pass-through rate for AWS’s advertised commercial list price at the time of the Government’s credits usage; reflecting any discounts or mark-ups established at the unit price of the BPA award. Example: Where there is a 5% discount applied, on a bill from Amazon of $1,000, the contractor would only deduct $950 credits from the Government account.

3.4.2 Discounts from CSP List Rates

If the Contractor offers a discount off of AWS commercial list prices, those discounts as defined during solicitation will be applied for the life of the ordering period. The contractor must perform on all orders at these rates as set at the time of award. The contractor cannot refuse any valid order at these rates.

3.4.3 Funds and Usage Expenditure Report (CDRL A004)

The Contractor shall provide a Funds and Usage Expenditure report (CDRL A004), on a monthly basis.

Details shall be provided in CDRL A004 concerning purchase of credits, listed by type; Delivery Order or Government Purchase Card (GPC).

Details shall be provided in CDRL A004 of cost allocation in terms of credits or dollars on a monthly basis, at a minimum. When requested by the Government, the Contractor shall provide a non-monthly report of cost allocation within two (2) business days. Cost Allocation reports provided by the Contractor shall be broken down by CSP cost allocation tagging and user-defined cost allocation tagging, as available by the CSP.

4 Special Requirements

This section describes special requirements. This includes Government furnished property, Government facilities, operational security, and mail.

4.1 Government Furnished Property (GFP)

There shall be no Government furnished property for the considerations of this BPA.

4.2 Government Facilities

There shall be no requirements for performance on-site, and no Government Facilities will be provided for the considerations of this BPA.

4.2 Operational Security (OPSEC)

The Contractor shall report to the Government within 1 (one) business day of any breaches, potential breaches or targeted attacks with regards to operations between the Contractor and the Government.

4.3 Purchase of Credits by Government Purchase Card

The resulting contracting will include pre-negotiated rates for credits. Therefore, FAR 52.232-36, Payment by Third Party will be included in the final contract to allow the use of a Government-Wide

Commercial Purchase Card (GPC) for purchases up to $25,000.00.

If requesting pre-priced products/items via GPC, the Weather Wing-designated GPC holder shall notify the contractor in writing or by phone of the project request. All project requests shall contain the contract number and the line items from the contract bid schedule proposed to be utilized (including quantities).

The GPC holder shall follow the GPC policies as outlined in AFI 64-117 and any internal procedures for placing orders via the GPC. This contract does not supersede any GPC rules or regulations. All GPC purchases are subject to the terms and conditions of this contract and the amount of each GPC purchase shall count towards the contract minimum and maximum amounts.

All projects over $25,000.00 will require issuance of a Delivery Order (SF-1449 or equivalent). Project requests must be submitted to the contracting office. Contracting will execute a new Delivery Order for each request.