Remote operation
Remote door and barrier opening: the operating sequence
Remote opening lets an authorized operator command a connected entrance from another location. Reliable operation depends on the decision procedure and the feedback available from the site.
Enlarge screenshot The decision
Verify the request before sending a command
The operator needs to identify the site and entrance, understand the request and check eligibility through the site’s approved procedure. An intercom call explains why someone is waiting; it does not automatically authorize entry.
Lexoh combines configured access equipment and remote actions in Security Center. Camera views and other records are available only where the relevant equipment and integrations are present.
Distinguish the command from the outcome
A remote command travels through the configured connection to the controller and connected operator. The movement then follows the equipment’s control and protective logic.
A command acknowledgement is not proof of an open door or a completed vehicle passage. Specify the status feedback needed for the task, such as door position or lane observation, and demonstrate what the operator sees if the command fails.
On a narrow screen, scroll the table horizontally to see every column.
| Step | Check | Limit |
|---|---|---|
| Authorize | Correct site, entrance and eligible request | A call or image alone does not grant permission |
| Command | Allowed action and controller connection | A sent command does not confirm physical movement |
| Verify | Current position feedback and relevant observation | A status label alone does not prove completed passage |
| Record or escalate | Action record, outcome and local contact | An unresolved mechanical fault still needs site assistance |
Give operators a bounded responsibility
Define which entrances each role may control and the checks required for visitors, deliveries, unpaid stays or failed credentials. State who can approve an exception outside that procedure.
Use individual operator accounts and review the available action records. Confirm the actual fields retained; do not assume every command automatically includes a written reason or a video clip. Train operators to record additional context through the agreed process.
Plan internet and power interruptions separately
Remote commands require a working communications path. Some configured controllers can continue local decisions using stored rights, but this must be confirmed for the selected hardware. New permissions and revocations may wait for reconnection.
A power interruption presents a different problem. Document the behaviour of the controller, lock or barrier, assistance equipment and any backup supply. Manual release and emergency access belong in the site’s approved procedure.
Introduce remote operation with a pilot
Choose one entrance and rehearse an authorized arrival, a refusal, an unanswered call and loss of connectivity. Test from the operator’s actual workstation, including access to the relevant records.
Measure call handling and unresolved incidents during the pilot. Remote assistance can resolve some requests without a visit, but damaged equipment, obstructions and maintenance still require a local response.
For powered gates and barriers, have the installer confirm that remote operation is permitted by the equipment instructions and site design. A camera view supports observation; it does not replace the required protective devices. If the operator cannot verify the conditions required by the site procedure, use the agreed local assistance route.
Questions
Practical questions
Does the on-screen command confirm that the entrance is clear?
No. The operator needs the current observations and status signals required by the approved procedure. An old image, a successful command acknowledgement or a connected status is not enough to establish that the movement area is clear.
What should happen if the command produces no confirmed result?
Check the selected entrance, connection status and available feedback. Follow the agreed failure and escalation procedure rather than sending repeated commands without understanding the result. Arrange local assistance when equipment or site conditions cannot be verified remotely.
Can an existing barrier be connected?
Its control interface, condition and protective logic must be reviewed. Compatibility cannot be established from the barrier’s age alone.
Does remote opening include a staffed call centre?
Staffing, coverage hours and escalation are a separate service scope. Define them before relying on off-site assistance.
References and further reading
- Cloud platform
Lexoh product or project reference.
- Parking intercom
Lexoh product or project reference.
Your project
Plan the remote response
Review entrances, operator roles and local backup arrangements with Lexoh.
Discuss the project