ICS Attach 1 -- SOO -- 10Dec19 (Final).pdf

STATEMENT OF OBJECTIVES

Advanced Development for Enhanced Performance Technologies (ADEPT)

Advanced Research Announcement (ARA) Call 1:

Integrated Cockpit Sensing (ICS)

10 Dec 2019

1.0 BACKGROUND

The purpose of the ADEPT ARA effort is to develop, mature, validate, and ultimately transition technologies fostered under the 711 HPW/RHB "Sensing and Assessment" product line, providing Airmen with physiological and cognitive performance sustainment and enhancement systems, personalized to the individual Airman, and appropriate for use in operational Air Force environments. This first Call of the ARA is to develop integrated technology platforms to address unexplained physiological events (UPEs) affecting aircrews of multiple Department of Defense (DoD) aircraft.

The DoD has ongoing concerns regarding physiological events affecting pilots of training, fighter, and attack aircraft, with both the USAF and USN grounding aircraft and expending considerable resources in search of root causes and solutions.

Ongoing research and development (R&D) efforts are seeking to improve the basic scientific understanding of physiological performance in these environments, along with efforts to develop physiological sensors that are effective in the cockpit for assessing pilot state and detecting conditions conducive to UPEs. Cockpit sensing remains a key gap, as there are no fielded solutions to provide data for root cause analysis, which in turn could drive pilot decision making as well as resource prioritization for life support systems modification.

2.0 SCOPE

The objective of the ADEPT ARA Call 1 ICS project is to experiment, develop, prototype, and demonstrate a prototype integrated sensor suite capability for effective cockpit sensing, including pilot physiology and cockpit environments (i.e., breathing gas). Work in Call 1 ICS will focus on a "stand-alone" ICS capability (i.e., an ICS system not connected to aircraft power or data feeds).

At close of research, experimentation and development the prototype ICS stand-alone system is expected to be at Technology Readiness Level (TRL) 7 (system prototype demonstration in an operational environment) and be ready for transition to platform program offices for acquisition.

3.0 TASKS / TECHNICAL AREAS / OBJECTIVES

Under this Call, 711 HPW/RHB will be procuring research, experimentation, development, and testing of five (5) copies of a complete prototype ICS system (common configuration). The five prototype systems, and related supporting hardware (including CAP), software, and documentation shall be delivered to the Government at the end of this effort. The Contractor shall propose a Technical Data Package (reference CLIN 0004 and CDRL A010). The work under this Call will be implemented through Cost Plus Fixed Fee (CPFF) or other cost-reimbursement contracts, or through Other Transactions (OT) for Experimentation (reference 10 USC 2373). If a CPFF or Cost type contract is awarded, the Technical Data Package CLIN, CLIN 0004, will be incorporated as a FFP CLIN. This Call has five technical objectives, with related tasks, as follows.

3.1 Data Collections and Data Analysis. The Contractor shall develop, plan, and execute research and experimentation in the domain area per the advanced development goals, which includes the following: prototype software development and testing; collection and analysis of physiological, behavioral, and environmental data; application of digital signal processing methods; analysis using algorithms, modeling and simulations; conducting literature searches; recruiting and screening participants; development and execution of experimental plans; reporting results; and conducting record keeping for experiments. Utilize best practices and knowledge of experimental methodologies to maintain a high level of research integrity.

Conduct descriptive and inferential statistical analyses using the collected data. Verify the integrity and accuracy of the data collection and analysis capabilities. Develop a method to ensure “sanitization” of data or software being brought into and out of the facility. Data collection in field conditions will be required.

3.2 Advanced Development. The Contractor shall integrate, validate, and demonstrate prototype integrated sensor systems (composed of already-existing Government-owned or commercial technologies), assessment techniques, and human interface capability in relevant, representative, and actual environments. This work is not intended to support development or maturation of specific sensor devices but instead integrate existing technologies and render the resulting data available and actionable. The integrated system must be certifiable under applicable elements of MIL-STD- 810H, Environmental Engineering Considerations and Laboratory Tests (i.e., range of temperature, humidity, and pressure), not interfere with current Aircrew Flight Equipment (AFE), and during development establish impact on ejection safety and ability to execute high-g maneuvering flight (+9Gz/- 3Gz). The system must be demonstrated during development to accommodate 95% of Air Force aircrew. The system must be easily installable/configurable, requiring less than 30 minutes to install. The system will not emit electromagnetic energy that exceeds the limits of MIL- STD-461G, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, and ADS-37A-PRF, Electromagnetic Environmental Effects (E3) Performance and Verification Requirements, as it applies to Mission Critical Equipment, or be degraded by electronic emissions in its operational environment.

3.2.1 Prototype Integration Platforms. Requirements analysis, selection, and software and systems engineering necessary to prototype an integration platform for multiple sensor inputs and output to display and alerting capabilities. The hardware used to accomplish integration of multiple sensor devices must be self-contained, self-powered, and small and lightweight enough to easily integrate into the cockpit. Small form factor computing, including smartphone or tablet platforms, is desirable to enable minimal additional devices that must be integrated in aircrew ensembles. Wireless connectivity (such as Bluetooth Low Energy (BLE)) is possible. Associated software design standards are expected to be Government provided, specifically the Cognitive Operations Gear Pack™ (COG Pack™) architecture. The integration platform must provide sufficient space and computing power to enable a minimum of 9 hours (Threshold (T)) and desired 12 hours (Objective (O)) of data storage and processing capacity. After flight, the system should have the capability to offload data into a repository for long-term retention. Overall system key performance requirements also include a false positive rate (Threshold < 1 per 5000 flight hours, Objective < 1 per 25000 flight hours), false negative rate (Threshold < 1 per 10 true positives, Objective < 1 per 100 true positives) and component mean time between failures (MTBF) (T=O, > 1k flight hours).

3.2.2 Air Quality Monitoring. Selection and integration of air quality sensors, typically assessed via in-line sensor technologies. Air quality should include at a minimum (T) oxygen, carbon dioxide, air pressure, and air flow, with ability to detect likely contaminants highly desirable (O).

3.2.3 Pilot Vital Signs. Selection and integration of sensor systems that provide direct or indirect evidence of pilot circulation, blood or tissue oxygenation, heart or pulse rate and variability, along with derived metrics including but not limited to peripheral capillary oxygen saturation (SpO2), estimated core temperature, and respiration rate.

3.2.4 Flight (Cockpit) Environment. Selection and integration of sensors that provide basic environmental parameters such as cabin pressure, temperature, and acceleration that may be provided as part of another component or a separate component.

3.2.5 Respiratory Function. Selection and integration of, at minimum

(T), respiration rate data. It is also desirable (O) to address work of breathing and metabolic output.

3.2.6 Onboard Analytics. Development, test, and evaluation of onboard analytics that are capable of generating derived parameters, applying decision rules or algorithms, and generating alerts to the pilot that are specific as to recommended corrective action(s).

3.2.7 Pilot Alerting. Selection, prototyping, test, and evaluation of pilot alerts that are easily perceptible and interpretable. Ideally this component would utilize multimodal alerting (i.e., visual, auditory, and/or haptic) to maximize probability of pilot receiving the alert. Any user inputs required in flight must be possible with one hand, and while wearing Nomex flight gloves.

3.3 Modeling and Simulation. The Contractor shall model and simulate operational tasks, environments, and systems to support analyses of alternatives and development of integrated systems.

3.4 Research Laboratories and Research Network. The Contractor shall provide technical and computer expertise to accomplish research in simulated environments or test beds. Specific tasks will include but are not limited to the following: test plan and human protocol development and approval;

acquisition and setup of special laboratory and test facility equipment to meet test program objectives; development and use of software packages to provide optimal research capability. The Contractor shall utilize its research network (academia, industry, DoD partners and AFRL organizations, as well as operational and acquisition users) to facilitate the conduct of this work.

The Government will conduct independent verification and validation of component and integrated system prototypes throughout the execution of this work utilizing Government assets and facilities, including use of altitude chambers, human rated centrifuge, and flight test assets as appropriate to the stage of development.

4.0 SECURITY REQUIREMENTS

4.1 Position of Trust. All contractor personnel require a minimum of a Federal Investigative Standards (FIS) Tier 1 (formerly known as National Agency Check with written Inquires (NACI)) with SF85 for any position that requires access to the Internet, use of automated systems, or unescorted entry into restricted or controlled areas prior to reporting for duty in performance of this effort. The investigation is not for a security clearance;

it is for a position of trust. This is a mandatory requirement set forth in DoDMAN5200.02_AFMAN16-1405, Air Force Personnel Security Program. All documentation required for security certification shall be the responsibility of the Contractor. No foreign nationals shall be employed for work under this contract without prior approval of the Government.

4.2 Individual Security Clearances. This ARA Call will require Contractor personnel to have an active clearance (SECRET) prior to reporting for duty.

Interim clearances for newly hired personnel shall be processed as expeditiously as possible. Such clearance must be obtained through the Defense Security Service. For clearance, Contractor personnel require a minimum of a FIS Tier 3 (formerly known as National Agency Check with Law and Credit/Access NACI) with SF86 for unescorted entry into restricted or controlled classified areas prior to reporting for duty.

4.3 Operations Security (OPSEC). The Contractor shall provide OPSEC protection for all sensitive/critical information as defined by AFI 10-701, Operations Security, the 711 HPW OPSEC Plan, and Critical Information List(s) applicable to the task(s) and supported organization(s). The contractor shall participate in the 711 HPW sustained OPSEC awareness training, or include OPSEC training as part of their ongoing security program.

The 711 HPW OPSEC coordinator will evaluate the OPSEC posture of AF contract activities and operations.

4.4 Information Security and Force Protection. The Contractor shall accomplish Information Security and Force Protection training as defined by AFI 16-1404, Air Force Information Security Program, and DoDIO- 2000.16V1_AFI10-245-O_AFMCSUP, Antiterrorism (AT) Program Implementation. The Contractor shall participate in the 711 HPW sustained Information Security and Force Protection/Antiterrorism training, or include this training as part of their ongoing security program. The 711 HPW Security Managers will evaluate the training posture of AF contract activities and operations. This requirement is set forth in AFI 16-1404, DoDIO- 2000.16V1_AFI10-245-O_AFMCSUP, and applicable AFRL and 711 HPW supplements.

4.5 Protection of Human Subjects. The Contractor shall comply with the provisions of the following directives:

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), Subparts A, B, C, and D

d. DoDI 3216.02_AFI40-402, Protection of Human Subjects and Adherence to Ethical Standards in Air Force Supported Research

e. AFRLI 40-402, Protection of Human Subjects in Research

Interaction with human research subjects shall not commence until approval from the Air Force Institutional Review Board (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 the Protection of Human Subjects of Research, 18 April 1979.

4.6 Highest Security Classification: SECRET.