Atch 1 IDIQ ICET SOO FINAL.pdf

FA8650-20-S-1958

TEMPEST ARA Call 01 Attachment 1

Indefinite Delivery/Indefinite Quantity

(IDIQ)

Statement of Objectives (SOO) For The

Integrated Demonstrations and Applications Laboratory (IDAL) Cognitive Enabling Technologies

(ICET)

09 December 2019

ICET

Integrated Demonstrations and Applications Laboratory Cognitive Enabling Technologies

1.0 INTRODUCTION/BACKGROUND

The increasing complexity and sophistication of enemy threat systems, coupled with an uncertain and rapidly changing threat environment, place serious demands upon the capabilities of USAF air and space systems. In spite of recent reductions in budget and force structure, the requirement remains to ensure a high level of mission completion and high survivability of USAF platforms, while simultaneously fighting on multiple fronts. For decades, DoD war plans focused on countering conventional military threats. New planning scenarios focus on preparing for a wider range of contingencies which require capabilities to address irregular, catastrophic and disruptive challenges while sustaining capabilities to address traditional challenges.

Recently released, the Department of Defense’s (DoD) Artificial Intelligence (AI) Strategy directs the DoD to accelerate the adoption of AI and the creation of a force fit for our time. AI is rapidly changing a wide range of businesses and industries. It is also poised to change the character of the future battlefield and the pace of threats we must face. In that regard, the capability to confront threats which may incorporate AI must be considered during testing and analysis of the performance our systems present. This effort must undertake this endeavor to be prepared for this type of threat.

The 21st Century Aerospace Force is becoming increasingly network-centric by leveraging revolutionary System of Systems (SoS) information concepts and technologies. In the past, warfighters were limited to platform-centric concepts and tactics. The evolving capability-based SoS Aerospace Force demands continuous situational assessments (threat and friendly), fused with threat/target data from both on- and off- board systems and continuous sensor network data exchanges to accomplish the mission. The combat battlefield is rapidly moving from platform-centric to network-centric warfare where missions are accomplished through capability-based layered sensing approaches that utilize multiple platforms, multiple sensors and real-time information exchanges. These new challenges have resulted in a Layered Sensing vision which requires the development/evaluation of advanced distributed sensor technologies. Current and future conflicts will utilize complex layered sensing “system of systems” concepts involving integrated sensor/electronic warfare (EW) technologies to accomplish combat missions.

Open air range testing of current and advanced sensor and electronic warfare (EW) technologies /capabilities are both time-consuming and cost-prohibitive. Open air ranges cannot generate the dense RF signal environments that would be experienced in actual real world situations such as military combat scenarios. Open air range productivity is low due to the fact that there are so many uncontrolled variables and the inability to make changes during the actual flight test.

Hardware-in-the-loop simulation is the most cost-effective methodology for maturing advanced sensor technologies because the battlefield can be brought to the laboratory through synthetic battlespace simulation. Synthetic battlespace simulation provides precise control of test conditions which enable the advanced sensor technologies to be subjected to multiple realistic combat situations making it possible to identify/resolve technology issues before ever flying or fielding the capability. It is a critical step that significantly reduces the time, risk, and especially cost associated with transitioning advanced sensor technologies.

The Sensors Directorate Integrated Demonstrations and Applications Laboratory (IDAL) conducts sensor applications research through synthetic battlespace simulation that integrates sensor/electronic combat technologies to meet urgent warfighter mission requirements. IDAL also conducts electromagnetic compatibility research (EMC) to resolve interoperability issues involving both military and commercial-off-the-shelf (COTS) equipment.

IDAL is a quick reaction capability (QRC) for rapidly developing, integrating, maturing, demonstrating, inserting and transitioning advanced “system of systems” layered sensing technologies. IDAL conducts collaborative partnerships that involve all phases of weapon system acquisition such as S&T research, system development/production/sustainment and operational assessments and deployments. IDAL conducts the collaborative partnerships through the government/contractor Integrated Product Team (IPT) process.

IDAL is a state-of-the-art classified research capability within Building 620, Sensors Directorate, Air Force Research Laboratory, Wright-Patterson AFB OH. IDAL consists of separated facilities within Bldg 620 involving a main classified vault, classified vault annexes and an EMC research facility. IDAL provides a hardware-in-the-loop capability that simulates threat targets/systems and scenarios to provide combat engagements in realistic multi-spectral synthetic battlespaces with man-in-the-loop control. IDAL supports both open-loop and closed-loop evaluations by providing a reconfigurable hardware/software simulator capability for conducting hardware-in-the-loop sensor technology demonstrations.

IDAL conducts sensor applications research and operational assessments through IDAL multi-spectral synthetic battlespace simulation capabilities such as the Dynamic Electromagnetic Environment Simulator (DEES), Micro-DEES, Combat Electromagnetic Environment Simulator (CEESIM), Electronic Defense Evaluator (EDE), Wideband Verification Instrumentation System (WBVIS), Broadband Signal Analyzer and Generator (BSAG), Advanced Signal Analysis Processor (ASAP), special test equipment, EMC Lab and operational test-beds.

2.0 SCOPE

Integrated Demonstrations and Applications Laboratory Cognitive Enabling Technologies (ICET) program provides the IDAL simulation and testbed capabilities required to rapidly develop, integrate, mature, insert and transition technologies/systems to meet critical/urgent warfighter mission requirements. The program involves phases of S&T research (6.3, 6.4, 6.5 & 6.7), weapon system development/production/sustainment and operational assessments /deployments through participation in collaborative partnerships. The program modifies, upgrades, develops, integrates, implements and maintains IDAL threat scenarios, digital simulations, hardware- in-the-loop simulators and technology/system/operational test-beds. The program utilizes IDAL threat scenarios, digital simulations, hardware-in-the-loop simulators and technology/system/operational test-beds to perform collaborative partnerships that involve areas such as applications research, operational assessments/verifications, production assessments/verifications and operational deployment modifications/verifications.

3.0 Technical Areas of Interests and Tasks

The contractor shall involve the Air Force Research Laboratory (AFRL) Project Engineer in all phases of weapon system acquisition such as Science & Technology (S&T) research (6.3, 6.4, 6.5, 6.7), weapon system development, production, sustainment and operational assessments and deployments. The contractor shall participate in the government-contractor Integrated Product Team (IPT).

3.1 Technical Areas of Interest 1: Technologies for Modeling and Simulation and to Advance RF Simulation

3.1.1 Task 1: Design, Develop and Evaluate High Fidelity Models The contractor shall develop the digital models required to assess technology and capability performance and to generate synthetic battlespace. Implementation of autonomous mode capability to emulate “cognitive” behaviors must be considered during the model development.

The contractor shall integrate the digital models into the IDAL simulation environment. The contractor shall develop, implement and document digital models in accordance with the specific task orders.

3.1.2 Task 2: Radio Frequency Synthetic Battlespace Simulation and Generation The contractor shall define, implement and verify threat scenarios required for IDAL synthetic battlespace generation. The contractor shall use threat data from intelligence products such as the Electronic Warfare Integrated Reprogramming Database and the MSFD. The contractor shall translate and integrate threat data into IDAL simulator formats and into the IDAL threat scenario library. Special attention should be given to threat data which have a high degree of adaptability which may indicate use of “cognitive” algorithms in use by the threat system. The contractor shall define, implement, verify and document threat scenarios in accordance with the specific task orders.

3.2 Technical Areas of Interest 2: Techniques, Methods and Technologies for Measuring Sensor System Performance

3.2.1 Task 3: Develop Integrated Evaluation Methods

The contractor shall develop the test-bed capabilities required to assess technology and capability performance and for synthetic battlespace generation. The contractor shall integrate the test-bed capabilities into the IDAL simulation environment. The contractor shall develop, implement and document test-beds in accordance with the specific task orders. The contractor shall conduct IDAL synthetic battlespace simulation demonstrations to integrate and mature technology and system capabilities. The contractor shall conduct application demonstrations utilizing the IDAL simulation environment. The contractor shall conduct technology, system and capability demonstrations in accordance with the specific task orders.

3.2.2 Task 4: Operational Technology Demonstrations and Assessments (3400) The contractor shall conduct operational assessments through IDAL synthetic battlespace simulation to establish, baseline and optimize operation performance. The contractor shall conduct operational assessments through Electromagnetic Compatibility (EMC) measurements to establish, baseline and optimize EMC interoperability. The contractor shall conduct operational assessments utilizing the IDAL simulation environment and EMC Lab capabilities.

The contractor shall conduct operational assessments in accordance with the specific task orders

3.2.2.1 Develop and Operate Research Networks and Platforms

The contractor shall provide qualified personnel to perform maintenance and operations activities, incidental to the research, required to conduct battlespace simulations to meet time and schedule requirements. The contractor shall develop the hardware-in-the-loop simulators required for synthetic battlespace generation. The contractor shall integrate the simulators into the IDAL simulation environment. The contractor shall develop, implement and document hardware-in-the-loop simulators in accordance with the specific task orders.

3.2.3 Task 5: Production Verifications (3010)

Perform production verification of production systems and capabilities through IDAL multispectral synthetic battlespace simulation. The contractor shall produce production verification simulators that shall be utilized to perform production line verification and deployed operational system and capability verification

3.3 Task 6: Special Projects

The contractor shall conduct special projects which do not logically fall within any of the previously defined task areas. These special projects typically involve aspects or parts of several of the previously defined task areas. These special projects involve urgent quick reaction capability needs that have critical performance, schedule and special security requirements. The contractor shall define and implement a flexible task order accomplishment methodology and plan that shall address the critical needs and account for the special security requirements.

4.0 PROGRAM MANAGEMENT

The contractor shall manage technical, schedule, and cost satisfaction of the program; plan, prepare, conduct, and document reviews; track CDRL satisfaction; and interface with the customer to assess performance satisfaction and re-plan the project as needed.

5.0 PERIOD OF PERFORMANCE

Basic IDIQ: 84 month overall period of performance (PoP) with 60 month ordering period.

6.0 DELIVERABLES

The contractor shall provide deliverables on a task order basis such as final reports, software, hardware and data items.

7.0 SECURITY

7.1 Program Security Requirements:

Individuals must be US citizens and may be required to have SCI DCID 6/4 Top Secret Eligibility based on a SSBI/SBPR to work classified efforts. Work will be required to be conducted within an accredited Special Access Program Facility (SAPF) and/or a Sensitive Compartmented Information Facility (SCIF). Specific security details and requirements will be outlined within future task orders. All classified efforts must be in compliance with the National Industrial Security Program Operating Manual (NISPOM). Other regulations/policy that may apply to this contract are JAFAN 6/0 (Revision 1); SAF/AAZ Memorandum “Air Force Special Access Programs Nomination Process (SAPNP)” (30 Sep 2013); USD(I) Memorandum, Special Access Programs Nomination Process (20 May 2013); the DoD Manual 5205.07, Volume 4 (10 Oct 2013); “Special Access Program (SAP) Security Manual”:

Marking; SAF/AAZ Implementation Memorandum (7 Nov 2013); United States Air Force Security Marking Guide for SAPs (17 Jul 2011) and Revision 1 (16 Oct 2013); DoD SAPCO Memorandum, JAFAN 6/9 (23 Mar 04), Change 1 (20 Dec 05) and JAFAN 6/3 (15 Oct 2004);

JAFAN 6/3 Implementation Guide, Version 1 (Sep 2006); DoD SAPCO Memorandum, Transition to the Risk Management Framework (RMF) (18 Dec 2013); Joint Special Access Program Implementation Guide (JSIG) (9 Oct 2013); DoD 8570.1-M, Information Assurance Workforce Improvement Program (24 Jan 2012 – incorporating Change 3); Intelligence Community Directives (ICD) 704 and 705; other applicable SCI regulations/policy; other applicable Security Classification Guides (SCG); and other applicable regulations/policy and subsequent revisions.

Provide the following information with proposal submission: CAGE Code, Organization Name, and Security Point of Contract (name/phone number).

The contractor shall implement the security program required to accomplish this effort. The contractor shall provide personnel with sufficient security clearance levels to be allowed access to the data necessary to execute the task order efforts. The contractor shall provide the secure facilities necessary to process the data generated under this task. The contractor shall have the ability to handle and store unclassified, proprietary, and classified information to perform this activity. The contractor shall 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. The contractor shall ensure appropriate security protection methods are in place commensurate with the security level of the material provided to the contractor and generated by the contractor for performance of this effort. The contractor shall 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. The contractor shall provide weekly/monthly status/progress reviews against the IDAL ICET security action plan baseline. The contractor shall coordinate security requirements/activities with the ICET project engineer and the IDAL program manager.

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

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

3.3 Task 6: Special Projects

8.0 SAFETY