Cycle times, counts, temperature, and duty reliability.
Show that the lane delivers. Measure cycle time, throughput, duty/heat (341, 512–513), and acoustics (546). Track power draw and EFO energy (517, 354), then test sequential lanes and mixed modes (525). Configure logging (541–544) and compare against pass/fail thresholds agreed in the spec/ITP (433, 714). Summarize results to feed cost/ROI pages (841, 843) and SLA targets (738). 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.
636.1 Cycle time & throughput
Measure up/down times and ops/hour. Metrics quantify HVM bollard lane capacity (542).
Use a stopwatch or PLC counters to record raise/lower cycle time and steady-state Ops/hour. Establish baseline values at nominal temperature and grid power, then repeat during a short soak test to expose drift. For public-facing lanes, include signage/annunciator dwell where it affects effective throughput.
Report median, 95th percentile, and cycle-time variance. Investigate outliers: loop re-triggers, thermal throttling, or supply sag may be implicated (514 Electrical Supply & Protection). Align KPI names/alert bands with 542 KPI Set.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global crash ratings |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
636.2 Duty cycle & heat
Run extended cycles; track temps (341, 512–513). Heat checks protect crash rated bollard components.
Plan a stepped-duty profile (e.g., 25% → 50% → 75% → peak) and log temperatures at the HPU, drive motor, and enclosure air. Compare with vendor derating curves and site heat-load estimates (see 926 Enclosure Heat-Load Estimator). For hydraulic systems (512) watch oil temperature and standby pressure trends; for electromechanical (513) monitor motor current and thermal alarms.
636.3 Noise & vibration
Record levels vs limits (546). Low noise maintains HVM bollard approvals.
Measure A-weighted dBA at agreed receptor points during raise/lower and at standby. Compare with project acoustic limits and local codes; enclosures with acoustic lining, isolation mounts, or pump duty/assist logic can reduce structure-borne noise. Document meter type, weighting, distance, and ambient noise floor for reproducibility (see 546 Acoustic limits).
636.4 Power draw & EFO energy
Log steady/transient and EFO usage (517, 354). Logs validate crash rated bollard power sizing.
Use a clamp meter/sub-meter to capture idle, raise, lower, and peak inrush; correlate with PLC COS logs. Verify EFO energy source (accumulator or capacitor) meets the spec and cool-down interval. Cross-check calculations with 924 HPU Duty/Energy Planner and the project 517 Energy Budget.
636.5 Sequential lane behavior
Test inter-lane coordination (525). Coordination keeps HVM bollard flows smooth.
For two or more lanes, validate sequencing logic when multiple requests arrive. Confirm the state machine prevents forbidden states and preserves safety cues/clear gaps. Record queue effects and announce dwell timings on HMI tiles for operators; align wording with your 525 Modes of Operation and 544 Operational Dashboards.
636.6 Mixed-mode scenarios
Switch modes during traffic (525). Mixed tests verify crash rated bollard robustness.
Exercise day/night profiles, lockdown/emergency, maintenance bypass, and fire-alarm overrides. Prove recovery paths and latched alarms behave as specified (see 536 Alarm Philosophy and 346 Fire/BMS Interfaces). Document any throughput penalty and capture operator messages that minimize mode error.
636.7 Trend/logging setup
Enable counters and health pings (541). Setup sustains HVM bollard KPI tracking.
Turn on device counters, health pings, trend tags for temperature/current/pressure, and first-out alarms. Push to a historian or lightweight dashboard (542–544). Ensure time sync (NTP) and stable asset naming; this data underpins MTBF, SLA availability gauges, and later 543 predictive maintenance.
636.8 Pass/fail thresholds
Compare to spec/ITP bands (433, 714). Thresholds make crash rated bollard acceptance objective.
Translate your specification and ITP into acceptance bands: cycle time (median/95th), Ops/hour minimum, power peaks, acoustic limits, and max temperatures. Record witness points and sign-offs for SAT (638). Nonconformances should open NCRs with defect class, root cause, and retest plan (719).
636.9 Results summary
Create a concise report and charts (544). Summary proves HVM bollard value.
Produce one-page charts: sparkline of cycle time, Ops/hour bar, temperature trend, and energy pie (idle/raise/lower/EFO). State pass/fail vs thresholds, list improvements (e.g., fan curve, pump duty/assist, EFO cool-down), and note business impacts for 843 ROI and 738 SLA targets. Archive logs/screenshots in the submission pack (938).
Related
External resources
- ASTM F2656 Crash-Rated Overview
- BSI — Impact Test Specifications (VSB systems)
- NPSA — Hostile Vehicle Mitigation (HVM)
636 Performance & Duty Tests — FAQ
What is an acceptable cycle time for an automatic HVM bollard?
It depends on model and duty. Many lanes target 3–6 s per raise and 2–5 s per lower. Use your project specification and ITP bands to define pass/fail, and verify under soak to catch thermal drift.
How do we prove the duty cycle is safe in hot climates?
Run stepped-duty tests while logging enclosure, oil/motor temperatures and current draw. Compare against vendor derating curves and confirm fans/venting or standby pressure tweaks keep all values within limits.
Do EFO tests damage the system?
Properly designed EFO uses stored energy (accumulator/capacitor) and a cool-down interval. When limits are respected, EFO should not harm the system. Always log EFO events and verify recovery to normal duty.
Which logs are essential for SAT sign-off?
Keep cycle-time series, Ops/hour counters, temperature/current trends, acoustic readings, and power/EFO snapshots. Pair with witness signatures, NCR closures, and dashboard screenshots in the submission pack.