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

More documents

Recommendations

Info

StB Bar Coded Boarding Pass Implementation Guide The format includes a "For individual airline use" field. The field size allows up to 255 characters per segment (from 00 to FF in ASCII-printed hexadecimal), or a total of 1020 characters for the 4 segments. Bar code readers work well on PDF417 reading up to 800 characters in one symbol. Although the standard allows up to 4 segments, it is unlikely to find boarding passes including 4 segments, each of them with more than 200 characters for airline individual use. It is recommended that the owner of the bar code reader performs a test with a worst-case scenario bar code containing the maximum number of characters allowed by the M format with 4 segments encoded. The read error rate should be calculated with this configuration. The issuer of the boarding pass should perform similar tests on the size of the bar code printed on boarding passes, to prevent incidents such as a bar code that does not fit on the boarding pass (see fig. 20). Figure 21 - Test of bar code size courtesy of Lufthansa Systems A survey of the samples provided by 30 airlines using BCBP shows that it would be possible to define a maximum and minimum size for the bar code (see fig. 21). That would enable scanners to have a sufficient resolution to read smaller codes and a sufficient window size to cope with larger codes. Bar code size Min Max Average Number of columns 4 12 7 Number of rows 9 34 18 Length (mm) 29 72 50 Height (mm) 9 22 13 Dim (Height/Rows) 0.35 1.11 0.79 Figure 22 - Bar code average size of BCBP samples For an optimal read rate it is recommended to design bar codes that aim at the average size above, and to ensure that all the equipment used will produce bar codes within the range above. 36/128 27-May-2009
BCBP technical implementation 5.2. BCBP Standard (Resolution 792) 5.2.1. Data format Airline issue one boarding pass per passenger. Before the BCBP standard, airlines issued one boarding pass per flight leg (if an itinerary segment contains two legs with the same flight number, one boarding pass per leg is needed to indicate the seat number). The BCBP standard enables airlines to encode either one flight leg or several legs into a single bar code and boarding pass. The format of the data in the 2D bar code is defined in the BCBP standard. For a definition of terms used in the items, refer to the IATA RP 1008 ‘GLOSSARY OF COMMONLY USED AIR PASSENGER TERMS’. Definitions • “OPERATIONAL LEG” means a flight that is physically operated and identified by its airline designator and flight number. Any other airline designators and/or flight numbers associated with the same flight are considered to be non-operational flights. • “FUNNEL FLIGHT” means a flight composed of two or more member flights, which is identified by the airline designator and flight number of one of the members. Legs AD and DE comprise Segment AE (ADE), and are identified by the member flight number DL 123. Recommendation The standard requires that airlines populate: • All the mandatory items. If an item is not available at time of issuance of the boarding pass (e.g. seat number for a stand-by passenger), the item should be populated with blanks, so that the number of characters is correct. • The conditional items available in their system. If an item is not used by the airline system for the flight (e.g. document verification or selectee indicator), the item should be populated with blanks. The size of the field can be defined if some of the last fields are not used. • The airline individual use item at their convenience. An item defined in the mandatory or conditional field should be encoded in those fields, not in the airline field. The BCBP standard contains fields and items defined and agreed by airlines. It is in the interest of the airline to strictly comply with the data format, so that interline partners and third parties can read the data. If the data do not comply with the standard format, the passenger will have face the consequences of the partner or third party requiring the bar code data, e.g. the operator of a lounge or fast track scanning boarding passes to grant access to the facility. There are 3 levels of 2D bar code non-compliance with the BCBP standard: Level Description Consequence 1 - Item formatting The item is not formatted correctly, e.g. leading zeros or trailing blanks missing 2 - Item value The value encoded is not defined, e.g. a proprietary value for compartment code or seat number 3 - Field formatting The field does not contain the correct items, or items do not have correct lenghts Risk of un-readable value Un-readable value Un-readable bar code 4 th edition - June 2009 - www.iata.org/stb/bcbp 37/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 96 and 97:
StB Bar Coded Boarding Pass Impleme
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
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

Create successful ePaper yourself

Delete template?

Save as template?