ATCH 1 - FY 2026 LPR SOW Final 1_27_2026.pdf

Licenses Plate Reader Data Access Statement of Work

1. Organization

The Bureau of Alcohol, Tobacco, Firearms & Explosives (ATF) is a component of the U.S. Department of Justice (DOJ); and the Office of Intelligence Operations (OIO) is a Directorate within ATF.

2. Background

OIO provides critical law-enforcement resources in support of reducing violent crime and protecting the public. Staffed by a number of dedicated law-enforcement intelligence analysts, support professionals, and officials, the mission of OIO has always been to enhance decision-making Bureau-wide by providing timely, accurate and focused intelligence through the collection and analysis of information.

In recent years, LPR systems have proven to be effective in a wide range of applications, including law enforcement. ATF aims to leverage these capabilities to support our operational objectives. Due to the rapid advancement of technology in vehicle identification systems, ATF seeks programs with assurance of application security, efficiency and accuracy in their vehicle recognition processes. The LPR technology will be utilized to query comprehensive data from both commercial and the law enforcement environments to identify targets related to ATF missions.

Key capabilities required to support the ATF missions are LPR systems that will facilitate real-time data monitoring of vehicular traffic, geospatially enabled watchlists that can enable ATF to match all available LPR data against vehicles of interest and receive hit notifications. A feature that can provide ATF the ability to enter an address to see all visits to that location. An LPR system that provides a reporting feature allowing for multiple points of interest to be defined on a map with corresponding geofence or area of interest and times/dates, for the location of common plates that are seen in more than one of the locations of interest. As well as able to provide the ability to identify other vehicles commonly seen near a known person(s) of interest’s vehicle.

3. Overview

In step with the vision of ATF to embrace and use leading-edge technology where appropriate, OIO utilizes a number of internal databases as well as external sources to provide timely and relevant information in support of ATF’s mission. The extensive LPR dataset has been proven and will continue to provide intangible value from an investigative perspective.

4. Objectives/Requirements

The primary objective of this effort is to procure a state-of-the-art License Plate recognition (LPR) system that enables efficient, accurate and secure querying of the relevant law enforcement and commercial databases.

This system shall/must support law enforcement operations to support ATF’s daily operational needs for use in intelligence and investigative activities, for example, to identify plates associated with potential suspects or persons of interest, and those subjects associated with the target individuals; support for complex investigations, such as investigations into violent gang activity, firearms traffickers or cigarette diversion activity. A LPR system is used in support of ATF’s critical mission to protect our communities from violent criminals; criminal organizations; the illegal use and trafficking of firearms; the illegal use and storage of explosives; acts of arson and bombings; acts of terrorism; and the illegal diversion of alcohol and tobacco products. ATF requires access to national license plate reader data and the LPR analytics software to support its daily operational needs for use in intelligence and investigative activities.

ATF requires a geospatially enabled query capability to leverage the data sharing initiative of a nationwide LPR system to match all available LPR data against agency created watchlists and provide “hits” on a map interface with agency-customizable icons. ATF will use this both to locate vehicles of interest and to visualize criminal hotspots for predictive policing efforts.

ATF requires the ability to see all “visits” to a particular location via entry of an address. In addition, select visits and monitor a location, seeing all LPR scans collected by a driver on a given “visit”.

ATF requires the ability to define multiple points of interest on a map, with corresponding geofences or areas of interest and times/dates, for the location of “common plates” that are seen in more than one of the locations of interest. This feature supports investigations into pattern crimes for generating leads into the identification of violent criminals and the identification of associated members of criminal organizations.

ATF requires the ability to identify “known associates” by querying a known plate to identify other vehicles commonly seen near the suspect vehicle. This feature is useful in identifying possible associates of a known suspect or perhaps establishing a pattern of surveillance between a perpetrator and a victim.

ATF requires the query capability to define a search using geofences or areas of interest through simple drawing tools (rectangles, circles, and custom polygons) on a map interface.

ATF requires the ability to search for vehicles based on the vehicle’s Year, Make and Model and in some cases color

ATF requires the ability to conduct batch queries of vehicles against data stored within the LPR system.

ATF requires the ability to export LPR data in a format easily utilized by ESRI and i2 Analysts Notebook, such as .csv, .xlsx, .xls, JSON, .shp, or via API.

ATF requires the accessibility via application programming interface (API) or other similar mechanisms so its data can be easily searched against and viewed in a federated search application or other external applications. APIs would be open-source and/or provided as an included service.

5. Tasks/Deliverables

The contractor shall perform the below tasks and provide the associated deliverables to meet the requirements in this scope of work

1. Activity/Usage Report. Provide ATF the ability to generate usage/activity reports, to include comprehensive auditing of individual user reports, encompassing all relevant data including last login, entries, queries, and overall system interactions. (Deliverable 1)

2. Training/Consultation. Provide training and consultation for the online system via web, in person, conference calls and/or user guides. (Deliverable 2)

3. User Management & User Administration. Provide ATF the ability to add and remove users and reset their passwords. (Deliverable 3)

4. Access & Security. Provide direct data network access through a secured Uniform Resource Locator (URL) so that user accounts remain protected. Users should have unlimited access (unlimited logins and unlimited queries). (Deliverable 4)

5. Support. Provide support via phone and or email. (Deliverable 5)

6. Deliverable Schedule

Task Task/Deliverable Due Date

5.1 Activity/Usage Report Daily 24/7 via the LPR system

5.2 Training/Consultation As needed/required

5.3 User Management & User Administration Daily 24/7 via the LPR system

5.4 Access & Security Daily, 24/7 if necessary

5.5 Support Daily, 24/7 via telephone and email

7. Points of Contact

The Contracting Officer (CO) and COR are identified below;

Amanda M. Boshears, Contracting Officer

99 New York Ave., NE, #3S147

Washington, DC 20226

202.648.9018 (Phone)

Amanda.Boshears@atf.gov

TBD - Contracting Officer’s Representative

7.1 Contract Management. Notwithstanding the contractor's responsibility for total management during the performance of this contract, maximum coordination between the CO, the COR and the contractor will be required. The above individual(s) will be the Government’s point(s) of contact during performance of the contract:

7.1.1 The CO is responsible for the contract administration and is the only individual authorized to approve changes in the terms, conditions, delivery schedules, technical requirements or price, as set forth in the contract. Any changes not made expressly by the CO will be considered to have been made without authority. In such cases, the contractor is operating at its own risk. No adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof. During any absence of the CO identified for this contract other warranted COs from ATF may authorize work under the contract.

7.1.2 The COR will be designated by the CO to monitor all technical aspects and assist in administering the contract. The types of actions within the purview of the COR's authority are to: assure that the contractor performs the technical requirements of the contract; perform, or cause to be performed, inspections necessary in connection with performance of the contract;

maintain both written and oral communications with the contractor concerning the aspects of the contract within his/her purview; monitor the contractor's performance under the contract and notify the contractor and CO of any deficiencies observed; and coordinate Government-furnished property availability and provide for site entry of contractor personnel, if required.

8. Hours of Work

Contractor shall provide Helpdesk technical support via e-mail and/or phone 24/7.

Period of Performance

The Period of Performance shall be March 1, 2026 – February 28, 2027 plus four (4) 12-month option periods, if exercised.

10.0 Contract Type

10.1 ATF anticipates a firm-fixed-price contract type for the effort.

11.0 Other Direct Costs (ODCs)

11.1 ODCs and travel are not anticipated for this contract.

12.0 Certification of Invoices

12.1 The Payment Office listed on the first page of the Award Document will make payment upon receipt of an accepted and proper invoice.

12.2 Invoices/vouchers shall be completed and submitted in accordance with (IAW) Clause #ATF- 14, Electronic Invoicing. The final invoice will be paid upon Government acceptance of all services being rendered.

12.3 The COR’s certification of acceptance is an integral part of the correct invoice/voucher discussed in the “Discounts for Prompt Payment” clause, (the Federal Acquisition Regulation (FAR) 52.232-8).

12.4 Upon certification, the COR or someone from the Program Office will enter a Receiver document in the financial & procurement system, as appropriate, authorizing Finance to pay the invoice.

12.5 The Invoice/Voucher shall include:

(a) Contract or other authorization number(s)

(b) Product or service description.

(c) Quantities received, if applicable

(d) Date(s) property or services accepted

(f) Signature, printed name, title, phone number, and mailing address of the receiving official

(g) POC to discuss invoice issues

13.0 Payment

Payment for all supplies and services shall be made upon Government acceptance, IAW the appropriate “Payments” clause, FAR 52.232-1.

14.0 Mandatory Use of Government to Government Electronic Mail

Unless exempted by the CO, in writing, communication after contract award with Government agencies shall ordinarily be transmitted via email.

15.0 Section 508 Compliance

IAW FAR 39.2, (1) Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities; and (2) Members of the public with disabilities seeking information or services from an agency have access to and use of information and data that is comparable to the access to and use of information and data by members of the public who are not individuals with disabilities. This acquisition must meet the applicable accessibility standards at 36 CFR Part 1194.