Pre-sales Flashcards
TK RFP for optimisation: 2 options
1) RMS + RAAV + DP (+ ABI option): DP omnichannel
2) Live DP on Ludwig shopping only
TK: subtlety of our proposal on channels with Ludwig shopping and options
Pricing is not Ludwig anyway
- Either they try to file aligned with Ludwig DP…
- Their pricing calls ours
IAG transformation program: name
Nexus
Aims of Nexus
IAG to rebuild
- commercial platform
- customer touchpoints
IAG Nexus: identified key customer experiences
- Personalised omni-channel retailing
- Customer hub (central place to manage profile)
- Travel Companion (self-servicing)
IAG Nexus: key features identified
Smart offers (bundling, pricing, new/ext content)
Attribute shopping
Interline
Single customer record
Data
IB specificities in IAG NGA RFP
IB wants to keep their shopping
Target date for SWA RMS decision
2Q23
EK promotion management RFI: Ludwig first proposal
- Shopping with FP when PC in input (otherwise EK shopping): then we push OfferID to EK
- Pricing: EK pricing calls us w/ OfferID
- No RES/TKT layer (unlike NAC)
- OfferID useful for feed to come back to us and count quotas
WS RFP
NDC + AAM for 2023
Then expand AAM to DIG in 2024
What is needed by ATC in standalone (not even NAC)
- OfferID
- Ticket (retrieved by TKT from external PSS via TKTREQ)
What is needed by ATC in standalone (not even NAC)
- OfferID
- Ticket (retrieved by TKT from external PSS via TKTREQ)
NZ uses QPX
For shopping for Star Alliance Redemption (NZ and partner flights)
NZ shopping & pricing RFP 2 phases
- Day 1:
- Redemption shopping/pricing for Star Alliance
- Pricing for Call Centre INT only
- Ancillaries
- Day 2:
- Pricing for Call Centre DOM
- Shopping for Digital
- Servicing, Promocode, Ancillary for commercial
NZ shopping & pricing RFP: why WBS and not DC
1) Cannot do pricing w/o OfferID and Day 1 is without shopping
2) No standalone ATC in DAPI: requires Order
NZ shopping & pricing RFP: what is considered as standard implem
Flex + Instant
Award Converter
Promocode
The rest is NOT standard: fare quote, ATC and AAS
NZ shopping & pricing RFP: what does ATC require in WBS and DC
WBS: Booking details + TKT + OfferID
DC: Order + TKT + OfferID
NZ shopping & pricing RFP: why position DC rather than WBS
- Preferred channel of NGA transfo
- Evolutive product
- Better if NZ want s to migrate .com
- More accessible to developers than WBS
NZ shopping & pricing RFP: SAR (Star Alliance Redemption) availability solution
Polling for (all?) airlines
NZ shopping & pricing RFP: why PAOREQ conversion is not sized py APA (API) team
They only do EDI/XML not EDI/JSON so has to be done directly by APE
NZ shopping & pricing RFP: DC ATC standalone w/o Order
Was done on Redemption flow for AC Rewards, would be available in Commercial but needs to be tested (20md)
NZ shopping & pricing RFP: what Akshay had missed and how he saved it
Had missed ATC Shopper was in scope and the pb is its WBS doesn’t allow OfferID in input but we had a verb for AC allowing to query the PSS for the OfferID
Codes to refer to the new airline in Saudi Arabia
ASC Aviation Services Company that issued the RFP
RIA for Riyadh
KSA for Kingdom of SA
New Saudi Airlines: target for CUT
end 2024
SWA revenue increase with Ludwig
1 million per day (1.2-1.8%)
BA consulting company
BranchSpace will help them in their transfo
Solution for New Saudi airlines PSS
- Prime booking: Offer/Order on top of PSS (DCS, RevAcc…)
- Servicing: PSS + support service
Support positioned to New Saudi airlines as part of PSS RFP
Support to agents to handle servicing of complex cases so don’t have to know TST, TSM-P, etc. Maybe just RECLOC and TKT#
NZ Shopping/Pricing RFP: OfferID refers to
SSP Offer
NZ Shopping/Pricing RFP: what happens if NZ doesn’t have the OfferID and details
Backpricing
- Could be wrong if filing has changed
- Costly process so SSP doesn’t want it as the baseline process hence OfferID (would impact ATC perf)
BA Nexus: solution with an external Merchandising
Digital does the orchestration:
- shopping/pricing:
- integrate OfMS APIs
- Offer Integration -> External Pricing -> External Merchandising
- booking: DIG pushes adj to PSS
BA Nexus: big benefit of external Merchandising
Don’t need ATPCo
- Could even keep BA pricing engine
BA Nexus: benefit of our solution with an external Merchandising
1) Seamless in DIG and servicing
2) Would allow to add DP, interline AAS, AAM (in complement to FLX for missing use cases)
JL DP: what is easier to start w/: INT or DOM
INT:
- Difficult technologically: AeRE and Flex version
DOM:
- Difficult regulations
- Difficult competition data: NH doesn’t distribute on EDI
