ANPR, readers, cameras, and event linking.
Secure access without friction. We map credentialing flows and ANPR whitelists to HVM bollard lane logic (821), position readers/keypads for usability (524), and design camera coverage that captures incidents and assists replay. Interlocks with nearby gates/doors (352) and aligned events/alarms reduce error. Scheduling, privacy, and retention policies complete a package that reviewers accept and operators can maintain for crash rated bollard sites (444, 717). Include one-sentence context that naturally links upward to the parent hubs (this section and the chapter hub). Add SIRA context with a link to SIRA Bollards (UAE) when relevant. Link installation pages only if helpful: What to Expect and Installation Guide.
Important: This is a general guide. For live projects we develop a tailored
Method Statement & Risk Assessment (MS/RA) and align with authority approvals (e.g., SIRA) where in scope.
534.1 Credentialing flows
Map request→authorize→execute (342). Flows prevent unsafe HVM bollard raises.
Design a simple, auditable path from a user’s request (card, PIN, ANPR, intercom) to authorization in the ACS, then execution by the lane controller. Each transition should be explicit in the interlock matrix and mirrored in the I/O list, with failure branches that keep the array in a safe state.
Where multi-factor credentials exist (e.g., card + ANPR), define the priority and timeouts to avoid “half-granted” states. For remote authorizations, require a positive state machine confirmation and visible HMI feedback before the bollard moves.
| Aspect | What matters | Where to verify |
|---|---|---|
| Authorization | Clear roles, authorization hierarchy | Integration Documentation |
| Safety | Interlocks and inhibits hold safe | Safety signalling |
| Audit | Change-of-state logs and operator notes | Operational dashboards |
534.2 ANPR & whitelist
Define list ownership and sync rules. Good ANPR prevents crash rated bollard delays (821).
Agree who owns the whitelist, how plates are added/removed, and how often the list syncs to lane controllers. Use a fail-secure approach: on comms loss, allow only benign vehicles explicitly on the local cache; everything else alerts and holds. Record detection confidence and provide an operator override path that preserves the defend line.
Place ANPR cameras to meet stopping-sight distance and sightline constraints; add illuminators if needed. Cross-link this flow with vehicle access lane rules (821) so bollard raise/hold decisions are consistent.
534.3 Reader/keypad placement
Place for sightlines/ergonomics and safe waiting (237, 353). Placement reduces HVM bollard errors.
Mount readers and keypads where drivers can reach without opening doors and while keeping the vehicle inside the safe hold line. Provide weather hoods and anti-glare angles; avoid tight turns that encourage over-shoot. Use induction loops and photo-eyes to guard against tailgating and rollback.
At pedestrian call points (intercoms, FOBs), add conspicuity cues and lighting. Where approvals apply, note SIRA camera/reader height preferences and include them in authority submittals (717).
534.4 Camera coverage
Cover approaches, heads, and control points. Coverage aids crash rated bollard incident review (544).
Design coverage for (a) approach and queue, (b) bollard head/array, and (c) control points/HMI. Use overlapping fields of view to capture the vehicle plate, the lane identifier, and the exact bollard movement. Label streams consistently so replay aligns with lane events on the dashboard (544).
Where cameras share poles with luminaires/signage, verify vibration and cable segregation with enclosures & cabling (347) and cables & routing (515).
534.5 Interlock with gate/door
Sequence with nearby gates to avoid traps (352). Interlocks protect HVM bollard users.
If a swing/slide gate or door is near the array, sequence so no vehicle is trapped between a raised bollard and a closing barrier. Use mutual exclusions: bollards hold down while the gate opens; the gate won’t close if the bollard is rising or a loop detects presence. Document these in the interlock matrix and verify during SAT steps (634–638).
534.6 Event/alarm alignment
Align timestamps and priorities (542). Alignment clarifies crash rated bollard timelines.
Synchronize time across ACS, SCADA/BMS, VMS, and the lane PLCs using NTP. Standardize alarm classes and priorities so operators know whether to stop traffic, dispatch security, or simply log. Ensure change-of-state messages carry lane, device, and operator IDs for audit and KPI accuracy (542).
534.7 Time schedules
Modes by hour/day/event (525). Schedules keep HVM bollard flows predictable.
Create predictable schedules for peak, off-peak, and event modes. Tie ACS schedules to modes of operation (525) so reader permissions, ANPR lists, and lane behaviors shift together. Provide a manual “holiday/event” switch with a clear Safe Local Mode banner on the HMI.
534.8 Incident replay
Store pre/post buffers for analysis. Replay improves crash rated bollard responses (547).
Configure the VMS to keep at least 10–20 s pre-event and 20–60 s post-event buffers on triggers like “bollard rise,” “EFO,” or “loop fault.” Tag clips with lane IDs and alarm classes so investigations and incident response (547) can reconstruct timelines quickly. Provide an operator checklist to export original footage into the handover pack (736).
534.9 Privacy & retention
Set retention and access rules. Governance sustains HVM bollard trust.
Define who can view live and recorded streams, how long data is retained, and how requests are logged. Use privacy masking for apartments, public sidewalks, or neighboring tenants. In UAE contexts, align with client policy and include a concise note in authority submittals (717); link reviewers to your evidence & documentation approach (444).
Related
External resources
- ASIS — Security Risk Assessment Standard
- NPSA — Hostile Vehicle Mitigation guidance
- FEMA 426 — Reference Manual
534 Access Control/CCTV Coordination — FAQ
What’s the safest way to handle comms loss between ACS and the bollard controller?
Use a fail-secure policy backed by a locally cached whitelist, clear alarms, and inhibits that keep the array in a safe state. Operators should see a prominent banner, and manual authorization must log lane, user, and reason.
How much pre/post video buffer do we need for incident replay?
As a baseline, keep 10–20 seconds before the trigger and 20–60 seconds after. Increase for complex approaches or where vehicles may stage before the hold line.
Where should we mount license plate cameras for reliable ANPR?
Place at an angle and distance that meets the vendor FOV/IR specs, with lighting and mounting that preserve plate legibility at the planned approach speed. Respect sightlines and avoid vibration on shared poles.
How do we prevent tailgating through a bollard lane?
Combine near-head loops, photo-eyes, and HMI prompts with sequencing that raises the bollard only for one authorized vehicle, plus timeouts and alarms for second-vehicle detection.