Study Guide / Working with Agency Private Fares (PF1) · PDF fileStudy Guide / Working with...

Study Guide / Working with Agency Private Fares (PF1) and Airline Private Fares /

Acknowledgement:

This Study Guide was developed by Galileo International, Customer Education - EMEA. For questions or comments, please send a message to [email protected]

©2004 Galileo International. All Rights Reserved.

Galileo and Focalpoint are registered trademarks or trademarks of Galileo International in the United States and/or other countries.

Galileo Number GN 696

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 iii

Contents

Module 1: Introduction .......................................................................1.1 What are Private Fares ...................................................................................................1.1

Private Fares Maintained by Travel Agencies...........................................................1.1 Airline Private Fares..................................................................................................1.1

Study Guide Objectives...................................................................................................1.2 How to use this Study Guide...........................................................................................1.2 Prerequisites ...................................................................................................................1.3 Online Help .....................................................................................................................1.3

Module 2: Account Names, Account Codes and Contract Codes..2.1 Module Objectives...........................................................................................................2.1 Agency Private Fares Structure ......................................................................................2.1

The Host Agency.......................................................................................................2.2 The Retail Location ...................................................................................................2.2 Identifying Your Accounts .........................................................................................2.2 Account Names.........................................................................................................2.3 Account Codes..........................................................................................................2.3

Adding to the Agency Private Fares Account Table........................................................2.4 Displaying the Agency Private Fares Account Table ......................................................2.5 Modifying an Account Name ...........................................................................................2.6 Deleting an Account ........................................................................................................2.7 Additional Agency Private Fares Account Table Formats...............................................2.8 Assigning a Contract Code .............................................................................................2.8 Organising your Database (Naming Conventions)..........................................................2.9

Account Names and Account Codes ........................................................................2.9 Contract Codes .......................................................................................................2.10 Summary.................................................................................................................2.11

Module Review..............................................................................................................2.12

Contents

iv Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0

Module 3: Building a Discount Rate Agency Private Fares Record3.1 Module Objective ............................................................................................................3.1 Building a Discount Agency Private Fares Record .........................................................3.2

Redisplaying the Screen .........................................................................................3.13 What is Validated for Discount Fares (North America) ...........................................3.13 What is Validated for Discount Fares (International)...............................................3.14 Working with the Fare Basis Code..........................................................................3.15 Working with City Pairs ...........................................................................................3.17

Module Review 1...........................................................................................................3.18 Module Review 2...........................................................................................................3.19

Module 4: Working with Wildcards....................................................4.1 Module Objectives...........................................................................................................4.1 Displaying the Geography Table.....................................................................................4.1

Additional Geography Table Formats .......................................................................4.2 Creating Wildcards..........................................................................................................4.3

Displaying Wildcards in a Contract ...........................................................................4.9 Exception City Pairs ................................................................................................4.11 Additional Wildcard Exceptions Formats.................................................................4.13

Module Review..............................................................................................................4.14

Module 5: Working with Zones ..........................................................5.1 Module Objectives...........................................................................................................5.1 Creating a Zone ..............................................................................................................5.1 Adding Cities or Wildcards to an Existing Zone ..............................................................5.4 Deleting Cities or Wildcards from a Zone........................................................................5.6 Modifying a Zone Code Description ................................................................................5.7 Deleting a Zone...............................................................................................................5.8 Additional Agency Private Fares Zone Formats..............................................................5.8 Adding a Zone Code to an Agency Private Fares Contract ............................................5.9 Module Review..............................................................................................................5.17

Review 1 .................................................................................................................5.17 Review 2 .................................................................................................................5.18

Contents

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 v

Module 6: Managing your Private Fares Records in Apollo............6.1 Module Objectives...........................................................................................................6.1 Copying an Agency Private Fares Record ......................................................................6.1 Modifying an Existing Private Fares Record ...................................................................6.6 Deleting a Private Fares Record .....................................................................................6.9 Module Review..............................................................................................................6.12

Module 7: Using Agency Private Fares...........................................7.1 Module Objectives...........................................................................................................7.1 Requesting Fare Displays ...............................................................................................7.1

Requesting an Integrated Fare Display.....................................................................7.2 Requesting a Non-Integrated Fare Display...............................................................7.4 Requesting a Fare Display with a Contract ...............................................................7.5 Requesting a Fare Display using Search Qualifiers..................................................7.6

Requesting Rules from a Fare Display ...........................................................................7.6 Displaying a Rule Summary......................................................................................7.7 Displaying Rule Paragraphs......................................................................................7.8

Quoting a Fare Using Agency Private Fares.................................................................7.10 Quoting a Fare with an Account Code ....................................................................7.10 Quoting a Fare using a Specific Contract ...............................................................7.12 Overriding an Airline Private Fare Quote ................................................................7.13 Additional Formats ..................................................................................................7.14

Displaying Rules from a Fare Quote .............................................................................7.14 Displaying Fare Rules for an International Itinerary ................................................7.14 Displaying Fare Rules for a North American Itinerary.............................................7.16

Moving an OSI Message...............................................................................................7.17 Document Production....................................................................................................7.18 Working with the Assumed City Function......................................................................7.18

Account Default.......................................................................................................7.18 Displaying an Assumed City File.............................................................................7.19 Cancelling Account Codes from the Assumed City File ..........................................7.20

Module Review..............................................................................................................7.21

Contents

vi Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0

Module 8: Working with Airline Private Fares ..................................8.1 Module Objective ............................................................................................................8.1 Working with Airline Private Fares ..................................................................................8.1

Using Private and Published Fares in Galileo...........................................................8.2 Using Optional Modifiers ...........................................................................................8.3 Using Account Codes................................................................................................8.4 Example Formats – Fare Display..............................................................................8.5 Example Formats – Fare Quote................................................................................8.6 Net Fares ..................................................................................................................8.7

Module Review................................................................................................................8.8

Module 9: Marking Up/Down Airline Private Fares ..........................9.1 Module Objectives...........................................................................................................9.1 Interpreting ATPCO Category 35 ....................................................................................9.1

Working with Category 35......................................................................................9.2 Displaying the Detail of Category 35.........................................................................9.3

Marking Up or Marking Down a Private Fare Filed by an Airline ....................................9.4 Marking Up or Marking Down a Net Fare Filed by an Airline ..........................................9.9 Module Review 1...........................................................................................................9.13 Module Review 2...........................................................................................................9.14

Module 10: Security Setup for Private Fares..................................10.1 Module Objective ..........................................................................................................10.1 Identifying the Security Requirements for Agency Private Fares..................................10.1

Apollo ......................................................................................................................10.1 Galileo .....................................................................................................................10.2

Identifying the Security Requirements for Airline Private Fares....................................10.3 Redistributing an Airline Private Fare......................................................................10.3

Module Review..............................................................................................................10.5

Module 11: Working with Selective Access....................................11.1 Module Objective ..........................................................................................................11.1 Working with Selective Access .....................................................................................11.1

Adding to the Permission File .................................................................................11.1 Building Affiliate Files....................................................................................................11.5 Building Customisers ....................................................................................................11.7 Module Review............................................................................................................11.10

Appendix A: Answer Key .................................................................. A.1

Contents

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 vii

Module 2: Account Names, Account Codes and Contract Codes................................. A.1 Module 3: Building a Discount Rate Agency Private Fares Record .............................. A.2

Review 1 .................................................................................................................. A.2 Review 2 .................................................................................................................. A.4

Module 4: Working with Wildcards ................................................................................ A.6 Module 5: Working with Zones...................................................................................... A.9

Review 1 .................................................................................................................. A.9 Review 2 ................................................................................................................ A.11

Module 6: Managing your Private Fares Records in Apollo ........................................ A.14 Module 7: Using Agency Private Fares....................................................................... A.15 Module 8: Working with Airline Private Fares ............................................................. A.16 Module 9: Marking Up/Down Airline Private Fares ..................................................... A.17

Review 1 ................................................................................................................ A.17 Review 2 ................................................................................................................ A.19

Module 10: Security Setup for Private Fares .............................................................. A.21 Module 11: Working with Selective Access................................................................. A.22 Module 11: Working with Selective Access................................................................. A.22

Appendix B: Building a Flat Rate Agency Private Fares Record.. B.1 Module Objective ........................................................................................................... B.1 Building a Flat Rate Agency Private Fares Record........................................................ B.2

What is Validated for Flat Rate Fares (International) ............................................. B.13 What is Validated for Flat Rate Fares (North America) .......................................... B.14 Redisplaying the Screen ........................................................................................ B.14

Appendix C: Building a Net-Net Rate Agency Private Fares RecordC.1 Module Objective ...........................................................................................................C.1 Building a Net-Net Rate Agency Private Fares Record .................................................C.2

What is Validated for Net-Net Rate Fares (International).......................................C.13 What is Validated for Net-Net Rate Fares (North America)....................................C.14 Redisplaying the Screen ........................................................................................C.14

Contents

viii Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0

Notes

Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0 1.1

Module 1: Introduction

Welcome to Working with Agency Private Fares (PF1) and Airline Private Fares, a self-study programme that allows you to learn at your own pace, and provides you with the knowledge and skills you need to work with specially negotiated private fares.

What are Private Fares

Private fares are fares that have been specially negotiated with an airline for exclusive use by an agency for a particular company, or for a specific destination or event. They are integrated with published fares, and you may access both products through fare display and fare quote to ensure your customers are quoted the best fare.

Galileo International offers two distinct private fares products, Agency Private Fares where the private fare database is maintained by the host agency, and Airline Private Fares where private fare data is filed directly into the Galileo 360° Fares database by ATPCO.

Private Fares Maintained by Travel Agencies

Private Fares allows you to manually build your own private fare database, and as the host agency you take responsibility for loading and distributing data. You make updates on-line and enter and maintain negotiated data using fill-in formats in the Apollo system, ensuring that the latest information is immediately available to your staff and customers. Private Fares resides in the Galileo 360° Fares database, but you have control over who may access the fares data.

This training programme focuses on discount rate fares

Discount rate fares

A discount rate fare is negotiated against a published fare and may be a percentage of the fare, an amount, or a combination of both. Additionally, the discount may be subtracted from or added to the published fare.

Airline Private Fares

Carriers who file fares with the Air Tariff Publishing Company (ATPCO) can provide you with your negotiated fare data directly into the Galileo 360° Fares database. This increases your agency productivity by reducing the time required to maintain your individual fare database.


1.2 Working with Agency Private Fares (PF1) and Airline Private Fares, Version 1.0

Study Guide Objectives

Upon completion of this study guide, you will be able to:

• Assign account names, account codes and contract codes to your negotiated fares

• Build a discount rate private fare record

• Work with wildcards

• Work with zones

• Manage your private fare records in the Apollo system

• Use Agency Private Fares in the Galileo system

• Set up Selective Access agreements

• Use Airline Private Fares in the Galileo system

• Mark up/down Airline Private Fares in the Galileo system

• Redistribute fares to other agencies

How to use this Study Guide

This is a self-paced study guide designed to assist you to work with Agency Private Fares and Airline Private Fares. It is divided into modules covering different topics, and it is recommended that you review the modules in order.

At the beginning of each new topic, follow the steps in the How to use section. There is a review at the end of each module to test your knowledge on the information presented.

Note: Galileo XG4 and Apollo GK4 have been used in this training course.



Prerequisites

It is assumed that you are the key individual in your agency responsible for creating and maintaining the private fares database for your office. You should be familiar with agency operations and your agency’s business process with negotiated fares. In addition, a working knowledge of Selective Access functionality is required.

You should also have a second level sign (secondary authoriser) and must be given permission within your sign-on to create, maintain and view information in your Agency Private Fares database.

Online Help

Help guides you through each task with step-by-step procedures, defines terms, and directs you to more information when necessary.

When to use

Use Help for guidance when you are creating or maintaining your Agency Private Fares database.

How to use

Take the following step to access the Help index for Agency Private Fares:

• Type HELP PRIVATE and press Enter.

Additional help

Once an Agency Private Fares record has been created, there are additional Help screens that include displayed private fare record information in a cryptic format. These Help screens eliminate the need to memorise cryptic formats in order to make changes to the stored data. Examples of these Help screens will be shown in later modules.



Notes


Module 2: Account Names, Account Codes and Contract Codes

Agency Private Fares allows you to integrate the fares that your agency has negotiated, with published fares that are distributed in Galileo 360° Fares database. You have the means of automating the paper-based reference material that may have been standard in your agency for many years.

Module Objectives

Upon completion of this module, you will be able to:

• Describe the structure of Agency Private Fares.

• Add to the Agency Private Fares account table.

• Display the account table.

• Modify an account name in the account table.

• Delete an account from the account table.

• Use additional account table formats.

• Assign a contract code to your negotiated fare.

• Organise your database.

Agency Private Fares Structure

Agency Private Fares are warehoused in a central location which has the responsibility for loading and distributing data. This location is referred to as the host agency.

As the host agency, you are responsible for creating and maintaining the Agency Private Fares database by entering information into a series of fill-in format screens called Agency Private Fares records (PFRs).

Once the Agency Private Fares database has been created, the host location may use Selective Access functionality to distribute contract information to other agency locations.

Agency Private Fares works in conjunction with published fares, ensuring that you quote the best fare to your customers. Agency Private Fares may be viewed using many of the tariff features available in the Galileo system.



The Host Agency

Subscribing to Agency Private Fares establishes your agency as the host agency. You are responsible for:

• Creating and maintaining the Agency Private Fares database.

• Determining which retail locations may view the private fares for fare display, fare quote and ticketing.

As your agency’s Agency Private Fares co-ordinator you are the first level of contact for retail locations when there is a question or a problem with a private fare.

The Retail Location

Retail locations use the Agency Private Fares database for fare display, fare quote and ticketing. This may be the same office as the host agency, or another location with another pseudo city code.

Travel agents at retail locations are not able to view or update Agency Private Fares records, but they use fare information stored in these records to find the best fare for their customers.

Identifying Your Accounts

Before you begin creating your Agency Private Fares database, you should review your negotiated fare contracts and determine what information is to be transferred to Agency Private Fares.

An account name and account code must be created which will represent each account or group of accounts that need to access the private fare information.

The account name and account code must be stored in the Agency Private Fares account table before you can create an Agency Private Fares record. In this module you will learn how to add, delete, and modify account information in the account table.



Account Names

The account name that you create will vary depending on the type of private fare that has been negotiated.

Note: The account name can have a maximum of 16 characters which may be alpha, numeric or a combination of both, and is a description of the account code. The only special character allowed is a hyphen (-).

Account Codes

The account code is an identifier for the name of the account, and usually an abbreviation of the account name. An account code is similar to a folder in a word processing directory in which you store files, your Agency Private Fares records. The same account code may be used as the storage area for many different agreements.

Note: Each individual agreement must be identified by a separate contract code assigned when the PFR is built.

The account code is used when pricing air segments, and as a modifier in fare display and fare quote entries to access private fare information.

The account code can have a maximum of six characters which may be alpha, numeric, or a combination of both. The first character must always be an alpha character.



Adding to the Agency Private Fares Account Table

The Agency Private Fares account table contains the account names and account codes that you have assigned to identify the private fares you have negotiated.

When to use

You must access the Agency Private Fares Account Table to add an account name and account code. They must be added to the table before you commence building a private fare record in Apollo.

The function identifier to access Agency Private Fares is $P/

How to use

Assume a private fare has been negotiated with US Airways. To add the account name US AIRWAYS and account code USAIR to the Agency Private Fares account table, enter:

$P/ACCT/ADD/USAIR/US AIRWAYS

Response:

Private Fares function identifier

Account table identifier

Add to table

Account code

Account name



Displaying the Agency Private Fares Account Table

As your agency’s Agency Private Fares co-ordinator, you may display the account table at any time.

When to use

Display the Agency Private Fares account table when you wish to view the list of account names and account codes of private fares maintained by your agency.

How to use

To display the account table, enter:

$P/ACCT

Response:

Note: The list is read from left to right, and is in alphabetical order by account name.

Private Fares function identifier Account table display



Modifying an Account Name

You may amend the account name in the Agency Private Fares account table by using the modify function.

When to use

Modify an account name when you wish to amend the descriptive name of an account you have entered, or perhaps when you have made a typing error.

How to use

To modify the account name US AIRWAYS that you entered previously to read US AIRWAYS INC, enter:

$P/ACCT/MOD/USAIR/US AIRWAYS INC

Response:

Note: Only the account name may be modified. If you wish to modify an account code, you first delete the existing account, and then add a new account name and account code to the account table.



Modify

Account code

Modified account name



Deleting an Account

It is good practice to delete an account from the Agency Private Fares account table when it is no longer used in your agency.

When to use

Delete an account when the Agency Private Fares contract has expired or has been discontinued, to ensure that the table represents an accurate listing of active accounts.

How to use

To delete the account for US Air that you previously modified, enter:

$P/ACCT/DEL/USAIR

Response:

Continued on next page



Delete

Account code



How to use (Cont.)

Note: All associated Agency Private Fares records (PFRs) must be deleted before you are able to delete an account from the account table. If you attempt to delete an account before doing so, the response is:

Additional Agency Private Fares Account Table Formats

The following table lists additional account table formats:

To display a list of… Enter…

PFRs associated with account code UA

$P/ACCT/DIS/UA

PFRs associated with account code FAR and airline BA

$P/ACCT/DIS/FAR+BA

Help formats $P/

Assigning a Contract Code

In addition to the account name and account code allocated to each of your negotiated fares, each agreement must be identified by a separate contract code. The contract code may be used as a modifier in fare display and fare quote entries to access private fare information.

Note: The contract code is assigned when the PFR is built.



Organising your Database (Naming Conventions)

It is important that negotiated fares are stored in the system in a logical way, so that the travel agent at the retail location is able to access relevant information easily.

Account Names and Account Codes

The account name that you allocate may vary depending on the type of private fare that has been negotiated.

The following table gives some examples of how you may wish to record account names and account codes at your agency, and keep separate different types of contracts.

When fares are negotiated…

Assign the account name:

Assign the account code:

With an airline to be used by all your customers

US AIRWAYS

UNITED AIRLINES

USAIR

UAL

To be used only by employees of a specific company

APEX ROUNDTUIT

SHELL OIL

APEX

SHELL

To be used by all your customers for travel to a particular part of the world

EUROPE

FAR EAST

EUR

FAR



Contract Codes

Each individual negotiated agreement must be identified by a contract code. A contract code may just be a reference number, or perhaps relate to the circumstances of a particular negotiation. The contract code may also be the code that an airline has given you as your reference.

If you have many fares with an airline to different areas of the world, you could assign a contract code relevant to the airline code, or to the particular destination.

The following table gives some examples of how you may wish to assign contract codes to your negotiated fares.

When fares are negotiated…

Assign the contract code:

Explanation:

As the result of a particular negotiation

JULCONF

2001MTG

UAEU

July conference

2001 Meeting

United Airlines to Europe

For a particular holiday destination

CAYMANS

EUW

AU

Cayman Islands summer

Europe winter season

Australia

As part of an airline program

AAMIA

UAPAR9

DALSYD

American Airlines MIA

United Airlines, Paris 9

Dallas to Sydney

Note: Contract codes may be from 1-8 characters in length, all alpha, all numeric, or a combination of both.



Summary

The relationship between account names, account codes and contract codes, may be illustrated by the following chart.

The contract codes are examples of different fares that an agency may have negotiated with United Airlines. All are stored under the "umbrella" of the account name, UNITED AIRLINES, and the account code UAL.

Account Name

UNITED AIRLINES

Account Code

UAL

Contract Code

EU2001

Contract Code

UAPAR9

Contract Code

CAYMANS

Contract Code

JULYCONF



Module Review

Use your study guide and the Apollo system as you work, and write down your answers in the space provided. When finished, check your answers in Appendix A: Answer Key.

1. Your agency has negotiated a private fare with Delta Airlines. Add the account name DELTA AIRLINES, and the account code DELTA to your account table.

2. Modify the account name to show DELTA AIR.

3. Delete the account for DELTA from your account table.


Module 3: Building a Discount Rate Agency Private Fares Record

An Agency Private Fares record (PFR) must be created for each discount fare that has been negotiated. Records are built for each type of private fare, and are specific to the airline with which the fare has been negotiated.

Each PFR contains three areas for storing contract information. They are:

• General information

• Rules summary

• City pair data

Module Objective

On completion of this module, you will be able to:

• Build a discount PFR in Apollo.



Building a Discount Agency Private Fares Record

Assume your agency has negotiated a discount of 20% off the super apex fare with Continental Airlines for round trip travel originating New York to cities in Europe. The following is the detail and agreed conditions of the fare:

Detail/Condition: Application/Restriction:

Account name CONTINENTAL

Account code COAIR

Contract code COEUR (CO to Europe)

Destination cities Amsterdam, Brussels, Rome

Application Round trip

Period of application Immediately – 30 September 2005

Last ticket date 23 September 2005

Booking class H

Published fare basis HKXAPE/HKWAPE/HLXAPE/HLWAPE

Minimum/maximum stay 7 days/2 months

Advance purchase 7 days

Stopovers None

Endorsements/restrictions NONREF APEX

Refund/cancellation penalty before departure

USD 200.00

Restricted travel dates 9 – 12 December 2004

Other restrictions Travel only on Continental. No voluntary rerouting



When to use

Create a discount Agency Private Fares record in Apollo when your agency has negotiated a discount fare with an airline.

How to use

Add the account name and account code to the Agency Private Fares account table. For information, refer to Module 2: Account Names, Account Codes and Contract Codes. Take the following steps to create the discount fare in Apollo:

1. Display the first fill-in format, the general information screen. Enter:

$P/DISC

Response:

123456789

101112



Discount fare identifier



How to use (Cont.) Screen 1 description:

Callout: Screen Response:

Description:

1 $P Redisplay of Agency Private Fares format entry.

DISCOUNT RATE

Agency Private Fares record type.

SCREEN 1 General information screen. Note: Screen 1 – General information. Screen 2 – First screen of rules summary. Screen 3 – Second screen of rules summary.

2 CONTRACT CODE

Mandatory field. Identifies the negotiated agreement.

ACCT CODE Mandatory field. Identifies the account code to which this PFR is associated.

CX Mandatory field. Airline with which the fare has been negotiated.

3 DISC PCT Percentage of discount to be added to or subtracted from the published fare. Mandatory field if not using a discount amount.

P/M Mandatory field when specifying a discount percentage. Indicates whether discount percentage is plus or minus.

DISC AMT Amount to be deducted from or added to the published fare. Mandatory field if not using a discount percentage. Note: May be used in addition to a discount percentage.

P/M Mandatory field when specifying a discount amount. Indicates whether discount amount is plus or minus.

CUR Currency code of the discount amount. Mandatory field when specifying a discount amount.

4 FIRST TVL First date of travel for the discounted fare. Note: Assumed to be the current date when left blank.

LAST TVL Mandatory field. Last date the discounted fare may be applied.

DISC IATA If you wish to discount IATA fares, enter Y. The default is N.

5 FIRST TKT First date that a ticket may be issued for the discounted fare. Note: Assumed to be the current date when left blank.

LAST TKT Last date that a ticket may be issued for the discounted fare. Note: When left blank, assumed to be the date entered in the LAST TVL field.

MULTI CX If multiple-carrier itineraries are to be ticketed using discount-type fares, where there are no overrides to the public rules, enter Y. The default is N. Note: If a private fare of one carrier outbound is to be combined with a private fare of another carrier inbound, both discount contracts must state that multiple carriers are allowed.



Callout: Screen

Response: Description:

6 BK CODE Booking code for the discounted fare if different from the published fare booking code. Note: You may specify a maximum of four booking codes.

FARE TYPE Mandatory field when not using PUBLISHED FBC. Identifies the fare type being discounted when the discount applies to any of the following fare basis codes in the category of: NLA – normal adult NLX – normal/excursion adult EXA – excursion Points to note: May be used in addition to PUBLISHED FBC. Leave blank when a published fare basis code is used.

BASE Enter P if only airline private fares are to be discounted/marked up. Enter B if both public and private fares are to be discounted/marked up. Enter N if only public fares are to be discounted/marked up. Enter C if airline net fares are to be marked up. The default is N.

7 TKT FBC/ DESIGNATOR

Fare basis code and ticket designator to be printed on the ticket.

TOUR NBR Tour number to be printed on the ticket (if applicable).

8 PUBLISHED FBC Mandatory field when not using FARE TYPE. Identifies the fare basis codes that apply to the contract. An asterisk may be placed in any position of the fare basis code, and multiple asterisks may be used. Each asterisk may replace one or multiple characters. For example: If the discount applies to all fare basis codes beginning with the letter Y, enter the fare basis code as Y*. If the discount applies to all fare basis codes starting with a K and containing a P, enter the fare basis code as K*P*.

9 ENDORSEMENT BOX

Allows for special ticketing requirements. Prints on the ticket.

10 OSI Other service information. Information appears in the rules summary, and may be moved manually into the Booking File.

11 NOTES Free text area to store information relevant to the contract.

12 SCREEN 2 When screen 1 is completed, type X and enter to move to screen 2.

SCREEN 3 Prompt for screen 3. Note: You are unable to go directly to this screen. You must move first to screen 2, and type Y after the question OVERRIDE / WAIVERS TO PUBLISHED RULES -Y/N-. Refer to page 3.7.

ADD When adding a contract with no rule data, type X and enter. Note: No overrides are assumed.

MODIFY When modifying an existing PFR, type X and enter.

DELETE When deleting an existing PFR, type X and enter.



How to use (Cont.) 2. Complete the screen as follows and enter at the cursor after the X:

Screen 2, the first screen of the rules summary, is automatically displayed.

Response:

123456

7

8

Note: All data input on this screen is for information only, except override/waivers to published rules.



Screen 2 description:


Description:


DISCOUNT RATE


SCREEN 2 First screen of rules summary. Note: Screen 1 – General information. Screen 2 – First screen of rules summary. Screen 3 – Second screen of rules summary.

2 PENALTIES Applicable cancellation penalties.

3 CHANGE/ REISSUE

Conditions relevant to itinerary changes and ticket reissues.

4 FREQUENT FLYER

Frequent flyer information.

5 FORM OF PAYMENT

Applicable forms of payment.

6 NOTES Freeform text area to store additional information relevant to the discounted fare contract.

7 OVERRIDE/ WAIVERS TO PUBLISHED RULES –Y/N –

This is the only mandatory field in this screen. If overrides to the published fare exist, type Y, tab to SCREEN 3, type X and enter. If overrides do not exist, type N, tab to ADD, type X and enter. Note: Refer to What is Validated for Discount Fares later in this module.

8 SCREEN 1 To return to screen 1, type X and enter.

SCREEN 3 Second fill-in format screen for rules summary. Type X and enter.

ADD Type X and enter to move forward to the city pair fill-in format screen.

MODIFY When modifying an existing PFR, type X and enter.

DELETE When deleting an existing PFR, type X and enter.




How to use (Cont.) 3. Complete the screen as follows and enter at the cursor after X.

Screen 3, the second screen of the rules summary, is automatically displayed.

Response:

12

3

456789

10

Note: There are no mandatory fields in this screen



Screen 3 description:


Description:


DISCOUNT RATE


SCREEN 3 Second screen of rules summary. Note: Screen 1 – General information. Screen 2 – First screen of rules summary. Screen 3 – Second screen of rules summary.

2 PROHIBIT TVL This field is used to indicate when travel is prohibited. Prohibited travel dates are validated within the period of the contract. The field has two lines – the first is for specific dates, and the second is for a range of dates. Note: The date format is day, month, year (DDMMMYY).

3 SEASONAL TVL

This field allows Galileo 360° Fares to validate the seasonal application for date ranges which make up a season. Seasonality dates are validated within the contract period.

4 FLIGHT APPL Flight applicability may be entered for specific flight numbers, or for a range of flight numbers.

5 ROUTINGS - VIA - NOT VIA - CXN

This field is used to specify routing restrictions, and requires city or airport codes.

DIRECT NONSTOP

If routing must be direct or non-stop, enter a Y. If routing is waived, enter a W. If left blank, the assumption is that there are no restrictions.

6 ADV RES Advance reservation requirement specified as a number of days.

ADV TKT Advance ticketing requirement specified as a number of days.

DAY RSTR S M T W T F S

Day of the week restrictions apply to the day(s) of the week that the fare is applicable. Enter a Y if travel is restricted to this day. Enter a W if the day of the week restrictions are waived. The day of the week restriction is validated. If left blank, the assumption is that there are no restrictions. Note: Restrictions are applicable for both outbound and inbound travel. When a fare is valid on a specific day of the week outbound, and on a different day of the week inbound, two directional contracts must be built.

7 MIN MAX

Minimum and maximum stay requirements may be shown as a numeric, or day of the week. Enter a W if requirements are waived. If using a day of the week, abbreviations are as follows: SU, MO, TU, WE, TH, FR, SA.

STOPS Specify permitted stopovers.




How to use (Cont.)


Description:

8 TIME OF DAY RSTR

Specify any time of day restriction.

9 NOTES Freeform text area to store additional information relevant to the discounted fare contract.

10 SCREEN 1 Type X to return to screen 1.

SCREEN 2 Type X to return to screen 2.

ADD Type X and enter to move forward to the city pair fill-in format screen.

MODIFY When modifying an existing Agency Private Fares record, type X and enter.

DELETE When deleting an existing Agency Private Fares record, type X and enter.

4. Complete the screen as follows and enter at the cursor after the X:

The city pair screen is automatically displayed.



Response:

1

23

4

City pair screen description:

Callout: Screen Response: Description:


2 CONTRACT CODE

ACCT CODE

CX

The appropriate contract code, account code and airline are repeated here.

3 ORG Origin city. If a city or airport code is not entered, the system reads from left to right and repeats the code from the previous ORG field.

DES Destination city. If a city or airport code is not entered, the system reads from left to right and repeats the code from the previous DES field.

DI Directional indicator N (no) or Y (yes). The entry from the previous DI field is repeated when left blank. Note: If no previous information is available, it is assumed that the fare is not directional, and N is entered automatically.

4 MORE To access additional space, tab to MORE, type X and enter. Note: There is no limit to the number of city pairs for each contract. A maximum of 28 city pairs may be entered on each screen.

END Type X and enter to store the Agency Private Fares record.

ZONE Type X and enter to display the screen to enter a zone code (if applicable).



5. Complete the screen as follows:

Enter at the cursor

Response confirming that the Agency Private Fares record and cities have been added:

Points to note:

• Once you store the PFR, city pairs are placed in alphabetical order by origin point on subsequent retrievals.

• Cities and/or wildcards may be grouped together to speed the building of your Agency Private Fares database. Refer to Module 4: Working with Wildcards, and Module 5: Working with Zones.

• When a negotiated fare has been added to the database, it must be thoroughly tested to ensure that all rules and conditions validate correctly.



Redisplaying the Screen You may redisplay the screen for the current Agency Private Fares contract on which you are working by entering one of the formats below:

When you wish to redisplay...

Enter...

The current screen $P*

Screen 1 $P*1

Screen 2 $P*2

Screen 3 $P*3

City screen $P*C

What is Validated for Discount Fares (North America)

Rules and conditions The conditions for rule validation are shown in the table below:

If… Then…

Override/waivers to Published Rules = N

The published rules are used to validate the fare routing and fare quote.

Override/waivers to Published Rules = Y

Only the following rules and conditions are validated: Screen 1

• Carrier

• Booking code

• First travel date/last travel date

• First ticketing date/last ticketing date

Screen 2

• No fields are validated

Screen 3

• Prohibited travel dates

• Day of the week restrictions

• Seasonality

Note: The fare routing is not validated.

Fare construction principles No fare construction principles are applied to the fare quote.



What is Validated for Discount Fares (International)

Rules and conditions The conditions for rule validation are shown in the table below:

If… Then…

Override/waivers to Published Rules = N

The published rules are used to validate the fare routing and fare quote.

Override/waivers to Published Rules = Y

Only the following rules and conditions are validated: Screen 1

• Carrier

• Booking code

• First travel date/last travel date

• First ticketing date/last ticketing date

Screen 2

• No fields are validated

Screen 3

• All fields are validated, except: - Time of day restrictions - Stopovers

Note: The fare routing is not validated.

Fare construction principles No fare construction principles are applied to the fare quote.



Working with the Fare Basis Code

An asterisk may be placed in any position of the published fare basis code, and multiple asterisks may be used. Each asterisk may replace one or multiple characters.

For example:

• If the discount applies to all fare basis codes beginning with the letter Y, enter the fare basis code as Y*.

• If the discount applies to all fare basis codes starting with a K and containing a P, enter the fare basis code as K*P*.

Example 1

All fare basis codes beginning with H and K may be discounted by completing screen 1 as follows:

Wildcardasterisk

Wildcardasterisk



Example 2

Fare basis codes BHWAP, BLWAP, BKWAP and BKWAP may be discounted by completing screen 1 as follows:



Working with City Pairs

If you specify city codes in the City screen, then the discount is applied for travel to and from the city regardless of which airport is used.

Example 1

If NYC is specified, the discount applies for travel from JFK, EWR or LGA.

Example 2

If EWR is specified, the discount applies for travel only from EWR.



Module Review 1

Use your study guide and the Apollo system as you work. When finished, check your answers in Appendix A: Answer Key.

Assume your agency has negotiated a discount of 25% off the BEE1M fare with Cathay Pacific Airways for round trip travel originating Singapore to Hong Kong and to cities in Japan and South Korea. The following is the detail and agreed conditions of the fare:


Destination cities Hong Kong, Tokyo, Osaka, Seoul


Period of application Immediately – 30 June of next year

Last ticket date 23 June of next year

Booking class B

Fare basis BEE1M

Minimum/maximum stay 7/30

Advance purchase None

Stopovers One stopover permitted

Endorsements/restrictions Travel only on CX


No restrictions

Restricted travel dates 10 - 20 February 2005

Other restrictions Travel only on Cathay Pacific Airways. No voluntary rerouting

1. Decide upon a suitable account name and account code and add them to the Agency Private Fares account table.

2. Decide upon a contract code, and build the discount fare in Apollo.

Note: When a negotiated fare has been added to the database, it must be thoroughly tested to ensure that all rules and conditions validate correctly.



Module Review 2


Assume your agency has negotiated a discount of 25% off all round trip special fares with Virgin Atlantic for travel originating London (any airport) to New York EWR airport only.

All rules and conditions of the fares apply, and there are no exceptions/overrides.

The discount applies to all fare basis codes beginning with Q..


2. Decide upon a contract code, and build the discount fare in Apollo.

Note: Specify a last travel date of 31 December 2005.



Notes


Module 4: Working with Wildcards

You may use wildcards as a substitute for common groupings of city and airport codes when entering city pair information into an Agency Private Fares contract. This is a great time-saver, and wildcards may be input in the city pair screen for discount fares, flat fares and net-net fares.

A geography table is available in the Agency Private Fares database to help you create wildcards.

Module Objectives

On completion of this module you will be able to:

• Display the geography table

• Create wildcards

Displaying the Geography Table

To help you create wildcards, the Agency Private Fares geography table allows you to verify ISO country codes and state and province codes for the USA and Canada.

Note: Some US state and Canadian province codes have been modified for use with Agency Private Fares, and not all are the same as conventional abbreviations.

When to use

Refer to the Agency Private Fares geography table to verify a country code or a state or province code of the USA or Canada when you wish to create a wildcard. You may display the table:

• In its entirety

• By US state and Canadian province codes

• By country code



How to use

Take the following step to display the Agency Private Fares geography table in its entirety. Enter:

$P/GEOG/DIS

Response:

Additional Geography Table Formats

The following table lists additional geography table formats:


State and province codes $P/GEOG/DIS/ST

State and province codes beginning with a specific letter

$P/GEOG/DIS/ST/C

ISO country codes $P/GEOG/DIS/CO

ISO country codes beginning with a specific letter

$P/GEOG/DIS/CO/D

Help entries $P/


Geography table

Display



Creating Wildcards

Wildcards save time when inputting information in a city pair screen, and may be used to group together city and airport codes. Wildcards may apply between countries, or between countries and cities.

The following may be used to build a wildcard:

• Any ISO country code

• State and province codes of: − Canada − USA

Note: The state or province code must precede the country code in the format, separated by a hyphen. For example, Alabama in the USA is identified as AL-US.

• IATA traffic conference areas − AR1 − AR2 − AR3

Note: A world-wide card may be designated as 999.

When to use

Create a wildcard to group together city and airport codes to save unnecessary repetition when inputting data.

Assume your agency has negotiated a discount of 10% off the BLE6M, BKE6M and BHE6M fares for travel with British Airways from London and Manchester to India and Bangladesh for employees of the Indian Development Agency.

In addition the discount applies also from Glasgow to Delhi, Mumbai and Dhaka.




When to use (Cont.)

All rules and conditions of the fare apply, and there are no exceptions/overrides. The following is the detail of the fare:


Account name INDDEVELOPMENT

Account code INDIA

Contract code INBD


Period of application Immediately – 31 December 2005

Booking class B

Fare basis BLE6M/BKE6M/BHE6M

Discount 10%

Endorsements/restrictions NONREF

Other restrictions Travel only on British Airways. No voluntary rerouting



How to use

Take the following steps to create a discount rate Agency Private Fares record using wildcards to represent the cities of India and Bangladesh in the city pair screen that follows.

Note: Be sure the account name and account code have already been added to the Agency Private Fares account table.

1. Enter:

$P/DISC

Complete screens 1 and 2 as follows, and enter at the cursor.

Screen 1 :





Screen 2:

N = no overrides

Enter at the cursor

Response:

2. Display the geography table to verify the country codes for India and Bangladesh. Enter:

$P/GEOG/DIS/CO


Geography table Display

Country code identifier



Response:

Instead of entering each city code for India and Bangladesh in the city pair screen, country codes may be used to represent those cities.

The following wildcards may be used when entering city pair information:

Country: Wildcard:

India IN

Bangladesh BD



3. Complete the screen as follows, and enter at the cursor.

Screen response that the Agency Private Fares record and cities have been added:



Displaying Wildcards in a Contract

Once they have been entered, it is possible to view the wildcards that have been included in an Agency Private Fares record.

When to use

Display the wildcards when you wish to view those that have been included in a contract.

How to use

Take the following step to view the wildcards you entered for the flat fare created for account code INDIA. Enter:

$P/WILD/DIS/INDIA/INBD/BA

Response:

Private Fares function

Wildcard identifier Display

Account code Contract code

Carrier code



Help

The prompt on line 4 indicates that city pairs also exist, and Help has automatically displayed the required input in cryptic format with a tab stop to enable you to move quickly to that screen. If required, enter:

$P/CITY/DIS/INDIA/INBD/BA

Response:

Note: Help automatically displays the cryptic entry on line 3 to return to the wildcards screen, if required.

Private Fares function

Wildcard identifier Display


Carrier code



Exception City Pairs

If wildcards are used in a contract, you may specify any cities which are to be excluded from the grouping. They are known as exception cities.

When to use

Add an exception city when a city is an exception to the wildcard grouping.

In the PFR that you built on the previous pages, assume that fares were agreed from London and Manchester to all cities in India served by British Airways, except to Calcutta. This city must be specified as an exception to the contracted fare.

How to use

Take the following steps to specify Calcutta as an exception city.

1. Display the Exception Cities – Add screen from London to India. Enter:

$P/XCTY/ADD/INDIA/INBD/BA/LON/IN

Response:

Private fares function identifier

Exception city Add


Carrier code City code

Wildcard



2. Complete the screen as follows and enter at the cursor:

Response:

Confirmation thatthe exception cityhas been added

3. Display the Exception Cities – Add screen from Manchester to India. Enter:

$P/XCTY/ADD/INDIA/INBD/BA/MAN/IN



Exception city Add

Account code

Contract code Carrier code

City code Wildcard



How to use (Cont.) 4. Complete the screen as follows and enter at the cursor:

Response:

Additional Wildcard Exceptions Formats

The following table lists additional wildcard exceptions formats:

To… Enter…

Display a list of wildcard exceptions

$P/XCTY/DIS/INDIA/ INBD/BA/MAN/IN

Delete a wildcard exception $P/XCTY/DEL/INDIA/ INBD/BA/MAN/IN

To receive help with your entry $P/



Module Review


Assume your agency has negotiated a discount of 30% off the one way M12 fare with United Airlines valid for travel originating the United Kingdom to California and Texas.

The following city pairs are excluded from the agreement:

• Glasgow to Houston

• Manchester to San Francisco

All rules and conditions of the fare apply, and there are no exceptions/overrides. The following is the detail of the fare:


Application One way

Period of application Immediately – 31 December 2005

Booking class M

Fare basis M12

Discount 30%

Endorsements/restrictions NONREF

Other restrictions Travel only on United Airlines. No voluntary rerouting

Exception cities Glasgow to Houston

Manchester to San Francisco


2. Decide upon a contract code, and build the discount fare in Apollo. Use wild cards to represent cities in the UK, California and Texas


Module 5: Working with Zones

Cities and wildcards may be grouped together to create a zone in order to speed the building of your Agency Private Fares database. Once created, a zone code is allocated to the grouping, and may be used with any account code or contract code in your private fares database.

Creation of a zone enables you to group your cities and wildcards precisely within your Agency Private Fares database.

Note: By creating a zone, you are able to quickly transfer data to your Agency Private Fares database, but contract information will not automatically change if there are any subsequent additions or deletions to the zone.

Module Objectives


• Create a zone

• Add cities or wildcards to an existing zone

• Delete cities or wildcards from an existing zone

• Modify a zone code description

• Delete a zone

• Use additional zone formats

• Add a zone to an Agency Private Fares contract

Creating a Zone

Each zone may contain a maximum of 50 cities and/or wildcards and must be defined in the system for subsequent use.

When to use

Create a zone when you wish to reduce the number of inputs when building and maintaining your Agency Private Fares database. Each zone must be identified by a unique zone code.



How to use

Take the following steps to create a zone to represent the cities below:

• Baltimore BWI

• Boston BOS

• Cincinnati CVG

• Cleveland CLE

• Detroit DTW

• New York JFK

• Philadelphia PHL

• Pittsburgh PIT

• Washington DCA

1. Display the zone table. Enter:

$P/ZONE

Response:

1

34

2

PrivateFares function identifier

Zone table identifier



Screen description:

Callout: Description:

1 Redisplay of Agency Private Fares format entry.

2 Zone code may be a maximum of 8 alpha/numeric characters, including the asterisk.

3 Description may be a maximum of 40 alpha/numeric characters.

4 A maximum of 50 cities and/or wildcards may be entered.

2. Complete the screen as follows, and enter at the cursor:

Enter at thecursor

Screen response confirming that the zone code and cities have been added:

Note: When cities are added to a zone, they are placed in alphabetical order.



Adding Cities or Wildcards to an Existing Zone

You may add further cities or wildcards at any time to the zone you have created.

When to use

Add further cities or wildcards when you need to expand your Agency Private Fares database.

How to use

Take the following steps to add Rochester ROC and wildcard Maine to zone *USA1 created above.

1. Display the Zone Table. Enter:

$P/ZONE/ADD/*USA1

Response:


Zone table identifier Add

Zone code




Enter atthe cursor

Screen response confirming that the city and wildcard have been added:



Deleting Cities or Wildcards from a Zone

You may delete cities or wildcards at any time from the zone you have created.

When to use

Delete cities or wildcards from a zone when you need to amend your database.

How to use

Take the following step to delete Cleveland from zone *USA1 created above. Enter:

$P/ZONE/DEL/*USA1/CLE

Screen response confirming that the city has been deleted:



Delete

Zone code

City code



Modifying a Zone Code Description

You may modify a zone code description if required.

When to use

Modify a zone code description if you wish to amend it, or if you have made a typing error.

How to use

Take the following step to modify the description for zone *USA1. Enter:

$P/ZONE/MOD/*USA1/NORTH EASTERN USA

Screen response confirming the change:

12

Screen description:

Callout: Description:

1 Old zone code description.

2 New zone code description.



Modify

Zone code

Modified zone code description



Deleting a Zone

A zone should be deleted when it is no longer required.

When to use

Delete a zone when the grouping of cities and wildcards is no longer required.

How to use

Take the following step to delete zone *USA1 from your Agency Private Fares database. The zone code, zone description and cities and wildcards that it contains are all deleted. Enter:

$P/ZONE/DEL/*USA1

Screen response confirming the deletion.

Additional Agency Private Fares Zone Formats

The following table lists additional zone formats:


Zone codes $P/ZONE/DIS

Cities and wildcards contained in a zone code

$P/ZONE/DIS/*USA1

Help formats $P/



Delete

Zone code



Adding a Zone Code to an Agency Private Fares Contract

Once a zone has been created it may be added to any Agency Private Fares contract. The input may be between zones, or between zones and cities and wildcards.

When to use

Add a zone code to an Agency Private Fares contract to speed the building of your database.

Assume your agency has negotiated a discount of 25% off the KNRO fare with American Airlines for travel originating Mexico City to cities in north-east USA. The following is the detail and agreed conditions of the fare:


Account name AMERICAN MEXUSA

Account code AAMEX

Contract code MEX1

Destination cities BOS, JFK, PHL, BWI, RIC

Application One way

Period of application Immediately – 31 May of next year

Last travel date 31 May of next year

Booking class K

Published fare basis KNRO

Stopovers None

Other restrictions Travel only on American Airlines. No voluntary rerouting

Note: All other fare conditions are the same as the filed fare.

How to use

Take the following steps to create a zone for the cities in the north-east USA specified above, and add it to the PFR in Apollo. The zone code is *UANEAST.

1. Display the zone table. Enter:

$P/ZONE






How to use (Cont.) 2. Complete the screen as follows, and enter at the cursor:

Enter atthe cursor

The screen response confirms that the zone code and cities have been added:

3. After you have added the account name and account code to the Agency Private Fares account table, display the discount fare fill-in format. Enter:

$P/DISC





Complete Screen 1 as follows, and enter at the cursor:





Response:



4. Tab to Zone, type an X and enter at the cursor.

Enter at the cursor

Screen response:




Note: At this point, the zone code is validated for existence. If a code does not exist, the system will error.

Screen response confirming that the entry will generate five city pairs:



6. Enter again as prompted to confirm the addition.

Screen response:

Note: This screen may be edited. You may blank out any city pairs not required, and add further city pairs if necessary.

7. Tab to End, type an X and enter at the cursor.



Screen response:

Important note: By creating a zone, you are able to quickly transfer data to your Agency Private Fares database, but contract information will not automatically change if there are any subsequent additions or deletions to the zone.



Module Review


Review 1

1. Decide upon a suitable zone code and description, and create a zone for the following US cities:

• Miami MIA

• Atlanta ATL

• New Orleans MSY

• Dallas DFW

• Houston IAH

2. Add the following two cities to the zone:

• Mobile MOB

• Tampa TPA

3. Delete Dallas from the zone.

4. Modify the zone code description.

5. Delete the zone from your Agency Private Fares database.



Review 2

Assume your agency has negotiated a discount of 25% off the normal Y class fare with Delta Airlines for travel between Miami and Belgium, France, Germany, Hungary, Italy, Portugal and Spain.

The following is the detail and agreed conditions of the fare. All conditions of the fare apply, and there are no overrides.


Application One way/ round trip

Period of application Effective immediately – 30 September 2005

Booking class Y

Published fare basis Y

Other restrictions Travel only on Delta. No voluntary rerouting

1. Decide upon a suitable zone code and description, and create a zone for countries in Europe:

• Belgium

• France

• Germany

• Hungary

• Italy

• Portugal

• Spain


3. Decide upon a contract code, and build the fare in Apollo, using the zone that you have created.


Module 6: Managing your Private Fares Records in Apollo

You must maintain your Private Fares database to ensure the information it contains is accurate, and that your customers are quoted the best fare.

Module Objectives


• Copy an existing PFR to create a new Private Fares record.

• Modify an existing Private Fares record.

• Delete a Private Fares record.

Copying an Agency Private Fares Record

If you have to create a new Private Fares record, a good time-saver is to copy contract information from an existing similar PFR. Your inputs do not affect the existing PFR, and you simply use it as the basis for creating a new record.



When to use

Copy an existing PFR when you have to create a new similar record.

Assume your agency has negotiated a discount of 25% off the KLXNR5/KLWNR5 fares with Delta Airlines for round trip travel originating New York JFK to cities in Europe. It is very similar to the one created for Continental Airlines in Module 3: Building a Discount Agency Private Fares Record in Apollo.

The following is the detail and agreed conditions of the fare.


Account name DELTA EUROPE

Account code DLEUR

Contract code DLEUR1 (Delta Airlines to Europe)

Destination cities Brussels, Amsterdam, Rome, Frankfurt


Period of application Immediately – 30 September 2005

Last ticket date 23 September 2005

Booking class K

Published fare basis KLXNR5/KLWNR5

Minimum/maximum stay 7 days/2 months

Advance purchase 7 days

Stopovers None

Endorsements/restrictions NONREF APEX


USD 200.00

Restricted travel dates 9 - 12 December 2004

Other restrictions Travel only on Delta. No voluntary rerouting

Note: Conditions which are different to the fare created in Module 3 are shown in bold.



How to use

After you have added the account name and account code to the Private Fares account table, take the following steps to copy the existing discount fare previously created in Apollo for Continental Airlines.

1. Display the PFR you created earlier for Continental Airlines, with account code COAIR and contract code COEUR. Enter:

$P/DIS/COAIR/COEUR/CO

Response:

2. Over-type the following fields with new data:

Field: New Data:

CONTRACT CODE DLEUR1

ACCT CODE DLEUR

CX DL

DISC PCT 25

BK CODE K

TKT FBC/DESIGNATOR KLXNR5/KLWNR5

ENDORSEMENT BOX VALID ONLY DL NO REROUTING



Display Account code




How to use (Cont.) Completed screen:

3. There is no information to amend on screen 2 or screen 3. Tab to

ADD, type X and enter at the cursor. A blank city pair screen is automatically displayed.

Response:



4. Complete the screen as follows, and enter at the cursor after the X:

Response that the Private Fares record and cities have been added:



Modifying an Existing Private Fares Record

You may need to revise or modify contract information after an Agency Private Fares record has been created. You may modify any field except those listed below.

• Contract code

• Account code

• Carrier code

• Currency code

When to use

Modify an existing Private Fares record when contract details have been amended, or to correct a typing error.

How to use

Take the following steps to amend the PFR created in Module 3: Building a Discount Agency Private Fares Record in Apollo. The advance reservation and advance purchase date must be amended. In addition, the refund/cancellation penalty before departure was specified incorrectly. The following fields must be corrected:

Field: New Data:

Advance reservation/advance purchase

14 days

PENALTIES USD 150.00




How to use (Cont.) 1. Display the PFR for Continental Airlines with the account code

COAIR, and contract code COEUR. Enter:

$P/DIS/COAIR/COEUR/CO

Response:

2. Display screen 2 and make the required modification to PENALTIES.

Completed screen:


Carrier code

Display




3. Display screen 3 and make the required modification to ADV RES and ADV TKT. Tab to MODIFY, type X and enter at the cursor.

Completed screen:

Amended data Amended data Enter at the cursor

Screen response:

Note: The time taken to update the record is dependent upon the size of the city pair data, but most times update is immediate. The system does not display a message when it has been completed.



Deleting a Private Fares Record

When a contract has expired, or if an agreement is terminated, the Private Fares record must be deleted from the database.

When to use

Delete a Private Fares record when a contract is no longer applicable.

How to use

Take the following steps to delete the PFR that you created at the beginning of this module for account code DLEUR and contract code DLEUR1 that was negotiated with Delta Airlines:

1. Display the PFR you created earlier. Enter:

$P/DIS/DLEUR/DLEUR1/DL

Response:


Display Account code




2. Tab to DELETE, type an X and enter at the cursor.

Completed screen:

Enter at thecursor

Screen response:

3. Enter after the response CONFIRM DELETE to confirm deletion.



Screen response:

4. If there are no other contracts associated with this account code, and it will not be used again, delete the account from the Private Fares account table. Enter:

$P/ACCT/DEL/DLEUR

Response:


Account table identifier Delete

Account code



Module Review

Use your study guide and the Apollo system as you work, and write down your answers in the space provided. When finished, check your answers in Appendix A: Answer Key.

1. Write down the four steps you would take to create a new Agency Private Fares record from an existing PFR.

_____________________________________________________________________________

_____________________________________________________________________________

_____________________________________________________________________________

_____________________________________________________________________________

2. Write down the three steps you would take to delete an Agency Private Fares record from the database.

_____________________________________________________________________________

_____________________________________________________________________________

_____________________________________________________________________________


Module 7: Using Agency Private Fares

After you have added an Agency Private Fares record to the database, it is immediately available for fare display, fare quote, and ticketing.

In this module you will learn how to use Agency Private Fares to request a fare display, fare rules, and fare quote.

Module Objectives


• Request a fare display

• Display rules from a fare display

• Request a fare using Agency Private Fares

• Display rules from a fare quote

• Move an OSI message from a contract

• Work with the assumed city function

Requesting Fare Displays

There are two types of fare displays for Agency Private Fares:

Integrated - Displaying both private and published fares so that you quote a

customer the best applicable fare.

Non-Integrated - Displaying only private fares.

You can customise fare displays with account code, contract code and fare display modifiers, and tailor your request to meet the needs of your customer. All existing modifiers can be used in random order, except:

• Validated fare display for North America (e.g. V15SEPV22SEP)



Requesting an Integrated Fare Display

Agency Private Fares integrates private and published fares in one fare display. The low-to-high display makes it easy for you to choose between a published and private fare.

When to use

Request an integrated fare display when you wish to view both private and published fares.

How to use

To display an integrated fare display, append any fare display entry with a dash (–), the Agency Private Fares identifier PRI, a dash (–), and the account code. You can specify up to three account codes.

Note: When you use fare display modifiers, they must precede –PRI, which indicates the beginning of Agency Private Fares modifiers.

Response displaying a list of published and private fares:

FDNYC10SEPAMS/CO– PRI – COAIR

Fare Display Private Fares identifier Account code



Screen description: Callout: Description:

1 Fare display entry with Private Fares identifier and account.

2 PRIVATE FARES FOR XG4 displays in header lines to show private fares exist for host pseudo XG4.

3 Dash (–) prior to airline code on lines 7 and 8 identifies a private fare.

4 Account code

5 Discounted fare shows the actual fare basis code on which the discount is calculated (HLXAPE).

• Net-net and flat fares do not display any information in the areas for mileage/routing (M/R), global indicator (GI) or day/time restriction (DT).

• Net-net and flat fares display the fare basis code of FLAT.

6 Contract name

7 Booking class

8 Pseudo city that owns the contract



Requesting a Non-Integrated Fare Display

A non-integrated fare display shows only private fares for a selected city pair. If a lower published fare exists it will not display.

Example

Your client works for the Indian Development Agency who have negotiated fares with British Airways for travel from the UK to India and Bangladesh. These fares allow changes without penalty.

When to use

Request a non-integrated fare display when you only want to view private fares.

How to use

To request a non-integrated fare display, append the display entry with dash (–) the Agency Private Fares identifier PRI, dash (–), and the account code followed by the Private Fares modifier :P

Response displaying only private fares:

FD01SEPLONDEL/BA – PRI – INDIA :P

Fare Display Private Fares identifier

Account code Private Fares modifier



Requesting a Fare Display with a Contract

You can specify a particular contract to tailor your fare request to show only applicable fares.

Example

You have a customer traveling from Mexico City to Boston with American Airlines, and a special fare has been negotiated for travel. While other negotiated fares may exist, your customer only qualifies for the MEX1 contracted fare.

When to use

Use a contract to quickly display only fares that apply to a particular contract.

How to use

To request an Agency Private Fare with a contract, append the fare display entry with a dash (–) the Private Fares identifier PRI, dash (–), and the account code, @@ and the contract code, followed by the Private Fares modifier :P.

Response displays only fares that apply to the account AAMEX and contract MEX1:

FD1NOVMEXBOS/AA – PRI – AAMEX @@MEX1 :P

Fare Display Private Fares identifier

Account code Contract

Private Fares modifier



Requesting a Fare Display using Search Qualifiers

Fare display qualifiers tailor a fare request to meet the needs of your customer. All existing qualifiers can be used except:

• Validated tariff display (e.g. V15SEPV22SEP)

When you use search qualifiers, they must precede the Agency Private Fares identifier –PRI, which indicates the beginning of Private Fares modifiers.

The following table lists sample formats for fare display search qualifiers. To search by… Use this format…

Carrier FD21JUNLONSJU/US–PRI–CARIB

Global indicator FD02JANCLEBOM:PA–PRI–ASIA

Fare type FD29AUGWASLON@C–PRI–VIRGIN

Combined qualifiers

FD10MARSFOMIA/AA@K7NR–PRI–GTE–WEST

Requesting Rules from a Fare Display

Fare rules provide you with specific restrictions and policies regarding a fare in a fare display. You can view rules for an Agency Private Fare from a fare display just as you would for a published fare. For flat or net-net fares, only rules that apply to a contract will display. If the private fare is a discount from a published fare, the contract rules appear first followed by the published fare rules.

Display fare rules when you want additional contract information or specific rule information regarding a fare.

There are two ways to display rule information from fare display:

Rule summary

Rule paragraph



Displaying a Rule Summary

The rule summary includes key rule paragraphs and a brief synopsis of the rule provisions for a fare.

When to use

Use a rule summary when you want an overview of fare restrictions and policies.

How to use

To view the rules for a private fare from a fare display, type the function identifier FN* and the line number of the fare, slash (/), and the letter S for summary.

Response displays a rule summary with contract rules appearing first.


FN*9/S

Function identifier Line number

Summary



How to use (Cont.) Move down (MD) to display specific rule information for the fare.

Displaying Rule Paragraphs

Rule paragraphs provide detailed information about rule provisions associated with a fare. Paragraph numbers reference a certain rule.

When to use

Use a rule paragraph when you need details about the rule provisions, such as day and time restrictions, refund policy, or penalties for changes.

How to use

To display rule information by paragraph, type the function identifier FN* followed by the line number of the fare, slash (/) and the paragraph number.

FN* 9 / P8

Function identifier Line number of the fare

Paragraph number



Response displaying contract rules first:

Move down (MD) to display paragraph 8 rule information:



Quoting a Fare Using Agency Private Fares

When you want Galileo 360° Fares to consider an Agency Private Fare when searching for the best fare for an itinerary, you must include the account code with your format entry. The resulting fare quote will be a published or private fare, or combination of both, whichever is lower.

When you select a private fare that has been negotiated as a discount from a published fare, the Galileo system validates the fare against the published rule.

All overrides or waivers are validated for international fares, except for time of day restrictions and stopovers. For fares within North America, no overrides or waivers are validated, except for prohibited travel dates, days of the week, and seasonality. Refer to Module 3: Building a Discount Agency Private Fares record for full details.

You can request a fare quote for the whole itinerary or for specific segments using an account code, and contract code if appropriate.

Note: The Galileo system does not validate international fare construction principles when a private fare is selected to price an international itinerary.

Quoting a Fare with an Account Code

If you want Galileo 360° Fares to search for the best fare for an itinerary and you use Agency Private Fares, you must include the account code with your entry.

When to use

When you want Galileo 360° Fares to search for the best public or private fare use the account code in your fare quote entry.

How to use

To request a fare quote and include private fares for a specific account code, use the function identifier FQ, and a dash (–) followed by the account code. For example:

FQ – UADE

Fare quote function identifier Account code



Screen response:

Note: Galileo 360° Fares quotes the best fare for the itinerary, and selects the private fare because it is less expensive.



Quoting a Fare using a Specific Contract

To ensure an accurate fare you may want to fare quote an itinerary using a specific contract.

Example

Your customer is traveling from Washington to London on United Airlines flight number 918. You have two private fare contracts for fares with United Airlines. One contract applies to all flights except flight number 918 and one contract specifically for flight number 918. To ensure that you fare quote the itinerary correctly, include the account code and contract in your entry.

When to use

Fare quote an itinerary by a specific contract to quote the applicable fare.

How to use

To price by a specific contract, type the fare quote function identifier FQ followed by a dash (–) and the account name, @@ and the contract code.

Screen response:

FQ – IBM @@ IBMLON

Function identifier




Overriding an Airline Private Fare Quote

Galileo 360° Fares searches for the best fare when fare quoting an itinerary. If you have both Agency Private Fares and Airline Private Fares, and wish to quote a fare at a higher Agency Private Fare, you must override the Airline Private Fare.

Assuming an Agency Private Fare exists and is the desired level for the fare quote, the fare quote request must include all of the following modifiers to force the Agency Private Fare to quote.

• Account code

• Contract code

• Fare basis code followed by the word FLAT to identify flat or net-net type contracts.

When to use

Use this entry to override a lower Airline Private Fare and quote a fare at a higher Agency Private Fare.

How to use

To override a lower Airline Private Fare, type the fare quote function identifier FQ, dash (–) and account code, @@ and the contract code, @ and the fare basis code.

FQ – COAIR @@COEUR @HKLAXP

Function identifier Account code

Contract Fare basis code



Additional Formats

The following table lists sample formats to quote a fare using Agency Private Fares:

To fare quote… Use this format…

Private fares only for a specific account.

FQ-SHELL:P

Private and published fares for a specific account (IBM) for the first passenger of a multi name record.

FQP1-IBM

Private and published fares for a specific account (CARIB) and specific contract (MAYMTG) for segment 1 only.

FQS1-CARIB@@MAYMTG

Private and public fares for segments 1 and 3 for a specific account (DELTA).

FQS1.3-DELTA

Note: These formats may be used with FQBB, FQBC, FQBA and FQA function identifiers.

Displaying Rules from a Fare Quote

You can view fare rules each time you fare quote an itinerary. The format you use will depend on whether the quote is for a North American or international itinerary. The response to either of the format entries is a display of the contract rules for the private fare, followed by any published rules for a discounted fare.

Displaying Fare Rules for an International Itinerary

When you have quoted a fare for an international itinerary, you can view fare rules from a fare quote. Rules for a private fare will display first, followed by the published fare rules if it is a discount fare.

When to use

Use this entry to display a summary of rules from a fare that has been quoted.

How to use

To view fare rules from a fare quote for an international itinerary use the following steps.



1. Request a fare component list. Type the function identifier for fare quote rules, followed by the fare quote number.

FQN 1

Screen response:

2. Select the fare component by line number, and request a summary of the fare rules. Type the fare component number, slash (/) followed by S, the summary indicator.

FN1 / S

Screen response:

Note: Move Down (MD) to see published fare rules.

Fare quote rules Quote number

Component number Summary



Displaying Fare Rules for a North American Itinerary

When you have quoted a fare for a North American itinerary, you can view the fare rules for each segment. Rules for a private fare display first, followed by the published fare rules if it is a discount fare.

When to use

Use this entry to display the rules of the fare that has been quoted.

How to use

Use the following entry to display a summary of fare rules for segment 1.

Screen response:

Move down to display the published rules.

FN S1

Function identifier

Segment number



Moving an OSI Message

Some contracts require you to enter an OSI message into the Booking File, prior to ticketing. An OSI message may be required by the airline that issued the contract for tracking purposes.

You can find required OSI messages by accessing the contract rules section of the fare rules. You can find OSI messages in any rules display either from a fare display or fare quote.

When to use

Add an OSI message when contract or fare rules indicate an OSI message is necessary.

How to use

To enter OSI information into a reservation use the tab key to tab to the end of the OSI line as illustrated below.

The Galileo system responds with an asterisk at the end of the OSI line to notify you that your entry has been accepted.



Document Production

Tickets for Agency Private Fares are issued in the same manner as published fares. Document production for a private fare is only allowed from a filed fare field.

All ticketing format entries stored in an Agency Private Fares record print on the ticket under the following conditions:

If… It prints…

A fare basis code exists In the fare basis code box on the ticket and in the linear.

A ticket designator exists On the ticket.

Note: If more than one ticket designator applies, MULTI will appear in the box.

An IT number exists On the ticket.

Endorsement box data exists On the ticket.

Discounts are off a published fare that has no overrides or waivers to the published rules

NVA/NVB dates only.

Working with the Assumed City Function

If you frequently use certain account codes, you can use the assumed city function to set your workstation to automatically check for private fares for a maximum of two accounts.

Account Default

You are able to set a default for a fare display. If you do not enter an account code with a fare display request, the account codes in the assumed city file are used.

When to use

Use an account default if you frequently work with the same accounts.



How to use

To enter account codes in the assumed city file type the function identifier HMCT, dash (–), the account code, slash (/) and ACCT for account table.

The Galileo system responds with OK.

Multiple Accounts

To enter multiple accounts (maximum 2), separate each code with a dash (–).

Example

HMCT–UNITED–EUROPE/ACCT

Displaying an Assumed City File

You can display the assumed city file to view your terminal settings.

When to use

Display your assumed city file to view your current settings.

How to use

To display the assumed city file use the following entry:

HMCT

Screen response:

HMCT – UNITED / ACCT

Function identifier

Account code Account table display



Cancelling Account Codes from the Assumed City File

You may cancel your preferences in the assumed city file at any time.

When to use

Cancel your account codes in your assumed city file when your preferences change.

How to use

To cancel the account codes in the assumed city file, type the function identifier HMCT, the letter X, dash (–), and ACCT for account table display.

Galileo 360° Fares responds with OK to confirm the deletion of the accounts.

HMCTX – ACCT

Function identifier

Cancel

Account table display



Module Review

Use your study guide and the Galileo system as you work, and write down your answers in the space provided. When finished, check your answers in Appendix A: Answer Key.

1. Request a fare display from Chicago to London for the 21st of next month for published and private fares for account code MILLER.

_____________________________________________________________________________

2. Request a fare display for private fares only from Los Angeles to Frankfurt for the 21st of next month. The account code is POWER.

_____________________________________________________________________________

3. Request a fare display for the 15th of next month from Washington DC to London. The account code is DELTA and the contract is GOLDFILE.

_____________________________________________________________________________

4. From an international fare display request a summary of rules for the fare on line 3.

_____________________________________________________________________________

5. Fare quote an itinerary with the account code POWER.

_____________________________________________________________________________

6. Fare quote an itinerary with the account code DELTA and the contract GOLDFILE.

_____________________________________________________________________________




7. Fare quote segments 1 and 4 with account code MILLER.

_____________________________________________________________________________

8. What is the entry to display your assumed city file?

_____________________________________________________________________________


Module 8: Working with Airline Private Fares

Airline Private Fares allows air carriers who file fares with Air Tariff Publishing Company (ATPCO) to provide you with private fare data directly into the Galileo 360° Fares database. Airlines control access to the data and Galileo 360° Fares functionality is used for rule validation.

Your agency productivity is increased because less time is required to maintain your own private fare records.

Module Objective

On completion of this module you will be able to work with Airline Private Fares.

Working with Airline Private Fares

Airlines are able to file private fares and their corresponding rules and routes with ATPCO, in the same manner as they file public fares for travel throughout the world. Galileo 360° Fares receives airline private fare data from ATPCO via electronic transmission three times a day.

Private fares filed with ATPCO have the same attributes as public fares, and the only thing that differentiates them from public fares is their restricted use. Security within ATPCO may limit their use to any of the following:

• An agency pseudo city code and CRS code

• An agency IATA number

• An agency location

Study Guide / Working with Agency Private Fares (PF1) · PDF fileStudy Guide / Working with...

Documents

Transcript of Study Guide / Working with Agency Private Fares (PF1) · PDF fileStudy Guide / Working with...