-
Notifications
You must be signed in to change notification settings - Fork 26
I 92 Harmonize booking of ancillaries
In OSDM we have two ways of booking ancillaries, firstly, via passanger type and secondly via
- Odile Angeras (Amadeus)
- Clemens Gantert (DB)
- Patrick Heuguet (UIC)
- Roland Klapwik (Sqills)
- Angelo Farruggia (SBB)
For developers
who need to buy ancillaries
the harmonization
is a benefits
that facilitates the implementation
unlike the current situation
our solution harmonizes the two worlds.
The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.
Less implementation and testing efforts needed.
The early measures that will help predict the business outcome hypothesis. For more on this topic, see the Innovation Accounting advanced topic article.
Implementations are based on the harmonized approach.
The reservation flow of the underlying H/H system needs to be supported.
MIDDLE
- see Passenger Type
- todo
-
Scenario 1 Passenger 1 Bike
Existing Mode
- 1 PassengerType Adult + 1 PassengerType Bike
New Mode
- 1 PassengerType Adult + 1 Ancillary Product of type Bike
-
Scenario 1 Bike
Existing Mode
- 1 PassengerType Bike
New Mode
- 1 PassengerType Adult + 1 Ancillary Product of type Bike Question who owns the Bike?
-
Scenario Bike is distance Bike
-
Topics to Solve
- How to request?
- Define Passengers:
PERSON
,PERSON_WITH_WHEELCHAIR
- Map Non Passenger Types to Product Categories (see Airline Taxonomy)
- Add possibility to request more than one ancillary, needs improvement on
OfferSearchCriteria
- Cluster products --> improve products to have this meta information (add
ProductTag
,...)
- Define Passengers:
- How does the offer look like?
-
BIKE
/DOG
/PET
/PRAM
: Mandatory Ancillary with optional/required reservation -
MEAL
/...: Ancillary only -
WHEELCHAIR
: modelling needed
-
- How does the booking look like?
- On open systems we can have two bookings.
- How to request?
OSDM Wiki