Government and embassy sites demand high assurance: resilient standoff, controlled access, and dignified streetscapes. Specify certified HVM bollards to secure frontages and approaches (214, 234) while preserving civic character (316, 366, 238). Align with blast/security policies, define operating protocols (525, 545), and submit robust documentation and certificates (431, 717). Keep rating-critical dependencies visible (421) and emergency access workable (233). 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.
812.1 Threat posture
Higher intent/energy scenarios drive HVM bollard ratings (221, 414). Document credible multi-hit (226).
Start with a threat analysis that names hostile vehicle classes and run-up vectors. Translate that into a VDA speed/energy envelope, then select a tested crash-rated system with evidence for the governing angle. Where dignitary schedules elevate risk, include multi-vehicle/multi-hit notes in the specification.
Use standards equivalency only when you provide traceable energy parity and orientation comparability. Document assumptions and sensitivity bands in the VDA (224, 228) and carry them into the selection narrative (413).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global crash ratings |
| Operations | Duty cycles, fail-state, safety | EFO & overrides |
812.2 Standoff & secure zones
Prioritize standoff envelopes (213) with islanded arrays (321). Crash rated bollard gaps must resist corner attacks (324).
Set the stand-off distance from the protected façade, then draw the array pattern to preserve a continuous secure zone. Treat corner throats and pinch points as hotspots (324) and keep clear-gap within the rule set even under dynamic deflection.
Where long frontages meet heritage curtilages, island clusters minimise interventions in paving modules while preserving the penetration line. Validate worst-case vector coverage with a simple vector diagram and include keepered options for stewarded openings (325).
812.3 Controlled access lanes
Fail-secure philosophy, EFO rules, and interlocks (355, 354, 352). Proof during SAT (638).
Embassy driveways typically use automatic HVM bollards with a fail-secure down philosophy, EFO timing windows (354), and an interlock matrix to prevent unsafe states. Define credentialed access, tailgating controls, and lane throughput targets (542).
During SAT, prove EFO energy, obstruction auto-reverse, and annunciation priorities. Capture results in the witness pack, with video/photo evidence and signed checklists.
812.4 Perimeter & approach
Interrupt long run-ups and screen bays (214, 325). Orient arrays to worst vectors (225).
Block approach paths by adding chicanes, speed humps, or planter setbacks before the defend line. At service yards, screen bays to remove straight run-ups and set corner islands to close drive-around defeats. Use VDA angle studies (225) to orient mixed-type arrays where turning clearance is tight.
Keep emergency/service access workable (233) with latched manual release procedures, blue-light access scripts, and a reset-to-normal checklist after each activation.
812.5 Streetscape & diplomacy
Balance appearance with deterrence (316, 366). Use sleeves that don’t void certification (415, 421).
Diplomatic sites must read as open and dignified while communicating deterrence. Choose heads/finishes that complement civic materials (316, 366) and apply allowable variants only. Decorative sleeves must sit within the certificate scope, and installation must respect rating-critical dependencies.
For coastal durability or hot climates, specify finishes that meet life-to-first-maintenance targets and avoid galvanic pairings around fixings; document this in the submission pack.
812.6 Blast & glazing interfaces
Coordinate with façade offsets and routes (234). Keep crash rated bollard performance independent of façade upgrades.
Crash-rated bollards mitigate vehicle-borne threats; they are not blast walls. Coordinate frontage protection with façade blast standoff and egress cones so that glazing replacements or screening do not undermine array coverage. Maintain an independent defend line so façade works can proceed without re-testing the vehicle barrier system.
812.7 Protocol & motorcades
Temporary openings with keepered gaps (325). Event plans (239) protect dignity and safety.
Design keepered openings for ceremonial arrivals: stewarded gates, corner chicanes, and removable bollards only where documented in the certificate family. Use a configured event mode with response windows, steward posts, and reset steps after convoys. Validate safe turn-in tangents and swept paths for armored vehicles without breaching clear-gap rules.
812.8 Evidence & governance
Equivalence and anti-downgrade clauses (414, 435). Traceability in packs (938).
Use anti-downgrade language and set equivalence proof requirements. Submission packs (431, 717, 938) should include authentic certificates, unedited test footage references, report numbers, and a document matrix mapping assumptions to drawings and method statements. Keep rating dependencies and as-tested configurations visible on drawings and in the ITP.
812.9 O&M & assurance
KPIs, drills, and audit cadences (542, 547, 728). Maintain availability targets (738).
Operate lanes to KPI thresholds (cycle time, ops/hour, MTBF) with alert bands (542) and keep an incident drill library (547). Record site audits (728), track service credits against availability targets (738), and perform post-incident inspections with evidence logs and torque audits where bollards have been struck.
