Bar-Coded Boarding Passes (BCBP) Implementation guide - IATA

More documents

Recommendations

Info

StB Bar Coded Boarding Pass Implementation Guide Field Name M / O Description Example Format Subtype Note Reply M Yes or No Boolean Reason code M* Code for the reason of a ‘no’ reply Integer Free text O Free text provided by the airline String Notes • The scope of the BCBP XML business requirements document is to define the format of messages exchanged between an airport security checkpoint and an airline system when a BCBP is scanned. • The scope is not to define how security agents decide which passenger can go through the checkpoints and how to communicate their decisions with the passengers. The BCBP XML messages do not interfere with the existing security processes. The BCBP XML schema is on the PADIS extranet: http://extranet2.iata.org/sites/padis_xml_typex_releases/default.aspx Recommendations • The BCBP XML schema is published to ensure that the airlines and third parties who wish to exchange BCBP data always do it in a consistent manner, to avoid uncessary duplication of efforts, potential misinterpretations and associated costs. • However the development of data exchange should be based on a multilateral local agreement. The BCBP XML schema is not encouraging such agreements, but wherever those agreements take place it recommends the most efficient implementation. • The message sent back by the airline system validates the authenticity of the bar code and the readiness of the passenger to fly. However the decision to let the passenger go through the airport security checkpoint remains an airport security’s decision. It is also the airport security’s decision to provide the passenger with explanation in case of refusal. 5.3. Boarding pass 5.3.1. Boarding pass history at a glance The industry defined the ATB2 in 1991 to replace the Transitional Automated Ticket (TAT) created in 1981. American Airlines started using 1D bar codes (code 128) on boarding passes in 1998 at selfservice and curbside check-in (see fig. 25). This was expanded to include flight check-in on aa.com as well. 44/128 27-May-2009
BCBP technical implementation Figure 26 - Boarding pass with a proprietary 1D bar code courtesy of American Airlines Alaska Airlines started putting 2D bar codes on their web boarding passes in 1999, and these passes allow up to four segments to be printed on one piece of paper, all in one bar code. IATA approved a standard for 2D bar codes on boarding passes in November 2004. Resolution 792 is known as the Bar Coded Boarding Pass standard. 5.3.2. Check-in data When the boarding pass is issued at check-in, the IATA standard requires the input of some specific data. Here is a typical flow of data introducing the PNR code (see fig. 22). Operating Carrier Carrier or Ground Handler 2 Print BCBP Reservation process (inventory system) 1 PNL / ADL Check-in process (Carrier or GH DCS) 3 Read BCBP Figure 27 - Data flow of passenger information at check-in 1. The reservation process of the operating carrier sends the Passenger Name Records (PNR) to the check-in process 2. The check-in process enables the printing of the BCBP, either at check-in desk, kiosk or on the web. Once the passenger is checked-in, a message is sent back to the check-in process 3. The BCBP are read at the gate, messages are sent back as flown The content of the Passenger Name List (PNL) and the Additions and Deletions List (ADL) are described in the Recommended Practice 1708. 5.3.3. Layout of the boarding pass Unlike Resolution 722c for ATB (see fig. 26), Resolution 792 for BCBP does not define a standard layout of the boarding pass. However the BCBP layout does have some constraints in order to guarantee readability. As layouts may vary from one airline to another, staffs need to be trained to read and accept the new documents. 4 th edition - June 2009 - www.iata.org/stb/bcbp 45/128
Page 1:
Simplifying the Business Bar Coded
Page 4 and 5: NOTICE DISCLAIMER. The information
Page 6 and 7: 6.7. Capacity planning ............
Page 8 and 9: Figure 53 - Data flow in a CUTE env
Page 11: 1. FOREWORD In developing and enhan
Page 14 and 15: StB Bar Coded Boarding Pass Impleme
Page 29 and 30: 4. IMPLEMENTING A BCBP PROJECT This
Page 31 and 32: Introduction The chart below (see f
Page 33 and 34: Introduction 9. CUSS kiosks: 2D bar
Page 35 and 36: Introduction The following items ar
Page 37 and 38: Introduction 4.5.5. Train The fifth
Page 39 and 40: Introduction BCBP IMPLEMENTATION MA
Page 41: Introduction The transition phase i
Page 50 and 51: 5.2.3. Encoding multiple flight leg
Page 52 and 53: 5.2.4. Version management Resolutio
Page 91 and 92: 7. MEDIA USED AS BOARDING PASSES Th
Page 93: Checklist and timeframe Figure 71 -
Page 104 and 105:
StB Bar Coded Boarding Pass Impleme
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132:
NOTES 4 th edition - June 2009 - ww
show all

Bar-Coded Boarding Passes (BCBP) Implementation guide - IATA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?