Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

1

Amadeus FareXpert Negotiated Fares

User Guide – April 2010

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

2

Introduction

Amadeus is pleased to announce an enhancement to the Fares module within Amadeus FareXpert Negotiated. Amadeus FareXpert Addons (release phase 1) allows users to construct negotiated fare extensions by adding one or two Add-ons to an existing fare. The Add-on fare can be constructed at the origin, destination, or both ends of the main fare route.

How does the Addons module work? Add -ons can only be attached to an existing main fare. This means that the Addons module cannot be accessed before the Rule Definition, the Rule Condition and the Fare have been created. (If the fare for which the Add -ons need to be attached is already in existence, then one can proceed straight to the Addons module.) At least one Location Aggregate (see further on for explanation) must be created before attempting to create an Add- on Fares. The Location Aggregate will contain points, either at the origin or destination, from/to the Gateway City/Cities.

Features of Addons panel

� Create and maintain Add-on characteristics (origin and destination cities, directionality, one-way or

return, etc.) � Create and maintain Add-on evolutions (amounts and validity dates periods) � Display Add-on characteristics and Add-on evolutions

Accessing the Addons module

To access the Addons module, from the Amadeus FareXpert main menu, select the Negotiated Fare module. Select Fares module and from the sub menu list select ‘Addons’.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

3

The Addons Selection screen needs to be populated with the mandatory Carrier Code and Tariff Number information. These relate to the ‘main’ Fare contract.

(The End Point City, the Gateway City and the Fare Class could be added at this stage but only if opening an existing Addon, not whilst creating a new one. This is a great filtering option when many Add-ons have been created)

Click on the Create button

Click on Start

Main Fare’s Carrier Code and Tariff

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

4

The layout of the Addons Module is very similar to the current Fares Module with a ‘split screen’ scenario. The upper part contains the Add-on Characteristics. This part requires to be populated first. The second part contains the Add-on Evolution associated to each Add-on Characteristic above. The Evolution part is where the Add-on amount needs to be added. Like in the Fares Module, there may be more than one Add-on Evolution (amount) associated to an Add-on Characteristic.

All fields in the Add-on Characteristics are mandatory except the Rule box. Remember that the City codes must be filled in the order requested, i.e. End Point City code goes before the Gateway City code. The Add-on Zone is also a mandatory field; this means that in order to create the Addons Module a Location Aggregate Name must be in place beforehand.

How to create an Add-on: Follow the screens below, in order to thoroughly understand how to create an Add-on for a main fare. Several examples have been created with Add-ons at origin, Add-ons at destination and Add-ons at both origin and destination. Example 1 In this example a fare with BA has been created. The main route of the fare is LON to BKK and there are Add-ons at origin in the UK. The gateway city is LON. Add-ons in the UK: from GLA, MAN and ABZ In order to create an Add-on screen the main fare LON BKK must be created first. Below is a screen shot of this fare Carrier BA, Tariff 4, Rule BKK1:

Insert a line

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

5

However, the first step is to create at least one Location Aggregate for the Add-ons. When there are Add-ons just at origin, one Location Aggregate needs to be created. The Location Aggregate will include destination points.

The next step is to proceed to Addons sub menu in the Fares Module. Only one Addons module will be created.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

6

End Point City: enter the destination/origin city (Add-on origin/destination) in this example GLA or ABZ or MAN Gateway City: add the relevant Gateway city for the Add-on (Gateway city means ‘the hub’ where an airline flies on the main route) in this case LON Fare Class: enter relevant Fare Basis Code of the main fare Rule: enter relevant Rule or leave blank to apply to every Rule within the main contract Directionality: enter directionality OW/RT: Enter whether your add on is one way or return (these need to be consistent with the type of fare basis entered in the Rule Definition. i.e. if Rule Definition has been loaded as RT then here must be loaded as RT too) Add-on Zone: This box MUST be populated with the Add-on Location Aggregate ‘opposite’ to the one relating to the Add-on. E.g. in this example, GLA via LON is the Add-on but the Add-on Zone must contain the Location Aggregate of the Thai destinations. Even if the destination is just BKK a location aggregate needs to be created. The reason why a Location Aggregate is necessary here is to attach the Add-on to a destination. The three dots may be used to prompt the name of the Aggregates available for this functionality. Currency: Add the currency in which the fares should be quoted. Once the Add-on from GLA to LON has been released then all other cities will need to be added in the Add On module (MAN to LON and ABZ to LON). Once all Add-ons have been added, the screen should look like below:

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

7

(NB :As the Addons Module is very ‘broad’ (BA Tariff 4) this means that a variety of different contracts could utilise this same Add-on Module. For example Add-ons to Malaysia or Singapore or India etc on BA. The Location Aggregate allows the Add-on to know where it needs to ‘attach’ itself and to which main contract.) Example 2: In this example a fare with AA has been created. The main route of the fare are LON to NYC and LON to LAX there are Add-ons at destination in the US. The gateway cities are NYC and LAX. Add-ons in the US: to PHL, BOS, LAS and SFO (PHL BOS and SFO via NYC and LAS, SFO via LAX) In order to create an Add-on screen the main fare LON NYC and LON LAX must be created first. Below is a screen shot of this fare Carrier AA, Tariff 1, Rule USA1:

However, once again the first step is to create at least one Location Aggregate for the Add-ons. When there are Add-ons just at destination, one Location Aggregate needs to be created. The Location Aggregate will include origin points.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

8

The next step is to proceed to Addons sub menu in the Fares Module. Only one Addons module will be created.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

9

End Point City: enter the destination/origin city (Add-on origin/destination) in this example PHL, BOS, LAS or SFO. Gateway City: add the relevant Gateway city for the Add-on (Gateway city means ‘the hub’ where an airline flies on the main route) in this case NYC and/or LAX. Fare Class: enter relevant Fare Basis Code of the main fare Rule: enter relevant Rule or leave blank to apply to every Rule within the main contract Directionality: enter directionality OW/RT: Enter whether your add on is one way or return (this needs to be consistent with the type of fare basis entered in the Rule Definition. i.e. if Rule Definition has been loaded as RT then here must be loaded as RT too) Add-on Zone: This box MUST be populated with the Add-on Location Aggregate ‘opposite’ to the one relating to the Add-on. E.g. in this example, PHL via NYC is the Add-on but the Add-on Zone must contain the Location Aggregate of the UK origins. Even if the origin is just LON a location aggregate needs to be created. The reason why a Location Aggregate is necessary here is, this time, to attach the Add-on to an origin. The three dots may be used to prompt the name of the Aggregates available for this functionality. Currency: Add the currency in which the fares should be quoted. Once the Add-on from NYC to PHL has been released then all other cities will need to be added in the Add On module (NYC to BOS, NYC to SFO, LAX to LAS and LAX to SFO). Once all Add-ons have been added, the screen should look like below:

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

10

(NB: As the Addons Module is very ‘broad’ (AA Tariff 1) this means that a variety of different contracts could utilise this same Addon Module. For example add ons going to US or Canada on AA. The Location Aggregate allows the Add-on to know where it needs to ‘attach’ itself and to which main contract.) Example 3: In this example, the main fare is with QF. Add-ons are required both from UK as well as within Australia. The gateway city in the UK is LON and in Australia is SYD. Add-ons in the UK: from EDI, GLA and NCL Add-ons in Australia: to PER, BNE and ASP Below is a screen of the main fares loaded LON SYD and LON MEL (in Low Season, only SYD is the gateway city) for Carrier QF Tariff 0004 and Rule QAN3 Add-ons need to be created in the Addons field within the Fares Module. However, the first step is, once again, to create Location Aggregates for all Add-ons. When there are Add-ons both at origin and at destination, two Location Aggregates need to be created. There is no particular order in which these need to be generated. One will include all UK origins GLA, EDI, NCL and LON (this could be left as GB also), the other will include all destinations in Australia PER, BNE, ASP as well as SYD and MEL (likewise this could be left as AU also).

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

11

Location Aggregate for the UK

Location Aggregate for Australia

Next step proceed to Addons sub menu in the Fares Module. Only one Addons will need to be created for both UK and Australian Add- ons. All Add-ons will be produced under the main fare rule Airline QF Tariff 0004.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

12

End Point City: enter the destination city (add on destination) Gateway City: add the relevant Gateway city for the add on (Gateway city means ‘the hub’ where an airline flies on the main route) Fare Class: enter relevant Fare Basis Code Rule: enter relevant Rule or leave blank to apply to every Rule within the main contract Directionality: enter directionality OW/RT: Enter whether your add on is one way or return Add-on Zone: This box MUST be populated with the Add-on Location Aggregate ‘opposite’ to the one relating to the add on. E.g. in this example, PER via SYD is the Add-on but the Add-on Zone must contain the Location Aggregate for the UK origins. Likewise, when creating Add-ons for the UK origins, the Add-on Zone box should contain the Location Aggregate for the Australian destinations. The three dots may be used to prompt the name of the Aggregates available for this functionality. Currency: Add the currency in which the fares should be quoted.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

13

Once the Add-on from SYD to PER has been released then all other cities will need to be added in the Addons module. In the example below, after SYD PER, the UK Add-on MAN LON has been added.

It is important to notice, once again, that the Addon Zone is filled with the opposite cities location aggregate. So, MAN LON will have the corresponding location aggregate 1AQF2 which includes all the Australian destinations. Once all Add-ons have been added, the screen should look like below:

Click on Submit & Close to create all Add-ons at once. All the Add-ons will be released to create a new ‘constructed’ fare on the main LON SYD fare. The above screen will create Add-ons for both origin and destination, allowing the fare to be constructed as an origin add on (ie MAN LON) or at destination (ie SYD PER) or at both ends thus creating a through fare MAN PER via LON and SYD.

Cop

yrig

ht ©

2005

Am

adeus G

TD

. A

ll R

ights

Reserv

ed

Am

adeus C

onfidential In

form

ation

. U

na

uth

orised u

se

and

dis

clo

sure

str

ictly fo

rbid

den

.

14

Addon Evolution Area: Amount: enter the amount corresponding to the add on Effective and Discontinue Dates: enter the corresponding effective and discontinue dates of the Add-on.

In the above example, the add on net amount to be added to the main through fare is GBP40 between today and 31

st October but will become GBP50 if sold for 1

st November onwards.

The functionality shown above with Evolutions is exactly the same as the current the Fares Module.

Important information about Addons Functionality of Add-on Module Phase 1:

• Add-ons will only work if the Airline coded in the Addons Module is the same as the Main Fare Contract. Eg MAN-BA-LON-BA-NYC

• Add-ons will work only if in the same domestic area. The only exception to this rule is that

Europe (zone 210) is considered ONE country and therefore Add-ons within Europe will work. Eg FRA-BA-LON-BA-NYC

Future plans for Phase 2 (release date to be advised):

• Add-ons with different carriers eg MAN-BD-LON-BA-NYC

• International Add-ons eg LON-SA-JNB-SA-WDH

• Flexibility of Fare Class and/or not mandatory – currently have to specify the whole fare class but want to be able to specify for example all N fare classes in one line N- or make the option of fare class not mandatory.

• Child / infant discounts that are different on the add-on contract to the main contract Eg LON-NYC child discount 75% and MAN-LON child discount 60%