### BEFORE THE

DEPARTMENT OF TRANSPORTATION

WASHINGTON, D.C.

Notice of IATA Traffic Conference

Actions Tentatively Exempted

From Filing for Approval Docket OST

- 2012

- 0058

NOTICE OF TIER 1 AGREEMENTS FILING

BY THE

INTERNATIONAL AIR TRANSPORT ASSOC IATION

1 4 August 2013

Communications with respect to this

Document should be sent to

Douglas Lavin

Regional Vice President

– North America

International Air Transport Association

1201 F Street, NW, Suite 650

Washington, DC 20004

(202) 628

- 9292

### Summary DOCKET: DOT

- OST

- 2012

- 0058 DOT ORDER: None Requested

Date: 1 4 August 2013

Filing fee/IATA Acct: Waived by Order 2012

- 4

- 18, Appendix

A, Section D

US/UST involved Yes

Intended effective date: 1 June 201 1

Meeting site, date: 3 2 nd 

### Pass enger Services Conference

(PSC), Geneva

, 21 October 201 0

Agreement(s)/Minutes PSC/RESO/1 49 bis dated 14 August

2013

PSC/MINS/038 dated 23 February 2012

Resolutions 003, 701, 720a, 722, 722a,

722c, 722f, 722g, 722h, 725b, 725c,

725 d , 725 f

, 725g, 725h, 726, 726e, 728,

7 31a, 735, 735d, 740, 742e, 745 , 763,

780

, and 7 92

.

Recommended Practices 1008, 1701 f

, 1707, 1707b, 1708, 1715, 1719 d, 1720a,

1721, 1745, 1773b, 1788, and 1 800

.

### NOTICE OF TIER 1 AGREEMENTS FILING

Pursuant to statements submitted by Member a irlines of the International Air Transport

Association (IATA), the undersigned has been constituted to be their attorney

- in

- fact for filing

with the Department of Transportation copies of agreements adopted by the IATA Traffic

Conferences.

On their behalf, and pursuant to the procedures specified in Order 2012

- 4

- 18 (13 April

2012), I am filing with the Department, in Docket OST

- 2012

- 0058, this Notice, the subject

agreements and supporting documentation. These agreements are Tier 1 agreements tentatively

ex empted by Order 2012

- 4

- 18 from Condition #2 to the Department’s approval of the Provisions

for the Conduct of the IATA Traffic Conferences, which condition requires pre

- implementation

Department review.

The subject agreements amend or establish Resolutio ns and/or Recommended Practices

that do not address subject areas which the Department has indicated it still chooses to review

under Condition #2. The text of the agreements and other conference documentation sent to

airline Members of IATA accompany thi s Notice. The cover pages of the documentation clearly

identify each affected Resolution and /or Recommended Practice and show whether the subject

agreements are amendments or new agreements. Other pages provide the text of each subject

agreement. Where an affected Resolution or Recommended Practice has previously been

exempted from Condition #2 by Department action, the cover pages include the appropriate

docket and order number. The cover pages include a summary to explain the nature and purpose

of the subject amendments and/or agreements.

### - 2

-

13461343.1 

### Respectfully submitted,

/s/ Douglas Lavin

Douglas Lavin

Regional Vice President

– North America

International Air Transport Association

Attorney

- In

- Fact

### - 3

-

13461343.1 

### CERTIFICATE OF SERVICE

A copy of this notice ha s been served this day by first class or priority mail on the

following person:

Chief, Transportation, Energy & Agriculture Section

Antitrust Division

Department of Justice

Washington, D.C. 20530

A copy of this notice has been sent this day by email to John Kiser (John.Kiser@dot.gov)

and to Della Davis (Della.Davis@dot.gov) of the Department of Transportation.

/s/ Douglas Lavin

Douglas Lavin

14 August 2013

Date Served

### - 4

-

13461343.1

# MINUTES

30 th 

## Joint ATA/IATA Passenger Services Conference (JPSC)

32 nd 

## IATA Passenger Services Conference (PSC)

Geneva

21 October 2010International Air Transport Association

Route de l’Aeroport 33

PO Box 416

CH - 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2724

Fax +41 22 770 2662

www.iata.org E-Mail: bruyerep@iata.org 

## M E M O R A N D U M

PSC/MINS/034

TO: All Members, Passenger Serv ices Conference - Accredited

Representatives

All Members, Joint ATA/IATA Passenger Services Conference -

Accredited Representatives (ATA members via Ms P. Edwards)

COPY: IATA Strategic Partners

FROM: Head, Passenger Interline Standards

DATE: 15 April 2011

SUBJECT: "PASSENGER WEEK 2010"

MINUTES

30th Joint ATA/IATA Passenger Services Conference (JPSC)

32 nd 

### IATA Passenger Services Conference (PSC)

Geneva 21 October 2010

Please find attached the Minutes of the 30th Joint ATA/IATA Passenger Services

Conference (JPSC) and the 32nd IATA Passenger Services Conference (PSC) as

approved by the Chairman.

The “expedited Resolutions and RPs” referr ed to in these Minutes are issued under

cover of Memorandum PSC/RESO/148 dated 29 October 2010

The “book of finally adopted resolutions & RPs” referred to in these Minutes are issued

under cover of Memorandum PSC/ RESO/149 dated 15 April 2011.

Michael MullerInternational Air Transport Association

Route de l’Aeroport 33

PO Box 416

CH - 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2724

Fax +41 22 770 2662

www.iata.org E-Mail: bruyerep@iata.org

# M I N U T E S

30th Joint ATA/IATA Passenger Services Conference (JPSC)

32nd IATA Passenger Services Conference (PSC)

Geneva, 121 October 2010

TABLE OF CONTENTS

Agenda

Item Subject Page

Number



### ADMINISTRATION

A1 Opening of Meeting 1

A2 Examination of Credentials of Accredited Representatives 1

A3 Approval of Minutes – JPSC/29 and PSC/31 1

A4 Status of PSC Resolutions and RPs 1

A5 Effectiveness Date of Am endments to Industry Standards 2

A6 Election of Chairman and Vice-Chairman 2

A7 Any Other Business 2

A8 Date and Place of Next Meeting 2

POLICY

P1 Report – Status of Industry Coding Systems 2

P1.1 Release of ISO Country Codes for Generic Tax, Fee, (TFC)

Charges Usage 2

P2 Assignment Criteria for Airli ne Designator, Location Identifier and

Accounting Codes (Resolutions 762, 763 and 767) 3

P3 Adding an Airport to an Exis ting Metropolitan Area (Resolution

763) 3

P4 Ratification of Special Fees and Charges Codes (Resolution

728) 4

### Agenda

Item Subject Page

Number



### P5 Report – BSP Form Codes and Document Supply Chain 4

P5.1 Form Codes (ATA Resolution 20.40 / IATA RP1720a) 4

P6 Alliance Code and MITA (Resolution 780) 4

P7 Opt Out of Accepting P aper Miscellaneous Documents for

Interline Travel (Resolution 780) 4

P8 ZED-MIBA Forum – Sunset of P aper Tickets for Interline Staff

Travel 5

P9 Paper Out Strategy 5

P10 Report – Simplifying the Business (StB) 5

P10.1 Report – Automated Baggage Rules Task Force (ABRTF) 5

P10.2 Presentation: IATA e-services 6

P11 XML Standards of the Future 6

P12 Co-ordination with the Commission of European Communities

(CEC) on PSC Matters 6

P13 Co-ordination with the US Depar tment of Transportation (DoT) –

Initiative for Self-Assessment 6

P14 Report - Agency Solutions Technical Working Group (ASTWG) 7

P15 Glossary of Terms 8

P16 Tax/Fee/Charge Code for Ai rport Charges (Resolution 728) 8

P17 Changes to MITA to Support Simplifying Interline Settlement

Project in Rev enue Accounting. 9

AIRPORT SERVICES

B1 Report of the Airport Services Committee (ASC) 9

B2 Report of the IATA Ground Handling Council

(IGHC) 9

B3 Report – Fast Travel – Pa ssenger Experience Management

Group (Resolution 705) 9

B3.1 Self-Service Baggage Check- In (Recommended Practice 1701f) 9

### Agenda

Item Subject Page

Number



### B3.2 Updates to Bar Coded B oarding Pass (Resolution 792) 10

B3.3 Amendment to Resolution 792 10

B4 Report of the Baggage Working Group (BWG) 10

B5 Report of the DCS Messages Working Group (DCSMWG) 10

B6 Dangerous Goods in Passeng er’s Baggage (Resolution 745) 10

B7/P Packaged Items (DCSMWG) 11

B7.1/P Consistent format for names on DCS messages 11

B7.2/P Use of Party/Gr oup Identification Element 11

B7.3/P Editorial for INFT example 11

B7.4/P Correction to example in TPL 11

B7.5/P Updates to API DOCO element in DCS to match RES format 11

B7.6/P Editorial repairs to RP 1707 11

B7.7/P SSR MEQT in DCS 12

B7.8/P Discussion on length of name field 12

B7.9/P Guideline for placing Group PNRs on PNL/ADL 12

B7.10/P SSRs based on Leg or Segment 12

B7.11/P New wheelchair code WCLB 12

B7.12/P Wheelchair codes for general use 12

B7.13/P SSR codes for service animals 12

B7.14/P Editorial for PNL/ADL 12

B7.15/P Editorial for PNL/ADL 12

B8/P Packaged Items (BWG) 13

B8.1/P Compliancy of the format of t he “Aircraft compartment” in the .U 13

### Agenda

Item Subject Page

Number



### element with all the Aircraft type positions

B8.2/P .S Changes to support Bag Validation Status 13

B8.3/P Clarification of Secondary Code ‘H’ in .J Element of a BPM 13

B8.4/P Extra sub element in the .U 13

B8.5/P Amendments to RP1800 Se ction 6 Process Specific Baggage

Codes 13

B8.6/P Amendments to RP18 00 Section 5.2 Sortation 14

B8.7/P Amendments to RP 1800 Section 5.3 Screening 14

B8.8/P Amendments to RP1745 Se ction 10 Baggage Request Message

(BRQ) 14

B8.9/P Amendments to RP1745 Section 2.2 14

B8.10/P Amendments to RP1745 Section 3, BTM 14

B8.11/P Amendments to RP1745 Se ction 4 Baggage Source Message

(BSM) 14

B8.12/P Amendments to RP1745 Se ction 5 Baggage Process Message

(BPM) 15

B8.13/P Amendments to RP1745 Section 6 Baggage Unload Message

(BUM) 15

B8.14/P .E Exception types 15

B8.15/P Amendments to RP1800 Section 5.9 Of floading/Reloading 15

B8.16/P Amendment to RP1745 Sect ions 1.6 and 10.8 to correct

typographical errors 15

B8.17/P Amendment to RP 1745/30.45 section 2.1.1 15

B8.18/P Discrepancies between IATA Reso 740 and ATA 30.35 15

B8.19/P Change of wordi ng in BTM Section 3.2.4 16

B8.20/P Change of wordi ng in BSM Section 4.2.3 16

### Agenda

Item Subject Page

Number



### B8.21/P Remove incorrect el ement in BTM section 3.9.6 16

B8.22/P Format description of the ULD in the .U element 16

B8.23/P Amendments to RP1800 5.10 Tracing 16

B8.24/P Amendments to RP1800 5. 11 Intermodal Receipt/Intermodal

Delivery 16

B8.25/P Amendments to RP1800 Section 5.4 Reconciliation 17

B8.26/P Amendments to RP 1800 Section 5.5 Tracking 17

B8.27/P Amendments to RP18 00 Section 5.6 Rerouting 17

B8.28/P Amendments to RP18 00 Section 5.7 Reflighting 17

B8.29/P Amendments to RP 1800 Section 5.8 Retagging 17

B9 Proposal for amendments to RP1745/30.45 and RP1800/30.49 17

B10 Explicit the use of the 10 License Plate Code 17

B11 Pro Rata of International Travel 18

TICKETING

T1 Report of the Ticketing Committee

Selection of Committee Member ship for the IATA Passenger

Forms and Procedures Committee (PFPC) 18

T2/P Ticketing “Package” 18

T2.1/P Add Reference to 725h in 722f ET & EMD Glossary 19

T2.2/P Fare Calculation Coupon Fi eld Listed Twice in 725g Matrix 19

T2.3/P Remove EMD from P= print Option in Transaction Action 19

T2.4/P Synchronize the Definitions of EMD Value Coupon, ET Flight

Coupon, and EMD-A (ATA only) 19

T2.5/P Remove “in connection” from EMD Value Coupon Definition 19

### Agenda

Item Subject Page

Number



### T2.6/P Inconsistent Resolutions for EMD-A group names 20

T2.7/P Acceptance of Discover Cards in the BSP 20

T2.8/P Acceptance of Diners Cards in BSP 20

T2.9/P Credit Card as FOID Masking 20

T2.10/P Discrepancy – Definition of Ticket Handler 20

T2.11/P Obtaining Coupon Control for Inadmissible Passengers 21

T2.12/P Rescission of Redundant Ticketing Resolutions 21

T2.13/P Text Changes for MCO and MPD Resolutions 21

T2.14/P XML, or PADIS standards, to be used with ATA 20.65 21

T2.15/P EMD With Surface Segments 21

T2.16/P EMD-A Coupon Associ ation to ARNK Segments 21

T2.17/P Consequential Amendm ents to the Data Elements Glossary

‘Segment Identifier’ 21

T2.18/P New Reissue ticket number or EM D number in Change of Status

to Exchange/Reissue. 22

T2.19/P Add FOID Information in Refund Response 22

T2.20/P Add RFIC and RFISC in History Display Response 22

T2.21/P Editorial change: align t he verbiage of sending multiple

times Change of Status and System Update to System Cancel

one. 22

T2.22/P Editorial change: clarify and ali gn the status allowed for

System Update. 22

### Agenda

Item Subject Page

Number



### T2.23/P Editorial c hange: Replace CRS/System Provider by

Validating Carrier in EMD – Airline resolution. 22

T2.24/P EMD: Multiple Coupons with Same Board and Off-Points 23

T2.25/P Should UAC Message be Defined for EMD? 23

T2.26/P Amendment to Defini tion of Marketing Carrier 23

T2.27/P Contradiction between Record Level and Coupon Level

Association 23

T2.28/P Responsibility for Disassoci ating an Already Associated EMD 23

T2.29/P Amendment to System Update 24

T2.30/P Amendment to Change of Status – Move Synchronization

Paragraph 24

T2.31/P Amendment to Resolution 725f Section 6.5.9 C hange of Status 24

T2.32/P Data Elements for Additiona l Services Missing from Matrices 24

T2.33/P Review f Form of Payment Credit Card Code in Resolution 728 24

T2.34/P Amend Amendment to RP1721 for Process Clarification 24

T2.35/P T2.21 JPSC IROPS NVA/ NVB to be Used. JPTC March –

Agenda Item 13. 25

T2.36/P Involuntary Rerouting Fare Basis to be Used – Deferred from

March JPTC Agenda item 16 25

T2.37/P Revised Surcharges Resolution 25

T2.38/P Editorial Corrections to PSC Resolutions Manual 25

T2.39/P Consequences of changing ‘C redit Card’ to ‘Payment Card’ 25

T2.40/P E-ticket Display After Agent Migration from a GDS to Another 26

T2.41/P Period of Validity 26

T3 ‘Void Exchange’ and ‘Refund Cance l’ Alignment to ‘Void Original

Issue’ 26

### Agenda

Item Subject Page

Number



### T4 Apply Highest RT Fare (RT Minimum Check) 26

T5 Resolution 725f and 725g Itinerary Receipt 26

T6 Third Party Data Collection – Inhibit Ticket Proposal 27

T7 Adding Additional Passenger Type Codes to the Name on the

Ticket 27

T8 Clarifications for the EMD Document Legal Notice (Terms and

Conditions) 27

T9 Alignment of ET and EMD Resolutions for the Delivery of Ticket

Notices and Receipts 27

T10 Clarification of Entity Permitted to Make Refunds 28

T11 EMD Issue and Exchange/Reissue Product Characteristics 28

T12 New Schedule Change Resolution V3 28

RESERVATIONS

R1 Report - ATA/IATA Reservations Committee (ResCom) 29

R2 Report - Reservations Working Group (RESWG) 29

R3 Secure Flight – Third Party Data Collection 29

R3.1 Allow Replies on SSR DOCx 29

R4 Wheelchair Code for Partially Immobile Passengers 29

R5 Lithium Ion Battery Powered Wheelchairs 30

R6 WCMP/WCBD/WCBW/WCOB 30

### R7/P Reservations “Package” 31

R7.1/P Passenger Name (Format) 31

R7.2/P Requesting Additional Passenger Information from the Booking

Source 31

R7.3/P Request for EMD Number 32

R7.4/P Request for New Passenger with Service Animal SSRs:

ESAN/SVAN (Bilateral) 32

R7.5/P Inclusion of Record Locator of Original Booking Office for Ticket

Number Notification Messages 32

MISCELLANEOUS

M1 Report - PSC Steering Group (PSCSG) 32

M2 Report - PADIS Board (PADIS) 32

M2.1 PNRGOV and Adoption by WCC 33

M3 Report - Cargo Services Conference (CSC) 33

M4 Report – Scheduling Services 33

M4.1 Report - Schedules Informa tion Standards Committee (SISC) 33

M5 Report – Fraud Prevention Working Group (FPWG) 33

M6 Report – BSP Data Interchange Standards Group (BDISG) 33

M7 Report – Strategic Partnerships 33

M8 Report – PCI DSS Working Group (PDWG) 33

M9 Report - Industry Carbon Offset Programme (ICOP) 33

M10 Report- Inflight Services 34

M10.1 Standard Inflight Ca tering Agreement (SICA) 34

Close of Meeting 34

### 1

MINUTES

30 th 

### Joint ATA/IATA Passenger Services Conference (JPSC)

32 nd 

### IATA Passenger Serv ices Conference (PSC)

Geneva, 21 October 2010



## ADMINISTRATION

A1 Opening of Meeting

1. The Chairman, Mrs. Patricia George, opened the 30 th 

### Joint ATA/IATA

Passenger Services Conference (JPSC) and the 32 nd 

### IATA Passenger

Services Conference (PSC) at 0900 hours on 21 October 2010. She

introduced Rosalie Crabbe (UA), Chairperson of the ATA Passenger Council.

The attendance list is shown in Attachment A

.

2. Conference noted the anti-trust warnings regarding discussion on

competitively sensitive topics.

3. The Chairman introduced the new IATA Senior Vice President of IDFS Mr.

Aleksander Popovich who emphasized the importance of PSC standards

setting activities.

4. It was noted that Mr. Eric Leopold had been appointed Head, Passenger

within the IDFS department.

A2 Examination of Credentials of Accredited Representatives

5. Conference noted the list of IATA PSC accredited representatives and ATA

Passenger Council representatives.

A3 Approval of Minutes – JPSC/29 and PSC/31

6. Conference approved as published the Minutes from the 29 th 

### meeting of the

JPSC and 31st meeting of the PSC.

A4 Status of PSC Resolutions and RPs

7. The Secretary, Mike Muller (IATA), reported that he had received approval

from the US Department of Transportation (DoT) for the expedited resolutions

from the 2008 meeting of the PSC. He advised that he would declare them

effective from 1 November 2010. Noting that this resulted in a nearly 2 year

delay, the Conference would be updated on the status of an initiative to waive

the need for anti-trust immunity for most IATA standards in order to

significantly accelerate the approval process (refer to agenda item P13).

### 2

A5 Effectiveness Date of Amendments to Industry Standards

8. Conference confirmed that the general effective date of 1 June 2011 would

apply to all amendments regarding resolutions, RPs and AIRIMP unless

otherwise agreed.

A6 Election of Chairman and Vice Chairman

9. Conference elected Ms. Patricia George by acclamation to a further three

year term of office. Ms. Stephanie Yen (DL) was elected by acclamation to the

post of Vice-Chairman. The Conference noted its thanks to Mr. Ross Leggett

(JL) for his service to PSC in the role as Vice-Chairman. The Chairman noted

that Mr. Leggett had moved position within his company and would no longer

be able to participate in PSC activities.

A7 Any Other Business

10. No other business was presented.

A8 Date and Place of Next Meeting

11. The Secretary advised that it is planned to hold the next meeting in

conjunction with a commercial event to be held in Asia in October 2011. Final

confirmation of dates and venue will be advised.

Secretary note 1: for online information on future IATA meetings, refer to 

### :

www.iata.org/workgroups/calendar



### Secretary note 2: the next PSC will be held in Singapore on 12-13 October

2011. Refer to Attachment B to see the schedule for industry standards

setting meetings during Passenger Week 2011.

Secretary note 3 : Passenger Week will be held concurrently with several

interesting sessions of a commercia l event called the World Passenger

Symposium. It will be the first annual edi tion of this important industry event –

refer to : http://www.iata.org/e vents/passenger-sympos ium/Pages/ index.aspx



## POLICY

P1 Report – Status of Industry Coding Systems

12. Conference noted this report.

### 3

P1.1 Release of ISO Country Codes for Generic Tax, Fee Charges (TFC)

Usage

13. Conference agreed to release 15 two-alpha codes shown in Attachment C

for future TFC allocation since it was noted that these codes would not be

used for allocation to the countries or territories to which they had been

assigned by ISO as country codes. All members and Strategic Partners were

again reminded to ensure that their systems be ready to accept alpha/numeric

TFC codes.

ACTION: All members a nd Strategic Partners

P2 Assignment Criteria for Airline Designator, Location Identifier and

Accounting Codes (Resolutions 762, 763 and 767)

14. The Secretary proposed various editorial changes to the main coding

resolutions (762, 763 and 767) with a view to simplifying procedures and

processes. UA and CO opposed such changes until any in terested member

could make a thorough review of the proposals. Accordingly it was agreed to

invite interested parties to a short Coding Working Group meeting to review

the proposed changes. Conference noted volunteers from KL, LH, UA, SITA

and Travelport.

ACTION: CODING WORKING GROUP

Secretary note: the Coding Working Group met in Montreal on 3-4 March

and will submit a revised proposal to the PSC in 2011.



### P3 Adding an Airport to an Existing Metropolitan Area (Resolution 763)

15. LH reported that in 1990 the EU had raised concerns regarding the IATA

polling procedures for adding a new airport to an existing metropolitan area.

The EU believed it could have potential for anti-competitive behavior. This

concern was derived from the fact that all carriers (i.e. those serving the

existing airports of the metropolitan area as well those serving the airport to

be added) were part of the polling procedures. Based on the EU intervention,

the PSC in 1991 (PSC/13) had felt obliged to change the provisions of

Resolution 763 to allow only the requesting airport and its airline(s) to be

involved in the poll.

16. However, LH noted that since this change there had been many cases of

misuse of the provisions of Resolution 763 by certain airlines to facilitate their

advertising campaigns, which in many cases resulted in passengers being

misled as to the area where their destination airport was located.

17. Accordingly LH proposed to revert to the original procedures regarding the

addition of an airport to an already existing metropolitan area. This is in

recognition that by allowing all airports and all airlines to participate in the

polling procedures, it would produce more justified results in terms of airports

actually functioning as gateways to a particular city.

### 4

18. Moreover LH proposed a safeguard mechanism to prevent abuse by

incumbent carriers by providing the relevant national aeronautical authority

with the power of veto to overturn any polling result that refuses to add an

airport to a metropolitan area (see new paragraph 1.5.3 in Resolution 763).

19. LH highlighted that airport operators would be required to support any

reasonable action and this provides an additional safeguard as concerns the

de-listing of airports from existing metropolitan areas or the dismantling of

existing metropolitan areas.

20. The PSC unanimously adopted the proposed changes to Resolution 763 as

shown in the book of finally adopted resolutions and RPs (published

separately).

P4 Ratification of Special Fees and Charges Codes (Resolution 728)

21. Conference agreed to ratify the list of codes shown in Attachment D that had

been assigned on a provisional basis since the last meeting of the JPSC in

October 2009.

P5 Report – BSP Form Codes and Document Supply Chain

22. The JPTC had endorsed a proposal from IATA to provide certain new form

codes regarding future allocations for VMPD, ATB MCO and OPET. The PSC

agreed to amend RP 1720a accordingly as shown in the book of finally

adopted resolutions & RPs. The ATA Passenger Council agreed to

counterpart changes to Resolution 20.04 as shown in Section II of the ATA

Minutes.

P5.1 Form Codes (ATA Resolution 20.40 / IATA RP1720a)

23. ATA proposed that IATA take counterpart action for RP 1720a to reflect

changes agreed to ATA form codes in a mail vote that was effective 1 January

2011. The PSC agreed to amend RP 1720a accordingly as shown in the

book of finally adopted resolutions & RPs.

P6 Alliance Code and MITA (Resolution 780)

24. Aerosvit proposed amendments to Resolution 780 (Multilateral Interline Traffic

Agreement – MITA) to adopt simple procedures for recognizing members of

an alliance and the ability of all such airlines to be considered party to the

MITA through a “parent” airline. Aerosvit advised that such changes would

facilitate cost reductions for airlines in an alliance. Noting 22 opposed and 5

abstentions, the Chairman ruled this item defeated. Hahn Air volunteered to

work with Aerosvit to explore cost effe ctive commercial agreements for airline

alliances.

### 5

P7 Opt Out of Accepting Paper Misc ellaneous Documents for Interline

Travel (Resolution 780)

25. The Secretary reminded members that the Multilateral Interline Traffic

Agreement (MITA) contains a provision that allows an airline to give 12

months notice to all its interline partners regarding their intention to stop

accepting paper tickets (refer to Resolution 780, paragraph 2.2.6). The

Secretary advised that to date 5 airlines have provided such notice: BA, CM,

MI, QR and SQ. To stay abreast of the increase in airlines giving 12 months notice,

refer to the list of “files” (folder “06”) in the MITA extranet site. For access to the

MITA private site, register via: http://www.iata.org/workgroups/Pages/mita.aspx



### 26. Accordingly the Secretary suggested that a logical next step is to amend

MITA to provide a similar provision to “opt out” of accepting paper

miscellaneous documents. Noting abstentions from NH and UA, the PSC

agreed to amend Resolution 780 as shown in the book of finally adopted

resolutions & RPs. The Secretary highlighted that BSPs would be 100% EMD

by the end of 2013.

P8 ZED-MIBA Forum – Sunset of Pape r Tickets for Interline Staff Travel

27. Conference noted with pleasure that ZMF members had agreed to a deadline

date of 31 March 2012 for exchange of paper tickets for interline staff travel.

Accordingly ZMF members will not accept pa per tickets for staff travel after 31

March 2012. Therefore it was proposed that IATA would endorse this

deadline by adding it to the provisions of Resolution 728 and RP 1788.

Conference agreed to these changes as shown in the book of finally adopted

resolutions and RPs.

28. ZMF members also proposed the establishment of a joint ZMF/IATA working

group to promote automated solutions for interline staff travel. Noting

abstentions from CO and UA, Conference agreed to establish the ZISTAS

Working Group with terms of reference as shown in Attachment E.

P9 Paper Out Strategy

29. Conference noted the recommendations from the StB Steering Group that

IATA should pursue a strategy of removing all remaining paper from the

interline process (e.g., paper tickets and miscellaneous documents including

the FIM). This was broadly supported by the PSC although CO and UA

advised that they are currently not in a position to retire paper tickets.

ACTION: StB Steering Group

P10 Report – Simplifying the Business (StB)

30. Conference noted with pleasure that the Bar Coded Boarding Passes initiative

was being closed at the end of 2010 since the industry was on track to

achieve 100% penetration of BCBP by the end of the year.

### 6

P10.1 Report – Automated Baggage Rules Task Force (ABRTF)

31. Conference noted the report of this project which had been launched in June

2010 by the IATA Board of Governors. Conference recognized that urgent

action was required in order to meet minimum implementation for certain

features in time for the effective date of 1 April 2011 when Resolution 302

comes into effect, replacing Resolutions 300 and 301. Conference agreed to

a list of action items including the establishment of an ABR Implementation

Steering Group, noting volunteers from Sabre, SITA, Amadeus, Travelport,

ITA Software, BA, AF, AA, CO, LH and LY.

32. Conference endorsed the proposal to allow the Ticketing Committee to

circulate a mail vote to adopt ticketing standards to expand the options

regarding showing free baggage allowance on electronic tickets. Conference

noted that it is planned to develop definitions for excess baggage, hold

baggage fees and interline processes for hold baggage fees to reflect action

in the market. It was reported that the US Department of Transportation

(DoT) had launched a notice of proposed rule making (NPRM) on related

subjects and therefore IATA should proceed with caution.

P10.2 Presentation: IATA e-services

33. Mr. Sebastian Touraine of IATA provided a presentation as shown in

Attachment F

.

P11 XML Standards of the Future

34. Conference noted with concern the proliferation of groups developing XML

schemas for the airline industry in an uncoordinated way. LH noted that a

vacuum had been created which could lead to fragmentation of standards

development and increased costs as a result. LH proposed that IATA

consider integrating the work of other XML standards organizations, if this

would make sense for an industry strategy.

35. Mr. Eric Leopold (IATA) reported that a recent meeting of the StB Steering

Group (StBSG) had concluded that there could be significant costs savings

regarding XML development and implementation as part of a wider

opportunity focused on “business services”. It was agreed that a vision had to

be defined, followed by the development of a business case that would

support an appropriate strategy to achieve the vision. He reported that a

newly formed group called the “StB Think Tank” (a subset of the StBSG)

would address this issue.

ACTION: StB Think Tank

P12 Co-ordination with the Commission of European Communities (CEC) on

PSC Matters

36. Conference noted this report with interest.

### 7

P13 Co-ordination with the US Depa rtment of Transportation (DoT) –

Initiative for Self-Assessment

37. Conference was reminded that several years ago IATA provided 4 lists of

“non-controversial” PSC standards to the US DoT with a request that such

standards be filed for information only. This was known as the “whittle-back”

of IATA’s anti-trust immunity because subsequent changes to a resolution or

RP in the list would mean that the entire resolution or RP itself would lose its

immunity from US anti-trust laws.

38. This exercise was undertaken primarily to reduce the workload on the US DoT

in reviewing PSC changes to resolutions and RPs with the hope that this

would accelerate the approval process. The Secretary reported that

regretfully this exercise has not produced significant improvements.

39. Accordingly, in close cooperation with IATA Legal and other IATA standard

setting departments, it had been concluded that the time is ripe to undertake a

proactive transition to a system that would require no immunity from

competition law for PSC standards.

40. Therefore in 2009 IATA opened dialogue with the US DoT regarding the

development of new procedures to create a “self-assessment” environment.

This means that all future PSC agreements (with a few exceptions) will be

provided to the DoT for “information only”. The huge advantage to this new

system is that the PSC will no longer suffer delays to implementation of

standards. However, PSC activities will need to even more closely monitored

by IATA Legal to ensure that Conference activity remains consistent with US

law. This is in recognition that the US DoT does not provide anti-trust

immunity to any standards that have been filed for “information only”.

41. The Secretary reminded Conference that in May 2010 IATA had filed an

official application for further exemption from “Condition #2” (Docket OST2010-0114). This would continue to permit the DoT and the traveling and

shipping public to be fully informed of the work and proposed actions of the

IATA Traffic Conferences before any recommended practice, agreement or

resolution is declared effective.

42. The concept is that IATA would file the vast majority of agreements for

“information only” and provide at least 30 days notice before the intended

effective date. This would allow the DoT (and other interested parties) a 30

day period in which to review the contents. If the DoT does not react with 30

days then IATA would be able to declare the agreements effective.

43. However, within the 30 day filing period it is worth noting that the DoT has the

ability to insist on a longer period of refl ection. Or the DoT could direct IATA

to file all or parts of the agreements in the traditional way for review and

approval.

44. The Secretary highlighted that the Do T had already identified certain subject

areas where the traditional filing regime would need to be respected, e.g. for

ticket notices.

45. The Secretary concluded that the proposed exemption would allow swift

implementation of most IATA agreements whilst preserving the ability to make

### 8

filings for appropriate action on matters of known regulatory sensitivity. He

reported that this is an important policy objective of IATA in order to allow

significant acceleration of the PSC approvals process for interline standards.

The Secretary would advise all members as soon as the DoT has acted on

the contents of Docket OST-2010-0114.

ACTION: Secretary

P14 Report - Agency Solutions Technical Working Group (ASTWG)

46. Subsequent to the 2 nd 

### meeting of the ASTWG, the European Travel Agents’

and Tour Operators’ Associations (ECTAA) suggested that the ASTWG could

bring further added value if it was enabled to discuss any technical aspect that

concerns airlines, GDSs and agents with a view to facilitate the distribution of

air tickets. Moreover the ASTWG could also bring important value regarding

the preparation of EMD implementation and how to facilitate the distribution of

un-bundled fares and ancillary services. Therefore ECTAA proposed that the

ASTWG Terms of Reference (ToR) be updated accordingly. Conference

agreed to amend the ToR as shown in Attachment G.

47. The ASTWG proposed to tighten the definition of code “0” in ticketing

resolutions. Subsequently airlines could consider, on an individual basis, if

they wished to implement a policy whereby they would restrict sending ADMs

on tickets that had been issued on the basis of the fare calculation mode

indicator (FCMI) “0”. This was rejected by the Ticketing Committee because it

was not clear that all GDSs had agreed to implement this change at this time.

Subsequently IATA management proposed amending ticketing resolutions for

code “0” to restrict its definition solely to where there had been no

manipulation at all and amend code “2” to be used when any manipulation

was applied. Conference did not agree to this because at least one carrier

was using code “2” defined in a different manner.

48. The Secretary noted that an additional problem was that there were two

options provided that could be reflected in the FCMI. Accordingly the

Secretary proposed on site changes to Resolutions 722, 722a, 722c, 725c,

725d, 731a and 742e to delete the option for the Fare Calculation Pricing

Indicator. This was agreed (noting abstentions from AC, JL and UA) as

shown in the book of finally adopted re solutions and RPs. The proposal will

be submitted to the ATA Passenger Council for adoption of counterpart

changes to Resolutions 20.1020.13, 20.51, 20.52, 20.100, 20.101, 20.102,

20.104 and 20.60.

P15 Glossary of Terms

49. Conference was advised that SITA had compiled a comprehensive glossary

of industry terms to facilitate understanding of definitions in resolutions and

recommended practices. Moreover it s spreadsheet format allows for easy

access to related definitions. It was proposed that RP 1008 be amended to

provide a URL so that the glossary could be easily accessible via the internet

(refer to the “Passenger Glossary of Terms ” at:

http://www.iata.org/whatwedo/passenger/Pages/index.aspx 

### ).

### 9

50. Accordingly Conference agreed to amend RP 1008 as shown in the book of

finally adopted resolutions and RPs. The ATA Passenger Council agreed to

counterpart changes to Resolution 100.15 as shown in Section II of the ATA

Minutes.

51. The Conference recorded its heartfelt thanks to Adrianna Colbath of SITA for

having developed the glossary over several months.

P16 Tax/Fee/Charge Code for Airport Charges (Resolution 728)

52. Mr. Dave McEwen (IATA) reminded Conference of the Ticket Tax Box Service

(TTBS) which comprises th e most current information on ticket taxes in a

database. Until the recent past, the database would only provide information

of taxes, fees and charges that had been mandated by the appropriate

authority to be collected separately and shown on the ticket.

53. However, he advised that the PSC meeting of 2008 had agreed that airlines

could request new codes for any published charge by an airport that is levied

on a per passenger basis. As a consequence the TTBS has seen a

significant increase in the volume and complexity of individual carrier filings

which has put the database under strain and caused complexity for the

revenue accountants. Accordingly it was proposed to establish code YX for

“airline own use only – airport charges” to be used in a similar fashion as

unilateral airline codes YQ and YR.

54. There was some sympathy for this proposal, however, noting opposition from

DL, UA and abstentions from AA, AF, CO, KL, the Chairman ruled this item

defeated.

P17 Changes to MITA to Support Si mplifying Interline Settlement (SIS)

Project in Revenue Accounting

55. Conference was requested to update Resolution 780 to clarify procedures

regarding the interline billing and settlement process. Conference agreed to

amend Resolution 780 as shown in the book of finally adopted resolutions and

RPs.



## AIRPORT SERVICES

B1 Report of the Airport Services Committee (ASC)

56. Conference noted this report. AZ, JL, LY and MS were elected for 3 year

term of office to the ASC. Thanks were noted to Rhonda Grant (AA), the

outgoing Chairman of the ASC. A copy of the ASC membership list is shown

in Attachment H

.

B2 Report of the IATA Grou nd Handling Council (IGHC)

57. Conference noted this report.

### 10

B3 Report – Fast Travel – Passen ger Experience Management Group

(Resolution 705)

58. Conference noted this report.

B3.1 Self-Service Baggage Check-In (Recommended Practice 1701f)

59. The Secretary reported that the Fast Travel Working Group and the

Baggage Working Group had jointly developed a completely new version of

RP 1701f and re-named it “Self-Service Baggage Check-In”. Lufthansa

requested that more detail be put into RP 1701f, however, the Secretary

advised that extra details would be best addressed in a separate

implementation guide. Noting opposition from LH, LX and OS together with

abstentions from AF, KL, MS and UA the Chairman declared the changes to

RP 1701f adopted as shown in the book of finally adopted Resolutions and

RPs.

B3.2 Updates to Bar Coded Boarding Pass (Resolution 792)

60. The BCBP Working Group advised that in order to align the usage of

mobile BCBP and also to cater for the emerging use of Near Field

Communications (NFC), Resolution 792 should be updated to provide

reference to Near Field Communications in a new version 4 of Resolution

792. The PSC agreed to the proposed changes to Resolution 792 as shown

in the book of finally adopted Resolutions and RPs. The ATA Passenger

Council agreed to counterpart changes to ATA 20.205 as shown in Part II of

the ATA Minutes.

B3.3 Amendment to Resolution 792

61. The BCBP Working Group proposed to add to Resolution 792 two

additional fields to enable the recording of non consecutive bag tags within

the conditional data elements of the barcode. The PSC agreed to the

proposed changes to Resolution 792 as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to ATA 20.205 as shown in Part II of the ATA Minutes.

B4 Report of the Baggage Working Group (BWG)

62. Conference noted this report and exte nded the life of th e BWG for a further

12 months. However, the Secretary proposed that the terms of reference be

updated to differentiate the scope of BWG activities from those performed by

the Passenger Experience Management Group (PEMG). Conference agreed

that draft terms of reference should be drafted and circulated to the PSC

Steering Group (PSCSG) for their comments and endorsement.

ACTION: PSCSG

### 11

B5 Report of the DCS Messages Working Group (DCSMWG)

63. Conference noted this report and exte nded the life of th e BWG for a further

12 months.

B6 Dangerous Goods in Passenge r’s Baggage (Resolution 745)

64. The Secretary proposed several updates to Resolution 745 including a

provision regarding the necessity to show specific information on dangerous

goods on airline websites for ticket purchase, check-in and airport check-in

terminals as of January 2013. The PSC agreed to all the proposed changes

to Resolution with a deferred effective date of 1 January 2013 as shown in the

book of finally adopted Resolutions and RPs.

B7/P Packaged Items (DCSMWG)

65. This “package” contained miscellaneous items documented in B7.1/P

through B7.15/P which had been developed by the DCSMWG and endorsed

by the ASC with no opposition noted. The Secretary advised that items

B7.8/P and B7.10/P were for information only and B7.11/P was withdrawn in

favor of agenda item R5. The PSC agreed to all proposed changes as shown

in the book of finally adopted Resolutions and RPs.

B7.1/P Consistent format for names on DCS messages

66. The editorial change to RP 1707b regarding the name element was agreed

by the PSC as shown in the book of finally adopted Resolutions and RPs.

B7.2/P Use of Party/Group Identification Element

67. The editorial change to RP 1707b and RP 1708 regarding party/group

identification was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs.

B7.3/P Editorial for INFT example

68. The editorial change to RP 1708 regarding SSR INFT was agreed by the

PSC as shown in the book of finally adopted Resolutions and RPs.

B7.4/P Correction to example in TPL

69. The editorial change to RP 1719d to show surnames listed individually on

a TPL was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs.

### 12

B7.5/P Updates to API DOCO element in DCS to match RES format

70. The change to RP 1707b regarding SSR DOCO to match changes made

in reservations standards was agreed by the PSC as shown in the book of

finally adopted Resolutions and RPs.

B7.6/P Editorial repairs to RP 1707

71. The editorial change to RP 1707 and RP 1707b was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs.

B7.7/P SSR MEQT in DCS

72. The editorial change to RP 1715 to add SSR MEQT was agreed by the

PSC as shown in the book of finally adopted Resolutions and RPs.

B7.8/P Discussion on length of name field

73. This item was for information only.

B7.9/P Guideline for plac ing Group PNRs on PNL/ADL

74. The change to RP 1707b to clarify that the size of the group and the total

number of named individual group members must be equal was agreed by the

PSC as shown in the book of finally adopted Resolutions and RPs.

B7.10/P SSRs based on Leg or Segment

75. This item was for information only.

B7.11/P New wheelc hair code WCLB

76. This item was withdrawn by the Secretary in favor of agenda item R5.

B7.12/P Wheelchair codes for general use

77. The change to RP 1708 and RP 1708a to update definitions for

wheelchairs was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs.

B7.13/P SSR codes for service animals

78. The change to RP 1708 and RP 1708a to add definitions for service and

emotional support animals was agreed by the PSC as shown in the book of

finally adopted Resolutions and RPs.

### 13

B7.14/P Editorial for PNL/ADL

79. The editorial change to RP 1708 to remove reference to code CHD was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs.

B7.15/P Editorial for PNL/ADL

80. The editorial change to RP 1708 to remove the mandatory oblique was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs.

B8/P Packaged Items (BWG)

81. This “package” contained miscellaneous items documented in B8.1/P

through B8.29/P which had been developed by the BWG and endorsed by the

ASC. The PSC agreed to all proposed changes as shown in the book of

finally adopted Resolutions and RPs, noting abstentions by AF and KL

regarding item B8.2/P. The ATA Passenger Council agreed to all counterpart

changes as shown in Section II of the ATA Minutes.

B8.1/P Compliancy of the format of the “Aircraft compartment” in the .U

element with all the Aircraft type positions

82. The change to RP 1745 to allow a single character in paragraph 2.3.24.5

for aircraft compartment of loading location was agreed by the PSC as shown

in the book of finally adopted Resolutions and RPs. The ATA Passenger

Council agreed to counterpart changes to RP 30.45 as shown in Section II of

the ATA Minutes.

B8.2/P .S Changes to support Bag Validation Status

83. The change to RP 1745 and RP 1800 to add V = Validated as optional

third status for bag tag in .S was agreed by the PSC as shown in the book of

finally adopted Resolutions and RPs, noting abstentions from AF and KL. The

ATA Passenger Council agreed to counterpart changes to RP 30.49 as shown

in Section II of the ATA Minutes.

B8.3/P Clarification of Secondary Code ‘H’ in .J Element of a BPM

84. The change to RP 1745 to remove H = Hand Scanner in .J processing

information was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to RP 30.45 as shown in Section II of the ATA Minutes.

### 14

B8.4/P Extra sub element in the .U

85. The change to RP 1745 to extend .U with a container handling type was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs. The ATA Passenger Council agreed to counterpart changes to RP

30.45 as shown in Section II of the ATA Minutes.

B8.5/P Amendments to RP1800 Se ction 6 Process Specific Baggage

Codes

86. The change to RP 1800 to align the process specific baggage codes was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs. The ATA Passenger Council agreed to counterpart changes to RP

30.49 as shown in Section II of the ATA Minutes.

B8.6/P Amendments to RP1800 Section 5.2 Sortation

87. The change to RP 1800 to amend the conditionality element for the

sortation process was agreed by the PSC as shown in the book of finally

adopted Resolutions and RPs. The ATA Passenger Council agreed to

counterpart changes to RP 30.49 as shown in Section II of the ATA Minutes.

B8.7/P Amendments to RP1800 Section 5.3 Screening

88. The change to RP 1800 to amend the conditionality element for the

screening process was agreed by the PSC as shown in the book of finally

adopted Resolutions and RPs. The ATA Passenger Council agreed to

counterpart changes to RP 30.49 as shown in Section II of the ATA Minutes.

B8.8/P Amendments to RP1745 Section 10 Baggage Request Message

(BRQ)

89. The change to RP 1745 to amend the element conditionality in the

baggage request message (BRQ) was agreed by the PSC as shown in the

book of finally adopted Resolutions and RPs. The ATA Passenger Council

agreed to counterpart changes to RP 30.45 as shown in Section II of the ATA

Minutes.

B8.9/P Amendments to RP1745 Section 2.2

90. The change to RP 1745 to amend the element conditionality in section 2.2

was agreed by the PSC as shown in the book of finally adopted Resolutions

and RPs. The ATA Passenger Council agreed to counterpart changes to RP

30.45 as shown in Section II of the ATA Minutes.

### 15

B8.10/P Amendments to RP1745 Section 3, BTM

91. The change to RP 1745 to amend the conditionality element in section 3

(BTM) was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to RP 30.45 as shown in Section II of the ATA Minutes.

B8.11/P Amendments to RP1745 Se ction 4 Baggage Source Message

(BSM)

92. The change to RP 1745 to amend the conditionality element in section 4

(BSM) was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to RP 30.45 as shown in Section II of the ATA Minutes.

B8.12/P Amendments to RP1745 Section 5 Baggage Process Message

(BPM)

93. The change to RP 1745 to amend the conditionality element in section 5

(BPM) was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to RP 30.45 as shown in Section II of the ATA Minutes.

B8.13/P Amendments to RP1745 Section 6 Baggage Unload Message

(BUM)

94. The change to RP 1745 to amend the conditionality element in section 6

(BUM) was agreed by the PSC as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to RP 30.45 as shown in Section II of the ATA Minutes.

B8.14/P .E Exception types

95. The change to RP 1745 to use the .E baggage exception data element for

the purpose of communicating limited release status of baggage items was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs. The ATA Passenger Council agreed to counterpart changes to RP

30.45 as shown in Section II of the ATA Minutes.

B8.15/P Amendments to RP1800 Section 5.9 Offloading/Reloading

96. The editorial change to RP 1800 to amend section 5.9 was agreed by the

PSC as shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

### 16

B8.16/P Amendment to RP1745 Sections 1.6 and 10.8 to correct

typographical errors

97. The editorial change to RP 1745 to remove redundant language in 1.6 was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs. The ATA Passenger Council agreed to counterpart changes to RP

30.45 as shown in Section II of the ATA Minutes.

B8.17/P Amendment to RP1745/30.45 section 2.1.1

98. The change to RP 1745 to define NA in 2.1.1 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.45 as shown in

Section II of the ATA Minutes.

B8.18/P Discrepancies between IATA Reso 740 and ATA 30.35

99. The change to Resolution 740 to resolve discrepancies with ATA

Resolution 30.35 was agreed by the PSC as shown in the book of finally

adopted Resolutions and RPs. The ATA Passenger Council agreed to

counterpart changes to Resolution 30.35 as shown in Section II of the ATA

Minutes.

B8.19/P Change of wording in BTM Section 3.2.4

100. The change to RP 1745 to align wording of BTMs with BSMs was agreed

by the PSC as shown in the book of finally adopted Resolutions and RPs.

The ATA Passenger Council agreed to counterpart changes to RP 30.45 as

shown in Section II of the ATA Minutes.

B8.20/P Change of wording in BSM Section 4.2.3

101. The change to RP 1745 to clarify wording of BSMs was agreed by the

PSC as shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.45 as shown in

Section II of the ATA Minutes.

B8.21/P Remove incorrect element in BTM section 3.9.6

102. The change to RP 1745 to amend an incorrect example in 3.9.6 was

agreed by the PSC as shown in the book of finally adopted Resolutions and

RPs. The ATA Passenger Council agreed to counterpart changes to RP

30.45 as shown in Section II of the ATA Minutes.

B8.22/P Format description of the ULD in the .U element

103. The change to RP 1745 to clarify the format description of the ULD in the

.U element was agreed by the PSC as shown in the book of finally adopted

### 17

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to RP 30.45 as shown in Section II of the ATA Minutes.

B8.23/P Amendments to RP1800 5.10 Tracing

104. The editorial change to RP 1800 to amend 5.10 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

B8.24/P Amendments to RP1800 5.11 Intermodal Receipt/Intermodal

Delivery

105. The editorial change to RP 1800 to amend 5.11 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

B8.25/P Amendments to RP1800 Section 5.4 Reconciliation

106. The editorial change to RP 1800 to amend 5.4 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

B8.26/P Amendments to RP1800 Section 5.5 Tracking

107. The editorial change to RP 1800 to amend 5.5 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

B8.27/P Amendments to RP1800 Section 5.6 Rerouting

108. The editorial change to RP 1800 to amend 5.6 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

B8.28/P Amendments to RP1800 Section 5.7 Reflighting

109. The editorial change to RP 1800 to amend 5.7 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

### 18

B8.29/P Amendments to RP18 00 Section 5.8 Retagging

110. The editorial change to RP 1800 to amend 5.8 was agreed by the PSC as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to RP 30.49 as shown in

Section II of the ATA Minutes.

B9 Proposal for amendments to RP1745/30.45 and RP1800/30.49

111. The ASC proposed to align RP 1800 and RP 30.49 with the new RP 1701f.

Changes to RP 1800 were agreed by the PSC as shown in the book of finally

adopted Resolutions and RPs, noting opposition from AF, KL, LH, LX and OS.

The ATA Passenger Council agreed to counterpart changes to RP 30.49 as

shown in Section II of the ATA Minutes.

B10 Explicit the use of the 10 License Plate Code

112. The ASC proposed to change RP 1745 to clarify how to use the 10-digit

Licence plate code. This was agreed by the PSC as shown in the book of

finally adopted Resolutions and RPs, noting an abstention from BA. The ATA

Passenger Council agreed to counterpart changes to RP 30.45 as shown in

Section II of the ATA Minutes.

B11 Pro Rata of International Travel

113. The ASC proposed to remove Article 5.4.10 from Resolution 780 regarding

advance notification of claims exceeding USD 1,500. This was agreed by the

PSC as shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to Resolution 30.21 as

shown in Section II of the ATA Minutes.



## TICKETING

T1 Report of Ticketing Committee – Se lection of Committee Membership for

the IATA Passenger Forms and Procedures Committee (PFPC)

114. Conference noted the report of the Joint Passenger Ticketing

Committee (JPTC) as presented. Chairman thanked the Committee for its

work done throughout the year.

115. Conference was advised that the terms of office for BA, MS, EK, KL,

LH and US, were expiring and that six Ticketing Committee members would

need to be selected. The Chairman asked if there were any other Members

that wished to be considered.

### 19

116. There were a total of 7 nominations for the six vacant positions.

Following a ballot, BA, MS, EK, KL, LH and US, were elected for a three year

period. A copy of the updated membership is shown in Attachment I

Conference noted that all places are now taken.

117. Conference also gave the authority for the EMDWG to report directly to

JPSC and have items recommended for adoption without requiring to be

passed to the JPTC.

T2/P Ticketing “Package”

118. This “package” contained miscellaneous items documented in T2.1/P

through T2.41/P which had been approved at JPTC with no opposition noted.

The PSC unanimously adopted agenda items T2.1/P, T2.2/P, T2.5/P through

T2. 7 /P, T2.10/P through T2.24/P, T2.26/P through T2.34/P, T2.36/P and

T2.37/P through T2.41/P as proposed. T2.3/P, T2.8/P, T2.9/P, T2.25/P,

T2.35/P and T2.37/P were withdrawn from the package for further

consideration. Amendments to the IATA standards are published in the book

of finally adopted resolutions and RPs as noted below. The ATA Passenger

Council unanimously agreed to counterpart changes in item T2.1/P through

T2.10/P with the exception of those items withdrawn and items T2.4/P and

T2.14/P which required ATA action only.

T2.1/P Add Reference to 725h in 722f ET & EMD Glossary

119. This item proposed to make an editorial correction to add reference to

725h to the glossary of 722f. The PSC agreed to change Resolution 722f as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to Resolution 20.60 as

shown in Section II of the ATA minutes.

T2.2/P Fare Calculat ion Coupon Field Listed Twice in 725g Matrix

120. This item proposed to remove the incorrect occurrence of “Fare

Calculation Coupon/ Itinerary Sequence Number” from the Matrix. The PSC

agreed to change Resolution 725g as shown in the book of finally adopted

Resolutions and RPs. The ATA Passenger Council agreed to counterpart

changes to Resolution 20.64 as shown in Section II of the ATA minutes.

T2.3/P Remove EMD from P= pr int Option in Transaction Action

121. This item proposed to remove “/EMD” and “/value” from the P = Print

option text in the Transaction Action section, since there are no print option

specifications for EMDs. The PSC agreed to change Resolution 722f as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to Resolution 20.60 as

shown in Section II of the ATA minutes.

### 20

T2.4/P Synchronize the Definitions of EMD Value Coupon, ET Flight

Coupon, and EMD-A (ATA only)

122. This ATA only item proposed to make consistent the definitions for

“EMD VALUE COUPON” and “ET FLIGHT COUPON” in 20.63 with those in

ATA Resolutions 20.60, 20.61, 20.62, 20.64 & 20.66. The ATA Passenger

Council agreed to changes to Resolution 20.63 as shown in Section II of the

ATA minutes.

T2.5/P Remove “in connection” from EMD Value Coupon Definition

123. This item proposed to revise the definitions for “EMD Value Coupon” by

removing ‘in connection’ to be consistent with both the definition of EMD-A,

and with the use of EMD-A in the Resolutions. The PSC agreed to change

Resolutions 722f, 722g, 722h, 725f, 725g and 725h as shown in the book of

finally adopted Resolutions and RPs. The ATA Passenger Council agreed to

counterpart changes to Resolutions 20.60, 20.61, 20.62, 20.63, 20.64 and

20.66 as shown in Section II of the ATA minutes.

T2.6/P Inconsistent Resolutions for EMD-A group names

124. This item proposed to that to be consistent with Resolution 725f that an

EMD-A shall be limited to one passenger name only. It should be noted that

EMD-S can be used for group names. The PSC agreed to change Resolution

725f as shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to Resolution 20.64 as

shown in Section II of the ATA minutes

T2.7/P Acceptance of Discover Cards in the BSP

125. This item proposed to update information pertaining to Discover cards

in section 7 ‘Form of Payment Code’ to accurately reflect the range of

numbers used for Discover cards. The PSC agreed to change Resolution 728

as shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to counterpart changes to Resolution 110.16 as

shown in Section II of the ATA minutes.

T2.8/P Acceptance of Diners Cards in BSP

126. This item proposed to update information pertaining to Diner’s cards in

section 7 ‘Form of Payment Code’ in Resolution 728 to accurately reflect the

range of numbers used for Diner’s cards and to delete references to

processing them as MasterCard transactions in the US. The PSC agreed to

change Resolution 728 as shown in the book of finally adopted Resolutions

and RPs. The ATA Passenger Council agreed to counterpart changes to

Resolution 110.16 as shown in Section II of the ATA minutes

### 21

T2.9/P Credit Card as FOID Masking

127. This item proposed to align FOID procedures with requirements of the

Payment Card Industry Data Security Standards (PCI DSS). PCI DSS

compliance is required when more than the first 6 and the last 4 numbers are

transmitted. The PSC agreed to change Resolutions 722f, 722g, 722h, 725f,

725g and 725h as shown in the book of finally adopted Resolutions and RPs.

The ATA Passenger Council agreed to counterpart changes to Resolutions

20.60, 20.61, 20.62, 20.63, 20.64 and 20.66 as shown in Section II of the ATA

minutes.

T2.10/P Discrepancy – Defi nition of Ticket Handler

128. This item proposed to align the definition of ‘Ticket Handler’ in the

involuntary rerouting resolution to the definition in the electronic ticketing

resolutions. The PSC agreed to change Resolution 735d as shown in the

book of finally adopted Resolutions and RPs. The ATA Passenger Council

agreed to counterpart changes to Resolution 120.20 as shown in Section II of

the ATA minutes.

T2.11/P Obtaining Coupon Control for Inadmissible Passengers

129. This item proposed to make it clear that when a request for control of

an electronic ticket flight coupon is made in an inadmissible passenger

scenario, bearing in mind the granting of control constitutes an endorsement,

such endorsement request shall not be rejected. The PSC agreed to change

Resolution 701 as shown in the book of finally adopted Resolutions and RPs.

T2.12/P Rescission of Redundant Ticketing Resolutions

130. PSC agreed to rescind IATA Resolution 726b, Multiple Purpose

Document (MPD) – Neutral Carbonized Automated since IATA BSPs are now

100% paperless.

T2.13/P Text Changes for MCO and MPD Resolutions

131. This item proposed to clarify that miscellaneous and multi purpose

documents shall not be issued in IATA BSPs. The PSC agreed to change

Resolutions 725b, 726 and 726e as shown in the book of finally adopted

Resolutions and RPs.

T2.14/P XML, or PADIS standards, to be used with ATA 20.65

132. This ATA only item proposed to amend ATA Resolution 20.65 to refer

to PADIS Message Standards rather than XML message standards. The ATA

Passenger Council agreed to changes to Resolution 20.65 as shown in

Section II of the ATA minutes.

### 22

T2.15/P EMD With Surface Segments

133. This item proposed to clarify that an EMD should not contain surface

segments or ARNKS since this would result in using up more EMDs as

conjunctive EMDs would be required to indicate a break in the journey. The

PSC agreed to change Resolutions 725f and 725g as shown in the book of

finally adopted Resolutions and RPs.

T2.16/P EMD-A Coupon Associ ation to ARNK Segments

134. This item proposed to make it clear that an EMD-A coupon cannot be

issued and associated to an ET coupon representing an ARNK (arrival

unknown) segment or separate arrival segment within a PNR itinerary. The

PSC agreed to change Resolutions 725f and 725g as shown in the book of

finally adopted Resolutions and RPs.

T2.17/P Consequential Amendments to the Data Elements Glossary

‘Segment Identifier’

135. This item proposed to clarify the definition of ‘Segment Identifier’ in the

data elements glossary since it was confirmed that ARNK or arrival unknown

segments do not apply to EMDs. The PSC agreed to change Resolutions 725f

and 725g as shown in the book of finally adopted Resolutions and RPs.

T2.18/P New Reissue ticket number or EMD number in Change of Status to

Exchange/Reissue.

136. This item proposed to amend the electronic ticket and EMD airline

matrices making the data elements ‘Coupon Number’ and ‘Coupon Status

Indicator’ conditional for the Change of Status message for a

reissue/exchange for the new reissue EMD. The PSC agreed to change

Resolutions 722f and 725g as shown in the book of finally adopted

Resolutions and RPs.

T2.19/P Add FOID Information in Refund Response

137. This item proposed amend IATA Resolutions 722g and 725g to include

the sending of the FOID information in the ET and EMD refund message. The

PSC agreed to change Resolutions 722f and 725g as shown in the book of

finally adopted Resolutions and RPs.

T2.20/P Add RFIC and RFISC in History Display Response

138. This item proposed to add the RFIC and RFISC as conditional

elements to the History Di splay response in the mess age construction matrix

which will allow an agent making a disp lay request to see what type of EMD

### 23

had been issued. PSC agreed to change Resolution 725g as shown in the

book of finally adopted Resolutions and RPs.

T2.21/P Editorial change: align the verbiage of sending multiple

times Change of Status and Syst em Update to System Cancel one.

139. This item proposed to align all the messages that are required to be

sent 5 times when no response is received. PSC agreed to change

Resolutions 722f, 722h, 725f and 725h as shown in the book of finally

adopted Resolutions and RPs.

T2.22/P Editorial change: clarify a nd align the status allowed for

System Update

140. This item proposed to amend the procedures for the system update

message to make it clear that it shall not apply to suspend status. PSC

agreed to change Resolutions 722f, and 725f as shown in the book of finally

adopted Resolutions and RPs.

T2.23/P Editorial change: Replace CRS/System Provider by

Validating Carrier in EMD – Airline resolution

141. This item proposed to replace ‘CRS/System Provider’ with ‘Validating

Carrier’ in the airline EMD resolution since it was creating the notion that the

CRS/System Provider was to perform certain validations when instead, in the

context of the airline resolution, it should be the ‘carrier’. PSC agreed to

change Resolution 725f as shown in the book of finally adopted Resolutions

and RPs.

T2.24/P EMD: Multiple Coupons with Same Board and Off-Points

142. This item proposed to clarify when separate EMD-As shall be issued

when multiple coupons are required for the same board and off points. PSC

agreed to change Resolutions 725f and 725g as shown in the book of finally

adopted Resolutions and RPs.

T2.25/P Should UAC Messag e be Defined for EMD?

143. This item proposed to delete the billing carrier process for the EMD and

to make it clear it is the responsibility of the operating carrier to get control of

any associated EMD in a codeshare scenario. However a carrier felt that the

billing process should not be deleted from the resolution. PSC agreed to

change Resolution 725f as shown in the book of finally adopted Resolutions

and RPs.

### 24

T2.26/P Amendment to Defini tion of Marketing Carrier

144. This item proposed to amend the definitions of Marketing and

Operating Carrier to make it clear that, in the context of the EMD the

marketing carrier should be defined as the carrier marketing the flight in a

code share situation for flight related services and the operating carrier shall

be the airline whose airline designator is recorded as the service provider on

the electronic value coupon(s). PSC agreed to change Resolutions 725f, 725g

and 725h as shown in the book of finally adopted Resolutions and RPs.

T2.27/P Contradiction between Re cord Level and Coupon Level

Association

145. This item proposed to correct contradictions in Resolutions 725f and 725g

related to the use of record level data viz. coupon level data since this could

lead to different interpretations of the resolution. PSC agreed to change

Resolutions 725f and 725g as shown in the book of finally adopted

Resolutions and RPs.

T2.28/P Responsibility for Disassociating an Already Associated EMD

146. This item proposed to clarify that it shall be the validating carrier of the

EMD-A who has the responsibility for disassociating an already associated

ET. PSC agreed to change Resolution 725f as shown in the book of finally

adopted Resolutions and RPs.

T2.29/P Amendment to System Update

147. This item proposed to clarify that the rule preventing System Update

when coupons were at final or suspend status did not apply to disassociation

of the EMD. PSC agreed to change Resolution 725f as shown in the book of

finally adopted Resolutions and RPs.

T2.30/P Amendment to Change of Status – Move Synchronization

Paragraph

148. This item proposed to move references to maintaining synchronization

between EMD-A coupons and ET coupons since they do not belong under the

Change of Status paragraph. PSC agreed to change Resolution 725f as

shown in the book of finally adopted Resolutions and RPs.

T2.31/P Amendment to Re solution 725f Section 6.5.9 Change of Status

149. This item proposed to add a new paragraph to reference coupon status

‘O’ when a carrier holding control of an EMD coupon is returning control to the

### 25

Validating Carrier. PSC agreed to change Resolution 725f as shown in the

book of finally adopted Resolutions and RPs.

T2.32/P Data Elements for Additional Services Missing from Matrices

150. This item proposed to add data elements that were missing from the

matrices. PSC agreed to change Resolutions 725f, 725g and 725h as shown

in the book of finally adopted Resolutions and RPs.

T2.33/P Review of Form of Payment Credit Card Code in Resolution 728

151. This item proposed to remove references to the Braathens ASA

Bracard as it no longer exists. PSC agreed to change Resolution 728 as

shown in the book of finally adopted Resolutions and RPs.

T2.34/P Amend Amendment to RP1721 for Process Clarification

152. This item proposed changes to the netting in exchange/reissue

transactions RP to ensure the process clearly follows all of the currency

provisions mandated by Tariff Composite Resolution 024e. PSC agreed to

change Recommended Practice 1721 as shown in the book of finally adopted

Resolutions and RPs.

T2.35/P T2.21 JPSC IROPS NVA/NVB to be Used

153. This item proposed to align the ticketing resolutions with the involuntary

rerouting ticketing provision allowing for the option to leave the NVA blank.

PSC agreed to change Resolutions 720a, 722 and 722c as shown in the book

of finally adopted Resolutions and RPs.

T2.36/P Involuntary Reroutin g Fare Basis to be Used

154. This item proposed to add additional procedures for exchange/reissue

processing in involuntary rerouting scenarios to clarify which fare basis code

should be used when on the original ticket there are different fare basis codes

used across the segments to be rerouted. PSC agreed to change Resolution

735d as shown in the book of finally adopted Resolutions and RPs.

T2.37/P Revised Surc harges Resolution

155. This item proposed to amend ticketing resolutions to expand on the

placement of the ‘Q’, representing surcharges in the fare calculation area,

since there were differing ways in which the placement was currently being

interpreted and there were many new ways of filing surcharges which were

not taken into account.

### 26

156. There was concern that the full impact of these changes had not been

considered by the Revenue Accounting and Prorate communities since it was

suggested there would be considerable impact requiring major system

changes which may not be proportionate to the issue that is being addressed

in this proposal. On a formal vote with BA and UA in opposition this item was

declared defeated by the Chairman. PSC asked for this item to be referred to

the Revenue Accounting Working Group and the Prorate Meeting (IPAC) for

their consideration and to forward this back to JPTC for further review.

ACTION: RAWG/IPAC/JPTC

T2.38/P Editorial Corrections to PSC Resolutions Manual

157. This item proposed editorial corrections to Resolutions 725f and 725g.

PSC agreed to change Resolutions 725f and 725g as shown in the book of

finally adopted Resolutions and RPs.

T2.39/P Consequences of changing ‘Credit Card’ to ‘Payment Card’

158. This item proposed to add a footnote into making it clear that the use of

the term credit card also referred to other payment cards. PSC agreed to

change Resolution 728 as shown in the book of finally adopted Resolutions

and RPs.

T2.40/P E-ticket Display After Agent Migration from a GDS to Another

159. This item proposed to add verbiage to the neutral ticketing resolutions to

ensure that when a travel agent migrated from one GDS to another they still

had access to their electronic tickets even though they may been issued in

another system. PSC agreed to change Resolutions 72 2g and 725g as shown

in the book of finally adopted Resolutions and RPs.

T2.41/P Period of Validity

160. This item proposed to add wording into Resolution 735d related to the

period of validity to make it clear that an expired ticket is not eligible for an

exchange to another traffic document other than for refund. PSC agreed to

change Resolution 735 as shown in the book of finally adopted Resolutions

and RPs.

T3 ‘Void Exchange’ and ‘R efund Cancel’ Alignment to ‘Void Original Issue’

161. This item proposed to align verbiage within Resolution 722g for “Void

Exchange”, “Refund Cancel” and Void Original Issue” of electronic tickets and

electronic miscellaneous to be aligned with the reporting guidelines of the

neutral settlement scheme. ARC agent procedures are less restrictive than

IATA agent procedures.

### 27

162. It was felt by some Members that the current ‘same calendar day’

should be maintained for the voiding period which is aligned to the fact that

everything is reported within the same calendar day.

163. With AC and BA in opposition and a further 6 Members in abstention,

this item was declared defeated by the Chairman and referred back to JPTC

for further review.

ACTION: JPTC

T4 Apply Highest RT Fare (RT Minimum Check)

164. This item proposed to align carrier fare filing standards with ticketing

standards by adding a ticketing rule for a round trip minimum fare check

driven by a carrier specific fare rule. PSC agreed to change Resolution 722 as

shown in the book of finally adopted Resolutions and RPs. The ATA

Passenger Council agreed to changes to Resolution 110.15 as shown in

Section II of the ATA minutes.

T5 Resolution 725f and 725g Itinerary Receipt

165. A number of proposals were submitted to align the data that is

presented on the EMD receipt with the data elements present in the matrices

and glossary. PSC agreed to change Resolutions 725f and 725g as shown in

the book of finally adopted Resolutions and RPs.

T6 Third Party Data Collecti on – Inhibit Ticket Proposal

166. This proposal sought to add wording into the ticketing resolutions to

ensure that prior to ticke t issuance the system prov iders made a validation

that the Secure Flight Passenger Data (SFPD) as required by the US

authorities was present and if it was not, then the electronic ticket issuance

request would not be sent. It was suggested that if this was not formalized in

resolution then there would be no obligation on the ticketing systems to

perform these checks.

167. Whilst there was strong support for the proposal, some Members felt

that putting such verbiage into a ticketing resolution implied that this

methodology was an industry mandate. IATA advised that the electronic

ticketing resolutions defi ne more a systems process for issuing tickets and

there were already precedents that pr ovide for system vali dations prior to

sending a ticket issuance request message.

168. On a formal vote with SK and JL in abstention PSC agreed to change

Resolutions 722f and 722g as shown in the book of finally adopted

Resolutions and RPs with an expedited effective date of 1 November 2010 as

shown in the expedited Resolutions and RPs.

### 28

T7 Adding Additional Passenger Type Codes to the Name on the Ticket

169. This item submitted directly to PSC by a Member proposed to have

additional Passenger Type Codes (PTCs) for youth, student and senior

citizens similarly appended to the name element as it is for infant and child in

order to facilitate eligibility checks.

170. Some Members felt that this was more of a fraud prevention related

issued rather than ticketing. Moreover that this information could be obtained

from the fare basis. On a formal vote this item was declared defeated by the

Chairman and referred to JPTC and the Fraud Prevention Working Group for

further consideration.

ACTION: JPTC/FPWG

T8 Clarifications for the EMD Do cument Legal Notice (Terms and

Conditions)

171. PSC confirmed the current legal notice for miscellaneous documents

as published in Resolution 726 Attachment A applies equally to the Electronic

Miscellaneous Document (EMD) and does not require any further amendment

to take account of electronic documents.

T9 Alignment of ET and EMD Resolution s for the Delivery of Ticket Notices

and Receipts

172. This item submitted by IATA management proposed to align the EMD

resolutions to be reflective of the same provisions in the ET resolutions for the

provision and delivery of mandatory notices and receipts. PSC agreed to

change Resolutions 725f and 725g as shown in the book of finally adopted

Resolutions and RPs.

T10 Clarification of Entity Permitted to Make Refunds

173. This proposal submitted by the PCI DSS working group was to make it

clear that, in accordance with established payment card industry rules, only

the original merchant has the authority to affect any refund. It was understood

that industry practice is that in any case carriers will only refund their own

tickets. The resolutions today suggests that a Member other than the original

validating carrier may refund a ticke t which contravenes payment card

industry rules.

174. A Member questioned as to what might happen in an alliance

environment where another carrier may be requested to affect the refund. It

was suggested that the situation differs around the world and further

investigation is required as there seems to be a contradiction in how refunds

are done today. There were also concerns as to what should happen in an

involuntary refund case as a result of an irregular operation.

### 29

175. On a formal vote with opposition from UA this item was declared

defeated by the Chairman. This item was referred back to PDWG for further

consideration.

ACTION: PDWG

T11 EMD Issue and Exchange/Reissue Product Characteristics

176. This item proposed to add new data elements to the EMD matrices that

would capture certain characteristics to a product or merchandise that was

being sold. It was suggested that selling merchandise was not airline core

business and as this item had come directly to PSC it was suggested to defer

this to EMDWG for further review. On a formal vote this item was declared

defeated by the Chairman and referred to the EMDWG for further discussion

ACTION: EMDWG

T12 New Schedule Cha nge Resolution V3

177. Conference confirmed that the evolution of a new schedule change

resolution is going in the ‘right direction’ and that further work and review

should continue with the irregular operations working group and JPTC.

ACTION: JPTC/IRWG



## RESERVATIONS

R1 Report - ATA/IATA Reserv ations Committee (ResCom)

178. Conference noted this report. AC, AF and LH were appointed to the

IATA Reservations Committee as shown in Attachment J

.

R2 Report - Reservations Working Group (RESWG)

179. Conference noted this report and endorsed the work plan as shown in

Attachment K . Conference agreed to extend the mandate of RESWG for a

further 12 months.

R3 Secure Flight – Third Party Data Collection

180. Conference noted that RP 1722g had been adopted via mail regarding

guidelines to inhibit ticketing for security reasons for effect 1 October 2010.

Supporting changes had been adopted for AIRIMP also via mail vote as

shown in Attachment L

.

### 30

181. However, there had been some confusion in the market regarding the

need for ticketing systems to validate fo r “secure flight” data before the

issuance of electronic tickets. Accordingly it was proposed to update and rename RP 1722g to RP 1722z and adopt counterpart changes to Resolutions

722f and 722g. Noting an abstention from JL, this was agreed by Conference

with an expedited effective date of 1 November 2010 as shown in the

expedited Resolutions and RPs (published separately). The ATA Passenger

Council adopted counterpart changes to RP 20.722 as shown in Section II of

the ATA Minutes.

R3.1 Allow Replies on SSR DOCX

182. The Reservations Working Group proposed to amend AIRIMP to allow

replies on SSR code DOCS to give the airline the ability to send an unsolicited

message to the PNR owner to facilitate meeting the requirements of Secure

Flight (agenda item R3 refers). UA was initially opposed until they could

check certain issues with their lawyers. Subsequently they advised that they

could abstain. Accordingly it was agreed to amend AIRIMP with an expedited

effective date of 1 February 2011 as shown in Attachment M . The ATA

Passenger Council agreed to make counterpart changes to SIPP 105.175

also as shown in Attachment M

.

R4 Wheelchair Code for Partially Immobile Passengers

183. The Secretary proposed establishing a new wheelchair code (WCHP)

to cater for partially immobile passengers. At the same time it was proposed

to amend the definition of code WCHC for passengers who are completely

immobile. The goal of this proposal was to improve communications between

airlines and airports regarding the amount of assistance required for certain

wheelchair passengers which would improve overall service levels. However,

DL and UA could not accept the proposal on the grounds that it was in conflict

with US regulations. Accordingly the Chairman ruled this item defeated. The

Secretary offered to seek a compromise solution that would satisfy the US

and European regulators and subsequently circulate an AIRIMP mail vote.

This course of action was agreed.

ACTION: Secretary/ECAC/DoT

Secretary note: it has not been possible to develop a compromise proposal

that satisfies both the ECAC and US regulations.



### R5 Lithium Ion Powered Wheelchairs

184. The Secretary to the IATA Dangerous Goods Board proposed to

establish a new wheelchair code (WCLB) to cater for lithium ion battery

powered wheelchairs in recognition that new legislation allowed the carriage

of such wheelchairs. At the same time it was proposed to amend the

definition of code WCBD to clarify that it is for battery powered wheelchairs

fitted with a non-spillable battery. DL and UA initially could not support this

proposal, however, they subsequently abstained on the understanding that

the new code would be for use on a bilateral basis. The amendments to

### 31

AIRIMP are shown in Attachment N. The ATA Passenger Council agreed to

make counterpart changes to SIPP also as shown in Attachment N

. Conference requested the Secretary to editorially add code WCLB to

Resolution 700 and RPs 1708 and 1708a.

ACTION: Secretary

R6 WCMP/WCBD/WCBW/WCOB

185. ResCom noted that several wheelchair codes were reserved for use on

US carriers whereas such codes could also be useful for other airlines.

Accordingly it was proposed to amend the definition of the codes so that they

could be used by anybody on a bilateral basis. Conference agreed to amend

AIRIMP as shown in Attachment O . The ATA Passenger Council agreed to

make counterpart changes to SIPP also as shown in Attachment O

.

R7/P Reservations “Package”

186. This “package” contained miscellaneous items documented in R7.1/P

through R7.5/P which had been approved at ResCom with no opposition

noted. Conference unanimously adopted changes to AIRIMP in agenda items

R7.1/P through R7.5/P as shown in Attachments P through T . The ATA

Passenger Council unanimously agreed to counterpart changes to SIPP in

agenda items R7.1/P through R7.5/P also as shown in Attachments P

through T

.

R7.1/P Passenger Name (Format)

187. ResCom agreed to a complete re-write of AIRIMP 2.6 regarding the

name element to provide more guidance for “compound names” and for cases

where there is no family name, or no name is given. Conference agreed to

amend AIRIMP as shown in Attachment P

. The ATA Passenger Council

agreed to counterpart changes in SIPP also as shown in Attachment P

.

R7.2/P Requesting Additional Passen ger Information from the Booking

Source

188. RESWG proposed to establish a new SSR code (ADPI) to request data

from the booking source in order to recognize the request in both the sending

and receiving system. Conference agre ed to amend AIRIMP as shown in

Attachment Q

. The ATA Passenger Council agreed to counterpart changes

in SIPP also as shown in Attachment Q . ( Note – this item had previously

been adopted via an AIRIMP mail vote dated 28 June 2010 ).

### 32

R7.3/P Request for EMD Number

189. ResCom proposed to establish a new SSR code (ADMD) and

accompanying bilateral procedures to facilitate the request for EMD numbers.

Conference agreed to amend AIRIMP as shown in Attachment R

. The ATA

Passenger Council agreed to counterpart changes in SIPP also as shown in

Attachment R

.

R7.4/P Request for New Passenger with Service Animal SSRs:

ESAN/SVAN (Bilateral)

190. ResCom proposed to establish 2 new SSR codes (ESAN regarding

emotional support animals and SVAN to di fferentiate such animals from pets)

to meet US regulations for passengers with disabilities. Conference agreed to

amend AIRIMP as shown in Attachment S

. The ATA Passenger Council

agreed to counterpart changes in SIPP also as shown in Attachment S

.

R7.5/P Inclusion of Record Locator of Original Booking Office for Ticket

Number Notification Messages

191. ResCom proposed to amend AIRIMP to provide the record locator for

the original booking source when an ET is issued. Conference agreed to

amend AIRIMP as shown in Attachment T

. The ATA Passenger Council had

previously agreed to counterpart changes in SIPP at the JPSC meeting in

2009.



## MISCELLANEOUS

M1 Report - PSC Steering Group (PSCSG)

192. Conference noted this report. Ms Stephanie Yen (DL) graciously gave

up her seat as “Member at large for TC1” as she was automatically a member

of PSCSG having been elected Vice-Chairman of the PSC (agenda item A6

refers). The position for TC2 was filled by Ms Linda Grinfeld (LY). The

Secretary noted that the positions to represent TC1 and TC3 remain open.

M2 Report - PADIS Board (PADIS)

193. Conference noted this report.

### 33

M2.1 PNRGOV and Adoption by WCO

194. Conference endorsed the proposal to hand over responsibility for

adopting changes to XML schemas for PNRGOV to the WCO with certain

caveats.

M3 Report - Cargo Services Conference (CSC)

195. Conference noted this report.

M4 Report – Scheduling Services

196. Conference noted this report.

M4.1 Report - Schedules Information Standards Committee (SISC)

197. Conference noted this report.

M5 Report – Fraud Prevention Working Group (FPWG)

198. Conference noted this report and that the TICKETS Service for

blacklisting paper tickets would close on 1 February 2011.

M6 Report – BSP Data Interc hange Standards Group (BDISG)

199. Conference noted this report.

M7 Report – Strategic Partnerships

200. Conference noted this report.

M8 Report – PCI DSS Working Group

201. Conference noted this report and endorsed the proposal to develop a

recommended practice to provide guidance for implementation of PCI DSS

compliant systems. Accordingly it was agreed to extend th e mandate of this

group by a further 12 months.

M9 Report – Industry Carbon Offset Programme (ICOP)

202. Conference noted this report and agreed to remove the expiry date

from codes OE, OF and OG in Resolution 722f, noting abstentions from LH,

JL, OS, AF, KL and UA. The changes to Resolution 728 are shown in the

book of finally adopted resolutions and RPs.

### 34

M10 Report – Inflight Services

203. Conference noted this report.

M10.1 Standard Inflight Catering Agreement (SICA)

204. Conference established RP 1773b to provide guidance regarding a

standard inflight catering agreement. A copy of RP 1773b is shown in the

book of finally adopted resolutions and RPs.

Close of Meeting

205. The Chairman requested Mr. Art Kourajian (U nisys) to come to the top

table where IATA presented him with a plaque to recognize his consistently

strong support for industry activities over many years. The Conference

wished him well in his retirement. The Chairman closed the meeting at 17.30

hours.Attendance List30th Joint IATA/IATA Passenger Services Conference (JPSC)Geneva, 21 22 October 2010Company Name Name Job Title EmailAdria Airways Djanino Bubola Area Manager djani.bubola@adria.siAerosvit Airlines Lyudmyla Slobodyanyuk Coordinator Intl. Sales lyudmyla.slobodyanyuk@gmail.comAerosvit Airlines Voloshyn Maxym Director Intl. Relations voloshyn.maxym@gmail.comAir Canada Ellen Lageveen GM Passenger Service Dept. ellen.lageveen@aircanada.caAir China Buyan Lilibuyan@airchina.comAir China Dong Fanfei Sr. Manager Tariffs dongfanfei@airchina.comAir China Fanfei Dong dongfanfei@airchina.comAir China Li Buyan Manager, Regulatory Affairs libuyan@airchina.comAir France Bernard Charrier Tariff Distribution Manager becharrier@airfrance.frAir France Stephane Vanovermeir Product Distribution Manager stvanovermeir@airfrance.frAir Nostrum Ana CarrileroAlitalia Compagnia Aerea Italiana Anna Rita Coletta GDS Affairs coletta.anna.rita@alitalia.itAll Nippon Airways Hidetomo Aramaki Director, Rev. Mgmt, Global Rev. Mgmt aramaki@ana.co.jpAll Nippon Airways Kuniko Miyazaki Procedures & Regulations, Passengerku.miyazaki@ana.co.jp;miyazaki@ana.co.jpAll Nippon Airways Mitsuyo IdeSnr Mgr, Pax Service PlanningOperations & Apt Svcsm.ide@ana.co.jpAll Nippon Airways Yuki ShimizuAsst Mgr, Pax Service PlanningOperations & Apt Svcsyuki.shimizu@ana.co.jpAmadeus Laetitia Loones Product Manager Ticketing Distribution lloones@amadeus.comAmadeus Marc Adam Product Definition Analyst marc.adam@amadeus.comAmadeus Pascale Mansart Code Share and TTY Product Definition pmansart@amadeus.comAmadeus Stephen-Terence Corking Solution Manager Development scorking@amadeus.comAmerican Airlines Karen Churchill Manager Airport Services karen.churchill@aa.comARC Keith Venzke Snr Mgr, Reporting & Settlement kvenzke@arccorp.comATA Jim CaseyVP Industry Services & Deputy GeneralCounseljcasey@airlines.orgATA Patty Edwards Managing Director, Passenger Services pedwards@airlines.orgAustrian Airlines Brigitte EberleManager Reservations & TicketingDevelopment & Supportbrigitte.eberle@austrian.comAustrian Airlines Marcus LenkHead of Reservatins & TicketingSteeringmarcus.lenk@austrian.comAXESS International Network Inc. Tomoko IgawaSr Mgr, Reservation & TicketingSystem, Product Plngigawa.tomoko@axess.co.jpBritish Airways Jerry Foran Product Delivery Manager jerry.foran@ba.comBrussels Airlines Ann Collette Procedure Officer anna.collette@brusselsairlines.comBrussels Airlines Tony Capiau IT Manager tony.capiau@brusselsairlines.comChairman Patricia George (Chairman) Chairman JPSC, COMP, ISSAC pageorge@wanadoo.frChina Eastern Wei Zhiqiang Deputy GM of RM Dept. zqwei@ceair.comAttendance List30th Joint IATA/IATA Passenger Services Conference (JPSC)Geneva, 21 22 October 2010Company Name Name Job Title EmailCondor Flugdienst GmbH Matthias O, Koester Head of Distribution matthias.koester@condor.comContinental Airlines Inc. Craig ThomasContinental Airlines Inc. Kathy EllisMgr, Station Administration &Automationkellis@coair.comContinental Micronesia Desmond Fullerton Senior Manager Technology des.fullerton@coair.comCubana de Aviacion SA Soinelia Rodriguez Tariffs Manager soinelia.rodriguez@cubana.avianet.cuCzech Airlines Jiří FontanaCzech Airlines Jirina Klimova Fare Distribution & Ticketing Senior Manjirina.klimova@csa.czCzech Airlines Michal Hájek Regulation Specialist michal.hajek@csa.czDelta Air Lines Kendal ChapmanProject Leader - ReservationsAutomationkendal.chapman@delta.comDelta Air Lines Stephanie Yen Manager, Industry Affairs stephanie.yen@delta.comEgyptair Hisham Magdy Industry Affairs Specialist hisham_magdy@egyptair.comEl Al Israel Airlines Ltd. Donna Bahar Mgr Reservation & Distribution Systems donnab@elal.co.ilEl Al Israel Airlines Ltd. Linda Grinfeld Deputy Director IATA & Pricing linda@elal.co.ilFinnair Marko HaaksialaFinnair Päivi Rautanen Product Manager paivi.rautanen@finnair.comGulf Air Warren HilesHahn Air Jörg Troester SVP Corporate Strategy j.troester@hahnair.comHahn Air Katharina Becker Director Legal Dept. k.becker@hahnair.comHawaiian Airlines Jared Stalder Process Development Specialist jared.stalder@hawaiianair.comHewlett Packard Lucia Gerber Product Manager lucia.gerber@hp.comIATA Mike Muller (Secretary) Head, Passenger Interline Standardsmullerm@iata.orgIATA Dave McEwen Manager, Passenger Interline Standardsmcewend@iata.orgIATA Eric Leopold Head, Passengerleopolde@iata.orgIATA Aleks Popovich Senior Vice President, IDFSpopovicha@iata.orgIATA Nicolas Bondarenco ABR Project Managerbondarencn@iata.orgIATA Paul Behan Head, Passenger Experiencebehanp@iata.orgIATA Stephan CopartProject Manager, Fast TravelProgrammecoparts@iata.orgIATA Mike Irons Manager, BCBP Project & Ticketing andironsm@iata.orgIATA Andrew Price Head, Baggage Servicespricea@iata.orgIATA Alban Sato Manager, Interline Tariffssatoa@iata.orgIATA Sebastien Touraine Project Manager, e-Servicestouraines@iata.orgIATA Cristina Rotor Manager, Tariff Solutions & Distributionrotorc@iata.orgIberia Airlines Mary Jo Reviejo Project Coordinator & Industry Relations mjreviejo@iberia.esIcelandair Thora Helgadottir Project Manager Customer Experience thorah@icelandair.isInfini Travel Information Inc. Mariko Wada Product Analyst wada0330@infini-trvl.co.jpAttendance List30th Joint IATA/IATA Passenger Services Conference (JPSC)Geneva, 21 22 October 2010Company Name Name Job Title EmailInfini Travel Information Inc. Toru Hasegawa Deputy Director hasegawa0203@infini-trvl.co.jpITA Software, Inc. Amy M. Sexton Legacy Systems Interaction - QA asexton@itasoftware.comITA Software, Inc. Kami Link QA Pricing Analyst klink@itasoftware.comJapan Airlines Eri Miyake Manager eri.miyake@jal.comKLM Royal Dutch Airlines Johan Lodewijckx Manager IATA & Industry Affairs johan.lodewijckx@klm.comKorean Air Keunhae KIM Manager kimkh@koreanair.comLOT Polish Airlines Beata Knobelsdorf-Kocepup IATA Rules & Regulation Advisor b.knobelsdorf-kocepup@lot.plLufthansa Danjela Janke Manager Global Ground Processes danjela.janke@dlh.deLufthansa Mario Zimmermann Snr Manager Global Ground Processes mario.zimmermann@dlh.deLufthansa Martin SchwarzLufthansa Michelle BryantManager Distribution Systems andIATA Industry Affairsmichelle.bryant@dlh.deMEA Salim Kharrat In Charge Agency & Procedures/CargoTkharrats@mea.com.lbQantas Airways Leonie Privett Manager Strategic Projects lprivett@qantas.com.auQatar Airways Stephane Baudemont Mgr, Interline, Tariffs & Industry Affairs sbaudemont@qatarairways.com.qaSabre Holdings Tim Powell Director Industry Affairs tim.powell@sabre.comSaudi Arabian Airlines Ayed Mesfer Alotaibi Snr Specialist Apt Svcs aalotaibi@saudiairlines.comScandinavian Airlines Elaine Rusen Manager Industry Affairs elaine.rusen@das.seSITA John Meeks Manager john.meeks@sita.aeroSouth African Airways Madelein VorsterSwiss International Air Lines Ltd. Patrick Graf Senior Manager, Head of Revenue Manapatrick.graf@swiss.comSwiss International Air Lines Ltd. Patrick Schmid Passenger Handling Policies partick.schmid@swiss.comSwiss International Air Lines Ltd. Vera Magron Habedus IT BA & Project Leader Senior vmag@swiss.comSyrian Arab Airlines Fajer Ali Manager, Agency Division fajer.ali@syriaair.comSyrian Arab Airlines Nadia Awad Intl. Organisations Manager fajer.ali@syriaair.comThai Airways Intl. Janpen Rana Chief, Sales and Marketing Procedures janpen.r@thaiairways.comTravelport Jim Erickson Senior Product Manager jim.erickson@travelport.comUnisys Corporation Arthur Kourajian Manager Airline Industry Affairs arthur.kourajian@unisys.comUnited Airlines Rosalie Crabbe Project Manager Partnerships & Internat rosalie.crabbe@united.comUS Airways Deryl Purvis rosana.turner@usairways.comUS Airways Alex Schaefer Manager Airport Services alex.schaefer@usairways.comVirgin Nigeria Airways Dorcas Aketch Manager Interline & IATA Affairs dorcas.aketch@virginnigeria.comPassenger Week 2011Singapore, 10-14 October 2011Wed, 12 Oct09.00-12.30PAConf/3413.30-18.00JPSCMon, 10 Oct09.00-10.00PSG/7811.00-18.00PAPGJC/15Tue, 11 Oct09.00-18.00PAConf/3418.00-19.00JPSC AgendaReview MeetingVersion 4.009.00-18.00JPSC09.00-10.00COMPAgendaReviewMeeting10.30-18.00COMPMeetingFri, 14 OctThu, 13 OctPSG=Passenger Agency ConferenceSteering GroupPAPGJC=Passenger Agency ProgrammeGlobal JointCouncilPAConf =Passenger Agency ConferenceJPSC =Joint ATA/IATA Passenger ServicesConferenceCOMP =Passenger Tariff Composite Conference

### JPSC/30 PSC/32 Oct 10

Attachment: C

Page: 1 of 1

Ticket Code Country

AD Andorra

AQ Antarctica

BV Bouvet Island

FM Micronesia

GS South Georgia & the South Sandwich Is.

HM Heard & McDonald Is.

IO British Indian Ocean Territories.

LI Liechtenstein

MC Monaco

SH Saint Helena

SM San Marino

TF French Southern Territories

TK Tokelau

UM US Minor Outlying Islands

VA Vatican City State

### JPSC/30 PSC/32 Oct 10

Attachment: D

Page: 1 of 3



## NEW TAX CODES

SEPTEMBER 2009

CODE N A M E C O U N T R Y R E Q U E S T

E D

B Y D A T E P U R P O S E / D E T A I L S

-OH- TRANSIT PASSENGER

SERVICE FEE LATVIA AIR BALTIC 31/08/09 FOR THE USE OF TRANSIT

PASSENGER TERMINAL

INFRASTRUCTURE.

-BT- PASSENGER SERVICE

CHARGE BHUTAN DRUKAIR 06/10/09 AIRPORT DEPARTURE TAX

-OI- PASSENGER SECURITY

SERVICE CHARGE JAPAN JAPAN AIRLINES 08/10/09 RECOVER COSTS OF AVIATION

SECURITY

- NH - PASSENGER TERMINAL

USAGE FEE JORDAN ROYAL

JORDANIAN

AIRLINES 22/12/09 COVER PASSENGER TERMINAL

COSTS, AS IMPOSED BY

JORDANIAN GOVERNMENT

- OJ - AIRPORT SECURITY FEE COTE D’IVOIRE SOCIETE

NOUVELLE AIR

IVOIRE 23/12/09 IMPROVEMENT OF THE CAPACITY,

FACILITIES AND EFFICIENCY OF

AVIATION SECURITY AT ABIDJAN.

- OK- EMBARKATION TAX GUINEA-BISSAU TAP AIR

PORTUGAL 29/12/09 PROVISION OF PASSENGER

SERVICES

- OL - SECURITY TAX GUINEA-BISSAU TAP AIR

PORTUGAL 29/12/09 PROVISION OF SECURITY SERVICES

- ON- AERONAUTIC

DEVELOPMENT TAX GUINEA-BISSAU TAP AIR

PORTUGAL 29/12/09 DEVELOPMENT OF AERONAUTICA L

INFRASTRUCTURE

- OQ- AIRPORT DEPARTURE

CHARGE NIGER AIR FRANCE 07 /01/10 DEVELOPMENT OF AIRPORT

INFRASTRUCTURE

-OR- AIRPORT TAX ECUADOR TAME 11/01/10 USAGE OF AIRPORT TERMINAL

AND AUXILIARY SERVICES

-OO- PASSENGER SECURITY

SERVICE CHARGE SINGAPORE SINGAPORE

AIRLINES 12/01/10 SECURITY COSTS, AND

MAINTENANCE AND OPERATING

COSTS OF SECURITY EQUIPMENT

- OP- AVIATION LEVY SINGAPORE SINGAPORE

AIRLINES 12/01/10 FUND CAAS ACTIVITIES TO

PROMOTE, DEVELOP AND

REGULATE AIRPORTS AND

IMPROVE PASSENGER SERVICE.

### JPSC/30 PSC/32 Oct 10

Attachment: D

Page: 2

- OS- AIRPORT SERVICE

AND SECURITY

CHARGE GRENADA AMERICAN

AIRLINES 22/01/10 PROVISION OF AIRPORT AND

SECURITY SERVICES

- IQ- DEPARTURE TAX IRAQ ROYAL

JORDANIAN

AIRLINES 28/01/10 PROVISION OF PASSENGER

SERVICES AT BAGHDAD

- OT - SECURITY AND

INFRASTRUCTURE

CHARGE SIERRA LEONE BRUSSELS

AIRLINES 28/01/10 DEVELOPMENT OF SECURITY

AND AIRPORT INFRASTRUCTURE

- OU - TRANSPORTATION TAX

SALES OUTSIDE COSTA

RICA COSTA RICA LINEAS AREAS

COSTARICENSES

(LACSA) 26/02/10 TO SUPPORT COSTA RICAN

TOURIISM INDUSTRY

-OV- TERMINAL EXPANSION

FEE MAURITIUS AIR MAURITIUS 26/02/10 EXPAND TERMINAL

INFRASTRUCTURE AT MAURITIUS

(MRU) INTERNATIONAL AIRPORT

-OX- AIRPORT SECURITY FEE MOZAMBIQUE LAM LINHAS

AEREAS DE

MOCAMBIQUE 01/04/10 PROVISION OF ENHANCED

SECURITY SERVICES

- OZ - AIRPORT

DEVELOPMENT

CHARGEa TURKS &

CAICOS IS. AIR TURKS

&CAICOS;

AMERICAN

AIRLINES 07/05/10 CONTRIBUTION TO ASSIST IN

OFFSETTING THE COST OF THE

PROVIDENCIALES

INTERNATIONAL AIRPORT

REDEVELOPMENT

- NY- PASSENGER SERVICE

FEE SUDAN SUDAN

AIRWAYS 02/07/10 TO DEVELOP AIRPORT SERVICES

- PB - ADVANCE TAX

(DOMESTIC) PAKISTAN PAKISTAN

INTERNATIONAL

AIRLINES 05/07/10 ADVANCE TAX ON THE

PURCHASE OF DOMESTIC

TICKETS TO COMPLY WITH

GOVERNMENT DECREE

- OW- EXCISE DUTY BANGLADESH BIMAN

BANGLADESH 12/07/10 IMPOST BY THE GOVERNMENT

OF BANGLADESH FOR EXCISE

DUTY

- PC- PASSENGER FACILITY

CHARGE – BONAIRE NETHERLANDS

ANTILLES KLM ROYAL

DUTCH AIRLINES 19/07/10 USAGE OF PASSENGER

FACILITIES AT THE BONAIRE

AIRPORT

### JPSC/30 PSC/32 Oct 10

Attachment: D

Page: 3



## CODES RESCINDED, WITH DRAWN OR EXPIRED

CODES REINSTATED

No codes were reinstated - OY - AIR TRANSPORT TAX GERMANY LUFTHANSA 03/09/10 IMPOST FOR THE EXCHEQUER OF

THE GERMAN GOVERNMENT TO

GENERATE INCREASED TAX

REVENUE.

- PP - AIRPORT SECURITY

CHARGE TURKMENISTAN TURKISH

AIRLINES 20/09/10 PROVISION OF ENHANCED

SECURITY SERVICES AT THE

ASHGABAD (ASB) AIRPORT

- PJ - PASSENGER FACILITY

CHARGE PANAMA TACA 21/09/10 AIRPORT MAINTENANCE AND

IMPROVEMENT

- PI - TOURISM ARRIVAL TAX

FOR SALES MADE

OUTSIDE NICARAGUA NICARAGUA TACA 21/09/10 IMPOST BY THE GOVERNMENT

OF NICARAGUA TO SUPPORT

THE INSTITUTO NICARAGUENSE

DE TURISMO (INTUR) AND

PROMOTION OF NICARAGUA

OVERSEAS

- PO - PASSENGER

PROCESSING FEE BAHAMAS BAHAMASAIR 22.09.10 RECOVER COST OF TERMINAL

SERVICES

-NS- TICKET AID TAX JORDAN ROYAL

JORDANIAN

AIRLINES 19/01/10 RESCINDED

-GD- GOVERNMENT TICKET

TAX GRENADA AMERICA

AIRLINES 01/02/10 DISCONTINUED

- JB - IVA (VALUE ADDED

TAX) ON THE AIRPORT

DEPARTURE TAX. PERU TACA 30/09/10 DISCONTINUED AND

INCORPORATED INTO THE

AIRPORT DEPARTURE TAX. NO

NEED TO SHOW IVA SEPARATELY

### JPSC/30 PSC/32 Oct 10

Attachment: E

Page: 1 of 3



### ZMF/IATA Staff Travel Automated Solutions (ZISTAS) Working Group

Terms of Reference

The ZED-MIBA Forum (ZMF) and IATA establish a joint working group to investigate

and recommend automated solutions in order to facilitate interline electronic staff

travel (industry discount) ticketing to meet the deadline of 31 March 2012, after

which ZMF members will no longer accept paper tickets.

Objectives

Decide which of the following items to progress, and produce a project plan for each

agreed item:

• Not Interline Electronic Ti cketing (NIET) (e.g. trans porting carrier tickets or

ticketless)

• IET: Whether SA messaging is a requirement

o AIRIMP requirements are already set, and will use SA even if DS or

MM are used internally

• IET: Listing website

Procedures should be as close as possible to commercial procedures, whilst

recognizing that this may be more diffic ult for standby travel without SA messaging

Work plan

IATA Resolutions and Recommended Practices

Determine any changes required to IATA Resolutions and/or Recommended

Practices, and liaise with owning managers in participating airlines to ensure detailed

specifications are developed

System Providers

Work with I.T. system providers, both hosted solution providers and rebate travel

system providers to understand and confirm ca pability, availability of all available

options and implementation strategies

Airlines

Evaluate and document airline specific requirements and agree a common process

Evaluate cost of SA messaging and come to an industry understanding of

reservations processes.

### JPSC/30 PSC/32 Oct 10

Attachment: E

Page: 2



### Communications

Evolve a communication plan both for ZMF and IATA members and non-participating

ZMF/IATA members on progress. Agree communications plan (especially who does

it and how, split into pro-active and re-active communications) and review feedback .

Stakeholders

Membership will consist of representative s from ZMF and IATA airlines as well as

industry suppliers (e.g. GDSs as hosted solution providers and rebate travel solution

providers) with expertise in ticketing, st aff travel procedures and automated systems.

The working group will have a one year m andate and will repo rt to the ZED-MIBA

Advisory Council (ZMAC) and the PSC with any proposed technical improvements.

The Secretary will be the IATA Manager, Passenger Interline Standards and a

nominated officer of the ZMAC.

Modus Operandi

2 meetings a year shall take place with additional conference calls and web

seminars as required. Meetings will be held in Montreal or Geneva.

### JPSC/30 PSC/32 Oct 10

Attachment: E

Page: 3



### In scope and out of scope

In scope

• Interline standby travel for airline staff

o Personal (ZED) Standby Travel on and by ZMF members

o Duty (MIBA) Standby Travel on and by ZMF members

• Interline bookable travel for airline staff

o Personal (ZED) Bookable Travel on and by ZMF members

o Duty (MIBA) Bookable Travel on and by ZMF members

• Communications to ZMF members and IATA

• Communicate to non-ZMF members, especially IATA members

Out of scope

• All other standby travel, including but not limited to:

o Commercial standby travel

o AD standby

o RG standby

o Standby travel on and by airlines not members of ZMF

• All other bookable travel, including but not limited to:

o Commercial bookable travel

o AD bookable

• RG bookable staff travel on and by airlines not members of ZMFSimplifying the Business1©COPYRIGHT IATA 2010Simplifying the BusinessEMD updatesSébastienTouraineProject Manager, IATA e-servicesPassenger WeekGeneva, 22 October 2010Simplifying the Business2©COPYRIGHT IATA 2010Agenda1.Why IATA is pushing for implementation of a global standard forAncillary Revenues?2.EMD worldwide industry deployment status3.Next steps and EMD implementation prioritiesSimplifying the Business3©COPYRIGHT IATA 2010Airlines Ancillary Services trend up by 43%to €11 billion in 2009(Source : Ideaworks)Simplifying the Business4©COPYRIGHT IATA 2010IATA e-services100% EMD to facilitate sales, fulfillment and collection ofancillary services through alldistribution channelsEMDTraditional MiscellaneousDocumentsDirect salesGDSOptional servicesAncillaryServicesVision is confirmed by latest campaign where94.6%of committedairlines plan to deploy EMD in all sales channelsSimplifying the Business5©COPYRIGHT IATA 2010E-Services Benefits -IATA Board Targets ̧Main Benefits: ̧A global industry standardforissuance, fulfillment and collection ofancillary services ̧Industry standardsolution that delivers acommon process acrossall sales channels ̧More efficient processes and increased back-office productivity ̧Increase visibility in Revenue Accounting and Revenue Management ̧BusinessCase: ̧$450m-$900m cost savings ̧$2bn revenue increase ̧Total: up to$2.9bnbenefits ̧Target: ̧End-2010: 6 major GDS and 10 airlines EMD capable ̧End-2012: all airlines EMD capable ̧End-2013: 100% EMD usage in BSPSimplifying the Business6©COPYRIGHT IATA 2010Current status of airlines -EMD capability ̧150 airlines representing 87% of passenger volumes of top 200 airlinesengaged are committed to EMD implementation ̧12 airlines forecasted to be EMD capable by end 2010 with one airline Majorin each region60494585Implemented EMDPlanning EMDCommittedtoEMDNoansweron commitmenttoEMDNot commitmenttoEMDSource: Initial resultsIATAStBcampaign–StatusOct-2010Simplifying the Business7©COPYRIGHT IATA 2010Enabling EMD-S and EMD-A ̧Airlines EMD solutions should enable both EMDsOnly 2% of the airlinesengaged plan to have EMD-S onlyTypeofsolution forEMDEMD-S only2%Notdecidedyet25%BothEMD-SandEMD-A73%Source: Initial resultsIATAStBcampaignto116 EMDcommittedairlinesSimplifying the Business8©COPYRIGHT IATA 2010GDS EMD deployment is an industry priority ̧94.6%of EMD committed airlines are planning to deploy EMD inall sales channelsAirline’s intention to approaching their GDSs0102030405060AmadeusSabreGalileoWorldspanOtherAbacusTravelsky

N u m b er o f ai r l i n esSource: Initial resultsIATAStBcampaignto116 EMDcommittedairlinesSimplifying the Business9©COPYRIGHT IATA 2010GDS and System providers are committed tosupport EMD ̧IATA has confirmed with6 top GDS(handling 95% of passengers GDS bookings)that they would be ready by end of 2010 ̧IATA visited majorsSystem Providersto ensure that EMD servers are underdevelopmentMajorGDS95%OtherGDS5%GDSby ticketvolumesinBSP(Jan 2010)*MajorGDS: Amadeus, Sabre,Abacus, ChinaTravelsky, Galileo andWorldspanHowever, IATA urges airlines and industry providers to accelerate theirimplementation slot allocations to make EMD a reality and bring the muchneeded benefits to the industrySimplifying the Business10©COPYRIGHT IATA 2010Coming soon...the 1stEMD sold viatravel agency in FinlandSimplifying the Business11©COPYRIGHT IATA 2010Perspective of EMD in the interline businessEMD service tointerline0102030405060708090100BaggageAirtransportationFinancialimpactAirportservicesIn-flightserviceSurfacetransportationMerchandise

N u m b e r o f a i r l in e s ̧88% of airlines engaged plan to use EMD for interliningPlans touse EMDforinterliningYes88%No12%Source: Initial resultsIATAStBcampaignto116 EMDcommittedairlinesSimplifying the Business12©COPYRIGHT IATA 2010IATA e-services Action Plan ̧IATA continuous supportto increase the number EMD capable airline, a mustbyend 2012 ̧Support and coordinate deployment ofancillary services in travel agencycommunity and BSP ̧Further mobilization ofRevenue Accounting and DCS/Ground Handlers community⇒Industry meetings⇒Regional Workshops⇒EMD matchmakerSimplifying the Business13©COPYRIGHT IATA 2010EMD Implementation Priorities ̧3 main EMD airlines implementation phases1.EMD capability on direct sales (all airlines committed)2.EMD deployment in GDS , reported inBSP ->100 % usage in BSP (end2013)3.EMD interline capability based on business requirements (bilateral, alliance) ̧GDS EMD live(one EMD issued by partner airlines in a BSP)deploymentis a priority ̧Stakeholder managementwith other systems impacted by EMDintroductionSimplifying the Business14©COPYRIGHT IATA 2010For updated information, go to e-servicesweb page ̧http://www.iata.org/whatwedo/stb/e-services/Pages/index.aspxSimplifying the Business15©COPYRIGHT IATA 2010For further information please contact:SébastienTouraineProject Manager,e-servicesSimplifying the BusinessGeneva, SwitzerlandE-mail Touraines@iata.orgTelephone +41 (22)770-2829Thank You!

### JPSC/30 PSC/32 Oct 10

Attachment: G

Page: 1 of 1



### Agency Solutions Technical Working Group (ASTWG)

Terms of Reference

The Agency Solutions Technical Workin g Group (ASTWG) may consider any

technical aspect in relation with the IATA Passenger Programme, which concerns

Accredited Agents, BSP Carriers and GDSs.

In order to enhance efficiency and minimize the likelihood of billing disputes, the

ASTWG is to determine the circumstances under which a GDS “guaranteed fare” is

accorded the same meaning by the Accredited Agent and the airline.

The working group will focus on process efficiency to make recommendations for

best practice and process improvements which reduce the need to issue ADMs and

specifically identify the technical criteria under which the ticket record is indeed

guaranteed by the GDS.

The conditions under which fares and associated conditions are filed by the airlines

with fare filing companies, for example, will also be examined.

The working group will define and agree the technical circumstances under which

the direct settlement of ADMs between the airline and the GDS may be envisaged.

Membership will consist of airline representatives from the PSC Steering Group as

well as members of IATA’s Strategic Partners programme, experts from Accredited

Agents and experts from other disciplines as required.

The working group will have a one year manda te and will report to the PSC with any

proposed technical improvements.

### JPSC/30 PSC/32 Oct 10

Attachment: H

Page: 1 of 1

AIRPORT SERVICES COMMITTEE (ASC) MEMBERSHIP 2011

Airport Services Committee (ASC) Membership 2010

Airline Traffic Conference Area Term of Office Expires

Air France 1 2012

Alitalia 2 2013

American Airlines 1 2011

British Airways 2 2012

Delta Airlines 1 2011

Egyptair 2 2013

El Al 2 2013

Iberia 2 2011

Japan Airlines 3 2013

KLM 2 2012

Lufthansa

(Vice Chairman) 2 2012

Malev 2 2011

Qantas 3 2011

US Airways 1 2011

United 1 2012

vacant

Vacant

vacant

### JPSC/30 PSC/32 Oct 10

Attachment: I

Page: 1 of 1



### TICKETING COMMITTEE (PFPC) MEMBERSHIP

Airline Traffic

Conference

Area Year Term of Office Expires

at Conclusion of Passenger

Services Conference:

Air Canada 1 2011*

Air France 2 2011*

All Nippon Airlines 3 2011*

American Airlines 1 2011*

British Airways 2 2013

Continental 1 2011*

Delta Air Lines 1 2012

Egyptair 2 2013

Emirates 2 2013

Japan Airlines 3 2012

KLM 2 2013

LAN 1 2012

Lufthansa 2 2013

SAS 2 2012

South African Airways 2 2011*

United Airlines 1 2011*

US Airways 1 2013

Virgin Atlantic Airways 2 2011*

* Expires at the conclusion of PSC 2011

### JPSC/30 PSC/32 Oct 10

Attachment: J

Page: 1 of 1



### IATA Reservations Committee Membership

Airline TC area Year Term of Office Expires

Air France (AF) 2 2013

Air Canada 1 2013

All Nippon Airways (NH) 3 2012

Continental Airlines (CO) 1 2011

Delta Air Lines (DL) 1 2012

Egyptair (MS) 2 2011

El Al (LY) 2 2012

Emirates (EK) 2 2011

Etihad (EY) 2 2011

Finnair (AY) 2 2012

Iberia (IB) 2 2011

Japan Airlines (JL) 3 2012

KLM (KL) 2 2012

Lufthansa (LH) 2 2013

Scandinavian Airlines System (SK) 2 2012

United Airlines (UA) 1 2012

US Airways (US) 1 2011

Virgin Atlantic (VS) 2 2011JPSC/30 PSC/32 Oct 10Attachment: KPage: 1 of 2TopicProgressNext StepsAction byTarget Date1 AIRIMP Audit and Clean-up Ongoing itemPhase 1 is completeFuture RESWG and ResCom meetings asappropriate.Should any member have additionalsuggestions for amendments, email to IATA.All2 TSA Secure Flight Program Developed options for consideration toensure that minimum mandatory TSA(secure flight) data elements are with theairline 72 hours before departure for allflights to/from/within USA (and for all flightsoperated by US carriers)RESWG/14 agenda item 5.1Agreed to offer a product to inhibitticketing if mandatory elements are notpresent at time of ticketingAll members of RESWG were urged toinvestigate these options within theircompanies and with their 3rdparty bookingpartners to determine which options should beimplemented as soon as possible. Memberswere requested to develop specific proposalsfor consideration at the next meeting.RESWG drafted a proposal to the SISC to addan indicator to the SSIM file to designate theapplicable flights, which will better allowairlines and GDS to inhibit ticketingIf it is approved by SISC, it will be included inthe October 2010 edition of the SSIM Manualand is effective the date of publication.AllSISCASAP (before01Nov2010)3 AIRIMP Request for APIDataUnisys proposed concept at RESWG/13RESWG14 endorsed the proposalAgreed at ResCom/22 – item 15JPSC IATA/ATA JPSC4 Fixed Request FixedReply/Cancel as Free TextRESWG/14 agenda item 7 Agenda item 7 from RESWG/14 to be updatedand submitted to RESWG/15Amadeus RESWG/155 Name Element Update RESWG/13Agreed at ResCom/22 – item 14Agreed minor amendment to AIRIMPJPSCIATA/ATAJPSC6 Passenger Name Element Concluded that input would be requiredfrom RES, TKT and DCS expertsRESWG/14 Item 5Agreed at ResCom/22 – item 14Schedule special session of RESWG just tofocus on this issue and invite experts fromticketing and DCSJPSCIATA/ATAJPSC7 Additional Services forInfants not Occupying a SeatBA to re-write the proposal following inputfrom RESWG/13BA to provide new item with examples to futuremeetingBA RESWG orResCom8 Discussion item on SSRs RESWG/13 reviewed proposal by SITARESWG/14 Amadeus will prepare an itemfor the next meetingAll members to propose changes to StephenCorking (Amadeus) for him to consolidate in asingle agenda proposalAllAmadeusRESWGJPSC/30 PSC/32 Oct 10Attachment: KPage: 29 Inclusion of Record Locatorof Original Booking Office forTicket Number NotificationMessagesConcluded that ResCom/22 should readdress the item as discussed atResCom/21Agreed at ResCom/22 (item 19) to resubmit item to JPSCJPSCIATA/ATAJPSC10 Additional services –increase number in partySubmitted to RESWG/14 by Amadeus Comments to be sent to Amadeus Amadeus RESWG/1511 Bilateral SSRs Submit to RESWG/15 Amadeus to prepare an agenda item fordiscussion at RESWG/15Amadeus RESWG/1512 Credit Card as FOIDIt seems some airlines are receiving credit cardinformation as FOID when they do not requestreceipt. Do we need to make it implicit that onlythose airlines wishing to receive it, receive it?AllRESWGmembersRESWG/1513 Automated Baggage RulesTask ForceRESWG requested to be informed ofstatusRESWG and ResCom are requested toregister for access to the ABRTF extranet siteat www.iata.org/workgroups/Pages/abrtf.aspxto get more information on this significantproject impacting DCS and check-in systems.AllRESWGmembersRESWG/15

### JPSC/30 PSC/32 Oct 10

Attachment: L

Page: 1 of 5



### Proposed Additions/Modificat ions to AIRIMP and ATA R esolution 105.175 with an

effective date of 01 May 2009

3.13 ADVANCED PASSENGER INFORMATION – API (105.175, section 12)

Information should be provided when a pass enger is travelling on an international a service(s)

where API is required by the departure or arrival authorities.

When SSR information is provided, formats s hould be observed and as many data elements as

possible should be provided. If it is not possibl e to provide all data elements, an Oblique (/) is

inserted to indicate an element is missing. This is not required when no further components are

provided.

Separate SSR items are required for each passenger, if applicable.



### The following documents have been defined by ICAO 9303 as travel documents

3.13.1.1 Definitions

The following documents have been defined by ICAO 9303 as travel documents:

Approved non-standard identity documents used for travel (as defined by the issuing

Country/State)........................... ..............................................................F

Identity Card (as defined by the issuing Country/State)...................................A

Identity Card (as defined by the issuing Country/State)...................................C

Identity Card (as defined by the issuing Country/State).....................................I

Passport Card........................................................................................IP

Passenger Passport................... ..............................................................P



## ...

A visa, is considered as supplementary to the travel documentation and, when required, visa

information is supp lied using SSR DOCO.

Other supplementary travel documentation, when applicable, is suppl ied using SSR DOCO.



## ...

### JPSC/30 PSC/32 Oct 10

Attachment: L

Page: 2



## 3.13.2 API – Passenger Other Supplementary Information

3.13.2.1 Definitions

The following data types are defined as supplementary travel information:

Visa Number ...................................................................................... V

Redress Number.................................................................................. R

Known Traveller Number..................................................................... K

(a) Visa

Visa and Place of Birth are the element s that may be included as other suppleme ntary

passenger information.

A Visa is considered a supplementary travel information document and must be used

in conjunction with a travel document such as a Passport.

If required, element Place of Birth requires manual data capture methods as it is

located in the visual zone of a passport and is identified using the full place name.

Place of Birth may also include the country code.

Element Visa issuing Country/State must be provided in situations where a passenger

is travelling to two or more Countries/Sta tes requiring separate Visa documents. This

element is a data collection requirement and is needed in order to provide the correct

Visa information for the relevant Country/State information.

(b) Redress Number

A Redress Number is issued by a partic ipating government to a passenger and

is considered supplementary travel informat ion. When available, this number may be

provided to the Member.

(c) Known Traveller Number

A Known Traveller Number is issued by a participating government to a passenger and

is considered supplementary travel informat ion. When available, this number may be

provided to the Member.

### JPSC/30 PSC/32 Oct 10

Attachment: L

Page: 3



### 3.13.2.2 C onstruction Rules and Sequence of Components – Non-Automated

Format

Components Number and

Type of

Characters Example

(a) Supplementary Identifier 3a SSR



### (b) Special Service Requirement Code 4a DOCO



### (c) Airline Designator 2an or 3a AA or / ABC



### (d) Status Code 2a HK



### (e) Number in Party for this SSR 1n 1



### (f) Place of Birth Max. 35a AMBER HILL GBR



### (g) Supplementary Travel Information Travel Document Type

ICAO 9303 = V 1a V



### (h) Visa Document Supplementary Travel Information Number Max.

25 15 an 9891404



### (i) Visa Document Place of Issue Max. 35a LONDON



### (j) Visa Document Issue Date

DDMMMYY 7an 14MAR03



### (k) Country/State for which the Visa Document

Supplementary Travel Information is applicable 1-3a USA



### (l) Infant Indicator

I = Infant

(if an infant not occupying seat) 1a I



### (m) Name Information

(If the Supplementary Travel Information ot her travel

related information does not apply to all passengers in the

PNR, follow with a hyphen and passenger name field for

whom the element applies.)

(i) Hyphen (-) Hyphen

- 

### (ii) PNR Associated Name Including number in party 1STEVENSON/JOH

NMR

### JPSC/30 PSC/32 Oct 10

Attachment: L

Page: 4



### 3.13.2.3 Construction Rules and Seque nce of Components – Automated Format

An oblique (/) is inserted between each of the elements following (f) Segment . Where

the components of the supplementary inform ation are not provided, an oblique (/) is

inserted to indicate an element is missing. This is not required when no further

components are provided.

Components Number and

Type of

Characters Example

(a) Supplementary Identifier 3a SSR



### (b) Special Service Requirement Code 4a DOCO



### (c) Airline Designator 2an or 3a AA or / ABC



### (d) Status Code 2a HK



### (e) Number in Party for this SSR 1n 1



### (f) Segment: The segment and flight data must be the same

as shown in a segment element.

(i) Boarding Point 3a LHR



### (ii) De-planing Point 3a JFK



### (iii) Flight Number 4n 0234



### (iv) Class of Service 1a F



### (v) Date (DDMMM) 5an 03OCT



### (g) Place of Birth Max. 35a AMBER HILL GBR



### (h) Supplementary Travel Information Travel Document Type

ICAO 9303 = V 1a V



### (i) Visa Document Supplementary Travel Information Number Max.

15 25an 9891404



### (j) Visa Document Place of Issue Max. 35a LONDON



### (k) Visa Document Issue Date

DDMMMYY 7an 14MAR03



### (l) Country/State for which the Visa Document

Supplementary Travel Information is applicable 1-3a USA



### (m) Infant Indicator

I = Infant

(if an infant not occupying seat) 1a I



### (n) Name Information

(If the Supplementary Travel Information other travel

related information does not apply to all passengers in the

PNR, follow with a hyphen and passenger name field for

whom the element applies.)

(i) Hyphen (-) Hyphen

- 

### (ii) PNR Associated Name Including number in party 1STEVENSON/JOH

NMR

### JPSC/30 PSC/32 Oct 10

Attachment: L

Page: 5



### 3.13.2.4 Examples

... (f) Non-Automated Format (1)

A passenger supplies a United Stat es Redress number for this PNR:

SSR DOCO AA HK1//R/1234567890123///US-1CADE/BOBBI



### Automated Format (2)

A passenger supplies a United Stat es Redress number for this PNR:

SSR DOCO AA HK1JFKLAX0001Y28JUN//R/1234567890123///US

SSR DOCO AA ///-1CADE/BOBBI



### (g) Cancellation - Non- Automated Format (1)

A passenger supplies a United Stat es Redress number for this PNR:

SSR DOCO AA XX1//R/1234567890123///US-1CADE/BOBBI



### Cancellation - Automated Format (2)

A passenger supplies a United Stat es Redress number for this PNR:

SSR DOCO AA XX1JFKLAX0001Y28JUN//R/1234567890123///US

SSR DOCO AA ///-1CADE/BOBBI

### JPSC/30 PSC/32 Oct 10

Attachment: M

Page: 1 of 1



### AIRIMP 2.11.6.7/ ATA 105.175

SSR

Code Action Code Reply Automated

Format Free Text In

Request Free Text in

Reply/Cancel Reference

... DOCS Mandatory Not Permitted

Optional Optional Not Permitted Not Permitted 3.1.3.1

...

AIRIMP 3.13.1.4 

### / ATA 105.175

(e) Unsolicited Reply

When the SSR is entered directly into an Airline PNR owned by a Third Party System an

unsolicited reply may be sent to the PNR owner.

Mrs Patty Edwards contacts DL to supply Secure Flight Data. The DL PNR is owned by 1P. DL

informs 1P by means of an unsolicited reply message.

Non Automated Format:

HDQRM1P

.ATLRMDL

HDQ1P QWERTY

1EDWARDS/PATTYMRS

DL0012J20NOV ATLLHR HK1

SSR DOCS DL KK1/////10FEB80/F//EDWARDS/PATRICIA-1EDWARDS/PATTYMRS

Automated Format:

HDQRM1P

.ATLRMDL

HDQ1P QWERTY

1EDWARDS/PATTYMRS

DL0012J20NOV ATLLHR HK1

SSR DOCS DL KK1 ATLLHR0012J20NOV/////10FEB80/F//EDWARDS/PATRICIA

SSR DOCS DL /// -1EDWARDS/PATTYMRS

### JPSC/30 PSC/32 Oct 10

Attachment: N

Page: 1 of 1



### 2.11.6.7 SSR Matrix

SSR Code Action Code Reply Automated

Format Free Text in

Request Free Text in

Reply/

Cancel Reference



### WCLB Mandatory Mandatory Mandatory Optional Optional Bilateral

.....

WCBW Mandatory Mandatory Mandat ory Optional Optional

7.1.8.2 Special Service Requirement (SSR) Codes

..... Wheelchair — Non-spillable battery to be transported by a passenger

which may will require advance notification / and may require

preparation/(dis)assembly. Weight and dimensions may be specified.

Wheelchair and battery must be claimed and rechecked at each

interline transfer point (required only for use by/between U.S. carriers) WCBD

Wheelchair – Lithium ion battery to be transported by a passenger

which will require advance notific ation/preparation. Weight and

dimensions may be specified. W heelchair and battery must be claimed

and rechecked at each interline transfer point WCLB

..... ..... Wheelchair — Wet cell battery to be transported by a passenger. May

Will require advance notification / and may require

preparation/(dis)assembly. Weight and dimensions may be specified.

Wheelchair and battery must be claimed and rechecked at each

interline transfer point (required only for use by/between U.S. carriers) WCBW

7.2 PASSENGER RESERVATIONS CO DES AND ABBREVIAT IONS (Decoding)

..... WCBD Wheelchair — Dry cell Non-spillable battery to be transported by a

passenger which may will require advance notification / and may require

preparation/(dis)assembly. Weight and dimensions may be specified.

Wheelchair and battery must be claimed and rechecked at each interline

transfer point (required only for use by/between U.S. carriers)

WCLB Wheelchair – Lithium ion battery to be transported by a passenger which

will require advance notification/preparat ion. Weight and dimensions may

be specified. Wheelchair and battery must be claimed and rechecked at

each interline transfer point

..... WCBW Wheelchair — Wet cell battery to be transported by a passenger. May

Will require advance notification / and may require

preparation/(dis)assembly. Weight and dimensions may be specified.

Wheelchair and battery must be claimed and rechecked at each interline

transfer point (required only for use by/between U.S. carriers)

### JPSC/30 PSC/32 Oct 10

Attachment: O

Page: 1 of 1



### 2.11.6.7 SSR Matrix

SSR

Code Action Code Reply Automated

Format Free Text in

Request Free Text

in Reply/

Cancel Reference



### WCBD Mandatory Mandatory Mandatory Op tional Optional Bilateral

WCBW Mandatory Mandatory Mandatory Op tional Optional Bilateral

WCMP Mandatory Mandatory Mandatory Op tional Optional Bilateral

WCOB Mandatory Mandatory Mandatory Op tional Optional Bilateral

7.1.8.2 Special Service Requirement (SSR) Codes

Wheelchair — Dry cell battery to be transported by a passenger which may require

advance notification/preparation/(dis)a ssembly. Weight and dimensions may be

specified. Wheelchair and battery must be claimed and rechecked at each interline

transfer point (required only for use by/between U.S. carriers) (by bilateral

agreement) WCBD

Wheelchair — Wet cell battery to be transported by a passenger. May require

advance notification/preparation/(dis)a ssembly. Weight and dimensions may be

specified. Wheelchair and battery must be claimed and rechecked at each interline

transfer point (required only for use by/between U.S. carriers) (by bilateral

agreement) WCBW

Wheelchair — Manual power to be tr ansported by a passenger. Weight and

dimensions may be specified (required onl y for use by/between U.S. carriers) (by

bilateral agreement) WCMP

On-board Wheelchair — provided by airli ne (required only for use by/between U.S.

carriers) (by bilateral agreement) 48 hours notice recommended but not required WCOB



### .....

7.2 PASSENGER RESERVATION S CODES AND ABBREVIATIONS

(Decoding)

..... WCBD Wheelchair — Dry cell battery to be transported by a passenger which may require

advance notification/preparation/(dis)a ssembly. Weight and dimensions may be

specified. Wheelchair and battery must be claimed and rechecked at each interline

transfer point (required only for use by/between U.S. carriers) (by bilateral

agreement)

WCBW Wheelchair — Wet cell battery to be transported by a passenger. May require

advance notification/preparation/(dis)a ssembly. Weight and dimensions may be

specified. Wheelchair and battery must be claimed and rechecked at each interline

transfer point (required only for use by/between U.S. carriers) (by bilateral

agreement)

WCMP Wheelchair — Manual power to be transported by a passenger. Weight and

dimensions may be specified (required onl y for use by/between U.S. carriers) (by

bilateral agreement)

WCOB On-board Wheelchair — provided by airline (required only for use by/between U.S.

carriers) (by bilateral agreement) 48 hours notice recommended but not required

### JPSC/30 PSC/32 Oct 10

Attachment: P

Page: 1 of 4

Secretary Note : delete all existing text in AIRIMP 2.6 and replace as shown below.

2.6 NAME ELEMENT

Increasing Governmental requirements concer ning Passenger Data highlight the need for

accurate recording of Name Information. I deally, the recorded Name should match that in an

official Travel Document, e.g. passport. As this may not always be possible, the following

guidelines should be used.

2.6.1 General

2.6.1.1 Whenever possible, use given names (first and mi ddle), initials and/or title to supplement

a family name to ensure accuracy and differentiate identification, and for the usage of the same

name on the ticket as in the PNR. Place the given names (first and middle), initials and/or title,

after the family name and separate reference to each individual passenger by a single oblique,

e.g. indicate Jean Duval as 1DUVAL/J EAN, Mr. Edward Charles Jones as

1JONES/EDWARDCHARLESMR, Miss Duvalier as 1DUVALIER/MISS, E. Ford, B. Ford and C.

Ford as 3FORD/E/B/C, Mrs. B. Khoury as 1KHOURY/BMRS, and Ms. A nne Judith Blythe as

1BLYTHE/ANNEJUDITHMS.

2.6.2 Identical Family Names

2.6.2.1 When passengers travelling together as a fam ily unit have identical family names,

indicate the family name once and prefix it with the number of passengers concerned, e.g.

3DOWNEY.

Example 1 — Family unit with identical family name:

4GOMEZGONZALEZ/MCMRS/JA/MMMS/MMSTR

When two or more parties having an identical family name are booked in the same PNR, i.e.

Group Booking, but are not a family unit (not re lated), the individual parties may be booked as

individual Name Elements.

Example 2 — Two parties, non-related, with identical family name:

2SINGH/B/E 3SINGH/J/JMRS/JMSTR

2.6.2.2 If the Name Element requires more than one line of 69 characters, enter the names in as

many lines as required, prov ided that each line does not ex ceed 69 characters and that the

second and subsequent lines start with a numeric prefix followed by a name.

Example — Family unit with identical family names, exceeding 69 characters:

2GOMEZGONZALEZ/MARIA CONCEPCION/JOSE ALEJANDRO

2GOMEZGONZALEZ/MARIA MAGDALENA/MIGUELANGEL

### JPSC/30 PSC/32 Oct 10

Attachment: P

Page: 2

2.6.3 Number in Party

2.6.3.1 Always prefix each family/group name wi th the appropriate number of seats to be

reserved for that family/group name, e.g. 1JONES, 2SMITH, 25SITA/TOUR. The number in the

party preceding a name is an in tegral part of that name.

2.6.3.2 The total number of seats indicated in the Na me Element must not exceed three digits.

Numerics must not be entered in the Name Element except when used as a prefix to indicate

the number of seats to be reserved for each family/group name. When an identification number

for a group is used in the Name Element, it must be spelled out in letters, i.e.

25AMEX/FOUR/TWO/SIX. Special characters other than the oblique as shown in 2.6.6 “Name

Element” must not be used.

2.6.3.3 The total number of seats indicated in the Na me Element must agree with the number of

seats in the Segment Element except as out lined in 3.6 “Messages Changing Name and/or

Number of Passengers (Option 2)”.

2.6.4 Compound Names

2.6.4.1 When a hyphenated name is involved, delete the hyphen or replace it with a space, i.e.

indicate James Robert Bryce-Buchanan as 1B RYCEBUCHANAN/JAMESROBERTMR or as

1BRYCE BUCHANAN/JAMES ROBERT MR.

2.6.4.2 When a double name is involved, the spac e separating the names is optional, i.e.

indicate Jesus Raul Gomez Gonzalez as 1GOMEZGONZALEZ/JESUSRAULMR or as

1GOMEZ GONZALEZ/JESUS RAUL MR.

Note: If a receiving system suppresses spaces when receiving names, the system may return

the names to the requesting system with or without the spaces in any reply or advice message.

2.6.5 Single Letter Family Name

To accommodate systems that cannot process single letter family names, two suggested

procedures follow:

2.6.5.1 Double the single letter family name as the fa mily name. For exampl e, Miss Moan Y will

be represented as YY/MOANMISS, or

2.6.5.2 Combine the single letter fam ily name with all the given nam e(s) of that passenger as

the family name. For exampl e, Miss Moan Y will be represented as YMOAN/MISS and Miss

Tuyetmai Van A will be represented as ATUYETMA IVAN/MISS. Multiple Members of a single

letter family name are to be represented by in dividual name elements. For example, John and

Sally U would be represented as UJOHN/MR and USALLY/MRS.

### JPSC/30 PSC/32 Oct 10

Attachment: P

Page: 3

2.6.6 Duplicate Names

When names in a PNR are being created and are an exact match, whenever possible add

middle name(s) and/or different titles to ma ke them unique for messaging and differentiation

purposes.

2.6.7 No Family Name

In the event that the passenger does not have a family name use the given name(s) in the

family name field and add a title in the given name field e.g. indicate PRINCE as PRINCE/MR,

MARY JO as MARYJO/MRS

2.6.8 No Given Names

When given names (first and middle) are not indi cated, initials and/or title should be included

whenever possible.

In the event that the passenger does not have a given name use only the title in the given name

field e.g. indicate PRINCE as PRINCE/MR, JONES as JONES/MR

2.6.9 Name Suffix

To accommodate name suffixes (such as Junior, Senior, or III), add the suffix to the family

name. For example, Mr John Olsen Jr. will be represented as OLSENJR/JOHNMR, and Mr

William Looney III will be repr esented as LOONEYIII/WILLIAMMR. For a family where not

everyone shares the suffix of one of its Member s, the names are to be represented by individual

name elements. For example, Mr and Mrs John Olsen Jr. and son Robert, would be

represented as OLSENJR/JOHNMR and OLSEN/JUDYMRS/ROBERTMSTR

2.6.10 Traveling with Children and Infants

When booking accompanied children or infants, the number of seats in the Name Element shall

include the number of seats required for them. A child always requires a seat. Depending on

each Member's rules, a seat may or may not be required for an infant. Ages of infants assist

airport staff to allocate bassinets to the bes t advantage while ages of children help determine

fuel requirements. Use SSR INFT for an infant (see 3.16) and SSR CHLD for a child (see 3.17).

2.6.11 Extra Seat

Reservation Procedure for Extra Seat — when making reservations for passengers requiring

(an) extra seat(s) for personal comfort or for cabin baggage occupying a seat, adhere to the

following rules for the Name Elem ent and the Supplementary Element.

In the Name Element, prefix the family name with the total number of seats desired. Add an

oblique and the given (first) name or initial and/or title followed by an oblique and the

appropriate code, “CBBG” for cabin baggage and “EXST” for extra seat for personal comfort.

### JPSC/30 PSC/32 Oct 10

Attachment: P

Page: 4

In a Supplementary Element, indicate how many seats are extra seats and identify the

reason for which the extra seats are needed. Use SSR followed by the same code as in the

Name Element (“EXST” or “CBBG”), the airli ne designator of the airline addressed, the

Action Code, the number of extra seats, the name of the passenger for whom the extra seats

are needed and the relevant information concerning the reason for which the extra seats are

required.

Example 1 — Mr. Albert Dooley is travelling alone but needs an extra seat because he is

oversized. He pays for the extra seat:

Name Element ..................... 2DOOLEY/ALBERTMR/EXST

Supplementary Element....... SSR EXST UA NN1 JFKNRT0801Y31AUG-1DOOLEY/ALBERTMR.OVERSIZED



### Example 2 — Mr. John Lynch is travelling alone but needs one extra seat for his cello as

cabin baggage:

Name Element ..................... 2LYNCH/JOHNMR/CBBG

Supplementary Element........ SSR CBBG TW NN1 STLMCI0417F01SEP-1LYNCH/JOHNMR.CELLO



### 2.6.12 Groups

2.6.12.1 When for a party, the individual passenger names are not yet available, use the

party name prefixed by the applicable number of seats, e.g. 6SEAMEN.

2.6.12.2 “Group Name” means a unique name assigned by the booking office for the

purpose of establishing the identity of pass engers travelling together over one or more

segments.

2.6.12.3 Group names must be recorded as received, and must not be modified unless

changed by the booking office in control of the group.

2.6.13 Ticketed Passengers

When a passenger making a reservation has indicated that he is already ticketed for the

itinerary requested, the name entered in the PNR shall be the same as the one appearing on

the ticket.

2.6.14 Unaccompanied Minor

When making a reservation for an unaccompanied minor use Supplementary Service

Identifier SSR followed by “UMNR”. Include the child's age as UM– –. Additional information

concerning the contacts and any connecting flights in itinerary may be supplied, if available,

at the time of booking.

Example:

SSR UMNR BA NN2 JFKFCO0110Y31AUG.UM08/09

### JPSC/30 PSC/32 Oct 10

Attachment: Q

Page: 1 of 2



### 3.13.4 Request Passenger Security Information

A member may request Passenger Security Information from the original booking

office to comply with government requirements.

Example 1A – DL sends an Advice Message to 1P requesting Secured Flight Data.

HDQRM1P

.ATLRMDL

HDQ1P YZ7EK3

ATLDL 9YR8WK

1ERICKSON/JIMMR 1CORKING/STEPHENMR 1POUCET/ISABELLEMRS

DL0239J03MAY AMSATL HK3

SSR ADPI 1P KK1 DL0239 REQ SEC FLT PSGR DATA 72 HBD FOR ALL PSGRS



### Example 1B – As a result, 1P sends a message notifying DL of the data using data

elements of the SSR DOCS.

ATLRMDL

.HDQRM1P

HDQ1P YZ7EK3/ABC/57256802/AMS/1P/T/NL

1ERICKSON/JIMMR 1CORKING/STEPHENMR 1POUCET/ISABELLEMRS

DL0239J03MAY AMSATL HK3

SSRDOCSDLHK1AMSATL0239J03MAY/////11JUN82/M//ERICKSON/JIM/JOHN

SSRDOCSDL///-1ERICKSON/JIMMR

SSRDOCSDLHK1AMSATL0239J03MAY/////30JAN72/U//CORKING/STEPHEN/TERRENCE

SSRDOCSDL///-1CORKING/STEPHENMR

SSRDOCSDLHK1AMSATL0239J03MAY/////20AUG90/F//POUCET/ISABELLE/HELENE

SSRDOCSDL///-1POUCET/ISABELLEMRS

### JPSC/30 PSC/32 Oct 10

Attachment: Q

Page: 2



### Example 2A – AF sends an Advice Message to 1P, requesting full API data.

HDQRM1P

.MUCRM1A

HDQ1P YZ7EK3

MUC1A A5SW8F

1ERICKSON/JIMMR 1CORKING/STEPHENMR 1POUCET/ISABELLEMRS

AF0681J06MAY ATLCDG HK3

AF8224J07MAY CDGAMS HK3

SSR ADPI 1P KK1 AF0681 FULL API DATA REQ 48 HBD FOR ALL PSGRS



### Example 2B – As a result, 1P sends a message notifying AF of the data using

data elements of the SSR DOCS, DOCO, and/or DOCA as applicable.

MUCRM1A

.HDQRM1P

HDQ1P YZ7EK3/ABC/57256802/AMS/1P/T/NL

1ERICKSON/JIMMR 1CORKING/STEPHENMR 1POUCET/ISABELLEMRS

DL0239J03MAY AMSATL HK3/1040 1420

AF0681J06MAY ATLCDG HK3 1A

AF8224J07MAY CDGAMS HK3 1A

SSRDOCSAFHK1ATLCDG0681J06MAY/P/MKC/AB4585622/US/11JUN82/M//ERICKSON/JIM

SSRDOCSAF////JOHN-1ERICKSON/JIMMR

SSRDOCSAFHK1ATLCDG0681J06MAY/P/LON/23774758SX/GB/30JAN51/U//CORKING

SSRDOCSAF////STEPHEN/TERRENCE-1CORKING/STEPHENMR

SSRDOCSAFHK1ATLCDG0681J06MAY/P/NCE/FR83847483/FR/20AUG90/F//POUCET

SSRDOCSAF////ISABELLE/HELENE-1POUCET/ISABELLEMRS

2.11.6.7 SSR MATRIX

SSR Code Action

Code Reply Automated

Format Free Text

in Request Free Text in

Reply/Cancel Reference

....

ADPI Mandatory Not

Permitted Not

Permitted Mandatory Not

Applicable See 3.

13.4

....

7.1.8 Supplementary element Codes

.... 7.1.8.2....

.... Advise Passenger 

### Security Information .................................................................ADPI

7.2

.... ADPI .................................................................Advise Passenger 

### Security Information

### JPSC/30 PSC/32 Oct 10

Attachment: R

Page: 1 of 1

SSR Matrix

2.11.6.7 SSR Matrix



### SSR

Code Action Code Reply Automate

d Format Free Text

in Request Free Text

in

Reply/Ca

ncel Reference

ADTK Not permitted Not

permitted Not

permitted Mandatory

See 3.1.14 Not

permitted See 3.1.14

ADMD Not permitted Not

permitted Not

permitted Mandatory

See 3.1.xx Not

permitted See 3.1.xx

....

3.1.xx EMD number request (bilateral)

3.1.xx.1 Example of an airline request for EMD to the originator of the booking where

several services requiring EMD issuance have been booked.

MUCRM1A

.AMSRMKL 121314

MUC1A RLO456

1JACOBS/RICKMR

KL 1260 Y 08JUN NCEAMS HK1

KL 1273 Y 10JUN AMSNCE HK1

SSR BIKE KL KK1 NCEAMS1260Y08JUN

SSR ASVC KL KD1 NCEAMS1260Y08JUN.F/S57/BIKE/

SSR ASVC KL///BIKES

SSR BIKE KL KK1 AMSNCE1273Y10JUN

SSR ASVC KL KD1 AMSNCE1273Y10JUN.F/S57/BIKE/

SSR ASVC KL///BIKES

SSR VGML KL KK1 NCEAMS1260Y08JUN

SSR ASVC KL KD1 NCEAMS1260Y08JUN.F/S18/VGML/

SSR ASVC KL///VEGETARIAN MEAL

SSR ADMD 1A KK1 TO KL BY 10MAY 1400 OTHERWISE WILL BE CANCELLED

### JPSC/30 PSC/32 Oct 10

Attachment: S

Page: 1 of 1

2.11.6.7 SSR Matrix



### SSR

Code Action

Code Reply Automated

Format Free Text

in Request Free Text in

Reply/Cancel Reference

EPAY Mandatory Mandatory See 3.1.14 See 3.1.14 Optional See 3.1.14

ESAN Mandatory Mandatory Mandatory Mandatory Optional Bilateral

...

STCR Mandatory Mandatory Mandatory Not

permitted Optional

SVAN Mandatory Mandatory Mandatory Mandatory Optional Bilateral

...

7.1.8 Supplementary element Codes

.... 7.1.8.2....

... Passenger with Emotional Support/Psychiatric Assi stance Animal in Cabin (specify Details) .............

ESAN

... Passenger with Service Animal in Cabin (specify Details) ............. SVAN

...

7.2 Passenger Reservations Co des and Abbreviations (Decoding)

... ERQ...............Endorsement Request

ESAN............. Passenger with Emotional Support/Ps ychiatric Assistance Animal in Cabin

(specify details)

... SUR...............Surface (ship, rail, bus, etc.)

SVAN.............Passenger with Service Anim al in Cabin (specify details)

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 1 of 7



### AIRIMP only

3.1.18.4 Electronic Tickets

Note: SSR “ TKNE ” shall be used only for notification that an electronic ticket has been issued.

(a) In the interline situation, those carriers in the itinerary including the validating carrier must be

notified that a ticket has been issued electronically. This notification must be sent at time of

Electronic Ticket issuance or reissue, and will take the form of an SSR advisory:

(b) the SSR message shall be sent to all carriers in the itinerary including the validating carrier as

bilaterally agreed;

(c) the SSR advisory is sent via teletype by the system issuing the electronic ticket;

(d) an SSR element must be generated for each electronically ticketed passenger for each

segment ticketed. If more than one passenger is ticketed from the same PNR, in the same

transaction, multiple passenger SSRs will be contained in the same message;

(e) the SSR advisory is sent immediately upon successful completion of the electronic ticket

issuance;

(f) the SSR code is TKNE;

(g) the SSR status code and number is HK1;

(h) an SSR TKNE is not sent on OPEN segments;

(i) an SSR TKNE is transmitted for Passive Segment(s);

• Segment Status Codes where a Passive Segment Notification Agreement exists (8.10)

PK — Confirmed, ticket number sent with the initial transmission of the passive.

PL — Waitlist, ticket number sent with the initial transmission of the passive.

PU — Ticket Number sent after the initial transmission of PK/PL.

• Segment Status Codes where no Passive Segment Notification Agreement exists

(see 8.10):

HK — Confirmed;

HL — Waitlist;

HN — Requested;

(j) an SSR TKNE is transmitted for Informational Segment(s)

• Segment Status Codes

HK — Confirmed;

HL — Waitlist;

HN — Requested;

.....

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 2



### 3.1.17 Advice of Electronic Tic ket Number for Passive Segments

3.1.17.1 Where a Passive Segment Notification Agreement Exists (See 8.10)

Ticket numbers/TCNs will be transmitted for Passive se gments. If ticket numbers/TCNs are sent with

the initial transmission of PK/PL segment(s), the Action Code of the segment(s) will be PK or PL. If

ticket numbers/TCNs are sent after the initial tr ansmission of PK/PL segments, the Action Code for

these same segment(s) will be PU. If the Record Locator of the receiving system or the record locator

of the booking source is known, it should be included as an OSI or SSR item, not in the Secondary

Record Locator Line

(See 2.5.2)

Example 11 — Message illustrating ticket number notification between members where the original

booking originates in another system than the system sending the message (initial Passive Segment

Notification message was previously sent). The Record Locator of the Booking Source is included as

an OSI item

Original Booking made by 1G

1NAME/AMR RecLoc QWERTY

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 KL 644 J 21JUN JFKAMS HK1 2205 1135

3. AZ1224 Y 23JUN AMSLIN HK1 1015 1130

Booking as received by KL

1NAME/AMR RecLoc XYZXYZ

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 KL 644 J 21JUN JFKAMS HK1 2205 1135

OWNER - QWERTY/XF6/5725680S/AMS/1G/T/NL

KL adds AZ1224 as a passive segment

1NAME/AMR RecLoc XYZXYZ

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 KL 644 J 21JUN JFKAMS HK1 2205 1135

3 AZ1224 Y 23JUN AMSLIN PK1 1015 1130

OWNER - QWERTY/XF6/5725680S/AMS/1G/T/NL

KL issues a ticket for all segments, including the AZ segment which was added as a passive segment

by KL. The Record Locator of the Booking Source (1G) is included as an OSI item.

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 3

Message sent by KL to AZ

ROMRMAZ

.MUCRM1A

Record Locator Sender .......... MUC1A XYZXYZ

Name Element ................ 1NAME/AMR

Segment Element .............. AZ1224Y23JUN AMSLIN PU1

Supplementary Element ......... SSRTKNEAZHK1 AMSLIN1224Y23JUN.0742400180117C3

Supplementary Element ......... OSI AZ RLOC SWI1G QWERTY



### 3.1.17.2 Where no Passive Segment Noti fication Agreement exists (See 8.10)

The message identifier PTN is used to allow the receiving system to recognize an E-ticket has been

issued for one or more passive segments in the message. If the Record Locator of the receiving

system or the record locator of the booking source is known, it should be included as an OSI or SSR

item, not in the Secondary Record Locator Line

(See 2.5.2)

Example 4 — Message illustrating ticket number notification between members where the original

booking originates in another system than the system sending the message. The Record Locator of

the Booking Source is included as an OSI item:

Original Booking made by 1G

1NAME/AMR RecLoc QWERTY

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 KL 644 J 21JUN JFKAMS HK1 2205 1135

3. AZ1224 Y 23JUN AMSLIN HK1 1015 1130

Booking as received by KL

1NAME/AMR RecLoc XYZXYZ

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 KL 644 J 21JUN JFKAMS HK1 2205 1135

OWNER - QWERTY/XF6/5725680S/AMS/1G/T/NL

KL adds AZ1224 as a passive segment

1NAME/AMR RecLoc XYZXYZ

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 KL 644 J 21JUN JFKAMS HK1 2205 1135

3 AZ1224 Y 23JUN AMSLIN PK1 1015 1130

OWNER - QWERTY/XF6/5725680S/AMS/1G/T/NL

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 4

KL issues a ticket for all segments, including the AZ segment which was added as a passive segment

by KL.

Message sent by KL to AZ

ROMRMAZ

.MUCRM1A



### Message Identifier

......... PTN

Record Locator Sender .......... MUC1A XYZXYZ

Name Element ................ 1NAME/AMR

Segment Element .............. AZ1224Y23JUN AMSLIN HK1

Supplementary Element ......... SSRTKNEAZHK1 AMSLIN1224Y23JUN.0742400180117C3

Supplementary Element ......... OSI AZ RLOC SWI1G QWERTY

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 5



### 3.1.18 Advice of Electr onic Ticket Number for Informational Segments

(Renumber current 3.1.18, 3.1.19, 3.1.20)

Informational segments are segments of a member included in a message addressed to another

member or system provider where the member of these segments does not share the same Predesignated Point as to where the message is sent.

These kinds of segments are included in the message because they are either an arrival and/or

continuation segment to segment of the addressee or the receiving system has a Full Itinerary

agreement with the sender.

When the a Member is using these informational segment for ticket issuance, a Ticket Notification

Message must be sent to the members of these segments.

If the Record Locator of the receiving system of the Ticket Notification Message or the record locator

of the booking source is known, it should be included as an OSI or SSR item, not in the Secondary

Record Locator Line

(See 2.5.2)

Example 1 — Message illustrating ticket number notification between members where the original

booking originates in another system than the system sending the message. The Record Locator of

the Booking Source is included as an OSI item:

Original Booking made by 1G

1SUNDSFJORD/YNGVARMR RecLoc QWERTY

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 NW 593 Y 11JUN JFKMSP HK1 0815 1026

3 NW1549 Y 20JUN MSPJFK HK1 1255 1654

4 KL 644 J 21JUN JFKAMS HK1 2205 1135

Booking as received by KL

1SUNDSFJORD/YNGVARMR RecLoc XYZXYZ

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 NW 593 Y 11JUN JFKMSP HK1 0815 1026

3 NW1549 Y 20JUN MSPJFK HK1 1255 1654

4 KL 644 J 21JUN JFKAMS HK1 2205 1135

OWNER - QWERTY/XF6/5725680S/AMS/1G/T/NL

KL issues a ticket for all segments, including the NW segments which were sent by 1G to KL as informational segments (Arrival and Onward)

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 6

Message sent by KL to NW:

HDQRMNW

.MUCRM1A

Record Locator Sender .......... MUC1A XYZXYZ

Name Element ................ 1SUNDSFJORD/YNGVARMR

Segment Element ............ KL641J10JUN AMSJFK HK1/1330 1525

Segment Element .............. NW0593Y11JUN JFKMSP HK1

Segment Element .............. NW1549Y20JUN MSPJFK HK1

Segment Element ............ KL644J21JUN JFKAMS HK1/2205 1135

Supplementary Element ......... SSRTKNENWHK1 JFKMSP0593Y11JUN.0742400180117C2

Supplementary Element ......... SSRTKNENWHK1 MSPJFK1549Y20JUN.0742400180117C3

Supplementary Element ......... OSI NW RLOC SWI1G QWERTY

Example 2 — Message illustrating ticket number notification between members where the original

booking originates in another system than the system sending the message. The Record Locator of

the Booking Source is included as an OSI item:

Original Booking made by 1G

1SUNDSFJORD/YNGVARMR RecLoc QWERTY

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 NW 593 Y 11JUN JFKMSP HK1 0815 1026

3 DL1077 Y 15JUN MSPATL HL1 0730 1100

4 DL1721 Y 17JUN ATLMSP HL1 1050 1235

5 NW1549 Y 20JUN MSPJFK HK1 1255 1654

6 KL 644 J 21JUN JFKAMS HK1 2205 1135

Booking as received by KL

1SUNDSFJORD/YNGVARMR XYZXYZ

1 KL 641 J 10JUN AMSJFK HK1 1330 1525

2 NW 593 Y 11JUN JFKMSP HK1 0815 1026

3 DL1077 Y 15JUN MSPATL HL1 0730 1100

4 DL1721 Y 17JUN ATLMSP HL1 1050 1235

5 NW1549 Y 20JUN MSPJFK HK1 1255 1654

6 KL 644 J 21JUN JFKAMS HK1 2205 1135

OWNER - QWERTY/XF6/5725680S/AMS/1G/T/NL

### JPSC/30 PSC/32 Oct 10

Attachment: T

Page: 7

KL issues the ticket for all segments, including the NW and DL segments which were sent by 1G to

KL as informational segments (Full Itinerary)

Message sent by KL to NW:

HDQRMNW

.MUCRM1A

Record Locator Sender ......... MUC1A XYZXYZ

Name Element ............... 1SUNDSFJORD/YNGVARMR

Segment Element ........... KL0641J10JUN AMSJFK HK1/1330 1525

Segment Element ............. NW0593Y11JUN JFKMSP HK1

Segment Element ........... DL1721Y17JUN ATLMSP HL1/1050 1235

Segment Element ............. NW1549Y20JUN MSPJFK HK1

Segment Element ........... KL0644J21JUN JFKAMS HK1/2205 1135

Supplementary Element ........ SSRTKNENWHK1 JFKMSP0593Y11JUN.0742400180117C2/117-118

Supplementary Element ........ SSRTKNENWHK1 MSPJFK1549Y20JUN.0742400180118C1/117-118

Supplementary Element ........ OSI NW RLOC SWI1G QWERTY

Message sent by KL to DL:

HDQRMDL

.MUCRM1A

Record Locator Sender ......... MUC1A XYZXYZ

Name Element ............... 1SUNDSFJORD/YNGVARMR

Segment Element ............. NW0593Y11JUN JFKMSP HK1/0815 1026

Segment Element ............. DL1077Y15JUN MSPATL HL1

Segment Element ............. DL1721Y17JUN ATLMSP HL1

Supplementary Element ........ SSRTKNEDLHK1 MSPATL1077Y15JUN.0742400180117C3/117-118

Supplementary Element ........ SSRTKNEDLHK1 ATLMPS1721Y17JUN.0742400180117C4/117-118

Supplementary Element ........ OSI DL RLOC SWI1G QWERTY

## M E M O R A N D U M

PSC/RESO/14 9 bis

To: All Members, Passenger Services Conference

- Accredited

Representatives

Copy: IATA Strategic Partners

From: Head, Passenger Interline Standards

Date: 1 4 August 2013

Subject: “PASSENGER WEEK 20 10 ”

BOOK O F FINALLY ADOPTED RESOLUTIONS & RPs

30 th 

### Joint ATA/IATA Passenger Services Conference (JPSC)

3 2 nd 

### IATA Passenger Services Conference (PSC)

Geneva, 21 October 20 10

Attached are the resolutions & recommended practices (RPs) which were adopted at the above

mentioned Conference. The Minutes of the Conference are issued separately under Memorandum

PSC/MINS/034 dated 15 April 2011.

The resolutions and RPs were originally circulated under cover of memorandum PSC/RESO/149

dated 15 April 2011 . Subsequently they were filed with Governments, where required, except for

the United States Department of Transportation (D o T)

. The intended effective date was 1 June

201 1

.

The delay in filing these resolutions and RPs with the DoT was in recognition of new procedures to

create a “self

- assessment” environment for PSC agreements. These new procedures were finally

revealed at the PSC meeting in October 2012 (refer to agenda item P5 in the Minutes circulated

under Memorandum PSC/MINS/042 dated 28 January 2013).

The DoT Ord er 2012

- 4

- 18 provides for a three

- tiered system for filing and implementation of PSC

agreements. This memorandum will be filed with the DoT using procedures for “Tier 1”. The

changes for RP 1708a adopted at the above

- mention ed conference will be filed sepa rately using

the procedures for “Tier 2”.

Mike Muller

## OUTLINE OF CONTENTS

RESOLUTIONS & RECOMMENDED PRACTICES

ADOPTED AT:

3 2 nd 

### PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE:

1 JUNE 20 1 1

Resolution/RP

**[Previously exempted]** 

### Title

PSC(3 2 )003

**[OST**

**- 2012** 

**- 0058]**  STANDARD RECISSION RESOLUTION

PSC(3 2 )70 1 INADMISSIBLE PASSENGERS AND DEPORTEES

(amending)

PSC(3 2 )720a

**[OST**

**- 2012** 

**- 0058]**  PASSENGER TICKET AND BAGGAGE CHECK

ISSUANCE AND HONORING PROCEDURES

(amending)

PSC(3 2 )722

**[OST**

**- 2012** 

**- 0058]**  TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC(32)722a

**[OST**

**- 01** 

**- 9575]**  OFF PREMISE TRANSITIONAL AUTOMATED TICKET

(OPTAT)

(amending)

PSC(32) 722c

**[OST**

**- 2012** 

**- 0058]**  AUTOMATED TICKET/BOARDING PASS

– VERSION 2

(ATB2)

(amending)

PSC (3 2 )722f

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC TICKET

– AIRLINE

(amending)

PSC(3 2 )722g

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC TICKET

– NEUTRAL

(amending)

PSC(3 2 )722h

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC TICKET

– GROUND HANDLING

( amending)

### PSC(32)725b

**[OST**

**- 2012** 

**- 0058]**  MISCELLA NEOUS CHARGES ORDER (MCO)

– ISSUANCE AND HONOURING PROCEDURES

(AGENTS)

(amending)

PSC(32)725c AUTOMATED MISCELLANEOUS CHARGES ORDER

(MCO) CARRIER (COUPON

- BY

- COUPON)

(amending)

PSC(32)725d

**[OST**

**- 2012** 

**- 0058]**  AUTOMATED MISCELLANEOUS CHARGES ORDER

(MCO) NEUTRAL (COUPON

- BY

- COUPON)

(amending)

PSC(32)725f

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC MISCELLANEOUS DOCUMENT

–

AIRLINE

(amending)

PSC(32)725g

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC MISCELLANEOUS DOCUMENT

– NEUTRAL

(amending)

PSC(32)725h

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC M ISCELLANEOUS DOCUMENT

– GROUND HANDLING

(amending)

PSC(32)726

**[OST**

**- 01** 

**- 9575]**  MULTIPLE PURPOSE DOCUMENT (MPD)

(amending)

PSC(32)726e

**[OST**

**- 01** 

**- 9575]**  MULTIPLE PURPOSE DOCUMENT (MPD)

– NEUTRAL,

CARBONISED, MANUAL

(amending)

PSC(3 2 )728

**[OST**

**- 2012** 

**- 0058]**  CODE DESIGNATORS FOR PASSENGER TICKET

AND BAGGAGE CHECK

(amending)

PSC(32)731a AUTOMATED PREPAID TICKET ADVICE (PTA)

– CARRIER (COUPON

- BY

- COUPON)

(amending)

PSC(3 2 )735

**[OST**

**- 2012** 

**- 0058]**  PERIOD OF VALIDITY

(amending)

PSC(3 2 )735d

**[OST**

**- 2012** 

**- 0058]**  IN VOLUNTARY CHANGE OF CARRIER, ROUTING,

CLASS OR TYPE OF FARE

(amending)

PSC(3 2 )740

**[OST**

**- 01** 

**- 9575]**  FORM OF INTERLINE BAGGAGE TAG

(amending)

### PSC(32)742e AUTOMATED EXCESS BAGGAGE TICKET

– CARRIER

(COUPON

- BY

- COUPON)

(amending)

PSC(3 2 )74 5 DANGEROUS GOO DS IN PASSENGER BAGGAGE

(amending)

PSC(3 2 )76 3

**[OST**

**- 2012** 

**- 0058]**  LOCATION IDENTIFIERS

(amending)

PSC(3 2 ) 780

**[OST**

**- 2012** 

**- 0058]**  FORM OF INTERLINE TRAFFIC AGREEMENT

– PASSENGER

(amending)

PSC(3 2 ) 79 2

**[OST**

**- 2012** 

**- 0058]**  BAR CODED BOARDING PASS (BCBP)

– VERS ION 3

4

(amending )

PSC(32)1008

**[OST**

**- 0** 

**2**

**- 13807**  **]** GLOSSARY OF COMMONLY USED AIR PASSENGER

TERMS

(amending)

PSC(3 2 )1701f SELF SERVICE BAGGAGE PROCESS CHECK

- IN

(amending)

PSC(3 2 )170 7

**[OST**

**- 01** 

**- 9575]**  STANDARD SYMBOLS FOR DESCRIPTION OF

STANDARD MESSAGE FORMATS

(amending )

PSC(3 2 )1707b

**[OST**

**- 01** 

**- 9575]**  DATA ELEMENT DIRECTORY FOR DCS PASSENGER

MESSAGES

(amending)

PSC(3 2 )1708

**[OST**

**- 0** 

**2**

**- 13807**  **]** PASSENGER NAME LIST (PNL) AND ADDITIONS AND

DELETIONS LIST (ADL)

(amending)

PSC(3 2 )171 5

**[OST**

**- 0** 

**2**

**- 11798**  **]** PASS ENGER SERVICE MESSAGE ( PSM )

(amending)

PSC(3 2 )1719 d TICKETLESS PRODUCT LIST (TPL)

(amending)

PSC(3 2 )1720a

**[OST**

**- 2012** 

**- 0058]**  STANDARD THIRTEEN

- DIGIT NUMBERING SYSTEM

FOR TRAFFIC DOCUMENTS

( amending )

PSC(32)1721

**[OST**

**- 2012** 

**- 0058]**  NETTING FOR EXCHANGE /REISSUE

TRANSACTIONS

(amending)

### PSC(3 2 )1745

**[OST**

**- 0** 

**2**

**- 13807**  **]** BAGGAGE INFORMATION MESSAGES

(amending)

PSC(3 2 )1773 b STANDARD INFLIGHT CATERING AGREEMENT

( **new** )

PSC(3 2 )178 8

**[OST**

**- 2012** 

**- 0058]**  TICKETING AND BAGGAGE REGULATIONS FOR

FREE AND REDUCED RATE TRANSPORTATION

(amending)

PSC(3 2 )1 800

**[OST**

**- 2012** 

**- 0058]**  AUTOMATED BAGGAGE HANDLING BASED ON THE

IATA LICENCE PLATE CONCEPT

(amending)

## SUMMARY OF CHANGES

RESOLUTIONS/RECOMMENDED PRACTICES FINALLY ADOPTED AT:

32 nd 

### PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE:

1 ST 

### JUNE 20 11

Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 003

STANDARD

RECISSION

RESOLUTION Resolution rescinds a

previously adopted

Resolution

. Rescinds Resolution 7 2 6 b ( M ultiple

Purpose Document (MPD)

– Neutral

Carbonized Automated which is no

longer supplied to travel agents.

RESOLUTION 70 1

INADMISSIBLE

PASSENGERS AND

DEPORTES Provides standard

procedures to facilitate

repatriation and ticketing for

inadmissible passenge rs and

deportees. Minor editorial enhancement to

improve the understanding that an

endorsement when requested for a

ticket shall not be denied.

RESOLUTION 720a

PASSENGER TICKET

AND BAGGAGE

CHECK

– ISSUANCE

AND HONOURING

PROCEDURES Provides governing rule s on

how to issue a ticket, and

applicable conditions for the

honoring and re

- issuance of

tickets. Clarification of what to enter in the ‘Not

Valid After’ box in an involuntary

reroute scenario.

RESOLUTION 722

TRANSITIONAL

AUTOMATED TICKET

(TAT) Provides governing rules on

how to produce an

“automated” ticket issued by

airlines. It also provides the

technical specifications and

applicable conditions for the

honoring of such tickets. Clarification of what to enter in the ‘Not

Valid After’ box in an involu ntary

reroute scenario. Ticketing rules are

added for when a carrier ‘round trip

minimum’ is collected.

References to the ‘Fare Calculation

Pricing and Reporting Indicator’ are

deleted and replaced with the ‘Fare

Calculation Mode Indicator’ with only

one option that defines three values

are retained. Multiple options for carrier

and/or system provider usage which

are not defined are deleted.

RESOLUTION 722a



### OFF PREMISE

TRANSITIONAL

AUTOMATED

TICKET (OPTAT) Provides technical

specifications and print line

specifications for the

issuance of paper

‘automated’ tickets issued by

airlines

. References to the ‘Fare Calculation

Pricing and Reporting Indicator’ are

deleted and replaced with the ‘Fare

Calculation Mode Indicator’ with only

one option that defines thr ee values

are retained. Multiple options for carrier

and/or system provider usage which

are not defined are deleted.

RESOLUTION 722c



### AUTOMATED

TICKET/BOARDING

PASS

– VERSION 2

(ATB2) Provides governing rules on

how to produce an

“automated” ticket issued by

airlines on magnetic stripe

encoded ticket stock. It also

provides the technical

specifications and applicable

conditions for the honoring of

such tickets. Clarification of what to enter in the ‘Not

Valid After’ box in an involuntary

reroute scenario.

References to the ‘Fare Calculation

Pricing and Reporting Indicator’ are

deleted and replaced with the ‘Fare

Calculation Mode Indicator’ with only

one option that defines three values

are retained. Multiple options for carrier

and/or system provider usag e which

are not defined are deleted.

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 722f

ELECTRONIC

TICKET

– AIRLINE Provides governing rules and

technical specifications on

how to produce an Electronic

Ticket (ET) issued by airlines.

This allows ticketing to be

performed without the

issua nce of paper tickets.

Also included are the

applicable conditions for the

issuance and honoring of

such tickets. Clarifications on how to display credit

card number data when used as a

‘Form of ID’ (FOID) are added to

comply with Payment Card Industry

Data Security Standards.

Various data elements are added and

amended.

Various amendments to the data

elements matrix.

RESOLUTION 722g

ELECTRONIC

TICKET

–

NEUTRAL Provides governing rules and

technical specifications on

how to produce an Electronic

Ticket ( ET) issued by travel

agents. This allows ticketing

to be performed without the

issuance of paper tickets.

Also included are the

applicable conditions for the

issuance and honoring of

such tickets

. Clarifications on how to display credit

card number data wh en used as a

‘Form of ID’ (FOID) are added to

comply with Payment Card Industry

Data Security Standards.

Various amendments to the data

elements matrix.

RESOLUTION 722h

ELECTRONIC

TICKET

– GROUND

HANDLING Provides governing rules and

technical specifica tions to be

followed for the third party

ground

- handling of electronic

tickets (E T s). This allows

airlines to have their

electronic tickets handled by

third party ground handlers. Clarifications on how to display credit

card number data when used as a

‘For m of ID’ (FOID) are added to

comply with Payment Card Industry

Data Security Standards.

Various amendments to the data

elements matrix.

RESOLUTION 725b

MISCELLANEOUS

CHARGES ORDER

(MCO)

– ISSUANCE

AND HONOURING

PROCEDURES

(AGENTS) Provides governing rul es on

how to issue a Miscellaneous

Charges Order (MCO) by

agents, and applicable

conditions for the honoring

and re

- issuance of these

documents

. Clarifies that in countries/areas where

an IATA Billing and Settlement Plan

(BSP) is established, the provision s of

this resolution only applies to the

issuance of automated MCOs issued

on blank card.

RESOLUTION 725c

AUTOMATED

MISCELLANEOUS

CHARGES ORDER

(MCO)

– CARRIER

(COUPON

- BY

COUPON) Provides technical

specifications and print line

specifications for the

iss uance of Miscellaneous

Charges Order ‘automated’

issued by airlines References to the ‘Fare Calculation

Pricing and Reporting Indicator’ are

deleted and replaced with the ‘Fare

Calculation Mode Indicator’

RESOLUTION 725d

AUTOMATED

MISCELLANEOUS

CHARGES O RDER

(MCO)

– CARRIER

(COUPON

- BY

COUPON) Provides technical

specifications and print line

specifications for the

issuance of Miscellaneous

Charges Order ‘automated’

issued by agents References to the ‘Fare Calculation

Pricing and Reporting Indicator’ are

de leted and replaced with the ‘Fare

Calculation Mode Indicator’

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 725f

ELECTRONIC

MISCELLANEOUS

DOCUMENT

–

AIRLINE Provides governing rules for

the issuance and use of

Electronic Miscellaneous

Documents (EMD) by airlines.

The EMD is an electroni c

method to document the sale

and usage of charges

associated to various usage,

e.g. excess baggage

charges. Procedures are added to make it clear

that surface segments shall not be

contained in an EMD nor shall an EMD

be associated to surface segments of

an electronic ticket.

Definitions of Marketing and Operating

Carrier are amended.

Clarifications on how to display credit

card number data when used as a

‘Form of ID’ (FOID) are added to

comply with Payment Card Industry

Data Security Standards

Various amendments to clarify the

control of an EMD coupon and its

relationship with an ET coupon.

Various editorial amendments and

amendments to the data elements

matrix.

RESOLUTION 725g

ELECTRONIC

MISCELLANEOUS

DOCUMENT

– NEUTRAL Provides governing rules for

the issuance and use of

Electronic Miscellaneous

Documents (EMD) by agents. Procedures are added to make it clear

that surface segments shall not be

contained in an EMD nor shall an EMD

be associated to surface segments of

an electronic ticket.

Definitio ns of Marketing and Operating

Carrier are amended. Clarifications are

added that allows an issuing agency to

exchange or refund EMDs irrespective

of the system provider they use to

generate the request.

Clarifications on how to display credit

card number data when used as a

‘Form of ID’ (FOID) are added to

comply with Payment Card Industry

Data Security Standards

Various amendments to clarify the

control of an EMD coupon and its

relationship with an ET coupon.

Various editorial amendments and

amendments to the data elements

matrix.

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 725h

ELECTRONIC

MISCELLANEOUS

DOCUMENT

– GROUND HANDLING Provides governing rules and

technical specifications to be

followed for the third party

ground

- handling of electronic

miscellaneous documents

(EMDs). This al lows airlines

to have their EMDs handled

by third party ground

handlers. Definitions of Marketing and Operating

Carrier are amended.

Clarifications on how to display credit

card number data when used as a

‘Form of ID’ (FOID) are added to

comply with Payme nt Card Industry

Data Security Standards

Various editorial amendments and

amendments to the data elements

matrix.

RESOLUTION 726

MULTIPLE PURPOSE

DOCUMENT (MPD) Provides details of the

different types of Multiple

Purpose Documents (MPDs)

that can be issu ed in its

various formats and

associated legal notice

. Reference to the Automated Neutral

Carbonized MPD is deleted.

RESOLUTION 726 e

MULTIPLE PURPOSE

DOCUMENT (MPD)

– NEUTRAL,

CARBONISED,

MANUAL Provides governing rules on

how to issue a Multiple

Purpose Document (MPD) by

agents. Clarification is added that the

provisions of this resolution only apply

to the issuance of this document in a

virtual format as the physical paper

documents have been withdrawn.

RESOLUTION 728

CODE

DESIGNATORS FOR

PASSENGER TI CKET

AND BAGGAGE

CHECK Provides various coding

structures in order to identify

the type of fare and other

conditions of travel for tickets

and other documents. New provisions are added for the

issuance of ZED/MIBA tickets which

shall only be electronic e ffective 01

April 2012.

References to Braathens ASA Bracard

are deleted.

Various editorial amendments to bank

card nomenclature.

Reference added to clarify that the

provisions for credit cards as payment

in this resolution also apply to payment

cards.

RESOLUTION 731a

AUTOMATED

PREPAID TICKET

ADVICE (PTA)

– CARRIER (COUPON

BY COUPON) Provides technical and print

specifications for the

issuance of an automated

Prepaid Ticket Advice (PTA) References to the ‘Fare Calculation

Pricing and Reporting Indicator ’ are

deleted and replaced with the ‘Fare

Calculation Mode Indicator’.

RESOLUTION 735

PERIOD OF

VALIDITY Provides governing rules to

establish the period of validity

of a ticket. A provision is added to clarify that

expired validity tickets are not eligi ble

for exchange or reissues.

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 735d

INVOLUNTARY

CHANGE OF

CARRIER, ROUTING,

CLASS OR TYPE OF

FARE Provides governing rules for

the involuntary rerouting of

passengers due to flight

disruptions. A revised definition of ‘Ticket Handler’

is added

.

Procedures are added clarifying what

to do in a reissue situation when there

are multiple fare basis codes.

RESOLUTION 740

FORM OF INTERLINE

BAGGAGE TAG Provides information,

standards and specifications

for industry baggage

tags/labels. Editorial am endment to resolve

discrepancies with ATA Resolution

30.35.

RESOLUTION 742e

AUTOMATED

EXCESS BAGGAGE

TICKET

– CARRIER

(COUPON

- BY

COUPON) Provides technical and print

specifications for the

issuance of an automated

Excess Baggage ticket by

carrier. Refer ences to the ‘Fare Calculation

Pricing and Reporting Indicator’ are

deleted and replaced with the ‘Fare

Calculation Mode Indicator’.

RESOLUTION 745

DANGEROUS

GOODS IN

PASSENGER

BAGGAGE Provides rules describing

what articles cannot be

carried in passeng er’s

checked bags or in the carry

on bags. 

### Added provision on the necessity to

show specific information regarding

dangerous goods on airline

websites for ticket purchase, check

in and airport check

- in

RESOLUTION 763

LOCATION

IDENTIFIERS Provides rules f or the

assignment of unique three

letter codes to identify

specific locations and

metropolitan areas Amended polling procedures regarding

metropolitan area codes

RESOLUTION 780

FORM OF INTERLINE

TRAFFIC

AGREEMENT

–

PASSENGER Provides the standard text fo r

multi

- lateral interline traffic

agreements. A new provision is added to allow

carriers to opt out of accepting interline

partners’ paper miscellaneous

documents

.

A clarification is added on how to

process baggage claims.

RESOLUTION 792

BAR CODED

BOARDI NG PASS

(BCBP)

– VERSION 3

4 Provides the governing rules

and technical specifications

for the issuance of a Bar

Coded Boarding Pass

(BCBP)

. Provisions for the application of Near

Field Communication (NFC) are

added.

New data elements to identify the

lice nse plate are added together with a

clarification of the formatting of the

baggage tag number.

RP1008

GLOSSARY OF

COMMONLY USED

AIR PASSENGER

TERMS Provides an extensive

glossary of commonly used

terms in air passenger

transportation

. A reference to a com prehensive

glossary tool available on the IATA

website is added.

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RP1701f

SELF SERVICE

BAGGAGE

PROCESS CHECK

- IN One of the “passenger

experience standards” that

provides guidelines for self

service baggage processing

at check

- in Various editorial updates t o clarify

procedures

RP 170 7

STANDARD

SYMBOLS FOR

DESCRIPTION OF

STANDARD

MESSAGE FORMATS Provides the specifications

and descriptions for standard

messages and symbols used

in messages Various editorial updates to clarify

procedures

RP 1707b

DATA ELEME NT

DIRECTORY FOR

DCS PASSENGER

MESSAGES Provides specifications and

rules governing the use of

DCS Passenger Messages.

These messages are used to

provide various pieces of

information that support the

“seamless” interline

transportation of passengers. Var ious editorial updates to clarify

procedures

RP 1708

PASSENGER NAME

LIST (PNL) AND

ADDITIONS AND

DELETIONS LIST

(ADL) Provides the definitions,

formats and procedures for

the creation, transmission

and interpretation of

Passenger Name Lists

Messages and

Additions/Deletion Lists

Messages associated with

the passenger data produced

by an airline reservations

system. Various editorial updates to clarify

procedures

RP 171 5

PASSENGER

SERVICE MESSAGE

(PSM) Provides guidance on how to

inform downline stat ions of

disembarking and transiting

passengers who require

assistance or special

handling Various editorial updates to clarify

procedures

RP 1719 d

TICKETLESS

PRODUCT LIST (TPL) Provides guidelines to

facilitate a standard process

between an operating car rier

and its ground handling

company for ticketless

products Various editorial updates to clarify

procedures

RP 1720a

STANDARD

THIRTEEN

- DIGIT

NUMBERING

SYSTEM FOR

TRAFFIC

DOCUMENTS Provides guidelines regarding

the numbering systems for

airline and travel agent traffic

documents. Updates to provide IATA with several

new form codes to satisfy the rapid

increase in use of electronic tickets

and miscellaneous documents

### Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RP1721

NETTING FOR

EXCHANGE/

REISSUE

TRANSACTIONS Provides guidelines for the re

calcul ation of fares, taxes,

fees and charges in

exchange and reissue

transactions. Clarifies which currency to use when

applying an exchange value towards a

fare and taxes, fees and charges.

RP 1745

BAGGAGE

INFORMATION

MESSAGES Provides the definitions,

forma ts and specifications for

all of the messages used in

the baggage handling

process. Various editorial updates to clarify

procedures

RP1773b

STANDARD

INFLIGHT CATERING

AGREEMENT Provides guidance regarding

standard inflight catering

agreements. Establishm ent of guidelines to facilitate

documentation of inflight catering

agreements

RP 1788

TICKETING AND

BAGGAGE

ALLOWANCES FOR

FREE AND

REDUCED RATE

TRANSPORTATION Provides guidelines for

issuance of tickets based on

free or reduced rate industry

transportat ion

. New provisions are added for the

issuance of ZED/MIBA tickets which

shall only be electronic effective 01

April 2012

RP 1800

AUTOMATED

BAGGAGE

HANDLING BASED

ON THE IATA

LICENCE PLATE

CONCEPT Provides guidelines for

automated baggage handling

withi n airline operations from

an airline perspective

. Various editorial updates to clarify

proceduresT2.12/P



## RESOLUTION 003

STANDARD RECISSION RESOLUTION

PSC(32)003 Expiry: 2 June 2011

Type: B

Resolved that, effective 1 June 2011, the following resolution is rescinded:

Resoluti on 726b, Multiple Purpose Document (MPD)

– Neutral Carbonized Automated

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 701

INADMISSIBLE PASSENGERS AND DEPORTEES

(amending)

PSC(1 6 32 )701 Expiry: Indefinite

Type: B

.....

T2.11/P



### 2. INADMISSIBLE PASSENGERS

.... 2.1.1 Notwithstanding any restrictions in the ticket, no endorsement requirement shall

apply. When endorsement is requested, such request shall not be denied.

....

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 720a

PASSENGER TICKET AND BAGGAGE CHECK

— ISSUANCE AND

HONOURING PROCEDURES

(amending)

PSC( 31 32 )720a E xpiry: Indefinite

Type: B

.....

T2.35/P



### .... 9. “NOT VALID AFTER” BOX

When a ticket has a normal one year validity and is not issued in conjunction or in

exchange for another ticket, no entry need be made. In all other cases, enter the expiry

da te (day and month). Do not complete until a confirmed reservation is entered on the

ticket.

Exception 1: Where tariff rules prohibit voluntary reservation changes, or where such

changes are only permissible against additional payment, the date to be enter ed in this

box shall be the same as the reservation date entered on the same coupon.

Exception 2: When a ticket is reissued under the provisions of Resolution 735d, the

original NVA date may be used or it may be left blank.

Any adjustments to the entry s hall be accomplished in accordance with Resolution 727.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 722

TRANSITIONAL AUTOMATED TICKET ( TAT)

(amending)

PSC( 31 32 )7 22 Expiry: Indefinite

Type: B

.....

T2.35/P



### .... 3.13 NOT VALID AFTER

When a ticket has a normal one year validity and is not issued in conjunction or in

exchange for another ticket, no entry need be made. In all other cases, imprint the

exp iry date (day and month only). Do not complete until a confirmed reservation is

imprinted on the ticket.

Exception 1: Where tariff rules prohibit voluntary reservation changes, or where such

changes are only permissible against additional payment, the dat e to be entered in this

box shall be the same as the reservation date entered on the same coupon.

Exception 2: When a ticket is reissued under the provisions of Resolution 735d, the

original NVA date may be used or it may be left blank.

Any adjustments t o the entry shall be accomplished in accordance with Resolution 727.

T4



### .... 

### 3.16 FARE CALCULATION

.... 3.16.10 Minimum Fares

.... 3.16.10.6 Round trip minimum

Where it is necessary to raise the applicable fare of a round trip pricing unit to the level

of th e highest round trip fare, imprint "P", city pair, followed by the amount. The entry

shall be made at the end of the itinerary preceding the total amount in NUCs.P14



### ....

3.29 FARE CALCULATION PRICING/REPORTING MODE INDICATOR

A Fare Calcul ation Pricing or Reporting Mode Indicator is imprinted on automated

passenger tickets. The Fare Calculation Pricing or Reporting Mode Indicator is a one

character identifier reflecting the method of pricing for the ticket that is issued. Such

indicator is imprinted automatically and can be located on the TAT tickets in the bottom

right hand corner of the validation area. There is no box demarcated. See also print

position E72. On ATB2 type tickets this indicator can be found in the “F.I.”(Fare

Indicator) bo x. See also print position E51.

Option 1 Imprinting the Fare Calculation Pricing Indicator

The values are:

0 = System computer priced (without any manual modifications except for the baggage

allowance)

1 = Manually priced

2

– 9 = For individual airline/syst em provider use

A

– Z = Unidentified industry use

Option 2 Imprinting the Fare Calculation Reporting

Indicator

There are three values as follows:

0 indicates that a fare has been system computer priced and that no change has been

made to the reservation, b etween pricing and ticket issuance with no manipulation. of

the fare, or any data filed with the fare, including taxes, fees and charges and applicable

standard fare conditions in accordance with Tariff Resolutions 100 and 101 with the

exception of the Tou r Code.

1 indicates that a fare has either been created manually or system computer priced with

agent override entries.

2 indicates that a fare has been system computer priced except for manipulation of the

baggage allowance and/or taxes, fees and charg es.P14



### RESOLUTION 722

Attachment ‘B’

TRANSITIONAL AUTOMATED TICKET (TAT)

LINE SPECIFICATIONS

— CHARACTER ALLOCATIONS

.... PRINT LINE E

Print Position

.... (72)

Option 1 Fare Calculation Pricing Indicator per Resolution 722c Attachment C

Referenc e No 10.

Option 2 Fare Calculation Reporting Indicator per Resolution 722c Attachment C

Reference No 10.

Fare Calculation Mode Indicator per Resolution 722 paragraph 3.29

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-P14



## RESOLUTION 722a

OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT)

(amending)

PSC( 30 32 )722a Expiry: Indefinite

Type: A

.....

Attachment ‘B’

OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT)

LINE SPECIFICATIONS

— CHARACTER ALLOCATIONS

.... (72)

Option 1 Fare Calculation Pricing Indicator per Resolution 722c Attachment C

Reference No 10.

Option 2 Fare Calculation Reporting Indicator per Resolution 722c Attachment C

Reference No 10

Fare Calculation Mo de Indicator per Resolution 722 paragraph 3.29

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 722c

AUTOMATED TICKET/BOARDING PASS

— VERSION 2 (ATB2)

(amending)

PSC( 30 32 )7 22c Expiry: Indefinite

Type: B

.....

T2.35/P



### .... 3.2.4 Not Valid After

When a ticket has a normal one year validity and is not issued in conjunction or in

exchange for another ticket, no entry need be made. In all other cases, imprint the

expiry date (day and month only). Do not complete until a confirmed reservation is

imprinted on the ticket.

Exception 1: Where tariff rules prohibit voluntary reservation changes, or where such

changes are only permissible against additional payment, the date to be entered in this

box shall be the same as the reservation date entered on the same coupon.

Exception 2: When a ticket is reissued under the provisions of Resolution 735d, the

original NVA date may be used or it may be left blank.

Any adjust ments to the entry shall be accomplished in accordance with Resolution 727.

### RESOLUTION 722c

Attachment ‘B’

ATB2

— PRINT LINE SPECIFICATIONS

P14



### 1.1 Flight Coupon

1.2 Passenger Receipt

– up to 4 flight segments

– optional layout

1.3 Passenger Rece ipt

– more than 4 flight segments

– optional layout

1.4 Audit/Agent/Tax

- Fee

- Charge Coupons

– up to 4 flight segments

– optional

layout

1.5Audit/Agent/Tax

- Fee

- Charge Coupons

– more than 4 flight segments

– optional

layout

1.6 Charge Form up to 4 flight segm ents

– optional layout

1.7 Charge Form more than 4 flight segments

– optional layout

Print Line E Position 51 Fare Calculation Pricing/Reporting Mode Indicator (refer to

Resolution 722 paragraph 3.29) Option 1 Imprinting the Fare Calculation Pricing

Ind icator

The values are:

0 = System computer priced (without any manual modifications except for the baggage

allowance)

1 = Manually priced

2

– 9 = For individual airline/system provider use

A

– Z = Unidentified industry use

Option 2 Imprinting the Fare Calcula tion Reporting Indicator

There are three values as follows:

0 indicates that a fare has been system computer priced and that no change has been

made to the reservation, between pricing and ticket issuance with no manipulation of

the fare, or any data filed with the fare, including taxes, fees and charges and applicable

standard fare conditions in accordance with Tariff Resolutions 100 and 101 with the

exception of the Tour Code.

1 Indicates that a fare has either been created manually or system computer pri ced

with agent override entries.

2 Indicates that a fare has been system computer priced except for manipulation of

the baggage allowance and/or taxes, fees

P14



### RESOLUTION 722c

Attachment ‘C’

MASTER LIST

— AUTOMATED TICKET/BOARDING PASS

— ATB2,

MAGNET IC STRIPE

ATB2 MAGNETIC STRIPE ITEM NUMBERS, ELEMENT DESCRIPTIONS,

FIELD SIZES AND REFERENCE NUMBERS

Item No. 33 Fare Calculation pricing/reporting mode indicator

### MAGNETIC STRIPE SPECIFICATIONS

— ATB2

FLIGHT COUPON (FORMAT CODE B)

AUDIT/AGENT COUPONS (FORMAT CODE G)

PASSENGER RECEIPT (FORMAT CODE L)

EXCESS BAGGAGE TICKET (FORMAT CODE A)

— (SECONDARY FORMAT CODE 1)

PREPAID TICKET ADVICE (FORMAT CODE A)

— (SECONDARY FORMAT CODE 4)

SPECIAL SERVICE TICKET (FORMAT CODE A)

— (SECONDARY FORMAT CODE 2)

... Item No. 33 Fare calculation pricing/reporting mode indicator

.... REFERENCES

— MAGNETIC STRIPE

SPECIFICATIONS

— ATB2

(all fields are fixed length, left justified and blank filled, unless otherwise specified by a

reference number. Each block shall end with an LR C [even parity].)

... No. 10 Fare Calculation Pricing/Reporting Mode Indicator

(refer to Resolution 722 paragraph 3.29):

Option 1 Imprinting the Fare Calculation Pricing

Indicator

The values are:

0 = System computer priced (without any manual modifications e xcept for the baggage

allowance)

1 = Manually priced

2

– 9 = For individual airline/system provider use

A

– Z = Unidentified industry use

Option 2 Imprinting the Fare Calculation Reporting Indicator

There are three values as follows:

0 indicates that a fare ha s been system computer priced and that no change has been

made to the reservation, between pricing and ticket issuance with no manipulation of

the fare, or any data filed with the fare, including taxes, fees and charges and applicable

standard fare conditi ons in accordance with Tariff Resolutions 100 and 101 with the

exception of the Tour Code.

1 Indicates that a fare has either been created manually or system computer priced with

agent override entries.

2 Indicates that a fare has been system computer pr iced except for manipulation of the

baggage allowance and/or taxes, fees and charges.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 722f

ELECTRONIC TICKET

- AIRLINE

(amending)

T2.5/P



### P SC( 31 32 )722f Expiry: Indefinite

Type: B

.....

....

3.4.1 EMD Value Coupon

– Coupon(s) of an EMD that is assigned a specific value.

May be valid for exchange (EMD

- S) or lifted in connection with an ET flight coupon

(EMD

- A).

....

T2.9/P



### 6.2 ISSUANCE

... 

### 6.2.1.7 The Validating Carrier 1 

### shall deliver an Itinerary/Receipt. This document shall

include, but not be limited to, the following:

.... Passenger Check

- In Identification Type (FOID)

— Optional 4



### ________________________________________________ __________ 4 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI1 23456XXXXXX7890

.... 6.3 DISPLAY

.... 6.3.3 Alternate search criteria to display an ET are:

....

— OR

— Passenger Check

- in Identification Type (FOID)

— Optional 1



### .

___________________________________________________________ 1 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890T2.21/P



### .... 6.4.6 Change o f Status

.... 6.4.6.1.1.2 If there is not a response to the “Change of Status” message, at a minimum

5 additional “Change of Status” messages shall be sent at agreed intervals.

.... 6.17 SYSTEM UPDATE

.... 6.17.2 If no response to the System Update message is re ceived, the sending system

shall resend the message a minimum of 5 times or as many times as necessary until a

response is received at a minimum 5 additional “System Update” messages shall be

sent at agreed intervals

.

T2.22/P

6.17.4 When the correspond ing ET flight coupon(s) are not at final status other than

final or suspend status , the receiving system shall not deny the System Update request.

When the corresponding ET flight coupon(s) are at final or suspend status, the receiving

system shall deny th e System Update request.

### RESOLUTION 722f

Attachment

Data Elements Glossary

T2.1/P



### Attachment ‘A’

ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS DATA ELEMENTS GLOSSARY



### Note: This glossary applies to the Airline ET Resolution (722f), the Neutral ET

Reso lution (722g), the Ground Handling ET Resolution (722h), the Airline EMD

Resolution (725f), and the Neutral EMD Resolution (725g) , and the Ground Handling

EMD Resolution (725h)

.

.....

CARRIER FEE DATA

.... M9



### Carrier Fee Type

- 2 ALPHANUMERIC

(Repeatable Fi eld)

..... OD = Fee related to the collection of Penalty Fees

OE

– Carbon Offset Service Code (applicable until 31 May 2011)

OF

- Carbon Offset Service Code (applicable until 31 May 2011)

OG

- Carbon Offset Service Code (applicable until 31 May 2011)

XP = P TA service charge (applicable to EMD

- S only)

....

T2.9/P



### PASSENGER CHECK

- IN (FOID)

(Applicable to IATA only)

An optional field used by the airline to index data for automatic airport check

- in. This

field may be comprised of the following three data elem ents:

Passenger Check

- In Identification

— 25 ALPHANUMERIC NUMBER (FOID)

(Applicable to IATA Only)

The actual form of identification number, e.g., 372810577909 for credit card

number. When the FOID is Credit Card it shall include only the first 6 and the l ast

4 digits of the credit card number. All remaining digits shall be replaced with an

X. E.g. 123456XXXXXX7890

Passenger Check

- In Identification (FOID)

— 4 ALPHA (Applicable to IATA

Only)

Owner or issuer of the form of identification, e.g., VI for VISA c redit card, US for

country code, etc.T2.17/P



### SEGMENT/COUPON IDENTIFIER

– 2 NUMERIC

The sequential number of an individual flight segment or value coupon, e.g. the first

segment of a multi

- coupon ticket or the first value coupon of a multi

- coupon E MD.

Related field

– see Total Number of Flight Segments.

Example for ET :

Itinerary Segments Total Number of Segments

ORDLAX 1 (of) 5

ARNK

- 5

SFOPDX 2 (of) 5

PDXMSP 3 (of) 5

MSPDFW 4 (of) 5

DFWORD 5 (of) 5

Example for EMD:

Itinerary Segments Total Number of Segments

ORDLAX 1 (of) 5

SFOPDX 2 (of) 5

PDXMSP 3 (of) 5

MSPDFW 4 (of) 5

DFWORD 5 (of) 5

Note: ARNK segments are not applicable to EMDs

T2.3/P



### ....

TRANSACTION ACTION

– 1 ALPHA

Defines the purpose of a request/outbound message. Transaction Action Codes are

listed in this Glossary.

.... P = Print

— Indicates a request to con vert the ET /EMD flight /value coupon(s) to paper

document(s)

.T2.18/P

RESOLUTION 722f



### ELECTRONIC TICKET

— AIRLINE

(amending)

Attachment B

MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

ELEMENT DESCRIPTION

Transaction NO

CHAR. A, N OR A/N DISPLAY UNSOLICITED AIRPORT CONTROL

(INFORMATION

– ATA ONLY) HISTORY DISPLAY REQUEST AIRPORT

CONTROL CHANGE OF STATUS

Action code

--- > D,J T (I

– IATA ONLY) H B C

RESOLUTION 722F REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Coupon Number 1 N C M C M M M 12

C

.......

Coupon Status indicator 1 A/N C M 11

C M M 12

C 5

......



### Notes: 12 

### Conditional for Change of status to Reissue/Exchange for the new reissue ticket/document number(s ).

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-T2.5/P



## RESOLUTION 722g

ELECTRONIC TICKET

– NEUTRAL

(amending)

PSC( 31 32 )722g Expiry: Indefinite

Type: B

.....

3.5.1.1 EMD Value Coup on

– Coupon(s) of an EMD that is assigned a specific value.

May be valid for exchange (EMD

- S) or lifted in connection with an ET flight coupon

(EMD

- A).

....

T2.9/P



### 6.2.3 Electronic Ticket

... 6.2.3.8 The issuing travel agency shall deliver an Itinerary/Rec eipt(s). This document(s)

shall include, but not be limited to, the following:

... Passenger Check

- In Identification Type (FOID) (Optional) 3

________________________________________________________________________________________

3 

### When the FOID is Credit Ca rd include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

...

6.3 DISPLAY

T2.40/ P



### 6.3.3 An ET shall only be displayed to the issuing agent or an accredited branch

location of the issuing agent, identified by Agent Numeric Code, irrespective of the

CRS/System Provider generating the request

. or an accredited branch location of the

sa me agent or the validating carrier.

....T2.9/P



### ... 6.3.5 Alternate search criteria to display an ET are:

— OR

— Passenger Check

- In Identification Type (FOID)

— Optional 1



### ______________________________________________________________

1 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

T2.40/P



### 6.6 EXCHANGE/REISSUE

.... 6.6.12 An ET shall only be exchanged/reissued by the issuing agent or an accredited

branch location of the issuing agent identified by Agent Numeric Code, irrespective of

the CRS/System Provider generating the request

. . or an accred ited branch location of

the same agent.

.... 6.8 REFUND

.... 6.8.4 An ET shall only be refunded by the issuing agent or an accredited branch

location of the issuing agent identified by Agent Numeric Code, irrespective of the

CRS/System Provider generating the request

. . or an accredited branch location of the

same agent.

### RESOLUTION 722g

Attachment B

T2.19 / P

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

– NEUTRAL MESSAGE



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

- ELEMENT DESCRIPTION

Transaction NO

CHAR. A,

N OR A/N ISSUANCE

(INFO RMAT

ON

- ATA ONLY) DISPLAY HISTORY

DISPLAY EXCHANGE/

REISSUE REFUND

Action code

--- > S D H E R

RESOLUTION 722 REQ RES REQ RES REQ RES REQ RES REQ RES

... Passenger Check

- in Identification

(FOID) 4 A O O O O O

P assenger Check

- in Identification

Number (FOID) 25 A/N O O O O O

Passenger Check

- in Identification

Type (FOID) 2 A O O O O O

## RESOLUTION 722h

ELECTRONIC TICKET

— GROUND HANDLING

(amending)

T2.5/P



### PSC( 31 32 )722h Expiry: Indefinite

Type: B

.....

.... 3.4.1 EMD Value Coupon

– Coupon(s) of an EMD that is assigned a specific value.

May be valid for exchan ge (EMD

- S) or lifted in connection with an ET flight coupon

(EMD

- A).

T2.9/P



### .... Section 6

– Procedures

6.1 GENERAL

.... 6.1.4 The Ground Handler may provide the passenger with a duplicate ET

Itinerary/Receipt(s). This document(s) shall include, but not be limited to, the following:

....

— OR

— Passenger check

- in identification (FOID) (optional) 4



### _____________________________________________________________ When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The F OID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

.

....

### 6.2 DISPLAY

6.2.4 Alternate search criteria to display an EMD are:

— OR

— Passenger Che ck

- In Identification Type (FOID)

— Optional 1



### ______________________________________________________________

1 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the l ast 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

.

T2.21/P



### ....

6.3.7 Change of Status

....

6.3.7.6 If there is not a response to the “Change of Status” message, at a minimum 5

additional “Cha nge of Status” messages shall be sent at agreed intervals.

.... 6.3.11 System Update

.... 6.3.11.4 If no response to the System Update message is received, the sending system

shall resend the message a minimum of 5 times or as many times as necessary until a

r esponse is received. at a minimum 5 additional “System Update” messages shall be

sent at agreed intervals

.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 725b

MISCELLANEOUS CHARGES ORDER (MC O)

— ISSUANCE AND

HONOURING PROCEDURES (AGENTS)

(amending)

T2.13/P



### PSC( 29 32 )725b Expiry: Indefinite

Type: B

.....

Members may use for issuance by approved Passenger Sales Agents, the

Miscellaneous Charges Order (MCO) form as described i n Resolution 725 to cover

collection for a Prepaid Ticket Advice (PTA) as provided in Resolution 731 and

collections for specified services such as air or surface transportation (including

combination with air transportation), excess baggage charges (wheth er rated as

baggage or cargo), land arrangements for inclusive tours, car hire, surface

accommodations, taxes/fees/charges, deposits, down payments, sundry

charges as provided in Resolution 727a, and hotel accommodations. When issued for a

PTA, the MCO sha ll not be used for transmittal of funds only. The MCO shall not be

issued for unspecified air transportation. When issuing and honoring MCOs, Agents

shall apply the following procedures.

In countries/Areas where a Billing and Settlement Plan (BSP) has bee n implemented,

the provisions of this resolution apply only in respect of the issuance of the automated

coupon

- by

- coupon MCO issued on blank paper or blank card in accordance with the

provisions of Resolution 725d.

Filing Period: Effe ctive Date:

18 April 2011

- 1 June 2011

23 May 2011

-P14



## RESOLUTION 725c

AUTOMATED MISCELLANEOUS CHARGES ORDER (MCO)

— CARRIER

(COUPON

- BY

- COUPON)

(amending)

PSC( 26 32 )725c Expiry: Indefinite

Type: B

.....

Attachment “ A”

.....

PRINT LINE E

Print Position

(51)

Fare calculation pricing/reporting mode indicator (optional) (refer to Resolution 722c,

Attachment ‘C’, Note No. 10) (RJ). (refer to Resolution 722 paragraph 3.29) (RJ)

Filing Period: E ffective Date:

18 April 2011

- 1 June 2011

23 May 2011

-P14



## RESOLUTION 725d

AUTOMATED MISCELLANEOUS CHARGES ORDER (MCO)

—

NEUTRAL

(COUPON

- BY

- COUPON)

(amending)

PSC( 30 32 )725d Expiry: Indefinite

Type: B

...

Attachme nt “A”

.....

PRINT LINE E

Print Position

(51)

Fare calculation pricing/reporting mode indicator (optional) (refer to Resolution 722c,

Attachment ‘C’, Note No. 10) (RJ). (refer to Resolution 722 paragraph 3.29) (RJ)

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT

— AIRLINE

(amending)

PSC( 31 32 )725f Expiry: Indefinite

Type: B

..... T2.15/P



### .... Section 1

– Introduction/Scope

... . 1.11 An EMD shall not contain ARNK coupons. See Segment/Coupon Identifier in the

Glossary Resolution 722f Attachment A.

T2.16/P



### 1.12 An EMD

- A coupon cannot be issued and associated to an ET coupon representing

an ARNK (arrival unknown) segment or sepa rate arrival segment within a PNR itinerary.

1.13 Coupons within an EMD are to be issued in sequential order without VOID

coupons.

Example:

An EMD

- A issued for services associated with ET coupons 1

- 3

- 4 would use one

EMD

- A, coupons 1

- 2

- 3.

T2.5/P



### .... 3.5. 1 EMD Value Coupon

– Coupon(s) of an EMD that is assigned a specific value.

May be valid for exchange (EMD

- S) or lifted in connection with an ET flight coupon

(EMD

- A).

.... T2.26/P



### Section 3

- Definitions

...

3.12 MARKETING CARRIER

– The airline whose Airli ne Designator is recorded as the

transporting carrier on the electronic value coupon(s)

. For a flight

- related service, the

carrier marketing the flight in a code share situation.

.... 3.14 OPERATING CARRIER

– The carrier used in a code share situation when different

from the Marketing Carrier. Where no Operating Carrier is specified in the ET coupon,

the Marketing Carrier shall be assumed to be the Operating Carrier. The airline whose

Airline Designator is recorded as the service provider on the electronic value coupon(s).T2.24/P



### ...

6.1 General

...

6.1.8.1

A separate EMD shall be issued when multiple coupons are required for the same

board and off points.

....

6.1.10 EMD

- Associated

T2.27/P



### Editor’s **Note: Renumber subsequent paragraphs.**

6.1.10.1 Only one ET record shall be associated to a single EMD

- A record. Multiple

EMD

- A record may be associated to a single ET record. Association shall always be at

coupon level.

T2.30/P



### 6.1.10.1 The intent of the association between the ET flight coupon(s) and the E MD

- A

value coupon(s) is to ensure the usage of the coupon is synchronized.

T2.28/P



### .... 6.1.10.2 Prior to associating an ET flight coupon record to an EMD

- A value coupon

record , any existing association to the EMD

- A value coupon record shall be removed by

the Validating Carrier of the EMD

- A using the System Update message for

disassociation.

T2.24/P



### 6.1.10.5. A separate EMD

- A shall be issued when multiple EMD coupons are required

for the same ET flight coupon.T2.9/P;T2.38/P;T5



### ... 6.2 ISSUANCE

... 6 .2.1.5 The Validating Carrier shall deliver a Receipt. This document shall include, but

not be limited to:

... .

Reason for Issuance Code definition,

Reason for Issuance Sub

- Code Description (as applicable),

.... Base Fare Amount /Charges

Equivalent Fare Paid Base Amount/Charges (as applicable),

Total Ticket/Document Amount,

Passenger Services

,

.... Endorsements/Restrictions (including period of validity) (when present)

Passenger Check

- In Identification Type (FOID)

— (optional) 1



### __________________________________ ___________________________ 1 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced wi th an X. E.g.

VI123456XXXXXX7890

.... T9



### 6.2.1.6 The Validating Carrier shall be provided deliver the “Terms and Conditions

Notice” contained in Resolution 726 Attachment ‘A’ to the passenger or purchaser.

T2.23/P



### 6.2.3 EMD

- Associated

....

6.2.3.3 Issuance of an EMD

- A shall be preceded by verification by the CRS/System

Provider Validating Carrier that the same board and off points [...] shall be present in

the same order as in ET record [...]T2.27/P



### ....

6.3 SYSTEM UPDATE

.... 6.3.1 Association shall always be at coupon level. Only one ET flight coupon shall be

associated to a single EMD

- A value coupon. Multiple EMD

- A value coupons may be

associated to a single ET flight coupon.

T2.21/P



### 6.3.3 If no response to the System Update message is received, the sen ding system

shall resend the message a minimum of 5 times or as many times as necessary until a

response is received. at a minimum 5 additional “System Update” messages shall be

sent at agreed intervals.

T2.22/P ;T2.29/P



### 6.3.5 When the corresponding ET flight coupon(s) are not at final or suspend status

other than final or suspend status , the receiving system shall not deny the System

Update request. When the corresponding ET flight coupon(s) are at final or suspend

status, the receiving system shall den y the a System Update request for association

.

.... T2.23/P



### 6.3.6 Association initiated by the Validating Carrier of the EMD

....

6.3.6.1 Prior to initiating a ‘System Update’ message for association the CRS/System

Provider Validating Carrier shall verify tha t the EMD

- A value coupons to be associated

are not in final status [...]

T2.9/P



### .... 6.4 DISPLAY

This action allows retrieval of all data elements related to the EMD value coupon(s) as

defined in the IATA Resolution 722f Glossary, Attachment ‘A’.

... 6.4.3 Alt ernate search criteria to display an EMD are:

Passenger Check

- in Identification Type (FOID)

— (Optional) 1



### ________________________________________________________________ 1 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

### 6.5 CONTROL

T2.30/P



### 6.5.9 Change of Status

When a carrier is being notified of a change of coupon status, only coupon(s) being

changed shall be included in the ‘Change of Status’ message.

The intent of the association between the ET flight coupon(s) and the EMD

- A value

coupon(s) is to ensure the usage of the coupon is s ynchronized.

T2.31/P



### 6.5.9.1.1 The above Coupon Status Indicators are final and close out the EMD

coupon(s).The transaction action is ‘C’ for ‘Change of Status’ message using a coupon

status of ‘E’, ‘F’ or ‘R’ for a final coupon status update , or ‘O’ wh en returning control to

the Validating Carrier

.

T2.21/P



### 6.5.9.1.1.2 If there is not a response to the “Change of Status” message, at a minimum

5 additional “Change of Status” messages shall be sent at agreed intervals.

T2.31/P



### .... 6.5.9.4. When the carrier holding control is returning control of an unused coupon to the

Validating Carrier, the Transaction Action is ‘C’ for ‘Change of Status’ message using a

coupon status of ‘O ’.

.... **Editor’s Note: following sections require re** 

**- numbering** 

.

**Current 6.5.**  **9.4 EMD**

**- Stand** 

**- alone through to 6.5.9.5.5**  **EMD**

**- Associated**  **to be**

**renumbered throughout as 6.5.9.5 though to 6.6.9.5.5.**

T2.25/P



### .... 6.5.11 Code Share

When an ET itinerary contains a code share flight with an associated EMD

- A value

coupon(s), it is the respons ibility of the ET flight coupon Operating Carrier to obtain

control of the applicable associated EMD

- A value coupon(s).

### T2.18 / P



### RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT

— AIRLINE

(amending)

Attachment B

ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

ELEMENT DESCRIPTION

Transaction NO

CHAR. A, N OR A/N DISPLAY REQUEST AIRPORT

CONTROL CHANGE OF STATUS SYSTEM UPDATE

Action code

--- > D B C U

RESOLUTION 725G REQ RES REQ RES REQ RES REQ RES

... Coupon Number 1 A/N C M M M 13 C 5 M

Coupon Status indicator 1 A/N C M M 13 C 5

...



### Notes: 13 

### Conditional for Change of status to Reissue/Exchange for the new reissue ticket/document number(s).

### RESOLUTI ON 725f

ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION

MATRIX

– AIRLINE MESSAGES

Attachment B

T2.32/P

ELEMENT DESCRIPTION

Data Element CHAR.

A, N

OR

A/N DISPLAY REQUEST

AIRPORT

CONTROL CHANGE OF

STATUS SYSTEM

UPDATE

Transaction Code

--- > D B C U

725 f REQ RESP REQ RESP REQ RESP REQ RESP

... Additional Services Filed Fee

Amount 12 A/N C C

Additional Services Filed Fee

Bankers Selling Rate (BSR) 13 A/N C C

...



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT

— NEUTRAL

(amending)

PSC( 31 32 )725g Expiry: Indefinite

Type: B

.....

T2.15/P



### .... Section 1

– Introduction/ Scope

.... 1.8 An EMD shall not contain ARNK coupons. See Segment/Coupon Identifier in the

Glossary Resolution 722f Attachment A.

T2.16/P



### 1.9 An EMD

- A coupon cannot be issued and associated to an ET coupon representing

an ARNK (arrival unknown ) segment o r separate arrival segment within a PNR

itinerary.

1.10 Coupons within an EMD are to be issued in sequential order without VOID

coupons.

Example:

An EMD

- A issued for services associated with ET coupons 1

- 3

- 4 would use one

EMD

- A, coupons 1

- 2

- 3.

T2.5/P



### .... 3.7.1 EMD Value Coupon

– Coupon(s) of an EMD that is assigned a specific value.

May be valid for exchange (EMD

- S) or lifted in connection with an ET flight coupon

(EMD

- A).

.... T2.26/P



### 3.14 MARKETING CARRIER

– The airline whose Airline Designator is recorded as the

transporting carrier on the electronic value coupon(s)

. For a flight

- related service, the

carrier marketing the flight in a code share situation.

....

3.16 OPERATING CARRIER

– The carrier used in a code share situation when different

from the Marketing Carrier. Where no Operating Carrier is specified in the ET coupon,

the Marketing Carrier shall be assumed to be the Operating Carrier. The airline whose

Airline Designator is recorded as the service provider on the electronic value coupon(s)

.T2. 24 /P



### ... 6.1 General

...

6.1.7.1 A separate EMD shall be issued when multiple coupons are required for the

same board and off points.

.... 6.1.9 EMD

- Associated

T2.27/P



### 6.1.9.1 Only one ET record shall be associated to a single EMD

- A record. Multipl e

EMD

- A record may be associated to a single ET record. Association shall always be at

coupon level.

**Editor’s Note: Renumber subsequent paragraphs.**  **Current 6.1.9.2 becomes 6.1.9.1**

T2.24/P



### .... **New 6.1.9.2**

6.1.9

. 2 A separate EMD

- A shall be issued when multiple EMD coupons are required for

the same ET flight coupon.

... 6.2 ISSUANCE

T2.38/P



### 6.2.1.1 Electronic or paper Passenger Receipt in accordance with 6.2.1. 5 6 ;

...T2.9/P;T5



### ....

6.2.1.6 The issuing travel agent shall deliver a Receipt. This docume nt shall include, but

not be limited to:

.... Reason for Issuance Code definition,

Reason for Issuance Sub

- Code Description (as applicable),

.... Base Fare Amount /Charges

Equivalent Fare Paid Base Amount/Charges (as applicable),

Total Ticket/Document Amount,

... . Endorsements/Restrictions (including period of validity) (when present)

Passenger Check

- In Identification Type (FOID)

— (optional) 1

....



### _____________________________________________________________ 1 

### When the FOID is Credit Card include the appropriate tw o

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

.... T9



### 6.2.1.7 The Validating Carrier or, when the electronic miscellaneous document is

issued by a travel agent, the issuing travel agent shall be provided deliver the “Terms

and Conditions Notice” contained in Resolution 726 Attachment ‘A’ to the passenger or

purchaser.

T2.6/P



### ....

6.2.3 EMD

- Associated

6.2.3.1 An EMD

- A shall be limited to one passenger or, in the case of payment of a

deposit, a group name only

.

....

6.3 DISPLAY

T2.40/P



### 6.3.2. An agency issued EMD shall only be displayed to the issuing agency or an

accredited branch location of the is suing agent, identified by Agent Numeric Code,

irrespective of the CRS/System Provider generating the request

. , location or an

authorized branch locationT2.9/P



### ... 6.3.5 Alternate search criteria to display an EMD are:

.... Passenger Check

- in Identifica tion Type (FOID)

— (Optional) 1

....



### ________________________________________________________________ 1 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digi ts of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

6.4 EXCHANGE/REISSUE

T2.40/P



### 6.4.11 . An agency issued EMD shall only be exchanged/reissued by the issuing agency

or an accredited branch location of the issuing agent,, identified by Agent Numeric

Code, irrespective of the CRS/System Provider generating the request

. location or an

authorized branch location

... 6.5 REFUND

.... 6.5.7 . An agency issued EMD shall only be refunded by the issuing agency or an accredited branch location of the issuing agent, identified by Agent Numeric Code,

irrespective of the CRS/System Provider generating the request

. , location or an

authorized branch location

.

### RESOLUTION 725g

Attachment ‘B’

T2.2/P



### Electronic Miscell aneous Document Message Construction Matrix

– Neutral

Messages

In ‘Fare Component Calculation Elements’ section:

Fare Calculation Coupon/Itinerary Sequence Number 2 A /N

T2.32/P



### ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION

MATRIX

– NEUTR AL MESSAGES

(amending)

ELEMENT DESCRIPTION

Transaction CHAR.

A, N

OR

A/N ISSUANCE DISPLAY HISTORY

DISPLAY EXCHANGE/

REISSUE REFUND SYSTEM

CANCEL REFUND

CANCEL VOID

Action Code

--- > S D H E R X,Y Z V,W

RESOLUTION 725 G REQ RESP R EQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

... Additional Services Filed Fee

Amount 12 A/N C C C C

Additional Services Filed Fee

Bankers Selling Rate (BSR) 13 A/N C C C C

...T2.19/P



### RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT

— NEUTRAL

(amending)

Attachment B

ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX

– NEUTRAL MESSAGES

ELEMENT DESCRIPTION

Transaction NO

CHAR. A, N

OR A/N IS SUANCE DISPLAY HISTORY DISPLAY EXCHANGE/

REISSUE REFUND

Action code

--- > S D H E R

RESOLUTION 725G REQ RES REQ RES REQ RES REQ RES REQ RES

... Passenger Check

- in Identification

(FOID) 4 A O O O O O

Passenger C heck

- in Identification

Number (FOID) 25 A/N O O O O O

Passenger Check

- in Identification

Type (FOID) 2 A O O O O O

### T2.20/P

RESOLUTION 725g



### ELECTRONIC MISCELLANEOUS DOCUMENT

— NEUTRAL

(amending)

Attachment B

ELECTRONIC MISCELLANE OUS DOCUMENT MESSAGE CONSTRUCTION MATRIX

– NEUTRAL MESSAGES

ELEMENT DESCRIPTION

Transaction NO

CHAR. A, N OR

A/N ISSUANCE DISPLAY HISTORY DISPLAY EXCHANGE/

REISSUE REFUND SYSTEM

CANCEL REFUND CANCEL VOID

Action code

--- > S D H E R X, Y Z V,W

RESOLUTION 725G REQ RES REQ RES REQ RES REQ RES REQ RES REQ RES REQ RES REQ RES

...

Reason for Issuance Code 1 A/N M M C M M M C

Reason for Issuance Sub Code 3 A/N M M C M M M

...



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 725h

ELECTRONIC MISCELLANEOUS DOCUMENT

— GROUND HANDLING

(amending)

PSC( 31 32 )725h Expiry: Indefinite

Type: B

**.....** T2.5/P



### 3.4.1 EMD Value Coupon

– Coupon(s) of an EMD that is assigned a specific value.

May be valid for exchange (EMD

- S) or lifted in connection with an ET flight coupon

(EMD

- A).

T2.26/P



### ...

3.13 MARKETING CARRIER

– The airline whose Airline Designator is recorded as the

transporting carrier on the electronic value coupon(s)

. For a flight

- related service, the

carrier marketing the flight in a code share situation.

.... 3.15 OPERATING CARRIER

– The carrier used in a code share sit uation when different

from the Marketing Carrier. Where no Operating Carrier is specified in the ET coupon,

the Marketing Carrier shall be assumed to be the Operating Carrier. The airline whose

Airline Designator is recorded as the service provider on the electronic value coupon(s).

T2.9/P



### ... 6.1 GENERAL

... 6.1.4 The Ground Handler may provide the passenger with a duplicate EMD

Itinerary/Receipt(s). This document(s) shall include, but not be limited to, the following:

.... Passenger Check

- In Identification Ty pe (FOID)

— (optional) 3



### _____________________________________________________________ 3 

### When the FOID is Credit Card include the appropriate two

- letter vendor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

cre dit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

.... 6.2 DISPLAY

This action allows retrieval of all data elements related to the EMD value coupon(s) as

defined in the IATA Resolution 722f Glossary, Attachment ‘A’.

...

### 6.2.4 Alternate search criteria to display an EMD are:

Passenger Check

- in Identification Type (FOID)

— (Optional) 1



### ________________________________________________________________ 1 

### When the FOID is Credit Card include the appropriate two

- letter ven dor

code of the credit card. The FOID shall include only the first 6 and the last 4 digits of the

credit card number. All remaining digits shall be replaced with an X. E.g.

VI123456XXXXXX7890

T2.21/P



### ....

6.3.7 Change of Status

....

6.3.7.2.1 If there is not a response to the “Change of Status” message, at a minimum 5

additional “Change of Status” messages shall be sent at agreed intervals.

.... 6.3.9 System Update

.... 6.3.9.5 If no response to the System Update message is received, the sending system

shall rese nd the message a minimum of 5 times or as many times as necessary until a

response is received. at a minimum 5 additional “System Update” messages shall be

sent at agreed intervals.

### RESOLUTION 725h

Attachment ‘B’

T2.32/P



### ELECTRONIC MISCELLANEOUS DOC UMENT MESSAGE CONSTRUCTION

MATRIX

– GROUND HANDLING MESSAGES

(amending)

ELEMENT DESCRIPTION

Data Element CHAR.

A, N

OR

A/N DISPLAY REQUEST

AIRPORT

CONTROL CHANGE OF

STATUS SYSTEM

UPDATE

Transaction Code

--- > D B C U

725 h REQ RESP REQ RES P REQ RESP REQ RESP

... Additional Services Filed Fee

Amount 12 A/N C C

Additional Services Filed Fee

Bankers Selling Rate (BSR) 13 A/N C C

...



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 726

MULTIPLE PURPOSE DOCUMENT (MPD)

(amending)

PSC( 29 31 )726 Expiry: Indefinite

Type: B

T2.13/P



### 2. The MPD is available in four three different formats which are the following

Resolutions:

Auto mated Carrier Carbonized MPD

— Resolution 726a;

Automated Neutral Carbonized MPD

— Resolution 726b;

Manual Carrier Carbonized MPD

— Resolution 726f;

Manual Neutral Carbonized MPD

— Resolution 726e 1.

....

1 In countries/Areas where a Billing and Settlement Pl an (BSP) has been implemented The Manual Neutral MPD is supplied to

travel agents in a virtual format version via IATA BSP link. The manual paper version is no longer supplied.



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-T2. 13 /P



## RESOLUTION 726e

MULTIPLE PURPOSE DOCUMENT (MPD)

— NEUTRAL, CARBONISED

, MANUAL

(amending)

PSC( 29 32 )726e Expiry: Indefinite

Type: B

RESOLVED that:

In countries/Areas where a Billing and Settlement Plan (BSP) has been implemented

, the Manual, Neutral Carbonized Multiple Purpose Document (hereinafter referred to as

MPDNCM) may be used by all approved Passenger Sales Agents on behalf of airlines

participating in that plan, as provided herein

. the pro visions of this resolution shall apply

only in respect of MPDNMs supplied in a virtual format version distributed and issued

via IATA BSP link

.

Attachment ‘ A ’ does not apply to IATA BSPs

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 728

CODE DESIGNATORS FOR PASSENGER TICKET AND BAGGAGE

CHECK

(amending)

PSC( 31 32 )728 Expiry: Indefinite

Type: B

...

P8



### 2.3 Fare Basis Codes for Zonal Employee Discount Tr avel Scheme (ZED)

The Zonal Employee Discount (ZED) travel scheme is a multilateral agreement by

airlines to offer reduced rate personal travel for airline industry employees and eligible

persons in a standard format that allows for the mutual acceptance of tickets in an

interline environment.

Effective for travel on/after 1 April 2012, tickets issued under the Zonal Employee

Discount (ZED) travel scheme and the Multilateral Interline Business Agreement (MIBA)

travel scheme by one member for travel on ano ther member's services shall be

electronic tickets. ZED/MIBA members shall not accept other airlines' paper tickets for

staff travel on or after 1 April 2012

.

....

T2.33/P



### 7. FORM OF PAYMENT CODE **(mandatory)**

.... Commercial Company Credit Cards

.... Airline Credit Cards

.... Braathens ASA Bracard BU 2



### .... Airline Issued Personal Cards

— Industry Identifier “2”

.... 2154 Braathens ASA Bracard

....T2.3 9 /P



### CREDIT CARD CODES (ALPHA) 1 3



### 3 Also applies to other payment cards.

T2.8/P



### .... 30XX 3000 00 to 30 59 99. 3095 00 to 3095 99 Diners Club

36XX 3600 00 to 3699 99 Diners Club/Carte Blanche 1



### 38XX 3800 00 to 3999 99 Diners Club/Carte Blanche

....

________________________________________________________________ 1 

### Processed as MasterCard (CA) t ransactions with point of sale American Samoa,

Bahamas, Bermuda, British Virgin Islands, Canada, Cayman Is, Dominican Republic,

Federated Sates of Micronesia (including Yap and Pohnpei), Marshall Is (including

Majuro), Guam, Haiti, Jamaica, Northern Marian a Is (Saipan), Palau, Puerto Rico, Turks

and Caicos Is, United States, U.S. Minor Outlying Islands defined as Baker Is, Howland

Is, Jarvis Is, Johnston Atoll, Midway Is, Navasaa Is, Palmyra Atoll, Wake Is), U.S Virgin

Is.

.... T2.7/P



### .... Merchandising and Banking Cards

– Industry Identifier “6”

6011 00 to 6011 99

- 6500 00 to 6509 99 6440 00 to 6599 00 Discover Card/Private

Issue Card

– Issued by Novus Card Products

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2 011

-P14



## RESOLUTION 731a

AUTOMATED PREPAID TICKET ADVICE (PTA)

— CARRIER

(COUPON

- BY

- COUPON)

(amending)

PSC( 26 32 )731a Expiry: Indefinite

Type: B

.....

Attachment ‘A’

.....

PRINT LINE E

Print Position

(51)

Fare calculation prici ng/reporting mode indicator (optional) (refer to Resolution 722c,

Attachment ‘C’, Note No. 10) (RJ). (refer to Resolution 722 paragraph 3.29) (RJ)

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 735

PERIOD OF VALIDITY

(amending)

PSC( 31 32 )735 Expiry: Indefinite

Type: B

T2.41/P



### RESOLVED that, unless otherwise specifically provided in the applicable fares

resolutions:

.... 5. For tickets submitted for exchange, the p eriod of validity of the new ticket issued in

exchange will be one year from the new date of commencement of flight travel or if

open

- dated and/or no portion of the ticket is used, one year from the date of new ticket

issue.

.... Note: Expired validity ticke ts are not eligible for exchange or reissue.

**Example 1**  **:** For a totally unused ticket issued 08JUN 04 10 when such ticket is

presented for reissue exchange on 06JUN 05 11 for travel commencing 07JUN 05 11

such ticket will have a validity of 07JUN 06 12 based on the new date of commencement

of travel for a ticket with a one year validity.

**Example 2:** For a totally unused ticket issued 08JUN10 with a one year validity when

such ticket is presented for exchange on 09JUN11 for travel commencing 10JUN11

such ticket is ex pired and may no longer be accepted for further exchange.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 735d

INVOLUNTARY CHANGE OF CARRIER, ROUTING, CLASS OR TYPE

OF FARE

(amending)

PSC( 31 32 )735d Expiry: Indefinite

Type: B

.....

T2.10/P



### ....

1.9 ‘TICKET HANDLER’ means the handling company used for passenger ticketing

and related ticketing services on behalf of the Marketing/Operating Carrier where the

handling company is using a system other than the Marketing/Operating Carrier's

system.

means an airline used to perform ticketing services on behalf of the Operating Carrier,

in locations where the Marketing/Operating Carrier does not have its own ticketing point

and using a different system to that of the Operating Carrier.

T2.36/P



### 6.4 Procedures for Reissue

.... 6.4.2.1

The provisions of this paragraph shall apply only in respect of reissue when the same

cabin class is booked in the flight coupons affected by the disruptio n.

Reservation procedures for upgrading to a higher compartment are covered in section

2.4.3.1.

In cases where an involuntary change results in a change from the original connecting

flight(s) and the fare basis differs on the coupon(s) affected by the di sruption, the fare

basis to be used on all reissued coupons shall be the fare basis of the first flight coupon

affected by the disruption.

Examples:

Original Routing: OSL

- LH

– X/HAM

- KL

- AMS

Fare Basis Codes: YW KPEX

New Routi ng: OSL

- KL

- AMS

New Fare Basis: YW

### or

New Routing OSL

- SK

- X/LON

- BA

- AMS

New Fare Basis YW YW

Original Routing: TYO AF X/PAR KL AMS

Fare Basis Codes: JLOW COW

New Routing: TYO

- KL

- AMS

New Fare Basis: JLOW

or

New Routing TYO

- SK

- X/CPH

- KL

- AMS

New Fare Basis JLOW JLOW

6.4.2.2 In cases where an involuntary change results in a change from the original

connecting flight(s) and the fare basis and cabin class differ on the coupon(s) affected

by the disruption, the fare basis to be used on all reissued coupons shall be the fare

basis of the first flight coupon affected by the disruption. Upgrading to a higher cabin

class that is not shown on the coupons affected by the involuntary rero uting shall only

be permitted in accordance with the procedures for upgrading to a higher compartment

covered in section 2.4.3.1.

The fare basis to be applied to the reissued ticket shall refer to the fare basis that was

shown on the first coupon affected by the disruption of the original ticket irrespective of

the actual cabin class of travel.

Examples:

Original Routing: TYO AF X/PAR KL AMS

Fare Basis Codes: FOWAF COWKL

New Routing: TYO

- JL

- AMS

New Fare Basis: FOWAF

### or

New Routing TYO

- SK

- X/CPH

- KL

- AMS

New Fare Basis FOWAF FOWAF

Examples:

Original Routing: AMS KL X/PAR AF TYO

Fare Basis Codes: COWKL FOWAF

New Routing: AMS

- JL

- TYO

New Fare Basis: COWKL

or

New Routing AMS

- KL

- X/CPH

- SK

- TYO

New Fare Basis COWKL COWKL

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 740

FORM OF INTERLINE BAGGAGE TAG

(amending)

PSC( 31 32 )740 Expiry: Indefinite

Type: B

B8.18/P



### ... 4.1 Checked Baggage Tags

..... Limited Release RFID RP1740 C RFID RP1740c ‘ I ’

...

5.1 Tag Number

Each baggage tag shall have a unique t ag number (tag number) printed on the tag as

specified below in alpha/numeric characters,

.......

...

5.1.1 Alpha/Numeric Characters:

5.1.1 (a) the two

- character designator assigned as their baggage tag issuer

code to the carrier or non

- airline company providing the tag;

5.1.1 (b) a six

- digit number

5.1.1.1 Manual tags provided by no n

- airline handling organizations, shall,

when used for the carriage of baggage on Member's flights, show the designator

'XH' as the baggage tag issuer code. When such non

- airline handling

organizations and any carrier use another company's departure contro l system to

provide a check

- in service, then the on

- demand baggage tags will not show 'XH'

but will bear a designator from the options in 5.1.1.2.

### 5.1.2 (a) 1st position:

• 0 = interline tag

• 1 = 'fallback' tag (for sortation systems see Res olution 30.70)

• 2 = interline expedite tag

• 3

- 9 = interline and on

- line use

5.1.2 (b) 2nd to 4th positions:

• the three

- digit numeric baggage tag issuer code assigned by IATA to the

carrier or non

- airline company.

5.1.2 (c) 5th to 10th positions :

• the six

- digit serial number

...

5.1.2.2 The bar coded tag number shall be printed on the information area, on each

removable stub and on the identification/claim portion of each tag. Bar code specifications

are provided in Attachment B.

...

5.3.1 The routing area contains information appropriate to each sector of the journey

and consists of:

5.3.1 (a) A final destination field, and underneath it, except on point to point tags;

5.3.1 (b) One or more transfer fields.

5.3.2 The final destination fi eld, and each transfer field shall have entered into them:

5.3.2 (a) The destination and transfer points respectively, expressed by the 3

- letter IATA

airport code;

5.3.2 (b) the airline code(s) and flight number(s) of the Operating Carrier(s);

5.3.2 (c) optional on demand printed tags numeric date (dd) and the time of departure.

...

### Editor’s note: **Example is after 5.2.9 but should be moved to**  **go after 5.4** 

BAGGAGE RECEIPT CARD

Sample 2 Not to Scale

...

5.4.6 Optionally, may contai n the following n otices :

...

5.8.4.1 Routing area

- demand printed tags

5.8.4.1 (a) the final destination field and each transfer field shall have a minimum height of

16 mm;

5.8.4.1 (b) If the transfer field also serves as a removable stub, a minimum heig ht of 26

mm is required to accommodate the baggage tag number in both alpha

numeric characters and bar

- code format.

5.8.4.2 Routing area

- manually issued tags;

5.8.4.2 (a) the final destination field and each transfer field shall have a minimum height of

25 mm;

5.8.4.2 (b) If the transfer field also serves as a removable stub, a minimum height of 35

mm is required to accommodate the baggage tag number in both alpha

numeric characters and bar

- code format.

...

### 5.8.7.1 Hole (see Attachments 'S' and 'S1' )

When using a hole to detect top of form, the following specifications apply. They are

based on facing the printer with the paper face (printed side) up.

5.8.7.1 (a) The distance from the left edge of the tag to the left edge of the hole is not

more th an 12.0 mm (0.472 in)

5.8.7.1 (b) The distance from the left edge of the tag to the right edge of the hole is not

less than 17.0 mm (0.670 in);

5.8.7.1 (c) Height of the hole

1.59 mm (0.0626 in) minimum

6.00 mm (0.236 in) maximum

5.8.7.2 Opacity ( See Attachment 'T')

To detect the difference between the opacity of the tag (face material and backing paper)

and the opacity of the backing paper between tags, the ratio shall be a minimum of 3:1,

defined as follows:

5.8.7.2 (a) Optical translucency of the backing paper shall be a minimum of 57%.

5.8.7.2 (b) Maximum optical translucency of the tag is 18%. The tag includes the backing

paper, adhesive and face material.

...

5.8.8.2 If top of form identification is obtained by using a hole, the following o ptions may

be used:

5.8.8.2 (a) A form feed area, as described in 5. 7 8 .8.1, may be used in conjunction with

a hole (see Attachments 'S' and 'S1');

5.8.8.2 (b) If a form

- feed area is not necessary tags need only be separated by a

perforation (see Attac hment 'U').

...

7.2.2 Must be used for all baggage checked, carried and returned to passengers within

the EU Union Area, and

...

7.3.1 Must be used for all expedite baggage forwarded, carried and delivered in the EU

Union Area which is not subject to Customs co ntrol within the EU Union Area, and

...

### Attachment A

...

“DEMAND PRINTED TAG”. For the purpose of this resolution, 'Demand Printed' tags

shall refer to tags “. that are completed by a computer generated system at time of

check

- in from roll or fan fold or other suitable stock. Demand printing may range from

printing only the routing information to the printing of all imprints required on the tag....

.....

Attachment F

...

MANUALLY ISSUED SELF

- SEAL TAG FOR BOXES AND CARTONS

In addition to the Common Specificat ions, the following also apply:

1 Bar Code (Boxes and Cartons)

A large bar code, as described in attachment B, shall be printed for sortation and/or

scanning.

...

Attachment L1

... 3. Format

Members may use either format of Expedite Baggage Tag shown in th e following

illustrations.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-P14



## RESOLUTION 742e

AUTOMATED EXCESS BAGGAGE TICKET

— CARRIER

(COUPON

- BY

- COUPON)

(amending)

PSC ( 26 32 )742e Expiry: Indefinite

Type: B

....

Attachment ‘A’

....

PRINT LINE E

Print Position

(51)

Fare calculation pricing/reporting mode indicator (optional) (refer to Resolution 722c,

Attachment ‘C’, Note No. 10) (RJ). (refer to Resolution 722 paragraph 3.29) (RJ)

....

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RESOLUTION 745

DANGEROUS GOODS IN PASSENGERS BAGGAGE

( amending )

B6



### PSC( 2 8 32 )745 Expiry: Indefinite

Type: B

**Editor’s Note**  : the current text of Resolution 745 will be given an expiry date of 31 December

2012. This version is valid from 1 January 2013

.



### Effective 1 January 2013

RESOLVED that Members shall:

1

. Observe the following with respect to the carriage of dangerous goods in or as

passenger

- checked or carry

- on baggage.

1.1 DANGEROUS GOODS

1.1.1 For safety reasons dangerous goods as defined in the IATA Dangerous Goods

Regulations (DGR), shall not be c arried in or as passenger checked or carry

- on

baggage except as specifically permitted in accordance with the provisions set out in

Subsection 2.3 of the current edition of the IATA DGR.

1.1.2 Members should develop and publish for passenger handling sta ff and cabin

crew the procedures to be followed to alert passengers that certain items of dangerous

goods are specifically prohibited from being in checked baggage, e.g. spare lithium

batteries. The procedures should address circumstances where due to the quantity of

carry

- on baggage or due to aircraft size limitations passenger carry

- on baggage

cannot be accommodated in the cabin.

**PASSENGER AWARENESS**

**— DANGEROUS GOODS**  **IN BAGGAGE**

4.1 To place special emphasis on passenger awareness of dangerous goods in

b aggage, Members must ensure that information as to the types of dangerous goods

which a passenger is forbidden from transporting aboard an aircraft is provided at the

point of ticket purchase. Information provided via the Internet may be in text or pictori al

form but should be such that ticket purchase cannot be completed until the passenger,

or a person acting on their behalf, has indicated that they have understood the

restrictions on dangerous goods in baggage

.

### 4.2 In addition, Members must ensure that notices warning passengers as to the type of

dangerous goods which they are forbidden from transporting aboard an aircraft are :

(a) prominently displayed in sufficient number at each of the places at an airport

where

o tickets are issued,

o passengers check ed in,

o aircraft boarding areas, and

(b) clearly displayed at any other location where passengers are checked in.

These notices must include visual examples of dangerous goods forbidden from

transport aboard an aircraft

4.3 Members should have informa tion on those dangerous goods which may be carried

by passengers in accordance with 1.1.1 available prior to the check

- in process on their

web sites or other sources of information.

4.4 When provision is made for the check

- in process to be completed remote ly (e.g. via

the Internet), Members should ensure that information on the types of dangerous goods

which a passenger is forbidden to transport aboard an aircraft is provided to

passengers. Information may be in text or pictorial form but should be such tha t the

check

- in process cannot be completed until the passenger, or a person acting on their

behalf, has indicated that they have understood the restrictions on dangerous goods in

baggage.

4.5 When provision is made for the check

- in process to be completed at an airport by a

passenger without the involvement of any other person (e.g. automated check

- in

facility), Members or the airport operator should ensure that information on the types of

dangerous goods which a passenger is forbidden to transport aboard a n aircraft is

provided to passengers. Information should be in pictorial form and should be such that

the check

- in process cannot be completed until the passenger has indicated that they

have understood the restrictions on dangerous goods in baggage.

**Note:**

The requirements in 4.1, 4.4 and 4.5 with respect to ticket purchase and check

- in on

operator websites will become mandatory with effect 1 January 2013.

Filing Period: Effective Date:

18 April 2011

- 1 June 201 1

23 May 2011

-P3



## RESOLUTION 763

LOCATION IDENTIFIERS

( amending )

PSC( 30 32 )763 Expiry: Indefinite

Type: B

RESOLVED that:

.....

1.4 An airport will not be listed in or de

- listed from the IATA Airline Coding Directory

under a metropolitan area location id entifier unless a specific request for such action is

submitted to the IATA or ATA Head Office, as appropriate.

1.4.1 If a request requires the creation of a new metropolitan area (from one to two

airports), the airport operators of each airport concerned as well as the airlines serving

those airports shall be included in the poll, as per 1.5. This provision shall also apply

for a request to remove an airport from a metropolitan area comprising only two airports

and the consequential dismantling of that metropolitan area.

1.4.2 However, if a request requires the listing/de

- listing of an additional airport to/from

a metropolitan area (comprising two or more airports), only the airport operator as well

as the airlines serving the additional airport shall b e included in the poll as per 1.5.

1.5 Creation/dismantling of a metropolitan area location identifier, or the listing/de

listing Listing or de

- listing of an airport under a metropolitan area location identifier, shall

only be actioned if it is establish ed by the IATA or ATA Secretariat that:

1.5.1 the operator(s) of the airport(s) in question support(s) such action; the operators

of the airports concerned support such action;

1.5.2 the national aeronautical authorities of a European Community country do not object to

such action. The national aeronautical authorities of an EC country will be notified of any

proposed amendment to a metropolitan area listing by the IATA or ATA Secretariat and be

asked to advise of any objection to such a proposed listing in writing with justification. If no reply

is received within 60 days it will be assumed that the national aeronautical authorities do not

object to the amendment;

### 1.5.3 a majority of responses from a poll of carriers operating scheduled air transport services

serving the airport(s) concerned support such action. For the purpose of determining which air

carriers serve such airport(s), the IATA or ATA Secretariat as appropriate will consult the airport

authority(ies) concerned. For the purposes of co mpiling the list of carriers serving an airport(s),

the airport authority(ies) is to include the teletype address and/or e

- mail address of the carriers

presently operating scheduled air transport services or which have operated to the airport during

the pr evious 12 month period. For the purposes of conducting a poll, the following criteria shall

apply;



### 1.5.2 a majority of responses from a poll of airlines operating scheduled air transport

services serving all the airports concerned support such action. For the purpose of

determining which airlines serve such airports, the IATA or ATA Secretariat as

appropriate will consult the airport authorities concerned. For the purposes of compiling

the list of airlines, the airport authorities are to include the te letype address and/or e

mail address of the airlines presently operating scheduled air transport services or

which have operated to the airport during the previous 12 month period.

1.5.3 In the event a majority of airlines do not support the proposed ac tion to list an

additional airport to an existing metropolitan area, IATA will inform the relevant national

aeronautical authority. In such case the national aeronautical authority may, at its

discretion, overturn the vote by advising IATA accordingly in writing and in that case the

airport will be listed in the existing metropolitan area. If no reply is received within 90

days it will be assumed that the national aeronautical authority supports the results of

the poll.

1.6 For the purposes of conductin g a poll, the following criteria shall apply:

1.5.4 1.6.1 the poll will be conducted not more than once per year for a given airport;

1.5.5 1.6.2 the poll will be sent by teletype and/or by e

- mail to:

1.5.5.1 1.6.2.1 the Passenger Services Confer ence Accredited Representative of

IATA Member carriers airlines or the interline contact of Member carriers airlines

participating in the MITA but not represented in the Passenger Service Conference,

1.5.5.2 1.6.2.2 the interline contact for non

- IATA c arriers airlines which are party to

the IATA Multilateral Interline Traffic Agreements,

1.5.5.3 1.6.2.3 the chief executive (head office teletype address and/or by e

- mail ) of

any other carrier(s) airline(s) indicated as concerned by the airport author ity(ies)

concerned;

### 1.5.5.4 1.6.2.4 all Accredited Representatives of the Passenger Services Conference

and the Composite Tariffs Conference for their information;

1.5.6 1.6.3 a majority shall be considered as a simple majority of carriers airlin es

responding to the poll, with non

- responses and abstentions not counting in the poll.

1.5.7 1.6.4 Requests received from non

- IATA and non

- ATA airlines for listing an

airport under a metropolitan area location identifier will be subject to a charge set by

IATA.

**Note** : The criteria set forth in this paragraph shall not apply to listings as they appeared

in the IATA Airline Coding Directory prior to 1 December 1987.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-780 P7

B11

P17 0 

## RESOLUTION 780

FORM OF INTERLINE TRAFFIC AGREEMENT

— PASSENGER

( amending )

PSC( 30 32 )780 Expiry: Indefinite

Type: B

....

RESOLVED that:

.....



## Attachment ‘A’

IATA INTERLINE TRAFFIC AGREEMENT

- PASSENGER

.....

2.2.6 Whereas certain parties .......

.....

2.2.7 Whereas certain parties to this agreement issue paper miscellaneous documents

and excess baggage tickets as defined in IATA Resolutions 722e, 725, 725a, 725b,

725c, 725d, 726, 726a, 726b, 726e, 726f, 731a, 742, 742a, 742c, 742d and 742e, any

other party which concurs with the Issuing Airline may refuse such paper miscellaneous

documents and excess baggage tickets. However, the refusing p arty will provide at

least 12 months notice to interline partners. The refusing party shall notify the IATA

Global Head, Passenger of which other party's paper tickets it refuses to accept, any

specific exclusions to its policy and will provide an effecti ve date. The IATA Head,

Passenger shall publish in the MITA Manual a list of such refusals and the

corresponding effective dates.

.....

5.4.10 When processing claims involving international travel and airline(s) pro rata share of

such claim exceeds US$1 ,500 (or equivalent), the claim receiving airline shall notify each such

airline before playing the claim. Failure to respond within thirty (30) days from the date of

notification will signify authorization to the carrier handling the claim to settle. For the purposed

of proration, settlement of partial loss and/or damage by the claim receiving airline shall be

accepted by the prorate partner(s) up to a limit of the total weight of the bag.

( 

### Editor’s **note:** re

- number subsequent paragraphs )

### .... 5.4 BAGG AGE CLAIMS AND PRORATION

5.4.8 Requests for prorate and provision of supporting documentation shall be made

directly to the headquarters central baggage claims office, not through the interline

billing and settlement process , using the format shown in Ap pendix ‘C’ “PRORATE

NOTICE” as required to support any claim under this agreement including requests for

100%:

.... 5.4.8.7 Invoice billings to the responsible carrier(s) through the airline clearing house

will be sent electronically following the electronic billing process outlined in Article 8 and

the IATA Clearing House procedures manual.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-B3.2



## RESOLUTION 792

BAR CODED BOARDING PASS (B CBP)

— VERSION 3 4

(amending)

PSC ( 30 32 ) Expiry: Indefinite

Type: B

RESOLVED that:

Members may issue, either for online or interline carriage, a Boarding Pass with version

2 4 of the Bar Code Boarding Pass standard as described herein. All of the following

specifications define the required characteristics of the elements and format of the Bar

Code on the Boarding Pass or electronic (mobile) device or stored on the NFC chip

.

Section 1

– General

INTRODUCTION

This resolution defines a m achine

- readable bar code for boarding passes or electronic

(mobile) devices. This data format supports single segment, multi

- segment and inter

line data encoding. The 2

- dimensional Bar Code format has the capacity to convey this

data allowing a wider range of devices to display or produce boarding passes with

encoded data

. This resolution defines Boarding Pass data supporting single

- segment, multi

- segment

and interline journeys; it also defines a machine

- readable bar code format and an NFC

format. Both 2

- d imensional bar code and NFC have the capacity to convey this data

allowing a wide range of devices to display or produce a boarding pass with encoded

data

.

1.1.2 USE OF ELECTRONIC (MOBILE) DEVICE BOARDING PASS

The Bar Codes presented here are designed fo r use on an electronic (mobile) boarding

pass. These Bar Codes should be able to be displayed by all modern electronic (mobile)

devices and to have the screen display optimized . Airport Bar Code Readers should be

able to read the printed Bar Codes as well as the electronic (mobile) presented

symbologies. The digital signature only applies to electronic (mobile) boarding passes.

The data can be stored either in a Bar Code or in an NFC chip. The Bar Codes

presented here are designed for use on an electronic ( mobile) boarding pass. The NFC

format presented here is designed for use on an NFC mobile device. Airport Boarding

Gate Readers should be able to read the mobile Boarding Pass, either Bar Code

symbologies or NCF chip.

.....

### 2.1.1 Bar Code on Printed Boar ding Pass

.....

2.1.2 Bar Code on Electronic (Mobile) Boarding Pass

.....

2.1.3 NFC on Electronic (Mobile) Boarding Pass

The NFC format for Boarding Pass contains structured data as defined in the resolution.

NFC relies on ISO/IEC 14443 to communicate dat a between the mobile device and the

reader. The NFC message contains data that can be used by airlines at their discretion.

2.2 STRUCTURE REQUIREMENTS

This The Bar Code Boarding Pass data format allows for ...

.....

2.3 BOARDING PASS DATA BAR CODE STRUC TURE SPECIFICATIONS

See Resolution 792, Attachment ‘A’.

**Note:** the S format was removed from these specifications in 2007. Therefore carriers

should stop using the S format no later than 1 June 2009

.....

2.8 DATA EXCHANGE OF 2D BAR CODE BOARDING PASS DA TA ELEMENTSB3.3



### Attachment ‘A’

BCBP M FORMAT VERSION 3 4

New Item

number Element description Field size Unique /

Repeated Data

type Formatting Ref

no

23 Baggage Tag License

Plate Number 13 U f As per BSM Specifications

RP1745

The 10 digit bag tag

number, as per BSM

specifications, Reso 740

and 3 digits identifying the

number of consecutive tags p



### Editor’s **note** : Add n ew conditional items “31” and “32”, following item “23”

New Item

number Element description Field

size Unique /

Repeated Data

ty pe Formatting Ref

no

31 1st Non

- Consecutive

Baggage Tag License Plate

Number 13 U f The 10 digit bag tag number,

as per BSM specifications,

Reso 740 and 3 digits

identifying the number of

consecutive tags p

32 2nd Non

- Consecutive

Baggage Tag License Plat e

Number 13 U f The 10 digit bag tag number,

as per BSM specifications,

Reso 740 and 3 digits

identifying the number of

consecutive tags p



### Attachment ‘C’

REFERENCES

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

- p Baggage tag license plate number As per BSM specifications RP1745

A maximum of 3 in stances of consecutive

tags per passenger are able to be encoded

in the Boarding pass Barcode

– see item

23P15



## RECOMMENDED PRACTICE 1008

GLOSSARY OF COMMONLY USED AIR PASSENGER TERMS

PSC( 30 32 )1008

RECOMMENDED that, except as otherwise specifically defined in IATA Resolutions for

use in drafting, applying and interpreting IATA Resolutions, documents and papers, the

following terms be used as hereinafter defined:

Members may consult a comprehensive glossary of definitions, many of them taken

from various IATA publications as shown in Attachment 'A'.

Attachment 'A' is published separately

- refer to “Pas senger Glossary of Terms” in the

“tools” section at: http://www.iata.org/whatwedo/passenger/Pages/index.aspx

Filing Period: Effective Date:

18 April 201 1

- 1 June 2011

23 May 2011

-B3.1



## RECOMMENDED PRACTICE 1701f

SELF SERVICE BAGGAGE PROCESS CHECK

- IN

(amending)

PSC( 31 32 )1701f

**Editor’s note: all current text is deleted and replaced with the following:** 

RECOMMENDED that, when Me mbers plan to offer Self Service Baggage Check

- in capability in a

dedicated or common use environment, for the purposes of individual airline processes, the specification

and standards as described in this Recommended Practice are applied.



### 1. INTRODUCTION/SC OPE

Self Service Baggage describes the specification and standards for self

- service tagging and fast drop off

for passenger checked baggage. Member airlines, handling agents and airports will implement Self

Service Baggage Check

- in to include, but not lim ited to, self

- service baggage functionality. Future

developments may include other functions, both business and technical.



### 2. PURPOSE

The Self

- Service Baggage Check

- in concept is to provide passengers with the ability to prepare their

baggage for acceptance by their airline by one or more of the following options:

- Register their baggage themselves through various self service channels

- Print and apply their own tags

- Deliver the bags to a recognizable fast bag drop off location for acceptance

The major benef its of Self

- Service Baggage Check

- in are:

- Extending customer control throughout the journey

- Enhancing customer experience

- Improve operational planning for the airline

- Faster processing time

- Allows agents to add value by focusing on exceptions and passeng ers with special needs.

- Optimize the use of airline and airport facilities



### 3. DEFINITIONS

The following definitions are detailed below to allow for a common understanding of the terms used in this

document.

3.1. Passenger Baggage Registration

The process by wh ich a passenger informs an airline of the number of bags the passenger intends to

check

- in.3.2. Self tagging

An airline or handling agent offering, via a self

- service channel, the ability to print bag tags for application

by the passenger.

3.3. Baggage Acceptance and Induction

The process by which an airline accepts and transports over its services all baggage as provided herein.

Reference RP 1780e Annex ‘’A’’

– Article 2

– Baggage Acceptance

3.4. Fast Bag Drop

A recognizable location for the purpose of baggage acceptan ce, following a completed check

- in.

3.5. Automated Fast Bag Drop

A recognizable, unassisted location for the purpose of baggage acceptance in a dedicated or common

use environment, and may include a self

- service check

- in capability.

3.6. Common Use Fast Bag Drop

A r ecognizable location for the purpose of baggage acceptance that services multiple airlines

simultaneously.

3.7. Process Steps

Self Service Baggage Process can be implemented with several possible touch points. An

Implementation Guide for Self Service Baggage C heck

- in will describe these various possibilities.

Note: The use of the term ‘Fast’ is intended to promote the concept of speed and not to refer to any

specific branding by any airline.



### 4. SELF SERVICE BAGGAGE PROCESS

4.1. Baggage Registration Process

The proce ss by which an airline is informed of the number of bags a passenger intends to check

- in

through available self service check

- in channels prior to printing the baggage tags.

4.1.1. License Plate generation:

It is recommended that license plates are generated t o meet IATA Resolution 740 Attachment B

- at this

stage and added into the BCBP as per IATA Resolution 792 which meets baggage receipt requirements

(see 4.3.4.4 below)

4.1.2. Messaging:

It should be noted that if baggage messages are generated, they may not b e desirable in the environment

before baggage labels are printed. See RP1745 for all baggage messaging details.

4.2. Self Tagging Process

The process by which an airline offers the ability for a passenger to print and apply their bag tags. This

process could take place at the airport or at any offsite location.

4.2.1. Bag Tag Status:At time of printing, the bag tag status should be inactive as per IATA RP 1745, which identifies the bag

tag as not approved to travel.

4.2.2. Messaging:

At the point of bag tag printi ng, the BSM should be sent with an inactive status as per IATA RP 1745.

An Implementation Guide for Self Service Baggage Check

- in will describe these various possibilities.

4.2.3. Baggage Tag Specifications:

The baggage tag used for self tagging process should be compliant with IATA Resolution 740 and 1740a

with:

4.2.3.1. Identification / Claim data:

It is recommended that the bag tag used for self tagging at a Self Service kiosk should not include any

removable identification/claim portion as optionally offered in Re solution 740. This will facilitate the

application of the tag by the passenger.

4.2.3.2. CUSS:

It is recommended that the same baggage tag stock is used for dedicated and CUSS environment.

4.2.3.3. Bag tag design:

It is recommended that the bag tag used at a self tagg ing process point be as simple as possible for the

passenger to apply. This should include clear and simple instructions indicated at the back of the bag tag.

4.2.3.4. Stock in Self

- service Kiosks:

Bag tag stock capacity should be maximized, e.g., through the use of fan folded stock.

4.3. Acceptance Process

The process to be used by an airline or agent contracted by the airline, offering a recognizable

acceptance point, as indicated at 3.4, 3.5 & 3.6, for the purpose of baggage processing in a dedicated or

common us e environment.

4.3.1. Eligibility :

To be eligible to use a Fast Bag Drop position requires that:

- The passenger has already checked

- in via a self

- service channel.

- The passenger is in possession of a boarding token that contains an airline defined unique id entifier that

can be matched to the passenger’s baggage information

- Where self

- tagging is offered, the passenger has printed and applied the bag tags to the bags.

4.3.2. Exceptions

There may be exceptions from the above stated group of eligible passengers due to local regulations.

Such exceptions should be advised to the passenger at the time of bag registration as outlined at 4.1

above.

4.3.3. Fast Bag Drop Specification

To facilitate the Fast Bag Drop process, the position:

- Should integrate appropriate equipmen t to read the boarding token presented and bag tags if already

applied to the bag

- Should integrate a scale that is interfaced to the workstation to allow for any individual airline process.

- Should integrate a bag tag printer, a boarding pass printer, a travel document scanner for specific

airline/airport requirements and exceptions processing, unless locally and mutually agreed upon.

Various implementations may be possible and will be described in the Self Service Baggage Process

Implementation Guide to be developed.4.3.4. Fast Bag Drop Process Description

4.3.4.1. The passenger approaches the Fast Bag Drop position with the baggage already

tagged and presents their boarding token to the agent. As specified in 4.3.2 there may

be exceptions when the baggage tags are to be printed at the Fast Bag Drop location

4.3.4.2. The boarding token should be read, followed by the bag tags to reconcile the bags

with the passenger.

4.3.4.3. If reconciliation is successful, the baggage can be inducted into the Baggage

Handling Systems (BHS).

- In duction point should be at the same location as the Fast Bag Drop.

In this instance:

Baggage Messaging is updated to show an active status and the baggage is

inducted. A Baggage Process Message (BPM) should be sent to the airline

system to confirm ind uction.

- For operational reasons, the induction point may be at a different location to

Fast Bag Drop. It is not recommended to utilize a different location for acceptance

and induction of the bag. Such situations should be exceptions where operational

o r regulatory circumstances do not otherwise allow.

In this instance:

Baggage messaging is updated to show a validated status, and the passenger

proceeds to the induction point with the baggage. At the induction point,

authorized personnel will verify th at the airline has validated that the baggage is

deemed acceptable to induct. If so, the BSM is updated to show an active status

and the baggage is inducted. A BPM should be sent to the airline system to

confirm induction. It is noted that the .S validated decision reflects airline

business rules

4.3.4.4. Should a separate or new receipt be required, it should be generated at the Fast Bag

Drop position where the baggage is validated by the airline.

The receipt data can be provided to the passenger in various for ms such as:

 Information provided on the boarding token. If baggage information on the

original boarding token differs from baggage information at Fast Bag Drop, a new

boarding token should be generated.

 Information provided on a separate receipt which cou ld be in a paper or

electronic format.

4.3.5. Fast Bag Drop Optional Processes for efficiency

4.3.5.1. Bag tags printed at Fast Bag Drop location. Bag tags may need to be generated at

the Fast Bag Drop location to address local requirements.

4.3.5.2. Document Check. It is rec ommended to offer Self Service Document Check as per

IATA RP 1701d. Document Check may be required at the Fast Bag Drop location to

address local requirements.

4.3.5.3. Excess Baggage / Individual airline baggage policies.It is recommended that the Fast Bag Drop process provides the capability to verifying

the baggage allowance according to individual airline policies.

4.3.5.4. Fee calculation and collection

In case of excess baggage, it is preferred that calculation of the fee and payment

related to such excess is perf ormed as early in the process as possible.

Excess baggage payment can be offered at a different location or at the Fast Bag

Drop location.

Where excess baggage payment is offered at the Fast Bag Drop location e.g. in the

case of an Automated Fast Bag Dro p, the payment process should be subject to the

relevant financial regulations.

4.3.5.5. Oversize and out of gauge baggage

For operational reasons it is recommended to process oversize and out of gauge

baggage outside of the self service process.

4.3.6. Fast Bag Drop Va riations

4.3.6.1. Automated Drop Off

A fast bag drop position may be automated and/or unassisted.

It is recommended that individual airline business rules and processes are applied at the Automated Fast

Bag Drop position.

4.3.6.2. Common Use Fast Bag Drop

A fast ba g drop position may be operated on a common use basis. A Common Use Fast Bag Drop

position will offer a Fast Bag Drop service to multiple airlines passengers simultaneously (single queue,

multiple airlines).

It is recommended that individual airline busin ess rules are applied at the Common Use Fast Bag Drop

location.

A Self Service Baggage Check

- In Implementation Guide will address implementation issues related to

Common Use Fast Bag Drop and Automated Fast Bag Drop.



### 5. END TO END MESSAGING AND INTERFACE TO AIRLINES’ SYSTEMS

5.1. End to End Messaging

See RP 1745 for baggage messaging examples to use.

5.2. Interface to airlines’ systems

It is recommended that the interface between airport systems and the airline host system is handled

through existing IATA messagin g standards.



### 6. SIGNAGE

It is recommended that the following signage/icons are used by member airlines, airports or handling

agents to advertise the simplified self

- service process availability at the airport.

This will create awareness, consistent passeng er experience and help penetration of the service globally.

.

### 7. GLOSSARY OF TERMS

ABS : Automated Baggage System

The generic term used to describe an automated system that uses the LPC in conjunction with the

messages defined i n the RP1745. Example BRS, BSS, etc to be defined

BCBP

– Bar Coded Boarding Pass

BOARDING TOKEN

– The Boarding Token is the token by which a passenger can get access to an

aircraft. The Boarding Token can be a BCBP (bar

- coded boarding pass of paper or mo bile), Machine

Readable Travel Documents (Passports, Visas, ID Cards), passenger biometrics, frequent flyer cards,

etc.

BPM

– Baggage Processed Message. The Baggage Processed Message is a collection of data showing

the loading status of baggage, its last known location and destination

BSM

– Baggage Source Message. The Baggage Source Message is sent by departing carrier from its

Departure Control or Check

- In System, or that of its handling agent, to the operator of an Automated

Baggage System at the point of departure.

BSS

- Baggage Sortation System

. An ABS that routes a bag to a handling location based on defined

sorting criteria.

BTM

– Baggage Transfer Message. Provides a receiving carrier at a transfer station with the details of all

baggage on an inco ming flight that is to be transferred to the receiving carrier's services by the delivering

carrier. A BTM only needs to be sent when baggage data has not been previously passed as part of a

through check

- in transaction.

LICENCE PLATE

– A unique ten digit number for each baggage tag. It serves to identify the respective

piece of baggage in automated sortation, reconciliation, and at delivery upon arrival, or when tracing in

the event of mishandling.

LPC

- License Plate Concept. The industry standard for A utomated Baggage Handling enables the

identification of a single bag by its License Plate Number (unique ten digit number, as defined in

ATA/IATA RESO 30.35/740 and ATA/IATA RESO 30.69/769, commonly called “tag number”) and the

access to data relevant to t he processing of that bag.

LPN

- Licence Plate Number. The LPN serves to identify the respective piece of baggage in Automated

Baggage System (ABS) and Departure Control Systems (DCS) and acts as a key to access the data

exchanged in Baggage Information M essages as

defined in RP1745.

MRTD

- Machine Readable Travel Document (e.g., passport, visa). Official document issued by aState or Organization which is used by the holder for international or domestic travel (e.g. passport, visa,

official document of i dentity), as defined in ICAO 9303. The MRTD contains mandatory visual (eye

readable) data and a separate mandatory data summary, intended for global use, reflecting essential data

elements capable of being machine read.

Unique Identifier

- An airline defi ned data to match boarding token with the passenger’s baggage

information. Examples could include sequence number or airline security number.

REFERENCES

IATA Passenger Services Conference and ATA Passenger Council Resolutions

IATA ATA ACI

740 30.35 Form of interline Baggage Tag

792 30.205 Bar coded Boarding Pass (BCBP)

1740a 30.42 Baggage Tag Media Quality Guidelines

1740c 30.40 Radio Frequency Identification (RFID) Specifications for

Interline Baggage

1745 30.45 Baggage Information Messa ges

1746 30.76 Baggage System Interface

1797 30.201 500A07 Common Use Passenger Processing Systems (CUPPS)

1800 30.49 Automated Baggage Handling based the IATA License

Plate Concept



### Filing Period: Effective Date:

18 April 20 11

- 1 June 2011

23 May 2011

-

## RECOMMENDED PRACTICE 1707

STANDARD SYMBOLS FOR DESCRIPTION OF STANDARD MESSAGE

FORMATS

B7.6/P



### PSC( 30 32 )1707

2.10 Length of Message

The length of a message includes all elements from the Address Elem ent, Communications

Reference Element, through the Text Elements, up to and including End of Message Element.

The maximum number of characters (including spaces, letter and figure shifts, carriage returns

and

line

- feeds) of which a message may be composed is governed by the IATA Systems and

Communications Reference Manual.

A name element and all of its related elements are not to be broken over Parts in any DCS

message.

end of part ENDPART10

2.11 End of Message

Due to length restrictions, a message ma y have to be transmitted in parts:

Construction Example Format

2.11.1 End of Single Part message ENDPTM < ≡ aaaaaa

2.11.2 End of Part in a Multi

- Part message ENDPART10 < ≡ aaaaaaaf(f)(f)

2.11.3 end End of final part message ENDPNL < ≡ aaaaa a

ENDADL < ≡ aaaaaa



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RECOMMENDED PRACTICE 1707b

DATA ELEMENT DIRECTO RY FOR DCS PASSENGER MESSAGES

B7.5/P



### PSC( 31 32 )1707b

.....

3.40.2 API DOCO E lement

This element lists Passenger other travel related information. Where the components of a

DOCO element provided, an oblique (/) is inserted to indicate an element is missing. This is not

required when no further components are provided.

Constructio n Example Data Field Name

3.40.2.1 element ID .R/ element ID

.... .... .... 3.40.2.8 travel document type V a(a)

3.40.2.9 oblique / information separator

3.40.2.10 visa travel document number 9891404 m[.. 15 25 ]

3.40.2. 11 oblique / information separator

3.40.2.12 visa travel document place of issue LONDON a(..35)

3.40.2.13 oblique / information separator

3.40.2.14 visa travel document issue date 12JUL64 date/full

3.40.2.15 oblique / information separator



### .....

B7.1/P



### 4. 1 A passenger name on any DCS message shall appear in the same format as it first

appeared on the PNL/ADL. Names cannot be broken over one line of 64 characters. Therefore,

if a complete Name Element cannot fit on one line of a DCS message, it can be truncated

according to individual message RP rules. Names cannot be re

- formatted (such as using only a

first initial instead of a full first name).

B7.6/P



### 4. 2 A Name Element and all of its related elements are not to be broken over Parts in any DCS

message.B7.2/P



### 4. 3 A Party/Group Identification (See RP 1707, 2.9.2) is assigned uniquely for one DCS

message, for one use. The Identification for a “set” of names can be different on each

subsequent list (such as first D2, t hen M2, then A2). The Identification’s purpose is to keep

names associated for their appearance on just one message. Furthermore, if a “set of names”

appears more than once on one message, each appearance of the “set of names” is to have a

unique Party/ Group Identification. Example: when a “set of names” appears on one ADL in the

section for Deletes and then again for Adds, such as:

ADL

.... DEL

1JONES/ARTHUR

- D3 .L/382U22

1MILLER/JON

- D3

1SMITH/ANN

- D3

..... ADD

1MILLER/JON

- E2 .L/382U22

1SMITH/ANN

- E2

....

This example shows clearly that a PNR of three (D3) are associated for the Delete, and that a

PNR of two (E2) remains for the Add.

B7.9/P



### 4. 4 When adding a Group PNR to a PNL or ADL, the size of the group and the total number of

named indivi dual group members must be equal. The number used in the party/group identifier

must be equal on the Group Name Element and each of the Name Element(s) for the individual

group members. For example, on the PNL/ADL, a Group PNR of 50 must have a total of 50

individual names (and NONAMES) , and the party/group identifier must be 50 for the Group

Name Element and each of the individual Name Elements.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-B7. 2/P



## RECOMMENDED PRACTICE 1708

PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS

LIST (ADL)

PSC( 31 32 )1708

2.6 ADL Elements

... 2.6.1.6.2 Delete some, but not all, passengers in a PNR:

Original entries on the PNL: DEL entry on ADLs:

PNR of two: Delete only Mr. Tournon , with DEL and ADD :

1BARTIENTOS/ALANMR

- C2 .L/FESW5W/TP DEL

1TOURNON/AMR

- C2 .R/VGML 1BARTIENTOS/ALANMR

- C2 .L/FESW5W/TP

1TOURNON/ALFREDMR

– C2 .L/FESW5W/TP

ADD

1BARTIENTOS/ALANMR .L/FESW5W/TP



### Note **1 :**  In order to dele te....

**Note 2** : The name BARTIENTOS/ALANMR does not have a Party/Group Identification because

it appears alone in the ADD section, with no other name to which it is associated.

Editor : Add this new paragraph after 2.6.4.3, and re

- number subsequent paragra phs.

2.6.4.4 Example of a cancellation in RES of one/some (but not all) of the passengers in a PNR

when the PNR has multiple surnames.

The PNL showed the PNR for Smith, Wong and Jones as:

....

- JMS12F

.... 1JONES/ROBERTMR

- R3 .L/T5G246

1SMITH/ANNAMRS

- R3 .L/T5G246

.... 1WONG/SANDRAMS

- R3 .L/T5G246

....

- JMS 23Y

....

Later, after the PNL has been sent, SMITH cancels her booking in RES. An ADL is sent

showing:

Note: The Party/Group Identification is different on the DEL (A3) and the ADD (B2), allowing

the proper re

- association in DCS of the new set of active names in the PNR.

### DEL

1JONES/ROBERTMR

- A3 .L/T5G246

1SMITH/ANNAMRS

- A3

1WONG/SANDRAMS

- A3

ADD

1JONES/ROBERTMR

- B2 .L/T5G246

1WONG/SANDRAMS

- B2

2.6 ADL ELEMENTS

The elements for delete (DEL), add (ADD), and change (CHG) are for use only on an ADL.

These elements are the headers, by destination and compartment, for ADL messages, which

alter the passenger information sent previously on PNLs or ADLs. These three elements always

appear on an ADL by destinatio n and compartment, in the sequence DEL, then ADD, then

CHG, and each appears on an ADL only if it has passenger entries.

2.6.4.6 Example of an upgrade in RES:

The PNL showed:

...

- MSP03F

......

- MSP73Y

1MACKIE/IANMR .L/CDE1RY/BA

Mr. Mackie has a change of cla ss and status in RES, so the ADL shows an ADD (under the new

compartment total) and a DEL (under the original compartment total):

Note: Mr Mackie appears in the ADD section before the DEL due to the destination and

compartment sequence.

...

- MSP04F

ADD

1 MACKIE/IANMR .L/CDE1RY/BA .R/RQST HK1 2A

......

- MSP72Y

DEL

1MACKIE/IANMR .L/CDE1RY/BA

....

2.6.4.7 Example of a divided PNR due to an upgrade in RES of one passenger:

....

.... Mr. Swann has requested an upgrade for Mrs. Swann. The PNR is divided and the fol lowing

ADL is sent.

Note: Mrs. Swann appears in the ADD section before the DEL due to the destination and

compartment sequence.

...

- ATL14F

....B7.15/P



### 2.12.6.3(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

Eleme nt ID

SSR code..... PCTC SSR/OSI/AUX code

oblique (mandatory) / information separator

space

- > information separator

contact name (if provided........

....

Examples:

**(Note to Editor : Please note that in the examples below, after the code PCTC, one** 

**oblique is being replaced by one space.)**

2AHARA/JOSEPHMR/KENDRAMRS

.R/PCTC / JOHN DOE/US1123456789/PHONE OF UNCLE AFTER 7PM

... 2ANDERS/ARNOLDMR/BEAMRS

- A10

.R/PCTC / BEVERLY TRAVEL/NL31205551234/SECRETARY MS HANSON

.RN/

- 1ANDERS/ARNOLDMR .R/PCTC / /R EFUSED

- 1ANDERS/BEAMRS

... 1ROTZKE/CARLYMS

- A10 .R/PCTC / WIZARD OF OZ/US12125551212

... 2SALINAS/RAYMR/JANEMRS .R/PCTC / /

- 1SALINAS/RAYMR

.R/PCTC / PETE SALINAS/MX123456789X123

- 1SALINAS/JANEMRS

... 1TURNIP/DAVEMR .R/PCTC / /REFUSED

B7.3/P



### 2.12.6.4(c) Constructio n rules for SSR INFT Occupying a Seat

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

....

.... Examples:

.R/INFT HK1 14JAN05 R

- 1NELSON/NICKMSTR

3BOND/PATMS/TIMMR/RICKMSTR .R/INFT HK1 14JAN09 R

- 1BOND/RICKMSTRB7 .12/P

R5 /R6



### 2.12.7 Table of SSR Codes

.... B7.13/P



### ESAN Emotional support/psychiatric assistance animals. Passenger with

emotional support / psychiatric assistance animal in cabin. Specify

details. Medical prescription required

.... SVAN Service ani mals. Passenger with Service animal in cabin. Specify details

.... WCBD Wheelchair ( dry cell non

- spillable battery): to be transported by a

passenger which may will require advance notification / and may require

preparation/(dis)assembly. Weight and dime nsions may be specified

(required for use only by/between U.S. carriers) (by bilateral agreement)

WCLB Wheelchair

– Lithium ion battery to be transported by a passenger which

will require advance notification/preparation. Weight and dimensions may

be sp ecified. Wheelchair and battery must be claimed and rechecked at

each interline transfer point (by bilateral agreement)

WCBW Wheelchair (wet cell battery): to be transported by a passenger which

may will require advance notification / and may require pre paration or

(dis)assembly. Weight and dimensions may be specified. Wheelchair and

battery must be claimed and rechecked at each interline transfer point

(required for use only by/between U.S. carriers) (by bilateral agreement)

.... WCMP Wheelchair (manua l power): to be transported by a passenger. Weight

and dimensions may be specified (required for use only by/between

U.S. carriers) (by bilateral agreement)

WCOB Wheelchair (on

- board): provided by airline (required for use

onlyby/between U.S. carriers) ( by bilateral agreement) 48 hours advance

notice recommended but not required.

B7.14/P



### 2.12.8

Code Description

CHD (discontinued 31May2008 to allow for a transitional period) Child,

preceded by number of child(ren), as fCHD. For example: 3C HD

DIPL...

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-B7.7/P



## RECOMMENDED PRACTICE 1715

PASSENGER SERVICE MESSAGE (PSM)

PSC( 30 32 )1715

2.6 SSR/OSI/AUX CODES AND COUNTS ELEMENT

2.6.5 Followi ng are the allowable SSR/OSI/AUX codes....

.....

MEDA Medical Case

MEQT Medical Equipment (to be used for airline or government

authorized medical equipment)

Filing Period: Effective Date:

18 April 2011

- 1 June 201 1

23 May 2011

-B7.4/P



## RECOMMENDED PRACTICE 1719d

TICKETLESS PRODUCT LIST (TPL)

PSC( 30 32 )1719d

Section 3

— Examples

3.1 EXAMPLE OF A TPL WITH NAMES AND BAGGAGE DETAILS, PRESENT FOR

SOME DESTINATION/COMPARTMENTS, BUT NOT ALL

CPHFFQI

.S GDRQQI 151422

TPL

QI798/15MAR SGD PART1

....

.... 1BANANA/CAMERONMISS .L/3246MH/IB .R/ETLP HK1 123R9W393D939

2MINT/GINA/UNA .L/346834/IB .R/ETLP HK2 12T356W566K66

1MINT/GINA .L/346834/IB .R/ETLP HK1 12T356W566K66

1MINT/UNA .L/346834/IB .R/ETLP HK1 12T356W5 66K66

1PINEAPPLE/MARIE .L/32J454/IB .R/ETLP HK1 1238F898G9898

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-1720a P5

P5.1 

## RECOMMENDED PRACTICE 1720a

STANDARD THIRTEEN

- DIGIT NUMBERING SYSTE M FOR

TRAFFIC DOCUMENTS

(amending)

PSC( 31 32 )1720a

....

Stock Provider

Party Type of Form No. of

Coupons IATA

Resolution /

Recommended

Practice ATA

Resolution Airline

Code

1 2 3 Form Code

4 5 6 Serial Number

7 8 9 10 11

12 13 Number

of

Digits in

Serial

Number Method of

Check Digit

Calculation

(see below)

...

Agency (US

ASP) 1

, 2

, 8 ATB Automated

MCO &

Electronic

Miscellaneous

Charges Order Coupon

by

- Coupon - - - 20.102

20.61 - - - 1 9 6

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 ATB Automated

MCO &

Electronic

Miscellaneous

Charges Order Coupon

by

- Coupon - - - 20.102

20.61 - - - 1 9 6

- - - - - - - - - 7 3

Reserved for

future industry

allocation

Agency

(BSP) 1, 2 Not assigned

Virtual M ultiple

Purpose

Document Paperless 302 7 Not

assigned

2

Reserved for

future industry

allocation

Agency

(BSP) 1, 2 Not assigned

ATB

Miscellaneous

Charges Order 725d 304 7 Not

assigned

3

Agency (US

ASP)1,2, 8 Automated

Miscel laneous

Charges Order

& Electronic

Miscellaneous

Charges Order Coupon

by

- Coupon - - - 20.102

20.64 - - - 5 0 5

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Automated

Miscellaneous

Charges Order

& Electronic

Miscellaneous

Charges Order Coupon

by

- Coupon - - - 20.102

20.64 - - - 5 0 5

- - - - - - - - - 7 3

Reserved for

future industry

allocation

Agency

(BSP) 1, 2 Not assigned

Off

- Premise

Electronic

Ticket (OPET) 722g 550 7 Not

assigned

3

1 Computer generated ticket serial number. All other passenger traffic documents have a preprinted ticket

serial number.

2 Standard neutral tic ket. Airline name and code are not preprinted.

8 Effective through December 31, 2010.

9 Effective January 1, 2011.... Agency (US

ASP) 1,2, 8 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 0

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 0

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 8 E lectronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 1

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 1

- - - - - - - - - 7 3

Agency (US

A SP) 1,2, 8 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 2

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 2

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 8 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 3

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 3

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 8 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 4

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 2 0.102

20.64 - - - 8 1 4

- - - - - - - - - 7 3

Agency (US

ASP)1,2, 8 Electronic

Miscellaneous

Document Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 5

- - - - - - - - - 7 3

Agency (US

ASP) 1,2, 9 Electronic

Miscellaneous

Document

ATB Automated

Miscellaneous

Charge s Order Coupon

- by

- Coupon - - - 20.102

20.64 - - - 8 1 5

- - - - - - - - - 7 3

Reserved for

future industry

allocation

Agency

(BSP) 1, 2 Not assigned

Off

- Premise

Electronic

Ticket (OPET) 722g 906 7 Not

assigned

3

Reserved for

fu ture industry

allocation

Agency (BSP) Not assigned

Off

- Premise

Electronic

Ticket (OPET) 722g 952 7 Not

assigned

3



### Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

### RESOLUTION 1721

NETTING F OR EXCHANGE / REISSUE TRANSACTIONS

(amending)

T2.34/P



### PSC( 30 32 )1721

...

4.1.6 Applying Exchange Value Towards Fare and TFCs

Once fare and TFC values eligible for exchange are determined, the steps below, in

compliance with IATA TFC Composite Resolutio n 024e, outline how to process the

exchange transaction.

4.1.6.1 Calculate the new fare in the currency of COC. If currency of COC is different

than currency of exchange, convert fare from COC currency to currency of exchange by

the current bankers rate o f exchange.

4.1.6.1.1 If the currency of payment is the same as the currency of exchange, subtract

eligible exchange value from new ticket fare amount. If the currency of exchange is

different from the currency of payment, convert the fare in the currency of exchange of

the new ticket to the currency of payment by the current banker’s rate of exchange and

subtract eligible exchange value from the new ticket fare amount in the currency of

payment

.

Filing Period: Effective Date:

18 Apri l 2011

- 1 June 2011

23 May 2011

-

## RECOMMENDED PRACTICE 1745

BAGGAGE INFORMATION MESSAGES

PSC( 31 32 )1745

B10

1.1 PURPOSE

This Recommended Practice governs Baggage Information Messages, which are sent between

departure control systems a nd Automated Baggage Handling systems. The messages are sent,

received and processed by those systems in order to achieve automated baggage sortation,

passenger and baggage reconciliation, and other baggage services. How these messages are

applied within t hese baggage processes is specified in IATA RP1800/ATA RP30.49 'Automated

Baggage Handling based on the IATA License Plate Concept'.

Baggage information included in these messages is linked with the unique 10

- digit bag tag

number defined as the License Plate Code (refer to IATA Resolution 740; ATA 30.35).

This 10 digit License Plate Code is a unique reference to a specific bag.

The Baggage Handling System that receives this 10 digit License Plate Code in a baggage

message, shall store this reference unc hanged in the system and will communicate about this

reference in a unchanged manner to other Baggage Handling Systems.

When the bag is reflighted in respect of resolution 740, resolution 743 and RP1800 , an expedite

label may be used, but with a reference to the original License Plate Code.

B8.16/P

........ 1.6 DELETE FUNCTION

The DEL function should be used to delete, or mark a record as deleted on the outbound flight(s) and

conditionally on the onward flights (.F, conditionally .O). (See 4.9.3 for an exa mple of the DEL function.) A

tag number that has been deleted may be reused for the same passenger for the same flight and date.

See Section 1.9 for Processing Of Duplicate Tag Numbers.

Examples:

a. Where a bag tag is issued in error and the bag has not been introduced into an automated baggage

system.

b. Where a tag number was incorrectly manually entered. c. Where a passenger checked 2 bags and

decides to take one of them as hand baggage.

d. When a passenger's itinerary (.F) changes for flight/date info rmation for any reason after baggage

check

- in, the latest BSM data must first be deleted and a new BSM sent.

e. When a BTM has been previously sent for an itinerary that is no longer current, a BTM DEL should be

sent.Use Elements And Data Items Examp le

(M) Baggage Source Indicator T

(M) Local, Transfer or Terminating Airport Code ZRH

(N) Part Number /

— show only oblique; no data

(C) Message Reference Number /1234567890

(O) Acknowledgement Request /A

(O) Encryption /123ABC456Z

(O) MESSAGE ACKNOWLEDGEMENT DETAILS

(M) Element Identifier .A

(M) Sender's Message Reference Number /BA2190123

(M) Type of Baggage Message and Status Indicator /BRQ

being acknowledged

(M) ACK or NAK /NAK

(O) Free Text / COPY TAG

(C) OUTBOUND FLIGHT INFORMATION

(M) Element Identifier .F

(M) Airline and Flight Number /SR101

(M) Date /16APR

(M) Destination Or Transfer Airport Code /JFK

(O) Class Of Travel Of Baggage /J

(C) INBOUND FLIGHT INFORMATION

(M) Element Identifier .I

(M) Airline and Flight Number /AZ318

(M) Date Of Departure /16APR

(M) Originating Airport Code /FCO



### ( O) Class Of Travel Of Baggage /J

(C) ONWARD FLIGHT INFORMATION

(M) Element Identifier .O

(M) Airline a nd Flight Number /UA203

(M) Date /16APR

(M) Destination Or Transfer Airport Code /DEN

(O) Class Of Travel Of Baggage /J

(C) BAGGAGE TAG DETAILS

(M) Element Identifier .N

(M) Baggage Tag Number /0085123456 (C) Number of

Consecutiv e Tags 003

(M) HANDLING LOCATION

(M) Element Identifier .H

(C) Handling Terminal /T4

(C) Handling Bay/Pier /GREEN

(C) Handling Gate/Stand /D46

(C) PASSENGER NAME

(M) Element Identifier .P

(M) Separator (oblique) /

(O) Numb er Of Passengers With This Surname 2

(M) Passenger's Surname SMITH

(O) Given Name and/or Initials and/or Title /TOMMR

(O) Additional Given Name and/or Initials and/or Title /ALICE(C) FREQUENT TRAVELLER NUMBER

(M) Element Identifier .Y

(M) F requent Traveler ID Number /KL662503

(O) Tier Information /GOLD

(C) CORPORATE OR GROUP NAME

(M) Element Identifier .C

(M) Corporate Or Group Name /IATA TOUR

(C) AUTOMATED PNR ADDRESS

(M) Element Identifier .L

(M) Automated PNR Add ress /XY1C3P

(C) BAGGAGE TAG PRINTER ID

(M) Element Identifier .T

(M) Bag Tag Printer ID /321A4C

(C) BAGGAGE EXCEPTION DATA

(M) Element Identifier .E

(M) Exception Type / CPY

(M) END OF MESSAGE IDENTIFIER ENDBRQ



### B8.17/P

...

2.1.1 Within each message section, elements and data items are shown as either mandatory,

conditional, optional, not applicable in relation to the processes described in RP1800, or

not used.

• Mandatory (M)

- shall be included in the message.

• Condit ional (C)

- shall be included in the message if specified conditions are met.

• Optional (O)

- may be included at the discretion of the sender.

• Not Applicable (N/A)

– considered not applicable for the message. In the case of

legacy use, involved systems may ignore elements and data items.

• Not Used (N)

- data item is shall not be used.

...

## RECOMMENDED PRACTICE 1745

BAGGAGE INFORMATION MESSAGES

B 8.9/P

2.2 QUICK REFERENCE INDEX OF BAGGAGE INFORMATION MESSAGE ELEMENTS

- VERSION 1

N/A

– should not force compan ies to change the program of baggage message to get rid of an element

Element

dentifier Title Examples Messages

BT

M BS

M BP

M BU

M BN

S BC

M BC

M

BA

M BC

M

FO

M BC

M

FC

M BC

M

FM

M BC

M

DB

M BM

M BRQ

Standard Message

Identifier (SMI) BTM, BSM, BPM, BUM, BNS, BCM

, BMM M M M M M M M M M M M M M

Secondary Level

Message Identifier BAM, FOM, FCM, FFM, DBM N/A N/A N/A N/A N/A N/A M M M M M N/A N/A

Change of Status

Indicator CHG or DEL C C N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

.A Message

Acknowledgement

Detai ls .A/QF006097/BSM/ACK or N/A N/A N/A N/A N/A

* M N/A N/A N/A N/A N/A O

N/A

.B Baggage Irregularities .B/OFF/0220123456001 N/A N/A C N/A N/A

* N/A N/A N/A C N/A C

N/A N/A

.C Corporate or Group

Name .C/SITA TOUR O O O O C

* N/A N/A N/A N/A N/A O O C

.D B ag Check in Details .D/TRST/QQP/07MAY/0845L/RA/TR

AINS OR O C O C O C N/A N/A N/A N/A N/A N/A N/A N/A N/A C N/A

.E Baggage Exception Data .E/RUSH O C O C C O C N/A

C * N/A N/A N/A N/A N/A C C

.F Outbound Flight

Information .F/LH1274/05MAY/JFK/F M C C M M

* N/A M M M M C C

.G Ground Transport .G///MARRIOT Alphen ad Rijn or

.G//25NOV2200/Willem de Zwijger

laan 234 alphen ad Rijn O O C O C N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

.H Handling Location .H/T4//16 or .H //GREEN or .H///D46 O O C O C O C O

* N/A O N/A N/A N/A O M C

.I Inbound Flight

Information .I/KL067/02APR/AMS/Y C M C O C O C N/A

* N/A N/A N/A N/A N/A M CElement

dentifier Title Examples Messages

BT

M BS

M BP

M BU

M BN

S BC

M BC

M

BA

M BC

M

FO

M BC

M

FC

M BC

M

FM

M BC

M

DB

M BM

M BRQ

.J Processing Information .J/R/43S/120D32/02APR/1545L/B2 N/A N/A O C N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

.K Default Message Printer .K/ 69C626 N/A O

N/A O

N/A O

N/A N/A

* N/A N/A N/A N/A N/A O

N/A N/A

.L Automated PNR Address .L/QRE7Q6 O

N/A O

N/A C

N/A O

N/A C

N/A N/A N/A N/A N/A N/A N/A C

N/A C N/A

.M UNUSED N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

.N Baggage Tag Detail s .N/0001123456002 M M C M M

* N/A N/A N/A N/A N/A C M C

.O Onward Flight

Information .O/UA423/02APR/DEN/F C C O C O C C

* N/A N/A N/A N/A N/A O C C

.P Passenger Name .P/1SMITH/HMR M C O C C C

* N/A N/A N/A N/A N/A C C

.Q Load Sequence Number .Q/023 N/A N/A C C N/A

* N/A N/A N/A N/A N/A C N/A

.R Internal Airline Data .R/FREE TEXT O O O O O

* O O N/A N/A N/A O N/A

.S Reconciliation Data .S/Y/23A/C234/333/Y/Y/A N/A C O C O C N/A N/A N/A N/A N/A N/A N/A O N/A

.T Baggage Tag Printer ID .T/221322 N/A

O O N /A

C N/A N/A N/A N/A N/A N/A N/A N/A N/A C

.U Loading Data .U/AVE12345NE/11R/T/Y/NRT/Y/NW

009/04MAR/SEL N/A N/A O C O C N/A N/A N/A N/A N/A N/A N/A C N/A

.V Version and

Supplementary Data .V/1TYYZ/PART1/1234567890/A M M M M M M M M M M M M M

.W Pieces We ight,

Dimensions and Type

Data .W/K/2/38/8 or .W/L/2/84/16 or

.W/P/3 or

.W/K/1/14//CM/68/54/26/02HWX O O N/A

O N/A O

N/A * N/A N/A N/A N/A N/A C N/A

.X Baggage Security

Screening .X/LEVEL1;

.X/HANDSEARCH;.X/XRAY, etc O C O C O C O N/A

* N/A N/A N/A N/A N/A C N/A

.Y Frequent Traveler

Number .Y/BXJ2238 or .X/BXJ2238/GOLD O O O O

N/A C

N/A * N/A N/A N/A N/A N/A O

N/A C

.Z UNUSED N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

End of Message Identifier ENDBTM, ENDBSM, ENDBPM, etc. M M M M M M M M M M M M M



### * Refer to each individual message for detailsB8.3/P



### ...

2.3.13 .J Processing Information ; 9 characters minimum; 55 characters maximum

Construction Example Format

2.3.13.1 Element Identifier: full stop (.), 'J' .J .a

2.3.13.2 Separa tor: oblique (/) / /

2.3.13.3 Secondary code R a

G=Ground Tracking, R=Reconciliation,

S=Sortation, H=Hand Scanner

... B8.2/P



### ... Example Format

2.3.22.17 Baggage Tag Status I A

‘I’ = Inactive, ‘A’=Active, ‘ V’=Validated

... B8.1/P



### 2.3.24 .U Loading Data ; 8 to 53 characters

Construction Example Format

2.3.24.1 Element Identifier: full stop (.), 'U' .U a

2.3.24.2 Separator: oblique (/) / /

2.3.24.3 Stowage Device ID AVE1234 5NW ammffff(f)mm(a)

2.3.24.4 Separator: oblique (/) / /

2.3.24.5 Aircraft Compartment or Loading Location 11R mm(mmm)

2.3.24.5 Aircraft Compartment or Loading Location 11R m (m mmm)

- maximum of 5 characters



### B8.22/P

.....B8.4/P



### 2.3.24 .U Loading Data; 8 to 5 3 60 characters

Construction Example Format

Construction Example Format

2.3.24.1 Element Identifier: full stop (.), 'U' .U a

2.3.24.2 Separator: oblique (/) / /

2.3.24.3 Stowage Device ID AVE12345NW ammffff(f)mm(a)

2.3.24.4 Separator: oblique (/) / /

2.3.24.5 Aircraft Compartment or Loading Location 11R mm(mmm)

2.3.24.5 Aircraft Compartment or Loading Location 11R m (m mmm)

- maximum of 5 characters



### B8.2 2/P

..... 

### 2.3.24.20 Separator: oblique (/) / /

2.3.24.21 Container Handling Type up to 6 8 characters PRIO m(m..m)

2.3.24.2 0 2 End of element delimiter < ≡ Examples:

.U/AVE1234NW/11R/T/Y/NRT/Y/NW009/04MAR /SEL <≡

.U//AFTRT/X/F/DEN<≡

.U///T//MIA//AA614<≡

.U/CAR1357KL//M<≡

.U/AVE1234NW/11R/M/Y/NRT/SORT

.U/AKH2345AF//S/M/Y/FCO/1R <≡

**Note:** The description for the Stowage Device ID AMMFFFF(F)MM(A) has to be read as

AMMFFFF(F)MM or AMMFFFF(F)AAA.



### B8.19/ P

Section 3

Section 3.2.4

“BTM’s must be sent to the receiving carrier host system upon flight departure or close out,

whereby the receiving carrier should immediately generate BSM’s to the affected BRS/BHS,

unless a local BSM has already been generated through IATCI, two step through check

- in or

because the BTM was sent late.”

BTMs must be sent to the receiving carrier’s host system no later than flight departure only

when through check

- in has failed or is not available. The receiving carrier must immed iately

process the BTM received and generate the BSM/T to the affected ABS . If through check

- in is

successful, a BSM will have been generated through the IATCI request and no BTM should be

sent. If the BTM is received after a BSM has already been generat ed, any processing of the

BTM must not lead to a new BSM being generated transfer for the passenger locally checked in.B8.10/P

... 

### 3.5 Element Sequence Summary

The following shows the sequence of elements in a BTM.

Element Requirement Definition

BT M Mandatory Standard Message Identifier

DEL Conditional Change of Status Indicator

.V Mandatory Version and Supplementary Data

.I Mandatory Inbound Flight Information

.F Mandatory Outbound Flight Information

.H Optional Handling Location

.N Ma ndatory Baggage Tag Details

.D Optional Conditional Baggage Check

- in Details

.W Optional Pieces, Weight, Dimensions and Type Data

.O Conditional Onward Flight Information

.P Mandatory Passenger Name

.G Optional Ground Transport

.Y Optional Fre quent Traveler Number

.C Optional Corporate or Group Name

.L Optional Automated PNR Address

.T Optional Baggage Tag Printer ID

.E Optional Conditional Baggage Exception Data

.R Optional Internal Airline Data

.X Optional Conditional Baggage Secu rity Screening

ENDBTM Mandatory End of Message Identifier

3.6 MULTIPLE USE OF ELEMENTS

...

The following schematic illustrates the multiple use of elements in the BTM:

.I

- Inbound Flight (BA185)

.F

- Connecting To Flight (US6745)

.N

- Baggage Ta g Details (for passenger #1 in .P element)

.N

- Baggage Tag Details (additional bag for same passenger)

.D

- Baggage Check

- in Details

.W

- Pieces and Weight Data

.O

- Onward Flight

.O

- Onward Flight

.P

- Passenger Name #1 (associated to .N el ement)

.Y

- Frequent Traveler Number

.C

- Corporate or Group Name

.L

- Automated PNR Address

.T

– Baggage Tag Printer ID

.E

- Baggage Exception Data

.E

- Baggage Exception Data

.R

- Internal Airline Data

.R

- Internal Airline Data

.X

- Baggage S ecurity Screening

.N

- Baggage Tag Details (for passenger #2 in .P element)

### .P

- Passenger Name #2 (associated to .N element)

.C

- Corporate or Group Number

.L

- Automated PNR Address

.T

– Baggage Tag Printer ID

.N

- Baggage Tag Details (for passenger #3 in .P element)

.P

- Passenger Name #3 (associated to .N element)

.C

- Corporate or Group Name

.L

- Automated PNR Address

.T

– Baggage Tag Printer ID

.X

- Baggage Security Screening

.F

- Connecting To Flight (US996)

- new outbound fl ight

.N

- Baggage Tag Details (for passenger # 4in .P element)

.D

- Baggage Check

- in Details

.W

- Pieces and Weight Data

.O

- Onward Flight

.O

- Additional Onward Flight

.P

- Passenger Name (associated to .N element)

.L

- Automated PNR Address

.T

– Baggage Tag Printer ID

.F

- Connecting to Flight (US111)

- new outbound flight

.N

- Baggage Tag Details (for passenger in .P)

.O

- Onward Flight

.P

- Passenger Name (associated to .N element)

See 3.9.5 for an example of multiple usage in a BTM.

3.7 USE OF CONDITIONAL ELEMENTS AND DATA ITEMS

...

3.7.6 Baggage Check

- in Details (.D)

The .D element becomes mandatory when the data is available.

3.7.7 Baggage Exception Data (.E)

The .E element becomes mandatory when the data is available.

3 .7.8 Baggage Security Screening (.X)

The .X element becomes mandatory when the data is available.

### 3.8 CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BAGGAGE TRANSFER

MESSAGE

... (M) OUTBOUND FLIGHT INFORMATION

(M) Element Identifier .F

(M) Airline and Flight Number /UA1234D

(M) Date /02APR

(M) Destination or Transfer Airport Code /DEN

(O) Class of Travel of Passenger /J

(O) HANDLING LOCATION

(M) Element Identifier .H

(C) Handling Terminal /T4

(C) H andling Bay/Pier /GREEN

(C) Handling Gate/Stand /D46

(M) BAGGAGE TAG DETAILS

(M) Element Identifier .N

(M) Baggage Tag Number /0074123456

(M) Number of Consecutive Tags 003

( M C ) BAGGAGE CHECK

- IN DETAILS

(M) Eleme nt Identifier .D

(M) Bag Check

- in Location Identifier /HOTC

(O) Bag Check

- in Location Description /Marriott

(M) Bag Check

- in Date /08May

(M) Bag Check

- in Time /0800L

(O) Carriage Medium /HV

(O) Transport ID /VAN379HJT

(M ) PASSENGER NAME

(M) Element Identifier .P

(M) Separator (oblique) /

(O) Number of Passengers with this Surname 2

(M) Passenger ' s Surname SMITH

(O) Passenger ' s Given Name and/or Initials and/or

Title (if available) /TOMMR

(O) Additional Given Names and/or Initials/Titles /ALICE

(O) GROUND TRANSPORT

(M) Element identifier .G

(O) Earliest Delivery date/time /25NOV1600

(O) Latest Delivery date/time /25NOV2200

(M) Address / Location Descriptio n /Address

(O) FREQUENT TRAVELER NUMBER

(M) Element Identifier .Y

(M) Frequent Traveler ID Number /KL662503

(O) Tier Information Identifier GOLD

(O) CORPORATE OR GROUP NAME

(M) Element Identifier .C

(M) Corporate o r Group Name /IATA TOUR

### (O) AUTOMATED PNR ADDRESS

(M) Element Identifier .L

(M) Automated PNR Address /6Y21AS

(O) BAGGAGE TAG PRINTER ID

(M) Element Identifier .T

(M) Bag Tag Printer ID /321A4C

( O C ) BAGGA GE EXCEPTION DATA

(M) Element Identifier .E

(M) Exception Type /RUSH

(O) INTERNAL AIRLINE DATA

(M) Element Identifier .R

(M) Free Text /FREE TEXT

(C) BAGGAGE SECURITY SCREENING

(M) Element Identi fier .X

(O) Baggage Security Screening Instruction /SEL

(O) Security Screening Result /CLR

(O) Security Screening Result Reason /T

(O) Security Screening Method /XRAY

(O) Autograph /SECURITY

(O) Free text /TRANSFER

(M) END OF PART

or END OF MESSAGE IDENTIFIER ENDPART1 or ENDBTM

Use Elements and Data Items Example

(O) BAGGAGE SECURITY SCREENING

(M) Element Identifier .X

(O) Baggage Security Screening Instruction /SEL

(O) S ecurity Reason Result /CLR

(O) Security Screening Reason Result /T

(O) Security Screening Method /XRAY

(O) Autograph /SECURITY

(O) Free text /TRANSFER

End of Element Delimiter < ≡ Example: .Y/BJX2238< ≡

**Note:** Only o ne bag (and one .N element, accordingly) is used per .W element, when

dimensions are specified.

### 3.9 EXAMPLE MESSAGES

...

3.9.2 Single Connection With Passenger Information

Description

BTM< ≡ Message identifier

.V/1TORD< ≡ Transfer baggag e for ORD

.I/KL318/16APR/AMS/J< ≡ Inbound from AMS on KL318; J

- Class

.F/UA423/16APR/DEN/F< ≡ Transfer to UA423 to DEN; F

- Class

.N/0074123512002< ≡ 2 Bags starting with 0074123512

.P/SMITH/TOMMR< ≡ Passenger’s name

.L/XY1C3P< ≡ PNR Addr ess

.R/LATE CONX

- AMS< ≡ Internal airline data

.X/SEL< ≡ Baggage Security Screening

ENDBTM< ≡ End of Message Identifier

3.9.3 Type

- B Message; Expedite (RUSH) Baggage Details, With Acknowledgement

Request

Description

ORDBTUA< ≡ Sent to Address

AMSKMKL 311800< ≡ Senders Address

BTM< ≡ Standard Message Identifier

.V/1TORD//1234567890/A/123ABC456Z< ≡ Transfer in ORD; message ack requested

with Encryption

.I/KL318/16APR/AMS/J< ≡ Inbound from AMS on KL318; J

- Class

.F/UA061/16APR/IAH/Y< ≡ Transferring to UA061 to IAH; Y

- Class

.N/2074999777001< ≡ 1 Bag tag; number 2074999777

.P/RUSH< ≡ Passenger name: 'Rush'

.E/RUSH< ≡ Expedite baggage identification

ENDBTM< ≡ End of Message Identifier

3.9.4 Example of Partitioned Message with Multiple Connecting Flights

Description

BTM< ≡ Standard Message Identifier

.V/1TORD/PART1< ≡ Transfer in ORD; Part

- 1

.I/KL067/02APR/AMS/J< ≡ Inbound from AMS on KL

- 67, J

- Class

.F/UA423/02APR/DEN/F< ≡ A. Bags transferring to DEN on UA423, F

- Class

.N/0074123456005< ≡ 1. Tag numbers: 0074123456

- 60

.O/UA897/02APR/SEA/F< ≡ a. Onward to SEA on UA897; F

- Class

.O/UA972 /03APR/ANC/Y< ≡ b. Then onward to ANC on UA972; Y

- Class

.P/PLEIJSIER/JANMR< ≡ c. Passenger name: Pleijsier

.L/H67XT4< ≡ d. PNR Address

.X/SEL< ≡ e. Screening De scription

.N/0074287163001< ≡ 2. Tag number: 0074287163

.W/K/1/34/5< ≡ a. Baggage Weight Data

### .O/UA881/02APR/LAX/F< ≡ b. Onward to LAX on UA881; F

- Class

.P/ERICKSON/TMR< ≡ c. Passenger name: Erickson

.L/TZ491A< ≡ d. PNR Address

.X/NON< ≡ e. Screening Description

.N/0074987654001< ≡ 3. Tag number: 0074987654

.N/0074987657003< ≡ Tag numbers: 0074987657

- 59

.W/K/4/73< ≡ a. Baggage Weight Data

.O/UA441/02APR/IAD/C< ≡ b. Onwa rd to IAD on UA441; C

- Class

.O/UA077/02APR/MIA/Y< ≡ c. Then onward to MIA on UA77; Y

- Class

.P/BOGGS/J< ≡ d. Passenger name: Boggs

.L/B116AJ< ≡ e. PNR Address

ENDPART1< ≡ End of Part

- Identifier

BTM< ≡ Standard Message Identifier

.V/1TORD/PART2< ≡ Transfer in ORD; Part

- 2

.I/KL067/02APR/AMS/J< ≡ Inbound from AMS on KL67; J

- Class

.F/UA002/02APR/SAN/Y< ≡ B. Bags trans ferring to SAN on UA002, Y

- Class

.N/0074283928002< ≡ 1. Tag numbers: 0074283928

- 29

.W/K/2/80/15< ≡ a. Baggage weight data

.P/ADELMAN/JACK< ≡ b. Passen ger name: Adelman

.R/SKIS< ≡ c. Internal Airline Data

.X/SEL< ≡ d. Screening Description

.F/UA532/02APR/SFO/Y< ≡ C. Bag transferring to SFO on UA532;Y

- Class

.N/0074312465001< ≡ 1. Tag number: 0074312465

.W/L/1/39/15< ≡ a. Baggage weight data

.P/2SCHUT/JMR/MMRS< ≡ b. Passenger name: Schut

.L/K3R1MT< ≡ c. PNR Address

ENDBTM< ≡ End of Message Identifier

### 3.9.5 Example of Multiple Usage

**Note:** Example is based on Section 3.6.

Description

BTM< ≡ Standard Message Identi fier

.V/1TEWR< ≡ Transfer baggage at EWR

.I/BA185/04FEB/LHR/F< ≡ Inbound flight BA185 from LHR; F

- Class

.F/US675/04FEB/PIT/F< ≡ A. Connecting to US675 to PIT; F

Class

This would be the first .F element

(transfer to flight). All the elements

between this .F and the next .F are

associated to this .F (flight). There

must be at least one .N element

before the next .F element.

.N/0125455911001< ≡ 1. .N element identifies baggage for

passenger Martin.

.N/0125455917002< ≡ 2. 2 additional bags for passenge r

Martin. (All the elements between

this .N and the next .N are

associated to these .N’s)

.W/P/3 a. Pieces and weight information:

Total 3 pieces of luggage.

.O/UA407/04FEB/ORD/F< ≡ b. Onward flight information; F

- Class

.O/UA5392/04FEB/MKE/Y< ≡ c. Additional onward flight; Y

- Class

.P/1MARTIN/J< ≡ d. Passenger’s name

.Y/BA296891/GOLD< ≡ e. Frequent traveler number

.C/SUNSHINE TOURS< ≡ f. Corporate or group name

.L/J94HR1< ≡ g. PNR Address (only one per

passenger)

.E/TOUR< ≡ h. Exception data

.E/VIP< ≡ i . Multiple occurrences of the .E element

.R/FREE TEXT< ≡ j. Internal airline data

.R/MORE FREE TEXT< ≡ k. Multiple occurrences of the .R

element

.X/NON< ≡ l. Screening description; se lect passenger cleared

The next .N element identifies baggage

data for next passenger who is also

connecting to the flight identified in the

initial .F element.

.N/0125455621004< ≡ 3. .N element identifies baggage for

passenger Thomas

.P/1THOMAS/R< ≡ a. Passenger ' s name

.C/GLOBE< ≡ b. Corporate or group name

.L/RY6CPV< ≡ c. PNR address

The next .N element identifies baggage data for

next passenger who is also connecting to the

flight identified in the initial .F

element.

### .N/01258699200001< ≡

4. .N element identifies baggage

data for passenger Jones

.P/1JONES/T< ≡ a. Passenger's name

.C/GLOBE< ≡ b. Corporate or group name

.L/RY6CPV< ≡ c. PNR address

X/SEL< ≡ d. Screening description

The next .F element identifies the second

connecting flight for inbound BA185 and

the

.Ns that follow are associated to this .F.

.F/US996/04FEB/DCA/Y< ≡ B. Connecting flight US996 to DCA; Y

Class

.N/0125456011017< ≡ .N element identifies baggage for

passenger

Snyder

. W/P/17< ≡ 1. Pieces and weight; Total 17 pieces

of luggage

.O/US1034/04FEB/MIA/Y< ≡ 2. Onward flight information; Y

- Class

.O/US7577/05FEB/GIG/Y< ≡ 3. Additional onward flight; Y

- Class

.P/SNYDER/R< ≡ 4. Passenger’s name

.L/Y6UW4H< ≡ 5. PNR address

The next .F element identifies the second connecting flight for inbound BA185 and

the .Ns that follow are associated to

this .F.

.F/US111/04FEB/MCO/Y< ≡ C. Connecting flight US111 to MCO; Y

- Class

.N/0125 214953002< ≡ .N element identifies baggage for

P assenger Alonzo

.O/MX693/05FEB/MEX/Y< ≡ 1. Onward flight information; Y

- Class

.P/1ALONZO/R< ≡ 2. Passenger's name

ENDBTM< ≡ End of Message Identifier

### 3.9.6 Example of BTM to delete a record in a sortation or reconciliation system at

JFK by SR

B8.21/P

Section 3.9.6

BTM

DEL

.V/1TJFK////123ABC4567

.I/SR101/18APR/JFK/C

.F/DL671/18APR/ATL/C

.N008512 3457001

.S/N

ENDBSM

BTM

DEL

.V/1TJFK////123ABC4567

.I/SR101/18APR/JFK/C

.F/DL671/18APR/ATL/C

.N0085123457001

ENDBTM

B8.10/P

3.9.7 Example of BTM on involuntary itinerary change (IROP)

Original BTM sent at flight close

- out

BTM<= Standard Messag e Identifier

.V/1TORD<= Transfer baggage at ORD

.I/UA958/01APR/DEN/Y<= Inbound from DEN on UA 958

.F/LH431/01APR/FRA/Y<= Transfer to LH 431 to FRA

.N/0016444010001<= 1 Bag Tag; number 0016444010

.P/LOWRY/K Passenger Name: Lowry

ENDBTM End of Message Ide ntifier

BTM DEL sent at PNR cancel

BTM<= Standard Message Identifier

DEL<= Change of Status Indicator.V/1TORD<= Transfer baggage at ORD

.I/UA958/01APR/DEN/Y<= Inbound from DEN on UA 958

.F/LH431/01APR/FRA/Y<= Transfer to LH 431 to FRA

.N/0016444010001 <= 1 Bag Tag; number 0016444010

.P/LOWRY/K Passenger Name: Lowry

.E/IROP Indicator for irregular operation and

involuntary re

- routing

.E/UNAC Unaccompanied baggage

.E/RRTE Indicator for re

- routing

ENDBTM End of Message Identifier

BTM sent at PNR cancel rebook

BTM<= Standard Message Identifier

.V/1TORD<= Transfer baggage at ORD

.I/UA248/01APR/DEN/Y<= Inbound from DEN on UA 248

.F/LH433/01APR/FRA/Y<= Transfer to LH 433 to FRA

.N/0016444010001<= 1 Bag Tag; number 0016444010

.P/LOWRY/K Passenger Name: Lowr y

.E/IROP Indicator for irregular operation and

involuntary re

- routing

.E/UNAC Unaccompanied baggage

.E/RRTE Indicator for re

- routing

.E/STCK Indicator to update routing

information on the baggage tag

ENDBTM End of Message Identifier

...

3.9.9 Example of BTM in the Intermodal Receipt/Intermodal Delivery Process

BTM<= Standard Message Identifier

.V/1TORD Transfer baggage at ORD

.I/YY1234/01APR/ZYR/Y Inbound from train station ZYR on

YY1234

.F/KL753/01APR/CUR/M Transfer to KL 753 to CUR

.N/001644401 0001 1 Bag Tag; number 0016444010

.D/TRST/QQP/07MAY/084512L Bag Checked in at Train Station;

Date; Time

.P/LOWRY/K Passenger Name: Lowry

.T/321A4C Printer ID

ENDBTM End of Message Identifier

### Section 4

- BAGGAGE SOURCE MESSAGE (BSM)

B8.20/P

Section 4.2.3

“When through check

- in facility is not available, upon receipt of a BTM, the receiving carrier may translate

the BTM data into a BSM and send it to the automated baggage system. (Refer to section 3 for BTM

specifications). When a BTM is received after local/through check

- in the BSM generated from that BTM

should not be sent. When a BSM generated from a BTM is received by a baggage handling system

(BHS) after the reception of a local BSM, the BHS should ignore the BSM which is generated from the

B TM.”

When a through check

- in facility has failed or is not available, the receiving carrier must immediately

process the BTM received and generate the BSM/T to the affected ABS . If through check

- in is

successful, a BSM will have been generated through the IATCI request and no BTM should be sent. If the

BTM is received after a BSM has already been generated, any processing of the BTM must not lead to a

new BSM being generated for the transfer passenger locally checked in.



### B8.11/P

...

4.5 Element Sequence S ummary

The following shows the sequence of elements in a BSM.

Element Requirement Definition

BSM Mandatory Standard Message Identifier

CHG or DEL Conditional Change of Status Indicator

.V Mandatory Version and Supplementary Data

.F Conditional Outbound Flight Information

.I Conditional Inbound Flight Information

.O Conditional Onward Flight Information

.N Mandatory Baggage Tag Details

.D Optional Conditional Check

- in Location Information

.S Conditional Reconciliation Data

.H Opt ional Conditional Handling Location

.W Optional Pieces, Weight, Dimensions and Type Data

.P Conditional Passenger Name

.G Optional Conditional Ground Transport ; Delivery address

.Y Optional Frequent Traveler Number

.C Optional Corporate or Group Name

.L Optional Automated PNR Address

.T Optional Baggage Tag Printer ID

.K Optional Default Message Printer

.E Optional Conditional Baggage Exception Data

.R Optional Internal Airline Data

.X Optional Conditional Baggage Security Scre ening

ENDBSM Mandatory End of Message Identifier

### 4.6 MULTIPLE USE OF DATA ELEMENTS

Multiple use of elements may be accomplished by following the structure of the BSM and the

sequencing of elements. The primary elements are the .F element (Outbound Flight Information) the

.N element (Baggage Details), and the .I element (Inbound Flight Information) for a terminating or

transfer BSM. The structure of the mandatory and conditional elements depends on whether the BSM

is for an originating, transfer or terminating flight. Optional elements, which are related to mandatory

elements are inserted in the order shown in 4.5. The .V element may occur once however elements

.O, .N, .P, .E and .R may be repeated multiple times, but only .O, .N, .E and .R may be used

consecutively.

The following schematic illustrates the multiple use of elements in a BSM.

Element Description

.F Outbound Flight (LAX

- NRT)

.I Inbound Flight (ORD

- LAX)

.O Onward Flight (NRT

- SIN)

.O Onward Flight (SIN

- SYD)

.N Baggage Tag Details

.N Baggage Tag Details

.S Reconciliation Data

.W Pieces and Weight Data

.P Passenger Name

.G Ground Transport; Delivery address

.G Remainder of delivery address

.Y Frequent Traveler Number

.C Cor porate or Group Name

.L Automated PNR Address

.T Baggage Tag Printer ID

.K Default Message printer

.E Baggage Exception Data

.R Internal Airline Data

.R Internal Airline Data

.X Baggage Security Screening

...



### 4.7.7 The P ieces And Weight Data element (.W)

The Number of Checked Bags is mandatory if using the Checked Bag Weight option.

4.7.8 Bag Check In Details (.D)

The .D element becomes mandatory when the data is available.

4.7.9 Baggage Exception Data (.E)

The .E elem ent becomes mandatory when the data is available.

4.7.10 Ground Transport (.G)

The .G element becomes mandatory when the data is available.

4.7.11 Handling Location (.H)

The .H element becomes mandatory when the data is available.

4.7.12 Baggage Securit y Screening (.X)

The .X element becomes mandatory when the data is available.

### 4.8 Construction of Elements and Data Items in the Baggage Source Message

Use Elements And Data Items Example

(M) STANDARD MESSAGE IDENTIFIER BSM

(C) CHANGE OF STA TUS INDICATOR DEL or CHG

(M) VERSION AND SUPPLEMENTARY DATA

(M) Element Identifier .V

(M) Data Dictionary Version Number /1

(M) Baggage Source Indicator T

(M) Local, Transfer or Terminating Airport Code ZRH

(N) Part Number

– show only oblique; no data /

(C) Message Reference Number /1234567890

(O) Acknowledgement Request /A

(O) Encryption /123ABC456Z

(C) OUTBOUND FLIGHT INFORMATION

(M) Element Identifier .F

(M) Airline and Flight Number /SR101

(M) Date /16APR

(M) Destination or Transfer Airport Code /JFK

(O) Class of Travel of Baggage /J

(C) INBOUND FLIGHT INFORMATION

(M) Element Identifier .I

(M) Airline and Flight Number /AZ318

(M) Dat e of Departure \ /16APR

(M) Originating Airport Code /FCO

(O) Class of Travel of Baggage /J

(O) ONWARD FLIGHT INFORMATION

(M) Element Identifier .O

(M) Airline and Flight Number /UA203

(M) Date /16APR

(M) Destination or Transfer Airport Code /DEN

(O) Class of Travel of Baggage /J

Use Elements And Data Items Example

(M) BAGGAGE TAG DETAILS

(M) Element Identifier .N

(M) Baggage Tag Number /0085123456

(M ) Number of Consecutive Tags 003

( O C ) CHECK IN LOCATION DETAILS

(M) Element Identifier: full stop (.) .D

(M) Bag Check in location Identifier /HOTC

(O) Bag Check in location description /MARRIOTT

(M) Bag Check In date /08MAY

(M) Bag Check in Tim e /0845L

(O) Carriage Medium /HV

(O) Transport ID (Free Text) /FEDEXVAN45

(C) RECONCILIATION DATA

(M) Element Identifier .S(M) Authority To Load /Y

(O) Seat number 10A

(O) Passenger Status /N

(O) Sequence Number /098

(O) Security Number /888

(O) Passenger Profile Status Y

(O) Authority to Transport /Y

(C) Baggage Tag Status /A

(C) HANDLING LOCATION

(M) Element Identifier .H

(C) Handling Terminal /T4

( C) Handling Bay/Pier /GREEN

(C) Handling Gate/Stand /D46

(O) PIECES AND WEIGHT DATA

(M) Element Identifier .W

(M) Pieces/Weight Indicator /K

(C) Number of Checked Bags /2

(O) Checked Weight /38

(O) Unchecked Weight /5

(C) Unit /CM

(O) Length of the bag /68

(O) Width of the bag /54

(O) Height of the bag /24

Use Elements And Data Items Example

(O) Baggage type code /02HWX

(C) PASSENGER NAME

(M) Element Id entifier .P

(M) Separator (oblique) /

(O) Number of Passengers With This Surname 2

(M) Passenger’s Surname SMITH

(O) Given Name and/or Initials and/or Title /TOMMR

(O) Additional Given Name and /or Initials and/or Title /ALICE

( O C ) GROUND TRANSPORT ; 10 to 26 characters

(M) Element identifier .G

(O) Earliest Delivery date/time /25NOV1600

(O) Latest Delivery date/time /25NOV2200

(M) Address / Location Description /Address

(O) FREQUENT TR AVELER NUMBER

(M) Element Identifier .Y

(M) Frequent Traveler ID Number /KL662503

(O) Tier Information Identifier /GOLD

(O) CORPORATE OR GROUP NAME

(M) Element Identifier .C

(M) Corporate Or Group Name /IATA TO UR

(O) AUTOMATED PNR ADDRESS

(M) Element Identifier .L

(M) Automated PNR Address /XY1C3P(O) BAGGAGE TAG PRINTER ID

(M) Element Identifier .T

(M) Bag Tag Printer ID /321A4C

(O) DEFAULT MESSAGE PRINT ER

(M) Element Identifier .K

(M) Baggage Message Default Printer ID /3D1C08

( O C) BAGGAGE EXCEPTION DATA

(M) Element Identifier .E

(M) Exception Type /RUSH

(O) INTERNAL AIRLINE DATA

(M) Element Identifier .R

(M) Free Text /DELAYED INBOUND

( O C ) BAGGAGE SECURITY SCREENING

(M) Element Identifier .X

(O) Baggage Security Screening Instruction /SEL

(O) Security Reason Screening Result /CLR

(O) Security Screening Reason Result Reason /T

(O) Security Screening Method /XRAY

(O) Autograph /SECURITY

(O) Free text /TRANSFER

(M) END of MESSAGE IDENTIFIER ENDBSM



### 4.9 Example Messages

4.9.1 BSM with minimum ele ments for sortation

BSM< ≡ Standard Message Identifier

.V/1TZRH< ≡ Version; Transfer bag at ZRH

.F/SR101/18APR/JFK/F< ≡ Outbound carrier & flight; Date; Destination; Class

.N/0085123456003< ≡ Bag tag number; Number of Consecutive Tags

ENDBSM< ≡ End of Message Identifier



### 4.9.2 Type 'B' Message

- Sent to a sortation and reconciliation system in ZRH by SR.

ZRHBSSR ZRHBRXH< ≡ Address of sortation (BS) and reconciliation (BR)

,HDQKMSR 311800< ≡ Signature of sender of message

BSM< ≡ Standard Message Identifier

.V/1TZRH//6543210014/A/123ABC456Z< ≡ Version; Transfer bag at ZRH; Ref. Number; Ack

Req. with Encryption.

.F/SR101/18APR/JFK/F< ≡ Outbound carrier & flight; Date; Destination; Class

.I/AZ318/18APR/FC O/J< ≡ Inbound carrier & flight; Date; Originating airport;

class

.N/0085123456003< ≡ Bag tag number; Number of Consecutive Tags

.S/Y/3A/C< ≡ Reconciliation data; Auth to load; seat 3A, ck'd in

.P/SMITH/TOM< ≡ Passenger Name

.L/XY 1C3P< ≡ Automated PNR Address

.T/321A4C< ≡ Printer ID

.E/RUSH< ≡ Rush Bag

.R/VIP< ≡ Internal airline data

.X/XRAY< ≡ Screening Description

ENDBSM< ≡ End of Message Identifier

### 4.9.3 Example of BSM To Delete a record in a sortation or reconciliation system at ZRH

by SR

BSM< ≡ Standard Message Identifier

DEL< ≡ Delete Function

.V/1LZRH////123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/SR101/18APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N /0085123457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S/N< ≡ Reconciliation data: Auth. to load=No

ENDBSM< ≡ End of Message Identifier



### 4.9.4 Example of BSM to delete a record in a sortation or reconciliation system at JFK

by SR

BSM< ≡ Standard Message Identifier

DEL< ≡ Delete Function

.V/1TJFK////123ABC456Z< ≡ Version; Transfer bag at JFK with Encryption

.F/SR101/18APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.O/SR1234/18APR/ATL/C< ≡ Onward connection

.N/0085123457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S/N< ≡ Reconciliation data: Auth. to load=No

ENDBSM< ≡ End of Message Identifier



### 4.9.5 Example of a BSM for re

- routing process

BSM< ≡ Standard Message Identifier

.V/1LZRH//// 123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/SR101/18APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/0085123457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S/Y< ≡ Reconciliation data: Auth. to load=Yes

ENDBSM < ≡ End of Message Identifier

BSM< ≡ Standard Message Identifier

DEL< ≡ Delete Function

.V/1LZRH////123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/SR101/18APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/0085123 457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S/N< ≡ Reconciliation data: Auth. to load=No

.E/IROP< ≡ Indicator for irregular operation and involuntary

re

- routing

.E/UNAC Unaccompanied baggage

.E/RRTE< ≡ Indicator for re

- routing

EN DBSM< ≡ End of Message Identifier

BSM< ≡ Standard Message Identifier

.V/1LZRH////123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/LH4210/18APR/JFK/Y< ≡ Carrier/Flight Number; Date; Destination; Class

.N/0085123457001< ≡ Bag Tag Numb er; Number of Consecutive Tags

.S/Y//////Y< ≡ Reconciliation data: Auth. to load=Auth. To

Transport=Yes

.E/IROP Indicator for irregular operation and involuntary

re

- routing

.E/UNAC< ≡ Unaccompanied baggage

.E/RRTE Indicator for re

- routing

.E/STC K Indicator for re

- tagging instruction

ENDBSM< ≡ End of Message Identifier4.9.6 Example of a BSM for re

- flighting process

BSM< ≡ Standard Message Identifier

.V/1LZRH////123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/SR101/1 8APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/0085123457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S/Y< ≡ Reconciliation data: Auth. to load=Yes

ENDBSM< ≡ End of Message Identifier

BSM< ≡ Standard Messag e Identifier

DEL< ≡ Delete Function

.V/1LZRH////123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/SR101/18APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/0085123457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S /N/< ≡ Reconciliation data: Auth. to load=No

.E/MIS< ≡ Indicator for mishandled baggage

ENDBSM< ≡ End of Message Identifier

BSM< ≡ Standard Message Identifier

.V/1LZRH////123ABC456Z< ≡ Version; Local bag at ZRH with Encryption

.F/LH4210 /18APR/JFK/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/0085123457001< ≡ Bag Tag Number; Number of Consecutive Tags

.S/Y//////Y< ≡ Reconciliation data: Auth. to load=Auth. To

Transport=Yes

.E/RUSH Indicator for rush baggage

.E/STCK Indicator for re

- tagging instruction

ENDBSM< ≡ End of Message Identifier

4.9.7 BSM for terminating bag at PIT for US flight 817 from FRA

BSM< ≡ Standard Message Identifier

.V/1XPIT< ≡ Version; Terminating bag at PIT

.I/US817/05DEC/FRA/J< ≡ Inbound Carrier/Flight; Date; From FRA

.N/5037155090005< ≡ Bag Tag Number & Number of Consecutive Tags

.P/2PAGE/L/B< ≡ Number in party and passenger surname

.L/XSEA7B< ≡ PNR Address

ENDBSM< ≡ End of Message Identifier

4.9.8 Examples of the change function

A. Original BSM:

BSM< ≡ Standard Message Identifier

.V/1LPIT////123ABC456Z< ≡ Version; Local bag at PIT with Encryption

.F/BA197/05DEC/LGW/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/7125123456002< ≡ Bag Tag Number; Numb er of Consecutive Tags

.S/N//S< ≡ Authorization to load=No; Standby passenger

.P/WEIL/W< ≡ Passenger Name

.L/H8J47X< ≡ Automated PNR Address

.T/4F0C32< ≡ Printer ID

.X/XRAY< ≡ Screening Description

ENDBSM< ≡ End of Message Identifier

Change Option #1

- To change the Reconciliation Data Element (.S) and add the Internal Airline Data element (.R)

BSM< ≡ Standard Message Identifier

CHG< ≡ Change of Status Indicator

.V/1LPIT< ≡ Version; Local bag at PIT

.F/BA197/05DEC/LGW/C< ≡ Carrier/Flight Number; Dat e; Destination; Class

.N/7125123456002< ≡ Bag Tag Number; Number of Consecutive Tags.S/Y/3A/C< ≡ Auth. to load=Y; Seat=3A; Passenger checked In

.R/ODD SIZE BAG< ≡ Internal airline data (comments)

ENDBSM< ≡ End of Message Identifier

C. Change Optio n #2

- Full message with Reconciliation Data element (.S) and the Internal

Airline Data element (.R,) added

BSM< ≡ Standard Message Identifier

CHG< ≡ Change of Status Indicator

.V/1LPIT////123ABC456Z< ≡ Version; Local bag at PIT with Encryption

.F/B A197/05DEC/LGW/C< ≡ Carrier/Flight Number; Date; Destination; Class

.N/7125123456002< ≡ Bag Tag Number; Number of Consecutive Tags

.S/Y/3A/C< ≡ Auth. to load=Y; Seat=3A; Passenger checked In

.P/WEIL/W< ≡ Passenger Name

.L/H8J47X< ≡ Automated PNR Address

. T/4F0C32< ≡ Printer ID

.R/ODD SIZE BAG< ≡ Internal airline data (comments)

.X/XRAY< ≡ Screening Description

ENDBSM< ≡ End of Message Identifier



### 4.9.9 Example of BSM with multiple usage of elements

**Note:** The following is an example of a batched BSM conta ining two .F elements.

BSM< ≡ Standard Message Identifier

.V/1TZRH< ≡ Version; Transfer bag at ZRH

.F/SR101/18APR/JFK/F< ≡ 1. Outbound Flight Information

.I/AZ318/18APR/FCO/J< ≡ a. Inbound Flight Information

.N/0085123456002< ≡ 1. Bag tag number & number of bags

.N/0085123473001< ≡ 2. Bag tag number & number of bags

.S/Y/3A/C< ≡ 3. Reconciliation Data

.P/SMITH/TOM< ≡ 4. Passenger Name

.L/XY1C3P< ≡ 5. Automated PNR Address

.T/321A4C< ≡ 6. Printer ID

.F/SR101/18APR/JFK/F< ≡ 2. Outbound Flight Information

.O/DL671/18APR/ATL/C< ≡ a. Onward Connection

.O/DL281/18APR/MYS/C< ≡ b. Onward Connection

.N/008512 3547002< ≡ 1. Bag tag number & number of bags

.N/0085123558002< ≡ 2. Bag tag number & number of bags

.S/Y/3A/C< ≡ 3. Reconciliation Data

.P/BROWN/JIM< ≡ 4. Passenger Name

.L/SAB4KP< ≡ 5. Automated PNR Address

.T/321A44< ≡ 6. Printer ID

ENDBSM< ≡ End of Message Identifier



### 4.9.10 BSM for remote checked in bag from home

BSM < ≡ Standard Message Identifier

.V/1RLHR < ≡ Version; Remote check in for Heathrow

.F/BA952/08MAY/FRA/J, < ≡ Flight details; Date; Destination; Class

.N/5037155090005 < ≡ Bag Tag Number & Number of Consecutive Tags

.D/HOME/TW149NT/07MAY/084502L/CO/ Bag collected from Home; Postcode; Date; Time

FEDEXVAN45 < ≡ Transport Method; Transport Id

.H/T1/CENTRAL/E20 < ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

.P/2PAGE/L/B < ≡ Number in party and passenger surname

.L/XSEA7B < ≡ PNR Address

EN DBSM < ≡ End of Message Identifier

### 4.9.11 BSM for remote checked in bag from Train Station

BSM < ≡ Standard Message Identifier

.V/1RLHR < ≡ Version; Remote check in for Heathrow

.F/BA952/08MAY/FRA/J < ≡ Flight details; Date; Destination; Class

.N/50 37155090005 < ≡ Bag Tag Number & Number of Consecutive Tags

.D/TRST/QQP/07MAY/084512L < ≡ Bag Checked in at Train Station; Date; Time;

.H/HEX/P1/E20 < ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

.P/2PAGE/L/B < ≡ Number in pa rty and passenger surname

.L/XSEA7B < ≡ PNR Address

ENDBSM < ≡ End of Message Identifier



### 4.9.12 BSM for remote checked in bag from a cruise ship at a Port

BSM < ≡ Standard Message Identifier

.V/1RLAX < ≡ Version; Remote Bag at LAX

.F/BA282/07MAY/ LHR/F < ≡ Outbound carrier & flight; Date; Destination; Class

.N/0085123456035 < ≡ Bag tag number; Number of Consecutive Tags (35)

.D/PORT/LXS/07MAY/084512L/CS/ Bag Checked in at Port; Port identifier; Date;

POV23684 < ≡ Time; delivery method to ai rport; VAN id

.S/Y/3A/C < ≡ Reconciliation data; Authority to load; seat 3A, ck'd in

.H/INT/GROUP/46 < ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

.P/SMITH/TOM < ≡ Passenger Name

.C/Royal PRINCESS < ≡ ROYAL PRINCESS

.L/XY1C3P < ≡ Automated PNR Address

.T/321A4C < ≡ Printer ID

.R/CRUISE < ≡ Internal airline data

.X/XRAY < ≡ Screening Description

ENDBSM < ≡ End of Message Identifier



### 4.9.13 BSM for Ground Transport at the destination

BSM< ≡ Standard Message Identifier

.V/ 1XFRA< ≡ Version; Terminating at Frankfurt

.I/BA952/08MAY/LHR/J< ≡ Inbound flight details; Date; origin; class

.N/5037155090005< ≡ Bag Tag Number & Number of Consecutive Tags

.P/2PAGE/L/B< ≡ Number in party and passenger surname

.G///MARRIOT FRANKFURT< ≡ Gr ound Transport (Delivery Address)

.L/XSEA7B< ≡ PNR Address

ENDBSM< ≡ End of Message Identifier

**Note:** It is important to recognize that all 10 digits in the BSM also show on the bag tag. For

example 4.9.5 shows '.N7125123456002' which means that the 2 bag tags actually issued have

numbers 7125 BA 123456 and 7125 BA 123457.



### B8.12/P

### Section 5

- Baggage Processed Message (BPM)

... 5.5 Element Sequence Summary

The following shows the sequence of elements in a BPM.

Element Requirement Definition

BPM Mandatory Standard Message Identifier

.V Mandatory Version and Supplementary Data

.K Optional Default Message Printer

.J Optional Conditional Processing Information

.F Conditional Information

.U Optional Conditional Loading Data

.N Co nditional Baggage Tag Details

.B Conditional Baggage Irregularities

.D Conditional Bag Check

- in Location Details

.Q Conditional Load Sequence Number

.I Optional Conditional Inbound Flight Information

.O Optional Conditional Onward Flight Information

.S Optional Conditional Reconciliation Data

.H Conditional Handling Location

.W Optional Pieces, Weight, Dimensions and Type Data

.P Optional Conditional Passenger Name

.G Conditional Ground Transport

.Y Optional Frequent Traveler Number

.C Optional Corporate Or Group Name

.L Conditional Automated PNR Address

.T Conditional Baggage Tag Printer ID

.E Optional Baggage Exception Data

.R Optional Internal Airline Data

.X Optional Conditional Baggage Secu rity Screening

ENDBPM Mandatory End of Message Identifier5.6 Multiple Use of Elements

Multiple use of elements may be accomplished by following the structure of the BPM, and the sequence of

its elements. The prime element is the .F (Outbound Flight Information). This provides the foundation for

the .U element (Loading Data) and the .N and .B elements (Baggage Details and Baggage Irregularities)

that follow it. As the .U element is optional, a .N or .B element may follow the .F element directly. O ptional

elements which are related to the mandatory elements are inserted in the order shown in 5.5. Except for

the .V, .K, and .J elements, all elements may occur multiple times, but only the. U (see 5.9.4), .N, .B, .O,

.E and .R may be used consecutiv ely. The .D element may only be used in conjunction with the .N element.

The following schematic illustrates the multiple use of elements in the BPM:

Element Description

.K Default Message Printer

.J Processing Information

.F Outbound Fligh t Information

.U Loading Data

.N or .B Baggage Details or Baggage Irregularities

.D Bag Check

- in Location Details (Only in association with .N)

.Q Loading Sequence Number

.I Inbound Flight Information

.O Onward Flight Information

.O Onward Flight Information

.S Reconciliation Data

.H Handling Location

.P Passenger Name

.G Ground Transport

.Y Frequent Traveler Number

.C Corporate or Group Name

.L Automated PNR Address

.T Baggage Tag Printer ID

.E Baggage Exception Data

.E Baggage Exception Data

.R Internal Airline Data

.R Internal Airline Data

N or .B Baggage Details or Baggage Irregularities

.Q Loading Sequence Number

.S Reconciliation Data

.P Passenger Name

.L Autom ated PNR Address

.E Baggage Exception Data

.E Baggage Exception Data

.X Baggage Security Screening

.U Loading Data

.N or .B Baggage Details or Baggage Irregularities

.Q Loading Sequence Number

.S Reconciliation Data

.P Passe nger Name

.L Automated PNR Address

.R Internal Airline data

.R Internal Airline Data

.X Baggage Security Screening

See 5.9.5 for an example of multiple usage in a BPM.

...5.7 Use of Conditional Elements And Data Items

...

5.7.2 Outbound F light Information element (.F)

The .F element is mandatory when used as part of a reconciliation or sortation process. If used for ground

tracking it is optional.

... 5.7.4 The Baggage Tag Details and Baggage Irregularities elements (.N and .B).

Either a .N or .B element must be included for baggage details, conditional on the status of the bag being

reported.

The .N element is used to uniquely identify a specific bag. It becomes mandatory when the data is

available.

The .B element is used to indicate bag gage irregularities. It becomes mandatory when a baggage

irregularity occurs. (see description of the .B element in the Data Dictionary).

The BPM may contain both the .N and the .B element for the same baggage tag number only in the case

of transferring ba ggage from one Load Unit to another.

Where a BPM contains multiple bags, both the .N and .B element may be present.

a. The .N element is used for loaded bags. b.

The .B element is used for bags not loaded due to irregularities.

5.7.5 The Load Seq uence Number element (.Q) is mandatory if the Loading Information element (.U) is

present and used for individual bags. When the Loading Information element (.U) is used for complete

loading units, the Load Sequence Number element (.Q) is not applicable.

... 5.7.7 Bag Check

- in Location Details (.D)

The .D element becomes mandatory when the data is available.

5.7.8 Ground Transport (.G)

The .G element becomes mandatory when the data is available.

5.7.9 Handling Location (.H)

The .H element becomes mandato ry when the data is available.

5.7.10 Inbound Flight Information (.I)

The .I element becomes mandatory when the data is available.

5.7.11 Processing Information (.J)

The .J element becomes mandatory when the data is available.

5.7.12 Onward Flight Infor mation (.O)

The .O element becomes mandatory when the data is available.

5.7.13 Passenger Name (.P)

The .P element becomes mandatory when the data is available.

5.7.14 Reconciliation Data (.S)

The .S element becomes mandatory when the data is available.

5.7.15 Baggage Tag Printer ID (.T)

The .T element becomes mandatory when the data is available.5.7.16 Loading Data (.U)

The .U element becomes mandatory when the data is available.

5.7.17 Baggage Security Screening (.X)

The .X element becomes mandator y when the data is available.

5.8 Construction of Elements And Data Items In The Baggage Processed Message

Use Elements And Data Items Example

(M) STANDARD MESSAGE IDENTIFIER BPM

(M) VERSION AND SUPPLEMENTARY DATA

(M)Element Identifier .V

(M) Data Dictionary Version Number /1

(M) Baggage Source Indicator L

(M) Local or Transfer Airport Code LHR

(O) Part Number /PART1

(C) Message Reference Number /1234567890

( O) Acknowledgement Request /A

(O) Encryption /123ABC456Z

(O) DEFAULT MESSAGE PRINTER

(M) Element Identifier .K

(M) Baggage Message Default Printer ID /3D1C08

( O C ) P ROCESSING INFORMATION

(M) Element Identifier .J

(M) Secondary Code /R

(O) Agent Identification /43S

(O) Scanner Identification /381761

(O) Date /03OCT

(O) Time /054312Z

(O) Reading Location /B4

(O) Sent to Location /R

(C) OUTBOUND FLIGHT INFORMATION

(M) Element Identifier .F

(M) Airline and Flight Number /BA117

(M) Date /03OCT

(M) Destination or Transfer Airport Code /SEL

(O) Class of Travel of Baggage /J

( O C ) LOADING DATA

(M) Element Identifier .U

(O) Stowage Device ID /AVE12345BA

(O) Aircraft Compartment or Loading Location /11R

(O) Type of Baggage in Container/Location / T

(O) Classes of Travel of Baggage /F

(O) Destination or Transfer Airport Code of the Container /SEL

(O) Sealed Container Indicator /Y

(O) Connection Airline Code and Flight Number /NW009

(C) Connection Departure Date /04OCT

(C) Destination or Transfer Airport Code of the Container /NRT(C) BAGGAGE TAG DETAILS

(M) Element Identifier .N

(M) Bag Tag Number /0085123456

(M) Number of Consecutive Tags 002

(C) BAGGAGE IRREGULARITIES

(M) Element Identifier .B

(M) Baggage Status Code /OFF

(M) Baggage Tag Number /0220123456

(M) Number of Consecutive Tags 002

(C) CHECK IN LOCATION DETAIL S

(M) Element Identifier: full stop (.) .D

(M) Bag Check in location Identifier /HOTC

(O) Bag Check in location description /MARRIOTT

(M) Bag Check In date /08MAY

(M) Bag Check in Time /0845L

(O) Carriage Medium /HV

(O) Transport ID (Free Text) / FEDEXVAN45

(C) LOAD SEQUENCE NUMBER

(M) Element Identifier .Q

(M) Load Sequence Number /095

( O C ) INBOUND FLIGHT INFORMATION

(M) Element Identifier .I

(M) Airline and Flight Number /BA178

(M) Date of departure /03OCT

(O) Originating Airport Code /JFK

(O) Class of Travel of Baggage /J

( O C ) ONWARD FLIGHT INFORMATION

(M) Element Identifier .O

(M) Airline and Flight Number /UA203

(M) Date /03OCT

(O) Destination or Transfer Airport Code /DEN

(O) Class of Travel of Baggage /J

( O C ) RECONCILIATION DATA

(M) Element Identifier .S

(M) Authority To Load /Y

(O) Seat Number /10A

(O) Passenger Status /C

(O) Sequence Number /098

(O) Security Number /888

(O) Passenger Profile Status /Y

(O) Authority to Transport /Y

(O) Baggage Tag Status /A

(C) HANDLING LOCATION

(M) Element Identifier .H

(C) Handling Terminal /T4

(C) Handling Bay/Pier /GREEN

(C) Handling Gate/Stand /D46(O) PIECES AND WEIGHT DATA

(M) Element Identifier .W

(M) Pieces/Weight Indicator /K

(C) Number of Checked Bags /2

(O) Checked Weight /38

(O) Unchecked Weight /5

(C) Unit /CM

(O) Length of the bag /68

(O) Width of the bag /54

(O) Height of the bag /24

(O) Baggage type code /02HWX

( O C ) PASSENGER NAME

(M) Element Identifier .P

(M) Separator (oblique) /

(O) Number of Passengers With This Surname 2

(M) Passenger’s Surname GROBE T

(O) Given Name and/or Initials and/or Title /M

(O) Additional Given Name and/or Initials and/or Title 

### /J

(C) GROUND TRANSPORT

(M) Element identifier .G

(O) Earliest Delivery date/time /25NOV1600

(O) Latest Delivery date/time /25NOV2200

(M) Address / Location Description /Address

(O) FREQUENT TRAVELER NUMBER

(M) Element Identifier .Y

(M) Frequent Traveler ID Number /KL662503

(O) Tier Information Identifier /GOLD

(O) CORPORATE OR GROUP NAME

(M) Element Identifier .C

(M) Corporate or Group Name /CITY BALLET

(C) AUTOMATED PNR ADDRESS

(M) Element Identifier .L

(M) Automated PNR Address /L2TVVP

(C) BAGGAGE TAG PRINTER ID

(M) Element Identifier .T

(M) Bag Tag Printer ID /321A4C

(O) BAGGAGE EXCEPTION DATA

(M) Element Identifier .E

(M) Exception Type /GRP

(O) INTERNAL AIRLINE DATA

(M) Element Identifi er .R

(M) Free Text /FREE TEXT AREA

( O C ) BAGGAGE SECURITY SCREENING

(M) Element Identifier .X

(O) Baggage Security Screening Instruction /SEL

(O) Security Reason Screening Result /CLR

(O) Security Scr eening Reason Result Reason /T

(O) Security Screening Method /XRAY

(O) Autograph /SECURITY

(O) Free Text /TRANSFER

(M) END OF PART or

END OF MESSAGE IDENTIFIER ENDPART1 or ENDBPM5.9 EXAMPLE MESSAGES

5.9.1 Processed Bags (Ty pe

- B Message)

- Sent to JL Host in LHR from LHR Reconciliation

System

LHRKMJL< ≡ From address

.LHRBRXH 311840< ≡ To address

BPM< ≡ Standard Message identifier

.V/1TLHR/PART1/555333702//123ABC456Z< ≡ Transfer bag in LHR; Multi part with

Encryption

.K/3D2C08< ≡ Message printer id

.J/R/4567/381761/23JAN/1835Z/R< ≡ Processing information

.F/JL402/23JAN/NRT/Y< ≡ Outbound flight JL402

.U/AVE1234JL/024L/T/Y/NRT/Y/JL955/23JAN/SEL< ≡ Loading information

.N/0131123456001< ≡ Bag tag number; number of consecutive

tags

.Q/006< ≡ Loading sequence

.S/Y< ≡ Authorization to load =Yes

.LSBJ14X< ≡ PNR address

. X/NON/XRAY/SECURITY/TRANSFER< ≡ Screening Description

.X/NON/CLR//XRAY/SECURITY/TRANSFER< ≡ Screenin g Description

.B/OFF/0125777432001< ≡ Offloaded bag tag number

.S/N< ≡ Authorization to load = No

.H/T1/CENTRAL/E20< ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

.P/1CHAN/T< ≡ Passenger’s name

.L/X4CM6Q< ≡ PN R address

.X/SEL/XRAY/SECURITY/TRANSFER< ≡ Screening Description

.X/SEL/CLR//XRAY/SECURITY/TRANSFER< ≡ Screening Description

.B/UNS/0038986251001< ≡ Bag Not Seen

.S/Y< ≡ Authorization to load = Yes

.P/1ELIOT/G< ≡ Number in Party, Passeng er Name

.L/TYH8NM< ≡ PNR address

.R/ORIGIN BAGS XRAYED< ≡ Internal airline data

.X/SEL/XRAY/SECURITY/TRANSFER< ≡ Screening Description

.X/SEL/CLR//XRAY/SECURITY/TRANSFER< ≡ Screening Description

ENDPART1< ≡ End Message Identifier

5.9.2 Of floaded Bag

BPM< ≡ Standard Message identifier

.V/1TORD< ≡ Transfer bags in ORD

.J/R/4567/381761/13JAN/183551L/R< ≡ Processing information

.F/BA296/13JAN/ORD/J< ≡ Outbound on BA296

.B/OFF/0016986470001< ≡ Offloaded bag tag number

.S/N//N< ≡ Authorization to load = No ; Passenger

status = N

.H/T1/CENTRAL/E20< ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim.P/1MASON/R< ≡ Passenger’s name

.L/YX476A6< ≡ PNR address

ENDBPM< ≡ End of Message Identifier

5.9.3 Bags Moved From One Container To Another

BPM< ≡ Standard Message Identifier

.V/1TIAD< ≡ Transfer bags at IAD

.F/UA259/10JUL/IAD/J< ≡ Outbound flight information

.U/AKE6654UA< ≡ Transfer bags from container

AKE6654UA .B/OFF/0016041172001< ≡ Offload

b ag number 0016041172

.Q/083< ≡ Loading sequence

.B/OFF/0016041218001< ≡ Offload bag number 0016041218

.Q/084< ≡ Loading sequence

.B/OFF/0016041388001< ≡ Offload bag number 0016041388

.Q/085< ≡ Loading sequence

.U/AKE9898LH< ≡ Transfer bags to container A KE9898LH

.N/0016041172001< ≡ Load bag number 0016041172

.Q/011< ≡ Loading sequence

.N/0016041218001< ≡ Load bag number 0016041218

.Q/012< ≡ Loading sequence

.N/0016041388001< ≡ Load bag number 0016041388

.Q/013< ≡ Loading sequence

ENDBPM< ≡ End of Message Identifier

5.9.4 All Bags Moved From One Container To Another

**Note:** This method can be used if the receiving system is able to track the contents of the ULD

(else, it is recommended to use the method as shown in example 5.9.3). When this method is

utili zed, Sections and 5.7.5 do not apply.

Note 2 is to be stricken.

Example of Multiple Usage of Elements

BPM< ≡ Standard Message Identifier

.V/1TIAD< ≡ Transfer bags at IAD

.F/UA259/10JUL/IAD/J< ≡ Outbound flight information

.U/AKE6654UA< ≡ Transfer all bags from this container

.U/AKE9898LH< ≡ To this container

ENDBPM< ≡ End of Message Identifier

5.9.5 Example of Multiple Usage of Elements

BPM< ≡

.V/1LLHR< ≡ Local bags at LHR

.K/3D2C08< ≡ Message printer ID

.J/R/50377/T4103/23J AN/183533L/T4C3< ≡ Processing information

.F/BA111/23JAN/SIN/F< ≡ Outbound flight BA111

.U/AVE1234BA//M/F/SIN/Y/QF6/24JAN/SYD< ≡ A. Loading information

.N/0125064717001< ≡ 1. 1st tag number & number

of tags.Q/006< ≡ a. Loading sequence

.S/ Y/4K/C< ≡ b. Auth. to load = Yes

.P/1NORMAN/G< ≡ c. Passenger’s Name

.G/25NOV1600/25NOV2200/Willem de Zwijger d. Ground Transport

laan 234/2405VM Alphen ad

Rijn

.G/Zuid Holland/Nederland e. Continuation of Ground

Transport

.Y/BA85521< ≡ d f

. Freq. Traveler Number.

.L/SBJ14X< ≡ e. PNR address

.N/0125064912001< ≡ 2. 1st tag number & number of tags

.Q/083< ≡ a. Loading sequence

.S/Y/12A/C< ≡ b. Auth. to load = Yes

.P/1ZELLER/F< ≡ c. Passenger’s name

.Y/US7444591< ≡ d. Freq. Traveler Num ber.

.L/X4CM6Q< ≡ e. PNR address

.X/SEL/ CLR// XRAY/SECURITY/TRANSFER< ≡ f. e. Screening Description

.N/0125064917001< ≡ 3. Additional bag

.Q/117< ≡ a. Loading sequence

.S/Y/12A/C< ≡ b. Auth. to load =Yes

.P/1ZELLER/F< ≡ c. Passenger’s name

.Y/US744 4591< ≡ d. Freq. Traveler Number.

.L/X4CM6Q< ≡ e. PNR address

.X/NON/ CLR// XRAY/SECURITY/TRANSFER< ≡ f. e. Screening Description

.B/NAL/0125068219001< ≡ 4. Not auth. to load bag

.S/N< ≡ a. Auth. to load = No

.P/1HAYD EN/B< ≡ b. Passenger’s name

.L/TYH8NM< ≡ c. PNR address

.R/ORIGIN BAGS XRAYED< ≡ d. Internal airline data

.X/NON/ CLR// XRAY/SECURITY/TRANSFER< ≡ e. Screening Description

.N/01250667239001< ≡ 5. Tag number & number of tags

.Q/127< ≡ a. Loading sequence

.U//11R/M//SIN< ≡ B. Loading information

.N/0125065209001< ≡ 1. 1st tag number and number of

tags

.Q/36< ≡ a. Loading sequence

.S/Y /23C/C< ≡ b. Auth. to load = Yes

.P/1JACKLIN/T< ≡ c. Passenger’s Name

.Y/QF003664< ≡ d. Freq. Traveler Number

.L/SBJ14X< ≡ e. PNR address

.X/NON/ CLR// XRAY/SECURITY/TRANSFER< ≡ f. Screening Description

ENDBPM< ≡ End of Message Identifier5.9.6 Example of Multi

- Sector Flights (Batched BPM)

- Routing: QF005

- FRA

- BKK

- SIN

- SYD

a. One BPM with multiple .F elements

BPM< ≡

.V/1LFRA< ≡ Local bags at FRA

.F/ QF005/21FEB/BKK< ≡ Outbound flight QF005 to BKK

.U/AKE1234QF//X/F/BKK < ≡ A. Loading information

.N/0081987654001< ≡ 1. 1st tag number & number of tags

.Q/006< ≡ a. Loading sequence

.P/1NORMAN/G< ≡ b. Passenger’s Name

.U/AVE789 0QF//M//BKK < ≡ B. Loading information

.N/0081123456001< ≡ 1. 1st tag number & number of tags

.Q/020< ≡ a. Loading sequence

.F/QF005/21FEB/SIN< ≡ Outbound flight QF005 to SIN

.U/AKE1234QF//X/F/SIN < ≡ C. Loading information

.N/00817 67676001< ≡ 1. 1st tag number & number of tags

.Q/026< ≡ a. Loading sequence

.P/1MAK/C< ≡ b. Passenger’s Name

.U/AKE6667QF//M//SIN < ≡ D. Loading information

.N/0081343434001< ≡ 1. 1st tag number & number of tags

.Q/030< ≡ a. Loading sequence

.F/QF005/21FEB/SYD< ≡ Outbound flight QF005 to SYD

.U/AKE1234QF//X/F/SYD < ≡ E. Loading information

.N/0081222222001< ≡ 1. 1st tag number & number of tags

.Q/022< ≡ a. Loading sequence

.P/1KOEPKE/A< ≡ b. Passenger’s Name

.U/AVE3333QF//M//SYD < ≡ F. Loading information

.N/0081393939001< ≡ 1. 1st tag number & number of tags

.Q/010< ≡ a. Loading sequence

ENDBPM< ≡ End of Message Identifier

b. Multiple BPMs for each flight segment

BPM< ≡

.V/1LFRA< ≡ Local bags at FRA

.F/QF005/21FEB/BKK< ≡ Outbound flight QF005

.U/AKE1234QF//X/F/BKK < ≡ A. Loading information

.N/0081987654001< ≡ 1. 1st tag number & number of tags

.Q/006< ≡ a. Loading sequence

.P/1NORMAN /G< ≡ b. Passenger’s Name

.U/AVE7890QF//M//BKK < ≡ B. Loading information

.N/0081123456001< ≡ 1. 1st tag number & number of tags

.Q/020< ≡ a. Loading sequence

ENDBPM

BPM< ≡

.V/1LFRA< ≡ Local bags at FRA

.F/QF00 5/21FEB/SIN< ≡ Outbound flight QF005

.U/AKE1234QF//X/F/SIN < ≡ A. Loading information

.N/0081767676001< ≡ 1. 1st tag number & number of tags

.Q/026< ≡ a. Loading sequence.P/1MAK/C< ≡ b. Passenger’s Name

.U/AKE6667QF//M/ /SIN < ≡ B. Loading information

.N/0081123456001< ≡ 1. 1st tag number & number of tags

.Q/030< ≡ a. Loading sequence

ENDBPM

BPM< ≡

.V/1LFRA< ≡ Local bags at FRA

.F/QF005/21FEB/SYD< ≡ Outbound flight QF005

.U/AKE1234QF//X/F/SYD < ≡ A. Loading information

.N/0081222222001< ≡ 1. 1st tag number & number of tags

.Q/022< ≡ a. Loading sequence

.P/1KOEPKE/A< ≡ b. Passenger’s Name

.U/AVE3333QF//M//SYD < ≡ B. Loading information

.N/0081393939001< ≡ 1. 1st ta g number & number of tags

.Q/010< ≡ a. Loading sequence

ENDBPM< ≡ End of Message Identifier

5.9.7 Single Bag From Sortation System

BPM< ≡ Standard Message identifier

.V/1LLHR< ≡ Transfer bags in LHR

.J/S//120D32/02APR/154559L/B2/ R1< ≡ Processing information

.F/BA117/02APR/SEL/J< ≡ Outbound on BA117

.N/0125123456001< ≡ Bag tag number

.P/1MASON/R< ≡ Passenger’s name

ENDBPM< ≡ End of Message Identifier

5.9.8 Single Bag From Reconciliation/Loading System

BPM< ≡ S tandard Message identifier

.V/1LLHR< ≡ Transfer bags in LHR

.J/R/43S//02APR/155501L/A23< ≡ Processing information

.F/BA117/03OCT/SEL< ≡ Outbound on BA117

.U/AKE1234BA//T/C Container ID

.N/0125123456001< ≡ Bag tag number

.Q/011< ≡ Loadi ng sequence

.P/1MASON/R< ≡ Passenger’s name

ENDBPM< ≡ End of Message Identifier

5.9.9 Bag(s) loaded in an aircraft Bulk compartment

BPM<≡ Standard Message identifier

.V/1LLHR<≡ Transfer bags in LHR

.F/BA117/03OCT/SEL<≡ Outbound on BA117

.U/HLD0004BA/H4 HOLD (Container) ID

.N/0125123456001<≡ Bag tag number

.Q/011< ≡ Loading sequence

.N/0125234567001<≡ Bag tag number

.Q/012< ≡ Loadi ng sequence.N/0125987654001<≡ Bag tag number

Q/013< ≡ Loading sequence

ENDBPM<≡ End of Message Identifier

5.9.10 Mishandled bag from sortation system

BPM<≡ Standard Message identifier

.V/1LLHR<≡ Transfer bags in LHR

.J/S//120/D32/0/2APR/154559L/ B2/R1<≡ Processing information

.F/BA117/2APR/SEL/J<≡ Outbound on BA117

.N / 0125123456001<≡ Bag tag number

.P/1MASON/R<≡ Passenger’s name

.E/MIS To indicate this is a mishandled baggage

ENDBPM<≡ End of Message Identifier

5.9.11 Re

- routing bag from so rtation system

BPM<≡ Standard Message identifier

.V/1LLHR<≡ Transfer bags in LHR

.J/S//120/D32/0/2APR/154559L/B2/R1<≡ Processing information

.F/BA117/0/2APR/SEL/J<≡ Outbound on BA117

.N / 0125123456001<≡ Bag tag number

.P/1MASON/R<≡ Passenger’s name

.E/RRTE< To indicate re

- routing process has been done

.E/STCK< To indicate re

- tagging process has been done

ENDBPM<≡ End of Message Identifier

5.9.12 Rush bag from sortation system

BPM<≡ Standard Message identifier

.V/1LLHR<≡ Transfer bags in LHR

.J/S//120/D32/0/2APR/154559L/B2/R1<≡ Processing information

.F/BA117/0/2APR/SEL/J<≡ Outbound on BA117

.N / 0125123456001<≡ Bag tag number

.P/1MASON/R<≡ Passenger’s name

.E/RUSH< To indicate rush process has been done

.E/STCK< To indicate re

- tagging pro cess has been done

ENDBPM<≡ End of Message Identifier

...



### B8.13/P

### Section 6

- BAGGAGE UNLOAD MESSAGE (BUM)

...

6.5 Element Sequence Summary

The following shows the sequence of elements in the BUM.

Element Requirement Definition

BUM Mandatory Standard Message Identifier

.V Mandatory Version and Supplementary Data

.K Optional Default Message Printer

.F Mandatory Outbound Flight Information

.U Optional Conditional Loading Data

.N Mandatory Baggage Tag Details

.I O ptional Conditional Inbound Flight Information

.O Optional Conditional Onward Flight Information

.Q Conditional Load Sequence Number

.S Optional Conditional Reconciliation Data

.H Conditional Handling Location

.P Conditional Passenger Name

. Y Optional Frequent Traveler Number

.C Optional Corporate or Group Name

.L Optional Automated PNR Address

.E Optional Conditional Baggage Exception Data

.R Optional Internal Airline Data

.X Optional Baggage Security Screening

ENDBUM Man datory End of Message Identifier

6.6 Multiple Use of Data Elements

Multiple use of elements may be accomplished by following the structure of the BUM and the

sequence of its elements. The prime element is the .F (Outbound Flight Information). This prov ides

the foundation for the .U element (Loading Data) and the .N element (Baggage Details) that follow it.

As the .U element is optional, the .N element may follow directly. Optional elements which are related

to the mandatory elements are inserted in th e order shown in 6.5. The .V element may occur once

however elements U, N, O, Q, E and R may be repeated multiple times, but only N, O, E and R can

be used consecutively.

The following schematic illustrates the multiple use of elements in the BUM.

Element s Description

.K Default Message Printer

.F Outbound Flight Information

.U Loading Data

.N Baggage Details or Baggage Irregularities

.I Inbound Flight

.O Onward Flight Information

.O Onward Flight Information

.Q Loading Sequence Number

.S Reconciliation Data

.H Handling Location

.P Passenger Name

.L Automated PNR Address

.E Baggage Exception Data

.E Baggage Exception Data

.R Internal Airline Data

.R In ternal Airline Data

.X Baggage Security Screening

.U Loading Data

.N Baggage Details or Baggage Irregularities

.Q Loading Sequence Number

.S Reconciliation Data

.P Passenger Name

.U Loading Data.N Ba ggage Details or Baggage Irregularities

.N Baggage Details or Baggage Irregularities

See 6.9.3 6.9.4 for an example of multiple use in a BUM.

6.7 Use of Conditional Elements and Data Items

6.7.1 Version and Supplementary Data (.V element)

The Mess age Reference Number is conditional upon the sender of the message requesting an

acknowledgement, in which case a Message Reference Number is required. Additionally, a separator

(oblique) is required in place of a Part Number (a BUM may not be partitioned ).

6.7.2 Loading Sequence Number element (.Q) is mandatory if the Loading Information element (.U) is

also present.

6.7.3 Baggage Exception Data (.E)

The .E element becomes mandatory when the data is available.

6.7.4 Handling Location (.H)

The .H element beco mes mandatory when the data is available.

6.7.5 Inbound Flight Information (.I)

The .I element becomes mandatory when the data is available.

6.7.6 Onward Flight Information (.O)

The .O element becomes mandatory when the data is available.

6.7.7 Reconcili ation Data (.S)

The .S element becomes mandatory when the data is available.

6.7.8 Loading Data (.U)

The .U element becomes mandatory when the data is available.

6.8 Construction of Elements and Data Items In The Baggage Unload Message

Use Elements and Data Items Example

(M) STANDARD MESSAGE IDENTIFIER BUM

(M) VERSION AND SUPPLEMENTARY DATA

(M) Element Identifier .V

(M) Data Dictionary Version Number /1

(M) Baggage Source Indicator T

(M) Local or Transfer Airport Code LHR

(N) Part number

– only show oblique, no data /

(C) Message Reference Number /1234567890

(O) Acknowledgement Request /A

(O) Encryption /123ABC456Z

(O) DEFAULT MESSAGE PRINTER

(M) Element Identifier .K

(M) Baggage Message Defau lt Printer ID /3D1C08

(M) OUTBOUND FLIGHT INFORMATION

(M) Element Identifier .F

(M) Airline and Flight Number /BA117

(M) Date /03OCT

(M) Destination or Transfer Airport Code /AMS

(O) Class of Travel of Baggage /J

( O C ) LOADING DA TA

(M) Element Identifier .U

(O) Stowage Device ID /AVE12345BA

(O) Aircraft Compartment or Loading Location /11R(O) Type of Baggage In Container/Location /T

(O) Classes of Travel of Baggage /F

(O) Destination Airport Code /AMS

(O) Sea led Container /Y

(N) Connection Airline Code and Flight Number

- not used in BUM

(N) Connection Departure Date

- not used in BUM

(N) Connection Destination Airport Code

- not used in BUM

(M) BAGGAGE TAG DETAILS

(M) Element Identifier .N

(M) Bag Tag Number /0085123456

(M) Number of Consecutive Tags 001

( O C ) INBOUND FLIGHT INFORMATION

(M) Element Identifier .I

(M) Airline and Flight Number /BA178

(M) Date of Departure /03OCT

(O) Originating Airport Code /JFK

(O ) Class of Travel of Baggage /J

( O C ) ONWARD FLIGHT INFORMATION

(M) Element Identifier .O

(M) Airline and Flight Number /AZ203

(M) Date /04OCT

(O) Destination or Transfer Airport Code /FCO

(O) Class of Travel of Baggage /J

(C) LOAD SEQUENCE NUMBER

(M) Element Identifier .Q

(M) Load Sequence Number /031

( O C ) RECONCILIATION DATA

(M) Element Identifier .S

(M) Authority to Load /N

(O) Seat Number /10A

(O) Passenger Status /N

(O) Sequence Number /098

(O) Security Number /088

(O) Passenger Profile Status /Y

(C) HANDLING LOCATION

(M) Element Identifier .H

(C) Handling Terminal /T4

(C) Handling Bay/Pier /GREEN

(C) Handling Gate/Stand /D46

(C) PASSENGER NAME

(M) Element Identifier .P

(M) Separator (oblique) /

(O) Number of Passengers With This Surname 2

(M) Passenger’s Surname JORGENSON

(O) Given Name and/or Initials and/or Title /K

(O) Additional Given Name and/or Initials and/or Title /A

(O) FREQUENT TRAVELER NUMBER

(M) Element Identifier .Y

(M) Frequent Traveler ID Number /KL662503

(O) Tier Information /GOLD

(O) CORPORATE OR GROUP NAME(M) Element Identifier .C

(M) Corporate or Group Name /HAMPTON SKI

(O) AUTOMATED PNR ADDRE SS

(M) Element Identifier .L

(M) Automated PNR Address /L2TVVP

( O C ) BAGGAGE EXCEPTION DATA

(M) Element Identifier .E

(M) Exception Type /SPEQ

(O) INTERNAL AIRLINE DATA

(M) Element Identifier .R

(M) Free Text /FREE TE XT AREA

(O) BAGGAGE SECURITY SCREENING

(M) Element Identifier .X

(O) Baggage Security Screening Instruction /SEL

(O) Security Reason Result /CLR

(O) Security Screening Reason Result /T

(O) Security Screening Method /XRAY

(O) Aut ograph /SECURITY

(M) Free text /TRANSFER

(M) END OF MESSAGE IDENTIFIER ENDBUM

6.9 Example Messages

6.9.1 Standard Offload (Type

- B), with Acknowledgement Request

LAXBRXH< ≡ From Address

.HDQKMCX 311840< ≡ To Address

BUM< ≡ Standar d Message Identifier

.V/1TLAX//1234567890/A/123ABC456Z< ≡ Transfer bag in LAX; Ack requested;

Ref Number 1234567890 with Encryption

.F/CX881/15JUN/HKG/Y< ≡ Outbound to HKG on CX881

.U/AVE4321SQ/024L/T/Y/KG< ≡ Loading Information

.N/01311234560 01< ≡ Bag tag number; number of consecutive tags

.Q/006< ≡ Loading sequence of bag

.S/N//N< ≡ Reconciliation data: Not authorized to load

.H/T1/CENTRAL/E20< ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

.P/WONG/V< ≡ Pa ssenger’s name

.L/SBJ14X< ≡ PNR Address

.R/CUSTOMS REQUEST< ≡ Internal Airline Data

.X/SEL/XRAY/SECURITY/TRANSFER< ≡ Screening Description

ENDBUM< ≡ End of Message Identifier6.9.2 Standard Offload (2 different containers and 2 different bags)

BUM< ≡ Standard Message Identifier

.V/1LPIT////123ABC456Z< ≡ Local bag in PIT with Encryption

.F/US816/01MAY/FRA/Y< ≡ Outbound to FRA on US816

.U/AVE0321US/0012/T/Y/FRA< ≡ Loading information

.N/0037336127001< ≡ Bag tag number; Number of Consecutive Tags

.Q/026< ≡ Loading sequence for this bag

.H/T1/CENTRAL/E20< ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

.P/WILSON/SARA< ≡ Number in party, Passengers name

.U/AKV9876US//T/Y/FRA< ≡ Loading information

.N/0125886172001< ≡ Bag tag number; Number of Consecutive Tags

.Q/012< ≡ Loading sequence

ENDBUM< ≡ End of Message Identifier

Standard Offload (1bag)

BUM< ≡ Standard Message Identifier

.V1LPHL////123ABC456Z< ≡ Local bag in PHL with Encry ption

.F/US14/01MAY/MUC/J< ≡ Outbound to MUC on US14

.U/AVE0321US/0012/T/J/MUC< ≡ Loading Information

.N/0037336127001< ≡ Bag Tag number, number of tags

.Q/026< ≡ Loading sequence for this bag

.H/T1/CENTRAL/E20< ≡ Handling Terminal; Handling Bay/ Pier;

Handling Gate/Stand/Claim

.P/1BROWNE/L< ≡ Passenger's name

ENDBUM< ≡ End of Message Identifier

6.9.4 Example of Multiple Use of Elements

BUM< ≡ Standard Message Identifier

.V/1LBKK////123ABC456Z< ≡ Local bag in BKK with Encryption

.F/QF006/01MAY/SYD/J< ≡ A. Outbound to SYD on QF006

.U/AVE4591QF//M/J/SYD< ≡ 1. Loading information

.N/012020161001< ≡ a. Tag number to unload

.Q/136< ≡ 1. Load sequence for bag

.P/SAMPRAS/P< ≡ 2. Passenger’s name

.N /0125020244001< ≡ b. Next tag to unload (same ULD)

.N/0125020318001< ≡ c. Another bag from same ULD

.U/AKV2479BA//T/J/SYD< ≡ 2. New ULD (Loading information)

.N/0125020398001< ≡ a. Tag number to unload

.I/JL173/0 1MAY/NRT< ≡ 1. Inbound info.

.Q/009< ≡ 2. Loading Sequence

.S/N/25K//C/010< ≡ 3. Reconciliation data

.N/0125020577001< ≡ b. Tag number to unload

.O/QF322/02MAY/BRI< ≡ 1. Connection flight info.

.Q/088< ≡ 2. Loading Sequen ce

.S/N/31K/C/101< ≡ 3. Reconciliation data

ENDBUM< ≡ End of Message Identifier

6.9.5 Standard Offload (2 bags: no container information)

BUM< ≡ Standard Message Identifier

.V/1LFRA////123ABC456Z< ≡ Local bag in FRA with Encryption

.F/UA941/27 MAY/ORD/J< ≡ Outbound to ORD on UA941

.N/0016170357001< ≡ Bag Tag number: number of tags

.N/0016179421001< ≡ Bag Tag number: number of tags

.H/T1/CENTRAL/E20< ≡ Handling Terminal; Handling Bay/Pier;

Handling Gate/Stand/Claim

ENDBUM< ≡ End of Message Identifier

### B8.8/P

Section 10

- BAGGAGE REQUEST MESSAGE (BRQ)

... 

### 10.5 Element Sequence Summary

The following shows the sequence of elements in a BRQ.

Element Requirement Definition

BRQ Mandatory Standard Message Identifier

.V Mandatory Version and Supplementary Data

.A Optional Message Acknowledgement Details

.F Conditional Outbound Flight Information

.I Conditional Inbound Flight Information

.O Conditional Onward Flight Information

.N Conditional Baggage Tag Details

.D Conditional Baggage Check

- In Details

.H Mandatory Conditional Handling Location

.P Conditional Passenger Name

.Y Conditional Frequent Traveler Number

.C Conditional Corporate or Group Name

.L Conditional Automated PNR Address

.T Conditional Baggage Tag Printer ID

.E Conditional B aggage Exception Data

ENDBRQ Mandatory End of Message Identifier

10.6 Multiple Use of Elements

The following schematic illustrates the multiple use of elements in the BRQ.

Element Description

.A Message Acknowledgement Details

.F Outbound Flight (LAX

- NRT)

.I Inbound Flight (ORD

- LAX)

.O Onward Flight (NRT

- SIN)

.O Onward Flight (SIN

- SYD)

.N Baggage Tag Details

.D Baggage Check

- in Details

.H .H Handling Location

.P Passenger Name

.Y Frequent Traveler Number

.C Corporate or Grou p Name

.L Automated PNR Address

.T Baggage Tag Printer ID

.E Baggage Exception Data

10.7 Use of Conditional Elements and Data Items

10.7.1 The .F element (Outbound Flight Information) is mandatory when the data is available

10.7.2 The .I eleme nt (Inbound Flight Information) is mandatory when the data is available.

10.7.3 The .O element (Onward Flight Information) is mandatory when the data is available.

10.7.4 The .N element (Baggage Tag Details) is mandatory when the data is available.

10.7.5 The .P element (Passenger Name) is mandatory when the data is available.

10.7.6 The .Y element (Frequent Traveler Number) is mandatory when the data is available.

10.7.7 The .C element (Corporate or Group Name) is mandatory when the data is available.

10 .7.8 The .L element (Automated PNR Address) is mandatory when the data is available.

10.7. 9 8 The .T element (Baggage Tag Printer ID) is mandatory when the data is available.

10.7. 10 9 The .E element (Baggage Exception Data) is mandatory for a copy tag reque st.

10.7. 11 10 The .V element (version and supplemental data) may contain a conditional Message

Reference Number and Acknowledgement Request Indicator.

10.7.11 Handling Location (.H)

The .H element becomes mandatory when the data is available.10.8 Const ruction of Elements and Data Items in the BRQ

Use Elements and Data Items Example

(M) STANDARD MESSAGE IDENTIFIER BRQ

(M) VERSION AND SUPPLEMENTARY DATA

(M) Element Identifier .V

(M) Data Dictionary Version Number /1

(M) Baggage So urce Indicator T

(M) Local, Transfer or Terminating Airport Code ZRH

(O) Part Number /

- show only oblique; no data

(C) Message Reference Number /1234567890

(O) Acknowledgement Request /A

(O) Encryption /123ABC456Z

(O) M ESSAGE ACKNOWLEDGEMENT DETAILS

(M) Element Identifier .A

(M) Sender’s Message Reference Number /BA2190123

(M) Type of Baggage Message and Status Indicator

being acknowledged /BRQ

(M) ACK of NAK /NAK

(O) Free Text /COPY TAG

(C) OUT BOUND FLIGHT INFORMATION

(M) Element Identifier .F

(M) Airline and Flight Number /SR101

(M) Date /16APR

(M) Originating Airport Code /JFK

(O) Class of Travel of Baggage /J

(M) INBOUND FLIGHT INFORMATION

(M) Element Identifier .I

(M) Airline and Flight Number /AZ318

(M) Date /16APR

(M) Originating Airport Code /FCO

(O) Class of Travel of Baggage /J

(M) ONWARD FLIGHT INFORMATION

(M) Element Identifier .O

(M) Airline and Flight Number /UA203

(M) Da te /16APR

(M) Originating Airport Code /DEN

(O) Class of Travel of Baggage /J

(C) BAGGAGE TAG DETAILS

(M) Element Identifier .N

(M) Baggage Tag Number /0085123456

(C) Number of Consecutive Tags 003

Use Elements and Data Items Exam ple

( O C ) HANDLING LOCATION

(M) Element Identifier .H

(C) Handling Terminal /T4

(C) Handling Bay/Pier /GREEN

(C) Handling Gate/Stand /D46

(C) PASSENGER NAME

(M) Element Identifier .P

(M) Separator (oblique) /

(O) Number Of Passengers With This Surname 2

(M) Passenger’s Surname SMITH

(O) Given Name and/or Initials and/or Title /TOMMR

(O) Additional Given Name and/or Initials and/or Title /ALICE

(O) FREQUENT TRAVELER NUMBER

(M) Element Identifier .Y

(M ) Frequent Traveler ID Number /KL662503

(O) Tier Information Identifier /GOLD

( O C ) CORPORATE OR GROUP NAME(M) Element Identifier .C

(M) Corporate or Group Name /IATA TOUR

(C) AUTOMATED PNR ADDRESS

(M) Element Identifier ./L

(M) A utomated PNR Address /XY1C3P

(C) BAGGAGE TAG PRINTER ID

(M) Element Identifier .T

(M) Bag Tag Printer ID /321A4C

( O C ) BAGGAGE EXCEPTION DATA

(M) Element Identifier .E

(M) Exception Type /CPY

(M) END OF MESSAGE IDENTIFIER ENDBRQ



### ...



### Recommended Practice 1745

Attachment A

B8.14/P

1 CODE SET FOR THE BAGGAGE EXCEPTION DATA ELEMENT

...

1.3 Additional Recommended Code Set for Baggage Identification or Handling

... JUMP JUMP passenger on jump seat, explains missing seat no. in .S eleme nt

LRFI Limited Release, Fragile or inadequate packing

LRLC Limited Release, Late Check

- in

LRLL Limited Release, Lack of Name Label

LRNA Limited Release, Not admissible in Cabin

LRPE Limited Release, Perishable

LRRD Limited Release, Received Damaged

LRSZ Limited Release, Size

MIS Mishandled baggage

...

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## RECOMMENDED PRACTICE 1773b

STANDARD INFLIGHT CATERING AGREEMENT

( new )

PSC(32)1773b

M10.1



### INSTRUCTIO NS ON HOW TO USE THE

STANDARD INFLIGHT CATERING AGREEMENT (SICA)

1) The SICA is structured as follows:

a. Cover Page

b. Articles 1 to 19

c. Annex A

– List of Inflight Catering Services

d. Annex(es) B

– Agreed Inflight Catering Services and Terms for Location(s)

e. Optio nal Annexes

Annex C

– Service Level Agreement (example provided)

Annex D

– Ethics Policy (example provided)

2) For ease of reference, the following terminology is used.

Agreement Annex A Annex B Annex C Annex D

Articles Sections Paragraphs KPI’s Chapters

Sub

- Articles Sub

- Sections Sub

- Paragraphs Sub

- Chapters

Clauses Items Lines

Annexes Schedules

3) The Cover Page is used to

a. Identify the Parties;

b. List all Annexes B that are applicable at the time of signature;

c. Confirm if an Annex C ap plies to the Agreement;

d. Confirm if an Annex D applies to the Agreement;

e. List any other annex(es) agreed between the Parties;

f. Document the commencement date of the Agreement; AND

g. Execute the Agreement.

4) If the Cover Page requires more than one page, page nu mbers shall show 2a, 2b, 2c, etc.

5) Modifications to Articles 1 to 19 must be recorded in Annex(es) B

.

6) Modifications to Annex A

– List of Inflight Catering Services must be recorded in Annex(es) B

.7) Annex B

– Agreed Inflight Catering Services and Ter ms for Location(s) is used to:

a. Define agreed inflight catering services for a specific Location or group of Locations;

b. Document any modification to Articles 1 to 19 agreed between the Parties;

c. Document any modification to Annex A agreed between the Parties

. Modifications may include text amendments, exclusions and inclusions.

As many Annexes B as necessary may be used, each Annex being identified as Annex B[1], Annex B[2], etc.

To each Annex B[x] must correspond a Schedule to Annex B[x]

– Agreed Price List.

8) This agreement structure allows the Parties to modify Articles / Sub

- Articles / Clauses, as well as Sections /

Sub

- Sections / Items, add / remove Location(s) and modify price lists as they see fit by simply replacing existing

Annex(es) B and/or Schedules to Annex B with new ones duly signed by both Parties.

9) Annex C only provides an example of a Service Level Agreement. The Parties are encouraged to define and

agree on specific Key Performance Indicators (KPI’s) based on the Services agreed between the Pa rties in their

agreement.

10) Annex D only provides an example of an Ethics Policy. The Parties are encouraged to define the ethics

policy they wish to comply with in their agreement.

11) The Parties may add any additional annex they wish to their agreement, as long as reference to each

additional annex is made in Annex B. In addition, when inserting an annex used in previous agreements, be

mindful of not contradicting Articles 1 to 19, and in particular the definitions set out in Article 1. Finally, each

additio nal annex must be referred to as Annex E, Annex F, etc.

12) Each Annex B may have its own commencement and expiry dates that are independent of the Agreement

as a whole. However, the expiry date of any Annex B may not exceed the expiry date of the Agreement.

13) Annex(es) B that are applicable at the time, optional Annexes C and D, as well as any other annex(es)

agreed between the Parties, must be agreed on the date of signature of the Agreement in order to be

incorporated.

14) New Annex(es) B may be signed by diff erent officers on an on

- going basis during the Term, as appropriate.

### STANDARD INFLIGHT CATERING AGREEMENT (SICA)

Table of Contents

COVER PAGE

ARTICLE 1 DEFINITIONS

ARTICLE 2 PROVISISON OF SERVICES

ARTICLE 3 SUBCONTRACTING, ASSIGNMENT & CH ANGE OF OWNERSHIP OR CONTROL

ARTICLE 4 CARRIER’S OBLIGATIONS

ARTICLE 5 STANDARDS OF WORK

ARTICLE 6 CARRIER’S RIGHT TO CONDUCT INSPECTIONS

ARTICLE 7 CARRIER’S LOCAL REPRESENTATION

ARTICLE 8 CONFIDENTIALITY AND DATA PROTECTION

ARTICLE 9 REMUNERATION

A RTICLE 10 DISBURSEMENTS

ARTICLE 11 INVOICES

ARTICLE 12 TITLE AND RISK

ARTICLE 13 LIABILITY AND INDEMNITY

ARTICLE 14 INSURANCE

ARTICLE 15 DISPUTE RESOLUTION

ARTICLE 16 STAMP DUTIES & REGISTRATION FEES

ARTICLE 17 TERM AND TERMINATION

ARTICLE 18 FORCE MAJEURE

ARTICLE 19 MISCELLENEOUS

ANNEX A List of Inflight Catering Services

ANNEX(ES) B Agreed Inflight Catering Services and Terms for Location(s)

ANNEX C Service Level Agreement (if applicable)

ANNEX D Ethics Policy (if applicable)

### INFLIGHT CATERING AGREEMENT

An Agreement made between:

[Carrier Name]

having its principal office at:

........................................................... hereinafter referred to as the ‘Carrier’,

and

[Caterer Name]

having its principal office at:

........................................................... hereinafter referred to as the ‘Caterer’,

hereinafter the Carrier and/or the Caterer referred to as the ‘Party(ies)’

This Agreement comprises the IATA Standard Inflight Catering Agreement (version dated 01 April 2010 as

attached) subject to the following modifications:

An nex(es) B1 to B [x]

– Agreed Inflight Catering Services and Terms for [List Location(s)]

(List all Annex(es) B that are applicable at the time of signature) ;

 Annex C

– Service Level Agreement [Check box if applicable to this Agreement] ;

 Annex D

– Ethi cs Policy [Check box if applicable to this Agreement] ;

 Additional annexes agreed between the Parties [Check box if applicable to this Agreement ]:

[ List all other annexes that form part of this Agreement]

This Agreement shall commence on [Select date from Date, Date of last signature by the Parties OR The first

day of supply of the Services at any Location to which this Agreement relates]

IN WITNESS WHEREOF, the Parties hereto have executed this Agreement

EXECUTED FOR AND ON BEHALF

OF [CARRIER NAM E] BY

Name:

Title:

Date: EXECUTED FOR AND ON BEHALF

OF [CATERER NAME] BY

Name:

Title:

Date:

Name:

Title:

Date: Name:

Title:

Date:

### ARTICLE 1. DEFINITIONS

For the sake of clarity, the following definitions shall apply to the SICA.

ADDI TIONAL SERVICES shall have the meaning set out in **Article 10**

.

ADMINISTRATION & SUPERVISION SERVICES shall have the meaning set out in **Article 2**

.

AUTHORISED REPRESENTATIVE shall have the meaning set out in **Article 6**

.

BONDED STORE ITEMS means all commissa ry items boarded as part of inflight catering and requiring separate

storage and inventory control due to their duty free status, including without limitation wines, spirits, duty free

goods, etc.

CARRIER'S AIRCRAFT means any aircraft owned, leased, char tered, hired or operated or otherwise utilized by

or on behalf of the Carrier and in respect of which the Carrier has either expressly or implicitly contracted,

instructed or otherwise requested the Caterer to perform or carry out any of the Services.

CA RRIER INSTRUCTIONS means written procedures, instructions, directions and/or regulations pertaining to

the Special Services provided by the Carrier to the Caterer as applicable during the Term.

CARRIER NOMINATED PRODUCTS means any items or services purcha sed by the Caterer from a third party

designated by the Carrier for the supply of these items, or delivery of these services, in connection with the

provision of the Services, and may include without limitation frozen casseroles, beef, chocolates, laundere rs, etc.

CARRIER SPECIFICATIONS means written procedures, instructions, directions and/or regulations pertaining to

the Scheduled Services provided by the Carrier to the Caterer from time to time during the Term. These shall

include, but not limited to, m enu details, menu specifications, meal loading charts, tray setting instructions and

galley loading diagrams. These may also include relevant technical instructions on how to operate aircraft doors,

if applicable.

CARRIER SUPPLIED ITEMS means all items su pplied by the Carrier to the Caterer and required for the

provision of the Services, and may include without limitation branded napkins, plastic cups, wines, spirits,

snacks, frozen casseroles, etc.

CONFIDENTIAL INFORMATION shall have the meaning set out in **Article 8**

.

CONVENTION means international conventions applicable to this Agreement from time to time, including but not

limited to the Warsaw Convention and the Montreal Convention.

DISCLOSER shall have the meaning set out in **Article 8**

.

DRY STORE ITE MS means all non

- duty free commissary items boarded as part of inflight catering including

without limitation snacks, canned soft drinks, napkins, and passenger amenities.

FORCE MAJEURE EVENT shall have the meaning set out in **Article 18**

.

INFLIGHT CATERIN G EQUIPMENT means any rotable and galley equipment provided by the Carrier and used

by the Caterer for the provision of the Services.

LAUNDRY ITEMS means all Carrier linen boarded by the Caterer as part of inflight catering.

LOCATION(S) means airport(s) at which the Caterer will provide the Services as set out in **Annex(es) B**

.

MEAL ORDER means the communication by the Carrier to the Caterer of the total number of passengers

expected on a given flight by class of service, including crew members, and speci fying the type of special meal

requested by each passenger having ordered a special meal.PASSENGER(S) means any passenger(s) transported by the Carrier on a flight to which this Agreement applies.

PERSONAL DATA shall have the meaning set out in **A rticle 8** 

.

RECIPIENT shall have the meaning set out in **Article 8**

.

SCHEDULED FLIGHT(S) means Carrier’s flight(s) undertaken on Carrier’s Aircraft that is integrated into the

Carrier’s scheduled operations, and may also include scheduled seasonal and charte r flights.

SCHEDULED SERVICES means the services set out in **Sections 1 to 9 of Annex A** that will be provided in

respect of the Carrier’s Scheduled Flights , or upon Carrier request, that may be provided in respect of extra

flights at the same Location(s) or flights at locations other than the Locations.

SENSITIVE DATA shall have the meaning set out in **Article 8**

.

SERVICES means the Scheduled Services, Special Services, Additional Services and the Administration &

Supervision Services as defined herein.

SPECIAL SERVICES means the services described in **Section 10 of Annex A** that will be provided on request

of the Carrier from time to time during the Term at the Locations and which may be more particularly described in

**Annex(es) B**

.

SUBCONTRACTOR means a th ird party appointed by the Caterer to provide any of the Services to the Carrier

on its behalf.

TERM shall have the meaning set out in **Article 17**

.

TERMINATION TRANSITION PERIOD shall have the meaning set out in **Article 17**

.

The SICA is made up of Article s, Sub

- Articles, Clauses and Annexes. **Annex A** is made up of Sections, Sub

Sections and Items. **Annex B** is made up of Paragraphs, Sub

- Paragraphs, Lines and Schedules. **Annex C** is

made up of Key Performance Indicators. **Annex D** is made up of Chapters and Sub

- Ch apters. This terminology

is used to facilitate referencing and to avoid confusion between the various parts of this Agreement.

Unless the context or express provision of this Agreement otherwise requires:

I) Words importing the singular shall include the plural and vice versa;

ii) All references to articles, sub

- articles, clauses, sections, sub

- sections, items, paragraphs, sub

- paragraphs,

lines, key performance indicators, chapters, sub

- chapters, annexes and schedules are references to those in this

Agreem ent;

iii) All references to this Agreement shall include annexes and schedules hereto and all amendments, variations,

replacements and novations hereof.

### ARTICLE 2. PROVISION OF SERVICES

2.1 General

2.1.1 The Caterer hereby undertakes to provide th e Services to the Carrier during the Term in the manner

specified in, and in accordance with, this Agreement. The specific Scheduled Services and/or Special Services

to be provided in each Location or group of Locations, and any specific terms applicable to the supply of such

services in that Location or group of Locations, shall be set out in separate annexes to this Agreement in the

form attached at **Annex B**

.



### 2.2 Scheduled Services

Scheduled Flights

2.2.1 The Caterer shall provide the Scheduled Service s to the Carrier in respect of Scheduled Flights at the

designated Location(s). The Carrier shall supply to the Caterer from time to time, and Caterer agrees to comply

with, Carrier Specifications in respect of the Scheduled Services. In the absence of Car rier Specifications the

Caterer shall follow its own standard practices and procedures in relation to the Scheduled Services.

Extra Flights

2.2.2 The Caterer shall also use its best endeavors to provide the Scheduled Services to the Carrier for flights

other than Scheduled Flights at the same Location(s), provided that reasonable prior notice of a requirement for

such services is given and the provision of such services will not prejudice commitments already undertaken.

Such services may also be govern ed by additional special conditions to be agreed in writing between the Parties

from time to time. The Caterer shall advise the Carrier in writing as soon as reasonably possible if it is unable to

provide the requested services.

Other Locations

2.2.3 Whe re the Carrier from time to time operates a flight from a location other than the Location(s), the Caterer

shall, on request, use best endeavors, subject to the Caterer operating a catering facility at the location and

having the means locally available, t o furnish Scheduled Services to such flight. Such services may also be

governed by additional special conditions to be agreed in writing between the Parties from time to time. The

Caterer shall advise the Carrier in writing as soon as possible if it is una ble to provide the Scheduled Services at

such other location. If the Caterer advises it is not able to provide the requested services at the location, the

Carrier shall be free to contract with another caterer (including Caterer’s competitors) for provisio n of such

services.



### 2.3 Special Services

2.3.1 The Caterer shall, upon request, use its best endeavors to provide the Carrier with the Special Services.

Such services shall be governed by special conditions to be agreed in writing between the Parties, a s well as by

this Agreement. The Caterer shall advise the Carrier in writing as soon as possible if it is unable to provide

requested Special Services.

### 2.4 Administration & Supervision Services

The Caterer shall provide the following services, at a ll Locations during the Term:

Administration

2.4.1 When advised by the Carrier of any changes, keep up to date the Caterer’s copy of the Carrier’s manuals,

circulars and other relevant operational documents connected with the performance of the Services.

2.4.2 Establish and maintain local procedures in accordance with the Carrier’s requirements.

2.4.3 As required, take prompt action on all communications addressed to the Caterer.

2.4.4 Prepare, sign, distribute, file and retain reports/statistics/docu ments as required in accordance with local,

national and international laws, rules, regulations and procedures and/or in accordance with the Carrier’s

requirements.

2.4.5 Receive and distribute all Carrier messages sent in connection with the services per formed by the Caterer.

Maintain a file containing all such messages received pertaining to each flight in accordance with the Carrier’s

requirements.

2.4.6 As per **Sub**

**- Article 9.3**  , effect payment, on behalf of the Carrier, for charges, fees or taxes impos ed or

levied by the Airport, Customs or other authorities against the Carrier or the Caterer in connection with the

services performed.

Supervision of Services Contracted by the Carrier with Third Party(ies)

2.4.7 

### As far as reasonably practicable, facil itate the provision of services contracted by the Carrier

with third party(ies) and co

- ordinate delivery schedules.



### 2.4.8 As far as reasonably practicable, ensure that the suppliers referred to in **Clause 2.4.7** are informed about

operational data and Carri er's requirements in a timely manner.



### 2.4.9 Liaise with the Carrier's designated representative.

2.4.10 Advise the Carrier in a timely manner of any irregularities, of which it becomes aware, arising under or in

connection with the provision of the Ser vices and related to the performance of suppliers referred to in **Clause**

**2.4.7**

.

### ARTICLE 3. SUBCONTRACTING, ASSIGNMENT & CHANGE OF OWNERSHIP OR CONTROL

Subcontracting of Services

3.1 The Caterer shall be entitled to subcontract any of the Services. I t is understood that, in this case, the

Caterer shall nevertheless remain liable to the Carrier for the proper rendering of the subcontracted services as if

they had been performed by the Caterer itself. The following services require the prior written con sent of the

Carrier before being subcontracted by the Caterer, which consent shall not be unreasonably withheld or denied,

and such approved Subcontractors shall be listed in **Annex(es) B**

. (a) Security checks of Inflight Catering Equipment and;

(b) Laundere rs and;

(c) Ramp services

.

3.2 The Carrier shall be entitled at any time during the Term to request details of the origin and producer of all

dishes presented by the Caterer and the Caterer shall be obliged to provide such information as soon as

reasonabl y practicable. In the event that the Carrier is dissatisfied with a particular Subcontractor used by the

Caterer, the Carrier shall be entitled to request the Caterer to appoint an alternate Subcontractor.

3.3 The Carrier shall not appoint any other perso n or company to provide the Services except in the event of a

strike by the Caterer, in the event of the Caterer’s inability to comply with Carrier’s requests under **Sub**

**- Articles** 

**2.2 and 2.3** , or in such special cases as shall be mutually agreed between the Parties.

Assignment

3.4 This Agreement has been made having regard to the legal personality of the Parties and neither Party shall have

any right to assign its rights or obligations under this Agreement to any third party without the express written cons ent

of the other Party.

Change of Ownership or Control

3.5 In the event of a change of ownership or control of either Party, the affected Party shall as soon as reasonably

practicable provide the other Party with written notice thereof, by courier or reg istered mail, return receipt requested.

For the purposes of this Sub

- Article, a change of ownership or control shall mean, with respect to the affected Party,

a change in the ability to determine the outcome of decisions about the Party’s financial and ope rating policies and

shall include, but not be limited to, a change in the majority or controlling shareholding (where the Party is a private

company), merger (where the Party is not the surviving entity) or in the case of the Caterer, disposal of its cater ing

business.

3.6 In such event, the Party not subject to a change of ownership or control reserves the right to terminate this

Agreement. In such case, that Party shall inform the affected Party of its intention within thirty (30) days by courier or

regi stered mail, return receipt requested. The Agreement shall terminate automatically without indemnification, nor

further notice, after a further period of thirty (30) days from the mailing of the notice mentioned above.

### ARTICLE 4. CARRIER’S OBLIGATION S

4.1 Carrier Specifications and/or Instructions

4.1.1 The Carrier shall supply the Caterer with sufficient and timely information, in the form of Carrier

Specifications and/or Carrier Instructions, to enable the Caterer to provide the Services in accord ance with its

obligations under this Agreement. The Carrier may amend the Carrier Specifications and/or Carrier Instructions

at any time during the Term. Any new or amended Carrier Specifications and/or Carrier Instructions shall be

deemed accepted by the Caterer unless the Caterer notifies the Carrier of its objection thereto, in writing setting

out the reason(s) for its objection, within seven (7) working days of the Caterer receiving the new or amended

Carrier Specifications and/or Carrier Instructions.



### 4.2 Flight Schedule Changes

4.2.1 The Carrier shall inform the Caterer as soon as commercially practicable about any changes of schedule

and/or frequencies and/or types of aircraft (including aircraft configuration).



### 4.3 Inflight Catering Equipment

4 .3.1 The Carrier shall supply the Caterer with sufficient Inflight Catering Equipment at each Location to enable

the Caterer to provide the Services in accordance with its obligations under this Agreement.



### 4.4 Carrier Supplied Items

4.4.1 The Carrier sha ll supply the Caterer with sufficient volumes of Carrier Supplied Items at each Location to

enable the Caterer to provide the Services in accordance with its obligations under this Agreement. It is the

Carrier’s responsibility to replenish Carrier Supplied Items and to maintain appropriate stock levels at all times.



### ARTICLE 5. STANDARDS OF WORK

5.1 In the provision of the Services, the Caterer shall pay due regard to safety and security, and shall comply

with all applicable local, national and internationa l laws and regulations.

5.2 The Caterer undertakes that it shall at all times during the Term:

(a) Ensure that all food and beverages provided to the Carrier meet the standards of hygiene and food safety

specified by IFSA/AEA World Food Safety Guidelines and/or ICQA Food Processing Safety Standards and

Interpretation Guidelines and/or the Carrier’s requirements as applicable and described in **Annex(es) B** , as well

as all applicable local, national and international laws, rules, regulations and procedures;

(b ) Regularly monitor such compliance and make available to the Carrier for inspection on request all

documentation pertaining to such monitoring of and compliance with such standards and guidelines.

5.3 The Caterer further undertakes that it shall at all t imes during the Term:

(a) Ensure that ramp operations meet the standards of ramp safety specified in IOSA Standards and ISAGO

Standards and/or the Carrier’s requirements as applicable and described in **Annex(es) B** , as well as all

applicable local, national and international laws, rules, regulations and procedures;

(b) Regularly monitor such compliance and make available to the Carrier for inspection on request all

documentation pertaining to such monitoring of and compliance with such standards and guideline s.

5.4 The Caterer shall ensure that the Services are provided in a timely manner and shall use best endeavors to

help ensure the Carrier’s Aircraft depart on time.

5.5 In case of multiple handling for the Carrier, priority shall, as far as possible, b e given to Carrier’s Scheduled

Flights operating on time, unless the Carrier provides instructions to the contrary.5.6 The Caterer shall be responsible for ensuring and maintaining the quality and safe storage of all food and

beverages produced withi n or delivered to its premises, including during transportation and aircraft loading. In the

case of Carrier Supplied Items and Carrier Nominated Products, the Caterer shall use commercially reasonable

efforts to inspect such items for quality upon deliver y to its premises, and thereafter shall be responsible for

ensuring the safe storage and maintaining the quality of such items, as well as during transportation and aircraft

loading.

5.7 The Parties shall comply with the ordering and cancellation procedur es as set out in Annex(es) B.

5.8 The Caterer shall ensure that any authorizations, permits or consents required by personnel performing the

Services for the Carrier are kept up

- to

- date. If at any time the Caterer is unable to provide duly authorized

per sonnel as required by the Carrier, the Caterer shall inform the Carrier immediately.

5.9 The Caterer shall provide adequate facilities for the receiving, cleaning, storage, preparation, production,

assembly, dispatch and transportation of all foods and b everages provided to the Carrier. Such facilities shall

enable the Caterer to comply with standards and guidelines applicable in the Location as specified in **Sub**

  ** Articles 5.1 and 5.2,** and, if applicable, service level agreement provisions as set out in **Ann ex C**  . Such facilities

shall include sufficient and appropriate air conditioned, cold and deep freeze storage accommodations.

5.10 The Caterer shall provide facilities to ensure the efficient and secure storage of the Carrier’s Inflight

Catering Equipment and Carrier Supplied Items.

5.11 The Caterer shall ensure that all property of the Carrier in the possession of the Caterer, or under its

control, shall be used exclusively for or in relation to the provision of Services to the Carrier and no such proper ty

will be reserved or used for any other purpose nor given to any other third party or person for any purpose

whatsoever without the prior agreement of the Carrier.

5.12 The Caterer shall immediately report to the Carrier's representative all loss of or damage, threatened or

actual, to Carrier’s Aircraft and/or any other property of the Carrier which comes to its attention in the course of

provision of the Services or which in any other way comes to the knowledge of the Caterer.

5.13 The Caterer shall s upervise and manage its own activities and those of its Subcontractors at all Locations.

5.14 The Caterer shall undertake to investigate in a timely manner all written complaints forwarded by the Carrier

in connection with the Services and shall provide a written report of its investigations to the Carrier within 21 days

from receipt of a written complaint.

5.15 If applicable, the Caterer shall comply with the service level agreement provisions set out in **Annex C**

.

5.16 If applicable, the Parties shall at all times during the Term comply with the Ethics Policy set out in **Annex D**

.

### ARTICLE 6. CARRIER’S RIGHT TO CONDUCT INSPECTIONS

6.1 In this Article, all reference to inspection(s) shall include audit(s).

6.2 The Carrier shall be entitled to inspe ct any of the Caterer’s premises or equipment used for the receiving,

cleaning, storage, preparation, production, assembly, dispatch and transportation of all items necessary for or

connected with the provision of the Services, and shall be entitled to ins pect the Services to be furnished to the

Carrier by the Caterer pursuant to this Agreement. Such inspections may be carried out without prior notice

during the Caterer’s normal business hours applicable in the Location, shall not be disruptive to the Cater er’s

normal operations, and shall be without prejudice to the Carrier’s rights to make any later claim against the

Caterer. While on the Caterer’s premises, the Carrier shall obey all applicable safety and security instructions,

whether issued by the Cater er or relevant authorities at the Location. A representative of the Caterer shall be

entitled to accompany the Carrier’s representative(s) during inspections.

6.3 The Parties acknowledge that certain part(s) of the inspections provided for in **Sub**

**- Article**  **6.2** (e.g. a flight

check) may take place outside normal business hours and the Caterer shall not unreasonably deny access to the

Carrier during such hours.

6.4 The Caterer shall co

- operate with the Carrier at all times during an inspection and shall prom ptly provide any

documentation and facilities reasonably requested by the Carrier for the purposes of the inspection.

6.5 The Carrier shall document its findings and shall provide a copy of such document to the Caterer. Where any

remedial action by the C aterer is required in order to rectify failures identified by the Carrier, the Caterer shall

provide an action plan to the Carrier for approval. The Caterer shall implement the approved action plan in

accordance with its terms.

6.6 The Carrier may, by pri or written notice to the Caterer and at its own cost, engage a third party (hereinafter

referred to as the ‘Authorized Representative’) to carry out inspections pursuant to **Sub**

**- Articles 6.2 to 6.5**  . Such

notice shall contain a description of the inspections to be carried out. The Authorized Representative shall have

the same authority as that of the Carrier.



### ARTICLE 7. CARRIER'S LOCAL REPRESENTATION

7.1 The Carrier may, at its own cost, place a representative(s) at all or some of the Location(s). Any arr angement

between the Parties for the supply of office equipment and premises by the Caterer to the Carrier to enable

Carrier representative(s) to perform its(their) duties shall be dealt with under a separate agreement.

### ARTICLE 8. CONFIDENTIALITY AND DATA PROTECTION

8.1 For the purposes of this Article, any reference to Party(ies) shall also be deemed to include their employees,

affiliates, subsidiaries, any Subcontractors and employees thereof.

8.2 The obligations set out in this Article shall surv ive termination or expiry of this Agreement for a period of two

(2) years.

Confidentiality

8.3 For the purposes of this Agreement ‘Confidential Information’ means information or material that is

designated by a Party (‘Discloser’) as confidential at the time of disclosure, or that may be reasonably considered

to be confidential, that has been or may be disclosed to the other Party (‘Recipient’), whether in written, oral or in

another tangible or intangible form, including but not limited to, information c oncerning the business, operations,

projects, technologies and affairs of the Discloser that has been or may be disclosed to the Recipient. For the

avoidance of doubt, all financial and pricing information exchanged by the Parties, whether or not recorded in this

Agreement shall be considered Confidential Information.

8.4 Confidential Information shall not include information which: (a) at the time of disclosure is or becomes

publicly known or within the public domain without the Recipient’s breach of this Agreement; (b) was known to

the Recipient prior to its receipt thereof from the Discloser; (c) has been or is lawfully obtained by the Recipient

from third parties without an obligation of confidence to the Discloser; (d) has been or is subsequently

indep endently conceived or discovered by the Recipient; (e) is approved for release by written authorization of

the Discloser; or (f) is required to be disclosed pursuant to a requirement of law, government agency or rules of

any listing or stock exchange, in w hich event the Recipient will give prompt written notice to the Discloser of such

requirement.

8.5 The Recipient warrants that (i) the Recipient will use the Confidential Information of the Discloser solely for

the purposes of performing its obligations under this Agreement, and will not appropriate it for its own use; and

(ii) the Confidential Information will be kept confidential during the Term and for a period of two (2) years

following termination or expiry of this Agreement.

8.6 Further, the Recip ient warrants that it will only disclose Confidential Information to those employees and/or

Subcontractors who need to know such information for the purposes of this Agreement and who have agreed

prior to such disclosure to be bound by the terms hereof to the same extent as the Recipient or, in the

alternative, who have agreed to be bound by terms similar to the terms hereof. In any event, the Recipient will be

responsible for any breach of this Article by any of its employees and/or Subcontractors as if th e Recipient had

committed the breach.

8.7 All Confidential Information is and shall remain exclusively the property of the Discloser and shall be returned

immediately to the Discloser and/or destroyed at the request of the Discloser upon termination or ex piry of this

Agreement.

8.8 Each Party acknowledges and agrees that the Discloser will have no adequate remedy at law if there is a

breach of these confidentiality provisions and, accordingly, that the Discloser shall be entitled to seek an

injunction or other equitable or preventative relief against the Recipient for such breach. Nothing herein shall be

construed as a waiver of any other legal or equitable remedies that may be available to the Discloser in the event

of a breach or threatened breach of th ese confidentiality provisions and the Discloser may pursue any other such

remedy, including the recovery of damages.Data Protection

8.9 ‘Personal Data’ refers to information relating to an identified or identifiable individual made available by on e

Party to the other Party in connection with this Agreement and includes Sensitive Data. ‘Sensitive Data’ is

Personal Data which consists of information relating to an individual’s racial or ethnic origin, political opinions,

religious beliefs, membership of a trade union, mental or physical health, sexual orientation, or the actual or

alleged commission of a criminal offence including any resulting prosecutions.

8.10 Each of the Parties is responsible for complying with any obligations applying respectiv ely to each of the

Parties under applicable data privacy laws and regulations. Neither Party will make any unreasonable request for

Personal Data, nor shall it request or supply Personal Data beyond what is necessary for it to fulfill the purposes

of this Agreement and for which it is requested or supplied. Each of the Parties will agree in advance as to the

type of Personal Data which it is necessary to make available for the purposes of this Agreement. Any specific

requirements relating to the disclosure or use of Personal Data in a particular Location shall be set out in the

applicable **Annex B**

.

8.11 Each of the Parties acknowledges that it is responsible for determining and implementing appropriate

technological, physical and organizational security meas ures required to protect Personal Data. Each of the

Parties shall adopt technological, physical and organizational security measures reasonably required in order to

protect Personal Data. Each of the Parties will ensure that any third party to whom Persona l Data is transferred

is bound by the applicable terms of these provisions.

8.12 Each of the Parties agrees that Personal Data will only be used, accessed, managed, transferred, disclosed

to third parties or otherwise processed to fulfill the purposes for which it was made available.

8.13 Each of the Parties agrees to reasonably cooperate with the other Party in connection with access requests

for Personal Data. Each of the Parties agrees to reimburse the other Party for any reasonable charges incurred

in providing each other assistance. Each of the Parties agrees to amend Personal Data only upon receiving

instructions to do so from the other Party, the relevant individual or as required by law.

8.14 Each of the Parties will promptly destroy and/or return to the other Party all Personal Data owned by the

other Party which is no longer necessary to fulfill the purposes for which it was made available, unless otherwise

instructed by the other Party, the relevant individual or required by law.



### ARTICLE 9. R EMUNERATION

9.1 In consideration for the Caterer providing the Scheduled Services in a Location the Carrier shall pay to the

Caterer the charges set out in the applicable **Annex B**

.

9.2 In consideration for the Caterer providing the Special Services the C arrier shall pay the charges agreed in

writing with the Caterer from time to time.

9.3 The charges set out in **Annex(es) B** , or fees invoiced to the Carrier in respect of Special Services, are

expressed net of VAT, GST or any other sales tax and shall not i nclude any charges, fees or taxes imposed or

levied by any Airport, Customs or other authorities against the Carrier or the Caterer in connection with the

provision of Services. Such charges, fees and/or taxes that may be charged by the Caterer to the Carr ier shall be

shown separately on any invoice and shall be borne by the Carrier.

9.4 The Carrier shall only be liable to pay for the Services ordered by the Carrier and duly provided to the Carrier

in accordance with this Agreement.

### ARTICLE 10. DISBUR SEMENTS

10.1 Disbursements made by the Caterer for services that are not defined in this Agreement, such as providing

food and beverages for Carrier meetings or providing Inflight Catering Equipment for Carrier cabin crew training

(‘Additional Services’) shall be reimbursed by the Carrier according to conditions mutually agreed in writing

between the Parties from time to time and in advance of such expenses being incurred.



### ARTICLE 11. INVOICES

11.1 The Caterer shall invoice the Carrier at the frequency s et out in the applicable **Annex B** in arrears, for all

Services provided in the preceding invoicing period, at the address and in the currency specified in the applicable

**Annex B** . Invoices shall be accompanied by all relevant supporting documentation in acco rdance with the

Carrier’s requirements.

11.2 Settlement shall be effected by the Carrier through the IATA Clearing House unless otherwise agreed

between the Parties in the applicable **Annex B**

.

11.3 Either Party shall have the right to rectify or seek rect ification of errors made in previous invoices. The

Carrier agrees not to withhold payment in respect of any item which is not disputed by the Carrier, provided that

any payment made by the Carrier hereunder shall be without prejudice to the Carrier’s right s to make any later

claim against the Caterer. Any claim shall be responded to by the Party receiving the claim within thirty (30) days

of receipt of such claim.



### ARTICLE 12. TITLE AND RISK

12.1 Risk for all products, including the responsibility for ensu ring the safe storage and maintaining the quality of

such food and beverages, shall pass to the Carrier when the Caterer has placed them into the designated

stowage positions onboard the Carrier’s Aircraft or wherever the Carrier has specified as the deliv ery point,

however the Caterer acknowledges that delivery to the Carrier shall not relieve the Caterer of any liability for loss

or damage arising from its acts or omissions prior to delivery.

12.2 Title to all non

- perishable items provided by the Caterer to the Carrier shall only pass on payment in full by

the Carrier for such items.



### ARTICLE 13. LIABILITY AND INDEMNITY

13.1 In this Article,

(a) All references to the ‘Carrier’ or the ‘Caterer’ shall include their employees, servants, agents and

Subcontr actors; and

(b) ‘Act or omission’ shall mean any act or omission done negligently or with intent to cause damage or

recklessly and with knowledge that damage would probably result.

13.2 The Caterer shall be liable to the Carrier for any loss or damage to any property owned or operated by or on

behalf of the Carrier, or any loss due to delay, that the Carrier may suffer as a result of the Caterer’s act or

omission arising under or in connection with the provision of the Services.

13.3 The Caterer shall be liable to and shall indemnify and hold harmless the Carrier in relation to claims by third

parties brought against the Carrier for loss or damage suffered as a result of the Caterer’s act or omission

arising under or in connection with the provision of th e Services, including, but not limited to, liability for death,

injury, property loss or damage, delay or infringement of intellectual property rights suffered by such third party.13.4 The Caterer’s liability to the Carrier under **Sub**

**- Articles 13.2 a**  **nd 13.3** shall exclude:

(a) In respect of liability under **Sub**

**- Article 13.2**  only, any indirect or consequential losses, such as loss of profits,

revenue, business opportunity, use of amenity, any special exemplary or punitive damages, or any loss that does

n ot directly or naturally flow from the act or omission giving rise to the loss;

(b) Any loss or damage, to the extent the same arose from or was contributed to by the act or omission of the

Carrier or a third party, including any third party bringing a cla im;

(c) In relation to property damage, any pre

- existing damage, deficiency or standard wear and tear to such

property;

(d) Any loss or damage, to the extent the same arose from or was contributed to by the failure of the Carrier, or

the third party bring ing a claim, to take commercially reasonable efforts to mitigate its loss; or

(e) Any loss or damage, to the extent the same arose from or was contributed to by a Carrier Nominated Product

or Carrier Supplied Item which at the time of delivery to the Cater er’s premises was not in accordance with

standards of hygiene and food safety agreed between the Parties in this Agreement.

13.5 The Caterer’s liability arising under **Sub**

**- Article 13.3**  shall never exceed the Carrier’s own liability towards

the relevant th ird party bringing a claim under applicable laws and Convention.

13.6 The Carrier shall be liable to the Caterer for any loss or damage the Caterer may suffer as a result of the

Carrier’s act or omission, except to the extent such loss or damage was cont ributed to by the Caterer or a third

party or relates to pre

- existing damage, deficiency or standard wear and tear of the Caterer’s equipment,

provided always that the Caterer shall take commercially reasonable efforts to mitigate its loss.

13.7 Each Par ty agrees to cooperate with the other Party in conducting an investigation into any loss or damage,

having reasonable regard to the nature and size of such loss or damage.

13.8 In the event that any claim to be indemnified is made by the Carrier in accor dance with this Agreement, the

Carrier shall give prompt written notice thereof to the Caterer and the Caterer may, at its option, assume control

of, and all expenses related to the defense, settlement, adjustment or compromise of such claim, provided that (i)

the Carrier shall give the Caterer all reasonable support and assistance in defending the claim; (ii) the Carrier

may, if it so desires, employ counsel at its own expense to assist in the handling of such claim and (iii) the

Caterer shall obtain the p rior written approval of the Carrier, which approval shall not be unreasonably withheld

or delayed, before entering any settlement, adjustment or compromise of such claim or ceasing to defend

against such claim, if pursuant thereto or as a result thereof t here would be imposed injunctive or other relief

against the Carrier other than monetary damages fully indemnified by the Caterer.

13.9 The obligations of the Parties under this Article shall survive termination or expiry of this Agreement for a

period o f two (2) years or such other period as may be agreed by the Parties and provided for in **Annex(es) B**

.



### ARTICLE 14. INSURANCE

14.1 The Caterer shall maintain, during the Term, including any Termination Transition Period if applicable,

insurance that is a dequate to cover all claims arising under this Agreement for which the Caterer may be liable to

the Carrier. Any specific insurance amounts agreed between the Parties shall be set out in **Annex(es) B** . The

Caterer shall provide, at any time on request, writt en evidence of such insurance cover to the Carrier in the form

of an insurance certificate.



### ARTICLE 15. DISPUTE RESOLUTION

15.1 In the event of any dispute or claim concerning the scope, meaning, construction or effect of this

Agreement, the Parties shall in the first instance make all reasonable efforts to resolve disputes amongst

themselves through negotiation. Failing mutual resolution of the dispute, the Parties may elect to resolve the

dispute through arbitration under the Rules of Arbitration of the International Chamber of Commerce. The venue,

format and language for the arbitration shall be specified in the applicable **Annex B** . In the event that the Parties

fail to agree to an arbitration process, the dispute shall be settled in accordance with the governing law of this

Agreement as set out in the applicable **Annex B** , excluding conflict of law provisions.

### ARTICLE 16. STAMP DUTIES & REGISTRATION FEES

16.1 Where stamp duties and registration fees may be prescribed under the laws specified in the applicable

**Annex B** for any Location, the allocation of such stamps duties and registration fees between the Parties shall

be set out in the applicable **Annex B**

.



### ARTICLE 17. TERM AND TERMINATION

17.1 This Agreement shall supersede any previous arrangeme nts between the Parties governing provision of the

Services at each Location.

17.2 This Agreement, and any **Annex B** , shall continue in full force unless or until terminated by either Party in

accordance with the terms of this Agreement and/or the relevant **Annex B** if applicable.

17.3 Any specific rights to terminate in respect of a particular Location shall be set out in the applicable **Annex B**

.

17.4 Notwithstanding **Sub**

**- Articles 17.2 and 17.3**  , either Party may at any time terminate this Agreement, or any

**Annex B** , forthwith by written notice to the other Party, at its absolute discretion, in the event that the notified

Party shall be in material breach of any term of this Agreement, and where such breach is capable of remedy the

notified Party shall have f ailed to remedy the same to the satisfaction of the affected Party within thirty (30) days

of such written notice. For the avoidance of doubt, material breaches for the purposes of this Agreement shall

include, but not be limited to:

(a) any failure by th e Caterer to comply with any of the standards of work defined in **Sub**

**- Articles 5.1 to 5.3**  , in

particular, any failure by the Caterer to comply with the Carrier’s requirements on hygiene and food safety, as

well as food and beverage quality;

(b) any failure by the Carrier to settle undisputed invoices, or parts thereof, as per the payment terms set out in

the applicable **Annex B**

.

17.5 In the event of the revocation, cancellation or suspension, wholly or in part, of the Carrier's or the Caterer's

permit(s) o r other authorization(s) to conduct its air transportation services or to furnish the Services, the affected

Party shall notify the other Party without delay. In the event that such revocation, cancellation or suspension

has occurred as a result of an ac t, omission or default of the affected Party, the notified Party may, at its entire

discretion, suspend or terminate this Agreement, or the relevant **Annex(es) B** , on the giving of twenty

- four (24)

hours written notice to the other Party. If such revocation , cancellation or suspension has occurred as a result of

a Force Majeure Event, the notified Party may at its entire discretion suspend this Agreement, or the relevant

**Annex(es) B** , at the effective date of such revocation, cancellation or suspension on the giving of twenty

- four

(24) hours written notice to the other Party.

17.6 In the event of suspension of Services by the Caterer in accordance with **Sub**

**- Article 17.5**  , the Carrier may

at its sole discretion engage a third party to provide the Services until such time as the Caterer is able once

again to perform its obligations in accordance with this Agreement.

17.7 Notwithstanding **Sub**

**- Articles 17.2 and 17.3**  , either Party may terminate this Agreement immediately at any

time if the other Party becomes insolv ent, makes a general assignment for the benefit of creditors, or commits an

act of bankruptcy or if a petition in bankruptcy or for its reorganization or the readjustment of its indebtedness be

filed by or against it, provided the petition is found justifi ed by the appropriate authority, or if a receiver, trustee or

liquidator of all or substantially all of its property be appointed or applied for.

17.8 In the event of this Agreement, or part thereof, being terminated by notice or otherwise, such terminat ion

shall be without prejudice to the accrued rights and liabilities of either Party prior to termination.

17.9 Upon termination of this Agreement, or any **Annex B** , for reasons other than the Caterer ceasing

operations, the Caterer shall:

(a) Continue to perform the Services under the same terms and conditions (including the pricing set forth in

**Annex(es) B** , and if applicable, the service level agreement provisions set forth in **Annex C** ) , at such terminated

location for the duration of any additional transi tion period agreed by the Parties (the ‘Termination Transition

Period’);.and(b) Make all reasonable efforts to cooperate fully with both the Carrier, and any third

- party provider designated

by the Carrier as the Caterer’s successor, in order to achieve a smooth transition between the Caterer and such

third

- party provider.



### ARTICLE 18. FORCE MAJEURE

18.1 Except for any obligation to pay sums already due under this Agreement, each Party shall be exempt from

its obligations hereunder and n either Party shall be liable for any failure to perform its obligations under this

Agreement due to circumstances beyond the Party's reasonable control including, but not limited to, acts of God,

war, strikes by a third party, government regulations, disaster, disease, epid emics, pandemics, quarantine

restrictions, terrorist actions, civil disorders, curtailment of transportation facilities or other emergencies that

make it impractical, inadvisable, illegal or impossible for a Party to perform its obligations under this Agre ement

(‘Force Majeure Events’).

18.2 In the event of suspension of Services or airline operations due to a Force Majeure Event, the affected

Party will immediately notify the other Party specifying the nature of the event and the likely length of suspensi on of Services or airline operations and the Parties shall jointly develop a contingency plan for the provision of

Services or airline operations during the term of any Force Majeure Event, including but not limited to a list of

agreed minimum services.

18.3 Notwithstanding **Sub**

**- Article 18.2** 

, in the event of a suspension of Services by the Caterer pursuant to **Sub**

 

** Article 18.1** the Carrier shall be entitled at its sole discretion, where practically feasible, to engage a third party,

at its own costs, to supp ly the Services for the duration of such suspension.

18.4 If any suspension of Services pursuant to **Sub**

**- Article 18.1**  lasts for more than sixty (60) days, then either

Party may, by notice in writing to the other Party, terminate this Agreement, or any appl icable **Annex B** , by giving

the other party thirty (30) days notice in writing.



### ARTICLE 19. MISCELLANEOUS

19.1 All notices and other communications under this Agreement shall be in writing and in the English language

and either delivered by hand or sent b y courier, registered mail, facsimile or email in each case to the address,

facsimile number or email address of the relevant Party specified in the applicable **Annex B** for each Location

and shall be considered served and received:

(a) In the case of delive ry by hand, upon the day of delivery or upon refusal on presentation;

(b) In the case of registered mail, upon registered receipt by the other Party;

(c) In the case of courier mail, upon registered receipt by the other Party;

(d) In the case of facsimile, upon sending provided the correct answer back is received;

(e) In the case of email, upon recipient read/delivery receipt confirmation.

19.2 This Agreement sets out the entire agreement and understanding between the Parties in connection with

the provisi on of the Services and supersedes and extinguishes any representations previously given or made

with respect to its subject matter. No alteration, modification or addition to this Agreement shall be valid and

binding unless recorded in writing and signed b y a duly authorized representative of both Parties.

19.3 The rights of either Party shall not be prejudiced or restricted by any indulgence or forbearance extended to

such Party or by any delay in exercising or failure to exercise any rights and no waiver by either Party of any

single breach shall operate as a waiver of any other or further breach.

19.4 The relationship of the Parties is that of independent contractors dealing at arm's length. Except as

otherwise stated in this Agreement, nothing in this Agreement shall constitute the Parties as partners, joint

venturers, fiduciaries or co

- owners, or constitute either Party as the agent, employee or representative of the

other, or empower either Party to act for, bind or otherwise create or assume any obl igation on behalf of the

other, and neither Party shall hold itself out as having authority to do the same.

19.5 Subject to the rights that may accrue to any successor or permitted assignees of the Parties, no provision

of the Agreement is be construed a s creating any rights enforceable by a third party, and all third party rights

implied by law are, to the extent permissible by law, excluded from this Agreement.

19.6 If any term of this Agreement is found to be illegal, invalid or unenforceable, in whol e or in part, under any

applicable enactment or rule of law, such term shall, insofar as it is severable from the remaining terms, bedeemed omitted from this Agreement and shall in no way affect the legality, validity or enforceability of the

remaining te rms.

19.7 In case of any inconsistency between the body of the Agreement and its annexes, **Annex(es) B** and if

applicable **Annex C** shall prevail.

19.8 Neither Party shall be authorized to refer to the other Party or to this Agreement in any marketing mater ials

or presentations, or to issue press releases in connection with this Agreement or with any Services, without the

prior written consent of the other Party.

19.9 Any specific requirements concerning the use of Carrier’s Trade Marks shall be set out in **Annex B**

.

19.10 The Parties agree that this Agreement and any documents and notices related thereto and/or resulting

therefrom shall be in English. Any translation hereof shall be for information purposes only and shall not be held

to be binding.

19.11 E xcept as otherwise expressly provided for in this Agreement, each Party will bear its respective expenses

incurred in connection with the preparation, execution and performance of this Agreement and the transactions

contemplated hereby, including all fees and expenses of its legal counsel and other representatives.

19.12 Each Party shall act in good faith in the performance of this Agreement, shall cooperate with the other

Party in relation to all matters concerning the provision of the Services and this A greement, and shall not

unreasonably withhold or delay any action, approval, direction, determination or decision required under this

Agreement.

19.13 This Agreement may be executed in counterparts, each of which shall be deemed to constitute an original,

and both of which together shall constitute one and the same agreement. To evidence execution of an original

counterpart of this Agreement, any Party may send a copy of its original signature on the execution page hereof

to the other Party by facsimile tr ansmission or by email



### STANDARD INFLIGHT CATERING AGREEMENT (SICA)

**ANNEX A**

**– LIST OF INFLIGHT CATERING SERVICES** 

SECTION 1. SECURITY

1.1 The Caterer shall provide, facilitate or arrange for the following, as per applicable requirements of local

author ities and the Carrier

(a) Control of access to the catering facility;

(b) Proper identification and authorization of personnel;

(c) Security check of catering uplifts;

(d) Sealing of food and/or bar trolleys/containers;

(e) Physical examination of caterin g vehicles prior to loading;

(f) Sealing of catering vehicles;

(g) Other security related matters, as set forth in **Annex(es) B**

.



### SECTION 2. PASSENGER AND CREW MEAL SERVICES

2.1 Passenger Meals

2.1.1 The Caterer shall provide all tray sets, dishes and bul k food (e.g. breads, cakes, fresh fruit, etc.) for

passengers in accordance with the Carrier’s Specifications.



### 2.2 Crew Meals2.2.1 The Caterer shall provide all tray sets, dishes and bulk food (e.g. breads, cakes, fresh fruit, etc.) for crew in

accordan ce with the Carrier’s Specifications.



### 2.3 Special Meals

2.3.1 The Caterer shall provide all special meals ordered for passengers and/or crew in accordance with the

Carrier’s Specifications.

2.3.2 The Caterer shall follow instructions provided in the IAT A Passenger Services Conference Resolutions

Manual (RP 1773) when the Carrier uses one of the IATA special meal codes as part of its Carrier Specifications.



### SECTION 3. DRY STORES

3.1 Dry Store Items

3.1.1 The Caterer shall provide Dry Store Items of th e quality and in the quantities specified by the Carrier for the

specific Location. In some cases, the Carrier may provide Carrier Supplied Items or may impose Carrier

Nominated Products.

3.1.2 The Caterer shall, if required by the Carrier, recover Dry S tore Items from in

- bound flights, sort, clean, pack

and account for them, and shall return them to dry stores, unless prohibited by local law.



### 3.2 Dry Stores

3.2.1 The Caterer shall provide facilities to ensure the segregated, efficient and secure storag e of Dry Store

Items.



### SECTION 4. BONDED STORES

4.1 Bonded Store Items

4.1.1 The Caterer shall provide Bonded Store Items of the quality and in the quantities specified by the Carrier

for the specific Location. In some cases, the Carrier may provide Ca rrier Supplied Items or may impose Carrier

Nominated Products.

4.1.2 The Caterer shall recover Bonded Store Items from in

- bound flights, sort, clean, pack and account for

them, and shall return them to bonded stores, unless prohibited by local law.



### 4.2 Bonded Stores

4.2.1 The Caterer shall provide facilities to ensure the segregated, efficient and secure storage of Bonded Store

Items.



### SECTION 5. LAUNDRY SERVICES

5.1 Laundry

5.1.1 The Caterer shall recover all Laundry Items from in

- bound flights and p rovide, facilitate or arrange for the

sorting, washing, dry

- cleaning, ironing, pressing, packing and accounting for them in accordance with the

Carrier’s requirements, and put them back in storage. In some or all Locations, the Carrier may impose Carrier

N ominated Products.



### 5.2 Sub

- Standard Laundry Items

5.2.1 The Caterer shall check all Laundry Items to ensure that sub

- standard items are not dispatched to an

aircraft. The Caterer shall withdraw from service all defective Laundry Items and shall return su ch items to a

location specified by the Carrier for replacement as specified in **Annex(es) B**

.

### 5.3 Storage

5.3.1 The Caterer shall provide facilities to ensure the segregated, efficient and secure storage of all Laundry

Items.



### SECTION 6. INFLIGHT CATERING EQUIPMENT HANDLING

6.1 Cleaning

6.1.1 The Caterer shall empty, sort, clean, inspect and reassemble in accordance with the Carrier’s requirements

Inflight Catering Equipment carried on the Carrier’s Aircraft.



### 6.2 Unserviceable Equipment

6.2.1 The Cater er shall ensure that no equipment is dispatched to an aircraft in an unserviceable condition. The

Caterer shall withdraw from service all defective Inflight Catering Equipment and shall return such equipment to a

location specified by the Carrier in **Annex( es) B**  for replacement or repair.



### 6.3 Storage

6.3.1 The Caterer shall provide facilities to ensure the segregated, efficient and secure storage of all Inflight

Catering Equipment.



### SECTION 7. STOCK CONTROL AND INVENTORY

7.1 Stock Control

7.1.1 The Cat erer shall maintain up to date stock control systems in respect of Dry and Bonded Store Items,

Laundry Items and Inflight Catering Equipment in accordance with the Carrier’s requirements as specified in

**Annex(es) B**

.



### 7.2 Inventory

7.2.1 The Caterer shall conduct inventories of Dry and Bonded Store Items, Laundry Items and Inflight Catering

Equipment in accordance with the Carrier’s requirements as specified in **Annex(es) B**

.



### SECTION 8. CATERING UPLIFT PREPARATION

8.1 Trolley / Container Loading

8.1.1 The Caterer shall load trolleys and containers according to the Carrier’s Specifications.



### 8.2 Staging

8.2.1 The Caterer shall store trolleys and containers containing food and beverages in a chilled or ambient area

as per the Carrier’s Specifications, but al ways in accordance with **Sub**

**- Article 5.2** 

.



### 8.3 Final Assembly

8.3.1 The Caterer shall assemble all trolleys, containers, equipment and passenger amenities to be loaded on

the Carrier’s Aircraft.



### 8.4 Documentation

8.4.1 The Caterer shall prepare all requi red Customs declaration forms, heating and plating instructions for cabin

crew and catering manifests.



### SECTION 9. AIRCRAFT LOADING AND UNLOADING

### 9.1 Transportation

9.1.1 The Caterer shall use approved vehicles and equipment, and licensed drivers for th e transportation,

unloading, loading, and delivery of catering uplifts to and from the Carrier’s Aircraft.



### 9.2 Belly Transfer

9.2.1 The Caterer shall pick up and stow outbound Inflight Catering Equipment recovered from the belly holds in

accordance with the Carrier’s Specifications. The Caterer shall offload and make available inbound Inflight

Catering Equipment for loading into belly holds in accordance with the Carrier’s Specifications.



### 9.3 Aircraft Loading

9.3.1 The Caterer shall stow catering uplift s in accordance with the Carrier’s Specifications.

9.3.2 The Caterer shall comply with the handover procedure set forth in **Annex(es) B**

.



### SECTION 10. SPECIAL SERVICES

10.1 Special Items

10.1.1 The Caterer shall on request of the Carrier, for a fee to b e agreed in advance between the Parties,

provide additional on board items such as birthday cakes, floral bouquets, bottles of champagne and other items

that may be agreed upon from time to time between the Parties.

### AN NEX B

Annex B is used to:

a. Define agreed inflight catering services for a specific Location or group of Locations;

b. Document any modification to Articles 1 to 19 agreed between the Parties;

c. Document any modification to Annex A agreed between the Parties.

Modifications may include text amendments, exclusions and inclusions.

For example, the specific ordering and cancellation procedures agreed between the Parties, the specific

insurance amounts agreed between the Parties, etc. need to be set out in Annex(e s) B.

As many Annexes B as necessary may be used, each Annex being identified as Annex B[1], Annex B[2], etc.

To each Annex B[x] must correspond a Schedule to Annex B[x]

– Agreed Price List.

Required information in the areas shaded yellow must be filled out.

Areas shaded gray should be filled out as required.

Each Annex B may have its own commencement and expiry dates that are independent of the Agreement as a

whole. However, the expiry date of any Annex B may not exceed the expiry date of the Agreemen t.

Annex(es) B that are applicable at the time must be agreed on the date of signature of the Agreement in order to

be incorporated.

New Annex(es) B may be signed by different officers on an on

- going basis during the Term, as appropriate.

The Parties m ay add any additional annex they wish to their agreement, as long as reference to each additional

annex is made in Annex B. In addition, when inserting an annex used in previous agreements, be mindful of not

contradicting Articles 1 to 19, and in particula r the definitions set out in Article 1. Finally, each additional annex

must be referred to as Annex E, Annex F, etc.

### STANDARD INFLIGHT CATERING AGREEMENT (SICA)

**ANNEX B [x]** 

**– AGREED INFLIGHT CATERING SERVICES AND TERMS FOR**  **[LIST**

**LOCATION(S)]**

This Annex B [x] forms an integral part of the Agreement signed between the Parties on [date] day of [month]

, [year]

and is governed by the terms and conditions contained therein.

This Annex B [x] is valid for the following Location(s) [and replaces the Annex B[x] si gned on [date] day of [month],

[year] between the Parties] : [List Location(s)]



### PARAGRAPH 1. DEFINITIONS

[Insert any additional definitions]



### PARAGRAPH 2. PROVISION OF SERVICES

[Insert any modifications to **Article 2** as appropriate]

The Caterer shall provi de the following Scheduled Services in the Location(s):

[Insert below modifications to **Annex A** as appropriate]

A.1 Security

A.1.1

[Insert any specific Carrier requirements in terms of security]

A.2 Passenger and Crew Meal Services

A.3 Dry Stores

A.4 Bonded Stores

A.5 Laundry Services

A.5.2

[Insert procedures for the segregation, handling and replacement of sub

- standard Laundry Items, including the

address where to ship sub

- standard Laundry Items]

A.6 Inflight Catering Equipment Handling

A.6.2

[ Insert procedures for the segregation, handling, repair or replacement of unserviceable Inflight Catering

Equipment, including address where to ship unserviceable Inflight Catering Equipment]

A.7 Stock Control and Inventory

A.7.1

[Insert procedures for stock control of Dry and Bonded Store Items, Laundry Items and Inflight Catering

Equipment]

A.7.2

[Insert procedures for inventory reporting of Dry and Bonded Store Items, Laundry Items and Inflight Catering

Equipment]

A.8 Catering Uplift Preparation

A .9 Aircraft Loading and Unloading

A.9.3.2[Insert procedures for the handover of all galley supplies upon delivery to the Carrier’s Aircraft]

If applicable, the Caterer shall also provide the following Special Services in the Location(s):

A.10 Special Se rvices

[Insert a description of any Special Services]



### PARAGRAPH 3. SUBCONTRACTING, ASSIGNMENT & CHANGE OF OWNERSHIP OR

CONTROL

[Insert modifications to **Article 3** as appropriate]

3.1 Pursuant to **Sub**

**- Article 3.1**  , the following Services shall be subcontra cted to the following companies by the

Caterer:

[List Services and companies]



### PARAGRAPH 4. CARRIER’S OBLIGATIONS

[Insert modifications to **Article 4** as appropriate]



### PARAGRAPH 5. STANDARDS OF WORK

[Insert modifications to **Article 5** as appropriate]

5.2

[Insert description of any specific Carrier requirements in terms of hygiene and food safety]

5.3

[Insert description of any specific Carrier requirements in terms of ramp safety]

5.7

[Insert ordering and cancellation procedures]



### PARAGRAPH 6. CARRIER’ S RIGHT TO CONDUCT INSPECTIONS

[Insert modifications to **Article 6** as appropriate]



### PARAGRAPH 7. CARRIER’S LOCAL REPRESENTATION

[Insert modifications to **Article 7** as appropriate]



### PARAGRAPH 8. CONFIDENTIALITY AND DATA PROTECTION

[Insert modifications to **Article 8** as appropriate]

8.10

[Insert description of any specific requirements relating to the disclosure or use of Personal Data]



### PARAGRAPH 9. REMUNERATION

[Insert modifications to **Article 9** as appropriate]

9.1 The charges for Scheduled Services sha ll be as set out in the Schedule hereto.



### PARAGRAPH 10. DISBURSEMENTS

[Insert modifications to **Article 10** as appropriate]10.1 Any agreed disbursement pursuant to **Article 10** made by the Caterer on behalf of the Carrier shall be

reimbursed at cost plus an accounting surcharge of [Insert percentage] %.



### PARAGRAPH 11. INVOICES

[Insert modifications to **Article 11** as appropriate]

11.1 Invoices

The Caterer shall invoice the Carrier [Insert invoicing cycle] in arrears.

Invoices shall be in [Insert currency ] and shall be addressed to:

[Insert invoicing address]

The payment terms shall be as follows:

[Insert payment terms]

[Insert description of any specific Carrier requirements in terms of supporting documentation for invoicing

purposes]



### PARAGRAPH 12. TIT LE AND RISK

[Insert modifications to **Article 12** as appropriate]



### PARAGRAPH 13. LIABILITY AND INDEMNITY

[Insert modifications to **Article 13** as appropriate]



### PARAGRAPH 14. INSURANCE

[Insert modifications to **Article 14** as appropriate]

14.1 The Caterer sh all acquire insurance coverage as per the following:

[Insert any specific insurance amounts agreed between the Parties]



### PARAGRAPH 15. DISPUTE RESOLUTION

[Insert modifications to **Article 15** as appropriate]

15.1 For the purposes of any local laws, regulat ions and guidelines applicable to the Services at the Location(s)

the place of supply of the Services shall be the Location. This Annex B[ x ] shall be governed by the laws of

[ ] and [Select Subject to the non

- exclusive jurisdict ion of the [ ] Courts OR Subject to

arbitration in [Insert venue, format and language]

.



### PARAGRAPH 16. STAMP DUTIES AND REGISTRATION FEES

[Insert modifications to **Article 16** as appropriate]

16.1 The allocation of any applicable stamp duties and registration fees between the Parties shall be as follows:

[Insert allocation between the Parties]



### PARAGRAPH 17. TERM AND TERMINATION

[Insert modifications to **Article 17** as appropriate]

17.2 Pursuant to **Article 17** , this Annex B [x ] shall be ef fective from [date] day of [month]

, [year] and shall remain

in full force until [date] day of [month]

, [year] or until terminated in accordance with the terms of **Article 17** and/or

this Annex B[ x ].17.3

[Insert any additional termination provisions, e.g. termination for convenience]



### PARAGRAPH 18. FORCE MAJEURE

[Insert modifications to **Article 18** as appropriate]



### PARAGRAPH 19. MISCELLENEOUS

[Insert modifications to **Article 19** as appropriate, including any other terms and conditions]

19.1 Pursuant to **Sub**

**- Article 19.1**  , the address for service of each Party shall be as per below:

19.1.1 Carrier [Postal address] [Fax number] [email address]

19.1.2 Caterer [Postal address] [Fax number] [email address]

19.9 Use of Carrier Trade Marks

[Insert descriptio n of any specific Carrier requirements concerning use of the Carrier Trade Marks]

[Insert Carrier Marks]

[Insert specifications and branding standards, as well as any other directions]

IN WITNESS WHEREOF, the Parties hereto have executed this Annex B [x ]

EXECUTED FOR AND ON BEHALF

OF [CARRIER NAME] BY

Name:

Title:

Date: EXECUTED FOR AND ON BEHALF

OF [CATERER NAME] BY

Name:

Title:

Date:

Name:

Title:

Date: Name:

Title:

Date:

### STANDARD INFLIGHT CATERING AGREEMENT (SICA)

**SCHEDULE TO A NNEX B**  **[x]**

**– AGREED PRICE LIST** 

This Schedule to Annex B [x] forms an integral part of the Agreement signed between the parties on [date] day of

[month]

, [year] and is governed by the terms and conditions contained therein.

Price List

9.1.1

[Insert the a greed price list]

Price List Changes

9.1.2

[Insert the agreed mechanism for price list changes]

Below only provides an example of a mechanism for price list changes.

The Caterer shall have the right at any time to propose modifications to the charges set out in this Price List. Any

notice of a change in charges shall specify the revised charges that the Caterer proposes to introduce, together

with the date on which they are to be brought into effect. No amended charge shall become effective without t he

written agreement of the Carrier such consent not to be unreasonably withheld or delayed. In the event of

agreement to a price change the Caterer shall issue a new Price List.

Notwithstanding the above, when schedule changes as mentioned in **Sub**

**- Article**  **4.2** affect the costs of

providing the services specified, either Party shall have the right to request an adjustment of the charges as from

the date of the relevant schedule change, provided that it does so within thirty (30) days of the schedule change

a nd the other Party consents to the new charges, such consent not to be unreasonably withheld or delayed.

Price Adjustment Formulas

9.1.3

[Insert the agreed price adjustment formulas]

IN WITNESS WHEREOF, the Parties hereto have executed this Schedule to Annex B [x ]

EXECUTED FOR AND ON BEHALF

OF [CARRIER NAME] BY

Name:

Title:

Date: EXECUTED FOR AND ON BEHALF

OF [CATERER NAME] BY

Name:

Title:

Date:

Name:

Title:

Date: Name:

Title:

Date:

### ANNEX C

Annex C only provides an example of a Se rvice Level Agreement.

The Parties are encouraged to define and agree on specific Key Performance Indicators (KPI’s) based on the

Services agreed between the Parties in their agreement.

DRAFTING NOTES

Pursuant to **Articles 5 and 6**

, **Annex A** and **Annex(es) B**  , the Caterer shall provide the Services according to

certain standards and guidelines. Further, pursuant to **Article 4** , the Carrier has agreed to facilitate the Caterer’s

provision of the Services by meeting certain obligations. It is highly recommended that both Parties adopt a list of

Key Performance Indicators (KPI’s) in order to manage their contractual relationship based on facts.

The delivery of Services and achievement of KPI targets must never compromise safety.

The measurement of KPIS’ may be provided by a number of entities including the Carrier, Carrier’s Authorized

Representative and the Caterer. There are three main methods of data gathering that can be used to measure

performance

(a) Specific measurement;

(b) Carrier feedback;

(c) Random sampling.

Specific Measurement

This method provides quantitative data that can be used to report on the performance of the Caterer and/or the

Carrier. Information can be obtained from a number of sources including daily flight statistics, flight reports,

inventory management systems, etc.

Carrier Feedback

Where performance is based on actual events that occur as specific outcomes of Caterer activity, the Carrier

should provide feedback to the Caterer.

Random Sampling

Performance indicators, which cannot be obtained by the above methods, can be obtained from self

- audits

performed by the Caterer, random spot checks performed by the Carrier, and/or inspections performed by the

Carrier or the Carrier’s Authorized Representative.

Penalties

The Parties may als o wish to negotiate penalties based on achieved performance on each KPI.

### STANDARD INFLIGHT CATERING AGREEMENT (SICA)

**ANNEX C**

**– SERVICE LEVEL AGREEMENT** 

KPI 1. Hygiene and Food Safety

Description

The purpose of this KPI is to ensure that high standards o f food safety and hygiene are maintained throughout

kitchen operations, in accordance with ITCA / AEA World Food Safety Guidelines and/or ICQA Food Processing

Safety Standards and Interpretation Guidelines and/or the Carrier’s requirements as applicable an d described in

**Annex(es) B** , as well as all applicable local, national and international laws, rules, regulations and procedures.

Monitoring Requirement

Caterer self audit each calendar month or unannounced external audit.

Performance

The minimum score f or an audit shall be considered to be 90%.

Corrective Action Plans & Timescales

If an audit is conducted and a score of less than 90% is achieved or a failure is observed on one of the critical

control points, then an action plan must be submitted to the Carrier detailing the action that will be taken to rectify

the situation. The timescales for completing any action plan will be as follows:

(a) Within 24 hours if the audit score is below 80% or if a failure in relation to a critical control point is obser ved;

(b) Within 72 hours if the audit score is between 81% and 89% but no critical control points have been failed.



### KPI 2. Ramp Safety

Description

The purpose of the KPI is to ensure that safe operations are maintained on the ramp in order to minimize t he risk

of incidents/accidents involving vehicles, aircraft and employees, in accordance with IOSA Standards and

ISAGO Standards and/or the Carrier’s requirements as applicable and described in **Annex(es) B** , as well as all

applicable local, national and int ernational laws, rules, regulations and procedures. The Caterer shall implement

and maintain a robust ramp safety management system. This should include Standard Operating Procedures

(SOP’s) which detail all safety and procedural aspects of the Caterer’s r amp operations. Additionally the Caterer

shall ensure that a training program is in place for all staff involved in airside operations. This training should

include personal safety and as well as operational vehicle safety. The Caterer should ensure that t he system is

fully documented and available for audit purposes by any interested third parties.

Monitoring Requirements

Caterer self audit on each shift or unannounced external audit.

Performance

The minimum score for an audit shall be considered to be 9 0%.

Corrective Action Plans & Timescales

If an audit is conducted and a score of less than 90% is achieved, then an action plan must be submitted to the

Carrier detailing the action that will be taken to rectify the situation. The timescales for the provi sion of action

plans shall be as follows:

(a) Score between 80% and 89%: 72 Hours

(b) Score under 80%: 24 Hours



### KPI 3. Aircraft Safety

Description

Any damage to aircraft due to catering is a serious business threat. Any incident/accident that occurs must be

followed up with robust corrective action. It is necessary that the Caterer implements and maintains a robust

ramp safety management system as per the requirements of **KPI 2**

.

PerformanceNil incident/accident allowed.

Monitoring Requirements

The Cater er must report any actual incident/accident to the Carrier and will be involved as necessary in any

investigation and will facilitate any insurance claim.

Corrective Action Plans & Timescales

Following any aircraft damage incident/accident an investigati on shall automatically be undertaken by the

Caterer. A report with recommendations shall be produced as a result of the investigation and submitted to the

Carrier. It is expected that the Caterer will take action to implement these recommendations.



### KPI 4 . On Time Performance

Description

The purpose of this KPI is to reduce the occurrence of flight delays attributed to inflight catering and avoid flight

delays of more than 5 minutes attributed to inflight catering.

Performance

No delays of more than 5 m inutes shall be allowed.

Monitoring Requirements

It is required that, for each delay of more than 5 minutes due to inflight catering, a full investigation be

undertaken by the Caterer. The investigation shall confirm whether inflight catering is responsi ble or not for the

alleged delay.

Corrective Action Plans & Timescales

If it is found that a delay can be attributed to the Caterer, the Caterer shall then identify the root causes and put

forward an action plan to prevent recurrence. The corrective actio n report completed by the Caterer must specify

timescales for the implementation of any required action.



### KPI 5. Food Quality

Description

This KPI is designed to assess the quality of the food being produced by the Caterer. The requirements of this

KPI a re designed to assess the overall quality of the food and also to measure how well the food produced

adheres to the Carrier’s menu specifications.

Monitoring Requirements

The Caterer shall

(a) Conduct daily weight and appearance checks on 10 full meals drawn at random from a variety of class of

service;

(b) Conduct twice a week food tasting checks on 10 full meals drawn at random from a variety of class of service;

(c) Record all food item substitutions.

Unannounced external audit based on ICQA Food Proc essing Quality Standards and Interpretation Guidelines.

Performance

Weight and appearance checks: 95% conformance

Food tasting: 85% conformance

Food item substitutions: Less than 2% of items

Corrective Action Plans & Timescales

If at the end of any month the Caterer finds that an aspect of this KPI has been breached the monthly summary

report which is submitted to the Carrier shall be accompanied by a corrective action plan that details the action

that is to be taken across the following month in order to rectify the situation.



### KPI 6. Commissary and Loading Services Quality

Description

This KPI is designed to assess the quality of commissary and loading services delivered by the Caterer. The

requirements of this KPI are designed to assess the Caterer’s p erformance in meeting Carrier’s Specifications in

terms of accurate loading of trolleys and containers. This KPI also measures the Caterer’s performance in terms

of meal overages and shortages.Monitoring Requirements

The Caterer shall conduct

(a) Monthl y 12 checks on compliance with Carrier Specifications in terms of packing plans at pre

- flight check

time, STD

- 3 hours;

(b) Daily 3 checks on accuracy of meal provisioned on board versus final Meal Order.

Performance

Compliance with packing plans: 99% co nformance

Meal provisioned versus Final Meal Order: 99% conformance

Corrective Action Plans & Timescales

If at the end of any month the Caterer finds that an aspect of this KPI has been breached the monthly summary

report which is submitted to the Carrier shall be accompanied by a corrective action plan that details the action

that is to be taken across the following month in order to rectify the situation.



### KPI 7. Communications

Description

This indicator is intended to monitor the Caterer’s customer ser vice performance in terms of communication with

the Carrier and its employees. It also aims to ensure that the root causes of cabin crew negative communications

are investigated and addressed.

Monitoring Requirements

The Caterer shall measure:

(a) Turna round time in acknowledging Carrier communications;

(b) Turnaround time in acknowledging cabin crew communications;

(c) Number of negative feedback from cabin crew.

Performance

Acknowledgment of Carrier communications within 1 business day: 100%

Acknowled gment of cabin crew communications within 1 business day: 100%

Percentage of negative feedback from cabin crew: 2.5%

Corrective Action Plans & Timescales

If at the end of any month the Caterer finds that more than 2.5% of cabin crew communications have be en negative, the monthly summary report which is submitted to the Carrier shall be accompanied by a summary of

negative feedback received from cabin crew and corrective action plans that detail the actions that will be taken

across the following month in o rder to rectify the situation.



### KPI 8. Stock Control / Inventory

Description

The purpose of this KPI is to monitor the Caterer’s performance in maintaining control of the Carrier’s stock.

Monitoring Requirements

The Caterer shall

(a) Measure monthly act ual stock level versus documented stock level for 30 different stock items;

(b) Measure monthly actual stock level versus station allocation for 30 different stock items;

(c) Monthly communicate stock levels to Carrier.

Performance

Actual stock level v ersus documented stock level: 5% variance maximum

Actual stock level versus station allocation: 5% variance maximum

Communication of stock levels: within 2 days of agreed date each month

Corrective Action Plans & Timescales

If it is found that for some s tock items the variance between actual stock level and documented stock level

exceeds 5%, the Caterer shall include in the monthly report to the Carrier an action plan detailing how the

situation may be rectified.



### KPI 9. Inflight Catering EquipmentDescr iption

The purpose of this KPI is to ensure that sufficient Inflight Catering Equipment is available at each Location to

facilitate the Caterer’s provision of the Services.

Monitoring Requirement

Use data compiled as per **KPI 8**

.

Performance

Actual stock l evel versus station allocation:

- 10% maximum.

Corrective Action Plans & Timescales

If the stock level of a particular Inflight Catering Equipment falls below 10% of station allocation within a given

month, the Carrier shall make arrangements to remedy th e situation and investigate the potential causes for this

shortage, and take measures to avoid recurrence.



### KPI 10. Carrier Supplier Items

Description

The purpose of this KPI is to ensure that sufficient Carrier Supplied Items are available at each Locat ion to

facilitate the Caterer’s provision of the Services.

Monitoring Requirement

Use data compiled as per **KPI 8**

.

Performance

Actual stock level versus station allocation:

- 10% maximum.

Corrective Action Plans & Timescales

If the stock level of a part icular item falls below 10% of station allocation within a given month, the Carrier shall

make arrangements to remedy the situation and investigate the potential causes for this shortage, and take

measures to avoid recurrence.

### ANN EX D

Annex D only provides an example of an Ethics Policy.

The Parties are encouraged to define the ethics policy they wish to comply with in their agreement.



### STANDARD INFLIGHT CATERING AGREEMENT (SICA)

**ANNEX D**

**– ETHICS POLICY** 



# CHAPTER 1. ETHICS

1.1 To respect the principles defended by the International Labour Organization

The Parties undertake to respect the principles defended in the Conventions of the International Labour

Organization and, in particular, the abolition of child Labour and the e limination of all forms of compulsory or

forced Labour.

1.2 Not to have recourse to illegal employment and to respect current Labour regulations

The Parties undertake not to employ unregistered workers. In particular, it undertakes to honor all obligation s

with respect to reporting to the administrative, Labour and tax authorities as required in the country concerned.

1.3 To Work Against Corruption

The Parties declare that they forbid the offer or payment of bribes to its customers or to the business asso ciates

of its customers. They also declare that they forbid their employees to request or accept bribes, whether for their

own benefit or that of their families, friends, associates or acquaintances.



# CHAPTER 2. LABOUR ST ANDARDS

2.1 To respect Labour reg ulations as well as all regulations specific to its activities

The Caterer undertakes in particular:

(a) Not to practice any form of discrimination with respect to hiring or personnel management, and to promote

equality in professional treatment;

(b) Not t o use any form of mental or physical coercion, or corporal punishment for disciplinary purposes and;

(c) To respect current legislation with regard to working schedules, remuneration, training, collective bargaining,

health and safety.

2.2 To put in place measures for risk prevention to ensure safety in the workplace, a prime concern in

the conduct of its activities

2.3 To implement quality measures and promote professional training for its personnel

# CHAPTER 3. ENVIRONME NTAL PROTECTION

3.1 To adhere t o the principles of environmental protection.

The Caterer declares that it supports and respects the fundamental principles of environmental protection

through the implementation of an environmental policy aimed at alignment with the best practices in the

profession.

3.2 To respect current environmental regulations

The Caterer undertakes to ensure scrupulous respect of applicable local, national and international regulations in

effect as well as general environmental protection principles in the framework of its activities on behalf of the

Carrier.

3.3 To control the impact of its activities on the environment and to adopt a policy of continuous

improvement

The Caterer undertakes to control the impact of its activities on the environment by adopting measur es to identify

the environmental consequences of these activities. It undertakes to set up a process of continuous improvement

in its management and control of the environmental impact of its activities.

3.4 To promote the principles of this charter among its own partners and suppliers

The Caterer undertakes to promote the principles set forth above in its dealings with its own suppliers, service

providers and/or sub

- contractors. It also assures the Carrier that it will ensure that its suppliers, service

providers and/or sub

- contractors respect all the principles set out in this Policy.

3.5 To agree that either Party may carry out audits to verify application of the principles of this Policy by

the other Party.



### Filing Period: E ffective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

### RECOMMENDED PRACTICE 1788

TICKETING AND BAGGAGE REGULATIONS FOR FREE AND REDUCED

TRANSPORTATION

(amending)

PSC( 31 32 )1788

...

P8

2. TICKETS ISSUED UNDER ID AGREEMENTS

......

Example:

LH/JL/KL

Effective for travel on/after 1 April 2012, tickets issued under the Zonal Employee

Discount (ZED) travel scheme and the Multilateral Interline Business Agreement (MIBA)

travel scheme by one member for travel on another member's service s shall be

electronic tickets. ZED/MIBA members shall not accept other airlines' paper tickets for

staff travel on or after 1 April 2012.

Filing Period: Effective Date:

18 April 2011

- 1 June 2011

23 May 2011

-

## REC OMMENDED PRACTICE 1800

AUTOMATED BAGGAGE HANDLING BASED ON THE IATA LICENCE

PLATE CONCEPT

B9

PSC( 31 32 )1800

... 2. PURPOSE

This document intends to provide a blueprint for automated baggage handling within airline

operations from airline perspective. It gives recommendations to airlines, airports and system

providers of how Baggage Information Messages should be applied in the context of baggage

processes.

It should serve as a guideline for following “standard processes”: Intermodal Receipt/Intermodal

Delivery, Sortation, Screening, Reconciliation, Tracking, Re

- Routing, Re

- Flighting,

offloading/Re

- Loading, Tracing and Re

- Tagging. Guidelines for “specific processes” like “Self

Service Check

- in” (CUSS, HOME) are under development and will be defined in th is document

at a later stage. and Self Service Baggage Processing as defined in RP1701f.

It has been developed by an industry working group consisting of airline, airports and system

provider representatives.

It is recommended that airlines should agree with their Automated Baggage System Business

Partner on the processes supported and message content needed.

...



### B9



# 5. PROCESS DESCRIPTIONS

The following process descriptions relate to so

- called standard processes. Specific processes

such as automate d handling of kiosk

- checked

- in (CUSS) and home

- checked

- in (HOME) will be

defined in this document at a later stage. Self Service Baggage Processing is defined in

RP1701f.

...

### B8.6/P

...

5.2.8 Specific El e ments 'Sortation'

M

– Mandatory

C

– Conditi onal

O

– Optional

.A

- (M) BCM

- BAM

.C

- (O) BTM, BSM, BPM

.D

- ( O C ) BSM

.E

- ( O C ) BTM, BSM, BPM

.F

- (M) BTM; (C) BSM, BPM

.G

- (C) BSM; (O) BTM, BPM

.H

- ( O C ) BSM; BPM ; (O) BCM

- FOM

.I

- (M) BTM; (C) BSM; (O) BPM

.J

- (O) BPM

.N

- (M) BTM, BSM; (C) BPM

.O

- (C) BTM, BSM; (O) BPM

.P

- (M) BTM; ( O C ) BSM, (O) BPM

.R

- (O) BTM, BSM, BPM, BCM

- BAM

.S

- (C) BSM; (O) BPM

.U

- ( O C ) BPM

.V

- (M) all messages used in this process

.W

- (O) BTM, BSM, BPM

.X

- ( O C ) BTM, BSM, BPM



### ...

### ... B8.7/P

5.3.8 Sp ecific Elements 'Screening'

M

– Mandatory

C

– Conditional

O

– Optional

.A

- (M) BCM

- BAM

.C

- (O) BTM, BSM, BPM,

.D

- ( O C ) BSM

.E

- (O) BTM, BSM, BPM; (C) BMM

.F

- (M) BTM, BCM

- BAM; BCM

- DBM; (C) BSM, BPM, (C) BMM

.H

- (O) BMM, BPM

.I

- (M) BTM, BMM; (C) BSM, (O) BPM

.J

- (O) BPM

.N

- (M) BTM, BS M; (C) BPM, BMM

.O

- (C) BTM, BSM; BMM, (O) BPM, BMM

.P

- (M) BTM; ( O C ) BSM, BMM, (O) BPM

.R

- (O) BTM, BSM, BPM, BMM

.S

- (C) BSM; (O) BPM, (O) BMM

.V

- (M) all messages used in this process

.W

- (O) BTM, BSM; (C) BMM

.X

- (O) BTM, BSM, BPM; (C) BMM



### ...

### B8.25/P

5.4.8 Specific Elements 'Reconciliation'

M

– Mandatory

C

– Conditional

O

– Optional

.A

- 

### (M) BCM

- BAM

.B

- 

### (C) BPM, BCM

- FMM

.C

- 

### (O) BTM, BSM, BPM, BUM; (C) BNS; (O) BMM

.E

- 

### ( O C ) BTM, BSM, BPM, BUM; (C) BMM

.F

- 

### (M) BTM, BCM

- FOM/FCM/FMM/DBM; (C) BSM, BPM, (C) BMM

.H

- 

### (O) BTM, BSM, BPM, BUM, BNS, BMM , BCM FOM

, (C) BUM

.I

- 

### (M) BTM, BMM; (C) BSM; (O) BPM, BUM

.J

- 

### (O) BPM , BMM

.N

- 

### (M) BTM, BSM, BUM, BNS , BMM ; (C) BPM , BMM

.O

- 

### (C) BTM, BSM, BNS , BMM; BPM (O), BUM , BMM; BPM

.P

- 

### (M) BTM; (C) BNS; BS M, BMM, BUM ; (O) BPM, BSM, BMM, BUM

.Q

- 

### (C) BPM, BUM, BMM

.R

- 

### (O) BTM, BSM, BPM, BUM, BNS, BCM

- BAM, BMM , BCM FOM

.S

- 

### ( C M ) BSM, ( O C ) BPM, BUM, (O) BMM

.U

- 

### ( O C ) BPM, BUM , BMM

.V

- 

### (M) all messages used in this process

.X

- 

### ( O C ) BTM, BSM, BPM; BUM (C) BMM, ( O) BUM

B8.26/P

... 5.5.8 Specific Elements

M

– Mandatory

C

– Conditional

O

– Optional

.A

- (M) BCM

- BAM

.C

- (O) BPM,

.D

- (N/A) (C) BPM

.E

- (O) (C) BTR, BPM,

.F

- (C) BTR, (C) BPM

.H

- (O) (C) BTR, BPM

.I

- (O) (C) BTR, (O) BPM

.J

- (C) BPM

.N

- (M) BTR, (C) BPM

.O

- (O) (C) BTR, BPM

.P

- (O) (C) BTR, (O) BPM

.R

- (O) BPM

.V

- (M) all messages used in this process

.X

- (O) (C) BPM



### ...

### B8.27/P

5.6.9 Specific Elements

M

– Mandatory

C

– Conditional

O

– Optional

.A

- (M) BCM

- BAM

.B

- (C) BPM

.C

- (O) BTM, BSM, BPM

.D

- ( O C ) BSM

.E

- ( O C ) BTM, BSM, BPM

.F

- (M) BTM, BCM; (C) BSM, BPM

.G

- (C) BSM, BPM, (O) BTM

.H

- ( O C ) BPM

.I

- (M) BTM; (C) BSM; (O) BPM

.J

- (O) BPM

.N

- (M) BTM, BSM; (C) BPM

.O

- (C) BTM, BSM; (O) BPM

.P

- (M) BTM; ( O C ) BSM, (O) BPM

.R

- (O) BTM, BSM, BPM, BCM

- BAM

.S

- (C) BSM, (O) BPM

.U

- (O) BPM

.V

- (M) all messages used in this process

.W

- (O) BTM, BSM

.X

- (O) BTM, BSM, BPM



### ...



### B8.28/P

5.7.8 Specific Elements

M

– Mandatory

C

– Conditional

O

– Optional

.A

- (M) BCM

- BAM

.C

- (O) BTM, BSM, BPM

.D

- (O) BSM

.E

- ( O C ) BTM, BSM, BPM

.F

- (M) BTM, BCM; (C) BSM, BPM

.H

- (O) BPM

.I

- (M) BTM; (C) BSM; (O) BPM

.J

- (O) BPM

.N

- (M) BTM, BSM; (C) BPM

.O

- (C) BTM, BSM; (O) BPM

.P

- (M) BTM, ( O C ) BSM, (O) BPM

.R

- (O) BTM, BSM, BPM, BCM

- BAM

.S

- (C) BSM; (O) B PM

.U

- (O) BPM

.V

- (M) all messages used in this process

.W

- (O) BTM, BSM

.X

- (O) BTM, BSM, BPM

### B8.29/P

5.8.8 Specific Elements ‘Re

- Tagging’

M

– Mandatory

C

– Conditional

O

– Optional

.A

- (O) BCM

- BAM BRQ

.C

- (O) BSM, BPM; ( O C ) BRQ

.E

- ( O C ) BSM, BPM; (C) BRQ

.F

- (C) BSM, BPM; (C) BRQ

.H

- (O) BSM, BPM; ( M C ) BRQ

.I

- (C) BSM; (O) BPM; (C) BRQ

.J

- (O) BPM

.L

- (O) BSM; (C) BPM; (C) BRQ

.N

- (M) BSM; (C) BPM; (C) BRQ

.O

- (C) BSM; (O) BPM; (C) BRQ

.P

- ( O C ) BSM, BRQ (O) BPM; (C) BRQ

.R

- (O) BSM, BPM

.S

- (C) BSM; (O) BPM

.T

- (C) BPM; (C) BRQ

.V

- (M) all messages used in this process

.Y

- (O) BSM, BPM; (C) BRQ

B8.15/P

Section 5.9 Offloading/Reloading

...

5.9.8 Specific El e ments Offloading/Reloading

M

– Mandatory

C

– Conditional

O

– Optional

.A

- 

### (M) BCM

- BAM

.B

- 

### (C) BPM

.C

- 

### (O) BSM, BPM

.E

- 

### ( O C ) BSM, BPM,

.F

- 

### (M) BCM

- BAM; (C) BSM, BPM, BUM

.H

- 

### ( O C ) BSM, BPM, BUM

.I

- 

### (C) BSM; (O) BPM, BUM

.J

- 

### (O) BPM

.N

- 

### (M) BSM, BUM; (C) BPM

.O

- 

### (C) BSM; (O) BPM, BUM

.P

- 

### (C) BSM, BPM, BUM

.R

- 

### (O) BSM, BPM, BUM

.S

- 

### (C) BSM; (O) BPM, BUM

.U

- 

### ( O C ) BPM, BUM

.V

- 

### (M) all messages used in this process

.W

- 

### (O) BSM

.X

- 

### (O) BSM, BPM, BUM

...

### B8.23/P

...

5.10.8 Specific Elements

M

– Mandatory

C

– Conditional

O

– Optional

.A

- 

### (M) BCM

- BAM

.B

- 

### (C) BPM

.C

- 

### (O) BPM

.E

- 

### ( O C ) BPM, (C) BNS

.F

- 

### ( C M ) BPM, (M) BNS

.H

- 

### (O) BPM, BNS

.I

- 

### ( O C ) BPM

.L

- 

### (O) BPM, (C) BNS

.N

- 

### (C) BPM, (M) BNS

.O

- 

### ( O C ) BPM, (C) BNS

.P

- 

### ( O C ) BPM, (C) BNS

.R

- 

### (O) BPM, BNS, BCM

- BAM

.V

- 

### (M) all messages used in this process

.X

- 

### (O) BPM

B8.24/P

...

5.11.8 Specific Elements

M

– Mandatory

C

– Conditional

O

– Optional

.A

- 

### (M) BCM

- BAM

.C

- 

### (O) BTM, BSM, BPM

.D

- 

### ( O C ) BTM, BSM, BPM

.E

- 

### ( O C ) BTM, BSM, BPM

.F

- 

### (M) BTM, (C) BPM

.H

- 

### (O) BTM, BSM, BPM

.I

- 

### (M) BTM, (C) BSM

, (O) BPM

.J

- 

### (O) BPM

.N

- 

### (M) BTM, BSM, (C) BPM

.O

- 

### (C) BTM, BSM, (O) BPM

.P

- 

### (M) BTM, ( O C ) BSM, BPM

.R

- 

### (O) BTM, BSM, BPM

.T

- 

### (O) BTM, BSM, BPM

.V

- 

### (M) all messages used in this process

.X

- 

### ( O C ) BTM, BSM, BPM

.Y

- 

### (O) BTM, BSM, BPM

### B8.5/P

B8 .2/P



### 6. Process Specific Baggage Codes according to IATA RP1745 /ATA RP 30.45

**Note:** S = significant to process; O = nice to have in process Code Description Bag

Messag

e

Element Inter

Modal

Receipt Sortatio

n Security

Screening Security

Transport

Author ization

( Reconciliation) Tracking Off

Loading Re

Loading Tracing Re

Routing Re

Flighting Re

Tagging Inter

modal Remark

...

C Passenger Status:

Checked

- In .S S S 2 O

...

DGR Dangerous goods in

checked baggage .E O S S O O O O O O

...

IROP Irregular

Operations Indicator

in case of

Involuntary

Changes .E O O O O O O O

S O

...

OFF Baggage Loading

Result: Offloaded .B S S S S S

...

R Processing

Informat ion:

Reconciliation .J S O O O O

...



### V Baggage Tag

Status:

Validated .S O S S