Multiple credentials
Use the plate, card, long-range tag or QR code that fits each arrival.
Access control
Parking access control for vehicles and controlled zones
Parking access control checks a vehicle’s identifier against the site’s current permissions before a configured entrance allows passage. Lexoh connects plates, RFID or UHF credentials, QR codes, barriers and assistance with the zones, schedules and exceptions agreed for the parking operation.
Operating design
Apply one access policy across multiple technologies
Choose the identification method around the arrival: a registered plate, a long-range tag, a deliberately presented card or a temporary QR code. Then define what the accepted or rejected result should do at the lane. The barrier installation must coordinate detection and safe movement. Where people also enter buildings, compare the separate requirements of building and site access control rather than treating a vehicle lane as a door. For permit administration, payment records and the daily work across sites, explore the parking management system.
Zones and lanes
Limit each right to the entrances and spaces it actually needs.
Schedules
Apply regular calendars and approved exceptions.
Lane commands
Send the decision to the barriers and controllers integrated into the project.
Supervision
Give staff the access-event context they need to investigate a refusal or assist a driver.
Room to evolve
Plan new users, lanes or technologies around the existing permission model, then verify compatibility and retest affected rules.
Decision path
An access decision in five steps
Identify the vehicle or credential, check its current access permissions, send the permitted command and record the result. Exceptions need an authorized person or alternate method; the barrier should not open solely because an identifier was read.
Read workflow steps
- Present
Plate, RFID, UHF or QR
- Identify
Associated account or right
- Evaluate
Zone, time and status
- Command
Action sent to the lane
- Record
Event visible to staff
The physical decision remains visible in its operational context.
View actual Lexoh interface
On site with Lexoh
A lane built around the traffic path
Reader position, stopping distance, barrier visibility, detection and safety determine the real experience. Lexoh designs those field elements with the software rules that apply each right.
For a vehicle-tag project, the Lexoh UHF9DBI is a 902–928 MHz reader with a 9–25 V DC supply and an IP65 enclosure. Its specified reading distance is up to 15 m under suitable conditions. Confirm the tag, mounting and read zone with real vehicles, including the adjacent lane. UHF9DBI specification (French PDF).
What this changes in the project
Equipment placement, civil work, communications and operating procedures are validated together before commissioning.
Turnkey delivery
What turnkey delivery covers
Lexoh coordinates the field work, platform rules, testing and operating handoff as one project.
- 01Inventory user groups and journeys
- 02Survey lanes, distances and available services
- 03Select credentials and readers
- 04Install barriers, controllers and communications
- 05Configure rules and exception procedures
- 06Test with vehicles and train staff
Operating contexts
Operating contexts this design supports
Businesses
Employee, visitor and supplier access with distinct schedules.
Residential sites
Resident rights, secondary vehicles and temporary guests.
Campuses
Several populations and zones under one policy.
Industrial sites
Dedicated lanes and role-limited supplier access.
Before specifications
Questions to settle before specifications
What should arrival feel like?
Free-flow, short-range or interactive journeys call for different credentials.
How does the lane behave during an incident?
Agree on manual operation, assistance and safety procedures.
Which zones must stay separate?
Structure rights around operating need.
Who administers changes?
Assign roles that can act without unnecessary privileges.
Compare the operating choices
Compare credentials by the arrival they must support
Compare the methods with the real user groups and lane layout. RFID means radio-frequency identification; UHF refers here to the ultra-high-frequency radio tags used for vehicles. After a read, the configured permission determines access. Confirm the credential media accepted by each device.
| Method | Useful planning context | What to confirm |
|---|---|---|
| Plate recognition | Recurring vehicles or visitors whose plates are registered | Capture conditions, plate changes, correct lane association and an unread-plate procedure |
| UHF vehicle tag | A recurring vehicle with an assigned tag | Reader/tag compatibility, placement, read zone and adjacent-lane checks |
| Presented RFID card | A deliberate interaction with a reader | Supported credential technology, driver reach, issue/revoke procedure and lost cards |
| QR code | A time-limited or issued code where supported | Issuer, validity, paper/phone presentation, scanner compatibility and refusal procedure |
Illustrative employee choice
Compare a registered plate with an assigned tag using the actual approach and vehicle changes. Select the method demonstrated in the lane, and document a supported alternative when reading fails.
Illustrative visitor choice
If the site issues a temporary code, verify who creates it, how the visitor receives it and when it expires. A trailer also changes stopping and turning geometry; the credential choice does not resolve those physical constraints.
Questions asked before a project
Clear answers about scope, operation and integration.
Plates work for touchless arrival, UHF for long-range reads, cards for deliberate presentation and QR for temporary rights. They can coexist.
Sometimes. Command interfaces, safety devices, detection and mechanical condition must be reviewed first.
Yes. They can be limited by time, calendar, site and zone.
They can use a preregistered plate, QR code, intercom or another journey defined for the site.
Both apply permissions, but a vehicle lane must account for approach geometry, queues, vehicle detection and barrier movement. Building entrances involve their own door hardware and operating requirements. A project may coordinate the user and site context while retaining distinct rights and control behavior for each entrance.
Lexoh uses a hybrid architecture: cloud management plus an offline mode, with a mesh network that lets site devices communicate without internet. Power loss is a separate case: the project defines backup power, barrier response and manual assistance. The commissioning plan verifies the configured lane functions and recovery procedures.
Review approach width, turning space, the driver’s reach to a reader and the full vehicle-and-trailer path through the controlled area. The installer must assess detection coverage and barrier behaviour for those movements, rather than relying only on passenger-car tests. Include the vehicles actually expected on site and document any separate route or assisted procedure needed for exceptional movements.
Agree on the work sequence, temporary circulation, user notices and the point at which each new access method becomes authoritative. Keep responsibility for the existing and new equipment clear during changeover. Before reopening a lane, the installation team should verify the agreed controls, detection and operating procedures. Plan a supported fallback and correction process if acceptance checks expose a problem.
Document the affected entrances, user groups, start and end times, and the person authorized to approve the change. Check how the temporary rule interacts with normal permits and restricted areas before applying it. Test representative allowed and refused entries, brief the assistance team and confirm the return to normal operation. A temporary event should not silently leave broader permissions active afterward.
It is the combination of an identifier (plate, RFID card, UHF tag or QR code), a reader at the lane, a rule engine that decides whether that identifier may enter this zone at this time, and an actuator such as a barrier. Lexoh adds the cloud platform where rights, events, video and payments are managed together.
Costs scale with lanes, credentials, civil work and software scope. The appropriate reader depends on the users and lane; adding payment, multiple zones or several sites changes equipment and configuration. The access control cost guide explains each cost block and the questions to ask each supplier.
Review lane geometry, vehicle detection, the supported barrier sequence and staff response with a qualified installer. Anti-passback can restrict repeated use of a credential; it does not physically stop a second vehicle following the first. Video can support review. Required safety devices and safe barrier movement remain essential; faster closing is not a substitute for an approved lane design.
Lexoh uses a hybrid architecture: cloud management through Lexoh Security Center and an offline mode with local device communication over a mesh network. Compare the responsibilities for remote administration, network access, power, maintenance and recovery. The project design defines the equipment and access rules for each lane; commissioning tests operation during an internet interruption and after reconnection. The cloud vs on-premise guide explains the responsibilities to compare.
Yes. Sites, zones and lanes are organised under one account, with rights that can be limited to one site or shared across all of them. Operators can review the sites their role permits them to access in one dashboard.
The schedule depends on equipment availability, approvals, civil and electrical work, integration, testing and staff training. A prepared lane and a site requiring excavation have different timelines. Agree on milestones, temporary traffic arrangements and acceptance checks in the project schedule before committing to an opening date.
Winter conditions can obscure the plate or reduce image quality. Camera position, lighting, capture distance and plate condition affect the result, so test representative conditions at the actual lane. For recurring users, compare an assigned UHF tag with plate recognition and document a supported alternative or assistance path for failed reads. A seasonal operating schedule alone does not establish that LPR is sufficient.
Design a lane that applies your rules
Tell us about the users, traffic and existing equipment before selecting the credential technology.