New Gen PSS Flashcards
NewGenPSS transition: steps
1- Foundations
2- Transformation
3- Simplification
NewGenPSS foundation step
How to get new revenues with the current architecture
so not much of Order
Interline hackathon: demo main highlights
Shopping creates an Offer that contains 2 products from 2 different airlines and can be seen in a UI
Hackathon scope (2)
- Define technological stack of OfmS
- 1st use case: interline à la NDC (shopping/pricing)
Main event broker selected for OfMS
NATS
OfMS benefits
1- Enhanced offers
2- Improved customer experience
3- Optimised distribution
4- Streamlined processes and synergies
OfMS benefits: 2 examples of “streamlined processes”
Centralised offer definition, etc.
Increase self-service capabilities
Needed for OfMS business continuity
API interoperability
OfMS transition: 2 steps
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
What modules does Ludwig keep even with External OfMS (3)
- OfMS APIs
- Offer framework for gateway
- Open Offer
2 modes of external content acquisition
- As part of Product catalogue
- Real time through NDC cascading
Open Offer APIs: categories
- CRUD
- Event streaming
Technical ways to control Offer definition
UI or Business Control API
Offer states
- Proposed = ready to be retailed
- Selected = requested to be confirmed
- Confirmed = ready to be contracted
HA: OfMS API for DCS
- Create Offer from PNR (bridge from legacy to OfMS, will disappear in channels fully Offer-based)
- ServiceList from Offer
- Book & price unchanged
Ludwig as box on top: acronym
NAC = Non-Altéa Carrier
Ludwig as box on top: high-level architecture
Front-Ends
|
Ludwig box on top
|
External PSS
Ludwig as box on top: benefit of using GDS flow
Few gaps and almost all airlines already distributed in Ludwig GDS today
Ludwig as box on top: main difference with GDS flow
Ticketing: Ludwig asks the external PSS to issue on the airline stock, not TA stock
What product can request an external PSS for ticket issuance and steps
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
Ludwig as box on top: what are the main gateways to the PSS
Ludwig Reservation and Web e-TKT/Web EMD
Ludwig as box on top: specificity of AA ticket issuance
Done by ARI Robotics so asynchronous: the customer doesn’t get his ticket right away
Ludwig as box on top: synch with ARI
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
Ludwig as box on top: who should do the servicing
The box as only it has access to price modifications, PSS has no idea (or has to be manual)
Ludwig as box on top: gaps for Offer
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)
The 2 key solutions for business continuity seen from Order
Order bi-modal
Offer integration layer (making the link btw PSS Offer and OMS)
Transition to NewGenPSS viewed from Digital
DC hides the transition for .com and gradual enhancements will not be disruptive
Transition to NewGenPSS viewed from Delivery
Order bimodal hides the changes to Delivery.
New capabilities can be rolled out later like sales at airport w/ OfMS
Benefits of NewGenPSS for financial flows
Real time so
- faster settlement
- more visibility
Hackathon: airlines
LH and EW
Difference between retailer/supplier model and legacy
In legacy model, the supplier is not contacted
Hackathon: high-level architecture
- 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
Hackathon: business logic
- Determine what a/l to contact on what part of the iti
- Reconcile the different bits of iti (MCT, 200 cheapest…)
Hackathon and cloud
Cloud-native in Azure
Hackathon : connectivity to Flex and 1N: APIs
- Flex: EDI
- 1N: NDC AirShopping/OfferPrice
Hackathon: where are offers stored
Open Offer of the retailer
Hackathon: leaders & groups involved
PO: Corinne
SM: Federico
OFR+SSP+TPE
Interline MVP: impact on INV
Inventory guarantee to simplify Digital pre-book orchestration
Scrum team on OfMS APIs and scope
Magnum:
- OfMS APIs
- Deeplink (EY, LH)
Scrum team for Interline MVP & scope
NUTS:
- Supplier/provider
- Interline MVP
- Polaris
Scrum for Open Offer
Groot
Types of OfMS APIs
- Sales channel API
- Core platform API
Interline: how is it handled today
One pricing engine on behalf of several a/l (either airline pricing or GDS)
Based on distributed schedules and filing
Interline: today - On SQ fare+LH fare, can SQ apply DP ?
- Needs LH agreement that still combinable
- Financial flow to be handled
- LH & SQ cannot control the iti price with conflicting instructions
Interline: retailer/supplier main benefit
Filing no longer needs to be aligned
Interline: retailer/supplier: name of what the retailer gives to the supplier
The settlement value
Interline: retailer/supplier: control of the supplier?
Can require boundaries on retailing price (but doesn’t know this price when building its suboffer)
Interline: retailer/supplier: what could be a first step?
Pending accounting transfo: settlement done on fare amounts instead of settlement values
Product cluster + ex
Set of products amongst which customers can perform their choice
- a subset of 4* hotels
What APIs are we developing in 2022
- HA
- EY+LH for deeplink in MetaSearch
- AF “Casa”
- AA
NAC: how is the catalogue built by the box on top
From ATPCo + RES layer gets info from PSS
Other potential benefit of OrMS for interline
Seamless management of invol & vol changes between partners?
NewGenPSS call centre solution and techno
Service Centre, based on RefX
Ludwig box on top: how do we find the ancillaries
Defined manually in AAM UI + ATPCo
Evolution of downstream applications in time to NewGenPSS
First settlement (after OOM)
Then delivery
Expected length of transformation [2023]
5 years to have the first fu use cases on NewGenPSS all the way to delivery (for the early adopters) so from 2027
When will bundling be available in the transformation
When Order becomes master
Customer segmentation for NewGenPSS and why
Strategic Altéa/Large Altéa/Other Altéa/Non-Altéa
Because NewGenPSS business case unblocks new funding depending on what we sign
Priority leads for NewGenPSS for Rémy
OneWorld (as BA, AY, AA and QR)
AI (rich and Tata group: hotels, TCS, etc.)
