OTTI CSO AOI 05 - Questions_Answers_Final.pdf

AOI 05 Number Q = Question

Topic Question Response

AOI 05 - Q01 Wearable Trigger Please confirm that the feature which triggers recording physical activities is on the device, such as through a button or menu interface on the device.

The activity cannot solely trigger from a personal phone.

AOI 05 - Q02 Wearable Trigger Please confirm that the trigger required is not sent by the mobile application triggering the device to start recording physical activities.

A. The system’s architecture must prevent the passive or automatic collection of activity data without explicit user action.

B. The solution must provide a manual, user-initiated mechanism for recording activities. The manual mechanism must be a physical button or switch integrated into the COTS hardware device.

The design of the physical button or switch shall incorporate features to prevent accidental activation during typical use. Examples include but are not limited to:

i. Recessed or shielded button/switch housing to protect against inadvertent contact

ii. A deliberate confirmation sequence for activation and deactivation, such as a “Press-and-hold” for a minimum of 3 seconds or a rapid “double-press”.

iii. Tactile and audible or haptic feedback to confirm successful activation or deactivation to the user C. The functionality governing the physical button or switch must be embedded in the device’s firmware and shall not be by passable or modifiable by external applications or phones.

AOI 05 - Q03 Security Clearance What level of security clearances are required after Phase 1?

Security clearances are not required. The system needs to meet the security requirements explained in the AOI

AOI 05 - Q04 Wearable Device Has USSF already purchased the physical devices that will be used for this effort?

The Government has not purchased the devices as we are waiting for AOI responses to determine the best device / solution.

AOI 05 - Q05 Service Support What are the service team requirements? A service team is responsible for logistics, including device distribution, replacements, helpdesk support, training, compliance, disenrollment adjudication, and contract management.

All Offerors will be required to provide ALL these functions. It is a critical element for Offerors to consider in the development of their proposal.

AOI 05 - Q06 Digital Architecture and Cybersecurity

What is the digital architecture? The digital architecture used for the AFRL CFA study will likely need to be upgraded to support a fully fielded program of record. The current AFRL architecture does not have all of the requirements specified in the AOI. Specific needs in the AFRL current infrastructure must be addressed with new solutions to address these limitations with innovation. Additionally, the current AFRL architecture utilizes an obfuscation approach to user login that is stressing the system logistically.

Possible limitation fixes to consider for the AFRL architecture and infrastructure:

-Encryption at the point of collection -Modified application to address PII and cyber compliance items -Cyber compliant clouds. This could include:

-- Contractor owned/contractor operated cloud environments with DISA certification -- Contractor owned/contractor operated cloud environment with DISA certification over to gov't IL5 environments such as GovCloud.

-- Push data directly to a gov't IL5 cloud -- Additional cloud hosted firewall protections -- Gov't application on user commercial device

Proposed architectures need to meet the cyber requirements, encrypt user data, mitigate potential OPSEC concerns, and protect Guardian data.

AOI 05 - Q07 Device Capabilities vs USSF Requirements

What are the core USSF requirements? Existing commercial devices offer numerous metrics (e.g., sleep, recovery), but the USSF has a narrower set of critical requirements with extremely high standards for accuracy and device interoperability.

The USSF would like to remain strictly focused on the core requirements and their metric alignment with policy. Further, the USSF would like to be able to limit the data collection on Government clouds to only the metric collection requirements to maintain user privacy.

AOI 05 - Q08 Capability Delivery Timeline

If a company cannot fully meet all requirements upon contract commencement, will the Government accept a phased approach to full capability delivery?

Existing wearables will be working with technology that has never been milspec’d for use before.

The USSF is anticipating some development to deliver the requirements. Offerors should provide their approach to meeting the final solution, including a phased approach if necessary.

AOI 05 - Q09 Form Factor Device Requirement

Please clarify the approximate total number of Guardians who will be provided with a Portable Wearable Fitness Device (PWFD) and associated software. Also please clarify how many of these individuals are military and how many are civilian.

Please assume 10,000 Guardians. All will be military.

AOI 05 - Q10 Miscellaneous Based on prior market research conducted by USSF and publicly available press releases, it appears that a multi-year pilot project is ongoing using specific PWFDs. Are there any best practices or key lessons learned from the current pilot that can be shared with industry to help inform a response?

The USSF requested AFRL to conduct a service wide, two-year study of Continuous Fitness Assessment (CFA) to refine cybersecurity and privacy approaches necessary for use of commercial wearables. The study also helped to assess the impact of wearables on Guardians' wellness, injuries, lost duty days, and fitness compared to similar Airmen to determine return on investment.

Additional cybersecurity requirements beyond what was accomplished in the AFRL are captured in the AOI requirements.

Data privacy and data management continues to be a priority amongst Space Force Guardians with respect to the PWFDs. Protecting Guardian privacy and data is vitally important in the adoption of the program while also maintaining the usability of the devices. Members across the Space Force that love the program want the ability to connect their device with other available applications.

AOI 05 - Q11 Miscellaneous What specific government-issued PWFDs are already in use providing CFA capabilities for Guardians as part of ongoing pilots? Please specify the form factor, models, and quantity for each. Are these devices going to continue to be used by USSF or must they be replaced as part of this opportunity?

The USSF is not directing the use of any specific device for the program of record. The CSO is meant to solicit innovative technologies and services to meet the stated mission. The Government plans to leverage lessons learned from devices used in the AFRL study to inform future requirements

AOI 05 - Q12 Form Factor Device Requirement

Providing Guardians with a choice of device from a range of options can have the added benefit of increasing ownership and engagement. However, this also creates additional complexity and cost. We understand that USSF requires devices in, “...customizable form factors or adjustable options to accommodate a wide range of user preferences and comfort needs.” Please elaborate on the difference between “customizable form factor” vs. “adjustable options”. Does “customizable form factor” refer to a choice between device case sizes, or does this mean something else? Does “adjustable options” refer, for example, to the size-color-style of an associate watch band, or does this mean something else?

Devices should be able to accommodate various Guardian sizes and shapes, body or wrist types, depending on the device proposed. The USSF is not mandating any specific device and does not want a device so customizable that the options are unweildy and costly to the Government. An example of adjustability for watches could mean various sized watch faces or bands. For other types of devices, it may mean different options of another feature to accommodate the comfort needs of a diverse population.

AOI 05 - Q13 General Will PWFDs be assigned to a single Guardian, or is there an intent to utilize pools of devices? If pooled, please specify the requirements for wiping/sanitizing PWFDs between users.

Each Guardian will be issued their own device.

AOI 05 - Q14 Form Factor Device Requirement

The “Form Factor Device Requirements”, subsection “e.” specifies a minimum 3-year operational lifespan.

Does USSF prefer a “big bang” implementation of PWFDs with all Guardians being immediately outfitted, or does USSF prefer a phased implementation approach to outfit the force over several years with a corresponding spread of life-cycle costs?

The USSF expects all Guardians to be outfitted, within reason, at the same time. The USSF intends to transition from the AFRL study to the program of record at a single instance to maintain Continuous Fitness Monitoring for the force. The 3-year lifespan pertains to the lifespan of the device itself, not the CFA or PWFD program.

AOI 05 - Q15 Device Management

The requirements call for a Device Management solution for securely managing Bluetooth-enabled devices. Does USSF have an existing solution vendors can integrate with, or must they provide a stand-alone solution?

There is currently no USSF solution nor any preferred or suggested solution.

AOI 05 - Q16 Security Measures Please confirm the minimum software hosting posture for Phase 1 through Phase 3. Is IL-5 required at award, or will IL-4 with IL-5 equivalent controls be accepted during pilot with an IL-5 ATO path identified in Phase 3?

An IL-4 ATO with IL-5 equivalent or an IL-5 ATO will be required at time of award

AOI 05