How do I implement a shared car operator
home > Modalities > Shared car
Q: How to implement a Shared-car operator?
A: I'll list them per module:
The planning module is pretty similar to the other modalities. A planning is posted, and - dependent on the time to depart, it can return OR specific assets (when it's in the near future) OR assetTypes.
The booking can be done for the asset or asset type, using the normal process in the TOMP-API: posting a booking (which returns a booking in PENDING state) and committing it.
Whenever an asset type is booked, the asset will be assigned after the booking process, but before the trip starts. (/legs/{id}/events – ASSIGN_ASSET)
The car can be opened using Bluetooth or over the internet (/legs/{id}/events – SET_IN_USE).
Locking the car at a location that’s not a valid end location (e.g. not at a hub (=station) or area), will pause the usage. (/legs/{id}/events – FINISH returns error => /legs/{id}/events – PAUSE called). When the car is opened again, the /legs/{id}/events – SET_IN_USE is called again.
Locked at a valid end location (/legs/{id}/events – FINISH) will end the leg.
