Attachment 1 - Basic IDIQ Statement of Objectives (SOO).pdf

DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited.

DISTRIBUTION STATEMENT A.

Attachment 1

Statement of Objectives (SOO) - IDIQ

Science and Technology Applied RF Systems (STARS)

ARA No.: FA8650-19-S-1110 Call 7

11 March 2024

1.0 Background

The Air Force Research Laboratory's (AFRL) Sensors Directorate (RY) mission is to lead the discovery and development of future capabilities, providing integrated Intelligence, Surveillance, and Reconnaissance (ISR), combat identification, and spectrum warfare effects. Recently

Department of the Air Force (DAF) published a set of operational imperatives for Air Force (AF) components to focus on and address. Operational Imperative 3 focuses on moving target engagement, Operational Imperative 4 focuses on tactical Air Dominance, and Operational

Imperative 6 focuses on Global Strike capabilities. As part of AFRL’s mission, radio frequency

(RF) system technologies must be developed and advanced to facilitate the realization of these operational imperatives. The Multispectral Sensing & Detection Division (AFRL/RYM) conducts exploratory and advanced development activities to meet Air Force aerospace RF sensor needs for air, space and command and control (C2) sensors systems. This includes modeling, simulation, research, design, test and evaluation of RF subsystems, sensors, and signal processing/exploitation algorithms for use in offensive, defensive and integrated offensive/defensive systems. The results of AFRL/RYM investments must help ensure unequaled persistent ISR; time sensitive targeting; and battlespace access capabilities for America's Air and

Space Forces through developing, demonstrating and transitioning advanced RF and electro-optical (EO) sensors/signal processing/exploitation. Past efforts include investigating advanced

RF sensing concepts that facilitate simultaneous imaging and detection of movers, detection and localization of emitters of interest, and the automated identification of targets of interest from a variety of sensing phenomenologies and concepts of operation (CONOPS).

2.0 Objective:

The objective of the STARS program is to develop advanced RF capabilities which will provide sensing for all-weather day-night ISR using non-traditional radar modes for persistent surveillance across permissive, contested, and highly contested boundaries in multiple environments (e.g., air, land, sea, space and cyber space) to improve the capabilities of the Air

Force and Tri-Service Communities. These capabilities will provide sensing solutions for Passive

Source Localization (PSL), Synthetic Aperture Radar (SAR), Moving Target Indication (MTI), as well as a myriad of enabling and complementary technologies and research areas including but not limited to Tracking, Automatic Target Recognition (ATR), Interference Suppression, and

Modeling Simulation and Analysis (MS&A). To achieve the stated objective, the program is to perform modeling, simulation, analysis, development, design, fabrication, testing, evaluation, demonstration and conceptualization of RF and multi-INT subsystems, components, devices, electronics manufacturing, and signal processing/exploitation technologies as well as leveraging past and ongoing advancements across the AFRL/RY Directorate. These objectives will be realized through individual task order (TO) projects with well-defined and focused objectives, resources, and periods of performance.

3.0 Tasks:

The tasks to fulfill the objectives of the STARS IDIQ (Indefinite Delivery/ Indefinite Quantity) contract will focus on subsystem design and fabrication for technology evaluation or demonstration. However, the Task Orders (TO) themselves may encompass one or multiple congregated sub-efforts in the following categories: (3.1) Algorithm and Software Design, Development, and Implementation; (3.2) Modeling, Simulation, and Analysis (MS&A); (3.3)

Laboratory and Flight Testing and RF Hardware Development; and (3.4) Systems Integration and

Transition Planning. Each category is described in more detail below.

3.1 Algorithm and Software Design, Development, and Implementation

The objective of this research is to advance RF algorithm and software design, development, and implementation. This includes fundamental analysis at the mathematical level, prototyping in high-level languages (e.g., MATLAB/Python), and realization of real-time implementations suitable for laboratory and flight testing activities (e.g., C/C++/Rust/Cuda potentially on embedded architectures) with the goal of producing technologies suitable for transition to operational systems.

3.1.1 Develop novel and/or advanced complete “mode” (e.g., Synthetic Aperture Radar, Moving Target Indication, and/or Passive Source Localization) level algorithms and techniques that address one or more of the relevant Operational Imperatives

(OI-3, OI-4 and/or OI-6). These approaches should include considerations for practical operation in relevant environments.

3.1.2 Develop novel and/or advanced enabling and supporting algorithms and techniques such as pre-processing (e.g., waveform design, pulse compression, interference suppression and signal pre-selection), and core processing steps (e.g., image formation, target detection, target recognition, signal analysis and identification).

3.1.3 Develop novel and/or advanced post processing and exploitation techniques such as sophisticated tracking approaches, ATR, and signal reconstruction.

3.1.4 Develop techniques addressing complementary phenomenologies/domains (e.g., EO, communications, light detection and ranging (LiDAR)) in pursuit of advanced RF sensing systems as part of multiple intelligence signal (multi-INT) fusion techniques.

3.2 Modeling, Simulation, and Analysis (MS&A)

The objective of this research is advance, design, develop, and employ tools that facilitate prediction of RF system or signal processing performance for exploratory, experimental planning, testing, and operational planning activities. The MS&A category includes

Engineering Level MS&A, and Mission Level MS&A.

3.2.1 Engineering Level MS&A are relevant tools and codebases/capabilities that facilitate understanding technologies at a practicable design level. For example, solutions that address Engineering Level MS&A may provide Signal Level

MS&A that mimic real-world signals and their interaction with the environment such that algorithms can be developed to process those signals.

3.2.1.1 Develop signal-based MS&A that will yield/produce/output representative synthetic data and facilitate the analysis of synthetic data suitable for algorithm development in lieu of and/or, in anticipation of, and/or in validation of flight test or operational data collections. Signal level MS&A is desired that can: simulate scenarios (e.g., platforms, flight paths, target paths, locations) with arbitrary signals (e.g., radar, communications, commercial broadcast) with modest or high fidelity system effects (e.g., transmit power, antenna patterns, polarization, coherence errors, arbitrary waveforms), and with environmental effects (e.g., clutter scattering, target scattering, stationary objects, moving objects, internal clutter motion).

3.2.1.2 Conduct signal-based analysis that includes variation of simulation parameters

(and in turn the underlying model parameters) in order to assess performance of (a) the model (e.g., fidelity vs measured) or (b) the downstream algorithms and techniques (e.g., finding or exercising edge cases of algorithmic techniques via simulated data).

3.2.1.3 Develop system and/or subsystem MS&A that can simulate RF systems such as a complete radar, a scheduler, or an antenna. This may include developing a system model for performance prediction/validation or employing an external model as part of analysis towards STARS objectives.

3.2.2 Mission Level MS&A are relevant tools and codebase/capabilities that facilitate understanding technologies as part of an operational or experimental construct.

Mission Level MS&A capabilities facilitate analysis of coarse operational impact, feasibility, and/or performance over system level concepts and applications such that concept exploration, system integration, flight testing, and CONOPS development activities can be executed with analytical backing.

3.2.2.1 Develop models that are parametric in nature.

3.2.2.2 Create simulations that take coarse system parameters (e.g., platform position and kinematics, coarse antenna pattern), and the results should be general metrics (e.g., antenna footprint gain, Probability of Declaration/ Probability of

False Alarm (Pd/Pfa), Noise Equivalent Sigma Nought (NES0), pixel resolution and approximation, ambiguity ratios).

3.2.2.3 Conduct analysis on simulation outputs to ensure suitability for integration with higher level tools (e.g., Advanced Framework for Simulation, Integration, and Modeling software (AFSIM)) such that full scenario mission level analysis can be completed.

3.2.2.4 Conduct analysis on varying scenario parameters (and in turn model parameters) to assess operational impact of coarse system designs, coarse

CONOPS, and coarse Tactics Techniques and Procedures (TTPs) such that the results can inform the other objectives related to system design or data collection /mission planning strategies.

3.3 Laboratory and Flight Testing and RF Hardware Development

The objective of this research is to advance the other technical areas via testing that ultimately facilitates the realization of complete solutions suitable for transition.

3.3.1 Design, develop, and execute data collection and test activities including software in the loop (SWIL) testing, hardware in the loop (HWIL) testing, chamber testing, fixed-site over-the-air testing, and flight testing. Reasonable/representative size, weight and power (SWaP), or other predicted operational constraints, should be identified and analyzed for applications addressing the three Operational

Imperatives (OI-3, OI-4, OI-6).

3.3.2 Design and develop test hardware such as radar systems, receiver systems, and transmit systems, including upgrades to existing systems as well as one-off test apparatuses. Systems should incorporate flexibility of operations to address, when possible, a wide range of operating environments (permissive, contested, and highly contested).

3.3.3 Conduct demonstrations and data collection activities that include Continental

U.S. (CONUS) and Outside Continental U.S. (OCONUS) activities as well as integration with operational systems or the operationalization of systems under test.

3.4 Systems Integration and Transition Planning

This objective seeks to address planning and executing technology transition and system transition activities for operational partners. This includes system deployment support and participation, system integration, testing and assessment, and other needed support activities.

3.4.1 Provide technology transition (operation and maintenance (O&M)) support to determine how to satisfy a deficiency or required modifications. Provide support testing related to the O&M of equipment and material acquired for use under appropriations other than Research, Development, Test, & Evaluation (RDT&E).

Incorporate minor upgrades and modernizations for technology refresh to operational systems and provide routine testing of operational systems to understand system performance. The Contractor shall not perform work under this task until authorization is given by AFRL.

4.0 General Requirements:

The objective of this section is to provide general requirements which are applicable to individual Task Order (TOs).

4.1 Government Furnished Information/Equipment

Design and develop solutions to maximize use of AFRL Government Purpose Rights (GPR) and Unlimited Rights (UL) Codebases and Intellectual Property (IP). Over many years of investment AFRL has grown Government IP significantly and this IP will be made available to performers. Performers should maximally leverage this IP and contribute to its continued development, refinement, and expansion as appropriate.

Currently the bulk of Government IP is MATLAB based with limited reliance on toolboxes.

Over time it is anticipated that these libraries transition to Python, and in some cases

C/C++/Rust (memory safe languages preferred) for real-time and/or high-performance-computing applications. Real-time and/or high-performance computing variants should be callable by high-level languages such as MATLAB and Python (or both) when feasible. An example of such a realization is the Fastest Fourier Transform in the West (FFTW) library which has Application Programming Interfaces (API) in both MATLAB and Python.

AFRL may provide software and/or hardware systems (e.g., KAAPS and Gotcha Spiral 2), that were delivered to AFRL with GPR and/or UL.

4.2 Government and Open Standards

Research and development conducted under STARS is to maximize the use of Government and other Open Standards where feasible. Government and Open Standards that are likely relevant include but are not limited to:

• MTI Standard Format - STANAG 4607

• Tracking Standard Format - STANAG 4676

• Compensated Receive Signal Data (CRSD)

• Compensated Phase History Data (CPHD)

• Sensor Independent Complex Data (SICD)

• Sensor Independent Derived Data (SIDD)

• Common Open Architecture Radar. Processing System (COARPS)

• Open Mission Systems (OMS)/ Universal Command and Control Interface (UCI).

Given the advanced nature of STARS it is anticipated that some standards do not have support for all emerging technologies. In those cases, the standard should be maximally leveraged with minimal bespoke augmenting features such that systems which accept the standard data formats will still function and those that can accept AFRL/STARS augmented data can exploit the additional information.

4.3 Common Development and Collaboration

4.3.1 Tasks completed under resulting task orders should maximize common development, continuous collaboration, and continuous testing and integration/testing with other performers under STARS. Task orders, sub-tasks, objectives, sub-objectives, etc. are anticipated to be complementary and sometimes co-dependent. As such, STARS teams are expected to collaborate continuously with each other, and with the Government team, throughout the duration of the contract, via Associate Contract Agreement (ACA).

4.3.2 Develop and contribute software in a Development, Security and Operations

(DevSecOps) and continuous integration/ continuous delivery (CI/CD) paradigm which includes automated unit / integration testing, linting, deployment, etc., as appropriate.

AFRL will provide a CI/CD environment as a baseline for collaboration, communication, and development. This solution may be augmented with additional solutions to meet team, customer, or other unique needs but should serve as the baseline for all development.

5.0 Management:

The overall management objective is to allow the offeror the maximum flexibility to innovatively manage the projected schedule, performance, risks, warranties, subcontracts and data to provide a STARS research program that satisfies the Government’s performance requirements.

5.1 Program Management and Reporting

Perform program management of cost, schedule, risk, and scope for the overall contract and for individual project research and development activities. Establish subcontracts as needed to meet contract objectives satisfying all technical requirements including data rights. Ensure access control measures are available and employed as required for proprietary information, classified information, and/or export-controlled information.

5.2 Technical Contract Management

The contractor shall keep track of each task, update the Government on the status of each task, and notify the Contracting Officer in the event of any change to cost, schedule, and/or performance of those tasks and overall STARS research program. The contractor is instructed that all tasks will be managed from the AFRL STARS Program Manager

(PM) and if the contractor is contacted by other organizations wanting to fund the contract, the contractor shall send the external organization to the AFRL PM immediately.

5.3 Kick-Off Meeting:

Host a kick-off meeting within 30 days of contract award, for each applicable task order.

Periodic program management reviews and technical interchange meetings will be required through the performance period of the STARS program. Agenda for all meetings will be developed jointly between contractors and Government POCs.

5.4 Technical Interchange Meetings (TIMs):

Host periodic TIMs, as required per individual task order.

5.5 Quarterly Program Reviews (QPR) and Conferences:

Participate in QPRs and Conferences, as required per individual task order. Note that conferences may be closed/non-public. Additionally, note that any information intended for public release must go through the AFRL/RY public release process with coordination through the AFRL STARS PM.

5.6 Incidental Material, Supplies and Testing Assets:

Procurement of materials if they are not available through Government channels and are required for the performance of this program. The materials may include consumable and/or non-consumable test equipment, supplies, replacements and new parts, components and subassemblies related to any of the sensing and processing elements, manufacturer’s literature, and manuals which are not available through Government channels and/or not available in sufficient time to meet the urgency requirements.

Flight/ground testing requirements may involve the need for and use of contractor-owned/operated and/or Government – owned/operated test bed aircraft.

6.0 Deliverables

Data shall be delivered in accordance with the Contract Data Requirements List (CDRL) as attached to the basic IDIQ. Specific hardware/software deliverables will be included in each task order, as applicable.

Attachment 1

7.0 Flight Tests

Comply with all the requirements of the AFRL test planning and approval process. This includes but is not limited to Technical Review Board (TRB) and Safety Review Board (SRB) reviews, AFRL airworthiness reviews in addition to all Air Force policies, regulations and instructions related to flight testing. Coordinate spectrum requirements for all testing and conduct any required coordination with the test location (e.g., range requirements, airspace coordination, ground instrumentation).

8.0 Operational Security - OPSEC

General OPSEC procedures, policies and awareness are required to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. The Critical Indicators and Information List

(CIIL) and the RY OPSEC Plan will be provided upon request by AFRL/RYSI Information

Protection Office. While working on the Government installation, OPSEC guidance and OPSEC training will be provided by AFRL/RYSI Information Protection Office. This training will ensure contractors are familiar with RY’s CIIL and RY’s OPSEC Plan as it pertains to their contract.

The contractor shall apply OPSEC in the management of their current program in accordance with (IAW) AFI 10-701 Operations Security and WPAFB Supplement to AFI-10-701.

9.0 Science and Technology (S&T) Protection

a. S&T Protection Plan Requirement: The Contractor shall support the Government in the planning, development, and implementation of the S&T Protection Plan (S&TPP), as required.

The S&TPP must document, at a minimum, (1) critical technology elements (CTE) and enabling technologies, (2) threats to and vulnerabilities of these items, and (3) selected countermeasures to mitigate associated risks.

10.0 Contract Holidays:

The Government will not be billed for holidays, except when services are required by the

Government and are performed on a holiday. The following days are contract holidays: New

Year’s Day, Birthday of Martin Luther King, Jr. (MLK Day), Washington’s Birthday

(Presidents’ Day), Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day.

Attachment 1

11.0 Associate Contract Agreement

Associate Contractor Agreements (ACA): ACA may be applicable after contract award, on any resulting task order. If determined to be applicable, the following language will be added to the resulting contract statement of work (SOW).

(a) The Contractor should enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement.

The agreements should include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the (insert name of the program or project), to ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Associate contractors are listed in (g) below.

(b) ACAs should include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and the relevant Government contracts of the associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

(c) Provide a copy of such agreement to the Contracting Officer for review before execution of the document by the cooperating contractors.

(d) The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

(e) Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement rests with the parties to the agreement, and not the Government.

(f) All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

(g) The following contractors are associate contractors with whom agreements are required: (TO

BE FILLED OUT ON EACH APPLICABLE TASK ORDER)

Contractor Address Program/Contract