ALR-69A Engineering Services DRAFT PWS.pdf

CONTROLLED UNCLASSIFIED INFORMATION

PR: FD2060-26-30369 PWS REVISION: 0 1

Performance Work Statement for

AN/ALR-69A Radar Warning Receiver (RWR) Engineering Services

Indefinite Delivery Indefinite Quantity (IDIQ)

Purchase Request: FD2060-26-30369

Date QAPC signs QASP.

Approved by: ____________________________ Anand Dave, CIV, USAF AN/ALR-69A Subject Matter Expert (SME) Electronic Warfare Division

AFLCMC/ESY

DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense (DoD) and US DoD Contractors only. (CRITICAL TECHNICAL INFORMATION) (21 November 2025). Other requests for this document must be referred to AFLCMC/ESY.

PR: FD2060-26-30369 PWS REVISION: 0 2

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to complement the AN/ALR-69A Radar Warning Receiver (RWR) organic engineering capability.

These services include Operational Flight Program (OFP) and Mission Data (MD) support, software re-host and maintenance, future block cycle (BC) planning, lab maintenance, software and test tool updates, documentation updates, analysis of alternatives (AOA) and roadmaps, system familiarization, hardware conditioning and failure analysis. Optional tasks encompass engineering studies and hardware redesigns.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by enabling aircrews and MD programmers to sustain and enhance the AN/ALR-69A, providing them with the flexibility to identify and process modern threats to meet mission requirements. Improvements and modifications will enhance situational awareness, reliability, maintainability, emitter ranging, azimuth angle accuracy, and threat ambiguity resolution. Furthermore, refined threat location data, enabled by platform integration, will allow aircrews to react in real-time to previously unknown threats, providing accurate information for engagement or route adjustment.

1.3 Background:

The AN/ALR-69A RWR emerged from a pressing need to improve the survivability of United States Air Force (USAF) aircraft in increasingly sophisticated threat environments. The ALR- 69A addresses limitations identified in earlier RWR systems like the AN/ALR-69 and AN/ALR-

46. The Cold War saw rapid advancements in Soviet air defense technologies, particularly surface-to-air missiles (SAMs) and interceptor aircraft equipped with powerful radar systems.

These new threats necessitated a more capable RWR that could provide earlier and more accurate warnings of radar-guided threats, enabling pilots to take timely defensive actions like employing electronic countermeasures (ECM), maneuvering defensively, or using chaff and flares. The AN/ALR-69A was designed with improved signal processing capabilities, greater frequency coverage, and a more sophisticated threat library to accurately identify and prioritize a wider range of radar emitters.

The integration of the AN/ALR-69A marked a significant leap forward in electronic warfare (EW) capabilities for the USAF. It was specifically designed to be retrofitted into a variety of aircraft, including the F-16 Fighting Falcon, A-10 Thunderbolt II, and C-130 Hercules, providing a standardized RWR system across different platforms. This commonality reduced logistical burden and simplified training. The ALR-69A incorporated features like improved emitter geolocation, allowing pilots to pinpoint the location of threats more accurately, and enhanced false alarm rejection, which helped reduce pilot workload by minimizing distractions from spurious signals. Its successful deployment and integration into the USAF inventory solidified its role as a crucial component of aircraft self-protection, providing a vital edge in the evolving landscape of air combat.

2.0 Services Summary

PR: FD2060-26-30369 PWS REVISION: 0 3

Performance Objective PWS Paragraph Performance Threshold Supply engineering services and materials with minimum re-work

4.0, 4.0.1, 4.0.1.1, 4.0.1.2, 4.0.1.3, 4.0.1.4, 4.0.1.5, 4.0.1.6, 4.0.1.7, 4.0.1.8, 4.0.1.9, 4.0.1.9.1, 4.0.1.9.2, 4.0.1.10, 4.0.1.11, 4.0.2, 4.0.3, 4.0.3.1, 4.0.3.2, 4.0.3.3, 4.0.3.4, 4.0.3.4.1, 4.0.3.4.2, 4.0.3.4.3, 4.0.3.4.4, 4.0.3.4.5, 4.0.4

No individual Engineering Task [as defined in the monthly status reports via Work Breakdown Structure (WBS)] or deliverable shall require re-work more than once. Re-work shall be defined as the work performed to correct defects/failures.

Timely Notification of Problems that Impact Cost/Delivery/Schedule

4.0, 4.0.1, 4.0.1.1 The contractor shall provide appropriate level of support to accommodate Government requirement according to request:

Emergency – 12 clock hours (in order to meet 24-hour requirement), Urgent – 48 clock hours (in order to meet 72-hour requirement), Routine – 7 calendar days.

Contractor Manpower Reporting

6.7 Within 30 calendar days of

contract/order award, the contractor shall establish a record for the contract/order in the System for Award Management (SAM) including Order Data, Contact Data and Location Data.

Adherence to Contractor QMS 6.9 100% compliance with the QMS is required.

Receipt of CDRL 5.2.2 There shall be no more than one late submission(s) of deliverables per quarter.

The contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised

PR: FD2060-26-30369 PWS REVISION: 0 4

delivery date acceptable to the Government.

Contractor Personnel Qualifications

Entire Contractor/Subcontractor personnel shall meet, at a minimum, the qualifications identified in the PWS.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be Provided: Government property to be provided is included in Appendix C.

3.3 Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.5 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/

PR: FD2060-26-30369 PWS REVISION: 0 5

Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

In response to real world events, as well as exercise activities, AFLCMC requires expert level contractor support to resolve complex issues within a short period of time. Expert level is defined as the ability to meet the requirements of DAFMAN 10-703 response times. The EW Integrated Reprogramming (EWIR) Process, as defined in DAFMAN 10-703, paragraph 1.3, is made up of four different steps. These steps are: 1) detect change; 2) determine impact; 3) reprogram; and 4) field change. This process is referred to by the unclassified code name PACER WARE. PACER WARE includes MD changes, OFP changes, or minor hardware changes that comply with the guidance in DAFMAN 63- 131, Modification Management, concerning modifications. These changes are categorized into three (3) priority levels: ROUTINE, URGENT and EMERGENCY.

Routine OFP changes are made as part of OFP update cycles. Urgent changes should reach the field within 72 hours, after a required change has been validated, or as negotiated between AFLCMC, EW Division, and the application Major Command (MAJCOM). Emergency changes affecting combat operations require 24-hour operations, with the goal of releasing necessary changes within 24 hours, after the required changes have been validated, depending on the complexity of the change. The contractor shall have the depth and breadth of knowledge required to meet EMERGENCY requirements immediately upon contract award.

4.0.1 TASK 1: Engineering Support

Under this task, the contractor shall provide systems engineering services for the AN/ALR-69A RWRs. System engineering services shall include deficiency/issue investigation, problem analysis, analysis of alternatives, and documentation of findings and proposed solutions in technical reports/memoranda. Specific deficiencies to be addressed include emitter detection/display/identification deficiencies, EW system interoperability, software problem report investigation, reprogramming issues, hardware/component issues, testability concerns, emitter investigations, Intelligence driven Area of Responsibility (AOR) investigations, Electromagnetic Interference (EMI)/Radio Frequency Interference (RFI), and Software Change Request (SCR) investigations. The contractor shall respond (by providing manpower and resources as necessary) to informal email requests/phone calls from the USAF technical representative within a specific period. Based on the level of request, the response times shall be Emergency – 12 clock hours; Urgent – 48 clock hours; & Routine – 7 calendar days.

Response times are required to meet the requirements of DAFMAN 10-703. The Contractor shall provide technical reports/memoranda as required to address technical issues requiring Government action and decision. (DI-MISC-80711A, Scientific and Technical Reports)

This task includes the support described in paragraphs 4.0.1.1 through 4.0.1.11.

4.0.1.1 OFP Support

PR: FD2060-26-30369 PWS REVISION: 0 6

The contractor shall provide software engineering services for PACER WARE OFP updates. The contractor shall respond (by providing manpower and resources as requested) to informal email requests/phone calls from the Government representative within a specific period. Based on the level of request, the response times shall be Emergency – 12 clock hours; Urgent – 48 clock hours; & Routine – 7 calendar days. Response times are required to meet the requirements of DAFMAN 10-703. Software support shall be provided for the multiple block cycles on a case-by-case basis and include all facets of the software development process from initiation to flight test support. Algorithms and System Change Requests (SCRs) shall be developed, documented, and coordinated with the Government for integration into the existing software baseline. The Contractor shall support Developmental and Operational Test, to include ground and flight test data reduction. In support of the software sustainment activity, the Contractor shall provide system-engineering services to resolve system deficiencies through studies and laboratory testing of the AN/ALR-69A systems. Results of AN/ALR-69A system engineering support shall be documented in technical reports/memoranda as required. If driven by an OFP update, the contractor shall also perform updates or develop support tools/equipment as requested by the Government. (DI-MISC-80711A, Scientific and Technical Reports)

4.0.1.2 MD Support

If requested by the Government, provide a combat mission-capable ALR-69A mission data that addresses real world threats and meets the country’s threat-specific emitters including analysis, design, development, and test based on the country’s baselined OFP within 6-12 months, depending on the urgency assigned by the country. This mission data will address anomalies that have been witnessed in lab, chamber and flight test events performed recently. The contractor shall conduct research to help the Government determine the optimal engineering approach to implementing the improved mission data. Provide engineering subject matter expertise for mission data development addressing anomalies and associated testing. Mission data development support includes Mission Data generation, design, and threat database programming. (DI-MISC-80711A, Scientific and Technical Reports)

4.0.1.3 Software Re-host Maintenance

The contractor shall ensure the future sustainability and longevity of the AN/ALR-69A RWR systems using modern processing and computing capabilities. The contractor shall, as directed by the Government:

a) Modify software, firmware, board support packages

b) Port software and signal processing capability for compatibility with newer processing/computing hardware, operating Systems, development environments

c) Support updates to conform with Open Architecture standards

d) Support digital engineering to develop and sustain modeling and simulation of AN/ALR

69A in a virtual environment

e) Support cybersecurity and integrity enhancements (DI-MISC-80711A, Scientific and Technical Reports)

4.0.1.4 Future Block-Cycle (BC) Planning

The contractor shall assist the Government with future block cycle planning for AN/ALR-69A OFP block cycles. (A002: DI-IPSC-81427B, Software Development Plan)

PR: FD2060-26-30369 PWS REVISION: 0 7

The Contractor shall:

a) Document and track SCRs, Operational Change Requests (OCRs) and Software Problems

Reports (SPRs)

b) Perform and document analyses to determine the feasibility and methodology of implementing the software changes

c) Perform analyses of alternatives to software changes

d) Assess and document the system and software impacts of each software change

e) Assess and document the operational impact for each software change (e.g. training, maintenance, and technical orders)

f) Develop budgetary estimates (to include current-year dollars & hours) for implementing each software change

g) Draft and provide a software development plan that contains work breakdown structures

4.0.1.5 Lab Maintenance

The contractor shall provide maintenance support for the Electronic Warfare Avionics Integrated Support Facility (EWAISF) to ensure organic capability to sustain the AN/ALR-69A OFPs, software tool (STs), test tools (TTs) and ALR-69A line replaceable units (LRUs).

In addition to maintenance support of the EWAISF lab, the contractor shall maintain the contractor’s own lab to ensure contractor capability to sustain the AN/ALR-69A OFPs, software tools, and test tools in parallel to organic sustainment. As directed by the Government, the contractor shall update the contractors OFP development stations, support tools stations, and test stations. As necessary, the contractor shall plan to design, implement, deliver, and test updates to the OFP development stations, support tools stations, and test stations. As necessary, the contractor shall update all available documentation for the stations mentioned in this paragraph.

4.0.1.6 ST/TT Development/Updates

The contractor shall develop, update or provide support for STs and TTs compatibility with AN/ALR-69A as required. Specific ST and TTs shall include, but are not limited to, EW Hotbenches, OFP Development and debug tools, Mission Data support tools, Versatile Depot Automated Test Station (VDATS), Automated LRU Testers, CAPRE, VIPER, Memory Loader Verifier (MLV), Joint Service Electronic Combat Test System (JSECTS), on-aircraft reprogramming tools and data recorders. The contractor shall plan for the development and/or update of tools as necessary to facilitate laboratory, ground and flight tests required to demonstrate that the corrected OFP and system updates meet operational and developmental requirements. The contractor shall provide customer support for STs and TTs, as well as assist organic personnel in troubleshooting any ST/TT issues. The Contractor shall investigate, define, & develop corrections for all SCRs prepared against any ST/TT, implement & test corrections, and deliver software.

4.0.1.7 Documentation Updates

The contractor shall, as directed by the Government, migrate current documentation and drawings to currently supported versions of Microsoft Office or applicable software, scrub available documentation for deficiencies and errors, and update the documentation accordingly.

Documentation includes software documentation, Technical Orders (TOs), handbooks, and engineering drawings.

PR: FD2060-26-30369 PWS REVISION: 0 8

4.0.1.8 Analysis of Alternatives (AOA)

As required, the contractor shall generate or update roadmaps and hardware and software roadmaps for the AN/ALR-69A RWRs. The AOA must consider existing obsolescence and future hardware/software upgrade paths for the AN/ALR-69A installation and weigh pros and cons in the areas of performance, cost, risk and sustainability. Perform the engineering research required for this task and capture results. (DI-MISC-80711A, Scientific and Technical Reports)

4.0.1.9 System Familiarization

The contractor shall develop and conduct a system familiarization program in the areas listed below as required. The Government will prioritize the specific OFP modules, ST, and TT.

Minimum requirements are outlined below for each. (DI-ADMN-81249C, Conference Agenda;

DI-ADMN-81250C, Conference Minutes; DI-ADMN-81373, Presentation Material)

4.0.1.9.1 Flight Test Data Collecting and Analyzing Support

a) Functions of new software, firmware or hardware changes

b) Setup, Configuration for test, and use of the above

4.0.1.9.2 OFP Software Modules and Mission Data Schedule Optimization

a) Functionality and interface requirements of modules within the AN/ALR-69A OFPs

b) MD impacts to optimize performance for the above modules

c) Testing, validation, and verification requirements for OFP modules

d) Functionality and data drivers within the mission data file generator (MDFG) that effect changes to optimize the calculated system’s receiver schedule

e) Programming aspects of pulse, Continuous Wave (CW), amplitude, missile guidance for optimum performance

f) Understanding of the MDFG reports that show receiver schedule timing and execution

4.0.1.10 Hardware Conditioning

The Contractor shall, as requested by the Government, induct AN/ALR-69A system hardware items to reload and condition items to requested configurations of firmware or software. Items will be delivered after passing production line acceptance testing. Items will be marked and preserved through shipping per paragraph 5.3.1 herein. Contractor shall request disposition instructions for each item. (DI-MISC-80711A, Scientific and Technical Reports; DI-MGMT- 80368A, Status Report)

4.0.1.11 Failure Analysis

The Contractor shall, as requested by the Government, induct AN/ALR-69A system hardware items to determine the root cause of failure and effect repair of the item. Contractor shall collect artifacts and deliver Failure Analysis Report that determines failure, determination of applicable warranty, and cost of repair. Items determined by the Government for repair will be delivered after passing production line acceptance testing. Items will be marked and preserved through shipping per paragraph 5.3.1 herein. Contractor shall request disposition instructions for each item. (DI-MISC-80711A, Scientific and Technical Reports; DI-MGMT-80368A, Status Report)

4.0.2 Option Task 2: Engineering Studies

PR: FD2060-26-30369 PWS REVISION: 0 9

The current threat spectrum is evolving, operational tempo is increasing, technology is rapidly changing, and obsolescence is increasing. As a result, the AN/ALR-69A RWRs and its protected platforms are challenged to remain mission capable. It is essential to periodically study the threat environment, technology, system effectiveness and architecture, platform installations, EMI/Electromagnetic Compatibility (EMC), integration with on-board/off-board systems, supportability, integration, tactics, apertures, system integrity, and reliability and maintainability.

The contractor shall conduct a study, as requested by the Government, relevant to the AN/ALR- 69A RWRs. The contractor shall hold a meeting to define requirements, scope of the study, and specific deliverables within three months of the Orientation Review (see section 3.6).

Government approval of meeting minutes for the requirements review constitutes approval to initiate the effort. The study may require design, development, and test of prototype hardware and software. Software and Hardware documentation shall include technical order (TO) redlines, Engineering Change Proposals (ECP), updated specifications, and drawings. The delivery of each study shall include a technical report. (DI-MISC-80711A, Scientific and Technical Reports;

DI-MGMT-81772, Lead Free Control Plan; DI-SESS-80639E, Engineering Change Proposal;

DI-FACR-82242, Hardware Design Description (HDD); DI-SESS-80643E, Specification Change Notice (SCN); DI-SESS-81002F, Developmental Design Drawings/Models and Associated Lists)

4.0.3 Option Task 3: Hardware Redesigns

LRU/Shop Replaceable Unit (SRU) obsolescence, safety concerns, platform installation concerns, improved capability, and sustainability often require system redesigns. Upon request from the Government, the contractor shall design, develop, prototype, test, and document a hardware update to the AN/ALR-69A. All hardware redesigns shall follow a phased approach.

The contractor may only proceed to the subsequent phase after Government approval. Phases are described as follows:

4.0.3.1 Phase I: Requirements Definition

In Phase I, the contractor shall analyze requirements, all available documentation, hardware, and characterize key performance parameters and develop a performance specification for the upgraded hardware. The contractor shall submit a technical report detailing all findings, options for hardware modifications to include risks, implementation and supportability costs of each option and a recommended implementation approach. The implementation costs shall, as a minimum, include Non-Recurring Engineering (NRE) costs, projected production costs, schedule and risk. The report shall identify all testing necessary to ensure that the hardware upgrade meets AN/ALR-69A system performance requirements. In all cases, the contractor shall meet or exceed performance of the baseline system. The contractor shall conduct the Preliminary Design Review (PDR) at the end of Phase I. (DI-SDMP-81465A, Performance Specifications Document; DI- MISC-80711A, Scientific and Technical Reports)

4.0.3.2 Phase II: Proof of Concept

Phase II will commence after Government review and approval of the Phase I technical report and PDR minutes. Based upon data presented in the report, the Government will provide direction to the contractor concerning the upgrade approach to be taken. The contractor shall develop a breadboard/prototype of each of the hardware upgrades. These breadboard/prototypes shall be designed and developed to demonstrate and prove that the functionality and interface of

PR: FD2060-26-30369 PWS REVISION: 0 10

the new design satisfies the required specifications. This phase shall conclude when the contractor successfully demonstrates, and the Government concurs, that the proof of concept was successful.

4.0.3.3 Phase III: Design and Packaging

In Phase III, the contractor shall provide the engineering services to perform the detailed design and modify/repackage the concept design into the required form factors. The contractor shall conduct a Change Design Review (CDR) at the end of Phase III. Following Government approval of the CDR minutes, the contractor can complete the detailed design and fabricate prototypes. A Technical Data Package (TDP) sufficient to procure the items under full and open competition shall be produced concurrently with the prototype fabrication. (DI-MISC- 80711A, Scientific and Technical Reports; DI-SESS-80639E, ECP; DI-FACR-82242, Hardware Design Description (HDD), DI-SESS-80643E, Specification Change Notice (SCN); DI-SESS-81002F, Developmental Design Drawings/Models and Associated Lists)

4.0.3.4 Phase IV: Testing

The contractor shall conduct sufficient testing on the LRU to ensure that no degradation in the overall performance of the associated LRU exists. Prior to qualification and EMI testing, the contractor shall conduct Acceptance Test (AT) and limited integration testing. The Government reserves the right to witness all testing.

4.0.3.4.1 Acceptance Testing

The contractor shall perform acceptance testing IAW a contractor generated, Government approved Acceptance Test Plan (ATP). The contractor shall prepare and deliver a test report detailing all test results. (DI-NDTI-80566A, Test Plan; DI-NDTI-80603A, Test Procedure; DI- MISC-80711A, Scientific and Technical Reports)

4.0.3.4.2 Qualification Testing

The contractor shall perform qualification testing on prototype IAW a contractor generated, Government approved Qualification Test Procedure (QTP). The contractor shall reference and analyze Environmental Engineering Considerations and Laboratory Tests (MIL-STD-810) performance specifications, and the Northrop Grumman Corporation A-10A Environmental Test Requirements Document (SA220R0307) while developing the QTP. When developing the test plan, as a minimum, vibration testing shall include the gunfire vibration test parameters identified in SA220R0307. The contractor shall ensure that the prototypes meet or exceed all A- 10 Environmental Test requirements defined in SA220R0307, Lockheed C-130J and C-5M environmental criteria, and Boeing C-17 and KC-46 environmental criteria while updating the system qualification procedures. The contractor shall prepare and deliver a test report detailing all test results. (DI-NDTI-80603A, Test Procedure; DI-MISC-80711A, Scientific and Technical Reports)

4.0.3.4.3 Electromagnetic Interference (EMI) Testing

The contractor shall perform EMI testing on prototype hardware IAW a contractor generated, Government approved EMI Test Plan. In developing the EMI Test Plan, the contractor shall utilize available documentation and EMI Characteristics Requirements for Equipment (MIL- STD-461G). The prototypes shall meet or exceed legacy LRU performance. The contractor shall

PR: FD2060-26-30369 PWS REVISION: 0 11

prepare and deliver a test report detailing all test results. (DI-NDTI-80603A, Test Procedure; DI- MISC-80711A, Scientific and Technical Reports)

4.0.3.4.4 Integration Testing

The contractor shall support Integration Testing of the upgraded hardware at the EWAISF and aircraft System Integrated Labs (SILs). It is the contractor’s responsibility to ensure that all tested prototypes are fully functional. As a minimum, Government Integration Testing will include:

a) Support Equipment testing

b) Threat Testing (Integrated Support Station (ISS/Independent Validation and Verification

(IVV) test)

c) Flight line Level Testers

d) If available and necessary, ground and flight testing

If deemed necessary, the Government may perform additional testing.

4.0.3.4.5 Functional Configuration Audit (FCA) / Physical Configuration Audit (PCA) The Government, with support from the contractor, will conduct an FCA/PCA at the contractor’s facility. (DI-SESS-81022E, Configuration Audit Summary Report)

4.0.4 Option Task 4: Material and Subject Matter Expertise Support The Government strives for a rapid prototyping and response capability within EW labs. In support of this capability, it is necessary to obtain material, domain specific expertise, and access to test support in a timely and cost-effective manner. The contractor shall provide support to Government technical personnel to develop and sustain a rapid prototype and engineering response capability for EW labs. In response to requirements provided by the USAF technical lead, perform market research and provide a materiel solution, equipment, familiarization, and/or support by access to appropriate domain specific subject matter expertise. (DI-MISC-80711A, Scientific and Technical Reports)

4.1 General Software Requirements

4.1.1 Software Engineering Process

The contractor shall perform the software engineering and support work required by each individual task IAW with a documented software engineering process. The contractor’s software engineering process and practices shall conform to requirements of an internationally recognized process model such as IEEE/EIA 12207 (ISO/IEC 12207) or the Software Engineering Institute’s Capability Maturity Model Integration (CMMI) level 3, an equivalent or higher. Upon request, the Contractor shall provide the USAF with access to the software process documentation, as well as the results of all current software process assessments. Coding shall be IAW documents A8116-032 and A5079-023 as applicable.

4.1.2 Software Configuration Management

The contractor shall implement a software configuration management program that conforms to EIA-649C, Standard for Configuration Management. The contractor shall conform to the most

PR: FD2060-26-30369 PWS REVISION: 0 12

current organic Government support and configurations tools to reflect the configurations management of the Government. Specific project implementation plans shall be documented in the software development plan.

Data (i.e., software and documentation) configuration shall be maintained under automated configuration management control. The configuration of all software shall be traced using SCRs and version control of all source code files. Automated computer-based tools shall be used to facilitate software configuration management.

4.1.3 Software Quality Assurance

The contractor shall implement a software quality assurance program IAW the contractor’s software engineering process. The software quality assurance program shall be tailored for small software projects and for software tools to ensure the proper level of effort is expended relative to the size and significance of the project.

4.1.4 Development Environment

The software development environment shall consist of programs compatible with the Windows version in use by EWAISF. The use of any other program or Personal Computer (PC) configuration and any changes to the PC configuration throughout the software engineering process shall require prior approval by the Government.

4.1.5 Software Development Plan

The contractor shall conduct software project planning for each software engineering task required by this contract.

e) The contractor shall prepare and deliver a software development plan for review and approval by the USAF. The software development plan shall be updated as changes occur during the software engineering effort. (DI-IPSC-81427B, Software Development Plan)

f) The contractor shall develop a work-based structure (WBS) that is based on PWS tasks and data deliverables.

g) The contractor shall devise and implement an earned value tracking system (EVMS) for measuring the contractor’s progress toward completing work package requirements. The tracking system shall report earned value on the identified work packages.

4.1.6 Software Requirements Review (SRR)

The Contractor shall conduct a SRR to collect and refine requirements for the software project.

At the SRR the Contractor shall present the following:

a) Results and status of any previous work performed on the software project

b) Contractor's understanding of the software baseline requirements

c) Contractor's understanding of the change requirements including all known SCRs, OCRs, and Software Problem Reports (SPRs)

d) Preliminary estimates of the effort, cost and time required to implement each change to the baseline requirements

e) Estimates of probability and severity of any risks involved with the software changes

f) Estimates of interdependences and constraints imposed on the software changes

PR: FD2060-26-30369 PWS REVISION: 0 13

g) Estimates of technical data, equipment, supplies and travel needed to implement the software changes

h) Opportunity for attendees to submit and discuss additional change requests

i) Proposed priority ranking of change requests

j) Software quality assurance provisions and tailoring for the project

k) Action items and preliminary minutes

4.1.7 Software Requirements Analysis

The contractor shall perform software requirements analysis, documentation, and tracking for the software support engineering required by this task. The contractor shall collect, decompose, and analyze operational, technical and sustainment requirements; shall allocate requirements to the existing configuration items; shall document requirements in software and interface requirements specifications; and shall prepare software change requests that detail the changes to be made to the baseline requirements. The contractor shall obtain USAF approval of the requirements specifications and software development plan prior to initiating detailed design and development of the software changes. The contractor shall track software requirements, interface requirements, and change requests throughout the software engineering task and update the documentation as changes occur. The contractor shall maintain AS-9100 level, or equivalent, certification to accomplish software tasks. (DI-IPSC-81433A, Software Requirements Specification)

4.1.8 Software Documentation

For all software projects, the Contractor shall create or update the following documentation:

a) Scientific and Technical Reports (DI-MISC-80711A)

b) Software Design Description (SDD) (DI-IPSC-81435B)

c) Software Requirements Specification (SRS) (DI-IPSC-81433A)

d) Interface Requirements Specification (IRS) (DI-IPSC-81434A)

e) Interface Design Description (IDD) (DI-IPSC-81436A)

f) Software Test Description (STD) (DI-IPSC-81439A)

g) Software Test Report (STR) (DI-IPSC-81440A)

h) Software Version Description (SVD) (DI-IPSC-81442A)

i) Software User Manual (SUM) (DI-IPSC-81443A)

j) Software Product Specification (SPS) (DI-IPSC-81441A)

k) Software Development Plan (SDP) (DI-IPSC-81427B)

l) Software Test Plan (DI-IPSC-81438A)

m) Database Design Description (DBDD) (DI-IPSC-81437A)

For software projects requiring Information Assurance (IA), the contractor shall generate the following:

a) Information Assurance Test (IA) Report (DI-MGMT-81843)

b) IA Test Plan (DI-MGMT-81844)

c) IA Design Review Information Package (DRIP) (DI-MGMT-81845)

4.1.9 Software Deliverable Format

The contractor shall deliver all source programs, computer software product end items for software projects, the development environment, and all supporting utility software. Both source

PR: FD2060-26-30369 PWS REVISION: 0 14

code and executable shall be delivered and made available for software test. Source code shall be written IAW established and approved project coding standards. The contractor shall build the executable program on a CD ROM with install capability and/or other approved secure, removable media device as approved by the government Information System Security Manager (ISSM). Source code and documentation shall be provided on a CD ROM and/or other approved secure, removable media devices. A SVD shall be submitted for Government review and approval. (DI-AVCS-80700A, Computer Software Product End Items (Source Code); DI-AVCS- 80700A, Computer Software Product End Items (Executable); DI-IPSC-81442A, SVD)

4.2 General Program Requirements

4.2.1 Program Management

The contractor shall assign a program manager (PM) to manage the work required. The 0PM shall have overall authority and responsibility for performing all required work, which includes ensuring that all contractual deliveries, as well as technical requirements, are complying. The PM shall be the chief point of contact to the Government regarding program and technical issues of this task; therefore, the contractor shall identify the assigned PM and associated contact information to the Government Procurement Contract Officer (PCO), PM, and Technical Representative. The Contractor shall implement a financial tracking system to track expenditure of contract funds over the period of performance per task. (DI-MGMT-81797, Program Management Plan)

4.2.2 Resource Management

The contractor shall provide timely notification of problems in program management that impact cost, delivery, or schedule. The contractor shall provide an initial Program Management Plan (PMP) for this effort; thereafter, monthly, the contractor shall provide a summary of documents generated and expenditures for this effort, to include travel. These summaries shall show the planned expenditures, comparing planned to actual expenditures. Deviations shall be explained, and recovery plans shall be developed. Technical tasking progress shall be summarized to include accomplishments, compliance to schedules, issues, problems, and risks to completion of the contracted effort. The Contractor shall provide this information in Monthly Status Report (MSR). (DI-MGMT-81797, Program Management Plan; DI-MISC-80711A, Scientific and Technical Reports; DI-ADMN-81373, Presentation Material; DI-MGMT-80368A, Status Report)

4.2.3 Configuration Management

The contractor’s Configuration Management shall be consistent with Software Engineering Institute Capability Maturity Model Integration (SEI CMMI) Level 3, or higher, processes defined in Capability Maturity Model Integration, Version 1.1. The Government may use the on-site Defense Contract Management Agency (DCMA) representatives to maintain insight into the Contractor’s Configuration Management program or utilize members of the AN/ALR-69A Program Office to monitor work performed against established policies and procedures.

4.2.4 Meetings and Conference Calls

The contractor shall support Government meetings for the purpose of maintaining open communication to identify any problem areas that may impact the schedule with a focus on timely corrective action. If hosting, the contractor shall provide meeting minutes within ten

PR: FD2060-26-30369 PWS REVISION: 0 15

business days after the completion of each meeting. The Government will provide at least one-week prior notification to the contractor before scheduling any status and planning reviews. The Government will determine the subject matter of all reviews, and the contractor shall assist in developing presentation material and the agenda prior to each review. Additionally, the contractor shall host or participate in meetings and telephone conference calls for the purpose of, but not limited to exchanging technical information, discussing status, reviewing requirements, managing resources, and planning. These activities will be scheduled as needed. (DI- ADMN- 81250B, Conference Minutes; DI-ADMN-81373, Presentation Material)

4.2.5 Reporting Requirements

No individual engineering task shall require re-work more than once. Re-work shall be defined as work performed to correct defects/failures.

4.2.5.1 Status Reporting

The contractor shall prepare and deliver a status report monthly throughout the period of performance of this effort. (DI-MGMT-80368A, Status Report).

The Government will use the status report to assess contractor performance during each phase of the effort. As such, the status report shall:

a) Include status of work performed during the current reporting period and work planned for the next reporting period

b) Include explanations for all re-work performed during the reporting period and/or planned for the following reporting period

c) Include reporting of earned value for each work package defined in the WBS. Earned value shall be represented by the Budgeted Cost of Work Performed (BCWP), Budgeted Cost of Work Scheduled (BCWS) and Actual Cost of Work Performed (ACWP) metrics respectively

d) Include financial reporting of current and cumulative expenditures

e) Include for each WBS work package the projected and expended cumulative staff hours, as well as current reporting period hours

f) Include trip reports for all contract related travel during the reporting period

For those requirements that specify bi-monthly status reviews, the minutes from the review, coupled with the required information previously listed, shall satisfy the monthly status report requirement.

Rework shall be defined as the work performed to correct defects.

4.2.5.2 Technical Reporting

The contractor shall prepare and submit interim, as well as a final technical report, IAW the requirements of National Information Standards Organization (NISO) Z39.18. Interim technical reports shall be prepared and submitted within 30 calendar days following the conclusion of a specific task (i.e., component demonstration) that warrants such a report. AFLCMC, EW Division, is the final decision authority to determine whether a task requires an interim technical report. The final technical report shall, as a minimum, include a summary of all work accomplished and the information gained in the performance of this contract, all interim

PR: FD2060-26-30369 PWS REVISION: 0 16

technical reports, pertinent observations, nature of issues, positive, as well as negative results, and design/test criteria where applicable. (DI-MISC-80711A, Scientific and Technical Reports)

4.3 Formal Audits and Reviews

The contractor shall support, participate in, and as directed by AFLCMC, EW Division, chair formal program reviews IAW the requirements defined herein, as well as each individual task.

The program reviews shall alternate between the contractor’s facility and AFLCMC, EW Division, unless otherwise approved by the Government. The contractor shall deliver presentation material, formal agenda, and minutes for each review except as otherwise noted herein. Approval of the formal minutes by the Air Force technical monitor shall constitute permission for the contractor to continue with work as defined herein. A program schedule organized by WBS shall be provided by the contractor prior to each new task’s Orientation Review and shall be discussed at all subsequent reviews. The contractor may combine program reviews with other reviews required to minimize cost. (DI-ADMN-81249C, Conference Agenda;

DI-ADMN-81250C, Conference Minutes; DI-ADMN-81373, Presentation Material)

4.3.1 Orientation Review

The contractor shall conduct an Orientation Review within 45 calendar days ARO of each individual task placed under this PWS. No formal pre-submitted agenda is required; but, as a minimum, the following items shall be included in this review:

a) Review Task Requirements

b) Review CDRLs

c) Review WBS

d) Review contract deliverables (non CDRL specific requirements)

e) Review program schedule requirements

f) Review technical data required in support of the task

g) Review any requests for non-interference use of Government Furnished Property (GFP) available under separate contracts

4.3.3 Subsequent Program Reviews

Subsequent program reviews shall be conducted as required in each individual task following the Orientation Review and shall include, as a minimum, the following items:

a) Review of previous program review minutes

b) Review and status of action items

c) Summary of work started and accomplished

d) Review any issues encountered with contract requirements

e) Review study results and status of all requirements

f) Review status of all CDRL deliverables

g) Review status of all other contract deliverables

h) Review of Government-Furnished Equipment (GFE) and requirements for Government information or material

i) Review program schedule

j) Action items and minutes

Unless specified in the individual task, Program Reviews shall be conducted quarterly after the Orientation Review.

PR: FD2060-26-30369 PWS REVISION: 0 17

4.3.4 Final Program Review

The Contractor shall conduct and document a Final Program Review (FPR) 25 – 35 calendar days prior to task completion. The FPR shall include program review items with a focus on the actions required to complete and close out the task.

4.3.5 Technical Coordination Meetings (TCMs)

The contractor shall support and participate in, at the discretion of the Government, TCMs with AFLCMC, EW Division, and associated contractors. The location of the TCMs will be mutually determined and agreed upon a minimum of seven calendar days prior to the TCM. No formal pre-submitted agenda is required; however, each TCM shall begin with the contractor providing a status of all work. The Contractor shall prepare the minutes from each TCM. The TCMs will be scheduled on an as needed basis and may be requested by either the Contractor or USAF.

Unless specified in an individual task, the Contractor shall be asked to support no more than seven TCMs per task.

4.4 Restrictions on the use of Proprietary Material

The contractor shall not develop any proprietary data or processes in the performance of the actions required by this contract. The Government will have unlimited or unrestricted rights to all technical data, drawings, and software developed exclusively with Government funding for this contract. The Contractor shall identify any proprietary hardware, software, drawings or data referring or relating to Government logistics support that has been developed at private expense.

The Government will have Government Purpose License Rights for logistical support if any proprietary hardware, software, drawings, or data developed at private expense is used.

For this PWS, "logistics support" refers to the Government’s ability to procure, supply and maintain the systems, as well as any/all updates to the systems’ hardware, software, and documentation. With Operational Safety, Suitability, and Effectiveness (OSS&E) responsibility, it is imperative that the Government (either organically or contractually) modify/perfect software, hardware, and/or documentation to keep the system viable and effective in an ever-evolving threat spectrum. For those efforts that are contracted, the Government requires the ability to compete the workload.

4.5 Ozone Depleting Substance (ODS)

All Military Specifications, Military Standards, drawings, and applicable documents on hardware, manufacturing processes, or data generation are provided to the contractor for background information. No task issued under this contracting vehicle will direct or require the contractor to utilize ODS. The contractor is requested to discontinue use of any products or materials requiring ODSs to accomplish the requirements associated with this PWS.

5.1 Period and Place of Performance

5.1.1 Contract/Order Period of Performance: The period of performance for the contract will extend to a period of 12 months After Receipt of Order (ARO) plus four option periods that are 12 months duration each. The total ordering period for this PWS is 60 months.

PR: FD2060-26-30369 PWS REVISION: 0 18

5.1.2 Place of Performance: These services will be performed at primarily the contractor’s facility but may require travel at the Government’s discretion to Continental United States (CONUS) locations.

5.2 Contract Data Requirements List(s) (CDRL)

Document Identifier Base Year

Option Year

Option Year

Option Year

Option Year

DID Title PWS Reference(s)

A001 B001 C001 D001 E001 DI-MISC-

80711A

SCIENTIFIC AND

TECHNICAL REPORTS

4.0.1, 4.0.1.1, 4.0.1.2, 4.0.1.3, 4.0.1.8, 4.0.1.10, 4.0.1.11, 4.0.2, 4.0.3.1, 4.0.3.4.1, 4.0.3.4.2, 4.0.3.4.3, 4.0.4, 4.1.8, 4.2.2, 4.2.5.2

A002 B002 C002 D002 E002 DI-IPSC-

81427B

SOFTWARE

DEVELOPMENT PLAN

4.0.1.4, 4.1.5, 4.1.8

A003 B003 C003 D003 E003 DI-

ADMN-

81249C

CONFERENCE

AGENDA

4.0.1.9, 4.3

A004 B004 C004 D004 E004 DI-

ADMN-

81250C

CONFERENCE

MINUTES

4.0.1.9, 4.3

A005 B005 C005 D005 E005 DI-

ADMN-

81373

PRESENTATION

MATERIAL

4.0.19, 4.2.2, 4.2.4, 4.3

A006 B006 C006 D006 E006 DI-

MGMT-

81797

PROGRAM

MANAGEMENT PLAN

4.2.1, 4.2.2

A007 B007 C007 D007 E007 DI-

MGMT-

80368A

STATUS REPORT 4.0.1.10,

4.0.1.11, 4.2.2, 4.2.5.1

A008 B008 C008 D008 E008 DI-IPSC-

81433A

SOFTWARE

REQUIREMENT

SPECIFICATIONS

4.1.7, 4.1.8

A009 B009 C009 D009 E009 DI-IPSC-

81434A

INTERFACE

REQUIREMENTS

SPECIFICATION

4.1.8

A00A B00A C00A D00A E00A DI-SESS-

80639E

ENGINEERING

CHANGE PROPOSAL

4.0.2, 4.0.3.3

A00B B00B C00B D00B E00B DI-IPSC-

81435B

SOFTWARE DESIGN

DESCRIPTION

4.1.8

A00C B00C C00C D00C E00C DI-IPSC-

81436A

INTERFACE DESIGN

DESCRIPTION

4.1.8

A00D B00D C00D D00D E00D DI-IPSC-

81439A

SOFTWARE TEST

DESCRIPTION

4.1.8

A00E B00E C00E D00E E00E DI-IPSC-

81440A

SOFTWARE TEST

REPORT

4.1.8

PR: FD2060-26-30369 PWS REVISION: 0 19

A00F B00F C00F D00F E00F DI-IPSC-

81442A

SOFTWARE VERSION

DESCRIPTION

4.1.8, 4.1.9

A00G B00G C00G D00G E00G DI-IPSC-

81443A

SOFTWARE USER

MANUAL

4.1.8

A00H B00H C00H D00H E00H DI-NDTI-

80566A

TEST PLAN…