Atch 1 - FA8634-26-R-B011 DEWS MDF Autotest SOW.pdf

FA8634-26-R-B011

Attachment 1

04/08/2026

Digital Electronic Warfare System (DEWS) Mission Data

File (MDF) Autotest Statement of Work (SOW)

08 April 2026

Digital Electronic Warfare System (DEWS) Mission Data File (MDF) Autotest Statement of Work (SOW)

1.0 BACKGROUND

Foreign Military Sales (FMS) F-15 fleets equipped with DEWS require periodic, timely updates to the system’s MDF in order to address emerging operational requirements. Current software used by the 68th Electronic Warfare Squadron (68 EWS) for the development and testing of these MDFs involves repetitive, time-consuming manual processes that degrade the ability to adequately respond to customer requirements on operationally relevant timelines.

2.0 SCOPE

The Contractor shall develop, deliver, integrate and test Autotest software into the DEWS test facility at the 68 EWS, Eglin Air Force Base, Florida in order to simplify and expedite the development, verification/validation and delivery of MDFs for Government-designated F-15 FMS programs.

3.0 PERIOD OF PERFORMANCE

• Base Period: 15 May 2026 – 30 April 2027

• Option 1: 01 May 2027 – 30 April 2028

• Option 2: 01 May 2028 – 30 April 2029

4.0 REQUIREMENTS

4.1 Government Test Facility Evaluation

The Contractor shall evaluate the DEWS test facility at the 68 EWS to determine if existing Government hardware can accommodate use of Autotest software. If hardware is determined to be insufficient to integrate Autotest software, the Contractor shall provide a detailed recommendation for required hardware updates.

4.2 Software Development

The Contractor shall develop Autotest software to meet the following requirements:

• Control the Advanced Architecture Phase Amplitude and Time Simulator (A2PATS) via external control messages

• Ingest output messages from the DEWS System Under Test (SUT)

• Use existing and government-requested adjudication logic to determine pass/fail of each simulated threat beam

• Produce output reports in accordance with government specified content and format

• Include a graphical user interface (GUI) to enable test system control, status monitoring, and reporting of the test results

(CDRL B004, DI-IPSC-81427B/T, Software Development Plan) (CDRL B007, DI-IPSC-81435B/T, Software Design Description)

(CDRL B010, DI-IPSC-81442A/T, Software Version Description) (CDRL B011, DI-IPSC-81443A/T, Software User Manual)

4.3 Software Delivery, Integration and Test

The Contractor shall deploy the Autotest software into the government directed lab. The Contractor shall test the software in the deployed lab environment against the following requirements:

• Process messages as fast or faster than the DEWS message output rate

• Record the lineage of DEWS messages during a test and make them available for inspection

• Successfully complete Government Acceptance Testing for accuracy equal to or greater than that achieved with existing manual test procedures

• Successfully complete Government Acceptance Testing for speed that represents a significant improvement when compared to the duration of existing manual test procedures

• Successfully complete Government Acceptance Testing for stability with run times of not less than eight (8) hours (Threshold) / 12 hours (Objective) without the need for manual intervention

(CDRL A012, DI-NDTI-80603A/T, Acceptance Test Procedure) (CDRL B008, DI-IPSC-81438A/T, Software Test Plan) (CDRL B012, DI-AVCS-80700A/T, Computer Software Product End Items) (CDRL B014, DI-IPSC-81439A/T, Software Test Description) (CDRL B016, DI-IPSC-81440A/T, Software Test Report)

4.4 Program Management

Program management includes financial management, contracting and security. The Contractor shall manage the program to ensure contract compliance, ensure active participation in virtual and in-person meetings, manage the on-time delivery of deliverables and support technical development activities.

Formal progress meetings shall be held approximately quarterly during the period from contract award through final software delivery/Government acceptance.

(CDRL A002, DI-ADMN-81250C/T, Conference Minutes) (CDRL A053, DI-ADMN-81373/T, Presentation Materials) (CDRL A056, DI-ADMN-81249C, Conference Agenda)

4.5 Travel

The Contractor shall travel to Eglin AFB, Florida as required to establish requirements, review the architecture and software design, integrate, test and evaluate performance of the system. The Contractor shall also travel to Eglin AFB, FL to conduct quarterly performance reviews; when possible these should be combined with other events.

5.0 CONTRACT DATA REQUIREMENTS LIST

The Contractor shall deliver the following as part of contract scope:

DATA ITEM DOCUMENT NUMBER DATA ITEM TITLE

A002 DI-ADMN-81250C/T Conference Minutes A012 DI-NDTI-80603A/T Acceptance Test Procedure A053 DI-ADMN-81373/T Presentation Materials

A056 DI-ADMN-81249C Conference Agenda B004 DI-IPSC-81427B/T Software Development Plan B007 DI-IPSC-81435B/T Software Design Description B008 DI-IPSC-81438A/T Software Test Plan B010 DI-IPSC-81442A/T Software Version Description B011 DI-IPSC-81443A/T Software User Manual B012 DI-AVCS-80700A/T Computer Software Product End Items B014 DI-IPSC-81439A/T Software Test Description B016 DI-IPSC-81440A/T Software Test Report

6.0 GOVERNMENT-FURNISHED/PROVIDED PROPERTY, EQUIPMENT, MATERIAL,

INFORMATION, OR SERVICE

The Government shall provide, without cost, hardware for integration of Autotest software. The Contractor will provide equipment, materials, and Services. The Contractor shall maintain sufficient equipment, parts and materials required to perform maintenance on the system.

7.0 GENERAL INFORMATION

7.1 Accident / Incident Reporting and Investigation

The Contractor shall record and report to the Contracting Officer (CO) all available facts relating to each instance of accidental government property damage or contractor personnel injury. The Contractor shall secure the scene of an accident and wreckage until released by the accident investigative authority through the CO. If the Government elects to investigate the incident, the Contractor shall cooperate fully with the

CO.

7.2 Subcontractor Compliance

The Contractor shall be responsible for ensuring Subcontractors satisfy the requirements outlined in the contract.

7.3 Duty Hours

The Contractor shall coordinate with the 68 EWS for access to Government facilities as needed.

7.4 Access to Base LAN

The Contractor shall be required to obtain a Common Access Card for each individual requiring access to the Base LAN System. All Contractors requiring access to the Air Force Network shall comply with associated training per all applicable guidance.

7.5 Key Personnel

Contractor-designated vital personnel shall be kept to a minimum. The Government intends to refrain from dictating the composition of the ideal team to perform services. The Government desires that “key personnel” be assigned for the duration of the contract.

Before starting the contract performance period, all contracted personnel must obtain a Common Access Card. All contractor personnel require a minimum of a NACI/SF85 for any position having access to the internet, automated systems, or unescorted entry into restricted or controlled areas before performing any maintenance actions.

The investigation is not for a security clearance but for a position of trust. This requirement is outlined in DoD 5200.1-R and AFI 31-501 Information Security. All documentation required for security certification shall be the responsibility of the Contractor. The facility commander or contracting officer can approve the hiring of foreign nationals.

The Contractor shall provide a list of key personnel with current contact information. The Contractor shall provide the key personnel list to the CO before the commencement of any work. The essential personnel list shall include names, duty titles, work/cell phone numbers, and whether they support O&M or Special Projects. The Site Lead will notify the CO when off-site and provide the name and telephone number of the person performing Site Lead duties during the absence.

7.6 Contract Holidays

Federal offices are closed on federal holidays, except during contingency operations. The Contractor shall not provide services on the following designated federal holidays and any additional federal holidays declared during the performance of the contract:

New Year's Day 01 January Martin Luther King, Jr. Day Third Monday of January President's Day Third Monday of February Memorial Day Last Monday in May Juneteenth June 19th Independence Day 04 July Labor Day First Monday in Sept Columbus Day Second Monday in October Veteran's Day 11 November Thanksgiving Day Fourth Thursday in November Christmas Day 25 December

Note: Any of the above holidays falling on a Saturday will be observed on the preceding Friday; holidays falling on a Sunday will be observed on the following Monday. All holiday observation time-off will be determined by specific location and operational needs.

7.7 Essential / Nonessential Personnel

The performance of these services is not mission essential during time of crisis. Should a crisis be declared, the CO or his/her representative will verbally advise the Contractor of the revised requirements, followed by written direction.

7.8 Physical Security

The contractor shall safeguard all Government property, documents, and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract.

7.9 Pass and Identification Items

The Contractor shall ensure all contracted personnel obtain necessary identification cards and all non-government vehicles have proper vehicle passes required for contract performance.

7.10 Retrieving Identification Media

The Contractor shall retrieve all identification media, including vehicle passes, from employees who depart for any reason before the contract expires.

7.11 Contractor Identification

All Contractor personnel shall wear the Air Force-issued Common Access Card when away from their immediate work area to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone, or via electronic mail, Contractor personnel shall identify themselves as contractors to avoid situations where sensitive topics might be better discussed solely between Government employees. Contractors shall identify themselves on any attendance sheet or coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, Contractors occupying collocated space with their government program customer should identify their workspace area with their name and company affiliation or, as a minimum, “Contractor” after the name.