Kiosk Software Replacement System

The Vendor is required to provide implement a modern, passenger-facing common use self-service (CUSS) kiosk software platform system will enable shared-use passenger processing functions including check-in, boarding pass issuance, and baggage tag processing across multiple airlines.
- Functional requirements
1. Common use self-service (CUSS) platform capabilities
• The CUSS platform shall provide passenger-facing self-service functionality for check-in, boarding pass issuance, baggage tag processing, and related airline transactions using authoritative airline departure control systems (DCS) and coordinated multi-device interaction across kiosk components.
2. Core CUSS capabilities
• Real-time execution of passenger transactions including check-in, boarding pass issuance, and baggage tag generation through airline DCS integrations
• Secure, session-based transaction handling with immediate validation against airline systems of record
• Support for high passenger volumes with efficient session queuing, timeout handling, and transaction flow control
• Coordinated interaction across kiosk peripherals including printers, scanners, and payment devices
• Multi-language user interface capability
• Configurable, role-based management of application behavior, airline configurations, and user interface standards
• Centralized control of CUSS software configuration, airline onboarding, and operational policies
• Controlled administrative override capabilities limited to session management and kiosk availability (e.g., out-of-service, restart), not passenger data or airline transactions
• Coordination with airport operational systems where applicable (e.g., alerts, messaging), without impacting airline-controlled transaction logic
• Support for integration with external services such as payment gateways, document validation services, or airline-approved third-party APIS
• Support for rendering airline-provided user interfaces or web-based applications within a secure, managed CUSS runtime environment
• Clear separation between airline-authoritative transaction data and any locally managed session or presentation-layer information
3. Airline application hosting and execution
• Support for airline-provided applications or interfaces executed within the CUSS runtime
• Logical isolation between airline applications to prevent data leakage or cross-airline interference
• Support for multiple concurrent airline sessions across kiosk fleet
• Ability to onboard new airlines without requiring system redesign or hardware modification
• Centralized management of airline configurations, permissions, and deployment states
4. Passenger transaction flow management
• Clear step-by-step transaction workflows
• Session timeout and reset behavior
• Ability to cancel or restart transactions safely
• Prevention of incomplete or invalid transactions
• Clear passenger messaging throughout all transaction states
• Support for accessibility requirements (ADA/WCAG compliance)
5. Resilience and transaction handling
• Graceful handling of airline system latency or temporary unavailability
• Prevention of transaction initiation when required upstream systems are unavailable
• Clear differentiation between successful, pending, and failed transaction states
• Configurable fallback messaging when services are unavailable
• Automatic session termination and data clearing after inactivity or failure
6. Degraded operations and system behavior
• The system shall clearly notify passengers of service limitations
• Transactions requiring airline validation shall not proceed
• No boarding passes, bag tags, or confirmations shall be issued without real-time authorization
• The system shall not simulate or approximate airline responses
• Kiosks may be placed into controlled out-of-service or limited-service modes
• All degraded states shall be centrally configurable and consistently applied.