(Draft Solicitation Notice) Traveler Processing and Vetting Software (TPVS) 2.0

Description

Special Notice: Request for Information The revised draft solicitation response deadline is suspended to solicit additional feedback for the U.S. Customs and Border Protection (CBP), Office of Information and Technology Passenger Systems Program Directorate, Traveler Processing and Vetting Services (TPVS) software application development, modernization, enhancement, and operations and maintenance services acquisition. CBP is seeking industry�s perspective and feedback on how to best structure this mission-critical acquisition and how to ensure the agency receives the best commercially-available solution and achieves a cost-efficient, fair and reasonable price. Feedback on the performance work statement and identified deliverables is requested as part of this with the objective of achieving outcome-based results. Responses must take into account the following: Dynamic, Evolving, and Emerging Requirements: TPVS requirements are not static and surges as demand emerges throughout performance. The acquisition strategy must support proposal solutions with a high degree of adaptability, allowing for continuous modernization and adjustments to priorities, as new information, industry advancements, and operational needs become clear. Streamlined Delivery: The Government anticipates a high likelihood of changes in project direction and operational shifts throughout the TPVS 2.0 lifecycle and, consequently, requires a flexible contract solution. The acquisition approach must balance the demands of contract administration with critical mission responsiveness. Industry should submit a two-page document with its recommendations and how it will deliver outcomes for the government. If there are current acquisitions that include these best practices, please reference them. A response submitted to the original RFI does not preclude Industry from submitting a response to this request for additional feedback. Industry should not provide the government with a capability statement. Responses are not required, and interested offerors who do not respond to this RFI will not be excluded from competition. Responses are due by 2PM ET, 24 October, 2025. ----------------------------------------------------------------------------------------------------------------------------------------------------- HISTORICAL GSA EBUY POST INFORMATION FOR TPVS 2.0 DRAFT SOLICITATION (GSA EBUY DRAFT RFQ - RFQ1780365) PURPOSE This posting is for a draft solicitation only. All information provided herein, including dates and attachments, is prelimary, tentative, and subject to change. The Government reserves the right to revise requirements, amend, or cancel this draft solicitation in its entirety, and is under no obligation to award a contract as a result of this notice. The tentative timeframes are not guaranteed and may be adjusted at the Government's discretion. This draft solicitation is provided to share preliminary requirements and specifications so that vendors can prepare their offers. Vendors are encouraged to review this draft closely to ensure readiness in the event a formal solicitation is released. BACKGROUND The Blanket Purchase Agreement (BPA) will be established through U.S. General Services Administration (GSA) Multiple Award Schedule Program for Traveler Processing and Vetting Software (TPVS) 2.0. This BPA will provide critical technology services in support of U.S. Customs and Border Protection (CBP) strategic initiatives. TPVS 2.0 BPA will cover the full range of life cycle services for CBP's Passenger Systems Program Directorate, including the TPVS suite of software applications and related specialized equipment. BPA task orders will be used to procure these services and equipment. The historical BPA number is 70B04C20A00000008 and current task order is 70B04C24F00000739. AMENDMENTS Submission of feedback or comments does not constitute an offer and will not result in an award. Minor draft amendments may not be reflected in every attachment. For major draft amendments, all attachments will be updated and reissued with the header disclosing a draft amendment number. This approach ensures vendors have a complete, consistent set of current documents and avoids confusion with older versions. Vendors should review the Amendments Repository attachment, which aligns with the posting amendment descriptions.