RFI_-_PAI_Alerting_Service.docx
DOCX document 4 MB Posted
- Attached to
- Publically Available Information Federal contract opportunity
- Solicitation number
- PAI001
About this file
This Request for Information solicits information from contractors regarding their ability to provide a solution to evaluate publicly available information in real time and provide alerts to users based on emerging global events and threats. Respondents are to provide details on their capabilities to scale to an enterprise DoD capability, deliver web and mobile applications with email alerts, tailor the system for indications and warnings and force protection, utilize multiple global information sources, and integrate with other systems. Responses in the form of a white paper are due by May 10, 2019 and are to be emailed to the points of contact listed, with proprietary information clearly marked. The government may meet with potential offerors to clarify capabilities. This pre-solicitation opportunity is being conducted by the Department of the Air Force Headquarters District Washington under solicitation number PAI001 for a publically available information solution.
The RFI - PAI Alerting System
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFI_PIA001_-_QA.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
REQUEST FOR INFORMATION
AF A2/6 ISR Operations / Headquarters U.S. Air Force
1.0 Description
The Department of Defense (DoD) as directed by the Office of the Under Secretary of Defense for Intelligence (OUSD(I)) requires a solution to evaluate publicly available information (PAI) in real time, in order to provide increased situational awareness, force protection, and Indications and Warnings (I&W) to Combatant Commands and Military Services on global events. The solution should leverage a variety of publicly available sources, evaluate content to detect emerging events and threats as they are developing, and push alerts to users based on user-defined areas and topics of interest, such as threats to US Forces (i.e., Force Protection, terrorist events, disaster relief, etc.) and event geolocation, both in CONUS and OCONUS. Solution must be capable of distributing alerts in near real-time via email, web-based applications, and mobile platforms.
1.2 THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Air Force is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it is the responsibility of the potential offerors to monitor this site and/or other resources for additional information pertaining to this requirement.
2.0 Background
Information and the first indication of a situation is often available quicker and in more abundance through publicly available means than through defense only channels. The early receipt of information provides commanders and DoD member’s additional decision space which can be imperative in the protection of forces and assets as well as enable them to tip and cue additional assets or take additional actions.
3.0 Requested Information
3.1 Interested contractors are requested to respond to this RFI with the following information:
3.1.1. Extent of the Contractor’s ability to scale to a DoD enterprise capability (3.2 million – access, data sharing, data citation)
3.1.2. Extent of the Contractor’s ability to provide web based and mobile applications, with email alerts.
3.1.3. Extent of Contractor’s ability to provide an application with an indications and warning/force protection alert focus.
3.1.4. Extent of the Contractor’s ability to provide a real-time push vs pull system user interface.
3.1.5. Extent of the Contractor’s ability to use multiple, global sources of publicly available information to create alerts.
3.1.6. Extent of the Contractor’s ability to provide an application requiring little to no training for users to learn how to use, and to provide a periodic, in-person training if/when required.
3.1.7. Extent of the Contractor’s ability to provide a training application to optimize user proficiency in preparation for use in the real-world.
3.1.8. Extent of the Contractor’s ability to provide a forcing function that ensures DoD-specific guidance is met before accessing an account, and restrict access to the application if the requirement is not met.
3.1.9. Extent of the Contractor’s ability to tailor the application to multiple, diverse mission sets.
3.1.10. Extent of the Contractor’s ability to provide an assessment of the veracity of the sources used to provide the alerts and identify sources that are from bot accounts.
3.1.11. Extent of the Contractor’s ability to provide a low-bandwidth capability for shipboard/degraded communications use.
3.1.12. Extent of the Contractor’s ability to provide an application programming interface (API) to link directly to other systems.
3.1.13. Extent of the contractor’s ability to provide an application that allows a user to define a route on a map and provide alerts along that route.
3.1.14. Extent of the contractor’s ability to confirm compliance with the terms of service for its data providers.
3.1.1.5 Extent of relevant and recent Past Performance Information (PPI) to substantiate capability to perform requirement (consider scope and ability to manage).
3.1.1.6 Extent of how contractor plans to integrate into the requirement, as the prime contractor, a sub-contractor, or via Joint Venture/Teaming arrangement.
4.0 Responses
4.1 Interested parties are requested to respond to this RFI with a white paper.
4.2. Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum:
4.2.1. Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact.
4.2.2. Recommended contracting strategy – Commercial, Non Commercial, etc
4.2.3. The North American Industry Classification System (NAICS) code is 541511 Custom Computer Programming Services. If applicable, please state contractor’s Business size specifically its small business and socio-economic categories, as it pertains to the designated NAICS (541511) for this acquisition.
4.2.4 The facility security clearance of the offeror, if applicable.
4.3 White papers in Microsoft Word for Office 2013 compatible format are due no later than, 10 May, 2019, 12:00 EST. Responses shall be limited to 4 pages for Section 2 and submitted via e-mail only to settima.m.harton.ctr@mail.mil and margaret.santos.civ@mail.mil. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned.
4.3.1 The Freedom of Information Act (FOIA) and its amendments have resulted in an increasing number of requests from outside the Government for copies of contract qualifications and proposals submitted to federal agencies. If you submit a response and you believe it to contain information that should be withheld from such requestors under FOIA on the grounds it contains “trade secrets and commercial or financial information” [5 USC§552(b)(4)], you should mark the submission in the following manner:
4.3.1.1 The following notice should be placed on the title page: “Some parts of this document, as identified on individual pages, are considered by the submitter to be privileged or confidential trade secrets or commercial or financial information not subject to mandatory disclosure under the Freedom of Information Act. Material considered privileged or confidential on such grounds is contained on page(s) _____.”
4.3.1.2 Each individual item considered privileged or confidential under FOIA should be marked with the following notice: “The data or information is considered confidential or privileged, and is not subject to mandatory disclosure under the Freedom of Information Act.”
5.0 Industry Discussions
Government may or may not choose to meet with potential offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks.
6.0 Questions
Questions regarding this announcement shall be submitted in writing by e-mail to the above contacts. Verbal questions will NOT be accepted. Questions will be answered via FedBizOpps post to this RFI. Accordingly, questions and answers shall NOT contain proprietary or classified information. All questions received by 4:00pm, 29 Apr 18 will be answered, questions received after this date may be answered.
7.0 Summary
THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can support the DoD as described in this RFI. The information provided in the RFI is subject to change and is not binding on the Government. The Air Force has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.
File details come from the government source that posted it. Updated .