IATA may maintain a repository of carrier-approved logos, for use by approved IATA associates or ACI member airports to enable the associates to find the latest approved version of carrier approved logos (or others, such as those used by ground handlers) for use on systems including CUPPS, FIMS, etc. It is recommended that the repository contain a variety of logos for each carrier, with descriptions for proper use (for a light background, for a dark background, for small logos on individual lines of FIMS displays, etc.). Additionally, each logo should be made available in a format scalable to a variety of display sizes so that the logo can be viewed without distortion. Every effort should CUPPS-RP — CUPPS Version 01.00 — Document Issue 00.00.5021 — *** FINAL ***
3.6. LOGO REPOSITORY 17
be made to provide enough information about each logo and its intended use, so as to reasonably ensure the logo will be correctly displayed.
18 CHAPTER 3. CUPPS TECHNICAL DOCUMENTATION SUMMARY
Figure 3.2: Detailed CUPPS Logical System Architecture
CUPPS-RP — CUPPS Version 01.00 — Document Issue 00.00.5021 — *** FINAL ***
3.6. LOGO REPOSITORY 19
Table 3.2: CUPPS Device Interfaces
Abbrev. Interface Support
BS Bag Scales Defined, Not Required
MS Magnetic Card Reader Defined, Required DD Display Devices (Signage) Defined, Not Required
PO Point of Entry Defined, Not Required
OC Optical Character Recognition Defined, Required
x Passport Defined, Not Required
RW Raw Devices Defined, Required
RB RFID Bagtag Printer Defined, Not Required
x Still Cameras Defined, Not Required
BC Barcode reader Defined, Required
PR Printer Defined, Required
Table 3.3: Required Workstation Components
Function Description
Computer The computer and its internal components.
Keyboard A standard 101+-key keyboard is required for each end-user workstation per local configurations.
Pointing Device A pointing device is required for each workstation.
Touch Screen A touch screen is required to support the check-in and boarding functionality required by airlines and airports.
Windows Operating System Services
Windows provided print spooler, file access, memory man-agement, etc.
Table 3.4: CUPPS Platform Server Software Components
Function Description
CUPPS platform functionality CUPPS Suppliers may implement software com-ponents on the CUPPS servers as they deem ap-propriate.
Operating System(s) CUPPS Suppliers are free to implement any op-erating system on the server hardware that sat-isfies CUPPS-TS.
20 CHAPTER 3. CUPPS TECHNICAL DOCUMENTATION SUMMARY
Table 3.5: CUPPS Platform Workstation Software Components
Function Description
Application Management CUPPS platforms must implement application man-agement functionality appropriate to support the CUPPS platforms.
Authentication Platforms must provide authentication services for users onto the workstation and local network re-sources.
COTS Software COTS applications must be well-behaved and must not pose any unreasonable performance or security impacts to the platform or local network.
Application Requirements Applications must be well-behaved, with no unrea-sonable performance impacts, security risks to the platform or local network.
Event Management Platform must implement an event management functions for application and platform events.
Hardware Abstraction Layer (HAL)
Platforms must provide a HAL that shields applica-tions from the Supplier, firmware, and connectivity of the peripheral.
Logging Platforms must provide a logging interface appropri-ate for application support and debugging purposes.
Menus Platforms must provide a Menu system with appro-priate security.
Alerts Platforms must provide security alert distribution by authorized administrators
Operating System Workstations must use an operating system as de-fined in the CUPPS-TS.
Permissions Platforms must manage and secure access to the plat-form, network resources, and user or airline data.
Platform Management Platforms must provide management functionality to facilitate the administration, support, and usage.
Software Distribution Platforms must provide a mechanism to distribute software
Storage Platforms must provide an interface for secure stor-age of data in or persistent areas.
Supplier CUPPS applications work across CUPPS implemen-tations.
World-Wide Naming Standards
A world-wide naming convention for the naming of CUPPS workstations and peripherals.
Performance Platform performance must meet or exceed defined parameters.
CUPPS-RP — CUPPS Version 01.00 — Document Issue 00.00.5021 — *** FINAL ***
21
Chapter 4
Roles and Responsibilities of CUPPS Parties
This section addresses the roles and responsibilities of the various CUPPS parties, as they pertain to overall system provision and maintenance.
To ensure a consistent interpretation of the material below, please note these definitions:
• Supplier A supplier is the entity that creates the system. Suppliers market their products and services to Providers.
• Provider A provider is the entity that acquires the system from a Supplier and provides it to the user community.
4.1 Platform Providers Responsibility
The Platform Provider will, as defined in the SLA, ensure that:
• The CUPPS Platform is operational and usable during the specified operational hours.
• The CUPPS Platform is functioning and certified according to CUPPS standards.
• Software levels and version control of the Platform are maintained for the site.
• Statistical and management information is available.
• Notification is made to the Application Provider of faults that cannot be resolved.
• That the ability exists to disable an application if it is deemed to be causing other applications and/or the CUPPS Platform to malfunction. If this is the case they will endeavor to inform the Application Provider in advance.
• CUPPS Workstation locations are to be locally and mutually agreed upon.
22 CHAPTER 4. ROLES AND RESPONSIBILITIES OF CUPPS PARTIES