I 59 Support for Swedish Market Part II - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

I-59 Support for Swedish Market - Part II

Description

Fix functional gaps for the Swedish market.

Must have:

• Adjustments to support BoB standard (non-booked tickets) --> TODO: add Improvement I-66
• Possibility to add ancillary to a booking - patch booking supports
• Indication of VAT exemption (covered by tripSpecification)
• "Remise a disposition (RAD)" --> Improvement I-65
• Possibility to provide age or DoB, depending on what customer has entered. To ensure fake DoB is not presented on fulfillment
• Refund to voucher (for rebookable tickets)

Could have:

• Split bookings --> TODO: add Improvement I-67
• (additional)customer details for non-trip sales?
• Additional parameters for booking search - e.g. possibility to search bookings by passenger details
• Ticket validation (Ticket Validation is part of UIC IRS 90918-4 and suported by UIC ETCD plattform. Specifications are available at UIC. please contact Clemens Gantert or David Sarfatti)
• Additional support for multi-ride/passes (right to check validity or see remaining rides left)
• Seatmap enhancements (potential)

Owner

• Stina Carlstedt (SJ)
• Sverker Östman (Samtrafiken)

Business Value

For customers

who do something

the solution

is a something – the ‘how’

that provides this value

unlike competitor, current solution or non-existing solution

our solution does something better — the ‘why’.

Business Outcomes

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

To do

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

add pagination support

/bookings/search

BookingSearchParameter:
  type: object
  description: >-
    parameter to be used to search for a booking. Contains personal data. 
    For a search via personal data an exact match of all elements 
    
    In case a ticket holder is indicated the parameter must match the ticket holder. 
    TODO - legal check by CIT
  properties:
    passengerFirstName:
      type: string
      description: First name of a passenger in the booking.      
    passengerLastName:
      type: string
      description: Last name of a passenger in the booking.
    passengerDateOfBirth:
      type: string
      format: date
      description: Date of birth of a passenger in the booking.
    bookingReference:
      type: string
      format: date
      description: Human-readable booking reference for the booking, e.g. PNR.
    fulfillmentReference:
      type: string
      description: Human-readable fulfillment reference for the booking, e.g. ticket number.
    travelDateBegin:
      type: string
      format: date-time
      description: Begin date for the travel date range to search.
    travelDateEnd:
      type: string
      format: date-time
      description: End date for the travel date range to search.
    origin: 
      $ref: '#/components/schemas/Place'
    destination:
      $ref: '#/components/schemas/Place'
    purchaseDateBegin:
      type: string
      format: date-time
      description: Begin date for the booking/purchase date range to search.
    purchaseDateEnd:
      type: string
      format: date-time
      description: End date for the booking/purchase date range to search.
    purchaserFirstName:
      type: string
      description: First name of the purchaser in the booking.      
    purchaserLastName:
      type: string
      description: Last name of the purchaser in the booking.
    purchaserEmail:
      type: string
      description: Email address of the purchaser in the booking.
    purchaserPhoneNumber:
      type: string
      description: Phone number of the purchaser in the booking.
    passengerEmail:
      type: string
      description: Email address of a passenger in the booking.
    passengerPhoneNumber:
      type: string
      description: Phone number of a passenger in the booking.
    publishedServiceName
      type: string
      description: Line name or service description as known to the public.
    travelAgencyName
      type: string
      description: Name of the travel agency (retailer organization) that created the booking.
    agentToolUserName
      type: string
      description: Name of the travel agency employee who created the booking.
    salesChannel
      type: string
      description: enum:"AGENT_TOOL", "TICKET_VENDING_MACHINE", ...
    paymentStatus
      type: string
      description: enum:"ALL", "PAID", "UNPAID"
    corporateCode
      type: string
      description: Corporate code issued by the referenced company.
    travelPassReference
      type: string
      description: Reference to the travel pass (multi-journey pass) used for the booking.