I 67 Split a Booking per Passenger - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

I-67: Split a Booking per Passenger

Description

This is an improvement related to the way travel agencies are working in SilverRails current sales application. Samtrafiken and Silverrail had some meetings and agreed that we probably not need this improvement in the OSDM standard. We put this improvement on hold for now and it is not necessary for PI-7.

Owner

  • Silverrail
  • Samtrafiken (Sverker Östman)
  • Amadeus (Koffi )

Business Value

  • Split at Pre booking step In a multi passenger booking, the travel agent requests to have a PNR per passenger in order to invoice each passenger separately. However, there is one booking request because the travel agent want all the passengers to be seated together.

  • Split in granular aftersales In some IMS (Inventory Management System), the booking needs to be homogeneous. Meaning that all the passenger must travel on all the segment. for such systems, the only way to perform a granular after sales is to extract from the parent booking the passenger(s) affected by the after sale operation. Granular after sales refers to scenario in which the travel agent wishes to refund or exchange a subset of passenger ticket in a multi passenger booking.

If the provider doesn’t support non homogenous booking (all the passengers are not on all the segment) then we need to split the PNR. If the provider does support non homogenous booking, there is no need to split.

Business Outcomes

The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.

The implementation of booking split at pre booking time will ensure that tarvel agent on the swedish market will still have the functionality after the migration.

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.

To do

Nonfunctional Requirements

Nonfunctional requirements (NFRs) associated with the epic.

To do

Specification Effort

Medium

To implement to split at pre booking time we can have a flag in the pre booking request that a booking per passenger should be created. The explicit request in a granular after sales scenario need a new endpoint that will take in input the parent booking reference and the references of the passenger the agent want to add to a new booking. In a explicit split scenario the parent booking reference is added to the child booking and vice versa.

Implementation

New end point POST bookings-split has been added.