Forced rotation is a way for the municipalities to prevent cars from staying too long in the same area.
In a park, the forced rotation policy will depend on the parking audience, the area, and the time and day.
When an end-user wants to park, StreetSmart can provide the ticket sales Application the maximum remaining parking time. the returned result depends on the expected parking location, the forced rotation policy, and the existing parking tickets of the vehicle for a pre-defined period for that location.
Remaining parking time is gained from the parkingRights response.
•GET /parkingRights
Forced rotation policy rules and already used parking time are taken into account to calculate the remaining parking time.
•GET /parkingOffers
Example:
In the down-town area, visitors can park for a maximum of 2 hours between 8:00 and 12:00, from Monday to Friday.
If the vehicle already has been parked for 1 hour. StreetSmart will return 1 hour of available remaining parking time.
|
If computedOffers are not taken into account by Ticket Sales Application (because, e.g., the project authorizes the Ticket Sales Application to use its own tariff engine), then please remember that several options may have to be supported by Ticket Sale Application: ●Free Time management: shift the start time of the paid period relative to configuration received in ParkingOffer (residualFreeTime, freeTimeStep, freeTimeCombinationMode, freeTimeArea) and choice of end-user ●Forced Rotation management: limit the end time of a parking ticket relative to configuration received in ParkingOffer (maxEndTime, forcedRotationArea) and choice of end-user ●Active ticket management: shift the start time of Parking ticket relative to parkingContract.ticketDeliveryStrategy and existing active ticket of same type. Of course, these 3 examples of features that have an impact on the tariff computation are optional and each city is free to consider it as a requirement or not. |
