FRG_BAA_13-012_Version_9.pdf

BAA 13-012 V.8

Published: 03/02/2017

BROAD AGENCY ANNOUNCEMENT (BAA)

FIRST RESPONDER GROUP

BAA 13-012

Version 9

Department of Homeland Security

Science and Technology (S&T) Directorate

Published: 06/28/2017

TABLE OF CONTENTS

1. GENERAL INFORMATION

1.1. Introduction

1.3. Program Mission and Objectives

1.4. Agency Name

1.5. Program Name

1.6. Research Opportunity Number

1.7. Government Representatives

2. RESEARCH OPPORTUNITY DESCRIPTION

2.1 Anticipated Technical Topic Areas (TTAs)

2.2. Type Classifications

3. AWARD INFORMATION

3.1. Anticipated Award Date

3.2. Anticipated Funding for the Program

3.3. Type of Contract/Instrument

3.4. Number of Awards Anticipated

3.5. Expected Amount of Individual Awards

3.6. Anticipated Period of Performance for Individual Awards

4. ELIGIBILITY INFORMATION

4.1. Federally Funded Research & Development Centers

4.2. Nonprofit Organizations, Educational Institutions and Small Business Set Aside

4.3. Organizational Conflict of Interest

5. APPLICATION AND SUBMISSION INFORMATION

5.1. Registration Requirements

5.2. White Paper Submission Requirements and Evaluation Process

5.3. Full Proposal Package Application and Submission Process

5.4. Format and Content of Full Proposals

5.5. Protection of Information Uploaded to BAA Website:

5.6. Full Proposal due Date and Time:

5.7. Submission of Late Full Proposals

5.8. Further Assistance Needed for this BAA

5.9. BAA Contractual and Technical Questions

5.10. Performer Technical Presentation

6. EVALUATION INFORMATION

6.1. Technical Evaluation Criteria

6.2. Past Performance Criteria

6.3. Cost/Price Criteria

6.4. Evaluation Order of Importance

6.5. Government Evaluation Panel

6.6. Notification to Offerors of Evaluation Findings

7. AWARD ADMINISTRATION INFORMATION

7.1. Comments or Concerns

8. OTHER INFORMATION

8.1. Information for Full Proposal Respondents

8.2. Government Property, Government Furnished Equipment (GFE) and Facilities

8.2. SAFETY Act

8.3. Export Control Considerations

8.4. Security Classification

8.5. Information for Full Proposal Respondents

8.6. Subcontracting Plan

8.7. Additional Deliverables

8.8. Reporting

8.9. Certificate of Current Cost or Pricing Data

8.10. Test and Evaluation Facilities

8.11. Hazardous Materials

8.12. Contract Award by Agencies Other Than DHS (using potential DFARS clauses)

8.13. Foreign (Joint) Funding – Provisions Necessary to Implement International Agreement(s)

1. GENERAL INFORMATION

1.1. Introduction

The Department of Homeland Security (DHS) Science & Technology (S&T) Directorate is announcing to business and academia its intent to solicit white papers and proposals under this Broad Agency Announcement (BAA). This Broad Agency Announcement (BAA) is contemplated in Federal Acquisition Regulations (FAR) 6.102(d)(2) and 35.016. This announcement does not request any white papers or proposals at this time.

Solicitations (or calls) for white papers and proposals will be accomplished via amendments to this BAA.

The over-arching strategy of the BAA involves the use of an existing 5-year open-ended BAA to quickly and efficiently execute research and development to deliver practical solutions to high priority first responder problems. This strategy will provide DHS an acquisition tool with the flexibility to solicit white papers and proposals and make awards to perform rapid prototyping (12 to 18 months) of technical solutions to meet present and compelling first responder needs, as ever-changing urgent operational issues and capability gaps are identified.

The BAA will remain “open for 5 years; however, white papers and proposals will only be solicited and accepted during calls. Each call will identify solicitation topics and contain a common cut-off date for white paper and proposal submission. White papers or full proposals received after the specified due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

Calls for white papers and proposals (made by amendments to this BAA) will occur periodically throughout the life of this over-arching BAA. Each call will: (1) identify specific topic areas; (2) identify any changes to the standard evaluation criteria or white paper and/or proposal preparation instructions, and; (3) contain common cutoff dates for submissions.

It is anticipated that solicitations issued under this BAA will be unrestricted. Small businesses are encouraged to propose on all of the solicitations. The NAICS code, unless otherwise stated in the BAA amendments, shall be 541712 (i.e., Research and Development in the Physical, Engineering, and Life Sciences except Biotechnology), and the size standard is 500 employees. White papers and proposals submitted shall be in accordance with this BAA and its appropriate amendment(s).

Interested Offerors shall be on alert for any BAA amendments that call for white papers and proposals, permit extensions to the submission dates, or otherwise change the requirements of this BAA or its subsequent amendments.

This announcement is restricted to work relating to applied research and that portion of advanced technology development not related to a specific system or hardware procurement. This announcement does not cover support services, such as technical services, or other types of support services. Such submissions are considered non-compliant with this BAA and will be rejected without evaluation.

1.2 Foreign Government Participation.

1.2.1 First Responder safety, efficiency and effectiveness is a global concern and FRG has collaborative activities with several countries. As a result, FRG BAA HSHQDC-13- R-B0012 intends to have foreign government participation, to include access to both white papers and proposal submissions for purposes of determining joint-funding and joint participation throughout the contract period of performance. Foreign government participation will be determined by technical topic area for each call based on FRG collaboration and may include any of the following international partners: (a) the United Kingdom of Great Britain and Northern Ireland; (b) the Kingdom of Sweden; (c) the Kingdom of the Netherlands; (d) the Government of France; (e) the Government of Germany; (f) the Government of Spain; (g) the European Union; (h) the Government of Israel;(i) the Government of Canada; (j) the Government of Mexico; (k) the Government of Australia; (l) the Government of New Zealand; (m) the Government of Singapore; (n) the Government of Finland; and (o) the Government of Japan.

1.2.2 In addition, foreign government personnel from any one or more of the aforementioned countries may participate in the selection process as peer/scientific reviewers of submitted white papers and/or proposals if their respective nation has been identified in the individual call made under CSD BAA HSHQDC-13-R-B0012. In the event that foreign government personnel do participate in the selection process, DHS will effect sharing of whitepapers and proposals subject to the provisions for handling both “Controlled Unclassified Information” and “Business Confidential Information” information, as stated in each country’s international agreements with the DHS, or the U.S. Government. In addition, foreign government personnel are not permitted to release any information to third parties, including others in their organization. By the act of submitting any material in response to this BAA, Offerors are therewith consenting to allowing access to financial, confidential, proprietary, and/or trade secret marked information, and any other material contained therein to foreign government personnel.

1.3. Program Mission and Objectives

The DHS Science & Technology First Responders Group (FRG) mission is to strengthen the first responder community’s ability to protect the homeland and respond to disasters.

Through the engagement of first responders at every stage, the FRG pursues a better understanding of needs and requirements, and develops innovative solutions to the most pressing challenges faced during day-to-day and large-scale emergencies.

The objectives of the FRG are:

(1) Enhance first responder preparedness and ensure effective emergency response.

(2) Create high impact technologies and knowledge products that facilitate the safety, effectiveness, and ease with which first responders do their work.

(3) Strengthen the Homeland Security Enterprise and First Responders’ capabilities to protect the homeland and respond to disasters.

1.4. Agency Name

Department of Homeland Security Science & Technology Directorate First Responders Group DHS S&T CBD – Mail Stop 0201 245 Murray Lane Washington, DC 20528-0201

1.5. Program Name

First Responders Group

1.6. Research Opportunity Number

BAA 13-012

1.7. Government Representatives

Science and Technology:

Mr. Milt Nenneman BAA Program Director First Responders Group Department of Homeland Security Science and Technology Directorate Washington, DC 20528

Business:

Ms. Sharon Flowers Procuring Contracting Officer Department of Homeland Security Office of Procurement Operations Science & Technology Acquisition Division Washington, DC 20528

2. RESEARCH OPPORTUNITY DESCRIPTION

2.1 Anticipated Technical Topic Areas (TTAs)

The following Technical Topic Areas (TTAs) are provided to help interested Offerors understand the first responder technology needs.

1. Wildland Fire Respiratory Protection

Existing respiratory protection solutions for wildland firefighting are either too bulky/cumbersome, too hot, provide insufficient protection, do not allow for strenuous activity, or do not provide extended-wear respiratory protection for the multiple hours a firefighter in the field must endure. Without effective options, many firefighters wear no protective equipment, or wear simple cotton bandanas; the resulting exposure to toxins and particulates in the environment raises their risk for cancer and other short- and long-term health issues.

The proposed solution will be a new piece of equipment worn by responders that is lightweight and offers a low-profile so it does not negatively impact the amount of gear a wildland firefighter can carry, the firefighters’ range of motion, or their ability to communicate. The device will not prevent wildland firefighters or other responders from safely performing their duties.

2. Emergency Response Vehicle Warning for Civilians

Emergency vehicle to civilian vehicle alerting system is needed for when an emergency vehicle is responding to an incident with lights and sirens. Current systems - lights and sirens - do not alert civilians to oncoming emergency vehicles well or soon enough. Many civilians do not hear or notice the lights and sirens and do not move in a timely manner for the emergency vehicle to continue towards their destination uninterrupted or without accident.

The proposed solution shall be a new notification system in addition to the traditional lights and sirens used on emergency vehicles. It shall interrupts the status quo in a vehicle, such a system that cuts into the radio (e.g. satellite radio, Bluetooth, or AM/FM stations) or an audio, visual, or vibration alert in the interior of a civilian’s vehicle. Additionally, the proposed solution will “listen to” emergency vehicles in close proximity that have activated their lights and sirens. In other words, when a first responder activates their lights and sirens, this technological solution shall alert vehicles of the emergency vehicle’s presence, allowing for a three pronged approach to notification: lights, sirens, and direct communication to civilian vehicles that are equipped with this new technology.

3. Emergency Vehicle to Emergency Vehicle Early Warning System

First responders, primarily those in the emergency medical services, Law Enforcement, and Fire department communities need the ability to warn each other of their presence as they are driving in emergency mode. Currently, there is a relatively short period of time available to alert others of an emergency vehicle’s proximity. The potential of having more than one emergency vehicle approaching or passing through the same location from different directions significantly increases the chance of a collision.

The proposed technology solution shall notify emergency response drivers of other approaching emergency vehicles from a distance and in a manner that ensures they are aware of an oncoming emergency vehicle. Each vehicle will communicate the proximity of the other vehicle as it is captured and relay that information to the driver of each respective emergency vehicle.

4. Multi-Mission Disrupter

There is a need to create a multi-mission disrupter system that includes a stand, aiming system and new ammunition to support the disrupter. The proposed unit would be closer to a one-size-fits-all standard eliminating the need for multiple disrupters; it would be easy to assemble and load; and, it would be smaller and weigh less than current models. The device will be agile with minimal time to prepare for use in a shooting configuration and will be able to support standard bomb squad operations in a land or water environment.

The technology solution will prove useful to the public safety bomb squad community in the conduct of their mission support to render safe operations by saving lives, preserving life and property, allowing for faster operations, and less collateral damage.

5. Multimeter Wire Attack Kit

There are currently no tools designed for EOD use that combines the functions of a multimeter with a wire attack kit and current probe into one device – the community currently uses commercial off the shelf (COTS) equipment designed for commercial work.

Creating an EOD specific device would remove unneeded features and simplify work done by the EOD technician, thus creating a safer more efficient tool that can conduct an electronic diagnostic of detonator wires and switches. The intent is to create a multimeter wire attack kit that has a high electrical isolation of the voltmeter built in and greater sensitivity of the microprobe with reduced meter readout error. With the development of this integrated tool, EOD operations would be able to be performed faster, more safely, and with greater accuracy.

6. Rescue Hoist Protective Glove

First responders who assist with rope rescues or hoist rescues have a very specialized need in regards to protective hand wear. While performing certain actions, the protective cover/webbing is prone to wear over time increasing the difficulty for the first responder as they perform their duties.

The proposed solution will be a new glove made of advanced materials or a replaceable insert/attachment that is more durable and longer lasting than current gloves in use. The new gloves, or inserts that can be attached to the gloves, will provide increased durability and can be worn by rescue helicopter personnel without interfering with other required duties. Additionally, the glove must have enough flexibility for the rescue helicopter personnel to perform other required duties and the solution cannot negatively impact the responder’s range of motion.

7. First Responder Routing Logic Guide

There is a need for an emergency responder routing system that would inform responders of upcoming road and traffic conditions and suggest alternate routes to safely and efficiently navigate their vehicles. Currently, many first responders are utilizing commercially available mapping applications such as Google maps on their cell phones to route themselves to incidents that they are dispatched to instead of using traditional Automatic Vehicle Location (AVL) systems and those systems do not include other road options that first responders could be taking to decrease incident response and egress times.

This solution shall create additional layers to existing solutions or a new application for first responders to meet the additional needs that they have while navigating roadways to incidents. the ability to take in external data sources for transit schedules (e.g., trains, drawbridges, public transit) as well as taking advantage of public and private property (e.g., right-of-ways, emergency access roads), express lanes, the ability to exceed speed limits, etc.

8. Integration of Public Data Feeds

Eyewitness accounts and information via open/publicly shared social media has great potential to significantly enhance situational awareness and the common operating picture (COP) for first responders. However, currently there is no platform to provide first responders with a single stream of data that includes open source social media and other shared information feeds (e.g. traffic and weather). This solution will provide a platform for first responders to incorporate these open data feeds into commonly used COP software with the ability to provide alerts of potential or emerging events based on triggers preset by the user. During an event, the system will continue to stream the integrated data to the users for constant up-to-date situational awareness as well as provide basic decision recommendations to inform resource allocation and response planning.

9. 3D Indoor Dynamic Mapping and Visualization

There is a need for technology that provides real-time 3D mapping and visualization of the inside of building spaces under varying conditions. Currently, first responders, in particular, firefighters and tactical law enforcement personnel, frequently operate in multi-story buildings under hazardous conditions. Exposure to such conditions without the ability to map out the location hinders the effectiveness of first responders during the course of an incident. The solution should provide first responders and Incident Commanders (ICs) the ability to render 3D dynamic mapping and visualization of indoor areas in terms of architectural and semantic information in real time. Additionally, the solution should have the durability and resiliency to succeed in extreme environmental operating conditions common to first responders and also have the ability to capture dynamic updates when structural changes occur (i.e. when the wall of a building collapses/crumbles mid-firefight) and render that information to the IC.

10. Energy Harvesting Fabrics

DHS S&T is looking for innovative energy-harvesting smart fabric technology for integration into first responder uniforms. The fabric should be able to be used for the manufacture of first responder garments, without compromising garment weight, traditional garment colors, comfort (including fit, garment “hand”, and cooling ability), environmental protection provided by the garment, or professional appearance of the garment ensemble. It should not interfere with the performance of any normal responder tasks. The fabric that is developed should be able to harness the energy from the environment in which the responders are operating to assist in powering the equipment that they are using.

Different operational scenarios are envisioned. The first is for a duty uniform that would be worn daily by law enforcement personnel, emergency medical technicians, and firefighters while they are performing routine tasks. It is envisioned that possible energy sources for these scenarios would include kinetic energy from the movement of the responders, solar energy, ambient light and heat sources, etc. The second scenario is a specialized application for firefighters, including wildland firefighters and structural firefighters. A fire environment has an abundance of thermal energy, and therefore is potentially a large source of power that can be utilized by responders to reduce their logical and weight burden. Applications include fabrics for use in structural turnout gear and/or wildland firefighting ensembles. A fabric that meets the requirements of any one of the scenarios presented above would be acceptable to meet the goals of this development effort.

2.2. Type Classifications

Prototype technologies delivered at the end of the period of performance (POP) shall be capable of achieving a Technical Readiness Level (TRL) of 7 or higher.

TRL 7 - System prototyping demonstration in an operational environment (ground or space): System prototyping demonstration in operational environment. System is at or near scale of the operational system, with most functions available for demonstration and test.

Well integrated with collateral and ancillary systems. Limited documentation available.

TRL 8 - Actual system completed and "mission qualified" through test and demonstration in an operational environment (ground or space): End of system development. Fully integrated with operational hardware and software systems. Most user documentation, training documentation, and maintenance documentation completed. All functionality tested in simulated and operational scenarios. Verification and Validation (V&V) completed.

TRL 9 - Actual system "mission proven" through successful mission operations (ground or space): Fully integrated with operational hardware/software systems. Actual system has been thoroughly demonstrated and tested in its operational environment. All documentation completed. Successful operational experience. Sustaining engineering support in place.

In order to meet the requirement, companies submitting white papers and full proposals shall identify which one of the two type classifications, described below, aligns with their proposed strategy.

1. Type I (Prototype Technology):

Technologies having a TRL of 3 or 4

• TRL 3 - Analytical and experimental critical function and/or characteristic proof-of concept: Proof of concept validation. Active Research and Development (R&D) is initiated with analytical and laboratory studies. Demonstration of technical feasibility using breadboard or brassboard implementations that are exercised with representative data.

• TRL 4 - Component/subsystem validation in laboratory environment:

Standalone prototyping implementation and test. Integration of technology elements. Experiments with full-scale problems or data sets.

2. Type II (Mature Technology):

Technologies having a TRL of 5 or 6

• TRL 5 - System/subsystem/component validation in relevant environment:

Thorough testing of prototyping in representative environment. Basic technology elements integrated with reasonably realistic supporting elements. Prototyping implementations conform to target environment and interfaces.

• TRL 6 - System/subsystem model or prototyping demonstration in a relevant end-to-end environment (ground or space): Prototyping implementations on full-scale realistic problems. Partially integrated with existing systems. Limited documentation available. Engineering feasibility fully demonstrated in actual system application.

3. AWARD INFORMATION

3.1. Anticipated Award Date

The anticipated award dates will be specified under each call for white papers and full proposals. Awards are probable based on amendments issued during the 5-year (FY13- FY17) solicitation period.

3.2. Anticipated Funding for the Program

Estimated Value: Although subject to official fiscal appropriation, it is anticipated that the FRG program will have $4 M per year with a total of $20M over the next 5 years to support this BAA. Additional joint funding from the countries DHS S&T has bi-lateral agreements with may be provided subject to their respective availability of funds, as well as interest in the particular proposal(s).

Note: The estimated value is not a promise of assured funding in that amount. Funding is uncertain and is subject to change. Changes in availability may occur as a result of Government discretion.

3.3. Type of Contract/Instrument

It is anticipated that a mix of contract types will be used throughout the life of this BAA.

The specific type of contract will be issued in each call for white papers and full proposals.

The Government reserves the right to award procurement contracts, Grants, Cooperative Agreements (CAs), Other Transactions (OTs), or Interagency Agreements (IAAs) to appropriate parties shall the situation warrant.

3.4. Number of Awards Anticipated

The total number of awards under this solicitation is unknown at this time. Future awards are probable based on calls or amendments issued during the 5-year (FY13-FY17) solicitation period.

3.5. Expected Amount of Individual Awards

The amount for each award will be based on the level of effort proposed and agreed to by the Government. The FRG’s desire is for companies and academia to leverage existing technology or development efforts when possible to minimize cost while meeting the stated objectives.

3.6. Anticipated Period of Performance for Individual Awards

The anticipated period of performance for each award is 12 months with no award exceeding 18 months.

4. ELIGIBILITY INFORMATION

Open to All Responsible Sources. CSD BAA HSHQDC-13-R-B0012 is open to ALL responsible sources domestic or foreign. Foreign or foreign-owned Offerors are advised that their participation is subject to the foreign disclosure review procedures, applicable export control laws, and other applicable federal laws, regulations, and policies pertaining to foreign entities. It is the intent of research and development contracting to obtain a broad base of the best contractor resources from the scientific and industrial community, to include small businesses and as a result, no portion of CSD BAA HSHQDC-13-R-B0012 will be set aside pursuant to FAR Part 19.502-2. Offerors may include (but are not limited to): single entities or teams from academia, private sector organizations, Government laboratories, and Federally Funded Research and Development Centers (FFRDCs), including Department of Energy National Laboratories and Centers.

4.1. Federally Funded Research & Development Centers

FFRDCs, including Department of Energy National Laboratories and Centers, are eligible to respond to this BAA, individually or as a team member of an eligible principal Offeror, so long as they are permitted under a sponsoring agreement between the Government and the specific FFRDC.

4.2. Nonprofit Organizations, Educational Institutions and Small Business Set Aside

The Government encourages Nonprofit Organizations, Educational Institutions, Small Businesses, Small Disadvantaged Business (SDB) concerns, Historically Black Colleges and Universities (HBCU), Minority Institutions (MI), Women-Owned Businesses (WB), and Historically Underutilized Business (HUB) zone enterprises as well as large businesses, academic institutions, and Government laboratories to submit research white papers and full proposals for consideration and/or to join others in submitting white papers and full proposals; however, no portion of the BAA will be set-aside for these special entities pursuant to FAR Part 19.502-2, because of the impracticality of reserving discrete or severable areas of research and development in any specific requirement area.

To ensure full consideration in these programs, registration in the https://baa2.st.dhs.gov/ website, described later in this document, requires the appropriate business type selection as well as accurate up-to-date information.

4.3. Organizational Conflict of Interest

Organizational Conflict of Interest issues will be evaluated on a case-by-case basis; as outlined below. Offers who have existing contract(s) to provide scientific, engineering, technical and/or administrative support directly to the DHS S&T will receive particular scrutiny.

https://baa2.st.dhs.gov/

(a) Determination. The Government has determined that this effort may result in an actual or potential conflict of interest, or may provide one or more Offerors with the potential to attain an unfair competitive advantage.

(b) If any such conflict of interest is found to exist, the Contracting Officer may (1) disqualify the Offeror, or (2) determine that it is otherwise in the best interest of the United States to contract with the Offeror and include the appropriate provisions to mitigate or avoid such conflict in the contract awarded. After discussion with the Offeror, the Contracting Officer may determine that the actual conflict cannot be avoided, neutralized, mitigated, or otherwise resolved to the satisfaction of the Government, and the Offeror may be found ineligible for award.

(c) Disclosure: The Offeror must represent, as part of its full proposal and to the best of its knowledge that: (1) It is not aware of any facts which create any actual or potential organizational conflicts of interest relating to the award of this contract; or (2) It has included information in its full proposal, providing all current information bearing on the existence of any actual or potential organizational conflicts of interest, and has included the mitigation plan in accordance with paragraph (d) of this provision.

(d) Mitigation/Waiver. If an Offeror with a potential or actual conflict of interest or unfair competitive advantage believes it can be mitigated, neutralized, or avoided, the Offeror shall submit a mitigation plan to the Contracting Officer for review. Award of a contract where an actual or potential conflict of interest exists shall not occur before Government approval of the mitigation plan.

(e) Other Relevant Information: In addition to the mitigation plan, the Contracting Officer may require further relevant information from the Offeror. The Contracting Officer will use all information submitted by the Offeror, and any other relevant information known to DHS, to determine whether an award to the Offeror may take place, and whether the mitigation plan adequately neutralizes or mitigates the conflict.

(f) Corporation Change. The successful Offeror shall inform the Contracting Officer within thirty (30) calendar days of the effective date of any corporate mergers, acquisitions, and/or divestures that may affect this provision.

(g) Flow-down. The contractor shall insert the substance of this clause in each first tier subcontract that exceeds the simplified acquisition threshold.

5. APPLICATION AND SUBMISSION INFORMATION

The following instructions may apply in total, or in part, to subsequent individual calls for white papers and full proposals. Each amendment to this BAA calling for white papers and full proposals will detail which preparation instructions apply. White papers and full proposals submitted shall be in accordance with this announcement and any instructions in the individual call. Offerors shall be alert for any BAA amendments that may permit extensions to the white paper or full proposal submission date.

5.1. Registration Requirements

Registration is not required to download the full proposal package; however, a registration in the DHS BAA Program Portal https://baa2.st.dhs.gov/ is required to upload a response to the BAA including a white paper and/or a full proposal submission.

5.2. White Paper Submission Requirements and Evaluation Process

If a call requests a white paper submission, Offerors must submit a white paper in order to be considered for participation in the submission of proposals.

Offerors submitting white papers will be required to upload their documents to the DHS BAA Portal by the established deadline for each BAA Call.

Offerors will have 30 business days from the official call for white papers before the submission deadline.

White papers should provide technical and managerial approach information, and will be assessed based on Criterions I, II, and III which are listed in descending order of relative importance as outlined in Section 6.1 below.

White papers cannot exceed a total number of 10 single-sided pages with the following stipulations:

• Paper Size – 8.5-by-11-inch paper

• Margins – 1 inch

• Spacing – Single- or double-spaced

• Font – Times New Roman, 12 point

White papers exceeding the page limit will not be evaluated.

After an evaluation of the white papers, the Contracting Officer will either encourage or discourage the submission of a full proposal based on the recommendation of the SSA. The SSA will make these recommendations based on a finding of whether a white paper is selectable or not selectable. If the SSA determines, based on the criteria found in Section 6.1, that a full proposal should be discouraged the Offeror will be informed in writing by the CO. No additional feedback will be provided to Offerors when proposals are discouraged. Offerors are not restricted from submitting a proposal even when notified in writing that the SSA is discouraging a full proposal. If the SSA determines, based upon the above criteria found in Section 5, that a full proposal should be encouraged the Offeror will be informed in writing by the CO.

Offerors receiving an “Encouraged” rating will be asked to submit a full proposal. All Offerors who submit a proposal will be asked to present their proposals at a Performer Technical Presentation of the Government Evaluation Panel and other invested stakeholders (see Section 5.10 below).

NOTE: User registration is not sufficient for registering the white paper or full proposal.

To register your submission, you must log on with your credentials. Click the “Start New Proposal” side link. When the Start the New Proposal page displays, pick the solicitation and topic, and then enter the title of the proposal that you are submitting. When you have entered the title, click the “Add Proposal to Activity Worksheet” button. The Proposal Activity worksheet page lists your full proposal in the In Progress section of the page.

Your full proposal is registered at this point. Repeat this step before the full proposal registration deadline for every proposal you wish to register.

After you have completed the coversheet and uploaded your full proposal documents, you must click on the “Submit Proposal” button to submit the full proposal; simply uploading the documents is not sufficient.

5.3. Full Proposal Package Application and Submission Process

Each call will specify when Full Proposals are due and when Performer Technical Presentations will take place. Submissions will not be accepted from organizations that have not registered. Any organization that wishes to participate in this BAA must register at: https://baa2.st.dhs.gov/.

Respondents who submit a full proposal may be called to present their proposal to the Government Evaluation Panel consisting of DHS FRG Program Managers (PMs), and experts from the first responder, business, and scientific communities. Federal Government personnel will be the sole voting faction of the Government Evaluation Panel. First responder representatives will be comprised largely from the FRG First Responder Resource Group (FRRG); a sub-group of the Government’s Incident Management Integrated Product Team (IPT). FRRG members are operational and subject matter experts in one or more emergency response disciplines (e.g., Fire, Law Enforcement, Emergency Medical Services, Explosives, HAZMAT, Search and Rescue, Emergency Management, Communications, and Counter-Terrorism/Intelligence). As such, they are uniquely aware of the most critical technical challenges facing the nation’s emergency response community.

Offerors must meet the minimum submission criteria outlined in Section 5.4 below in order for their proposal to receive further evaluation. If the minimum criteria are not met, S&T has the right to reject the Offeror’s proposal.

(a) Submitting a Response to this BAA:

No Classified White Papers or Full Proposals (or portions thereof) will be accepted.

The white paper and full proposal submissions will be protected from unauthorized disclosure in accordance with FAR 15.207, applicable law, and DHS regulations. In addition, foreign government personnel from the 13 countries, participating as outlined in Section 1.1 above, are bound by the non-disclosure provisions covering the protection of

“business confidential” information, as stated in their international agreements with the DHS and are not be permitted to release any information to third parties, including others in their organization. By submission of a full proposal, Offerors are hereby consenting access to financial, confidential, proprietary, and/or trade secret marked information in the proposal to these foreign government personnel. To review these international agreements, see the section titled, “Cooperation in Homeland/Civil Security Matters” at the following link:

http://www.dhs.gov/files/international/counterterrorism.shtm.

Offerors are expected to appropriately mark each page of their submission that contains proprietary information.

The DHS BAA website at https://baa2.st.dhs.gov offers electronic access to BAA solicitations, frequently asked questions (FAQs), answers to FAQs, abstracts of previously funded projects, and hyperlinks to other useful information.

Please refer to the “Registrations and Submissions Training Guide”, in the upper right hand corner of the FAQ page for step-by-step instructions for registering your company and submitting your full proposal.

IMPORTANT: Before submitting a white paper or full proposal for the first time, you must first register your company and user account in the system. It is recommended that the Business Official or an authorized representative designed by the Business Official be the first person to register for your company. Your company’s Taxpayer Identification Number (TIN) is required during registration. (If your company is registered, other new users may register and associated their information with the company’s existing record.

When registration is completed, users can submit and manage their white papers and proposals.

NOTE: User registration is not sufficient for registering the white paper or full proposal.

To register your submission, you must log on with your credentials. Click the “Start New Proposal” side link. When the Start the New Proposal page displays, pick the solicitation and topic, and then enter the title of the proposal that you are submitting. When you have entered the title, click the “Add Proposal to Activity Worksheet” button. The Proposal Activity worksheet page lists your full proposal in the In Progress section of the page.

Your full proposal is registered at this point. Repeat this step before the full proposal registration deadline for every proposal you wish to register.

After you have completed the coversheet and uploaded your full proposal documents, you must click on the “Submit Proposal” button to submit the full proposal; simply uploading the documents is not sufficient.

5.4. Format and Content of Full Proposals

Proposal Format

Full proposals will consist of two volumes:

• Volume 1 - Technical Proposal

• Volume 2 - Cost Proposal

For each volume, the following format shall apply:

• Paper Size – 8.5-by-11-inch paper

• Margins – 1 inch

• Spacing – Single- or double-spaced

• Font – Times New Roman, 12 point. Text embedded within graphics or tables in the body of the Project Description Form shall be legible and not smaller than 8 point.

• Number of Pages – o Volume 1 (Technical Proposal): No more than 30 single-sided pages. Proposals exceeding the page limit will not be evaluated. The Official Transmittal Letter, as well as the cover page, table of contents and resumes/biographical information about potential performers in the proposal are not subject to the page limitation.

o Volume 2: (Cost Proposal): No page limit.

• Copies – A full proposal shall consist of one electronic file for the Technical Proposal volume and one electronic volume for Cost proposal volume. Electronic files will be in portable document format (PDF), readable by IBM-compatible PCs. Each file size must be no more than 10 MB.

Proprietary or Export Control Marking: Offerors are expected to appropriately mark proprietary and/or export controlled information contained in their full proposals. For additional information regarding export controlled information, refer to bullet “Export Control” identified in Proposal Content below.

Proposal Content

Volume 1: Technical Proposal

Volume I of the full proposal shall be in the form of a Technical Proposal volume.

Responsiveness to the order and content of sections listed in Volume I is important to assure thorough and fair evaluation of full proposals. Nonconforming proposals may be rejected without review. The Technical Proposal must cover the following points in more detail:

• Official Transmittal Letter: This is an official transmittal letter with authorizing official signature. For an electronic submission, the letter can be scanned into the electronic full proposal. The letter of transmittal shall state whether the full proposal has been submitted to another government agency, other than DHS S&T, and if so, which one and when.

• Cover Page: This shall include the words “Technical Proposal” and the following:

1) BAA number;

2) Call number;

3) Technical Topic Area;

4) Title of Full Proposal;

5) Type of classifications;

6) Identity of prime Offeror and complete list of subcontractors, if applicable;

7) Technical point of contact (name, address, phone/fax, electronic mail address);

8) Administrative/business point of contact (name, address, phone/fax, electronic mail address); and,

9) Duration of effort (separately identify the basic effort and any options)

10) In accordance with FAR 4.1201, prospective Offerors for contracts and for

OTAs involving prototypes (Section 845), shall state the certifications in the System for Award Management (SAM) at www.sam.gov have been completed and shall provide the Certification Validity period; and

11) The signature and title of an authorized representative of the entity submitting the full proposal. If multiple organizations are participating, one signature from the principal/leading organization is acceptable.

• Table of Contents

• Executive Summary: Summarize the full proposal and the expected benefits of the solution.

• Proposal: Describe the proposed work and the associated technical and management issues.

• Performance Goals: Describe the overall methodology and how it will meet the program objectives and the specific Technical Task Area.

• Detailed Technical Approach: Describe the proposed design and technical issues.

Identify the critical technical issues in the design and concept.

• Statement of Work (SOW), Schedule, and Milestones: Provide an integrated display for the proposed research, showing each task with major milestones.

Include a proposed schedule for the effort (estimated dates of tasks, milestones and deliverables). Describe how each task will be performed and identify sub-tasks, if appropriate. Include a section clearly marked as the SOW you propose to undertake. It is anticipated that the proposed SOW will be incorporated as an attachment to the resultant award instrument. To this end, such proposals must include a severable self-standing SOW without any proprietary restrictions, which can be attached to the contract or agreement award.

https://www.sam.gov/

• Deliverables: Provide a brief summary of all deliverables proposed under this effort, including data, and reports consistent with the objectives of the work; along with suggested due dates (calendar days after the effective date of award). This section shall be severable, i.e., it will begin on a new page and the following section shall begin on a new page. It is anticipated that the proposed detailed list and description of all deliverables will be incorporated as an attachment to the resultant award instrument. To this end, such proposals must include a severable self-standing detailed list and description of all deliverables without any proprietary restrictions, which can be attached to the contract or agreement award.

• Management Plan: Provide a brief summary of the management plan, including an explicit description of what role each participant or team member will play in the project, and their past experience in technical areas related to this proposal.

• Commercialization Plan: Offerors must also include a description in the proposal of their plan for commercializing the technology, or other plans for getting the technology into established transition paths. Technology transition plans that include commercial partnerships are preferred, but transition into the open source community is also acceptable. This request does not entail providing a full business plan, nor does it imply that DHS views commercialization activities as in the scope of this solicitation. The intent is for Offerors to provide evidence that, as part of the technical plan development, consideration has been given to the ultimate commercialization of the outputs of DHS-funded programs. Such considerations would include expected user base, how the technology will be used, and how it will be transitioned, manufactured and distributed in to broad use. Of key importance are the identification of technology diffusion paths that are appropriate for the type and maturity of the technology involved, and any additional factors that might increase the likelihood of it being commercialized. Offerors who intend to partner with other companies for manufacturing and distribution services shall identify their partners and the partner’s capabilities.

• Facilities: List the location(s) where the work will be performed, and the facilities to be used. Describe any specialized or unique facilities which directly affect the effort.

• Government-Furnished Resources: Provide a brief summary of required information and data which must be provided by the Government to support the proposed work, if any.

• Cost Summary: Summarize the projected total costs for each task in the initial period of performance and any proposed option year of the effort, including a summary of subcontracts, man hours, and consumables.

• Resumes for Key Personnel: In Appendix A, provide resumes and curriculum vitae (CVs) for each of the key personnel. These resumes do not count toward the 30-page limit.

• Other DHS Support: As an appendix, provide a list of any current or pending awards or proposals with DHS that pertain to the work, submitted either as a prime contractor, subcontractor/consultant, or teaming partner. This section will not count towards the 30-page limit.

• Export Control: Offerors are advised that the export of any goods or technical data from the United States, and the disclosure of technical data to foreign nationals, may require some form of export license from the U.S. Government. Failure to obtain necessary export licenses may result in criminal liability of Offerors under U.S. laws.

Offerors are responsible for ensuring compliance with the International Traffic in Arms Regulations administered by the U.S. Department of State (22 C.F.R. Parts 120 to 130), Export Administration Regulations administered by the U.S.

Department of Commerce (15 C.F.R. Parts 730 to 774), and Foreign Assets Control Regulations administered by the U.S. Department of Treasury (31 C.F.R. Parts 501 to 598), as warranted, and with compliance with all recordkeeping requirements under U.S. export regulations. Offerors are responsible for compliance with any applicable export license, reporting, or other preapproval requirements by the U.S.

Government. DHS neither represents that a license or preapproval shall not be required nor that, if required, it shall be issued. Nothing granted herein to Offerors provides any such export license or other preapproval.

Offerors shall identify any anticipated export compliance issues in their response to this solicitation. Specifically, Offerors are advised to include information in their response regarding any known equipment, software or technical data that will be developed as a result of work to be performed under this solicitation that is subject to export control restrictions.

• Assertion of Data Rights: Include here a summary of any assertions to any technical data or computer software that will be developed or delivered under any resultant award. This includes any assertions to pre-existing results, prototypes, or systems supporting and/or necessary for the use of the research, results, and/or prototype. Any rights asserted in other parts of the full proposal that would impact the rights in this section must be cross-referenced. If less than unlimited rights in any data delivered under the resultant award are asserted, the Offeror must explain how these rights in the data will affect its ability to deliver research data, subsystems, and toolkits for integration as set forth below. Additionally, the Offeror must explain how the program goals are achievable in light of these proprietary and/or restrictive limitations. If there are no claims of proprietary rights in pre-existing data, this section shall consist of a statement to that effect.

Full proposals submitted in response to this BAA shall identify all technical data or computer software that the Offeror asserts will be furnished to the Government with restrictions on access, use, modification, reproduction, release, performance, display, or disclosure. Offeror’s pre-award identification shall be submitted as an attachment to its offer and shall contain the following information:

(1) Statement of Assertion. Include the following statement: “The Offeror asserts for itself, or the persons identified below, that the Government’s rights to access, use, modify, reproduce, release, perform, display, or disclose only the following technical data or computer software should be restricted:”

(2) Identification of the technical data or computer software to be furnished with restrictions. For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process as specifically as possible (e.g., by referencing specific sections of the full proposal or specific technology or components). For computer software or computer software documentation, identify the software or documentation by specific name or module or item number.

(3) Detailed description of the asserted restrictions. For each of the technical data or computer software identified above in paragraph (2), identify the following information:

(i) Asserted rights. Identify the asserted rights for the technical data or computer…