Slide show template - Startpage |...

Change the Year in the Copyright field 1. Click ‘Insert’ in Top menu 2. Click ’Header & Footer’ 3. Write new Year in field ‘Footer’ 4. Click ‘Apply to All’

confidential

RESTRICTED

Profile Evolution

© 2

015 A

madeus I

T G

roup S

A

GLOBAL COMMUNICATION

Smriti SONAM

APRIL 2015


AGENDA

Functional changes

Display

Create/Update

Transfer

Miscellaneous

Roadmap

Activation & Implementation strategy

© 2

015 A

madeus I

T G

roup S

A


FUNCTIONAL CHANGES A

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 4

Traveller Profile

© 2

015 A

madeus I

T G

roup S

A

Display Create/Update

Transfer Miscellaneous


Insert Co-branding logo 1. Click on placeholder

2. Click ’Insert’ 3. Click ‘Picture’

4. Locate the co-branding logo, click Insert

5. Align with bottom line of amadeus-logo

DISPLAY 1

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 6

FUNCTIONAL CHANGES

1.AIR preferences – Fixed order of display for PPK elements

2.Retention of profile in the context after Profile mode exit (PME)

3.Similar Name List Display modification

© 2

015Am

adeus I

T G

roup S

A


confidential

RESTRICTED

Page 7

Today

_ No preset order for the PPK elements input.

_ Display as per as their order of input (i.e) from oldest to newest.

_ New behaviour will always follow the fixed order K, DOM and EFT, instead of the order of input

_ Current Behaviour New Behaviour

D1.AIR preferences – Fixed order of display for PPK elements Description: To provide a fixed order to display of PPK element input

Reason: To have similar behaviour as in other preferences

This benefits the customers as now profiles are consistent and the storage of elements follow one particular order independent of order of entry

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 8

_ Current behaviour:

PME and PIE(Profile ignore/exit profile mode) both have the same behavior. Both exit profile mode and clean the profile in the context. After PME or PIE, a PD returns NEED PROFILE DISPLAY.

_ New behaviour:

Only in PME will exit profile mode but it will keep the profile in the context (if there is any).

D2.Retention of profile in the context after Profile mode exit (PME)

Description: To prevent profile from being ignored when performing PME command.

Benefit: Two options are now available: Exit and ignore the profile (PIE) or just exit profile mode (PME)

Impacts the Travel Choice biasing : From now on, with PME entry the profile remains available, though biasing process is not hindered and a new search of the profile is not needed.

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 9

D3.Similar Name List Display modification

Description: Application of new rules to display similar names

Traveller profile name display: 22 characters

Company profile names display: 25 characters

Traveler names split : name’s length > 22 char

Company names split : name’s length > 25 char

Reason: To harmonize the airline and traveller profile behaviour. Hence common set of rules are created and full profile name is displayed.

Traveller Profile Current behaviour New behaviour

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 10

Company Profile

Current behaviour New behaviour

© 2

015 A

madeus I

T G

roup S

A






CREATE UPDATE

2

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 12





FUNCTIONAL CHANGES

1.Non acceptance of provider code at profile update

2.Fare PNR Transferable Elements – INF and PAX deletion in profile

3.Remark Update harmonization

4.SSR Creation / Update in Traveler, Company and Agency Profiles

5.SSR Explosion in Profile

6.FO Element Removal

7.Option Element


confidential

RESTRICTED

Page 13

_ Cryptic Entry:

_ >RM FREETEXT *AL-AF

_ Current behaviour

_ New behaviour

_ Note: Error messages shall not be received as per the new behaviour because AL-AF will be treated as free text.

C/U1.Non acceptance of provider code at profile Description: For the following elements Provider Codes will not be accepted anymore. In the case where a profile that already contains Provider Code , those Provider codes will remain hidden.

• Miscellaneous remark (RM) Confidential remark (RC)

• Fare discount (FD) Fare endorsement (FE)

• Commission (FM) Form of payment (FP)

Miscellaneous ticketing information (FS) Tour code (FT)

Fare print override (FY) Miscellaneous ticketing information (FZ)

Advanced seat request (ST)

Reason: Minimum usage. Only 193 Traveller Profiles use this functionality

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 14

_ Current behaviour

• FE accepted PAX and INF

• Some others are not accepted and are returning an error:

• Error message received :

_ New behaviour

• PAX and INF will not be accepted for any Fare entries

C/U2.Fare PNR Transferable Elements – INF and PAX deletion in profile Description: INF and PAX entries will no more be accepted as input for fare entries.

Reason: The number of profiles using these entries is very less

(PAX: 2906 Traveller Profile for FE) (PAX: 86 Company Profile for FE)

(INF: 33 Traveller Profile for FE) (INF:6 Company Profile for FE)

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 15

Ex: If RM element in profile (RMC CHECK) is updated by 5/A/NEW REMARK entry: Following are the results.

Current behaviour in PNR mode

Profile mode


C/U3.Remark Update harmonization Description:

• Only change of text of the remark is allowed

• Changing the category is not permissible

Reason: Alignment to PNR behaviour

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 16

_ Current behaviour New behaviour

C/U4.SSR Creation / Update in Traveler, Company and Agency Profiles Description: Air code and Status code update will be possible even if already defined.

Reason: Alignment of Distribution Profile to Airline Profile behaviour

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 17

Ex: For SR*BIKE entry:

_ Current behaviour

_ New behaviour

C/U5.SSR Explosion in Profile Description: SSR explosion entry, which is currently rejected, will be accepted for Traveller, Company and Agency profiles.

Reason: To harmonise the display between all profiles.

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 18

C/U6.FO Element Removal

Description:

FO element will be removed from the profiles for the following reasons:

• FO elements are not linked to profile process

• Statistics show very little evidence of FO element usage by Travel agencies (less than 0,01% of profiles concerned)

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 19

_ Current behaviour

_ New behaviour

_ PNR behaviour

C/U7.OP: Option Element Description: When entering an OP with several offices or dates, several OPs will be created each one containing only one date and one office.

Reason: Increase legibility also alignment to PNR

© 2

015 A

madeus I

T G

roup S

A






TRANSFER

3

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 21

FUNCTIONAL CHANGES

1.Error message during profile transfer

2.Transfer of profile elements to a PNR while updating a profile

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 22

_ Current behaviour

_ New behaviour

_ <Element Type>, <Line Number of Profile Display>: <Functional Error Message> (<Error Code>)

T1.Error message during profile transfer

Description: Providing a new structure to the error message

Benefit: Increasing illegibility of the error message

Addition of functional error to the existing error message.

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 23

_ Current behaviour

_ New behaviour

T2.Transfer of profile elements to a PNR while updating a profile

Description: Agent will be forced to save a the profile before transferring it to a PNR (same as it is currently applicable to PME)

Benefit: Prevention of loss of data

© 2

015 A

madeus I

T G

roup S

A

FUNCTIONAL CHANGES

1.Error message standardization

2. Itinerary Section removal for traveller, company and agency profiles


confidential

RESTRICTED

Page 26

1). Format of display (removal of space character)


2). Homogenization of display


M1.Error message standardization

Description: Formulate a standard display for any kind of error message

Two major changes to be noticed:

1. Removal of space in display format

2. Homogenization of the displays for all the invalid formats

Reason: standardize the format and display of all the error messages.

ELEMENT NOT ALLOWED > INVALID/ITEM ALREADY EXISTS>

ELEMENT NOT ALLOWED> INVALID/ITEM ALREADY EXISTS>

PCN/ak!@#$\%^*s1548aug()-+=\{[\}]:; -> CHECK INPUT PCN/SS12^SS -> INVALID FORMAT >PCN/SS12^SS PCN/SS^12SS -> CHECK INPUT PCN/skjskdLLP./[]lkl -> INVALID FORMAT >PCN/SKJSKDLLP[]LKL PCN/skjskdLLP[]lkl -> CHECK INPUT

INVALID FORMAT/NOT ENTERED/>

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 27

M2.Removal of Itinerary data section

Reason: Statistics show very little evidence of Itinerary data in profiles (less than 0,01% of profiles concerned)

Description: The itinerary section includes the following types of itinerary segments:

- Segment Sell (SS) :

Reserve seats on flights for particular classes and dates.

- Open flight segments (SO) :

Used when the agent does not know all the details of a passenger flight plan.

- Informational flight segments (SI) :

Used to maintain continuity in an itinerary.

Not mandatory

Ensure that the PNR contains as much detail as possible concerning the passenger's itinerary.

© 2

015 A

madeus I

T G

roup S

A


confidential

RESTRICTED

Page 29

ROADMAP : DISPLAY

_ UAT start date for DISPLAY: Starting from Week 26 2015

_ Production start date: Week 30 2015

_ Production / UAT end date: Week 38 2015

JUNE JULY SEPTEMBR

2015

UAT PROD

Starts Week 26 Starts Week 30

Finishes on Week 38


confidential

RESTRICTED

Page 30

ROADMAP : TRANSFER/CREATE-UPDATE/MISC

_ UAT start date: Week 36 2015

_ Production start date: Week 41 2015

_ Production / UAT end date: Week 8 2016

© 2

015 A

madeus I

T G

roup S

A

2015 2016

SEPTEMBER OCTOBER FEBRUARY

UAT PROD

Starts Week 36 Starts Week 41

Finishes on Week 8


confidential

RESTRICTED

Page 32

Activation and Implementation Strategy

_ Activation to be done in several drops

• Depends on number of profile cryptic entries used

• From small to high traffic

_ Activation will be done in 2 Phases :

Phase 1: Activation by vendor code excluding the GCG

Phase 2: Activation by GCG

Slide show template - Startpage |...

Documents

Transcript of Slide show template - Startpage |...