1. Aviation Information Data Exchange (AIDX) ACI – Europe IT Conference November, 2009 Yngvar Sundsfjord, COWI

2. AIDX Aviation Information Data Exchange –A standard format for exchanging flight data –Employs open, standard XML architecture –Utilizes standard IATA code sets –Developed by IATA “XML Working Group” –For JPSC and PADIS

3. An accepted standard ACI Recommended Practice 501A07 ATA Recommended Practice 30.201A IATA Recommended Practice 1797A PADIS Board approved 9.1 schema –From the XML WG; October 30, 2009

4. Why a standard format? Numerous flight data formats in use –Airline-airport and airport-system Creates high maintenance costs Desire to “Simplify The Business” Write one format for multiple uses Improve deliverability, reliability, stability

5. Brief history of AIDX 2003 ACI-NA “Seattle Summit” –3 airlines, 2 airports, 3 IT providers teamed up –Called “FIMS” for several years 2005 – first schema design 2007 – successful production use in DEN –The “7.1” schema deployed 2008 – sought international confirmation

6. AIDX as world standard To increase acceptance and deployment Incorporated AIDX into CUPPS –CUPPS Recommended Practice revised February, 2008 to reference AIDX Drafted international AIDX configuration –Working with PADIS - XML Working Group –Uses common IATA code sets and references –In synch with other developing XML schemas

7. Who is on board with AIDX Airlines Air Tran Alaska American BA Continental Delta Frontier Northwest Sun Country United AirTran Airports DEN Detroit IND JFK T-7 LAS MSP Orlando Portland RDU San Francisco Seattle Sydney Vendors ARINC Com-Net ERA IBM InterSystems ITS SITA Ultra Electronics HMS Host CSE Int’l FlightStats FlightView

8. Next Steps for AIDX Complete the Implementation Guide Make schema and documents available –IATA extranet site –CUPPS.AERO site –AIDX.AERO web site being crafted Support new projects

9. Next Steps for AIDX Interest in AIDX (no commitments) –InterSystems at Vancouver –SITA with CO and Type-X proof of concept –Sabre Airline Solutions –American Airlines –Northwest: 7.1 in use at IND –United: 7.1 in use at 6 cities; 5 pending –Frontier: partnering with FlightView at DEN –LAS and DEN: pilot and production efforts

10. Next Steps for AIDX Interest in AIDX (no commitments) –Specified in SFO AODB/FIDS/RMS project by ARINC (4Q 2009). –Specified for Blaise Diagne International Airport in Dakar, Senegal (4Q 2010) –AirTran waiting on specs to drive next step

11. Next Steps for AIDX Interest in AIDX (no commitments) –Cairns Airport waiting on vendor specs –Portland will incorporate in new projects –Delta at 9 airports; requests will drive next step

12. Questions?