City of Tucson (Arizona) posted this RFI on Oct 28, 2026. Responses are due Nov 30, 2026. Category: Information Technology. Solicitation number 270200.
This bid was found on the agency's procurement portal. The portal's own text is not republished here; the summary below was written by ProposalWorkspace's AI from the bid documents. The full posting is on the portal - sign up free to get the link.
Summary fields on this page were extracted by AI from the bid documents. Always verify dates, amounts and requirements against the official solicitation.
This RFI is issued solely to obtain information from the marketplace. It is not a Request for Proposals, Invitation for Bids, offer to contract, or promise that a future procurement will occur. Responses are voluntary and will be used to inform project planning, requirements development, acquisition strategy, budgeting, and risk management.
The purpose of this Request for Information is to identify organizations with the capability and experience to help plan, design, configure, implement, integrate, host, operate, and support a Transit Account and Passenger System (TAPS), and to obtain industry recommendations regarding how a project of this type should be structured and delivered.
The agency has developed a preliminary enterprise Scope of Work describing a potential future-state platform for rider registration, customer account management, credentials, utilization tracking, reporting, cybersecurity, system integration, and future account-based fare collection. Before finalizing a procurement strategy or detailed requirements, the agency wants to understand the current marketplace, available solution models, implementation practices, technology alternatives, cost drivers, risks, and lessons learned from comparable programs.
TAPS is envisioned as an enterprise customer account platform rather than a stand-alone card database. The agency's preliminary concept includes rider registration, account management, credential management, usage-event capture, administrative tools, reporting and analytics, secure interfaces, and future fare-readiness. [...]
The agency currently anticipates a secure, modular, scalable, cloud-hosted solution with separate non-production and production environments, documented interfaces, configurable roles, auditability, backup and recovery, monitoring, and support. Respondents should describe whether this concept aligns with current industry practice and identify more effective alternatives.
**Response Format:** Electronic PDF; respondents may also provide an editable copy if permitted by procurement instructions.
**Suggested Length:** Approximately 25–40 pages excluding appendices; concise responses are preferred.
**Questions:** Submit through the procurement contact and method identified in the issued RFI.
**Confidential Information:** Clearly identify information claimed to be confidential or proprietary; treatment remains subject to applicable public-records law.
**Cost to Respond:** The agency will not reimburse respondents for costs incurred in preparing a response or participating in follow-up market research.
The agency may elect to conduct non-competitive informational meetings, demonstrations, or follow-up interviews after reviewing RFI responses. Participation in such activities would be for market research only and would not confer an advantage in any future procurement.
Sign up free to get this document.