Badge-free identification
Use the plate as an identifier for a lower-friction arrival.
Vehicle identification
License plate recognition for parking and access control
License plate recognition (LPR, also called ANPR) reads plate characters from a camera image and compares the result with the parking rules configured for that vehicle. Lexoh plans the capture point, permit or visitor match, lane command and assistance path for reads that cannot be confirmed.
Touchless access
Plate-based permits
Event history
Site and schedule rules
Capture design
Operating design
Reading quality starts well before the software
A readable plate is only the first step. The system must distinguish an authorized vehicle from an expired permit, an unexpected visitor or a changed registration. Camera angle, distance, speed, lighting and plate condition affect capture; the organization supplies the matching policy. Connect digital parking permits to the vehicle access workflow, and test both accepted and rejected journeys at the actual lane.
Permits and allow lists
Tie one or more plates to a period, site, zone or user category.
Real-time lane decision
Compare the read with current access rules before sending an action.
Operational context
Keep the event and result available when staff investigate a denied entry.
Multi-site rules
Manage shared policies alongside local site exceptions.
Fallback method
Combine LPR with QR, RFID or an intercom when the operation calls for it.
Decision path
From plate image to access decision
Capture and recognition establish the proposed identifier; authorization checks whether that identifier has a current right for this site, zone and time. Keep those results separate so staff can diagnose an unreadable plate without mistaking it for an expired permit.
Read workflow steps
- Capture
Image suited to the lane
- Read
Plate characters
- Normalize
Format matched to data
- Decide
Zone, time and status
- Record
Result available to staff
The physical decision remains visible in its operational context.
View actual Lexoh interface
On site with Lexoh
A camera designed into the lane
The capture position must work with the stopping point, vehicle detection, barrier and other readers. Designing them together gives the plate event useful context and leaves room for a second access method.
What this changes in the project
Equipment placement, civil work, communications and operating procedures are validated together before commissioning.
Turnkey delivery
A complete LPR deployment
Lexoh reviews traffic and access rules before finalizing camera placement and platform configuration.
- 01Survey traffic and the capture point
- 02Review distance, angle and lighting
- 03Install cameras and communications
- 04Prepare authorized plate data
- 05Configure schedules and exceptions
- 06Test day, night and real operating cases
Operating contexts
Where plate recognition is most useful
Employees and subscribers
A fluid arrival based on a registered vehicle.
Residents
Authorized vehicles and replacements managed under the site policy.
Preregistered visitors
Temporary rights attached to the plate supplied before arrival.
Multi-site organizations
Consistent policy with rights limited to the appropriate locations.
Before specifications
Decisions that shape reliability
Does the lane create a stable capture point?
A predictable vehicle path and appropriate speed help produce a usable image.
How are dirty or obscured plates handled?
A secondary method and assistance procedure keep the operation moving.
Who can review plate events?
Roles, retention and use should follow the organization’s approved policies.
Can a permit contain multiple plates?
Define replacement, simultaneous-use and duplicate rules in advance.
Questions asked before a project
Clear answers about scope, operation and integration.
Not always. RFID, QR or intercom assistance can still cover exceptions, visitors or situations where a plate is unavailable.
A system can be designed for varied lighting, but results depend on the camera, placement, scene and testing at the actual site.
Yes. The permit can contain the plate plus the site, zone and schedule rules that apply to it.
The organization should define purpose, access roles, retention and internal procedures; the solution is configured around those requirements.
No. Plate recognition identifies the registration shown in an image. Vehicle detection establishes arrival, presence or passage for the lane controls. The barrier design must separately address detection, safety devices and closing behavior; a readable plate does not by itself establish that the lane is clear.
Use representative vehicles and plates at the planned capture position, in daytime and after dark. Test valid, expired, unknown and replacement-vehicle records as well as an unreadable plate and the assistance path. Agree on the sample, acceptable results and correction process before commissioning. A universal accuracy percentage would not describe every lane.
An authorized administrator should verify the user and enter the replacement plate for the permitted period and zones. Decide whether the original vehicle keeps its right during that period or must be suspended. Test the updated record at the intended entrance and remove the temporary authorization when it ends. The procedure should prevent a short vehicle substitution from creating an indefinite additional right.
Review the capture area, vehicle stopping position and association between each camera and its lane controller. Test simultaneous approaches so a plate read in one lane is not treated as permission for the neighbouring lane. Include turning vehicles and queues in the site review. Camera placement and supported configuration must be validated against the actual geometry before approving the design.
Separate a missing or unclear image from a readable plate that lacks permission. Review the available image and event context, then inspect the camera view, lighting, lens condition, stopping position and obstructions. Record the conditions in which failures recur so the installer can investigate a pattern. Use the approved secondary credential or assistance process while the cause is being addressed.
Validate the lane before selecting the camera
We can review traffic, capture conditions and access rules to define a suitable LPR architecture.