NGLudwig - Architecture Flashcards
Modularity at which levels?
Component, module, service
Simplification related to DCS
No more RES/DCS windows constraints as all on same paradigm
Data domains in Offer Management (3)
Offer data domain
Product data domain
Stock data domain
OfferSet vs Offer vs OfferItem vs ServiceItem
OfferSet: set of offers returned for a request
Offer & OfferItem are sellable: OfferItem seems to be the real one /!\
ServiceItem is deliverable and linked to the Product Data Domain
Below ServiceItem
ServiceItemExecution: additional info for delivery not intrinsic to the product
Data domain related to Product Data Domain downstream (1) and correspondance
Delivery Data Domain with “Operational Product” matching Product Instance
Hierarchy of Product Data Domain and example for lounge
Product Definition (metadata)
>
Product Class (template) - slot at the lounge (across the year)
>
Product Instance (deliverable) - slot for a given day
Data domain related to Offer Data Domain towards touchpoints
Cart Data Domain: cart contains Offer Items
Data Domains: correspondance across Offer, Product and Stock Data Domains
OfferServiceItem <-> Product Instance <-> Stock Item AND Booking
The 3 states of an Offer and details
- Proposed (result of shopping)
- Selected (result of pricing, guarantees price+INV. Also returns new offers for upsell options)
- Confirmed (contracted)
How are new products automatically created
“Create Product Instance” wakes up every day to create new instances in, say, 365 days
Lounge example: stock unit vs booking
Stock unit = 30min span
Booking = 6 consecutive 30min units
SV lounge part useful for NGL
Creation of lounge product and stock keeper per slot
One of the technological simplifications of the retailing transformation
Get rid of fragmented, siloed systems with hundreds of components, uncorrelated data, etc.
