I 92 Harmonize booking of ancillaries - UnionInternationalCheminsdeFer/OSDM GitHub Wiki
I-92: Harmonize the Booking of Ancillaries
Description
In OSDM we have two ways of booking ancillaries, firstly, via passanger type and secondly via
Owner
- Odile Angeras (Amadeus)
- Clemens Gantert (DB)
- Patrick Heuguet (UIC)
- Roland Klapwik (Sqills)
- Angelo Farruggia (SBB)
Business Value
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.
Business Outcomes
The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.
Less implementation and testing efforts needed.
Leading Indicators
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.
Nonfunctional Requirements
- The reservation flow of the underlying H/H system needs to be supported.
- Compatibility with OSDM Offline Model
Specification Effort
MIDDLE
Initial Analysis
Amadeus Vision
Approach via Passenger Type
- see Passenger Type
Approach via Product Type
- Product type does not exist in the OSDM; proposed by I-93: Product types.
Approach of the Airline World
Scenarios
-
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
- 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 non/optional/required reservationCAR
/MOTOCYCLE
/TRAILER
: Mandatory Ancillary with required reservation. Modeled asTransportable
, needs thinking.LUGGAGE
, Meal, ...: Ancillary onlyWHEELCHAIR
,PRM
,ACCOMP_PRM
,ACCOMP_DOG
: modelling needed, overlaps withPassenger.prmNeeds
.FAMILY_CHILD
- How does the booking look like?
- On open systems we can have two independent bookings.
- How to request?
-
Input from Roland
{
"offerSearchCriteria": {
"ancillaries": [
{
"type": "BIKE",
"passenger": "abc",
"amount": 2
}
]
},
"passengers": [
"externalRef": "abc",
"type": "PERSON"
]
}