profile evolution - startpage |...

$: Profile Evolution - Startpage | Amadeusinsights.sca.amadeus.com/siteassets/product-news/2015-03/...Title Profile Evolution Author Zakaria ALKABBAB $contractor$ Created Date 10/7/2015$
Change the Year in the Copyright field1. 2. 3.

4.

Confidential

RESTRICTED

Confidential

RESTRICTED

Profile Evolution

© 2

015 A

madeus I

T G

roup S

A

GLOBAL COMMUNICATION

Zakaria AL KABBAB

SEPTEMBER 2015


4.

Confidential

RESTRICTED

Page 2

Agenda

© 2

015 A

madeus I

T G

roup S

A

A. Functional changes1. Search and Display

2. Update and Transfer

B. Roadmap1. Search and Display

2. Update and Transfer

C. Activation & Implementation strategy


4.

Confidential

RESTRICTED

FUNCTIONAL CHANGESA

© 2

015 A

madeus I

T G

roup S

A


4.

Confidential

RESTRICTED

Page 4

Traveller Profile

© 2

015 A

madeus I

T G

roup S

A

Phase 1: Search and Display

Phase 2: Update And Transfer


4.

Confidential

RESTRICTED

SEARCH & DISPLAY1

© 2

015 A

madeus I

T G

roup S

A


4.

Confidential

RESTRICTED

Page 6

1.Similar Name List Display modification

2. Itinerary Section removal

3.[Postponed] Retention of profile in the context after Profile mode exit (PME)

4.[De-scoped] SSR Multiple update

© 2

015 A

madeus I

T G

roup S

A

Functional changes


4.

Confidential

RESTRICTED

Page 7

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 ProfileCurrent behaviour New behaviour

© 2

015 A

madeus I

T G

roup S

A

A.1.1. Similar Name List Display modification


4.

Confidential

RESTRICTED

Page 8

Company Profile

Current behaviour New behaviour

© 2

015 A

madeus I

T G

roup S

A

A.1.1. Similar Name List Display modification


4.

Confidential

RESTRICTED

Page 9

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

A.1.2. Removal of Itinerary data section


4.

Confidential

RESTRICTED

UPDATE & TRANSFER2

© 2

015 A

madeus I

T G

roup S

A


4.

Confidential

RESTRICTED

Page 11

1.[new] Retention of profile in the context after Profile mode exit (PME)

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

3. Non acceptance of provider code at profile update

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

5. Remark Update harmonization

6. SSR Explosion in Profile

7. FO Element Removal

8. OP Option Element

9. Error message during profile transfer

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

11.Error message standardization

© 2

015 A

madeus I

T G

roup S

A

Functional changes


4.

Confidential

RESTRICTED

Page 12

Description:

To prevent profile from being erased 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.

_ 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).

© 2

015 A

madeus I

T G

roup S

A

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


4.

Confidential

RESTRICTED

Page 13

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

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

© 2

015 A

madeus I

T G

roup S

A

A.2.2. AIR preferences – Fixed order of display for PPK elements


4.

Confidential

RESTRICTED

Page 14

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 Travel Profile use this functionality

_ 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.

© 2

015 A

madeus I

T G

roup S

A

A.2.3. Non acceptance of provider code at profile


4.

Confidential

RESTRICTED

Page 15

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)

_ 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

© 2

015 A

madeus I

T G

roup S

A

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


4.

Confidential

RESTRICTED

Page 16

Description:

• Only change of text of the remark is allowed

• Changing the category is not permissible

Reason:

Alignment to PNR behaviour

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


© 2

015 A

madeus I

T G

roup S

A

A.2.5.Remark Update harmonization


4.

Confidential

RESTRICTED

Page 17

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.

Ex: For SR*BIKE entry:

_ Current behaviour

_ New behaviour

© 2

015 A

madeus I

T G

roup S

A

A.2.6. SSR Explosion in Profile


4.

Confidential

RESTRICTED

Page 18

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

A.2.7. FO Element Removal


4.

Confidential

RESTRICTED

Page 19

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

_ Current behaviour

_ New behaviour

_ PNR behaviour

© 2

015 A

madeus I

T G

roup S

A

A.2.8. OP: Option Element


4.

Confidential

RESTRICTED

Page 20

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.

_ Current behaviour

_ New behaviour

_ <Element Type>, <Line Number of Profile Display>: <Error message coming from PNR> (<Error Code>)

© 2

015 A

madeus I

T G

roup S

A

A.2.9. Error message during profile transfer


4.

Confidential

RESTRICTED

Page 21

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

_ Current behaviour

_ New behaviour

© 2

015 A

madeus I

T G

roup S

A

A.2.10. Transfer of profile elements to a PNR while updating a profile


4.

Confidential

RESTRICTED

Page 22

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.

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


2). Homogenization of display


© 2

015 A

madeus I

T G

roup S

A

A.2.11. Error message standardization

ELEMENT NOT ALLOWED >INVALID/ITEM ALREADY EXISTS>

ELEMENT NOT ALLOWED>INVALID/ITEM ALREADY EXISTS>

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

INVALID FORMAT/NOT ENTERED/>


4.

Confidential

RESTRICTED

Page 24

_ UAT start date (All offices): 24 JULY 2015

_ Pilot start date (Non GCG): 3 SEPTEMBER 2015

_ Production start date (Non GCG): 29 OCTOBER 2015

_ Pilot start date (GCG): 5 NOVEMBER 2015

_ Production start date (GCG): 19 NOVEMBER 2015

_ Production start date (Offices with traffic > 1%): 26 NOVEMBER 2015

Roadmap: SEARCH & DISPLAY

JUNE JULY SEPTEMBER

S&D

UAT

PROD

Starts 24 JULY Starts 29 OCT

OCTOBER NOVEMBER

Starts 3 SEP

PILOT


4.

Confidential

RESTRICTED

Page 25

_ UAT start date (All offices): 3 DECEMBER 2015

_ Pilot start date (Non GCG): 12 JANUARY 2016

_ Production start date (Non GCG): 9 FEBRUARY 2016

_ Pilot start date (GCG): 8 MARCH 2016

_ Production start date (GCG): 5 APRIL 2015

_ Production start date (Offices with traffic > 1%): 24 APRIL 2015

© 2

015 A

madeus I

T G

roup S

A

Roadmap: UPDATE & TRANSFER

2015 2016

UAT

PROD

Starts 3 DEC Starts 9 FEB

JANUARY FEBRUARY MARCH APRILJULY

Starts 12 JAN

PILOT


4.

Confidential

RESTRICTED

Page 27

_ Activation done in several drops

• From small to high usage of profiles

_ Use of Office Mask

Activation and Implementation Strategy


4.

Confidential

RESTRICTED

Thank you

© 2

015 A

madeus I

T G

roup S

A

You can follow us on:

AmadeusITGroup

amadeus.com/blogamadeus.com

profile evolution - startpage |...

Documents