LPR365: a plate observation is not an access permission
Design capture, policy, barrier control and exception handling separately.
Updated
Principle and limits
A recognition result contains an observed plate candidate and context. Access policy evaluates permitted lists, schedules, site rules and confidence handling. A barrier controller governs physical movement and safety inputs. These responsibilities must stay separate. The deployed LPR365 version, camera integration and controller must support the chosen path; recognition alone must not replace the safety system.
Worked example
A listed plate outside its permitted time may require denial or review even if recognition is correct. An unreadable plate requires the agreed alternative, such as intercom or operator verification. Test repeated approaches and two vehicles close together: duplicate suppression must not hide a second vehicle. No sample policy here establishes a site’s actual permission rules.
Installation and acceptance
Record image readability, correct reads, policy outcomes and verified barrier states separately. Include day/night, regional formats, queues, offline lists and revoked permissions. Verify event/video association and controlled retention of plates. Confirm controller feedback and safety behavior with its responsible installer before accepting automated operation.