2018_BAA_ResponderEarlyID_SOO_J.pdf

Responder Early Identification Statement of Objectives BAA 18-02/Call 0001/SOO J

April 1, 2019 Science and Technology Directorate (DHS) Department of Homeland Security (S&T)

BAA 18-02/Call 0001/ SOO J Responder Early Identification

Table of Contents

Contents

1.0 Problem Statement

2.0 Purpose and Scope

3.0 Background Environment

3.1 Mission Scenarios

3.2 Current Technology Shortfalls and Threats

4.0 Potential Solution Attributes

4.1 Concept of Operations (ConOps)

5.0 Solution Capabilities and Requirements

5.1 Must Have Requirements

5.2 Desirable Capabilities or Characteristics

6.0 System Support

6.1 Contractual Requirements

6.1.1 Period and Place of Performance

6.1.2 System Affordability

6.2 Solution Support

6.2.1 Training

6.2.2 Storage and Maintenance

1.0 Problem Statement

In various types of emergencies, it would be valuable for responders to automatically be made aware of each other’s arrival and location. This would enable them to better coordinate their actions.

In order to plan collaborative response activities more safely and effectively, first responder teams need a technology that will track team member locations in real-time. An example of when this would be useful is a situation involving an active shooter or other hostile actor. This technology will help responders to avoid harming each other in error.

2.0 Purpose and Scope

This technology shall provide geolocation tracking of responders on the scene during an emergency and notify nearby responders of each other’s presence and location. The system shall be easy to activate and use in an emergency situation and be able to incorporate responders from a range of services and levels of government. The system should be secure, and as part of registration users should list their qualifications and have them verified by their agency. The system should also be able to communicate across various platforms (e.g., web-based, Android OS, iOS).

3.0 Background Environment

3.1 Mission Scenarios

• Responders arriving on the scene of an incident need to alert other responders to their presence and location, both to better coordinate their efforts and (in incidents involving hostile actors) to avoid accidentally harming one another.

3.2 Current Technology Shortfalls and Threats

There are multiple applications that perform some of the tasks that this technology should provide:

o One platform logs the responders that are on the scene and helps commanders form personnel into an organizational structure. It allows responders to log in remotely if they have the app and are vetted members of the program. This feature can help to alert other personnel of the responders that are already on the scene, but only if they already have the app.

o There is an app that allows teachers and administrators at schools to send an alert if there is a shooting at their school. The app sends the alert to law enforcement personnel who are in the area so that they can respond to the incident. The app also logs who the alert was sent to, however, it is not clear if it tracks the law-enforcement officers while they are at the scene.

o There is a situational awareness app that allows responders to track and communicate with team members during an incident. It is available to all US government agencies for free and allows for communication across agencies. It allows for responders to be shown on a floorplan, however, the floorplan needs to be loaded in the system, otherwise it defaults to using Google map images.

4.0 Potential Solution Attributes

This system will allow responders to identify who is already on the scene, and if possible, provide their location as well. This will be useful in a situation such as a school shooting where a responder in plain clothes should be identifiable so that he is not mistaken for the gunman/shooter. The system should clearly identify the responder so as to avoid friendly fire.

The system should be quick and easy to use so that it can be activated at a moment’s notice in an emergency. It should use a cross-jurisdictional platform that can incorporate responders from a range of services and levels of government. Ideally, the system should provide the geolocation of responders that are on the scene. The responder(s) should be easily identifiable, and the system should notify other responders of each other’s presence and location. The system should also be able to communicate across various platforms.

4.1 Concept of Operations (ConOps)

• When arriving on scene, the first responder can activate the system, alerting others that they are on-scene. If formal check-in is established on the incident, this system will allow the responder to check-in remotely, without having to go to the central location.

• System will also advise of staging areas, if applicable.

• The system will notify other responders that there is a responder in the area.

5.0 Solution Capabilities and Requirements

5.1 Must Have Requirements (Key Performance Parameters)

The proposed solution shall include:

• Responders should be able to log into the system remotely.

• The system should be easy to use and quick to implement so that it can be activated without much effort during an emergency.

• The system should also only be available to credentialed personnel.

• The system should be accessible to a range of departments across jurisdictions and levels of government.

• The system should also be compatible with other similar systems.

• The system should identify the responder and make it clear that they are not a gunman or shooter.

• The responder should be identifiable to the civilians as well as other responders.

• The system should track the location of responders.

5.2 Desirable Capabilities or Characteristics

In addition to the must have requirements reported in subsection 5.1, there are performance and/or system standards that exceed the proposed solution requirements.

• The system should track the identity of the responder (or identify their organization/department).

6.0 System Support

6.1 Contractual Requirements

6.1.1 Period and Place of Performance

The length of time of the contract shall be between 15-18 months and shall not exceed 18 months.

All developmental activities will be performed at the contractor-designated site(s). DHS may require the contractor to perform critical design reviews and/or product presentations at DHS-specified locations.

6.1.2 System Affordability

First responder agency budgets are limited and should be taken into consideration when developing and determining a price per unit cost model.

6.2 Solution Support

6.2.1 Training

Training information as required shall be provided on any specialized equipment, and shall include how to properly store, clean, deploy, and maintain the basic ensemble/unit. Any specialty requirements of personnel conducting maintenance, storage, extraction, or delivery will be identified including certification requirements. Training material shall be available initially in hard-copy, and subsequently in soft-copy format.

6.2.2 Storage and Maintenance

The contractor shall identify all necessary storage and maintenance requirements for the proposed solution including: the required maintenance schedule, identification of the specific components of the ensemble that requires maintenance, the type of maintenance required, and whether the maintenance can be performed in the field by operational personnel or if it will be required to be returned to the manufacturer for the required maintenance.

If the proposed solution is virtual, describe any storage or maintenance requirements, including archival activities, and the personnel performance needs associated with the solution.