In the fieldLac-MéganticReader and gate at the marina.Access control
Open the launch only for authorized users.
Connect wash records and access rights to the gate. The reader, controller and platform check your configured conditions before sending an opening command.
- Access rights checked before opening
Wash records or access rights, according to your site’s conditions.
- Reader, gate and platform connected
Find available access requests and events in one place.
- A person to help with exceptions
Your team or the Lexoh call centre can assist the user.
A clear answer at every access point.
Present the access right. Check the conditions. Open the gate. One information chain, made visible in a few seconds.
Interface concept · illustrative interactive scenario
An obvious place to start.
The screen invites the user to present a credential accepted by the site: a card, code, or another compatible access right.
Role in the system
Access control begins before gate selection
The organization first defines who may enter, which identifier they use, when access is available and which prior steps apply. Visitors, emergency services, employees, vendors and users who need a corrected record also require procedures.
- FunctionRight checked
- The presented identifier is compared with configured conditions.
- Site requirementsOpening recorded
- The request and available result are associated with the site.
- OperationsEmergency access
- Manual and emergency methods are agreed with the owner.
Access-point design
Geometry and safety guide installation.
Reader position, stopping space, gate movement, vehicle detection and pedestrian circulation are considered together. Manufacturer safety devices and procedures continue to apply.
- Lane and queue space
- Reader and signage visibility
- Detection and gate movement
- Clearance and emergency access
Access decision
The system checks only conditions approved by the organization.
When an identifier is presented, the platform or configured logic reads the associated right. A valid authorization produces the opening command; a refusal presents the available reason and selected next action.
Policy changes, temporary exceptions and staff rights are logged according to the chosen functions and permissions.
Incident and outage
Operations follow a known procedure.
A damaged gate, inconsistent sensor or communications loss may require local intervention. The fallback procedure identifies who can open the site, how it is secured and how the event is documented.
FAQ
Equipment questions
01Does access control require a wash station?
Not in every project. The checked condition can be a local right, a recorded wash status, or a combination defined by the organization.
02Can an existing gate be used?
Possibly, after review of its condition, interfaces, safety devices and manufacturer support.
