DoD_RIF_2017_Amendment_0002_20170426.docx

DoD Rapid Innovation Fund FY 2017 – Amendment 0002

Solicitation Number: HQ0034-17-BAA-RIF-0001 The purpose of Amendment 0002 to the DoD Rapid Innovation Fund FY2017 Broad Agency Announcement, HQ0034-17-BAA-RIF-0001 is to provide answers to submitted questions and make changes [corrections] to the solicitation. The final cut-off date to submit questions and have a response provided in an amendment to the BAA is Friday, April 28, 2017.

General Questions & Answers:

Q1) The instructions say: Headers: The offeror’s name and applicable requirement number shall be in the header of each page. The header may be included in the one-inch margins … Pages shall be numbered consecutively. Can I put the page numbers in the headers along with the other required header information (also within that 1” margin)?

A1) Please adhere to the instructions under Section 9.5. White Paper Submissions, under this BAA.

Q2) I wanted to refer the reader to our website and where there are videos with more information, should the reader want to find out more about our company and applicable projects. Is that allowed?

A2) The White Papers instructions does not restrict you from referring to your company website in your submission, but please ensure your submission adequately address all instructions and guidance provided in the BAA.

Q3) If an interested company submits a white paper prior to the submission deadline and Q&A’s are released that affect the response, can an updated submission be provided so long as it is prior to the closing date/time?

A3) Yes you may submit an updated white paper if answers to queries affect your submittal prior to the closing date/time. Please ensure you notify us when doing so as we can help you to facilitate.

Q4) Is it relevant to FY2017 RIF to submit white paper on the development of breast cancer vaccine?

A4) White-papers are to address the topics/requirements in the published BAA. There are no “open” or “other” topic areas in the FY2017 RIF BAA.

Q5) The instructions for the technical description include the following “1. Contribution to the Requirement: Provide a high-level project overview describing how (3-5 sentence description) this contribution addresses one or more of the goals listed below”, my question is, if my white paper addresses all 5 of the goals, am I limited to 3-5 sentences total, or is it 3-4 sentences per goal?

A5) Use as much of your three page white paper limit as you think you need for this portion. I’ve seen as little as three sentences and as much as the whole first page. It’s your paper.

Solicitation – Annex Changes Within Section 13.2 Department of the Army Annex:

The following new requirement has been added:

Requirement #: ARMY-FY17-44-CSCSS06 Title: Active Blast Mitigation System (ABMS) Integration to Tactical or Combat Vehicles Military System or Acquisition Customer: Various PEO CS & CSS PMs Description: An Active Blast Mitigation System (ABMS) is a system that automatically detects an underbody/IED threat as it occurs and rapidly reacts by signaling countermeasures to autonomously protect vehicle occupants and other sensitive equipment. This new technology attempts to neutralize the impulse introduced from a threat by initiating a counter impulse that will minimize impulse experienced. In order to advance the TRL to 8/9 further verifications are required including safety, integration feasibility to the existing fleet, and durability. This effort will require those verifications to be executed on a fielded tactical or combat vehicles (such as Stryker, JLTV, or MATV). Several Project Managers (PMs), such as PM Stryker, PM Mine Resistant Ambush Protected (MRAP), PM Joint Light Tactical Vehicles (JLTV), and PM Transportation Systems (TS), are very interested in the maturation of ABMS as a means to protect vehicle occupants in hostile environments on new and existing vehicles while maintaining mobility. The objective of this effort is to provide individual platform PMs with a ready solution to mitigate underbelly IED and mine blast events for future Force Protection. There is a need to mature this technology, demonstrate its effectiveness and ability to better protect Soldiers on military vehicles, and develop documentation (performance specification and technical data package) for acquisition for Force Protection needs.

Technical POC : Pat Griffin, 586-459-7107, patrick.r.griffin.civ@mail.mil

Within Section 13.3 Department of the Navy (DoN) Annex:

Amend Requirement # FY16-DoN-RIF-ANP-03, as follows:

Requirement #: FY16-DoN-RIF-ANP-03 Title: Development of the Additive Manufacturing (AM) Technology Military System or Acquisition Program Customer: All Naval Programs Description: Additive manufacturing has the potential to increase readiness and improve maintenance and sustainment operations through reducing long lead times and eliminating obsolescence related issues. Furthermore, the technology enables improvements to current systems (e.g., light weighting, part count reduction, and increase system performance) through designs that are not possible by conventional manufacturing techniques. However, for the technology to transition from indirect uses to efficiently producing qualified end use parts several technology barriers need to be overcome.

(1) Non-destructive evaluation techniques need to be developed to allow the inexpensive evaluation of components produced through additive manufacturing. Correlations also need to be drawn between the detected defects and the corresponding material properties of the component.

(2) Large area additive manufacturing techniques need to be developed to allow the benefits of AM to a larger number of components. To date popular AM techniques are either limited in size or require extensive post processing for acceptable surface finishes. Techniques that allow much larger components to be produced with minimal post processing are desired.

(3) A large scale data storage and management infrastructure that will enable the storage, access and transfer of AM related material property data across multiple Department of Navy entities is needed. This will enable the naval AM community to maintain, manage, and verifiably retrieve the large amounts of material property data and more rapidly produce AM components with confidence in final material properties.

(4) Cybersecurity methodologies are desired that ensure data transferred between naval networks and AM equipment are safe and secure. DON desires methodologies that allow networked AM machine access while ensuring cybersecurity requirements are met. This will necessitate an effort to establish a fully integrated and scalable data architecture, leveraging user authentication and configuration management techniques to ensure data integrity is securely managed in transit and at rest throughout the AM process.

(5) Supporting data access tools are required with analytical capability to optimize selection of viable families of AM candidate parts without requiring the burden of manual item-by-item review. The solution should also include analytical capabilities to effectively manage product technical and logistics information and provide users with substantive assessments on an item’s suitability to AM production.

(6) Smart workflow management processing that will assess required production workloads and will optimize and distribute AM jobs. The processing of workloads will leverage smartgrid technologies to assess and distribute desired workloads based on user defined criteria such as priority, materials, and urgency.

Technical POC: Ben Bouffard, Benjamin.bouffard@navy.mil, 301-227-5135

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

The following new requirements have been added:

Chief Information Officer / Defense Information Systems Agency (CIO / DISA) Requirement #: CIO_DISA-17-BAA-RIF-0004 Title: Browser Isolation Military System or Acquisition Customer: DISA Description: The vast amount of threats against the DoD come from a user's interaction with the internet via a browser. The DoD needs a different approach to the way in which end user's browsers interact with the Internet. The ability to isolate a user's browser activity from the DoDIN could dramatically change the way that the DoD defends its networks. The DoD is seeking a solution that hosts a user's browsing session in a commercial data center and allows the user to interact with the browser through a secure video stream. This service shall also allow management of browsing activity and capability delivered to the end user. The technical solution must demonstrate effectiveness, reliability, and scalability.

Technical POC: Steve Wallace, 301-225-7018, stephen.m.wallace24.civ@mail.mil; Erin Maultsby, 301-225-9451, erin.j.maultsby.civ@mail.mil Requirement #: CIO_DISA-17-BAA-RIF-0005 Title: Identity Access Management (IdAM) Military System or Acquisition Customer: DISA Description: The U.S. federal government has widely adopted the use of common access cards (CACs) or personal identity verification (PIV) coupled with primary key infrastructure (PKI). This approach employs two-factor authentication involving something the user possesses (i.e., CAC/PIV) and something the user knows via a personal identification number (PIN). Unfortunately, the complexity and cost of this system has prevented its adoption in mainstream business applications.

Fast Identity Online (FIDO), the world’s largest ecosystem for standards-based, interoperable authentication produces technical specifications that define a common interface for user authentication on a client device (e.g., smartphone) through biometrics, PINs, and two-factor methods. FIDO protocols are based on public key cryptography and are advertised as being strongly resistant to phishing attacks. FIDO essentially employs PKI without the complex and costly infrastructure component.

DISA seeks to determine of the viability of FIDO implementation and use within the DoD information technology infrastructure. It is proposed that FIDO standards and technologies be examined as a potential alternative to DoD PKI. DISA is currently scrutinizing authentication techniques such as derived credentials to facilitate greater ease in mobility device use. FIDO standards and technologies have been developed for the same purpose. Thus, investigation of FIDO standards/technologies in parallel with derived credential development would provide DoD leadership greater knowledge of authentication innovation within both the commercial and government sectors.

Technical POC: Steve Wallace, 301-225-7018, stephen.m.wallace24.civ@mail.mil; Joseph Kovasic, 301-225-9443, joseph.kovacic.civ@mail.mil; Erin Maultsby, 301-225-9451, erin.j.maultsby.civ@mail.mil

U.S. Special Operations Command (USSOCOM) Amend SOCOM Requirement #1, as follows:

Requirement #: SOCOM-17-BAA-RIF-0001 Technical POC has added: Joel Fritz, joel.fritz@socom.mil, 813-826-7290

DOD Rapid Innovation Fund – Amendment 0002 1