823.1 Entry/exit vectors

Short run-ups, tight radii, glancing risks (214, 225). Arrays must keep crash rated bollard penetration low.

Entry and exit points often create “short run-up” conditions with sharp turn-ins that increase glancing impact risk. Use the approach path review (214) and impact-angle study (225) to position the defend line so vehicles cannot exploit corner throats or bell-mouths.

At throat locations, set array rhythm and clear-gap calculations (322) to the governing angle, not just perpendicular spacing. If the turn-in forces a shallow strike, consider a short corner chicane or island nose to keep penetration within the product’s P-value envelope.

For exits, prevent tailgating by setting a hold line before the gate and using interlock logic (352) that starves signals when the downstream lane is occupied.

823.2 Ticketing & ANPR

Queue lengths, reader offsets, bypass rules (534). No credential bypass of HVM bollard interlocks (352).

Ticketing machines, pay-on-exit readers, and ANPR cameras influence vehicle stopping points and headway. Place devices so drivers stop with predictable wheel and bumper positions for loop detection and safe capture height. Use the ACS/CCTV coordination guide (534) to set offsets and sightlines that minimize “reader shuffles.”

Credential checks must never bypass the interlock matrix. Readers may grant authorization, but bollard raise/lower still depends on lane-cleared sensors, safe local mode, and forbidden-state protections (352). Add a short queue management plan for peak times to avoid spillback into streets.

823.3 Height & clearance

Ramp grades affect head height and gaps (312, 232). Control underslung services (335).

Steep ramp grades change effective height and clear-gaps at nose-over and toe-in points. Cross-check the height setting guidance (312) and spacing rules (232) at multiple stations along the grade, not just at landings. If gradients vary, validate with a quick swept-path and projected-gap check during design.

Keep underslung services away from bollard positions and utility easements (335). Use shallow-foundation options where utilities constrain depth, and verify sump/duct alignments don’t erode capture height by forcing sleeves to sit proud of finished levels.

823.4 Pedestrian routes

Crossings, guard rails, visibility (237, 353). Protect people near HVM bollard lines.

Pedestrian sightlines and signage (237) should make desire lines obvious and separate them from vehicle approaches. Where crossings must traverse HVM lanes, use refuge pockets, high conspicuity cueing, and signal aspects (353) to indicate safe-to-cross states. Avoid creating “trap space” between bollards and guard rails.

At frontage doors or glazing adjacent to ramps, blend a frontage protection array (323) with the ramp interface so a stray low-speed overrun cannot reach entrances. Where bikes or buggies share space, check for handlebar traps and stagger posts if needed.

823.5 Reversing/loading

Keepered openings and marshals (325). Maintain crash rated bollard function during maneuvers.

Loading and reversing areas often demand a temporary opening. Use keepered openings with stewarded control and a short service-access plan (325). If removable (lift-out) posts are required, define keepered dimensions, end-stops, and a reset-to-normal checklist so the penetration distance isn’t compromised after maneuvering.

For automatic lanes near loading, add a latched access state that times out and then re-arms sensors, preventing a truck from lingering with posts down. Where multiple movements occur, create a simple RACI for marshals and drivers.

823.6 Drainage on ramps

Kerb upstands, channels, sumps (334, 616). Prevent water into pits.

Ramps collect water and grit. Use kerb upstands and micro-channels (334) to deflect runoff away from bollard pits. Where equipment pits exist, provide sumps with freeboard (616), silt baskets, and backflow prevention to keep chambers dry during storms and car-wash discharge events.

On down-ramps, add ponding edges and draw pits before the lane hardware so water cannot sheet-flow into enclosures. Confirm hydrostatic uplift and buoyancy checks for any chambers adjacent to storm drainage.

823.7 Fire/egress logic

Fire interface priorities and global drop/raise (532). Logic preserves HVM bollard safety.

Coordinate with the fire alarm interface (532) to define which lanes drop in a confirmed evacuation versus which remain raised to protect the secure perimeter. Program a clear priority matrix so EFO, fire, and manual commands never create a forbidden state. Test fail indications at the HMI so stewards know when the system is in fire override.

When car parks are mixed-use (e.g., retail plus residential), review building egress paths against lane sets, ensuring blue-light access is possible without exposing people to ramp flows. Record the chosen philosophy in the FDS and SAT witness procedure.

823.8 Signage & pricing

Clarity reduces dwell and blocking (357). Flow sustains crash rated bollard throughput.

Ambiguous pricing or time bands cause hesitation at the throat, reducing throughput. Use consistent signal aspects and conspicuity (357) before decision points, not at them. Place tariff boards where drivers can read without blocking the loop—ideally upstream of the hold line—and mirror the same logic on exits to prevent last-second U-turns.

Digitally, align ANPR messages and payment confirmations with the physical signs so legitimate vehicles clear the lane in one pass. That protects the throughput assumptions used in your interlock timeouts.

823.9 Evidence pack

Swept paths, spacing calcs, photos (322, 716). Pack satisfies reviewers (717).

Compile an evidence pack with: (a) clear-gap calcs (322), (b) swept-path overlays for entry and exit vectors, (c) lane logic excerpts from the interlock matrix, and (d) a wide→detail photo set (716) showing sightlines and device positions. For UAE projects, include a short SIRA note on scope and authority touchpoints and reference any applicable authority submittals (717).

Close with a one-page index and a submission cover that maps drawings, calcs, and photos to reviewer questions. This speeds approvals and avoids resubmittal cycles.

823 Car Parks & Ramps Interfaces — FAQ