Specifications include, but are not limited to: 5.1 Passenger Processing System Currently, PMGAA utilizes a CUTE platform to enable passenger processing functionality for the airlines operating at Phoenix-Mesa Gateway Airport (Airport). The new passenger processing system will be a CUPPS compliant system that will facilitate the seamless sharing of physical check-in and gate counter positions among multiple airlines, ground handlers, or other users. Whether operating simultaneously or consecutively, these entities will utilize the facility with their respective host software and a standardized set of compatible hardware. Notably, this will be achieved without necessitating any specific software or equipment adjustments by individual airlines. The CUPPS-compliant platform for Departure Control System (DCS) applications will accommodate each airline operating on the CUPPS at the Airport during implementation. The CUPPS host interface solution will support the existing connectivity requirements of participating airlines. Furthermore, the solution will be flexible and adaptable, capable of accommodating new and additional airlines and accommodating future changes to PMGAA’s business model. 5.1.1 The comprehensive scope of the solution encompasses: a. Common Use Terminal Equipment b. Integration with Common Use Self-Service Bag Drop (planned for the future) 5.1.2 The proposed CUPPS solution will consist of the following: a. 32 check-in counter positions b. 22 gate counter positions 5.2 Content Management System (CMS) PMGAA seeks to replace its existing CMS with a new, feature-rich, versatile, and sustainable CMS. The goal is to meet the visual information display needs and requirements of airlines, the Airport, and passengers for the foreseeable future across PMGAA’s campus. The proposed CMS will seamlessly integrate into and support PMGAA's common-use environment and approach. It is envisioned to provide the airport with control over content across all connected devices. 5.2.1 The solution's scope, to be provided and configured, includes: a. Content Management System b. Content development for existing displays c. Content development for future displays d. Integration with Resource Management System e. Integration of a data feed for flight information 5.2.2 The scope includes the purchase of new 55” displays and Digital Display Controllers (DDCs), to facilitate the following types and counts of displays: a. Gate Backwall Displays: 16 b. Check-in Backwall Displays: 16 c. Flight Information Displays: 19 d. Information Displays: 10 e. Baggage Information Displays: 4 The scope also includes the purchase and integration of two (2) new Baggage Input Consoles. The consoles are to be located outdoors in close proximity to the existing baggage belt controls. The consoles must be rated for outdoor use, and able to withstand outdoor temperatures up to 120 degrees Fahrenheit and must be dustproof. 5.3 Resource Management System (RMS) PMGAA seeks to replace its RMS and Airport Operational Database (AODB) to improve its operational efficiency. The new system should improve RMS functionality including seasonal flight scheduling and easy schedule manipulation and updates, daily and irregular operations management, and leveraging internal and external sources of data for better decision-making and reporting purposes. In addition, the AODB should be considered the source of truth and integrate with other PMGAA systems to provide up-to-date and accurate data. 5.3.1 The scope of the solution to be provided and configured includes: a. Data Warehouse/reporting functionality b. Interfaces to other PMGAA systems c. CMS (flight information for FIDS, BIDS, GIDS, etc.) d. Real-time data feed (currently OAG FlightView)
