Please enable JavaScript to view this site.

PRD_IHE_001_Implementation helper for Points of Sale 2.4

Navigation: » No topics above this level «

Parking ticket products

 Scroll Prev Top Next More

StreetSmart supports 3 kinds of tickets: New ticket, Ticket extension, and Ticket stop.

For details see the schema ParkingTicketProduct

The availability of these tickets depends on several criteria:

•The parking location can be limited to specific parking audiences. E.g., residents only, electric vehicles only ...

•The park can be configured to not allow extending or stopping a ticket, or even starting a new ticket when there is an ongoing one.

•The park can implement forced rotation allowing the parking audience to only park for a specific maximum number of hours during a pre-defined period in an area

The type of parking tickets a ticket sales Application can offer to an end-user can be retrieved with a GET /parkingOffers (cf. Ref.01) request to StreetSmart

 

PRD_IH~1_img3

On StreetSmart, a parking ticket can be changed:

Its end-date and amount can change depending on the requested actions, extending or stopping a ticket.

 

PRD_IH~1_img3

The Ticket Sales Application must send in the correct attributes fitting the request to send to the ParkingTicketProduct class.

Mandatory attributes

•park: URI of park for the project

•licensePlate: As license plates can be the same in different regions/countries, use the correct attribute; plate, plateRegion, or plateCountry.
Non alphanumerical characters will be removed from plate field by StreetSmart when storing the information.

•startTime: datetime in ISO8601 format. See Ref.03
[-]YYYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]
Do not use milliseconds.
Use "Z" to specify a time zone: Z(+|-)hh:mm other than UTC

•endTime: datetime in ISO8601 format. See startTime for the format.
The value must be later than the startTime.

•duration: duration in ISO8601 format.
Must be equal to endTime - startTime

•paidDuration: duration of parking corresponding to paid amount, in ISO8601 format.

•freeDuration: duration of free parking in ISO8601 format.
Free parking corresponds to a credit of parking time that can be offered to the end-user. This duration will decrease any remaining free time for next offers.

•paidAndFreeDuration: duration in ISO8601 format.
The sum of paidDuration and freeDuration. If the duration - paidAndFreeDuration is greater than zero (0), this means that the duration includes some non-paying periods e.g. due to tariff.

•parkingAmount: amount paid for parking in main currency. For example, 2.25 for 2.25 €.

•parkingTaxAmount: Tax part of parkingAmount in the main currency. For example, 0.50 for 0.50 €.

•serviceFeeAmount: an additional amount paid for delivered services linked to parking ticket delivery

•serviceFeeTaxAmount: Tax part of serviceFeeAmount amount

•currency: ISO 4217 3-character currency code (may be extracted from Park resource). See Ref.04

•parkingAudience: URI of parkingAudience (may be found in selected ParkingContract)

•tariffArea: URI of tariffArea (may be found in selected ParkingContract)

•validityArea: array of URI of validity Areas (may be found in selected ParkingContract)

Optional attributes

•freetimeArea: URI of freetimeArea (may be found in selected ParkingContract). It is mandatory to fill it when freeTime is used

•forcedRotationArea : URI of forcedrotationArea (may be found in selected ParkingContract)  It is mandatory to fill it when forcedRotation is used

•parkingSpace: reference to parkingSpace.  It is recommended to fill it when a payBySpace mode is used

•productID: reference to selected parkingOffer; We recommend to copy the value of attribute sp:category of ParkingOffer selected by the end-user. This attribute is to be treated as a mandatory attribute. The value cannot be one due to compatibility constraint.

•parkingContract: URI of selected parkingContract. We recommend to fill this new attribute to have a clear link to the previous contract used. As this is a new optional attribute, we continue to ask that Ticket Sales Application fills the parkingAudience attribute and all URI of Areas (for compatibility reasons). Filling this attribute is a way for the Ticket Sales Application to propose more precise the valid options to the end-user.

•tariffModifier: list of TariffModifier object. For each, only @id is required. When tariffModifier is part of the parkingOffer retrieved from GET /parkingRights response and applied by the sale application, it must be set in the ParkingTicket product (new, extend, stop).