STATEMENT OF OBJECTIVES FOR THE

BLAST EXPOSURE MONITORING (BEMO) SYSTEM

Basic Document: 6 March 2020

Prepared by

SOF AT&L –KR/PEO-SW Program Manager – US Army Medical Materiel Development Activity – Ft Detrick, MD

21702 Program Manager – Special Operations Forces Survival, Support & Equipment Systems US Army Combat Capabilities Development Command – Soldier Center, Natick, MA

01760

1.0 Program Objectives 1.1 Measure and record blast overpressure exposures that occur with heavy

weapon system use, breaching, and other dynamic training environments. 1.2 Advance the state of the art for blast exposure monitoring (BEMO)

technologies and information system integration to support the US Special Operations Command (USSOCOM) Comprehensive Strategy for Special Operations Forces Warfighter Brain Health.

1.3 Understand current blast exposure levels in a dynamic environment and mitigate sources of unnecessary exposure without degrading the quality of training or combat.

1.4 Enhance competition and affordability for future Government procurements by conducting competitive prototyping evaluations of multiple BEMO technologies.

1.5 Award a production contract without the use of competitive procedures in accordance with 10.U.S.C. 2371b(f), but only upon a determination that a prototype project for this transaction has been successfully completed as measured by the Successful Criteria in Appendix A.

1.6 Employment of the production version of the BEMO system by USSOCOM, which may also be adopted by General Purpose Forces in all Services. Services shall be responsible for establishing a procurement mechanism to support their requirements.

2.0 Agreement Objectives 2.1 Delivery of 105 operational BEMO system prototypes in accordance with the

agreed delivery schedule, which must: (i) meet the Successful Criteria in Appendix A; and (ii) be near production-ready blast gauge sensors that constitute operational prototypes at Technology Readiness Level (TRL) 7.

2.2 Notification to the Performer that the Government may award a follow-on production FAR-based contract or other transaction agreement (OTA) to a Performer that successfully completes the prototype project, but that such award is not guaranteed. The Government will notify the Performer(s) of any decision to conduct a follow-on prototype effort or enter into a follow-on production effort.

2.3 Receive from the Performer managerial and technical information in the most efficient manner that maintains transparency and provides the Government with insight into the prototype program’s status on cost, schedule, and technical performance throughout the duration of the OTA.

3.0 Management Objectives 3.1 A program plan developed, delivered, and executed by the Performer to ensure

successful performance of the BEMO system prototype project, which shall outline the Performer’s approach to program management, schedule management, technical baseline management, and data management, as well as

the successful execution of a potential follow-on production contract or agreement.

3.2 An independent evaluation by the Government of the operational suitability and technical performance of the operational prototype.

3.3 Performer management of the program baselines to ensure all efforts remain within cost and schedule utilizing company business processes to allocate resources, identify affordability initiatives, and provide timely status of on-going project tasks.

3.4 Receipt of an integrated master schedule, which shall be developed, maintained, delivered, and implemented by the Performer.

3.5 Government awareness of subcontractors and vendors to ensure the Performer manages its subcontractors and vendors in a manner that reveals the overall team structure transparently to the Government.

4.0 Technical Objectives 4.1 BEMO Prototype Development and Integration Phase 1. The Performer shall

provide a TRL 7 prototype to meet Government performance requirements specified in Appendix A by 01 March 2021. At the end of Phase 1, the Performer shall deliver:

4.1.1 A summary of performance characteristics (Vendor Specification Sheet) for the BEMO system, summary of results of vendor-sponsored testing to date, description of calibration, quality assurance, and quality control processes used in manufacturing, operator manuals, training materials, interface control documents, any type of required maintenance devices, literature to allow for Government calibration, and Department of Defense Architecture Framework (DODAF) 2.02 documents supporting system integration (e.g., SV-1, etc.).

4.1.2 A BEMO system capability set consisting of prototypes and ancillary items sufficient to equip 10 personnel for a period of 60 days (with spares) and sufficient for the Government to conduct an initial independent evaluation of the system. Ancillary items may include, but are not limited to, software, mobile electronic devices, cables, bar code scanners, mounts / personnel attachments, etc. The capability set must enable Government evaluators to configure BEMO prototypes for use and download full resolution data.

4.2 BEMO Prototype Development and Integration Phase 2. Performer participation in Government Technical Reviews (GTR). The Performer will participate in a Government-led review of the results of initial Government independent evaluation and identify potential technical and operational changes that could resolve noted issues. The GTR will occur within CONUS. At the end of Phase 2, the Performer shall deliver:

4.2.1 A BEMO system capability set that address the technical changes and issues from the GTR, consisting of prototypes and ancillary items sufficient to equip 10 personnel for a period of 60 days (with spares) and sufficient for the Government to conduct a follow-on independent evaluation of the system. Ancillary items may include, but are not limited to, software, mobile electronic devices, cables, bar code scanners, mounts / personnel attachments, etc. The capability set must enable Government evaluators to configure BEMO prototypes for use and download full resolution data.

4.3 BEMO Prototype Development and Integration Phase 3. The Performer shall resolve any remaining issues identified by the Government from Phase 2. The awardee shall deliver revisions, as needed, to Vendor specification Sheet for the BEMO system, summary of results of vendor-sponsored testing to date, description of calibration, quality assurance, and quality control processes used in manufacturing, operator manuals, training materials, interface control documents, any type of required maintenance devices, literature to allow for Government calibration, and DODAF 2.02 documents supporting system integration (e.g., SV-1, etc.).

4.4 The Performer shall deliver a BEMO system capability set consisting of prototypes and ancillary items sufficient to equip 100 personnel for a period of 180 days (with spares) and sufficient for the Government to conduct an independent evaluation of the system.

4.5 Information System Integration. The Performer shall develop and deliver a data dictionary and data model for all BEMO inputs and outputs that are intended to be passed to the BEMO system and from the BEMO system to Android Tactical Assault Kit (ATAK) Tactical Assault Kit (TAK) Server and SMARTABASE Athlete Data Management Software (Smartabase).

4.6 ATAK and TAK Integration. The BEMO operating software shall follow open architecture best practices and avoid the use of proprietary software. The Performer shall develop ATAK plug-in and other firmware and software, as needed, to employ the BEMO system using Government owned and configuration managed mobile devices and information systems (IS) and to move data from tactical end user devices to enterprise IS within the SOF Cloud. ATAK plugs-in developed under this effort must be published to the Government managed TAKMAPS.COM website and be fully transparent (source code is viewable) and available to all authorized MilTAK users and developers.

4.7 Smartabase Integration. The Performer shall build and deliver a well-documented Application Programming Interface (API) to Smartabase and provide summarized processed clean data for Smartabase. Coordinate with the Smartabase Original Equipment Manager (OEM) Fusion Sports, and Government Smartabase builders and program managers to develop and demonstrate Smartabase data views (mock ups and specifications) and to

provide input, as needed, for documentation of the Government Risk Management Framework (RMF).

5.0 Reference Documents. 5.1 Deputy Secretary of Defense Comprehensive Strategy and Action Plan for

Warfighter Brain Health (Appendix B) 5.2 USSOCOM Brain Health Policy 19-01 (Appendix B)

6.0 DATA DELIVERABLE(S) 6.1 IMS 6.2 Monthly / Quarterly Report: Performer shall provide monthly status report in

Microsoft word format. 6.3 Final report: Items identified in section 4.3 will suffice as final report

7.0 DELIVERY SCHEDULE: 7.1 Delivery of Phase 1: 01 March 2021 (Tentative) 7.2 Delivery of Phase 2: 01 June 2021 (Tentative) 7.3 Delivery of Phase 3: 01 September 2021(Tentative)

Appendix A: Essential Characteristics and Successful Criteria

1) Ease of wear and use: Provide options to the user (e.g. several mounting concepts) that they can choose from to fit mission requirements and still be able to reliably collect blast overpressure exposure data. The mounting options should allow for use while in plain clothes/civilian attire.

2) Automation of gauge activation and assignment to the individual (via QR code scan, near field communication (NFC) etc.) Demonstrate an efficient and user friendly method to match blast gauge sensors with the operator’s unique ID with the ATAK or Smartabase (via QR code, NFC, BLE, or other wireless)

3) Automation of data capture and transmission. Configuration has built in flexibility with auto/manual settings for data transfer from the ATAK via TAK server host synchronization, file prompt, or customizable auto download at specified times (set up a widget that operator can use to select best way to transfer data based on mission requirements). Demonstrate wireless push of data through ATAK and Smartabase.

4) Intuitive summary data GUI on ATAK plug in. The plug in will include a

GUI that provide a list of overpressure data that can be filtered by severity within a selected range of psi (0.5 – 100psi), or by date/time, within a selected period of time, of up to 7 days. GUI will provide an intuitive method of displaying blast exposure levels to the operator. The GUI will also provide cumulative impulse data for each individual that can be filtered by severity or date/time as described above for overpressure data.

5) Minimal wireless emission. The blast gauge must operate with minimal electromagnetic and radiated emissions signature (MIL-STD-461G certified for electromagnetic interference emission and susceptibility).

6) Size, Weight: Threshold of 2cu in/2oz, with an objective < 1cu in, 1oz.

7) Water resistant and weatherproof: Blast gauge must maintain full operational capacity in temperature extremities in accordance with MIL-STD-810H Ingress Protection level (IP) 68. Blast gauges must be fully operational while water resistant (heavy rain) and sweatproof.

8) Accuracy: Gauge must accurately capture single event blast exposure within 80% of standard for threshold and at 100% accuracy of standard for objective (pencil gauge is the standard).

9) Data capture sampling rate: Gauge must have a threshold sampling rate of 100kHz = threshold and objective of unlimited sampling rate capable of capturing every event fired.

10) Battery: gauge must have a battery threshold of 9 months battery life, with an objective of having wireless rechargeable battery capabilities with 150 hours of continuous use before recharge.

11) The BEMO system must reliably record blast overpressure events that meet or exceed the defined recording threshold (typically between 0.5 and 1 PSI). False Negative Rate Threshold [T] < = 10% Objective [O] < = 2% while simultaneously meeting service life (battery life) specifications. (e.g., if a sleep mode is used the BEMO must wake up from sleep mode every time it interfaces with blast overpressure T= O).

12) Memory: Gauge must be able to hold minimum of 200 full events with objective of unlimited event capture. Gauge must be able to auto delete events after successful transfer to ATAK.

a) The sensor and/or plug will provide a full memory warning (exceeding 80% memory).

13) Calibration: Gauge must auto-calibrate and auto-check for calibration. The sensor and/or plug-in must have the ability to indicate a warning if/when an issue arises with the auto-calibration on ATAK and Smartabase.

14) Integration to TAK and Smartabase

a) Demonstrate interoperability (system of systems) between the blast gauge sensor, ATAK plug-in, TAK server, and Smartabase via wireless data capture and transmission.

b) Demonstrate an intuitive functional plug in on ATAK: A functional plug-in that matches a set of gauges with the operator’s unique ID with the ATAK (via QR code, NFC, BLE, or other wireless); configuration has built in flexibility with auto/manual settings for data transfer from the ATAK via TAK server host synchronization, file prompt, or customizable auto download at specified times (set up a widget that operator can use to select best way to transfer data based on mission requirements).

(i) The plug in shall have built in algorithms for processing data and preparing information for transfer into Smartabase.

(ii) The plug in will clear all memory data from the gauge when data is successfully transmitted through the TAK Server to Smartabase.

(iii) The plug in will provide a low battery warning (

Appendix B: References