Statement of Work

Section 1.0 - Background

The U.S. Air Force requires specialized software to provide meteorological and weather forecasting personnel with advanced radar data display and analysis capabilities. This software is critical for generating decision-quality weather intelligence to support military flight operations, tactical missions, and installation safety.

The primary purpose of this software is to display and analyze data collected by the 158 WSR- 88D Doppler Weather Radars operated under the Tri-Agency NEXRAD Program. The solution must also be capable of displaying and analyzing archived WSR-88D data, as well as radar data from other weather systems that comply with the WSR-88D Interface Control Document (ICD) standards. This includes the Air Force AN/TMS-2 Portable Doppler Radar.

Additionally, the software must be capable of acquiring data from the NEXRAD program's Radar Product Central Collection/Distribution Service (RPCCDS), which is the NEXRAD Program solution for the collection and distribution of data from all Air Force, National Weather Service (NWS), and Federal Aviation Administration (FAA) owned WSR-88D weather radars.

Section 2.0 - Technical Requirements

1. Display and interrogate NEXRAD Level 3 Data

"The software must display and interrogate all standard NWS NEXRAD Level 3 products, to include: Reflectivity, Mean Radial Velocity, Spectrum Width, and Dual-Polarization variables (Differential Reflectivity [ZDR], Correlation Coefficient [CC], and Specific Differential Phase [KDP]). It must include interactive cursor readouts for exact coordinate data value querying."

2. Display and interrogate NEXRAD Level 2 Data

"The software must display and manipulate super-resolution NEXRAD Level 2 data. It must provide real-time volume rendering, cross-section profiling (vertical and horizontal), and 3D volume visualization of Level 2 base data without latency-induced degradation of the workstation."

3. Ingest Data from AF NEXRAD Local Data Manager

"The software must natively ingest, and automatically directory-monitor real-time data feeds pushed via the Air Force NEXRAD Local Data Manager (LDM) / Unidata LDM protocol without requiring third-party format conversion tools."

4. Display and interrogate data from AN/TMS-2

"The software must directly display, calibrate, and interrogate polar and radial data files generated by the AN/TMS-2 Tactical Weather Radar (TWR) system, preserving the native resolution and metadata of the tactical radar."

5. Display archived radar data

"The software must allow local loading, indexing, and seamless chronological playback/looping of historical, archived Level 2 and Level 3 data files (e.g., from NCEI/NOAA) completely offline without requiring an internet connection."

6. Capable of use on AF SDC and Army Gold Disc computers

"The software must be fully compatible with the Air Force Standard Desktop Configuration (SDC) and Army Gold Disc (AGD) operating environments. It must run successfully as a standard user without requiring local administrative privileges and must comply with DISA Application Security Technical Implementation Guides (STIGs)."

7. Supports Secure Transfer Protocols

"The software must support secure data transmission and authentication using SFTP, HTTPS, and SSH protocols utilizing FIPS 140-2/3 validated cryptographic modules."

Derivation Notes:

Requirements 1.2, and 5 are derived from the NEXRAD Joint Operational Requirements (JOR) document.

Requirement 3 is derived from the NEXRAD Program communications architecture and Radar Product Central Collection and Dissemination Service (RPCCDS) solution.

Requirement 4 is derived from the Tactical Weather Radar (TWR) Operational Requirements Document (ORD).

Requirements 6 and 7 are derived from Air Force and Army Cybersecurity requirements.

Section 3.0– License Requirements

The Government requires perpetual, transferable licenses for the proposed software. The licenses must permit installations and use by all authorized U.S. Air Force and U.S. Army personnel and their support contractors.

The licenses must be transferable, allowing the Government to deactivate a license on a retired or re-imaged machine and reactivate it on another without requiring vendor intervention, administrative delays, or incurring additional costs.

The procurement requirement is divided into two distinct licensing categories as outlined in the table below:

License Category Quantity Description

Full Perpetual License 80 New, comprehensive software licenses providing full operational and analytical capabilities.

Upgrade Licenses 590 Licenses dedicated to upgrading existing, previously fielded software versions to the current version.

Total Scope 670 Total combined software footprint to be managed under this agreement.

Vendors must describe their licensing verification mechanism (e.g., license keys, server-based authentication, or offline verification files) and confirm that all 670 licenses can be easily managed and transferred across Air Force and Army environments.

Section 4.0 – Delivery Method

Within thirty (30) days After Receipt of Order (ARO), the vendor shall deliver all required products electronically. Delivery must be executed via a secure electronic download portal (e.g., DoD SAFE or a vendor-provided secure HTTPS portal utilizing FIPS-validated cryptography).

The electronic delivery package must contain:

• Software installation binaries compatible with the environments specified in Section 2.0.

• The required 670 perpetual software license keys (80 full, 590 upgrade) as specified in Section 3.0.

• Complete technical documentation, including software installation manuals, administration guides, and user manuals.

• All necessary cybersecurity documentation, including STIG compliance checklists, software vulnerability reports, and a Software Bill of Materials (SBOM) to support the network authorization process.

Section 4.1 – Delivery Schedule

All deliverables must be completed in accordance with the schedule below:

Deliverable Item Delivery Method Timeline

Initial Delivery Package (Binaries, Documentation, Security Files)

Secure Electronic Download

No later than 30 days ARO

License Keys (80 Full, 590 Upgrade)

Secure Electronic Delivery No later than 30 days ARO

Section 5.0 – Maintenance and Support

The initial software purchase shall provide perpetual licenses for the current major version of the software. The purchase price must include ongoing product support and all minor software upgrades, maintenance releases, patches, and bug fixes at no additional cost for the life of that major version.

Section 5.1 – Scope of Maintenance and Support

Support services must include, but are not limited to:

• Administrative License Support: Rapid assistance and resolution for any license key issues, including resetting lost keys, reactivating keys after hardware failures, or transferring licenses between workstations at no additional cost.

• Technical Assistance: Access to technical help-desk support for troubleshooting installation or operational issues.

• Software Patches: Continuous delivery of security patches, vulnerability resolutions, and performance bug fixes.

Section 5.2 – Major Version Upgrades

Major version updates (e.g. transitioning from Version 1.x to Version 2.0) are not included in the base purchase price. However, vendors must describe their upgrade pricing model in their response and provide estimated pricing or a predetermined pricing structure for major version upgrades so the Government can accurately assess the total lifecycle cost of the software.

Section 6.0 – Cyber Security/Air Force Network

The software must be approved for use on the Air Force Network (AFNET) and must have or be capable of maintaining an Authority to Operate (ATO).

The vendor must provide all necessary documentation to support the Risk Management Framework (RMF) assessment and authorization process. This includes, but is not limited to:

• A complete Software Bill of Materials (SBOM) to identify open-source and third-party dependencies.

• Results of recent static and dynamic application security testing (SAST/DAST) or automated vulnerability scans.

• Documentation demonstrating compliance with applicable DISA Application Security STIGs.

Section 7.0 Inspection and Acceptance

The Government will perform inspection and acceptance testing within thirty (30) days of successful electronic delivery of the software binaries and license keys.

Acceptance will be formally granted once the Government verifies that:

• The software is fully functional and successfully installs on the Air Force Standard Desktop Configuration (SDC) and Army Gold Disc (AGD) environments.

• The software executes successfully under a standard user account without requiring administrative privileges.

• The software meets all mandatory technical specifications and performance metrics outlined in Section 2.0.

• All 670 license keys (80 full, 590 upgrade) have been delivered, verified, and are fully operational.