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

13 January 2014

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) 62 8

- 9292Summary DOCKET: DOT

- OST

- 2012

- 0058 DOT ORDER: None Requested

Date: 13 January 201 4

Filing fee/IATA Acct: Waived by Order 2012

- 4

- 18, Appendix

A, Section D

US/UST involved Yes

Intended effective date: 1 June 201 4

Meeting site, date: 35 th Pa ssenger Services Conference

(PSC), Dublin

, 31 October

- 1 November

201 3

Agreement(s)/Minutes PSC/RESO/163 dated 23 December 2013

Resolutions 003, 722, 722f, 722g, 722h,

725f, 725g, 725h, 728, 735d, 735e, 736,

740, 745, 752, 753

, 780 and 780e

.

Recommended P ractices 1008, 170 6c,

1707a, 1707b, 1708, 17 15

, 1716, 1717a,

1719, 1719a, 1719b, 1720a

, 1741 , 17 52

, 17 80e, 1790, 1790a and 1797.NOTICE OF TIER 1 AGREEMENTS FILING

Pursuant to statements submitted by Member airlines of the International Air Transport

A ssociation (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

exempted 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 intended effective date of the agreements is 1 June 2014

.

The subject agreements amend or e stablish Resolutions 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 this 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.Respectfully submitted,

/s/ Douglas Lavin

Douglas Lavin

Regional Vice President

– North America

International Air Transport Association

Attorney

- In

- Fact

- 2

-CERTIFICATE OF SERVICE

A copy of this notice has 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

13 January 2014

Date Served

- 3

-

## MINUTES

3 3 rd 

### Joint A 4 A/IATA Passenger Services Conference (JPSC)

3 5 th 

### IATA Passenger Services Conference (PSC)

Dublin

31 October

– 1 November 2013

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

PSC/MINS/ 046

TO: All Members, Passenger Services Conferen ce

- Accredited

Representatives

All Members, Joint A 4 A/IATA Passenger Services Conference

- Accredited Representatives (A 4 A members via Ms P. Edwards)

COPY: IATA Strategic Partners

FROM: Head

, Airline Distribution Standards

DATE: 2 3 December 2013

SUBJ ECT: MINUTES

3 3 rd Joint A 4 A/IATA Passenger Services Conference (JPSC)

3 5 th IATA Passenger Services Conference (PSC)

Dublin, 31 October

– 1 November 2013

Please find attached the Minutes of the 3 3 rd Joint A 4 A/IATA Passenger Services

Conference (JPSC) an d the 3 5 th IATA Passenger Services Conference (PSC) as

approved by the Chairman.

The “expedited resolutions and recommended practices” referred to in these Minutes

are issued under cover of Memorandum PSC/RESO/ 162 dated 29 November 2013

.

The “book of fin ally adopted resolutions & RPs ” is issued under cover of Memorandum

PSC/RESO/ 163 Dated 20 December 2013.

Dave McEwen

International Air Transport Association

Route de l’Aeroport 33

PO Box 416

CH

- 1215 Geneva 15 Airport

Switzerland

T el: +41 22 770 2 086

Fax +41 22 770 2896

www.iata.org E

- Mail: m cewend @iata.org

## M I N U T E S

3 3 rd Joint A 4 A/IATA Passenger Services Conference (JPSC)

3 5 th IATA Passenger Services Conference (PSC)

Dublin, 31 O ctober

– 1 November 2013



### TABLE OF CONTENTS

ADMINISTRATION

Agenda

Item Subject Page Number

A1 Opening of Meeting 1

A2 Examination of Credentials of Accredited

Representatives 1

A3 Approval of Minutes

– JPSC/32 and PSC/34 1

A4 Status of PSC R esolutions and RPs 1

A5 Effectiveness Date of Amendments 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

Agenda

Item Subject **Page Number**

P1 Rep ort

– Status of Industry Coding Systems 2

P2 Ratification of Special Fees and Charges Codes (Resolution 728) 2

P2.1 Ticket Tax Box Service (TTBS) 3

P2.1.1 Report

- Working Session on IATA Cessation of ‘Carrier Specific

Amounts’ filings in TTBS 3

P2.2 Ratification of Payment Card Code (Resolution 728) 3

P3 Report

– Status Report

- BSP Form Codes 4

P4 Report

– Coding Working Group (CODEWG) 4

P5 Co

- ordination with the US Department of Transportation (DoT)

– Initiative for Self

- Assessment 4

P6 Passenger Rights and Conditions of Carriage (RP 1724) 5

P7 Co

- ordination with the Commission of European Communities

(CEC) on PSC Matters 5

P8 Report

– Simplifying the Business (StB) and Think Tank 5

P8.1 Biometrics Multidiscipl inary Working Group (BMWG) 5

P9 Report

– Passenger Distribution Group (PDG) 6

P9.1 Report

– DDX Working Group (DDXWG) 6

P10 Contacts for MITA Concurrences, Correspondence and Billings

(Resolution 780) 6

P10.1 Proration in MITA ( Reso lution 780) 6

P10.2 Provision in MITA to Interline EMDs 6

P11 Handling Disruptive/Unruly Passengers (RP 1798a) 7

P12 Decision of PSC to Remove all Remaining Paper 7

P13 Authentication of Card

- Present and Card

- Not

- Present 7

### AIRPORT SERVICES

Agenda

Item Subject Page Number

B1 Report of the Airport Services Committee (ASC) 8

B2 Report of the A4A Baggage Committee 8

B3 Report of the IATA Ground Handling Council

(IGHC) 8

B4 Report of the Baggage Working Group (BWG) 8

B5 Report of the Baggage Steering Group (BSG) 8

B6 New R e s o l uti on E l e c t r on i c Bag g a ge Clai m

R e c e i pt 8

B7 R e s ol u tio n o n B a gg a g e T r a c ki ng Vot i n g 9

B8 R e c o m men d e d Pr act i c e o n B a gg ag e B r o k e r 9

B9 Updates to R e s o l uti on 7 4 0: Up d a te f or V o tin g 9

B10 Update to Resolution 745

– Dangerous Goods in

Passenger Baggage 9

B11 Report

– Common Use Working Group (CUWG) 9

B11.1 Passenger and Baggage Conformance Services 10

B12 Report

– DCS Messages Working Group

(DCSMWG) 10

B13/P DCS Messages Working Group “Package” 10

B13.1/P Remove SVC and AUX 10

B13.2/P Add ASL Elements to Table 10

B13.3/P Editorial Update 10

B13.4/P Customer Contact Information 11

B13.5/P New PFS Category 11

### TICKETING

Agenda

Item Subject **Page Numb er** 

T1 Report of the Ticketing Committee (TKTcom) 11

T2/P Ticketing “Package” 12

T2.1/P Clarification on Void Exchange Transaction 12

T2.2/P Online Sales of Additional Services in Interline E

- Ticket

Scenarios 12

T2.3/P Updating the ‘Applicable To’ Comments in the

Glossary

- Status Update 12

T2.4/P Update Procedures for the Exchange/Reissue of

Partially Flown Coupons 13

T2.5/P Additional Surcharge Example 13

T2.6/P Ticket Numbers to be Displayed in ITR 13

T2.7/P Rescission of Code ‘OG’ for Ca rbon Offset 13

T2.8/P Removal of Footnotes from RP 1720a Att. A 14

T2.9/P Complete EMD Block Space Codeshare Procedures 14

T2.10/P Delete Reference to ‘Print Line A’ in Data Element

‘Invoice Number’ 14

T2.11/P Delete Data Element ‘Tour Name’ 14

T2.12/P Exchange Reissue Transactions

– Move Definitions 14

T2.13/P Delete Data Element, ‘Sold Date of Flight’ 15

T2.14/P Add ‘Optional’ to ‘Remarks’ Change of Status Request 15

T2.15/P Update Matrix for Total Fare in EMD neutral

Exchange/Reissue Re sponse 15

T2.16/P Stopover Charges in Fare Calculation 15Page Number

T3 Add Remarks Field in Matrix to EMD Airline 16

T4 ATPCO 98X and 99X Sub

- Codes 16

T5 EMD

- S ICW Document Type 16

T6 New Form of Payment

– Mobile Virtual Money

T 7 Glossary and Matrices Review WG

– Report and Items

Requiring Conference Action 17

T8 Exchange and Reissue of EMDs

– Report of EARWG 18

T9 EMD

- A Processing in Change of Gauge (COG) 18

T10 Report of the Premium Economy Fares Working Gr oup 18

T11 Baggage Allowances in Involuntary Rerouting

Scenarios 19

T12 Data Element ‘Previous Coupon Status’ Missing in

EMD Neutral History Display 19

T13 Tax/Fee/Charge Data at the Ticket/Coupon Level

– Corrections to Matrices 20

T14 Date of Birth at Document Level 20

### RESERVATIONS

Agenda

Item Subject Page Number

R1 Report

– A4A/IATA Reservations Committee

(ResCom) 20

R2 Report

- Reservations Working Group

(RESWG) 20

R3/P Reservations “Package ” 20

R3.1/P Revision for PNR Update Message to Advise

EMD Number (for services / fees which are

not filed in ATPCO) 21

R3.2/P Client Identification Procedures 21

R3.3/P SSR ASVC Definition 21

R3.4/P SSR ASVC examples

– editorial changes 22

R 3.5/P Customer Contact Information 22

R3.6/P Customer Contact Information

–

Recommended Practice 22

R3.7/P Add Examples for SSR DOCO Known

Traveler 23

R3.8/P Code Share Agreement

– editorial change 23

### MISCELLANEOUS

Agenda

Item Sub ject Page Number

M1 Report

- PSC Steering Group (PSCSG) 23

M2 Report

- PADIS Board (PADIS) 24

M2.1 Report

– PNRGOV Working Group 24

M2.2 Industry Standard for Reporting Billing Data of Aeronautical

Charges 24

M2.3 PADIS Messaging Week, Septembe r 2013 24

M2.4 Data Model Project 24

M2.5 PADIS Communications Standards Coordination Committee

(CSCC) 24

M2.6 PAXLST Message 24

M3 Report

- Cargo Services Conference (CSC) 25

M4 Report

– Scheduling Services 25

M4.1 Report

– Schedul es Information Standards Committee (SISC) 25

25

M5 Report

– PCI DSS Issues Affecting the Industry 25

M6 Report

– BSP Data Interchange Standards Group (BDISG) 25

M7 Report

– Strategic Partnerships 25

M8 Report

– Travel Partners Standards Council (T PSC) 26

M9 Information Notice: Mandatory Training for Transport of Live

Animals in 2014 261

MINUTES

3 3 rd Joint A4A /IATA Passenger Services Conference (JPSC)

3 5 th IATA Passenger Services Conference (PSC)

Dublin, 31 October

– 1 November 2013



### ADMINISTRATION

A1 Opening of Meeting

1. The Chairman, Mrs. Patricia George, opened the 3 3 rd Joint A 4 A/IATA

Passenger Services Conference (JPSC) and the 3 5 th IATA Passenger

Services Conference (PSC) at 14 00 hours on 31 October 201 3

. She

introduced Rosalie Crabbe (UA), Chair man of the A 4 A Passenger Council.

The attendance list is shown in **Attachment A** 

.

2. Conference noted the anti

- trust warnings regarding discussion on

competitively sensitive topics from IATA as well as from the A4A

.

A2 Examination of Credentials of Accredited Representatives

3. Conference noted the list of IATA PSC accredited representativ es and A4A

Passenger Council representatives.

A3 Approval of Minutes

– JPSC/ 3 2 and PSC/3 4

4. Conference approved as published the Minutes from the 3 2 nd meeting of the

JPSC and 3 4 th meeting of the PSC.

A4 Status of PSC Resolutions & RPs

5. The Secretary, Mr Mike Muller (IATA), reported that he had worked with the

staff of the US DoT to fine

- tune filing procedures for PSC standards using

the “Tier 1” procedures. This resulted in quick declaration of effectiveness

for all the changes adopted by the PSC in 201 2 except for Resolution 787

(enhanced airline distribution) which was filed in the traditional way using

“Tier 3” procedures.

6. The Secretary confirmed that he had filed most of the changes adopted by

the PSC in 2010 and 2011 using “Tier 1” procedures as e xplained in agenda

item P5.2

A5 Effectiveness Date of Amendments to Industry Standards

7. Conference confirmed that the general effective date of 1 June 201 4 would

apply to all amendments regarding Resolutions

, RPs and AIRIMP unless

otherwise agreed.

A6 Election of Chairman and Vice

- Chairman

8. Mrs Patricia George (PSC Chairman) and Stephanie Yen (PSC Vice

Chairman) had come to the end of their term of office and they both indicated

that they would be prepared to stand again for these positions. Noting no

other nominations, the Secretary declared that by acclamation Mrs Patricia

George was re

- elected as PSC Chairman and Stephanie Yen re

- elected as

PSC Vice

- Chairman for three years.

A 7 Any Other Business

9. No other business was presented.

A 8 Date and Plac e of Next Meeting

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

conjunction with the World Passenger Symposium in October 201 4

. Final

confirmation of dates and venue will be advised.

**Secretary note:** it has been decided to hold the 201 4 JPSC/PSC

meeting either in Vancouver or San Diego.

**Secretary note:**  for online information regarding IATA meetings, refer

to : http://www.iata.org/whatwedo/workgroups/Pages/c alendar.aspx



### POLICY

P1 Report

– Status of Industry Coding Systems

11. Conference noted this report.

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

12. Conference agreed to ratify the list of codes shown in **Attachment B**  that

had been a ssigned on a provisional basis since the last meeting of the JPSC

in October 201 2

. Mr Johan Lodewijckx (KL) noted that code SF appeared

twice and the Secretary clarified that the first one for Indonesia should be

deleted as this had been withdrawn shortly after initial assignment

.3

P2.1 Ticket Tax Box Service (TTBS)

13. Conference noted that the Ticket Tax Box Services' comprehensive

database compiles the most current information on all ticketable taxes,

charges and fees applied on passenger air transportati on. Conference was

reminded that in 2008 it agreed to a more flexible interpretation of rules

regarding tax/fee/charge amounts and since that time a gulf had been

created between the plethora of carrier specific amounts as opposed to

“ bone fide ” amounts t hat could be collected on an interline basis and

reflected in the Revenue Accounting Database (RATD).

14. Mr Dave McEwen (IATA) advised that IATA had circulate d a message to the

industry that it is planned to bring the TTBS back to pre

- 2008 status and is

pr ovid ing advance notice of one year regarding cessation of carrier specific

amounts in the TTBS. The PSC Steering Group had endorsed this approach

and s ubsequently a migration plan has been designed in coordination with

ATPCO to include four phases to cove r all carrier specific amounts

worldwide.

15. Mr Johan Lodewijckx (KL) urged IATA to hold more workshops on this issue

(agenda item P2.1.1 refers) so that more airlines could understand and

evaluate the transition of carrier specific amounts from the TTBS to the new

ATPCO product. Mr Tim Powell (Sabre) voiced concern on lack of clarity

regarding the interim period and the migration strategy. Ms Michelle Bryant

(LH) confirmed that her airline had concerns regarding certain definitions and

therefore would find it difficult at this time to endorse the deadline date of 1

August 2014 for final migration. Mr McEwen confirmed that IATA’s intention

is to ensure that the transition is as smooth as possible and that a maximum

amount of members are provided with an opp ortunity to participate in

“working sessions” to understand the issues and provide feedback regarding

the transition. He proposed that the working sessions be given the

opportunity to re

- confirm the deadline date or to propose a more suitable

date.

ACTI ON: IATA/WORK ING SESSIONS

P2.1.1 Report

- Working Session on IATA Cessation of ‘Carrier Specific

Amounts’ filings in TTBS

16. This agenda item reported on the results of the first working session with the

participation of KL, CX, SN, TK, EK and BA. The Se cretary clarified that

these airlines had been invited on the basis that they were most affected in

the markets of Australia and the United Kingdom where the majority of

carrier specific amounts are filed.

P2. 2 Ratification of Credit Card Code (Resoluti on 728)

17. Conference agreed to amend Resolution 728 with the addition of code EL to

identify Elo as a domestic payment card in BSP Brazil. The changes to

Resolution 728 are shown in the book of finally adopted resolutions & RPs,

published separately. The A4A Passenger Council adopted counterpart

changes to SIPP Resolution 110.16.4

P3 Status Report

– BSP Form Codes

18. Conference noted that the BSPs are fast running out of ticket numbers due

to a steady increase in the amount of electronic tickets being issue d and the

pending sharp increase in the amount of EMDs to be issued. It was reported

that a special sub

- group of the TKTcom would meet in November 2013 to

start developing scenarios that would address the long

- term viability of ticket

number management. Mr McEwen (IATA) underlined the critical nature of

the problem and suggested that any solution is likely to cause some pain to

the industry in view that a long

- term solution is required which is why

members need to work closely with the A4A

, ARC , BSP and a ll other

affected industry suppliers

.

ACTION: FORM CODE AND DOCUMENT

WORKING GROUP

19. IATA proposed to mak e various changes to RP 1720a to anticipate the move

from V

- MPDs and V

- MCOs in favor of EMDs. With the exception of form

code 180, all proposed chan ges were agreed as shown in the book of finally

adopted resolutions & RPs with a delayed effective date of 1 July 2014 . The

A4A Passenger Council adopted counterpart changes to SIPP Resolution

20.04 also with a delayed effective date of 1 July 2014.

P4 Report

– Coding Working Group (CODEWG)

20. Conference noted the report of the CODEWG and the Secretary announced

that IATA would withdraw the proposed changes to Resolution 763 at this

time. This is in recognition that the fundamental change from metropolit an

area code concept to the city code concept had not been sufficiently well

drafted in the Resolution and that in any case all proposed changes to

coding resolutions should first be addressed by ResCom before being

considered by the Conference.

ACTION: C ODEWG/ResCom

21. The Secretary noted that Hahn Air was continuing to work closely with the

CODEWG to pursue the establishment of a new service called Global

Consolidation Service (GCS) into Resolution 762 based on a business model

somewhere between that of a CRS and an airline which would require

access to a two

- character “GCS” designator code

. T he Secretary applauded

Hahn Air for developing new and innovative business models , noting that

IATA will always support and encourage the JPSC to consider new,

innov ative solutions for the industry. The Secretary understood that the CRS

of Hahn Air (Hahn Air Systems) was currently using its code H1 for filing

schedules and filing fares which is contrary to the restrictions placed on

codes assigned to CRSs following t he provisions of Resolution 762. Hahn

Air declined to comment.

P5 Co

- ordination with the US Department of Transportation (DoT)

– Initiative for Self

- Assessment5

22. The Secretary confirmed that during 2013 he had started filing PSC

agreements that had been held in abeyance for the last 3 years in

anticipation of action by the US DoT to agree to the Tier 1, 2 and 3 system of

self

- assessment. He advised that the entire backlog of PSC agreements will

have been filed before the end of the year with the vast maj ority being

declared effective within 30 days pursuant to the Tier 1 formalities.

ACTION: SECRETARY

P6 Report

– Passenger Rights and Conditions of Carriage

23. The Secretary noted that over the past years there had been a proliferation

of “ passenger right s ” regimes. Linked to this is the stalemate regarding

IATA’s recommendations for conditions of carriage enshrined in RP 1724

which had been stuck at the US DoT since the year 2000 waiting for

approval. It had been concluded that approval action on RP 172 4 was rather

unlikely in view that certain governments are not in favor of any organization

promulgating recommendations regarding what could be the rights and

responsibilities of airlines and their passengers. Therefore the Secretary

proposed that RP 172 4 be rescinded and this approach had been endorsed

by the PSC Steering Group. Accordingly the PSC agreed to rescind RP

1724 as part of Resolution 003 as shown in the book of finally adopted

Resolution & RPs.

P7 Co

- ordination with the Commission of Euro pean Communities (CEC)

on PSC Matters

24. This report was noted

.

P8 Report

– Simplifying the Business (StB) and Think Tank

25. This report was noted. Mr Claude Muller (IATA) provided a report on

progress of the New Distribution Capability (NDC) initiatives . A copy of his

slides can be found in **Attachment C** . Mr Sebastien Touraine (IATA)

provided news regarding the EMD project and advised that not all BSPs

would be 100% EMD by year end, therefore flexibility had been agreed by

the StB Steering Group for cer tain regions of the world. Accordingly he

suggested that form code 180 should remain active for V

- MPDs (agenda

item P3 refers).

**Secretary note:** documents circulated a few days after the JPSC meeting

containing pertinent details regarding EMDs is shown in **Attachment D**

.

P8.1 Biometrics Multidisciplinary Working Group (BMWG)

26. Conference was advised that the PSC Steering Group had agreed to

establish a Biometrics Multidisciplinary Working Group (BMWG) to build a

common framework on the use of biometrics in aviation. A copy of the

BMWG terms of reference is shown in **Attachment E**

.6

P9 Report

– Passenger Distribution Group (PDG)

27. The PSC noted this report and established the PDG Advisory Forum with

terms of reference as shown in **Attachment F** . The PSC agre ed to extend

the mandate of the PDG itself with amended terms of reference as shown in

**Attachment G**

.

P9.1 Report

– DDX Working Group (DDXWG)

28. Conference noted this report.

P10 Contacts for MITA Concurrences, Correspondence and Billings

(Resolution 780 )

29. AVIANCA, TACA, LACSA and Trans American Airlines noted that the MITA

manual was publishing outdated communications systems that allow airline s

to concur for interlining, e.g. teletype address, telex number and fax number.

These airline s proposed that t he MITA manual and appropriate standards

(Resolutions 660, 780, 780e and RP 1780e) be updated to promote the use

of email addresses as this is nowadays the cheapest and most effective way

to communicate in writing. The PSC agreed to update Resolutions 780

, 780e and RP 1780e as shown in the book of finally adopted resolutions &

RPs. Action on Resolution 660 is for the consideration of the Cargo Services

Conference (CSC).

ACTION: CSC (RESOLUTION 660)

ACTION: SECRETARY (MITA MANUAL)

P10.1 Proration in MITA ( Resolution 780)

30. The Baggage Working Group (BWG) proposed that Resolutions 780 and

780e be updated to allow more accurate and fair calculations on proration

, basing the sharing on actual flown miles. The PSC agreed to amend

Resolutions 780 and 780e as shown in the book of finally adopted

Resolution & RPs.

P10.2 Provision in MITA to Interline EMDs

31. The Secretary noted that whereas Article 2 of MITA Resolution 780

Attachment ‘A’ provides for the issuance of ‘ all other documents necessary

or appropria te for ...transportation’

, there is no specific requirement in MITA

for a separate concurrence to issue and accept Electronic Miscellaneous

Documents (EMDs) as there is for electronic tickets. However there is a

provision to opt out of accepting interline pa per MCOs and excess baggage

tickets.7

32. The Secretary reported that a s the EMD becomes more widely implemented,

members are beginning to think about interlining. As with ETs, in order to

interline an EMD it is necessary to have a separate technical agreemen t

known as a General Business Requirements (GBR) agreement before

members can interline them. However there is no specific provision in MITA

to address this in a similar way as for electronic tickets.

33. To address this gap the Secretary proposed to add a s imilar provision for the

acceptance of interline EMDs whilst adding a requirement to notify IATA

when this has been implemented. IATA will maintain a separate list of

interline EMD agreements in the MITA manual. In addition he proposed to

make a technical correction to Resolution 780 whilst adding the paper

miscellaneous documents and excess baggage ticket “ opt

- out ” facility to

Resolution 780e. The PSC agreed to amend Resolutions 780 and 780e as

shown in the book of finally adopted resolutions & RPs.

P 11 Handling Disruptive/Unruly Passengers (RP 1798a)

34. This item was withdrawn by IATA in recognition that it had not yet been fully

vetted by appropriate security and legal groups.

P12 Decision of PSC to Remove all Remaining Paper

35. Members re

- confirmed th e deadline date for removal of all paper documents

no later than 1 April 2016. It was agreed that TKTcom should update

appropriate resolutions with this deadline date. The Secretary urged all

members to evaluate what they needed to do in order to achieve this

deadline.

ACTION: ALL MEMBERS

36. Mr Jorg Troester (HR) suggested that the Secretary send a note to the ZED

MIBA Forum to advise then of this deadline date.

ACTION: SECRETARY/ZED

- MIBA FORUM

P13 Authentication of Card

- Present and Card

- Not

- Present

37. The Secretary of the BDISG note d that EMV and 3DS specific data elements

are currently not part of DISH standards Revision 20.3 and will not be

included within the upcoming Revision 22. Accordingly it is recommended

that EMV/3DS data formats be defined an d reported (conditionally) on the

RET file and be present on the output HOT, CSI, and CSP files. Additionally

it was recommended that the technical standard be part of the DISH 22.1

version and that a set timeframe is proposed for a global implementation of

EMV/3DS . Subsequently PAConf Resolution 890 and other impacted

resolutions would be aligned . Such action would help significantly in

reducing fraud risk exposure. The PSC agreed with the proposed course of

action.8



### AIRPORT SERVICES

B1 Report of t he Airport Services Committee (ASC)

38. Conference noted this report which advised that the ASC had met

electronically, and endorsed all the agenda items submitted to it.

Membership of the ASC has increased significantly, and the positions of the

Chairman ( US Airways) and Vice

- Chair man (Delta Airlines ) have now been

filled. It was highlighted that t he ASC will be briefed electronically on a more

regular basis in 2014, with mail votes as and when needed, allowing for a

greater overall participation in the Co mmittee

. The 2014 membership of the

ASC is shown in **Attachment H** 

.

B2 Report of the A4A Baggage Committee

39. Conference noted the group’s membership.

B3 Report of the IATA Ground Handling Council (IGHC)

40. Conference noted the report of the IGHC.

B4 Repo rt of the Baggage Working Group (BWG)

41. Conference noted the report of the BWG and agreed to extend the

mandate for the group by a further 12 months. The BWG Chairman, Mr Rick

Nagy (AS), complimented the active participation of airlines, airports and

suppl iers in continuing to show strong innovation for the benefit of the airline

industry.

B5 Report of the Baggage Steering Group (BSG)

42. Conference noted the report of the BSG and agreed to extend its

mandate by a further 12 months. Southwest was elected to fill the vacant

position on the BSG as shown in **Attachment I**

.

B6 New R e s o l uti on E l e c t r on i c Bag g a ge Clai m R e c e i pt

43. The ASC submitted this new resolution because i nnovation in the area of

baggage tagging means that we will see more home printed and perman ent

baggage tags being accepted by airlines. These tags do not have a tear off

baggage claim receipt, so an alternative mechanism needs to be made

available to passenger s , in case their bag should be mishandled. The PSC

agreed to establish Resolution 752 a s shown in the book of finally adopted

resolutions & RPs . The A4A Passenger Council agreed to establish

counterpart Resolution 30.52 as shown in part II of the A4A Minutes

.9

B7 R e s ol u tio n o n B a gg a g e T r a c ki ng Vot i n g

44. The ASC submitted this new resolution, which introduces mandatory

tracking of bag through the recording of delivery and acquisition of the

baggage. Three key tracking points are mandated in the resolution. In order

to allow airlines and airports time to prepare their IT systems and operational

processes, the effective date for this new resolution was proposed as 1 June

2018 . PSC agreed to establish Resolution 753 with a delayed effective date

of 1 June 2018 as shown in the book of finally adopted resolutions & RPs

. The A4A Passenger Council agr eed to establish counterpart Resolution

30.53 with a delayed effective date of 1 June 2018 as shown in part II of the

A4A Minutes

.

B8 R e c o m men d e d Pr act i c e o n B a gg ag e B r o k e r

45. The ASC submitted this new recommended practice, which introduces a

mechanism to share baggage data between systems on an on

- demand

basis, rather than through current fire

- and

- forget messages. PSC agreed to

establish RP 1752 as shown in the book of finally adopted resolutions &

RPs

. The A4A Passenger Council agreed to establish count erpart

Resolution 30.52a as shown in part II of the A4A Minutes

.

B9 Updates to R e s o l uti on 7 4 0: Up d a te f or V o tin g

46. The ASC submitted an updated Resolution 740, which describes the form

of the interline baggage tag. The resolution was updated to show the c orrect

10

- digit licence plate representations of the baggage licence plate barcode,

and also to include the form of the home printed and permanent baggage

tags. The PSC agreed to the updates to 740 as shown in the book of finally

adopted resolutions & RPs

. The A4A Passenger Council agreed to the

counterpart updates in Resolution 30.35 as shown in part II of the A4A

Minutes

.

B10 Update to Resolution 745

– Dangerous Goods in Passenger Baggage

47. The ASC submitted an update to Resolution 745 which mandated t hat

airlines must, rather than should, notify passengers of items to be removed

from their luggage. The PSC approved the updated Resolution 745 as

shown in the book of finally adopted resolutions & RPs

.

B11 Report

– Common Use Working Group (CUWG)

48. Confe rence noted this report and agreed with the proposal to update RP

1706c and RP 1797 to reflect changes that have occurred in the market.

The PSC agreed to the changes in RP 1706c and RP 1797 as shown in the

book of finally adopted resolutions & RPs. The A4A Passenger Council

agreed to counterpart changes in RP 30.100 and RP 30.201 as shown in

part II of the A4A Minutes10

B11.1 Passenger and Baggage Conformance Services

49. The CUWG proposed the establishment of guidelines to facilitate the

standardization of data exchange regarding web services technology to

support common use self

- service bag drop. The PSC agreed to establish

RP 1741 as shown in the book of finally adopted resolutions & RPs. The

A4A Passenger Council agreed to establish counterpart RP 30.1 41 as

shown in part II of the A4A Minutes

B12 Report

– DCS Messages Working Group (DCSMWG)

50. Conference agreed to extend the mandate of the DCSMWG by 12

months.

B13/P DCS Messages Working Group “Package”

51. This “package” contained miscellaneous items do cumented in B13.1/P

through B13.5/P which had been developed by the DCSMWG and endorsed

by the ASC with no opposition noted. The PSC agreed to all proposed

changes in agenda items B13.1/P through B13.5/P as shown in the book of

finally adopted resolutions & RPs , except for B13.4/P which was agreed for

expedited e ffect 1 January 2014 . The A4A Passenger Council agreed to

make counterpart changes to A4A resolutions in agenda item B13. 3 /P as

shown in Part II of the A4A Minutes

.

B13.1/P Remove SVC and AUX

52. D uring the DCSMWG meeting in September 2012, RP 1708 item 2.12.2

was discussed as to whether SVC could be sent on the PNL/ADL message.

The RESWG reviewed this and found it is no longer valid. The DCSMWG

was requested to remove AUX and SVC from the DCS rec ommended

practice s

. The PSC agree d to amend RPs 1707a, 1707b, 1708, 1715, 1716,

1719a and 1719b as shown in the book of finally adopted resolutions & RPs.

B13.2/P Add ASL Elements to Table

53. RP 1719e was approved in the last DCSMWG meeting. The message

elements need ed to be added to the table in 1.3 “ Standard Elements U sed in

DCS Passenger Messages ” of RP 1707b and DL proposed to add the

mandatory, conditional and optional elements of RP 1719e to the table in 1.3

“ Standard Elements Used in DCS Passenger Messages ” of RP 1707b

. ‘AUX’

from 2.24 and 3.38 will be removed from the table in Attachment A_B13.2/P,

and paragraph 3.38 will be renumber ed to 3.39

. The PSC agree d to amend

RP 1707b as shown in the book of finally adopted resolutions & RPs.

B13.3/P Ed itorial Update11

54. Consequent to the adoption of RP 1719e, The DCSMWG identified in the

current RP 1790 that the new RP number needs to be added. The PSC

agree d to amend RP 1790 as shown in the book of fi nally adopted

resolutions & RPs. The A4A Passenger Co uncil agreed to make counterpart

changes to A4A Resolution 10.90 as shown in Part II of the A4A Minutes.

B13.4/P Customer Contact Information

55. RP 1708 currently includes 2.12.6.3 Remarks Element for Passenger

Provided Contact Information. The DCSMWG agr eed that, in accordance

with changes made in AIRIMP 3.20 and 2.11, RP 1708 should be modified to

clarify that it is for emergency contact information. A new section was also

proposed to be added for the Passenger Contact Information Notification for

irreg ular operations

. The PSC agree d to the changes in RP 1708 as shown

with the expedited r esolutions & R ecommended Practices

, for expedited

effect 1 January 2014 to be aligned with the agreements made by the

Passenger Agency Conference (PAConf) for the same subject

.

B13.5/P New PFS Category

56. The category CHGFL allows for recording passengers being transferred

from a flight (which is under irregularity) onto another flight. While th is

category serves its purpose for accounting on the sending flight, the

acc ounting is not served for the receiving flight: For such transfers, there is

currently only the category GOSHO available

– which is understood by the

revenue management systems as additional demand. Consequently, their

forecasts from such flights end up w ay too high. Therefore LH requested

that a new category is introduced, complementing CHGFL.

57. With the new category

, passengers being transferred from another flight

are identified unmistakably, leading to more accurate forecasts and clear

accounting. R ecommended Practice 1707b will not be affected by this and

may remain as is. The PSC agree d to the changes in RP 17 1 9 as shown in

the book of finally adopted resolutions & RPs.



### TICKETING

T1 Report of the Ticketing Committee

58. Conference noted the r eport of the Joint Passenger Ticketing Committee

( TKTcom ) as presented. The Chairman thanked the Committee for its work

done throughout the year.12

59. Conference was advised that the term of office for 6 members was

expiring . A ccordingly BA, EK, KL, LH, MS and US were elected for a three

year period. A copy of the updated membership is shown in **Attachment J** 

.

T2/P Ticketing “Package”

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

through T2. 16/ P which had been approved at TKTcom with no opposition

noted. Agenda item s T2.14/P and T2.16/P w ere withdrawn from the

package for further consideration.

61. The PSC unanimously adopted agenda items T2.1/P through T2.16 /P as

shown in the book of finally adopted Resolutions & RPs as detailed below

.

62. Noting that T2.10/P through T2.13/P were for IATA action only, the A4A

Passenger Council unanimously agreed to counterpart changes in items

T2.1/P through T2.9/P and T2.14/P through T2.16/P as shown in Section II

of the A4A Minutes

.

T2.1/P Clarificatio n on Void Exchange Transaction

63. The Ticketing Committee ( TKTcom ) proposed amendments to resolutions to

clarify void procedures in an exchange transaction.

64. The PSC agreed to amend Resolutions 725f as shown in the book of finally

adopted Resolutions & RPs. The A4A Passenger Council agreed to make

counterpart changes to Resolution 20.66 as shown in Section II of the A4A

Minutes.

T2.2/P Online Sales of Additional Services in Interline E

- Ticket

Scenarios

65. The Ticketing Committee ( TKTcom ) proposed a new Recom mended

Practice to describe procedures for online sales of additional services in

interline e

- ticket scenarios.

66. The PSC agreed to establish Recommended Practice 1790a as shown in the

book of finally adopted Resolutions & RPs. The A4A Passenger Council

ag reed to adopt a counterpart Recommended Pract ice 10.90a as shown in

Section II of the A4A Minutes.

T2.3/P Updating the ‘Applicable To’ Comments in the Glossary

- Status

Update

67. The Ticketing Committee ( TKTcom ) proposed amendments to resolutions to

add a new applicability table to the data elements glossary that would make

it clear which data elements applied to which resolution.13

68. The PSC agreed to amend Resolution 72 2 f as shown in the book of finally

adopted Resolutions & RPs. The A4A Passenger Council agreed to make

counterpart changes to Resolution 20.6 0 as shown in Section II of the A4A

Minutes.

T2.4/P Update Procedures for the Exchange/Reissue of Partially Flown

Coupons

69. The Ticketing Committee ( TKTcom ) proposed changes to IATA Resolutions

722f and 735e to provide a means to identify that an exchange/reissue

transaction was the result of a diversion en route. This is necessary to

determine the place of interruption and perform the correct proration

.

70. The PSC agreed to amend Resolution s 72 2 f and 735e as shown in the book

of finally adopted Resolutions & RPs. The A4A Passenger Council agreed to

make counterpart changes to Resolution 20.6 0 as shown in Section II of the

A4A Minutes

.

T2.5/P Additional Surcharge Example

71. The Ticketing Committee ( TKTcom ) proposed changes to add an additional

example into the Resolution to clarify procedures when ticketing multiple

surcharges applied to consecutive segments within a fare component.

72. The PSC agreed to amend Resolution 72 2 as shown in the book of finally

a dopted Resolutions & RPs. The A4A Passenger Council agreed to make

counterpart changes to Resolution 20. 10 as shown in Section II of the A4A

Minutes

.

T2.6/P Ticket Numbers to be Displayed in ITR

73. Ticketing Committee ( TKTcom ) prop osed changes to clarify procedures for

displaying ticket numbers in the ITR when a conjunction ticket is issued.

74. The PSC agreed to amend Resolutions 722f, 722g, 722h, 725f, 725g and

725h as shown in the book of finally adopted Resolutions & RPs. The A4A

Passenger Council agree d to make counterpart changes to Resolutions

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

A4A Minutes.

T2.7/P Rescission of Code ‘OG’ for Carbon Offset

75. Ticketing Committee ( TKTcom ) proposed to discontinue the use of code

‘ OG’ for carbon offset since it not being used.

76. The PSC agreed to adopt changes to Resolution 722f with an expedited

effectiveness date of 1 January 2014 as shown in the expedited book of

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to14

make counterpart changes to Resolution 20.60 as shown in Section II of the

A4A Minutes.

T2.8/P Removal of Footnotes from RP 1720a Att. A

77. Ticketing Committee ( TKTcom ) proposed to remove outdated footnotes from

RP 1720a/A4A 20.04.

78. The PSC agreed to adopt changes to Recommended Practice 1720a as

shown in the book of finally adopted Resolutions & RPs. The A4A Passenger

Council agreed to make counterpart changes to Resolution 20.04 as shown

in Section II of the A4A Minutes.

T2.9/P Complete EMD Block Space Codeshare Procedures

79. Ticketing Committee ( TKTcom ) proposed to update messaging matrices to

reflect the correct messaging for EMD Change of Status Request in an EMD

blockspace codeshare scenario.

80. The PSC agreed to amend Resolutions 725f, 725g and 7 25h as shown in the

book of finally adopted Resolutions & RPs. The A4A Passenger Council

agreed to make counterpart changes to Resolutions 20.63, 20.64 and 20.66

as shown in Section II of the A4A Minutes.

T2.10/P Delete Reference to ‘Print Line A’ in Da ta Element ‘Invoice

Number’

81. Ticketing Committee ( TKTcom ) proposed to delete reference to ‘Print Line A’

in the data elements glossary.

82. The PSC agreed to amend Resolution 722f as shown in the book of finally

adopted Resolutions & RPs.

T2.11/P Delete Da ta Element ‘Tour Name’

83. Ticketing Committee ( TKTcom ) proposed to delete data element ‘Tour

Name’ from the data elements glossary.

84. The PSC agreed to amend Resolution 722f as shown in the book of finally

adopted Resolutions & RPs

.

T2.12/P Exchange Reissu e Transactions

– Move Definitions

85. Ticketing Committee ( TKTcom ) proposed to move the definitions of

‘Exchange/Reissue Transactions’ from the data elements glossary to the

resolution since there is no specific data element.15

86. The PSC agreed to amend Resolut ion 722f as shown in the book of finally

adopted Resolutions & RPs

.

T2.13/P Delete Data Element, ‘Sold Date of Flight’

87. Ticketing Committee ( TKTcom ) proposed to remove data element ‘Sold Date

of Flight’ as it is redundant.

88. The PSC agreed to amend Resol ution 722f as shown in the book of finally

adopted Resolutions & RPs

.

T2.14/P Add ‘Optional’ to ‘Remarks’ Change of Status Request

89. This item was re moved from the package of items noted under T2/P to be

discussed and voted separately. Ticketing Committee ( TKTcom ) proposed to

add the possibility to optionally add ‘Remarks’ into the EMD G round

–

H andling resolution 725h which would allow ground

- hand ers to add remarks

to an EMD. A Member felt the use of the ‘Remarks’ element should be used

only to reflect ad ditional information as to what the service was at issuance

time only. They were concerned about what a 3 rd party ground

- handler may

add in remarks after the fact . (See also agenda item T3 for proposed

changes to the matrix)

.

90. With 1 IATA Member opposed and 3 abstentions this item was declared

defeated by the Chairperson. There was no motion for an A4A vote.

T2.15/P Update Matrix for Total Fare in EMD neutral Exchange/Reissue

Response

91. Ticketing Committee proposed to add ‘Conditional’ for the response in the

data element ‘Total Ticket/Document Sell Amount’ for ‘Exchange/Reissue’

transactions in the neutral EMD Resolution 725g thereby aligning it with

procedures for electronic tickets.

92. The PSC agreed to amend Resolution 725g as shown in the book of fin ally

adopted Resolutions & RPs. The A4A Passenger Council agreed to make

counterpart changes to Resolution 20.64 as shown in Section II of the A4A

Minutes.

T2.16/P Stopover Charges in Fare Calculation

93. This item was removed from the package of items not ed under T2/P to be

discussed and voted separately. Ticketing Committee ( TKTcom ) proposed

changes to clarify where stopover charges should be place in the fare

calculation noting that the stopover will now be placed directly after the

segment where the sto pover occurs based on the booked itinerary. It was

noted that this was a major change requi ring a considerable amount of re

programming work and that it is such a fundamental change that it would

involve considerable development.16

94. With 1 IATA Member, who requested to abstain by name (SA), and, with no

opposition noted the PSC agreed to amend Resolution 722 as shown in the

book of finally adopted Resolutions & RPs. The A4A Passenger Council

agreed to make counterpart changes to Resolution 20. 10 as shown in

Section II of the A4A Minutes. A Member asked that this item be referred to

the postponed Revenue Accounting meeting due to be held in Montreal in

December.

**Secretary Note :**  This item was presented to the Revenue Accounting

meeting however no discussion w as forthcoming due to shortage of time.

T3 Add Remarks Field in Matrix to EMD Airline

95. Ticketing Committee ( TKTcom ) proposed to add the possibility to optionally

add ‘Remarks’ into the EMD Ground

– Handling matrix in Resolution 725h

which would allow gr ound

- handers to add remarks to an EMD. A Member felt

the use of the ‘Remarks’ element should be used only to reflect additional

information as to what the service was at issuance time only. They were

concerned about what a 3 rd party ground

- handler may add in remarks after

the fact . (See also agenda item T 2.14/P )

.

96. With 1 IATA Member opposed and 3 abstentions this item was declared

defeated by the Chairperson. There was no motion for an A4A vote.

T4 ATPCO 98X and 99X Sub

- Codes

97. Ticketing Committee propo sed to add ‘Reason for Issuance Sub

- Codes’ in

the 98 and 99 series and their definitions into the data elements glossary in

order to make it clear that these codes are available for industry generic

usage and could be interlined.

98. The PSC agreed to amend Resolution 72 2f as shown in the book of finally

adopted Resolutions & RPs. The A4A Passenger Council agreed to make

counterpart changes to Resolution 20.6 0 as shown in Section II of the A4A

Minutes. Additionally Conference recommended IATA work on expand ing

the definitions to provide guidance on their usage.

**Secretary Note** : A proposal will be discussed at the forthcoming EMDTF in

February 2014.

ACTION: EMDTF

T5 EMD

- S ICW Document Type

99. Ticketing Committee proposed to add a new data element indicatin g the type

of document that the EMD

- S was issued in connection with. A Member

questioned the need for this especiall y as an EDIFACT upg rade would be

required and the data element referenced paper tickets. In response a

system provider advised they have a l ot of interest in this requirement noting17

that there is no other way to determine this and a number of projects were

dependent on it.

100. With 10 IATA Members abstaining but with no opposition noted t he

PSC agreed to amend Resolution s 72 2f, 725f, 725g and 72 5h as shown in

the book of finally adopted Resolutions & RPs. The A4A Passenger Council

agreed to make counterpart changes to Resolution s 20.6 0, 20.63, 20.64 and

20.66 as shown in Section II of the A4A Minutes. Additionally Conference

recommended IATA wor k on expanding the definitions to provide guidance

on their usage.

T6 New Form of Payment

– Mobile Virtual Money

101. Ticketing Committee proposed to add a new form of payment to take

account of the growing use of electronic funds transfers via mobile

telep hones in order to differentiate them from cash or payment card

transactions.

102. The PSC agreed to amend Resolution 72 8 as shown in the book of

finally adopted Resolutions & RPs with a delayed effective date of 1 January

2015 . The A4A Passenger Council agre ed to make counterpart changes to

Resolution 110.16 also with a delayed effective date of 1 January 2015 as

shown in Section II of the A4A Minutes.

T7 Glossary and Matrices Review WG

– Report and Items Requiring

Conference Action

103. As a result of a compl ete review of the ET/EMD matrices and dat a

elements glossary

, a number of anomalies were found which require

Conference action. Ticketing Committee proposed a series of amendments

to the ET/EMD data elements glossary and associated matrices.

104. In addition

, Ticketing Committee proposed that the data elements

glossary, the 6 messaging matrices and the Glossary Applicability Reference

Table (GART) be removed from both the IATA and the A4A printed

publications and

, instead

, provide them electronically in one fo rmat only. The

format to be adopted was the A4A format. This will ensure that after all the

effort to synchronize them in 2013, any future changes can be handled using

1 set of matrices only.

105. In order to ensure that any adopted changes to the glossary an d/or

matrices are included and to ensure that they remain synchronized, the

Ticketing Committee proposed that a Glossary and Matrices Maintenance

Group (GMMG) be set up in order to update them . T he Terms of Reference

of this group are shown in **Attachment K** 

.

106. The PSC agreed to amend Resolution 72 2f as shown in the book of

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to

make counterpart changes to Resolution 20.60 as shown in Section II of the

A4A Minutes. JPSC endorsed the new approac h to the publication of the

glossary and messaging matrices as well as the formation of the GMMG18

ACTION: GMMG TO UPDATE GLOSSARY & MATRICES FOR 2014

T8 Exchange and Reissue of EMDs

– Report of EARWG

107. The JPSC noted the report of the Exchange and Reiss ues Working

Group

– EMD and the proposal endorse d by the Ticketing Committee

( TKT com ) to add optional change procedures for EMDs.

108. The PSC agreed to amend Resolution 7 36 as shown in the book of

finally adopted Resolutions & RPs. There was no A4A voting, h owever the

A4A Secretary advised this would be reviewed at their next ticketing

meeting.

109. Additionally it was noted that there remains outstanding work to be

done to define how an EMD will be exchange/reissued

, specifically what the

monetary entries will l ook like since there are no standards for this as well as

attempt to resolve outstanding currency issues especially when multiple

currencies are involved.

ACTION A4A TICKETING COMMITTEE; EARWG

- EMD (as part of TKTWG)

T9 EMD

- A Processing in Change of Gau ge (COG)

110. A group of volunteers were authorized by the Ticketing Committee to

prepare a proposal on how to issue EMD

- As for a non

- ticketed segment

when it forms part of a Change of Gauge (COG) flight since currently

ticketing resolutions require a match b etween the origin and destination of

the ET with the same origin and destination of the EMD.

111. Since it was determined that a standard is urgently required a

proposal was submitted directly to Conference for approval. A package of

changes were proposed incl uding changes to resolution text and additional

data elements as well as background information. It was noted that there is

already a provision to book such services adopted in AIRIMP specifically for

seats but the verbiage in the ticketing resolution spec ifically does not allow

the ticketing.

112. One Member voiced concerns over how this would impact revenue

accounting and felt they could not vote in favor for this proposal

. Another

Member had concerns about what would happen with taxes whilst another

Member had concerns about the expansion of this practice.

113. On a formal vote with two IATA Members opposed and 6 in

abstention, this item was declared defeated by the Chairperson. As a result

of the IATA vote there was no motion by A4A to vote. This item was refe rred

back to the Ticketing Committee for further review.

ACTION: TKTcom

T10 Report of the Premium Economy Fares Working Group19

114. Conference noted the report and presentation provided by the

Premium Economy Fares Working Group (PEFWG) , a group set up by t he

Tariff’s Composite Conference to look at introducing a fourth cabin class to

provide clarity on mixed class fare construction for Premium Economy and to

enable IATA to produce interlineable IATA Flex fares.

115. As a result of the decision of the Composite Conference to adopt th is

proposal, counterpart changes to PSC resolutions were submitted for

Conference a ction.

116. The PSC agreed to amend Resolution s 728, 735d and

Recommend ed Practices 1008 and 1707b as shown in the book of finally

adopted Resolutions & R Ps. The A4A Passenger Council agreed to make

counterpart changes to Resolution s 110.16 and 100.15 as shown in Section

II of the A4A Minutes.

117. With regard to implementation

, it was acknowledged that the adoption

of this new fourth cabin will require close coordination with many other

industry groups and an implementation plan needs to be agreed . Conference

adopted a delayed effective date of 31 October 2014 . A joint Composite

Conference/PSC task force wil l be established to oversee implementation. A

report will be provided to PSC in October 2014 to understand the progress

made to implementation and to evaluate whether these dates are realistic

, or

whether the implementation would need to be deferred following the

assessment received from system providers and Members.

ACTION: Joint Composite Conference/PSC Task Force

T11 Baggage Allowances in Involuntary Rerouting Scenarios

118. This item submitted by a group of airlines (AV, TA, LR and T0) sought

to amend Resolution 735d to specify that the New Operating Car rier should

accept the baggage allowance applicable to the fare and/or baggage see

applicable to the original itinerary at no extra charges or fees unless it is

exceeded in which case the original carrier should be responsible.

119. On a formal vote with three IATA Members opposed and 5

abstentions this item was declared defeated by the Chairperson. It was

note d that this item had not been reviewed by the Ticketing Committee. As a

result of the IATA vote there was no motion for an A4A vote. Carrie r s were

advise d to submit this item to the next Ticketing Committee.

T12 Data Element ‘Previous Coupon Status’ Missing in EMD Neutral History

Display

120. The PSC agreed to amend Resolution 725g as shown in the book of

finally adopted Resolutions & RPs by adding the ‘Prev ious Coupon Status’ to

the EMD neutral history display response which had been inadvertently

omitted. The A4A Passenger Council agreed to make counterpart changes

to Resolution 20.64 as shown in Section II of the A4A Minutes.20

T13 Tax/Fee/Charge Data at the Ticket/Coupon Level

– Corrections to

Matrices

121. The PSC agreed to amend Resolution s 722f, 722g, 722h, 725f, 725g

and 725h to add two data elements, ‘Tax/Fee/Charge Data Coupon Number’

and ‘Tax/Fee/Charge Data Ticket/Document Number’ as shown in the book

of finally adopted Resolutions & RPs in to the Tax/Fee/Charge Data at the

Ticket Coupon Level data group which had been omitted. The A4A

Passenger Council agreed to make counterpart changes to Resolution s

20.60, 20.61, 20.62, 20.63, 2 0.64 and 20.66 as sho wn in Section II of the

A4A Minutes.

T 14 Date of Birth at Document Level

122. The BSP Data Interchange Specifications Group wished to propose

adding a new data element ‘Date of Birth at Document Level’ into the

electronic ticket and electronic miscellaneous documents glossary and

matrices in order to allow accounting systems to validate the date of birth of

the passenger when age

- related discounts are applied . There is currently no

document level element where this is captured. It was noted that this will

all ow the date of birth to be accommodated in the latest DISH V22 which is

soon to be implemented otherwise it will be some considerable time before

the next DISH version is released.

123. The PSC agreed to amend Resolution s 722f, 722g, 725f and 725g as

shown in the book of finally adopted Resolutions & RPs

. The A4A Passenger

Council agreed to make counterpart changes to Resolution s 20.60, 20.61,

20.63, and 20.6 4 as shown in Section II of the A4A Minutes.



### RESERVATIONS

R1 Report

- A4A /IATA Reservations Commit tee (ResCom)

124. Conference noted this report. AC, AF and LH were appointed to the

IATA Reservations Committee as shown in **Attachment L** 

.

R2 Report

- Reservations Working Group (RESWG)

125. Conference noted this report and endorsed the work plan as shown in

**At tachment**  **M**

. Conference agreed to extend the mandate of RESWG for a

further 12 months.

R 3 /P Reservations “Package”

126. This “package” contained miscellaneous items documented in R 3 .1/P

through R 3

. 8 / P which had been approved at ResCom with no opposition

note d. Conference unanimously adopted changes to AIRIMP in agenda21

items R3.1/P through R3.8/P as shown in **Attachments N**  **through T** 

. The

A4A Passenger Council unanimously agreed to counterpart changes to SIPP

in agenda items R3.1/P through R3.8/P also as shown in N **through T** 

.

R 3 .1/P Revision for PNR Update Message to Advise EMD Number (for

services / fees which are not filed in ATPCO )

127. The RESWG agreed to amend examples in AIRIMP 3.12.2.1, where

an EMD is issued under a group name. The amended example was agr eed

with the understanding that currently systems are not capable to issue EMD

with group names, and that it should be used only if a passenger name was

not available . The group also confirmed that that the status code should be

HS1 validating the number o f services provided, which is in line with the

number of SSR. Conference agreed to amend AIRIMP as shown in

**Attachment N** 

. The A4A Passenger Council agreed to counterpart changes

in SIPP also as shown in **Attachment N** 

.

R 3 .2/P Client Identification Procedu res

128. The RESWG proposed to update the SSR CLID description in chapter

3.8.3 to include the possibility to have a SSR CLID client number per PNR if

required. T he proposal is not intended to remove a facility that can be done for

each passenger, rather to ad d more options. The process remains bilateral.

CLID entered associate with all the passengers in the PNR, with the

understanding that passengers not eligible for CLID would not be in the PNR

. Conference agreed to amend AIRIMP as shown in **Attachment O** 

. The A4A

Passenger Council agreed to counterpart changes in SIPP also as shown in

**Attachment O** 

.

R 3 .3/P SSR ASVC Definition

129. After discussion regarding the removal of EMD type, it was agreed

that EMD type should remain in some case s as the data was required b y DCSMWG to trigger processing that may be required by airlines. The

RESWG reviewed if the EMD type needs to be transmitted in all cases and if

such data should be mandatory for certain status codes.

130. Concerns had been expressed on the reliability of EMD type,

particularly the uncertainties of not knowing the validating carrier. The

RESWG agreed on the ‘SSR ASVC Definition’ with an amendment to (c)

Construction

– Transmission of EMD in an SSR ASVC, box (q), and

forward ed the recommendation to ResCom

.

a. The ResCom agreed that EMD type information may be needed in the

response to a SSR ASVC, and when the information is not needed,

this can be indicated by using ‘//’. The group also agreed that the

component should be optional. Conference agreed to amend AIRI MP

as shown in **Attachment P** 

. The A4A Passenger Council agreed to

counterpart changes in SIPP also as shown in **Attachment P** 

.22

R 3 .4/P SSR ASVC examples

– editorial changes

131. Linked to agenda item R3.3/P “SSR ASVC definition for EMD type”,

The RESWG agreed t o update the SSR ASVC examples to remove the EMD

type in reply messages, according to the rule where EMD type must be

transmitted with the EMD number in ASVC HS and should not be transmitted

in any SSR ASVC reply messages. Conference agreed to amend AIRIMP as

shown in **Attachment Q** 

. The A4A Passenger Council agreed to counterpart

changes in SIPP also as shown in **Attachment Q** 

.

R 3 .5/P Customer Contact Information

132. The RESWG agreed to move CTCM and CTCE from OSI to SSR to

facilitate automated format of the c ontact information. The group believed

that the codes should be deleted from OSI, however an airline required that

the codes be kept. To allow for the system development the group discussed

the possibility of introducing a sunset date to be determined at a future

meeting. It was also understood that the OSI is optional information and

despite the deletion of the codes may continue to be used. T he group

expressed concern that the passenger contact information may not be

provided by agents even if the infor mation is made mandatory . PNRs could

also contain fictitious passenger contact information.

133. The RESWG was also concerned with the handling of group PNRs,

as the volume of contact information will be too large. While the group’s

consensus is that only one contact should be entered for group PNRs,

liability of such case needs to be assessed by IATA.

134. Based on the RESWG proposal, ResCom discussed whether

preferred language of communication should also be included in the

information. Whilst it is understood th at airlines cannot be expected to deliver

on the preferred languages, the group agreed to include the information

using the ISO language codes and added examples. It was also understood

that travel agents would need to refer to ISO language code s

.

135. Confer ence agreed to amend AIRIMP as shown in **Attachment R**  for

expedited effect 1 January 2014 to be aligned with the agreements made by

the Passenger Agency Conference (PAConf) for the same subject

. The A4A

Passenger Council agreed to counterpart changes in SI PP also for expedited

effect 1 January 2014 as shown in **Attachment R** 

.

R 3 .6/P Customer Contact Information

– Recommended Practice

136. The Simplifying the Business (StB) steering group proposed to revise the

wording in RP 1770 to align with the updates propos ed in AIRIMP in Agenda

Item 3.5/P “Customer Contact Information”. The PSC agree d to amend RP

1770 as shown with the expedited r esolutions & R ecommended Practices for

expedited effect 1 January 2014 to be aligned with the agreements made by

the Passenger A gency Conference for the same item.23

R 3 .7/P Add Examples for SSR DOCO Known Traveler

137. In order to reduce confusion as well as data quality issues

reported for some of the SSR DOCO messages transmitted to TSA,

A4A proposed, in order to help ensure consiste ncy across the

industry, examples be added in AIRIMP and SIPP for Known

Traveler. Currently there are many variations being used throughout

the industry, which are causing confusion for the users.

138. It was further clarified that it is essential to understan d the difference

between a Redress Number and a Know n Traveler Number. A Redress

Number is provided by DHS to a traveler who has been misidentified by the

DHS Watch list match process. A Known Traveler is the Global Entry, Nexus

or Sentri pass ID number as signed to a traveler. When the Known Traveler

Number is included in the BCBP scanned by TSA at the security check lane,

the passenger qualifies for TSA’s pre

- check program for fast track lanes

through security (where available).

139. It was also noticed there is an error in the cancellation example

for Redress Number. The example states ‘A passenger supplies a

United States Redress number for this PNR’, which is a mistake. The

correction to this example is also included as a part of the proposal.

140. The group als o agreed that further clarification may be required for the

construction rules in Section 3.13.2.2, and this was added to the work plan. It

was also suggested that the Reservations Services Manual is the

appropriate tool to elaborate on the definitions and differences between

‘Known Traveler’ and ‘Redress Number’

141. Conference agreed to amend AIRIMP as shown in **Attachment S** 

. The A4A Passenger Council agreed to counterpart changes in SIPP also as

shown in **Attachment S** 

.

R 3 .8/P Code Share Agreement

– editoria l change

142. In reviewing the Reservations Services Manual 24 th Edition, the

Reservations Services Manual Taskforce (RSMTF) noticed that an editorial

change to the code share definition in AIRIMP section 8.13 is required. The

editorial change has no impact on AIRIMP messaging. Conference agreed to

amend AIRIMP as shown in **Attachment T** 

. The A4A Passenger Council

agreed to counterpart changes in SIPP also as shown in **Attachment T** 

.



### MISCELLANEOUS

M1 Report

- PSC Steering Group (PSCSG)

143. Conference noted this report. The Chairman proposed that the group

meets more than once a year face

- to

- face

.

ACTION: SECRETARY /PSCSG24

M2 Report

- PADIS Board (PADIS)

144. Conference noted this report

. Conference approved the request from

Swiss to join the PADIS Board. The PA DIS Chairman, Mr Dave Weghorst

(DL), urged member airlines to join the Board in view that there were 8 open

slots.

M2.1 PNRGOV Working Group

145. Conference noted this report

.

**Secretary note:** subsequent to the JPSC meeting a group of

governments circulated a letter of appreciation regarding the PNRGOV

Working Group as shown in **Attachment U** 

.

M2. 2 Industry Standard for Reporting Billing Data of Aeronautical Charges

146. Mr Giorgio Camilleri (IATA) reported that IATA had established an

industry working group to develop a standard to facilitate the automated

transmission and reporting of data for billing aeronautical charges with terms

of reference as shown in **Attachment V** 

**.** He urged any volunteers to contact

him directly via email: CamilleriG@iata.org

M2.3 PADIS Messaging Week, September 2013

147. Conference noted this report.

M2.4 Data Model Project

148. Conference noted this report and approved the “operational

stakeholder views” as shown in **Attachment W** 

.

M2.5 PADIS Comm unications Standards Coordination Committee (CSCC)

149. Conference noted this report and endorsed the solution approach

which included a chart showing relevant components in the communications

stack and conceptually how different components relate to each othe r as

shown in **Attachment X** 

.

M2. 6 PAXLST Message

150. The PSC reconfirmed that PADIS will make periodic revisions to the

UN/EDIFACT PAXLST message based on the published revisions of WCO

APICC and to upgrade the IATA PADIS message as soon as practicable.

The PSC also agreed to changes in RP 1717a to incorporate the

development of the XML schemas for the PAXLST message as shown in the

book of finally adopted Resolution & RPs.25

M3 Report

- Cargo Services Conference (CSC)

151. Conference noted this report.

M4 Rep ort

– Worldwide Airport Slots

152. Conference noted this report and agreed that such reports are no

longer required for the JPSC. Members can keep updated by referring to the

IATA website: http://www.iata.org/policy/slots/Pages/slot

- guidelines.aspx

M4.1 Report

- Schedules Information Standards Committee (SISC)

153. Conference noted this report and endorsed the revised terms of

reference as shown in **Attachment Y** 

.

M5 Report

– PCI DSS Is sues Affecting the Industry

154. Conference endorsed the request that members continue to w ork with

the PCI

- SG in order to develop a PCI and EMV Chip & PIN compliant

sol u tion to accept card payments in a common use/shared environment

. Moreover, members should s upport the roles and responsibilities of airlines,

airports, vendors in achieving PCI compliance at airports to develop 3

reference models which will allow airports to make considered compliance

decision s and will provide a uniform way for assessment s

.

155. IATA was requested to m ake a self

- assessment questionnaire

available to Travel Agents and IATA was asked to continue working with the

Card Brands and the PCI Council to facilitate implementing the PCI Standard

in the airline industry. The PSC endorsed th is approach.

M6 Report

– BSP Data Interchange Standards Group (BDISG)

156. Conference noted this report and PSC representatives were urged to

encourage their DISH revenue accounting/IT experts’ involvement in

BDISG/DISH activities

.

ACTION: PSC ACCREDITED RE Ps

M7 Report

– Strategic Partnerships

157. Conference noted this report. The Secretary acknowledged that in

many PSC standards development activities there was strong support and

leadership from employees of Strategic Partner companies. Accordingly he

wan ted to record sincere thanks from IATA and its member airlines for this

continuing strong collaboration.26

M8 Report

– Travel Partners Standards Council

158. The Secretary reported whereas IATA would continue to monitor

intermodal activities, a recent meeting of the StB Steering Group had

advised that this is not a priority for IATA at this time.

M 9 Information Notice: Mandatory Training for Transport of Live Animals in

2014

159. Conference noted this advice that as of 1 October 2013 there is a

requirement for m andatory minimum training for acceptance staff at airports

regarding live animals. More information is available from Ms Andrea

Gruber: grubera@iata.org

Close of Meeting

160. The Chairman closed the meeting at 11.35 hours on 1 November

2013

. Paula Heilig (Travelport) was recognized for her strong and continuing

contribution to industry standards. Mike Muller (IATA) was warmly thanked

for his contributions to the PSC for over 2 decades and the Conference

wished him w ell for his retirement.JPSC/32 PSC/34 Oct 12Attachment: APage: 1 of 3Airline / Company Name First Name Last Name Job Title EmailAdria Airways Tina Jordan Head of Passenger Relations tina.jordan@adria.siAir Canada Janet Wallace Director, Airport Services, Contracts & Administration janet.wallace@aircanada.caAir China Mingzi Li Marketing Passenger Service Regulations Supervisor limz@airchina.comAir China Zhiwei Du Quality Supervision Specialist duzhiwei@airchina.comAir China Mei Su Manager sumei@airchina.comAir France Jean Wieviorka VP Organization and Project jewieviorka@airfrance.frAir France KLM Guillaume Reboul-Salze Dirstibution Projects Manager gureboulsalze@airfrance.frAirlines for America Patricia Edwards managing director passenger services pedwards@airlines.orgAirlines for America James Casey Vice President & Deputy General Counsel jcasey@airlines.orgAirlines Reporting Corporation (ARC) James Keith Venzke Senior Manager - Industry Standards kvenzke@arccorp.comAirlines Reporting Corporation (ARC) Philip Myers Ground Ops Product Development Mgr. pmyers@arccorp.comAlaska Airlines Rick Nagy Director, Airport Experience rick.nagy@alaskaair.comAlaska Airlines Rosalie Hallenbeck Manager, Product Management rosalie.hallenebck@alaskaair.comAmadeus Stephane Aznar Manager stephane.aznar@amadeus.comAmadeus Isabelle Poucet Product Manager ipoucet@amadeus.comAmadeus Daniel Hassellof Sr Business Technology Analyst dhassellof@amadeus.comAmerican Airlines Laurence Chevallay Customer Contact analyst laurence.chevallay@aa.comAmerican Airlines Kris Wilson Sr. Manager Customer Contact kris.wilson@aa.comAmerican Airlines Timothy McMahan Manager timothy.mcmahan@aa.comANA All Nippon Airways Oto Junji Manager, Settlement Services j.oto@ana.co.jpANA All Nippon Airways Mitsue Sato mitsue@ana.co.jpBritish Airways Jerry Foran Head of Product Delivery jerry.foran@ba.comChina Eastern Airlines Jingjing Liu Supervisor jjliu@ceair.comChina Eastern Airlines Qiong Shen Supervisor shenqiong1@ceair.comChina Eastern Airlines Jian Pu Vice Director jamespu@ceair.comChina Southern Airlines Sun Li Manager of passenger rules and regulations sunli_cz@cs-air.comChina Southern Airlines Qianqian Tan Manager of International pricing tanqq@csair.comCroatia Airlines Ivana Janusic Customer RelationsManager ivana.janusic@croatiaairlines.hrDelta Air Lines Stephanie Yen Manager - Industry Affairs stephanie.yen@delta.comDelta Air Lines Dave Weghorst Sr. Business Analyst dave.weghorst@delta.comDelta Air Lines Kendal Chapman Project Leader - Ticekting/Reservations Automation kendal.chapman@delta.comDeutsche Lufthansa AG Michelle Bryant Manager Development Distribution Systems& IATA Indumichelle.bryant@dlh.deEgyptair Hassan Sallam Industry Affairs Specialist industry_aff@egyptair.comEl Al Israel airlines Ltd. Linda Grinfeld Deputy director IATA and Pricing linda@elal.co.ilEmirates Richard Pearl Industry Affairs Specialist richard.pearl@emirates.comFinnair Päivi Rautanen Product Manager paivi.rautanen@finnair.comGoogle Inc Cynthia Towne Sr Product Specialist ctowne@google.comGoogle, Inc. Amy Sexton Sr. Product Specialist amysexton@google.comHahn Air Lines Jörg Troester SVP Corp Strat j.troester@hahnair.comHahn Air Lines Katharina Becker General Counsel k.becker@hahnair.comIATA Alban Sato Manager Tariffs and Reservations Standards satoa@iata.orgIATA David McEwen Head of Airline Distribution Standards mcewend@iata.orgIATA Mike Muller Head. Interline & Intermodal Policy mullerm@iata.orgIATA Patricia George Industry Meeting Chairman pageorge@wanadoo.frIATA Marie Zitkova Manager Messaging Standards zitkovam@iata.orgIATA Aleks Popovich SVP Financial & Distribution Services popovicha@iata.orgIATA THIBAUT RUY Manager e-services ruyt@iata.orgIATA Sebastien Touraine Project Manager, e-services touraines@iata.orgIATA Magali Collot Development Manager collotm@iata.orgIATA Dimiter Zahariev Manager Passenger Experience Development zaharievd@iata.orgIATA Nadarajah Prabaharan Assitant Director praban@iata.orgIATA Paul Behan Head, Passenger Experience behanp@iata.orgIATA Alice Fong Poh Gek Director, DPC and Industry Systems fonga@iata.orgIATA Claude Muller Head, NDC mullerc@iata.orgIATA Michael Thomas Data Model Architect thomasm@iata.comIATA Andrew Price Head of Baggage Services pricea@iata.orgIATA Giorgio Camilleri Manager, Product Management camillerig@iata.orgIATA Cristina Rotor Manager rotorc@iata.orgIATA Daniel Kanter Senior Legal Counsel kanterd@iata.orgIATA Juan Antonio Rodriguez Gil Head of Service Centre rodriguezja@iata.orgIcelandair Anita Knutsdottir Manager Pricing & Interline ak@icelandair.isIcelandair Helga Bjornsdottir Project Manager Pricing & Tariffs dept. helgabj@icelandair.isIcelandair Bryndis Magnusdottir Project Manager Customer Experience bryndism@icelandair.isIcelandair Anna Tomasdottir Manager Ticketing agt@icelandair.isJapan Airlines Noriko Ogawa Manager noriko.ogawa@jal.comJapan Airlines Atsuko Tomura Manager atsuko.tomura@jal.comJapan Airlines Kentaro Kandori Supervisor International Passenger Systems, IT Planninkentaro.kandori@jal.comKLM Royal Dutch Airlines Johan Lodewijckx Manager IATA & Industry Affairs johan.lodewijckx@klm.comKorean Air Keunhae Kim Duputy general manager kimkh@koreanair.comLAN Airlines (LATAM Airlines Group) Maria Picasso Airport Procedures Manager maria.picasso@lan.comLAN Airlines (LATAM Airlines Group) Patricia Nunez Head of Commercial Procedures patricia.nunez@lan.comNavitaire Robin Aborn Software Business Analyst, Associate Manager robin.aborn@navitaire.comPakistan International Airlines Feyaz Ali Shah DEPUTY GENERAL MANAGER khisapk@piac.aeroSAA Madelein Vorster Manager madeleinvorster@flysaa.comSabre Holdings Tim Powell Director Industry Affairs Tim.Powell@Sabre.comSAS Elaine Rusén Manager Industry Affairs elaine.rusen@sas.seSaudi Airabian Airlines Ayed Alotaibi Mgr. airport svcs. prgms. AALOTAIBI@SAUDIAIRLINES.COMSaudi Airabian Airlines Mohammed Alshaikh MANAGER DCS malshaikh@saudiairlines.comSITA John Meeks Manager, Business and Competitive Intelligence john.meeks@sita.aeroSouthwest Airlines Pamela Graham Finance Dept. Business Process Consultant pam.graham@wnco.comSouthwest Airlines Michael Clark Finance Manager Michael.Clark@wnco.comSwiss International Airline Ltd Sonja Kaempf Senior Business Analyst sonja.kaempf@swiss.comTravelport Caroline Wilkinson Senior Product Manager caroline.wilkinson@travelport.comTravelport Paula Heilig Lead Business Analyst paula.heilig@travelport.comTurkish Airlines Ibrahim Gökhan Örmeci IATA Ticketing and Regulations Manager GORMECI@THY.COMTurkish Airlines Diden Alpay Ulucan SPECIALIST DALPAY@THY.COMTurkish Airlines Tugba Yaprak SPECIALIST TYAPRAK@THY.COMUnisys John Kunitz Sr Development Manager john.kunitz@unisys.comUnited Airlines Rosalie Crabbe Mgr. Accessible Programs & Industry Affairs rosalie.crabbe@united.comUS Airways Deryl Purvis SNR ANALYST POLICIES & PROCEDURES DERYL.PURVIS@USAIRWAYS.COMUS Airways Heather Hamel SR. ANALYST AIRPORT POLICIES & PROCEDURES HEATHER.HAMEL@USAIRWAYS.COMUS Airways Simon Bridges Manager, Airport Policies and Procedures simon.bridges@usairways.comVietnam Airlines Hang Nguyen Thuy TARIFFS MANAGER HANGNTT@VIETNAMAIRLINES.COMVietnam Airlines Nhan Nguyen Thi TICKETING EXECUTIVE NHANNT@VIETNAMAIRLINES.COMVirgin Australia Simon Pitt Manager, International Revenue Simon.pitt@virginaustralia.comEndJPSC/ 3 3 PSC/3 5 Oct 1 3

**Attachment: B** 

Page: 1 of 2



### NEW TAX CODES

Since September 2012

Alpha/Alpha codes

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

SH AIRPORT

ADMINISTRATION

CHARGE ANTIGUA

AND

BARBUDA CARIBBEAN

AIRLINES (BW) SEP 20, 2012 TO FUND THE OPERATIONAL COSTS OF AIRPOR

ANTIGUA AND BARBUDA

TK SECURITY FEE AFGHANIST

AN SAFI AIRWAYS

(4Q) OCT 11,

2012 FOR THE PASSENGER SECURITY FACILITIES

VK DEPARTURE CHARGE SAMOA AIR NEW

ZEALAND (NZ) OCT 17,

2012 FOR PROVISION OF AIRPORT SERVICES

YJ AIRPORT SERVICE

CHARGE ST VINCENT

AND

GRENADINE

S LIAT LTD (LI) 0CT 31,

2012 FOR FUNDING AIRPORT FACILITATION

YW EXIT TAX BOLIVIA BOLIVIANA

DE AVIACION

(OB) NOV 2,

2012 GOVERNMENT IMPOSED TAX TO RAISE

REVENUE FOR THE BOLIVIAN GOVERNME NT

YX PASSENGER SERVICE

CHARGE KUWAIT KUWAIT

AIRLINES (KU) NOV 21,

2012 TO COVER THE COST OF SITA SERVICES

YY TOURISM GOODS

AND SERVICES TAX MALDIVES MALDIVIAN

ISLAND

AVIATION

SVCS (Q2) DEC 20,

2012 FOR DOMESTIC AIR SERVICES

ZF SECURITY CHARGE BULGARIA BULGARIA AIR

(FB) JAN18,

2013 TO COVER THE COST OF PASSENGER SECURITY

FACILITIES.

YZ SECURITY CHARGE MALAWI KENYA

AIRWAYS

(KQ) JAN 30,

2013 TO COVER PASSSENGER SECURITY FACILITIES

TY SOLIDARITY TAX CHAD AIR FRANCE

(FR) MAR 7,

2013 TO CONTRIBUTE TO WORLDW IDE SOLIDARITY

AID FOR DEVELOPMENT

WR SAFETY LEVY

INTERNATIONAL TONGA AIR NEW

ZEALAND (NZ) MAR 15,

2013 TO SUPPORT REPAIRS AND MAINTENANCE OF

COMMUNICATION, NAVIGATION AND

SURVEILLANCE EQUIPMENT

ZR INTERNATIONAL API UAE EMIRATES (EK) MAR 25,

2013 TO COVE R THE COST OF API PROJECT

ZK RETENTION INCOME

TAX ARGENTINA AEROLINEAS

ARGENTINAS

(AR) MAR 28,

2013 TO COLLECT IN ADVANCE THE RETENTION INC

TAX FROM PASSENGERS

JB AIRPORT

DEVELOPMENT TAX AZERBAIJA

N HAVA

YOLLARY (J2) APR 12,

2013 TO COVER COST OF INFRA ESTRUCTURE

MODERNIZATION OF THE NEW TERMINAL IN GY

PQ ENVIRONMENT TAX CHAD AIR FRANCE

(FR) MAY 3,

2013 TO CONTRIBUTE FOR THE PROTECTION OF

ENVIRONMENT

SF SECURITY FEE GREENLAN

D AIR

GREENLAND

(GL) MAY 7,

2013 TO COVER COST OF PASSENGER SECURITY FACJPSC/33 PSC/35 Oct 13

**Attachment: B** 

Page: 2

Alpha

- Numeric codes

A1

(suspended) IMMIGRATION FEE SIERRA LEONE BRITISH AIRWAYS

(BA) MAY 31,

2013 FOR UPGRADE OF IMMIGRATION

CONTROL SYSTEM

A2

(suspended) TRANSIT PASSENGER

SERVICE FEE BRAZIL TAM LINHAS

AEREAS (JJ) JUL 22,

2013 COST OF PROVIDING PASSENGER

FACILITIES AND SERVICES

A3 IMMIGRATION USER

FEE CHAD AIR FRANCE (FR) JUL 31,

2013 FINANCE INVESTMENT FOR OPERAT

OF THE IMMIGRATION CONTROL SYJPSC/33 PSC/35 Oct 13

**Att achment:**  **C**

Page: 1 of 1

#  Resolution 787 remains pending before the U.S. Department of

Transportation (DOT). While DOT is under no deadline, a decision is

expected this fall.

 Standard Development

– Until now, the focus has been on the

shopping domain. The business requirements and the supporting

schemas for this functional domain are being finalized, subject to

approval of Resolution 787 by DOT.

 Pilot phase proceeding as planned. 5 pilots kicked

- off. Additional 5

pilots in pipeline.

 Adoption

– PDG Advisory Forum. Drive a common industry

perspective on key topics through the inclusion of airlines, agents

and providers. Make recommendations to PDG to improve the NDC

standard for the benefits of the customers and the air travel

distribution value chain

1 

# NDC status vs. targets

NDC Update

# The NDC Roadmap

Resolution 787

2012 2013 2014 2015 2016 Shopping

Booking &

Servicing

Payment & Ticketing

Reporting, Settlement & Agency Accounting Interface

Interline

Airline Profile 

## NDC 1.0 Capability Deployment

Industry Pilots

NDC XML

Schemas Industry

Pilots Capability

Deployment

# NDC Industry Pilots

Active pilots Endeavor: AA, JRT

SkyCouch: NZ , JRT



## Pipeline Chinese Airlines (2) Airline Profile

North American Airlines (2)

European Airline

Australian Airline Alpine: LX, Datalex, PROS, HP

SkyDreamer : HU, Travelsky, CTBA

Sunshine: CZ, Travelsky, Ctrip

2013:Q1 Q2 Q3 Q4 2014: Q1 Q2 Q3 Q4

Demonstrator V1 Demonstrator V2 Demonstrator V3

NDC Update

#  End

- to

- end processed

– As attention now moves on from Shopping,

it becomes important to agree the remaining end

- to

- end processes

. The goal being to very much complete the vision of NDC as allowing

airlines to take control of their indirect sales distribution but still

disrupt as little as possible of other processes.

 Alignment

– Members are being encouraged to discuss these end to

end requirements with their colleagues in other functional

departments affected by these activities

– most notably in

Reservation Systems, Revenue Management and Revenue

Accounting.

4 

# Key issues

NDC Update

#  To draw attention of members to the likely process changes under

NDC in both interim and final status.

 To ask members to discuss these proposed processes with

colleagues on the PDG and DDX Working Groups to ensure

alignment.

5 

# Recommendations

NDC UpdateJPSC/33 PSC/35 Oct 13

**Attachment: D** 

Page: 1 of 1JPSC/33 PSC/35 Oct 13

**Attachment: E** 

Page: 1 of 1

BIOMETRICS MULTIDISCIPLINARY WORKING GROUP (BMWG)

TERMS OF REFERENCE

1. ESTABLISHMENT OF THE GROUP

a. A Group is established to formulate the use of biometrics throughout

the 14 steps of Passenger Experience.

b. The Group shall report to the Passenger Experience Management

Group (PEMG). The Group shal l consist of IATA & A4A Member

Airlines, ACI Member Airports, Governments, IATA Strategic

Partnership participants and Checkpoint of the Future Expert Groups.

2. FUNCTIONS OF THE GROUP

The main functions of the Group are:

a. To develop options and use case sce narios for Identity Registration,

Authentication, Enrolment and Verification processes to capture

passenger biometrics and use them throughout the journey;

b. To develop recommendations for standards and best practices for the

use of biometrics;

c. To submit a r eport of its activities to each PEMG meeting;

d. To liaise closely with other working groups

– Fast Travel Working

Group, Passenger Facilitation Working Group, Common Use Working

Group and Checkpoint of the Future

.

3. MEETINGS OF GROUP

a. The Group shall meet as required but no less than once per year. A

Group quorum shall consist of not less than 6 members.

b. The Group shall elect its own Chairperson and Vice

- Chairperson from

voting members.

c. Registered IATA, A4A or ACI Member, Governments, IATA Strategic

Partnersh ip participants and Checkpoint of the Future Expert Groups

members may attend meetings.

d. IATA and A4A members may vote.

e. Recommendations of the Group shall be submitted to PEMG.

f. The Group shall determine its own working procedures and may

establish further s ub

- groups as it determines necessary.

4. ELECTIONS OF CHAIRPERSON AND VICE

- CHAIRPERSON

The BMWG will elect a Chairperson from an A4A/IATA airline member. The BMWG

will elect a Vice

- Chairperson from a Government or an Airport company.JPSC/33 PSC/35 Oct 13

**Attachment: F** 

Page: 1 of 1

PDG Advisory Forum (AF)

Terms of Reference

The PDG Advisory Forum is established by the Passenger Distribution Group (PDG) with the

following terms of reference.

Objectives

• Drive a common industry perspective on k ey topics through the inclusion of airlines, agents

and providers

• Ensure ease of deployment and encourage broad

- based adoption of NDC by industry

stakeholders including airlines, GDSs, IT providers, and the travel trade, benefitting

customers

• Make recomm endations to PDG to improve the NDC standard for the benefits of the

customers and the air travel distribution value chain

Appointments

• The PDG AF will comprise a group of companies from across the value chain with a wide

spectrum of perspective and a ba lanced geographical representation: airlines, GDS, IT

companies, travel agents and corporate buyers

• The number of participants is limited to a maximum of 15 organizations in order to promote

interactions.

• The PDG AF members will be appointed upon invitat ion by the PDG Chair to ensure

cohesiveness.

• The PDG AF Chair will facilitate the discussion and report progress, outcomes and

submissions to PDG; the PDG AF Chair will be appointed by the PDG Chair.

Meetings

• Annual in

- person meetings at IATA’s Head (Mo ntreal), Executive (Geneva), or Regional

offices.

• Regular calls (monthly or quarterly)

• Meeting agendas shall be circulated in advance of each meeting for review and comments by

delegates; meeting minutes shall be circulated following each meeting.

Part icipation

• Each appointed organization may send one delegate to PDG AF meetings.

• Active participation is required. Participants will have seniority and authority to represent their

organization and make decisions on their behalf.

• Due to the limited number of seats, absence for two consecutive meetings will trigger a review

of membership of the company concerned and the seat may be offered to a new participant.

Decisions

• Recommendations from PDG AF, whether consensus or disparate views, will be reported t o

the PDG for consideration; in order to ensure effective support of the items in PDG, at least

one airline member of PDG AF needs to sponsor the submission.

• Final decisions on recommendations will be made by the PDG and communicated to PDG

AF.

Administ rative

• The PDG AF will have a one

- year mandate (usual IATA term, renewable as required) and will

report to the PDG with recommendations.

• IATA will carry out the role of Secretary of the PDG AFJPSC/33 PSC/35 Oct 13

**Attachment: G** 

Page: 1 of 1

Pas senger Distribution Group (PDG)

Terms of Reference

The Passenger Distribution Group is established by the Passenger Services Conference (PSC) with

the following terms of reference.

Objectives

• Set a vision for multi

- channel airline distribution

• Promote t he benefits of NDC

• Encourage broad

- based adoption of NDC by industry stakeholders including airlines, GDSs,

• Distributors, and the travel trade, benefitting customers

• Validate the strategy and industry business case and requirements

• Act as an industry voice on airline distribution

• Define key industry messages for distribution

- related matters

• Review progress of IATA projects in distribution

• Act as a watch group on industry developments

• Be the central provider of industry informational and statistical data

Ap pointments

• The PDG is a group with a maximum of 18 IATA member airlines. Non

- member airlines may

receive a special invitation from the IATA Director FDS Transformation

• Due to the strategic nature of discussions, delegates must be decision

- makers on distribution

matters with the competence and the authority to discuss these distribution topics at PDG.

• Industry stakeholders may be invited to attend specific meetings in t he capacity of observer

upon invitation the IATA Director FDS Transformation

Schedule

• Annual in

- person meetings at IATA’s Head (Montreal), Executive (Geneva), or Regional

offices

• Regular calls (monthly or quarterly)

• Meeting agendas shall be circulated in advance of each meeting for review and comments by

delegates, the Chairmen of the PSC Steering Group and the StB Steering Group. Minutes

shall be taken at each meeting and circulated among the delegates for review, comment, and

approval

• Active participatio n is necessary. Absence for two consecutive meetings will automatically

trigger a review of membership of the airline concerned

Technical sub

- groups

• The PDG may create technical sub

- groups to address specific issues and business

requirements, for example requirements to develop new schemas or rules and tools. Such

sub

- groups will be coordinated with the secretariat of the PSC and/or the Passenger Agency

Conference (PAConf).

Administrative

• The PDG will have a one year mandate (renewable as required) and wi ll report to the PSC

with any proposed technical improvements, recommendations and an industry standards

implementation plan.

• During the year the PDG will provide regular progress reports to the PSC Steering Group and

the StB Steering Group

• The group will coordinate its activities with other industry groups involved in airline distribution

• The Secretary is the IATA Director FDS Transformation ( leopolde@iata.org)JPSC/33 PSC/35 Oct 13

**Attachment: H** 

Page: 1 of 1

Airport Services Committee (ASC) Memb ership 201 4

Airline Traffic

Conference

Area Term of Office Expires

Air Canada 1 2015

Alitalia 2 2015

American Airlines 1 2014

British Airways 2 2015

Delta Airlines

(Vice

- Chairman) 1 2014

Egyptair 2 2016

El Al 2 2016

Iberia 2 2014

Ja pan Airlines 3 2016

KLM 2 2015

South African Airways 2 2014

Turkish Airlines 2 2015

United Airlines 1 2015

US Airways

(Chairman) 1 2016

vacant

vacant

vacant

vacantJPSC/33 PSC/35 Oct 13

**Attachment: I** 

Page: 1 of 1

Baggage Stee ring Group Membership

- 2014

Name Airline E

- Mail Status

Harvey Tate British Airways harvey.tate@ba.com Active

Darphin, Mikaël Air France midarphin@airfrance.fr Active

Hosford, David Delta Airline s <david.hosford@delta.com> Active

Rick Nagy Alaska Airlines Rick.Nagy@AlaskaAir.com Active

Phil. Ryan US Airways <Phil.Ryan@USAirways.com> Active

Bali Mabena South African Airways BaliMabena@flysaa.com Active

Micheal Harwe rth Lufthansa German Airlines micha.harwerth@dlh.de Active

Jaap Schut KLM Jaap.Schut@klm.com Active

Paul Pemberton American Airlines Active

Southwest

Airport Advisors

John Shepperd British Airports Authority john_shepperd@baa.com Active

David Bourgon McCarran Las Vegas

Airport <davidb@mccarran.com> Active

Mark van Gaalen Amsterdam Schiphol

Airport <ga alen@schiphol. nl> ActiveJPSC/33 PSC/35 Oct 13

**Attachment: J** 

Page: 1 of 1

Ticketing Committee (TKTcom) Membership

- 2014

Airline Traffic

Conference

Area Year Term of Office Expires

at Conclusion of Passenger

Services Conference:

Air Ca nada 1 2014*

Air France 2 2014*

All Nippon Airlines 3 2014*

American Airlines 1 2014*

British Airways 2 2016

Cathay Pacific 3 2015

Delta Air Lines 1 2015

Egyptair 2 2016

El Al 2 2014*

Emirates 2 2016

Finnair 2 2015

Japan Airlines 3 2015

KLM 2 2016

Lufthansa 2 2016

SAS 2 2015

South African Airways 2 2014*

United Airlines 1 2014*

US Airways 1 2016

* Expires at the conclusion of PSC 201 4JPSC/33 PSC/35 Oct 13

**Attachment: K** 

Page: 1 of 1

Glossary and Matrices Maintenance Group (GMMG)

Terms of Reference

A joint IATA/A4A maintenance group is established by the Passenger Services

Conference (PSC) called the Glossary and Matrices Maintenance Group (GMMG).

The objectives are to:

• Maintain the Electronic Ticket and Electroni c Miscellaneous Documents Data

Elements Glossary and Matrices,

• Oversee the production of the Electronic Ticket and Electronic Miscellaneous

Documents Glossary in IATA Resolution 722f and A4A 20.60,

• Oversee the production of the 6 messaging matrices publish ed in IATA

Resolutions 722f, 722g, 722h,725f,725g and 725h and the 7 messaging

matrices in A4A Resolutions 20.60, 20.61, 20.62, 20.63, 20.64, 20,65 and

20.66,

• Incorporate changes adopted at the annual Joint IATA/A4A Passenger

Services Conference into the g lossary and matrices,

• Maintain the Glossary Applicability Reference Table (GART),

• Make an annual report to TKTcom and propose changes where necessary.

Participation

The maintenance group will be attended by both the IATA and A4A Secretaries to

TKTcom. A n invitation to participate will be extended to interested airline Members

and system provider volunteers.

Modus Operandi

The GMMG will meet once annually via remote conferencing in January of each

year.JPSC/33 PSC/35 Oct 13

**Attachment: L** 

Page: 1 of 1

**IATA Reservations Committee Membership**

Airline TC area Year Term of Office Expires

Air France (AF) 2 201 6

Air Canada (AC) 1 2016

All Nippon Airways (NH) 3 2015

British Airways (BA) 2 2014 *

Delta Air Lines (DL) 1 2015

Egyptair (MS) 2 2014*

El Al (LY) 2 2015

Emirates (EK) 2 2014*

Etihad (EY) 2 2014*

Finnair (AY) 2 2015

Iberia (IB) 2 2014*

Japan Airlines (JL) 3 2015

KLM (KL) 2 2015

Lufthansa (LH) 2 2016

Scandinavian Airlines System (SK) 2 2015

South African Airways 2 2014*

United Airlines (UA) 1 2015

US Airways (US) 1 2014*

* Expires at the conclusion of PSC 201 4JPSC/ 33 PSC/35 Oct 13

**Attachment: M** 

Page: 1 of 4

RESWG Work Plan

Topic(agenda reference) Progress Next Steps Action by Target Date

1 Reservations Services Manual

(RSM)

(RESWG/19 #16) RESWG/20

• Make manual documents available to

volunteers (LH UA SITA)

• Review first several chapters together and

post comments on the forum

Chapter 1

- 7

• Discuss at RESWG/20

• Establish a sub

- group to review the structure,

consider approach, prioritize (meeting 1 st

quarter 2013)

• Meeting in August 2013

• IATA will circulate notification that the manual

is ready for publication IATA

All

IATA

– open

forum

All

IATA and

volunteers End of

August

2 New RP for Ancillary Services RESWG/20

Discussed for an RP more in detail

than RP1790 Additional Services

EMDTF provided

comments/suggestions for

RESWG/20 KL AY Sabre Amadeus reviewed the developed

outline and prepare p resentation to EMDTF

Update to be given at ResCom

Presentation given to EMDTF

Additional processes defined KL AY Sabre

Amadeus RESWG/21

3 Revision for PNR Update

Message to Advise EMD

Number

(RESWG/19 #11)

Revision of ResCom/24

agenda #9 for an exampl e RESCOM/25 #5

Agreed as proposed with the

understanding that currently

systems are not capable to issue

EMD with group names Forwarded the item to ResCom and EMDTF.

EMDTF addressed the fact that most systems are

unable to issue EMD with group names, and i f not

possible advised RESWG/20 what kind of EMD is

to be issued and how. ResCom

EMDTF JPSC

4 Alphanumeric in SSR CLID

(On

- site discussion at

ResCom/24) RESCOM/25 #6

Two items presented to RESWG/19

(#17 & #18) Forwarded agreement for agenda #17 to ResCo m IATA JPSC

5 Management of portion filed

ancillary services This item to be removed To be included in the RP AF/KL RESWG/21JPSC/33 PSC/35 Oct 13

**Attachment: M** 

Page: 2 of 4

Topic(agenda reference) Progress Next Steps Action by Target Date

6 Business Requirement for

SVC information in Remarks

Element in PNL

(RESWG/19 #5) Request DCSMWG to remove any reference to

SVC and AUX in Resolution 1708 2.12, including

examples, and 3.1.2

Ensure that after the removal of SVC and AUX,

EMD

- S data elem ent will be received by DCS by

means of /R element ASVC

Endorsed by DCSMWG DCSMWG ASC

JPSC

7 US DoT Requirement for

Notification of HazMat

Restriction

(RESWG/19 #19) Airlines and systems to send any clarification

required from DoT to A4A no later than 31

December 2012

A4A to send the questions to DoT for response no

later than end of January 2013

A4A/IATA set up working group

– require

volunteers

Updated at ResCom; awaiting DOT comments

regarding Advisory Circular

Next meeting July 1

- 2, 2013 to further

de velopment of Advisory Circular All

A4A

All On going

8 SSR ASVC Definition for

EMD

- Type

(RESWG/19 #4) RESCOM/25 #7

• Forward the amended proposal to ResCom

• Place the proposal on EMDTF

• Review editorial changes for examples and re

propose

• Endorsed by RESC OM IATA

IATA

Amadeus JPSCJPSC/33 PSC/35 Oct 13

**Attachment: M** 

Page: 3 of 4

Topic(agenda reference) Progress Next Steps Action by Target Date

9 ATPCO Clarifications on

Ancillaries for pre

- reserved

seat assignment (RESWG/19

#5) , co deshare (RESWG/19

#6) and Service Bundle

booking (RESWG/19 #10) Request ATPCO to update the status for the code

share segments at EMDTF and report back to

RESWG/20

Awaiting ATPCO clarification at RESWG/21

Amadeus and Travelport attended ATPCO

meeting and report back to ResCom/25

ATPCO provided update to RESCOM/25

Need clarification on processes for code share,

interlining, seating, bundled service

Ongoing; expect update at RESWG/21 IATA, ATPCO RESWG/21

10 Managing Duplicate Service

Bookings

(RESWG/19 #7) Clarify the process in the proposed new RP for

Ancillary services (item #3 above)

Will be incorporated into the new RP KL AY Sabre

Amadeus RESWG/21

11 Evaluate the possibility of

EMD interline lite solution Pending feedback from JPTC RESWG/21

12 Upda te on Interlineable

Premium Economy Pending feedback from the Composite Group RESWG/21

13 Passenger Contact

Information RESWG/20

RESCOM/25 #9 and #10 KL to submit on

behalf of RESWG JPSC

14 Exchange and Reissue

–

EMD

(RESWG/ 20 #9) Pending until afte r the TKTWG makes further

progress on 725g/20.64

JPTC endorsed a message to allow travel agent

to associate an EMD to a different ET

Add additional example in AIRIMP for clarification TKTWG

KL RESWG/21

15 Clarification of Known

Traveler in section 3. 13.2.2 of

AIRIMP ResCom/25 #11 Added examples of Known Traveler

Review the definitions of Known Traveler and

Redress to develop a generic text and review

construction rules in 3.13.2.2. at RESWG

Clarify these definitions in the RSM A4A

Travelport/A4A JPS C

RESWG/21JPSC/33 PSC/35 Oct 13

**Attachment: M** 

Page: 4 of 4

Topic(agenda reference) Progress Next Steps Action by Target Date

16 Positioning of Oblique in

Security Messages ResCom/25 Need to provide a clarification back to the

PNRGOV group

The missing piece is in 2.11.6.2

– proposal to be

drafted for RESWG/21

– amended agenda item

19, and address the areas in the book which

reference this type of information Sabre RESWG/21

17 Time Limit for Ancillaries

(ADMD ) ResCom/25 #14 Proposal to upd ate the construction rules Sabre RESWG/21

18 ADTK ResCom/25 #14 Proposal to update the construction rules Sabre RESWG/21

19 Requests a standard

format to manual re

associate of an EMD

number into a PNR ResCom/25 #26 Need to add an example on how to re

- associate

an existing EMD to a new service, using SSR

ASVC status code HS

Need confirmation from CX on proposed concept

to ensure this meets their requirement KL

– see item 16

above RESWG/21

20 Cancelling Special Service

Request by the Member Need to am end 3.3.10 to align with the newly

added 3.3.9 KL/HR RESWG/21JPSC/33 PSC/35 Oct 13

**Attachment: N** 

Page: 1 of 1

3.21.2 Additional Services

– Non

- Segment Associated Services

3.21.2.1 Examples

.....

Example 6

– Message from booking source to Mem ber advising the EMD has been issued for a group

deposit for which no previous request was sent

HDQRMDL

.MUCRM1A 231051

MUC1A 2GLYIP/NCL7X2063/96129250/NCL/1A/N/GB//GS

20RESWORKINGGROUP

DL1234Y18NOV LHRATL HN20

DL4321Y22NOV ATLLHR HN20

SVC DL HS1 LHR 18NO V/D/997/GROUP DEPOSIT/NM

- 20RESWORKINGGROUP

/0061234567896C1.GROUP DEPOSIT EUR500JPSC/33 PSC/35 Oct 13

**Attachment: O** 

Page: 1 of 1

AIRIMP and A 4 A Resolution



### 3.8.3 Client Identification Procedures **(Bilateral)**

Note: bilateral agreement required.

3. 8.3.1 Client Identification Number

Bilateral agreements between airlines to recognize “Client Identification” when travelling on

participating airlines, may contain the provision to exchange this information between Members or

from CRSs to Members within t he passenger's reservation message. This information will be

exchanged in a separate SSR item for each passenger or the information may be exchanged in a

single SSR item applying to all passengers in the message using the following format s:

Format:

Supple mentary Service Code .................................. SSR

“Client Identification” SSR Code .............................. CLID

Airline participating in itinerary and the programme

(YY not permitted).................................................. ..KL

Status Code followed by an oblique (/) .................... HK/

Passenger's “Client Identification”, followed by a

hyphen ...................................................................... ABC000NL

Passenger name, preceded by a numeric (optional)

. - 1 NAME/FIRSTNAME

When the Client identification number does not apply to all passengers in the message, passenger

name(s) must follow the Client identification number

Example of an SSR item advising Client ID information:

SSR CLID KL HK/ABC000NL

- 1SMIT/BRIA N

Example of an SSR item advising Client ID number applying to all passengers in the message

SSR CLID LH HK/LH123456789

3.8.3.2 Reply Message Format

Upon receipt of an Invalid Client ID Number, the receiving carrier may send an advisory to that

effect a nd that no action has been taken to update its records. Use “NO” Advice Code. Add free text

explanation following name element, preceded by a period (.)

Example:

SSR CLID KL NO/ABC000NL

- 1SMIT/BRIAN.INVLD CLIENT NUMBER

Example of CLID NO applying to all pa ssengers in the message

SSR CLID LH NO/ LH123456789.INVLD CLIENT NUMBERJPSC/33 PSC/35 Oct 13

**Attachment: P** 

Page: 1 of 3

AIRIMP and A4A SIPP Resolution 3.9.11.1

< SSR ASVC Definition >

2.11.6.7 Additional Services: Segment

- Associated

Requests and replies for additional services (segment associated) will use SSR ASVC. Additionally

SSR ASVC can be used to advise the member that an EMD has been issued for a service without

having sent a previous request.

The format for the SSR is as follows:

(a) Co nstruction

– Initial request message

Components Number and

Type of

Characters Mandatory/

Optional

/Conditional Examples

(a) Element Identifier 3 a M SSR

(b) SSR Service Code 4 a M ASVC

(c) Airline designator (3 character

codes are preceded with an

ob lique) 2 an or 3 a M BA

(d) Action Code 2 a M NN

(e) Number of services requested 1

– 3 n M 1

(f) Departure Airport 3 a M NCL

(g) Arrival Airport 3 a M LHR

(h) Flight number (with leading

zeros) 4 n M 1321

(i) Reservation Booking Designator 1a M J

( j) Date 2 n 3 a M 30JUN

(k) If applicable, Name element,

preceded by a hyphen Refer to

name element paragraph

2.11.6.1(k) C

- 1BIGGIN/ANDREW

(l) Period M

. (m) Reason for Issuance Code

(RFIC) 1 an M I

(n) Reason for Issuance sub code

(RFISC) (1) 3

– 15 an M /E23

(o) If applicable, SSR Code (1)

Mandatory for non

- standalone

Not applicable for standalone (2) 4a C /VGML

(p) Commercial Name of service if

available (1) 1

– 30 an C /VEGETARIAN

MEAL

(1) Components (n)

– (p) must be preceded by an oblique (/). W here components are not

available, an oblique is inserted to indicate that an element is missing. When no further

components are provided, do not includ e obliques beyond the final component provided.

(2) Non

- standalone SSR ASVC is used in conjunction with a st andard SSR element requesting

the service whereas standalone SSR ASVC is used as an independent SSR, when no

standard SSR code exists to request the serviceJPSC/33 PSC/35 Oct 13

**Attachment: P** 

Page: 2

(b) Construction

– Reply to an SSR ASVC

Replies a re standard SSR ASVC replies using the codes listed in 3.21.1.2

Components Number and

Type of

Characters Mandatory/

optional/

Conditiona

l Examples

(a) Element Identifier 3 a M SSR

(b) SSR Service Code 4 a M ASVC

(c) Airline designator (3 character

code s are preceded with an

oblique) 2 an or 3 a M BA

(d) Action Code 2 a M KK KD SD UN

NO UC HX

(e) Number of services requested 1

– 3 n M 1

(f) Departure Airport 3 a M NCL

(g) Arrival Airport 3 a M LHR

(h) Flight number (with leading

zeros) 4 n M 1321

(i) Reservation Booking Designator 1a M J

(j) Date 2 n 3 a M 30JUN

(k) If applicable, Name element,

preceded by a hyphen Refer to

name element paragraph

2.11.6.1(k) C

- 1BIGGIN/ANDREW

(l) Period M

. (m) Reason for Issuance Code

(RFIC) 1 an M I

(n) R eason for Issuance sub code

(RFISC) (1) 3

– 15 an M /E23

(o) SSR Code (1)

Mandatory for non

- standalone

Not applicable for standalone (2) 4a C /VGML

(p) Commercial Name of service if

available (1) 1

– 30 an C /VEGETARIAN

MEAL

(q) Type of EMD issued (1)

A

— EMD

- A (Associated)

S

— EMD

- S (Stand

- alone) 1 a O /S

( r ) EMD number including coupon

number (1)

Mandatory for SD status

Mandatory for UN, NO, UC and

HX statuses after EMD issuance

Not applicable for other statuses As defined C /1251234567890C1

(1) Compone nts (n)

– ( r ) must be preceded by an oblique (/). Where components are not

available, an oblique is inserted to indicate that an element is missing. When no further

components are provided, do not include obliques beyond the final component provided.

(2) Non

- s tandalone SSR ASVC is used in conjunction with a standard SSR element requesting

the service whereas standalone SSR ASVC is used as an independent SSR, when no

standard SSR code exists to request the serviceJPSC/33 PSC/35 Oct 13

**Attachment: P** 

Page: 3

(c) Construction

– Transmission of EMD in an SSR ASVC

Components Number and

Type of

Characters Mandatory/

optional/

Conditiona

l Examples

(a) Element Identifier 3 a M SSR

(b) SSR Service Code 4 a M ASVC

(c) Airline designator (3 character

codes are pre ceded with an

oblique) 2 an or 3 a M BA

(d) Action Code 2 a M HS XX

(e) Number of services requested 1

– 3 n M 1

(f) Departure Airport 3 a M NCL

(g) Arrival Airport 3 a M LHR

(h) Flight number (with leading

zeros) 4 n M 1321

(i) Reservation Booking D esignator 1a M J

(j) Date 2 n 3 a M 30JUN

(k) If applicable, Name element,

preceded by a hyphen Refer to

name element paragraph

2.11.6.1(k) C

- 1BIGGIN/ANDREW

(l) Period M

. (m) Reason for Issuance Code

(RFIC) 1 an M I

(n) Reason for Issuance sub cod e

(RFISC) (1) 3

– 15 an M /E23

(o) If applicable, SSR Code (1) Mandatory for non

- standalone

Not applicable for standalone (2) 4a C /VGML

(p) Commercial Name of service if

available (1) 1

– 30 an C /VEGETARIAN

MEAL

(q) Type of EMD required issued (1)

A

— E MD

- A (Associated)

S

— EMD

- S (Stand

- alone) 1 a C /S

(r)

(q) EMD number including coupon

number (1) Mandatory for HS status

Mandatory for XX status after EMD

issuance As defined C /1251234567890C1

(1) Components (n)

– ( r q ) must be preceded by an oblique (/). Where components are not available, an oblique is inserted to

indicate that an element is missing. When no further components are provided, do not include obliques beyond the final

component provided.

(2) Non

- standalone SSR ASVC is used in conjunction wi th a standard SSR element requesting the service whereas

standalone SSR ASVC is used as an independent SSR, when no standard SSR code exists to request the serviceJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 1 of 1 0

3.21.1.3 Examples (SIPP 105.17 5, Section 17.1.3)

[...]

Example 1(c)

— Message from the Member to the booking source confirming the additional

service (ASVC) with KD as an EMD

- A is required. This additional service message is sent as a

reply to an NN request or as follow

- up message to a previously sent KK reply.

HDQRM1S

.HDQRMBA 061519

HDQ1SQWERTY

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG HK2

SSR ASVC BA KD1 LHRCDG 0202Y14MAY

- 1SMITH/WALTERMR.H/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT /A

Example 1(d)

— Message from the booking sour ce to the Member advising the EMD

- A has been

issued. This message is sent in response to a KD or SD.

HDQRMBA

.HDQRM1S 061520

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG HK2

SSR ASVC BA HS1 LHRCDG 0202Y14MAY

- 1SMITH /WALTERMR.H/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT/A/1250241234567C3

Example 2

— Message from the Member advising a schedule change where additional service

has not been rebooked.

HDQRM1S

.HDQRMBA 061520

ASC

HDQ1SQWERTY

2SMITH/WALTERMR/MARYMRS

BA 02 02Y14MAY LHRCDG UN2

BA 0204Y14MAY LHRCDG TK2/1100 1100

Example 2(a)

— Message from the Member advising a schedule change where additional service

has been rebooked; no EMD is required even if one had been previously issued.

HDQRM1S

.HDQRMBA 061520

ASC

HDQ 1SQWERTY

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG UN2

BA 0204Y14MAY LHRCDG TK2/1100 1100

SSR ASVC BA KK1 LHRCDG 0204Y14MAY

- 1SMITH/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENTJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 2 of 10

Example 2(b)

— Message from the Member advising a schedule change where additional service

has been rebooked; EMD was not previously issued but EMD

- S is now required.

HDQRM1S

.HDQRMBA 061520

ASC

HDQ1SQWERTY

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG UN2

BA 0204Y14MAY LHRCDG TK2/1100 1100

SSR ASVC BA KD1 LHRCDG 0204Y14MAY

- 1SMITH/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT /S

Example 2(c)

— Message from the Member advising a schedule change where additional service

has been rebooked; EMD was p reviously issued and subsequent EMD action may be required.

Send EMD

- S and coupon number in message.

HDQRM1S

.HDQRMBA 061520

ASC

HDQ1SQWERTY

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG UN2

BA 0204Y14MAY LHRCDG TK2/1100 1100

SSR ASVC BA SD1 LHRCDG 0204Y14M AY

- 1SMITH/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT / S / 1250241234567C3

Example 2(d)

— Message from the Member advising a schedule change where segment(s) and

additional service(s) have been rebooked to a different number of segments than the original booking;

EMD was previously issued; EMD action (reissue) is required. Member may choose whether to

include 0, 1 or 2 SSRs. The previously issued EMD and coupon number are not included in the

message. HDQRM1S

.HDQRMBA 061520

ASC

HDQ1SQWERTY

2SMITH/ WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG UN2

BA 0204Y14MAY LHRMAN TK2/1100 1300

BA 0206Y14MAY MANCDG TK2/1400 1500

SSR ASVC BA KD1 LHRMAN 0204Y14MAY

- 1SMITH/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT /S

Or

HDQRM1S

.HDQRMBA 061520

ASC

HDQ1SQWERTY

2 SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG UN2

BA 0204Y14MAY LHRMAN TK2/1100 1300

BA 0206Y14MAY MANCDG TK2/1400 1500

SSR ASVC BA KD1 LHRMAN 0204Y14MAY

- 1SMITH/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT /S

SSR ASVC BA KD1 MANCDG 0206Y14MAY

- 1SMIT H/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT /SJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 3 of 10

Example 2(e)

— Message from the Member advising a schedule change where segment(s) and

additional service(s) have been rebooked to a f ewer number of segments than the original

booking; EMD was previously issued. EMD action (reissue) is now required. The previously issued

EMD and coupon number are not included in the message. The optional EMD type (A or S) is not

included.

HDQRM1S

.HDQRMB A 061520

ASC

HDQ1SQWERTY

2SMITH/WALTERMR/MARYMRS

BA 0204Y14MAY LHRMAN UN2

BA 0206Y14MAY MANCDG UN2

BA 0202Y14MAY LHRCDG TK2/1100 1300

SSR ASVC BA KD1 LHRCDG 0202Y14MAY

- 1SMITH/WALTERMR.I/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT

Example 3

— Message from the booking source to the Member requesting unaccompanied minor

handling; ASVC is also sent denoting agent is aware an EMD is required.

HDQRMBA

.HDQRM1S 061519

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA NN1 LHRCDG 0202Y14MAY.UM07

SSR ASVC BA NN1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR

Example 3(a)

— Message from the Member to the booking source confirming the unaccompanied

minor handling; ASVC is sent with KD indicating an EMD

- S is required.

HDQRM1S

.HDQRMBA 061519

HDQ1SQWERTY

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07

SSR ASVC BA KD1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR /S

Example 3(b)

— Message from the booking source to Member requesting unaccompanied minor

handling; no ASVC is sent.

HDQRMBA

.HDQRM1S 061519

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA NN1 LHRCDG 0202Y14MAY.UM07JPSC/33 PSC/35 Oct 13

**Att achment:**  **Q**

Page: 4 of 10

Example 3(c)

— Message from the Member to the booking source confirming unaccompanied

minor handling; The optional EMD type (A or S) is not included. ASVC is sent with KD indicating an

EMD is required.

HDQRM1S

.HDQRMBA 061519

HDQ 1SQWERTY

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07

SSR ASVC BA KD1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR

Example 4

— Message from booking source to Member requesting a non

- smoking aisle s eat

assignment; no ASVC is sent.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSSA KL NN1 NCLAMS1234S30JAN

Example 4(a)

— Message from the Member to the booking source confirming the seat ass ignment;

no EMD is required, therefore no ASVC is sent.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSSA KL KK1 NCLAMS1234S30JAN.24C

Example 4(b)

— Message from the Member to the booking source confirming the seat assig nment;

ASVC is sent with KD as EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSSA KL KK1 NCLAMS1234S30JAN.24C

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/NSSA/CHARGEABLE SEAT /A

Example 5

— Message from the b ooking source to Member requesting chargeable aisle (CA) seat

assignment; no ASVC is sent.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSST KL NN1 NCLAMS1234S30JAN.CAJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 5 of 10

Example 5(a)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent with KK indicating no EMD is required, as Member will not charge for the seat.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAW B

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSST KL KK1 NCLAMS1234S30JAN.24C

SSR ASVC KL KK1 NCLAMS1234S30JAN.H/S23/NSST/CHARGEABLE SEAT

Example 5(b)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent with KD indic ating an EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSST KL KK1 NCLAMS1234S30JAN.24C

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/NSST/CHARGEABLE SEAT /A

Example 6

— Message from the booking source to the M ember requesting a seat assignment;

ASVC is also sent denoting agent is aware an EMD

- A is required.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSSA KL NN1 NCLAMS1234S30JAN.C

SSR ASVC KL NN1 NCLAMS1234S30JAN.H/S23/NSSA/CHARGEABLE SEAT

Example 6(a)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent with KD indicating an EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCL AMS HK1

SSR NSSA KL KK1 NCLAMS1234S30JAN.24C

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/NSSA/CHARGEABLE SEAT /A

Example 6(b)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent with KK indicating an EMD is not required, as Member will not charge for the seat.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR NSSA KL KK1 NCLAMS1234S30JAN.24C

SSR ASVC KL KK1 NCLAMS1234S30JAN.H/S23/NSSA/CHARGEABLE SEATJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 6 of 10

Example 7

— Message from the booking source to the Member requesting chargeable seat

assignments; ASVC is not sent.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

2WALKER/JOHNMR/SARAH MRS

KL1234S30JAN NCLAMS HK2

SSR NSS T KL NN2 NCLAMS1234S30JAN

Example 7(a)

— Message from the Member to the booking source confirming seat assignments;

two ASVCs are sent with KD indicating EMD

- S is required for each passenger.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

2WALKER/JOHNMR/SARAHMRS

KL 1234S30JAN NCLAMS HK2

SSR NSST KL KK2 NCLAMS1234S30JAN.24B24C

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WALKER/JOHNMR.H/S23/NSST/

SSR ASVC KL /// CHARGEABLE SEAT /S

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WALKER/SARAHMRS.H/S23/NSST/

SSR ASVC KL ///CHARGEABLE SEAT /S

Exam ple 8

— Message from the booking source to the Member requesting chargeable seat

assignments; two ASVCs are sent.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR NSST KL NN2 NCLAMS1234S3 0JAN

SSR ASVC KL NN1 NCLAMS1234S30JAN

- 1WALKER/JOHNMR.H/S23/NSST/

SSR ASVC KL /// CHARGEABLE SEAT

SSR ASVC KL NN1 NCLAMS1234S30JAN

- 1WALKER/SARAHMRS.H/S23/NSST/

SSR ASVC KL /// CHARGEABLE SEAT

Example 8(a)

— Message from the Member to the booking source con firming seat assignments;

two ASVCs are sent with KD indicating EMD

- S is required for each passenger.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR NSST KL KK2 NCLAMS1234S30JAN.24B24C

SSR ASVC KL KD1 NCLAMS1234S3 0JAN

- 1WALKER/JOHNMR.H/S23/NSST/

SSR ASVC KL /// CHARGEABLE SEAT /S

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WALKER/SARAHMRS.H/S23/NSST/

SSR ASVC KL /// CHARGEABLE SEAT /SJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 7 of 10

Example 9(a)

— Message fr om the Booking Source to the Member requesting two bikes for a single

passenger without a SSR ASVC.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR BIKE KL NN2 NCLAMS1234S30JAN

- 1WALKER/JOHNMR

Example 9(b)

— Message from the Member to the Booking Source confirming two bikes for a single

passenger; ASVC is sent with KD as EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

HDQ1P 7YHAWB

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR BIKE KL KK2 NCLAMS1234S30JAN

- 1WALKER/JOH NMR

SSR ASVC KL KD2 NCLAMS1234S30JAN

- 1WALKER/JOHNMR.H/S57/BIKE/

SSR ASVC KL /// BIKES /A

Example 9(c)

— Message from the Booking Source to the Member cancelling two bikes for a single

passenger also including the SSR ASVC.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YH AWB

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR BIKE KL XX2 NCLAMS1234S30JAN

- 1WALKER/JOHNMR

SSR ASVC KL XX2 NCLAMS1234S30JAN

- 1WALKER/JOHNMR.H/S57/BIKE/

SSR ASVC KL /// BIKES

3.21.1.4 Examples of Request and Reply Messages for Pre

- reserved seats in SSR

SEAT elements in conjunction with SSR ASVC elements

When seat reservations involve chargeable seats, the SSR ASVC may be used. See rules for

construction of the SSR ASVC in 2.11.6.6.

Example 1

— Message from booking source to Member requesting a non

- smoking aisle seat

assignment; no ASVC is sent.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL NN1 NCLAMS1234S30JAN.NAJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 8 of 10

Example 1(a)

— Message from the Member to the booking source confirming the seat assignment;

no AVSC is included because no EMD is required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN. 24CN/RS

Example 1(b)

— Message from the Member to the booking source confirming the seat assignment;

ASVC is sent with KD as EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JA N.24CN/RS

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT /A

Example 2

— Message from the booking source to Member requesting chargeable seat assignment;

no ASVC is sent.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WA LKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL NN1 NCLAMS1234S30JAN.NC

Example 2(a)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent with KK indicating no EMD

- A is required, as Member will not charge for the seat.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS

SSR ASVC KL KK1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT

Example 2(b)

— Message from the Member to the booking source confirming se at assignment;

ASVC is sent with KD indicating an EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT /AJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 9 of 10

Example 3

— Message from the booking source to the Member requesting a seat assignment;

ASVC is sent denoting agent is aware an EMD

- A is required.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315 /NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL NN1 NCLAMS1234S30JAN.NA

SSR ASVC KL NN1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT

Example 3(a)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent w ith KD indicating an EMD

- A is required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT /A

Example 4

— Message from the b ooking source to the Member requesting a seat assignment;

ASVC is also sent denoting agent is aware an EMD is required.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL NN1 NCLAMS1234S 30JAN.NA

SSR ASVC KL NN1 NCLAMS1234S30JAN.I/S23/SEAT/CHARGEABLE SEAT

Example 4(a)

— Message from the Member to the booking source confirming seat assignment;

ASVC is sent with KK indicating an EMD is not required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS

SSR ASVC KL KK1 NCLAMS1234S30JAN.I/S23/SEAT/CHARGEABLE SEATJPSC/33 PSC/35 Oct 13

**Attachment: Q** 

Page: 10 of 10

Example 5

— Message from the booking source to the M ember requesting chargeable seat

assignments; ASVC is not included in the message.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

2WALKER/JOHNMR/SARAH MRS

KL1234S30JAN NCLAMS HK2

SSR SEAT KL NN2 NCLAMS1234S30JAN.NEAC

Example 5(a)

— Message from the Member to the booking source confirming seat assignments;

two ASVCs are sent with KD indicating that an EMD

- A is required for each passenger.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

2WALKER/JOHNMR/SARAH MRS

KL1234S30JAN NCLAMS HK2

SSR SEA T KL KK2 NCLAMS1234S30JAN.24BN24CN/RS

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WALKER/JOHNMR.I/S23/SEAT/

SSR ASVC KL /// CHARGEABLE SEAT /A

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WALKER/SARAHMRS.I/S23/SEAT/

SSR ASVC KL /// CHARGEABLE SEAT /A

Example 6

— Message from t he booking source to the Member requesting chargeable seat

assignments; two ASVCs are sent.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR SEAT KL NN2 NCLAMS1234S30JAN.NC

SSR ASVC K L NN1 NCLAMS1234S30JAN

- 1WALKER/JOHNMR.I/S23/SEAT/

SSR ASVC KL ///CHARGEABLE SEAT

SSR ASVC KL NN1 NCLAMS1234S30JAN

- 1WALKER/SARAHMRS.I/S23/SEAT/

SSR ASVC KL ///CHARGEABLE SEAT

Example 6(a)

— Message from the Member to the booking source confirming seat assi gnments;

two ASVCs are sent with KD indicating EMD

- A is required for each passenger.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

2WALKER/JOHNMR/SARAHMRS

KL1234S30JAN NCLAMS HK2

SSR SEAT KL KK2 NCLAMS1234S30JAN.24BN24CN/RS

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WAL KER/JOHNMR.H/S23/SEAT/

SSR ASVC KL ///CHARGEABLE SEAT /A

SSR ASVC KL KD1 NCLAMS1234S30JAN

- 1WALKER/SARAHMRS.H/S23/SEAT/

SSR ASVC KL ///CHARGEABLE SEAT /AJPSC/33 PSC/35 Oct 13

**Atta chment:**  **R**

Page: 1 of 2

EFFECTIVE 1 JANUARY 2014

3.20 PASSENGER PROVI DED CONTACT INFORMATION

3.20.1 Passenger IROP Contact Information

Members must be able to contact the passenger in an IROP situation. Therefore the

booking source shall advise both the mobile phone number , including the country code,

and the e

- mail addres s of the passenger to the member.

Optionally, preferred language may be included in the message using the language

codes in ISO

- 639

- 1. Languages supported by carriers may vary.

Note: Use // (double slash) in place of @ (at sign) and “..” (double dot) i n place of

“_” (underscored) in E

- mail address.

3.20.1.1 Examples

Example 1

– Messages from the booking source to the members advising passenger

contact information; a mobile number and e

- mail address. The mobile phone number of

Mrs. Carri Cullinane is c ountry code 1 and phone number 2021234567 (including area

code if applicable), the email address is: C.Cullinane@Freeweb.com. The mobile phone

number of Mrs. Michelle Diva is country code 49 and phone number 6987654321

(including area code if applicable), the e

- mail address is: Michelle_Diva@Nobility.org

, the

language preference is German

.

MUCRM1A

.HDQRM1P

Record Locator

................... HDQ1P QWERTY/ABC/23212345/FRA/1P/DE/T

Name Element

................... 1 CULLINANE/CARRIMRS 1DIVA/MICHELLEMR S

Segment Element

............... LH 470Y10JUN FRAYYZ HK2 1A

Segment Element

............... UA4811Y10JUN YYZCLE HK2/1820 1937

Segment Element

............... UA4812Y20JUN CLEYYZ HK2/1614 1734

Segment Element

............... LH 471Y20JUN YYZFRA HK2 1A

Supplementary Element

...... SSR CTCM LH HK1/12021234567

- 1CULLINANE/CARRIMR S

Supplementary Element

...... SSR CTCM LH HK1/496987654321 /DE

- 1DIVA/MICHELLEMRS

Supplementary Element

...... SSR CTCE LH HK1/C.CULLINANE//FREEWEB.COM

1CULLINANE/CARRIMRS

Supplementary Element

...... SSR CTCE LH HK1/MICHELLE..DIVA//NOBILTY.ORG /DE

1DIVA/MICHELLEMRS

MUCRMUA

.HD QRM1P

Record Locator

................... HDQ1P QWERTY/ABC/23212345/FRA/1P/DE/T

Name Element

................... 1 CULLINANE/CARRIMRS 1DIVA/MICHELLEMRS

Segment Element

............... LH 470Y10JUN FRAYYZ HK2/1415 1655

Segment Element

............... UA4811Y10JUN YYZCLE HK2

Segment Element

............... UA4812Y20JUN CLEYYZ HK2

Segment Element

............... LH 471Y20JUN YYZFRA HK2/1850 0835/1

Supplementary Element

...... SSR CTCM UA HK1/12021234567

- 1CULLINANE/CARRIMRS

Supplementary Element

...... SSR CTCM UA HK1/496987654321 /DE

- 1DIVA/MICHELLEMRS

Supplementary Element

...... SSR CTCE UA HK1/C.CULLINANE//FREEWEB.COM

1CULLINANE/CARR IMRS

Supplementary Element

...... SSR CTCE UA HK1/MICHELLE..DIVA//NOBILTY.ORG /DE

1DIVA/MICHELLEMRSJPSC/33 PSC/35 Oct 13

**Attachment: R** 

Page: 2

EFFECTIVE 1 JANUARY 2014

3.20.2 Passenger Emergency Contact Information

Secretary note : Followed by the curre nt 3.20. Renumber paragraphs 3.20.1 to 3.20.10

2.11.7.4 Contact Information in OSI

.....

(c) Contact CTC

– follow the abbreviation CTC by the nature of contact, e.g.:

A

– Address (home or hotel)

B

– Business telephone

E

– Email

Note: Use // (double slash) in place of @ (at sign) and “..” (double

dot) in place of “_” (underscored) in E

- mail address.

F

– F ax

H

– Home telephone

M

– Mobile phone

T

– Travel agent telephone

P

– Passenger t elephone , type may be specified

......

2.11.6. 9 SSR Matrix

SSR

CO DE ACTION

CODE REPLY AUTOMATED

FORMAT FREE TEXT

IN REQUEST FREE TEXT IN

REPLY/CANCEL REFERENCE

.....

CTCE Mandatory Not permitted Not permitted Not permitted Not permitted See 3.20.1

CTCM Mandatory Not permitted Not permitted Not permitted Not perm itted See 3.20.1

.....

7.1.8.2 Special Service Requirement (SSR) Codes

..... Passenger provided emergency contact information..................................................PCTC

Passenger IROP contact information e

- mail address...............................................CTCE

Passenger IROP contact informati on mobile phone number..................................CTCM

.....

7.2 PASSENGER RESRVATIONS CODES AND ABREVIATIONS (Decoding)

......

CTCE

...................... Passenger IROP contact information e

- mail address

CTCM

...................... Passenger IROP contact information mobile phone number

......

PCTC

...................... Passenger provided emerg ency contact for passenger information

......JPSC/33 PSC/35 Oct 13

**Attachment: S** 

Page: 1 of 1

SIPP 105.175, SECTION 12.2.4/AIRIMP SECTION 3.13.2.4

...

(g ) Cancellation

- Non

- Automated Format (1)

A passenger supplies a United States Redress Numb er for this PNR.

SSR DOCO AA XX1//R/1234567890123///US

- 1CADE/BOBBI

Cancellation

- Automated Format (2)

A passenger supplies a United States Redress Number for this PNR.

SSR DOCO AA XX1JFKLAX0001Y28JUN//R/1234567890123///US

SSR DOCO AA ///

- 1CADE /BOBBI

(h) Non

- Automated Format (1)

A passenger supplies a United States Known Traveler Number for this PNR.

SSR DOCO AS HK1//K/123456789///US

- 1NAGY/RICK

Automated Format (2)

A passenger supplies a United States Known Traveler Number for this PNR.

SSR DOCO AS HK1DCASEA0001Y30APR//K/123456789///US

SSR DOCO AS ///

- 1NAGY/RICK

(i) Cancellation

- Non

- Automated Format (1)

SSR DOCO AS XX1//K/123456789///US

- 1NAGY/RICK

Cancellation

- Automated Format (2)

SSR DOCO AS XX1DCASEA0001Y30APR//K/12 3456789///US

SSR DOCO AS ///

- 1NAGY/RICK

...JPSC/33 PSC/35 Oct 13

**Attachment: T** 

Page: 1 of 1

8.13. Code Share Segments

...

OPERATING CARRIER: is the airline actually providing the aircraft and crew and

operating the flight. (From SSIM t ake value in the DEI 50 which must be qualified

with DEI2 )

.

...JPSC/33 PSC/35 Oct 13

**Attachment: U** 

Page: 1 of 1JPSC/33 PSC/35 Oct 13

**Attachment: V** 

Page: 1 of 1

Aeronautical Charges Exchange Working Gr oup (ACXWG)

Terms of Reference

The ACXWG will:

• Define an industry standard to facilitate the automated transmission and

reporting of data for billing of aeronautical charges;

• Define the requirements for a standard message to transmit and report billing

data elements for calculation of billing data of aeronautical charges (PSCs,

PFCs, terminal charges, etc.);

• Define a Business Requirements Document (BRD) with both functional and

nonfunctional requirements to facilitate development of a corresponding XML

a nd/or EDIFACT message by PADIS;

• Once the XML and/or EDIFACT message has been published by PADIS,

ACXWG is responsible for initiating any change requests and maintaining the

corresponding message implementation guide.

• ACXWG to monitor the work progress of t he deployment of the industry

standard, the execution of the pilot testing and the go live.

The ACXWG is open to all IATA and A4A members as well as IATA Strategic

Suppliers and airport authorities.

The ACXWG will have a one year mandate.

The Secretary of the ACXWG is Giorgio Camilleri ( camillerig@iata.org )JPSC/33 PSC/35 Oct 13

**Attachment: W** 

Page: 1 of 1

Data Model Project

Operational Stakeholder Views

The objective was to identify top views reflecting core airline activities in alignment

wi th major stakeholder groups. For this purpose, the group also reviewed the list of

IATA committees and IATA conferences with their permanent committees.

The following criteria were set for defining/selecting top level operational views:

• It should

o Rel ate to a core airline activity at a very high level

o Be stable over time; once defined the view should not change

o Be mapped to a clearly identified group(s) of stakeholders

• Views are not exclusive, the same information stored in the model can be

acces sed through multiple views;

• Views do not need to map to business domains or business frameworks;

• It is not necessary to have a complete list of operational views; additional

views can be added later.JPSC/33 PSC/35 Oct 13

**Attachment: X** 

Page: 1 of 1

1.1 Private IP connectivity

(MPLS, VPLS, IPSec VPN etc ) 1.2 Native internet

connectivity Legacy

connectivity

(SNA, X.25 etc ) Legacy protocols

2.1 Internet Layer (IPv4, IPv6) 3.1Transport Layer

(UDP, TCP, ICMP etc.) Message content (XML, JSON, plain text etc.)

4.7

DNSB.1 Transport SecurityB.2 Message SecurityC.3Discovery / Directory ServicesC.2NameResolutionC.1Address TranslationA.1 Messaging standards(Addressing, Reliabilityetc.)

deprecated

CSCC Out of

Scope CSCC Out of

Scope Optional 

# IATA CSCC Reference Communications Model v1.0

Key: SOAP

WS

- RM XML API

WS

- Reliability

WS

- MakeConnection WS

- Addressing

HTTP SOAP

WS

- RM

WS

- Reliability

WS

- MakeConnection WS

- Addressing

HTTPS HTTP XML API

HTTPS Message

Envelope Message

Envelope

HTTPS Type X

Message

Envelope

Type X

Reliability

SOAP

Reliability Reliability

Issue, if

required CSCC

In ScopeJPSC/33 PSC/35 Oct 13

**Attachment: Y** 

Page: 1 of 1

SISC TERMS OF REFERENCE

The Schedules Information Standards Committee (SISC) is established by the IATA

Passenger Services Conference (PSC) with the following terms of referen ce:

• Develop and maintain a set of common standards for the exchange of schedule

data, including industry standard code sets for a variety of schedule related data

elements;

• Disseminate and encourage the use of common schedule data handling

procedures and standard formats for the exchange of schedule information as

published in the Standard Schedules Information Manual (SSIM);

• Develop business requirements and change requests for XML schemas

published by PADIS, and maintain corresponding Implementation Guid es;

• Liaise with other IATA committees and working groups, in particular the

Schedule Policy Working Group (SPWG) as well as other organizations as

appropriate to meet changing industry requirements and to further the objectives

of the SISC;

• The Joint Sched ules Advisory Group (JSAG) will ensure formal liaison between

the airport coordinator community and SISC;

• SISC will provide an annual report to the PSC comprising all proposed and

adopted changes to SSIM. In addition a written report of the work of SISC will

be made to the Heads of Delegation Meeting of the regularly scheduled IATA

Schedules Conferences;

• The PSC will be responsible for final endorsement of proposed changes to

SSIM;

• Participation is by schedules specialists from IATA airlines and industry experts

in the IATA Strategic Partnership programme;

• A rapporteur will be established to provide liaison for non

- IATA airlines

participating in the Schedules Conference;

• Airport Coordinators participating in the IATA Schedule Conference are invited

to participate in SISC.

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

PSC/RESO/ 163

To: All Members, Passenger Services Conference

- Accredited

Representatives

Copy: IATA Strategic Partners

From: Head, Airline Distribution Standards

Date: 2 3 December 2013

Subject: BOOK OF FINALLY ADOPTED RES OLUTIONS & RPs

3 5 th IATA Passenger Services Conference (PSC)

Dublin, 31 October

– 1 November 2013

Attached are the resolutions & recommended practices (RPs) which were adopted at the above

mentioned Conference.

The filing period is established as 2 3 D ecember 2013

– 1 7 February 2014

. To ensure timely

approval, Members are requested to file these agreements, where required, with their

Governments upon receipt of this document and to advise this office (email: m cewend @iata.org ) of

their Government’s acti on by the end of the filing period ( 14 February 2014 )

.

Filing formalities with the Canadian Transportation Agency on behalf of Canadian Members will be

accomplished by this office.

Filing formalities with the United States Department of Transportation (D oT) on behalf of IATA

Members will be accomplished by IATA’s Regional Vice President, North America.

The intended effective date is 1 J une 20 1 4

.

David McEwen International Air Transport Association

Route de l'Aeroport 33

PO Box 416

CH

- 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2 086

Fax: +41 22 7 70 2896

### OUTLINE OF CONTENTS

RESOLUTIONS & RECOMMENDED PRACTICES

ADOPTED AT:

3 5 th PAS SENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 June 2014

Resolution/RP Title

PSC(35) 003 STANDARD RECISSION RESOLUTION

PSC(35) 722

**[OST**

**- 2012** 

**- 0058]**  TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC(35) 722f

**[OST**

**- 2012** 

**- 0058]**  ELE CTRONIC TICKET

– AIRLINE

(amending)

PSC(35) 722g

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC TICKET

– NEUTRAL

(amending)

PSC(35) 722h

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC TICKET

– GROUND HANDLING

( amending)

PSC(35) 725f

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC MISCELLANEOUS DOCUMENT

–

AI RLINE

(amending)

PSC(35) 725g

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC MISCELLANEOUS DOCUMENT

–

NEUTRAL

(amending)

PSC(35) 725h

**[OST**

**- 2012** 

**- 0058]**  ELECTRONIC MISCELLANEOUS DOCUMENT

– GROUND HANDLING

(amending)

PSC(35) 728

**[OST**

**- 2012** 

**- 0058]**  CODE DESIGNATORS FOR PASSE NGER TICKET

AND BAGGAGE CHECK

(amending)

PSC(35) 735d

**[OST**

**- 2012** 

**- 0058]**  PROCEDURE FOR INVOLUNTARY CHANGE OF

ROUTING EN ROUTE

(amending)PSC(35) 735 e PROCEDURE FOR INVOLUNTARY CHANGE OF

ROUTING EN ROUTE

(amending)

PSC(35) 73 6 VOLUNTARY CHANGE S TO TIC KETS AND

MISCELLANEOUS DOCUMENTS

(amending )

PSC(35) 7 40

**[OST**

**- 01** 

**- 9575]**  FORM OF INTERLINE BAGGAGE TAG

(amending)

PSC(35) 74 5

**[OST**

**- 2012** 

**- 0058]**  DANGEROUS GOODS IN PASSENGERS BAGGAGE

(amending)

PSC(35) 75 2 ELECTRONIC BAGGAGE CLAIM RECEIPT

**(new)**

PSC(35 ) 75 3 BAGGAGE TRACKING

**(new)**

PSC(35) 780

**[OST**

**- 2012** 

**- 0058]**  FORM OF INTERLINE TRAFFIC AGREEMENT

- PASSENGER

(amending)

PSC(35) 780e

**[OST**

**- 2012** 

**- 0058]**  IATA INTERLINE TRAFFIC PARTICIPATION

AGREEMENT

– PASSENGER

(amending)

PSC(35) 1 008

**[OST**

**- 0** 

**2**

**- 13807**  **]** GLO SSARY OF COMMONLY USED AIR PASSENGER

TERMS

(amending)

PSC(35) 1706 c

**[OST**

**- 2012** 

**- 0058]**  COMMON USE SELF

- SERVICE

(amending)

PSC(35) 1707a

**[OST**

**- 01** 

**- 9575]**  DATA FIELD DIRECTORY FOR DCS PASSENGER

MESSAGES

(amending)

PSC(35) 1707b

**[OST**

**- 01** 

**- 9575]**  DATA ELEMENT DIRECTORY FOR DCS PASSENGER

MESSAGES

(amending)

PSC(35) 1708

**[OST**

**- 02** 

**- 13807]**  PASSENGER NAME LIST (PNL) AND ADDITIONS AND

DELETIONS LIST (ADL)

(amending)

PSC(35) 17 15

**[OST**

**- 0** 

**2**

**- 11798**  **]** PASSEN GER SERVICE MESSAGE (PSM)

(amending)PSC(35) 17 16

**[OST**

**- 0** 

**2**

**- 1380**  **7 ]**  PASSEN GER INFORMATION LIST (P IL )

(amending)

PSC(35) 17 17a PA XLST MESSAGE

(amending)

PSC(35) 1719

**[OST**

**- 01** 

**- 9575]**  PASSENGER FINAL SALES MESSAGE (PFS)

(amending)

PSC(35) 1719 a

**[OST**

**- 01** 

**- 9575]**  FREQUENT TRAVELLER LIST ( FT L)

(amending)

PSC(35) 1719b

**[OST**

**- 02** 

**- 13807]**  PASSENGER RECONCILE LIST (PRL)

(amending)

PSC(35) 17 20a

**[OST**

**- 2012** 

**- 0058]**  STANDARD THIRTEEN

- DIGIT NUMBERING SYSTEM

FOR TRAFFIC DOCUMENT

(amending)

PSC(35) 17 41 PASSENGER AND BAGGGAGE CONFORMANCE

SERVICES

**(new)**

PSC(35) 17 52 RELIABILITY AND INTEGRITY OF BAGGAGE

MESSAGING

**(new)**

PSC(35) 17 80e IATA INTERMODAL INTERLINE TRAFFIC

AGREEMENT

- PASSENGER

( amending )

PSC(35) 1790

**[OST**

**- 2012** 

**- 0058]**  ADDITIONAL SERVICES

(amending)

PSC(35) 179 0a ONLINE SALES OF ADDITIONAL SERVICES IN

INTERLINE E

- TICKET SCENARIOS

**(new)**

PSC(35) 1797

**[OST**

**- 2012** 

**- 0058]**  COMMON USE PASSENGER PROCESSING

SYSTEMS (CUPPS)

(amending)

### SUMMARY OF CHANGES

RESOLUTIONS/RECOMMENDED PRACTICES ADOPTED AT:

3 5 th PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 June 2014

Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 003

STANDARD

RECISSION

RESOLUTION Resolution rescinds a

previously adopted Resolution. RP 1724 rescinded regarding General

Conditions of Carriage (Pas senger

and Baggage)

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 t ickets. Amendments to how to reflect

stopover surcharges in the fare

calculation. Additional example on

how to reflect multiple surcharges in

the fare calculation is added.

RESOLUTION 722f

ELECTRONIC

TICKET

– AIRLINE Provides governing rules and

technic al specifications on how

to produce an Electronic Ticket

(ET) issued by airlines. 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. Defini tion of Exchange/Reissue

Transactions is added.

A new Glossary Applicability

Reference Table is added to the Data

Elements Glossary.

Generic Reason for Issuance Sub

Codes for industry usage have been

added.

Various editorial and technical

amendments are added to the

glossary and related matrices.

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 wit hout the

issuance of paper tickets. Also

included are the applicable

conditions for the issuance

and honoring of such tickets. Various editorial and technical

amendments are added to the

glossary and related matrices.Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 722h

ELECTRONIC

TICKET

– G ROUND

HANDLING Provides governing rules and

technical specifications to be

followed for the third party

ground

- handling of electronic

tickets (ETs). This allows

airlines to have their electronic

tickets handled by third party

ground handlers. Various edit orial and technical

amendments are added to the

glossary and related matrices.

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 electronic

method to document the sale

and usage of charges

associated to various usage,

e.g. excess baggage charges. Various editorial and technical

amendments are added to the

glossary and related matrices.

RESOLUTION 725g

ELECTRONIC

MISCELLANEO US

DOCUMENT

–

NEUTRAL Provides governing rules for

the issuance and use of

Electronic Miscellaneous

Documents (EMD) by agents. Various editorial and technical

amendments are added to the

glossary and related matrices.

RESOLUTION 725h

ELECTRONIC

MISCELLA NEOUS

DOCUMENT

– GROUND HANDLING Provides governing rules and

technical specifications to be

followed for the third party

ground

- handling of electronic

miscellaneous documents

(EMDs). This allows airlines to

have their EMDs handled by

third party ground h andlers. Various editorial and technical

amendments are added to the

glossary and related matrices.

RESOLUTION 728

CODE

DESIGNATORS FOR

PASSENGER TICKET

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. A fourth cabin ‘Premium Economy’ is

added.

A new form of payment to recognize

electronic funds transfer is added for

mobile transactions.

A new card brand ‘EL’ is added for

domestic usage in Brazil.

R ESOLUTION 735d

INVOLUNTARY

CHANGE OF

CARRIER, ROUTING,

CLASS OR TYPE OF

FARE Provides governing rules for

the involuntary rerouting of

passengers due to flight

disruptions. The definition for normal fares is

amended to reflect the addition of a

new cabin class.

RESOLUTION 7 35e

PROCEDURE FOR

INVOLUNTARY

CHANGE OF

ROUTING EN ROUTE Provides procedures for the

involuntary rerouting of

passengers due to flight

disruptions en route

(diversion)

. A provision to carrier forward original

flight coupon data on the reissued

ticket is added.Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RESOLUTION 7 36

VOLUNTARY

CHANGES TO

TICKETS Provides governing rules for

the voluntary changes to ticket

of passengers due to flight

disruptions. New optional change procedures for

the exchange/reissue of Electronic

Miscellaneou s Documents are added.

RESOLUTION 7 40

FORM OF INTERLINE

BAGGAGE TAG Provides information,

standards and specifications

for industry baggage

tags/labels. Edited for correct representation of

the 10 digit license plate

Inclusion of home printed baggage tag

and permanent tag examples.

RESOLUTION 745

DANGEROUS

GOODS IN

PASSENGER

BAGGAGE Provides rules describing what

articles cannot be carried in

passenger’s checked bags or

in the carry

- on bags. Reference to the effectiveness date of

1 January 2013 is dele ted and the

provision has been made mandatory

by amending ‘should’ to ‘must’

thoughout.

RESOLUTION 7 52

ELECTRONIC

BAGGAGE CLAIM

RECEIPT Provides procedures regarding

the data to be provided for an

electronic baggage receipt Introduced to allow baggage ta g

formats without claim portions.

RESOLUTION 7 53

BAGGAGE

TRACKING Provides procedures on how

to maintain an accurate

inventory of baggage being

tracked through the systems Introduced to provide procedures on

maintaining accurate inventory of

baggage trac ked in systems.

RESOLUTION 780

FORM OF INTERLINE

TRAFFIC

AGREEMENT

–

PASSENGER Provides the standard text for

multi

- lateral interline traffic

agreements. Procedures are added to advise

acceptance of carriers’ interline

Electronic Miscellaneous Documents

and to opt out of accepting interline

paper excess baggage tickets and

MCOs.

Clarifications are added to make it

clear who is responsible for sharing

baggage claims.

RESOLUTION 780e

IATA INTERLINE

TRAFFIC

PARTICIPATION

AGREEMENT

–

PASSENGER Provides the standard text for

multi

- lateral interline traffic

agreements where only one

airline is able to issue tickets. Procedures are added to advise

acceptance of carriers’ interline

Electronic Miscellaneous Documents

and to opt out of accepting interline

paper ex cess baggage tickets and

MCOs.

RP 1008

GLOSSARY OF

COMMONLY USED

AIR PASSENGER

TERMS Provides a listing of common

terms and their definitions A new definition for ‘Premium

Economy’ fares is added as well as

consequential changes to Normal

Fares and Busi ness Fares.

RP 1706c

COMMON USE SELF

SERVICE Provides a recommended

practice outlining specification

and standard for members

who plan to operate shared

self

- service devices in a

common environment. Editorial amendments to replace the

word ‘provider’ wit h ‘operator’.Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RP 1707a

DATA FIELD

DIRECTORY FOR

DCS PASSENGER

MESSAGES Provides definitions and

formats for the automatic

creation, transmission, receipt

and interpretation of this group

of messages. Removed element AUX as this is no

longer needed

RP 17 07b

DATA ELEMENT

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 p assengers. • Removed element AUX as this is

no longer needed

• Added ASL’s mandatory,

conditional and optional elements

for the standard elements used

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. Removed element AUX as this is no

long er needed

RP 1715

PASSENGER

SERVICE MESSAGE

(PSM) Provides guidance on how to

inform downline stations of

disembarking and transiting

passengers who require

assistance or special handling Removed element AUX as this is no

longer needed

RP 1716

PASSENGE R

INFORMATION LIST Provides guidance to

member’s cabin crews on

necessary information

concerning passengers on

board and, optionally, about

seats blocked for other

purposes and downline seat

protection Removed element AUX as this is no

longer needed

RP 1717a

PAXLST MESSAGE Provides guidelines for the

transmission of Advance

Passenger Information (API) Editorial update

RP 1719

PASSENGER FINAL

SALES MESSAGE

(PFS) The PFS message gives

information to reservations

systems about the final counts

loaded on a n aircraft at the

departure station. List

contains a numeric summary

of passenger counts and may

contain passenger names • Removed element AUX as this is

no longer needed

• Added new category CHGTO to

identify passengers being

transferred from another flight

.Resolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RP 1719a

FREQUENT

TRAVELLER LIST

(FTL) The PFS message gives

information to reservations

systems about the final counts

loaded on an aircraft at the

departure station. List

contains a numeric summary

of passenger counts and may

contain passenger names

. Removed element AUX as this is no

longer needed

RP 1719b

PASSENGER

RECONCILE LIST

(PRL) The PRL is a list containing all

passenger check

- in details for

actual boarded passengers of

a flight departure. Removed element AUX as this is no

longer needed

R P 1720a

STANDARD

THIRTEEN

- DIGIT

NUMBERING

SYSTEM FOR

TRAFFIC

DOCUMENTS Provides guidelines regarding

the numbering systems for

airline and travel agent traffic

documents Form Codes are re

- assigned to

OPEMDs subsequent to the sunset of

the VMCO and VMPD. Redundant

footnotes are removed. Editorial

updates are also added.

RP 1741

PASSENGER AND

BAGGAGE

CONFORMANCE

STANDARDS Provides web services

specifications to support

business requirements for a

common use self

- service bag

drop process Establishment of n ew specifications

RP 1752

RELIABILITY AND

INTEGRITY OF

BAGGAGE

MESSAGING Provides guidelines and best

practices to increase the

reliability and integrity of

baggage messaging Establishment of new guidelines and

best practices for the use of a

baggage bro ker.

RP 1780e

IATA INTERMODAL

INTERLINE TRAFFIC

AGREEMENT

-

PASSENGER Provides guidelines to facilitate

the exchange of passengers

between different modes of

transport Editorial update

RP 1790

ADDITIONAL

SERVICES Guidelines to facilitate the

reservation s, sales and

delivery of airline additional

services Added to the list of standard

messages to be applied RP1719e

(ASL)

RP 1790a

ONLINE SALES OF

ADDITIONAL

SERVICES IN

INTERLINE E

- TICKET

SCENARIOS Guidelines for the

reservations, sales and

delivery of ad ditional services

using an EMD Establishment of new guidelinesResolution/

Recommended

Practice Summary of

Resolution/RP Summary of Amendment

RP 1797

COMMON USE

PASSENGER

PROCESSING

SYSTEMS (CUPPS) Provides guidelines for

CUPPS systems that enable

airlines to share check

- in

desks or gate podiums for

boarding processes Provisions fo r PCI

- DSS compliance is

added. The word ‘provider’ is replaced

with ‘operator’.RESOLUTION 003

STANDARD RECISSION RESOLUTION

PSC(35)003 Expiry: 2 June 2014

Type: B

P6

Resolved that, effective 1 June 2014, the following RP is rescinded:

RP 1724

– General Conditions of Carriage (Passenger and Baggage)

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 201 4RESOLUTION 722

TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC( 34 35 )722 Expiry: Indefinite

Type: A

RESOLVED that,

.....

T2.16

3.16.6 Stopover and/or Transfer Charges

3.16.6.1 When a stopover and/or transfer charge is applicable to a specific point, imprint

“S” followed by the amount immediately after the city to which it applies.

Example:

NYC_NA_MIA_S10.00NA_LAX

3.16.6.2 When a charge is applicable for stopover(s) and/or transfer(s) in excess of

those allowed by the fare, imprint “S” preceded by the number of excess stopovers

and/or transfers followed by the total amount of such excess charges. This entry shall

b e made at the end of the itinerary preceding the total amount in NUCs.

Example

3S45.00

For each stopover or transfer charge. imprint “S” followed by the amount immediately

after the city to which the charge applies.

Example:

HKG CC TYO Q4.25CC SFO S50.0 0BB MEX

M606.50BB LAX S40.00CC TYO S60.00CC HKG

M606.50NUC1367.25END ROE7.80275

.....

T2.5

3.16.7.3 Multiple Surcharges

... 3.16.7.2

...

Example (return journey with a surcharge applied in both fare components)

YTO CC X/TYO BB SIN Q YTOSIN13.09 M3497.42BB X/TYO CC YTO Q

SINYTO13.09 M3497.42NUC7021.02END ROE1.14527.T2.16

Resolution 722 Attachment ‘C’

GLOSSARY

Symbol Entry

S NYC_BB_MIA_S10.00BB_LAX

Stopover charge applicable to

a specific point

S345.00

Stopover charge(s) in excess

of those allowed by the fare

S PAR_BB_BKK_S50.00BB_HKG

_S40.00CC_SYD

Stopover or transfer

charge (s)

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 722f

ELECTRONIC TICKET

— AIRLINE

(amending)

PSC( 34 35 )722f Expiry: Indefinite

Type: B

RESOLVED that,

.....

T2.12

Section 3

– Definitions

... 3.9. EXCHANGE/REISSUE TRANSACTIONS

Exchange is defined as the value of one document moved to another document, in

accordance with the provisions of IATA Passenger Tariff Coordinating Conference

Resolution 017f Section C 1 'Voluntary Reroutings' (for totally unused tickets).

Reissue is defined as an issuance of a new ticket against a previously issued ticket, in

accordance with the provisions of IATA Passenger Tariff Coordinating Conference

Resolution 017f Section B 'Voluntary Reroutings' (for partly used pricing units).

...

**Secretary Note** : Renumber remaining paragraphs

.

T2.6

**....** 6.2.1.7 The Validating Carrier 1 shall deliver an Itinerary/Receipt. This document shall

include, but not be limited to, the following:

.... Ticket/Document Number(s) 5

....

....

5 Include conjunction ticket/document numbers.Attachment ‘A ’ T7

ELECTRONIC TIC KET AND MISCELLANEOUS DOCUMENTS

DATA ELEMENTS GLOSSARY

(amending)

**Note:** This Glossary applies to the Airline ET Resolution (A4A 20.60/IATA 722f), the Neutral ET Resolution

(A4A 20.61/IATA 722g), the Ground Handling ET Resolution (A4A 20.62/IATA 722h), the Airline EMD

Resolution (A4A 20.63/IATA 725f), the Neutral EMD Resolution (A4A 20.64/IATA 725g), the Electronic

Ticketing Third Party Resolution (A4A only, 20.65) and the Ground Handling EMD Resolution (A4A

20.66/IATA 725h).

**Note:** For the applicability of individual data elements, refer to the Glossary Applicability Reference Table

and the individual matrices

Glossary Applicability Reference Table T 2.3

The table represents the resolutions matrices in which the data elements are applicable

invoice Y = This data element is used in at least one message in the Resolution listed.

For data element groups (e.g. CARRIER FEE DATA) a Y = At least one data element of

this group is used in at least one message in the Resolution listed.

Blank = This data element is not used in any message in the Resolution listed

. Secretary Note: This entire table is new.

RESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

ACCOUNT CODE Y Y

ADDITIONAL COLLECTION

- TAX/FEE/CHARGE

AMOUNT(S) Y Y Y Y Y Y

ADDITIONAL COLLECTION

- TICKET/DOCUMENT

TOTAL AMOUNT Y Y Y Y Y Y

ADDITIONAL SERVICES FILED FEE AMOUNT

ADDITIONAL SERVICES FILED FEE BANKERS

SELLING RATE (BSR)

ADDRESS VERIFICATION CODE (CREDIT CODE) Y

AGENT NUMERIC CODE (IATA NUMBER) Y Y Y Y Y Y

AGENT PSEUDO CITY CODE Y Y Y Y Y Y

AIRLINE CONFIRMATION NUMBER Y Y Y Y Y Y

AIRLINE DESIGNATOR (VALIDATING CARRIER) Y Y Y Y

AIRLINE INDEXING FIELD Y Y Y Y Y Y

APPROVAL CODE (CREDIT CARD) Y Y

AROUND THE WORLD FARE INDICATOR Y Y

ASSOCIATED FARE BASIS Y Y Y

AUTHORISED AMOUNT (CREDIT CARD) Y Y Y

BAGGAGE POOL INDICATORS Y Y

BAGGAGE TAG NUMBERS Y Y

BANK EXCHANGE RATE (BSR) Y Y Y

BASE FARE AMOUNT Y Y Y Y Y Y

BASE FARE NET AMOUNT Y Y Y Y Y

BASE FARE SELL AMOUNT Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

BILLING AIRLINE ACCOUNTING CODE Y

BILLING CARRIER INDICATOR Y

BOOKING AGENT IDENTIFICATION Y Y Y Y Y Y

CARRIER FEE DATA:

- Begin Y Y

Carrier Fee Type Y Y

Carrier Fee Owner Y

Carrier Fee Code Y Y

Carrier Fee Commercial Name Y Y

Carrier Fee Reporting Indicator Y Y

Carrier Fee Amount Y Y

Carrier Fee Application Code Y Y

Carrier Fee From Airport/City Code Y Y

Carrier Fee To Airport/City Code Y Y

Carrier Fee Form of Payment Type Y Y

Carrier Fee Form of Payment Credit Card Vendor

Code Y Y

Carrier Fee Form of Payment Credit Card Account

Number Y Y

Carrier Fee Approval Code (Credit Card) Y Y

Carrier Fee Expiry Date (Credit Card) Y Y

Carrier Fee Tax Code Y Y

Carrier Fee Tax Amount Y Y

Carrier Fee Tax Currency Code Y Y

Carrier Fee Tax Application Code Y Y

Carrier Fee Tax On Tax Code Y Y

Carrier Fee Tax On Tax Amount Y Y

Carrier Fee Tax on Tax Currency Code Y Y

Carrier Fee Tax on Tax Application Code Y Y

Carrier Fee Fare Component Number Y

Carrier Fee Fare Component Rule Code Y

Carrier Fee Fare Component Rule Number Y

Carrier Fee Fare Component Tariff Number Y

Carrier Fee Fare Component Rule Matching Fare

Class Y

CARRIER FEE DATA:

- End

CERTIFICATE NUMBER Y Y Y Y

CHECKED

- IN/LIFTED AIRLINE DESIGNATOR

(MARKETING CARRIER) Y Y Y Y Y Y

CHECKED

- IN/LIFTED AIRLINE DESIGNATOR

(OPERATING CARRIER) Y Y Y Y Y Y

CHECKED

- IN/LIFTED DATE OF FLIGHT Y Y

CHECKED

- IN/LIFTED DESTINATION

AIRPORT/CITY CODE Y Y Y Y Y Y

CHECKED

- IN/LIFTED FLIGHT DEPARTURE TIME Y Y

CHECKED

- IN/LIFTED FLIGHT NUMBER

(MARKETING CARRIER) Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

CHECKED

- IN/LIFTED FLIGHT NUMBER

(OPERATING CARRIER) Y Y

CHECKED

- IN/LIFTED FLIGHT PREFIX/SUFFIX

(MARKETING CARRIER) Y Y

CHECKED

- IN/LIFTED FLIGHT PREFIX/SUFFIX

(OPERATING CARRIER) Y Y

CHECKED

- IN/LIFTED ORIGIN AIRPORT/CITY

CODE Y Y Y Y Y Y

CHECKED

- IN/LIFTED RESERVATIONS BOOKING

DESIGNATOR (MARKETING CARRIER) Y Y

CHECKED

- IN/LIFTED RESERVATIONS BOOKING

DESIGNATOR (OPERATING CARRIER) Y Y

COMMISSION AMOUNT Y Y

COMMISSION RATE Y Y

COMMISSION TYPE Y Y

CONSUMED AT ISSUANCE INDICATOR Y

COUPON NUMBER Y Y Y Y Y Y

COUPON STATUS INDICATOR Y Y Y Y Y Y

COUPON VALUE Y Y Y

COUPON/ITINERARY SEQUENCE NUMBER Y Y Y Y Y Y

CREDIT CARD CORPORATE CONTRACT Y Y Y Y

CREDIT CARD TRANSACTION INFORMATION Y Y Y Y

CURRENT AIRLINE DESIGNATOR (MARKETING

CARRIER) Y Y

CURRENT AIRLINE DESIGNATOR (OPERATING

CARRIER) Y Y

CURRENT DATE OF FLIGHT Y Y

CURRENT DESTINATION AIRPORT/CITY CODE Y Y

CURRENT FLIGHT DEPARTURE TIME Y Y

CURRENT FLIGHT NUMBER (MARKETING

CARRIER) Y Y

CURRENT FLIGHT NUMBER (OPERATING

CARRIER) Y Y

CURRENT ORIGIN AIRPORT/CITY CODE Y Y

CURRENT RESERVATIONS BOOKING

DESIGNATOR (MARKETING CARRIER) Y Y

CURRENT RESERVATIONS BOOKING

DESIGNATOR (OPERATING CARRIER) Y Y

CUSTOMER FILE REFERENCE Y Y Y Y

CUSTOMER IDENTIFICATION Y Y Y Y

DATE OF SERVICE Y Y Y

DOCUMENT TYPE Y Y Y Y Y Y

EMERGENCY LOCK INDICATOR Y Y

ENDORSEMENTS/RESTRICTIONS Y Y Y Y Y Y

EQUIVALENT FARE PAID Y Y Y Y Y Y

EQUIVALENT FARE PAID NET AMOUNT Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

EQUIVALENT FARE PAID SELL AMOUNT Y Y

EXCESS BAGGAGE DATA ELEMENTS:

- Begin Y Y Y

Currency Code Per Unit Y Y

Excess Baggage/Over Allowance Qualifier Y Y Y

Rate Per Unit Y Y Y

Total Number in Excess Y Y Y

EXCESS BAGGAGE DATA ELEMENTS:

- End

EXCHANGED RESIDUAL FARE COMPONENT

DATA:

- Begin Y Y

Exchanged Residual Fare Component Count Y Y

Exchanged Residual Fare Component Number Y Y

Exchanged Residual Fare Component Coupon

Sequence Y Y

Exchanged Residual Fare Calculation

Coupon/Itinerary Sequence Number Y Y

Exchanged Residual Fare Component From

Airport/City Code Y Y

Exchanged Residual Fare Component Airline

Designator Y Y

Exchanged Residual Fare Component To Airport/City

Code Y Y

Exchanged Residual Fare Component Stop/No

Stopover Indicator (X/O) Y Y

Exchanged Residual Fare Component Base Amount Y Y

Exchanged Residual Fare Component Base Net

Amount Y Y

Exchanged Residual Fare Component Base Sell

Amount Y Y

Exchanged Residual Fare Component Fare Basis

Code Y Y

Exchanged Residual Fare Component Ticket

Designator Y Y

Exchanged Residual Fare Component Construction

Principle Indicator Y Y

Exchanged Residual Fare Component Construction

Principle From Airport/City Code Y Y

Exchanged Residual Fare Component Construction

Principle To City/Airport Code Y Y

Exchanged Residual Fare Component Construction

Principle Amount Y Y

Exchanged Residual Fare Component Fare Rule

Code Y Y

Exchanged Residual Fare Component Waiver Code Y Y

Exchanged Residual Total Base Construction

Amount Y Y

Exchanged Residual Total Net Construction Amount Y Y

Exchanged Residual Total Sell Construction Amount Y Y

Exchanged Residual Rate of Exchange (ROE) Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

Exchanged Residual Tax/Fee/Charge Amount Y Y

Exchanged Residual Total Amount Y Y

Exchanged Residual Total Net Amount Y Y

Exchanged Residual Total Sell Amount Y

EXCHANGED RESIDUAL FARE COMPONENT

DATA:

- End

EXCHANGED TICKET/DOCUMENT QUALIFIER Y Y Y

EXPIRY DATE (CREDIT CARD) Y Y Y

EXTENDED PAYMENT CODE Y Y Y Y

FARE BASIS Y Y Y

FARE CALCULATION AREA Y Y Y Y Y Y

FARE CALCULATION AREA NET AMOUNT Y Y

FARE CALCULATION AREA SELL AMOUNT Y Y

FARE CALCULATION MODE INDICATOR Y Y Y Y Y Y

FARE CALCULATION PRICING INDICATOR Y Y Y Y Y Y

FARE COMPONENT CALCULATION:

- Begin Y Y Y Y Y

Fare Component Calculation Account Code Y Y Y Y Y

Fare Component Calculation Input Designator Y Y Y Y Y

Fare Component Calculation Price Quote Date Y Y Y Y Y

Fare Component Count Y Y Y Y Y

Priceable Unit Number Y Y Y Y Y

Fare Component Coupon Priced RBD Y Y Y Y Y

Fare Component Priced Passenger Type Code Y Y

Fare Component Number Y Y Y Y Y

Fare Component Construction Principle Indicator Y Y Y Y Y

Fare Component Construction Principle From

Airport/City Code Y Y Y Y Y

Fare Component Construction Principle To

City/Airport Code Y Y Y Y Y

Fare Component Construction Principle Amount Y Y Y Y Y

Fare Component Coupon Sequence Y Y Y Y Y

Fare Calculation Coupon/Itinerary Sequence Number Y Y Y Y Y

Fare Component Airline Designator Y Y Y Y Y

Fare Component From Airport/City Code Y Y Y Y Y

Fare Component Stop/No Stopover Indicator (X/O) Y Y Y Y Y

Fare Component To Airport/City Code Y Y Y Y Y

Fare Component Base Amount Y Y Y Y Y

Fare Component Base Net Amount Y Y

Fare Component Base Sell Amount Y Y

Fare Component Fare Basis Code Y Y Y Y Y

Fare Component Fare Owner Y Y Y Y Y

Fare Component Fare Rule Code Y Y Y Y Y

Fare Component Rule Number Y Y Y Y Y

Fare Component Agreement Code Y Y Y Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

Fare Component Tariff Number Y Y Y Y Y

Fare Component Ticket Designator Y Y Y Y Y

Fare Component Ticket Designator Qualifier Y Y Y Y Y

Fare Component Waiver Code Y Y Y Y Y

Rate of Exchange (ROE) Y Y Y Y Y

Total Base Construction Amount Y Y Y Y Y

Total Net Construction Amount Y Y Y

Total Sell Construction Amount Y Y Y

FARE COMPONENT CALCULATION:

- End

FARE RULE INDICATOR Y Y

FARE TRANSACTION VALUES:

- Begin Y

Base Fare Transaction Amount Y

Equivalent Paid Fare Transaction Amount Y

Transaction Conversion Rate Y

Transaction Reissue Sequence Number Y

FARE TRANSACTION VALUES:

- End

FEE OWNER AIRLINE DESIGNATOR Y Y

FLOWN AIRLINE DESIGNATOR (MARKETING

CARRIER) Y Y Y Y Y Y

FLOWN AIRLINE DESIGNATOR (OPERATING

CARRIER) Y Y Y Y Y Y

FLOWN DATE OF FLIGHT Y Y

FLOWN DESTINATION AIRPORT/CITY CODE Y Y Y Y Y Y

FLOWN FLIGHT DEPARTURE TIME Y Y

FLOWN FLIGHT NUMBER (MARKETING CARRIER) Y Y

FLOWN FLIGHT NUMBER (OPERATING CARRIER) Y Y

FLOWN FLIGHT PREFIX/SUFFIX (MARKETING

CARRIER) Y Y

FLOWN FLIGHT PREFIX/SUFFIX (OPERATING

CARRIER) Y Y

FLOWN ORIGIN AIRPORT/CITY CODE Y Y Y Y Y Y

FLOWN RESERVATIONS BOOKING DESIGNATOR

(MARKETING CARRIER) Y Y

FLOWN RESERVATIONS BOOKING DESIGNATOR

(OPERATING CARRIER) Y Y

FORM OF PAYMENT AMOUNT Y Y Y Y Y Y

FORM OF PAYMENT CREDIT CARD ACCOUNT

NUMBER Y Y Y Y Y Y

FORM OF PAYMENT CREDIT CARD VENDOR

CODE Y Y Y Y Y Y

FORM OF PAYMENT TYPE Y Y Y Y Y Y

FREE BAGGAGE ALLOWANCE Y Y Y

FREQUENT FLYER AIRLINE DESIGNATOR Y Y Y Y Y Y

FREQUENT FLYER REFERENCE NUMBER Y Y Y Y Y Y

GROUND HANDLED AIRLINE DESIGNATOR Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

GROUND HANDLING SYSTEM INDICATOR Y Y

IN CONNECTION WITH ADULT

TICKET/DOCUMENT Y Y Y

IN CONNECTION WITH COUPON NUMBER Y Y Y Y Y Y

IN CONNECTION WITH DOCUMENT NUMBER Y Y Y Y Y Y

IN CONNECTION WITH INFANT

TICKET/DOCUMENT Y Y Y

IN CONNECTION WITH QUALIFIER Y Y Y Y Y Y

INVOICE NUMBER (Print Line A

- Neutral

Documents) Y Y Y Y

INVOLUNTARY INDICATOR Y Y Y Y Y Y

ISSUANCE INFORMATION

ISSUED IN EXCHANGE FOR Y Y Y Y Y Y

ISSUING AGENCY/AIRLINE

– NAME AND PLACE

OF ISSUE Y Y Y Y Y Y

ISSUING AGENT IDENTIFICATION Y Y Y Y Y Y

NET REPORTING INDICATOR Y Y Y Y

NETTING DATA ELEMENTS:

- Begin Y Y Y

Additional Collection Base Fare Amount Y Y Y

Additional Collection Base Fare Net Amount Y

Additional Collection Base Fare Sell Amount Y

Additional Collection Equivalent Paid Base Fare

Amount Y Y Y

Additional Collection Equivalent Paid Base Fare Net

Amount Y

Additional Collection Equivalent Paid Base Fare Sell

Amount Y

Additional Collection Equivalent Paid Total Amount Y Y Y

Additional Collection Total Tax Amount Y Y Y

Additional Collection Total Net Amount Y

Additional Collection Total Sell Amount Y

Residual Value Base Fare Amount Y Y Y

Residual Value Base Fare Net Amount Y

Residual Value Base Fare Sell Amount Y

Residual Value Equivalent Paid Base Fare Amount Y Y Y

Residual Value Equivalent Paid Base Fare Net

Amount Y

Residual Value Equivalent Paid Base Fare Sell

Amount Y

Residual Value Equivalent Paid Total Amount Y Y Y

Residual Value Total Tax Amount Y Y Y

Residual Value Total Amount Y Y Y

Residual Value Total Net Amount Y

Residual Value Total Sell Amount Y

Penalty Fee Amount YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

NETTING DATA ELEMENTS:

- End

NEW FARE BASIS CODE

NEW REISSUE TICKET NUMBER QUALIFIER Y Y Y Y

NON

- COMMISSIONABLE INDICATOR Y

NON

- ENDORSABLE INDICATOR Y Y Y Y Y Y

NON

- INTERLINABLE INDICATOR Y

NON

- REFUNDABLE AMOUNT QUALIFIER/NO

VALUE AMOUNT QUALIFIER/PENALTY AMOUNT

QUALIFIER Y Y Y Y Y Y

NON

- REFUNDABLE INDICATOR Y Y Y Y Y Y

NON

- REFUNDABLE/NO VALUE/PENALTY

AMOUNT Y Y Y Y Y Y

NON

- REISSUEABLE/NON

- EXCHANGEABLE

INDICATOR Y Y Y

"NOT VALID AFTER” DATE Y Y Y

"NOT VALID BEFORE” DATE Y Y Y

NOTICES REQUIRED Y Y

NUMBER OF BAGGAGE PIECES Y Y

NUMBER OF BOOKLETS ISSUED Y Y Y Y Y Y

NUMBER OF TICKET/DOCUMENT NUMBERS Y Y Y Y Y Y

ORIGINAL FARE BASIS CODE

ORIGINAL ISSUE AGENT NUMERIC CODE (IATA

NUMBER) Y Y Y Y Y Y

ORIGINAL ISSUE DATE (DDMMMYY) Y Y Y Y Y Y

ORIGINAL ISSUE LOCATION

— CITY CODE Y Y Y Y Y Y

ORIGINAL ISSUE TICKET/DOCUMENT NUMBER Y Y Y Y Y Y

PARTY TO BE BILLED

PASSENGER CHECK

- IN (FOID):

- Begin Y Y Y Y Y Y

Passenger Check

- In Identification (FOID) Y Y Y Y Y Y

Passenger Check

- In Identification Number (FOID) Y Y Y Y Y Y

Passenger Check

- In Identification Type (FOID) Y Y Y Y Y Y

PASSENGER CHECK

- IN (FOID):

- End

PASSENGER NAME Y Y Y Y Y Y

PASSENGER SPECIFIC DATA (Print Line A) Y Y Y Y Y Y

PASSENGER TELEPHONE NUMBER Y Y Y

PASSENGER TYPE CODE (stored in passenger

name record) Y Y Y Y Y

PENALTY RESTRICTION INDICATOR Y Y Y Y Y Y

PNR REFERENCE Y Y Y Y Y Y

PNR REFERENCE OF VALIDATING CARRIER Y Y Y Y Y Y

PRESENT AT Y Y Y

PRESENT CREDIT/DEBIT CARD INDICATOR Y Y Y Y

PRESENT TO Y Y Y

PREVIOUS COUPON STATUS INDICATOR Y Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

PRICING DATE (DDMMMYY) Y Y Y

PRICING ISO COUNTRY CODE Y Y Y

PRICING LOCATION CITY/AIRPORT CODE Y Y Y

PRICING SYSTEM CODE Y Y Y Y Y Y

PRICING TIME OF ISSUE (HHMM) Y Y Y

PRINT LINE TEXT

PROMOTIONAL CODE Y Y Y

REASON FOR ISSUANCE CODE Y Y Y

REASON FOR ISSUANCE SUB CODE Y Y Y

REASON FOR ISSUANCE SUB CODE

DESCRIPTION Y Y Y

REDIRECTED DATE OF FLIGHT Y Y

REDIRECTED DESTINATION AIRPORT/CITY

CODE Y Y

REDIRECTED FLIGHT DEPARTURE TIME Y Y

REDIRECTED FLIGHT NUMBER Y Y

REDIRECTED FLIGHT PREFIX/SUFFIX Y Y

REDIRECTED FROM AIRLINE DESIGNATOR Y Y

REDIRECTED ORIGIN AIRPORT/CITY CODE Y Y

REDIRECTED RESERVATION BOOKING

DESIGNATOR Y Y

REDIRECTED RESERVATION STATUS CODE Y Y

REDIRECTED TO AIRLINE DESIGNATOR Y Y

REFUND

- CALCULATION INDICATOR Y Y Y

REFUND

- TAX/FEE/CHARGE AMOUNT(S) Y Y

REFUND

- TICKET/DOCUMENT TOTAL AMOUNT Y Y

REISSUED FLOWN FLIGHT COUPON DATA:

- Begin Y Y Y Y Y

Reissued Flown Airline Designator (Marketing

Carrier) Y Y Y Y Y

Reissued Flown Airline Designator (Operating

Carrier) Y Y Y Y Y

Reissued Flown Count of Intermediate Stops Y Y Y Y Y

Reissued Flown Coupon Number Y Y Y Y Y

Fare Calculation Coupon/Itinerary Sequence Number Y Y Y Y Y

Reissued Flown Date of Flight Y Y Y

Reissued Flown Destination Airport/City Y Y Y Y Y

Reissued Flown Equipment Type Y Y Y

Reissued Flown Fare Basis Code Y Y Y

Reissued Flown Flight Arrival Date Y Y Y

Reissued Flown Flight Arrival Time Y Y Y

Reissued Flown Flight Departure Time Y Y Y

Reissued Flown Flight Number (Marketing Carrier) Y Y Y

Reissued Flown Flight Number (Operating Carrier) Y Y Y

Reissued Flown Intermediate Airport/City Code

Stop(s) Y Y Y Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

Reissued Flown Origin Airport/City Y Y Y Y Y

Reissued Flown Reservation Booking Designator

(Marketing Carrier) Y Y Y

Reissued Flown Reservation Booking Designator

(Operating Carrier) Y Y Y

Reissued Flown Stopover Code (X/O Indicator) Y Y Y Y Y

Reissued Flown Ticket Designator Y Y Y Y

Reissued Flown Waiver Code Y Y Y Y Y

Reissued Ticket Date of Issue Y Y Y Y Y

Reissued Ticket Number Y Y Y Y Y

REISSUED FLOWN FLIGHT COUPON DATA:

-

End

REISSUED TICKET/DOCUMENT DATE OF ISSUE

REISSUED TICKET/DOCUMENT NUMBER

REMARKS Y Y

RESERVATION CHANGE AIRLINE DESIGNATOR

(MARKETING CARRIER) Y Y

RESERVATION CHANGE AIRLINE DESIGNATOR

(OPERATING CARRIER) Y Y

RESERVATION CHANGE DATE OF FLIGHT Y Y

RESERVATION CHANGE DESTINATION

AIRPORT/CITY CODE Y Y

RESERVATION CHANGE FLIGHT DEPARTURE

TIME Y Y

RESERVATION CHANGE FLIGHT NUMBER

(MARKETING CARRIER) Y Y

RESERVATION CHANGE FLIGHT NUMBER

(OPERATING CARRIER) Y

RESERVATION CHANGE ORIGIN AIRPORT/CITY

CODE Y

RESERVATION CHANGE RESERVATION

BOOKING DESIGNATOR (MARKETING CARRIER) Y Y

RESERVATION CHANGE RESERVATION

BOOKING DESIGNATOR (OPERATING CARRIER) Y

RESERVATION CHANGE RESERVATION STATUS

CODE Y Y

RESPONSE COMMENTS Y Y Y Y Y Y

SEGMENT/COUPON IDENTIFIER Y Y Y Y Y Y

SERVICING AIRLINE/SYSTEM PROVIDER

IDENTIFIER Y Y Y Y Y Y

SETTLEMENT AUTHORISATION CODE Y Y Y Y Y

SOLD AIRLINE DESIGNATOR (MARKETING

CARRIER) Y Y Y Y Y Y

SOLD AIRLINE DESIGNATOR (OPERATING

CARRIER) Y Y Y Y Y Y

SOLD DATE OF FLIGHT Y Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

SOLD DESTINATION AIRPORT/CITY CODE Y Y Y Y Y Y

SOLD FLIGHT ARRIVAL DATE Y Y Y

SOLD FLIGHT ARRIVAL TERMINAL Y

SOLD FLIGHT ARRIVAL TIME Y Y Y

SOLD FLIGHT DEPARTURE TERMINAL Y

SOLD FLIGHT DEPARTURE TIME Y Y Y

SOLD FLIGHT NUMBER (MARKETING CARRIER) Y Y Y

SOLD FLIGHT NUMBER (OPERATING CARRIER) Y Y

SOLD ORIGIN AIRPORT/CITY CODE Y Y Y Y Y Y

SOLD RESERVATION BOOKING DATE

SOLD RESERVATIONS BOOKING DESIGNATOR

(MARKETING CARRIER) Y Y Y

SOLD RESERVATIONS BOOKING DESIGNATOR

(OPERATING CARRIER) Y Y

SOLD RESERVATIONS STATUS CODE Y Y Y

SOLD SEAT NUMBER Y

SOURCE OF APPROVAL CODE (CREDIT CARD) Y Y Y Y

SPONSOR INFORMATION Y Y Y Y Y Y

STAFF AIRLINE OF EMPLOYMENT Y Y

STAFF DATE OF JOINING (DDMMMYY) Y Y

STAFF ID NUMBER Y Y

STAFF RESERVATION ENTITLEMENT Y Y

STAFF STATUS Y Y

STAFF TYPE OF TRAVEL Y Y

STATISTICAL CODE Y Y

STOPOVER CODE (X/O INDICATOR) Y Y Y Y Y Y

TAX/FEE/CHARGE CODE

TAX/FEE/CHARGE DATA AT THE TICKET

COUPON LEVEL:

- Begin Y Y Y Y

Cabin Y Y Y Y

Equipment Code Y Y Y Y

Journey Turnaround Airport/City Code Y Y Y Y

Passenger Date of Birth Y Y Y Y

Tax/fee/charge Amount Y Y Y Y

Tax/fee/charge Code Y Y Y Y

Tax/Fee/Charge Data Coupon Number Y

Tax/Fee/Charge Data Ticket/Document Number Y

Unticketed Point City/Airport Code Y Y Y Y

Unticketed Point Date and Local Time of Arrival Y Y Y Y

Unticketed Point Date and Local Time of Departure Y Y Y Y

Unticketed Point Departure Equipment Code Y Y Y Y

TAX/FEE/CHARGE DATA AT THE TICKET

COUPON LEVEL:

- End

TAX/FEE/CHARGE DETAILS:

- Begin Y Y Y Y Y YRESOLUTION GLOSSARY DATA ELEMENT: 722f 722g 722h 725f 725g 725h

Tax/Fee/Charge Amount Paid/New/To Be Refunded

Qualifier Y Y Y Y Y Y

Tax/Fee/Charge Amount Y Y Y Y Y Y

Tax/Fee/Charge Amount Currency Code Y Y Y Y Y Y

Tax/Fee/Charge Tax Code Y Y Y Y

Tax/Fee/Charge Filed Amount Y Y Y

Tax/Fee/Charge Filed Amount Currency Code Y Y Y

Tax/Fee/Charge Filed Code Y Y Y

Tax/Fee/Charge Filed Currency Conversion Rate Y Y Y

Tax/Fee/Charge Qualifier Y Y Y

TAX/FEE/CHARGE DETAILS:

- End

TAX ON COMMISSION INDICATOR Y Y

TAX ON EMD QUALIFIER Y Y Y

TICKET HANDLED AIRLINE DESIGNATOR Y Y Y

TICKET HANDLER SYSTEM INDICATOR Y Y Y

TICKET ISSUANCE ORIGINATOR CODE Y Y Y Y Y Y

TICKET TYPE INDICATOR Y Y

TICKET/DOCUMENT NUMBER Y Y Y Y Y Y

TICKETING DATE OF ISSUE (DDMMMYY) Y Y Y Y Y Y

TICKETING ISO COUNTRY CODE Y Y Y Y Y Y

TICKETING LOCATION CITY/AIRPORT CODE Y Y Y

TICKETING MODE INDICATOR (/ OR X) Y Y

TICKETING TIME OF ISSUE (HHMM) Y Y Y

TOTAL NUMBER OF FLIGHT/VALUE COUPONS Y Y Y Y Y

TOTAL TICKET/DOCUMENT AMOUNT Y Y Y Y Y

TOTAL TICKET/DOCUMENT NET AMOUNT Y Y

TOTAL TICKET/DOCUMENT SELL AMOUNT Y Y

TOUR CODE Y Y Y Y Y Y

TOUR NAME

TRANSACTION ACTION Y Y Y Y Y Y

TRANSACTION AGENT I.D. Y Y Y Y Y Y

TRANSACTION AGENT PSEUDO CITY CODE Y Y Y

TRANSACTION DATE/TIME

(DDMMMYY/HHMMSSZ) Y Y Y

TRUE ORIGIN/DESTINATION CITY CODES Y Y Y Y Y Y

VALIDATING AIRLINE DESIGNATOR Y Y Y Y Y

WAIVER CODE Y Y Y Y Y Y

WEIGHT OF BAGGAGE Y YT2.10

**...** INVOICE NUMBER (PLA) 10 ALPHANUMERICS

An agency or airline assigned number to internally identify the associated itinerary

invoice.

**Secretary note:** Remove from matrix also

T2.11

... Tour Name 86

ALPHANUMERICS

Name of the tour.

...

EXCHANGED/RESIDUAL FARE COMPONENT DATA T2.12

Exchange is defined as the value of one document moved to another document, in

accordance with the provisions of IATA Passenger Tariff Coordinating Conference

Resolution 017f Section C 1 'Voluntary Reroutings' (for totally unused tickets).

Reissue is defined as an issuance of a new ticket against a previously issued ticket, in

accordance with the provisions of IATA Passenger Tariff Coordinating Conference

Resolution 017f Section B 'Voluntary Reroutings' (for partly used pricing units).

T2.13

... SOLD FLIGHT DEPARTU RE DATE 7 ALPHANUMERIC

The scheduled date of departure in the format DDMMMYY for each coupon as it was

sold.

... SOLD DATE OF FLIGHT 7 ALPHANUMERIC

The scheduled date of departure in the format DDMMMYY for each coupon as it was

sold.

... DATE OF BIRTH

– 7 ALPHANUMERIC T14

The date of birth of the passenger in the format of DDMMMYY applied at the

ticket/document level.

...T2.4

....

REISSUED FLOWN FLIGHT COUPON DATA (Repeatable field)

Reissued Flown Involuntary Indicato r 1 ALPHANUMERIC

A code to indicate an involuntary change occurred on the flown coupon as follows:

D Diversion en Route

... T7

REASON FOR ISSUANCE CODE 1 ALPHANUMERIC

(Refer A4A RP 10.90 or IATA RP1790) (stored in passenger name record)

T4/T7

REASON FOR ISSUANCE SUB CODE

— 3 ALPHANUMERIC

(Applicable to 725f, 725g and 725h only), (Refer RP1790)

A secondary three

- character code which qualifies the Reason for Issuance Code as

sourced from ATPCO for the ATPCO optional services product.

IATA Standard Codes

The following codes are IATA standard codes to be used in accordance with the

associated definitions.

Sub Code Definition

999 UNDER COLLECTIONS FARES

998 UNDER COLLECTIONS TAX FEES CHARGES

997 DEPOSITS DOWN PAYMENTS

996 REFUNDABLE BALANCES

995 CANCELLATION FEE

994 REBOOKING FEE DOMESTIC WITH TAXES EG VAT WHERE APPLICABLE

993 REBOOKING FEE INTERNATIONAL

992 TICKET AMENDMENT FEE

991 TICKET FEE

990 BOOKING FEE

99K INVOLUNTARY DOWNGRADING

99J DISCOUNT CARD

99I RESIDUAL VALUE

99H UPGRADE AIRPORT TAX

980 LAND SERVICE

981 CABIN BAGGAGE

982 CARGO 1 to 25 POUNDS

983 CARGO 26 to 50 POUNDS

984 CARGO 51 to 75 POUNDS

985 CARGO AIRWAY BILL

986 CARGO MAIL ENVELOPE

987 CARGO SMALL PACKAGE

988 CREDIT CARD CHARGE

98A NON REVENUE INTERNATIONAL SERVICE FEE

98B TRANSPORTATION CREDIT VOUCHER

98C UNSPECIFIED TRANSPORATION

98D FOR REFUND ONLY

98E NON REFUNDABLE AMOUNT

98F PENALTY FEE

98G BOOKING CODE DISCREPANCY

98H STOPOVER CHARGE

98I SERVICE CHARGE

98J MISCELLANEOUS CHARGE

98K NET FARE DIFFERENCET5

...

IN CONNECTION WITH COUPON NUMBER

— 1 NUMERIC

(Repeatable field)

This element shall contain the coupon number(s) associated with the “in connection

with” document number.

IN CONNECTION WITH DOCUMENT NUMBER

— 14 ALPHANUMERIC

(Repeatable field) (14th digit reserved for future use)

A document number representing a transaction that is issued in relation to this

transaction.

IN CONNECTION WITH QUALIFIER

— 1 NUMERIC

A code used to indicate that an EMD

- A coupon is associated to or disassociated from

an ET coupon.

1 = Associated

2 = Disassociated

IN CONNECTION WITH DOCUMENT TYPE

– 1 ALP HA

(applicable to 725f, 725g, 725h only)

A code used to indicate the type of the document to which the EMD

- S is issued in

connection with.

J = EMD

- A

P = Paper document

T = E

- ticket

Y = EMD

- S

....

T7

PARTY TO BE BILLED 73 ALPHANUMERIC

The name of the Tour Operator to be billed.

...

... PRINT LINE TEXT 86 ALPHANUMERIC

Free form data as defined in the applicable Resolution.

...

remove the element from the matrices as shown below:

722f/20.60, 722g/20.61, 722h/20.62, 725f/20.53, 725g/20.64, 20.65, 725h/20.66

...

281 PRINT LINE TEXT (Not

Applicable) 86 A/N

...SOLD AIRLINE DESIGNATOR (MARKETING CARRIER) 3 ALPHANUMERIC

(Print Line F, Positions 20

- 22)

The two/three character designator identifying the Marketing Carrier for each coupon as it

was sold. (See Resolution definition of Marketing Carrier.)

STATISTICAL CODE 3 ALPHANUMERIC

**Note: IATA and A4A definitions differ.**

IATA only

For tickets:

Used for domestic or international sales differentiation; ‘D’ or ‘I’ should be inserted in the

first character position.

• If the ticket itinerary is Domestic and the point of sale is within the country of the

itinerary, value should be “D”.

• If the ticket itinerary is Domestic and the point of sale is outside of the country of

the itinerary, val ue should be “I”.

• If the ticket itinerary is International, value should be “I”.

For EMD

- A :

Used for domestic or international sales differentiation; ‘D’ or ‘I’ should be inserted in the

first character position.

• If EMD

- A coupons routing is domestic (all board points and off points within the

same country) and the point of sale is within the country of thee routing, the value

should be ‘D’.

• If EMD

- A coupons routing is domestic (all board points and off points within the

same country) and the point of sale is outside of the country, value should be ‘I’.

• If EMD

- A coupons routing is international, value should be ‘I’.

For EMD

- S:

Used for domestic or international sales differentiation; ‘D’ or ‘I’ should be inserted in the

first character position.

• If the EMD

- S has a routing, then the rule for EMD

- A applies.

• If the EMD

- S has no routing attached, then the value should be blank.

A4A only

**Note:** Intentionally written to be applicable to A4A Resolutions/Recommended Practices

only

**.**

Used for domestic or intern ational sales differentiation; ' D ' or ' I ' should be inserted in the

first character position. For the purpose of this Resolution, transportation which is not

wholly within the United States and/or between the United States and Canada or

between points in C anada is considered international for both an original issuance and

an exchange or reissue transaction.

For EMD

- A :Used for domestic or international sales differentiation; “D” or “I” should be inserted in

the first character position.

• If EMD

- A coupons routing is domestic (transportation which is wholly within the

United States and/or between the United States and Canada or between points

in Canada), the value should be “D”.

• When EMD

- A coupon routing is not domestic, it is international, and the value

should be ‘I’.

For EMD

- S:

Used for domestic or international sales differentiation; “D” or “I” should be inserted in

the first character position.

• If the EMD

- S has a routing, then the rule for EMD

- A applies.

• If the EMD

- S has no routing attached, then the value should be blank.

TAX ON COMMISSION INDICATOR 1 ALPHANUMERIC

(Applicable to IATA Only)

An Indicator (value =Y) to signal that a tax is to be calculated by the BSP Processing

Center.T13

Attachment ‘B’

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

(amending)

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

Data Element No. Char

acters

A N, or A/N Display

D, J Unsolicited

- Airport

Control

(Information

–

A4A only)

T I History

Display

H Request

Airport Control

B Change of

Status

C Redirect

Airport

Control

N Reservatio

n Change

A Emergency

Lock

M System

Update

U

20.60/722f

– 2013 MANUAL REQ RESP REQ RESP REQ RES

P REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

Tax/Fee/Charge Data at the Ticket

Coupon Level

– Begin:

Airport Code (Not Applicable) 5 A C C C

Applicable Amount (Not Applicable) 11 A/N C C C

Cabin 1 A/N C C C

Currency Type (Not Applicable) 4 A/N C C C

Equipment Type Code 3 A/N C C C

Journey Turnaround Airport/City Code 5 A/N C C C

Passenger Date of Birth 6 N C C C

Reported Amount (Not Applicable) 11 A/N C C C

Segment Tax Airport Code (Not

Applicable) 6 A C C C

Tax/Fee/Charge Amount 12 A/N C C C

Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Data Coupon Number 1 N C C C

Tax/Fee/Charge Data Ticket/Document

Number 14 A/N C C C

Unticketed Point Airport/City Code 5 A/N C C C

Unticketed Point Date and Local Time of

Arrival 11 A/N C C C

Unticketed Point Date and Local Time of

Departure 11 A/N C C C

Unticketed Point Departure Equipment

Code 3 A/N C C C

Tax/Fee/Charge Data at the Ticket

Coupon Level

– End:T2.13

Attachment B

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

NOTES:

1. Only to be used in a cod eshare situation to identify the Billing Carrier when different 6. Not used at this time.

from the Operating Carrier. For Unsolicited Airport Control it shall only be used when the 7. To be used whe n the Coupon Status Indicator is being changed to ‘F’.

Operating Carrier is sending the Billing Carrier the Flo wn Ticket/coupon(s) information 8. To be used when a carrier has Airport Control and wants to redirect c ontrol to another carrier.

needed to settle w ith the Validating Carrier. 9. To be used in a code share flight situation when the Operating Carrier (Code Share Partner) is

2. See Resolution for required combination of 'search criteria' requesting Airport Control of an ET.

(Section titled 'Display' under ' Procedures'). 10. To be used in a code share flight situation to identify the Marketing Carrier.

3. Not used at this time 11. If a paper ticket is issued, the Coupon Status Indicator 'T' is mandatory.

4. This data element shall NOT be sent in Information Message

. 12. Conditional for Change of Status to Reissue/Exchange for the new reissue ticket/document.

(Applicable to A4A only) number(s).

5. Must send when the status is being changed to ‘E’, ‘F’, ‘R’, ‘X’ or ‘P’.

A = Alphabetic Characters Only N = Numeric Characters Only A/N = Alphabetic and Numeric Characters Allowed

C = Condi tional (must provide if available/applicable) M = Mandatory (must provide at all times) O = Optional

@ = New Element in this Revision  = Change to Element in this Revision  = Deleted Element in this Revision

Data Element No. Char

acters

A N, or

A/N Display

Transaction

Action Code

D, J Unsolicited

- Airport

Control

(Information

– A4A only)

Transaction

Action Codes

T I

(I

– A4A only) History

Display

H Request

Airport

Control

Transaction

Action Code

B Change of

Status

Transaction

Action Code

C Redirect

Airport

Control

Transaction

Action Code

N Reservatio

n Change

Transaction

Action Code

A Emergency

Lock

Transaction

Action Code

M System

Update

Transaction

Action Code

U

20.60/722f

– 2013 MANUAL REQ RESP REQ RESP REQ **RES**

**P** REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

... Sold Date of Flight 7 A/N 0 2 C C C C

... Sold Flight Departure Date 7 A/N 0 2 C C C CT2.4

Attachment ‘ B ’

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

(amending)

ELEMENT

DESCRIPTION

Transaction CHAR.

A, N

OR

A/N DISPLAY UNSOLICITED

AIRPORT

CONTROL

(INFORMATION

– ATA ONLY) HISTORY

DISPLAY REQUEST

AIRPORT

CONTROL CHANGE

OF STATUS REDIRECT

AIRPORT

CONTROL RESERVATION

CHANGE EMERGENCY

LOCK SYSTEM

UPDATE

Action Code

--

- > D, J T (I

– ATA

ONLY H B C N A M U

RESOLUTION

722 f REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

... Reissued

Flown

Involuntary

Indicator 1 A/N C C C

...

T14

Data Element No.

Char

acters

A, N OR

A/N Display

Transaction

Action

Code

D Unsolicited

Airport

Control

Transaction

Action

Code

T (I

- A4A

ONLY)

Information

- A4A Only) History

Display

Transaction

Action

Code

H Request

Airport

Control

Transaction

Action

Code

B Change of

Status

Transaction

Action

Code

C Redirect

Airport

Control

Transaction

Action

Code

N Reservation

Change

Transaction

Action

Code

A Emergency

Lock

Transaction

Action

Code

M System

Update

Transaction

Action Code

U

20.60/722 f RE

Q RESP RE

Q RESP RE

Q RESP REQ RES

P RE

Q RESP RE

Q RESP REQ RESP RE

Q RESP RE

Q RESP

Date of Birth 7 A/N C C C

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 722g

ELECTRONIC TICKET

— NEUTRAL

(amending)

PSC( 34 35 )722g Expiry: Indefinite

Type: B

RESOLVED that,

.....

T2.6

6.2.3.8 The issuing travel agency shall deliver an Itinerary/Receipt. This document

shall include, but not be limited

to, the following:

.... Ticket/Document Number(s) 5

....

....

4 Include conjunction ticket/document numbers.

T2.1

... 6.6 EXCHANGE/REISSUE

... 6.6.13 When an “Exchange/Reissue” message is used, no part of the transaction may

be voided. The new ticket may only be exchanged/reissued, or refunded, or reversed

with a Void Exchange/Reissue message. (See Void Original Issue or

Exchange/Reissue section)

...T14

Attachment ‘B’

Data Element No.

Char

acters

A, N

OR A/N Issuance

– Information

Transaction

Action Code

S AND I

(I applicable

to A4A only ) Display

Transaction

Action

Code

D History

Display

Transaction

Action

Code

H Exchange/

Reissue

Transaction

Action

Code

E Refund

Transaction

Action

Code

R Reservation

Change

Transaction

Action

Code

A Refund

Cancel

Transaction

Action Code

Z System

Cancel

Transaction

Action

Codes

X And Y Void

Transaction

Action

Codes

V And W

20.61/722 g REQ RESP REQ RES

P RE

Q RESP RE

Q RESP RE

Q RESP REQ RES

P REQ RESP RE

Q RESP RE

Q RESP

Date of Birth 7 A/N C C CT13

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

- NEUTRAL MESSAGES

Data Element No.

Char

acters

A, N

OR A/N Issuance

– Information

S AND I

(I applicable

to A4A only ) Display

D History

Display

H Exchange/

Reissue

E Refund

R Reservation

Change

A Refund

Cancel

Z System

Cancel

X And Y Void

V And W

20.61/722 g

- 2013 MANUAL REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

TAX/FEE/CHARGE DATA AT THE TICKET

COUPON LEVEL

- Begin:

Airport Code (Not Applicable) 5 A C C C

Applicable Amount (Not Applicable) 11 A/N C C C

Cabin 1 A/N C C C

Currency Type (Not Applicable) 4 A/N C C C

Equipment Code 3 A/N C C C

Journey Turnaround Airport/City Code 5 A/N C C C

Passenger Date of Birth 6 N C C C

Reported Amount (Not Applicable) 11 A/N C C C

Segment Tax Airport Codes (Not Applicable) 6 A C C C

Tax/Fee/Charge Amount 12 A/N C C C

Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Data Coupon Number (Not

Applicable) 1 N C C C

Tax/Fee/Charge Data Ticket/Document Number

(Not Applicable) 14 A/N C C C

Unticketed Point Airport/City Code 5 A/N C C C

Unticketed Point Date and Local Time of Arrival 11 A/N C C C

Unticketed Point Date and Local Time of

Departure 11 A/N C C C

Unticketed Point Departure Equipment Code 3 A/N C C C

TAX/FEE/CHARGE DATA AT THE TICKET

COUPON LEVEL

- End.T2.13

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014 ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

- NEUTRAL MESSAGES

NOTES:

1. Mandatory when used to cancel an ' Exchange/Reissue ' Message 4. If a paper ticket is issued, the coupon status indicator ' T ' is mandatory.

2. See Resolution for required combinations of ' Search Criteria ' 5. This data element shall not be sent in an ' Information ' Message

(Section titled ' Display ' under ' Procedures ' ) 6. This data element applies to the new ticket. All other data elements in the Response Message

apply to the

3. Used by the Validating Carrier to locate the document(s) being exchanged ticket coupon being exchanged.

A= Alphabetic Characters Only N=Numeric Characters Only A/N=Alphabetic and Numeric Characters Allowed

C = Conditional (must provide if available/applicable) M = Mandatory (must provide at all times) O = Optional

@ = Element Added in t his Revision  = Element Changed in this Revision  = Deleted Element in this Revision

Data Element No.

Char

acters

A, N

OR A/N Issuance

– Information

Transaction

Action Codes

S AND I

(I applicable

to A4A only ) Display

Transaction

Action Code

D History

Display

Transaction

Action Code

H Exchange/

Reissue

Transaction

Action Code

E Refund

Transaction

Action Code

R Reservation

Change

Transaction

Action Code

A Refund

Cancel

Transaction

Action Code

Z Syste

m

Cancel

Transaction

Action Codes

X And Y Void

Transaction

Action Codes

V And W

20.61/722 g

- 2013 MANUAL REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

Sold Date of Flight 7 A/N C O 2 C C C C C

...

Sold Flight Departure Date 7 A/N C O 2 C C C C CRESOLUTION 722h

ELECTRONIC TICKET

— GROUND HANDLING

(amending)

PSC( 34 35 )722h Expiry: Indefinite

Type: B

RESOLVED that,

.....

T2.6

**....** 6.1.4 The Ground Handler may provide the passenger with a duplicate

Itinerary/Receipt. This document shall include, but not be limited

to, the following:

.... Ticket/Document Number(s) 5

....

....

5 Include conjunction ticket/document numbers.Attachment B

T2.13

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX

- GROUND HANDLING MESSAGES

NOTES:

1. Not used at this time. 6. Not used at this time.

2. See Resolution for required combi nation of ’search criteria’ 7. To be used when the Coupon Status Indicator is being changed to ‘F’ or ‘ G’.

(Section titled ‘Display’ under ‘Procedures’). 8. To be used when an Operating Carrier forwards Airport Control to a Ground Handler as a result of

Redirect.

3. Not used at this time. 9. To be used in a code share flight situation.

4. Not used at this time 10. To be used in a code share flight situation to identify the Marketing Carrier.

5. Must send when the status is being changed to ‘F’ or ‘ G’

. 11. If a paper ticket is issued, the Coupon Status indicator ’T’ is mandatory

– applicable to A4A only.

A = Alphabetic Characters Only N = Numeric Characters Only A/N = Alphabetic and Numeric Characters Allowed C = Conditional (must provide if available/applicable)

M = Mandatory (must provide at all times) O = Optional N/A = Not Applicable T = Ticket

@ = New Element in this Revision  = Change to Element in this Revision  = Deleted Element in this Revision

Data Element No. Char

acters

A N, or

A/N Display

Transaction

Action Code

D Airport Control

Request

– Ground

Handling

Transaction

Action Code

G Change of

Status

Transaction

Action Code

C Redirected

Airport Control

Transaction

Action Code

N Emergency

Lock

Transaction

Action Code

M Unsolicited

- Airport Control

– Ground

Handling

Transaction

Action Code

K @System

Update

20.62/722h

– 2013 MANUAL REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

Sold Date of Flight 7 A/N O 2 C C C

... Sold Flight Departure Date 7 A/N O 2 C C C

...RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT

— AIRLINE

(amending)

PSC( 34 35 )725f Expiry: Indefinite

Type: B

RESOLVED that,

T2.6

**....** 6.2.1.5 The Validating Carrier 1 shall deliver a Receipt. This document shall include, but

not be limited

to, the following:

.... Ticket/Document Number(s) 5

....

....

5 Include conjunction ticket/document numbers.

T2.9

6.5 CONTROL

... 6.5.10 Code Share

...

6.5.10.1 For special settlement arrangements where the Billing Carrier will settle the

Flown/Used coupon(s) with the Validating Carrier, the Operating Carrier must include the

Billing Carrier Airline Designator Billing Airline Accounting Code in the Change Status

m essage to the Validating Carrier.

6.5.10.2 If Billing Carrier Airline Designator Billing Airline Accounting Code is included in

the Change of Status Message sent by the Operating Carrier, the Validating Carrier will

generate a SAC in the response message using the Billing Carrier Airline Designator

account code Billing Airline Accounting Code in the SAC.Attachme nt ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENT

MESSAGE CONSTRUCTION MATRIX

– AIRLINE MESSAGES

T14

Data Element No.

Char

acters

A, N

OR A/N Display

Transaction

Action Code

D Request

Airport

Control

Transaction

Action Code

B Change of

Status

Transaction

Action Code

C System

Update

Transaction

Action Code

U Unsolicited

Billing

Transaction

Action Code

L

20.63/725 f

- 2012 MANUAL REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

Date of Birth 7 A/N C C

T2.9

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

REQ RESP REQ RESP REQ RESP REQ RESP

Billing Airline

Accounting Code (App.

725f) 4 A/N C 1

NOTES:

1 Intentionally left blank Only used in a Codeshare scenario to identify the Billing Carrier when different from

the Operating Carrier.

T5

ELEMENT DESCRIPTION

Transaction NO CHAR.

A, N OR

A/N DISPLAY REQUEST AIRPORT

CONTROL CHANGE OF

STATUS SYSTEM UPDATE UNSOLICITED BILLING

Action code

- > D B C U L

RESOLUTION 725f REQ RESP REQ RESP REQ RESP REQ RESP REQ RES

... IN CONNECTION WITH

DOCUMENT TYPE 1A C C C

...T13

Data Element No.

Char

acter

s

A, N

OR

A/N Display

Transaction

Action Code

D Request

Airport

Control

Transaction

Action Code

B Change of

Status

Transaction

Action Code

C System Update

Transaction

Action Code

U Unsolicited

Billing

Transaction

Action Code

L

20.63/725 f REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

Tax/Fee/Charge Data at the

Ticket Coupon Level

– Begin:

Airport Code (Not Applicable) 5 A C C C

Applicable Amount (Not

Applicable) 11

A/N C C C

Cabin 1 A/N C C C

Currency Type (Not Applicable) 4 A/N C C C

Equipment Type Code 3 A/N C C C

Journey Turnaround Airport/City

Code 5 A/N C C C

Passenger Date of Birth 6 N C C C

Reported Amount (Not

Applicable) 11

A/N C C C

Segment Tax Airport Code (Not

Applicable) 6 A C C C

Tax/Fee/Charge Amount 12

A/N C C C

Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Data Coupon

Number 1 N C C C

Tax/Fee/Charge Data

Ticket/Document Number 14

A/N C C C

Unticketed Point Airport/City Code 5 A/N C C C

Unticketed Point Date and Local

Time of Arrival 11

A/N C C C

Unticketed Point Date and Local

Time of Departure 11

A/N C C C

Unticketed Point Departure

Equipment Code 3 A/N C C C

Tax/Fee/Charge Data at the

Ticket Coupon Level

– End:

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT

— NEUTRAL

(amending)

PSC( 34 35 )725g Expiry: Indefinite

Type: B

RESOLVED that,

.....

T2.6

**....** 6.2.1.6 The Issuing Travel Agency shall deliver Receipt. This document shall include,

but not be limited

to, the following:

.... Ticket/Document Number(s) 5

....

....

5 Include conjun ction ticket/document numbers.

Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUME NT

MESSAGE CONSTRUCTION MATRIX

– NEUTRAL MESSAGES

T2.9

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

REQ RESP REQ RESP REQ RESP REQ RESP

Billing Airline

Accounting Code (App.

725f) 4 A/NT14

Data Element No.

Char

acters

A, N

OR A/N Issuance

– Information

Transaction

Action Code

S AND I

(I applicable

to A4A only ) Display

Transaction

Action

Code

D History

Display

Transaction

Action

Code

H Exchange/

Reissue

Transaction

Action

Code

E Refund

Transaction

Action

Code

R System

Cancel

Transaction

Action

Codes

X And Y Refund

Cancel

Transaction

Action Code

Z Void

Transaction

Action

Codes

V And W

20.64/725 g

- 2012 MANUAL REQ RESP REQ RES

P RE

Q RESP RE

Q RESP RE

Q RESP REQ RES

P REQ RESP RE

Q RESP

Date of Birth 7 A/N C C C

T2.15

Element Description

Data element No. Char,

A, N, or A/N Issuance Display History

Display Exchange/

Reissue ...

Resolution 725g Req Res Req Res Req Res Req Res

Total Ticket/Document Amount 12 A/N M C M C

Total Ticket/Document Net Amount 12 A/N C C C C

Total Ticket/Document Sell Amount 12 A/N C C C C

T5

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 REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

... IN CONNECTION WITH

DOCUMENT TYPE 1A C C C C C

...T13

Data Element No.

Characters

A, N OR A/N Issuance

– Information

Transaction

Action Code

S AND I

(I applicable to A4A only ) Display

Transaction

Action Code

D History

Display

Transaction Action

Code

H Exchange/

Reissue

Transaction

Action Code

E

20.64/725 g

- REQ RESP REQ RESP REQ RESP REQ RESP

Tax/Fee/Charge Data at the Ticket

Coupon Level

– Begin:

Airport Code (Not Applicable) 5 A C C C

Applicable Amount (Not Applicable) 11 A/N C C C

Cabin 1 A/N C C C

Currency Type (Not Applicable) 4 A/N C C C

Equipment Type Code 3 A/N C C C

Journey Turnaround Airport/City

Code 5 A/N C C C

Passenger Date of Birth 6 N C C C

Reported Amount (Not Applicable) 11 A/N C C C

Segment Tax Airport Code (Not

Applicable) 6 A C C C

Tax/Fee/Charge Amount 12 A/N C C C

Tax/Fee/Charge Code 2 A/N C C C

Tax/Fee/Charge Data Coupon

Number 1 N C C C

Tax/Fee/Charge Data

Ticket/Document Number 14 A/N C C C

Unticketed Point Airport/City Code 5 A/N C C C

Unticketed Point Date and Local

Time of Arrival 11 A/N C C C

Unticketed Point Date and Local

Time of Departure 11 A/N C C C

Unticketed Point Departure

Equipment Code 3 A/N C C C

Tax/Fee/Charge Data at the Ticket

Coupon Level

– End:

Other 725g / 20.64 messages are not used by “Tax/Fee/Charge Data at the Ticket/Coupon

Level” and are not shown here for clarity.T12

Data

Element No.

Chara

cters

A, N

OR

A/N Issuance

– Information

Transaction

Action Code

S AND I

(I applicable

to A4A only ) Display

Transaction

Action Code

D History

Display

Transaction

Action Code

H Exchange/

Reissue

Transaction

Action Code

E Refund

Transaction

Action Code

R Refund

Cancel

Transaction

Action Code

Z Void

Transaction

Action Codes

V And W System

Cancel

Transaction

Action

Codes

X And Y System

Update

Transaction

Action Codes

U

20.64/725 g

- REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP RESP RESP REQ RESP REQ RESP REQ RESP

Previous

Coupon

Status

Indicator 1 A C

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 725h

ELECTRONIC MISCELLANEOUS DOCUMENT

— GROUND HANDLING

(amending)

PSC( 34 35 )725h Expiry: Indefinite

Type: B

RESOLVED that,

T2.6

**....** 6.2.1.6 The Ground Handle may provide the passenger with a duplicate EMD Receipt.

This document shall include, but not be limited

to, the following:

.... Ticket/Document Number(s) 5

....

....

5 Include conjunction ticket/document numbers.

Attachment ‘B’

ELECTRONIC MIS CELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX

– GROUND HANDLING MESSAGES

T2.9

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

REQ RESP REQ RESP REQ RESP REQ RESP

Billing Airline

Accounting Code (App.

725f) 4 A/N

T5

ELEMENT DESCRIPTION

Transaction NO CHAR.

A, N OR A/N DISPLAY AIRPORT CONTROL

REQUEST

– GROUD

HANDLING CHANGE OF STATUS SYSTEM UPDATE

Action code

- > D B C U

RESOLUTION 725h REQ RESP REQ RESP REQ RESP REQ RESP

... IN CONNECTION WITH

DOCUMENT TYPE 1A C C

...T13

Data Element No.

Characters

A, N OR

A/N Display

D Request Airport

Control

Ground Handling

B Change of

Status

C System

Update

U

20.66/725H

- 2012 MANUAL REQ RESP REQ RESP REQ RESP

RE

Q RES

P

Tax/Fee/Charge Data at the Ticket

Coupon Level

– Begin:

Airport Code (Not Applicable) 5 A

Applicable Amount (Not Applicable) 11 A/N

Cabin (Not Applicable) 1 A/N

Currency Type (Not Applicable) 4 A/N

Equipment Type Code (Not Applicable) 3 A/N

Journey Turnaround Airport/City Code (Not

Applicable) 5 A/N

Passenger Date of Birth (Not Applicable) 6 N

Reported Amount (Not Applicable) 11 A/N

Segment Tax Airport Code (Not Applicable) 6 A

Tax/Fee/Charge Amount (Not Applicable) 12 A/N

Tax/Fee/Charge Code (Not Applicable) 2 A/N

Tax/Fee/Charge Data Coupon Number

(Not Applicable) 1 N

Tax/Fee/Charge Data Ticket/Document

Number (Not Applicable) 14 A/N

Unticketed Point Airport/City Code (Not

Applicable) 5 A/N

Unticketed Point Date and Local Time of

Arrival (Not Applicable) 11 A/N

Unticketed Point Date and Local Time of

Departure (Not Applicable) 11 A/N

Unticketed Point Departure Equipment

Code (Not Applicable) 3 A/N

Tax/Fee/Charge Data at the Ticket

Coupon Level

– End:

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 728

CODE DESIGNATORS FOR PASSENGE R TICKET AND BAGGAGE CHECK

(amending)

PSC( 3 4 35 )728 Expiry: Indefinite

Type: B

T10

RESOLVED that:

In order to identify the fare and conditions of travel on passenger tickets and other traffic

documents, the codes shown below shall be used:

1. FARE BASIS CODE **(mandatory)**

This code gives information regarding type of fare, class entitlement, minimum and

maximum validity, reservations entitlement, seasonality, days of travel and advertising or

sales restrictions.

The fare basis code elements shall be combined in the same descending order as listed in

1.1 to 1.6.

1.1 Prime Code (mandatory)

First Class Category

P First Class Premium

F First Class

A First Class Discounted

Business Class Category

J Business Class Premium

C Business Class

D Business Class Discounted

I Business Class Discounted

Z Business Class Discounted

Premium Economy Class Category

W Premium Economy Class ( **effective from 31 October 2014**  ).

E Premium Economy Class Discounted ( **effective from 31 October 2014** ).Economy/Coach Class Category

W Economy/Coach Premium ( **effective from 31 October 2014** ).

S Economy/Coach

Y Economy/Coach

B Economy/Coach Discounted

H Economy/Coach Discounted

K Economy/Coach Discounted

L Economy/Coach Discounted

M Economy/Coach Discounted

N Economy/Coach Discounted

Q Economy/Coach Discounted

T Economy/Coach Discounted

V Economy/Coach Discounted

X Economy/Coach Discounted

......

7. FORM OF PAYMENT CODE **(mandatory)**

... T6

DP

– direct form of payment (Airlines Reporting Corporation).

EF

- Electronic Funds Transfer (For airline use only) payment was processed using an

online or mobile payment service provider or vendor, may be followed by any combination

of alpha numeric characters as required by internal accounting systems. Refundable only

by issuing airline. ( **The provisions of this paragraph shall become effective from 1**

**January 2015** ).

.... P2.2

Payment instruments. domestic usage only

Elo EL BSP Brazil domestic card

....

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 735d

INVOLUNTARY CHANGE OF CARRIER, ROUTING, CLASS OR TYPE OF FARE

(amending)

PSC( 34 35 )735d Expiry: Indefinite

Type: B

RESOLVED that,

..... T10

..... 1.4 ‘NORMAL FARES’ means a fare established in the Resolution 030/ 040/050/060 series

for business intermediate , first

, premium economy or economy class service and any other

fare denominated and publi shed as a normal fare (e.g. C2,F2,Y2 CIF, FIF, WIF,YIF ).

Children’s fares and infant's fares which are established as a percentage of the fares

referred to above are also considered to be normal fares. ( **This paragraph effective from** 

**31 October 2014** ).

.....

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 735e

PROCEDURE FOR INVOLUNTARY CHANGE OF ROUTING EN ROUTE

(amending)

PSC( 30 35 )735e Expiry: Indefinite

Type: B

T2.4

.....

Section 6 ISSUING AND HONOURING PROCEDURES

6.5 Procedures for the Exchange/Reissue of Electronic Tickets (optional)

6.5.2 The full details of the original electronic ticket coupon, including original issue and

issued in exchange for data shall be carried forward to the new ticket in accordance with

the provisions of Resolution 735d.

The original coupon data shall be carried forward to the new reissued ticket, as Reissued

Flown Flight Coupon Data with the Reissued Flown Involuntary Indicato r ‘D’ (Diversion en

route)

6.5.3 No exchange/reissue message shall be sent to the original vali dating carrier. The

original operating carrier shall report the original coupon as ‘flown’ to the original validating

carrier without including any involuntary indicator

.

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 736

VOLUNTARY CHANGES TO TICKETS AND MISCELLANEOUS DOCUMENTS

(amending)

PSC( 30 35 )736 Expiry: Indefinite

Type: B

RESOLVED that:

....

T8

8. OPTIONAL CHANGE PROCEDURES FOR ELECTRONIC MISCELLANEOUS

DOCUMENTS

8.1 WHOLLY UNUSED

The value of a wholly unused EMD may be used as full or partial payment, based on

applicable fee provisions, for a new EMD/ET irrespective of whether the original EMD was

issued with a coupon value or a fee calculation.

8.2 PARTIALLY U SED

8.2.1 PARTIALLY USED WITH COUPON VALUE

Where a change is requested on a partially used EMD issued with the coupon value

method, the value of remaining coupons may be used, based on applicable fee provisions,

towards the value for a new EMD/ET.

8.2.2 PARTIALLY USED WITH FEE CALCULATION

Option 1: Establishing the value of unused coupon(s)

Where a change is requested on a partially used EMD with the fee calculation method, the

unused value, based on applicable fee provisions of the EMD may be dete rmined by:

Step 1: Subtracting the total fee calculation of the coupon(s) flown from the total fee

calculation;

Step 2: Such value may be used towards a new EMD/ET;

Step 3: For EMDs, such value may be used for a fee calculation or a coupon value

method.

Example: Original Issue HEL 6X PAR 6X GVA EUR100.00ENDFlown HEL 6X PAR EUR60.00

Point of rerouting: PAR

Value for Exchange EUR40.00

New Routing PAR 6X ZRH EUR35.00 Refundable/residual balance EUR5.00

Option 2: Recalculation

Where a change is requested on a partially used EMD with the fee calculation method,

establish the fee calculation of the new EMD for the amended journey from origin to

destination. Compare the fee calculation of the old EMD with the fee calculation for the

new EMD to esta blish the difference if any. The fee calculation for the used portion(s)

must be carried forward to the new EMD.

Example:

Original Issue: HEL 6X PAR 6X GVA EUR100.00END

Point of rerouting: PAR

Recalculation: HEL 6X PAR 6X GVA 6X ROM EUR125.00END

Addit ional Collection: EUR25.00

**Secretary Note:** Renumber existing section 8 to section 9 and renumber any other

subsequent sections.

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014R E S O L U T I O N 7 4 0

FORM OF INTERLINE BAGGAGE TAG

(amending)

PSC( 32 35 )740 Expiry: Indefinite

Type: B

..... B9

1

. 2 Exper i men t a l B a g gag e T a g

I f a M e m b er desires to e x p e ri m en t w i t h a ba g g ag e t ag f or i n t er li n e

c a r r i ag e wh i c h d oe s no t m e e t a ll t h e r e qu i r em en t s o f t h i s R e s o lu t ion

, s u ch M e m ber s h a ll r e q ue st ap pr o v al f ro m t h e A 4 A B agg a g e

C o m m i t t e e /I A TA Ai r p or t S e r v i c e s C o m m i t t e e ( ASC ) B a g gag e W o r k i n g

G ro up (BW G ) v i a t h eir r e s pe c t i ve s e c re ta r i e s

. I f a pp ro v e d the M e m b er

m a y u se t h e exp er im en t a l ba g ga ge tag f or on e y e ar f r o m t h e d a te o f

c o mm en c e m en t o f t h e e x p er i m en t. T h e m e m b e r c o nd ucti n g t he

e xp er im en t, an d o t h er M e m be r s h a v in g car r i e d b a g g ag e w i t h t h e

e x p e ri m e n t a l t a g

, s h al l i n f o r m t h e J PBC A 4 A B a g ga ge C o m m i t t e e /I A TA

Ba g gag e Wo r k in g Gr ou p ( BW G ) o f t h eir e x p er ie nce w i t h s u ch t ag

. I n c ase

M e m b e r s re p o r t ne g a t i v e e x pe r i e nce w i t h t h e ex p e r im e n t al t a g

, t he JPBC

A 4 A B a g ga ge C o m m i t t ee / I ATA B agga ge Wo r k in g G ro up ( BW G ) s h a l l no t

g i v e a ppro v a l to e x t en d t h e e xpe r im en tal p er io d w i t hou t t h e c on s en t o f t h e

M e m be rs t h a t r ep o r t e d t h e nega t i ve e x p e r i en c e

.

......

3. 2 E x p e d i t e ( R U S H) B aggag e T ag s a n d E x p e d it e ( R U S H )

S t i ck e r s

T h e s e s h a ll be u s ed when f orw a r di n g mi s han d l ed ba g gage in ac c o rda n c e w ith

R e s o l uti o n 7 43 (A4A 30.70)

. Exc e p t i on a l l y

, w he r e pe rm i t t e d b y c i v i l a v i a t i o n

r e gu la t o rs, w he n a c a r r ie r i s f o r w a r di n g f o r a s i ng l e f l i gh t s e g m e n t o n t hei r o w n

m e t a l a n d a l l bag s a re v e r i f i e d f o r t h e f l i gh t b y s c an n i n g t h e b a g ga g e li c en s e

p l a t e

, t he n a RU SH t a g n ee d n o t b e a f f i x e d

. A F W D m e ss a g e s h a l l b e s e n t t o t h e

L L o f f i ce o f t h e f i n a l s t a t i o n.....

4. TYP E S O F BA G T A G S

Sp e c i f i c a ti on s w h i c h a p pl y t o a l l o f t h e f o l lo wi n g ty pe s o f ba g ga ge ta g s ( e x c ep t

s p e c i al p u rpo se t a g s ) are g i ven i n s e c t i on 5

. Un i q u e s pe c i f i c a t i o n s an d il lu s t ra ti on s

f o r t h e fo l l o w i ng t y pe s o f b a gg a g e t a g s a r e c on ta ine d in t h e a t t a c h m e n t s in d i c a ted

b e lo w.

4.1 C hecked B a gg a ge T a gs:

d e m a n d p r in t e d ‘ H ’

s t r i n g t y p e ‘ E’

s e lf

- s e a l t yp e f o r hand le ‘ F ’

s e lf

- s e a l f o r b o x e s / ca r t o n s ‘ F ’

p o i n t to p o in t ‘ G ’

li m i t e d r e l ea s e R F I D R P 1 7 40 c ‘ I’

H o me Pr i n t e d b a gg a g e Ta g ‘ V ’

Permanent Baggage Tag ‘W’

.....

5

. 4 Id e ntifi c a t ion/ C l a i m Po r t io n

A ll b a g gage t a g s

, as n o t e d in 4

. 1

, s h all have a re m o v able i den t i f i c a t i on / claim

por t i o n

, or o p t i onal l y ei t he r a p r in t ed or el e c t ronic B a g gage Recei p t ( s ee R e s o l u t i on

752 f or d e t ails o f t he e l e ct r o nic b agg ag e claim r e c e ip t ) and P a ss en ger I d e n t i f i c a t ion

c a rd

, w h i ch when c o m p l ete d

, s hall be r e moved and a f f i x e d t o t he pa s s e ngers t i c k e t

so t ha t a l l in f o r m a t i on on b o t h t he t ic k e t and t he id e n t i f i c a t i o n / c l a im por t i on

r e m ain v i s ibl e

. T h e i den t i f i c a t i on / c l a im portio n

, or op t io n al l y the B a g g a g e R ec e i p t

a nd P a s s e ng er Identification c a r d co n t a ins t he f ol l owin g :A t t a c h m e nt ‘E’

**Editor’s note** : “XB” has been deleted in the examples for the barcodesA t t a c h m e nt ‘F’

**Editor’s note** : “XB” has been deleted in the examples for the barcodesA t t a c h m e nt ‘F’

**Editor’s note** : “XB” has been deleted in the examples for the barcodesA t t a c h m e nt ‘H’A t t a c h m e nt ‘H’

**Editor’s note** : “XB” has been deleted in the examples for the barcodesA t t a c h m e nt ‘H’

**Editor’s note** : “XB” has been deleted in the examples for the barcodesA t t a c h m e nt ‘I’A t t a c h m e nt ‘J’A t t a c h m e nt ‘K’

E X PED I T E T A G

- DE M A N D PR I N T ED

I n ad d it i o n to t h e C o m m o n S p e c i f i c a t i o n s

, t h e f o ll ow i n g a l s o ap p ly t o t h e E xpe d ite T a g :

1. D e m an d p r i n t e d e x p e d ite t a g s m a y o p t i on a l ly ha v e b l a ck

, r a t he r t ha n r e d

, h a t c h i n g a l on g t h e

edg e o f t h e t a g.

E X AM P L E S O F D E MAND P R I N TE D E X PE D IT E BA GG A G E T A G S

**Editor’s note** : “XB” has been deleted in the examples for the barcodesA t t a c h m e nt ‘L1’A t t a c h m e nt ‘L1’A t t a c h m e nt ‘R’A t t a c h m e nt ‘V’

H O M E P R I N T ED B A G G A G E T A GA t t a c h m e nt ‘W’

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 745

DANGEROUS GOODS IN PASSENGERS BAGGAGE

( amending )

B10

PSC( 32 35 )745 Expiry: Indefinite

Type: B

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 ca rried 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 must develop and publish for passenger handling staff 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 must address circumstances where due to the quantity

of carry

- on baggage or due to aircraft size limitations passenger carry

- on baggage

canno t be accommodated in the cabin.

PASSENGER AWARENESS

— DANGEROUS GOODS IN BAGGAGE

2.1 To place special emphasis on passenger awareness of dangerous goods in

baggage, 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 pictorial

form but should must 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 restricti ons on dangerous goods in baggage

.2.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 numb er at each of the places at an airport where

o tickets are issued,

o passengers checked 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

2.3 Members should have information 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 info rmation.

2.4 When provision is made for the check

- in process to be completed remotely (e.g. via

the Internet), Members should must ensure that information on the types of dangerous

goods which a passenger is forbidden to transport aboard an aircraft is pro vided to

passengers. Information may be in text or pictorial form but should must be such that 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 dan gerous goods in

baggage.

2.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 must ensure that information on the types of

dangerous goods which a passenger is forbidden to transport aboard an aircraft is

provided to passengers. Information should be in pictorial form and should must 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:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 752

E LECT R O N I C B AG G A GE C LAI M R E C EI PT

(new)

PSC( 35 ) 752 Expiry: Indefinite

Type: B

RESOLVED that,

B6

T h e pu r po s e o f a n e l e c tr on i c b a gg ag e c l a i m r e c e ip t i s to p r o v id e e s s e n t i a l i n f o r m a t io n t o

s t a f f t r a c i n g a b a g wh e n a b a g i s m i s ha n dl e d a n d f a i l s to a r r i v e w i t h t h e pa ss e n g e r a t t h e i r

d e st i n a t i o n

.

A i r l i n e s s h a l l u s e a n el e ctr o n i c b a g ga g e c l a i m r e c e ip t w h e n a p ape r c l a i m r e c e i p t i s n o t

b ei n g i s s ue d

. Th e r e c e ip t s ha l l b e a v a i l ab l e to t h e p a ss e ng e r a s a c o n s e q ue n c e o f t h e

a i r l i n e t a k in g c u s t od y o f t h e ba g

.

In o r de r t o i s s u e a n e l e c t r o n i c b a g ga g e c l a i m r e c e ip t

, ai r l in e s m u s t ha v e a v al i d el e ctr o ni c

m e a n s o f c o mm u n i c a t i o n w i th t h e p a ss e ng e r, s u ch a s a n e

- m a i l a dd r e ss o r t el e ph o n e

n u m be r. A l t e r n a t i v e l y t h e p a s s e nge r c a n a cc e s s a n ai r li n e w e b s i t e to r e tr i e ve t h e

de t a i l s o f t h e b a g s ho u l d t h e n ee d a r i s e

. T h i s m e t ho d m a y b e u s e f u l wh e n t h e

p a ss e nge r ha s p u r c ha s e d a t i c k e t t h r o ug h a tr a v e l a g e n t a n d t h e ai r l i n e h a s n o c o n t a ct

d e t a i l s f o r t h e p a s s en ge r.

Mi n i

m u m El ec t r on i c B a gg a g e C l a im R ec e i p t D a ta

P a s s en g e r N a me

D e s t i n a t i o n a n d F l i gh t N u m be r V i a an d Fl i gh t Nu m be r

... V i a an d Fl i gh t Nu m be r O r i g i n F li g h t Nu m b e r D a te

N u m b e r o f B a g s an d b a g ga g e n u m be rs P N R Re f e r e n c e**U se**  **o f**  **Free T**  **e x**  **t**

Airlines may use free text in the messages to make the baggage claim receipt more

human readable, such as:

Dear Mr. Houman Goudazi,

This is your baggage receipt for your journey to from GVA to PHX on UA123 via EWR

(UA005) and LHR (BA732) today, 07th January 2013. This receipt is for 3 bags,

3016123456, 3016123457, 3016123458.

If you have any problems receiving your baggage in PHX, please visit

www.united.com/baggage to raise a claim. Your ticket reference today is SD3E4

Alternatively our customer services staff will be happy to help you.

OR

Mr. Goudarzi,

This is your receipt for bags 3016123456, 3016123457, 3016123458 from GVA to PHX on

UA123 via EWR (UA005), LHR (BA732), ticket ref SD3E4

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 753

B AG G A GE TRACKING

(new)

PSC( 35 ) 753 Expiry: Indefinite

Type: B

RESOLVED that,

B7

For effect 1 June 2018,

I AT A m e m be r s s ha l l m a i nta i n an a c c u r a te i n v ent o r y of b a ggage by m on i t or i ng t he a c qu isi t i on

a n d de l iv e r y of baggage.

P urpo s e

A c c u r ate baggage i n v e n tor i es w ill :

• pre v ent and redu c e m i s han d li ng b y deter m i n in g c u s tody o f e v e ry bag dur i ng

d i f fere n t pha s es o f baggage c h a i n,

• i n c rea s e pa s s eng e r s a t i s fa c t i on, a s m i s ha n d li ng i s redu c e d

,

• redu c e t he p o s s i b ili t y of bag g age fraud by c l o s i ng the b aggage j ourne y

,

• ena b l e e x c ept i ons to be de t e c ted w here baggage i s de liv ered t o a par t y

, but not

p ro c e s s ed fu r t he r

,

• s peed up re c on cil i a t i o n a nd f l i ght read i ne s s f o r d e part i ng f l i g h t s

,

• he l p m ea s u r i ng c o m p li an c e t o S L A s

,

• P ro vi de e v i den c e to an a u t o m a t i c i nt e r li ne pr o ra t i on pro c e s s

.

Me m b e r O b l i ga t i ons Me m b e rs s ha l l be ab l e t o:

• D e mo nst r ate D elive r y

, o f baggage w hen c u s to d y c hange s ;

• D e mo nst r ate a cquisiti o n

, o f baggage w hen c u s tody c h ange s ;

• Pr ovide an inve n t or y o f ba g s

, upon dep a r t u re o f a f li g h t.

• B e capa b l e o f e xcha n gi n g these events w i t h oth e r a i r li n es as

need e d T he m i n i m u m s e t o f c u s to d y c ha n ges s ha l l be:

D e l i v e r y of the bag to t he pa s s en g er (de liv ery i s b y t he hand l er, a c qu i s i t i on i s b y the

arr iv a l s fa cili t y

, s u c h as an arr iv a l s be l t, the pa ss eng e r ’ s ho m e, et c .)D e l i v e r y of t he bag t o t he a i r c r a f t (de l i v e r y i s by the hand l er, a c qu isi t i on i s b y the f l i ght)

D e l i v e r y o f t he bag to a n a i r li ne s y s t e m ( d e liv e r y i s b y the hand l er, a c q u i s i t i on i s b y the

a i r li ne s y s t e m )

R e f e ren c es

I AT A R e s o l ut i ons M anua l : R P 1800 and R P 1740

A4A TPM RP30.49 and Resolution 30.35

Filing Period: Effective Date:

2 3 December 2013 1 June 2018

1 7 February 2014RESOLUTION 780

FORM OF INTERLINE TRAFFIC AGREEMENT

– PASSENGER

( amending )

PSC ( 34 35 )780 Expiry: Indefinite

Type: B

.....

Attachment ‘A’

P10.2

... Article 2

- Issuance of Tickets and MCOs

...

2.2 Acceptance

... 2.2.7 Whereas certain parties to this agreement issue Electronic Miscellaneous

Documents as defined in IATA Resolution 725f and Resolution 725g, any other party

which concurs with the Issuing Airline may accept such electronic miscellaneous

documents. Any party which issues electronic miscellaneous documents shall notify the

IATA Head, Interline & Intermodal Policy. Any other party may agree to accept such

electronic mi scellaneous documents, and shall notify the IATA Head, Interline &

Intermodal Policy of which other party's electronic miscellaneous documents it will accept.

The IATA Head, Interline & Intermodal Policy shall publish in the MITA Manual a list of the

parti es which issue electronic miscellaneous documents, and the other parties which have

agreed to accept each other party's electronic miscellaneous documents

2.2. 7 8 Whereas certain parties to this agreement issue paper miscellaneous documents

and excess bag gage tickets as defined in IATA Resolutions 722e, 725, 725a, 725b, 725c,

725d, 726, 726a, 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 bagg age tickets. However, the refusing party will provide at least 12 months ’

notice to interline partners. The refusing party shall notify the IATA Head, Interline &

Intermodal Policy of which other party's paper miscellaneous documents and excess

baggage tic kets it refuses to accept, any specific exclusions to its policy and will provide

an effective date. The IATA Head, Passenger shall publish in the MITA Manual a list of

such refusals and the corresponding effective dates.P10.1

.....

5.4.3 When it is not established which airline is responsible, each party Carrying Airline

that participated in the carriage of the passenger shall share the claim settlement on the

basis of the non

- stop distance (statute miles) between the first and last ticketed points of

each carrier, as shown in the IATA Ticketed Point Mileage Manual flown mileage between

all ticketed points of each carrying airline . Baggage transfer records....

P10

.....

10.2.5 The concurrence procedures outlined above may be expedite d in the following

manner. The earlier party shall notify the later party of its intent to concur on an expedited

basis, by teletype message email addressed to mita@iata.org with a copy to the IATA

Head, Interline & Intermodal Policy. If no objection is re ceived from the later party the

concurrence shall be deemed to be effective ten (10) days after the dispatch of the

teletype message email addressed to mita@iata.org . The IATA Head, Interline &

Intermodal Policy will circulate a list of expedited concurren ces in the regular transmittals.

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RESOLUTION 780e

IATA INTERLINE TRAFFIC PARTICPATION AGREEMENT

— PASSENGER

(amending)

PSC( 34 35 )780 Expiry: Indefinite

Type: B

RESOLVED that,

..... P10.2

Article 2

- Issuance of Tickets and MCOs

... 2.2 Acceptance

...

2.2.7 Whereas certain Issuing Airlines party to this agreement issue Electronic

Miscellaneous Documents as defined in IATA Resolution 725f and Resolution 725g, any

Participating Airline which has agreed to accept the Issuing Airline's miscellaneous

documents, may accept such electronic miscellaneous documents. Any Issuing Airline

which issues electronic miscellaneous documents shall notify the IA TA Head, Interline &

Intermodal Policy. Any Participating Airline may agree to accept such electronic

miscellaneous documents, and shall notify the IATA Head, Interline & Intermodal Policy of

which Issuing Airline's electronic miscellaneous documents it wi ll accept. The IATA Head,

Interline & Intermodal Policy shall publish in the MITA Manual a list of the Issuing Airlines

which issue electronic miscellaneous documents, and the Participating Airlines which have

agreed to accept the Issuing Airline's electro nic miscellaneous documents.

2.2.8 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, 726e, 726f, 731a, 742,742a, 742c, 742d and 742e, any Participating

party which concurs with the Issuing Airline may refuse such paper miscellaneous

documents and excess baggage tickets. However, the refusing party will provide at least

12 months’ notice to interline partners. The refusing part y shall notify the IATA Head,

Interline & Intermodal Policy of which other party's paper miscellaneous documents and

excess baggage tickets it refuses to accept, any specific exclusions to its policy and will

provide an effective date. The IATA Head, Inter line & Intermodal Policy shall publish in the

MITA Manual a list of such refusals and the corresponding effective dates.

.....P10.1

5.4.3 When it is not established which airline is responsible, each Carrying Airline that participated

in the carriage of the passenger shall share the claim settlement on the basis of the non

- stop

distance (statute miles) between the first and last ticketed p oints of each Carrying Airline, as

shown in the IATA Ticketed Point Mileage Manual flown mileage between all ticketed points of

each carrying airline . Baggage transfer records....

P10

.....

10.2.6 The concurrence procedures outlined above may be expedited in the following

manner. An Issuing Airline shall notify a Participating Airline of its intent to concur on an

expedited basis, by teletype message email addressed to mita@iata.org with a copy to the

IATA Head, Interline & Intermodal Policy. If no object ion is received from the Participating

Airline, the concurrence shall be deemed to be effective ten (10) days after the dispatch of

the teletype message email addressed to mita@iata.org . The IATA Head, Interline &

Intermodal Policy will circulate a list of expedited concurrences in the regular transmittals.

Filing Period: Effective Date:

2 3 December 2013 1 June 2014

1 7 February 2014RECOMMENDED PRACTICE 1008

GLOSSARY OF COMMONLY USED AIR PASSENGER TERMS

(amending)

PSC( 32 35 )1008

T10

.....

1. TERMS OF GENERAL APPLICATION

.....

“FARE, PREMIUM ECONOMY”, means the fare established for a premium economy

class service.

“FARE, NORMAL” means a fare established in the Resolution 030/ 040/050/060

series for business intermediate , first

, premium economy or economy class service

and any other fare denominated and publis hed as a normal fare (e.g. C2,F2,Y2 CIF,

FIF, WIF,YIF ). Children's fares and infants' fares which are established as a

percentage of the fares referred to above are also considered to be normal fares.

“ BUSINESS INTERMEDIATE CLASS” means a class of service with seating

standards which may be superior to those provided on premium economy /tourist

economy class but less liberal than standards provided in first class.

“PREMIUM ECONOMY CLASS” means a class of service with seating standards

which may be superior to those provided on economy/tourist class but less liberal

than standards provided in business class

.

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1706 c

COMMON USE SELF SERVICE

(amending)

PSC( 3 3 35 )1706 c

B11

.....

3.8 Platform Provider Operator

This is the entity that is responsible for ongoing provision and management of the

Platform.

.....

3.10 Relationship Among Entities Involved in the CUSS System

**Secretary note** : in the figure, replace the box “Platform Provider ” by “Platform

Operator ” above the black box called “Service Provider”.

3.11 Selection Interface Screen

This is the initial screen a customer will interact with prior to selecting an airline

application. This will be provided by the Platform Provider Operator

.

.....

5. KIOSK PLATFORM/CUSS PRODUCT FUNCTIONALITY

The Kiosk Platform comprises, at minimum, the Hard ware specified in Section 11.1

titled “Minimum Kiosk Components”.

The CUSS product functionality shall be bilaterally agreed upon between the

individual airline(s) and the Platform Provider Operator and must adhere to the

Certification process outlined in the “Certification Document”. This is published in the

“CUSS Manual” separately from this Recommended Practice.

The Kiosk is envisaged to support a comprehensive range of airline processes and

servi ces.

The support of a specific process and services for any airline is dependent on the

software provided by th e airline Application Provider.

Initial focus of the product will be on passenger check

- in.

Devices within a Kiosk shall only be used by applicat ions initiated and operated within

th e Kiosk or diagnostic software.

All physical components shall be equally accessible to all participating airlines

according to bilateral agreements between airlines and Platform Providers Operators

.5.1 Data Securit y

This Recommend Practice and the CUSS Technical Specification recognize and

acknowledge that the CUSS standard should facilitate, and not prevent, the PCI Data

Security Standard compliance of the Kiosk provider as well as of the Application

Providers. Jus t a few of the ways that can prevent compliance follow:

1. Storage of magnetic stripe data and/or equivalent data on the chip in the

customer's network after authorization;

2. Applications that require customers to disable other features required by the

PC I Data Security Standard, like anti

- virus software or firewalls, in order to get

the payment application to work properly; and

3. Vendors' use of unsecured methods to connect to the application to p rovide

support to the customer.

Secure kiosk enclosures and components, when implemented in a PCI DSS

compliant environment, will minimize the potential for security breaches leading to

compromises of full magnetic stripe data, card verification codes and values (CAV2,

CID, CVC2, CVV2), PINs and PIN blocks, and the damaging fraud resulting from

these breaches.

See the References paragraph f or more information on PCI

- DSS.

Operating systems and third party applications such as java, antivirus and Internet

browsers, in support of common use platforms and airline ap plications, are necessary

to airport operations. Ensuring that these systems/applications are supported and

secured versions is a vital part of a comprehensive security plan. It is recommended

that proper patch management is maintained for all systems/appl ications and that

versions no longer supported are upgraded or replaced. Failure to maintain

compliance with the technical specification and industry best practices could have

severe consequences including, but not limited to, extended unavailability of ki osks.

Proper patch management is a requirement to obtain a nd maintain PCI

- DSS

compliance.

.....

6. PASSENGER EXPERIENCE MANAGEMENT GROUP

A Passenger Experience Management Group (refer to Resolution 706 [A4A 30.200]

comprised of airlines will be responsible for managing the certification process and

amending CUSS standards as published separately from this Recommended

Practice , e.g. Technical Specifications published in the CUSS Manual

.

.....9. SERVICE LEVEL AGREEMENTS (SLAs) AND RESPONSIBILITIES

This sect ion addresses various aspects of the Service Level Agreement (SLA)

document where the Service Levels to be provided by the Platform Provider Operator

of CUSS and the Service Levels provided by the Application Provider are mutually

agreed. The SLA will also include change management procedures. As a guideline, a

sample SLA template is shown in the “CUSS Manual”.

10 9 .1 Platform Provider’s Operator's Responsibility

The Platform Provider Operator will, as defined in the SLA, ensure that:

the CUSS Kiosk is operational and serviceable during the specified operational

hours,

the CUSS Platform is functioning and certified according to CUSS standards,

software levels and version control of the Platform are maintained at that site,

statistical and management information is available,

they notify the Application Provider of faults that cannot be resolved,

they have the ability to turn off an application if it is deemed to be causing

other applications and/or the CUSS Kiosks to malfunction. If th is is the case

they will endeavor to inform the Application Provider in advance,

Kiosk locations are locally and mutually agreed.

The Platform Provider Operator will also demonstrate that its Kiosk Enclosure and

Kiosk Platform comply with any applicable re gulations or standards that apply to the

site where the kiosk is deployed, including relevant Access, Data Privacy, and Data

Security standards.

In addition, the Provider Operator must deploy a platform that complies with and

implements the CUSS FOID Addendum as described and by the date set in

paragraph 5.2.

9.2 Application Provider's Responsibility

The Application Provider is responsible for the application code, which must follo w and pass the Certification process.

If the Application Provider decides to use a dedicated Application Server, either at the

CUSS site or a location that is under the control of the Application Provider, then that

Application Provider is responsible for the maintenance and the upkeep of the Server.

The Application Provider is responsible for any communication lines to and from the

Application Provider's mainframe or Server location.

The Application Provider must provide the correct protocol and interfaces to allow

connection at the CUSS site as mutually and bilaterally agreed between the Platform

Provider Operator and the Application Provider.

.....9.4 Management Information and Availability Figures

The Platform Provider Operator should be able to supply all Application Providers the

Availability figures and access to the management tool used for real time status of the

CUSS installation.

9.5 Additional Responsibilities

The Platform Provider Operator and Application may have addit ional local or site

responsibilities not listed here.

.....

13. CUSS MANUAL DOCUMENTATION

IATA shall produce, update, and make available the CUSS Manual in electronic

format which shall set forth, among other things, CUSS standards and Technical

Specifications. As a condition to certification, Application and Platform Providers,

shall be required to maintain a current subscription to the CUSS Manual. To enable it

to defray the costs incurred in developing and maintaining the CUSS Manual, IATA

shal l establish an annual subscription fee for the CUSS Manual. Access to the CUSS

Manual, and the fee to be charged, will be non

- discriminatory, i.e., all interested

parties, whether or not members of IATA, will be afforded access to the CUSS

Manual on the sa me terms, and will pay an equal fee for such access.

The CUSS documentation can be found on the IATA PEMG Extranet. It is part of the

offer for IATA Strategic Partners in the area of Common Use

.

14. GLOSSARY OF TERMS

AEA PECTAB

— Parametric table as specifie d by the latest edition of the Association

of European Airline (AEA) joint technical specifications. A parametric table defines

the print and magnetic strip locations for the IATA ATB documents (or other

documents in ATB format).

APPLICATION PROVIDER

— See p aragraph 3 “Definitions”

APPLICATION SUPPLIER

— See paragraph 3 “Definitions”

ARCHITECTURE

— See paragraph 3 “Definitions”

AVAILABILITY

— The percentage of time, during kiosk hours of operation, where a

kiosk is able to fulfill its functionality, and is availabl e for operational use. There are

some outages which affect availability of the CUSS kiosk that the Service Provider

will not have control over. These outages will not be classed as an operational outage

which will be penalized against the Service Provider.

COMMON ENVIRONMENT

— e.g. an airport as defined in IATA RP 1797.

CUSS APPLICATION

— See paragraph 3 “Definitions”

PASSENGER EXPERIENCE MANAGEMENT GROUP

— A Passenger Experience

Management Group (PEMG) comprised of airlines will be responsible for managing

the certification process and amending CUSS standards.

GPP

— General Purpose PrinterKIOSK, KIOSK ENCLOSURE

— The common term used to describe the repository of

the hardware. See paragraph 3 “Definitions”.

OPEN ARCHITECTURE

— Means that it is possible to use any Hardware or software

that conforms to CUSS standards.

PLATFORM

— Comprises common Hardware, software and networking infrastructure

required to run the CUSS Applications.

PLATFORM PROVIDER OPERATOR

— See paragraph 3 “Definitions”.

PLATFORM SUPPLIER (S)

— See paragraph 3 “Definitions”.

PROPRIETARY DATA

— Data that originates from an Application Provider.

SERVICE PROVIDER (S)

— See paragraph 3 “Definitions”

SELECTION INTERFACE SCREEN

— See paragraph 3 “Definitions”

SERVICE LEVEL AGREEMENT (SLA)

— A document where the se rvice levels to be

provided by the Platform Provider Operator of CUSS and the service levels provided

by the Application Provider are mutually agreed. See paragraph 9 “SLAs”.

.....

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1707a

DATA FIELD DICTIONARY FOR DCS PASSENGER MESSAGES

(amending)

PSC( 34 35 )1707a

B1 3.1

.....

RECOMMENDED that:

Members who transmit Departure Control (DCS) Passenger Messages shall apply the following

definitions and formats for the automatic creation, transmission, receipt and interpretation of this group

of messages.

This Data Field Dictionary for DCS Passenger Messages is the primary reference for the Data Element

Directory for D CS Passenger Messages found in Recommended Practice 1707b. The Data Field

Dictionary and the Data Element Directory are the primary references for the description, use,

interpretation and guide while working with DCS Passenger Messages as described in Reco mmended

Practices 1708

– 1719 d e

.

**Note:** DCS Baggage Messages are documented in Recommended Practice 1745.

Data Field Name Example Format/Reference

account number: frequent flyer identification 123ABC789 m[2..25]

...

SSR/OSI /AUX code SFML a[3..4]

(refer to AIRIMP

Codes and

Abbreviations)

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1707b

DATA ELEMENT DIRECTORY FOR DCS PASSENGER MESSAGES

(amending)

PSC( 34 35 )1707b

B13.2B13.1

.....

2.9.3 Block Seats Indicator

When inventory is booked in RES for special usage, such as for extra cabin baggage (CBBG) or

stretcher (STCR), the SSR/OSI /AUX codes are shown in .R/ elements with the individual name of

each applicable passenger on the PNL/ADL. The seats blocked for the special usage are shown on

the PNL/ADL with a special form of the Name Element, using ZZ as the surname in alphabetical

sequenc e. The “given name” field can show free text or an SSR/OSI /AUX code to show the special

usage. The Passenger name comes across on the PNL/ADL with a group identifier as

1JONES/PETER

- C2 followed by a .R/ element for the service item (CBBG) and the number of seat (s)

blocked appears with the same group identifier as 1ZZ/CBBG

- C2 under the relevant Totals by

Destination element. This special form of the Name Element is used only to show the number of seats

blocked and appears only on the PNL/ADL, as bilaterally agreed.

...

2.23 DOWNLINE DESTINATION AND RECAP ELEMENT

This element is used to show a downline destination and a numeric summary of special services for a

DCS message, such as PSM.

Construction Example Data Field Name

...

2.23.8 total number of SSR/OSI /AUX services

required for this destination 12 number/one

- to

- three

2.23.9 SSR/OSI /AUX count header SSR SSR

...

2.24 SSR/OSI /AUX CODES AND COUNTS ELEMENT

This element lists the SSR/OSI /AUX codes that apply to a message. Each code is followed by the counts

of the services for passengers, by compartment, in descending order. The counts are zero

- filled.

Construction Example Data Field Name

2.24.1 AUX, SSR or OSI code WCHR SSR/ OSI /AUX code

2.24.2 space (only if a three character OSI code was

entered) → information separator

2.24.3 space → information separator

2.24.4 number of SSR or OSI or AUX services applicable

for this compartment 002 number/thre e

...3.24 .R/ REMARKS ELEMENT

Construction Example Data Field Name

3.24.1 element ID for Remarks Element .R/ element ID

3.24.2 applicable SSR

, or OSI or AUX code SFML SSR/OSI /AUX code or bilateral

(number, when present, may precede OSI code) 1VIP agreed code

(Bilateral agreed code) ETLP

...

3.39 SSR/OSI /AUX SERVICES ELEMENT

This element lists the SSR/OSI /AUX code(s) that apply to a passenger.

Construction Example Data Field Name

3.39.1 space → information separator

3.39.2 SSR

, or OSI or AUX code WCHR SSR/OSI /AUX code

3.39.3 space (if free text follows) → information separator

3.39.4 free text BROKEN LEG free flow text

...

3.40.1 API DOCS Element

This element lists Passenger primary travel documents. Where the components of a DOCS element

are not provided, an oblique (/) is inserted to indicate an element is missing. This is not required when

no further components are provided. The Passenger Identification Element may follow the final

eleme nt entered.

...

Construction Example Data Field Name

3.40.1.1 element ID for Remarks Element .R/ element ID

3.40.1.2 SSR code DOCS SSR/OSI /AUX code

...

3.40.2 API DOCO Element

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. The Passenger Identification Element

may follow the final element entered.

Constr uction Example Data Field Name

3.40.2.1 element ID .R/ element ID

3.40.2.2 SSR code DOCO SSR/OSI /AUX code

...

3.40.3 API DOCA Element

This element lists Passenger address information. Where the components of a DOCA element are not

provided, an oblique (/) is inserted to indicate an element is missing. This is not required when no

further components are provided. The Passenger Identification Element may follow the final element

entered.

Construction Example Data Field Name

3. 40.3.1 element ID .R/ element ID

3.40.3.2 SSR code DOCA SSR/OSI /AUX code

...T10

.....

Section 4

— Implementation Guidelines

......

4.3 The construction rules for DCS messages say to include compartments or fare

classes (RBD) in “descending order”. This means in “descending commercial value”,

best

- to

- worst, such as first class, then business class, then premium economy class,

then economy class. The concept of “descending order” does NOT relate to

alphabetical order or the physical seating position on the aircraft.

......

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1708

PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS LIST (ADL)

(amending)

PSC( 34 35 )1708

B13.1

.....

2.6.3 CHG (CHANGE) ELEMENT

2.6.3.5.1 Delete an SSR/OSI /AUX element:

**Original entries on the PNL:** CHG entry on ADL:

**PNR with a special meal: Delete the special meal:** 

1FOX/ARTHURMR .R/VGML CHG

1FOX/ARTHURMR

2.6.3.5.2 Add an SSR/OSI /AUX element in the PNR, and show all of the current elements on the CHG entry:

Original entries on the PNL: CHG entry on ADL:

**PNR with a wheelchair and a special meal for Add a special meal for Mr. Bainge:** 

**party of 2:**

1BAINGE/DAVIDMR

- D2 .R/WCHR CHG

1TRANE/RONMR

- D2 .R/VGML 1BAINGE/DAVIDMR

- D2 .R/WCHR .R/SFML

...

2.12 REMARKS ELEMENT

2.12.1 This element is conditional.

2.12.2 It is used when a passenger has one or more SSR/OSI /AUX elements within a PNR.

Note: the AUX element code SVC (per AIRIMP) is the only AUX element that can be

included in DCS messages

. 2.12.3 This element conveys supplementary infor mation from reservations control to the boarding airport's

Departure Control System. In general, it contains information that is held in the PNR of one or more

passengers in the SSR

, or OSI or AUX elements of the PNR. Where a Remarks Element is derived from a

PNR for a party/group it shall be shown against the individual name of each applicable passenger in the

party/group to whom it applies. Remarks Elements are entered after any Inbound and Onwa rd Connection

Elements.

Example of an SSR element on a PNL/ADL as a .R/ Element:

.R/SPML AI HK1 DESIRES MIDNIGHT SNACK

- 1WONG/JASMINEMS

• Note that the .R/ element for an SSR has the same format on PNL/ADL for the RES/AIRIMP automated

and non

- automated form at. ( See AIRIMP 2.12.6)

• Note that some Remarks Elements (.R/) have unique or complex requirements for their layout. Those

Remarks Elements are shown independently in Section 2.12.6 below, where specific rules and examples

are shown.

• For general construction rules, see RP 1707b, Remarks Element.

• The Remarks Element uses the standard, authorized IATA AIRIMP codes for SSR and OSI AUX elements.

The codes that are acceptable for use on the PNL/ADL are listed below in this section.

. . .

• All of the app licable SSR and OSI or AUX elements from a PNR can be added for a name entry on a

PNL/ADL. A name entry on a PNL/ADL has no limit for the number of Remarks Elements.

• Passenger Identification appears on Remarks Elements according to the rules stated in RP 1 707b, Section

3.37, Passenger Identification (ID).

...2.12.6.2 Remarks Element for Frequent Traveler Information

2.12.6.2(a) The Remarks Element for frequent traveler information uses the AIRIMP standard codes for

frequent traveler, such as FQTV, FQTR, FQTU, and FQTS. However FQTU should be used only

for upgrade to frequent flyers whereas other upgrades should use UPGR.

2.12.6.2(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b )

element ID .R/ element ID

SSR frequent traveler code FQTV SSR/OSI /AUX code

2.12.6.3 Remarks Element for Passenger Provided Contact Information

2.12.6.3(a) The Remarks Element for passenger contact information uses the IATA AIRIMP standard code for

passenger provided contact: PCTC.

2.12.6.3(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for psgr provided contact PCTC SSR/OSI /AUX code

2.12.6.4 Re marks Element for Infant Information

2.12.6.4(a) The Remarks Element for infant information uses the IATA AIRIMP standard code SSR INFT for

infant. The SSR may show the infant as not occupying a seat (sitting on an adult's lap) or occupying a seat.

2.12.6. 4(b) Construction rules for SSR INFT Not Occupying a Seat

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for infant INFT SSR/OSI /AUX code

2.12.6.4(c) Construction rules for SSR INFT Occupying a Seat

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for infant INFT SSR/OSI /AUX code

2.12.6.5 Remarks Element for Child Information

Child information is sent using the SSR CHLD element.

The SSR CHLD is constructed as follows:

Field Example Data Field Name

element ID .R/ element ID

child element identifier CHLD SSR/OSI /AUX code

2.12.6.6 Remarks Element for Ticket Number Information

2.12.6.6(a) The Remarks Element for ticket number identification information uses the IATA AIRIMP

standard codes for ticketing, such as TKNE or TKNA.

2.12.6.6(b) Construction rulesField Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

ticket element identifier TKNE SSR/OSI /AUX code

...

2.12.8 Table of OSI /AUX Codes and Miscellaneous Abbreviations

The following OSI /AUX codes and miscellaneous abbreviations from the IATA AIRIMP or bilaterally agreed

codes are used in .R/ Remarks Elements.

They are shown in the table in alphabetical order by code.

Code Description

DIPL Diplomatic courier

. . . SVC Additional Serv ices

— Non

- segment

- associated services (See AIRIMP for format )

TKNO Ticket number

VIP Very Important Passenger, optionally preceded by number of VIP(s), as (f)VIP.

For example: 2VIP

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1715

PASSENGER SERVICE MESSAGE (PSM)

(amending)

PSC( 33 35 )1715

B13.1

.....

1.1 DEFINITION

The Passenger Service Message (PSM) informs downline stations and applicable airport authorities of

disembarking and transiting passengers who require assistance or special handling. On multi

- sector

flights, each departure station shall transmit a separate PSM to each downline station, relating the

data of disembarking and transiting passe ngers that applies to that downline station. The PSM is

created with specific passenger names and their related SSR/OSI /AUX service(s). The PSM contains

a numeric recap of the PSM services required for each downline destination, followed by the names

and services for each destination, and may include supplementary information.

1.4 COMPONENTS

The PSM contains the following components:

Address Element HDQRMNW

Communications Reference Element .AMSKPKL 131313

Message Identifier Element PSM

Flight Element NW055/13MAR AMS PART1

Downline Destination and Recap Element

- DTW 5PAX/8SSR

SSR/OSI /AUX Codes and Counts Element DEAF 003F 001C 000Y

WCHR 002F 000C 003Y

VIP 001F 001C 000Y

Compartment and count line F CLASS 5PAX/7SSR

Name Element and Seat Number 1VINCENT/GERARDMR 22A

Onward Connection NW1234F13SFO

SSR/OSI /AUX Services Element WCHS HAS OWN CARRY CASE

Supplementary Information Element SI

EXPECT COMPLAINTS AT ARRIVAL

End Element ENDPSM

2.4 FLIGHT ELEMENT

2.4.1 This element is mandatory.

2.4.2 For a code

- share flight, show operating carrier and flight number.

2.4.3 For construction rules, see RP 1707b, Flight Element.

2.4.4 Example:

GF003/18MAR BAH PART1

**Note:** Whe n there are no PSM SSR/OSI /AUX services (as listed below) and no SI free format

text to be included in the whole message, insert the NIL Element on the next line after the

Flight Element and terminate the message with the End Element.

2.6 SSR/OSI /AUX CODES AND COUNTS ELEMENT

2.6.1 This element is conditional.

2.6.2 It is used when at least one of the allowable SSR/OSI /AUX codes as shown below is present

for the passenger in the DCS.

2.6.3 In alphabetical order under each destination, list the SSR/OSI /AUX code(s) and count(s) that

apply.

2.6.4 Show counts for each code by compartment. Compartments are listed in descending order.

2.6.5 Following are the allowable SSR/OSI /AUX codes for the PSM (as taken from RP 1708,

PNL/ADL):ASVC Additi onal Services

— Segment

- associated (See AIRIMP for format)

. . . SVC Additional Services

— Non

- segment

- associated (See AIRIMP for format)

2.6.6 For construction rules, see RP 1707b, SSR/OSI /AUX Codes and Counts Element.

2.7 COMPARTMENT AND COUNT LINE **(Message**

**- specific Data)** 

2.7.1 This information is mandatory.

2.7.2 It appears as a header for each compartment per destination. Compartments are listed in

descending order.

2.7.3 Enter the compartment code, space, and the word “CLASS”, followed by a sp ace and the

number of passengers requiring service for this airport/compartment and “PAX”. Follow

this with a space oblique space and the number of SSR/OSI \ AUX services required for this

airport/compartment and “SSR”.

2.7.4 When a compartment has no pass engers to list with PSM SSR/OSI /AUX services enter

one space and the word “NIL” after the word “CLASS”.

2.9 ONWARD CONNECTION

2.9.1 This information is conditional.

2.9.2 It is used when a passenger with an allowable SSR/OSI /AUX code has an onward

connection from the PSM flight.

2.9.3 Only the first onward connection from the PSM flight is shown for a passenger.

2.9.4 If the onward connection is a code

- share flight, show operating carrier and flight number.

2.9.5 The entry beg ins on a new line, preceded with one space.

2.9.6 For construction rules of the onward connection flight details, see RP 1707b, Onward

Connection(s) Element. However, do not include the element ID (.O/).

2.9.7 Example:

SR1234F27ZRH

**Note:** On subsequ ent lines, enter as many alphabetically listed SSR/OSI /AUX Services

that apply to this passenger.

2.10 SSR/OSI /AUX SERVICES ELEMENT

2.10.1 This element is mandatory.

2.10.2 Each PSM SSR/OSI /AUX service code is listed on a separate line.

**Note:** the AUX element code SVC (per AIRIMP) is the only AUX element that can be

included in DCS messages.

2.10.3 The allowable SSR/OSI /AUX codes to include for a passenger on a PSM are listed in the

table for

SSR/OSI /AUX Codes and Counts Element as shown in this Recommended Practice.

2.10.4 For construction rules see RP 1707b, SSR/OSI /AUX Services Element.

... Section 3

— Examples

3.1 EXAMPLE OF PSM MESSAGES SENT FOR A FLIGHT ORY

- GVA

- ATH

3.1.1 PSM from ORY sent to GVA inc luding SSR/OSI /AUX items and SI text

3.1.2 PSM for the same flight sent from ORY to ATH including SSR/OSI /AUX items

and SI text

3.2 EXAMPLE OF A PSM WITHOUT SSR/OSI /AUX ITEMS AND WITH SI FREE TEXT

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1716

PASSENGER INFORMATION LIST (PIL)

PSC( 30 35 )1716

B13.1

.....

2.4 PASSENGER INFORMATION **(Message**

**- specific Data)** 

As a minimum, the PIL includes passengers who have one or more SSR/OS I /AUX services. The

services included on the PIL are a sub

- set of the acceptable SSR/OSI codes listed in RP 1708,

according to user preference (usually limited to in

- flight services). Additionally, according to user

preference, just passengers of a specifie d class (such as first class) can be listed on the PIL, whether

or not they have confirmed SSR/OSI /AUX services. In this case, the user may choose to list all of the

seat numbers in that compartment, as a means of identifying un

- occupied seats. Seat number s (with

their associated passenger data) are listed in ascending order per compartment.

2.4.1 Construction Rules

Field Example Data Field Name

(see RP 1707a/b)

2.4.1.1 seat number 17D seat number

(start a new line for each seat number)

2.4.1.2 space → information separator

2.4.1.3 passenger's destination BKK airport code

(may be omitted for a single leg flight)

2.4.1.4 space → information separator

2.4.1.5 passenger name BROWN/JOHN name elemen t

(do not include number before surname on PIL,

as described in ‘name element’)

2.4.1.6 Free format information WCHCOWN free flow text

(Use applicable SSR

, or OSI or AUX code(s) from

RP 1708 and/or appropriate comments.)

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1717a

PAXLST MESSAGE

PSC( 15 35 )1717a

M2.6

RECOMMENDED that:

1. Members participating in Advance Passenger Information programmes with

customs or other control authorities shall refer to the “Guidelines for Customs

Administration and Air Carriers” which may be obtained from the World Customs

Organization (www.wcoomd.org).

2. The UN/EDIFACT and the XML Passenger List Message (PAXLST) may be used

for the transmission of data by Members participating in such programmes.

3. The IATA version of the PAXLST message will be maintained by the Passenger

and Airport Data Interchange Standards (PADIS) Board and for more information

contact: PADIS. Secretariat@iata.org.

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1719

PASSENGER FINAL SALES MESSAGE (PFS)

(amending)

PSC ( 34 35 )1719

B13.5

.....

2.8.8 The categories are:

CFMWL Passenger without OK ticket, shown on PNL/ADL as a revenue passenger on the waiting

list (.WL/); boarded.

FQTVN Frequent traveler number (if not shown on, or modified from, the passenger data the

PNL/ADL).

NOSHO Shown on PNL/ADL but not checked

- in (exclude .ID2/ passengers)

OFFLK Passenger with OK ticket shown in PNL/ADL, checked

- in but not departed. For example,

not boarded because of capacity.

OFFLN Passenger with OK ticket, not shown on PNL/ADL, checked

- in but not departed. For

example, not boarded because of capacity.

NOREC Passenger with OK ticket, not shown on PNL/ADL; departed.

GOSHN Passenger without OK ticket, not shown on PNL/ADL; not departed; indicates to

reservations that a higher passenger demand than the offered aircraft capacity has

existed (exclude .ID2/ passengers).

GOSHO Passenger without OK ticket, not shown on PNL/ADL; departed.

CHGCL Voluntary Compartment Change; upgraded/downgraded, passenger

- to be listed under

compartment travelled.

INVOL Involuntary Compartment Change; upgraded/downgraded, passenger

- to be listed under

compartment travelled.

CHGSG Change of Segment; passenger travelling to another destination then booked to.

CHGFL Passenger, not covered under any other category tr ansferred to other flight due to flight

irregularity.

CHGTO Passenger involuntarily transferred from another flight to this flight due to irregularity.

IDPAD ID passenger boarded on a space available basis.

APIPX Changed or added API information for this passenger.

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1719a

FREQUENT TRAVELLER LIST (FTL)

PSC( 31 35 )1719a

B13.1

.....

2.11 FREQUENT TRAVELLER INFORMATION

2.11.4 Construction Rules

Field Example Data Field Name

(see RP 1707a/b)

2.11.4.1 space → information separator

2.11.4.2 element ID .R/ element ID

2.11.4.3 applicable frequent traveler SSR code FQTR SSR/OSI /AUX code

( use only FQTV, FQTR, or FQTU)

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1719b

PASSENGER RECONCILE LIST (PRL)

PSC( 34 35 )1719b

B13.1

.....

2.18 REMARKS ELEMENT

2.18.1 This element is conditional.

2.18.2 It is mandatory for .R/SEAT when seat numbers have been assigned.

2.18.3 It is mandatory for PAXLST information when it is present.

2.18.4 It is optional for all other types of remarks a s bilaterally agreed.

2.18.5 This element follows the guidelines of RP 1708 (PNL/ADL) for the inclusion of SSR/OSI /AUX

codes.

2.18.6 For construction rules, see RP 1707b, Remarks Element. This element uses element ID “.R/”.

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1720a

STANDARD THIRTEEN

- DIGIT NUMBERING SYSTEM FOR TRAFFIC

DOCUMENTS

(amending)

PSC( 33 35 ) 1720a

**....**

RECOMMENDED PRACTICE 1720a

Attachment ‘A’

Effective July 1 2014

P3

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 BSP 1,2 ATB

Miscellaneous

Charges Order

Off

- Premise

Electronic

Miscellaneous

Document

(OPEMD) Coupon

– by Coupon

- 725d

725g - - - - 191

- - - - - - - - 7 3

Agency BSP 1,2 ATB

Miscellaneous

Charges Order

Off

- Premise

Electronic

Miscellaneous

Document

(OPEMD) Coupon

– by Coupon

- 725d

725g - - - - 192

- - - - - - - - 7 3

... Agency BSP 1,2 Virtual Multiple

Purpose

Document Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) Coupon by

Coupon

(paperless)

- 725g

- --- 201

------- 7 2 3

... Agency BSP 1,2 ATB

Miscellaneous

Charges Order

Off

- Premise

Electronic

Miscellaneous

Document

(OPEMD) Coupon

– by Coupon

- 725d

725g - - - - 304

- - - - - - - 7 3

Agency BSP 1,2 Multiple Purpose

Document Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) 1 Coupon 726e

725g - - - - 305

- - - - - - - 7 1 3Stock

Provider

Party Type of Form No. of

Coupons IATA

Resolution /

Recommend

ed Practice ATA

Resolutio

n Airline

Code

1 2 3 Form

Code

4 5 6 Serial

Number

7 8 9 10

11 12 13 Numbe

r of

Digits

in

Serial

Numbe

r Method of

Check

Digit

Calculatio

n

(see

below)

Agency BSP 1,2 Multiple Purpose

Document Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) 1 Coupon 726e

725g - - - - 309

- - - - - - - 7 1 3

... Agency BSP 1 ,2 Excess Baggage

Ticket Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) 2 Coupon 742

725g - - - - 352 7 3

... Agency BSP 1 ,2 Multiple Purpose

Document Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) 1 Coupon 742

725g - - - - 500 7 1 3

Agency BSP 1 ,2 Multiple Purpose

Document Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) 1 Coupon 742

725g - - - - 501 7 1 3

Agency BSP 1 ,2 Multiple Purpose

Document Off

Premise

Electronic

Miscellaneous

Document

(OPEMD) 1 Coupon 742

725g - - - - 502 7 1 3

Agency BSP

1,2 ,5 Off

- Premise

Automated

Ticket and

Boarding Pass

(ATB)

& Electronic

Ticket (OPET) Coupon

by

- Coupon 722g

- - - - 83 8 3

Agency BSP 1,2 Automated

Miscellaneous

Charges Order

Off

- Premise

Electronic

Miscellaneous

Document

(OPEMD) Coupon

– by Coupon

- 725d

725g - - - - 88 8 7 3

Agency BSP 1,2 Automated

Miscellaneous

Charges Order

Off

- Premise

Electronic

Miscellaneous

Document

(OPEMD) Coupon

– by Coupon

- 725d

725g - - - - 907 7 3Agency BSP

1,2 ,5 Off

- Premise

Automated

Ticket and

Boarding Pass

(ATB)

& Electronic

Ticket (OPET) Coupon

by

- Coupon 722g

- - - - 93 8 3

Agency BSP 1,2 Not assigned

Off

- Premise

Electronic

Miscellaneous

Document

(OPEMD) - 725g

- --- 950 7 Not

assigned

3

...

1 Computer generated ticket serial number. All other Passenger Traffic Documents have a preprinted ticket serial number

2 Standard neutral ticket. Airline name and code are not preprinted

T2.8

... 3 Up to 31 May 2008 this form code was classified as “Off

- Premise Transitional Automated Ticket (OPTAT) & Electronic Ticket”

using check digit method 2. Until such time as an advice is issued that this form code is recycled and the new check digit

method is effective, the previous check digit method 2 is sti ll to be used for documents issued up to 31 May 2008 (i.e.

documents related to ADM/ACM, Exchanges, Issued in Connection With). Systems and processing centres must not make

changes to the check digit routine until advised by IATA

.

5 Up to 31 May 2008 this form code was classified as “Off

- Premise Automated Ticket/Boarding Pass (OPATB) & Electronic

Ticket” using the same check digit method 3

8 Effective through December 31, 2010

9 Effective January 1, 2011

10 Up to 31 May 2008 this form code was classified as “Off

- Premise Transitional Automated Ticket” (pre

- printed) using check

digit method 1. Until such time as an advice is issued that this form code is recycled and the new check digit method is effective,

the previous check digit method 1 is still to be u sed for documents issued up to 31 May 2008 (i.e. documents related to Refunds,

ADM/ACM). Systems and processing centres must not make changes to the check digit routine until advised by IATA.

11 Up to 31 May 2008 this form code was classified as “Passenger Ticket” using check digit method 1. Until such time as an

advice is issued that this form code is recycled and the new check digit method is effective, the previous check digit method 1 is

still to be used for documents issued up to 31 May 2008 (i.e. docu ments related to Refunds, ADM/ACM). Systems and

processing centres must not make changes to the check digit routine until advised by IATA.

**Secretary Note:** the footnotes to be removed from the form code number matrix

where they are currently shown.

Fili ng Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1741

PASSA N GE R AND BAGGAGE CONFORMANCE SERVICES

( new )

PSC( 35 )1741

B11.1

RECOMMENDED that:

When an airline, airport or associated service provider plans to use web services

technology to support the business requirements for a common use self

- service bag

drop process, the web services specifications as described in this Recommended

Practice shall be applied.

1. Purpose

The purpose of t his RP is to standardize data exchange supporting common use self

service bag drop through the use of web s ervices technology in order to:

- Allow for a simple 'plug and play' solution which airlines using web services

can roll out anywhere and

- Support a sha red infrastructure environment.

2. Scope

The scope of the functional requirements of the web services specifications is derived

from the use cases supplied by the IATA Fast Travel Working Group (FTWG). The

requirements have been mapped to a technology neutral model. Additionally, a

conformance authentication service has been identified for both passenger and

baggage covering five generi c operations for each element.3. System Overview

The following scenario represents a simple system to show the diffe rent entities

involved:

4. Technical specifications

XML schemas and web services specifications for the above defined operations will

be maintained by the IATA PADIS Board and published on PADIS Extranet site at:

https://extranet2.iata.org/sites/padis

.

5. Implementation guide

An implementation guide containing sample process chains and test cases to give

guidance on implementing a process will be maintained by the TSG Common Use

Web services and published on https://extranet2.iata.org/sites/pemg/common

- use

wg/tsg

- webservices

.

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014 Airport Airline

Customer (Passenger)

using the Common

Use Self Bag Drop Passenger

Conformance

Web Service Baggage

Conformanc

e Web

E SB (E nterprise Service Bus)

Web Services Baggage

Conformance

Web Service Passenger

Conformance

Web ServiceRECOMMENDED PRACTICE 1752

REL IA BILITY AND ITEGRITY OF BAGGAGE MESSAGIN G

( new )

PSC(35)1752

B8

Expiry: Indefinite

Type: B

R E C O M ME N D ED t h a t:

I n o r de r to i n c r e a se t h e r e l iab i l i t y an d in t e g r i t y o f b a g g a g e m e s s ag i n g an d c o n s e q u en t l y

a l l o w b a gg a g e jou r n e y s t a k e holde r s to k no w w h a t ha s h ap p en e d t o a s p e c i f i c ba g du r i n g i t s

j o u r n e y a n d t h e s t a t u s o f t h e ba g to e na b l e t h e n e x t s t e p i n t h e b a g g ag e jou r ne y to b e

u n d e r t a k e n

, M e m b e r s s h a l l a dop t t h e B a g ga g e B r o k e r s t a n da rd a n d be s t p r a c t i c e s and

s h a l l w o rk w i th t h e c o mm u ni t y i n o r d e r to i m p l e m e n t these s t a n d a r d s.

Introduction

B ag ga g e B r o k e rs a l lo w t h e c o m m un i t y t o o v e r c o me t h e F i re an d F o r ge t n a t u re o f

c u rr e n t ba g g a g e m e ss a g i n g w h i c h l a c k s in t e g r i ty an d d a ta r e du n da n c y

, i m pa c t i n g t h e

p r o c e ss i n g o f b ag s

.

Scope

B ag ga g e Br o k e r s a re r e l e v a n t t o a l l b a g ga g e p r o c e s s e s i n w hi ch t h e s y st e m i s un a b l e t o

c o m p le te a p r o c e ss du e t o m i s s in g

, c o r r u p t e d o r c on f l i c t i n g i n f o r m a t i o n r ega r di n g a ba g

.

Purpose

T o en ab l e b ag g ag e p r o c e s s e s to r eq u e s t m e s s a g i n g da ta ne ed e d to c o m p le t e p r o c e s s e s

, B ag ga g e B r o k e r s w il l e xc h a n g e d a t a so t ha t da ta i s s u e s c a n b e f i x ed

. In t h i s m an ne r t h e

o v e r a l l b a g g a g e d a ta e n v i r on m e n t w i l l i m p r o ve a s t h e a d op t i o n i n c r ea s e s.

Ba gg a g e B r o k e r

E a c h b a g ga g e s y st e m t h a t s en d s o r r e c e i v e s b ag g a g e m e s s a g i n g da t a s ha l l h a v e a

B ag ga g e Br o k e r in t e r f a c e

, a l lo w i n g t h e p o i n t

- t o

- p o i n t e x c h a n g e o f d a ta a c r o s s t h e n e t w o r k o f

B ag g ag e Br o k e rs. T h e B ag ga g e B r o k e r en v i r o n m e n t i s e n v i s i on e d t o c o n s i s t o f a n e t w o r k

o f B a gg ag e Br o k e r i n t e r f a c e s t h a t r e qu e st d a t a f r o m o n e a n o t h e r i n c a s e o f m e ss a g i n g

f a i lu r e s o r d a ta g a p s

, a v o i d in g t h e n e e d f o r a c en t r a l r e p o s i t o r y

. B ag ga g e B r o k e r in t e rf a c e s

a r e m o de r a t e d a n d ow n e d b y t he i r r e s p e c t i ve b a g g a g e s y st e m ow ne r

.

T h i s r e c o mm e nd e d p r a ct i c e e x pa n d s o n h o w B a g g a g e Br o k e r in t e rf a c e s c a n e xc h a n g e

da t a fr o m e a c h o t he r, a l lo w in g f o r a f r e el y c o m p e t i t i v e s e r v i c e t o b e d e v e lo p e d

.

Baggage Broker interface

The Baggage Broker interfaces shall be able to send queries to and receive responses from

other baggage systems that have a Baggage Broker interface. For Baggage Broker

interfaces to have permission to connect to each other, Baggage system owners shall

eng age in bilateral agreements for connection permissions.

Baggage Broker interface identifier

For the Baggage Broker network to work, the individual Baggage Broker interfaces need to

have a unique identifier. The Baggage Broker interface identifier shall be a 10

- digit

alphanumeric case

- insensitive number.M es s a ging

The messaging between Baggage Brokers is envisioned to be:

• Automatic host to host queries.

• Real

- time, to enable process continuity.

• Through the Internet protocol.

The messaging computing shall be on local Baggage Broker level without the intervention of a

central system.

M es s a ging c o m p re s s i o n

Co m p r e ss i o n o f q ue r i e s an d r e s po n s e s i s r e c o m m en d e d i f t h e d e cr e a se i n da t a tr a n s f e r

ou t wei g h s t h e t i me r e q ui r e d to c o m p r e ss an d d e c o m p r e ss d a t a

, a n d i f t h e B a gg ag e

Br o k e r i n t e r f a c e r e c ei v i n g a m e s s a g e s u p po r t s t h e c o m p r e s s io n m e t h od

.

M es s a g i n g f or m a t

T h e m e ss a gi n g be t w ee n B a gg ag e Br o k e r s s h a l l b e i n X M L

. M e m b e rs s ha l l wo rk w i th t h e

c o m m un i t y t o :

• M a p t h e b a g ga g e p r o c e ss e s;

• I d en t i f y t h e b u s in e s s r e q ui r e m e n ts;

• De f i n e t h e XML d a ta t y p e s

, d a ta c on d i t i o n s, n a m e s

, d a ta a t t r i bu t e s and other

required XML m e ss a g i n g s p e c i f i c a t i o n s t o w a r d s a c o m p le t e XML s c he m a

f a c i l i t a t i n g X ML m e s s a g i n g be t w e e n B ag ga g e B r o k e r s

.

T h e B ag g a g e X M L G r ou p i s c u r r en t l y d e v e l o pi n g X ML b a s e d m e s s ag i n g st a n d a r d s

. T h e

g r ou p o pe r a t e s w i t hi n t h e P a ss e ng e r a n d A i r po r t D a ta I n t e r c h a ng e St an da r d s ( P A D IS)

f r a m e wo rk to en s u re c o n s i s t en c y a n d in t e r o p e r a b i li t y w i t h o t he r a i r li n e m e ss a g i n g s t an da r d s

w i t h t h e str a t e g i c d i r e c t i o n d e t e rm i ne d b y the B ag ga g e S t ee r i n g G r o u p ( BS G ).

Ba gg a g e B r o k e r A d dr e s s Boo k

B ag ga g e B r o k e r i n t e rf a c e s ha v e t o de t e r m i n e w h o t o s e n d t h e q ue r y t o

, to r e c e i v e t h e

c o r r e c t B a g ga g e I n f o rm a t io n M e s s ag e

. H o w e v e r t h e b ag g ag e l i c e n se p l a t e a s pe r

R e s o lu t i o n 7 4 0 d o e s n o t c on t a i n s u f f i c i en t in f o r m a t io n f o r t h e B ag g a g e Br o k e r s to e x t r a ct

t h e i de n t i t y o f t h e s y st e m t h a t i s ab l e to p r o v i d e t h e b a g m e ss a ge

. T h e r e f o r e t h e B ag ga g e

Br o k e r A d d r e s s B oo k s hal l p r o v id e t hi s in f o rm a t i o n

, wh e re i n c a se o f m e ss a g i n g f a i lu r e s o r

da t a ga p s, B a g g ag e Br o k e r s c a n de t e rm i n e t h e B a gg a g e B r o k e r in t e r f a ce i de n t i f ie r o f t h e

b ag g a g e s y st e m t h a t h a s t h e B ag g ag e I n f o r m a t io n M e ss a g e a s s o c i a t e d w i t h t h e b a g ga g e

l i c e n se p l a t e

.

In order for the Baggage Broker Address Book to be able to provide the correct address to the

Baggage Broker interfaces, the following conditions must be met:

• T h e B a g ga g e Br o k e r A dd r e ss B o o k s hal l c o n t a i n up

- t o

- d a te ba g t a g n u m b e r r a n g e s

a ss o c ia t e d w i t h s pe c i f i c B a gg ag e Br o k e r in t e rf a c e i de n t i f ie r s

. T h e r ul e s h a l l b e ei t h e r a

b o u n d r a n g e o r a r ang e o f b a g t a g nu m be rs st a r t i n g w i t h a pa r t i c u l a r c o m b in a t i o n o f

c h a r a ct e r s an d d i g i ts. S e e A t t a c h m e n t ‘ A’ f o r e x a m p l e s.

• T h e bi l a t e r a l a g r e e m e n ts b e t we e n t h e B a gg ag e B r o k e r I n t e rf a c e s s h a l l b e m a i n t a i n e d

an d s t o r e d i n t h e B a g g ag e B r o k e r A d d r e ss B o o k

.• T h e B a g g ag e Br o k e r i n t e rf a c e i d en t i f i e r s s h a l l b e a ss i gne d an d m a in t a i n e d b y I A T A t h e

B a gga g e B r o k e r A dd r e ss B oo k m o d e r a t o r

.

• T h e B a gg a g e Br o k e r in t e r f a c e s n ee d to b e p e r io d i c a ll y s y n c e d w i th t h e B a gg a g e Br o k e r

A dd r e s s B o o k p r e v en t i n g t h e n e e d f o r qu e r y i n g t h e B a gg a g e Br o k e r A dd r e ss B o o k e v e r y

t i me t h e re i s a ne e d t o loo k u p o t he r B a gg ag e Br o k e r s

, i

. e

. B a gg ag e B r o k e rs s h a l l h a ve

a l o c a l c o p y o f t h e B a g g ag e Br o k e r A dd r e s s B oo k

.

• T h e s y n c fr e q u e n c y b e t w e e n t h e B a g ga g e B r o k e rs a n d t h e B a g g ag e B r o k e r A d d r e ss B o o k

s h a l l b e s e t b y t h e m o de r a t o r o f e a ch B a g gag e b r o k e r in t e r f a c e

.

Business case

T h e op er a t i o na l a n d f in a n c ia l b e n e fi t s o f a do p ti n g t h e Ba g g ag e Br o k er w ill di f f e r p e r a i r l i n e

a n d w ill d ep en d on f o r ex a m p l e :

• T h e e ff i c i e n c y o f t h e m e ss a gi n g s y s t e m an d p r o c e du r e s i n p l a c e

.

• R a t e o f m e ss a g i n g f ai l u r e s a n d da ta ga p s.

• T h e i m p a ct o f t h e m e s s ag in g f a i l u r e s a n d da t a ga p s o n t h e b a gg a g e m i s h and l i n g

.

• Sc o p e o f a d op t i o n

.

• C o s t o f s e tt i n g u p t h e B ag g ag e Br o k e r in t e rf a c e

. W hil e t h e b e ne f i ts o f ado p t i n g t h e B ag ga g e B r o k e r s t a n d a r d a re de t a i le d i n t h e

p r e v i o u s s e c t i o n s, t h e f o ll ow in g f a c t o r s h a v e be e n id e n t i f i e d i n t h e b u s i n e ss c a s e :

1. T h e B ag g a g e B r o k e r st a n d a r d i s a m e c h a n i s m f o r "f i l li n g i n " m i s s i n g bag ga g e

m e ss ag in g da t a

.

2. It r e c o r d s, an a l y z e s a n d r e po r t s w he r e t h e r e a re p r o bl e m s

.

3. T h e c o m m u n i c a t io n b e t w e e n t h e B a gg ag e Br o k e r in t e r f a c e s s ha l l b e i n X ML o v e r

t h e I n t e r n e t Pr o t o c o l w i t ho u t ad d i t i on a l c h a r g e s f o r t h e u s e rs.RECOMMENDED PRACTICE 1752

Attachment ‘ A ’

Example of bag tag ranges linked to Baggage Broker interface identifiers within the

Baggage Broker Address Book.

# Range Interface

identifier

1 0085123* 1avjkgdsf2

2 0085123000

-

0085123456 f7wmxcd89d

Example 1 indicates that for:

• All bag tag numbers starting with 0085123, Baggage Broker interface identifier

1avjkgdsf2 shall be queried in case of messaging failure or data gaps.

Example 2 indicates that for:

• All bag tag numbers bound between the bag tag numbers 0085123000

- 0085123456, Baggage Broker interface identifier f7wmxcd89d shall be queried

in case of messaging failure or data gaps.

Filing Period: Effective Date:

20 December 2013 1 June 2018

14 February 2014RECOMMENDED PRACTICE 17 80e

IATA INTERMODAL INTERLINE TRAFFIC AGREEMENT

- PASSENGER

(amending)

PSC( 25 35 )17 80e

P10

RECOMMENDED that:

.....

8.2.6 The concurrence procedures outlined above may be expedited in the following

manner. An issuing airline shall notify a participating transportation provider of its

intent to concur on an expedited basis, by teletype message email addressed to

mita@iata.org with a copy to the IATA Head, Interline & Intermodal Policy

(YULTXXB) . If no objection is received from the Participating transportation provider,

the concurrence shall be deemed to be effective ten (10) da ys after the dispatch of

the teletype message email addressed to mita@iata.org . The IATA Head, Interline &

Intermodal Policy will circulate a list of expedited concurrence in the regular

transmittals

.....

RECOMMENDED PRACTICE 1780e

Annex ‘A’

IATA INTERM ODAL BAGGAGE AGREEMENT

– CITY TERMINALS

6.1.6 The concurrence procedures outlined above may be expedited in the following

manner. An issuing airline shall notify a participating surface transportation provider

of its intent to concur on an expedited basi s, by teletype message email addressed to

mita@iata.org with a copy to the IATA Head, Interline & Intermodal Policy

(YULTXXB) . If no objection is received from the Participating transportation provider,

the concurrence shall be deemed to be effective ten ( 10) days after the dispatch of

the teletype message email addressed to mita@iata.org . The IATA Head, Interline &

Intermodal Policy will circulate a list of expedited concurrence in the regular

transmittals

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1790

ADDITIONAL SERVICES

(amending)

PSC( 34 35 )1790

B13.3

.....

6. AIRPORT PROCESS

6.1 Industry standard messages in accordance with provisions of Recommended Practices

1708 (PNL/ADL), 1715 (PSM), 1716 (PIL), 1719 (PFS) and 1719b (PRL) and 1719e (ASL)

shall be used to transmit data for Additional Services.

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014RECOMMENDED PRACTICE 1790a

ONLINE SALES OF ADDI TIONAL SERVICES IN I NTERLINE E

- TICKET

SCENARIOS

(new)

PSC(35)1790a

T2.2

.....

Recommended that:

Member Airlines and/or GDSs may use, the following guidelines for the reservations,

sales, and delivery of Additional Services in specific scenarios using an EMD when a

full interline EMD is not in place with their interline partner, as described hereafter.

1. SCOPE

1.1 This Recommended Practice describes a procedural solution that allows a

Member to issue its own EMD and service its own ancillary services product(s) where

the Validating Carrier of the Electronic Ticket is different to the Operating Carrier on

whom the ancillary services are sold.

1.1.1 The scope defines a procedure that may be f ollowed when such Validating

Carrier and Operator carrier have an established interline electronic ticket agreement

but do not have an interline electronic mi scellaneous document agreement.

1.1.2 Alternatively the scope defines a procedure in code share s cenario, where EMD

validating carrier is the operating carrier. The procedure may be followed when such

Validating, Marketing and Operating carrier have an established interline electronic

ticket agreement but do not have an interline electronic miscellane ous document

agreement between the e

- tick et and EMD validating carriers.

1.2 This Recommended Practice describes how an EMD

- A can be issued and

validated on its own operating carrier code, and issue its own EMD coupon(s) which

are required to be lifted at the same time as the electronic ticket coupon(s) validated

on another carrier.

1.3 This procedure shall be limited to two interline partners, where one Member is the

Validating Carrier of the electronic

- ticket and the other Member is the Validating

Carrier of the EMD. The electronic

- ticket must contain at least one coupon of the

Operati ng Carrier who will issue its own EMD as Validating Carrier of the EMD. The

EMD shall contain only coupons of the Member who is both the Validating Carrier of

the EMD and the Operating Carrier providing the service that is purchased on such

EMD.

The reco mmended practice process covers both airline and travel agency sales.2. OBJECTIVE

The objective of this Recommended Practice is to describe an internal process

whereby the Operating Carrier may book and issue as Validating Carrier its own

EMD

- A in order to sell its own ancillary services when the electronic ticket is issued

by one of its interline partners with whom it does not have an Interline Electronic

Miscellaneous Document agreement, without requiring the Validating Carrier of the

electronic t icket to make any system adjustments to support this business process. A

process description and ex ample is shown in Attachment A.

3 RESERVATION PROCESS

3.1 Additional services shall be booked in accordance with the provisions of AIRIMP

Chapter 3.19 ‘Ad ditional Services’.

4. TICKETING

4.1 EMD Issuance and system update message process (See Attachment A)

4.1.1 The Operating Carrier referenced on the interline electronic ticket shall issue

the EMD

- A validated on its own carrier code.

4.1.2 After obtaining airport control of the interline electronic ticket, only a system

update information message is sent from the Validating Carrier of the EMD to

request the internal association of the EMD

- A to the electronic ticket of its interline

partner’s cou pon.

4.1.3 No system update message is sent from the Validating Carrier of EMD to the

Validating Carrier of the e

- ticket. If the flight is code share where EMD validating

carrier is operating the flight, no message is sent to the marketing carrier.

4.1. 4 Upon receipt of the information only System Update message, the

corresponding ET flight coupon(s), shall be updated with the In Connection With

Document Number and the In Connection With Coupon Number.

4.2 EMD

- A Coupon usage process (Ref. to attachment A)

4.2.1 In accordance with the provisions of Resolution 725f the EMD

- A, coupons shall

be lifted at the same time of the corresponding electronic ticket coupon.

4.2.2 The Operating Carrier of the Electronic Ticket shall generate a ‘Change of

Status’ re quest to set final status to FLOWN for the ET coupon

4.2.3 Upon receipt of a positive response from the Validating Carrier of the e

- ticket,

the operating carrier shall ensure that its own internal process is used to change the

status of its own EMD

- A cou pon to FLOWN/USED4.3. Request Airport Control by the Validating Carrier of Electronic Ticket

4.3.1 If the Validating carrier of the electronic ticket requests airport control back

from the operating carrier, the Validating Carrier of the EMD

- A shall ensure that such

EMD

- A is disassociated in order not to deny the airport control request so that contro l

of the ET can be returned to the Validating Carrier.

4.3.2 The Validating Carrier of the EMD

- A shall ensure that no reference is made to

such EMD

- A and shall update the corresponding ET flight coupon(s), by removing

the In Connection With Document Num ber and the In Connection With Coupon

Number prior to returning control of the electronic ticket coupons.

5 AIRPORT PROCESS

Airport process should be in accordance to Airport Process section as described in

Recommended Practice 1790.

Attachment A

The following attached diagram is showing how the ticketing process is supposed to

function for step 1 (EMD Issuance and system update message process) and step 2

(EMD

- A Coupon usage process):RECOMMENDED PRACTICE 1797

COMMON USE PASSENGER PROCESSING SYSTEMS (CUPPS)

(amending)

PSC( 34 35) 1797

B11

....

1.1 Benefits of CUPPS

A CUPPS implementation will enable airlines to provide passenger services in the

context of a shared check

- in, gate podium, or kiosk.

The major benefits of CUPPS are:

■ Efficient use of expensive facilities on

- and off

- airport, thereby reducing the need for

facility expansion.

■ Flexibility for accommodating flight segment additions or deletions by carriers in the

use of space.

■ The ability for an application provider to maintain a single CUPPS

- compliant

application that will be seamlessly functional on any CUPPS platform, regardless of the

particular platform provider supplier

. ■ A platform that can easily accommodate various peripheral devices in support of

business processes.

■ An enabler for improved customer service.

■ A flexible architecture to easily accommodate alterations in the passenger processing

flow.

■ An accommodation of the flow of data between emerging and evolving airport and

air line systems, as mutually agreed upon between the platform provider operator and

application provider.

■ Improved flexibility for system upgrades and new versions of software and hardware.

■ Enhanced ease of access to new markets, with overall predictabili ty of cost

magnitudes from a technology deployment standpoint.

1.2 CUPPS Product Strategy

The CUPPS product strategy is to deliver a common use platform to support individual

and shared airline processes at a shared workstation at check

- in, gate, and othe r

positions, while maintaining the ability for users to maintain their brand images. The key

to the product strategy is an open architecture system where it is possible to use

virtually any hardware or software that complies with CUPPS standards included i n the

CUPPS Technical Specification (CUPPS

- TS).The functionality described is not exclusive; any future products and/or applications, as

appropriate, may be introduced as business needs change.

The initial CUPPS strategy is focused on implementation in both the agent

- assisted

check

- in and boarding environments on

- airport and potentially in kiosk environments.

CUPPS could also be carried forward to provide services at other venues such as rental

car agencies, bus terminals, seaports, and railway statio ns.

The development of the CUPPS product will initially be done collaboratively with the

cooperation of airlines and airports, platform providers operators , and platform

suppliers.

.....

1.6 CUTE to CUPPS Migration

With any next

- generation standard or product, a mechanism must be provided to

migrate from the previous standard or product to the next

- generation standard. This

section provides the migration considerations for moving from CUTE to CUPPS.

Given the wide a rray of variations between CUTE implementations combined with the

differences that exist due to the local business and operational scenarios at each CUTE

location, there is no one migration strategy that is applicable across suppliers.

Therefore, each plat form provider operator and/or platform supplier that proposes a

CUPPS solution must provide a reasonable and realistic migration strategy.

.....

2.1.1 Access to the CUPPS

- TR and CUPPS

- TS

In accordance with the Governance terms of reference, ACI, A4A, and IATA shall

produce, update, and make available the CUPPS

- TR and CUPPS

- TS in electronic

format which shall set forth the standards and specifications for CUPPS. As a condition

to certification, application providers and platform providers shall be required to maintain

a current subscription to the CUPPS

- TR and CUPPS

- TS. To enable them to defray the

costs incurred in developing and maintaining the CUPPS

- TR and CUPPS

- TS, ACI,

A4A, and IATA may establish an annual subscription fee for the documents. Access to

t hese documents, and the fee to be charged, will be non

- discriminatory, i.e. all

interested parties, whether or not members of ACI, A4A, or IATA, will be afforded

access to the documents on the same terms, and will pay an equal fee for such access.

The CUPP S

- TR and CUPPS

- TS can be found on the IATA PEMG Extranet. It is part of

the offer for IATA Strategic Partners in the area of Common Use.

.....2.1.3 Data Privacy

The rules governing the safeguards placed on data acquisition, retention, and

accessibility are defined below. Table 4 provides a summary comparison of Public Data,

Personal Data, and Proprietary Data.

Additionally CUPPS recognizes and acknowledges that it should facilitate, and not

prevent, the end customers' PCI Data Security Standard complian ce. Examples of

practices that can prevent compliance include:

■ Storage of magnetic stripe data and/or equivalent data on the chip in the customer's

network after authorization.

■ Applications that require customers to disable other features required by the PCI Data

Security Standard, such as anti

- virus software or firewalls, in order to get the payment

application to work properly.

■ Vendors' use of unsecured methods to connect to the application to provide support to

the customer.

Secure devices, when implemented in a PCI

- DSS compliant environment, will minimize

the potential for security breaches leading to compromises of full magnetic stripe data,

card verification codes and values (CAV2, CID, CVC2, CVV2), PINs and PIN blocks,

and the damaging fraud r esulting from these breaches.

The Application Supplier/Provider shall ensure that when a Payment Card is read for

any purpose other than payment, such as Form of Identification (FOID), the application

shall include only the first 6 and the last 4 digits o f the credit card number. All remaining

digits shall be replaced with an X. E.g. 123456XXXXXX7890.

This behavior is in compliance with Card Scheme Operating Regulations and IATA

Resolutions 722

- f

- g

- h & 725

- f

- g

- h.

Operating systems and third party applica tions such as antivirus and Internet browsers,

in support of common use platforms and airline applications, are necessary to airport

operations. Ensuring that these systems/applications are supported and secured

versions is a vital part of a comprehensive security plan. It is recommended that proper

patch management is maintained for all systems/applications and that versions no

longer supported are upgraded or replaced. Failure to maintain compliance with the

technical specification and industry best pract ices could have severe consequences

including, but not limited to, extended unavailability of Check

- in/Boarding Gates. Proper

patch management is a requirement to obtain and maintain PCI

- DSS compliance.

For more information on PCI

- DSS and for the current version please visit:

www.pcisecuritystandards.org

.....2.1.7 Usage and/or Performance Data

Acquisition, retention, and accessibility of Usage and/or Performance Data are to be

provided in accordance with the CUPPS

- TS. In the absence of superseding rules, the

default rule implemented by CUPPS must be that Usage Data is:

■ Acquired automatically by CUPPS.

■ Retained for a period defined by, and at the discretion of, the platform provider

supplier

. ■ Ac cessed only by:

○ The using entity, i.e. the entity using CUPPS whose activity was recorded by

the platform. A using entity must not be able to access another using entity's

data.

○ The platform provider operator

. ○ The platform supplier.

.....

2.1.9 CUPPS Logical System Architecture Summary

Figure 1 shows a summary view of the logical architecture of a CUPPS implementation.

Each block in the diagram is described below. Airline application server(s) or host

system(s) communicate to the airline CUPPS applica tion using a mutually supported

communications protocol. The architecture and functionality of the airline back

- end

systems or airline application are outside of the scope of CUPPS and are therefore not

discussed.

The CUPPS application communicates with t he CUPPS platform utilizing the interface

defined in the CUPPS

- TS. Applications may only access CUPPS

- defined peripherals

via the interface defined in the CUPPS

- TS. Direct access to a CUPPS

- defined

peripheral device is not allowed. Applications may access workstation components (see

Table 6) via basic operating system services.

The airline system manager or the platform provider’s supplier's system manager

components may communicate with a CUPPS platform using the management interface

defined in CUPPS

- TS.

.....3. Roles and Responsibilities

This section addresses the roles and responsibilities of the various CUPPS parties, as

they pertain to overall system provision and maintenance.

To ensure a consistent interpretation of the material below, please note these

definitions:

■ Supplier: A supplier is the entity that creates the system. Suppliers market their

products and services to providers operators

.

■ Provider Operator : A n provider operator is the entity that acquires the system from a

supplier and provides it to the user community.

3.1 Platform Provider’s Operator's Responsibility

The platform provider operator will, as defined in the SLA, ensure that:

■ The CUPPS platform is operational and usable during the specified operational hours.

■ The CUPPS platform is functioning and certified according to CUPPS standards.

■ Software levels and version control of the platform are maintained for the site.

■ Statistical and management information i s available.

■ Notification is made to the application provider of faults that cannot be resolved.

■ That the ability exists to disable an application if it is deemed to be causing other

applications and/or the CUPPS platform to malfunction. If this is th e case they will

endeavor to inform the application provider in advance.

■ CUPPS workstation locations are to be locally and mutually agreed upon.

3.2 Application Provider's Responsibility

The application provider is responsible for the application code, which must follow and

pass the Certification and Deployment process as defined in the CUPPS

- TS.

If the application provider decides to use a dedicated application Server, either at the

CUPPS site or a location that is under the control of the application provider, then that

application provider is responsible for the maintenance, administration, and support of

the Server.

The application provider is responsible for any communication lines to and from the

application provider's server(s).

The application provider must provide the correct protocol and interfaces to allow

connection at the CUPPS site as mutually agreed between the platform provider

operator and the application provider.3.3 Establishment of Service Levels

Minimum Service Lev els, in the form of a Service Level Agreement (SLA) will be locally

and mutually agreed upon between the platform provider operator , the platform supplier,

and the application supplier. As a guideline, a sample SLA template is included in the

CUPPS

- TS.

3. 4 Management Information and Availability Figures

The platform provider operator should be able to supply all application providers the

Availability figures and access to the management tool used for real time status of the

CUPPS installation.

.....

5. Abb reviations and Glossary

A4A

Airlines for America (formerly the ATA

– Air Transport Association).

.....

PAT

See NAPT.

Platform Provider Operator

A Platform Provider Operator is an entity that acquires a CUPPS Platform from a

Platform Supplier and offers it to the user community. A Platform Provider Operator is

responsible to manage, maintain and administer the implemented Platform in a

production environment.

.....

Filing Period: Effective Date:

20 December 2013 1 June 2014

14 February 2014