Atch 2 TO 01 ICET SOO FINAL.pdf

FA8650-20-S-1958

TEMPEST ARA Call 01 Attachment 2

TASK ORDER 0001

STATEMENT OF OBJECTIVES (SOO)

Technologies for Advanced RF Simulation

(TARFS)

For the

IDAL Cognitive Enabling Technologies

(ICET)

09 December 2019

1.0 OBJECTIVE

The objective of this task order is to develop, implement, and use simulation capabilities required to conduct Integrated Demonstrations and Applications Laboratory (IDAL) multi-spectral synthetic battlespace simulations. Accomplishing this goal requires research into areas such as digital models, man/hardware-in-the-loop simulators, sensor testbeds, simulation capability integration and verification/validation of IDAL RF battlespace simulation integrated capabilities.

Recent advances in simulation technologies include increased instantaneous bandwidth, improved waveform fidelity, and expanded dynamic range. Laboratory evaluations of new radar frequency (RF) sensors drive the incorporation of these on-going advances into battlespace simulators. The IDAL synthetic battlespace simulation and generation capabilities will be used to conduct sensor technology applications research in order to transition sensors, information processing and simulation technologies to meet warfighter requirements. This task integrates technology by conducting advanced technology demonstrations and system level evaluations.

The efforts supported by this task involve time critical milestones and complex leading-edge technologies for Department of Defense (DoD) weapon system and Foreign Military Sales (FMS) programs.

2.0 SCOPE

The TARFS Task Order provides the IDAL simulation and testbed functions required to rapidly develop, integrate, mature, transfer and transition technologies and systems to meet critical warfighter mission requirements. TARFS modifies, upgrades, develops, integrates, implements and maintains IDAL threat scenarios, digital simulations, man/hardware-in-the-loop simulators and technology demonstrator test-beds. The task uses threat scenarios, digital simulations, man/hardware-in-the-loop simulators and technology/system/operational testbeds to perform collaborative partnerships.

3.0 TASKS AND TECHNICAL REQUIREMENTS

3.1. Task 1: Design, Develop and Evaluate High Fidelity Models

3.1.2. Sub Task 1.1: IDAL Threat Analyses

Conduct threat performance analyses needed to define and implement modifications and upgrades to digital models, simulators and testbeds to faithfully represent synthetic battlespaces. Performance analysis includes active participation in threat working groups, intelligence conferences, and exploitation exercises. Access to highly classified threat intelligence is expected.

3.2. Task 2. Radio Frequency Synthetic Battlespace Simulation and Generations

3.2.1. Sub Task 2.1: IDAL Simulation Requirements

Define IDAL simulation requirements for synthetic battlespace generation to demonstrate and assess sensor technologies, integrated systems, and novel sensor capabilities

3.2.2. Sub Task 2.2: Synthetic Battlespace Simulations

Define and construct IDAL synthetic battlespace simulations required to integrate, develop and transition sensor technologies and capabilities.

3.2.3. Sub Task 2.3: IDAL Simulator Modifications and Upgrades

Define, develop, and implement modifications and upgrades to the IDAL simulators and testbeds. These modifications and upgrades are required to generate dense, high-fidelity simulations of background signals, threats and threat scenarios.

3.3. Task 3: Develop and Operate Research Networks and Platforms

3.3.1. Sub Task 3.1: IDAL Simulator Maintenance and Operation

Perform necessary IDAL maintenance and operation required to enable IDAL Program Managers to conduct synthetic battlespace simulations within required timeframes per RY Operating Instruction 21-101 (Logistics/Maintenance Support Processes) and AFRLI 21-101 (Logistics Maintenance Management). This task is incidental to the research to be performed.

3.4. Task 4: Operational Technology Demonstrations and Assessments

3.4.1. Sub Task 4.1: Electromagnetic Compatibility (EMC) Interoperability Research

Perform EMC interoperability research to define and determine EMC interoperability performance and to identify and resolve EMC interoperability issues. Use, modify, or upgrade the EMC measurement capability, as required, to conduct EMC interoperability research.

4.0 PROGRAM MANAGEMENT

The contractor shall manage technical, schedule, and cost performance of the work; plan, prepare, conduct, and document reviews; track Contract Data Requirements List (CDRL) completion; and interface with the customer to assess performance progress and re-plan the project as needed.

5.0 PERIOD OF PERFORMANCE

The technical effort shall be 30 months, with three additional months allotted for completion of the final report for a total of 33 months.

6.0 DELIVERABLES

Deliver data in accordance with DD 1423-1 Contract Data Requirements List, dated 21 November 2019. The contractor may propose additional deliverables as appropriate to the task order.

7.0 CONTRACT HOLIDAYS

The Government will not be billed for holidays, except when services are required by the Government and are actually performed on a holiday.

The following days are contract holidays: New Year’s Day, Martin Luther King, Jr. Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, and Christmas Day.

8.0 SECURITY

8.1 Program Security Requirements:

See DD Form 254, Department of Defense Contract Security Classification Specification.

Implement the security program required to accomplish this effort. Provide personnel with sufficient security clearance levels to be allowed access to the data necessary to execute the task order efforts. Provide the secure facilities necessary to process the data generated under this task. Properly handle and store unclassified, proprietary, and classified information. Provide the security required to perform this effort and shall implement special security requirements in accordance with classified attachments provided through government special project channels.

Ensure appropriate security protection methods are in place commensurate with the security level of the material provided and generated for performance of this effort. Develop/implement an IDAL ICET security action plan that provides measurable work tasks and schedule milestones to accomplish IDAL ICET security objectives/requirements on a timely basis. Provide weekly/monthly status/progress reviews against the IDAL ICET security action plan baseline.

Coordinate security requirements/activities with the ICET project engineer and the IDAL program manager.

8.2 General Operations Security (OPSEC):

General Operations Security (OPSEC) procedures, policies and awareness are required in an effort 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 Information List (CIL) and the RY OPSEC Plan will be provided upon request by AFRL/ RYOY Information Protection Office. While working on the government installation, OPSEC guidance and OPSEC training will be provided by AFRL/RYOY 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 their management of their current program IAW AFI 10-701 Operations Security and WPAFB Supplement to AFI-10-701.

8.3 Program Protection Plan:

All DoD contractors (including subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract where critical program information (CPI) has been identified to protect the CPI to the standards articulated in the Program Protection Plan and in accordance with DoDI 5200.39. Upon contract award, all identified DoD contractors (including subcontractors) shall acknowledge and meet the requirements stated by the Program Manager for the protection of CPI. The DoD contractor must immediately notify the U.S. Government upon the discovery of any nonconformance with CPI protection.

8.4 Safety:

All contractor personnel who are delegated authority for opening the secure areas are also authorized to close; perform end-of-day security checks of the area (including doors, safes, security codes and combination locks) during normal and extended duty day; and set the alarms.

They are also responsible for after-hours alarm response in accordance with AF and DoD requirements.

The contractor must comply with all federal, state, and local safety and environmental regulations. Requires an approved Safety Plan IAW AFI 91-202 AFRL Supplement 1 before any experiment may be conducted. The contractor must comply with all Air Force safety and environmental regulations.

The contractor must comply with system safety requirements contained in MIL-STD 882D, Section 4 “General Requirements,” for any deliverable systems or hardware. The contractor must identify safety-critical components of those systems or hardware, and software interfaces with those components. The contractor must test and verify the safety-critical hardware and software for safety acceptance.