Last Updated: 08/22/2011 - ATPCO Guides... · FROP Guide 2 August 22, 2011 Product Description...

Last Updated: 08/22/2011

Airline Tariff Publishing Company Washington Dulles International Airport

45005 Aviation Drive Dulles, VA 20166

Telephone: 703-471-7510 Fax: 703-471-1497 www.atpco.net

http://www.atpco.net/�

FROP Guide

ii August 22, 2011

Table of Contents

Introduction ................................................................................................................................... 1 Product Description ...................................................................................................................... 2

About FROP................................................................................................................................ 2 Security and Private Fare Data ................................................................................................... 2 Selection Parameters ................................................................................................................... 3 Distribution and Schedule ........................................................................................................... 3 File Recovery .............................................................................................................................. 4 Attention New Customers ........................................................................................................... 4

Selection Parameter Maintenance ............................................................................................... 5 Maintain Your Selection Parameters Online .............................................................................. 5

Date Conditions .................................................................................................................... 11 Electronically Transmit Your Selection Parameters ................................................................. 12 Instruct ATPCO to Maintain Your Selection Parameters ......................................................... 13

Record Layout Description ........................................................................................................ 14 Header ....................................................................................................................................... 14 Origin ........................................................................................................................................ 14 Destination ................................................................................................................................ 15 Fare Basis .................................................................................................................................. 15 One-way Amount ...................................................................................................................... 16 Round Trip Amount .................................................................................................................. 16 Advance Purchase ..................................................................................................................... 17 Minimum Stay .......................................................................................................................... 18 Filler .......................................................................................................................................... 19 Maximum Stay .......................................................................................................................... 19 Season Start/End Dates ............................................................................................................. 20 Direction of Period of Application ........................................................................................... 21 Reservation Booking Code ....................................................................................................... 21 Flight Application ..................................................................................................................... 22 Routing Number........................................................................................................................ 23 Rule Number ............................................................................................................................. 23 First Travel Date ....................................................................................................................... 24 First Sale Date ........................................................................................................................... 24 Children’s Discount .................................................................................................................. 25 Fare Indicator ............................................................................................................................ 25 Global Indicator ........................................................................................................................ 26 Carrier ....................................................................................................................................... 26 Currency .................................................................................................................................... 27 Last Travel Date ........................................................................................................................ 27 Last Sale Date ........................................................................................................................... 28 Tariff Number ........................................................................................................................... 28 Public/Private ............................................................................................................................ 29 Fare Type .................................................................................................................................. 30 Day of Week Application (Outbound/Inbound) ....................................................................... 31

FROP Guide

iii August 22, 2011

Output .......................................................................................................................................... 32 Record Layout Description—Header ....................................................................................... 33 Customer Support ....................................................................................................................... 34

Technical Support ..................................................................................................................... 34 Glossary ....................................................................................................................................... 35

Table of Figures

Figure 1: Native Applications Logon Screen .............................................................................. 5 Figure 2: ATPCO Main Menu ..................................................................................................... 6 Figure 3: ATPCO International System File Maintenance Selections Screen ........................ 6 Figure 4: ATPCO International System Special Maintenance Menu...................................... 7 Figure 5: ATPCO International System Maintenance Tables Menu ...................................... 7 Figure 6: ATPCO International System Fare/Rule Selection Parameters Screen ................. 8 Figure 7: ATPCO International System Fare/Rule Selection Parameters Screen ................. 9 Figure 8: ATPCO International System Fare/Rule Selection Parameters Table ................. 11 Figure 9: Sample Selection Parameters Text File .................................................................... 12

FROP Guide

1 August 22, 2011

Introduction This document describes the Fare Rule Output Product (FROP) and topics concerning the product’s composition, maintenance, and output.

The FROP Guide is divided into four major sections: Product Description, Selection Parameter Maintenance, Processing and Output, and Customer Support. The Product Description section describes FROP and its data coverage, distribution, and schedule. The Selection Parameter Maintenance section explains how to maintain your FROP selection parameters online, via electronic transmission, or by instructing ATPCO. The Processing and Output section defines the different fields of the standard FROP 137-byte record layout and addresses how the data you receive in your FROP records is obtained. Finally, the Customer Support section provides information on how to contact ATPCO should you have additional questions or problems regarding FROP.

FROP Guide

2 August 22, 2011

P roduc t Des c ription

About F R OP FROP is a data feed product composed of public, constructed, and/or private fares that are available for sale in the marketplace. FROP consists of two separate products: FROP International and FROP North America. FROP International is composed of public, private, and constructed fares for travel outside the United States and Canada. This includes fares that are between a point in the United States and a point outside the United States (except Canada) or between two points outside the United States and Canada. FROP North America is composed of public and private fares for travel within the United States and/or Canada. This includes fares between a point in the United States and a point in Canada, between two points in the United States, or between two points in Canada.

FROP offers three choices of fare and rule data: public, constructed, and private. Public data includes published International and North American fares and rules. Constructed data includes unpublished fares and rules resulting from an International fare and its arbitrary. Private data includes your private International and North American fares and rules and the private International and North American fares and rules owned by your partners.

Each fare received is combined with key elements from supporting rule, footnote, and fare basis information such as advance purchase, minimum and maximum stay, seasonality, children’s discount, ticketing and travel dates, day of week application, and flight application. All data that meets a customer’s selection criteria is selected and distributed each time FROP is run. FROP is sent to you in the form of fixed-length 137-byte records that are easy to load and parse. This makes FROP ready to employ and easy to incorporate into your own customized products.

S ecurity and P rivate F are Data As well as receiving their own private data, FROP customers can select and receive the private fares owned by a partner organization.

ATPCO uses a secure filtering program to ensure that FROP customers receive fares that only they are authorized to have. To receive private fares that your organization does not own, instruct ATPCO in writing as to the private fares you wish to receive. Send requests to select private data and FROP Instruction Template forms to Product Support (e-mail, [email protected]). After ATPCO receives and verifies your request to access private data, you will be able to select private tariffs using one of the three methods described in the Selection Parameters section.

mailto:[email protected];�

FROP Guide

3 August 22, 2011

S election P arameters You choose the fares and rules you need in FROP by using selection parameters or filters such as tariff, carrier, country pairs, city pairs, fare basis, and directionality. There are three easy ways of managing your selection parameters. You can maintain your selection parameters online via ATPCO’s International Fare System. You can also transmit your selection parameters to ATPCO in a prescribed record layout. Alternatively, you can instruct ATPCO to maintain your selection parameters for you, in which case, you are responsible for notifying ATPCO of changes. All fares that match your selection parametersin effect at the time of processingare selected from ATPCO databases, merged into FROP’s record layout, and sent to you.

To instruct ATPCO to maintain your selection parameters, you must give 14 days advance notice to enable ATPCO to build the initial criteria. Afterward, you may instruct ATPCO in writing of changes to your selection parameters between the hours of 8:30 a.m. and 5:30 p.m. (EST) Monday through Friday. To instruct ATPCO to begin or continue maintaining your selection criteria, contact Product Support (e-mail, [email protected]). ATPCO will make all necessary efforts to update requests within 48 hours of their receipt.

For more information about selection parameters, please see the Selection Parameter Maintenance section.

Dis tribution and S chedule FROP can be distributed to you as frequently as once per day (seven days a week) or on a prearranged schedule (weekly, monthly, etc). FROP can also be distributed on an on-demand basis. FROP begins processing at approximately 8:00 p.m. (EST) on weekdays and 5:00 p.m. (EST) on weekends and distributes data after processing is completed. Neither processing nor distribution occurs on Christmas Day, New Year’s Day, or Easter Sunday. Fourteen days advance notice is required to establish an initial schedule. Changes in schedule may be made on the basis of the same advanced notification. To set up or make a change to your schedule, contact Product Support.

You may receive your data by electronic transmission (IBM Netview FTP or Internet FTP) or on an IBM T3480 or T3490 cartridge. Alternatively, you can opt to obtain FROP files yourself (instead of having ATPCO send FROP files via electronic transmission or via IBM cartridge). To set up or change your method of data distribution or schedule, contact Product Support (e-mail, [email protected]).



FROP Guide

4 August 22, 2011

F ile R ecovery ATPCO retains FROP files for 45 days after processing. Arrangements can be made to resend any file within this timeframe. To request file recovery, contact Product Support (e-mail, [email protected]).

Attention New C us tomers New customers must complete the following tasks to ensure proper FROP transmission:

• Sign the FROP contract (be sure to include your current mailing address) and send it via mail or fax to ATPCO: c/o FROP, Product Manager, Washington Dulles International Airport, PO Box 17415, Washington, DC, 20041-0415 (fax, 703-471-1497).

• Notify ATPCO of your intended distribution schedule (do you want FROP data every day, once a week, once a month, etc?).

• Notify ATPCO of the type of product you want to receive (do you want FROP International or FROP North America?).

• Notify ATPCO of the type of fare information you want to receive by including the tariff code (do you want private fares, public fares, or both?).

• Notify ATPCO if you wish to receive private fares that your organization does not own.

• Notify ATPCO of your intended distribution method (do you want to receive your FROP data via electronic transmission or on an IBM T3480 or T3490 cartridge?).

• Notify ATPCO of your intended selection maintenance method (do you want to update your selection parameters yourself or do you want ATPCO to update your selection parameters for you?). Please see the Selection Parameter Maintenance section for more information.

• Make sure you understand the Service Level Agreement.


FROP Guide

5 August 22, 2011

S elec tion P arameter Maintenanc e

Maintain Y our S election P arameters Online The FROP selection table contains the parameters that determine the fares you receive in your FROP output. This table is accessed via ATPCO’s International Fare System; therefore, you will need access authority for this system. You can access and update the table yourself or you can instruct ATPCO to maintain the table for you. The screens shown below are those that appear in the Native Applications which can be accessed using FareManager Econnect (http://econnect.atpco.net/).

NOT E : B efore F R OP c us tomers c an ac c es s F areManager E c onnec t they mus t obtain a us er name and pas s word from AT P C O. F or ins tructions on how to obtain a us er name and pas s word, c ontac t P roduct S upport (e-mail, F R OP @ atpc o.net).

To code the FROP selection table:

1. Open a Native Applications session.

Figure 1: Native Applications Logon Screen

2. Enter your user name and password.

3. Press Ctrl. The Main Menu will appear.


FROP Guide

6 August 22, 2011

Figure 2: ATPCO Main Menu

4. Enter the number corresponding to the International Fare System (8 in Figure 2) or type internat (the International Fare System option) and press Ctrl. The ATPCO International System File Maintenance Selections screen will appear.

PITM400 ATPCO INTERNATIONAL SYSTEM 03APR 08 FILE MAINTENANCE SELECTIONS 16:37:24 1. Special Maintenance 2. Construction Tables Enter Selection: Printer Id: 00 Copies: 01 PF1 2 3 4 5 6 7 8 9 10 11 12 Printers End Exit

Figure 3: ATPCO International System File Maintenance Selections Screen

5. Enter 1 (the Special Maintenance option) and press Ctrl. The ATPCO International System Special Maintenance Menu will appear.

FROP Guide

7 August 22, 2011

PITM700 ATPCO INTERNATIONAL SYSTEM 03APR 08 SPECIAL MAINTENANCE MENU 16:39:40 1. Maintenance Tables 2. Zone Special Job Submission 3. Zone Special Job Display Enter Selection: PF1 2 3 4 5 6 7 8 9 10 11 12 End Exit

Figure 4: ATPCO International System Special Maintenance Menu

6. Enter 1 (the Maintenance Tables option) and press Ctrl. The ATPCO International System Maintenance Tables Menu will appear with your user ID prefilled.

PITM705 ATPCO INTERNATIONAL SYSTEM 03APR 08 MAINTENANCE TABLES MENU 16:40:48 Select the Table Type: 2 1. Inclusive Table 2. Fare/Rule Product 3. Zone Special Table Select the Table Option: 2 ---inclusive tables--- Cxr Table No. Ctry City FC Zone 1. Create _ _ _ _ _ 2. Display/Modify AA ___ 3. Delete ___ ___ 4. Print ___ ___ 5. Copy Table ___ ___ Copy To: ___ 6. List ___ ___ PF1 2 3 4 5 6 7 8 9 10 11 12 Init End Delete Print Exit

Figure 5: ATPCO International System Maintenance Tables Menu

FROP Guide

8 August 22, 2011

7. Type 2 for the Table Type and 2 for the Table Option. Then press Ctrl. The Fare/Rule Selection Parameters table will appear.

Figure 6: ATPCO International System Fare/Rule Selection Parameters Screen

There are ten selection parameter fields in the Fare/Rule Selection Parameters table. They are described below (required fields are indicated in bold letters):

A Action: (A) Add, (D) Delete, or (C) Change a parameter.

I Include/Exclude Parameter: Entering I (for Include) will result in a FROP file that includes any fare segment that meets all other selection criteria. Entering E (for Exclude) will result in a FROP file that excludes any fare segment that meets all other selection criteria.

D

Direction of the flight: (T) To, (F) From, or (B) Bidirectional. These values apply only to the direction of the flight. A value of T (to origin) will match a fare record with a first city code that matches the destination and a second city code that matches the origin. A value of B (between) will match any fare record with a first city code that matches either the origin or the destination and a second city code that matches the other entry. A value of F (from origin) will match a fare record with a first city code that matches the origin and a second city code that matches the destination.

Prop Prop Number: (000) This selection parameter field is prefilled.

Tariff

Tariff: Enter a valid fares tariff (maximum, seven alphanumeric characters). The tariff will be verified as either a valid International public fares tariff, valid International private fares tariff owned by the FROP customer, valid North American public fares tariff, or valid North American private fares tariff owned by the FROP customer.

Cxr

Carrier: Enter a carrier code. The carrier code will be verified as a valid carrier. This field may be left blank, in which case the FROP customer will obtain data for every carrier that is valid for the tariff entered (public tariffs) and is eligible to be accessed by the FROP customer (private tariffs).

City and Country

When coded, this information (detailed in the next four cells) refers to the origin and destination of each fare segment being processed. An exact match is required when origin or

FROP Guide

9 August 22, 2011

Codes destination city (Cty) is provided. If only origin or destination country (Ctry) is provided, then the applicable city within each fare is ignored and an exact country match is required.

NOTE: The value of some city codes in either the origin city or destination city field will cause additional parameters to be programmatically created with additional airport codes or new city codes supplementing the original entry. For example, an entry of NYC in the Fare/Rule Selection Parameters table would produce a query including JFK, EWR, and LGA. The new parameters are not stored on the FROP Selection table.

Orig Cty Origin City: Enter a three-letter city code.

Orig Ctry Origin Country: Enter a two-letter country code (this field is automatically filled when the origin city is entered).

Dest Cty Destination City: Enter a three-letter city code.

Dest Ctry Destination Country: Enter a three-letter country code (this field is automatically filled when the destination city is entered).

FC Fare Basis: When provided, fare basis indicates a value that must be matched for a fare segment to be selected. All fare bases are selected if this value is not provided.

Const ID Construction ID: International published and constructed (Y), North American published (D), International published only (S), and International constructed only (C).

Press the Tab key to move from field to field while you code the Fare/Rule Selection Parameters screen. To add many parameters quickly, press PF4 to obtain a screen with prefilled fields, including A, D, and Prop.

By either defining the parameters or leaving them undefined, you can launch queries that are either broad or specific. For example, you could code a FROP selection table as follows:

Figure 7: ATPCO International System Fare/Rule Selection Parameters Screen

1 2 3 4 5 6 7

FROP Guide

10 August 22, 2011

According to the parameters entered in Figure 7, lines 1–7 are described as follows:

1. The FROP customer is interested in including all published and constructed fares in tariff EUROP between London, United Kingdom, and Paris, France, for all fare bases on British Airways.

2. The FROP customer asks to exclude all published and constructed Y class fares in tariff EUROP provided by British Airways between London, United Kingdom, and Paris, France.

3. The FROP customer asks for all published fares in tariff EUROPD1 for British Airways between London, United Kingdom, and all other locations.

4. The FROP customer asks for all published and constructed fares in tariff TAFP for British Airways from Chicago, IL, USA, to London, United Kingdom.

5. The FROP customer asks for information on all published and constructed fares in tariff TAFP for British Airways to Washington, DC, USA, from London, United Kingdom.

6. The FROP customer excludes bidirectional constructed Qantas Airways fares in tariff TPFP for fare class F.

7. The FROP customer asks for information on all published and constructed Qantas Airways fares between Washington, DC, USA, and Sydney, Australia.

FROP Guide

11 August 22, 2011

Date Conditions The Fare/Rule Selection Parameters (Figure 8) table will have one of the following date conditions:

Figure 8: ATPCO International System Fare/Rule Selection Parameters Table

1. No date provided.

In this case, the current date is assumed and data is selected for further processing, provided the data does not have a discontinue date or a last ticketing date before the current date.

2. From date is provided.

The date coded is treated the same way as the current date in that data is selected for further processing provided it does not have either a discontinue date or a last ticketing date before the coded date. The date entered may represent a past, current, or future date.

NOTE: To select historical data, code a past date in the From field. For example, a fare with a last travel date of 15FEB00 can be selected on 16FEB00 by coding a From field of 14FEB00. Note that data will be purged from the ATPCO databases 7 days after its discontinue date.

3. Both From and To dates are provided.

In this case, the To date will always be equal to or greater than the From date. Data is selected for further processing provided it does not have a discontinue date or a last ticketing date before the From date or an effective date or a first travel date after the To date. In other words, the

From and To date fields

FROP Guide

12 August 22, 2011

selected date must have a date that falls somewhere within the range specified by the From and To dates.

E lectronically T rans mit Y our S election P arameters Selection parameters can be transmitted and automatically uploaded to the FROP selection table. You can transmit your selection parameters by creating a plain text (ASCII) file in the proper format and transmitting the file using your local procedures. If you are interested in transmitting your selection parameters, contact Product Support (e-mail, [email protected]).

To create a plain text file (ASCII) with FROP selection parameters:

1. Open a plain text file (ASCII).

2. Use the following table to enter parameter information.

FIELD DESCRIPTION REQUIRED FIELD? FIELD WIDTH BYTE LOCATION Reserved Yes 2 0001–0002 Carrier Code No 3 0003–0005 Tariff Code Yes 7 0006–0012 Filler No 3 0013–0015 First City Code No 5 0016–0020 First Country Code No 2 0021–0022 Second City Code No 5 0023–0027 Second Country Code No 2 0028–0029 Fare Class No 8 0030–0037 Directionality (B/F/T) No (default B) 1 38 Include/Exclude (I/E) No (default I) 1 39 Construction ID (Y/S/C/D) Noa 1 40 Filler Yes 55 0041–0084 a This field defaults to Y for International tariffs or D for North American tariffs.

Each time you transmit selection parameters, you must complete an 84-byte text file. The first two bytes are reserved (enter two spaces). The third through fifth bytes are reserved for the carrier code; therefore, enter the two-letter carrier code and one space. Continue until you have filled all 84 bytes. For example, the customer could prepare the following data to transmit:

Figure 9: Sample Selection Parameters Text File

…

1. B A T A F P W A S U S P A R F R Y B I Y

2. A A T A F P P A R F R W A S U S

3. U A T P F P C H I U S S Y D A U

4. Q F T P F P N Y C U S H K G H K

5. A S P F 0 1 W A S U S A N C U S 1 2 3 4 5 6 7 8 F I D

FROP Guide

13 August 22, 2011

According to the parameters entered in Figure 9, lines 1–4 are described as follows (see next page):

1. The FROP customer wants published and constructed fares for carrier BA with a TAFP tariff between Washington DC, USA, and Paris, France for fare class Y.

2. The FROP customer wants fares for carrier AA between Paris, France, and Washington DC, USA; the customer specifies the TAFP tariff code.

3. The FROP customer wants fares with a TPFP tariff code between Chicago, IL, USA, and Sydney, Australia.

4. The FROP customer wants QF fares with a TPFP tariff code between New York, NY, USA, and Hong Kong.

5. The FROP customer wants AS fares with a PF01 tariff code from Washington, DC, to Anchorage, AL, for fare class 12345678.

After transmitting the above data, any preexisting entries will be automatically deleted from the FROP selection table. However, it is possible to retain old parameters and add new parameters simultaneously. To accomplish this task, contact Product Support (e-mail, [email protected]).

Ins truct AT P C O to Maintain Y our S election P arameters

To instruct ATPCO to maintain your selection parameters, you must give 14 days advance notice to enable ATPCO to build the initial criteria. Afterward, you may instruct ATPCO in writing of changes to your selection parameters between the hours of 8:30 a.m. and 5:30 p.m. (EST) Monday through Friday. To instruct ATPCO to begin or continue maintaining your selection criteria contact Product Support (e-mail, [email protected]; telephone number, (703) 471-7510 ext. 1465; fax number, (703) 471-1497; hours, M–F 8:30 AM to 5:30 PM). ATPCO will make all necessary efforts to complete update requests within 48 hours of their receipt.


FROP Guide

14 August 22, 2011

R ec ord L ayout Des c ription This section describes the fields that are included on the standard 137-byte record layout. Refer to the Record Layout attachment for a summary.

Header A header record occurs once as the first record of a file. It provides the date and time at which the file was created, and the number of records in the file. The value output to bytes 1-2 is null. The value output to bytes 3-16 is a date and time stamp in the mm/dd/yyhhmmss format (month/day/yeartime). The value output to bytes 17-25 is the numeric record count, right justified with leading zeros.

Following is an example of a FROP output record:

Header (bytes 1–16)

********************************* Top of Data ********************************** ..10/20/03200811000009619

This record was created on 20 October 2003 at 8:08:11 PM and contained 9,619 records.

Origin Origin information is obtained from the origin of the fare record. The value output to bytes 1–3 is a three-letter city code representing the origin of the fare.

Following is an example of a FROP output record (the text has been wrapped to save space):

Origin (bytes 1–3)

WASLONBPX20 000002814000000005628000001 SU 001M201199 121299 BF3000 3284191199 191199075.00SATYY USD26030026030000001P EIP-----X------XX

According to the output record, this fare has an origin of Washington, DC.

FROP Guide

15 August 22, 2011

Des tination Destination information is obtained from the destination of the fare record. The value output to bytes 4–6 is a three-letter city code representing the destination of the fare.


Destination (bytes 4–6)


According to the output record, this fare has a destination of London, United Kingdom.

F are B as is Fare basis information is obtained from the fare class of the fare record. The value output to bytes 7–14 is an industry code up to eight alphanumeric characters long that signals governing conditions in an abbreviated form such as class of service, booking code, minimum or maximum stay, peak or off-peak seasonality, weekend or midweek travel. This code is carrier-specific and is provided in the fare record.


Fare Basis (bytes 7–14)


According to the output record, this fare has a fare basis of BPX20.

FROP Guide

16 August 22, 2011

One-way Amount One-way amount information is obtained from the fare amount field of the fare record. The value output to bytes 15–26 is the one-way amount of the fare presented with three zeros to the right of the implied decimal point. If the fare can only be priced as a round trip, then spaces are output. If there is no round trip amount on the FROP record, then the fare can only be priced one-way.


One-way Amount (bytes 15–26)


According to the output record, this fare has a one-way amount of 2,814.00.

R ound T rip Amount Round trip amount information is obtained from the fare amount field of the fare record. The value output to bytes 27–38 is the round trip amount of the fare presented with three zeros to the right of the implied decimal point. If the fare can only be priced as a one-way, then spaces are output. If there is no one-way amount on the FROP record, then the fare can only be priced as a round trip.


Round Trip Amount (bytes 27–38)


According to the output record, this fare has a round trip amount of 5,628.00.

FROP Guide

17 August 22, 2011

Advance P urc has e Advance Purchase information is obtained from rule and footnote Category 5 (advance reservations and ticketing). Rule Category 5 is processed first. Footnote Category 5 is processed only in the event that a matching rule Category 5 is not found.

Advance reservation information is processed first, with advance ticketing information processed only when advance reservation information is not located. The value output to bytes 39–41 is the amount of time that reservations or ticketing must be made before travel. Because of space limitations, a period of time reflected in days is numeric (e.g., 030 = 30 days), whereas a period of time reflected in months is alphanumeric (e.g., 01M = 1 month). If the advance reservations or ticketing requirement is measured in hours or minutes, FROP will output blanks. If there are neither advance reservations nor advance ticketing requirements, then the value output to bytes 39–41 is blank, indicating that no requirements exist.


Advance Purchase (bytes 39–41)


According to the output record, this fare has a 1-day advance purchase requirement.

FROP Guide

18 August 22, 2011

Minimum S tay Minimum stay information is obtained from the rule and footnote Category 6. The governing rule is processed before the footnote to determine if there is a minimum stay requirement.

The value output to bytes 42–44 specifies the first time return may commence. The minimum stay requirement can be a day of the week or a number of days or months. For a day of the week stay, a two-letter abbreviation is output, indicating the night on which the passenger is required to stay. For example, if a passenger must spend a Sunday night at a destination, then the output would read SU, indicating Sunday. For a several day stay, a three-character alphanumeric value is output. For example, if a passenger must spend 7 days at a destination, then the output would read 07D, indicating 7 days. For a month or longer stay, a three-character alphanumeric value is output. For example, if a passenger must spend 1 month at a destination, then the output would read 01M, indicating 1 month. If there is no minimum stay requirement, then spaces are output in bytes 42–44.


Minimum Stay (bytes 42–44)


According to the output record, this fare has an overnight minimum stay requirement, indicating that the customer must spend a Sunday night at the destination before returning.

FROP Guide

19 August 22, 2011

F iller The value output to byte 45 is always a space because byte 45 is reserved as a filler.


Filler (byte 45)


According to the output record, there is a space in byte 45. For every fare, there will always be a space in byte 45 because byte 45 is reserved as a filler.

Maximum S tay Maximum stay information is obtained from the rule and footnote Category 7. The governing rule is processed before the footnote to determine if there is a maximum stay requirement.

The value output to bytes 46–49 specifies the last time return travel may commence or must be completed. The maximum stay requirement can be that a passenger returns on a specific day of the week or a numbers of days or months. If a passenger is required to return on a specific day, a three-letter abbreviation is output indicating the day on which the passenger is required to return. For example, if passengers must return the first Sunday after arrival, then the output would read SUN, indicating Sunday. For a return required after several days, a four-character alphanumeric value is output. For example, if passengers must return 7 days after arrival, then the output would read 007D, indicating 7 days. For a return required after a month or longer, a four-character alphanumeric value is output. For example, if passengers must return 1 month after arrival, then the output would read 001M, indicating 1 month. If there is no maximum stay requirement, then spaces are output in bytes 46–49.


Maximum Stay (bytes 46–49)


According to the output record, this fare includes a maximum stay requirement of 1 month.

FROP Guide

20 August 22, 2011

S eas on S tart/E nd Dates Season start/end dates are obtained from the rule and footnote Category 3 (seasonal application). Both the footnote and rule are processed.

The values output to bytes 50–62 specify the permitted dates of travel. The result is a seasonal range, which may cover more than one time period. If there is one pair of season start and end dates, then one FROP record will be generated. If there is more than one pair of season start and end dates, then more than one FROP record will be generatedone for each season. In this way, a unique FROP output record is created for each applicable period of seasonal application. This will also occur when there are different seasonal applications in both the governing rule and footnote.

The season start/end dates field in the FROP output record is composed of two six-byte date fields with a blank space separating them. The dates refer to the beginning and end of a season and are output in DDMMYY format (with YY not always filled). A season of February (i.e., from February to February) will default to a date range 0102___0128__.


Season Start/End Dates (bytes 50–62)


According to the output record, this fare has a season start date of November 20, 1999, and a season end date of December 12, 1999. Note that byte 56 is a filler and will always be filled with a space.

FROP Guide

21 August 22, 2011

Direction of P eriod of Application The direction of period of application is obtained from the rule and footnote Category 3 (seasonal application). Both the footnote and the rule are processed.

The value output to byte 63 is the direction of period of application requirement. This field is filled by determining the travel application assumption override requirement. The assumption for Category 3 is that a seasonal fare is based on the date of the originating flight of the priceable unit. If the assumption is overridden, then an R is output to the FROP record. This is an abbreviation of the default value RU, which means refer to rule (or footnote, if this is where the period of application was obtained). If the seasonal application applies to the date of the originating flight of the priceable unit, then a space is output to the FROP record.


Direction of Period of Application (byte 63)


According to the output record, the assumption that a seasonal fare is based on the date of the originating flight of the priceable unit applies to this fare.

R es ervation B ooking C ode Reservation booking code information is obtained from the first character of the fare basis code indicating the primary booking code. The value output to byte 64 is a one-character value that determines the class of service in which to book the customer.


Reservation Booking Code (byte 64)


According to the output record, this fare has reservation booking code of ‘B.’

FROP Guide

22 August 22, 2011

F light Application Flight application information is obtained from Category 4. Rule Category 4 is processed first, with footnote Category 4 processed only in the absence of rule Category 4 data.

• If travel is required on direct flights, then D is output. However, if travel is not required on direct flights, processing continues.

• If the fare is only valid (or not valid) on certain flight numbers, then an F is output.

• If no specified flight restriction applies, then FROP will output a different code to indicate a different type of restriction.

• For restrictions concerning travel via specified locations, FROP will output a V.

• For restrictions concerning certain airports, FROP will output an A. For restrictions concerning certain carriers, FROP will output a C.

• If more than one of these three restrictions exists (travel, airport, or carrier), FROP will output an M to signify that multiple restrictions exist.

If none of the restrictions indicated above are found, then no flight restrictions are associated with the fare product, and a blank is output.


Flight Application (byte 65)


According to the output record, this fare has a flight restriction.

FROP Guide

23 August 22, 2011

R outing Number Routing number information is obtained from the fare record. The value output to bytes 66–69 is either a code that identifies transfer and stopover points and the carriers that may be used for travel or the value 0000, indicating a maximum permitted–mileage condition applies.


Routing Number (bytes 66–69)


According to the output record, routing number 3000 governs this fare.

R ule Number Rule number information is obtained from the fare record. The value output to bytes 70–74 is a code that defines the conditions associated with a fare.


Rule Number (bytes 70–74)


According to the output record, rule number 3284 governs this fare.

FROP Guide

24 August 22, 2011

F irs t T ravel Date First travel date information is obtained from the rule and footnote (when present) Category 14 (travel restrictions).

The value output to bytes 75–80 is the earliest date on which a passenger may travel. If there is a fare with multiple first travel dates, then the earliest date is determined and compared with the effective date, and the most restrictive date is output as the effective date of the fare. The date is output in DDMMYY format.


First Travel Date (bytes 75–80)


According to the output record, this fare has a first travel date of November 19, 1999.

F irs t S ale Date First sale date information is obtained from the rule and footnote Category 15 (sales restrictions). Category 15 data found in the governing rule is compared with any data found in the footnote, and the most restrictive date is used.

The value output to bytes 81–86 is the earliest date on which any one sector may be ticketed. If there is a fare with multiple first sale dates, then the earliest first sale date is compared with the effective date on the fare record. If the first sale date is greater than the effective date, then the effective date is changed to equal the first sale date. In this way, the FROP fare product cannot be used for travel before it is eligible to be ticketed. The resulting first sale date is output in the DDMMYY format. If there is a fare without a first sale date, then spaces are output indicating no ticketing restrictions.



First Sale Date (bytes 81–86)

According to the output record, this fare has a first sale date of November 19, 1999.

FROP Guide

25 August 22, 2011

C hildren’s Dis count Children’s discount information is obtained from the rule or footnote Category 19 (children’s discounts). The governing rule is processed first; if there is no rule, then the footnote is used to determine any applicable children’s discount.

The value output to bytes 87–92 is the percentage of a fare that a child would be charged. If there is only one children’s discount possible, then a percent is output to the FROP record. If more than one level of children’s discount is possible (excluding infants), the default indicator RU is output (meaning refer to rule). If no matching Category 19 data is found, then there is no children’s discount possible, and spaces are output to the FROP record.



Children’s Discount (bytes 87–92)

According to the output record, this fare has a 75% children’s discount.

F are Indicator Fare indicator information is obtained by processing the tariff code from the fare record against an ATPCO Tariff Identification directory. The value output to byte 93 is one of three letters, which represent one of three meanings. If the fare is published, then an S is output. If the fare is unpublished (constructed), then a C is output. If the fare is considered North American, then a D is output.



Fare Indicator (byte 93)

According to the output record, the value in byte 93 is an S, indicating that this fare is published.

FROP Guide

26 August 22, 2011

G lobal Indicator Global indicator information is obtained from the fare record. The value output to bytes 94–95 is a two-letter code that applies to a specific part of the world. For example, if AF was output to bytes 94–95, the fare would have a global that meant via Africa. For more information on global indicators, see the Glossary.



Global Indicator (bytes 94–95)

According to the output record, this fare has a global indicator of AT, indicating that the fare is via Atlantic.

C arrier Carrier information is obtained from the fare record. The value output to bytes 96–98 is a two- or three-letter carrier code, indicating the carrier who owns the fare.



Carrier (bytes 96–98)

According to the output record, carrier YY will provide air travel for this fare.

FROP Guide

27 August 22, 2011

C urrenc y Currency information is obtained from the fare record. The value output to bytes 99–101 is the monetary unit that applies to the one-way and round trip amounts of the fare.



Currency (bytes 99–101)

According to the output record, this fare costs 2814.00 one-way and 5628.00 round trip. These amounts are in US Dollars because of the USD value output to bytes 99–101. If, for example, this fare had a round trip amount measured in British pounds, then the value output to bytes 99–101 would appear as GBP.

L as t T ravel Date Last travel date information is obtained from the rule and footnote (when present) Category 14 (travel restrictions).

The value output to bytes 102–107 is the last date on which return travel must either commence or be completed. If there is a fare with multiple last travel dates, then the most restrictive date is output. If no dates exist, then 999999 is output, indicating that the record applies indefinitely. The resulting value output to bytes 102–107 is in the format DDMMYY.



Last Travel Date (bytes 102–107)

According to the output record, the last day on which a passenger can travel using this fare is March 26, 2000.

FROP Guide

28 August 22, 2011

L as t S ale Date Last sale date information is obtained from Category 15 (sales restrictions). Category 15 is processed differently than most other Categories in that both the rule and footnote is processed.

The value output to bytes 108–113 is the last sale date of the fare and represents the last date on which ticketing may occur on all sectors. If there is a fare with multiple last sale dates, then the most restrictive date is output.

In the absence of any Category 15 data, in either the rule or footnote(s), the discontinue date from the fare is applied. A default of 999999 is used in the absence of any fare discontinue date.



Last Sale Date (bytes 108–113)

According to the output record, this fare has a last sale date of March 26, 2000.

T ariff Number Tariff number information is obtained from the fare record. The value output to bytes 114–118 is the tariff number. The tariff number directly corresponds to the name of the tariff. For example, the tariff number 00005 corresponds to the WHFP tariff.



Tariff Number (bytes 114–118)

According to the output record, this fare has a tariff number of 00001, which corresponds to the TAFP tariff.

FROP Guide

29 August 22, 2011

P ublic/P rivate Public/private information is obtained from processing the tariff code against an ATPCO Tariff Identification directory. The value output to byte 119 is one of three one-letter tags that indicate one of three tariff types. If the tariff is private, then an R is output. If the tariff is public, then a P is output. If the fare belongs to a prerelease tariff, then an A is output.



Public/Private (byte 119)

According to the output record, this fare belongs to a public tariff.

FROP Guide

30 August 22, 2011

F are T ype Fare type information is obtained from the ATPCO Automate Rules system. The value output to bytes 121–123 is a code identifying a specific category (i.e., business class, first class, excursion, or group) that further defines the fare basis code.



Fare Type (bytes 121–123)

According to the output record, this fare has a fare type of EIP, which is an Economy Instant Purchase fare.

FROP Guide

31 August 22, 2011

Day of Week Application (Outbound/Inbound) Day of week application (outbound/inbound) information is obtained from Category 2 (date/time application). This Category reflects any applicable day of week travel restriction. Rule Category 2 data is processed first. Footnote Category 2 data is processed only in the event that matching rule data is not found. The result is a series of X’s in bytes 124–137, indicating the days on which outbound and inbound travel is allowed. The first seven bytes (bytes, 124–130) represent outbound travel Monday through Sunday. The second seven bytes (bytes, 131–137) represent inbound travel Monday through Sunday. A blank in any field indicates that travel (outbound or inbound) is not allowed on those days.

For bytes 124–137, the intent is to indicate the days of the week on which travel is permitted. If there is no day of week restrictions, then travel is valid on all days of the week, and an X is output beside all days, Monday through Sunday both outbound and inbound. If travel is not valid on certain days, then the bytes that represent the days that are not valid for travel are left blank on the FROP output record. For example, if outbound travel is not valid on Tuesday, then byte 124 would receive an X, byte 125 would receive a space (indicating that travel is not valid), and the remaining bytes (126–137) would receive Xs.



Day of Week Application (bytes 124–137)

According to the output record, travel on this fare is only valid outbound on Saturday and inbound on Saturday or Sunday.

FROP Guide

32 August 22, 2011

Output Field Description Byte

Locations Specifications

Origin 01–03 Three-position City Code from the fare record. Destination 04–06 Three-position City Code from the fare record. Fare Basis 07–14 Maximum of 8-byte code from the fare record. One Way Amount 15–26 Numeric fare amount from the fare record. Right justified with leading zeros; currencies have 3

significant digits to the right of decimal. Round Trip Amount 27–38 Numeric fare amount from the fare record. Right justified with leading zeros; currencies have 3

significant digits to the right of decimal. Advance Purchase 39–41 Displayed as day, month, or year (e.g., 045, 01M, or 01Y, respectively) derived from footnote or

rule Cat 05. Refer to rule (RU) for conditions other than days, months, or year coding. Minimum Stay 42–44 Derived from Cat 06 rule or footnote (3 byte). Day of week (e.g., SU) or 2-byte numeric trailing with

alpha codes: D = days, M = months, or Y = years. RU indicates other conditions. Filler 45 Represented by a space. Maximum Stay 46–49 Derived from Cat 07 rule or footnote (4 byte). Day of week (e.g., SUN) or 3 byte numeric trailing

with alpha codes: D = days, M = months, or Y = years. RU indicates other conditions. Season Start Date 50–55 Represents beginning travel. Expressed in DDMMYY format; derived from rule or footnote Cat 03.

If multiple seasons exist for a single fare record, then multiple output records are created for each seasonal period.

Filler 56 Represented by a space. Season End Date 57–62 Represents last travel. Expressed in DDMMYY format; derived from rule or footnote Cat 03. If

multiple seasons exist for a single fare record, then multiple output records are created for each seasonal period.

Direction of Period of Application

63 Blank if based on originating flight of the priceable unit travel (the Cat 03 assumption) or R indicating that the assumption is overridden and refer to rule for other criteria.

Reservation Booking Code 64 First character of the Fare Basis Code defining the primary booking code. Flight Application 65 Hierarchy: D = direct service, F = specific flight no., V = via point, A = airport, C = specific carrier, M

= multiple conditions (refer to rule). Derived from footnote or rule Cat 04 (if coded). Routing Number 66–69 Numeric (four positions) derived from the Routing Number field of the fare record. Rule Number 70–74 Alphanumeric (four positions) derived from the Rule Number of the fare record. First Travel Date 75–80 In DDMMYY format. Derived from fare record effective date unless modified by a footnote or rule

Cat 14 or 15. First Sale Date 81–86 In DDMMYY format. Unless modified by a footnote or rule Cat 15 an open selling date will be

blank.

FROP Guide

33 August 22, 2011

Field Description Byte Locations

Specifications

Children’s Discount 87–92 Derived from Cat 19 in a percentage format (e.g., 067.00) or populated with RU, meaning refer to rule when more than one percentage applies.

Fare Indicator 93 On the basis of the tariff the fare is selected from. Contains S = Specified, D = Specified North American, or C = Constructed.

Global Indicator 94–95 Two alphanumeric characters derived from the Global Indicator field of the fare record. Carrier 96–98 Three alphanumeric characters derived from the fare record. Currency 99–101 Three alpha characters derived from the fare record. Last Travel Date 102–107 In DDMMYY format or ‘999999’ meaning no discontinue date. Hierarchy derived from fare record,

Cat 14 footnote, or Cat 14 rule (if coded). Last Sale Date 108–113 In DDMMYY format or ‘999999’ meaning no sell to date. Hierarchy derived from fare record

cancellation, Cat 15 footnote (if it exists), or Cat 15 rule (if coded). Tariff Number 114–118 Five-digit numeric of the fare file from which the record was selected. Public/Private 119 Single alpha character: P = Public, R = Private, or A = Advanced Publication (prerelease). Filler 120 Represented by a space. Fare Type 121–123 Three alpha characters derived from Record 1. Day of Week Application Outbound/Inbound

124–137 Outbound (124–130), Inbound (131–137). Derived from rule Cat 02 coding. If no coding exists, then default is to populate all days of week (with an X) as valid travel days.

R ec ord L ayout Des c ription—Header FIELD DESCRIPTION BYTE

LOCATIONS SPECIFICATIONS

Sort ID 01–02 Sort field which places header as the first record of the file. Always low-values. Date 03–10 The date file creation is completed. Expressed mm/dd/yy. Time 11–16 The time file creation is completed. Expressed hhmmss. Record Count 17–25 Numeric record count. Right justified with leading zeros. Filler 26–137 Filler

FROP Guide

34 August 22, 2011

C us tomer S upport

T echnical S upport If you did not receive your scheduled FROP file, have a question about the FROP data you received, are having problems transmitting your selection parameters, or have issues regarding connectivity, contact the ATPCO Help Desk at (703) 661-8229 or send an e-mail message to [email protected]. The Help Desk is available 24 hours a day, 5 days a week (7 AM Monday–7 AM Saturday) to provide support. The Help Desk employee who answers the phone will help you solve your problem or connect you with someone who can. The Help Desk can also be contacted for general product support; in addition, FROP customers can e-mail [email protected].

mailto:[email protected]�

mailto:[email protected]�

FROP Guide

35 August 22, 2011

G los s ary Arbitraries The fares (or rates) that may be combined with an

International fare (or rate) published to a gateway to create a through-fare. Arbitraries may not be sold separately for travel and are usually published between points within the same country. Also referred to as add-ons or proportionals.

Byte The unit of storage in the computer that can represent

a single character of data in standard format. It consists of 8 bits each that can be on (represented by a 1) or off (represented by a 0). Each unique combination of 1s and 0s represents a particular letter, number, or special character.

Category A group of data pertaining to a specific type of rule

provision. City pair The origin and destination of a fare. Constructed fare Also called an unpublished fare. The construction of

an international through fare by combining a published gateway fare with an arbitrary.

Current date When no specified selection date is provided, this

reflects the date on which FROP processing begins (FROP is processed after nightly subscriptions, which are scheduled for 8:00 PM on weekdays and 5:00 PM on weekends). It defines a date on which tickets must be eligible for purchase to be selected.

Customized Applications Online software (econnect.atpco.net) that provides

access to ATPCO native databases with PC-type features and functions.

Directional indicator A tag (usually hidden) that determines the true origin

and destination of a fare or application of supporting text. This tag allows data to be stored most efficiently and displays data in its true order (from point A to point B or vice versa).

Effective date The first date on which a fare may be used for travel. Fare basis code (Also called fare, fare basis, fare class, or fare type.)

An industry code (always beginning with a letter) up to eight alphanumeric characters long that signal parameters in an abbreviated form such as class of service, booking code, minimum or maximum stay, peak or off-peak seasonality, weekend or midweek travel, etc.

FareManager eConnect FareManager eConnect is a browser-based software

http://www.econnect.atpco.net/�

FROP Guide

36 August 22, 2011

consisting of customized and native applications that provides an easy way for customers to access the ATPCO databases using the Internet.

Fare product A fare that has been merged with its governing rule,

footnote, and fare class restrictions. Fare record A record containing data such as a market, footnote,

fare class, and amount. FROP An acronym for Fare Rule Output Product.

Global indicator A two-letter code defining an applicable area such as AF Via Africa AP Via Atlantic and Pacific AT Via Atlantic CT Circle Trip DO Domestic EH Within TC2, within TC3, TC2-TC3 not via

TC1 EU Via Europe FE Russian Federation in TC2, Ukraine–TC3

direct ME Via Middle East PA Via Pacific PE TC1-Central/South Africa via TC3 PN TC1–TC3 via Pacific and via North America PO Via North Pole RW Round the World SA South Atlantic SN Via South Atlantic (routing permitted in one

direction via North/Mid Atlantic) SP Via South Pole TS Via Siberia WH Within Western Hemisphere Governing rule The rule in which the governing provisions for a fare

resides. International Fares System This ATPCO database contains fare and other

international passenger fares information. Native Applications Online software (econnect.atpco.net) that provides

access to ATPCO current applications with a 3270 emulator.

Priceable unit A one-way fare independent of another fare

component, or a combination of fare components that are interdependent to qualify for autopricing.

http://www.econnect.atpco.net/�

FROP Guide

37 August 22, 2011

Private fare International and North American fares and rules that are owned by a FROP customer and not distributed to the public.

Provision See Restriction below. Public information Information (such as a carrier’s instructions to update

rules or fares) that has been officially filed with the pertinent government.

Record layout An illustration of the data fields and their positions. Restriction A condition, coded in a rule or footnote Category,

that governs a resolving fare for a specified period of time.

Rule The rule contains information that defines the

conditions associated with the use of a fare. Sector The portion of travel between two fare break points

as determined in fare construction covered by a single flight coupon. Sectors are made up of one or more segments or legs.

Specified Selection Date A date specified in the From and/or To fields in the

Fare/Rule Selection Parameters table that overrides the current date in determining the criteria for selecting International fares.

User name The seven-letter identification name used for access

to ATPCO systems. Version (of a Fare Product) A picture of a fare product for a specific date range. YY Generic carrier code used for carriers that participate

in IATA agreements. Any participant may use the fares and rules identified by the carrier YY.

Last Updated: 08/22/2011 - ATPCO Guides... · FROP Guide 2 August 22, 2011 Product Description...

Documents

Transcript of Last Updated: 08/22/2011 - ATPCO Guides... · FROP Guide 2 August 22, 2011 Product Description...