-
Notifications
You must be signed in to change notification settings - Fork 42
TOMP‐API v2.0 Functionalities
- serves both station-based and free-floating setups. Even dynamic setups.
- direct booking of assets on the street AND search for assets
- use GBFS's published vehicles
- book assets in the (near) future
- use deposits
- Purchase products, like monthly cards, subscriptions or multi-ride vouchers
- Usable with external route planners
- can be used to open locks of any kind.
- can be used to open lockers and chargers
- copes with helmets and helmet boxes
- start, stop, pause and resume trips
- deliver proof (photos) of correct parking
- facilitates any support scenario, even the replacement of the asset
- allows for adjusting the rental until the start of the trip
- reuse existing published data, like MDS policies: (no-)parking zones, speed limits, etc.
- offers functionalities for different payment methods
- charge different prices based on pause status
- request payment directly after the trip has finished
- serves both station-based, free-floating and round-trip setups.
- Search for offers, but also book a car on the street
- In case of offerings, adjust the offer (additional services, child seats, insurance, ..) and specify traveler's details (e.g. driver's license)
- Purchase the offer or adjusted package
- Purchase products, like monthly cards, subscriptions or multi-ride vouchers
- Usable with external route planners
- can be used to open garage doors
- start, stop, pause and resume trips
- deliver proof (photos) of correct parking
- custom functionality to operate the car, charging equipment or garage doors
- publish on-street and off-street parking locations
- reporting incidents, flat tires, etc
- request to extend the usage time
- request location of parked vehicle
- formalized process to replace the (broken) vehicle
- warn the traveler based on MDS policy-zones
- inform the traveler (time left, operational instructions)
- Report the balance
- Request immediate payment after the trip
- Redress options, like refunding
- Handling fines
- usable with route planners
- can be used with e.g. GTFS-OnDemand
- supports from full AVs to traditional taxis
- call-a-cab; instant booking
- specify connecting services, allowing to publish guarantees
- pickup / drop off locations
- specify luggage sizes and weights
- specify personal details, reduced mobility
- confirm after scheduling (and dispatching)
- report ETA till pick up point (incl. location)
- the driver/chauffeur controls the execution (not the traveler), and starts/stops the (leg of the) trip
- custom functions for AV
- Reporting no-show (of taxi & traveler)
- Unable to locate
- Fixed prices, corrections at the end
- Pay when finished
- Redress options, like refunds and compensations
- Offers With or without seat reservation
- Check-in/Check-out, Gate controlled, Be-in/Be-out, Check-in/Be-out
- Search for offers, modify the offered packages (additional services, personal details)
- Or directly purchase the offer
Introduction
- Roadmap
- Semantic versioning
- Use cases
- Changes per version
- Contribution
- Participants
Workflow
- Operator information
- Planning phase
- Booking phase
- Trip execution phase - start
- Trip execution phase - on route
- Trip execution phase - end
- Support
- Payment
Points of attention
- Modalities
- Specifying locations
- GDPR
Eco system
- Relations
Introduction
Scope of the TOMP-API
Versioning and releases
Process Flows
- Authentication
- Operator Information
- Privacy and Registration
- Planning Module
- Booking Module
- Trip Execution Module
- Payment Module
- Support Module
Meta-Information
Reference implementations
To-dos and risks
Technical Specifications
A1 List of terms and definitions
A2 Passenger characteristics dictionary
A3 APIs available on the transportation ecosystem
A4 Overview of the User stories
A5 Authors, Architects, collaborators and stakeholders involved
A6 Adoption and Implementation of the TOMP-API