An exit queue needs an agreed escalation plan, a tested controller response and a recorded interval for reconciling affected parking sessions.
Agree the escalation trigger, responsible staff and approved traffic arrangements before an exit queue becomes an incident. Any controlled override needs an authorized operator, a tested restoration procedure and a way to reconcile sessions affected by the changed operation.
Review proposed changes with site safety and road authorities where required. Holding a barrier open can be part of an assessed response, but a free-flow setting should not be assumed to solve every queue or settle its payment consequences.
Staffed exits and ticket equipment already needed contingency procedures when normal processing could not serve the traffic. Plate-based workflows add session records to that problem.
The decision to hold a barrier open still concerns the controller, the road interface and the assessed operating plan, rather than the recognition software alone.
Attendant assistance, another exit, a changed payment process or a planned temporary opening may suit the site. A one-click toggle is not inherently necessary.
The chosen response should fit the installed equipment, the people available to operate it and the approved arrangements for circulation inside the property and at the public road.
Define who assesses the queue, who changes controller mode and what triggers escalation. Test the approved method with the gate specialist, including lost communications and safe restoration. Continue permitted observations where feasible, and mark when ordinary access or charging rules were suspended so later reviewers can interpret the resulting gaps rather than invent exit times.
An authorized ten-minute opening, for example, needs a recorded start and end. Those boundaries distinguish exceptional departures from ordinary ones. Establish whether the opening affects an external payment ledger and how incomplete sessions are reconciled afterwards; changing the physical lane state should not silently become a decision to cancel or retain every charge.
Aero Ranger CORE Enforcement Overrides records authorized exceptions with reasons and action history. This can document a reviewed change to ordinary operations during congestion. Available actions, timestamps and external reconciliation need verification in the proposed deployment.
The documented feature does not establish a native 'Free Flow Open' gate command or automatic cancellation of charges for the affected interval; those require separate supported arrangements.
Aero Ranger: Enforcement overrides; Aero Ranger: Audit logs
Sources were reviewed on the publication date. Check the linked material for current details.
