N241-064 TITLE: Advanced Wearable Integration and Synchronization Hub (AWISH)
OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Human-Machine Interfaces; Integrated Network Systems-of-Systems
OBJECTIVE: Develop a hub system that optimizes data capture, synchronization times, and integrates data collected from physiological wearable devices.
DESCRIPTION: It is well known that insufficient sleep quality and quantity lead to health and performance decrements which can be catastrophic in military settings. In response to the Government Accountability Office recommendations to Congress on fatigue in the Navy (GAO-21-366), the Command Readiness, Endurance, and Watchstanding (CREW) program is advancing a fatigue monitoring and mitigation solution for the Navy. An initial prototype of a wearable-based infrastructure has been developed and tested with several ships (e.g., USS San Diego, USS Montgomery). However, technical improvements are required to move this product from a research and development phase to a pre-commercialization phase to support at scale deployment.
The objective of this SBIR topic is to develop a standalone hub system capable of capturing data off physiological wearable devices (e.g., Oura ring, Polar Grit X Pro, PowerWatch, etc.) and then to push the data to the backend data infrastructure. These data captured shall provide an early indicator for fatigue and sleep deficiency for which mitigation strategies may be implemented. The hub system should reduce active human interactions which in turn will reduce human error; as well as optimize sync transfer times between wearables and the hub, increase data throughput, extend bluetooth range for Pi devices evaluate (and/or identify alternative device to use), and create a system dashboard U/I that provides real time stats and allows ease of access/control over the networked system (primary/lead hub and subordinate hubs) to push time updates, monitoring system a stand-alone light weight server. The hub should create a solution for message queuing and automated pushing of files upon restoration of network connectivity following lost network access. The hub should improve or replace automated method for wearable device pairing. The awardee will deliver complete technical documentation and a complete user manual for both the primary and secondary hubs.
PHASE I: Define and develop a concept for a hub that can meet the hardware and software performance constraints listed in the Description. The hub concept should develop means and methods that advance the current mechanisms for data capture and transfer from wearable physiological devices. The hub concept should be backend architecture agnostic, meaning that it should be able to push to a multitude of data management architectures. The Phase I option, if exercised, would include the initial layout and capabilities description to build the hub in Phase II.
PHASE II: Develop a prototype hub based on Phase I work for demonstration and validation. The prototype hub should be delivered at the end of Phase II, ready to be fielded by the Government.
PHASE III DUAL USE APPLICATIONS: Integrate the Phase II developed hub prototype into deployed Naval vessels and transition finalized product to Naval Surface Force (SURFOR). The Phase III hub should integrate with the CREW data infrastructure used by the Navy. Dual uses in the commercial sector include sporting teams and emergency services (e.g., Fire, EMS).
KEYWORDS: Physiological monitoring, sleep, fatigue, wearables, human performance, data integration
** TOPIC NOTICE **
The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 24.1 SBIR BAA. Please see the official DoD Topic website at www.defensesbirsttr.mil/SBIR-STTR/Opportunities/#announcements for any updates.
The DoD issued its Navy 24.1 SBIR Topics pre-release on November 28, 2023 which opens to receive proposals on January 3, 2024, and now closes February 21, (12:00pm ET).
Direct Contact with Topic Authors: During the pre-release period (November 28, 2023 through January 2, 2024) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on January 3, 2024 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period.
SITIS Q&A System: After the pre-release period, until January 24, 2023, at 12:00 PM ET, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at www.dodsbirsttr.mil/topics-app/ by logging in and following instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.
Topics Search Engine: Visit the DoD Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoD Components participating in this BAA.
|1. Can we assume that the system should support sensor device (using Bluetooth) handover, without the need for user interaction, between hubs as users are moving around in the ship?
2. If so, should the handover mechanism minimize (or avoid) disruption of ongoing data transfers from the sensor device to the hub and local server, or is some data loss accepted? What is an acceptable delay to make a handover (in milliseconds or seconds)?
|1. Correct. Handovers must occur without user involvement / interaction.
2. Data loss is not acceptable. Objective for handover / transfer is to 10-seconds, threshold is 2-mins. There is some flexibility on these general time ranges though.