Choose the parking workflow before choosing the terminal. A ticket-based lane issues a ticket or uses a card at entry, then validates the relevant credential at exit. An ANPR lane uses a vehicle's license plate to identify the parking session. Either approach needs a defined process for payment, exit and exceptions.
Map the driver's route
| Decision | What to confirm |
|---|---|
| Entry | Will the driver take a ticket, present a card or have the plate read? |
| Payment | Is parking free, paid at a self-service kiosk before exit or paid at the exit? |
| Exit | What will the system verify before it signals the barrier to open? |
| Exceptions | Who handles an unread plate, a lost ticket or a payment the system cannot match? |
| Integration | Which terminals, controllers or software are already on site, and which will be supplied with the project? |
Compare the equipment around the lane
For a ticket workflow, the SXK-820 documentation shows how entry and exit terminals fit into a system with a barrier, parking software and an optional separate payment point, depending on the configuration. Plan where a driver can stop to take or present a ticket and where operators will handle exceptions.
For an ANPR workflow, the SXK-LPR100 family provides integrated parking terminals. Share the countries whose plates the system needs to read, the lane approach and photos of the proposed mounting position. Confirm how the terminal will pass a vehicle record to the selected software and how that software will handle payment and issue the exit signal.
Prepare a request for a system quote
List the number of spaces and the entry and exit lanes. Add the proposed payment location, whether drivers need tickets, the existing software and your budget range. A site plan with the intended barrier and terminal positions makes the request easier to review. If you only need hardware for an existing system, include the interface requirements for that equipment.
Compare the parking entry and payment options or prepare a project brief.
