RFI_TSC_NoSQL_11.6.docx

FEDERAL BUREAU OF INVESTIGATION

FINANCE AND FACILITIES DIVISION | PROCUREMENT SECTION

REQUEST FOR INFORMATION (RFI) TEMPLATE

REQUEST FOR INFORMATION (RFI)

TSC No SQL Database Requirement 11/1/2025

FEDERAL BUREAU OF INVESTIGATION

FINANCE AND FACILITIES DIVISION | PROCUREMENT SECTION

REQUEST FOR INFORMATION (RFI) TEMPLATE

DISCLAIMER:

THIS NOTICE IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT A REQUEST FOR PROPOSAL OR QUOTE. IT DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY.

INTRODUCTION

Responses to this RFI may be used to formulate final requirements and/or to identify qualified vendors capable of meeting those requirements. The description below outlines preliminary requirements envisioned for the Terrorist Screening Center (TSC) No Structured Query Language (NoSQL) Database Requirement.

The information gathered may be used to formulate acquisition strategies for competitive solicitations.

BACKGROUND

The TSC conducts its screening mission through the development of technology initiatives for the watchlisting and encounters database that is shared with Federal, State, local and international law enforcement and national security partners.

To carry out its mission, the TSC requires a renewal of its NoSQL database environment. This software would be considered commercial, and this effort will not be consolidated with previous efforts. The NoSQL database software solution must allow the migration of information from a variety of sources to be integrated into one database platform.

NoSQL multimodal database software must be able to natively store JSON and XML files and support common programing languages such as Java / JavaScript, and C++. The database solution must be able to support atomic transactions, which is a key component to NoSQL data insertions. This provides more consistency when transactions leave the database in a valid state.

One of the primary pillars of the TSC mission is information sharing with domestic and international partners. Using this atomic transaction capability, the chosen database software can then support flexible replication (flexrep) of multiple data environments. Flexrep allows for transactions based on system priority to move data and keep systems in sync across applications and different classification enclaves, which is essential to the screening and vetting national security mission.

In addition to the critical atomic transactions and flexrep capabilities, the TSC also requires the following for its NoSQL database solution:

Mandatory Requirements

· Dynamic Business Rules for documents stored within the database (identifies what information will be sent to external facing applications and what information will be sent to downstream partners)

· Extract Transform and Load (ETL) Processes Business Rules for documents stored within the database (identifies what information will be sent to external facing applications and what information will be sent to downstream partners). Note: ETL is a key feature that allows for the transformation of data, to include ingests from external partners, making the information consumable by the TSC applications

· Geospatial visualization of data based on geo-coded data elements

· Export rules & export generation into multiple formats (JSON, XML, CSV, etc.)

· Ability to manage the storage and processing of up to 50 Terabytes of data

· Natively store in AWS Simple Storage Service (S3) using pointers to retrieve data

· Natively index data for Boolean-faceted searches

· Horizontally-scalable solution that is highly available and resilient to Availability Zone (AZ) failure

· Ability to separate data by storage speed and cost factors

· Ability to create relationships between data points - e.g. SPARQL query to retrieve and manipulate data stored in Resource Description Framework (RDF) format.

· Ability to use industry standard programming language

· Alert notifications based on changes in the data

· Ability to update data in bulk via a built-in mechanism

· Ability to separate binary and indexed / searchable documents Lastly, to comport with security requirements, FBI/TSC requires software vendors to be Federal Risk and Authorization Management Program (FedRAMP) rated High. This rating is based on the national security sensitivities of the TSC data, which is enforced by the Authorizing Official (AO). The FedRAMP rates Commercial off the Shelf (COTS) products.

Optional Requirements In addition to the No SQL database software, the TSC also is interested in commercial software solutions that can also provide search / query capabilities of up to 50 Terabytes of data with more specific requirements highlighted below pertaining to identity, single, and batched searches:

1. Identity Search Requirements

1. Identity Search solution can query various facet types including name, dob, citizenship, and system identifiers (two dimensional - type and value).

2. Identity Search can apply different search algorithms based on different facet types. For example, exact match for citizenship, date editing distance for dates of birth (DOB), etc.

1. DOB Search must be configurable (ex: +/- 5 years)

1. Certain facets should take into account typographic errors

3. Search solution’s name algorithm needs to be culturally aware to handle names from various countries and ethnicities based on full names. A full name can have several name tokens (i.e. full name typically consists of 4 or 5 name “tokens” for some cultures). Names could be misspelled and flipped (given name and surname are in wrong order).

a. Search algorithm should include fuzzy name search to aid misspelled names are found.

1. Search solution for locations should be able to match based on physical location. One scenario would be to search off AOR such as the DC area, which encompasses multiples states/major airports. Another example is being able to match locations that are physically the same or similar but may have changed names or be called different names (for example: Israel, Czech Republic, Swaziland).

1. Search solution should return a list of ranked search result based on search criteria and a threshold parameter. Each match result should have a normalized aggregate score.

1. Search solution needs to search about 15 million names, DOBs, and system identifiers (e.g. passports, driver license numbers).

1. There are about 2500-3000 adds, mods, deletes on identities daily. It needs to periodically (every 5 minutes) sync up with Search solution through an API.

1. Search solution should provide ability to monitor status of its cluster and check if it is in sync with the identity database and provide notifications if out of sync.

1. Search solution should provide ability to reconcile with the Identity database if they are out of sync.

1. Search solution should be able to accommodate and search against multiple search populations at the same time.

1. Search solution needs to be deployed in a highly available and scalable fashion on Cloud. Losing part of the cluster due to AZ failure can result in performance degradation but the search cluster needs to remain available for searches.

1. Search solution needs to scale linearly by adding extra nodes to the cluster. Autoscaling in/out based on threshold values would be preferable.

1. Preferred search solution should be a cloud native, that leverages managed services where possible to reduce footprint and cost.

1. Search solution should provide tuning parameters and different weighting options for search facet for system administrators.

1. Search solution should provide the ability to drill down to see each facet score given a match result.

1. Search solution should provide the ability to easily add new facet types/searchable fields.

1. Search solution should be index based. The index should be in memory and persist to disk to handle node failure.

1. Search solution must handle data profiles, which will be pre-set by system to determine what results can be returned.

1. Search solution should provide other government clients as references for this specific use (identity name search).

1. Search solution should provide quarterly releases/patches and must include remediation of vulnerabilities discovered during security scanning.

A. Single Search Requirements

1. User enters search criteria and a threshold on the UI and waits for the search result.

1. The search result is expected to return to the user in less than 3 seconds.

1. The match results are sorted based on the aggregated match scores.

B. Batch Search Requirements

1. User uploads a file with search criteria into the system and initiates the search.

1. User can set the max result size and threshold for search criteria.

1. Search runs in the background.

1. The UI periodically refreshes to display the batch search request status. Once the search is completed, the result file will be available to be downloaded.

1. Batch search should take a lower priority than single search. In other words, running a big batch search should not starve new single searches.

1. Multiple batch searches can be conducted with minimal performance degradation.

CONTRACTOR QUALIFICATIONS

This RFI is open to small and large businesses for market research only to request input from potential providers of No SQL database software solutions.

The Government would like to know which firms can provide the No SQL database software solutions for this contemplated requirement by identifying themselves and responding to this RFI. The Government requests the following information:

1. Company name and business size.

2. Provide evidence to show that your company can provide the requested services and/or products required (i.e. technical ability, personnel, and experience). Information provided shall be succinct and related to the requested information in this RFI. All submissions shall be unclassified.

3. Address whether your company has a GSA Schedule and if they are capable of providing these services on schedule. If able to provide the services on schedule, provide the schedule and SIN.

4. Details for how your product is packaged, outlining any special terms or limitations to licensing, access, and support. The details shall include rough order of magnitude pricing for provided capabilities, including a la carte pricing for add on that may be part of the provided solution.

5. Details and information identifying any code packaged as part of this product developed outside of the United States.

6. Any other assumptions, comments, concerns, and/or questions relating to the contemplated services.

Required Information:

Contractor Legal/DBA Name:

Address:

Point of Contact:

Telephone:

Email Address:

DUNS Number:

Cage Code:

Facility Clearance (if applicable):

Applicable NAICS Codes:

Standard Business Size:

GSA Schedule:

NASA SEWP Contract:

CONTEMPLATED REQUIREMENT

FBI's Terrorist Screening Center (TSC) Information Technology Unit is issuing this Request for Information (RFI) to:

· Gather industry information on the enclosed requirements.

· Request information on any industry changes or improvements that the FBI should consider when looking to achieve products and capabilities that meet requirements and are compatible with the commercial environment.

· Request information on potential barriers to obtaining solutions that meet objectives needed to accomplish stated requirements. The areas of interest for contemplated requirements and scenarios are addressed below.

DISCLAIMER and RESPONSES

THERE IS NO COMMITMENT BY THE GOVERNMENT TO ISSUE A SOLICITATION AS A RESULT OF THIS RFI. THIS IS BEING ISSUED SOLEY FOR INFORMATIONAL AND PLANNING PURPOSES AND DOES NOT CONSTITUTE A SOLICTIATION. IN ACCORDANCE WITH FAR 15.201(e), RESPONSES TO THIS NOTICE ARE NOT OFFERS AND CANNOT BE ACCEPTED BY THE GOVERNMENT TO FORM A BINDING CONTRACT. THIS IS NOT A REQUEST FOR PROPOSAL OR QUOTE. IT DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT AS A RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF RESPONSES TO THIS ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY.

WHAT SHOULD BE INCLUDED IN YOUR RESPONSE

1. All interested parties shall submit capability packages in response to this notice.

2. Do submit succinct, thoughtful responses to the requirements/questions listed in this RFI.

3. Do submit comments that address the FBI's requirements, assumptions, conditions or contemplated approaches to this future acquisition.

4. Do submit information and suggestions that may encourage new, different, or innovative approaches that would result in products, solutions, and direct savings to the FBI.

WHAT SHOULD NOT BE INCLUDED IN YOUR RESPONSE

1. Do not submit proposals or offers.

2. Do not submit past performance information or general descriptions of corporate experience.

3. Do not submit requests to be considered for award or to be notified of a future solicitation.

4. Do not submit requests to be added to a mailing list or distribution list.

5. Do not submit questions or comments not related to this RFI.

6. Do not respond via telephone.

RFI SUBMITTAL INSTRUCTIONS:

The Government requests response to this RFI to be submitted via electronic means to the POC outlined below. Any request for clarification to this RFI are due by 11/13/2024 Noon Eastern to ensure response. The Government reserves the right to respond to questions provided after the deadline. Formal responses are due by 11/27/2024 Noon Eastern. Each submission shall not exceed 25 pages in length, including cover page, table of contents, and any other information. Submit RFI Information via email to the attention of:

Contracting Point of Contact: Brandon James Email: bmjames@fbi.gov

image6.jpg image7.jpg image8.png