Attachment 1_MATRIX Basic IDIQ SOO_FINAL.pdf

FA8650-21-S-6002

Attachment 1

Statement of Objectives (SOO)

Mission Analytics Technology & Research for Innovative eXploitation

(MATRIX)

12 Apr 2021

1.0 Background

This effort advances the overall mission of the Mission Analytics Branch (711HPW/RHWA) which is focused on conducting basic, applied, and advanced scientific and technical research to inform fundamental design principles and theories in human-machine teaming, human performance, psychological processes, and physiological indicators to enhance Airman analytic efficiency and effectiveness across a variety of mission environments. Progress must be achieved through solutions that team human analysts with automated decision support analytics to amplify their joint ability to monitor and make sense of the world beyond what either human or automation can achieve independently. By combining perspectives and principles from human factors and cognitive systems engineering with methods and technologies from data and computer science, this results in the creation and transition of innovative technology solutions that can revolutionize analytics for the warfighter in a variety of domains.

2.0 Scope

Apply cognitive systems engineering and agile software development methods to envision enhanced workflows, develop and transition rapid software prototypes, and conduct scientific research and experimentation that improves analytic reasoning, insight, and meaning-making from complex and uncertain data in a variety of operational domains. Also, apply human factors and data science principles to research foundational knowledge and constructs to develop and assess airman-centric analytics that support all mission phases in distributed, dynamic, contested, and degraded operational environments.

This effort will directly execute research & development in both the

Systems Analytics Core Research Area (CRA) and Analytic Tools Product Line (PL). Systems Analytics is one of 12 CRAs in the Airman Systems Directorate (RH) and is focused on studying the macro cognition of Airman using computational tools to achieve mission objectives, encompassing interactions between operators, analytics, and environment. The CRA is broken down into two primary challenge areas or “Big Rocks”, Analytic enabled Cognition (AeC) and Sensemaking at Scale (SaS). AeC tailors analytic capabilities to the context specific cognitive requirements of Airmen and SaS rapidly extracts meaning from complex, uncertain, multi-dimensional data sources.

The Analytic Tools Product Line is the primary mechanism to mature and transition various analysis products to external customers. Analytic Tools attempts to deliver automation and machine learning (ML) based tools to transform manual and error prone processes, manage data at scale to deal with the various complexities of war, tools to addresses multi-domain challenges and coalition warfare and novel ways to access data and defeat persisting customer identified needs.

3.0 Objectives

The objectives of this effort are to conduct basic, applied and advanced research and development in three main technical areas: Multi-Source Analytics, Joint All-Domain Systems Analytics and Machine Learning Analytics.

3.1 Multi-Source Analytics

This technical area covers the application of cognitive systems engineering concepts through airman-centered knowledge elicitation to design and envision cognitively enhanced workflows, develop rapid prototypes, and conduct scientific research and experimentation with the goal of enabling transition of innovative capabilities that improve analytic insight and reasoning of Air Force analysts. Projects under this area include, but are not limited to, Rapid Reaction Design & Development (R2D2) which develops operational prototype data analytic solutions based on various customer needs; Dynamic Wide Area Discovery & Exploration (DWADE) which evaluates patterns of cognitive work to support future wide area analysis; Meaning Making in the Information Environment (MMIE) which characterizes the Information Environment to forecast adversary threats, assesses Courses of Action and projects adversary responses, evaluates the effect of various actions and monitors vulnerability to adversary influence and Systems Analytics Assessment (SAA) which assesses and quantifies conditions under which analytics enhance or undermine cognition.

3.2 Joint All-Domain Systems Analytics

This technical area leverages human factors principles to research foundational knowledge and constructs that enable the development and assessment of airman-centric human-machine teaming capabilities to support enhanced global situation awareness and decision-making for integrated joint all-domain planning and execution in distributed, dynamic, contested and degraded operational environments. Projects under this area include, but are not limited to, Joint All-Domain Integrated Intelligence surveillance and reconnaissance (JADII) which conducts research to enable and enhance Airman-Machine teaming for distributed Joint All-Domain operations; Joint All-Domain Collection Management (JADCM) which is developing a suite of systems to support and enhance the Collection Management process through automation, M&S and advanced crowdsourcing methodologies; Sphinx, an analytical collaboration forecasting prototype that provides the ability for Priority Intelligence Requirements (PIRs) to be associated with forecasted adversary actions and assessed by analysts using probabilities of occurrence and justifications; and Kraken, an ISR feasibility engine capable of ingesting collection plans into a synthetic environment, executing full spectrum asset/sensor/target pairing with theater attributes, then providing collection plan outcome probabilities.

3.3 Machine Learning Analytics

This technical area applies machine learning, data science, signal processing, and computer science techniques to process and exploit multi-dimensional data across a variety of modalities and media types, focusing on multimodal human language technologies and topological data analysis.

Projects under this area include, but are not limited to, eXplainable Artificial Intelligence (XAI) which develops robust deep learning architectures that maintain both performance and explainability; Human Language Technologies (HLT) which performs speech and language processing research across English and multiple foreign languages and multiple modalities (e.g., video, audio, text, and images) and Applied Operational Analytics (AOA) which applies data analytics and machine learning technologies to address a variety of Air Force challenges.

3.4 Requirements

3.4.1 Knowledge Elicitation

Perform goal-directed work observation and one-on-one interviews with multiple roles and positions within a particular analytic cell at various operational sites worldwide. The main goal of the analysis is to identify and organize problems and issues that are uncovered during the interviews and observations. These knowledge elicitation and user analyses may include, but are not limited to Cognitive Task Analysis (CTA), Critical Decision Method (CDM), Knowledge Audit (KA), Envisioning Desirements (ED), Critical Events Analysis, Task Diagrams, Decision Requirement Tables, and detailed cognitive daily walkthroughs.

3.4.2 Software Development

Develop algorithms and software to implement various analysis concepts to enhance visualization and information discovery of multimodal data in a rapid prototyping environment. Utilize data analysis methods to identify correlations within data to assist analyst automation, and decision processes.

Develop web applications to create a synergistic collaborative environment to store, process, and display data among geographically separated users.

Utilize latest Application Program Interfaces (APIs) to create various visualization components. Integrate individual components into a coherent system for deployment on virtualized environments, and production servers.

3.4.3 Analytics Assessment

Investigate theoretically driven, evidence-based approaches to improving meaning making in various analytic environments. Additionally, study the macro-cognition of Airmen using various computational tools to achieve mission objectives, encompassing interactions between operators, advanced analytics, and environment.

3.4.4 Representative Assessment Environments

Develop realistic multi-domain environments, scenarios and metrics for use in the Analyst Test Bed infrastructure located at WPAFB, OH to support assessment of various analytic tools/capabilities, apply models of platforms/sensor capabilities, mission requirements, target characteristics and other capabilities for multi-domain operations.

3.4.5 Data Collection and Analysis

Perform usability analyses, general human factors evaluations, and human performance assessment of various data analytics methodologies and technologies.

3.4.6 Research Laboratories and Research Network

Provide all engineering and related efforts necessary to integrate developed software components which will enhance research goals, improve reliability, increase productivity, enhance flexibility, or improve fidelity in 711 HPW/RHWA laboratories. Prepare Certification and Accreditation packages for software baselines installed in various 711 HPW/RHWA laboratory facilities.

3.4.7 Foreign Government Collaborations

Individual task orders issued under this effort may involve collaboration with countries of the North Atlantic Treaty Organization (NATO) and other United States partnered countries. The contractor shall ensure that personnel working task orders that involve foreign government collaborations receive the appropriate briefings for managing, transmitting, storing and protecting information necessary for the successful completion of these task orders.

4.0 Data Items/Deliverables

4.1 Data Items: The contractor shall deliver data in accordance with DD Form 1423-1, Contract Data Requirements List (CDRLs) (see BAA Attachment 5). Specific CDRLs will be identified for each task order.

4.2 Software: To be specified on individual task orders as applicable.

4.3 Hardware: To be specified on individual task orders as applicable.

5.0 Management

5.1 Protection of Human Subjects

The Contractor shall comply with the provisions of the following directives/ regulations:

a) Title 32, Code of Federal Regulations, Part 219 (32 CFR 219), “Protection of Human Subjects.”

b) Department of Health and Human Services Regulations, “Protection of Human Subjects” (45 CFR Part 46), effective 14 Jul 2009, Subparts A, B, C, & D.

c) DoD Directive 3216.02, “Protection of Human Subjects and Adherence to Ethical Standards in DoD Supported Research,” (certified current as of 8 Nov 2011).

d) Air Force Instruction 40-402, 10 Sep 2014, “Protection of Human Subjects and Adherence to Ethical Standards in Air Force Supported Research.”

e) AFRL Instruction 40-402, 9 Jul 2014, “Protection of Human Subjects Research.”

Interaction with human research subjects shall not commence until approval from the Air Force IRB has been obtained. Interaction includes communication or interpersonal contact between investigator and subject for the purposes of conducting research.

If an IRB exemption is granted, then the provisions above would no longer be applicable; however, standard ethical principles should still be adhered to. Investigators should refer to, and abide by, “The Belmont Report: Ethical Principles and Guidelines for protection of Human Subjects of Research,” 18 April 1979.

5.2 Contract Holidays

The prices/costs in Section B of the contract/task order include holiday observances; accordingly, the Government shall not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. The following days are contract holidays:

(1) New Year’s Day, (2) Birthday of Martin Luther King, Jr., (3) Washington’s Birthday, (4) Memorial Day, (5) Independence Day, (6) Labor Day, (7) Columbus Day, (8) Veterans Day, (9) Thanksgiving Day, and (10) Christmas Day.

6.0 Security Requirements

The contractor shall adhere to the base security and AFRL security policies when their personnel are on base. Furthermore, the contractor will also adhere to the Security Agreement for Integrated Visitor Groups or any additional security requirements provided by the Government through the specific task order Statement of Work (SOW) or applicable documentation such as the DD Form 254, Program Protection Plans (PPPs), Security Classification Guides (SCGs), and the Operational Security (OPSEC) Plan.

6.1 Safeguarding of Unclassified Controlled Technical Information

(UCTI)

Contract personnel shall be capable of accessing, handling, marking, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of Controlled Unclassified Information (CUI). The contractor shall submit all CUI by a controlled means using USPS mail, Safe Access File Exchange (SAFE) website, and/or FIPS 140-2 validated encryption software such as https://spi.dod.mil/ewizard.htm.

The contractor, and its task order subcontractors (if applicable), must encrypt all emails containing technical data or other critical information for this program. AFRL program information is not approved for public release, social media, and/or use in advertisement or public website posts without approval from the task order manager, 711 HPW security and the AFRL Public Affairs office. The requirements for safeguarding UCTI will apply to all task orders issued under the MATRIX contract and apply to any task order subcontractors.

6.2 Operations Security (OPSEC)

The contractor shall provide OPSEC protection for all sensitive/critical information and indicators involved in execution of this contract, as defined by AFI 10-701 (Operations Security). 711 HPW Critical Information and Indicators are protected under the 711 HPW Operations Security Program and the 711 HPW Critical Information and Indicators List (CIIL). Contractor employees granted access to critical information and indicators will be provided initial OPSEC training by the 711 HPW OPSEC Coordinator upon in-processing and prior to being granted access to CIIL items related to the contractor. The contractor will also participate in 711 HPW’s annual OPSEC training and education programs, which includes periodic updates and refresher training on CIIL items applicable to the contractor. The 711 HPW OPSEC coordinator will evaluate the OPSEC posture of AF contract activities and operations.

All contractor personnel require a minimum of a Tier 1 background check (T1)/SF85 for any position that requires access to the internet, use of automated information systems to cover standalone computers or unescorted entry into restricted or controlled areas prior to reporting for duty in support of any requirement. The investigation is not for a security clearance; it is for a position of trust. This is a mandatory requirement set forth in DoDM 5200.02_AFMAN 16-1405, Air Force Personnel Security Program. All documentation required for security certification shall be the responsibility of the contractor.

6.3 Safeguarding Export Controlled Information

The contractor shall not export technical data with military application without an approval, authorization, or license under the Arms Export Control Act, as amended 22 U.S.C. 2751-2794, including the International Traffic in Arms Regulation (ITAR), 22 C.F.R. 120 et seq.; and the Export Administration Act of 1979, 50 U.S.C app. 2401-2420. The contractor shall use the Militarily Critical Technologies List (MCTL) as general guidance for the purposes of making this determination.

An export license is require before assigning any foreign source to perform work under this agreement and before granting access to foreign persons to any equipment and technical data generated or delivered during performance (see 22 C.F.R Section 125).

The requirements for safeguarding Export Controlled Information will apply to all task orders issued under the MATRIX contract and apply to any task order subcontractors. All documents determined to contain export controlled technical data will be marked with the following notice:

WARNING: - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., App. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

6.4 Information Security and Force Protection

The contractor shall provide Information Security and Force Protection training as defined by AFI 16-1404 (Air Force Information Security Program) and AFI 10-245 (Air Force Antiterrorism Standards). The contractor shall participate in the 711 HPW sustained information Security and Force Protection/Antiterrorism training or include this training as part of their on-going security program. The 711HPW Security Managers will evaluate the training posture of AF contract activities and operations. This requirement is set forth in AFI 16-1404, AFI 10-245 and applicable AFMC and local supplements. Information Security and Force Protection requirements will apply to all task orders issued under this contract.

6.5 Common Access Card (CAC) Requirement

Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology networks in connection with the work on this contract must be U.S. citizens and have at least a favorable T1 investigation. Possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

6.6 Security Clearances

The Contractor shall maintain a U.S. Facility Clearance of Top Secret.

Moreover, based on the individual task order requirements, it is foreseen that certain contractor employees will be required to have or obtain a Tier 5 Critical-Sensitive or Special-Sensitive investigation in order to grant them access to TS or TS/SCI information. Onsite contractor personnel must have an active clearance or Interim access at/or above the level of classified information access required on the specific task order. Interim clearances for newly hired personnel shall be processed as expeditiously as possible since some contractor personnel will be required to utilize the SIPRNET and process classified materials; however this will be on a case-by-case basis.

Such clearance must be obtained through the Defense Investigative Services.

Contractor personnel who already have approved security clearances are highly preferred. The contractor shall be required to wear contractor identification badges and maintain currency in all Privacy Act Laws. If subcontractors are needed to perform classified work, the contractor will notify the Program Manager responsible for that task order 15 days prior to any agreement. Furthermore, if subcontractors are required to perform classified work on a task order, the contractor shall submit a signed copy of the subcontracted DD Form 254 to the Government Contracting Officer and task order manager within 30 calendar days of establishment of the contract or agreement.

6.7 Disposition of Classified Material and Access

Once a task order has completed, the contractor and, if applicable, any task order subcontractors, shall account for all classified hardware and material given, used, or generated during the task order period of performance. If the classified hardware or material will not be used on another task order under this contract, the contractor will submit an encrypted, unclassified list of all materials and/or hardware in their possession to the Government Contracting Officer. In the list of items, the contractor shall outline those items they wish to keep and the corresponding justification. The Government Contracting Officer and the 711th Industrial Security Manager will determine if the material will be destroyed, transferred or returned back to the Government.

At the end of this contract, the same requirement above applies.

However, if there is a follow on effort to this contract, a final DD form 254 must be issued to the contractor authorizing the contractor to retain the classified material, access, hardware for a specified time period until the follow-on contract is awarded and the material, access, information etc. is transferred to that new effort.