Airport CommissionIssuing agency·San Francisco, CA·via the City and County of San FranciscoRequest for Proposals (RFP) 11211.52
San Francisco International Resource Management System/ Airport Operations Database Implementation, Maintenance and Support Services
The San Francisco International Airport is seeking to procure Resource Management System (RMS)/ Airport Operations Database (AODB) Implementation, Maintenance and Support Services.
San Francisco International Airport (“SFO” or “the Airport”) served 52 Million Annual Passengers (“MAP”) in 2025 and is on track to reach 70MAP in the next decade. Serving as a major gateway to Europe and Asia across four terminals (1, 2, 3 and International) and seven concourses (A to G). SFO utilizes a shared use terminal strategy. The Airport’s capacity and flight schedule are facilitated as a Level 2 airport by the FAA Slot Administration Office within the Air Traffic Organization in accordance with the Worldwide Airport Slot Guidelines.
Common Use Passenger Technology (CUP-T) is the umbrella term for three separate procurements that when completed will encompass the technologies needed to support common use at the Airport.
The three separate CUP-T procurements include: (1) the Resource Management System (RMS) – Airport Operations Database (AODB); (2) Passenger Processing Systems (PPS) which includes Common Use Passenger Processing (CUPPS), Common Use Self Service (CUSS), Self Service Bag Drop (SSBD), Biometric (such as facial scans) for Passenger Boarding; and (3) Information Display Systems (IDS).
The intent of these separate procurements is to achieve best-of-breed solutions.
This Scope of Work (also referred to as the “Scope of Services”) covers the procurement, implementation, integration, and ongoing maintenance of the first CUP-T procurement identified above, which includes two core Airport operations and capacity management technology platforms: the RMS and AODB, as further detailed below:
1.1.1 Airport Operational Database. The AODB is the authoritative, real-time operational data platform for the Airport. It provides integrated capabilities for real-time messaging, storage and retrieval of operational information, and serves as the master source of flight data. The AODB shall expose Representational State Transfer (REST) and event-based Application Programming Interfaces (APIs), for data and service integration with the Airport’s enterprise data platform and data-domain structure and shall make operational data available to downstream systems such as the IDS.
1.1.2 Resource Management System. The RMS supports SFO Operations in the planning and real-time assignment of physical Airport resources, including gates, check-in counters, baggage claim carousels, baggage makeup conveyors, and remote aircraft parking positions including fixed-base operation and cargo stands. The RMS shall provide planning functions, “best-fit” assignment recommendations, and real-time conflict detection and warnings.
Contractor shall ensure the RMS/AODB will interoperate cleanly with the separately-procured passenger processing platform and with the third-party IDS through documented, standards-based interfaces.
Software licenses provided under this Agreement shall be enterprise-wide and shall support all potential authorized users as designated by the Airport.
Please visit the Airport e-Procurement Portal to review solicitation information, documents, submit question and proposal: https://procurement.opengov.com/portal/sfo/projects/301413
Attached documents:
• EXT_AIR___RFP_11211.52_SFO_CUPT_RMS_AODB_IMSS.xml
The scope covers the procurement, implementation, integration, and ongoing maintenance of the RMS and AODB platforms. The AODB is the authoritative, real-time operational data platform providing integrated capabilities for real-time messaging, storage and retrieval of operational information, and serves as the master source of flight data. The RMS supports SFO Operations in the planning and real-time assignment of physical Airport resources including gates, check-in counters, baggage claim carousels, baggage makeup conveyors, and remote aircraft parking positions. The RMS shall provide planning functions, 'best-fit' assignment recommendations, and real-time conflict detection and warnings. The contractor shall ensure the RMS/AODB will interoperate cleanly with the separately-procured passenger processing platform and with the third-party IDS through documented, standards-based interfaces. Software licenses provided under this Agreement shall be enterprise-wide and shall support all potential authorized users as designated by the Airport.
We post new it & software opportunities in California as agencies publish them. Get them in one email — free, and unsubscribe whenever.
Most California work asks for the two below, and the solicitation documents are where it’s stated. One prequalification covers both — on this bid and the next.
A surety’s written statement that it expects to bond you up to a stated amount, subject to final underwriting. It’s what an agency asks to see before they take your bid seriously.
Source: City of San Francisco Bids (bid SFGOV~0000012090), retrieved via the City and County of San Francisco. View the official posting, and always confirm requirements and deadlines with the issuing agency.
