Reservation Booking Designators (RBDs)

Transcription

1 Reservation Booking Designators (RBDs) How to Instruct and Code RBDs for Chart 1 and Chart 2 Updated 5 July Airline Tariff Publishing Company. All rights reserved.

2

3 Reservation Booking Designators (RBDs) Table of Contents Introduction to RBDs... 3 Mission... 5 Summary Reading the Chart Format Mission Summary Viewing RBD Data Online Mission Filter and Find functionality Filter Find Viewing all RBD Chart 1s View Chart 1 from a Fare Class in GFS Summary Creating RBD Instructions Mission Overview Restrictive capabilities Points to remember RBD Application Geography Directionality RBD Chart RBD Chart Summary Coding Conventions Mission Coding conventions Sequencing data Coding Chart Travel segment indicators Primary or Secondary on YY fares Helpful hints for coding Summary Updating RBD Data Mission Locations for Update Fare Class Application i

4 Reservation Booking Designators (RBDs) Category data tables Booking Code Exception Tables Copying an existing table Changing an existing data table number Canceling an existing table Updating an existing table RBD Chart 1 RBDs for Fare Owner and Concurring Carriers right-click menu RBD Chart 1 and Chart 2 Details forms Duplicate Sequence and Most Restrictive checks Summary Introduction to the Sequence List and Details Screens Mission Purpose of the Sequence List screen Purpose of the Details screen Summary Coding the Sequence List Screen Mission Sequence List screen Fields and values Summary Coding the Details Screen Mission Fields and values Summary Appendix A Definitions for RBDs Appendix B Chart detail information Appendix C Chart format Appendix D Non-concurring carrier list Appendix E Private Chart 1 Download Appendix F Screen images Appendix G Byte numbers and Match or Action Appendix H Subscriptions Schedule ii

5 Introduction to RBDs Where do I code my RBD provisions?

6

7 Introduction to RBDs Mission After completing this module, you will be able to explain why Reservation Booking Designators (RBDs) exist, their importance, and terminology. In addition, you will be able to identify what ATPCO offers as the single source for RBD data. Why is this module important? It is important that airline fares price correctly. In order for airline pricing analysts to instruct RBD data to ATPCO so that it will price correctly, they must know the purpose of an RBD and its importance to the industry. Carriers rely on RBDs to control inventory, thus controlling overall profits for each flight. An error in instructing may seem slight; however, this error may result in a significant amount of lost revenue for the carrier. You need to be able to identify where to code your RBD provisions in order for your global distribution system (GDS) or computer reservations system (CRS) to accurately price according to your intention. RBD data may be included within Fare Class Application, Chart 1, Chart 2, Discounts (Categories 19 22), and Fare By Rule (Category 25). This module identifies the purpose of RBD data in each of the records and categories where RBD data exists. Purpose A complex fare structure has evolved in the airline industry because of advancements in pricing analysis. Airlines determine how much it costs per passenger seat mile and seat capacity of aircraft, and competition in the markets served to determine their pricing strategy. In order to maximize pricing strategies, airlines use yield management programs to forecast, price, and control inventory. Through yield management practices, smaller units in each cabin of service allow airlines more control over their inventory. In particular, this practice affects the economy cabin, allowing an airline to sell some seats at prices to match competition and to sell other seats at a price that would still make a profit for the flight. Reservation booking designators (RBDs) are the vehicle for inventory control because they meet these needs and maximize profits at the same time. The determination of airline pricing relies heavily upon the laws of supply and demand. For example, in order to maximize profits for a particular flight, the number of seats allocated for a particular booking code may change depending on the demand for seats for that flight. The goal is to have the right mix of booking codes in order to improve load factors, thus improving profitability. Generally, a few passengers on each flight pay an unrestricted full fare; some pay a restricted full fare, and the remaining passengers pay a discounted fare with multiple restrictions. The number of restrictions associated with a fare generally equates to the discount of the fare. For example, more restrictions associated with a fare means the passenger will likely be paying a lower fare. 5

8 Introduction to RBDs ATPCO as single source provider of RBD data If you decide to have ATPCO code your RBD data, we have a standardized instruction format that looks exactly like the output, ensuring data quality. As a neutral business-to-business organization within the travel industry, ATPCO provides solutions and services that improve our customer s efficiencies in the distribution of fare-related data. For more than 50 years airlines have trusted ATPCO in this capacity, making ATPCO the world s leader in the distribution of airline fare and fare-related data. Recognized by IATA as the single source provider of RBD data, more than 500 airlines trust ATPCO for an accurate low-cost distribution method of their booking code data. Airlines rely upon RBDs for inventory management and requested that ATPCO become the single source provider of RBD data. ATPCO has been providing the airline industry an automated solution for RBDs for more than 20 years. Once you have filed your RBDs via ATPCO s Government Filing System (GFS), your RBD data is available to anyone with access to ATPCO. Additionally, your RBD data will be sent to all the major global distribution systems and computer reservation systems on a predetermined processing schedule. Features ATPCO enables you to create RBD provisions that may be automated by your GDS. The major GDSs and CRSs work with ATPCO and our customers to determine industry business needs and to develop appropriate applications to automate these industry decisions. Subscribers to ATPCO s RBD product are able to receive RBD data in each of our subscription processing times. See Appendix G for subscription processing times. If you have the ability to access ATPCO s database in your office or home, you are able to remotely update your RBD data by signing on to the FareManager Rules system. If you have questions while you are coding your RBDs or once you have filed your RBD data via GFS, contact our Customer Service department via ServiceManager at ATPCO provides training for instructing and coding RBDs at our offices or on-site at your facility. Contact Shauna Koca, Manager of Product Training at skoca@atpco.net for additional information. 6

9 Introduction to RBDs Benefits Ke speaks four lanugages.as the world s leader in the collection and distribution of farerelated data, ATPCO offers an RBD product that gives you the ability to quickly distribute changes to your booking codes. Working with the airlines and major GDSs and CRSs, ATPCO developed an automated system for processing a traditionally paper-driven function. Automation of RBD data enables ATPCO to provide a consistent output of RBD data. If you look at your RBD data in GFS, Rules, International Fares, or the Passenger Interline Pricing/Prorate System (PIPPS), your RBD data will appear the same. When you make changes to your RBD data, your private data will remain private until you file your changes in GFS. Product overview RBDs are a subset of the FareManager Rules system. In order to update your RBD provisions, you must have update authority within the FareManager Rules system. RBDs are further subdivided by the type of RBD restrictions you are creating. ATPCO classifies these different restrictions into a Chart format. Use Chart 1 when you are the airline that owns the fare. Chart 1 allows you to include RBD restrictions for primary and secondary portions of travel for your airline or another airline that allows concurrence. Use Chart 2 when another airline or YY (IATA) owns the fare. Chart 2 enables you to indicate how to book passengers traveling on your equipment for portions of travel on another carrier s fare or a YY fare. Chart 1 is further divided to clarify RBD restrictions. Fare Class Application contains a Chart 1 that applies exclusively to that specific fare class. This is also referred to as RBD Exception Table. Data tables for Discounts (Categories 19 22) contain a field to indicate the resulting prime RBD for the new discounted fare. Data tables for Fare By Rule (Category 25) contain a Chart 1 to indicate the applicable RBD for the resulting fare. Booking Code Exception Table (Chart 1) identifies how to book passengers traveling on a fare for the tariff, carrier, and rule for the Chart 1 owner or passengers traveling on a fare for any rule within the tariff and carrier for the Chart 1 owner. 7

10 Introduction to RBDs Location The Automated Structure of the RBD product consists of four main components. 1. Prime Booking Code The Prime Booking Code is located in the Fare Class Application. The Prime Booking Code is usually the first letter of the fare basis code, unless stated otherwise in a rule instruction. 2. Chart 1 RBD Exceptions Chart 1 applies to the carrier that owns the fare and contains exceptions to the prime RBD. Chart 1 data may appear in the Fare Class Application or Chart 1 RBD Exception Table. 3. Chart 2 Chart 2 applies when the fare belongs to another carrier. The Chart 2 carrier is providing transportation on another carrier s fare. 4. Category 25 RBDs are coded in Fare By Rule (Category 25) to override data for the base fare. 8

11 Introduction to RBDs Assumption Non-concurrence Today s airlines require more control over their booking and inventory. Consequently, ATPCO adapted to non-concurrence for all new customers. Non-concurrence means that publishing carriers cannot instruct on behalf of another transporting (secondary) carrier without authorization. Each non-concurring carrier takes full control and responsibility for its booking code data when that carrier provides transportation on another carrier s fare. The Concurrence Table is a directory level that only ATPCO employees may update. This table enables ATPCO to maintain concurrence between carriers based upon the following parameters: Carrier Tariff Rule number or range of rule numbers Fare type Fare class code or fare family All public tariffs All private tariffs A Concurring Carriers look-up list is available within Chart 1 to list the carriers that allow concurrence or non-concurrence for the Chart 1 within the Concurrence Table. Edits within Chart 1 prevent the coding of any carrier absent from the Concurrence Table. If the carrier is not present, the system will not allow the coded data to be validated and saved. There are frequent changes made to the non-concurring list. ATPCO maintains an up-todate list and advises the industry of changes to this list. Changes to the non-concurring list are posted in a Bulletin that are sent to data providers and subscribers. 9

12 Introduction to RBDs Table matching In order to determine whether fares are booking as intended, it is important to be able to identify the processing path of booking code data. Below is an outline of where processing will begin to look for booking code data. When processing RBD data, your GDS/CRS will pass through the records in the following order: 1. Fare Class Application (obtaining fare basis code) 2. Fare Class Application RBD Exception Table 3. Chart 1 Record 6 Rule Specific 4. Chart 1 Record 6 Default (only if no rule specific) 5. Chart 2 Record 6 for other carrier s providing transportation 6. Fare Class Application prime booking code The application of your RBD data will occur in the following order: 1. Chart 1 in Fare Class Application (RBD Exception Table), or in Fare By Rule (Category 25) 2. Chart 1 in Booking Code Exception Table (Record 6) 3. For the owning carrier, apply the prime RBD if no exceptions exist 4. For secondary portion of travel, apply RBD from transporting carrier s Chart 2 10

13 Introduction to RBDs Summary Recognized by IATA as the single source provider of RBD data, ATPCO is trusted by over 200 airlines for an accurate low-cost distribution method of booking code data. Airlines rely upon RBDs for inventory management and requested that ATPCO become the single source provider of RBD data. ATPCO enables you to create your RBD provisions that may be automated by your GDS. RBDs are a subset of the FareManager Rules system. In order to update your RBD provisions, you must have update authority within the FareManager Rules system to code your RBD data. RBDs are further subdivided by the type of RBD restrictions you are creating. ATPCO classifies these different restrictions into a Chart format. Use Chart 1 when you are the airline that owns the fare. Chart 1 allows you to include RBD restrictions for secondary portions of travel for your airline or another airline that allows concurrence. Use Chart 2 when another airline or YY (IATA) owns the fare. Chart 2 enables you to indicate how to book passengers traveling on your equipment for portions of travel on another carrier s fare. Chart 1 is further divided to clarify RBD restrictions. Fare Class Application records contain a Chart 1 that applies exclusively to that specific fare class. Details records for Categories (Discounts) contains a field to indicate the resulting prime RBD for the new discounted fare. The details record for Category 25 (Fare By Rule) contains a Chart 1 to indicate the applicable RBD for the resulting fare. Record 6 Booking Code Exception Table identifies how to book passengers traveling on a fare for the tariff, carrier, and rule for the Chart 1 owner, or any rule within the tariff and carrier for the Chart 1 owner. The Automated Structure of the RBD product consists of four main components. 1. Prime Booking Code 2. Chart 1 RBD Exceptions 3. Chart 2 4. Category 25 Non-concurrence means that other publishing carriers cannot instruct on behalf of another transporting (secondary) carrier without authorization. Each non-concurring carrier takes full control and responsibility for their booking code data when the transporting carrier provides transportation on another publishing carrier s fare. 11

14 Introduction to RBDs A Concurrence Help Screen is available within Chart 1 to list the carriers that allow concurrence within Chart 1. Edits within Chart 1 prevent the coding of any carrier absent from the Concurrence Table, unless permitted within the Concurrence Table. 12

15 Reading the Chart Format How to view RBDs in GFS and FareManager Rules

16

17 Reading the Chart Format Mission After completing this module, you will be able to identify the RBD charts and the purpose of each column located within the Charts. Why is this module important? Chart 1 and Chart 2 provide the format for displaying and reading RBDs. In order to correctly instruct and read those charts, it is important to learn about the various parts of each and how they are put together. The RBD format consists of Chart 1, which is organized by ATPCO tariff and applies to the carrier that owns the fare. Chart 2 applies to all tariffs worldwide and applies to the transporting carrier when another carrier owns the fare. In Chart 1 and Chart 2, some columns represent different data. This module discusses each chart and the type of data contained within each chart. 15

18 Reading the Chart format Fare Class Application: Prime Booking Code Every Fare Class Application contains a fare basis code and a prime booking code (except Standby fares). The prime RBD applies to the publishing carrier and all portions of travel on the fare unless otherwise specified in the Fare Class Application RBD Exception Table or in Chart 1 (RBD Exception Table). Usually, the prime RBD is the first letter of the fare basis code, unless indicated otherwise in an instruction. The only exceptions to this are when information applicable to the publishing carrier is contained within a Fare Class Application RBD Exception Table or Chart 1 (RBD Exception Table). It is important to note that the prime RBD does NOT apply to any participating carrier in a YY fare record. RBD information for YY fares must be found in Chart 2 (Default RBD Table) for the transporting carrier. The Fare Class Application prime booking code in domestic US/CA fares applies to all portions of travel unless specific exceptions are coded within the Fare Class Application RBD Exception Table. For international fares, the Fare Class Application prime RBD applies to all portions of travel on the fare for the publishing carrier unless exceptions exist. It is important to remember that the prime RBD does not apply to interline carrier transportation including YY fares where exceptions will be specified within the Default RBD Table (Chart 2) for the transporting carrier. The prime RBD may appear in GFS text as follows: Fare Class Explanation Book Codes IHKIOSK2 HIGH SEASON APEX NONREFUNDABLE FARES BETWEEN FRANCE AND SPAIN AND CANARY ISLANDS FOR ROUND TRIP FARES I Figure 1 Example of the Fare Class Application where the Prime Booking Code = I for TREUR 01 Rule TNG9 Fare Class IHKIOSK2 16

19 Reading the Chart Format Chart 1 RBD Exceptions Chart 1 applies to the carrier that owns the fares. Chart 1 contains RBD information that applies to the marketing carrier for the significant flight segment (owner of the fare), as well as secondary flight segments that may be on another carrier or the owning carrier. Chart 1 is organized by ATPCO tariff (equivalent to a geographic area). Chart 1 may apply to a specific rule number or all rules within that tariff. The Fare Class Application prime booking code will apply to the publishing carrier unless exceptions are specified in a Fare Class Application RBD Exception Table or in a Chart 1 RBD Exception Table. When an RBD Table is found in the Fare Class Application, it applies to a specific fare basis code. In Chart 1 RBD Exception Tables, the booking code exceptions may apply to all rules or specific rules within that tariff. Processing 1. The Fare Class Application RBD Exception Table takes precedence over the Chart 1 RBD Exception Table. 2. When processing a Chart 1 RBD Exception Table, first attempt to match the rule number involved. 3. If that rule number is not present, apply the Chart 1 RBD Exception Table that is 0000 (OTHR in GFS Text). 4. When neither exists, the prime booking code for the fare basis code will be applied for the publishing carrier. 5. If a carrier providing transportation is not included in Chart 1, the data will be found in the transporting carrier s Chart 2. Note: If a rule-specific Chart 1 RBD Exception Table exists when processing exceptions, the CRS/GDS will apply the information contained in that table. It will not continue reading to the OTHR table to identify other exceptions to the prime booking code. If the system is attempting to match to a carrier other than the publishing carrier, the transporting carriers Chart 2 will be examined to determine exceptions if no match is made in Chart 1. 17

20 Reading the Chart format The RBD Exceptions may appear in the FareManager Rules system as follows: Figure 2 Example of a Fare Class Application with an RBD Booking Code Exception Table. Figure 3 Example of a rule-specific RBD Exception Tables 18

21 Reading the Chart Format For travel: WAS BA LON on a BA MHEE21 fare class Chart 1 for BA Rule 3000 FARE IDENTIFIER ANY FARE ANY FARE Figure 4 LOCATIONS/FLIGHTS FLT SEGMENTS FROM PHX WAS/VV. EACH FLT SEGMENT WITHIN THE UNITED STATES Chart 1 RBD Exception Table for BA MHEE21 MKTG CXR RBD NOTE HP M REQ HP L REQ Find the applicable Chart 1 for the fare For Example: IPRA BA 3000 Does the flight segment belong to the carrier that owns the fare? Yes Search Chart 1 for applicable type fare and specific location/flight information. Is there a match? If yes, apply RBD If no, apply prime booking code of M for BA between WAS and LON. Figure 5 Processing flow chart 19

22 Reading the Chart format For travel: PHX HP WAS BA LON on a BA MHEE21 fare class. Chart 1 BA 3000 FARE IDENTIFIER ANY FARE ANY FARE LOCATIONS/FLIGHTS FLT SEGMENTS FROM PHX WAS/VV. EACH FLT SEGMENT WITHIN THE UNITED STATES Figure 6 Chart 1 RBD Exception Table for BA 3000 MKTG CXR RBD NOTE HP M REQ HP L REQ Find the applicable Chart 1 for the fare IPRA BA 3000 Does the flight segment belong to the carrier that owns the fare? No Is HP a non-concurring carrier? No Review Chart 1 for applicable type fare and specific location/flight information. Is there a match? If yes, apply RBD M between PHX and WAS on HP. Figure 7 Processing flow chart 20

23 Reading the Chart Format Chart 1 Example LH (Belongs to the carrier that owns the fare.) IPREUAS - BETWEEN EUROPE AND ASIA FARE IDENTIFIER LOCATIONS/FLIGHTS MKTG CXR RBD NOTE ALL FIRST EACH FLT SEGMENT WITHIN EUROPE LH C REQ A ALL FIRST ALL FIRST ALL FIRST FLT SEGMENTS FROM LAST POINT IN EUROPE - 1ST ARR IN MIDDLE EAST/VV FLT SEGMENTS FROM LAST POINT IN EUROPE - 1ST ARR IN AFRICA/VV FLT SEGMENTS FROM LAST POINT IN AREA 2-1ST ARR IN AREA 3/VV LH F REQ A LH F REQ A LH F REQ A C- TYPE EACH FLT SEGMENT WITHIN EUROPE LH C REQ C- TYPE FLT SEGMENTS FROM LAST POINT IN EUROPE - 1ST ARR IN MIDDLE EAST/VV C- TYPE FLT SEGMENTS FROM LAST POINT IN EUROPE - 1ST ARR IN AFRICA/VV C- TYPE FLT SEGMENTS FROM LAST POINT IN AREA 2-1ST ARR IN AREA 3/VV LH LH LH C REQ C REQ C REQ D- TYPE EACH FLT SEGMENT WITHIN EUROPE LH D REQ D- TYPE FLT SEGMENTS FROM LAST POINT IN EUROPE - 1ST ARR IN MIDDLE EAST/VV D- TYPE FLT SEGMENTS FROM LAST POINT IN EUROPE - 1ST ARR IN AFRICA/VV D- TYPE FLT SEGMENTS FROM LAST POINT IN AREA 2-1ST ARR IN AREA 3/VV LH LH LH D REQ D REQ D REQ H- TYPE EACH FLT SEGMENT LH H REQ G- TYPE EACH FLT SEGMENT LH G REQ ER TYPE EACH FLT SEGMENT WITHIN EUROPE LH C REQ Note A ALL FIRST - FU/FR/FS/FX/FRO Fare Identifier Identifies fare families, ATPCO fare type, or multiple fare types. Locations/Flights Identifies the portion of the fare that is associated to the specified RBD. MKTG CXR RBD Note Airline who is recorded on the flight coupon as the transporting carrier. Specified booking code that applies. System-assigned alpha notes that are standard across the industry. Refer to the Rules Coding Resource for definitions of the fare type codes. 21

24 Reading the Chart format Chart 2 Default RBD data Chart 2 contains RBD information for the owner of the table when the carrier is being used on a secondary sector of another carrier s fare, or on sectors for transportation on a YY fare. This chart applies to all rules, all global areas, and is not tariff restricted. These charts convey the RBD information for electronic and/or manual ticketing. For international published fares (except YY), the Chart 2 may be used for portions transported by interline carriers; not for portions transported on the owning or publishing carrier. For international YY fares, the Chart 2 may be used for all transporting carriers, even the carrier involved in the overwater or primary portion of travel. Note: YY will never have a Chart 2 because YY will never be the transporting carrier. The Default Booking Codes may appear in GFS text as follows: Chart 2 FARE IDENTIFIER ALL BUSINESS ALL BUSINESS NOTES: B ALL BUSINESS-BR/BRO/BU/BX LOCATIONS/FLIGHTS MKTG CXR RBD NOTE CO FARES B EACH FLT SEGMENT WITHIN EUROPE AF C J R/OF CO FARES B EACH FLT SEGMENT WITHIN EUROPE AF Y REQ 22

25 Reading the Chart Format For travel: PHX WN WAS BA LON Find the applicable Chart 1 for on the a fare BA MHEE21 fare class. IPRA BA 3000 Does the flight segment belong to the carrier that owns the fare? No, between PHX and WAS travel is via WN Is WN non-concurring? WN is a concurring carrier Review BA s rule 3000 Chart 1 for applicable type fare and specific location/flight information for WN. Is there a match? If no If yes Go to Chart 2 default Booking Code for WN Apply that RBD Is there a match? Yes If no Apply RBD CRS/GDS should fail the fare 23

26 Reading the Chart format Chart 2 Example LH RES BOOKING DESIGNATORS FOR LH FLIGHT SEGMENTS ON OTHER CARRIERS/YY FARES FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/FLIGHTS RBD FOR LH NOTE OAL ALL FIRST EACH FLT SEGMENT F REQ A OAL BR TYPE EACH FLT SEGMENT D REQ OAL BX TYPE EACH FLT SEGMENT D REQ OAL ALL BUSINESS EACH FLT SEGMENT C REQ B OAL ALL ECONOMY EACH FLT SEGMENT H REQ C OAL ALL EXCURSION EACH FLT SEGMENT Y REQ D OAL ALL SPECIAL EACH FLT SEGMENT Y REQ F OAL ANY OTHER FARE EACH FLT SEGMENT Y REQ Note A ALL FIRST - FU/FR/FS/FX/FRO Note B ALL BUSINESS - BU/BR/BX/BRO Note C ALL NORMAL ECONOMY- EU/ER/EAP/EIP Note D ALL EXCURSION - XEX/XPB/XPN/XPX/XAP/XAB/XAN Note F----ALL SPECIAL ECONOMY - SB/SAP/SIP Fare Owner/Publisher Fare Identifier Locations/Flights Note Carrier that owns the fare may be specified as OAL=Other Airline Excluding the publishing carrier, ANY= any carrier, or a specified carrier code excluding the publishing carrier. Identifies the fare basis code, fare family, ATPCO fare type, or multiple fare types applicable to the RBD. Applies to each flight segment in the absence of geographic data. When geographic locations are specified: applies to the last point out of the specified location to the first arrival in a location. Refer to the Rules Coding Resource guide for definitions of the fare type codes. 24

27 Reading the Chart Format Summary Every Fare Class Application contains a fare basis code and a prime booking code (except Standby fares). The prime RBD applies to the publishing carrier and all portions of travel on the fare. Chart 1 applies to the carrier that owns the fares. It contains RBD information that applies to the marketing carrier for the significant flight segment (owner of the fare) as well as secondary flight segments that may be transported by another carrier or the owning carrier. Organized by ATPCO tariff (equivalent to a geographic area), Chart 1 may apply to a specific rule number or all rules within that tariff. The Fare Class Application prime booking code will apply unless exceptions are specified in a Fare Class Application RBD Exception Table (999) or in a Chart 1 RBD Exception Table. When an RBD Table is found in the Fare Class Application, it applies to that specific fare basis code. In processing, the Fare Class Application RBD Exception Table takes precedence over the Chart 1 RBD Exception Table. When processing a Chart 1 RBD Exception Table, first attempt to match the rule number involved. If that rule number is not present, apply the Chart 1 RBD Exception Table that is 0000 (OTHR in GFS Text Menu). When neither exists, the prime booking code for the fare basis code will be applied. Chart 2 applies to the carrier that is ticketed on the secondary flight portions of another carrier s fare. It contains RBD information for the owner of the table when the carrier is being used on a secondary sector of another carrier s fare, or on sectors for transportation on a YY fare. This chart applies to all rules, all global areas, and is not tariff restricted. These charts convey the RBD information for electronic and/or manual ticketing. For international published fares (except YY), the Chart 2 may be used for portions transported by interline carriers; not for portions transported on the owning or publishing carrier. For international YY fares, the Chart 2 may be used for all transporting carriers, even the carrier involved in the overwater or primary portion of travel. It is important to know YY will never have a Chart 2 because YY will never be the transporting carrier. 25

28

29 Viewing RBD Data Online How to view RBDs in GFS and FareManager Rules

30

31 Viewing RBD data online Mission After completing this module, you will be able to view RBD data in the FareManager Rules system and Government Filing System (GFS) Text Menu. Why is this module important? In order to determine whether fares are booked in the proper booking class, it is important to be able to view booking code data in GFS text. In the GFS application, you may view RBD text for public data or your private data by selecting Fare Rule/Fare Class. Not only can you view your airline s booking code data, but you can also view any public data that has been filed in GFS. It is therefore possible for airlines to verify that their interline agreements are coded correctly when travel is provided on another airline. 29

32 Viewing RBD data online Filter and Find functionality The Filter and Find options allow you to quickly locate RBD sequences based on specific search criteria. Both options find the same data (provided the search criteria are the same). The difference is how the results are displayed. This section is expandable and collapsible depending on your preferences. It is important to note that to reset the RBD list to its default state, you should clear the Filter and Find criteria and then click the Find button, or simply click the Get Data button on the Navigation pane. Filter and Find options have become a valuable asset for lengthy RBDs. The Filter and Find options help you to research in a more timely and accurate manner. In order to use these options, you will need to access RBD Chart 1 or RBD Chart 2 in the FareManager Rules system. Step 1. On the Rules Home page Navigation Pane, choose RBD Chart 1 or RBD Chart 2 from the Select data drop-down menu. Figure 8 Rules Home screen 30

33 Viewing RBD data online Step 2. Type the Carrier, Tariff, and Rule on the Navigation Pane. Figure 9 RBD Chart 1 Navigation Pane Step 3. Click. The RBD Sequence List (grid format) appears. Figure 10 RBD Chart 1 RBD s for Fare Owner and Concurring Carriers Step 4. To access the Filter/Find features, click the next to Filter Sequence List. Figure 11 RBD Chart 1 Filter/Find field expanded 31

34 Viewing RBD data online Filter The Filter option displays only the matched sequences, as shown here. Filter Fields Result Display Figure 12 RBD Filter display 32

35 Viewing RBD data online Find The Find option displays all RBD sequences with the matching results highlighted in yellow, as shown in Figure 13. Find Fields Result Display Figure 13 RBD Find display The Filter and Find sections contain the following fields: Carrier Application RBD1 and RBD2 Fare Class/Family and Exact Match checkbox Fare Type Location 1, Location 2, and Exact Match checkbox Travel portion Direction Sequence Return entire sequence (Filter only) 33

36 Viewing RBD data online Carrier Step 1. Type the two-letter carrier code of the carrier. (In Figure 14 the code is Z7.) Step 2. Click to execute the search. Figure 14 RBD Find within Chart 1 and Chart 2 Note: For these examples, we ll use the Find in Sequence List option, which highlights the data you are searching for. When using the Filter in Sequence List option, remember that only the data you searched for will be displayed. 34

37 Viewing RBD data online Application Step 1. If you need to search for Required RBDs, type an R. Step 2. Click the button. If you are unsure of the values, click the link above the field to view a complete list of the applicable values for this field. Figure 15 35

38 Viewing RBD data online RBD1 and RBD 2 Step 1. If you need to determine what markets, fares, or other criteria, have a specific RBD that applies, type the RBD value in the RBD1 and/or RBD2 field. Step 2. Click. Figure 16 RBD1/RBD2 Fare Class/Family and Exact Match checkbox This field is used to identify the Fare Class/Family on the Sequence List. If this field is populated, the coding may indicate a specific fare class (which must exist in the Fare Class Application screen) or a fare family, which is a fare class with a hyphen in the beginning, middle or end of the fare class code. Note: When the Exact Match checkbox is selected, the Fare Class/Family field will be matched exactly. If you code MW7AP and MX7AP in the Fare Class/Family the summary text returned will look for MW7AP and MX7AP only, and will not display MW-AP or MX-AP in case a 14-day advance purchase fare is coded. Figure 17 Fare Class/Family 36

39 Viewing RBD data online Fare Type The Fare Type field is used to indicate whether the category provision applies to a certain fare type. A match to this field is made by comparing the fare type code indicated here to the Record 1. Step 1. Specify the Fare Type in the Fare Type field. If you are unsure of the values, click the link to view a complete list of the applicable values for this field. Figure 18 Fare Type 37

40 Viewing RBD data online Location 1 and Location 2 Step 1. Type the application location or click the Location 1 or Location 2 link to access the look-up list. Use the drop-down menu to choose from the following options: Area City/Airport Nation State/Province Zone Step 2. Click to execute the search. You can search on one or two location codes. Note: When the Exact Match field is populated, the Locations fields will be matched exactly. If you code LON PAR in the Locations fields and select this checkbox, the sequences returned will look for LON PAR only, and will not display GB-FR or or a sequence without Locations code. Figure 19 Locations no Exact Match Figure 20 Locations Exact Match 38

41 Viewing RBD data online Travel Portion Step 1. Specify a Travel Portion code to search for RBD data that has that Travel Portion value. For example, select Atlantic portion from the drop-down menu to search for all sequences that have the Transatlantic value coded. Step 2. Click. If you are unsure of the values, click the link to view a complete list of the applicable values for this field. Figure 21 39

42 Viewing RBD data online Direction Step 1. Specify a Direction code to search for RBD data that has that directional value. For example, select From Location 1 from the drop-down menu to search for all sequences that have From Location 1 coded. (This value also requires that a location be coded.) Step 2. Click. If you are unsure of the values, click the drop-down menu to view a complete list of the applicable values for this field. Figure 22: Found data 40

43 Viewing RBD data online Sequence Step 1. Type the sequence number. Step 2. Click to view the sequence with the specified sequence number. Figure 23: Found data Page Number This feature is located below the Filter/Find fields. Be sure to click and to remove any coding in the Filter/Find fields before using this feature. This is useful when there are multiple screens of sequences coded. Figure 24 Step 1. Enter the screen number. Step 2. Click to view the screen with the specified screen. 41

44 Viewing RBD data online Viewing all RBD Chart 1s Step 1. On the Navigation Pane in the Select Data drop-down menu, choose RBD Chart 1. Type the Carrier, and Tariff and then click to view the RBD Chart 1 List pop-up window. Figure 25 Step 2. Type the Carrier and then click to view the RBD Chart 1 List pop-up window. This display allows the user to view all chart 1 data that the referenced carrier has in all Tariffs (public tariffs only, unless the user has partner access security permission to view the private data). Figure Chart 1 List Step 3. From here, you can either click the Rule link to access the Chart 1 RBDs for Fare Owner and Concurring Carriers screen directly, or click the Close button to close the pop-up window. 42

45 Viewing RBD data online Step 4. From the GFS Main Menu, click Fare Rule/Fare Class to view RBD data. Figure 27 ATPCO Government Filing System Step 5. The screen for Text Menu will appear Figure 28 GFS Text Menu Step 6. Step 7. Step 8. Identify the Carrier and Area in which you wish to view RBD data. Enter ZZ as the Area code to view Chart 2 (tariff: All). To narrow the search, use the Tariff or In Effect On field, or both. Click List in the RBD field. 43

46 Viewing RBD data online Step 9. Check the RBD table that you wish to view. Click Text in the For Selected box to view the text for the selected RBD Table. Click Print in the For Selected box to print the text for the selected RBD Table. Figure 29 GFS Text Menu RBD Application List Figure 30 GFS Text Menu RBD Application List Click <<Previous to scroll backwards. Click Previous Version to see the text for the previously filed RBD provision. Click Top to scroll to the top of the RBD chart. Click Bottom to scroll to the end of the RBD chart. Click Next Version to see the text for subsequent versions of RBD text. Click Next>> to scroll forward. 44

47 Viewing RBD data online View Chart 1 from a Fare Class in GFS Step 1. Step 2. Step 3. Enter the Carrier, Area, and Tariff. Enter the specific fare class in the Fare Class box. (Figure 31 shows this process). If you need to view the list of fare classes, click List. Click Text to view the Fare Class Text for all the fare class codes valid for the specified carrier and tariff. Figure 31 GFS Text Menu In GFS you are able to view the applicable Chart 1 RBD Exception text from a Fare Class when you see Exceptions to the right of the RBD. Figure 32 GFS Text Menu Fare Class Text Display Step 4. Click Exceptions to view the Chart 1 for the Carrier, Tariff, and Fare Class specified. 45

48 Viewing RBD data online Figure 33 GFS Text Menu RBD Application Display Click <<Previous to scroll backwards. Click Previous Version to see the text for the previously filed RBD provision. Click Top to scroll to the top of the RBD chart. Click Bottom to scroll to the end of the RBD chart. Click Next Version to see the text for subsequent versions of RBD text. Click Next>> to scroll forward. 46

49 Viewing RBD data online Summary The Filter and Find functions within the RBD product have become a valuable asset. These functions help you research RBDs that are rather lengthy in a more timely and accurate manner. The Filter and Find functions are located on the RBD Chart 1 and RBD Chart 2 Sequence List screens. The RBD Filter and Find functions allow you to further restrict the parameters of the search function by indicating one or more of the following: Carrier Application RBD1 and RBD2 Fare Class/Family and Exact Match checkbox Fare Type Location 1 and Location 2 and Exact Match checkbox Travel portion Direction Sequence Return entire sequence (Filter only) 47

50

51 Creating RBD Instructions The instruction is the key to the proper application of RBD data

52

53 Creating RBD instructions Mission After completing this module, you will be able apply to identify how to instruct RBD Chart 1 and RBD Chart 2. Additionally, you will learn how to avoid common instruction errors. Why is this module important? Booking code data may be expressed in several places: Prime booking code in the Fare Class Record (Record 1) RBD Chart 1 Booking Code Exception in Fare Class Record (Record 1) and Booking Code Exception Table (Record 6) RBD Chart 2 Default Booking Codes in Booking Code Exception Table (Record 6) Discount Categories (prime RBD for the discounted fare) Category 25 Fare By Rule Some common instructions include RBDs based on fare identifier, geography, directionality, and primary or secondary carrier on YY fares. Some of these may become quite complicated when coding the RBD table. 51

54 Creating RBD instructions Overview RBD Chart 1 or RBD Chart 2? ATPCO s RBD format includes two charts that each contain specific data. Who owns the fare? Who is providing transportation? What tariff does the restriction apply to? In which Record would you find the Chart? RBD Chart 1 RBD Chart 2 Carrier that owns the fare publishes RBD Chart 1 Data for marketing carrier providing primary and/or secondary transportation Data for transporting (concurring) carriers providing secondary transportation Organized by Tariff/Carrier/Rule specific or all rules default within the Tariff/Carrier Record 1 Record 3 (Category 25 only) Record 6 Owner of the chart provides secondary transportation on another carrier s fare publishes Owner of the chart is providing primary and/or secondary transportation on YY fares or other carrier s fares Applies to all (public and private) fares and rules within all global areas Record 6 Why do I need to instruct or code my RBD provisions? RBDs are the key to inventory control, serving an essential role in the processing of fare and rule information. It is therefore essential that you create and maintain your RBD provisions for accurate inventory control. All carriers are assumed to be non-concurring and may not include data on your behalf within their Chart 1 provision. The assumption for non-concurrence is supported by edits in the system that restrict the coding of non-concurring carriers in another carrier s Chart 1, unless permitted in the Concurrence Table maintained by ATPCO. If you do not create a Chart 2, your airline s revenue will be impacted because other airlines will not be able to book you on their fares. What information do I need to implement RBDs? To create an instruction for your RBDs, a good place to start is with any Special Prorate Agreements that your organization currently maintains. These agreements contain all the booking agreements that your organization has made with another organization. Depending on your airline, you may have several different agreements that you will need to compile into different Chart 1 and Chart 2 provisions. 52

55 Creating RBD instructions Next, you will need to determine how you need passengers to be booked on IATA fares when your organization provides transportation. Chart 2 should contain provisions identifying how to book passengers transported on your airline for a YY fare. You need to determine how you want to book passengers transported on your airline for fares on all other airlines not mentioned in your Special Prorate Agreements. Finally, you will need to determine how to book passengers traveling on your fare and equipment. For example, what happens if you have a passenger traveling from LON WAS CLT on a business class fare but do not provide business class service between WAS CLT? You may use Chart 1 to identify how to book those passengers. What is concurrence and non-concurrence? Determining concurrence is an integral part of coding RBDs. If you are a concurring carrier, other airlines may maintain RBD data on your behalf within their Chart 1 (meaning the other airline owns the fare and you are providing transportation on their fare). Non-concurring carriers do not allow other airlines to maintain RBD data on their behalf. Non-concurring carriers take the responsibility and control of all their RBD data by using a Chart 2 to indicate how to be booked when they provide transportation for another carrier s fare. The industry assumption is that all carriers are non-concurring. Edits within the FareManager Rules system restrict the coding of non-concurring carriers in Chart 1 unless partial concurrence is specifically indicated in the RBD Concurrence Table. Non-concurrence Today airlines require more control over their booking and inventory; consequently, ATPCO adapted to assume non-concurrence for all new customers. Non-concurrence means that other carriers cannot instruct on behalf of another (secondary) carrier without authorization. Each non-concurring carrier takes full control and responsibility for their booking code data when that carrier provides transportation on another carrier s fare. The Concurrence Table enables you the ability to restrict concurrence within the RBD product. The Concurrence Table is a directory level that only ATPCO employees may update. This table enables ATPCO to maintain concurrence between carriers based upon the following parameters: Carrier Tariff Rule number or range of rule numbers Fare type Fare class code or fare family All public tariffs All private tariffs 53

56 Creating RBD instructions A Concurrence Help Screen is available within Chart 1 to list the carriers that allow concurrence for that Chart 1. Edits within Chart 1 prevent the coding of any carrier not included within the Concurrence Table. What does non-concurrence mean to me? Non-concurring carriers apply to public and private tariffs and may not be mentioned in any other carrier s Fare Class Application RBD Exception Table or RBD Chart 1 Booking Code Exception Tables unless an agreement with the non-concurring carrier has been made. In addition, non-concurring carriers cannot be mentioned along with RBD data within a category s free-form text. Non-concurring carriers may be mentioned in any carrier s Record 6 RBD Chart 2 Default Booking Code Table. Remember, Chart 2 identifies RBD information for the carrier that owns the Chart 2 when that carrier provides secondary transportation on any other carrier s fare or primary or secondary transportation on a YY fare. How do I instruct or code non-concurring carriers? When analysts are coding RBDs with RBD data pertaining to another carrier s flight segments, they will have to check if this carrier is concurring or non-concurring. If the carrier is a non-concurring carrier with the fare owning carrier not listed as an exception, this information cannot be processed in the Fare Class Application RBD Exception Table, RBD Chart 1, or any free-form text in the coded rules categories. The fare owning carrier must contact the non-concurring carrier, who has two options: 1. The non-concurring carrier can complete all necessary paperwork to allow the fare owning carrier as an exception to the non-concurrence. This paperwork has to be sent to ATPCO in order for ATPCO to process and update all applicable lists. 2. The non-concurring carrier can add the fare owning carrier into their Chart 2. The non-concurring carrier must instruct ATPCO if that carrier does not code its own Chart 2s. RBD data in Chart 1 cannot include non-concurring carrier information without special permission from the non-concurring carrier. These non-concurring carriers need to instruct their RBD data in their Chart 2. ATPCO maintains a list of all concurring carriers and maintains exceptions for partial nonconcurrence in the Concurrence Table. 54

57 Creating RBD instructions How does my GDS process non-concurring carriers? AA is a non-concurring carrier. For travel: PHX AA WAS BA LON on a BA MHEE21 fare class. Find the applicable Chart 1 for the fare IPRA BA 3000 Does the flight segment belong to the carrier that owns the fare? In this case, the flight segment (PHX TO WAS on AA) does not belong to the carrier that owns (BA) the fare. Between PHX and WAS travel is via AA Is the carrier non-concurring? AA is a non-concurring carrier; therefore, AA cannot be coded in another carrier s Chart 1. Go to Chart 2 default Booking Code for AA Is there a match? Assuming MHEE21 is an Excursion apply RBD M Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON AA OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD FOR AA NOTE ANY ALL ECONOMY EACH FLT SEGMENT. M REQ D EXCURSION ANY ALL ECONOMY EACH FLT SEGMENT. M REQ F PROMOTIONAL ANY ALL ECONOMY SPECIAL EACH FLT SEGMENT M REQ E 55

58 Creating RBD instructions Restrictive capabilities Reservation booking code exceptions can be expressed in the FareManager Rules system for any or all of the following conditions: Publishing/Owning carrier (carrier on the primary portion of travel) Interline/secondary carrier Market (city pair) Specific flight number or range of flight numbers Specific equipment type State code Country code Zone code (for example, zone 210 = Europe) TC Area code Portion of travel (for example, Western Hemisphere) Point of sale or SITO/SOTO/SOTI/SITI Date of travel Specific days of week or range of days Specific time of day or range of time Specified fares only, constructed fares only or both Fare type (for example, XEX indicates regular excursion fares) Fare family (for example, B- indicates all B- type fares) 56

59 Creating RBD instructions Points to remember RBD Chart 1 contains the RBD information that applies to the marketing carrier for the significant flight segment as well as secondary flight segments. This chart is read first. If RBD information is not found for a carrier other than the owner of the Chart 1, the transporting carriers in Chart 2 will be read to determine the applicable booking code. In addition, remember these points about Chart 1: Is organized by ATPCO tariff File updates that involve the CTA (Canadian Transportation Authority) on three-day short notice. RBD may only be cancelled if there are no valid fares attached or if only the Booking Code changed. The cancellation can be filed on statutory notice or as a three-day short notice application. Can be referenced from a Fare Class Record or from an RBD Application Record. The Fare Class Record exception is fare class specific. The Booking Code application may apply to specific or all rules within a tariff. Exceptions apply for Owning Carrier Secondary segments on the owning carrier or another carrier RBD Chart 2 applies to the publishing carrier that is providing transportation on another carrier or YY fare. Applies to all global areas and is not tariff restricted. When viewing in GFS, use Area ZZ and tariff All. Filings for area ZZ may be filed on one-day short notice. The CTA does not review these RBDs online; they should be filed on paper also. Applies to the ticketed carrier on a secondary flight portion of another carrier s fare or on sectors for transportation on a YY fare. Used for all secondary carriers, but not for the primary/owning carrier For YY fares, may be used for all carriers, even the carrier involved in the primary portion of travel. Non-concurring carriers are carriers who do not wish for another carrier to instruct RBD data on their behalf. These carriers are listed in the beginning of each applicable Chart 1. RBD data for these carriers may be found in their Chart 2. Refer to the ATPCO Fare Type Matrix for fare type definitions and fare type groupings. 57

60 Creating RBD instructions Explanation of notes Alpha notes are industry standards and are assigned by the system as follows: A All First Class (*F) B All Business (*B) C All Normal Economy (*E) D All Economy Excursion (*X) E All Economy Special (*S) F All Economy Promotional (*P) G All Premium First Class (*R) H All Economy (*Y) I All Add-On J All Premium Economy(*W) Z Defines specific fare types code Numeric notes are assigned by the system and are carrier-specific. These notes reflect any field coded that does not appear in the chart text. For example, equipment types appear in a numeric note. Abbreviations PRT Portion of travel (such as WH for Western Hemisphere and AT for Atlantic) OAL Other airline; excludes the publishing carrier (OAL) /VV Vice versa; used when LOCS are displayed without direction 58

61 Creating RBD instructions RBD Application PERM Permitted REQ Required R/OF Required when offered R/AV Required when available ADD Additional information exists that cannot be autopriced NRBD No RBD applies carrier does not participate STBY No RBD exists because the fare is Standby NPRM Not permitted PPNO Permitted when Prime Booking Code is not offered PPNA Permitted when Prime Booking Code is not available RPNO Required when Prime Booking Code is not offered RPNA Required when Prime Booking Code is not available Booking Application code Within Chart 1 and Chart 2 you have the ability to further restrict how the RBD for a specific restriction is to apply. The most frequently used Booking Application codes are Permitted (P) Required (R) Required When Offered (W) Required When Available (V) Not Permitted (N) When using these codes, you must be sure of your exact intention. For example, assume that you file fares between NYC and TYO via SFO. Now assume the prime booking code is M class. How do you want the passenger to be booked for portions of travel where M class is unavailable? The Booking Code application values allow you to determine how the passenger should be booked. If a booking code is expressed as Required, then all conditions must be met in order to validate that booking code. If these conditions are not met, a fail condition applies to that booking code. If a booking code is expressed as Permitted and the conditions are met, this booking code may be used. It is important to remember when Permitted is specified to include what booking code is required in the event the permitted booking code is unavailable. When a booking code is expressed as Not Permitted, this indicates that no RBD applies because the carrier does not participate in the fare, therefore, RBD validation should fail. 59

62 Creating RBD instructions Booking codes expressed as Required When Available apply when the specific booking code is available on a given flight and is required to be applied. If the specified booking code is not available, the system will continue processing until a match is made. If a booking code is expressed as Required When Offered and that class of service is offered on a flight, the specified booking code is required. If the specified booking code is offered but unavailable, the itinerary should fail validation. If the booking code is not offered, processing will continue looking for another sequence or apply the prime RBD. Permitted and Required The instruction states: for all P-type fares between A 01 and Argentina, RBDs F and P are permitted, RBDs C and Y are required. What is the intent? In this case, F and P are permitted; so if F or P seats are available, pass autopricing. If F or P are unavailable, the RBDs C or Y must be applied (either one of them) to pass autopricing. The processing flow Autopricing will validate the P (Permitted) sequence first and, even if there is no F or P seat (available or offered), will then go on to the next sequence, the R (Required) sequence, and pass or fail pricing depending on the booking code availability. When should you use these values? If you have an itinerary where multiple (and equal level) RBDs apply, use the Permitted and Required together to describe the provision. For example, the booking codes between NYC TYO are M, B, H, and V, and they would be instructed or coded as follows: Between NYC TYO v.v. PERM M B Between NYC TYO v.v. REQ H V How would you code the following provision? Between NYC TYO book in M, B, H, K, or V class. Market Booking Code Application RBD 60

63 Creating RBD instructions When is Required not required? If the Advance Reservations and Ticketing provision for the fare being validated allows Standbys and Waitlists, if an RBD is specified as Required, Required When Available, or Required When Offered, the GDS is still able to book the passenger as a Standby or Waitlist. The RBD will be determined at a later point. Required When Available and Required When Offered The instruction states: For all P-type fares between A 01 and Argentina, RBD F is Required When Available RBD C is Required When Offered What is the intent? The carrier wants the GDS/CRS to check inventory for an F seat before using C class. If F seats are not offered, pricing will go on to the next sequence. If F seats are offered and available, price by using the F RBD. If F seats are offered and unavailable, pricing will go on to the next sequence. If no F seat is available, the system will go on to the next sequence and search for a C seat in the inventory. If C seats are not offered, pricing will go on to the next sequence. If C seats are offered and available, price by using the C RBD. If C seats are offered and unavailable, fail the fare. The processing flow Required When Available means that RBD is required when it is available. If the RBD is not available, processing will continue to the next sequence. Required When Offered means if the requested inventory is offered, that RBD is required. If the RBD is offered but not available, autopricing will fail. If the requested inventory is not offered, the CRS will check the next sequence or apply the prime booking code for the carrier owning the fare. 61

64 Creating RBD instructions When should you use these values? Sometimes a passenger will purchase a business or first class ticket for an itinerary where portions of travel are to cities that are not serviced by aircraft with two or three cabins. How do you book that passenger s ticket? The most common way to accomplish this is by using the Required When Available and Required When Offered values. Assume your airline has fares between US-TYO but only flies from/to SFO/LAX. In some markets (NYC/WAS), the passenger must travel to SFO/LAX for their connection to TYO. In other markets (RIC/CLT), the passenger must use commuter service to access a larger airport. You might instruct or code the following provision to allow a passenger to purchase a business class ticket for their entire itinerary: Within the United States Required When Offered C Within the United States Required When Available F Within the United States Required Y What RBD will apply for travel within the United States to the gateway cities of San Francisco and Los Angeles? (Assume the prime RBD is C.) Fare Break Point Via Point Via Point Fare Break Point Class of Service Offered to SFO/LAX from Domestic US points First Business Economy SFO TYO Yes Yes Yes What RBD(s) applies for Business Class fares? LAX TYO Yes Yes Yes WAS SFO TYO Yes Yes Yes NYC SFO TYO Yes No Yes RIC WAS No No Yes WAS SFO TYO Yes No Yes RIC WAS No No Yes WAS SFO TYO No No Yes CLT NYC Yes No Yes NYC LAX TYO Yes Yes Yes 62

65 Creating RBD instructions Permitted, Required When Available, Required When Offered, Required The instruction states: For all P-type fares between A 01 and Argentina, RBD F is Permitted RBD J is Required When Available RBD C is Required When Offered RBD Y is Required What is the intent? RBD F is an option, not a must ; RBD J is a must when available; RBD C is a must when offered. Finally if C is not offered, RBD Y is the last choice. The processing flow The GDS/CRS will attempt to book RBD F if it is available. If F is available, F will be shown as the RBD for the portion of travel being validated. If F is not available, processing will continue to the next sequence to attempt to book J if available. If J is not available, processing will continue to the next sequence and attempt to book the passenger in C class. If C is offered but not available, it will fail pricing. If C is available, it will price at this point. If C is not offered, processing will continue to the next sequence, book Y required. If Y is not available, the CRS should fail the fare. 63

66 Creating RBD instructions RBD application conclusion The order in which Booking Application codes are sequenced determines the processing flow. R (Required) is always the last sequence in a set. W (Required When Offered) is similar to the value R, because it will fail autopricing if the RBD is offered but not available. V (Required When Available) is similar to R, because it is required to be used if the RBD is available. If the RBD is not available, the GDS/CRS will continue processing to the next sequence. P (Permitted) is an option; autopricing will not fail and the system will check the next sequence for another RBD. Never sequence V after W with the same booking code. If the RBD is offered, the system will apply it when it is available. If it is not available, autopricing will fail at the W sequence and never read the V sequence. Geography Location 1/Location 2 The Location fields indicate which travel portions are applicable for the RBD information. The Location fields may indicate cities, states, zones, countries, and areas. Information in these fields can be indicated as from/to, between/and, or origination from. TSI restrictions may also apply to these locales. When the same location is coded in Location 1 and Location 2, the application is within. When the Directional field is set with a value of From Location 1 or To Location 1 in combination with Location 1 or Location 2 fields, the booking code applies From the direction of the specified location or To the direction of the specified location. When the Directional field is set with a value of Origin Location 3 or Origin Location 4 in combination with Location 1 or Location 2 fields, the booking code applies Originating from the specified location. The Direction field may only be set with values of Origin Location 3 or Origin Location 4 when using the expanded screen. (Must Match Fare Component is required when Originating is used.) When the locale fields are blank, the assumption is the RBD applies to each flight segment. When the locale fields are coded without identifying additional restrictions to which the specified RBD applies, the assumption will be that it applies to flight segments departing from the last point in a location to the first arrival in a location. 64

67 Creating RBD instructions Directionality The Direction field allows you to specify RBD restrictions based on the passenger s direction of travel. Only code these fields when specifying geography in Location 1 and Location 2. The applicable Directional Indicator values follow: From Location 1 To Location 1 Origin Location 3 Origin Location 4 From Location 1 and To Location 1 apply to the direction of travel within the fare component regardless of fare selection. Origin Location 3 and Origin Location 4 apply to travel from the fare origination point. Origination is determined by the origination point of the fare component when the fare is used outbound and the destination point of the fare component when the fare is being used inbound. When Directional Indicator value 3 or 4 is present, edits require that you code Must Match Fare Component. From Direction of travel starting at the specified location, regardless of point of origin. To Direction of travel heading toward the specified location, regardless of point of origin. Origin Starting place of the journey as shown on the ticket, regardless of direction of travel. Incorrect directional coding and misinterpretation of an instruction can change the intent regarding rules provisions. For booking code restrictions that contain geographic information with directionality, it is important to understand how that directionality is applied. International fares are filed directionally, from one market to the next, and the fare may be charged round trip. 65

68 Creating RBD instructions From/To For excursion type fares from LON to ZRH, booking code L is required. What should apply when the passenger travels from ZRH to LON? Fare applies round trip LON ZRH LON The instruction states from LON to ZRH, the booking code L will be applied on the outbound LON ZRH portion only. If there is no match for the ZRH LON portion, the CRS will then apply the prime booking code for the carrier owning the fare. The text would state this: Chart 1 FARE IDENTIFIER LOCATIONS/FLIGHTS MKTG CXR RBD NOTE ANY FARE FLT SEGMENTS FROM LON ZRH. DO L REQ Origin Originating requires using the Must Match Fare Component tag. For excursion type fares originating LON to ZRH, booking code L required for A3 portions of travel. Fare applies round trip LON ZRH LON The instruction states originating LON to ZRH, the booking code L will apply to the LON ZRH portion and the ZRH LON portion when the fare is originating LON. If the fare is originating ZRH and there is no match in the Record 6, the GDS/CRS will follow the processing steps to determine the applicable RBD. The text would state this: Chart 1 FARE IDENTIFIER ANY FARE LOCATIONS/FLIGHTS DO FARES ORIGINATING LON-ZRH EACH FLT SEGMENT MKTG CXR RBD NOTE A3 L REQ Note: Be careful when using the direction fields. If information pertains to round-trip fares and it is the intent to cover the return portion of travel, then you must use tags Origin Location 3 and Origin Location 4 to state originating provisions. If the intent is to cover one sector and not to cover the return travel, then use From Location 1 and To Location 1. The application of From/To versus Originating is universal for the FareManager Rules product and is not solely related to booking codes. 66

69 Creating RBD instructions Fare Identifiers The Fare Identifier column represents the fare basis code, fare type, fare family, groups of fare types, or any fare that is permitted for the specified restriction. When instructing these provisions, the intent must be clear in order for proper autopricing to occur. Analyze the instructions below. Identify any confusion that may arise on the coder s part. 1. RBD applies to all PEX fares 2. RBD applies to all Special Fares 3. RBD applies to all Promotional Fares 4. RBD applies to all *EE* fares 5. RBD applies to all F or F- fares 6. RBD applies to all Economy type fares 7. RBD applies to all YPX fares 8. RBD applies to all Special Economy fares 9. RBD applies to all YEE fares 67

70 Creating RBD instructions According to the ATPCO Fare Type Matrix, what fare type codes are defined by the following fare identifiers? 1. All Excursion 2. All Normal Economy fares 3. All Special Economy fares 4. All First fares 5. All Business fares 6. All Promotional fares 7. All Special fares 68

71 Creating RBD instructions RBD Chart 1 CXR: Geographic Coverage: RBD for all sectors is 1st letter of fare basis code? yes or no FARE IDENTIFIER LOCATIONS/FLIGHTS MKTG CXR RBD NOTE Notes 69

72 Creating RBD instructions RBD Chart 2 CXR: RESERVATION BOOKING DESIGNATORS FOR SEGMENTS ON OTHER CARRIERS/YY FARES FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/ FLIGHTS RBD for NOTE Notes 70

73 Creating RBD instructions Summary RBD Chart 1 contains the RBD information that applies to the marketing carrier for the significant flight segment as well as secondary flight segments. This chart is read first. If RBD information is not found for a carrier other than the owner of the RBD Chart 1, the transporting carriers in RBD Chart 2 will be read to determine the applicable booking code. In addition, remember these points about RBD Chart 1: Organized by ATPCO tariff Can be referenced from a Fare Class Record or from an RBD Application Record. The Fare Class Record exception (Table 999) is fare class specific. The Booking Code application may apply to specific or all rules within a tariff. Exceptions apply for: Owning Carrier Secondary segments on the owning carrier or another carrier RBD Chart 2 applies to the publishing carrier that is providing transportation on another carrier or YY fare. Applies to all global areas and is not tariff restricted. When viewing in GFS, use Area ZZ and tariff All.. Applies to the ticketed carrier on a secondary flight portion of another carrier s fare or on sectors for transportation on a YY fare. Used for all secondary carriers, but not for the primary/owning carrier For YY fares, may be used for all carriers, even the carrier involved in the primary portion of travel. Non-concurring carriers are carriers who do not wish for another carrier to instruct RBD data on their behalf. These carriers are listed in the beginning of each applicable RBD Chart 1. RBD data for these carriers may be found in their RBD Chart 2. Alpha notes are industry standards and are assigned by the system as follows: A All First Class B All Business C All Normal Economy D All Economy Excursion E All Economy Special F All Economy Promotional G All First Class Premium H All Economy I All Add-On Z Defines specific fare types code Numeric notes are assigned by the system and are carrier specific. These notes reflect any field coded that does not appear in the chart text. For example, equipment types appear in a numeric note. 71

74 Creating RBD instructions Abbreviations PRT Portion of travel (for example, WH for Western Hemisphere and AT for Atlantic) OAL Other airline; excludes the publishing carrier. (OAL) /VV Vice versa; used when LOCS are displayed without direction How to apply the RBD PERM Permitted NPRM Not permitted REQ Required R/AV Required when available R/OF Required when offered STBY No RBD exists because the fare is Standby ADD Additional information exists that cannot be autopriced 72

75 Coding Conventions What are the coding conventions for RBDs?

76

77 Coding Conventions Mission After completing this module, you will be able to identify coding conventions for creating RBD provisions. Why is this module important? This module discusses industry-accepted coding conventions for RBDs. You will learn about instructing and coding non-concurring carriers, prime RBD, Point of Sale TSI, SITI/SOTO/SOTI/SITO, sequencing data specific to RBD Chart 2, using Travel Segment Indicators, double leveling, and other helpful hints for coding RBDs. 75

78 Coding Conventions Coding conventions Non-concurring ATPCO assumes that all carriers are non-concurring to RBD data unless otherwise specified. A carrier cannot instruct or code RBD data on behalf of another carrier unless the other carrier files a concurrence agreement with ATPCO permitting the instruction (for example, a carrier cannot instruct or code RBD data into Fare Class Application RBD Exception Table, Record 6 Chart 1, or Fare By Rule [Category 25] on behalf of a secondary carrier). If a carrier wishes to concur to another carrier instructing or coding RBD on their behalf, then instruct the carrier to file the necessary concurrence agreement paperwork with ATPCO. ATPCO will enter the concurring exceptions into the Concurrence Table Prime RBD The prime RBD should not be duplicated in Fare Class Application RBD Exception Table or Record 6 Chart 1 for the owning carrier. The Resulting Fare prime RBD should not be duplicated in Fare By Rule (Category 25) for the owning carrier. Point of Sale TSI The Point of Sale TSI specifies that the ticket must be sold outside the location specified in Point of Sale Location in order to match the segment. TSI 33 (outside the following geographic locale) is the only valid TSI that can be used in the Point of Sale TSI field. SITI/SOTO/SOTI/SITO Effective January 2005, IATA no longer uses the terms SITI, SOTO, SOTI, and SITO in industry resolutions. ATPCO is not eliminating these terms and thus you may continue to use them in your rule provisions as needs arise. For additional information, see PTB 190 issued on 29 December

79 Coding Conventions Sequencing data Sequence data from most specific to least specific. More specific sequences should have a lower sequence number than less specific sequences. Sequence numbers are automatically assigned by the system in the order you create your data. Example: Incorrect sequencing Seq # IF Via Cxr Locs RBD Data 1 Blank BA LON MAN REQ B 2 Blank BA GB GB REQ K BA GB FR REQ Q Sequence 1 indicates that if the sector being validated is between LON and MAN on marketing carrier BA, then RBD B is required for the sector. Sequence 2 indicates that if the fare component being validated contains a sector within GB and a sector between GB and FR, then RBD K is required for the sector within GB and RBD Q is required for the sector between GB and FR. In the above data, sequence 2 is more specific than sequence 1. Although sequence 1 contains cities rather than nations, sequence 2 is more specific because it requires two sectors on the fare component in order to match/validate. In this example, sequence 2 should have a lower sequence number than sequence 1. 77

80 Coding Conventions Coding Chart 2 Coding the basic sequence does not involve specifying what fare or whose fare. This assumes the fare owner can be any carrier, thus no owning carrier code is listed. A single segment basic sequence may be used if no information is being coded to differentiate locations for the fare component and the flight segments. This coding may be done on the RBD details grid screen. Example Carrier 01 will be booked in V when providing transportation on any other carrier s promotional fare. Figure 34 Sequence in a Sample Chart 2 The information above may be coded on the RBD details grid because the RBD information is very general, indicating that 01 is to be booked in V on any *P (Promotional) type fares published by any other carrier in any geographic locations worldwide. These more general sequences should appear near the end of the Chart 2. The more specific sequences that describe fare ownership, fare component, or portion of travel information are sequenced before any general statements such as the one listed in the example above. Multi-segment sequences are coded in the Expanded screen and use the fare owner carrier code and the Chart 2 owner (transporting carrier) code. Segment 1 describes information regarding the fare component or portion of travel and Segment 2 describes the flight segments involved with transportation and the RBD for the secondary carrier. The carrier providing transportation is the Chart 2 owner. It is preferable to keep the fare owner carrier codes in alphabetical order to allow for easier data maintenance. The coding involved with the majority of Chart 2 sequences involves multiple segment sequences. Single-segment Chart 2 sequences assume any carrier owns the fare and that the Chart 2 owner provides the transportation for a particular flight segment. Multisegmented sequences follow a different format in order to specify the carrier who owns the fare. Multi-segment sequences work on the premise that the owner of the Chart 2 is providing transportation on another carriers fare. Therefore, the two-segmented sequence first describes the owner of that fare and its associated fare component information. 78

81 Coding Conventions Travel segment indicators Location TSI TSIs specify the point or portion of travel that must be present in order to match the segment. TSIs modify the application of the Location 1 and Location 2 data. Any TSI is valid. Must be value Blank in the first segment in the sequence when IF Tag is Must Match Fare Component. Use of an arrival TSI (such as TSI 44) will modify the departure validation of Start/Stop Dates, Day of Week, and Start/Stop Times. Following is a list of TSIs currently used in the Location TSI field in Fare Class Application RBD Exception Table. The table is arranged by usage in descending order (beginning with the most commonly used TSI). Usage is based on the number of Fare Class Application RBD Exception Table sequences as of April TSI Definition Application 18 All international sectors FC/PU 19 All domestic sectors FC/PU 43 Departure of each transpacific sector FC 42 Departure of each transatlantic sector FC 31 Transatlantic sector(s) FC/PU 76 All domestic sectors of the journey J 32 Transpacific sector(s) FC/PU 47 Overwater segment(s) FC/PU 40 Departure of outbound transatlantic sector PU 89 On each intercontinental sector FC/PU 82 Departure from gateway FC/PU 56 Departure of inbound transatlantic sector PU 55 Departure of inbound transpacific sector PU 41 Departure of outbound transpacific sector PU 33 Outside the following geographic locale FC/PU 49 Arrival at the following geographic locale FC/PU 12 Arrival at destination gateway FC/PU 75 All international sectors of the journey J 06 Departure from origin gateway FC/PU 48 Departure of first international sector FC/PU 83 Arrival at gateway FC/PU 79

82 Coding Conventions Double leveling data tables Sometimes booking code information for a future effective date needs to be implemented in the Chart 1 and Chart 2. When this occurs, a special procedure referred to as double leveling allows data to be applied accurately and at the correct time. Example of un-filed data tables with double leveling 01 has a data table that is in effect 13OCT15. They want data to be entered with the future effective date of 31OCT15. The old data table will be discontinued effective 30OCT15 and the new table will go into effect 31OCT15. The new data is filed through GFS. Figure 35 Example of un-filed data tables with double leveling Example of filed data tables with the need to double level Here the carrier sends an instruction with new data that needs to be put in effect as soon as possible. The analyst will have to pull forward the data table that is currently being applied until 30APR14 and amend this table. Figure 36 Step 1. Example of filed data tables with double leveling Right click on the future-dated sequence and advance the date to tomorrow. Type the table number of the chart that is in effect today (609437) then save then make the required changes Figure 37 Step 2. Step 3. Step 4. Step 5. Example of filed data tables with double leveling Once the amendments are complete (in table ), save the changes. See in Figure 37 that the future-dated sequence has a new table number, Go back to the Batch list and change the Effective Date of the batch header to 01MAY14. Now, go back into the Record 6/RBD Chart and type over the data table in effect today with the data table effective 01MAY14 (data table in this example) and save to the previous batch. Make the required changes and save. 80

83 Coding Conventions Step 6. Release and file the batch. This is a very important process when coding the Record 6. If there are future effective dates, this process must be completed in order for the correct information to always be applied. If you do not update the table applying currently, and only update the table with the future effective date, errors will occur. This new information would not be applied until (in this case) the future effective date. 81

84 Coding Conventions Primary or Secondary on YY fares Primary Portion of Travel Secondary Portion of Travel Primary significant flight portion. The significant flight portion within a given fare component. Note: The determination of what is the primary flight portion may vary by CRS/GDS and is currently being addressed by the IATA Resolution Advisory Panel. Secondary flight portion. Any flight portion that is not primary within a given fare component. This field primarily exists for YY fares, allowing carriers to indicate whether RBD provisions apply on primary or secondary portions of travel when that carrier participates in a YY fare. Many carriers may not be aware of the existence of this field; therefore, they will not properly instruct their data. This data is represented in a YY Fare Class Application RBD Exception Table, Chart 1 Booking Code Exception Table and any carrier s Record 6, Chart 2 Default Booking Code Table. The CRS that is pricing the fare determines which portion of travel is considered the primary portion of travel. The primary portion of travel may be the longest flown segment or it may be the sector from the last point out of a country or zone to the first point into a different country or zone. Example 1 DL SR SR ATL BOS ZRH VIE Secondary portion Primary portion Secondary portion Figure 38 An ATL VIE fare component where SR provides transportation on the primary portion of travel (BOS ZRH) In the above example, BOS ZRH may be determined to be the primary portion of travel. Because SR provides transportation between BOS ZRH, the CRS would select the SR fare during fare selection. For carrier booking code restrictions submitted for YY fares, do the restrictions apply when the submitting carrier flies the primary or secondary portions of travel, or both? If the instruction states: The booking code data applies for sectors of other airline fares and Industry fares. Based on that wording, all sectors of travel on that carrier for YY fares apply the booking code restrictions. Chart 2 provides the capability for a carrier to indicate primary and secondary carrier s applicable booking codes for travel on another carrier or YY fares. 82

85 Coding Conventions Example 2 Instruction states: Chart 2 for 01 FARE IDENTIFIER LOCATIONS/FLIGHTS MKTG CXR RBD NOTE XPB Type Fares EACH FLT SEGMENT YY M REQ Z NOTES: Z XPB Super/Special Instant Purchase LON SIN HKG Secondary portion Primary portion Figure 39 An ATL VIE fare component where SR provides transportation on the primary portion of travel (BOS ZRH) The owner of the LON HKG fare component is YY. The instruction does not contain geographic restrictions, the data is assumed to apply to the entire fare. Therefore, RBD M will be applied to the entire LON HKG fare. In the absence of geographic location, ATPCO assumes that the booking code restriction applies to all portions of the fare transported unless specifically stated otherwise. When specific geographic information is indicated, the booking code applies to the last point out and first point into the geographic locations specified. If a carrier does not wish the RBD to apply to all portions, the instruction should state the following: Chart 2 for 01 FARE IDENTIFIER XPB TYPE FARES XPB TYPE FARES NOTES: Z XPB Super/Special Instant Purchase LOCATIONS/FLIGHTS YY FARES ON 01 PRIMARY FLT SEGMENTS YY FARES ON 01 SECONDARY FLT SEGMENTS MKTG CXR RBD NOTE YY M REQ Z YY Q REQ Z 83

86 Coding Conventions Example 3 Chart 2 for 01 FARE IDENTIFIER ALL BUSINESS TYPE FARES ALL BUSINESS TYPE FARES LOCATIONS/FLIGHTS YY FARES ON 01 PRIMARY FLT SEGMENTS YY FARES ON 01 SECONDARY FLT SEGMENTS NOTES: B ALL BUSINESS BND/BOX/BR/BRO/BRW/BTP/BU/BX MKTG CXR RBD NOTE YY Q REQ B YY K REQ B Itineraries for a business type fare for YY fare may be booked as follows: 01 book in K 02 (see 02 Chart 2) ZRH FRA SIN Secondary portion Primary portion Figure 40 A ZRH SIN fare component for carrier YY where 01 provides transportation on the secondary portion of travel (ZRH FRA) and 02 provides transportation on the primary portion of travel (FRA SIN) 01 book in K 01 book in Q ZRH FRA SIN Secondary portion Primary portion Figure 41 A ZRH SIN fare component for carrier YY where 01 provides transportation on the secondary portion of travel (ZRH FRA) and 01 provides transportation on the primary portion of travel (FRA SIN) The examples above show that a carrier may wish to have different booking code provisions when participating on a YY fare, depending on the portion of travel on which they provide service. If you do not specify whether the provision applies to primary or secondary portions of travel, then it is assumed that it applies to all portions of travel. 84

87 Coding Conventions Example 4 Chart 2 for 01 FARE IDENTIFIER ALL BUSINESS TYPE FARES LOCATIONS/FLIGHTS YY FARES ON EACH 01 FLT SEGMENT NOTES: B ALL BUSINESS BND/BOX/BR/BRO/BRW/BTP/BU/BX MKTG CXR RBD NOTE YY Q REQ B An itinerary for a business type fare for YY fare may be booked as follows: 01 book in Q 01 book in Q ZRH FRA SIN Secondary portion Primary portion Figure 42 A ZRH SIN fare component for carrier YY where 01 provides transportation on the secondary portion of travel (ZRH FRA) and 01 provides transportation on the primary portion of travel (FRA SIN) 85

88 Coding Conventions Helpful hints for coding 1. When coding Chart 1 rule specifics, do not restate the prime booking code unless instructed by the carrier. Figure 43 Fare Class Details screen Chart 1 for 01 rule TNG1 FARE IDENTIFIER LOCATIONS/FLIGHTS MKTG CXR RBD NOTE ANY FARE EACH FLT SEGMENT 01 M REQ 86

89 Coding Conventions 2. When sequencing within the Record 6, try to keep sequences containing a carrier together. Example: Carrier BD is coded within 01 s Chart 2, so all sequences containing BD should be kept together in the correct hierarchy order. Chart 2 for 01 FARE IDENTIFIER ALL BUSINESS TYPE FARES XEX TYPE FARES XPX TYPE FARES ALL ECONOMY TYPE FARES LOCATIONS/FLIGHTS MKTG CXR RBD NOTE BD FARES B ON EACH 01 FLT SEGMENT 01 Q REQ BD FARES Z ON EACH 01 FLT SEGMENT 01 K REQ BD FARES Z ON EACH 01 FLT SEGMENT 01 K REQ BD FARES H ON EACH 01 FLT SEGMENT 01 V REQ NOTES: B ALL BUSINESS BND/BOX/BR/BRO/BRW/BTP/BU/BX H- ALL ECONOMY FARE TYPES EXCEPT ADD-ONS/FIRST/BUSINESS/ CONCORD TYPES Z XEX- REGULAR EXCURSION FARES XPX INSTANT PURCHASE EXCURSION FARES 3. Use *Y when all economy fares share the same booking code. If there is one different booking code for one type of economy type fares, place the one economy type above the *Y and allow the *Y to stand for all other economy fare types. See the example above. Any of the XEX or XPX fares will apply the K RBD. Any other Economy fare will apply the V RBD. 4. Do not instruct to put information into a YY Chart 1, this information should be included in your carrier s Chart 2. 87

90 Coding Conventions Summary Coding the basic sequence assumes the fare owner can be any carrier, thus no owning carrier code is listed. A single-segment basic sequence may be used if no information is being coded to differentiate locations for the fare component and the flight segments. This coding may be done on the RBD details grid screen. TSIs specify the point or portion of travel that must be present in order to match the segment. TSIs modify the application of the Location 1 and Location 2 data. ATPCO assumes that all carriers are non-concurring to RBD data, unless otherwise specified. A carrier cannot instruct or code RBD data on behalf of another carrier unless the other carrier files a concurrence agreement with ATPCO permitting the instruction to be processed (for example, a carrier cannot instruct or code RBD data into the Fare Class Application RBD Exception Table, Record 6 Chart 1, or Fare By Rule [Category 25] on behalf of a secondary carrier). The prime RBD should not be duplicated in the Fare Class Application RBD Exception Table or Record 6 Chart 1 for the owning carrier. The Resulting Fare prime RBD should not be duplicated in Fare By Rule (Category 25) for the owning carrier. Sequence data from most specific to least specific. More specific sequences should have a lower sequence number than less specific sequences. The system auto generates the sequence number as you create your data. So the order in which the data is code is extremely important to the correct sequencing of data. Double leveling data tables is essential to correctly code the Record 6 when information has to be applied at a future date. Primary and Secondary Portions of Travel apply only to YY fares. If provisions applying to primary or secondary portions of travel are not addressed, then it is assumed that it applies to all portions of travel. 88

91 Updating RBD Data How do I update my RBD data?

92

93 Updating RBD Data Mission After completing this module, you will be able to identify the steps to access and update RBD data. Why is this module important? There is different functionality within the RBD product than the Fare Class Application and categories within the FareManager Rules system. Therefore, it is important that you are able to create, change, delete, and postpone RBD provisions. This module discusses the functionality of RBDs within the Fare Class Application, Discounts (Categories 19-22), Fare By Rule (Category 25), RBD Chart 1, and RBD Chart 2. In addition, you will learn how to create, change, insert, and delete sequences and segments within a RBD Chart 1 and/or RBD Chart 2. Learning to update your RBD data allows you to control your RBD output product. It eliminates the need to rely on ATPCO analysts to determine and code the data. You will have immediate control over changes and additions relevant to their desired RBD information. Locations for Update Depending on the application, RBD data may be found in different records within the Rules system. Fare Class Application Prime RBD The prime booking code is usually the first letter of the fare basis code unless stated otherwise. RBD Chart 1 This chart applies to the carrier that owns the fare and contains exceptions to the prime RBD. 91

94 Updating RBD Data Category Data Tables Discounts (Categories 19 22) The discount categories contain a field to indicate the prime RBD for the resulting fare if the discounted prime RBD is different from the base fare. Fare By Rule (Category 25) Category 25 contains a field to identify the prime RBD and exceptions to that prime RBD within RBD Chart 1 if different from the base fare RBD provisions. RBD information coded within Category 25 applies to the resulting fare. Booking Code Exceptions RBD Chart 1 RBD Chart 1 applies to the carrier that owns the fare and contains exceptions to the prime RBD. RBD Chart 1 exceptions may be coded for specific rules or to all rules not specifically mentioned. RBD Chart 2 RBD Chart 2 applies when the fare belongs to another carrier. The RBD Chart 2 carrier is providing transportation on another carrier s fare. 92

95 Updating RBD Data Fare Class Application Every Fare Class Application contains a fare basis code (fare class code) and a prime booking code (RBD). Step 1. To view the Fare Class Application, choose Fare Class from the Select Data drop-down menu on the Navigation Pane. Figure 44 Rules Home Page Step 2. Type the desired Carrier, Tariff, and Rule and click the button. The Fare Class list appears. Figure 45 Fare Class Sequence List screen Usually, the prime RBD is the first letter of the fare basis code. The prime RBD applies to the publishing carrier and all portions of travel on the fare. RBDs for interline carriers can be specified in the fare owner s RBD Chart 1 or the interline (secondary) carrier s RBD Chart 2. 93

96 Updating RBD Data The prime RBD does not apply to any participating carrier in a YY fare record. RBDs for YY fares are specified in each carrier s RBD Chart 2 (Default RBD Table) Sometimes a Fare Class Application will have a RBD Chart 1 table coded within a specific fare class. In this rare occurrence, the RBD Chart 1provision applies only to that fare basis code. There are two ways to access the Fare Class Application RBD Chart 1: 1. From the Fare Class List screen, click View: All Columns and scroll over to the RBD Chart 1 field. Click the RBD Chart 1 field and then click update the RBD Chart 1 RBD Exceptions pop-up window. to view or Figure 46 Fare Class List screen 2. From the Fare Class Details screen, click the button next to the RBD Chart 1 field to view or update the RBD Chart 1 RBD Exceptions pop-up window. When an RBD Chart 1 is coded to a specific fare basis code, the RBD Chart 1 field will have a table number present. Figure 47 Fare Class Details screen The screen you see next is the RBD Chart 1 - RBD Exceptions pop-up window. 94

97 Updating RBD Data Figure 48 RBD Chart 1 RBD Exceptions pop-up window The RBD Chart 1 RBD Exceptions pop-up window contains a Details screen. To view or update the Details screen, right-click a sequence and click. Figure 49 ATPCO Passenger Rules/Footnotes System RBD Exception Table The screens that follow are the Segment 1 and Segment 2 screens of the RBD Chart 1 Details screen for each individual sequence within the Chart. 95

98 Updating RBD Data Figure 50 RBD Chart 1 Details - Segment 1 Figure 51 RBD Chart 1 Details - Segment 2 96

99 Updating RBD Data To view the text for the RBD Chart 1 Details coding, click Actions > View Text. Figure 52 RBD Application Table Segment 1 The RBD Table Text pop-up window is displayed. To close, click the the bottom of the screen. button at Figure 53 RBD Text Display 97

100 Updating RBD Data Category data tables RBD data may be coded within the Discount categories (Categories 19 22) and Fare By Rule (Category 25). Discount categories The Discount categories contain fields to identify the prime RBD for the discounted fare. When this field is blank, the prime RBD for the base fare is the same prime RBD for the discounted fare. Figure 54 Category 19 (Children s Discounts) Details screen Input the prime RBD that is required for the discounted fare if the prime RBD is different from the base fare prime RBD. 98

101 Updating RBD Data Fare By Rule Category 25 contains fields to identify the prime RBD for the resulting fare. Additionally, Category 25 enables you to code exceptions for the resulting fare if different than the base fare prime RBD. RBD data in Category 25 is found in the Resulting Fare Information section of the Fare Calculation/Resulting Fare tab. See Creating Negotiated Fares and Fare By Rule for more information on using Chart 1 in Category 25. Figure 55 Category 25 (Fare By Rule) Details screen Once a prime RBD is coded in the RBD field, if there are exceptions to the Prime, you must create a RBD Chart 1 within the Category 25 provision to identify booking code exceptions for the resulting fare. To update the RBD Chart 1 in Category 25, click next to the RBD Chart 1 field. 99

102 Updating RBD Data You will see the RBD Chard 1 RBD Exceptions screen, as shown in Figure 56. Update RBD Chart 1 as applicable. Figure 56 Category 25 (Fare By Rule) RBD Chart 1 RBD Exceptions To view text from the RBD Chart 1 RBD Exceptions screen, right-click a sequence and click View Text. To view text from the RBD Chart 1 Details screen, click Actions > View Text. Figure 57 Category 25 (Fare By Rule) RBD Table Text Click Click on the RBD Table Text screen to return to the RBD Exception Table. again to return to the Fare Calc/Resulting Fare screen. 100

103 Updating RBD Data Figure 58 Category 25 (Fare By Rule) Fare Calculation/Resulting Fare tab with RBD Chart 1 table Update the Fare By Rule provision as applicable. 101

104 Updating RBD Data Booking Code Exception Tables RBD Chart 1 and RBD Chart 2 The structure of Record 6 includes two Charts that contain data for: 1. Exceptions to the prime RBD for the carrier that owns the fare and how to book other secondary carriers providing transportation on that fare 2. How to book the RBD Chart 2 publishing carrier when that carrier provides transportation on another carrier s fare Creating a new table On the Navigation Pane, use the link to see which data is coded. If the screen is blank, you do not have a RBD table for the tariff specified, as shown in Figure 59: Figure 59 Step 1. RBD Chart 1 List To create a new RBD Chart 1 or RBD Chart 2, use the Navigation Pane to access the desired data; type the Carrier, Tariff, and Rule number for RBD Chart 1, or type the Carrier for RBD Chart 2. Step 2. Click the button. This is how the RBD Chart 1 RBD s for Fare Owner and Concurring Carriers screen will appear when data table has not yet been coded. 102

105 Updating RBD Data Figure 60 RBD Chart 1 RBDs for Fare Owner and Concurring Carriers Step 3. Code the RBD Chart 1 as needed. RBD Control Information RBD Control Information Figure 61 RBD List Control Information RBD control information provides important details such as the RBD table number, work unit ID, batch ID, GFS FAN, user ID, and status. All this information is very useful for research and updating purposes. When you first access the RBD data, the most recent version of the chart is displayed. If needed, you can access previous versions of the chart. This section also has a right-click menu so you can action the data. 103

106 Updating RBD Data Note: The control information appears only for Chart 1 and 2. If you are accessing RBD exceptions from Fare Class Application or Fare By Rule (Category 25), the control information does not appear. RBD Control right-click menu Figure 62 Get Data: Displays the General Rule Index data for the selected row of control information. View Text: Opens the text pop-up window that displays the text for the RBD information. Copy/Paste: Copies the selected row and pastes it as the last segment. This is useful for reinstating older RBD data. Delete: Deletes an incomplete RBD control segment. The row will be marked for deletion and will be removed when you click Save. Discontinue: The selected row is discontinued with the effective date of the active batch. If there is no active batch, the system prompts you to create or select a batch. Advance: The selected row is advanced with the effective date of the active batch. If there is no active batch, the system prompts you to create or select a batch. Postpone: The selected row is postponed with the effective date of the active batch. If there is no active batch, the system prompts you to create or select a batch. 104

107 Updating RBD Data Saving RBD data Figure 63 RBD Chart 1 Step 1. After coding the sequences, click the button. Figure 64 Step 2. The Manage Batches window appears. Input the effective date of the RBD table in the Batch Date field. You may update your effective date manually or click the calendar option to select the effective date. 105

108 Updating RBD Data Figure 65 Step 3. Input the Comments to identify the information contained within this batch and associate the batch with a work unit. 106

109 Updating RBD Data Figure 66 Step 4. Click. 107

110 Updating RBD Data Copying an existing table Step 1. You have the option to copy rules and tables. To copy a RBD Chart 1 table, locate the data on the Browse tab, right-click it, and click. RBD Chart 1 for TRN1 is copied Figure 67 RBD Chart 1 - Copy Step 2. The Copy To pop-up window appears. Fill in the Carrier, Tariff, and Rule. You can change the Effective Date, if needed. Check the Include Incomplete Segments, if needed. TRN1 data is copied to TRN2 Figure 68 RBD Chart 1 Copy To pop-up window 108

111 Updating RBD Data Step 3. Click. Figure 69 Status Dashboard The Status Dashboard pop-up window appears. The current job is highlighted in yellow and appears on Row 1. When the Status is Complete, close the Status Dashboard and return to the Browse tab to access the new data. You might have to click the Refresh button to refresh the status. Figure 70 RBD Chart 1 Browse Tab access The new RBD Chart 1 will also appear on the Find or Create tab if you click the link. 109

112 Updating RBD Data Figure 71 RBD Chart 1 List 110

113 Updating RBD Data Changing an existing data table number Step 1. To change the Table Number of an existing Chart, put your cursor on the Table Number field of the RBD Chart 1 RBD s for Fare Owner and Concurring Carriers screen. Rule Numbers 2000 and 3000 are assigned Table Number Figure 72 RBD Chart 1 Table Number Update 111

114 Updating RBD Data Step 2. Simply type over the old table number with the new table number and click the button to apply the data on the screen. To change the Table Number to , overtype the Table Number. Figure 73 RBD Table Number Update Step 3. Click. Figure 74 RBD Chart 1 Table Number Update Step 4. Receive message Update successful. 112

115 Updating RBD Data Canceling an existing table Step 1. To cancel an existing table, use the Browse tab to access the desired data, right-click the RBD Chart 1 and click. Figure 75 Discontinue RBD Chart 1 Browse tab The RBD Chart 1 will be canceled with the same effective date as the batch header. If a new rule is created in error and needs to be removed, this portion can be deleted so long as the batch attached to the rule has not been filed. Remove the new rule in the same way that you would cancel an existing table: select Delete. This data can also be deleted by accessing the Batch List tab, selecting the associated batch, and choosing Delete Incomplete Segments. This action will remove all unfiled data in that batch from the system and the batch will then be empty. Figure 76 Discontinue RBD Chart 1 RBD Control right-click menu 113

116 Updating RBD Data Postponing the effective date Step 1. Click the Active Batch link on the Dashboard and then click Select Batch. Figure 77 RBD Chart 1 Manage Batches pop-up window Step 2. Choose the desired batch and desired effective date. When postponing effective dates, the Effective Date must match the effective date of the Active Batch on the Dashboard. Figure 78 RBD Chart 1 postpone effective date 114

117 Updating RBD Data Step 3. On the RBD Chart 1 or RBD Chart 2 screen, right-click the desired sequence on the RBD Control and click Postpone. Step 4. Click. 115

118 Updating RBD Data Advancing the effective date of an unfiled segment Step 1. Click Active Batch link on the Dashboard and then click Select Batch. Figure 79 RBD Chart 1 Manage Batches pop-up window Step 2. Note: Choose the desired batch and desired effective date. Filings presented to the Canadian government have to be sent through GFS on four days short notice. 116

119 Updating RBD Data When advancing effective dates, the Effective Date must match the effective date of the Active Batch on the Dashboard. Figure 80 RBD Chart 1 advance effective date Step 3. On the RBD Chart 1 or RBD Chart 2 screen, right click the desired sequence on the RBD Control and click Advance. Step 4. Click. 117

120 Updating RBD Data Updating an existing table Before adding new sequences within a table, review sequencing principle: most specific to least specific. Determine where the new sequence within a table needs to be inserted. RBD Chart 1 RBDs for Fare Owner and Concurring Carriers right-click menu Figure 81: RBD Sequence List grid This is the RBD Sequence List grid. Like all grids in the new FareManager Rules system, it has right-click and multi-select functionality. The first five columns are anchored and unscrollable. Because some RBDs sequences have two segments, each segment is one row on the grid. Both rows, or segments, will share the same shading to indicate they are of the same sequence. Most fields now have drop-down menus and look-up lists to make entering data easier. Sequences can be reordered or moved easily using the new drag-and-drop functionality. Additionally, sequences and all the data belonging to the sequence can now be copied. 118

121 Updating RBD Data RBD List View modes There are two view modes: 1. Default: (System Assumption) RBD Chart displays the most commonly coded RBD field/columns. 2. All: Displays all the RBD fields and columns. Table number This is the table number that represents the RBD information. You are able to copy or reuse table numbers. To do so, simply type the table number and click the arrow next to the field. The grid will be updated with the associated RBD data. Page control and Navigation Use these fields to control the amount of RBD data displaying in the grid. Additionally, use the arrow buttons to access pages in the RBD sequence list. Button Click Save once after all updates have been made. It is unnecessary to click Save after each update or before you navigate to the RBD details. You are able to navigate to and from the grid and details form without having to click Save. When you click Save, depending on the amount of data to be saved, the system may open the activities dashboard. Please note, the duplicate sequence and most restrictive condition check occur when the Save button is clicked. An error message appears if the system encounters any issues. 119

122 Updating RBD Data Actions drop-down menu Click the Actions drop-down menu to access these options: View Concurring Carrier: Opens the Concurring Carriers pop-up window. Here you are able to search Concurring carrier information. Refresh: This action resets all the RBD data with data from the last save. All unsaved changes are removed. You can also Ignore Changes for a single row by using the right-click menu. Date Actions The Date Actions link provides a drop-down menu for you to perform date functions to the RBD chart data. The date actions apply to all the data in the Chart. The Date Actions are Discontinue: The selected RBD Control row is discontinued. A calendar prompt appears requiring you to indicate the effective date for the data to be discontinued. Advance: The selected RBD Control row is advanced. A calendar prompt appears requiring you to indicate the effective date for the data to be advanced. Postpone: The selected RBD Control row is postponed. A calendar prompt appears requiring you to indicate the effective date for the data to be postponed. 120

123 Updating RBD Data RBD List right-click menu Figure 82 Right-click menu View detail Displays RBD Details form screen for selected row. The system will implicitly save any changes made on the RBD List screen, so it is not necessary to click the Save button. View text Opens the text pop-up window and displays the text for the selected rows only. Move When you select Move from the right-click menu, a cascading menu appears with these options: From Indicates the selected row is to be moved from its location in the list. If the segment is filed, the system discontinues the selected RBD row and creates a new row moved to its new location. Once the Move has been initiated, you must right-click again in the desired location to complete the move process. Before/After Once you have selected a row to be moved, you must then indicate where it should be moved to. Select the new location and indicate whether it should be moved before or after the selected row. Note: You can also click and drag the row to move it. 121

124 Updating RBD Data Copy Copies the specified row (RBD segments or sequence) as indicated, including all detail data. To copy multiple rows, press and hold the Ctrl key, then click on each desired row to highlight it. Once all rows are highlighted, right click and select Copy from the menu. Copy Sequence Copies all the sequences and all their associated segments (rows). Highlighting any row of the sequence will copy all segments (rows) associated to the sequence. Paste as New Sequence When this option is selected, a cascading menu appears with these two options: Before Pastes all the copied rows as new sequences before the first segment of the selected sequence. A row must be copied before you can select this option. After Pastes all the copied rows as new sequences after the last segment of the selected row. A row must be copied before you can select this option. Paste as New Segment When this option is selected, a cascading menu appears with these two options: Before Pastes all the copied rows as new segments before the first segment of the selected sequence. A row must be copied before you can select this option. After Pastes all the copied rows as new segments after the last segment of the selected sequence. A row must be copied before you can select this option. Delete Sequence Deletes the selected RBD sequence and all its segments. Once delete has been applied, the selected rows are highlighted in grey, indicating the rows are marked for deletion. Additionally, the rows are disabled from editing. You must click Save to complete the deletion process. Once Save is clicked, the rows marked for deletion are deleted. 122

125 Updating RBD Data Once the rows are deleted, they cannot be retrieved. You can multi-select rows to delete all of them at once. Undo Delete Sequence This option deselects a row for deletion. The row becomes enabled for editing. Delete Segment Deletes the selected RBD segment. Once Delete has been applied, the selected segments are highlighted in grey, indicating the rows are marked for deletion. Additionally, the rows are disabled from editing. You must click Save must to complete the deletion process. Once Save is clicked, the rows marked for deletion are deleted. Once a row is deleted, it cannot be retrieved. You can multi-select rows to delete all of them at once. Undo Delete Segment This option deselects a row for deletion. The row becomes enabled for editing. Insert Sequence When this option is selected, a cascading menu appears with these two options: Before Inserts a sequence above the selected row. After Inserts sequences after the selected row. Insert Segment When this option is selected, a cascading menu appears with these two options: Before Inserts a segment above the selected row. After Inserts a segment after the selected row. 123

126 Updating RBD Data RBD Chart 1 and Chart 2 Details forms Figure 83 RBD form Each row on the RBD Sequence List has its own Details form view accessed by clicking View Details on the right-click menu. The RBD form includes Navigation pane Form details Insert, copy, paste, and delete functionality Easy navigation among RBD sequences with the Previous Sequence and Next Sequence links 124

127 Updating RBD Data Navigation pane Figure 84 Navigation pane You can click the arrows to expand the navigation pane. Use the navigation pane to quickly access other rules data. Form Details Figure 85 RBD Form Details 125

128 Updating RBD Data These are the RBD details. All RBD fields are available on the form, including those found on the All Columns grid view. Each segment of a sequence appears in tab format. You can toggle between the tabs without saving. Notice in Figure 85 there are two tabs representing each segment of the sequence. You can toggle easily between the two simply by clicking the tab you wish to view. Please note there is no Save button on this screen. You can only save on the RBD Sequence List and once all your updates have been made. Buttons Click this button to insert a blank segment. Click this button to copy and paste the segment in view. Click this button to delete the RBD sequence and all its segments. When this button is clicked, all the fields in the form become protected to prevent editing. Click this button to undo a deleted sequence. All fields are enabled for editing. Links Use these links to access the previous/next sequence. Click this link to go back to the RBD List screen. 126

129 Updating RBD Data Actions drop-down menu Click here to access the Actions drop-down menu. This menu offers the following functions: View Concurring Carriers: This action opens the Concurring Carriers pop-up window. Here you are able to search concurring carrier information. View Text: This feature displays the text pop-up window. 127

130 Updating RBD Data Duplicate Sequence and Most Restrictive checks Two new checks have been added to ensure the integrity of your RBD data. These checks are preformed automatically when the Save button is clicked. If there is an error, the system displays a message. Duplicate Sequence In the Duplicate Sequence check, the system looks for sequences that share the same coding. Figure 86 RBD Duplicate Sequence Check Figure 86 shows an example of the Duplicate Sequence Check. Highlighted in the figure are rows 7 and 10, which are duplicate sequences. 128

131 Updating RBD Data Most Restrictive Check In the Most Restrictive Check, the system ensures that the order of sequences is valid. Figure 87 Most Restrictive Check Figure 87 shows an example of the Most Restrictive Check. The last two rows are sequenced incorrectly. 129

132 Updating RBD Data Summary Depending on the application, RBD data may be found in different records within the FareManager Rules system. Record 1 Prime RBD RBD Chart 1 Record 3 Categories (Discounts) Category 25 (Fare By Rule) Record 6 RBD Chart 1 RBD Chart 2 The RBD Details screen is used if the information that needs to be coded is not located on the RBD List screen. The RBD Details screen is also used when an IF set is needed. If information has been coded on the RBD Details screen, you will be able to tell from the RBD List screen because this screen will be highlighted. 130

133 Introduction to the Sequence List and Details Screens The relationship between the Sequence List and Details screens

134

135 Introduction to the Sequence List and Details Screens Mission After completing this module, you will be able to identify the relationship between the Sequence List and Details screens for RBD. Why is this module important? Within Chart 1 and Chart 2 are two screens to code RBD data. It is important to identify the differences and processing of data coded on the Sequence List screen versus data coded on the Details screen. The RBD table consists of sequences and segments. This module discusses the relationship between the sequences and segments that make up the charts. 133

136 Introduction to the Sequence List and Details Screens Purpose of the Sequence List screen The RBD Sequence List screen contains basic booking code data that describes the conditions and exceptions to those conditions. All the fields on the Sequence List screen are also included on the Details screen. The Details screen simply displays the fields in an easy-to-use form layout. However, the Details screen may be used to view only one sequence at time whereas the Sequence List screen lists multiple sequences. In addition, the Sequence List screen has two views: Default and All Columns. The views are changeable by selecting an option from the View drop-down menu. Typically, data present in Chart 1 belongs to the owner of the Chart 1 but may apply for secondary transportation provided by another concurring carrier. Figure 88 RBD Chart 1 Sequence List screen 134

137 Introduction to the Sequence List and Details Screens Chart 2 describes other carrier s fares where the owner of the Chart 2 provides transportation. Therefore, basic one-line sequences assume it is any carrier s fare, on which the Chart 2 owner provides transportation. The two-line sequence provides the owner of the fares (top row) and their details as well as information for the Chart 2 Owner (bottom row). Figure 89 RBD Chart 2 Sequence List screen 135

138 Introduction to the Sequence List and Details Screens No fare owner is named; therefore, the bottom segment remains blank. The assumption is that 01 is to be booked in Y on any other carriers with PGV type fare. Figure 90 RBD Chart 2 Details screen with multiple segments Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE ANY PGV TYPE EACH FLT SEGMENT Y REQ Z NOTES: Z PGV GROUP INCLUSIVE TOUR Chart 2 Default RBDs text translation Book Y when 01 provides transportation on any carrier s PGV type fare. Basic one-line sequences in Chart 2 show how the Chart 2 owner (01 in this case) is to be booked when providing transportation on any other carrier s fare that 01 participates in. When a Chart 2 sequence is coded using only a single line as shown above, the assumption is that the RBD is applicable to any fare published by any other carrier or YY fare. If the intention is to express specific information about which carrier publishes the fare or provides specific information about the fare component or portion of travel on a fare, multi-segmented sequences are coded. If additional information needs to be coded for an RBD, you may access the Details screen by right-clicking a sequence on the Sequence List and then selecting the View Details command. 136

139 Introduction to the Sequence List and Details Screens The Sequence List screen allows users to code multiple sequences before having to validate and save the information. The Sequence List screen also allows users to view multiple sequences at once. Purpose of the Details screen The Details screen for RBDs allows you to create If Then conditions that clarify your booking code restrictions for specific markets, fare classes, and other criteria. The Details screen contains the same fields as the Sequence List screen. These fields are used to further define the application of the RBD data coded on the Sequence List screen. All coding may be done on the Details screen, since all fields on the Sequence List screen are carried over to the Details screen. However, some users find it more efficient to code using the Sequence List screen whenever possible. The Details screen may be coded with multiple segments. By default, the screen displays information for Segment 1. To insert a second and subsequent segment, click the button. Segment 1 indicates which fare the system should look at, and the bottom half indicates the transporting carrier with the applicable RBD. In Chart 1, sequences coded on the Sequence List screen occupy only the top half of the screen and do not differentiate between what fare and where, as shown in Figure 91. Figure 91 RBD Chart 1 Details screen 137

140 Introduction to the Sequence List and Details Screens Screen Description If Matching for Carrier Describes whether the segment matches the fare component or the portion of travel Defines the owning carrier for the fare Fare Class/Fare Type Fare description information including the fare family and fare type Travel Flights Location restrictions Ability to restrict travel to primary or secondary sectors Ability to restrict travel to specific location portions Date restrictions including date ranges Day of week restrictions Specific flight numbers or ranges of flight numbers Specific equipment type requirements Point of Sale = Selling and Ticketing Locations Information RBD Ability to restrict sales to specific locations Ability to define whether selling and/or ticketing must be inside or outside the country of commencement RBD codes RBD application Flight Segment Description and RBD Information Transporter/Chart 2 owner Flight segment location RBD information 138

141 Introduction to the Sequence List and Details Screens Multi-segmented Sequences Multi-segmented sequences describe fare information in Segment 1 and transporting information in Segment 2. Segment 2 is usually involved with the coding of Chart 2 to indicate If Then statements. Fare information describes the owner of the fare, the markets of the fare, and the specific type of fare. Transporting information identifies the flight segments provided by the transporting carrier (Chart 2 owner) and the associated RBD for the fare. Chart 2 describes RBDs for transportation by the Chart 2 owner of another carrier s fare. Therefore, Segment 2 will always contain the Chart 2 owner who provides transportation for the fare. Figure 92 RBD Chart 2 Details screen with multiple segments 139

142 Introduction to the Sequence List and Details Screens The Segment 1 represents the fare component for the owning carrier s fare. The Segment 2 displays the flight segment and RBD information for the transporting carrier s portion of travel. Figure 93 RBD Chart 2 Sequence List screen with multiple segments Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 Segment 2 identifies how to book 01 when 01 provides transportation between Tel Aviv and London on VS fares originating Israel for Q- Type fares. OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE VS Q- TYPE VS FARES ORIGINATING ISRAEL FLT SEGMENTS FROM TLV -LON/VV. NOTES: Z PGV GROUP INCLUSIVE TOUR V REQ When there are two or more lines of data with the same sequence number, you have created multi-segment sequences. Imagine a horizontal line and assign the top segment fare information and the bottom segment transporting information to help to interpret the data. If it is necessary to specify the owning carrier or distinguish fare component information about what fare is used or where the flight segments occur, you must code a multisegmented sequence on the Details screen. 140

143 Introduction to the Sequence List and Details Screens Summary The RBD Sequence List screen contains basic booking code data that describes the conditions and exceptions to those conditions. All the fields on the Sequence List screen are also included on the Details screen. If additional information needs to be coded for an RBD, users may access the Details screen by right-clicking a sequence and then selecting the View Details command. The Details screen for RBDs allows you to create If Then conditions that clarify your booking code restrictions for specific markets, fare classes, and other criteria. The Details screen contains additional fields that cannot be coded on the Sequence List screen. These fields are used to further define the application of the RBD data coded on the Sequence List screen. All coding may be done on the Details screen, since all fields on the Sequence List screen are carried over to the Details screen. The Details screen includes information about: Fare Class/Fare Type Travel restrictions Flight restrictions Point of sale RBD and RBD application 141

144

145 Coding the Sequence List Screen Coding data on the Sequence List screen

146

147 Coding the Sequence List Screen Mission After completing this module, you will be able to identify the coding for the fields on the Sequence List screen within the RBD product. Why is this module important? In order for your RBDs to accurately autoprice, you need to create RBD provisions that accurately reflect your airline s intention. This module discusses the fields and coding for the Brief screen, as well as sequencing and coding conventions. The Sequence List screen for RBDs contains fields and elements that your airline may use to automate booking code exceptions. Therefore, it is essential that you are able to accurately update the Sequence List screen in the RBD product to reflect your airline s intention. 145

148 Coding the Sequence List Screen Sequence List screen Figure 94 RBD Chart 1 Sequence List screen (scrolled left, all columns displayed) Fields in All Columns view include: Must Match Carrier APPL (application) RBD (1/2) Fare Class/Fare Family (Fare Family only on Chart 1) Fare Type Travel TSI (travel segment indicator) DI (directional indicator) Type (referring to location type of LOC 1) LOC 1 Type (referring to the location type of LOC 2) LOC 2 Sector Portion First Date Last Date 146

149 Coding the Sequence List Screen Depending on your screen resolution, these fields will likely be viewable when the screen is scrolled to the right in All Columns view: Travel Days of the week (M, T, W, Th, F, S, S) First Time Last Time Flights Number 1 On/Through Number 2 Equipment Point of Sale Outside Type Location Sell/Ticket User ID Sequence 147

150 Coding the Sequence List Screen Fields and values Right-click menu Figure 95 Right click menu Right-click a sequence to access a menu with these options: View Detail (opens the Details screen) View Text (viewable only if data has been saved) Move (allows you to change the order of sequences) Copy Copies the specified row (RBD segments or sequence) as indicated, including all detail data. To copy multiple rows, press and hold the Ctrl key, then click each desired row to highlight it. Once all rows are highlighted, right-click and select Copy from the menu. Copy Sequence: Copies the sequence(s) and all its associated segments (rows). Highlighting any row of the sequence will copy all segments (rows) associated to the sequence. Paste as New Sequence (pastes copied data before or after point of selection) Paste as New Segment (pastes copied data before or after selected segment) Delete Sequence Insert Sequence (inserts a blank sequence before or after point of selection) Insert Sequence (inserts a blank segment before or after point of selection) 148

151 Coding the Sequence List Screen Must Match Figure 96 Must Match menu The Must Matching tag identifies the relationship between multiple segments within a single sequence. The values within this field define how to match the data within the sequence. You may code up to 5 recurring segments within a single sequence within the RBD Table. When data applies to a sector, validation is against ticketed points. These are the valid values for this field: Fare Component Portion of Travel This field is required when you create If Then provisions for your RBDs. When coding this provision, use two segments: Segment 1 is considered the IF condition. Segment 2 is considered the THEN condition. Note: Remember that a sequence can consist of no more than five segments and the relationship between segments is AND, making all a MUST condition. 149

152 Coding the Sequence List Screen Carrier Figure 97 Carrier field Required The Carrier field enables you to 1. Specify RBD data for the carrier that is providing transportation for your fare (Chart 1). 2. Specify how to book passengers when your carrier provides transportation on another carrier s fare (Chart 2). Chart coding differences Value Application Chart 1 Chart 2 Non-concurring Must be present in the Concurrence table Not Permitted Carriers Permitted OAL Any carrier except the owning carrier Not Permitted Permitted In Chart 1, the carrier code will edit against the Concurrence Table when coded with any carrier code other than the Chart 1 owner. If the carrier is non-concurring, edits restrict coding non-concurring carriers unless permitted in the Concurrence Table. When you are coding Chart 1 within Fare Class Application or data table for Fare By Rule (Category 25), edits prevent you from coding an invalid alphanumeric code. 150

153 Coding the Sequence List Screen Application and RBD Figure 98 APPL and RBD fields Required This field identifies how the RBD specified in the RBD fields are to apply. Click to view the valid values for the Application field. The most commonly used valid values for application include the following: Text REQ PERM R/AV R/OF NPRM STBY ADD Meaning Required Permitted Required when available Required when offered Not Permitted No RBD exists because the fare is Standby Additional significant data applies to the following booking code. 151

154 Coding the Sequence List Screen Coding Application The Booking Code fields specify the applicable RBD(s) for the sector being validated. Up to two RBDs may be specified per line The relationship among the RBDs is OR, except when multiple segments are coded for one sequence number. Coding conventions for Application types The RBD value must be a one- to two-letter code, except as follows: When the IF Tag is Must Match Fare Component, the RBD value must be Blank in the first segment of the sequence. When the IF tag is Must Match Portion of Travel, the RBD field may be populated in conjunction with additional travel or flight data coded in that segment When the Restriction Tag is Standby, the RBD value may be a one- to two-letter code or the word ANY, signifying any booking code. Required is always the last sequence in a set. Required When Offered is similar to Required because it will fail autopricing if the RBD is offered but not available. Permitted and Required When Available will not cause autopricing to fail and the system will check the next sequence for another RBD. Never sequence Required When Available after Required When Offered with the same booking code if the RBD is offered, the system will grab it when it is available. If it is not available, autopricing will fail at the Required When Offered sequence and never read down to the Required When Available sequence. Required when offered T Required when available T What if T is offered but not available? It is redundant coding to create two sequences with the same RBD: the first one with Required When Available and the second one with Required When Offered. The system will never read the second sequence. Required when available T Required when offered T The system will require that T be booked when available but will never read to the second sequence. 152

155 Coding the Sequence List Screen Fare Class/Fare Family, Fare Type Figure 99 Fare Class/Fare Family and Fare Type fields Not Required The Fare Type field identifies the type of date coded in the Fare Class/Fare Family and Fare Type field. The list that follows identifies the valid values and their application. Type Notes Fare Class Code Only valid in Chart 2 Fare Type Code Example: XAP Fare Family Example: YH- type fares Arbitrary Example: M***** type fares 153

156 Coding the Sequence List Screen Coding Fare Class/Fare Family and Type In the Fare Class/Fare Family field, type the fare class, fare type, or fare family as applicable. Click the right side of the of the Fare Type field to open the Fare Type look-up list from which you may search for and select a code for use. Choose a fare type that describes what you typed in the Fare Class/Fare Family field. Intention Specific Fare Class Code Wildcard or group of Fare Class Codes Specific ATPCO Fare Type All First/All Business/ All Economy/All Excursion Type Fares Any Fare Type Application Fare Basis Code Specific 8-character fare class (fare basis) code. Note: This is valid only in Chart 2. Hyphen (-) Fare Families The fare family is a fare class coding convention designed to match any alphanumeric string of characters. Place a hyphen in the position at which variations take place. The following rules apply when using the hyphen convention: When a hyphen is present in the fare family string there is also an assumed hyphen at the end of the fare family string. (e.g., -70 = BE70NR ) The numeric string of the fare class type being matched cannot be altered by additional numeric. (e.g., BE-70 does not match BE170 or BE1270) The alphabetic components of the fare class can be altered by the use of a hyphen anywhere in the string. (e.g., -E70 = BE70, YNWE70, Q123E70R) A hyphen in the beginning of the string of characters in the fare family must be replaced with at least one character and cannot be left blank. (e.g., -HE70 does not match HE70NR) Example 1: YH- Processing resolves to all fare class codes beginning with YH. Example 2: BE-70. Some of the fare class codes that processing can match are BEX70 and BE1X70 (processing will not match BEX170). Fare Type For example, XAP (Advanced Purchase) XPX (Instant Purchase). Fare types will be shown in the format of XPX. Valid Fare Type Codes are specified in Section C Appendix B Fare Type Matrix. Asterisk (*) plus the first character of an ATPCO Fare Type represents Multiple Fare Types by using the first character of a group of Fare Types preceded by an asterisk. For example, *E states that all fares with an ATPCO fare type commencing with E are included. Multiple fare types will display as ALL ECONOMY with fare types EAP/EBN/EIP/END/ER/ES/EU in the text. Refer to the Fare Type Matrix for the definition of asterisk/letter combinations. Three asterisks (***) = any fare type 154

157 Coding the Sequence List Screen Fare Class Example (Only in Chart 2) Figure 100: Fare class example FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/FLIGHTS DO MHEE21 DO FARES EACH FLT SEGMENT Figure 101: RBD Text RBD FOR 01 L REQ NOTE 155

158 Coding the Sequence List Screen Fare Family Example Figure 102: Fare family example FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/FLIGHTS DO BX15M- DO FARES EACH FLT SEGMENT Figure 103: RBD Text RBD FOR 01 L REQ NOTE 156

159 Coding the Sequence List Screen Fare Type Example Figure 104: Fare Type example FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/FLIGHTS DO XAP TYPE DO FARES EACH FLT SEGMENT NOTES; Z - - XAP - - REGULAR APEX Figure 105: RBD Text RBD FOR 01 L REQ NOTE Z 157

160 Coding the Sequence List Screen Multiple Fare Types Example Figure 106: Multiple Fare Types example FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/FLIGHTS DO ALL ECONOMY DO FARES EACH FLT SEGMENT RBD FOR 01 L REQ NOTE NOTES; H - - ALL ECONOMY ALL FARE TYPES EXCEPT ADD-ON/FIRST/ BUSINESS/PREMIUM ECONOMY TYPES Figure 107: RBD Text H 158

161 Coding the Sequence List Screen Multiple Fare Types Available *R ALL PREMIUM FIRST RR/ RU *F ALL FIRST FND/FOX/FR/FRO/FRW/FS/FTP/FU/FX *J ALL PREMIUM ECONOMY NORMAL-WR/WU *B ALL BUSINESS BND/BOX/BR/BRO/BRW/BTP/BU/BX *W ALL PREMIUM ECONOMY NORMAL-WR/WU *Z ALL PREMIUM ECONOMY SPECIAL-ZAP/ZEX/ZIP/ZOX/ZPX/ZZP *E ALL ECONOMY NORMAL EAP/EBN/EIP/END/ER/ERW/ES/EU *X ALL ECONOMY EXCURSION XAB/XAC/XAN/XAP/XAW/XBB/XBN/ XEL/XES/XEX/XND/XOX/XPB/XPC/XPL/XPN/XPS/XPV/XPX *S ALL ECONOMY SPECIAL SAP/SB/SBP/SH/SIP *P ALL ECONOMY PROMOTIONAL PBT/PCF/PCR/PEM/PG/PGA/PGC/PGI/ PGM/PGN/PGO/PGV/PGZ/PIT/PM/PMI/PRO/PS/PSA/PSD/PSZ/PTP/PU/ PVU/PZ *A ALL ADD-ON AC/AD/AF/AS/AY *Y ALL ECONOMY ALL FARE TYPES EXCEPT ADD-ON/FIRST/BUSINESS/ PREMIUM ECONOMY TYPES Note: As fare types are added and amended in the ATPCO Fare Matrix, the definitions above will also change to reflect new fare types. 159

162 Coding the Sequence List Screen Any Fare Type Example Figure 108: Any Fare Type example FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/FLIGHTS DO ANY FARE TYPE DO FARES EACH FLT SEGMENT RBD FOR 01 L REQ NOTE NOTES; H - - ALL ECONOMY ALL FARE TYPES EXCEPT ADD-ON/FIRST/ BUSINESS/PREMIUM ECONOMY TYPES Figure 109: RBD Text H Note: Before coding, determine the order of sequences. Sequences follow the same principle as all Rules applications: from most specific to least specific. 160

163 Coding the Sequence List Screen Travel Segment Indicator Figure 110 TSI field Travel Segment Indicators (TSIs) identify the portion of travel that must be present in order to match the segment. TSIs can be coded alone or in conjunction with the location fields to modify the application of the geography. The TSI application may be fare component (FC), fare component/pricing unit (FC/PU), pricing unit (PU), or journey (J); however, validation of the TSI is always against a portion of the fare component being validated and is not against the pricing unit or journey. Processing will attempt to validate the point/portion of travel (sector) specified by the TSI against the fare component being validated and will not go outside the fare component and attempt to validate on the pricing unit/journey. 161

164 Coding the Sequence List Screen Example TSI 42 (departure of each transatlantic sector) indicates that processing should attempt to validate the departure of transatlantic sectors on a portion of travel on the fare component being validated. TSI 01 (departure from fare origin) indicates that processing should attempt to validate the departure from the origin of the pricing unit on a portion of the fare component being validated (if the pricing unit origin is on another fare component, then no-match the sequence). TSI 59 (departure of journey origin) indicates that processing should attempt to validate the departure from the point of origin of the journey on a portion of the fare component being validated (if the journey origin is on another fare component, then no-match the sequence). Coding TSIs Determine whether requirements pertain to certain travel segment indicators (TSIs). If so, you can code this information. Tab to the TSI field located under the Travel header. Type the applicable TSI code. You may also click the right side of the field to open the TSI look-up list, from which you may search and select codes for use. TSIs are used in conjunction with locales or can stand alone. TSIs and portions of travel can be combined in one sequence. Figure 111 TSI Look-up list 162

165 Coding the Sequence List Screen Valid TSIs The list below identifies the most frequently used TSIs in RBDs and their application (FC/PU/J). Additional TSIs are viewable on the TSI look-up list. TSI Definition Application 18 All international sectors FC/PU 19 All domestic sectors FC/PU 43 Departure of each transpacific sector FC 42 Departure of each transatlantic sector FC 31 Transatlantic sector(s) FC/PU 76 All domestic sectors of the journey J 32 Transpacific sector(s) FC/PU 47 Overwater segment(s) FC/PU 40 Departure of outbound transatlantic sector PU 89 On each intercontinental sector FC/PU 82 Departure from gateway FC/PU 56 Departure of inbound transatlantic sector PU 55 Departure of inbound transpacific sector PU 41 Departure of outbound transpacific sector PU 33 Outside the following geographic locale FC/PU 49 Arrival at the following geographic locale FC/PU 12 Arrival at destination gateway FC/PU 75 All international sectors of the journey J 06 Departure from origin gateway FC/PU 48 Departure of first international sector FC/PU 83 Arrival at gateway FC/PU 163

166 Coding the Sequence List Screen Directional Indicator Not Required The Direction field allows you to specify RBD restrictions based on the passenger s direction of travel. When Direction is coded, geography is required in Location 1 and in Location 2 when Origin Location 2 is coded. Figure 112 Sequence List screen with each directional value coded Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE ANY ANY FARE FLT SEGMENTS FROM LON 1ST V REQ ARRIVAL IN EUROPE ANY ANY FARE FLT SEGMENTS FROM LAST POINT Q REQ IN EUROPE-LON OAL ANY FARE OAL FARE ORIGINATING LON- EUROPE EACH FLT SEGMENT K REQ OAL ANY FARE OAL FARES ORIGINATING EUROPE- LON EACH FLT SEGMENT Z REQ Figure 113: RBD Text Determine whether RBD requirements apply to the direction of travel or fare origin. If based on direction of travel, follow these steps. Tab to the Directional Indicator field. Select From Location 1 to indicate the provision applies for travel from location 1 to location 2 164

167 Coding the Sequence List Screen Select To Location 1 to indicate the provision applies for travel from location 2 to location 1 When the Directional Indicator field is coded, the location field to which it refers is required. From/To values are based on the direction of travel within the fare component regardless of how the fares were selected. Figure 114 Sequence List screen with From LON to Zone 210 (Europe) (first sequence) Figure 115 Details screen with From LON to Zone 210 (Europe) Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE ANY ANY FARE FLT SEGMENTS FROM LON 1ST ARRIVAL IN EUROPE V REQ Figure 116: RBD Text Figure 117 Sequence List screen with From Zone 210 (Europe) to LON (second sequence) 165

168 Coding the Sequence List Screen Figure 118 Details screen with From Zone 210 (Europe) to LON Segment 1 (What is the fare?) OAL indicates Other Airlines Excluding the Publishing Carrier Must Match Fare Component Origin Location 1 (LON) Segment 2 (How are passengers transported on my airline to be booked on OAL s fare?) Booking Code K is Required. Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE ANY ANY FARE FLT SEGMENTS FROM LAST POINT IN EUROPE-LON Figure 119: RBD Text Determine whether RBD requirements depend on direction of travel or fare origination. If based on fare origination, tab to Directional Indicator field: Select Origin Location 1 to indicate the RBD provision applies to fares originating in Location 1. Select Origin Location 2 to indicate the RBD provision applies to fares originating in Location 2. When you Origin Location 1 or Origin Location 2, you must set the Must Match Fare Component tag on the Expanded screen. Q REQ When coding directionality, the location field to which it refers is required. Origin Location 1 and Origin Location 2 values are based on origination. Origination is determined by the origination point of the fare component when the fare is used outbound and the destination point of the fare component when the fare is being used inbound. When Directional Indicator is coded for Origin Location 1 or Origin Location 2, edits require that IF Tag be coded to match to the fare component. Figure 120 Sequence List screen with Originating LON to Zone 210 (Europe) (second sequence) 166

169 Coding the Sequence List Screen Figure 121 Details screen with Originating LON to Zone 210 (Europe) Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE OAL ANY FARE OAL FARE ORIGINATING LON- EUROPE EACH FLT SEGMENT K REQ Figure 122: RBD Text Segment 1 (What is the fare?) OAL indicates Other Airlines Excluding the Publishing Carrier Must Match Fare Component Origin Location 2 (Europe) Segment 2 (How are passengers transported on my airline to be booked on OAL s fare?) Booking Code Z is Required. Figure 123 Sequence List screen with Origination Zone 210 (Europe) to LON (second sequence) 167

170 Coding the Sequence List Screen Figure 124 Details screen with Origination Zone 210 (Europe) to LON Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE OAL ANY FARE OAL FARES ORIGINATING EUROPE- LON EACH FLT SEGMENT Z REQ Figure 125: RBD Text 168

171 Coding the Sequence List Screen Location 1, Location 2, and Type Figure 126 Loc 1, Loc 2, and Type fields Required when directionality is coded The Location fields indicate which travel portions are applicable for the RBD information. The Location fields may indicate cities, states, zones, countries, and areas. Information in these fields can be indicated as from/to, between/and, or origination from. TSI restrictions may also apply to these locales. When the same location is coded in Location 1 and Location 2, the application is within. When the Directional field is set with From/To in combination with Location 1 or Location 2 fields, the booking code applies FROM the direction of the specified location or TO the direction of the specified location. When the Directional field is coded with a value of Origin in combination with Location 1 or Location 2 fields, the booking code applies Originating from the specified location. The Direction field may only be set with Origin values when using the Expanded screen. (Must Match Fare Component is required when Originating is used.) 169

172 Coding the Sequence List Screen Coding Locations Determine whether restricting RBD requirements by location is required. If locations are needed, type a code or click the right side of the field to open the Help List for Locations. For every coded location, place a corresponding type code (city, state, nation, zone, area, or airport) in the Type fields by clicking the drop-down menu and selecting an option. Tab to Location 1 input the applicable location code. City/Airport codes are 3 letters States/Provinces are 2-letter State/Province code, space, 2-letter Nation code for US or CA Nation codes are 2 letters Zones are 3 numbers Areas are 01, 02, or 03 If more than one location is required, tab to Type and Location 2 and input the second location. Make sure that the hierarchy is correct (city before state and nation before zone, for example). Up to 2 locations may be present. When Location 1 is present and Location 2 is blank, the geographic point specified in Location 1 applies from/to. The fourth sequence applies for any travel from or to LON. Figure 127 Sequence List screen for RBDs When both Location 1 and Location 2 are present, the specified geographic points have a between/and relation application. The last sequence applies for travel between NYC and BOS. Figure 128 Sequence List screen for RBDs When the same geographic point is specified in Location 1 and Location 2, the application is within. 170

173 Coding the Sequence List Screen The third sequence applies for travel within France. Figure 129 Sequence List screen for RBDs The application of Loc 1 and Loc 2 may be modified by data in the TSI field and/or the Directional field. Figure

174 Coding the Sequence List Screen Sector Figure 131 Sector field Not Required Coded on Segment 2 to indicate how to book the Chart 2 owner on primary/secondary sectors of YY fares Sector is intended for use in Chart 2 when you are specifying how to book a passenger traveling on your carrier s equipment when using an IATA (YY) fare. Use these values to specify what RBD is required when your airline provides travel on the primary sector and what RBD is required when your airline provides travel on the secondary sector for YY fares. To code this field, select Primary or Secondary from the drop-down menu. Select Primary or Secondary to indicate whether the data in the segment applies for the primary or secondary portion of travel. Leave the Primary/Secondary field blank to indicate that the data in the segment applies to either the primary or secondary portions of travel. If travel is the primary portion of travel or on secondary portions of travel, processing will match the segment. When validating RBD data for a domestic fare (includes AllFares Domestic and US/CA Domestic), if Primary or Secondary is present, the processing will no-match the sequence and continue to the next sequence. Note: Determination of primary and secondary portions of travel is based on the guidelines set forth by IATA. Portion Figure 132 Portion field Not Required The Portion of Travel field is a match field that identifies a specified portion of travel for which the specified RBD applies. 172

175 Coding the Sequence List Screen The validation occurs based upon the ticketed points of the passenger s travel. When the Portion of Travel field is blank, the data within this sequence applies to any portion of travel unless specifically identified in the other fields for geography. Coding Portion of Travel Determine whether RBD requirements pertain to certain travel portions. Tab to the Portion field. Click the right side of the field to access a drop-down menu with a list of codes. Select the Portion of Travel by clicking the value. Portions of Travel usually stand alone. Portion of Travel and TSIs can be combined in one sequence. 173

176 Coding the Sequence List Screen Portion drop-down menu The following values are valid for the Portion drop-down menu. Value Atlantic portion Domestic portion Within Eastern Hemisphere Domestic except US/CA Pacific portion Within Western Hemisphere Validates Against Sector that crosses the Atlantic Ocean. One end point of the sector is in Area 1, the other end point of the sector is in Area 2/3, and the global indicator of the fare component encompassing the sector being validated refers to the Atlantic Ocean. Domestic sector. Both end points of the sector are in the same ATPCO country code. Note the following exceptions: Travel between countries XU/RU is domestic. Travel between United States and Canada is not domestic. Travel between countries in Scandinavia is not domestic. Travel between a nation and its territory possessing its own ATPCO Country Code is not domestic travel (cabotage travel is not domestic). Travel between a nation and its territory not possessing its own ATPCO Country Code is considered part of the sovereign state and is domestic. Both end points of the sector are in Area 02 or one end point is in Area 02 and the other end point is in Area 03. Both end points of the sector are in the same ATPCO country code (does not apply to country codes US and CA). Note the following exceptions: Travel between countries XU/RU is domestic. Travel between countries in Scandinavia is not domestic. Travel between a nation and its territory possessing its own ATPCO Country Code is not domestic travel (cabotage travel is not domestic). Travel between a nation and its territory not possessing its own ATPCO Country Code is considered part of the sovereign state and is domestic. Sector that crosses the Pacific Ocean. One end point of the sector is in Area 1, the other end point of the sector is in Area 2/3, and the global indicator of the fare component encompassing the sector being validated refers to the Pacific Ocean. Both end points of the sector are in Area

177 Coding the Sequence List Screen First Date/Last Date Figure 133 RBD Chart 1 showing First Date and Last Date fields The First Date and Last Date fields indicate the first and last dates on which the provisions in this segment apply. The date range fields in RBDs act much the way they do throughout the Rules system. RBDs may be applicable on a specific date, set of dates, or date range using these fields. RBD data may be restricted to a specific date range. Two fields are available. To code the first date range, tab to the First Date field and enter the date in DDMMM YY or DDMMM format. When coding DDMMM YY, the date must be tomorrow or later. You may also click the calendar icon to open a calendar from which you may select dates. To code the second date range tab to the Last Date field and input the last date, following the same format for the first date. Note: If only the first field is coded, the system will fill in the second field with the same date. 175

178 Coding the Sequence List Screen Day of Week Figure 134 RBD Chart 1 showing Day of the Week fields This field is used to apply the RBD data to a specific day or a range of days of the week. The system assumption is that any given RBD applies all seven days of the week. You can override this assumption by coding specific days of the week To code days of the week, simply select the checkboxes of the days that apply. Up to six days can be tagged at once. If you try to tag all seven days, you would be restating the system assumption, which the system will not allow. Days of the week are another restrictive capability that will generate a numeric note. 176

179 Coding the Sequence List Screen Time of Day Figure 135 RBD Chart 1 showing First Time and Last Time fields This field is used to apply the RBD data to a specific time or time period and may be used in conjunction with days of the week. You may specify the time format that you wish to use by clicking the Preferences link. If you choose to use 24-hour clock, type times using the HHMM format (for example, 0700). If you choose to use the 12-hour clock, type four numbers, using the 12-hour clock. Indicate immediately following the time entered which time applies: A for AM P for PM For the 12 o clock hour, indicate: N for Noon M for Midnight To enter a second time, tab to the Last field and enter the time as instructed. If the time is entered only in the first field, the system will generate 1200M in the last field. If the time is entered only in the last field, the system will generate 1201A in the first field. The system will generate a numeric note in text to indicate this type of restrictive capability. 177

180 Coding the Sequence List Screen Figure 136: Preference options 178

181 Coding the Sequence List Screen Flights Figure 137 Flights fields Not Required The Flights group-box contains fields that allow you to indicate a specific flight number or a range of flight numbers for the RBD restriction. When the fields are blank, there are no restrictions to the flight numbers for the RBD provision specified. The fields allow you to specify RBDs to be applicable to one or more flight numbers. Choose Or or Through as the relationship between flight one and flight two based on whether you want the flights to be individual or a range. (Not permitted when Must Match Fare Component is coded.) Note: When Must Match Fare Component is coded, edits prevent you from entering Flight Number 1 and/or Flight Number 2 on Segment 1 of the sequence (cannot enter Flight Number data in the If segment). Flight Number data may be entered in the second through the fifth segments of the sequence). RBD data may only apply to one specific flight number, to a series of flight numbers, or to a flight range. To code flight numbers, tab to Number 1 field located under the Flights header and type the first number. Flight numbers can be 1 to 4 digits. Next, tab to the Or/Through field. If flight numbers are to be read separately, select Or from the drop-down menu: RBD applies on flight 16 or 17. For a flight range, select Through from the drop-down menu: RBD applies on flights 16 through 20. To add a second flight, tab to the Number 2 field and type the second number. The system will allow encoding only of positive statements, as in RBD applies to flight numbers 2000 through If your instruction reads This RBD does not apply to flight range , the statement has to be reverted to a positive statement: RBD applies to flight range 1 through 1999 and RBD applies to flight range 3001 through Note: If several flight numbers or ranges are needed, then multiple sequences must be added. Remember: Flight numbers must be coded without leading digits. Flight number 1 will be coded as 1, not as Flight number 16 will be coded as 16 not as This aids the autopricing process. 179

182 Coding the Sequence List Screen Equipment Type Not Required Figure 138 RBD Chart 1 showing Equipment Type field RBD data may be restricted to a specific equipment type, such as only on a train, a bus, a jet, or a Boeing 747. Type equipment type codes in the field. If the code for the requested equipment is not known, click the Equipment Type hyperlink to open the Equipment Type look-up list, from which you may search for and select codes for use. Figure 139 Equipment Type look-up Once the data is coded, the system will automatically generate a numeric note describing the equipment restriction. There are no restrictions to the equipment type when this field is blank. Note: When If Matching Fare Component is coded, edits prevent entering Equipment Type in the first segment of the sequence (cannot enter Equipment Type in the Segment 1). Equipment Type may be entered in the second through the fifth segments of the sequence. 180

183 Coding the Sequence List Screen Point of Sale Figure 140 RBD Chart 1 showing Point of Sale group-box Not Required Segment 1 and Segment 2 The Point of Sale field allows you to code TSI 33 (Outside the location specified in the next field) or to specify the location where the fare may be sold. RBD data may be restricted to a certain point where the fare may be sold. This restriction can only be coded within the expanded screen. Once within the expanded screen, tab to the TSI or T LOC fields located under the Point of Sale header. To enter a location, choose a type from the Type drop-down menu: Nation Zone City Airport Area State Tab to the LOC field and enter a code. Click the Location link to open the Help List for Locations from which you may search for and select codes for use. 181

184 Coding the Sequence List Screen Sell/Ticket Figure 141 Sell/Ticket field Not Required Use the Sell/Ticket field to indicate that the RBD provision applies when the sale and ticketing are within or outside the country of origin. Available values on the Sell/Ticket drop-down menu include: SITI: Sales Inside, Ticketing Inside SOTO: Sales Outside, Ticketing Outside SOTI: Sales Outside, Ticketing Inside SITO: Sales Inside, Ticketing Outside 182

185 Coding the Sequence List Screen Sequence Number Figure 142 Sequence field Multiple RBD restrictions may apply within your RBD provisions for Chart 1 and Chart 2. Therefore, sequence numbers are required to identify the order in which the GDS should process the chart. When your GDS is processing RBD data, the GDS will process the sequences in order of lowest numbered sequence to the highest numbered sequence. RBD data should be sequenced from most specific (lowest number) to least specific (highest number). Sequence numbers may be 1 through 9,999,999 but are automatically assigned by the Rules system when data is saved. You may move the order of sequence by right-clicking a sequence and then selecting the Move command. When creating a new sequence, you may first choose the point of insertion to order the sequence by right-clicking and selecting the Insert (before or after) command. When determining the order of a new sequence, be sure to consider the sequence numbers already in use and how you will code future data. It is important that you use sequence numbers with large gaps between them in case you need to add new restrictions between existing sequences. If you have data coded in Segment 1 and Segment 2, the sequence number will be shown twice to indicate additional requirements apply. Figure

186 Coding the Sequence List Screen Summary Field Must Match/If Matching Carrier APPL RBD Fare Class/Fare Family Fare Type TSI DI Type LOC 1/LOC 2 Sector Portion First/Last Date Day of Week First/Last Time Flights Equipment Point of Sale Sell/Ticket Sequence Description This field allows you to specify whether the segment must match the fare component or the portion of travel. Specifies the owning carrier of the fare component being validated and/or the marketing carrier providing transportation on the sector being validated. RBD Application. To see a list of application codes, click the right side of the field; the RBD Application look-up will appear. Indicates the applicable reservation booking designator(s) that applies once all data in the segment is matched. Indicates that the data in the segment applies to fares with the specified fare class code or fare family. Fare Class appears on the Chart 2 screen only. Indicates that the data in the segment applies to fares with the specified fare type code. Indicates that the RBD data in the segment applies to the specified point/portion of travel within the fare component being validated. Indicates the directional application of the Geographic Specification data in the Location fields. The Type fields describe the data coded in the LOC 1 and LOC 2 fields. Options include: city, state, nation, zone, area, and airport. Indicates that the data in the segment applies to the specified locale(s) within the fare component or to fare components with the specified locale(s) as terminal points. The Sector field may be used to indicate that the RBD applies to the primary or secondary sectors of travel. Indicates that the data in the segment applies to the specified portion of travel within the fare component being validated. These fields may be used to indicate the first and last date applicable travel may occur. These fields may be used to specify days or a range of days on which the RBD may apply. This field may be used to indicate the first and last time applicable travel may occur. These fields may be used to specify applicable flight numbers or a range of flight numbers. To specify a range, select the Through option from the Or/Through dropdown menu. This field may be used to specify equipment types that may be used for the segment. Click the Equipment Type hyperlink to open a look-up with a list of valid codes. This field may be used to specify the location at which sales must or may not occur. To indicate that sales may not occur at a certain location, select the Outside checkbox. This drop-down menu may be used to indicate that the sale and/or issuance of a ticket must occur inside or outside the country of commencement. Identifies the order in which the data should be processed. 184

187 Coding the Details Screen Coding RBD data on the Details screen

188

189 Coding the Details Screen Mission After completing this module, you will be able to update the Details screen for your Chart 1 and Chart 2 provisions. Why is this module important? The Details screen contains the same fields that may be coded on the Sequence List screen. However, they are displayed in a form format that may be easier for some users. 187

190 Coding the Details Screen Fields and values Figure 144 RBD Chart 2 Details The Details screen consists of these fields: If Matching For Carrier Fare Class/Fare Type Fare Class/Family (Fare Family only on Chart 1) Fare Type 188

191 Coding the Details Screen Travel TSI (travel segment indicator) Direction (directional indicator) Type (referring to location type of LOC 1) Location 1 Type (referring to the location type of LOC 2) Location 2 Sector Portion of Travel First Date Last Date First Time Last Time Day of Week (Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday) Flights Flight 1 On/Through Flight 2 Equipment Type Point of Sale Outside Type Location Sell/Ticket RBD (two fields) Application (application) 189

192 Coding the Details Screen If Matching Figure 145 If Matching field The If Matching tag identifies the relationship between multiple segments within a single sequence. The values within this field define how to match the data within the sequence. You may code up to 5 recurring segments within a single sequence within the RBD Table. When data applies to a sector, validation is against ticketed points. These are the valid values for this field: Fare Component Portion of Travel This field is required when you create If Then provisions for your RBDs. When coding this provision, use two segments: Segment 1 is considered the IF condition. Segment 2 is considered the THEN condition. Note: Remember that a sequence can consist of no more than five segments and the relationship between segments is AND, making all a MUST condition. 190

193 Coding the Details Screen Carrier Segment 1 Via Carrier: Whose fare? Segment 2 Via Carrier: Who is providing the transportation? Figure 146 Carrier field Required Segment 1 and Segment 2 The Carrier field enables you to 1. Specify RBD data for the carrier that is providing transportation for your fare (Chart 1). 2. Specify how to book passengers when your carrier provides transportation on another carrier s fare (Chart 2). Chart coding differences Value Application Chart 1 Chart 2 Non-concurring Must be present in the Concurrence table Not Permitted Carriers Permitted OAL Any carrier except the owning carrier Not Permitted Permitted In Chart 1, the carrier code will cross edit against the Concurrence Table when coded with any carrier code other than the Chart 1 owner. If the carrier is non-concurring, edits restrict coding non-concurring carriers unless permitted in the Concurrence Table. 191

194 Coding the Details Screen Fare Class/Fare Type Figure 147 Fare Class/Fare Type field In the Fare Class/Fare Family field, type the fare class, fare type, or fare family as applicable. Click the right side of the of the Fare Type field to open the Fare Type look-up list from which you may search for and select a code for use. Choose a fare type that describes what you typed in the Fare Class/Fare Family field. The Fare Type indicator identifies the type of data coded in the Fare Class/Family field. The list that follows identifies the valid values and their application. Type Notes Fare Class Code Only valid in Chart 2 Fare Type Code Example: XAP Fare Family Example: YH- type fares Arbitrary Example: M***** type fares Coding Fare Type Type a valid Fare Type field or click the Fare Type link to open the Fare Type look-up list from which you may search for and select fare type codes. 192

195 Coding the Details Screen TSI Figure 148 TSI field Travel Segment Indicators (TSIs) identify the portion of travel that must be present in order to match the segment. TSIs can be coded alone or in conjunction with the location fields to modify the application of the geography. The TSI application may be fare component (FC), fare component/pricing unit (FC/PU), pricing unit (PU), or journey (J); however, validation of the TSI is always against a portion of the fare component being validated and is not against the pricing unit or journey. Processing will attempt to validate the point/portion of travel (sector) specified by the TSI against the fare component being validated and will not go outside the fare component and attempt to validate on the pricing unit/journey. To code the field, type a valid TSI code or click the TSI link to open the TSI look-up list from which you may search for and select codes for use. Figure 149 TSI look-up list 193

196 Coding the Details Screen Direction Figure 150 Direction field Not Required Segment 1 and Segment 2 The Directionality field allows you to specify RBD restrictions based on the passenger s direction of travel. Code these fields only when specifying geography in Location 1 and Location 2. These are the applicable Direction values: From Location 1 To Location 1 Origin Location 1 Origin Location 2 194

197 Coding the Details Screen From/To Determine whether RBD requirements apply to the direction of travel or fare origin. If based on direction of travel, follow these steps. Step 1. Tab to the Direction field. Select From Location 1 to indicate the provision applies for travel from location 1 to location 2 Select To Location 1 to indicate the provision applies for travel from location 2 to location 1 When the Directionality field is coded, the location field to which it refers is required. From/To values are based on the direction of travel within the fare component regardless of how the fares were selected. Figure 151 Sequence List screen with From LON to Zone 210 (Europe) Figure 152 Details screen with From LON to Zone 210 (Europe) Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE ANY ANY FARE FLT SEGMENTS FROM LON 1ST ARRIVAL IN EUROPE V REQ Figure 153 Sequence List screen with From Zone 210 (Europe) to LON Figure 154 Details screen with From Zone 210 (Europe) to LON 195

198 Coding the Details Screen Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE ANY ANY FARE FLT SEGMENTS FROM LAST POINT IN EUROPE-LON Q REQ Origin Determine whether RBD requirements depend on direction of travel or fare origination. If based on fare origination, tab to Direction field: Segment 1 (What is the fare?) OAL indicates Other Airlines Excluding the Publishing Carrier Must Match Fare Component Origin Location 1 (LON) Select Origin Location 1 to indicate the RBD provision applies to fares originating in Location 1. Select Origin Location 2 to indicate the RBD provision applies to fares originating in Location 2. When you select Origin Location 1 or Origin Location 2, you must set the Must Match Fare Component tag on the Details screen. When coding directionality, the location field to which it refers is required. Origin Location 1 and Origin Location 2 values are based on origination. Origination is determined by the origination point of the fare component when the fare is used outbound and the destination point of the fare component when the fare is being used inbound. When Directional Indicator is coded for Origin Location 1 or Origin Location 2, edits require that the If tag be coded to match to the fare component. Figure 155 Sequence List screen with Originating LON to Zone 210 (Europe) Segment 2 (How are passengers transported on my airline to be booked on OAL s fare?) Booking Code K is Required. Figure 156 Details screen with Originating LON to Zone 210 (Europe) 196

199 Coding the Details Screen Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE OAL ANY FARE OAL FARE ORIGINATING LON- EUROPE EACH FLT SEGMENT K REQ Figure 157 Sequence List screen with Origination Zone 210 (Europe) to LON Segment 1 (What is the fare?) OAL indicates Other Airlines Excluding the Publishing Carrier Must Match Fare Component Origin Location 2 (Europe) Figure 158 Details screen with Origination Zone 210 (Europe) to LON Chart 2 Default RBDs RES BOOKING DESIGNATORS FOR TRANSPORTATION ON 01 OWN/ PUB FARE IDENTIFIER LOCATIONS/FLIGHTS RBD NOTE OAL ANY FARE OAL FARES ORIGINATING EUROPE- LON EACH FLT SEGMENT Z REQ Segment 2 (How are passengers transported on my airline to be booked on OAL s fare?) Booking Code Z is Required. 197

200 Coding the Details Screen Type, Location 1, and Location 2 Figure 159 Type and Location 1/Location 2 fields Required when directionality is coded The Location fields indicate which travel portions are applicable for the RBD information. The Location fields may indicate cities, states, zones, countries, and areas. Information in these fields can be indicated as from/to, between/and, or origination from. TSI restrictions may also apply to these locales. When the same location is coded in Location 1 and Location 2, the application is within. When the Directional field is set with From/To in combination with Location 1 or Location 2 fields, the booking code applies FROM the direction of the specified location or TO the direction of the specified location. When the Directional field is coded with a value of Origin in combination with Location 1 or Location 2 fields, the booking code applies Originating from the specified location. The Direction field may only be set with Origin values when using the expanded screen. (Must Match Fare Component is required when Originating is used.) 198

201 Coding the Details Screen Coding locations Determine whether restricting RBD requirements by location is required. If locations are needed, type codes in the fields. You may also click the Location 1 and/or Location 2 fields to open the Help List for Locations, from which you may search for and select codes for use. For every coded location, place a corresponding type code (city, state, nation, zone, area, or airport) in the Type fields by clicking the drop-down menu and selecting an option. Figure 160 Help List for Locations City/Airport codes are 3 letters States/Provinces are 2-letter State/Province code, space, 2-letter Nation code for US or CA Nation codes are 2 letters Zone codes are 3 numbers Areas are 01, 02, or 03 If more than one location is required, tab to Type and Location 2 and type the second location. Make sure that the hierarchy is correct (city before state and nation before zone, for example). Up to two locations may be present. 199

202 Coding the Details Screen Sector Figure 161 Sector field Not Required Coded on Segment 2 to indicate how to book the Chart 2 owner on primary/secondary sectors of YY fares Sector is intended for use in Chart 2 when you are specifying how to book a passenger traveling on your carrier s equipment when using an IATA (YY) fare. Use these values to specify what RBD is required when your airline provides travel on the primary sector and what RBD is required when your airline provides travel on the secondary sector for YY fares. To code this field, select Primary or Secondary from the drop-down menu. Select Primary or Secondary to indicate whether the data in the segment applies for the primary or secondary portion of travel. Leave the Primary/Secondary field blank to indicate that the data in the segment applies to either the primary or secondary portions of travel. If travel is the primary portion of travel or on secondary portions of travel, processing will match the segment. When validating RBD data for a domestic fare (includes AllFares Domestic and US/CA Domestic), if Primary or Secondary is present, the processing will no match the sequence and continue to the next sequence. Note: Determination of primary and secondary portions of travel is based on the guidelines set forth by IATA. 200

203 Coding the Details Screen Portion of Travel Figure 162 Portion of Travel field Not Required Segment 1 and Segment 2 The Portion of Travel field is a match field that identifies a specified portion of travel for which the specified RBD applies. The validation occurs based upon the ticketed points of the passenger s travel. When the Portion of Travel field is blank, the data within this sequence applies to any portion of travel unless specifically identified in the other fields for geography. Coding Determine whether RBD requirements pertain to certain travel portions. If so, you can code this information on the Brief or Expanded screens. Tab to the Portion field. To research options for this field, click Select the Portion of Travel by clicking the value. to view the list of all valid codes. Portions of Travel usually stand alone. Portion of Travel and TSIs can be combined in one sequence. Edits prevent the coding of the Portion of Travel field in the first segment of the sequence when the If field applies to the fare component. 201

204 Coding the Details Screen Portion of Travel field values Title Atlantic portion Domestic portion Within Eastern Hemisphere Domestic except US/CA Pacific portion Within Western Hemisphere Validates Against Sector that crosses the Atlantic Ocean. One end point of the sector is in Area 1, the other end point of the sector is in Area 2/3, and the global indicator of the fare component encompassing the sector being validated refers to the Atlantic Ocean. Domestic sector. Both end points of the sector are in the same ATPCO country code. Note the following exceptions: Travel between countries XU/RU is domestic. Travel between United States and Canada is not domestic. Travel between countries in Scandinavia is not domestic. Travel between a nation and its territory possessing its own ATPCO Country Code is not domestic travel (cabotage travel is not domestic). Travel between a nation and its territory not possessing its own ATPCO Country Code is considered part of the sovereign state and is domestic. Both end points of the sector are in Area 02 or one end point is in Area 02 and the other end point is in Area 03. Both end points of the sector are in the same ATPCO country code (does not apply to country codes US and CA). Note the following exceptions: Travel between countries XU/RU is domestic. Travel between countries in Scandinavia is not domestic. Travel between a nation and its territory possessing its own ATPCO Country Code is not domestic travel (cabotage travel is not domestic). Travel between a nation and its territory not possessing its own ATPCO Country Code is considered part of the sovereign state and is domestic. Sector that crosses the Pacific Ocean. One end point of the sector is in Area 1, the other end point of the sector is in Area 2/3, and the global indicator of the fare component encompassing the sector being validated refers to the Pacific Ocean. Both end points of the sector are in Area

205 Coding the Details Screen Date Range Figure 163 RBD Chart 1 showing First Date and Last Date fields The First Date and Last Date fields indicate the first and last dates on which the provisions in this segment apply. The date range fields in RBDs act much the way they do throughout the Rules system. RBDs may be applicable on a specific date, set of dates, or date range using these fields. RBD data may be restricted to a specific date range. Two fields are available. To code the first date range, tab to the First Date field and type the date in DDMMM YY or DDMMM format. When coding DDMMM YY, the date must be tomorrow or later. You may also click the calendar icon to open a calendar from which you may select dates. To code the second date range tab to the Last Date field and type the last date, following the same format for the first date. Note: If only the first field is coded, the system will fill in the second field with the same date. 203

206 Coding the Details Screen Time of Day Figure 164 RBD Chart 1 showing First Time and Last Time fields This field is used to apply the RBD data to a specific time or time period and may be used in conjunction with days of the week. Type four numbers, using the 12-hour clock. Indicate immediately following the time entered which time applies: A for AM P for PM For the 12 o clock hour, indicate: N for Noon M for Midnight To enter a second time, tab to the Last field and enter the time as instructed. If the time is entered only in the first field, the system will generate 1200M in the last field. If the time is entered only in the last field, the system will generate 1201A in the first field. The system will generate a numeric note in text to indicate this type of restrictive capability. 204

207 Coding the Details Screen Day of Week Figure 165 RBD Chart 1 showing Day of the Week fields This field is used to apply the RBD data to a specific day or a range of days of the week. The system assumption is that any given RBD applies all seven days of the week. You can override this assumption by coding specific days of the week. To code days of the week, simply select the check-boxes of the days which apply. Up to six days can be tagged at once. If you try to tag all seven days, you would be restating the system assumption, which the system will not allow. Days of the week are another restrictive capability that will generate a numeric note. 205

208 Coding the Details Screen Flights Figure 166 Flights fields Not Required The Flights group-box contains fields that allow you to indicate a specific flight number or a range of flight numbers for the RBD restriction. When the fields are blank, there are no restrictions to the flight numbers for the RBD provision specified. The fields allow the coder to specify RBDs to be applicable to one or more flight numbers. Choose Or or Through as the relationship between flight one and flight two based on whether you want the flights to be individual or a range. (Not permitted when Must Match Fare Component is coded.) Note: When Must Match Fare Component is coded, edits prevent you from entering Flight Number 1 and/or Flight Number 2 on Segment 1 of the sequence (cannot enter Flight Number data in the If segment). Flight Number data may be entered in the second through the fifth segments of the sequence). RBD data may only apply to one specific flight number, to a series of flight numbers, or to a flight range. 206

209 Coding the Details Screen To code flight numbers, tab to Number 1 field located under the Flights header and enter the first number. Flight numbers can be 1 to 4 digits. Next, tab to the Or/Through field. If flight numbers are to be read separately, select Or from the drop-down menu: RBD applies on flight 16 or 17. For a flight range, select Through from the drop-down menu: RBD applies on flights 16 through 20. To add a second flight, tab to the Number 2 field and type the second number. The system will only allow encoding of positive statements, as in RBD applies to flight numbers 2000 through If your instruction reads This RBD does not apply to flight range , the statement has to be reverted to a positive statement: RBD applies to flight range 1 through 1999 and RBD applies to flight range 3001 through Note: If several flight numbers or ranges are needed, then multiple sequences must be added. Remember: Flight numbers must be coded without leading zeros. Flight number 1 will be coded as 1, not as Flight number 16 will be coded as 16 not as This aids the autopricing process. 207

210 Coding the Details Screen Equipment Type Figure 167 RBD Chart 1 showing Equipment Type field Not Required RBD data may be restricted to a specific equipment type, such as only on a train, a bus, a jet, or a Boeing 747. Type equipment type codes in the field. If the code for the requested equipment is not known, click the Equipment Type hyperlink to open the Equipment Type look-up list, from which you may search for and select codes for use. Figure 168 Equipment Type look-up Once the data is coded, the system will automatically generate a numeric note describing the equipment restriction. There are no restrictions to the equipment type when this field is blank. Note: When If Matching Fare Component is coded, edits prevent entering Equipment Type in the first segment of the sequence (cannot enter Equipment Type in the Segment 1). Equipment Type may be entered in the second through the fifth segments of the sequence. 208

211 Coding the Details Screen Point of Sale Figure 169 RBD Chart 1 showing Point of Sale group-box Not Required Segment 1 and Segment 2 The Point of Sale field allows you to code TSI 33: Outside (and the location specified in the Location field) or to specify the location where the fare may be sold. RBD data may be restricted to a certain point where the fare may be sold. This restriction can only be coded on the Details screen. Once within the Details screen, tab to the TSI field in the Travel group box or Type and Location field located in the Point of Sale group box. To enter a location, choose a type from the Type drop-down menu: City State Nation Zone Area Airport Tab to the Location field and enter a code. Click the Location link to view the Help List for Locations list from which you may search for and select codes for use. 209

212 Coding the Details Screen Sell/Ticket Figure 170 Sell/Ticket field Not Required Use the Sell/Ticket field to indicate that the RBD provision applies when the sale and ticketing are within or outside the country of origin. These are the values on the Sell/Ticket drop-down menu: SITI: Sales Inside, Ticketing Inside SOTO: Sales Outside, Ticketing Outside SITO: Sales Inside, Ticketing Outside SOTI: Sales Outside, Ticketing Inside 210

213 Coding the Details Screen RBD and Application Figure 171 RBD Chart 1 showing RBD and Application fields Required when If matching: Fare Component is coded This field identifies how the RBDs specified in the RBD fields are to apply. Click the Application link to open the RBD Application look-up list, from which you may search for and select codes for use. These are the valid values for Application: Code Description P PERM Permitted R REQ Required W R/OF Required when Offered V R/AV Required when Available U ADD Additional significant data applies to the following RBD N NRBD No RBD applies carrier does not participate S STBY Standby X NPRM Associated RBD is not permitted 211

214 Coding the Details Screen Coding Application The RBD fields specify the applicable RBD(s) for the sector being validated. Up to two RBDs may be specified per line The relationship among the RBDs is OR, except when multiple segments are coded for one sequence number. 212

215 Coding the Details Screen Summary Field If matching For Carrier Fare Class/Family Fare Type TSI Direction Type Location 1/Location 2 Sector Portion of Travel First/Last Date First/Last Time Day of Week Flight 1/Or/Through/Flight 2 Equipment Type Outside/Type/Location Sell/Ticket Description This field allows you to specify whether the segment must match the fare component or the portion of travel. Specifies the owning carrier of the fare component being validated and/or the marketing carrier providing transportation on the sector being validated. Indicates that the data in the segment applies to fares with the specified fare class code or fare family. Fare Class appears on the Chart 2 screen only. Indicates that the data in the segment applies to fares with the specified fare type code. Indicates that the RBD data in the segment applies to the specified point/portion of travel within the fare component being validated. Indicates the directional application of the Geographic Specification data in the Location fields. The Type fields describe the data coded in the Location 1 and Location 2 fields. Options include: city, state, nation, zone, area, and airport. Indicates that the data in the segment applies to the specified locale(s) within the fare component or to fare components with the specified locale(s) as terminal points. The Sector field may be used to indicate that the RBD applies to the primary or secondary sectors of travel. Indicates that the data in the segment applies to the specified portion of travel within the fare component being validated. These fields may be used to indicate the first and last date applicable travel may occur. This field may be used to indicate the first and last time applicable travel may occur. These fields may be used to specify days or a range of days on which the RBD may apply. These fields may be used to specify applicable flight numbers or a range of flight numbers. To specify a range, select the Through option from the Or/Through drop-down menu. This field may be used to specify equipment types that may be used for the segment. Click the Equipment Type hyperlink to open a look-up with a list of valid codes. This field may be used to specify the location at which sales must or may not occur. To indicate that sales may not occur at a certain location, select the Outside check-box. This drop-down menu may be used to indicate that the sale and/or issuance of a ticket must occur inside or outside the country of commencement. 213

216 Coding the Details Screen Field RBD Application Description Indicates the applicable reservation booking designator(s) that applies once all data in the segment is matched. RBD Application. To see a list of application codes, click the right side of the field; the RBD Application look-up will appear. 214

217 Appendix A Definitions for RBDs

218

219 Definitions for RBDs RBD Chart 1 RBD Chart 2 marketing carrier non-concurring owning carrier primary portion of travel prime RBD RBD Record 6 Convention 1 Record 6 Convention 2 secondary portion of travel sector RBD information for the carrier owning the fare (aside from primary RBD) and for secondary carriers participating on the fare. Contains information on exceptions to the primary RBD. Same as Record 6 Convention 2. RBD default information for the marketing carrier who is on the ticket but does not own the fare (fare owner can be a carrier code or YY). Applies for secondary transportation on another carrier s fare, or for primary or secondary transportation on a YY fare. Same as Record 6 Convention 1. The carrier code that will appear on the flight coupon of the ticket (typically used for code share). When a carrier does not permit any other carrier to instruct or enter RBD data on their behalf for secondary transportation, then this carrier is non-concurring. The nonconcurring carrier chooses to publish RBD data in its own Record 6 Convention 1 for secondary sectors where they are the transporting carrier. ATPCO assumes that all carriers are non-concurring unless the carrier provides a concurrence agreement to ATPCO. The carrier who owns or publishes the fare (same as publishing carrier). For RBD processing, the owning carrier is either the carrier code on the Fare Class Application for the fare component being validated or the carrier code on the Category 25 sequence for the fare being created. A portion of travel of a fare component that determines the fare that will be selected for the entire fare component. Assigned to the fare by the Fare Class Application carrier (not valid for YY or *M fares unless a Carrier Table is present in the segment). Usually the first letter of the fare class code. The reservation booking designator (booking code) that can or must be used. RBD default information for the marketing carrier who is on the ticket but does not own the fare (fare owner can be a carrier code or YY). Applies for secondary transportation on another carrier s fare or for primary or secondary transportation on a YY fare. Same as Chart 2. RBD information for the carrier owning the fare (aside from primary RBD) and for secondary carriers participating on the fare. Contains information on exceptions to the primary RBD. Same as Chart 1. A portion of travel of a fare component that is not determined as primary portion of travel. A portion of a journey covered by a single flight coupon (used in international tariffs; same as segment). 217

220

221 Appendix B Chart detail information

222

223 Chart Detail Information Chart 1 Detail Information Must Match This field indicates whether the RBD segment must match the fare component or the portion of travel. Carrier This is the airline whose Airline Designator is recorded as the transporting carrier on the electronic flight/value coupon(s). This column will include one of the following: Carrier Code. For example, KL, QF, UA, TW, BA, AF, AI. OAL. Other Air Lines excluding the owner of the RBD chart. ANY. Any carrier. APPL (Application) P R W V U N S X O A G H Permitted Required Required when Offered Required when Available Additional significant data applies to the following RBD No RBD applies carrier does not participate Standby Associated RBD is not permitted Permitted when Prime Booking Code is not OFFERED Permitted when Prime Booking Code is not AVAILABLE Required when Prime Booking Code is not OFFERED Required when Prime Booking Code is not AVAILABLE RBD Specific Reservation Booking Codes that apply. There are two RBD fields. 221

224 Chart Detail Information Fare Family 1. Indicated by a single hyphen in place of one or more characters within the fare basis code. For example, in B-XE14 the hyphen represents either a complete number, letters, or a combination of the two; therefore, BKXE14, BHXE14, BK7XE14 and even BK7XE14N match. Fare families are shown in the format of B- XE14 TYPE. Fare Type 1. For example, XAP is Advanced Purchase and XPX is Instant Purchase. ATPCO needs carriers to provide the specific fare types and not statements such as Apex Fares, because there are multiple fare types which the carrier may or may not want included as an Apex fare. Fare types will be shown in the format of type - XPX. 2. An asterisk (*) plus the first character of an ATPCO Fare Type. Multiple Fare Types can also be represented by using the first character of a group of fare types preceded by an asterisk. For example, *E states that all fares with an ATPCO fare type commencing with E are included. Multiple fare types will display as ALL ECONOMY in the text. 3. Three asterisks (***) = any other fare Travel (Locations) Locations describes which portion of the fare is associated to the specified RBD. When this information is not instructed, the assumption will be that the RBD applies Each flight segment. When locations are instructed without identifying the portion of the fare to which the specified RBD applies, the assumption will be that it applies to flight segments departing from the last point in a location to the first arrival in a location. Use the drop-down menu in the Sector field to indicate whether the applicable travel sector is primary or secondary. Use the Portion drop-down menu to indicate that travel applies to Atlantic portion Domestic portion Within Eastern Hemisphere Domestic except US/CA Pacific portion Within Western Hemisphere First and last travel dates may be coded in the First Date and Last Date fields. You may specify valid days of the week or ranges of days using the check boxes for each week day. First and last travel times may be coded in the First Time and Last Time fields. 222

225 Chart Detail Information Flights These are flight numbers that must be used to apply the specific RBD. They must be stated in a positive manner. For example, FLTS would indicate that the RBD stated applies only when using the flight range specified. Some options for location information are as follows: 1. Each flight segment 2. Flt segments from last point in loc 1-1st arr in loc/vv 2 3. Flt segments from last point in loc - 1st arr in loc. 4. Flt segments from last point in loc or 1st arr in loc 5. Flt segments from last point in loc. 6. Flt segments to 1st arrival in loc. 7. Fares originating loc-loc. 8. Each flt segment portion of travel. 9. Each flt segment within loc. 10. Cxr fares originating loc-loc 11. Cxr fares for each cxr flt segment. 12. Cxr fares from/to loc for each cxr flt segment. 13. Cxr fares between loc-loc for each cxr flt segment. 14. Cxr fares originating loc-loc for each cxr flt segment. 15. Cxr fares originating loc-loc for each cxr flt segment within loc. 16. Cxr fares from loc-loc for each cxr flt segment. 17. Cxr fares between loc-loc for each cxr flt segment prt of tvl. 18. Cxr fares from loc-loc for each flt segment within loc. 19. Cxr fares between loc-loc for cxr flt segments from last pt in/1st arr in loc. 20. Cxr fares within loc for each cxr flt segment within loc. 21. Cxr fares within loc for cxr flt segments from last pt in loc - 1st arr in loc/vv. Some options for flight information are as follows: 1. Each flt segment on cxr flt(s) #(s). 2. Each flt segment within loc on cxr flt(s) #(s). 3. Flt segments from last pt in loc-1st arr in loc/vv on cxr flt(s) #(s). 4. Flt segments from last pt in loc-1st arr in loc on cxr flt(s) #(s). 5. Flt segments from last pt in/1st arr in loc on cxr flt(s) #(s). 6. Cxr flt(s) #(s) from last pt in loc-1st arr in loc/vv. 7. Cxr flt(s) #(s) from last pt in loc-1st arr in loc. 8. Cxr fares from/to loc for each cxr flt segment prt of tvl on flt(s) #(s). 9. Cxr fares originating loc-loc for each cxr flt segment on flts #(s). 1 loc = locale 2 vv = vice versa 223

226 Chart Detail Information 10. Cxr flt(s) #(s) from last pt in/1st arr in loc 11. Cxr fares from loc-loc for each cxr flt segment within loc on cxr flts #(s). 12. Cxr fares originating loc-loc for each flt segment within loc on cxr flts #(s). Additional standard phrases will be added as needed. The flight and location information may be combined. The Marketing carrier should be clearly stated. For example, Flt segments from Europe Africa/vv each flt segment within Europe on BA flts In this example, the fares may belong to South African Airways, but the RBD applicable is for the European portion on BA flights Note The note is the numbers or letters that refer to more information presented at the bottom of the page. Alphabetic notes are industry standard (note that definitions below are subject to change): A = All fare types that fall under *F (all first) B = All fare types that fall under *B (all business) C = All fare types that fall under *E (all normal economy) D = All fare types that fall under *X (all excursion) E = All fare types that fall under *S (all special economy) F = All fare types that fall under *P (all status promotional) G = All fare types that fall under *R (all premium first) H = All fare types *Y except *A, *F, *B, *R, *J, *W, *Z (all economy cabin) I = All fare types that fall under *A (all add-ons) J = All fare types that fall under *W (all premium economy normal) K =All fare types that fall under *J (all business economy special) L = All fare types that fall under *Z (all premium economy special) Z = Definitions of Fare Types used in this Chart Numeric notes are specific to a carrier. The most common note information involves locations and/or flights. Because this information is now included in the chart, notes should be kept to a minimum. 224

227 Chart Detail Information Chart 2 Detail Information Must Match This field will indicate if the RBD segment must match the fare component or the portion of travel. Carrier This is the carrier that owns/publishes the fare. For example, KL, QF, UA, BA, AF, OAL (other air lines). APPL (Application) P R W V U N S X Permitted. Required Required when Offered Required when Available Additional significant data applies to the following RBD No RBD applies carrier does not participate Standby Associated RBD is not permitted RBD These are specific Reservation Booking Codes that apply. There are two RBD fields. Fare Class/Fare Family 1. Fare Class Code. Specific 8-character fare class (fare basis) code. Note: This is only valid in Chart Hyphen (-) Fare Families. Indicated by a single hyphen in place of one or more characters within the fare basis code. For example, B-XE14 where the hyphen represents a complete number, letters, or a combination of the two; therefore, BKXE14, BHXE14, BK7XE14 and even BK7XE14N match. Fare families will be shown in the format of B-XE14 TYPE. 225

228 Chart Detail Information Fare Type For example, XAP is Advanced Purchase and XPX is Instant Purchase. ATPCO needs carriers to provide the specific fare types and not statements such as Apex Fares, because there are multiple fare types which the carrier may or may not want included as an apex fare. Fare types will be shown in the format of type - XPX. 1. Asterisk (*) plus the first character of an ATPCO Fare Type. Multiple Fare Types can also be represented by using the first character of a group of fare types preceded by an asterisk. For example, *E states that all fares with an ATPCO fare type commencing with E are included. Multiple fare types will display as ALL ECONOMY with fare types EU/ER/EAP/EIP in the text. 2. Three asterisks (***) = any other fare Travel (Locations) Locations indicate which portion of the fare is associated to the specified RBD. When this information is not instructed, the assumption will be that the RBD applies Each flight segment. When locations are instructed without identifying the portion of the fare to which the specified RBD applies, the assumption will be that it applies to Flight segments departing from the last point in a location to the first arrival in a location. Use the drop-down menu in the Sector field to indicate whether the applicable travel sector is primary or secondary. Use the Portion drop-down menu to indicate that travel applies to Atlantic portion Domestic portion Within Eastern Hemisphere Domestic except US/CA Pacific portion Within Western Hemisphere First and last travel dates may be coded in the First Date and Last Date fields. You may specify valid days of the week or ranges of days using the check boxes for each week day. First and last travel times may be coded in the First Time and Last Time fields. 226

229 Chart Detail Information Flights These are flight numbers that must be used to apply the specific RBD. They must be stated in a positive manner. For example, FLTS would indicate that the RBD stated applies only when using the flight range specified. Some options for location information are as follows: 1. Each flight segment 2. Flt segments from last point in loc 3-1st arr in loc/vv 4 3. Flt segments from last point in loc-1st arr in loc. 4. Flt segments from last point in loc or 1st arr in loc 5. Flt segments from last point in loc. 6. Flt segments to 1st arrival in loc. 7. Fares originating loc-loc. 8. Each flt segment portion of travel. 9. Each flt segment within loc. 10. Cxr fares originating loc-loc 11. Cxr fares for each cxr flt segment. 12. Cxr fares from/to loc for each cxr flt segment. 13. Cxr fares between loc-loc for each cxr flt segment. 14. Cxr fares originating loc-loc for each cxr flt segment. 15. Cxr fares originating loc-loc for each cxr flt segment within loc. 16. Cxr fares from loc-loc for each cxr flt segment. 17. Cxr fares between loc-loc for each cxr flt segment prt of tvl. 18. Cxr fares from loc-loc for each flt segment within loc. 19. Cxr fares between loc-loc for cxr flt segments from last pt in/1st arr in loc. 20. Cxr fares within loc for each cxr flt segment within loc. 21. Cxr fares within loc for cxr flt segments from last pt in loc-1st arr in loc/vv. Some options for flight information are as follows: 1. Each flt segment on cxr flt(s) #(s). 2. Each flt segment within loc on cxr flt(s) #(s). 3. Flt segments from last pt in loc-1st arr in loc/vv on cxr flt(s) #(s). 4. Flt segments from last pt in loc-1st arr in loc on cxr flt(s) #(s). 5. Flt segments from last pt in/1st arr in loc on cxr flt(s) #(s). 6. Cxr flt(s) #(s) from last pt in loc-1st arr in loc/vv. 7. Cxr flt(s) #(s) from last pt in loc-1st arr in loc. 8. Cxr fares from/to loc for each cxr flt segment prt of tvl on flt(s) #(s). 3 loc = locale 4 vv = vice versa 227

230 Chart Detail Information 9. Cxr fares originating loc-loc for each cxr flt segment on flts #(s). 10. Cxr flt(s) #(s) from last pt in/1st arr in loc 11. Cxr fares from loc-loc for each cxr flt segment within loc on cxr flts #(s). 12. Cxr fares originating loc-loc for each flt segment within loc on cxr flts #(s). Additional standard phrases will be added as needed. The flight and location information may be combined. The Marketing carrier should be clearly stated. For example, Flt segments from Europe Africa/vv each flt segment within Europe on BA flts In this example, the fares may belong to South African Airways, but the RBD applicable is for the European portion on BA flights Equipment Click the right side of the Equipment field to open the Equipment Type look-up list, from which you may select codes. Point of Sale Use the Point of Sale fields to restrict the location of sale. Select a location type from the Type drop-down menu. Type location codes in the Location field or click the right side of the field to open the Help List for Locations, from which you may search for and select codes for use. Sell/Ticket Use the drop-down menu to indicate that selling and ticketing must take place: SITI sold inside, ticketed inside the country of commencement SOTO sold outside, ticketed outside the country of commencement SITO sold inside, ticketed outside the country of commencement SOTI sold outside, ticketed inside the country of commencement 228

231 Chart Detail Information Note Numbers or letters that refer to more information presented at the bottom of the page. Alphabetic notes are industry standard (note that definitions below are subject to change): A = All fare types that fall under *F (all first) B = All fare types that fall under *B (all business) C = All fare types that fall under *E (all normal economy) D = All fare types that fall under *X (all excursion) E = All fare types that fall under *S (all special economy) F = All fare types that fall under *P (all status promotional) G = All fare types that fall under *R (all premium first) H = All fare types *Y except *A, *F, *B, *R, *J, *W, *Z (all economy cabin) I = All fare types that fall under *A (all add-ons) J = All fare types that fall under *W (all premium economy normal) K =All fare types that fall under *J (all business economy special) L = All fare types that fall under *Z (all premium economy special) Z = Definitions of Fare Types used in this Chart Numeric notes are specific to a carrier. The most common note information involves locations and/or flights. Because this information is now included in the chart, notes should be kept to a minimum. 229

232

233 Appendix C Chart format

234

235 Chart Format Chart 1 CXR: Geographic Coverage: RBD for all sectors is 1st letter of fare basis code? yes or no FARE IDENTIFIER LOCATIONS/FLIGHTS MKTG CXR RBD NOTE Notes 233

236 Chart Format Chart 2 CXR: RESERVATION BOOKING DESIGNATORS FOR SEGMENTS ON OTHER CARRIERS/YY FARES FARE OWNER/ PUBLISHER FARE IDENTIFIER LOCATIONS/ FLIGHTS RBD for NOTE Notes 234

237 Appendix D Non-concurring carrier list

238

239 Non-concurring Carrier List Nearly 500 carriers currently include their booking code information in ATPCO, making the information available in both automated and printed products. The non-concurring carrier list now includes nearly 200 carriers. The non-concurring carriers as of June 2016 are as follows: AA BI ET IB KX MX PX SY U6 Z6 AB BP EY IE K5 NH PZ S2 U9 3H AC BR FB IG LA NN P1 S3 VA 3L AF BT FI IT LG NU QF S4 VN 4M AH BW FJ IY LH NX QR S7 VS 5T AI B2 FM JJ LI NZ QS TA VV 7F AM B6 FP JL LO OA QV TG VX 7H AP B7 FV JP LP OK RJ TK VY 9B AR CA F7 JV LR OM RO TN V3 9U AS CI GA JZ LX OS RQ TP WF 9W AT CM GF J0 LY OU R7 TU WG AV CU GL J2 ME OV SA T3 WJ AX CX G3 KA MF OZ SB T7 WK AY CY HA KC MH PC SK UA WM AZ CZ HG KE MI PG SN UL WN A3 DL HM KL MJ PK SP UN XF BA EI HU KM MO PR SQ UO XL BE EK HX KQ MS PS SU US YM BG EN HZ KU MU PW SV UX YR When a carrier becomes non-concurring, a Bulletin is released to announce the new nonconcurrence. See the Bulletins page of our Web site for the most recent non-concurring carrier list. All carriers must review their booking code information to ensure that the abovementioned carriers have been removed. You can view which carriers have published permission for other carriers to file on their behalf in the RBD Concurrence Help screen in the FareManager Rules system. Carriers are reminded that the following information is critical to the accurate pricing of worldwide fares by GDSs: You may include booking code information in the ATPCO automated booking code product for fares worldwide. You are not required to have fares in the ATPCO fares database in order to provide booking code information. 237

240

241 Appendix E Private Chart 1 Download

242

243 Private Chart 1 Download RBD Private Chart 1 Download ATPCO has developed a download tool in FareManager so you can view your carrier s RBD information that is published in another carrier s private tariff Chart 1 and/or Fare By Rule (Category 25). Security does not allow you to access another carrier s Chart 1 and/or Fare By Rule through the Rules or GFS applications. If you have access to the FareManager Rules system, you can perform the download for your carrier. Step 1. In order to view RBD data that is found in another carrier s private Chart 1, go to the FareManager Rules home page. Type your carrier code in the Carrier field located under the RBD Download RBD Private Chart 1 heading and then click the button. Figure 172 Rules Home Page Step 2. Note: A file download pop-up window will appear. Click Open to view the file or Save to save the file to your computer. Internet Explorer may display a message that reads: To help protect your security, Internet Explorer blocked this site from downloading files to your computer. Click here for options Click the message and then select the Download File command. Figure 173 File Download pop-up window 241

244 Private Chart 1 Download Step 3. Double-click the RBDDOWNLOAD (USER ID and DATE).csv file to view the contents in Microsoft Excel. Figure 174 RBD Download.csv file Step 4. The WinZip pop-up window may open to confirm that you wish to open the file. Click the Open button to confirm. Figure 175 WinZip pop-up window Once the file is open, the Excel spreadsheet will appear in the format shown in Figure 176. Figure 176 Excel Spreadsheet Example Format If your carrier s RBD information does not exist in another carrier s private Chart 1, the spreadsheet will be blank. 242

245 Appendix F Screen images

246

247 Screen Images RBD Chart 1 Figure 177 RBD Chart 1: default view Figure 178 RBD Chart 1: default view with collapsed navigation pane 245

248 Screen Images Figure 179 RBD Chart 1: all columns view (scrolled left) Figure 180 RBD Chart 1: all columns view (scrolled right) 246

249 Screen Images Figure 181 RBD Chart 1: details screen 247

250 Screen Images RBD Chart 2 Figure 182 RBD Chart 2: default view Figure 183 RBD Chart 2: default view with collapsed navigation pane 248

251 Screen Images Figure 184 RBD Chart 2: all columns view (scrolled left) Figure 185 RBD Chart 2: all columns view (scrolled right) 249

252 Screen Images Figure 186 RBD Chart 2: details screen Figure 187 Chart 1 RBD Exceptions screen (scrolled left) Figure 188 Chart 1 RBD Exceptions screen (scrolled right) 250

253 Screen Images Figure 189: Chart 1 RBD Exceptions screen (scrolled right) Figure 190: Chart 1 RBD Exceptions screen (scrolled right) 251