AI Driven Image Search Tool

Request for Information (RFI) & Notice of Vendor Engagement

This RFI is issued by the United States Patent and Trademark Office (USPTO) to gather market information regarding a Software as a Service (SaaS) solution for an Artificial Intelligence (AI) Driven Image Search Tool. The USPTO aims to understand the commercial marketplace to meet its requirements for processing and granting patents. This RFI is part of a preliminary market information gathering process to identify vendors likely to successfully meet the agency's needs for an alternative competition.

• The USPTO is seeking solutions that align with the requirements outlined in the draft Performance Work Statement (PWS).
• The primary goal is to acquire a complete turnkey solution for all three patent types.
• A preference is stated for solutions that are already in a final FedRamp status, though FedRamp in-process status may be considered.

This RFI process involves two phases:

• Phase 1: Vendor Questionnaire
  • Respondents must complete RFI Attachment 1 – RFI Response Template, including a "Corporate Profile" and responses to specific RFI questions (#1-3).
  • Responses are due by 12:00 PM ET on June 19, 2026, submitted via email to Brian.Carper@uspto.gov and David.Hill@uspto.gov.
  • Questions regarding the RFI are due by 12:00 PM ET on June 3, 2026, submitted via RFI Attachment 3 – Question and Answer Sheet to David.Hill@uspto.gov.
  • The Government will review Phase 1 submissions to determine which vendors are most likely to meet requirements.
• Phase 2: Product Demonstrations and Interactive Dialogue
  • Only vendors determined most likely to meet agency needs from Phase 1 will be invited to Phase 2.
  • Product demonstrations are anticipated between July 13, 2026, and July 17, 2026.
  • Demonstrations will be virtual and will have a time limit of approximately 90 minutes.
  • The objective is to provide an operational demonstration of the solution's capabilities and functionality.

• Vendors that do not respond to this RFI will not be considered for the alternative competition and will not be eligible to compete as a prime offeror.

• Submission of a response does not guarantee eligibility to compete.

• This RFI is not a request for quotation or proposal, and no entitlement to payment will arise from participation.

• The USPTO may conduct one-on-one market research sessions.

• The Government reserves the right to ask questions before, during, or after demonstrations.

• The Government may issue multiple awards/solicitations if deemed in the best interest of the Government.

• Proprietary information submitted will be protected per FAR. Vendors must identify proprietary information within RFI Attachment 1.

Form / Attachment / Pricing Sheet

This document is an Excel file containing a template for bidders to provide their "Corporate Profile" and "List of Questions" in response to a Request for Information (RFI). It outlines the specific information required from potential vendors regarding their company, business size status, and points of contact. It also includes a list of detailed questions from the government that bidders are expected to answer.

• Corporate Profile Sheet: Requires company name and address, Unique Entity Number, current and anticipated business size status under NAICS 541519 ($34M), company point of contact details, name of solution, and OEM or Authorized Reseller status.
• List of Questions Sheet: Contains three detailed questions covering:
  1. FedRAMP authorization status, continuous monitoring processes, experience with 3PAOs, POA&M management, SIA for system updates, and FedRAMP milestone status if applicable.
  2. Technical capabilities and experience in customizing UI/UX workflows, integrating with Okta (OpenID Connect), and implementing automated export/redaction builders.
  3. Technical approach for ingesting, normalizing, and maintaining patent data from international authorities, including AI architecture for complex multi-image queries and meeting strict SLA for similarity rankings and classification suggestions.

This template is crucial for bidders to understand the specific data and technical details the government is requesting. Completing this form accurately and thoroughly will be essential for a compliant and competitive response to the RFI. Bidders must address all aspects of the three detailed questions, particularly concerning FedRAMP compliance, customization capabilities, and AI-driven patent data processing.

Statement of Work (SOW) / Performance Work Statement (PWS)

The objective is to acquire a FedRAMP-authorized, AI-driven Software-as-a-Service (SaaS) image search platform to enhance the prior art search capabilities of USPTO Patent Examiners. The tool aims to improve search completeness and examiner efficiency by allowing searches using uploaded images as direct queries.

• Provisioning, configuration, customization, and ongoing maintenance of an enterprise-wide AI-driven SaaS image search platform for approximately 12,000 users.

• Augmenting, not replacing, existing USPTO enterprise search systems.

• Aggregating and maintaining global patent and trademark databases from at least 80 international authorities.

• Providing robust AI-powered image-to-image search capabilities, including multi-image uploads and image manipulation tools.

• Configuring the user interface (UI), user experience (UX), and examiner workflows to align with USPTO-specific requirements and Cooperative Patent Classification (CPC) standards.

• Ensuring FedRAMP authorization, integration with USPTO's Identity, Authentication, and Authorization Management (IAAM) via Okta, and AI transparency.

• Implementing a Train-the-Trainer (TtT) methodology for USPTO personnel.

• Maintain FedRAMP authorization and obtain/maintain a USPTO Authorization to Operate (ATO).

• Adhere to FISMA, FIPS, and NIST guidelines.

• Provide monthly usage metrics (unique users, session lengths, queries, exports, image imports, classification metrics).

• Ensure AI components are transparent, explainable, and auditable, complying with relevant Executive Orders.

• Automatically delete uploaded images and derived representations immediately upon session end.

• Automatically redact confidential material from exports.

Not explicitly stated in the provided text, but implies an ongoing service for USPTO examiners.

• FedRAMP authorization is mandatory.
• Integration with USPTO IAAM via Okta.
• Strict data handling protocols, including immediate session data deletion and automated export redaction.
• U.S. citizenship and CONUS work restrictions for personnel handling nonpublic data.
• Government retains exclusive rights and ownership of Customized Code (Special Works).
• Contractor retains IP rights for the Base SaaS Platform, granting the Government a non-exclusive license.
• Contractor shall securely return all Government Data and Customized Code upon contract termination.

Questions & Answers / Clarifications

This document contains a question and answer sheet related to a SAM.gov opportunity. It appears to be an Excel file where questions from potential bidders are intended to be listed alongside their corresponding answers from the government.

As of the provided text, there are no questions or answers listed in the document. The sheet is structured with columns for 'Question #', 'Reference', 'Question Category (Contract or Technical)', 'Question', and 'Answer', but all rows below the header are blank.

This document, in its current state, provides no specific clarifications or impacts on the solicitation. It is an empty template for Q&A.

Form / Attachment / Pricing Sheet

This document, an Excel spreadsheet named 'PWS-Att-1-Deliverables-List Draft.xlsx', details the specific deliverables required under the Performance Work Statement (PWS) for this opportunity. It outlines each deliverable, its associated task, and the due date or frequency.

Task 1: Project Management

• Initial / Final Transition-In Plan (Draft with proposal; Final 3 days after kickoff)
• Designation of Primary and Backup POC (Within 14 days of award)
• Status Meeting Agendas and Minutes (Ongoing)
• Initial Transition-Out Plan (3 months after contract award)
• Final Transition-Out Plan (3 months prior to contract end)
• Monthly SLA Report, System Performance Report, Incident and Support Report, Usage Metrics Report (Monthly)
• Access to Live Incident Log (Continuous)
• Ad Hoc Reports (Upon request)

Task 2: Security & AI Compliance

• FedRAMP Authorization & 3PAO Assessments (Prior to operational use / Annual)
• System Security and Privacy Plan (SSPP) (Prior to operational use / Updated as required)
• Contingency Plan (Prior to operational use / Updated as required)
• Security Impact Analyses (SIA) (Before system changes)
• Plan of Action and Milestones (POA&M) (Ongoing updates)
• Personnel Roster (U.S. Citizenship/CONUS) (Before operational use)
• AI Transparency & Explainability Document (EO 13960/14179) (Before operational use)
• Data Deletion Procedures & Proof of Deletion (Procedures: Before deployment; Proof: Upon COR request)

Task 3: SaaS Customization (Special Works)

• Operational SaaS Web Portal (Okta integrated) (Per approved Transition-In schedule)
• Customized Code (Prior to operational use)
• System Configuration and Customization Plan (Before tool deployment)
• Custom Report Templates & Export/Redaction Builder (Before tool deployment)
• Enhancement Release Notes (With each software update)

Task 4: Database & Search

• Weekly Database Update Logs (Weekly)
• Master List of Aggregated Authorities (Ongoing)
• Functional Demo & UAT Sign-off (Before tool deployment)

Task 5: Training

• Trainer Kits (Facilitator guides, scripts, slides, FAQs) (Prior to / Per approved training schedule)
• Section 508 Compliant Manuals & Quick Reference Guides (Before tool deployment)
• Initial Super-User Training Delivery (up to 50 users) (Per approved training schedule)
• Ongoing Trainer Support (Office hours, refreshers) (Ongoing / Periodic)

This document is critical for bidders to understand the specific deliverables and reporting requirements associated with the contract. It outlines the timing and frequency of these deliverables, which will be essential for developing a compliant and accurate proposal, including resource planning and cost estimation. Bidders must pay close attention to the due dates, especially those tied to proposal submission (e.g., Transition-In Plan) and contract award/kickoff.

Form / Attachment / Pricing Sheet

This document outlines the Performance Standards and Acceptable Quality Levels (AQLs) for the contract, detailing specific metrics and surveillance methods. It serves as a critical reference for bidders to understand the expected performance and quality requirements.

• Performance Objectives: Covers Project Management, System Availability, Security & Compliance, SaaS Customization, Database Aggregation, and Training.
• Associated Deliverables: Lists specific deliverables (e.g., D1, D6, D12) linked to each performance objective.
• Performance Standards: Defines measurable targets for each objective (e.g., 95% on-time deliverables, >= 99.9% monthly uptime, 100% FedRAMP compliance).
• Acceptable Quality Levels (AQLs): Specifies the minimum acceptable quality for each standard (e.g., no more than 1 revision required, zero critical open POA&M items).
• Surveillance Methods: Details how performance will be monitored and assessed (e.g., COR inspection, automated monitoring, review of reports).
• Incentive/Disincentive: Indicates where incentives or disincentives may apply based on performance.

This attachment is crucial for bidders to understand the specific, measurable requirements of the contract. It directly informs how proposals should be structured, how technical solutions should be designed, and how performance will be evaluated post-award. Bidders must ensure their proposed approach can meet or exceed these defined standards and AQLs.