Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Ludwig [deprecated] > New Gen PSS > Flashcards

New Gen PSS Flashcards

1
Q

NewGenPSS transition: steps

A

1- Foundations
2- Transformation
3- Simplification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

NewGenPSS foundation step

A

How to get new revenues with the current architecture
so not much of Order

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Interline hackathon: demo main highlights

A

Shopping creates an Offer that contains 2 products from 2 different airlines and can be seen in a UI

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Hackathon scope (2)

A
  • Define technological stack of OfmS
  • 1st use case: interline à la NDC (shopping/pricing)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Main event broker selected for OfMS

A

NATS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

OfMS benefits

A

1- Enhanced offers
2- Improved customer experience
3- Optimised distribution
4- Streamlined processes and synergies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

OfMS benefits: 2 examples of “streamlined processes”

A

Centralised offer definition, etc.
Increase self-service capabilities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Needed for OfMS business continuity

A

API interoperability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

OfMS transition: 2 steps

A

1- Relies fully on PSS but stores Open Offers

2- Mix of PSS granular verbs or OfMS APIs. If use OfMS, benefit from Orchestration that can go to PSS or new content or external content

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What modules does Ludwig keep even with External OfMS (3)

A
  • OfMS APIs
  • Offer framework for gateway
  • Open Offer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

2 modes of external content acquisition

A
  • As part of Product catalogue
  • Real time through NDC cascading
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Open Offer APIs: categories

A
  • CRUD
  • Event streaming
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Technical ways to control Offer definition

A

UI or Business Control API

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Offer states

A
  • Proposed = ready to be retailed
  • Selected = requested to be confirmed
  • Confirmed = ready to be contracted
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

HA: OfMS API for DCS

A
  • Create Offer from PNR (bridge from legacy to OfMS, will disappear in channels fully Offer-based)
  • ServiceList from Offer
  • Book & price unchanged
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Ludwig as box on top: acronym

A

NAC = Non-Altéa Carrier

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Ludwig as box on top: high-level architecture

A

Front-Ends
|
Ludwig box on top
|
External PSS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Ludwig as box on top: benefit of using GDS flow

A

Few gaps and almost all airlines already distributed in Ludwig GDS today

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Ludwig as box on top: main difference with GDS flow

A

Ticketing: Ludwig asks the external PSS to issue on the airline stock, not TA stock

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What product can request an external PSS for ticket issuance and steps

A

Web eTKT and Web EMD
1- prepare everything on behalf of the a/l
2- get the ticket number and update PNR in external PSS with it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Ludwig as box on top: what are the main gateways to the PSS

A

Ludwig Reservation and Web e-TKT/Web EMD

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Ludwig as box on top: specificity of AA ticket issuance

A

Done by ARI Robotics so asynchronous: the customer doesn’t get his ticket right away

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Ludwig as box on top: synch with ARI

A

ARI Robotics requests issuance via WBS but will be replaced by DIH as ARI is being decommissioned
Note that PNR synch is still with RES

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Ludwig as box on top: who should do the servicing

A

The box as only it has access to price modifications, PSS has no idea (or has to be manual)

25
Q

Ludwig as box on top: gaps for Offer

A

Everything is off the shelf except:
- Service inventory (9MY)
- Dashboards (based on HOT) (2MY)
- BIF for INV criteria (0.5MY)
- Number of seats left (0.5MY)

26
Q

The 2 key solutions for business continuity seen from Order

A

Order bi-modal
Offer integration layer (making the link btw PSS Offer and OMS)

27
Q

Transition to NewGenPSS viewed from Digital

A

DC hides the transition for .com and gradual enhancements will not be disruptive

28
Q

Transition to NewGenPSS viewed from Delivery

A

Order bimodal hides the changes to Delivery.
New capabilities can be rolled out later like sales at airport w/ OfMS

29
Q

Benefits of NewGenPSS for financial flows

A

Real time so
- faster settlement
- more visibility

30
Q

Hackathon: airlines

A

LH and EW

31
Q

Difference between retailer/supplier model and legacy

A

In legacy model, the supplier is not contacted

32
Q

Hackathon: high-level architecture

A
  • Digital sends shopping request (DC)
  • OfMS orchestration
    • NATS orchestrate different micro-services including “Connectors” and services with business logic
  • Calls to Ludwig FP and 1N shopping
  • Store in Open Offer
33
Q

Hackathon: business logic

A
  • Determine what a/l to contact on what part of the iti
  • Reconcile the different bits of iti (MCT, 200 cheapest…)
34
Q

Hackathon and cloud

A

Cloud-native in Azure

35
Q

Hackathon : connectivity to Flex and 1N: APIs

A
  • Flex: EDI
  • 1N: NDC AirShopping/OfferPrice
36
Q

Hackathon: where are offers stored

A

Open Offer of the retailer

37
Q

Hackathon: leaders & groups involved

A

PO: Corinne
SM: Federico

OFR+SSP+TPE

38
Q

Interline MVP: impact on INV

A

Inventory guarantee to simplify Digital pre-book orchestration

39
Q

Scrum team on OfMS APIs and scope

A

Magnum:
- OfMS APIs
- Deeplink (EY, LH)

40
Q

Scrum team for Interline MVP & scope

A

NUTS:
- Supplier/provider
- Interline MVP
- Polaris

41
Q

Scrum for Open Offer

A

Groot

42
Q

Types of OfMS APIs

A
  • Sales channel API
  • Core platform API
43
Q

Interline: how is it handled today

A

One pricing engine on behalf of several a/l (either airline pricing or GDS)
Based on distributed schedules and filing

44
Q

Interline: today - On SQ fare+LH fare, can SQ apply DP ?

A
  • Needs LH agreement that still combinable
  • Financial flow to be handled
  • LH & SQ cannot control the iti price with conflicting instructions
45
Q

Interline: retailer/supplier main benefit

A

Filing no longer needs to be aligned

46
Q

Interline: retailer/supplier: name of what the retailer gives to the supplier

A

The settlement value

47
Q

Interline: retailer/supplier: control of the supplier?

A

Can require boundaries on retailing price (but doesn’t know this price when building its suboffer)

48
Q

Interline: retailer/supplier: what could be a first step?

A

Pending accounting transfo: settlement done on fare amounts instead of settlement values

49
Q

Product cluster + ex

A

Set of products amongst which customers can perform their choice
- a subset of 4* hotels

50
Q

What APIs are we developing in 2022

A
  • HA
  • EY+LH for deeplink in MetaSearch
  • AF “Casa”
  • AA
51
Q

NAC: how is the catalogue built by the box on top

A

From ATPCo + RES layer gets info from PSS

52
Q

Other potential benefit of OrMS for interline

A

Seamless management of invol & vol changes between partners?

53
Q

NewGenPSS call centre solution and techno

A

Service Centre, based on RefX

54
Q

Ludwig box on top: how do we find the ancillaries

A

Defined manually in AAM UI + ATPCo

55
Q

Evolution of downstream applications in time to NewGenPSS

A

First settlement (after OOM)
Then delivery

56
Q

Expected length of transformation [2023]

A

5 years to have the first fu use cases on NewGenPSS all the way to delivery (for the early adopters) so from 2027

57
Q

When will bundling be available in the transformation

A

When Order becomes master

58
Q

Customer segmentation for NewGenPSS and why

A

Strategic Altéa/Large Altéa/Other Altéa/Non-Altéa

Because NewGenPSS business case unblocks new funding depending on what we sign

59
Q

Priority leads for NewGenPSS for Rémy

A

OneWorld (as BA, AY, AA and QR)
AI (rich and Tata group: hotels, TCS, etc.)

Ludwig [deprecated] (54 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions