Filing ZED/MIBA Fares Reference Manual

Transcription

1 Filing ZED/MIBA Fares Reference Manual Version June Airline Tariff Publishing Company. All rights reserved.

2 Filing ZED/MIBA Fares Reference Manual 1. Introduction Disclaimer Assumptions Fare Basis Code, Ticket Designators, and Tour Code Fare Basis Codes Fare Type and Passenger Type Codes Filing Requirements Applicable Rule Categories Third-Party Ticketing Appendix A: Glossary Appendix B: Things You Need To Know Appendix C: ATPCO Fare By Rule Tariffs Appendix D: ATPCO Fare Rule Categories ZED/MIBA Instruction Filing Template February 2014

3 1. Introduction The ZED/MIBA Working Group has identified the need to automate the pricing of ZED/MIBA fares. This automation can best be accomplished by using ATPCO Fare By Rule (Category 25) because filing individual ZED/MIBA fares in every market would be burdensome to implement, costly, and time-consuming to maintain. Category 25 enables ZED/MIBA fares to be filed using the mileage table with a specified fare associated to the mileage. Category 25 results in much fewer initial filings and literally no maintenance when markets are added or dropped. This document describes how to file ZED/MIBA fares using Category 25. Note that some GDSs may not yet process all the Category 25 data required for ZED/MIBA fares, or may process some Category 25 and other ATPCO rule category data slightly differently than other GDSs. All ZED/MIBA airlines are urged to contact the GDS that will be processing their ZED/MIBA fare data to ensure the processing is compliant with ATPCO Category 25 data application. Category 25 is a part of the ATPCO FareManager Rules System. Full automated functionality for other restrictions is available in the system, but this document will only address the core ZED/MIBA provisions. Data is organized in the ATPCO system in distinct rules based on the carrier with whom you have an agreement. For example, carrier XX has an agreement with carrier BB for BB employee travel on carrier XX, the rule number for that agreement would be XXBB. When BB is filing their Category 25 fares for XX employees, the rule number would be BBXX. In an alliance agreement where all carriers within the alliance receive the same discount level, one rule could be used with a descriptive rule assignment. 2. Disclaimer All fare rule data in this document is fictitious and is provided solely for illustration of examples for coding Category 25 ZED/MIBA fares. Fare levels are provided to ATPCO by the ZED/MIBA Working Group. The accuracy of these fare levels should be verified with msc@zedmiba.org before data is released. 3. Assumptions Airline analysts using this manual are knowledgeable in ATPCO Rules system and are familiar with ATPCO FareManager screens and how to input data. All ZED/MIBA airlines will file ZED/MIBA fares using the fare basis codes, fare levels, and passenger type codes defined in this document. ZED segments will be booked with airline code, flight number and date. Segment status will vary by GDS, but in all cases will result in status box of paper or electronic ticket as SA for space available ZED fares and HK for positive space ZED fares. MIBA fares apply only for MM positive space confirmed travel at 0.00 fare and for space available 0.00 fare. MIBA segments will be booked with airline code, flight number, and date. Segment status will vary by GDS, but in all cases will result in the Status box of the paper or electronic ticket showing MM for space available MIBA fares and MM for positive space MIBA fares. 2 5 February 2014

4 ZED/MIBA travel will be in the economy cabin and business class cabin as agreed bilaterally, and RBD used will be according to the transporting airline s rules. ZED/MIBA fare filings do not validate eligibility. Each carrier is responsible for filing and maintaining their own ZED/MIBA fares for travel by employees of another carrier where a ZED/MIBA contract has been agreed. ZED/MIBA fare levels are base amounts only. All interlineable applicable taxes, fees, and charges will be applied. ZED/MIBA fares are only combinable with themselves and other carrier ZED/MIBA fares where a formal agreement has been established. See the chart on page 41. ZED/MIBA fares are direct through flights with the same flight number and no change of aircraft. If a carrier wishes to permit only non-stop flights, this must be specified in Category 4 (Flight Application). ZED/MIBA fares are charged on a per-sector basis. Connections may be booked; however, each flight segment will be charged separately for taxes, fees, and charges for connections. ZED/MIBA mileage calculation is based on TPM (Ticket Point Mileage). If direct flights are permitted, the calculation starts at the origin of the segment and stops at the destination of the segment; in such cases mileage for intermediate flag stops or flight interruptions are not calculated. Security for ZED/MIBA fares will be coded in Category 15 (Sales Restrictions) or a Category 35 Security Table. Use of an account code will be optional. If used, each airline must advise of the codes used. 4. Fare Basis Code, Ticket Designators, and Tour Code (per IATA-agreed standards) Fare Basis Codes Fare Basis Codes are a maximum of eight characters. ZED Fare Basis Code (Adult and Child) Y IDZ H 1 R 2 1 = Confirmed space; 2 = Standby R = Eligible person of authorizing airline Mileage zone number (1 through 9, or 0 for infants only) ZED fare level (H-High, M-Medium, L-Low, or I for infants) Z = Zed fare adult and infant; C = Zed fare child Interline Discount Class of service (Y= Economy, C = Business) 3 5 February 2014

5 MIBA Fare Basis Code (0.00 fares) Y ID00 S 1 1 = Confirmed Space; 2 = Space Available Same carrier/other Airline (S = same carrier; B = Other Airline) 0 = 0.00 fare level 0 = 0.00 fare identifier Interline Discount Class of service (Y = Economy, C = Business) Ticket Designators will be coded as the passenger type code (PTC) assigned by the carrier. Please see the list of all applicable ZED/MIBA passenger types that are defined in Section 6 of this document. For example, ZEA passenger type would be coded as ZEA ticket designator. Fare basis YIDZH1R2 with ZEA as the ticket designator would be displayed as YIDZH1R2/ZEA. Tour Codes Tour code information will be placed in Category 27 (Tours) in free-form text. The agent must manually enter the tour code on the ticket. Please see tour code box format below for more information on how to format tour codes. Tour Code Box Format Character Description 1 to 7 Seniority Employment Date in DDMMMYY format, (e.g. 01JUL76). Airlines unable or unwilling to enter date of employment must use the fictitious date of 00MMM00. 8 to 9 Two-character airline designator identifying the member airline (not the designator of any airline S/A/F) 10 and 11 Two-character (numeric) code describing the type of rebate. 01 DHC, Deadheading Crew 06 Duty Travel Confirmed 10 Duty Travel Space Available 07 Personal Travel Firm (Bookable) 12 Personal Travel Standby 12 One alpha character describing whether the employer is the member airline (character A) or an S/A/F (characters B and onward) 13 Spare, optional one character for carrier s own use 4 5 February 2014

6 Examples of Tour Code Tour Code 01JUL96LH01B 08SEP88SK06A 10DEC85AA12A Explanation Crew member (employment date of 1 July 1996) of LH 100percent owned scheduled airline on non-offloadable crew transfer Staff member (employment date of 8 September, 1988) of SAS (not an S/A/F) on bookable/firm duty travel Staff member (employment date of 10 December, 1985) of AA (not an S/A/F) on standby personal travel 5 5 February 2014

7 5. Fare Basis Codes All Fare Basis Codes are to be used with below formats. Please refer to the ZED and/or MIBA agreement for the most current levels. ZED Space Available Economy Class ADULT LOW LEVEL ZED MEDIUM LEVEL ZED HIGH LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES FARE CLASS/TKT DES YIDZL1R2 YIDZM1R2 YIDZH1R YIDZL2R2 YIDZM2R2 YIDZH2R YIDZL3R2 YIDZM3R2 YIDZH3R YIDZL4R2 YIDZM4R2 YIDZH4R YIDZL5R2 YIDZM5R2 YIDZH5R YIDZL6R2 YIDZM6R2 YIDZH6R YIDZL7R2 YIDZM7R2 YIDZH7R YIDZL8R2 YIDZM8R2 YIDZH8R YIDZL9R2 YIDZM9R2 YIDZH9R2 The standard ZED child fare is calculated at 67% of the accompanying ZED adult fare amount. CHILD LOW LEVEL ZED MEDIUM LEVEL ZED HIGH LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES FARE CLASS/TKT DES YIDCL1R2 YIDCM1R2 YIDCH1R YIDCL2R2 YIDCM2R2 YIDCH2R YIDCL3R2 YIDCM3R2 YIDCH3R YIDCL4R2 YIDCM4R2 YIDCH4R YIDCL5R2 YIDCM5R2 YIDCH5R YIDCL6R2 YIDCM6R2 YIDCH6R YIDCL7R2 YIDCM7R2 YIDCH7R YIDCL8R2 YIDCM8R2 YIDCH8R YIDCL9R2 YIDCM9R2 YIDCH9R2 6 5 February 2014

8 ZED Space Available Business Class ADULT LOW LEVEL ZED MEDIUM LEVEL ZED HIGH LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES FARE CLASS/TKT DES CIDZL1R2 CIDZM1R2 CIDZH1R CIDZL2R2 CIDZM2R2 CIDZH2R CIDZL3R2 CIDZM3R2 CIDZH3R CIDZL4R2 CIDZM4R2 CIDZH4R CIDZL5R2 CIDZM5R2 CIDZH5R CIDZL6R2 CIDZM6R2 CIDZH6R CIDZL7R2 CIDZM7R2 CIDZH7R CIDZL8R2 CIDZM8R2 CIDZH8R CIDZL9R2 CIDZM9R2 CIDZH9R2 The standard ZED child fare is calculated at 67% of the accompanying ZED adult fare amount. CHILD LOW LEVEL ZED MEDIUM LEVEL ZED HIGH LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES FARE CLASS/TKT DES CIDCL1R2 CIDCM1R2 CIDCH1R CIDCL2R2 CIDCM2R2 CIDCH2R CIDCL3R2 CIDCM3R2 CIDCH3R CIDCL4R2 CIDCM4R2 CIDCH4R CIDCL5R2 CIDCM5R2 CIDCH5R CIDCL6R2 CIDCM6R2 CIDCH6R CIDCL7R2 CIDCM7R2 CIDCH7R CIDCL8R2 CIDCM8R2 CIDCH8R CIDCL9R2 CIDCM9R2 CIDCH9R2 7 5 February 2014

9 ZED Confirmed Space Economy Class ADULT LOW LEVEL ZED MEDIUM LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES YIDZL1R1 YIDZM1R YIDZL2R1 YIDZM2R YIDZL3R1 YIDZM3R YIDZL4R1 YIDZM4R YIDZL5R1 YIDZM5R YIDZL6R1 YIDZM6R YIDZL7R1 YIDZM7R YIDZL8R1 YIDZM8R YIDZL9R1 YIDZM9R1 The standard ZED child fare is calculated at 67% of the accompanying ZED adult fare amount. CHILD LOW LEVEL ZED MEDIUM LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES YIDCL1R1 YIDCM1R YIDCL2R1 YIDCM2R YIDCL3R1 YIDCM3R YIDCL4R1 YIDCM4R YIDCL5R1 YIDCM5R YIDCL6R1 YIDCM6R YIDCL7R1 YIDCM7R YIDCL8R1 YIDCM8R YIDCL9R1 YIDCM9R1 8 5 February 2014

10 ZED Confirmed Space Business Class Fares ADULT LOW LEVEL ZED MEDIUM LEVEL ZED ZONE MILES FARE CLASS/TKT DES FARE CLASS/TKT DES CIDZL1R1 CIDZM1R CIDZL2R1 CIDZM2R CIDZL3R1 CIDZM3R CIDZL4R1 CIDZM4R CIDZL5R1 CIDZM5R CIDZL6R1 CIDZM6R CIDZL7R1 CIDZM7R CIDZL8R1 CIDZM8R CIDZL9R1 CIDZM9R1 9 5 February 2014

11 MIBA Economy Class Fares LOW LEVEL MEDIUM LEVEL HIGH LEVEL ZONE MILES FARE BASIS FARE BASIS FARE BASIS YIDML1S1 YIDMM1S1 YIDMH1S YIDML2S1 YIDMM2S1 YIDMH2S YIDML3S1 YIDMM3S1 YIDMH3S YIDML4S1 YIDMM4S1 YIDMH4S YIDML5S1 YIDMM5S1 YIDMH5S YIDML6S1 YIDMM6S1 YIDMH6S YIDML7S1 YIDMM7S1 YIDMH7S YIDML8S1 YIDMM8S1 YIDMH8S YIDML9S1 YIDMM9S1 YIDMH9S1 MIBA Business Class Fares LOW LEVEL MEDIUM LEVEL HIGH LEVEL ZONE MILES FARE BASIS FARE BASIS FARE BASIS CIDML1S1 CIDMM1S1 CIDMH1S CIDML2S1 CIDMM2S1 CIDMH2S CIDML3S1 CIDMM3S1 CIDMH3S CIDML4S1 CIDMM4S1 CIDMH4S CIDML5S1 CIDMM5S1 CIDMH5S CIDML6S1 CIDMM6S1 CIDMH6S CIDML7S1 CIDMM7S1 CIDMH7S CIDML8S1 CIDMM8S1 CIDMH8S CIDML9S1 CIDMM9S1 CIDMH9S1 If you have a user ID and password for the ZED/MIBA site at zedmiba.org, you can access it for the most current levels, which are updated annually in October. Send any questions about ZED/MIBA fares to msc@zedmiba.org February 2014

12 6. Fare Type and Passenger Type Codes Fare Type (FTC): PST for ZED/MIBA confirmed fares; PU for ZED/MIBA Standby fares Carriers must specifically state which passenger types they wish to use if instructing ATPCO to code. Passenger Type Codes (PTC) are as follows: PTC Description PTC text translation Leisure ZCO Children of employee/retiree over 23 years of age (24 and over) ZCO = ZED Children Over 23 years of age ZCS Common-law spouse (includes same-sex and opposite sex) ZCS = ZED Common-law Spouse of Employee ZCU Children of employee/retiree from 21 to under 24 years of age ZCU = ZED Children Under 24 years of age ZEA Employee, retiree, spouse, and children from 12 to under 24 years ZEA = ZED Employee Adult of age ZEC Children of employee/retiree from 2 to under 12 years of age ZEC = ZED Employee Child ZEF Employee/retiree family members ZEF = ZED Employee/Retiree Family Members ZEI Infant of employee/retiree from 0 to under 2 years of age ZEI = ZED Employee Infant ZEP Parents of employee/retiree ZEP = ZED Employee Parent/Retiree Parent ZES Employee/retiree sibling ZES = ZED Employee/Retiree Sibling ZNN Young person ZNN = ZED Young Person ZPA Accompanied travel partner of employee/retiree Adult ZPA = ZED Adult Travel Partner of Employee/Retiree ZPC Accompanied travel partner of employee/retiree Child ZPC = ZED Child Travel Partner of Employee/Retiree ZPU Partner unaccompanied ZPU = ZED Partner Unaccompanied ZSO Common-law spouse of employee/retiree, registered, opposite sex ZSO = ZED Common-law Spouse, Opposite sex ZSP Spouse (includes legal and common-law) ZSP = ZED Spouse ZSS Common-law spouse of employee/retiree, registered, same sex ZSS = ZED Common-law Spouse, Same sex Duty AST Active employee standby travel AST = Staff on Duty Standby STA Active employee confirmed travel STA = Staff on Duty with Reservation Dead Head Crew DHC Active crew confirmed travel DHC = Crew Staff with Reservation on dead head positioning June 2016

13 The following PTCS were voted to be removed from the ATPCO Fares Filing Guide (but still available to use) PTC Description PTC text translation ZED When all ZED eligible persons have the same level discount ZED = Zonal Employee Discount ZPS Parents of single employee/retiree ZPS = ZED Parent of Single Employee ZPM Parents of married employee/retiree ZPM = ZED Parent of Married Employee ZSA Sisters/brothers of single employee/retiree ZSA = ZED Sibling Adult of Single Employee ZMA Sisters/brothers of married employee/retiree ZMA = ZED Sibling Adult of Married Employee ZWA Widows/widowers of employee/retiree ZWA = ZED Widow/Widowers Adult of employee Note: It is the responsibility of the ticketing agent or agent-less front-end software to validate that the passenger requesting the ZED fare is eligible to travel under the ZED agreement. Example: Carrier XX has an agreement with carrier CC for carrier CC employee parents. When carrier CC is issuing the ticket, it is carrier CC s responsibility to validate that the CC parent is eligible to fly on XX June 2016

14 7. Filing Requirements Each ZED/MIBA fare for each ZED/MIBA agreement and applicable PTC requires filing Fare By Rule Index and all applicable categories pertinent to the ZED/MIBA fare. The filing carrier needs to file ZED/MIBA fares in all applicable tariffs where the carrier provides scheduled service. (See Appendix C for a list of applicable tariffs.) S/A/F (subsidiary, affiliate, franchise) carriers that market flights independently from their parent airline must file their ZED/MIBA fares (or arrange to have them filed for them) within the tariffs of their marketing/parent carrier. The S/A/F ZED/MIBA fares will be distinguished from the marketing/parent carrier ZED/MIBA fares by using the Operating Carrier fields in Category 4. Security (who may sell and ticket the fares) may be filed in Category 15 or Category 35. Category 35 can limit access to specific ticketing locations by using Security Table 983 (such as LINIATA, department code, or other mutually agreed-upon fields). It is the responsibility of the authorizing airline to direct their employees and the employees of their S/A/F partners to the appropriate ticketing locations. Category 35 should be used for security purposes only. The screens below illustrate how to file ZED/MIBA fares. There are two options for filing your ZED/MIBA data in ATPCO, depending on how you organize your data and how many passenger types you use. Please review both options and then pick the most efficient method when filing data in ATPCO June 2016

15 Option 1 This coding method is more efficient when a carrier requires only a few passenger types. The process for filing ZED/MIBA fares is listed below. G30: Data distribution (send only to the appropriate GDS for the carrier stated in the ZED/MIBA agreement) Fare By Rule Index: Passengers (including primary and secondary) are required; however, optional features include adding specific geographic locations and account codes Category 25: Mileage table and fares for passengers Category 15/35: Security Category 19: Secondary passenger types for children and infant fares June 2016

16 Fare By Rule Index (Record 8) One Fare By Rule Index will be needed for each primary passenger type. Code the primary passenger type in the Passenger Type field. If you are using Category 35 for security information, then you must select the Negotiated Fares (35) box June 2016

17 Within the Fare by Rule Index, each record ID must have a passenger. Specify primary passenger type. Specify, if applicable, the account code and geographic application. Specify children/infant secondary passenger types in the Category discounts section. You must include any passenger type that is coded in Category 19. If passengers are coded in Categories 19 22, they must be coded in Fare By Rule Index June 2016

18 Fare By Rule (Category 25) Record 2: Primary Passengers Fare By Rule (Category 25) Category Control (Record 2) is where the Geographic locations are coded June 2016

19 Fare By Rule (Category 25): Data Table Stringing In Fare By Rule (Category 25), each THEN is coded for one passenger, followed by the OR for all the mileage parameters, including the additional fare calculation/resulting fare information. For each new passenger type you must start with a THEN and follow with an OR for all the mileage parameters, including the additional fare calculation/resulting fare information. Hint: For many passenger types with the same fare level amount, see the Option 2 All Other Discounts (Category 22) screens later in this document. Refer to Section 8 for more information on how to code them. Each THEN/OR table has one associated screen. Contained on this screen are the The Passenger Type Code. Fare Calculation information: K Specified in Alternate Currency, the Fare Level, Currency, and Mileage Band, and the Resulting Fare Information, as shown below. If you are using Category 35 for security information, the display type must be marked as Selling Fare June 2016

20 Category 25 overrides are not coded for ZED/MIBA fares. ZED/MIBA is filed as specified fare amounts; therefore, all rule conditions are specified in the ZED/MIBA rule because there are no base fares to start with June 2016

21 Category 19: Secondary passengers Category 19 Sequence List is where you create a sequence for child/infant passengers June 2016

22 Category 19: Data Table Stringing Specify separate tables for each child/infant passenger type, making sure the tables are linked with an OR relational indicator June 2016

23 Category 19: Discount Information Screen for ZED Child Code Child passenger type with age requirement. Calculate 67 percent of primary passenger type that is coded in Category 25. Code a separate table, connected with OR, referencing each ZED adult fare class in the fare calculation box. Also, in the same table under Resulting Fare, code the applicable Child fare class that is based on the adult fare class code. Code Ticket Designator to be the same as Passenger Type. Code each ZED adult fare class code here for each associated mileage band. Only one fare class code per table is allowed. Code all tables for each mileage band, and link with OR. Code each corresponding ZED child fare class code in the resulting fare class code field. EX: Code YIDCL1R2 in resulting fare class when YIDZL1R2 is in base code June 2016

24 Category 19: Accompanying Passenger Screen for ZED Child Code that the child must be accompanied on all flights/same compartment by the primary accompanying passenger coded in Category June 2016

25 Category 19: Discount Information Screen for ZED Infant Code Infant passenger type with age requirements. Select the No Charge check box in the 1 st Amount field. Code the resulting Fare Class Code as YIDZI0R1 or YIDZI0R2 for economy class fares. Code the resulting Fare Class Code as CIDZI0R2 for business class fares. Code Ticket Designator to be the same as Passenger Type June 2016

26 Category 19: Accompanying Passenger Screen for ZED Infant Code that the infant must be accompanied on all flights/same compartment by the primary accompanying passenger coded in Category June 2016

27 Option 2 This coding method is more efficient when a carrier requires many passenger types (excluding children/infant) that are all filed at the same fare levels. The process for filing ZED/MIBA fares is listed below. G30: Data distribution (send only to the appropriate GDS for the carrier stated in the ZED/MIBA agreement) Fare By Rule Index: Passengers (including primary and secondary) are required; however, optional features include adding specific geographic locations and account codes Category 25: Mileage table and fares for primary passenger Category 15/35: Security Categories 19 22: Secondary passenger types for children and infant fares, and secondary passengers (excluding children/infant) that are calculated at 100 percent of the primary passenger June 2016

28 Fare By Rule Index One Fare By Rule Index will be needed for each primary passenger type. Code the primary passenger type in the Passenger Type field. If you are using Category 35 for security information, then you must select the Category 35 checkbox June 2016

29 Within the Fare By Rule Index, each record ID must have a PTC. Code primary passenger type. Code, if applicable, the account code and geographic application. Code children/infant secondary passenger types and secondary passengers that are calculated at 100 percent of the primary passenger in the Category Discounts section. You must include any passenger type that is coded in Categories Secondary passengers are coded here. If passengers are coded in Categories 19 22, they must be coded here also June 2016

30 Category 25 Record 2: Primary Passengers Fare By Rule (Category 25) Sequence List is where the Geographic locations are coded June 2016

31 Fare By Rule (Category 25): Relational Indicators In Fare By Rule (Category 25), each THEN is coded for one passenger, followed by the OR for all the mileage parameters, including the additional fare calculation/resulting fare information and mileage. The system automatically assigns the relational indictor for you June 2016

32 Category 19: Secondary passengers Category 19 Sequence List (Record 2) is where you create a sequence for child/infant passengers June 2016

33 Category 19: Relational Indicators Code separate tables for each child/infant passenger type. Link the tables with OR June 2016

34 Category 19: Discount Information Screen for ZED Child Code Child passenger type with age requirement. Calculate 67 percent of primary passenger type that is coded in Category 25. Code a separate table, connected with OR, referencing each ZED adult fare class in the fare calculation box. Also, in the same table under Resulting Fare, code the applicable Child fare class that is based on the adult fare class code. Code Ticket Designator to be the same as Passenger Type. Code each ZED adult fare class code here for each associated mileage band. Only one fare class code per table is allowed. Code all tables for each mileage band and link with OR. Code each corresponding ZED child fare class code in the resulting fare class code field. EX: Code YIDCL1R2 in resulting fare class when YIDZL1R2 is in base code June 2016

35 Category 19: Accompanying Passenger Screen for ZED Child Code that the child must be accompanied on all flights/same compartment by the primary accompanying passenger coded in Category June 2016

36 Category 19: Discount Information Screen for ZED Infant Code Infant passenger type with age requirements. Select No Charge in the 1 st Amount field. Code the resulting Fare Class Code as YIDZI0R1 or YIDZI0R2 for economy class fares. Code the resulting Fare Class Code as CIDZI0R2 for business class fares. Code Ticket Designator to be the same as Passenger Type June 2016

37 Category 19: Accompanying Passenger Screen for ZED Infant Code that the infant must be accompanied on all flights/same compartment by the primary accompanying passenger coded in Category June 2016

38 Category 22: Sequence List Category 22 Sequence List is where you create a sequence for the secondary passengers with the same fare levels as the primary passenger. Note: Children/Infant secondary passengers must be coded in Category June 2016

39 Category 22: Discount Information Screen Code the passenger types for secondary passengers. (Child/Infant secondary passenger types must be coded in Category 19.) Calculate 100 percent of the primary passenger type coded in Category 25. Code Ticket Designator with the secondary passenger type June 2016

40 Category 22: Accompanying Passenger Screen If the secondary passenger must be accompanied by the primary passenger, code restrictions on this screen. If no restrictions apply, leave it blank June 2016

41 Categories 15 and 35 Security Security, as agreed upon by the Authorizing/Transporting carrier, can only be coded to be allowed with the Publishing carrier and another carrier or carriers and if applicable departments apply within the carrier. Specific ticketing locations, duty codes, and/or LNIATA are not permitted. Security information can be coded in either category. If you are instructing ATPCO to input data, please specify in which category you want security coded. Ensure that the applicable GDS processes the agreed-upon fields. Example: Airline XX staff only, with department code EMPTRVL and duty code 7, can access airline BB s ZED/MIBA fares. How do I decide which category to use for security? Category 15 will accommodate your needs if you want to allow the publishing carrier (you) and another carrier to view and sell your fares. Example: Publishing carrier XX and carrier ZZ can sell the fares. Category 35 should be used if carrier ZZ had only certain departments in their organization permitted to sell the fare. Example: Publishing carrier XX can sell the fare and carrier ZZ department ABC can sell the fare. Category 15 has edits in place which will not allow the user to code security restrictions for other than the publishing carrier that defines internal departments in their company February 2014

42 8. Applicable Rule Categories The chart below is just a guideline of how to instruct ZED/MIBA fares for all other applicable categories. These are just guidelines and are not intended as an instruction. Note: All categories in bold are required categories and should be coded in your ZED/MIBA rule. Category Title Data Category 50 Rule Title and Application XX/BB ZED/MIBA Fares for Standby/Confirmed Space Travel Category 1 Eligibility Eligibility for ZED/MIBA passengers plus ages and/or Account Codes Category 2 Day/Time Applicable travel days, if any, applicable to ZED/MIBA travel Category 4 Flight Application Nonstop flights or Direct flights only (based on ZED/MIBA agreement) XX marketed and operated flights only and/or XX marketed flights operated by BB Category 5 Reservations and Ticketing Reservations not permitted. Standby travel only. Category 7 Maximum Stay Code Maximum Stay for three months ISTA (interline Staff Travel Agreement) states The ticket validity shall be no more than three (3) months from the date of issue. Such validity must be shown in the "Not Valid After" box of each coupon of the ticket. Category 10 Combinations Add-ons not permitted End-on-End, Single Open Jaw, Double Open Jaw, Round Trip, Circle Trip May be combined with any YIDZ-/YIDC- type fare, or any CIDZ/CIDC- type fare, or any YID0- in the applicable tariff/rule number and for the applicable carriers. Category 11 Blackouts Any applicable embargo or blacked out travel dates for ZED/MIBA per agreement. Can be specified by geographic location and/or direction. Category 12 Surcharges General Rule does not apply Category 18 Endorsements Applicable ticket endorsement information, if any, applicable to ZED/MIBA Category 19 Child/Infant Discount Code the specific child/infant discount passenger types and discount applicable per the ZED/MIBA agreement. ATPCO will not assume which child passenger type to code. Code the specific passenger types for the person who must accompany the child/infant February 2014

43 Category Title Data Category 22 Other Discounts If multiple passenger types have the same Fare by Rule Index and Category 25 as the primary passenger type, code the first passenger type in the Fare by Rule Index and Category 25 with all the different mileage provisions, and then code the remaining passenger types in the Fare by Rule Index and Category 22 as secondary passenger type calculated at 100 percent off the primary passenger type that you have coded in Category 25. Passenger types that apply for child/infant should be coded in Category 19. Free-form text may include the following: Not valid with any other promotion, certificate, discount, award, or group travel. Award mileage accrual not permitted. Category 27 Tours Tour Code information will be placed in Category 27(Tours) in free-form text. The agent must manually enter these on the ticket. See Section 4 for tour code format information February 2014

44 9. Third-Party Ticketing Care must be taken when a transporting airline has one ZED/MIBA agreement with one authorizing airline and a different ZED/MIBA agreement with a second authorizing airline, and the second authorizing airline uses the first authorizing airline as its ZED/MIBA ticketing airline. This situation should be handled in the same way you would handle a parent airline and an S/A/F that have separate ZED agreements with a single transporting airline. For example, transporting airline TT has one ZED/MIBA agreement with authorizing airline SS and a second ZED/MIBA agreement with authorizing airline RR, and SS is RR s ZED/MIBA ticketing airline. In order to ensure that SS prices and tickets both RR s eligible persons and SS s eligible persons according to each airline s ZED agreement with TT, SS and RR must agree at which ticketing locations SS will issue ZED tickets for RR s eligible persons, and those ticketing locations must be identified to TT. Then, TT files its RR ZED fares secured to just those ticketing locations and its SS ZED fares secured to all except those ticketing locations. Ticketing locations can be defined using any mutually agreed-upon Category 35 Security Table 983 fields such as LINIATA, duty code, department code, etc., provided the GDS used by SS processes the agreed-upon bytes February 2014

45 Appendix A: Glossary authorizing airline booked eligible person GDS MIBA subsidiaries/affiliates/ franchisees (S/A/F) ticketing airline transporting airline A ZED/MIBA member through which employee discount travel benefits are derived. Unless there is an agreement for a third party to issue ZED/MIBA tickets, this is the airline that does the ticketing and, therefore, does the pricing of ZED/MIBA fares. The term booked in this document means an itinerary created in accordance with the concurrence. It does not necessarily mean that a reservation/seat is confirmed. Any person eligible for travel under the conditions of the ZED/MIBA agreement. Global distribution system. MIBA in the context of this document includes MM fares/confirmed 0.00 fares and Standby 0.00 fares. It excludes ID50. Entities related to the ZED/MIBA member that fulfill the individual respective category conditions as reflected in Appendix C of the ZED/MIBA agreement. A ZED/MIBA member that issues reduced-rate tickets to its eligible persons according to the ZED/MIBA agreement for transportation over the routes of another party (or parties) to the ZED/MIBA agreement. In the case of third-party ticketing, see Section 9. A ZED/MIBA member that transports eligible persons of the other party (or parties) according to the ZED/MIBA agreement. More specifically, this is the airline whose carrier code appears on the flights to be priced and ticketed using ZED/MIBA fares. In the case of S/A/Fs and if bilaterally permitted codeshares, this may be different from the operating airline February 2014

46 Appendix B: Things You Need To Know Keep these things in mind when you file your fares: 1. This document covers both ZED and MIBA fare filing guidelines. However, it is understood that it is only mandatory to file your ZED fares. Filing them is a ZED membership criterion. a. Filing MIBA is optional at this time, until a vote on MIBA takes place. 2. ZED Members In accordance with ZED Appendix Fares Filing, please file your fares as soon as possible. Filing must be completed within six months after publication of this guide. 3. Traffic Rights Issue If you require ticketing for non-stop segments and you don t have traffic rights on one or more of those segments, you may not be able to file a fare for those particular segments. 4. Data Collector File A grid/data collector will be created for all members on the ZED/MIBA Web site to enter the following information required by the filing airline. This data collector will be available shortly on the ZEDMIBA Web site to ensure proper filing, so please complete it as soon as possible. a. Which GDS are you using? b. If you are using an account code(s), please try to restrict to one account code per rule if possible. Account codes are not mandatory, however, some airlines use them as an option and for additional security. c. What Passenger Types will you need to be filed for you as applicable to your concurrences (e.g., specific PTC versus generic PTC)? d. If you are about to change your GDS, please advise that in the grid so the filing airline can leave the G30 open for future use. 5. It has been agreed to file only fares available for all your ticketing offices, not fares limited to specific offices. Limitation to specific offices is left to each airline as a procedural item. The exception is if you have third-party ticketing; you must agree to that bilaterally. 6. Children s fares are a pre-calculated percentage discount off the adult fare. Please see Section 5 of this document for amounts. 7. We are not using the accompanied or unaccompanied rules in fares filing, so we are applying these rules procedurally rather than with a PTC. New PTCs may be created at a later stage. 8. If you use Category 35 for your security, you must code display type L in Category 25. If you use Category 15 for your security, normal status is applied. The usage of Category 35 or 15 is the choice of each filing airline February 2014

47 9. Whom to contact if you need additional information: a. Submit questions on how to input data into ATPCO system to ServiceManager at b. Send questions on pricing or processing to your GDS account Manager. c. Send questions regarding information in this manual to the Member Service Centre at 10. A list of valid tariffs to use for creating ZED/MIBA fares are referenced in Appendix C of this document. You can direct these requests to ServiceManager at selecting Directory as the Request Type February 2014

48 Appendix C: ATPCO Fare By Rule Tariffs Tariff Definition FBRNAPV Within US/CA; Between US and CA FBRINPV Between US/CA-Area 1/2/3 FBRA1P Within Area 1 Except US/CA FBRA2P Within Area 2 FBRA3P Within Area 3 FBRA12P Between Area 1 and Area 2 Except US/CA FBRA13P Between Area 1 and Area 3 Except US/CA FBRA23P Between Area 2 and Area February 2014

49 Appendix D: ATPCO Fare Rule Categories Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 Category 12 Category 13 Category 14 Category 15 Category 16 Category 17 Category 18 Category 19 Category 20 Category 21 Category 22 Category 23 Category 25 Category 26 Category 27 Category 28 Category 29 Category 31 Category 32 Category 33 Category 34 Category 35 Category 50 Eligibility Day/Time Seasonality Flight Application Advanced Reservations and Ticketing Minimum Stay Maximum Stay Stopovers Transfers Permitted Combinations Blackout Dates Surcharges Accompanied Travel Travel Restrictions Sales Restrictions Penalties Higher Intermediate Points Ticket Endorsements Children Discounts Tour Conductor Discounts Agency Discounts All Other Discounts Miscellaneous Provisions Fare By Rule Groups Tours Visit Another Country Deposits Voluntary Changes Involuntary Changes Voluntary Refunds Involuntary Refunds Negotiated Fare Restrictions Application and Other Condition 48 5 February 2014

50 ZED/MIBA Instruction Filing Template Tariff: Carrier: Rule: Requested G30 Distribution To: (list all GDSs that apply): List the geographic location that this applies to: LOCATION 1 LOCATION 2 Does this apply in either direction or only originating from Location 1? Primary passenger List the applicable passenger type and fare class in the chart. Passenger type Fare class Mark one of the below for Routing/MPM requirements: Routing Tariff/Number Any Routing MPM Any Routing/MPM 49 5 February 2014

51 Account Code If an account code is applicable for this passenger, please list the account codes that apply to each GDS. Account code GDSs Account code GDSs Security Category 15 Category 35 CXR/GDS IATA/PCC/Office ID Secondary passengers 1. Are children discounts allowed? Yes No 2. Are infant discounts allowed? Yes No 3. Excluding child and infant, are there any other secondary passengers that have the same fare level as the primary passenger? Yes No If yes, list passenger types. Refer to section 8 for further information on guidelines concerning other rule categories (such as combinations and ticket endorsements) February 2014