Attachment 1 - RFI Response Form Final.docx

RFI #24-IS-CM-MONITORING

Attachment 1 – RFI Response Form I. Company and Solution Overview Section

1. Company Information:

a. Company Name:

b. Company Address:

c. Company Website:

d. Company Point of Contact Information:

i. Name:

ii. Email:

iii. Phone:

e. SAM.gov Unique Entity Identifier:

f. North American Industry Classification Standard (NAICS) codes your company operates under that are applicable to this requirement:

g. Small Business Status:

h. Brief Company Overview:

i. List of Federal Government Clients Served with Similar Requirements:

2. Is your company and solution on any General Services Administration (GSA) federal supply schedules? If so, provide the following information:

a. GSA Contract Number:

b. Federal Supply Schedule:

3. Is your company and solution available on any other governmentwide contracts? If so, provide the following information:

a. Name of the Contract Vehicle(s) (NASA SEWP, OASIS, etc.):

b. Contract Number(s):

4. One Paragraph Executive Summary of Your Solution that Meets the RFI Requirements:

II. Answers to RFI Requirements A. Required Features/Functions:

(Please respond with Yes or No.)

Additional Relevant Information Related to This Feature/Function

(Please keep response brief; may be left blank.)

R1 - The source must have a capability to set up bulk alerting and monitoring without personnel having to manually run the searches each time.

R2 - The source must have the capability to monitor for risk events such as, changes in company ownership, legal structure, management, address, and Foreign Ownership, Control, or Influence (FOCI). The source must also have the capability to monitor for unreported mergers/acquisitions, company financial issues (bankruptcy, insolvency, unpaid debt), cyber breaches, criminal activity, sanctions, etc.

R3 - The source must be able to ingest DCSA’s list of approximately 15,000 facilities and their seed data, then return results on current issues and monitor that information for changes.

R4 - The source must be equipped to return monitoring results on a daily, weekly, or monthly basis.

R5 - The monitoring results must be returned to program personnel via Excel or .csv file.

R6 - The monitoring results must highlight keywords used to match article to relevant risk event, as well as provide a one or two sentence highlight (snippet) of the article or risk event.

R7 - The monitoring results must trace back to the originating location for the alert.

R8 - Monitoring results must have duplicates removed so that the same information is not reported multiple days, weeks, or months in a row. For example, information (alert) picked up from major news outlet is not repeated the following week when the same information is released by smaller outlets.

R-9 - The software must allow program personnel to update the list of monitored facilities on a daily or weekly basis as they are added/removed from the NISP.

B. Desired Features/Functions:

(Please Respond with Yes or No)

Additional Relevant Information Related to this Feature/Function (Please keep response brief; may be left blank.)

D1 - API Connection. As the program builds out a bridge solution for the alerts, the ability to connect to the software via an application programming interface (API) to assist with ingesting and assigning alerts is desired.

D2 - Keyword and Category Modification. The ability to add, modify, and remove key words and categories as needed is desired.

D3 - Comprehensive Analysis Report. The ability to have pull-out analysis and reports of specific alerts relevant to the mission is desired. This may be performed by a company data scientist, analyst, or other means.

III. Additional Information

1. Proposed NAICS Codes and Feedback:

2. Price (Rough Order of Magnitude) Estimate:

3. Feedback/Suggestions: