Example: stock market

Common Processing Systems Recommended Practice

Airports Council InternationalRecommended Practice 500A07 Air Transport AssociationRecommended Practice Air Transport AssociationRecommended Practice 1797 CUPPS Issue: Updated:05 SEP2007 CommonUsePassengerProcessingSystemsRecom mendedPractice** FINAL **Airports Council InternationalRecommended Practice 500A07 Air Transport AssociationRecommended Practice Air Transport AssociationRecommended Practice 1797 CUPPS Issue: Updated:05 SEP2007 CommonUsePassengerProcessingSystemsRecom mendedPractice** FINAL **c 2005-2007, IATA. All rights edition: 03 JUN2007 Acknowledgments:AcrobatR is a registered trademark of Adobe Systems JRETMare trademarks of Sun Microsystems, , Internet ExplorerR , ExcelR is a registered trademark of Microsoft VistaTMis a trademark of Microsoft document was typeset using the LATEX ContentsBrief ContentsiContentsiiiList of TablesvList of Figuresvii1 Common Use Passenger Processing Systems (CUPPS)12 Overview53 CUPPS Technical Documentation Summary94 Roles and Responsibilities of CUPPS Parties215 Applicable Industry Standards23 Abbreviations25 References27 Index29 CUPPS-RP CUPPS Version Document Issue ** FINAL **iiiCo

Airports Council International Recommended Practice 500A07 Air Transport Association Recommended Practice 30.201 International Air Transport Association

Tags:

  System, Processing, Recommended, Processing systems recommended

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of Common Processing Systems Recommended Practice

1 Airports Council InternationalRecommended Practice 500A07 Air Transport AssociationRecommended Practice Air Transport AssociationRecommended Practice 1797 CUPPS Issue: Updated:05 SEP2007 CommonUsePassengerProcessingSystemsRecom mendedPractice** FINAL **Airports Council InternationalRecommended Practice 500A07 Air Transport AssociationRecommended Practice Air Transport AssociationRecommended Practice 1797 CUPPS Issue: Updated:05 SEP2007 CommonUsePassengerProcessingSystemsRecom mendedPractice** FINAL **c 2005-2007, IATA. All rights edition: 03 JUN2007 Acknowledgments:AcrobatR is a registered trademark of Adobe Systems JRETMare trademarks of Sun Microsystems, , Internet ExplorerR , ExcelR is a registered trademark of Microsoft VistaTMis a trademark of Microsoft document was typeset using the LATEX ContentsBrief ContentsiContentsiiiList of TablesvList of Figuresvii1 Common Use Passenger Processing Systems (CUPPS)12 Overview53 CUPPS Technical Documentation Summary94 Roles and Responsibilities of CUPPS Parties215 Applicable Industry Standards23 Abbreviations25 References27 Index29 CUPPS-RP CUPPS Version Document Issue ** FINAL **iiiContentsBrief ContentsiContentsiiiList of TablesvList of Figuresvii1 Common Use Passenger Processing Systems (CUPPS).

2 History ..22 of CUPPS .. Product Strategy .. vs. CUTE Summary .. Platform Standards.. Management Oversight .. to CUPPS Migration ..73 CUPPS Technical Documentation .. to the CUPPS-TR and CUPPS-TS .. Technical Documentation Ownership .. Privacy .. Data.. Data .. Data .. and/or Performance Data .. Logical system Architecture .. Logical system Architecture Summary ..16 CUPPS-RP CUPPS Version Document Issue ** FINAL ** .. Repository ..164 Roles and Responsibilities of CUPPS Providers Responsibility .. Providers Responsibility .. of Service Levels .. Information and Availability Figures .. and Deployment ..225 Applicable Industry Standards23 Abbreviations25 References27 Index29 CUPPS-RP CUPPS Version Document Issue ** FINAL **vList of Foundational Principles.

3 History .. vs. CUPPS Summary .. to CUPPS Migration Considerations .. of Data Privacy Rules .. Device Interfaces .. Workstation Components .. Platform Server Software Components .. Platform Workstation Software Components .. Recommend Practices Reference .. Resolutions Reference .. Resolutions Reference .. Document References ..24 CUPPS-RP CUPPS Version Document Issue ** FINAL **viiList of CUPPS Logical system Architecture .. CUPPS Logical system Architecture ..18 CUPPS-RP CUPPS Version Document Issue ** FINAL **1 Chapter 1 Common Use PassengerProcessing Systems (CUPPS) Recommended PracticeRECOMMENDED that, when an organization plans to operate shared passengerprocessing Systems in an airport or other Common environment, for the purposes ofsupporting multiple airline processes, the specifications and standards as described inthis Recommended Practice shall be IntroductionCommon Use Passenger Processing Systems (CUPPS) describes the range of services,specifications, and standards enacted to enable multiple airlines, service providers, orother users to share physical check-in or gate podium positions (whether simultaneouslyor consecutively).

4 The CUPPS scenario assumes a circumstance whereby an airlineor employee other service provider interacts with a passenger for check-in and boardingprocesses. This Technical Specification describes agent platforms that will accommodate,but not be limited to, check-in and boarding activities. Future developments may providefor other functions, both business and shows the CUPPS foundational CUPPS Version Document Issue ** FINAL **2 CHAPTER 1. Common USE PASSENGER Processing Systems (CUPPS) Revision HistoryTable shows the revision history for this : CUPPS Foundational PrinciplesPrincipleDescriptionPlatform IndependenceDifferences in legacy CUTE Platforms lead to ad-ditional application complexities and CUTE vendor-specific versions that must be maintained over Process Facilitation CUPPS provides a flexible Platform that facilitatesApplication functionality that may be used for a va-riety of business functions.

5 Minimum, Defined CUPPS Platforms must provide the functionality de-fined as required in the CUPPS Technical provides the tools and technologies that maylead to additional economies of scale and economiesof provides enhanced predictability in termsof deployment and overall platform and applicationmaintenance (duration, cost, etc.)ServiceabilityCUPPS provides the tools and technologies to in-crease efficiencies of application upgrades and CUPPS Version Document Issue ** FINAL ** REVISION HISTORY3 Table : Revision HistoryIssue 03 JUN2007 James McElhannon, SITA Continued initial draftCUPPS-RP CUPPS Version Document Issue ** FINAL **5 Chapter 2 OverviewThis section provides an overview of the benefits of CUPPS, its strategy as a product,the management oversight of the ongoing CUPPS activities, and migration Benefits of CUPPSA CUPPS implementation will enable airlines to provide passenger services in the contextof a shared check-in, gate podium, or major benefits of CUPPS are.

6 Efficient use of expensive facilities on- and off-airport, thereby reducing the needfor facility expansion. Flexibility for accommodating flight segment additions or deletions by carriers inthe use of space. The ability for an Application Provider to maintain a single CUPPS-compliantapplication that will be seamlessly functional on any CUPPS platform, regardlessof the particular Platform Provider. A platform that can easily accommodate various peripheral devices in support ofbusiness processes. An enabler for improved customer service. A flexible architecture to easily accommodate alterations in the passenger process-ing flow. An accommodation of the flow of data between emerging and evolving airportand airline Systems , as mutually agreed upon between the Platform Provider andApplication Provider.

7 Improved flexibility for system upgrades and new versions of software and CUPPS Version Document Issue ** FINAL **6 CHAPTER 2. OVERVIEW Enhanced ease of access to new markets, with overall predictability of cost magni-tudes from a technology deployment CUPPS Product StrategyThe CUPPS product strategy is to deliver a Common use Platform to support individualand shared airline processes at a shared workstation at check-in, gate, and other posi-tions, while maintaining the ability for users to maintain their brand images. The key tothe product strategy is an open architecture system where it is possible to use virtuallyany hardware or software that complies with CUPPS standards included in the CUPPST echnical Specification (CUPPS-TS).The functionality described is not exclusive; any future products and/or applications, asappropriate, may be introduced as business needs initial CUPPS strategy is focused on implementation in both the agent-assistedcheck-in and boarding environments on-airport and potentially in kiosk could also be carried forward to provide services at other venues such as rentalcar agencies, bus terminals, seaports, and railway development of the CUPPS product will initially be done collaboratively with thecooperation of airlines and airports, platform providers, and platform CUPPS vs.

8 CUTE SummaryThere are many differences between the legacy CUTE environment and the new CUPPS forward-looking environment. Table below provides a summary of the major CUPPS Platform StandardsThe CUPPS Platform comprises, at minimum, the hardware and software componentsdefined in the CUPPS-TS. The CUPPS Platform is envisaged to support a comprehen-sive range of airline and airport passenger processes and services. Initial focus of theproduct will be on passenger check-in (which could include baggage check-in) and board-ing. Devices within a CUPPS Platform shall only be used by applications initiated andoperated within the platform or diagnostic Providers are responsible for the delivery of particular application function-ality required to support the business processes of its physical components located at a particular airport shall be equally usable by allparticipating CUPPS Version Document Issue ** FINAL ** CUPPS MANAGEMENT CUPPS Management OversightA CUPPS Management Group (refer to Res.)

9 706 [1] and/or ATA Res. ) comprisedof airlines, airports, ACI/IATA World Business Partners and Associate Members willbe responsible for defining the certification process and amending the CUPPS standardsas published separately from this Recommended Practice , , the CUPPS-TS. Formalterms of reference will be developed for the ongoing Governance of this body and CUPPS Management Group will be a standing body tasked with the continuedmaintenance of this RP and the CUTE to CUPPS MigrationWith any next-generation standard or product, a mechanism must be provided to migratefrom the previous standard or product to the next-generation standard. This sectionprovides the migration considerations for moving from CUTE to the wide array of variations between CUTE implementations combined with thedifferences that exist due to the local business and operational scenarios at each CUTE location, there is no one migration strategy that is applicable across Suppliers.

10 Therefore,each Platform Provider and/or Platform Supplier that proposes a CUPPS solution mustprovide a reasonable and realistic migration shows the general considerations that each Suppliers migration strategy willlikely address. Not every item will be applicable for a given situation nor will the listpresented in Table constitute the entire list of considerations that every site mustcontemplate. These reflect examples of major Suppliers are not required to provide solutions to any or all of the considerationsgiven in Table , nor are the Suppliers prohibited from providing functionality that isoutside of the CUPPS specification. It is understood that CUPPS Suppliers will continueto offer solutions to customers based on mutually agreeable terms and :CUTE Suppliers are required to provide support for their ex-isting CUTE platforms for a period of three years from thedate of first publication of the CUPPS Technical CUPPS Version Document Issue ** FINAL **8 CHAPTER 2.


Related search queries