827.1 Interfaces with fences/walls

Avoid vehicle lever arms and weak joints. Tie HVM bollards to boundary logic (214).

Start by confirming the intended secure perimeter and how the boundary actually behaves on site (step backs, plinths, buttresses). Where a wall abuts a bollard run, align the defend line so there’s no nose that a vehicle can use as a lever to rotate a post. Reference the site’s perimeter & approach paths to anticipate approach vectors.

Interfaces should be “hard” and continuous: fill voids, cap rebates, and coordinate coping levels so the array’s clear-gap is maintained right to the wall face. Use infill rails/plates only if they are part of the tested system or documented in your design selection as a non-structural screen.

Where fences meet bollards, avoid flexible mesh that can deform under push; add kicker beams or set posts close enough that the fence can’t be driven between them. For heritage walls, consider a freestanding bollard return that respects setbacks while preserving fabric, then stitch back visually via finishes (see color & aesthetic finishes).

827.2 Corners & returns

Treat radii and pinches (324). Preserve crash rated bollard clear gaps (232).

Corners distort spacing quickly. Use a short “chicane nose” or a two-post return to keep the clear-gap rule through the turn. At tight radii, project the array centreline and solve for effective gap on the chord, not the arc. See Corners, Islands & Pinch Points.

Where a façade steps, add a short return (2–3 posts) to remove pinch points and prevent diagonal “sneak” paths. Check sweeping vehicle envelopes if the corner is adjacent to vehicle access lanes, and confirm sightlines do not hide gaps.

827.3 Gates & doors

Interlock with adjacent gates/doors (352, 534). Prevent unsafe openings.

Design the gate/bollard interface as one security control point. Mirror the gate leaf stop with a bollard “stopper” post so the gap never exceeds the array’s limit when the gate is open. Define interlocks in the interlock matrix, and coordinate with access control/CCTV for safe states and annunciation.

At doors, maintain a consistent near-door spacing and confirm egress cones. Where doors swing outward, check the door-swing zone doesn’t create a keepered opening against a post. If credentialed access is used, integrate card reader standoffs and lighting to avoid ad-hoc brackets that create climb/lever points.

827.4 Level changes & ramps

Step/retaining interfaces and drainage (629, 334). Height affects HVM bollard performance (312).

Grade breaks change effective height. Where the paving drops away, a post can lose capture height, undermining containment. Adjust post heights or add a low plinth to preserve the tested geometry (see height setting).

At retaining edges, use continuous grade beams or stepped footings to avoid cantilevered slab noses that can spall on impact. Drainage must not create ponding along the defend line—tie into surface reinstatement details and provide weeps or micro-channels per drainage guidance.

827.5 Utilities corridors

Protect easements; choose shallow options (243–244). Evidence for approvals (717).

Map easements and declare a utility avoidance zone beneath proposed tie-ins. Where conflicts arise, pivot to depth classes and shallow foundations that are compatible with protections and duct banks (ducting & pathways).

Capture utility proving (PAS-128 methods, trial pits) in the authority submittals so reviewers can see why a given foundation choice is valid at the interface. For UAE projects, note SIRA expectations succinctly and link to SIRA Bollards (UAE).

827.6 Sightlines to security

CCTV coverage and lighting (534, 353). Sightlines reinforce crash rated bollard deterrence.

Tie-ins should not create blind pockets behind planters, walls or returns. Confirm that cameras have coverage and that conspicuity is maintained via safety signalling and lighting. Coordinate reader posts, VMS and signage to avoid narrows that look like gaps on CCTV.

Document camera/lighting adjustments in the interface drawings, and include simple wayfinding so pedestrians don’t push into maintenance strips or service gates inadvertently.

827.7 Planting & furniture edges

Avoid hiding gaps; use planters tactically (238). Aesthetics per 316/366.

Planters can close short spans or soften long runs, but their placement must not mask a residual gap. Keep the planter’s solid base aligned with the array and avoid “wheel notches” at corners. Where planters are non-rated, treat them as visual fillers only and rely on the posts for stopping power (see frontage protection arrays).

Furniture (benches, bins, cycle hoops) should never substitute for posts at the boundary. Use finishes, bands and sleeves to integrate the look and preserve clarity (see heads & attachments and aesthetic finishes).

827.8 Maintenance strips

Access widths and surfacing (365). Strips preserve HVM bollard serviceability.

Provide a clear, safe strip along walls/fences for inspection, cleaning, and access to enclosures. Specify robust surfacing and keep inspection bands free of planting that could conceal fasteners or tamper points. Reference design for maintenance to size widths for typical tasks (e.g., hydraulics checks, fastener torque audits).

Where the strip intersects doors or service gates, add a short paved return to guide pedestrians and avoid desire lines that cut through landscaping. Use tactile cues only where mandated so you don’t unintentionally signal a “path” through the defend line.

827.9 As-built documentation

Detail tie-ins in 731 with photos (716). Records support crash rated bollard audits.

Interfaces are where problems emerge later, so capture them in as-built drawings & models with a wide→detail photo set. Label gaps, heights, footing type and any barriers connected to walls/fences.

Store interface photos in the evidence capture standard format, cross-referenced to the sheet index. This simplifies audits, supports future post-incident inspections, and proves that the installed geometry matches the tested assumptions.

827 Perimeter Tie-Ins & Boundaries — FAQ