16WS Cloud Platform BPA

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. 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. 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. 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. 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. 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. Requirements The following section specifies the overall technological performance required under the BPA and Call Orders. 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. 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. Qualifying Characteristics of CSP Environment and Services The following section details specific Government requirements for CSP Environment and Services. 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. 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. 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…