I 27 Add support for group reservations - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

Description

Add support to sell group reservations.

Owner

  • Sören Meyer (DB)
  • Elisabeth Gilgen / Schlapbach Andreas (SBB)

Business Value

For customers

who want to reserve and buy group reservations

the selling of group reservation

is an additional service

that allows to offer and sale passes and reduction cards

unlike the current standard

our solution allows to distribute a new segment of products.

Business Outcomes

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

  • Group reservation are an important product for e.g. Swiss tourism.

Leading Indicators

The early measures that will help predict the business outcome hypothesis.

Nonfunctional Requirements

Nonfunctional requirements (NFRs) associated with the epic.

  • If the product catalog is large then pagination should be supported.

Need

We are currently revamping seat and group reservation in Switzerland. We want to position OSDM as the new distribution and carrier interface within public transport in Switzerland. We have multiple partners interested in implementing OSDM in Q2/2021. In order for them to adopt OSDM they however require the support of group reservation by the OSDM standard.

Initial Analysis

  • Billeto

    • Group pricing per default, one fulfillement for the whole group

  • Sqills

    • Customer: group leader (could but must not be a passenger).
    • Number of passengers steers whether group tarifs

  • DB:

    • Offer request can be sent even if train is not yet scheduled
    • Distinction between who picks up the tickets and the one who bought it

  • SBB

    • Offer request can be sent even if train is not prepared yet
    • Touristic scenario: Train's can be booked 1 year in advance, group leader get's informed a month in advance when the

  • Amadeus:

    • In air the booking horizon is one year. Extending the horizon to rail would be of great benefit.
    • Amadeus' booker is Sqills' customer

Impact on OSDM

  • Scope 1.3:

    • Decision: Name of the booking entity: booker.
    • Add roles to passenger or define a customer/booker (which is not part of passenger as he/she doesn't travel)

  • Scope 1.4:

    • Add new state to booking ("booking to be confirmed")
    • Implies confirmation mechanism, which confirms booking and sends fulfillement to customer/booker

Specification Effort: MIDDLE