Migration Plan to move Baggage Fees from F and P

Migration Plan to move Baggage Fees from F and P Contents Background ___ 2
Business Value in Moving Baggage Fees from F and P ___ 3
Business Value in Eliminating Type P 3 Roadmap to move Baggage Filings from F and P ___ 4
Industry Migration Readiness 5 Filing Scenarios ___ 6
Excess Baggage on the Piece System 7 Data Processing and Subscriptions Impact ___ 12
Excess Baggage on the Weight System 16 Heavy and/or Oversize Bag within the Allowance on the Piece System 23 Data Processing and Subscriptions Impact ___ 25
Concurrence (Type F) vs. Baggage Selection (Types A, P and C ___ 26
Airline Control of Display vs.

Sale ___ 30
Data Application Questions ___ 34
Differentiating Service Type P (prepaid baggage fees) and C (baggage charges)? 34 Data Processing and Subscriptions Impact ___ 35
Process INF occurrence when there is only an ADT booking 36 Data Processing Impact ___ 36
Advance Purchase to/from US with an intermediate stopover 37 Data Processing Impact ___ 38
Appendix A – Future Considerations ___ 39
Channel within Office ID 39 Business Request for Application of Occurrence within Bag Type 42 Determining the Most Significant Carrier (MSC) when performing an automated reissue with a flown segment and change of itinerary 47 Processing multiple pricing solutions when one bag type (e.g.

RFISC) is not permitted 48

Background Prior to 1 April 2011, airlines filed baggage fees as flight-related services (Service Type F) in ATPCO Optional Services as a quick way to offer and sell baggage. The ATPCO Optional Services product was built with the intention of offering flight-related services such as meals and seats and unaccompanied minor fees but wasn’t truly intended for baggage allowance and charges. After 1 April 2011 and the implementation of the ATPCO Baggage Allowance and Charges product and IATA Resolution 302 and the US DOT Disclosure and Reservation, airlines and systems decided to migrate baggage fees filed as flight-related services to prepaid baggage (Service Type P) and baggage charges (Service Type C).

This decision was initially confirmed at the ATPCO Optional Services Working Group in 2014 and discussion has been ongoing through the ATPCO Optional Services Working Group in 2015 and 2016. In 2015, ATPCO asked the industry to sign off on the migration (announced in ATPCO bulletin 15-022). While airlines and systems agree that the data should be moved, there are still outstanding questions from the same parties regarding how the data will be moved and processed in a way to ensure there is a smooth transition for GDSs and merchandising systems and downstream processes such as EMD (Electronic Miscellaneous Document) and reservations messaging.

Most importantly, there must not be a loss of revenue due to this migration.

In the second quarter of 2016, ATPCO presented a proposal to the industry for how to move baggage fees from Type F. This proposal appeared to confirm the airline business desire to migrate the data but also that there were concerns about how to move the data. Feedback from airlines and systems included the following:
  • How do we correctly implement Service Type C processing? Areas of concern include how to differentiate between Service Type P and C baggage fee filings, how to accommodate occurrence processing for infant passengers, how to process reissues, and how to process occurrence in overweight/oversize scenarios, and others.
  • How do we address product limitations in handling occurrence processing?
  • What is the industry plan for migration?
  • How should carriers re-file their data that is currently in Service Type F and P to Service Type C?
  • How should we pass occurrence of excess baggage in the Reservations message?
  • How should we differentiate EMDs sold for prepaid versus check-in charges (e.g., include the Service Type in the EMD)? In 2017, ATPCO along with two airlines and three systems created a task force to begin working through these issues. The task force participated in several conference calls and a face-to-face meeting in May 2017. The result of these discussions was documented and put into a proposal that was presented to the Optional Services and Branded Fares Working Group in November 2017. In 2018, ATPCO incorporated the Working Group feedback to create this plan for how to migrate baggage fee filings from F and P.

Business Value in Moving Baggage Fees from F and P ATPCO, airlines and systems have identified the following three main benefits of moving baggage fees from F and P: 1. Regulatory Compliance – Unlike Service Type F, Service Type C for baggage is designed to align with IATA Resolution 302 and the US DOT/CTA reservations and disclosure 2. Industry/System alignment – There is a cost today associated with not having industry alignment for baggage fee processing. These costs include but are not limited to systems having to maintain exception processing, airlines having to distribute baggage fee provisions in multiple ways to different systems, and added airline and system training costs 3.

Interline/Code Share Collection – Service Type C for baggage contains industry standard rules for whose baggage rules apply and clarifies how to collect baggage rules in interline scenarios. Moving baggage fees from Service Type F will give the industry a single process that will accommodate code share and interline travel.

Business Value in Eliminating Type P As airlines and systems in the task force delved deeper into the issues with migrating baggage fees from F, questions emerged regarding how to differentiate Type P from Type C. Among other concerns, systems have an inconsistent definition of how to process Type P versus Type C and airlines are unclear when to file in type P versus Type C. Ultimately, the task force proposed to eliminate Type P and the majority of the Working Group agreed with this approach. ATPCO, airlines and systems suggest the following business values for eliminating Type P: 1. Reduce the cost of working around inconsistent systems processing of Type P, 2.

Reduce the input, subscriptions and processing costs of managing multiple Service Types for baggage charges, and 3. Simplifying airline filing processes to a single Service Type (and removing airline confusion of when to use Type P versus Type C).

Migration Plan to Move Baggage Fees from F and P 4 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Roadmap to move Baggage Filings from F and P There will be a two-phased approach for migrating baggage fees from F. Phase 1 is an intermediate migration effort to copy / move the baggage fee filings in F and P to C using the sub codes as they are defined in F today. Phase 2 will migrate all sub codes to a small, manageable, standardized list of sub codes that will ease interline sub code management.

Current State (2017) Intermediate (1Q19) End State (TBD) - Baggage Filings in F, P and C - Lack of regulatory compliance (US DOT/CTA/Reso 302) - Lack of industry standard - IATA Reservations Working Group and Interline Electronic Miscellaneous Document (EMD) agenda items to update res and ticketing standards - Interline / Codeshare inconsistency - Airlines and ATPCO copy over baggage charges filings from F and P to C (airlines should work with their system providers to determine readiness) - ATPCO to submit a Milestone 2 / 3 to the industry by the end of February 2018 asking for industry sign-off on the proposed solution - Systems develop processing for C (by 4th quarter 2018) – Industry implementation for ATPCO data application will be by end of 4th quarter 2018 – no data application support for baggage filings in F and P types after end of 4th quarter 2018 - Industry migrates from F and P to C on 31MAR19 - Airlines may continue to use sub codes as specified in F type (e.g.

0CC). For baggage charges on the piece system, occurrence filing is required. Note: ATPCO onlines will automatically populate occurrence for these values. - ATPCO implements prepaid/check-in tag in S7 C type and ensures the capability to specify “all airlines” as a point of sale - ATPCO implements new Weight and Size Table in S5 Services Record to allow airlines to file a data-driven weight and size (for new, generic heavy and oversize within the allowance sub codes as a start) - Downstream processes (RES, EMD work as they do today) - ATPCO publishes a list of acceptable sub codes for the phase 1 migration (see Attachment A – Acceptable Sub Codes for Phase 1 and 2 Migration) - ATPCO discourages baggage filings in F and removes P type - To ease interline sub code management, standardize sub codes for normal bags to a handful [See accompanying Recommended Sub Code List] o Migrate airlines away from C Type Codes o Migrate airlines away from F Type Codes - Downstream Reservation and EMD processes become more robust to accommodate occurrence and weight/size processing - Regulatory compliance - Industry standard processing -

Migration Plan to Move Baggage Fees from F and P 5 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Industry Migration Readiness ATPCO is working with airlines and systems and IATA to determine how best to provide a status on the downstream reservations and EMD standards. What follows is a list of the known downstream functionality requested, the industry body impacted, and the status: Functionality Requested Industry Body Impacted Status Service Reference Number - This will add a Service Reference Number to the Reservations message to allow for the messaging of multiple services of the same type.

IATA Res Working Group TBD – ATPCO is working with airlines and IATA to determine how we can best provide a status Service Type – This will permit the inclusion of Service Type on the EMD to permit distinguishing between prepaid and check-in bag fees of the same Reason for Issuance Sub Code. IATA EMD Baggage Working Group IATA Ticketing – Resolution 722f/A4A 20.60 – 2016 value Additional Services Service Type is a value on the ticketing record which “specifies the type of additional service or baggage for which an EMD is being issued. The Additional Services Service Type is intended to map to the Service Type (S7 Byte 21).

It was approved in PADIS EDIFACT version 12:1.

Occurrence – This will define the occurrence of excess baggage sold on the EMD. IATA EMD Baggage Working Group The Additional Number of Services/Fees value is defined within IATA Resolution 725f, 725g and 725h and was approved in PADIS edifact version 10:1 published in 2010 ATPCO is working with IATA to determine the implementation status within airlines and systems.

Migration Plan to Move Baggage Fees from F and P 6 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Filing Scenarios What follows are different baggage fee filling scenarios showing filings that exist today in Type F and how they will be moved to Type C. The Task Force proposes a unified industry approach on how to transition these filings keeping in mind the implications to pricing and down-line reservations and revenue accounting. Filing scenarios examined include the following:
  • Excess baggage on the piece system,
  • Excess baggage on the weight system, and
  • Overweight within the allowance on the piece system.

Migration Plan to Move Baggage Fees from F and P 7 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Excess Baggage on the Piece System Excess baggage on the piece system occurs when a passenger’s baggage exceeds the number permitted free in the baggage allowance. For example, a passenger has a 1 PC free allowance and decides that they want to bring a second piece. In the case of a passenger purchasing an excess bag at time of passenger ticketing, systems that process baggage in F type today look for a F type filing for the Checked Bag First (0CC) or Checked Bag Second (0CD). The proposal moving forward is for systems to look for a C type filing with an occurrence value of 1.

For Phase 1, the Task Force proposes that airlines copy their F and P Type filings to Type C and add occurrence into the data filing. Airlines may use the sub codes that they use in F type today (e.g. 0CC) to express excess baggage on the piece system and will file occurrence within the first/last occurrence fields on the Provisions Record S7. For those airlines that do use the F Type sub codes, ATPCO will survey the industry to define a default weight and size.

See Phase 1 example migration on the following pages for Type F and Type P.

Migration Plan to Move Baggage Fees from F and P 8 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Phase 1 Task Force Proposal for Prepaid Excess Baggage on the Piece System – copy* F and P type filings to C *There may be additional geographical, cabin and fee application considerations when moving from F and P to C. For example, F Type does not have the capability to express geographies based on the journey and this capability is available in C Type. Example F Type Filing Record Type Service Type Sub Code SSR Commercial Name Description 1 Description 2 S5 F 0CC BAG1 Checked Bag First B1 – First Bag Blank Record Type Service Type Sub Code Sequence Fee Adv Res Pub/ Pri Security Table S7 F 0CC 1000 USD 25 24 hr Pri Discounted: web, internet check-in The data indicates the Checked Bag First (0CC) is USD 25 with 24-hour advance reservation over the web or by internet check-in.

The occurrence here is defined within the RFISC but the weight and size of the bag are not.

Example C Type Filing (prepaid bag) Record Type Service Type Sub Code SSR Commercial Name Description 1 Description 2 S5 C 0CC* BAG1 Checked Bag First B1 – First Bag Blank Record Type Service Type Sub Code Prepaid / Check-in Sequence Fee Adv Res Occurrence (First-Last) Pub/ Pri Security Table S7 C 0CC* P 1000 USD 25 24 hr 1-1 Pri Discounted: web, internet check-in The data indicates a prepaid “Checked Bag First” is USD 25 with 24-hour advance reservation over the web or internet check-in. The occurrence here is defined within the data (First-Last Occurrence).

Airlines may choose to use a F Type Code (e.g.

0CC) OR may choose to use a C Type code with a specific weight and size (e.g. 0GO). If a C Type Sub code (e.g. 0GO) is used, there may be issues with Reservations and EMD as most systems have yet to implement Service Reference Number in the Reservations message and Occurrence on the EMD. Please see accompanying Recommended Sub Code List document. Copy to C + add Prepaid/Check-In Value P (Note: ATPCO will automatically populate the occurrence into the filing for the F Type Sub Codes)

Migration Plan to Move Baggage Fees from F and P 9 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Example P Type Filing Record Type Service Type Sub Code SSR Commercial Name Description 1 Description 2 S5 P 0GO BAG1 UPTO50LB 23KG AND62LI 158LCM 23 - Up To 50 lb/23 kg 6U - Up to 62 li/158 lcm Record Type Service Type Sub Code Sequence Fee Adv Res Occurrence Pub/ Pri Security Table S7 P 0GO 1000 USD 25 24 hr 1-1 Pri Discounted: web, internet check-in The data indicates the first prepaid excess bag (0GO) is USD 25 with 24 hour advance reservation over the web or by internet check-in.

The occurrence here is defined within the data and the weight and size of the bag are defined within the sub code attributes. Example C Type Filing Record Type Service Type Sub Code SSR Commercial Name Description 1 Description 2 S5 C 0GO* BAG1 UPTO50LB 23KG AND62LI 158LCM 23 - Up To 50 lb/23 kg 6U - Up to 62 li/158 lcm Record Type Service Type Sub Code Prepaid / Check-In Sequence Fee Adv Res Occurrence Pub/ Pri Security Table S7 C 0GO* P 1000 USD 25 24 hr 1-1 Pri Discounted: web, internet check-in The data indicates the first prepaid excess bag is USD 25 with 24 hour advance reservation over the web or internet check-in.

The occurrence here is defined within the data (Occurrence). The weight and size of the bag are defined within the sub code attributes. *Airlines may choose to use a C Type Code (e.g. 0GO) in which case the system will use the description attributes to define the weight and size and occurrence is defined within the data OR may choose to use a F Type code with occurrence defined within the sub code (e.g. 0CC) Please see Please see accompanying Recommended Sub Code List document.

Copy to C + Add Prepaid / Check-In value P (Note: Airlines should make sure that Occurrence is filed in Type C)

Migration Plan to Move Baggage Fees from F and P 10 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 For Phase 2, the Task Force proposes the envisioned end state for excess baggage filings on the piece system is to use sub codes with weight and size defined within a new weight and size table in the Services Record S5. Airlines will be able to differentiate prepaid from excess using the new “prepaid / check-in” indicator but all data will be in C Type.

See Phase 2 example migration on the following page.

Migration Plan to Move Baggage Fees from F and P 11 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Phase 2 Task Force Proposal for Excess Baggage on the Piece System – replace RFISC code for C Type filing Example C Filing (after Phase 1) Record Type Service Type Sub Code SSR Commercial Name Description 1 Description 2 S5 C 0CC BAG1 Checked Bag First B1 – First Bag Blank Record Type Service Type Sub Code Prepaid/ Check-In Sequence Fee Adv Res Occurrence Pub/ Pri Security Table S7 C 0CC P 1000 USD 25 24 hr 1-1 Pri Discounted: web, internet check-in, etc.

The data indicates the prepaid Checked Bag First is USD 25.

The occurrence here is added within the data. Example C Filing Record Type Service Type Sub Code SSR Commercial Name Weight and Size Table S5 C XX1* XBAG CHECKED BAG 12345678 Record Type Service Type Sub Code Prepaid/ Check-In Sequence Fee Adv Res Occurrence Pub/ Pri Security Tbl S7 C XX1* P 1000 USD 25 24 hr 1-1 Pri Discounted: web, internet check-in, etc. The data indicates the first additional bag is USD 25. The occurrence here is defined within the data (Occurrence). *Fictional sub code used for illustration purposes. Standard, Interlineable sub codes have yet to be defined but these will be sub codes without description attributes containing occurrence (e.g.

B1 – Checked Bag First), without description attributes containing weights (e.g. 23 - Up to 50 lb/23 kg) and without description attributes containing sizes (e.g. 6U - Up to 62 li/158 lcm). This should reduce the number of sub codes to a standard list which should contain a standardized list of sub codes (e.g. Excess Bag, Excess and Heavy Bag, Excess and Oversize Bag, Excess and Heavy and Oversize Bag, Heavy within the Allowance, Oversize within the Allowance) which can accommodate all standard bag sub code filings and be more easily managed for interline.

Replace with Standard, Interlineable Sub Codes and define weights and sizes within the weight and size table in the S5 Services Record and add occurrence within the S7 Provisions Record Weight and Size Table 12345678 Up To/ Over Weight Unit Size Unit U 32 KG 158 LCM U 70 LBS 62 LI

Migration Plan to Move Baggage Fees from F and P 12 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Data Processing and Subscriptions Impact The above plan to handle weights and sizes within the allowance requires updates to the following subscriptions documentation:
  • New Weight Size/Table in the S5 o Updates to S5 Record Layouts, Field Descriptions and Data Application o New Record Layouts, Field Descriptions and Data Application for the Weight and Size Table
  • Updates to Sub Code List as specified in accompanying Recommended Sub Code List
  • New Prepaid / Check-In Tag in the S7 o Updates to S7 Record Layouts, Field Descriptions and Data Application Finalized subscription documentation will be published with a Milestone 3 after industry review.

Migration Plan to Move Baggage Fees from F and P 13 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Chargeable Service Reservation (SSR + ASVC) For Phase 1, if airlines use the F type sub codes (e.g. 0CC) that have occurrence defined within the sub code attributes, then there is no change to the current process Example (Phase 1) SSR BAG1 in the filing is used to reserve the first bag. Any additional bags will be reserved with a different RFISC and SSR. HDQRM1A .HDQRM1S HDQ1S ZS67DG/08GH/67363547/DFW/1S/T/US 1BAGGAGE/PREMR LH0439J21APR DFWFRA HK1 1A SSRBAG1LHNN1 DFWFRA0439J21APR SSRASVCLHNN1 DFWFRA0439J21APR.C/0CC/BAG1/CHECKED BAG FIRST Note: If an airline doesn’t use an F Type sub code with occurrence defined within the sub code but rather a C Type sub code (e.g.

0GO) they may run into partner issues with downstream processes related to Reservations and EMD until those airlines and their system providers are ready for phase 2.

For Phase 2, if airlines use the C type sub codes (e.g. XX1) that have occurrence defined within data, then airlines and systems may have to bilaterally establish a method to transmit occurrence until airlines and systems implement the messaging of “Service Reference Number” as an additional data element. The absence of doing so may result in confusion when a partner sells more than one “0GO” and then doesn’t know whether it’s the first or the second occurrence of that RFISC that was sold.

An example for Phase 2 will be provided once it’s passed in resolution.

Migration Plan to Move Baggage Fees from F and P 14 Copyright © 2017 ATPCO.

All rights reserved. 2 February 2018 EMD For Phase 1, if airlines copy the F type sub codes (e.g. 0CC) to C that have occurrence defined within the sub code attributes, then there is no change to the current process for defining occurrence. There is an EMD change for defining a charge that’s prepaid versus check-in. Example (Phase 1) The RFISC is captured in the EMD and the occurrence is 1-1. EMD 7774554567891 NAME - BAGGAGE/PRE DOI-21APR17/DFW RECLOC-ABCDEF CPN A/L BRDOFF STAT ICW 1 BB DFWFRA O 7772300123456/A FOA REASON FOR ISSUANCE QTY OCC BB C-BG- -0CC FIRST CHECKED BAG 1P 1-1 RATE USD25.00 PER PIECE FEE CALC - DFW BB FRA10.00EUR10.00END BASE USD25.00 TTL USD25.00 FOP – CASH For Phase 2, if airlines use the C type sub codes (e.g.

0GO) that have occurrence defined within data, then airlines and systems may have to implement the occurrence value in the EMD. There is an EMD change for defining a charge that’s prepaid versus check-in. Example (Phase 2) The updated RFISC is captured in the EMD and the occurrence is 1-1. An example follows: EMD 7774554567891 NAME - BAGGAGE/PRE DOI-21APR17/DFW RECLOC-ABCDEF

Migration Plan to Move Baggage Fees from F and P 15 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 CPN A/L BRDOFF STAT ICW 1 BB DFWFRA O 7772300123456/A FOA REASON FOR ISSUANCE QTY OCC BB C-BG- -XX1 CHECKED BAG 1P 1-1 RATE USD25.00 PER PIECE FEE CALC - DFW BB FRA10.00EUR10.00END BASE USD25.00 TTL USD25.00 FOP – CASH Service Type on the EMD Considering that this Task Force proposal suggests eliminating Service Type P, there may be a challenge with revenue accounting a bag that is sold as pre-paid versus check-in (considering that the Service Type is being used to distinguish the two).

To resolve this issue, ATPCO proposes that systems will be able to determine whether a request is for pre-paid or check-in based on the value in the new prepaid/check-in tag (see section Data Application Questions – Differentiating between Service Type P (prepaid baggage fees) and C (baggage charges))

Migration Plan to Move Baggage Fees from F and P 16 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Excess Baggage on the Weight System All excess baggage on the weight system will be migrated from F and P as part of Phase 1. Excess baggage on the weight system occurs when the weight of all a passenger’s baggage exceeds the weight system allowance. For example, a passenger has a 20KG allowance and brings two pieces @ 15KG each (totaling 30KG). In this case, there are 10 excess kilos. The system will look to match to a filing for sub code 0DG and 10 KG excess weight per kilo and assess a charge.

Today, ATPCO C Type data application suggests that airlines file weight system charges with generic sub code 0DG. This filing also includes fee application options for how to assess a rate per kilo such as a specified amount, a specified amount per kilogram (e.g. 5 EUR per kg) or a percentage of a fare per kilogram (e.g. %1 of the highest OW fare per kg). The Task Force recognizes baggage on the weight system filed in F in two different ways. 1 Filed in F as a specified amount per tier of prepaid excess baggage. For example, tier 1 of up to 5 KG excess baggage = 5 EUR, tier 2 of up to 10 KG excess baggage = 10 EUR, tier 3 of up to 20 KG excess baggage = 15 EUR.

Example – Prepaid baggage tiers Record Type Service Type Sub Code Sequence Fee Adv Res Pub/ Pri Security Tbl S7 F 0C1 1000 EUR 125 24 hrs Pri Discounted: web, internet check-in, etc. S7 F 0C2 1000 EUR 150 24 hrs Pri Discounted: web, internet check-in, etc. The data indicates the fee for an extra 15 kg of prepaid excess baggage (i.e. 0C1) is 125 EUR and the fee for 20KG of prepaid excess baggage (i.e. 0C2) is 150 EUR. 2 Filed in F as a specified amount with a fee application of “per kg” as specified in the sub code (e.g. 0CU = ONE KILOGRAM BAGGAGE). Example – Prepaid fee per kg Record Type Service Type Sub Code Sequence Fee Adv Res Pub/ Pri Security Tbl S7 F 0CU 1000 EUR 10 24 hrs Pri Discounted: web, internet check-in, etc.

The data indicates the fee for prepaid excess baggage on the weight system is 10 EUR per kilogram. Record Type Sub Code Commercial Name Description 1 S5 0C1 UPTO33LB 15KG BAGGAGE 15 - Up to 33 lb/15 S5 0C2 UPTO44LB 20KG BAGGAGE 20 - Up to 44 lb/20 Record Type Sub Code Commercial Name Description 1 S5 0CU ONE KILOGRAM BAGGAGE 01 - 1 Kilogram

Migration Plan to Move Baggage Fees from F and P 17 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 The Task Force proposes that airlines copy their F and P filings to C as follows:
  • For tiered pre-paid baggage, copy filings from F and P to C, change to standard weight system charge sub code 0DG and add tiered baggage weights in the Weight/Unit fields.
  • For a specified amount per kilogram, copy filings from F and P to C, change to standard weight system charge sub code 0DG and add fee application.

Tiered Pre-Paid Baggage on the Weight System As part of Phase 1, the Task Force proposes to copy F and P filings to C to account for selling prepaid baggage sold as a specified amount per tier on the weight system.

After copying over the data, airlines should change the sub code to standard sub code 0DG, add tiered baggage weights in the Weight/Unit fields and double check the fee application.

Migration Plan to Move Baggage Fees from F and P 18 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Copy* F Type Filing (filed as a tier) *There may be additional geographical, cabin and fee application considerations when moving from F and P to C. For example, F Type does not have the capability to express geographies based on the journey and this capability is available in C Type. Example F Filing Record Type Service Type Sub Code SSR Commercial Name Description 1 S5 F 0C1 NBAG UPTO33LB 15KG BAGGAGE 15 - Up to 33 lb/15 kg S5 F 0C2 OBAG UPTO44LB 20KG BAGGAGE 20 - Up to 44 lb/20 kg Record Type Service Type Sub Code Sequence Fee Fee Appl Adv Res Pub/ Pri Security Tbl S7 F 0C1 0500 EUR 110 4 24 hr Pri Discounted: web, internet check-in, etc.

S7 F 0C2 1000 EUR 150 4 24 hr Pri Discounted: web, internet check-in, etc. The data indicates the fee for an extra 15KG (0C1) of prepaid excess baggage is 110 EUR and the fee for an extra 20KG (0C2) of prepaid excess baggage 150 EUR.

Example C Filing Record Type Service Type Sub Code SSR Commercial Name Description 1 S5 C 0DG XBAG WEIGHT SYSTEM CHARGE WT – Weight System Charge Record Type Service Type Sub Code Prepaid/ Check-In Sequence Fee Fee Appl Weight Unit Adv Res Pub/ Pri Security Tbl S7 C 0DG P 0500 EUR 110 4 15 KG 24 hr Pri Discounted: web, internet check-in, etc. S7 C 0DG P 1000 EUR 150 4 20 KG 24 hr Pri Discounted: web, internet check-in, etc. The data indicates the fee for an extra 15KG (sequence 500) of prepaid excess baggage is 110 EUR and the fee for an extra 20KG (sequence 1000) of prepaid excess baggage 150 EUR.

COPY TO C, change sub code, add Prepaid/Check-In tag and add Baggage weight tier

Migration Plan to Move Baggage Fees from F and P 19 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Chargeable Service Reservation (SSR + ASVC) No change to the current process. SSR XBAG in the filing is used to reserve the excess baggage. An example follows: HDQRM1A .HDQRM1S HDQ1S ZS67DG/08GH/67363547/GVA/1S/T/US 1BAGGAGE/PREMR LH0439J21APR GVAFRA HK1 1A SSROBAGLHNN1 GVAFRA0439J21APR SSRASVCLHNN1 GVAFRA0439J21APR.C/0DG/XBAG/WEIGHT SYSTEM CHARGE EMD No change to the current process.

The RFISC is captured in the EMD. An example follows: EMD 7774554567891 NAME - BAGGAGE/PRE DOI-21APR17/GVA RECLOC-ABCDEF CPN A/L BRDOFF STAT ICW 1 BB GVAFRA O 7772300123456/A FOA REASON FOR ISSUANCE QTY OCC BB C-BG- -0DG WEIGHT SYSTEM CHARGE 20 Blank RATE EUR150.00 WEIGHT FEE CALC - GVA BB FRA150.00EUR150.00END BASE EUR150.00 TTL EUR150.00 FOP – CASH

Migration Plan to Move Baggage Fees from F and P 20 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Charge Per Kilo for Pre-Paid Baggage on the Weight System As part of Phase 1, the Task Force proposes to copy F and P Type filings to C, add fee application and change the RFISC to 0DG (generic weight system sub code) to account for selling prepaid baggage sold as a charge per kilo on the weight system. Copy* F type Filing + change fee application + change RFISC *There may be additional geographical, cabin and fee application considerations when moving from F and P to C Example F Filing Record Type Service Type Sub Code SSR Commercial Name Description 1 S5 F 0CU XBAG One Kilogram Baggage 01 – one kilogram baggage Record Type Service Type Sub Code Sequence Fee Fee Appl Adv Res Pub/ Pri Security Tbl S7 F 0CU 1000 EUR 15 3 Blank Blank Blank The data indicates the charge for prepaid baggage on the weight system is 15 EUR per one kilogram baggage sold.

The fee application is defined within the sub code description.

Example C Filing Record Type Service Type Sub Code SSR Commercial Name Sub Group Description 1 Description 2 S5 C 0DG XBAG WEIGHT SYSTEM CHARGE XS – Baggage Excess WT – Weight System Charge Blank Record Type Service Type Sub Code Prepaid / Check-In Sequence Fee Fee Appl Occurrence Pub/ Pri Security Tbl S7 C 0DG P 1000 EUR 15 K Blank Pri Discounted: web, internet check-in, etc. The data indicates the fee for prepaid excess baggage on the weight system is 15 EUR per kilogram. The fee application (K = per kg) is defined within the Fee Appl data element.

Copy to C + add fee application + change sub code

Migration Plan to Move Baggage Fees from F and P 21 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Chargeable Service Reservation (SSR + ASVC) No change to the current process. SSR XBAG in the filing is used to reserve the excess baggage. An example follows: HDQRM1A .HDQRM1S HDQ1S ZS67DG/08GH/67363547/GVA/1S/T/US 1BAGGAGE/PREMR LH0439J21APR GVAFRA HK1 1A SSRXBAGLHNN1 GVAFRA0439J21APR SSRASVCLHNN1 GVAFRA0439J21APR.C/0DG/XBAG/WEIGHT SYSTEM CHARGE There is an existing request out to the IATA Reservations Working Group to add the amount sold on the weight system to the reservations message.

If airlines and systems do want to sell weight system charges per kilogram, they will need to be able to bilaterally support messaging the quantity sold until this is passed in Resolution and implemented.

EMD The RFISC is captured in the EMD. An example follows: EMD 7774554567891 NAME - BAGGAGE/PRE DOI-21APR17/GVA RECLOC-ABCDEF CPN A/L BRDOFF STAT ICW 1 BB GVAFRA O 7772300123456/A FOA REASON FOR ISSUANCE QTY OCC BB C-BG- -0DG WEIGHT SYSTEM CHARGE 5 Blank RATE EUR150.00 WEIGHT

Migration Plan to Move Baggage Fees from F and P 22 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 FEE CALC - GVA BB FRA150.00EUR150.00END BASE EUR150.00 TTL EUR150.00 FOP – CASH The IATA IEMD Task Force has published a best practice recommendation to use the quantity data element on the EMD to publish the quantity of weight system charges purchased.

Migration Plan to Move Baggage Fees from F and P 23 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Heavy and/or Oversize Bag within the Allowance on the Piece System A heavy and/or oversize bag within the allowance is a bag that is less than or equal to the free baggage allowance number on the piece system but is heavier than the allowable weight for a single piece. For example, a passenger has a 1PC allowance with one piece permitted free @ 50 lbs / 23 kgs and brings one piece @ 60 lbs /27 kgs. In this case, the bag is within the allowance but is heavy (i.e. 10 lbs / 7 kgs over).

The system will then look to match to a filing that expresses a heavy bag fee within the allowance number.

Today, for heavy and/or oversize within the allowance, ATPCO C Type data application suggests that airlines file a sub code that expresses the weight and size with no occurrence. For example, using the above 1 PC free @ 50 lbs / 23 kgs mentioned above, the airline could file a 0FM (up to 70 lbs / 32 kgs) with no occurrence to express a heavy bag within the allowance. Example –Overweight within the Allowance Filing Example (as per ATPCO guidance) Record Type Service Type RFISC (sub code) Sequence Fee Free/ Not Avail Occurrence S7 C 0FM 1000 EUR 140 Blank 3-Blank S7 C 0FM 2000 EUR 110 Blank 2-2 S7 C 0FM 3000 EUR 80 Blank 1-1 S7 C 0FM 4000 EUR 50 Blank Blank-Blank The data indicates the baggage charge for the 3rd or more excess and heavy bag is 140 EUR, the baggage charge for the 2nd excess and heavy bag is 110 EUR, the baggage charge for the 1st excess and heavy bag is 80 EUR and the baggage charge for a heavy bag within the allowance is 50 EUR (sequence 4000).

There are limitations to this approach. The first being that an airline cannot provide a unique commercial name (e.g. HEAVY WITHIN THE ALLOWANCE) because the commercial name is defined at the S5 level and applies once for all sub codes of the same type. With this approach, the same commercial name applies for heavy and in excess of the allowance as well as heavy and within the allowance. The second issue, along the same lines as the Commercial Name, is that the SSR is at the S5 level and applies once for all sub codes of the same type. This means that any reservations messaging done using SSR cannot distinguish between a heavy bag within the allowance being reserved and an excess and heavy bag being reserved.

Heavy within the Allowance sequenced higher with Blank occurrence

Migration Plan to Move Baggage Fees from F and P 24 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Task Force Proposal for Phase 1 Filing Heavy Baggage within the Allowance on the Piece System To ensure a unique commercial name and a SSR and RFISC (sub code) combination, the Task Force proposes to create new sub codes (RFISCs) to specify “heavy within the allowance”, “oversize within the allowance”, “extra heavy within the allowance” and “extra oversize within the allowance”.

When airlines decide to file prepaid heavy within the allowance charges in C, any bags that are heavy/oversize within the allowance will be filed in C using these sub codes. This means that any airlines with data filed as heavy within the allowance using the current approach will be advised to change their filings to use these new sub codes. Also, for these sub codes only (to start), airlines will file the weights and sizes within a new weight/size table.

Example F Filing Prepaid Baggage Fees for Heavy/Oversize within the Allowance The Task Force advised ATPCO there are no known airlines selling prepaid heavy/oversize baggage within the allowance in Service Type F. Example C Filing Prepaid Baggage Fees for Heavy/Oversize within the Allowance Excess and heavy baggage will still be filed with bag types containing weights and sizes within description elements. New sub codes will be used to specify heavy and oversize bags within the allowance - please see accompanying Recommended Sub Codes document. Any filings for baggage within the allowance will be filed with Blank occurrence.

ATPCO will add an edit to require that only for these sub codes a value “BlankBlank” will be populated in the occurrence fields to represent that no occurrence applies and will define in data app that these sub codes should not show up in the same “multiple pricing solutions” as excess bags.

Record Type Service Type Sub Code SSR Commercial Name Description 1 Description 2 Weight and Size Table S5 C 0FM EHBG UPTO70LB 32KG AND62LI 158LCM 32 - Up to 70 lb /32 kg 6U - Up to 62 li /158 lcm 99999999 S5 C XXX* HBAG HEAVY WITHIN PC ALLOWANCE Blank Blank 12345678 *Fictional Sub Code and SSR used for illustrative purposes. New sub codes will be created upon approval of the proposal. See attached Recommended Sub Code List for proposed attribute definitions. Weight and Size Table 12345678 Up To/ Over Weight Unit Size Unit U 32 KG 158 LCM U 70 LBS 62 LI

Migration Plan to Move Baggage Fees from F and P 25 Copyright © 2017 ATPCO.

All rights reserved. 2 February 2018 Record Type Service Type Prepaid / Check-in Sub Code Sequenc e Fee Occurrence Adv Res Security Tbl S7 C C 0FM 500 EUR 75 1-1 24 hr Discounted: web, internet check-in S7 C C XXX 1000 EUR 25 Blank-Blank 24 hr Discounted: web, internet check-in The data indicates the fee for a prepaid heavy bag within the allowance is 25 EUR. The charge for a heavy within the allowance prepaid bag up to 32 kgs and 70 lbs is 75 EUR.

Data Processing and Subscriptions Impact The above plan to handle weights and sizes within the allowance requires updates to the following subscriptions documentation:
  • New Weight Size/Table in the S5 o See accompanying S5 Record Layouts, Field Descriptions and Data Application o See accompanying Record Layouts, Field Descriptions and Data Application for the Weight and Size Table
  • First/Last Occurrence Fields o See accompanying S7 Field Descriptions and Data Application
  • Multiple Pricing Solutions o See accompanying S7 Data Application for Multiple Pricing Solutions Finalized subscription documentation will be published with a Milestone 3 after industry review.

Migration Plan to Move Baggage Fees from F and P 26 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Concurrence (Type F) vs. Baggage Selection (Types A, P and C) Baggage Allowance and Charges are different from most ancillaries in that baggage fee policies often span one or more flights on different airlines. For example, a MAN-BA-x/LHR-AA-JFK itinerary (with through-checked baggage in LON) will result in one checked baggage allowance and fee that applies from MAN all the way through to JFK. Most flight-related services apply a fee per flight. For example, a meal service fee may be applied once for MAN-LHR and then again for LON-JFK.

Considering the differences between baggage allowance and charges and other flight-related services, it is worth mentioning that there are differences between Type F and Type C in determining how to select the airline whose baggage rules apply. Type F, which was developed prior to Type C, relies on a concurrence filing that starts with the operating carrier and then looks at the portion of travel to see whether the other operating and marketing carriers concur to offering that service. With the Type F solution, it could result in multiple operating carriers and/or marketing carriers offering a baggage service.

Type C, which was implemented along with IATA Reso 302 and the US DOT/CTA reservations and disclosure, looks at the portion of travel and selects one carrier whose baggage allowance and charges rules apply. For itineraries subject to the US DOT/CTA reservation and disclosure, these governments stipulate that the first marketing carrier’s rules apply. For itineraries subject to IATA Reso 302, the most significant carrier’s rules (following a selection logic like fare selection) apply.

Airlines should educate themselves on the differences between the carrier whose rules apply when moving baggage fees from Service Type F to Service Type C. Type P is defined today to process Baggage Selection the same as Type C and there should be no difference in processing when migrating from P to C. Details regarding the carrier selection rules for Optional Services Type F are found in the ATPCO Data Application for Optional Services Concurrence Record S6 document. Details regarding the baggage selection logic rules for Type C are found in the ATPCO Baggage Allowance and Charges in Optional Services Attachments A and B.

Examples of some of the differences between Type F and C type processing in codeshare/interline scenarios follow:

  • Migration Plan to Move Baggage Fees from F and P 27 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Example 1 - International To/From US/CA (US DOT/CTA) Itinerary: Mkt Cxr =XX Mkt Cxr = XX Op Cxr = XX Op Cxr = ZZ MAN x/LHR JFK Data: Record Type Bytes 1-2 Carrier Bytes 3-5 Srvc Code Bytes 6-7 Sub Code Bytes 8-10 Flt/Tkt/Mch Byte 21 Ind/Cxr Byte 42 Concur Byte 55 S5 XX OC 0CC F I 1 Record Type Bytes 1-2 Carrier Bytes 3-5 Seq Nbr Bytes 6-12 Srvc Code Bytes 25-26 Sub Code Bytes 27-29 Group Bytes 40-42 Sub Group Bytes 43-45 Carrier Bytes 52-54 Mkt/Op Byte 55 S6 ZZ 0001000 OC 0CC Blank Blank XX M Type C Baggage Selection Result
  • Processing selects the First Marketing Carrier XX (the US DoT specifies that the first marketing carrier’s rules apply for travel to/from US)
  • Processing looks up S7 Service Type C for carrier XX MAN-JFK to determine the checked baggage allowance and charges Type F Concurrence Result
  • XX is the marketing carrier; therefore, concurrence is required from all operating carriers (ZZ and XX) to assess XX’s MAN-JFK 0CC service
  • Processing matches an applicable ZZ Record S6 specifying ZZ concurs to XX’s 0CC service. XX concurrence to itself is assumed.
  • Processing determines a XX MAN-JFK is a valid pricing solution
  • Migration Plan to Move Baggage Fees from F and P 28 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Example 2 - International Not To/From US/CA (IATA Reso 302) Itinerary: Mkt Cxr = XX Mkt Cxr = ZZ Op Cxr = XX Op Cxr = ZZ SIN x/BKK LHR Data: Record Type Bytes 1-2 Carrier Bytes 3-5 Srvc Code Bytes 6-7 Sub Code Bytes 8-10 Flt/Tkt/Mch Byte 21 Ind/Cxr Byte 42 Concur Byte 55 S5 ZZ OC 0CC F I 1 S5 XX OC 0CC F I 1 Record Type Bytes 1-2 Carrier Bytes 3-5 Seq Nbr Bytes 6-12 Srvc Code Bytes 25-26 Sub Code Bytes 27-29 Group Bytes 40-42 Sub Group Bytes 43-45 Carrier Bytes 52-54 Mkt/Op Byte 55 S6 ZZ 0001000 OC 0CC Blank Blank XX M S6 XX 0001000 OC 0CC Blank Blank ZZ M Type C Baggage Selection Result
  • Processing selects the Most Significant Carrier ZZ (as travel BKK-LON crosses from TC area 3 to TC area 2)
  • Processing looks up S7 Service Type C for carrier ZZ BKK-LHR to determine the checked baggage allowance and charges Type F Concurrence Result
  • ZZ is the marketing carrier; therefore, concurrence is required from all operating carriers (ZZ and XX) to assess ZZ’s 0CC service
  • Processing matches an applicable XX Record S6 specifying XX concurs to ZZ’s 0CC service
  • Processing determines a XX SIN-LHR is a valid pricing solution and goes to the S7 to determine the applicable fee
  • Migration Plan to Move Baggage Fees from F and P 29 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 -AND-
  • XX is the marketing carrier; therefore, concurrence is required from all operating carriers (ZZ and XX) to assess XX’s 0CC service
  • Processing matches an applicable ZZ Record S6 specifying ZZ concurs to XX’s 0CC service
  • Processing determines a ZZ SIN-LHR is a valid pricing solution and goes to the S7 to determine the applicable fee Result: A ZZ 0CC and XX 0CC solution are both considered valid. In this case, both airline’s baggage service may be offered with conflicts with Reso 302 regulations.

Migration Plan to Move Baggage Fees from F and P 30 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Airline Control of Display vs. Sale Airlines require the ability to allow the display of baggage fees (for disclosure) while limiting the locations that can sell baggage fees in the marketplace. What follows is a possible airline baggage policy with the rules for display vs. sale and how this may be coded in ATPCO Optional Services Service Type C. Example - Airline baggage policy Airline Bag Policy Rec Type Data Requirements Check-In Prepaid Disclosure S5 RFISC 0CC 0CC Booking Method None None Ticketing Method None None S7 Security Table Public: DOT disclosure Public: Benchmarking Bag Sale S5 RFISC 0GO 0GO Booking Method XBAG XBAG Ticketing Method EMD EMD S7 Security Table Private distribution: Full fare Private distribution Discounted Kiosk and Call center within 24hr Discounted: web, internet Check-in, Travel agent, reservation ticket office and call center up to 24h An example for how to file the above policy is provided on the following pages.

Migration Plan to Move Baggage Fees from F and P 31 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Example (how the above policy could be filed for Phase 1) Record Type Service Type Sub Code SSR EMD TYPE S5 C 0CC ABAG 2 (Associated to a flight coupon) Record Type Service Type Sub Code Sequence Free/ Not Avail FBA Note Text S7 A 0DF 1000 F 1 Blank Record Type Service Type Prepaid / Check-In Sub Code Sequence Fee Occurrence Pub/ Pri Adv Res Security Table S7 C P 0CC 0001000 EUR 50 1-1 P 24 H S7 C P 0CC 0002000 EUR 50 1-1 Blank 24 H Table 183 Data Trvl Agt Byte 22 Cxr/ GDS Bytes 23-25 Duty Bytes 26-27 Geo Spec Bytes 28-33 Code Bytes 40-48 Vw/B k/Tkt Byte 49 Blank Blank Blank Blank A RES 1 Blank XX Blank Blank A WEB 1 Blank XX Blank Blank X ECHECK 1 X Blank Blank Blank Blank 1 Table 183 Data Trvl Agt Byte 22 Cxr/ GDS Bytes 23-25 Duty Bytes 26-27 Geo Spec Bytes 28-33 Code Bytes 40-48 Vw/Bk/ Tkt Byte 49 Blank Blank Blank A 1,2,3 Blank 2

Migration Plan to Move Baggage Fees from F and P 32 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 S7 C C 0CC 0005000 EUR 90 1-1 P Blank S7 C C 0CC 0006000 EUR 90 1-1 Blank Blank The data represents the above airline baggage policy. Sequences 1000 and 2000 represent the prepaid baggage fees and sequences 5000 and 6000 represent the checked baggage fee. Sequence 1000 is privately distributed and may be displayed/booked/sold at the airline reservation ticket office, at the airline website, at internet check-in or through a travel agent. Sequence 2000 is publicly distributed and available for display only at all points of sale (because Pub / Private is value Blank) Sequence 5000 is privately distributed and may be displayed/booked/sold at the airline call center and the airline kiosk.

Sequence 6000 is publicly distributed and may be displayed by all points of sale but can only be sold by sky team alliance airlines.

There isn’t a way today to specify “all airlines” in the carrier field of the Security Table. ATPCO proposes relaxing the edits to permit carrier “YY” to mean “any carrier” to help ease the coding to permit partner sale of baggage fees. See accompanying Tbl183_dapp_C_RetireF for details. The following (highlighted) is proposed to be added to S7 Baggage in Optional Services field descriptions and data application. Processing Scenarios (using the above airline display filing) Scenario 1 – CDG-XX (XX op)-ATL for a passenger at an online travel agency at time of passenger ticketing that requires disclosure of first and second checked bag fee on the passenger ticket.

Result: Processing resolves to C | C | 0CC | 0006000 and discloses the EUR 90 fee. (Note: Systems may choose to offer the C | P | 0CC | 1000 prepaid offer but should likely advise shoppers that this fee can only be booked and sold through specific locations). Scenario 2 - CDG-XX(ZZ op)-ATL passenger looking to purchase 1 excess bag at time of passenger ticketing for pricing on airline XX’s website. Table 183 Data Trvl Agt Byte 22 Cxr/ GDS Bytes 23-25 Duty Bytes 26-27 Geo Spec Bytes 28-33 Code Bytes 40-48 Vw/Bk/ Tkt Byte 49 Blank *S Blank Blank Blank 1 Blank Blank Blank A 1,2,3 Blank 2 Table 183 Data Trvl Agt Byte 22 Cxr/ GDS Bytes 23-25 Duty Bytes 26-27 Geo Spec Bytes 28-33 Code Bytes 40-48 Vw/Bk/ Tkt Byte 49 Blank XX Blank Blank X KIOSK 1 Blank XX Blank Blank X CALLC 1

Migration Plan to Move Baggage Fees from F and P 33 Copyright © 2017 ATPCO. All rights reserved. 2 February 2018 Result: Processing resolves to C | P | 0CC | 1000 and applies the EUR 50 fee. Scenario 3 - CDG-XX(ZZ)-ATL at time of passenger check-in at XX kiosk. Result: Processing resolves to C | C | 0CC | 5000 and applies the EUR 90 fee. Scenario 4 - ATL-XX(ZZ)-x/AMS-ZZ(ZZ)-NCE at time of passenger check-in at partner ZZ kiosk. ZZ is a sky team partner. Result: Processing resolves to C | C | 0CC | 6000 and applies the EUR 90 fee.

  • Data Processing Impact Updates to the Security Table 183 to accommodate airline requirement to specify Carrier/GDS wildcards for all carriers within an alliance (e.g. *S) and all carriers (YY)
  • Please see accompanying Security Table 183 Field Descriptions and Data Application documents
Next part ... Cancel