250 likes | 395 Views
CUPPS Update to AITSC. CUPPS Leadership Team. Samuel Ingalls (LAS): Chair Bill Heppner (AS): Vice-Chair Thomas Jeske (LH): Vice-Chair Larry Kretz (SITA): Technical lead. Background. “Seattle Summit” held with airports and airlines (2003)
E N D
CUPPS Leadership Team Samuel Ingalls (LAS): Chair Bill Heppner (AS): Vice-Chair Thomas Jeske (LH): Vice-Chair Larry Kretz (SITA): Technical lead
Background • “Seattle Summit” held with airports and airlines (2003) • Seeking common ground of collaboration on various fronts • Broken into three basic segments • Security, benchmarking and technology • In the Technology category: • CUPPS • FIMS • WiFi • Infrastructure
Background • Charter from JPSC (October 2004) to rewrite RP 1797 (CUTE) • Made an official sub-group of CUSS MG • Terms of reference developed • Geneva (November 2004) • TOR’s included airports • Name note (Thanks GTAA!)
Broad Industry Participation and Support Airports Council International RP 500A07
CUPPS Participants • AA • AC • ACI • AF • AirIT • Amadeus • AMS • APD • ARINC • AS • ATA • AttachMate • AUS • B6 • BA • BAA • Bahrain • Barich • BOM • Brock • CA • CAAS • CO • CPH • CX • DFW • DL • DMJM Aviation • EDS • Fraport • IATA • IB • IBM • IER • INK • JL • Kinetics • KL • LA • LAS • LH • LH Systems • MAN • Materna • MCO • MIA • NIIT • NW • PANYNJ • PDX • QF • RESA • Sabre • SAC • SAN • SAS • SFO • SITA • SQ • T Systems • TA • TravelSky • TSA • U2 • UA • Ultra • US • VIE • VS • Worldspan • WN • YUL • YVR • YYZ 74 Organizations, 180 Individual Participants
Status • Documents: • Recommended Practice document (final) • Technical Requirements document • Note: No similar document for CUSS • Draft Technical Specification document-95% • Work teams: • Network & Security • Software & Devices • Certification & Deployment, • Governance • Pilot Team • FIMS Team (tentative)
Foundational Principles • 1. Applications run on any platform • 2. CUPPS facilitates rather than mandates business processes • 3. CUPPS platform will have minimum, defined functionality • 4. Affordability • 5. Serviceability • 6. Predictability
Airport Benefits • Overall acceptance of common use • Lowering the barriers to entry • Enhanced competition among vendors • Differentiation based on service and price • Airport messaging • LDCS functionality • Dynamic signage
Airport Benefits • Ease of bringing new carriers into the common use fold • Flexibility around peripheral deployment and updates • Reduces total cost of ownership • Ease of platform deployment • Support for added security and remote management • Defined network requirements
After Approval? • Proof of Concept Trials begin: 2008 • CUPPS governing body established • CUPPS continues on as a living group and document • Trials completed end of Q1 2009 • Final Technical Specification published • Q2 2009 • Validation entity for platforms and applications • Provided by IATA/ATA/ACI • CUPPS Vendors • Three years legacy app support
Proof of Concept Trials • Trial Teams: • Three airports • Three vendors • Approximately four air carriers • Mix of international and U.S. domestic carriers Airport 1 Vendor 1 Air Carriers Airport 2 Vendor 2 Airport 3 Vendor 3
Proof of Concept Trial Outputs • Technical Specification functions as intended • True interoperability achieved • Test scripts developed • Platform • Application • Feedback to the Governing Body and the CUPPS MG
Next Steps • Finalize the Technical Specification • CUPPS conference calls • Every two weeks • Call Times: 0700 U.S. West Coast, 1000 U.S. East Coast; 1600 Geneva; 2200 PEK/HKG • Next meetings: • Dallas: 15 - 17 January • Geneva: 25 – 26 February • TBD (YVR?): 8 – 10 April
Looking to the Future… • CUSS under CUPPS?
Contact Info • Samuel Ingalls: sami@mccarran.com • Bill Heppner: bill.heppner@alaskaair.com • Thomas Jeske: thomas.jeske@dlh.de • Larry Kretz: larry.kretz@sita.aero