-
Notifications
You must be signed in to change notification settings - Fork 26
I 6 Add support for new mobility services
- Support booking of on demand services or linking with MAAS APIs
- Support of account based travel
- UIC D2D project
- Andreas Schlapbach
- Clemens Gantert
- Sales including the last mile via on demand services.
The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.
To do
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 (NFRs) associated with the epic.
To do
Many unknowns including non-technical questions and unclear scope (TOMP integrating a MAAS standard versus a MAAS standard integrating TOMP / products / services).
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.
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 (post payment process if out-of-scope of current OSDM scope)
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.
Can OSDM be used to retrieve Offers and bookings that can fed into a MaaS API (e.g. TOMP)?
Two variations
- integrate TOMP content to OSDM so that it can be sold using OSDM
- integrate OSDM content to TOMP so that it can be sold using TOMP
OSDM Wiki