Migration Plan to move Baggage Fees from F and P

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.