RFI Attachment 1- Blast Overpressure Sensor System (BOSS) Requirement Document.docx
DOCX document 64 KB Posted
- Attached to
- Blast Overpressure Sensor System (BOSS)
- Solicitation number
- W91CRB-26-RFI-BOSS
About this file
This is a Requirement Document attachment to a Request for Information (RFI) for the Blast Overpressure Sensor System (BOSS), a soldier-worn device mandated by Congress through the 2018, 2019, and 2020 National Defense Authorization Acts to monitor blast overpressure exposure and support longitudinal medical studies on how blast exposure affects service member brain health. The Department of the Army Materiel Command, Army Contracting Command Aberdeen Proving Ground is conducting market research to identify qualified vendors capable of meeting Key Performance Parameters (KPPs) and Key System Attributes (KSAs), with RFI responses due by 1600 Eastern on 11 September 2026 to roxanne.a.dalrymple.civ@army.mil and timothy.j.compton7.civ@army.mil.
The BOSS device must meet specific technical requirements including: triggering at 80% reliability between 0.5-60 psi peak pressure levels (desired 0.5-100 psi) with visual red/yellow/green indicators; sensor accuracy within 20% error for peak pressure and impulse data and 10% error for full duration exposure; sensor precision within 5x reference gauge variability (desired 2x); reporting peak pressure, duration, impulse, and waveform data; recording Universal Coordinated Time (UTC) with synchronization across multiple sensors; sampling rate of 100 kilohertz (desired 400 kHz); maintaining false negative and positive rates of 10% or lower (desired 1%); storing minimum 500 full events (desired 10,000); demonstrating interoperability with tactical systems (TAK server) and DoD information systems via wireless transmission; compliance with MIL-STD 461G electromagnetic emissions standards; and an intuitive app with manual and automated data transmission capabilities to leader dashboards. The Government seeks to assess industry capability, evaluate feasibility and technology maturity, and refine acquisition planning based on vendor responses.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amended_RFI Attachment 1- Blast Overpressure Sensor System (BOSS) Requirement Document.pdf | ||
| Boss Sources Sought.pdf | ||
| Q_and_A_W91CRB_26_RFI_BOSS.pdf | ||
| RFI Attachment 2_Blast Overpressure Sensor System (BOSS) Remarks.xlsx | XLSX spreadsheet | |
| Boss Sources Sought.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Title: Blast Overpressures Sensor System (BOSS)
Requiring Activity/ Agency Name: Capability Program Executive-Ground (CPE-Ground), Soldier Medical Devices (SMD)
Background: Through three National Defense Authorization Acts (NDAA), Section 734 of the 2018 NDAA, Section 253 of the 2019 NDAA, and Sections 717 and 742 of the 2020 NDAA, Congress mandated longitudinal medical studies on Blast Overpressure (BOP) exposure. These studies aim to improve the DoD’s understanding of how blast exposure affects Service Members’ brain health and to better inform policies on risk mitigation, unit readiness, and health care decisions. The BOSS will be a Soldier‑worn device designed to track, store, and transmit blast overpressure events caused by shock waves above normal atmospheric pressure, whether from tier‑one weapons or explosions during training and combat. By proactively monitoring blast exposure, BOSS may help reduce injury severity. It will provide real-time data to inform medical decisions and maintain exposure history for long‑term health monitoring within the PEO Soldier Data Eco-System.
Purpose: The Government intends to conduct a Sources Sought to identify qualified sources capable of meeting the required Key Performance Parameters (KPPs), as well as to gain an understanding of how potential vendors may be able to meet these requirements in the future. Through this market research effort, the Government seeks to assess current industry capability, evaluate associated risks, and determine the feasibility and maturity of potential paths toward full KPP compliance. The information received will help the Government shape acquisition planning, refine requirements, and better understand the solutions available or emerging within industry.
Key Performance Parameter (KPPs) and Key System Attribute (KSA) : The Government has identified both required and desired Key Performance Parameters (KPPs) and Key System Attributes (KSAs) for this requirement. The required KPPs and KSAs represent the minimum performance thresholds that must be met for a solution to be considered acceptable; failure to meet any required (minimum) KPP will result in the solution being deemed noncompliant. The desired KPPs, while not mandatory, reflect enhanced performance objectives that the Government prefers but does not require. For clarity, these KPPs are presented in two columns—“Minimum” for required thresholds and “Desired” for preferred performance—enabling vendors to clearly distinguish between mandatory requirements and aspirational capabilities when preparing their responses.
| # | |
| Key Performance Attribute | |
| Key Performance Attribute Threshold | |
| Key Performance Attribute Objective | |
| Evidence to Provide |
| A. In a laboratory-controlled environment, and in various positions, the system shall trigger at least 80% of the time at peak pressure levels between 0.5-60 psi. |
| A1. The system desired Peak Pressure Levels are between 0.5 - 100 psi. |
· In-house, government or independent laboratory level or field testing showing triggering threshold and statistical (n>100) reliability.
Visual red, yellow green indicator on the sensor or interface App.
| 1. |
| Pressure Range |
B. The device shall provide the user with an indicator when the exposure event breeches a given threshold. The indicator threshold will be adjustable and can be turned off when in a contested environment.
Threshold required
C. The system shall have a visual red, yellow green indicator on the sensor or interface App
| Threshold Required |
| N/A |
| 2. |
| Sensor Accuracy |
| The system, when measured in a controlled laboratory evaluation, and in a manner that the device would be worn by Soldiers, shall accurately capture peak pressure and impulse data within a total error of 20% of standard reference gauge/pencil gauge over the pressure measurement range. |
| The system, when measured in a controlled laboratory evaluation, and in a manner that the device would be worn by Soldiers, shall accurately capture full duration exposure and impulse data within a total error of 10% of standard reference gauge/pencil gauge over the pressure measurement range. |
| •In-house, government or independent laboratory level or field testing showing statistical (n>100) reliability in sensor measurement (peak and impulse) as compared to lab grade high fidelity pressure sensors. |
| 3. |
| Sensor Precision |
| In a laboratory-controlled environment, total variability in peak pressure and exposure duration measurements of the system shall be within 5x reference gauge variability. |
| In a laboratory- controlled environment, total variability in peak pressure and exposure duration measurements of the system within 2x reference gauge variability. |
| · In-house, government or independent laboratory level or field testing that shows a 5 sigma (T), 2 sigma (O) standard deviation off the mean measurement for expected charge weight PSI over a statistically (n>100) relevant number of tests. |
| 4. |
| Blast Metric Reported |
| The system shall report the peak pressure, duration, and impulse of a BOP event. |
| The system reports the peak pressures, durations, impulse values, and stores the wave forms. |
| · Sample data file expected as an output from the sensor that reflects metrics |
| # | |
| Key System Attribute | |
| Key System Attribute Threshold | |
| Key System Attribute Objective | |
| Evidence to Provide |
| 1. |
| Estimating Orientation and Sensor Time Synching/Stamping |
A. The system shall record the Universal Coordinated Time (UTC) (Zulu time) at which each Blast Overpressure (BOP) event occurred, and for systems with multiple sensors, the triggering of any sensor in the system starts all sensor simultaneously to ensure all pressure sensors are synced for each event.
A1. The system records and time stamp the Universal Coordinated Time (UTC) (Zulu time) of arrival to the nearest microsecond for each pressure sensor and determine orientation of the Soldier to the blast source based on that data
· Demonstrate ability to capture local time via GPS, computer connection or other medium to provide a date time stamp associated with event exposure data.
B. The system shall record, and time stamp the time of arrival to the nearest second for each overpressure sensor.
· Documentation of architecture diagrams that show simultaneous trigger mechanisms to distributed sensor systems
| 2. |
| Interoperability |
A. The system shall demonstrate interoperability between tactical systems (e.g., TAK server) and selected data management systems via wireless data capture and transmission EUD transport when connected.
| Threshold Required |
| · Demonstration of existing Android or IOS App that could be extensible to referenced systems. |
B. As Next Generation Command and Control (NGC2) prototype matures and transitions to production, the system will be embedded in the NGC2 technology stack.
| 3. |
| Integration with Information Systems |
The system shall demonstrate interoperability (system of systems) between the BOP sensor device and widely accessible DoD information systems.
| Demonstrate interoperability (system of systems) between the BOP sensor device and widely accessible DoD information systems via wireless data capture and transmission. |
| · Ability to connect secure (https) internet site or the DoD cloud systems for data transport to DoD IS’s. |
| 4. |
| Wireless Emission/Transmission |
A. The system shall be IAW MIL-STD 461G to operate with minimal electromagnetic interference emissions signature.
| Threshold required |
| · In-house, government or independent laboratory level or field-testing showing compliance. |
B. The system shall provide a “mission mode” to stop all wireless transmissions unless requested by the handheld device.
Threshold Required
| 5. |
| Memory |
The system shall be able to hold a minimum of 500 full events. The device and/or associated app must have a full memory warning (exceeding 80% memory). An indicator light (that can be disabled), or on-screen warning when connected to an EUD will alert the user when memory is low.
| The system holds a minimum of 10,000 full events and has a full memory warning (exceeding 80% memory) |
| · In-house, government or independent laboratory level or field-testing showing compliance. |
| 6. |
| Sampling Rate |
| The system sampling rate shall be ≥ 100 kilohertz (kHz). |
| The system sampling rate is ≥ 400kHz. |
| · In-house, government or independent laboratory level or field-testing showing compliance. |
| 7. |
| Recording Reliability |
The system shall maintain a false negative rate of ≤ 10% and a false positive rate of ≤ 10% while simultaneously meeting service life (battery life) specifications
| The system maintains a false negative rate of ≤ 1% and a false positive rate of ≤ 1% |
| · In-house, government or independent laboratory level or field-testing showing compliance. |
| 8. |
| Automation of Data Capture and Transmission |
A. The app shall demonstrate an intuitive and functional program that transmits data in a standardized format and is usable on widely accessible DoD information systems. Sensor devices shall have manual settings for data transfer to widely accessible DoD information systems (e.g., tactical systems and/or middleware via EUD transport). Data shall be viewable by Leaders on a dashboard vignette.
A1. Demonstrate an intuitive and functional app that transmits data in a standardized format and is usable on widely accessible DoD information systems that has built-in algorithms for processing data and preparing information for transfer into storage server. Sensor devices shall have wireless push of data to widely accessible DoD information systems (e.g., tactical systems or middleware via EUD transport). Data shall be viewable by Leader and medical provider on a dashboard vignette
· In-house, government or independent laboratory level or field-testing showing compliance.
B. Sensor devices shall have manual settings for data transfer to widely accessible DoD information systems (e.g., tactical systems and/or middleware via EUD transport).
| B1. Threshold Required |
| N/A |
C. The app shall clear or overwrite all memory data from the sensor device when data is successfully transmitted through to storage server. The sensor device software shall provide a low battery alert (<20% battery life) and full memory alert.
| C1. Threshold Required |
| N/A |
| 9. |
| Interface control document (ICD) |
| A. The sensor shall execute secure, interoperable, non-proprietary data exchange with operational, clinical (e.g., BATDOK, OpMED CDP, MHS GENESIS), and tactical systems. |
| A1. Threshold Required |
| B. For Bluetooth and BLE communications, the sensor shall conform to the Bluetooth SIG Health Device Profile (HDP) or Generic Attribute Profile (GATT) to transmit data. |
| B1. Threshold Required |
| C. For 802.3 or 802.11 TCP/IP medical data payload transmissions shall conform to non-proprietary industry standards (specifically RESTful APIs (JSON/XML), HL7 FHIR and IEEE 11073) |
| C1. Threshold Required |
| N/A |
| D. All interfaces, data structures, and export functions shall be fully documented and operate independently of closed, proprietary vendor gateways. |
| D1. Threshold Required |
ADDITIONAL PERFORMANCE Attribute: The below are non-essential additional characteristics that the government desires but are not required to be deemed acceptable. If the below items are not included with the device sales as “No Charge”, separately price them on the quote.
| # |
| Additional Performance Attribute |
| Additional Performance Attribute Threshold |
| Additional Performance Attribute Objective |
| Evidence to Provide |
| 1. |
| Automation of Sensor Device Activation and Assignment |
A. The system shall utilize an efficient and user-friendly method to match BOP sensor devices with the operator’s unique ID via widely accessible DoD information systems (e.g., tactical systems, middleware via EUD transport).
| A1. The system will utilize an automated means to match BOP sensor devices with the operator’s unique ID via QR code scan, near field communication, or other wireless method |
| · In-house, government or independent assessment of data files contain a unique ID (i.e. CAC personal key identifier (PKI)) that can be used to associate to the wearer. |
B. The system shall allow for memory erase and re-assignment to a new operator.
B1. Threshold Required
| 2. |
| Calibration |
The system shall auto-calibrate and auto-check for calibration. The device and/or plug-in shall have the ability to indicate a warning if/when a calibration issue arises
| Threshold Required |
| · Documentation of calibration report at startup or predetermined times at a regular interval. |
| 3. |
| Sensor Device Reset Rate |
| Device sensor shall have a reset rate of no more than three (3) seconds |
| Device sensor has no reset time. |
| · In-house, government or independent laboratory level or field-testing showing compliance. |
| 4. |
| Storage |
A. The system can perform when stored for up to 18 months, IAW and as described in MIL-STD-810H.
| A1. Can perform when stored for up to 4 years, as described in MIL-STD-810H |
| · Documentation of physical sensor and compliance to. |
B. System components must not require cold chain storage or specialized storage conditions
B1. Threshold Required
| 5. |
| Data Standardization |
A. The system shall generate BOP exposure data in a standard format that is displayed for review and transmitted as transient data to reviewers.
| A1. Threshold Required |
| · Documentation and compliance with government provided data format and ICD. |
B. Data will be available in a standard non-proprietary open architecture format for future manipulation and system integration.
B1. Threshold Required
| 6. |
| Warranty |
The system shall include a minimum one‑year warranty period.
The system includes a minimum five‑year warranty period
N/A
Requirements Document Key Performance Attributes/ Key System Attributes/ Additional Performance Attributes Critical Logistic Specifications/ Additional Performance Parameters
1. Critical Logistic Specifications: The below are essential logistical characteristics and the minimum must be met to be considered acceptable by the government. They are separated by “minimum” and “desired” column. If the below items are not included with the device sales as “No Charge”, separately price them on the quote.
| # |
| Operational Characteristic |
| Minimum Required |
| Desired Characteristics |
| 1. |
| Manuals |
| The vendor must provide 1 physical and 1 digital User/Operator, Maintenance/Service Manual with each procured device. |
| Minimum Requirement |
| 2. |
| Delivery |
| The vendor must deliver the system and consumables within 45-90 days after contract award to include CONUS and OCONUS locations. |
| The vendor can deliver the |
system and consumables within 30-45 days after contract award to include CONUS and OCONUS locations.
| 3. |
| Risk Management Framework (RMF) / |
Authority to Operate (ATO)
| The vendor must provide supporting documentation as required by the client to complete Risk Management Framework procedures and Authority to Operate activities for cybersecurity protections if deemed relevant |
| Minimum Requirement |
| 4. |
| Copyright |
Release
| The vendors must provide Operational and Maintenance copyright/distribution releases to support Army Technical Manuals to distribute to the force. |
| Minimum Requirement |
ADDITIONAL PERFORMANCE PARAMETERS: The below are non-essential additional characteristics that the government desires but are not required to be deemed acceptable. If the below items are not included with the device sales as “No Charge”, separately price them on the quote.
| # |
| Additional Performance Parameters (APPs) |
| Additional Performance Parameters |
| 1 |
| Defense Logistics Agency Electronic Catalog (ECAT) |
| The vendor works with DLA troop support, Prime Vendor or Non- prime vendor 3rd party to get their products on the ECAT contract vehicle for future procurement and make available any service contracts ECAT as well |
| 2 |
| Manufacturing capability, order quantities and schedule |
| The vendor will provide information on manufacturing capability to help support the client in understanding supportable order quantities and schedule |
File details come from the government source that posted it. Updated .