Common-Use Airport Systems: CUTE, CUPPS, CUSS and Common-Use Bag Drop

A query like "common-use passenger processing system for King Salman Phase II" points at one of the foundational IT decisions in any large terminal: whether check-in desks, gates, bag-drops and kiosks belong to a single airline or are shared infrastructure that any airline can log into. Common-use systems are what let one physical check-in counter serve Emirates in the morning and a different carrier in the afternoon. This brief explains the common-use concepts and the acronyms — CUTE, CUPPS, CUSS, common-use bag drop — and what a Gulf airport buying or upgrading them should weigh, anchored to the IATA standards rather than any vendor's marketing.

What "common use" means and why airports want it

In a dedicated model, an airline owns its check-in row and gate equipment; the desks sit idle when that airline is not operating. In a common-use model, the airport (or its IT provider) owns the workstations, kiosks, gates and bag-drops, and any airline's departure-control system (DCS) runs on that shared hardware through a common-use platform. The airport gains far higher asset utilisation, flexibility to re-allocate counters and gates by time of day, and the ability to grow airline capacity without proportionally growing the physical footprint. For a large, fast-growing Gulf hub serving dozens of carriers, common use is effectively the default for new terminals.

The acronyms — what each one is

• CUTE — Common Use Terminal Equipment. The original generation of common-use platform: a proprietary middleware layer that let multiple airlines' applications run on shared airport workstations. CUTE was effective but vendor-specific, which created lock-in and interoperability friction between airports running different CUTE platforms.
• CUPPS — Common Use Passenger Processing Systems. The IATA standard (Recommended Practice 1797) that succeeded the CUTE concept. CUPPS standardises the platform interface so that an airline's certified application runs on any compliant CUPPS platform at any airport, regardless of which vendor supplied it. CUPPS is the interoperability standard the industry moved toward to break the lock-in of proprietary CUTE.
• CUSS — Common Use Self-Service. The IATA standard (Recommended Practice 1706) for shared self-service kiosks — the check-in kiosks any participating airline's application can run on. CUSS lets one bank of kiosks serve many airlines.
• Common-Use Bag Drop (CUBD). The shared self-service or agent-assisted bag-drop equivalent, increasingly governed by IATA guidance and integrated with CUSS kiosks so a passenger can check in and drop a bag on shared equipment end to end.

The relationship is roughly: CUPPS is the modern standard for shared agent positions (check-in desks, gates), CUSS is the standard for shared self-service kiosks, and CUBD extends self-service to bag drop. CUTE is the legacy term many people still use loosely to mean "common use" in general.

How the pieces fit together

A modern common-use deployment usually combines:

• CUPPS platform running on shared check-in and gate workstations, hosting each airline's DCS application.
• CUSS kiosks for self-service check-in.
• Common-use bag drop (self or assisted) feeding the BHS.
• A common-use network and back end managing user sessions, peripheral sharing (boarding-pass printers, bag-tag printers, document readers, payment), and airline application provisioning.
• Increasingly, biometric and "off-airport"/mobile processing, where the common-use platform integrates with biometric identity (face-on-the-move at bag-drop, security and boarding) under IATA's One ID direction.

Peripheral standards matter: shared printers, scanners and readers must work across every airline application on the platform, which is exactly what the IATA standards exist to guarantee.

The standards and bodies

• IATA RP 1797 (CUPPS) — the common-use passenger-processing interoperability standard.
• IATA RP 1706 (CUSS) — the common-use self-service kiosk standard.
• IATA One ID — the strategic direction for biometric, document-free passenger processing, which common-use platforms increasingly support.
• IATA Resolution 753 — baggage tracking, relevant where common-use bag drop feeds the BHS.
• Local civil-aviation and data-protection rules (GCAA, GACA, QCAA and national data-protection laws) govern biometric and passenger-data handling.

Specifying standards compliance (CUPPS, CUSS) rather than a proprietary platform is the single most important procurement decision, because it preserves airline interoperability and avoids the lock-in that made the original CUTE generation painful.

GCC-specific considerations

• Scale and carrier mix — Gulf hubs serve many airlines and very high peaks; the platform must scale and re-allocate resources dynamically.
• Biometric ambition — several Gulf airports are moving aggressively toward biometric, document-light journeys, so the common-use platform's One ID and biometric integration roadmap is a real evaluation factor.
• Bilingual passenger interfaces (Arabic/English) on kiosks and bag-drops are expected.
• Data residency and privacy — biometric and passenger data handling must comply with local data-protection regimes; clarify where data is processed and stored.
• Integration with the BHS and DCS estate already in place, and with the airport operational database (AODB) and resource-management systems.

What this means for procurement

Start from interoperability: specify CUPPS- and CUSS-compliant platforms so any airline's certified application runs on the shared estate, and so you are not locked to one vendor's proprietary stack. Then layer the requirements that matter for a modern Gulf hub: dynamic resource allocation at scale, common-use bag drop integrated with the BHS, a credible biometric/One ID roadmap, bilingual interfaces, and data-residency compliance. The major common-use and passenger-processing vendors include SITA (which now owns Materna IPS, trading as "IPS, a SITA company"), Amadeus, Damarel, RESA and Embross, among others; many also provide the biometric and bag-drop layers. The standard comes first, the platform second — a proprietary, non-interoperable common-use system recreates the very lock-in the industry spent two decades escaping.