I 16 Add support to sell non journey based products - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

Add support to sell non-journey based products such as day passes or reduction cards.

• Meyer Sören / Dorsch Jessica (DB)
• Mund Christian / Eder Sabine (ÖBB)
• Alexander Gellner / Schlapbach Andreas (SBB)

For customers

who want to buy passes or reduction cards

the selling of non-journey based products

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.

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

• Touristic passes are an important product for e.g. Swiss tourism.

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

• A day pass is sold in 2021.

Nonfunctional requirements (NFRs) associated with the epic.

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

Day Pass, e.g.:

• Germany: Baden-Würtenberg Ticket, Bahncard 100, ...
• Switzerland: One-day passes

Reduction card, e.g.

• Germany: BahnCard 25/50,...
• France: Carte Jeune/Carte Weekend/Carte Senior/Carte Enfant/Carte et Abonnement Fréquence/Forfait
• Austria: ÖBB Vorteilscard,...
• Switzerland: Swiss Travel Pass, Swiss Travel Pass Flex, Swiss Half Fare Card, Swiss Family Card

• UC 1: Reduction cards are included in the price calculation for a trip.

  A customer adds its reduction cards which are taking into account in the offer reply.

• UC 2: For a journey, non-journey based product offers are returned additionally.

  1. A customer wants to travel from A to B.
  2. Additionally to journey based offers the customer receives offers for non-journey based products of type ‘day pass’ as well.
  3. The customer then buys such a non-journey based product.

  Thus, this behavior can be understood as day pass cross selling.

• UC 3: Customer wants to buy a non-journey based product.

  • Use Case Scenario 3a:

    A customer is offered a non journey based product in the offering phase.

  • Use Case Scenario 3b:

    A customer wants to buy a dedicated product (e.g. Weekend Carte / STS Card).

  • Use Case Scenario 3c:

    A customer wants to buy a certain category of products (e.g., reduction card / daily pass, ...).

  • Use Case Scenario 3d:

    A rail agent wants to sell a dedicated product to a costumer.

  To support these scenarios, a product catalogue is needed. It should have the following properties:

  • Product identifier and description
  • Search tags
  • Necessary and mandatory properties including their types. E.g.: Validity.
  • Products and products category can be searched and requested.
  • The product catalogue can be accessed dynamically, i.e. once per day and imported into a distribution system.
  • This functionality most be exposed by each RSP which then can be exposed by OSSM.

• review the existing /offers-collection/ resource for completeness.
• add a resource to OSDM for products: /products/?filter=<criteria>
• update product with missing attributes

The following use case is related but needs to be addressed in a different improvement:

• UC 4: Up-selling a non-journey based product to a journey-based offer.

  1. A customer wants to travel from A to B.
  2. Additionally to journey based offers the customer receives offers for non-journey based products of type ‘reduction card’ as well.
  3. If bought, the reduction is applied to the journey-based offers.

  Thus, this behavior can be understood as reduction card cross selling.

Merged: https://github.com/UnionInternationalCheminsdeFer/OSDM/pull/178/