I 65 Support for Remise à Disposition - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

I-65: Support for Remise à Disposition

Description

Add support for Remise à Disposition (RAD) in OSDM.

We need two steps for this process

• refund done at the station (not the travel agency) calculating the refund fee and releasing booked places without accounting / payment
• refund at the agency for the payment and to trigger the accounting

Owner

• Sverker Östman (SJ)
• Roland Klapwik (Sqills)
• Ralf Bayer (DB)

Business Value

For customers

who want to return the ticket and get it reimbursed later

the support for this process

is an addition of a refund state

that denotes a refund to be reimbursed later

unlike current solution

our solution supports this process.

Business Outcomes

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

The Remise a disposition process suppored by various railways is supported by the OSDM specification.

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.

As INITIATED is not an end state, we need tp define a cleanup mechanism.

Specification Effort

To estimate by technical experts

SMALL

Initial Analysis

We need two steps for this process

• refund done at the station (not the travel agency) calculating the refund fee and releasing booked places without accounting / payment
• refund at the agency for the payment and to trigger the accounting

We need to extend the refund state model:

• Currently: INITIATED --> CONFIRMED
• New: INITIATED --> ACCEPTED (booking is “refunded” but payment and accounting are pending, maybe there is a better word) --> CONFIRMED To go from INITIATED to ACCEPTED we can use the existing PATCH with the new state.