Airport Data Exchange Protocol Airport Process Design Ron Hiscox AITSC, Madrid, December 13, 2007

Airport community members need to share data due to increasingly shared passenger processes:  Check-in process  Baggage sortation  Security checkpoint  Baggage drop-off  Retail concessions  Boarding  Passenger tracking  APIS data, watchlist links ADEP Background

Development of the ADEP Protocol to allow:  Data aggregation  Application development  Implementation of shared processes ADEP Requirement

The ADEP Recommended Practice should:  Define the ADEP architecture  Define the data interchange (XML schema)  Reference and adapt the required technical standards  Define implementation guidelines for data viewing and modification (data access rights)  Define data fields (mandatory/optional) ADEP Recommended Practice

ADEP Architecture Airlines Data SourcesADEP Community Applications Airport Community XML Interface ADEP Data Fields Security Bag Drop Concessions Airport Planning

Security / Access control  Validation of barcoded boarding passes / tokens Common bag drop points  Activation of bag tags  Bag tag / boarding pass reconciliation Concessionaires  Identify eligibility for tax free purchases  Customer relationship management Airport Planning  Passenger tracking  Process throughput and management  Simulation and modelling Airport Community Needs Security Bag Drop Concessions Airport Planning

AITSC Actions:  Agree on the principles of the Airport Data Exchange Protocol  Agree on the proposal to set up a working group  Agree on participation from AITSC airport members ADEP WG Actions  Establish guidelines and Terms of Reference for the working group  Establish a timeline, milestones and next steps Next steps / Actions