Attachment 2 - Task Order 0001 SOO.pdf

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

DISTRIBUTION STATEMENT A.

Attachment 2

Statement of Objectives (SOO)

Task Order 0001 – Andromeda

SCIENCE AND TECHNOLOGY APPLIED RF SYSTEMS (STARS)

07 March 2024

1. Background

The focus of research for this effort is to develop advanced radio frequency (RF) capabilities specifically addressing challenges unique to Air Force Operational Concepts and in turn the

Operational Imperatives by leveraging emerging commercial and government developed RF sensor and RF sensor signal processing technologies. These technologies will be integrated to provide a variety of sensing solutions across multiple RF sensing research areas.

Over the past several years, AFRL/RY has developed multiple prototype codebases and datasets establishing a baseline for advancement via the STARS IDIQ objectives. These include predominately unlimited rights/ Government purpose rights (UL/GPR) codebases built upon

MATLAB and Python as well as complementary codebases developed by other communities.

Additionally, a significant amount of data suitable for addressing a subset of STARS objectives has been collected via experimental data collections.

2. Objective

The objective of this task includes designing and implementing a digital development environment that supports advanced RF sensing capabilities by leveraging emerging commercial and government developed RF sensor and RF sensor signal processing technologies. This task order will serve as a baseline effort for all follow-on task orders under STARS. Utilizing the provided Government furnished software and information, a framework will be developed in which all future task orders will stem from.

Develop plans for conducting software quality assurance throughout development efforts, establishing continuous transitioning of algorithms/tools to Government development environments, performing security testing on all software, implementing testing, maintain configuration control, delivery, documentation and packaging, and develop and deliver training and associated documentation.

3. Tasks

These research objectives aim to develop a system design, develop and support preliminary demonstrations of a working prototype, and deliver a validation plan.

3.1. Software Integration Digital Laboratory (STARS IDIQ SOO 3.1, 3.2)

The objective of this research includes creating a system design based on the

Government-provided list of software (see 4.5) as well as any proposed alternatives or future concepts followed by the creation of an architecture and continuous integration stack realizing this design.

3.1.1. Develop a processing stack design that incorporates government provided RF signal processing libraries as well as any proposed alternatives or future concepts. Illustrate interfaces between sub-components including potential separation of functionality/responsibility, data formats/ application programming interfaces (APIs), and resulting capabilities. Incorporate considerations for processing chains that leverage measured RF data, simulated RF data and processing techniques. Incorporate considerations for mission and flight test planning and performance prediction capabilities.

3.1.2. Develop a development stack design that facilitates the processing stack (e.g., compatible across software languages and security environments) including high level language development (e.g. MATLAB, Python), real-time processing (e.g. Rust/Go) and containerization (e.g. Docker, Singularity). Include considerations and risk mitigations for limited connectivity environments. Work with AFRL/RY stakeholders to incorporate considerations and risk mitigations for OPSEC restrictions.

3.2. Signal Processing and Analysis (STARS IDIQ SOO 3.1, 3.2)

The objective of this research is to validate the Software Integration Digital Laboratory functionality, capabilities, and ensure compatibility with government environments.

Relevant details such as run-time, resources utilized by the hardware, and any software dependencies that will be utilized to track development.

3.2.1. Design at least one relevant prototype RF signal processing algorithm using the Software

Integration Digital Laboratory. Apply the algorithm to government provided data sets and assess with provided tool chains as appropriate.

3.2.2. Exercise government provided toolchains and proposed alternatives applied to government provided datasets. Assess code and solution space coverage. Analyze the outputs of the Software Integration Digital Laboratory with respect to provided example outputs.

3.3. Configuration Control (STARS IDIQ 4.3)

The objective of this research is to design Configuration Control solutions, especially with respect to the Software Integration Digital Laboratory such that continuous transition of development activities can be executed to government environments.

3.3.1. Design a configuration management plan (CMP) that incorporates modern continuous integration/continuous deployment (CI/CD) concepts tailored to STARS objectives.

Approaches should include considerations for security to realize a complete

“DevSecOps” capability. Solutions are desired that facilitate both stable deliveries

(intended for end users of STARS technologies) as well as developmental deliveries

(intended for AFRL/RY collaborators willing to accept experimental features and capabilities and the commensurate immaturity and risks in order to facilitate collaborative development).

3.4. Releasability:

The contractor shall properly mark the security classification of all deliverables, including the status of international releasability. The contractor shall ensure all modified software is releasable to relevant international partners, and the software has been properly reviewed for releasability. The contractor will ensure they are familiar with relevant science and technology protection plans/guides, which will be provided by the government, and that they will conduct research and development in accordance with those guides.

4. Program Management

This effort shall execute in accordance with General Objectives (4.0) and Management (5.0, excluding 5.6) objectives identified in the STARS IDIQ SOO.

4.1. Deliverables

The Government desires all data, models, and software developed and acquired under this effort to be delivered without restriction as to their use or future distribution, unless subject to licensing restriction imposed by a third party. The Government desires that the contractor acquire software, models, and data with unrestricted rights/licensing as directed by the Government whenever possible and shall assist as needed in making the cost/benefit tradeoffs associated with acquiring said rights/licensing. All software, models, and data developed under this contract shall be delivered to the Government with unlimited rights.

4.1.1. Data Items: The contractor shall deliver in accordance with the following Contract Data

Requirement List (CDRL).

4.1.2. Software: Deliver all software developed/procured under this contract to include prototype software, executable and source code.

4.2. Government Furnished Software and Information

The Government anticipates the purchase of software may be required during the period of performance for this effort. The list of anticipated software below is provided for planning purposes only and is subject to change due to mission requirements. The software shall be included as part of the contractor’s cost proposal. Any additional software required to complete the above objectives shall be included as part of the contractor’s overall technical approach and cost proposal.

4.2.1. Software anticipated to be provided or currently used by the Government under STARS:

• AFSIM - “Advanced Framework for Simulation, Integration and Modeling” is a powerful, flexible software simulation tool for use in research and development (R&D), operations analysis, and experimentation communities. The software covers domains from sub-surface to space and can be used to assess how military systems function throughout the course of a mission. AFSIM is available via an Information Transfer

Agreement. AFSIM will serve as the baseline for mission level analysis.

• ABACUS – AFRL developed MATLAB based parametric analysis tool for RF collection analysis developed by AFRL with Unlimited Rights. ABACUS facilitates analysis over a field of regard (e.g. signal-to-noise ratio (SNR) over a scene of interest). ABACUS can serve as the back end of mission level analysis such as AFSIM by requesting points of

Table 1: Contract Data Requirements List

A001 Scientific and Technical Reports DI-MISC-80711A/T

A002 Funds and Man-Hour Expenditure Report DI-FNCL-80331A/T

A005 Status Report DI-MGMT-80368A/T

A007 Presentation Material DI-ADMIN-81373/T

A011 Software Test Plan DI-IPSC-81438A/T

A012 Software Design Description DI-IPSC-81435A/T

A014 Computer Software Product DI-IPSC-81488/T

A015 Data Accession List DI-MGMT-81453A/T

A017 Report, Record of Meeting/Minutes DI-ADMN-81505/T

A018 Certificate of Services Technical Assistance Activity Report DI-MGMT-80910/T

A019 Contract Work Breakdown Structure DI-MGMT-81334D/T

A021 Interface Design Description DI-IPSC-81436A/T

A022 Software Version Description DI-IPSC-81442A/T

A023 Software User Manual DI-IPSC-81443A/T interest rather than scene extents. ABACUS will serve as the baseline for parametric analysis of RF systems and scenarios.

• AFRLMAT – AFRL developed MATLAB based RF signal processing library including

RF pre-processing, synthetic aperture radar (SAR), and moving target indication (MTI) algorithms.

• Data Release Scripts – A set of MATLAB and Python scripts designed to facilitate data conversion and preparation for release to broad audiences.

• DRSLAM – AFRL developed MATLAB and C/C++ based RF signal level modeling and simulation capabilities. DRSLAM provides a myriad of capabilities including but not limited to simulating transmit RF system performance (e.g. antenna pattern, power levels, transmit waveform bandwidth and modulation) interaction with scenes (general clutter, scene specific clutter, targets, etc) and receive RF system performance.

• NGA SAR Toolbox – Publicly available MATLAB based SAR processing toolbox including APIs for accessing government reference data standards and example processing algorithms.

• NGA SarPy – Publicly available Python based SAR processing toolbox including APIs for accessing government data standards and example processing algorithms.

• Spyglass – AFRL developed tool for quickly assessing received signals

• Tracker Component Library – Publicly available MATLAB library containing many features focused on tracker development

4.2.2. Data sets anticipated to be provided by the Government under STARS:

• Distributed RF Data Collection (DRDC) – Data collection completed in 2022 that contains monostatic (single co-located transmitter and receiver), bistatic (separated transmitter and receiver), and multistatic (multiple sets of separated transmitters and receivers) data sets. Data is generally available in sensor specific formats, select data is available pre-processed in to CRSD format. Toolchains for converting to compensated receive signal data (CRSD) format are included in AFRLMAT

• Monostatic RF Data Collection – A myriad of monostatic data collections are anticipated to be made available including experimental (e.g. GOTCHA) as well as operational.

5. Operational Security – OPSEC

The contractor shall have a sufficient number of personnel that meet security, experience, Attachment 2 and educational requirements specified for this effort and the overall STARS Contract for the labor category requested.

General Operations Security (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

CIL and RY’s OPSEC Plan as it pertains to their contract. The contractor shall apply OPSEC in the management of their current program IAW AFI 10-701 Operations Security and

WPAFB Supplement to AFI-10-701.

6. Science and Technology (S&T) Protection

6.1. S&T Protection Plan Requirement: The Contractor shall support the USG in the planning, development, and implementation of the S&T Protection Plan, 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.

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

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

Attachment 2

(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