Common Use Terminal Equipment (CUTE) / Common Use Passenger Processing Systems (CUPPS)
Common Use Terminal Equipment (CUTE) / Common Use Passenger Processing Systems (CUPPS)
Common Use Terminal Equipment (CUTE) / Common Use Passenger Processing Systems (CUPPS)
SPECIFICATION
Content of CUTE/CUPPS
General Standards Design Requirements Structural Design IWS and Peripherals Integration Requirements
All peripherals and software shall be complied with both CUTE and CUPPS platforms
The CUTE/CUPPS system should be designed on IP-based protocols and must offer true end-to-end IP connectivity, from the mainframe
Standards Requirements
IATA Airport Terminals Reference Manual : The Contractor shall design,
manufacture and install the CUTE/CUPPS in accordance with the IATA Airport Terminals Reference Manual The CUTE/CUPPS solution should comply with the latest version of the IATA resolution 1797 (system functionalities and peripherals shall be complied with CUPPS) and 1774 (Protection of Privacy and Transporter Data Flows of Personal Data used in International Air Transport of Passengers and Cargo). Alternative internationally recognised industrial standards could be used but it must be equivalent or higher than the
Design Requirements
CUTE/CUPPS will use a high-speed LAN architecture fully redundant and resilient while providing flexibility and scalability CUTE/CUPPS should use TCP/IP as its LAN network protocol and Simple Network Management Protocol (SNMP)
Login authentication and network communications should be secured . Antivirus, firewall, and intrusion detection from multiple vendors should be integrated into both CUTE/CUPPS & CUSS
Technical View :
Integration Requirements
To the FIDS systems for above counter signage to allow check-in and boarding agents to locally control FIDS display To Revenue Management System : charging for CUTE/CUPPS services used by airlines, based on time based usage. To MIS, BHS and Airport Security System