I 6 Add support for new mobility services

I-6: Add Support for New Mobility Services

Description

• Support booking of on demand services or linking with MAAS APIs
• Support of account based travel

Owner

• UIC D2D project
• Andreas Schlapbach
• Clemens Gantert

Business Value

• Sales including the last mile via on demand services.

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: LARGE

Many unknowns including non-technical questions and unclear scope (TOMP integrating a MAAS standard versus a MAAS standard integrating TOMP / products / services).

Requirement Analysis:

Support of account based travel

The passenger is participating in a post payment scheme which overlaps with the trip requested via OSDM and wants an offer that takes this into account.

Support of On-Demand Services

The passenger wants an offer and a booking for an On-Demand Service provided in the trip. The On-Demand Service is priced at shopping time.

Support of On-Demand Services with pricing after use

The passenger wants an offer and a booking for an On-Demand Service provided in the trip. The On-Demand Service is partially or completely priced after use.

Support for Integration into a MaaS API (TOMP)

Can OSDM be used to retrieve Offers and bookings that can fed into a MaaS API (e.g. TOMP)?