RIF_2016_Amendment_0001.pdf

DOD FY 16 Rapid Innovation Fund – Amendment 0001 1

DoD Rapid Innovation Fund FY 2016 – Amendment 0001

Solicitation Number: HQ0034-16-BAA-RIF-0001 The following answers are provided to the first round of submitted questions. The final cut-off date to submit questions and have a response provided is Friday, April 15, 2016. Questions submitted after April 15 are subject to the availability of personnel and may not be answered in a timely manner or at all.

** AF RIF Submission Website Announcement ** BAA paragraphs 9.4 and Section 13.4 provide instructions for submission of White Papers for Air Force requirements to their RIF submission website, http://www.AFRapidinnovationFund.com. Due to maintenance issues, the Air Force submission site is currently not available. The site is expected to be back on line not later than March 29, 2016. For specific questions, please contact Mr. John R. (JR) Smith, email:

john.r.smith346.ctr@mail.mil, phone: 571-256-0316.

General Questions & Answers:

Q1) Can you please explain the difference between HQ0034-16-BAA-RIF-0001A andHQ0034-16-

BAA-RIF-0001B? They look identical to me. DODRIF.COM only lists A, but both are listed on the Defense Innovation Marketplace website.

A1) There is no difference between FY2016 Rapid Innovation Fund Broad Agency

Announcement (BAA) HQ0034-16-BAA-RIF-0001A and HQ0034-16-BAA-RIF-0001B.

The BAA has two North American Industry Classification System (NAICS) codes for this announcement, 541712: Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology), and 541711: Research and Development in Biotechnology. Federal Business Opportunities only permits one NAICS code per solicitation/announcement, therefore we must post twice.

Q2) Are potential offerors and TPOCs allowed to meet while the solicitation is open, with the understanding that no specifics of the offerors approach to the topics will be discussed?

The purpose of such a meeting, from the offerors point of view, would be to make the TPOC aware of the offeror and its general capabilities, so that the offeror will not be at a competitive disadvantage to other organizations that are already known to the TPOC.

A2) Please see Section 6.2 of the BAA where it defines how offerors can communicate with

TPOCs. "Communication is limited to phones calls and emails."

Q3) Is it correct that any RIF contract "for work that derives from, extends, or logically concludes that firm's work under a prior SBIR funding agreement" will include DFARS 252.227-7018?

A3) The vendor should assert its SBIR data rights during the proposal submission phase. If the contracting officer determines that the proposed effort does derive, extend or logically conclude a prior SBIR effort, the contracting officer will include the clause.

Important Note: The following changes have been made to this solicitation since its release

— March 1, 2016.

http://www.afrapidinnovationfund.com/ mailto:john.r.smith346.ctr@mail.mil

DOD FY 16 Rapid Innovation Fund – Amendment 0001 2

Solicitation - Annex Text Changes

Within Section 13.2 Department of the Army Annex:

The following new requirement is added:

Requirement #: ARMY56-PEOCSCSS09 Title: Active Blast Mitigation for Tactical Vehicles Military System or Acquisition Program Customer: PM Transportation Systems Description: An active blast mitigation system is a system that is designed to counteract, or mitigate, underbody blast forces encountered on military vehicles thereby reducing and preventing injuries to mounted-Warfighters and damage to other vehicle systems. There is a need to mature this technology, integrate and demonstrate its effectiveness and ability to better protect Soldiers on Medium and Heavy Tactical Vehicles, and develop documentation (performance specification and technical data package) sufficient for system acquisition for future Force Protection needs.

Technical POC: Joe Keusch 586-282-8660, joseph.m.keusch.civ@mail.mil

Within Section 13.5 Office of the Secretary of Defense (OSD)/ Defense Agencies Annex:

Requirement #: ASDR&E-16-BAA-RIF-ARL-HPO-0001, Military System or Acquisition Customer and Description, has been changed to read:

Military System or Acquisition Customer: Numerous DoD Strike and Intelligence, Surveillance & Reconnaissance (ISR) applications (ACC/A5 Future ISR Branch or AF/A2) Description: The DoD seeks a demonstration of a multi-vehicle control station in which a single operator can supervise and control multiple Group 3-5 unmanned air vehicles. This technology should combine a human-centered approach to designing the interface, and a mission assessment approach to optimizing manpower usage. Unmanned systems have been, and will continue to be, utilized by the Air Force, Army, Navy, and Marine Corps as a force multiplier and a means to extend warfighter reach in contested environments. Manpower for unmanned vehicle operations, and the associated costs, has increased due to today's usage of these systems. Recent research using the government owned and developed Vigilant Spirit Control Station (VSCS) indicates that there are human-centered approaches to building a multi-vehicle control station that result in manageable cognitive workload for a single operator. Solutions should integrate Vigilant Spirit-type capabilities with proposed unmanned air vehicles for demonstration in operationally relevant simulations and/or flight tests utilizing emerging open architecture solutions.

Technical POC: Dr. Guy French, 937-713-7072, guy.french@us.af.mil mailto:joseph.m.keusch.civ@mail.mil mailto:guy.french@us.af.mil