W911W4-19-R-9000_-__2019_INSCOM_RFI_CALL_FOR_WHITE_PAPERS.pdf

Request for the Submission of White Papers for INSCOM Technology Needs Solicitation Number: W911W4‐19‐R‐9000 Agency: Department of the Army Office: Army Contracting Command Location: ACC ‐ WRN ‐ INSCOM (W911W4)

Notice Type:

Special Notice Posted Date:

April 16, 2019 Response Date:

May 31 2019 11:59 pm Eastern Archiving Policy:

Manual Archive Archive Date:

Original Set Aside:

N/A Set Aside:

N/A Classification Code: D ‐‐ Information Technology services, including telecommunications services NAICS Code: 541 ‐‐ Professional, Scientific, and Technical Services/541330 ‐‐ Engineering Services

Synopsis:

Added: April 16, 2019 pm Solicitation Number: W911W4‐19‐R‐9000 Notice Type: Special Notice‐Request for white papers Original Set Aside: N/A Set Aside: N/A Classification Code: D ‐‐ Information Technology services, including telecommunications services NAICS Code: 541 ‐‐ Professional, Scientific, and Technical Services/541330 ‐‐ Engineering Services Synopsis: Request for the submission of White Papers for INSCOM Technology Needs THIS IS A REQUEST FOR THE SUBMISSION OF WHITE PAPERS (WP) ONLY. Responses to this notice will be used by the Government to make appropriate acquisition decisions. This notice is for planning purposes only, and does not constitute an Invitation for Bid, Request for Proposal, Solicitation, and Request for Quote, or an indication that the Government will contract for the items contained in this notice. This request is not to be construed as a commitment on the part of the Government to award a contract, nor does the Government intend to pay for any information submitted as a result of this request. The Government will not reimburse respondents for any cost associated with submission of the information being requested or reimburse expenses incurred to interested parties for responses to this notice or any follow‐up information requests. No telephone calls will be accepted requesting a bid package or solicitation. There is no bid package or solicitation. All interested sources must respond to any future solicitation announcements separately from responses to this request for the submission of White Papers.

The Intelligence and Security Command (INSCOM) executes mission command of operational intelligence and security forces; conducts and synchronizes worldwide multi‐discipline and all‐source intelligence and security operations; delivers linguist support and intelligence‐related advanced skills training, acquisition support, logistics, communications, and other specialized capabilities in support of Army, Joint, and Coalition Commands and the U.S. Intelligence Community.

1. Focus Areas and Requirements:

INSCOM has identified areas for which we are requesting White Papers from Industry on mature Commercial Off‐The‐Shelf (COTS) solutions relevant to the following Focus Areas and requirements:

0001: Open Source Intelligence (OSINT):

a. Software as a service capability which can recognize text within an image, capture and classify/categorize the content and provide an interface to query related images. Shall ingest multiple image formats, resolution and file sizes without any degradation to the original image as well as process and display any available Exchangeable Image File Format (EXIF) data. Must have the ability to perform keyword search against all ingested content. Must be able to process industry standard image formats, to include (but not limited to), JPEG, TIFF, GIF, EPS, PNG.

b. Software as a Service (SAAS) based capability which provides an interactive and visual architecture supporting the discovery of publicly available information through automated queries against multiple data sources while analyzing real‐world relationships between entities.

The proposed tool will identify relationships by querying sources, extracting metadata and displaying information on a node‐based graph suitable for link analysis; depicting the link between names, email addresses, aliases, groups, companies, organizations, websites, domains, domain name system (DNS) names, netblocks, IP addresses, affiliations, documents and files.

The node‐based graph shall be exportable to CSV, XLS, XLSX, PDF and image formats. The tool shall be capable of ingesting CSV, XLS and XLSX files to aid in building queries.

c. Capability for automation support to OSINT activities auditing. Specifically, provide technical solutions to automatically translate percent encoded characters to original language or character set. Shall provide an automated solution to acquire and substitute destination addresses for shortened URL in audit logs. The solutions may be provided as a supplement to existing auditing software, from within a managed attribution enclave, or as part of proposal for new auditing tools. In any of these cases, however, solutions must not broadcast large batches of OSINT audit data to external entities.

0002: Management Systems

a. Human Intelligence (HUMINT) operations requirements management system that incorporates latent sematic indexing (LSI) capabilities and is accredited for use on JWICS and SIPR and is Intelligence Community Information Technology Enterprise (ICITE) compliant. Must scale to Army wide use.

b. Capability to monitor intelligence operational facility status around the globe in real time to implement condition based maintenance and improve predictability, outage response times and readiness.

0003: Language Translation:

a. Software as service video translation capability which can ingest video from multiple sources to include direct upload, URL, and real‐time broadcast television. The capability will process the spoken language into transcribed text in the source language and also transcribed and translated English. The transcribed and translated content shall be presented on screen and in sync, with the spoken word represented via underline or highlight, as the video plays through.

The content shall be exportable in whole and segment with the translated words subtitled on screen. Must perform keyword search against all ingested content. Quality shall be equal to or better than commercial free solutions.

0004: Cross Domain:

a. NSA Raise the Bar (RTB) compliant high speed cross domain solution to move terabytes of unclassified commercial imagery, OSINT, and other geospatial data to Government networks.

Also capable of near real time transfer of diverse data types, such as full motion video (FMV), and structured between SIPR, JWICS and coalition networks.

0005: Collection and Communication:

a. Capability for transmitting secure voice and data via High Frequency (HF) channel bi‐ directionally at 1.5Mbps. Must arrive with transmit/receive/processing components. Have the ability to connect to the Army Tactical Network and operate across NIPR and SIPR. Must support 6 simultaneous users per each defined network. One soldier must be able to set up and tear down within 20 minutes. Each component will require no more than a two soldier lift.

Battery back‐up will supply power for 6 hours of use. Must be capable of operating on the move.

b. Mobile satellite communication (SATCOM) capability with a minimum transmit/receive capacity of 10Gbs.

c. Light weight, mobile, and scalable SATCOM system that can be rapidly set‐up and operational in a minimal amount of time by 4 or less soldiers.

0006: Other

a. Artificial Intelligence / Machine Learning that accelerate processes to 1) Determine threat courses of action, 2) Assess environmental effects on operations, 3) Prepare and produce intelligence reports – all INTs, 4) Perform situation development, 5) Identify and characterize sensor data.

b. Capability or capabilities to counter or reduce the effects of GPS jamming on airborne and ground systems.

c. Entity resolution software for reports and unstructured documents that integrates into an ArcGIS architecture.

d. Airborne multi‐function display, with a communications security (COMSEC) port, capable of loading mapping data. Display can be turned on/off with a simple switch allowing a classified overlay providing mapping data in parallel with Federal Aviation Administration (FAA), International Civil Aviation Organization (ICAO), and Jeppesen mapping. System can be zeroized and reloaded as needed.

e. Data fabric that: 1) can store and correlate tabular, geospatial, imagery, audio/video, graph data as well as unstructured documents, 2) has tools to automatically gather information from multiple points, 3) has automated loading of data into the end data store with auditing, 4) has automated application of rules or functions to the extracted data in order to prepare for loading into the end target, 5) is compatible with the intelligence community (IC) and Department of Defense (DoD) existing Identity and Access management (IdAM) solutions.

2. Use of Vulcan for INSCOM White Paper Submissions Vulcan is a web interface and automated tech scouting tool to streamline efforts across the enterprise to discover and enable the sharing of vendor technologies within the Special Operations Forces (SOF)/DoD enterprise. INSCOM will use Vulcan to support this event.

Please ensure that you are using the Vulcan interface for your submittal. To do so, sign up and/or log in to Vulcan at https://www.vulcan‐SOF.com. You must use your official organizational email when registering. It is recommended that you watch the “Creating a Scout Card in Vulcan” video in the Vulcan TV area of the site for useful tips on submitting a strong technology profile. Follow the below instructions for submitting a response. Please ensure that all responses are at the “Unclassified” level.

a. Once logged in to Vulcan, navigate to “Calls” in the top menu.

b. Vendors desiring to submit White Papers in response to the INSCOM Capability Needs listed in Paragraph 1 above MUST click on the call titled: “2019 INSCOM Industry Day RFI for White Papers”.

c. The submission page for the RFI will allow you to either submit a technology that your organization has already uploaded to Vulcan OR a new product/technology that you can upload as a Vulcan “Scout Card”. However, note that you MUST upload your associated White Paper to any scout card that you submit. If you are submitting a new scout card, you will be asked to:

1) Enter the title of the solution described in your White Paper.

2) Provide the contact information of the person(s) who represent your solution.

3) Tag your scout card with one or more areas of interest (type into the Vulcan Tags field to select from a list).

4) Be direct and concise in describing your technology and what sets it apart (differentiators).

5) Indicate your TRL (and other readiness levels if applicable).

6) Provide optional Specifications and User information.

7) Upload pictures (.jpg, .png, gif file size not to exceed 5MB) and [if available] a public video link (YouTube or Vimeo).

8) Upload your White Paper (file size not to exceed 5MB) and follow the requirement instructions in the document section of the form. You may upload additional supporting documents if available.

d. Note that the link may be used to upload multiple submissions (different technology products) if you elect to submit more than one White Paper (i.e., you will create a Vulcan Scout Card for each and attach a different White Paper to each Vulcan Scout Card that you submit). You should NOT create duplicates of the technology scout cards that may already have been created in the system by your organization. In this case, just update the existing scout card and attach the requisite White Paper as you submit to the RFI.

e. If you experience any problems with the Vulcan‐SOF site or have any issues uploading your inputs as prescribed above, contact the Vulcan Help desk at contact@vulcan‐sof.com.

f. Note that you can continuously edit your technology scout cards at any point up until the RFI deadline. Do NOT wait until the deadline to sign‐up for a Vulcan account and manage your input. It is highly recommended you register and become familiar with Vulcan well in advance of the RFI close date.

3. White Paper Submission Guidelines

a. Submitted White Papers are discouraged from being marketing in nature or previously submitted ideas. INSCOM is looking for true innovative, out‐of‐the‐box thinking, conceptual approaches, and ideas with respect to the focus areas listed. White Papers must be in the following format:

1) All White Paper submissions must be UNCLASSIFIED.

2) No more than twenty pages in length, single spaced in Microsoft Word or .pdf compatible format including graphs, pictures, and analyses. Documents longer than 20 pages will not be considered in their entirety. White Paper Data Sheet, Cover page and table of contents, if included, will not be included in the page count.

3) Page size shall be 8.5x 11 inches; Margins one inch, font size shall be 12 point, legible for tables and figures.

4) The White Paper Data Sheet (Appendix A) must be filled out and attached clearly outlining which INSCOM Capability Need(s) the white paper pertains to. This ensures adequate and timely consideration.

b. Include the following information at minimum:

1) Clearly identify the functional and/or cost reduction benefits of your product or concept.

2) Identify the technical and programmatic risks you foresee in completing (or adapting) your design and include your program plan, timeline, testing, and current design level effort.

3) We are looking for mature technologies that would be available for operational environment testing or qualification (i.e., TRL 7‐9). Empirical, laboratory, or field test data to support the maturity of the proposed technology should be included.

4) If available, please include a schedule and cost estimate in your white paper.

NOTE: 1) Do not send .ZIP files; 2) Do not send password protected files.

4. White Paper Due Date, Information and POCs:

All White Papers must be submitted through Vulcan no later than the RFI close date. Exceptions for missing the submission date due to issues with Vulcan will not be granted.

The initial response will undergo a technical assessment that may be followed by requests for clarifications or an invitation for oral presentations/demonstration, with a desired end state of vendor participation in Government conducted technology assessments. This is in no manner an opportunity to submit a proposal for research and development funding.

Responses will be reviewed by both Government and Contractor personnel. Contractor personnel provide Engineering Technical Assistance (ETA) support, and are under a Non‐Disclosure Agreement.

All submissions will be acknowledged as received by INSCOM, and then staffed to requiring activities with corresponding capability gaps.

Submissions are due on 31 May 2019 by 11:59 pm Eastern Daylight Time (EDT). Early submissions are highly encouraged.

Point of Contact:

Technical Points of Contact(s): Stephen Woolwine, Email: usarmy.belvoir.inscom.mbx.g7‐ techassess@mail.mil, Contracting Officer: Michelle Miller Contracting Office Address: Attn: IAPC, 8825 Beulah Street, Fort Belvoir, Virginia 22060‐5246, United

States

APPENDIX A - White Paper DATA SHEET

This data sheet must be completed and submitted with the White Paper. Do not modify the template and please include a response for each item, leaving none blank.

Solicitation Number:

Company: Product Name:

1. Short Product Description:

2. Focus Area / Focus Area Details (List all Focus Areas and sub-categories FROM THE RFI that apply to the solution proposed in the White Paper) as shown in the below example.

EXAMPLE:

0001: OSINT:

a. Software as a service capability which can recognize text within an image, capture and classify/categorize the content and provide an interface to query related images. Shall ingest multiple image formats, resolution and file sizes without any degradation to the original image as well as process and display any available EXIF data. Must have the ability to perform keyword search against all ingested content. Must be able to process industry standard image formats, to include, but not limited to, (JPEG, TIFF, GIF, EPS, and PNG).

0005: Collection and Communication:

a. A Light weight, mobile, and scalable SATCOM system that can be rapidly set‐up and operational in a minimal amount of time by 4 or less soldiers.

3. Technical Maturity of Capability (Technology Readiness Level (TRL) ): See TRL descriptions at: https://www.army.mil/e2/c/downloads/404585.pdf

4. List current DOD/Intel customers:

5. Intellectual Property Rights (Select One and/or explain): Restrictive Limited Unlimited

6. Existing Information Assurance/Cyber Security Accreditations

Solution DOES / DOES NOT have an Authorization to Operate (ATO) Expire Date:

Comments:

Solution DOES / DOES NOT have an Assess Only Authorization Comments:

Solution DOES / DOES NOT have any other Government recognized evaluations (i.e. EAL, Common Criteria, DO160, MILSPEC ratings) Comments:

7. Licensing (to include licensing model/per unit cost)

8. Will you provide no-cost trial licenses for the 30-90 Assessment Evaluation Period if selected as an assessment candidate?

9. Training Requirement:

Type(s) Available: Duration of Training:

10. Contact Information: (Please list Primary and Secondary POC) (Individuals that have the authority and knowledge to discuss responses with Government representatives)

Primary:

Name:

Email:

Phone:

Secondary:

Name:

Email:

Phone: