FBI-RFI-26-DI-LPR.pdf

PDF 368 KB Posted

Attached to
License Plate Reader Data Tools
Solicitation number
FBI-RFI-26-DI-LPR
Issued by

About this file

This is a Request for Information (RFI) from the Federal Bureau of Investigation (FBI) seeking vendor-supported License Plate Reader (LPR) Data tools and services. The FBI's Directorate of Intelligence is looking for tools that collect Publicly Available Information (PAI) and/or Commercially Available Information (CAI) from the internet and LPR infrastructure. The RFI outlines extensive technical requirements, including mandatory capabilities such as a user-friendly GUI, robust system security, 508 compliance, and advanced features like artificial intelligence, geospatial search capabilities, image and video capture, and mobile device compatibility.

Key submission details include: responses are due by 5:00 PM ET on November 6, 2025, to be emailed to Joseph Spatafore (jspatafore@fbi.gov) in Microsoft Word or PDF format, not exceeding 15 pages. The FBI seeks US-based companies that provide actual LPR data tools (no resellers) with Software-as-a-Service (SaaS) delivery. Vendors must provide detailed information about their licensing models, pricing structures, support and maintenance, and technical capabilities. The RFI emphasizes that this is for market research and information gathering, with no guarantee of a future solicitation or contract award.

View the file

Other files

File Type Posted
RFI-LPR-Answers.xlsx XLSX spreadsheet

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

FEDERAL BUREAU OF INVESTIGATION

FINANCE AND FACILITIES DIVISION | PROCUREMENT SECTION

LICENSE PLATE READER DATA TOOLS

Attachment AS - Request for Information (RFI)

FBI-RFI-26-DI-LPR

Version 1.2 Page 1

REQUEST FOR INFORMATION (RFI)

LICENSE PLATE READER DATA

October 22, 2025

Information Technology Unit

REQUEST FOR INFORMATION (RFI) TEMPLATE

Version 1.2 Page 2

DISCLAIMER:

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.

INTRODUCTION

The United States Department of Justice (DOJ), Federal Bureau of Investigation (FBI), Directorate of Intelligence (DI), Information Technology Section (ITS) is seeking vendor-supported License Plate Reader (LPR) Data tools and services that collect Publicly Available

Information (PAI) and / or Commercially Available Information (CAI) from the internet and

LPR infrastructure, systems, and networks.

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 capabilities envisioned for the FBI’s License Plate Reader Data Tools Indefinite Delivery

Indefinite Quantity (IDIQ) contract, hereafter referred as LPR IDIQ. Responses to the RFI should include detailed information on potential software and products and how the FBI could

Version 1.2 Page 3 best implement and utilize them, as well as potential costs for implementation (e.g., licensing prices). The FBI may request demonstrations of proposed products and solutions after responses are received. The information gathered may be used to formulate acquisition strategies for competitive solicitations.

1.0 BACKGROUND

The Directorate of Intelligence (DI) of the FBI manages the Open-Source Intelligence (OSINT) tools acquisition, providing tools and training to assist Headquarters Divisions and Field Offices in conducting OSINT research and searches nationwide. The DI ensures that users have tools required to search for threats, subjects, victims, and investigative leads. The DI also ensures that users complete the applicable training to perform these searches in accordance with applicable federal laws, regulations, and policy.

The growing use of and advancements of LPR technology has enabled the capture of images of license plates and vehicles in multiple settings, environments, and geographic locations. With a vast and varied array of cameras, identifying threat-related data relevant to an authorized law enforcement purpose can be challenging. However, efficiently identifying, organizing, and analyzing lawfully collected publicly available and commercially available data is paramount to preventing, investigating, and defeating threats to our nation and American interests abroad.

Tools that capture such relevant information are important in helping the FBI solve the complexities of this multifaceted problem. At the same time, it is important that appropriate security and privacy safeguards are implemented to protect the privacy and civil liberties of individuals. The acquisition strategy is to provide multiple options for such LPR tools, to serve multiple geographic locations, investigative threat types and use cases, and meet the needs of a diverse user base in accordance with law, regulation, and policy.

Version 1.2 Page 4

1.1 TERMS:

Publicly Available Information (PAI):

Any information or data about an individual or group of individuals, including their devices or locations, that is made is accessible to the general public, governmental, or nongovernmental entities without any special permissions or qualifications.

Commercially Available Information (CAI):

Any information or data about an individual or group of individuals, including their devices or locations, that is made available or obtainable and sold, leased, or licensed to the general public, governmental, or nongovernmental entities. This CAI definition includes PAI, and hereafter shall be indicated as CAI to include both types of information.

2.0 PURPOSE

The FBI requests capability statements of professional services firms with expertise in LPR data and software to include publicly available and commercially available information platform offerings. The intent of this Request for Information (RFI) is to obtain information that will assist the FBI in determining the market for independent, professional firms that can provide LPR data with the capability to leverage analytics and provide data enrichment and context. There is a crucial need for accessible data sources to provide a diverse and reliable range of collections across multiple LPR camera networks, platforms, and collections. The ability to segment and customize data collection capabilities is important for tools to align with authorized law enforcement usage. More detailed capabilities are found below. The FBI also requests explanations of additional, new, or cutting-edge capabilities that a company may provide which were not requested, but which might be of interest to the FBI and add value to this contract.

The objective of the Request for Information (RFI) is to survey the landscape of LPR data tools that exist across the market and meet the requirements set forth below. Ultimately the FBI intends to develop a storefront of approved tools by leveraging the Indefinite Delivery Indefinite

Version 1.2 Page 5

Quantity (IDIQ) type of contract vehicle with resources that align with the needs, requirements, and specifications for FBI use.

Note on AdTech: One source of CAI that is not sought in this RFI is Advertising Technology

(AdTech) or the use of Mobile Advertising IDs (MAIDs), where users’ location data can be obtained and tracked. If any offerors have AdTech in their systems, this capability must be disabled before FBI use. (Note that MAID is a unique, resettable identifier assigned to each mobile device. It helps advertisers track user interactions with their content without revealing personal identity information. However, when these companies use AdTech associated with

PAI/CAI and social media, PII can be associated with the MAID.)

3.0 TARGET AUDIENCE

For this RFI market research only, to request input from potential providers, the FBI is seeking vendors who supply the LPR data tools and services, not re-sellers. No re-sellers will be considered valid submitters. The Offerors in this RFI should be able to describe how they provide Publicly Available Information (PAI) and / or Commercially Available Information

(CAI) from their platforms.

This RFI is open only to US-based companies. They may be other-than small businesses as well as small businesses, 8(a), minority-owned, and other specialty classes of businesses. The

Government seeks to know which firms can provide the designated services and products 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

Version 1.2 Page 6 shall be unclassified. Responses shall not be a regurgitation of the FBI’s requirements.

Responses shall demonstrate your company’s abilities to provide the requirements.

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 Name and Schedule Identification Name (SIN).

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

4.0 REQUIRED INFORMATION

Contractor Legal/DBA Name:

Company Address:

Point of Contact:

Telephone:

Email Address:

Unique Entity ID (UEI):

Cage Code:

Facility Clearance (if applicable):

Applicable NAICS Codes:

Standard Business Size:

GSA Schedule:

NASA SEWP Contract:

Other GWACS:

Version 1.2 Page 7

5.0 CONTEMPLATED CAPABILITIES

The FBI’s Directorate of Intelligence (DI), Information Technology Section (ITS) is issuing this

Request for Information (RFI) to:

1. Gather industry information on the enclosed capabilities.

2. 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.

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

Mandatory Capabilities for All Respondents

Capability Definition Notes / Examples

US Company

Vendor shall be a US company or subsidiary.

No foreign companies will be considered.

Only actual LPR Data companies accepted for this RFI

No re-sellers will be considered.

Software as a System

(SaaS)

Vendor shall provide

Software as a Service

(SaaS), for FBI users to log into a vendor website to access the tool. No software shall be downloaded, installed, or integrated into

FBI computers. The

Vendor’s system shall provide capability to access and use the system from various commercial web-browsers, specifically

Chrome and Edge, among others.

Version 1.2 Page 8

User-friendly GUI

The Vendor shall provide a coherent, organized, and intuitive Graphic User

Interface (GUI) that is easily navigated by non-technical users. The GUI shall not be cluttered or confusing and shall be able to be understood without needing extensive training. Searches shall be easily configured and launched, and the GUI shall allow users to populate and analyze search results without assistance.

Searches are often complicated to set up and returns can be hard to interpret;

therefore, the tool must have an intuitive

GUI that users can easily configure.

System Security The Vendor shall ensure their website and system maintain a robust secure posture to safeguard usernames, passwords, and FBI usage and search terms. The Vendor shall provide the FBI with information in the original proposal regarding the security posture of their system, such as being FedRAMP-certified, 256-bit encryption, and other stringent security measures that are taken to safeguard the user data in the system. A Vendor selected for the contract shall provide this same information once a year to the Government.

The Vendor shall also inform the FBI in the proposal and yearly how they save / archive

FBI user information. No FBI user information shall be sold to data resellers. Vendor shall ensure anonymity of FBI users by providing unique usernames that do not reveal actual names or affiliation.

Version 1.2 Page 9

508 Compliance The Vendor shall ensure their system is 508 Compliant, or working towards 508

Compliance, including acceptable color-blind accommodations. The Vendor shall provide a 508 Compliance scorecard in their proposal, and, if the Vendor is put under contract, shall provide the scorecard yearly, showing progress in making their system 508 Compliant.

Statistics/Metrics The Vendor shall provide user account management abilities, to include providing new accounts and deleting unnecessary accounts as requested by the FBI. The

Vendor shall provide tracking, auditing, and statistics on tool usage by FBI personnel, upon request. Basic statistics required include total number of accounts, number of searches monthly, number of one-time searches vs. persistent searches (if the system distinguishes those), duration of use, last login of users, and so forth. Usage reports for basic statistics shall be provided in the Monthly Report in .csv or .xlsx format.

System Reliability The Vendor shall provide notice of all upgrades and modifications to the system.

This notification shall be provided in a timely manner for the FBI to review the changes and ensure that all legal constraints and ease -of-use requirements will be met by the

Version 1.2 Page 10 changes. The Vendor shall be ready to modify, within reason, their system for legal reasons if required, for instance, for

Privacy and Civil Liberties purposes. The Vendor shall ensure their system is available

24 /7 for use by the FBI, and shall inform the FBI if there are technical problems with the system that result in downtime.

Relevant / accurate search results

The Vendor shall provide the user relevant results for a search, location of interest, individual/vehicle, and/or identifier(s), Result details include where information was originally derived, for the purposes of serving legal process, when necessary.

Vendor should also explain how long data is retained in the system, and whether unnecessary returns can be removed during review of data returns.

Training / Guidance

The Vendor shall give users access to training and best practices for tool usage.

Vendor shall provide both, virtual and self-paced on-line training.

Of special interest:

• Human support during interactive virtual trainings.

• On-demand training options to supplement human support

Export capability for data returns, via API and from Graphic User

Interface (GUI) user the ability to export data from tool via API and/or GUI in structured data formats.

User can access data either via API to ingest and analyze or export from the GUI

(e.g., in csv format, pdf report, audio or video file, images, etc.).

Thus, user can export analysis and results to incorporate into work products.

User support

The Vendor shall give users access to a support team to assist with resolving issues, providing guidance, etc.

Request is to have:

• A support team, POC, or phone number needs to be available 24/7 on-call for issues.

• During business hours human support should be able to field questions in real-time.

Technical system support

The Vendor shall provide personnel that are available to conduct system improvements/ upgrades specific to FBI needs.

Vendor shall be able to accommodate, within reason, modifications and adjustments required for legal processing purposes.

Version 1.2 Page 11

User Account

Management /

Reporting

Tool shall provide administrator management capabilities that track user accounts and provides useful stats / reports on tool usage to the Government.

Tool should include features for vendor administrators to manage and track user accounts, including controlling user permissions, analyzing user statistics, and generating usage reports.

Tool should be able to handle large numbers of accounts (e.g., 3,000 + users).

How a Vendor retains FBI users’ data is a question that the Vendor should be able to answer.

Coverage capabilities Vendor Tool shall provide robust geographical LPR coverage.

Vendor shall provide a listing of geographical coverage at minimum of state level. Vendor shall provide a LPR

Heatmap and number of cameras the

Vendor pulls data from.

Data Source(s) The Vendor shall ensure the user has access to robust LPR data sources.

Vendor shall describe source of LPR Data

(traffic cameras, toll plaza, commercial cameras, law enforcement cameras, etc.).

LPR data analysis Vendor shall provide the ability to conduct analysis across time and location with advanced filtering capabilities within their data holdings.

Vendor shall describe LPR data analysis capabilities.

User enabled ad hoc searches

Vendor shall provide the user with the capability to perform in-platform one- time manual searches.

• License Plate information

(full/partial)

• Time/Date criteria

• Location

Other data that the Vendor provides may include:

• Plate state

• Vehicle Make/Model

• Vehicle Description

Capable of sorting and filtering results, including but not limited to location, chronological listing of returns, etc.

Version 1.2 Page 12

User enabled persistent searches

Vendor shall have the ability to create and run persistent searches to collect over time without having to actively recreate and perform multiple queries.

• License Plate information

(full/partial)

• Plate state

• Location

• Vehicle Make/Model

• Vehicle Description

• Time/Date criteria

User can customize how to leverage the data (not just traditional text-based queries, but other ways to shape the findings, such as geolocation, start/end time range, image-based searches, etc.).

Real-time alerts, push alerts

Vendor shall provide the ability to push alerts to users in real-time/near-time based on established search criteria.

Push alerts must be received in real-time or near real-time (i.e., alerts are sent with little to no lag time). Also included shall be the ability to customize alerts.

Collaborative Features

Vendor’s Tool shall provide robust collaboration capabilities within the system.

Examples of collaboration features include, but are not limited to sharing data streams and filters with other users, ability to flag, tag, color-code, comment, and annotate data returns. Desired but not required: The ability to build and share profiles of topics or key identifiers.

Artificial Intelligence

(AI)

The Vendor shall provide artificial intelligence based analytics to include, natural language processing (NLP) and/or machine learning (ML) analytic capabilities. Useful AI features include, but are not limited to, event timelines and event tracking, and the ability to identify potential threats.

Include AI features, for example (but not exclusively) capabilities listed below:

Details about the tool analytic processes that are used to support these capabilities will need to be shared with Government

(e.g., how are data trained, what analytic results are provided. This can include threshold detection, changing trends, etc.).

Provide narrative / event tracking, also called “event timeline.”

Geospatial search capabilities ability to search data by city, county, state, region, country, and user defined geo-fencing

The tool should provide the ability to focus on customer-specified location areas of interest (e.g., user can select location-

Version 1.2 Page 13 capabilities. This capability shall include map visualizations.

specific boundaries / regions when searching/analyzing results/etc.).

Image Capture The Vendor shall provide image review, search, analysis, and capture capabilities that include the following: Optical

Character Recognition (OCR) of text (in large and common languages) in images and object identification.

Facial recognition is not a requirement for the FBI, and such capabilities shall be turned off if they exist in the

Vendor system.

Provide details about how the tool captures, processes, and analyzes images and whether users can perform image and object-based searches.

Video Capture The Vendor shall provide video review, search, analysis, and capture capabilities that include the following: Optical

Character Recognition (OCR) of text (in large and common languages) in video and object identification.

Video Facial recognition is not a requirement for the FBI, and such capabilities shall be turned off if they exist in the

Vendor system.

Provide details about how the tool captures, processes, and analyzes videos and whether users can perform image and object-based searches.

Mobile device compatibility

Vendor shall provide capability for Tool to be accessed and used on mobile interfaces

User can have full search and mapping capabilities while using a mobile device.

Hotlists Vendor shall ensure that the tool is capable of integration and updates/import with NCIC hotlist.

System can accept updates/imports of

NCIC/automated hotlists with frequent update capability. System can accept batch and manual updates.

Version 1.2 Page 14

6.0 RESPONSES

6.1 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 capabilities/questions listed in this RFI.

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

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

5. Pricing Information Requested:

Licensing Model

a. Describe all available licensing types (e.g., user-based, floating, enterprise-wide).

b. Specify what each license type includes, how usage is measured, and any limitations.

License Duration and Renewal

c. Indicate whether licenses are perpetual, annual, or subscription-based.

d. Detail what each model entails, including update rights, support coverage, and renewal terms.

Hardware and Infrastructure Requirements

e. List any hardware, software, or third-party dependencies required for deployment or optimal performance.

f. Include minimum specifications and scalability considerations.

Terms and Conditions

g. Provide full documentation of product usage terms, including restrictions, termination clauses, and service-level agreements.

Support and Maintenance

h. Describe the scope of support included with each license type (e.g., hours of availability, support channels, response times).

i. Clarify whether updates, patches, and upgrades are included or billed separately.

Pricing Structure

j. Submit a detailed price list for all licensing tiers.

k. Include volume discounts, onboarding/training fees, and any optional add-ons.

Note: All responses must be explicit and include descriptive detail sufficient to evaluate the vendor’s capabilities.

Version 1.2 Page 15

6.2 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 submit information on capabilities that are planned but do not exist in your system today.

7. Do not respond via telephone.

8. Do not regurgitate the FBI’s requirements in your response.

7.0 RFI SUBMITTAL INSTRUCTIONS

1. Email Subject line: The subject line of the email correspondence shall read – License Plate

Reader Data RFI (Company Name).

2. Questions Regarding the RFI: All clarifications, questions, and responses must be made via email. All questions regarding this RFI shall be in writing. No phone calls will be accepted.

Phone messages will not be returned. Questions regarding this RFI are due by 5:00PM ET on

October 28, 2025. Questions shall be submitted via e-mail to the Contracting Officer, Joseph

Spatafore (jspatafore@fbi.gov). Oral questions will NOT be accepted. The Government does not guarantee that questions received after that date and time will be answered. Questions shall NOT contain classified information. To the maximum extent possible, the Government will strip all questions and responses of proprietary information (as indicated by the respondent) and make collective responses available to all interested parties by 5:00PM ET on October 31, 2025.

3. Submission Medium and Due Date: All responses shall be submitted electronically in

Microsoft Word or Portable Document Format (PDF) format and shall not exceed 15 pages (not counting cover page). All responses should be e-mailed no later than 5:00PM ET on November

6, 2025, to Joseph Spatafore. E-mail verification will be sent upon receipt.

mailto:jspatafore@fbi.gov

Version 1.2 Page 16

4. Financial Obligation: The cost of responding to the RFI shall be exclusively borne by the organization submitting the information. No costs will be reimbursed by the Government.

The FBI makes no implied or in fact contract by issuing this RFI.

File details come from the government source that posted it. Updated .