DRAFT PWS - Engineering Services for ALR-69A - 20260320.pdf

Performance Work Statement for

AN/ALR-69A Radar Warning Receiver (RWR) Indefinite Delivery Indefinite Quantity (IDIQ)

Engineering Services

DISTRIBUTION D. Distribution authorized to Department of Defense (DoD) and US DoD Contractors only.

ADMINISTRATIVE OR OPERATIONAL USE, March 2026. Other requests for this document will be referred to AFLCMC/ESY, 235 Byron Street, Ste 19A, Robins AFB, GA 31098-1670

WARNING - This document contains technical data, directly or by reference, whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended. Violations of these export laws are subject to severe criminal penalties. Mark and disseminate document in accordance with provisions of DoD Directive 5230.25 and E.O. 13559.

DESTRUCTION NOTICE – Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Controlled by: Information Protection CUI category: CUI Basic

Distribution: DoDI 5230.24 marked herein

1.0 Description of Services

1.1. (CUI) This PWS describes the scope of services and materials required to complement the AN/ALR-69A organic engineering capability. While the scope of this PWS is extensive in nature, the expertise required is specific to the AN/ALR-69A RWR systems. The Contractor shall supply AN/ALR-69A RWR engineering services and materials as required to complement the Air Force Life Cycle Management Center, Electronic Warfare and Avionics Division (AFLCMC/ESY) organic engineering capability. These services and materials shall include:

Requirement Description CUI A Engineering Support of software tasks for repair, perfection of the AN/ALR-69A

Operational Flight Programs (OFPs) and Mission Data File (MDF) tables (to include block cycle build(s) prior to full inclusion into OFP)

B Laboratory, ground, and flight test support for OFP effectiveness/certification and integration efforts

C Engineering Support for AN/ALR-69A technical support/integration with;

weapons system (i.e. aircraft), mission equipment avionics, flight line equipment, as well as Depot and field level support equipment

D Studies, analyses, evaluation, and experiments utilizing hardware/software to define deficiencies, modifications, capabilities, and supportability issues for the system

E Technical services for new or current aircraft integration efforts involving the RWR; for interoperability or compatibility with systems installed along with the AN/ALR-69A

F Deliver Hardware and software items in support for the AN/ALR-69A Software Engineering Environment (SEE) and Test Tools (TTs)

G Design and prototype AN/ALR-69A software/firmware modifications and integration efforts to/for the RWR system

H Documentation support that includes updating AN/ALR-69A software documentation, source data for commodity technical orders, technical data package (system and parts specifications), and familiarization training materials

I Engineering Services to support organic source of repair (SOR) capabilities, to define test program sets (TPS) requirements, to plan and update SEE and TTs associated with the AN/ALR-69A RWR system

1.2. Benefit to United States Air Force (USAF):

(CUI) This effort provides a significant benefit to the USAF by enabling aircrews and Mission Data (MD) programmers to maintain effectiveness in the Area of Responsibility (AOR). It allows them to effectively identify and provides situational awareness for emerging threats to meet their mission requirements. The effort will make the system more sustainabe translating to an improved ability to identify/range/locate threats, increased integration with the aircraft platform and improved angle accuracy.

1.3. Background:

GLOVER, LA.FOREST E CIV USAF AFMC AFLCMC/ESYC

Should Golden Assets be included here

DAVE, ANAND V CIV USAF AFMC AFLCMC/ESY

No, it isn’t applicable.

(CUI) As the United States Air Force (USAF) engineering authority for the AN/ALR-69A system, the AN/ALR-69A Program Office needs to direct a tasking alignment of the Contractor to maintain a common software/hardware engineering environment and the configuration tracking to understand functional changes in the software and hardware. The Government’s goal is to keep the software/hardware baselines similar which will make a single AN/ALR-69A baseline. This will reduce the sustainment cost of maintaining and improving the AN/ALR-69A software and hardware across various aircraft platforms.

2.0 Services Summary

(U) The Government will evaluate performance of the services listed in the services summary (SS) table below to determine if each task order meets the performance thresholds. The Contracting Officer Representative (COR) will follow the methods of surveillance specified in the Government’s Quality Assurance Surveillance Plan (QASP), and when the proper level of performance is not met, the Contracting Officer (CO) will issue a Corrective Action Request (CAR). When an observation indicates defective performance, the COR will require the contractor representative to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation, only acknowledgment that they have been made aware of the defective performance.

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

TBD 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

TBD 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

7TBD 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 TBD 100% compliance with the QMS is required.

Receipt of CDRL TBD 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 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 Technical Requirements

(CUI) The AN/ALR-69A System tasking and studies requires a specific skill-set and knowledgeable staff capable of addressing the broad range of activities as indicated in Section 1.

In maintaining Operational Safety, Suitability, and Effectiveness (OSS&E), the correctness and availability of documentation is critical. The Contractor shall maintain the technical data package for tasks that change the software Computer Software Configuration Items (CSCIs) or Hardware Configuration Item (HWCI); to include software documentation, Technical Data Package (TDP)/drawings support, firmware support, Technical Orders (TOs) changes, handbooks, test procedures, support/test tools and training materials. As AFLCMC/ESY continues to develop organic staff and capability, this contracting vehicle will be utilized to supplement the stated organic repair capability. The Contractor shall maintain a technical staff with the depth and breadth of knowledge required to enhance the government organic staff.

(CUI) TThe four categoriesinstances of software sustainment operational tempo are Block cCycle (BC), Routine, Urgent and Emergency (Reference DAFMAN 10-703). The typical BC operations tempo (Block cycle) will be an output of tested software changes for integration into the common allocated software baseline every 120 days. BClock cycle software leaps will be defined to less than this, i.e. within 60 calendar days. Additionally, in response to real world events, as well as exercise activities, AFLCMC/ESY requires expert level Contractor support to resolve complex issues within a short period of time. The Contractor shall be required to provide deliveries along with documentation of the change appropriate to the level of request where:

Emergency is within 12 clock hours from tasking; Urgent is within 48 clock hours from tasking;

and a Routine tasking change within 7 calendar days. The contractor shall have the depth and breadth of knowledge required to meet Emergency requirements immediately upon contract award

3.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)

3.2. Operational Flight Program (OFP) Support

(CUI) 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 DAL 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)

3.3. Mission Data Support

(CUI) 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, depending on the urgency assigned by the country. This mission data will address anomalies that have been identified in lab, chamber, ground and flight test events. 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)

3.4. 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)

3.5. Future Block Cycle Planning

(CUI) The Contractor shall assist the Government with future block cycle planning for AN/ALR- 69A OFP block cycles. The Contractor shall:

f. Document and track SCRs, Operation Change Requests (OCR) and Software Problem Reports (SPR)

g. Perform and document analyses to determine the feasibility and methodology of implementing the software changes

h. Perform analyses of alternatives to software changes

i. Assess and document the system and software impacts of each software change

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

k. Develop budgetary estimates (to include both current year dollars & hours) for implementing each software change

l. Draft and provide a software development plan that contains work breakdown structures

m. Draft and provide a software engineering environment plan that assesses the current and future configuration of support posture.

(A002)

3.6. 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.

3.7. 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.

3.8. Software Product Validation

3.8.1. Operational Flight Program (OFP) Certification

(CUI) The contractor shall certify the compliance and vulnerability of the OFP that is generated or supplied against the Information Assurance (IA) certification package security plan.

3.8.2. Mission Data Generator Certification

(U) The contractor shall generate mission databases as directed by the government. The contractor shall validate the efficiency and correctness of the output files from the updated Mission Data File Generators (MDFG) and the MDFs that it generates. The contractor shall certify the compliance and vulnerability of the tool product that is generated or supplied against the IA certification package security plan.

3.9. Certification Support

3.9.1. Classified Products

(U) The Contractor shall plan and perform security tests that are defined in the AN/ALR-69A cyber security assessment and authorization package that will culminate in an AN/ALR-69A sub-system platform information technology (PIT) certification for a standalone test environment and shall also support determinations by multiple weapons system offices within its connected topology to those information system (IS) networks. (A00P; A00R; A00N)

3.9.2. SIPRNET Products

(U) The Contractor shall plan and perform tests that shall culminate in authorization to operate (ATO) certification on standalone and on Secret Internet Protocol Router Network (SIPRNET) machines connected to those IS networks. (A00P; A00R; A00N)

3.10. 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.

3.11. Analysis of Alternatives (AOA) Roadmaps

(CUI) As required, the contractor shall generate or update hardware and software roadmaps for the AN/ALR-69A RWR. 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)

3.12. System Familiarization

(CUI) 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)

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

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

3.13. Hardware Conditioning and Failure Analysis

3.13.1. Hardware Conditioning

(U) 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)

3.13.2. Failure Analysis

(U) 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. As requested by the government, contractor shall screen units to determine condition (DI-MISC-80711A, Scientific and Technical Reports)

3.2. System Engineering

3.2.1. Engineering Studies

(CUI) 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, Electromagnetic Inerference (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 RWR. 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)

3.2.2. 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 unless otherwise directed by the government. The contractor may only proceed to the subsequent phase after Government approval. Phases are described as follows:

3.2.2.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)

3.2.2.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 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.

3.2.2.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)

3.2.2.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.

3.2.2.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)

3.2.2.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)

3.2.2.4.3. Electromagnetic Interference 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 prepare and deliver a test report detailing all test results. (DI-NDTI-80603A, Test Procedure; DI- MISC-80711A, Scientific and Technical Reports)

3.2.2.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.

3.2.2.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)

3.3. Material and Subject Matter Expertise Support

(CUI) 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)

3.4. General Software Requirements

3.4.1. Software Engineering Process

(CUI) 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 approved contractor coding standards and process documents.

3.4.2. Software Configuration Management

(U) 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 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.

3.4.3. Software Quality Assurance

(U) 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

3.4.4. Development Environment

(CUI) The software development environment shall consist of programs compatible with the Windows version in use by the 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.

3.4.5. Software Development Plan

(U) The Contractor shall conduct software project planning for each software engineering task required by this task. The Contractor shall prepare and deliver an updated software development plan for review and approval by the USAF. The software development plan shall be updated as changes occur during the software engineering task. (A002)

3.4.6. Software Requirements Review

(U) 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

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 (A003, A004)

3.4.7. Software Requirements Analysis

(U) 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. (A008; A00A)

3.4.8. Software Documentation

(CUI) For all software tasks, the Contractor shall create or update the following documentation defining the delivered baseline:

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)

3.4.9. Software Deliverable Format

(U) The Contractor shall deliver source programs, computer software product end items for software projects, the development environment, and all supporting utility software for the task.

Work product source code, executable, documentation, and test artifacts shall be delivered and made available for software integration and test. All files shall be delivered as electronic files for Government editing tools identified in CDRL. Source code, executables and documentation shall be delivered in a media format as directed by the government. As directed by the government, an SVD for each CSCI and/or the overall system SVD shall be submitted for USAF review and approval. (A010, (Source Code); A010, (Executable); A00F)

4.0 General Program Requirement

4.1. Program Management

(CUI) For each task, the Contractor shall assign a program manager (PM) to manage the work required. The PM shall have overall authority and responsibility for performing and documenting all required work, which includes ensuring that all contractual deliveries, as well as technical requirements, are in compliance. The PM shall be the chief point of contact to the USAF regarding program and technical issues of this task; therefore, the Contractor shall identify the assigned PM and associated contact information to the USAF’s Procurement Contract Officer (PCO), PM, and Technical Representative. The Contractor shall implement a financial tracking system per the management plan to track expenditure of contract funds over the period of performance per task. The contractor shall maintain a list of program documents and deliver this list for Government review and further Deliver.

4.2. Status Reporting

(CUI) The Contractor shall provide timely notification of problems in program management that impacts cost, delivery, or schedule. 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). (A001; A002; A005; A007)

4.3. Configuration Management

(U) 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.4. Meetings and Conference Calls

(U) 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 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. (A003; A004;

A005)(DI- ADMN-81250B, Conference Minutes; DI-ADMN-81373, Presentation Material)

4.5. Reporting Requirements

(U) No individual engineering task shall require re-work more than once. Re-work shall be defined as work performed to correct defects/failures. The Contractor shall provide timely notification of problems in program management that impacts cost, delivery, or schedule.

4.5.1. Status Reporting

(CUI) The Contractor shall prepare and deliver a status report on a monthly basis throughout the period of performance of this effort. The USAF will use the status report for assessing Contractor performance during each phase of the effort. As such, the status report shall (DI-MGMT- 80368A, Status Report).:

a) Be organized by WBS using MIL-HDBK-881, DoD Handbook – Work Breakdown Structure, as a guide

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

c) Include reporting of projected versus actual cost and work performed.

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

g) Include, in detail, an explanation of deviations and any recovery plans.

h) Technical tasking progress shall be summarized to include accomplishments, compliance to schedules, issues, problems, and risks to completion of the contracted effort

(U) 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 that work performed to correct defects. (A007)

4.5.2. Technical Reporting

(CUI) 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/ESY is the final decision authority to determine whether or not 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 technical reports, pertinent observations, nature of issues, positive, as well as negative results, and design/test criteria where applicable. (A001) (DI-MISC-80711A, Scientific and Technical Reports)

4.6. Formal Audits and Reviews

(CUI) The Contractor shall support, participate in, and as directed by AFLCMC/ESY, 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/ESY unless otherwise approved by the Government. The Contractor shall deliver presentation material, formal agenda, and minutes for each review per paragraph

4.4 except as otherwise noted for the following sub-paragraphs 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. (A003; A004; A005) . (DI-ADMN-81249C, Conference Agenda; DI-ADMN- 81250C, Conference Minutes; DI-ADMN-81373, Presentation Material)

4.6.1. Orientation Review

(U) 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.6.2. Subsequent Program Reviews

(U) Subsequent program reviews shall be conducted as required in each individual task following the task’s Orientation Review, program reviews will commence after Orientation Review and occur at most quarterly 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 Government-Furnished Equipment (GFE) and requirements for Government information or material

i) Review program schedule

j) Action items and minutes

4.6.3. Final Program Review

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

4.6.4. Technical Interchange Meetings (TIMs)

(CUI) The Contractor shall support and participate in, at the discretion of the USAF, TIMs with AFLCMC/ESY and associated Stakeholders. The location of the TIMs will be mutually determined and agreed upon a minimum of seven (7) calendar days prior to the TIM. No formal pre-submitted agenda is required; however, each TIM shall begin with the Contractor providing a status of all work. The Contractor shall prepare the minutes from each TIM. The TIMs 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 TIMs per task.

4.7. Data Rights

(U) Unless agreed upon by the Government, Contractor shall not develop any proprietary data or processes in the performance of the tasks required by this contract. The Government will have unlimited or unrestricted rights to all modified technical data, modified drawings, and modified software or wholly developed items with or in part with Government funding for this contract under the Rights in Technical Data Clause, Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013. The Contractor shall identify any patents, proprietary hardware, software, drawings or data referring or relating to Government logistics support that has been developed at solely private expense. The Government will have Government Purpose Rights to these items to satisfy logistical support if any proprietary hardware, software, drawings, or data developed at private expense is allowed.

For the purpose of 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 OSS&E responsibility, it is imperative the Government can (either organically or contractually) modifyf software, hardware, and/or documentation to keep the system viable and effective in an ever-evolving threat spectrum.

4.8. Ozone Depleting Substances (ODS)

(U) 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 processes, products or materials requiring ODSs to accomplish the requirements associated herein.

4.9. Data Management

(U) The Contractor shall electronically deliver all contractual data using the Government-controlled method of delivery, Multi-user Engineering Change Proposal (ECP) Automated Review System (MEARS), https://mears1.redstone.army.mil/mears/Default.aspx. The Contractor shall work with the Government to ensure that an adequate number of Contractor personnel obtain and possess Public Key Infrastructure (PKI) certification from an accepted Government source. The Contractor shall be receptive to the training offered by the Government on the MEARS system. The Contractor shall prepare, maintain, and track the contract data status, schedule and ensure timely data deliveries. An alternate method of delivery when MEARS is down for maintenance will be the DISA application, known as DOD SAFE, https://safe.apps.mil/. It will be available to all DOD Common Access Card (CAC) holders or Contractor personnel who possess PKI certification from and accepted Government Source.

4.10. Preparation for Shipment and Delivery

4.10.1. End Items and Components

(U) The Contractor shall package and mark hardware end items and components IAW the contract (basic or order, as applicable) Air Force Materiel Command (AFMC) Form 158, Packaging Requirements; MIL-STD-129P, Department of Defense Standard Practice / Military Marking for Shipment and Storage; MIL-STD-147E, Department of Defense Standard Practice / Palletized Unit Loads; MIL-STD-130N, Department of Defense Standard Practice / Identification Marking of U.S. Military Property; MIL-STD-2073-1D, Standard Practice for Military Packaging; and MIL-STD-1686C Electrostatic Discharge Control Program for Protection of Electrical and Electronic Parts, Assemblies and Equipment. The Contractor shall ensure that classified material is packaged, marked and shipped IAW DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) and the contract DD254. The Contractor shall package, mark, and status material IAW other applicable Government regulations including, but not limited to, those regarding security, safety and environmental concerns. End item shipments shall be documented on DD1149 and delivered with part of the shipment.

4.10.2. Shipping Containers

(U) The size and type of containers to be used for shipment of real property are documented in the supply system provisioning data for the hardware part number/National Stock Number (NSN). IAW MIL-STD-2073-1E, shipping containers received, which meet the requirements of the Air Force Material Command (AFMC) Form 158 and are suitable for return shipment of serviceable assets, shall be reclaimed and stored for reutilization. Unsuitable shipping containers shall be disposed of and replaced with new containers that meet the requirements of the AFMC Form 158.