Contractors are not required to respond to this announcement, but may do so at their own cost. The United States Government will not pay for information requested nor will it compensate any respondent for any cost incurred in developing information provided to the United States Government.
2.0 Background
Intel Support to Targeting application will enable the user to automatically migrate critical factors analysis regarding the threat in the form of critical capabilities, critical requirements, and critical vulnerabilities. This application supports both initial and refined formulation of High Payoff Target (HPT) and High Value Target (HVT) lists based on the threat's critical vulnerabilities, allowing for identification of Target Areas of Interest (TAIs) and key command decision points for supporting either threat interdiction or threat COA disruption. For details, reference supporting Draft Requirements Checklist available upon request.
3.0 White Paper and Supporting Documentation
The supporting documents for this RFI are marked as For Official Use Only (FOUO). To obtain a copy of the supporting documents (Draft Requirements Checklist), send an email with your organization name, address, and CAGE Code to [email protected].
Responses to this RFI are due no later than 1700 EDT on 25 OCT 2019 and must address the following information requests listed below in a white paper and requested attachments. The white paper shall not exceed 3 pages, not including cover sheet or cover letter, plus the Requirements Checklist and Rough Order of Magnitude (ROM) estimate.
Section 1: Draft Requirements Checklist
Upon request and receipt of the Draft Requirements Checklist, complete the Checklist Spreadsheet; annotating which requirements the proposed solution meets, a short (100 words or less) description of how the vendor product meets each item in the checklist, and a short (100 words or less) description of any operational history implementing with the Government or Commercial (Software in Production), and/or any history demonstrating the requirements to the Government.
Section 2: System Description
Describe the software packages and hardware platform that the proposed solution is hosted on, to include CPU, RAM, and Storage specifications. This information can be provided in the short white paper (3 pages or less).
Section 3: Commerciality
Describe how the proposed solution meets, or has the potential to meet through minor modifications, the Federal Acquisition Regulation (FAR) 2.101 Definition of a "commercial item." Describe if or how a solution can meet the FAR 2.101 definition of a commercial item if minor modifications are required, and discuss the time frame involved. This information can be provided in the short white paper (3 pages or less).
Section 4: Costs
(A) Provide a Rough Order of Magnitude (ROM) estimate of applicable costs for the proposed solution. The ROM should include licensing costs for the following: Term (with durations and price ranges), Annual subscription and/or Perpetual, at the quantities and number of users indicated, as well as Unlimited Enterprise and any cost for hardware and cloud service providers if any. If the proposed solution does not offer any of these licensing methods, provide one applicable to you. In addition, provide a Rough Order of Magnitude (ROM) estimate for follow-on maintenance/sustainment support (yearly).
(B) If applicable, provide a Rough Order of Magnitude (ROM) estimate of itemized costs for "Development" to meet each item marked "No" or "Partially" in the Checklist completed in Section 1. If "Development" are included with the license at no additional cost, state as such in ROM estimate.
(C) Provide a Rough Order of Magnitude (ROM) to support the Risk Management Framework (RMF) Accreditation of the proposed solution across the specified Networks. If RMF Accreditation costs are included with the license and/or maintenance/sustainment at no additional cost, clearly indicate so.
This notice is part of Government Market Research, a continuous process for obtaining the latest information on the commercial status of the industry. This RFI is for planning purposes, and does not constitute a commitment, implied or otherwise, that a procurement action will follow.
The Government will use the information submitted in response to this notice at its discretion and will not provide comments to any submission; however, the Government reserves the right to contact any respondent to this notice for the sole purpose of enhancing understanding of the notice submission. Information received will not be considered confidential/proprietary unless marked accordingly. Company proprietary data will be reviewed by Government employees and authorized representatives only. Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI, including any market research product demonstrations.
Responses to this RFI are to be marked For Official Use Only (FOUO) because of the Draft Requirements Checklist Spreadsheet and received no later than 1700 EDT 31 OCT 2019.
All interested parties shall respond in as clear manner as possible to each of the areas listed above. Information is preferred in soft-copy form in Microsoft Word/Excel and shall not exceed 10 pages. You may forward your responses via email address to: [email protected]; Subject Line: "Intel Apps RFI- Targeting". All information must be in writing or via email to above distribution email address; telephone requests for additional information will not be honored. You may forward responses to US Army, CCDC, C5ISR Center, I2WD, 6605 Surveillance Loop (Bldg. 6003) Aberdeen Proving Grounds, MD 21005, ATTN: FCDD-ISI-IT (Intel Apps RFI). Acknowledgement of receipt will be issued. If you choose to submit proprietary information, mark it accordingly.