License Plate Reader IDIQ QA.xlsx
XLSX spreadsheet 20 KB Posted
- Attached to
- License Plate Reader IDIQ for FBI Directorate of Intelligence Federal contract opportunity
- Solicitation number
- SHOP-PR-26-003385
About this file
This is a Questions and Answers document template for the License Plate Reader IDIQ solicitation. The file appears to be a Microsoft Excel spreadsheet designed to capture and organize questions submitted by potential offerors regarding the solicitation, along with corresponding government responses. The document structure facilitates the Q&A process typical of federal contract competitions, allowing interested parties to seek clarification on solicitation requirements, specifications, and terms before submitting proposals.
The template is intended to support the FBI Directorate of Intelligence's IDIQ contract for Internet/Cyber Security Data Subscriptions related to License Plate Reader tools and Open Source Intelligence operations. As a standard Q&A vehicle, this document would be populated with specific questions from vendors and official government answers to ensure all potential contractors have equal access to clarifying information during the solicitation period. The document serves as an administrative tool to manage the pre-award communication process and maintain transparency throughout the competitive bidding phase.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| LPR IDIQ Modification.pdf | ||
| License Plate Reader IDIQ QA.xlsx | XLSX spreadsheet | |
| LPR IDIQ Modification.pdf | ||
| LPR IDIQ Modification.pdf | ||
| Attachment 3 - LPR IDIQ Price Template.xlsx | XLSX spreadsheet | |
| Attachment 1 - LPR IDIQ Statement of Work.pdf | ||
| LPR IDIQ - UCF RFP 1.2.pdf | ||
| LPR IDIQ Modification.pdf | ||
| Attachment 3 - LPR IDIQ Price Template.xlsx | XLSX spreadsheet | |
| Attachment 1 - LPR IDIQ Statement of Work.pdf | ||
| Attachement 2 - LPR IDIQ Terms and Conditions.pdf | ||
| LPR IDIQ - UCF RFP .pdf |
Show all 12
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
Sheet1
| License Plate Reader IDIA Q&A | |
| Question | Answer |
| Is the 75% coverage threshold under CLIN 0001 measured by geographic area, population, FBI field office area of responsibility, camera density per state, or another metric? | All of the above factors will be taken into consideration to satisfy any FBI needs. |
| If a single offeror does not independently meet the 75% Eastern Lower 48 threshold but provides high-density coverage of one or more states containing major FBI field offices, would such an offeror be eligible for award under the dual-award provision in Section 3 of the SOW, or would the Government prefer such capability be structured as a subcontracting arrangement under another offeror? | All of the above factors will be taken into consideration to satisfy any FBI needs. |
| The SOW reserves OnRamp authority throughout the period of performance and notes that OnRamp solicitations may be limited to specific CLINs. Could the Government clarify the anticipated trigger criteria for OnRamps, and whether OnRamps may include regional gap-fill within an already-awarded CLIN to address coverage shortfalls in specific states or AORs? | Trigger conditions may include, but are not limited to: Geographic or regional shortfalls where awarded contractors cannot provide sufficient LPRs, sustained inability of current contract holders to meet demand in specific states or AORs, emergent operational needs requiring additional providers or expanded regional support. |
| Could you please confirm the anticipated start date for the period of performance? | Anticipated start date is contingent on many internal processes but will be no later than 09/30/2026. |
| We are performing independent research on the Combined Synopsis/Solicitation (SHOP-PR-26-003385). We would like to know if this is a brand-new contract OR if there is (was) an incumbent performing these services. If not brand new, could you please provide the current / previous contract number and what the total contract value was? | This information is not pertinent or needed in order to provide a response. |
| Can you please include attachment 3 in the RFQ? We are not seeing it posted | The attachment has been added to the solicitation. |
| One point that would benefit from additional clarification is whether the requested solution is intended to leverage the existing camera infrastructure to generate new data and analytics, or whether the intent is to integrate with and query an already established database environment | The FBI does not own any camera infrastructure, therefore we cannot expand something we do not have. |
| Are you willing to consider a hardware data source (CCTV camera) with a solution that can also connect any other cameras you will use in coverage areas? | This IDIQ is not designed for hardware purchase. |
| Do you already own any sources of data (e.g. cameras) in specified areas? | No |
| Are you looking for access to an ALPR system already in place? | Yes |
| Can the Government confirm the NAICS code for the opportunity is 541519 as listed on the SF1449 in Attachment 2? The SAM.gov solicitation notices shows a NAICS of 561990. | The correct NAICS is 513210. |
| Does the Government anticipate purchasing LPR hardware as part of this IDIQ? SOW paragraph 1.2 states the FBI requires professional service firms that can provide LPRs. | No |
| Given that this is anticipated to be a FFP contract, it is not clear what information the Government is requesting on Attachment 3 – Cost Proposal. Is the Cost Proposal a pricing schedule that will be used for future task orders? Can the Government provide additional instructions on what should be included on our Cost Proposal? | Attachment 3 is the Government’s standardized pricing template used to evaluate proposed pricing consistently across all vendors. The pricing submitted in Attachment 3 will be considered firm‑fixed and treated as the vendor’s best and final offer. The pricing provided will also serve as the established pricing for future task orders issued under this contract. Vendors are only required to complete the CLINs for which they are submitting a proposal. |
| The RFP instructions state that if a vendor is proposing multiple CLINS, they are required to submit a separate technical proposal for each CLIN. Attachment 3 – Cost Proposal includes a tab for each CLIN. Can you confirm that we are only required to complete CLIN pricing for the specific CLINS we are submitting a technical proposal for? | Only CLINs that have technical proposal should have a cost proposal. |
| The RFP states the FBI does not have its own LPR hardware. Should the proposal include the cost of hardware procurement, installation, and maintenance, or is the FBI specifically looking for a 'data-only' SaaS license for access to third-party cameras? | No- We are looking for 'data-only' |
| Is the FBI open to owning their own turnkey network of cameras rather than just buying access to data collected by third party cameras, companies, and toll booths? | No later than 14 business days after the date of award. |
| Can the FBI clarify the 'Blind Logging' requirement? Is the requirement for the Contractor to be unable to see the search query (Zero-Knowledge Architecture), or must the system automatically purge search history after a set period? | Refer to the current CJIS policy in terms of Blind logging and Search History retension. |
| Regarding 'Offline (queued) searches,' does the FBI prefer a system that requires manual queuing of large data exports, or would a real-time, AI-indexed system that allows instant 'Free-Form' searching across all historical data be preferred? | We will consider both as long as they align with the FBI's AI usage policy. |
| Would a FedRAMP-authorized SaaS platform with pre-built integrations to CJIS, NCIC, Evidence.com and FUSUS be preferred? | Please see SOW |
| Would the government consider extending the page limit of Volume 2 Technical response to 15 pages? | Page limit will be extended to 15. |
| The forumla that calculates Total CLIN Price seems inaccurate. May vendor correct this error to reflect the accurate total per CLIN or will the government reissue a new document? | This error has been corrected. If there are still issues, please correct on vendor end. |
| Is it acceptable for vendors to add a column to the pricing document to account for the requested 6-month extension? | A column has been added to each CLIN for 6 month extension pricing. |
| Within how many days from award will users require access credentials? | No later than 14 business days after the date of award. |
| Is this opportunity for Software only, or will it include installation of LPR hardware in locations where there are gaps? | This IDIQ is not designed for hardware purchase. |
| If this requires hardware solutions, will you require a fixed, mobile, or a mix of both? | This IDIQ is not designed for hardware purchase. |
| Will the initial training requirements need to occur simultaneously, or can we phase this over time to cover 56+ locations? | Depends on service and locational needs |
| Does the FBI have access to the data sources mentioned in section 3.17? | The contractor must provide this data source. |
| Could you please clarify what the “Quantity” column in the pricing sheet represents? Specifically, should this be interpreted as a unit tied to a defined Period of Performance (e.g., annual or monthly), or as another pricing construct? | It is tied to the POP and how each company prices products (monthly vs annually). |
| The SOW references support for Open-Source Intelligence (OSINT) and social media-related capabilities; however, there does not appear to be a corresponding requirement or pricing structure tied to these capabilities. Can you confirm whether OSINT capabilities are expected to be included as part of the proposed solution, and if so, how they should be addressed within the pricing response? | OSINT is optional and pricing should reflect as such. |
| The SOW references both law enforcement and commercially available LPR data sources. Can you clarify whether vendors are expected to provide both data types as part of their solution, or if offerings may be limited to one or the other depending on capability? | Vendors are not expected to have both but it would be beneficial. |
| The CLIN structure references “additional coverage areas” for each region; however, this term is not defined further. Can you provide additional detail or examples of what constitutes an “additional coverage area” within each CLIN, and how this should be reflected in the technical and pricing response? | The additional coverage area is any area not listed in the CLIN that is being bid on. |
| Section L, page 8 states the proposals remain valid for 120 days, however, the Company Data section on page 9 states 90 days. Can you clarify which is the length the FBI requires? | Proposals must remain valid for 120 days. |
| Would the FBI consider a platform if it provides nationwide coverage, but does not support configuration to limit data collection, access, or operations by specific geographic regions as defined in the CLIN structure? | We would consider it, however the area of coverage needs to be clearly defined. |
| Please clarify how the Government defines “coverage” for purposes of evaluating the required “75% locations” threshold within each CLIN. Specifically: Is coverage based on geographic area, population density, roadway coverage, active camera locations, traffic volume, metropolitan areas, or another methodology? How will the Government evaluate sufficiency of operational coverage? | All of the above factors will be taken into consideration to satisfy any FBI needs. |
| Does the Government have a desired operational saturation level for: interstate highways, urban corridors, border regions, ports of entry, or other high-priority investigative areas? | No |
| What supporting documentation or methodology should vendors provide to substantiate claimed coverage percentages and operational footprint? | We will consider all methodology, however the preferred is heat maps and number of camera's/images. |
| May vendors propose coverage across multiple CLINs even if operational density differs significantly between regions? | They may, however, they need to also provide separate pricing structures to CLIN specific areas only as well in addition to cross coverage pricing/coverage. |
| The SOW references both enterprise licensing and tiered licensing structures. Does the Government have a preferred pricing construct for: enterprise-wide access, named users, concurrent users, query-based licensing, or regional subscriptions? | We prefer as stated- Enterprise licensing and tiered licensing structures. |
| Should persistent searches, hotlists, and notification capabilities be proposed as: included core functionality, optional functionality, or separately priced capabilities? | Included core functionality |
| Can the Government provide estimated assumptions regarding: user counts, query volume, persistent searches, API usage, or concurrent sessions to support pricing normalization across vendors? | We cannot as these would vary depending on AOR |
| Does the Government anticipate future Task Orders being: geographically scoped, use-case specific, enterprise-wide, or office/division specific? | We cannot anticipate future task orders as we are unaware of the options that this IDIQ will present. |
| Please clarify the Government’s operational definition of: “real-time” versus “near real-time” for data ingestion and notification capabilities. | Real-time refers to processing data instantly with virtually no delay, while near real-time introduces a slight, acceptable time lag (seconds to minutes) to allow for data buffering, batching, or processing |
| Please clarify acceptable implementation approaches for “blind logging” requirements, including whether: encrypted audit logging, hashed query retention, or ephemeral query processing would satisfy the requirement. | Blind Logging is no retention or storage of any queries executed through logs, cache, or saved searches. |
| Does the Government require: current FedRAMP Moderate authorization, FedRAMP equivalency, sponsorship/in-process status, or alignment with FedRAMP Moderate security controls? | Current authorization is required. |
| Please clarify under what circumstances vendors are considered to be: accessing Criminal Justice Information (CJI), versus providing commercial SaaS capabilities containing commercially available information. | CJI is data provided by Law Enforcement entities |
| Does the Government anticipate API usage primarily for: bulk export, system-to-system integration, alerting workflows, or operational query integration? | Potentially, all. |
| The SOW references retention periods up to 120 days. Will longer historical retention periods be viewed favorably during technical evaluation? | We evalute based on the SOW. |
| To what level should vendors identify underlying LPR collection source types (e.g., commercial, repossession, tolling, municipal, etc.) within technical submissions? | This is a vendor determination |
| How does the Government prioritize: ingestion latency, historical depth, geographic density, and overall record volume during evaluation? | We evalute based on the SOW. |
| How will AI/ML capabilities be weighted relative to core operational LPR functionality during evaluation? | We evalute based on the SOW. |
| Does the Government view: geospatial analysis, correlation analytics, or inference capabilities as differentiators during technical evaluation? | We evalute based on the SOW. |
| Can the Government provide an estimated number of anticipated awards per CLIN? | One awardee per CLIN; however we reserve the right to award up to two based on coverage requirements. |
| Does the Government anticipate periodic on-ramp competitions as a routine mechanism for expanding vendor participation during contract performance? | This will be dependent on the market and is not guarenteed. |
| Can the Government clarify the relative weighting of: geographic coverage, operational maturity, technical capability, support infrastructure, and pricing within the evaluation process? | As part of the technical requirements geographic coverage, operational maturity, technical capability, and support infrastructure will be considered more important than price. |
| The solicitation identifies NAICS Code 561990 – All Other Support Services. Given that the requirement is centered on the delivery of commercial License Plate Reader (LPR) data, software platforms, analytics, and SaaS-enabled investigative capabilities, will the Government revise the solicitation to utilize NAICS Code 513210 – Software Publishers and incorporate FAR 52.219-1 accordingly? | The NAICS code will be adjusted to 513210. Competition will remain full and open. |
| In Attachment 1 Statement of Work, Section 3 Requirements states that for each CLIN, “The proposed tool must be successful and active in 75% locations within states…”. Will the government clarify the method that will be used to determine “active in 75% locations”? | FBI will utilize geographic area, population, FBI field office area of responsibility, camera density per state to determine this metric. |
| In Attachment 1 Statement of Work, Section 3 Requirements states that, “Vendors must provide a coverage map within the technical response, clearly depicting their operational footprint and indicating the percentage of each region covered for the CLIN(s) proposed.” Due to the density of the data, a print version of the coverage map would not be useable without providing hundreds of pages of maps. Will the government allow offerors to provide an online format for the coverage maps to better visualize the data? | Yes |
| In the RFP document, Section L Instructions, Conditions, and Notice to Offerors under “Instructions,” point 4 and point 8 state that “Proposals must be remain valid for 120 days.” Under Volume I – Company Data, point 12 states that Offerors “Must clearly indicate the quote is valid for 90 days from quote response date.” Please clarify the proposal validity timeframe. | Proposals must remain valid for 120 days. |
| 52.219-6 Notice of Total Small Business Set-Aside (Nov 2020) : RFP clause stating award will ONLY be given to a small business. The headline in SAM.gov confirms there is no set a sideused. Therefore, we respectfully request removal of this clause in its entirety. | Clause will be removed. |
File details come from the government source that posted it. Updated .