Use this page to set realistic budgets before design hardens. We break down cost ranges for low-speed and certified crash rated bollard solutions, then show how depth/utilities (241–246, 244, 422), controls/safety (341–355), and reinstatement (629) move totals. Commissioning/testing (631–638), spares/warranty (854), and use-case examples link to selection guides (432–434, 443) so HVM bollard choices are grounded in cost reality. 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.
841.1 Cost elements
Break costs into design, product, foundations, controls, install, commissioning, O&M. Separate HVM bollard hardware from crash rated bollard civil works (331–333).
Start by splitting the estimate into (a) pre-construction (site surveys, design, approvals), (b) supplied hardware (fixed/manual vs automatic HVM bollards), (c) foundations and reinstatement, (d) electrical/controls and safety devices, (e) installation, and (f) commissioning and documentation. Treat the tested system as bollard-plus-foundation; don’t under-scope civil works when comparing “bollard prices”. Link your structural checks to 333 Design checks.
For certified crash-rated products, carry allowances for test-proven foundation types, minimum 243 depth class, sump/drainage where required, and equipment enclosures. Low-speed solutions often shift cost from certification to simpler civils, but may still require sleeves, grade beams, and reinstatement to public-realm standards (629).
Commissioning is a real line item: plan for pre-commission checks (631), interlocks/safety verification (634–635), and performance/duty testing (636–637). Document outcomes in your handover pack to support warranty and life-cycle budgeting (854 Warranty & Spares Policy).
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | 410 Global crash ratings |
| Operations | Duty cycle, fail-state, safety measures | 350 Safety & Interlocks |
| Install | Depth class, utilities, reinstatement | 600 Installation |
841.2 Capex vs Opex
Model energy, spares, inspections (517, 734). Lifecycle shows HVM bollard value beyond purchase.
Capital expenditure (Capex) covers supply and build; operational expenditure (Opex) covers power, inspections, consumables and 734 preventive maintenance. For automatic lanes, estimate annual energy using your panel load and duty assumptions (517 Energy Budget). Add spares (seals, sleeves, safety edges) and a reactive allowance for incidents. A 10-year TCO model makes higher-rated systems’ durability and lower failure rates visible against cheaper, lightly-built options.
841.3 Quantity drivers
Arrays, spacing, standoff, utilities clashes (321–324, 232, 243). Drivers scale crash rated bollard cost.
Quantities scale from the 320 array logic: required stand-off, clear-gap rules (232), near-door and corner treatments (323–324). Utilities constraints (243) push you toward shallow systems or rail modules, affecting unit cost and productivity. Model arrays in regular, staggered, or mixed types (321, 326) to avoid over-ordering and to minimize reinstatement wastage.
841.4 Foundation choices
Deep vs shallow impacts labour/plant (332, 244). Right choice reduces HVM bollard rework.
Foundation type determines excavation size, spoil handling, and programme risks. Where clashes or slabs limit depth, evaluate 244 shallow foundations against the product’s as-tested configuration and site ground (422). Deep sockets can reduce reinstatement area; shallow rails can increase civils footprint but avoid diversions. Always validate with 332 foundation types and the project’s utilities survey (240–246).
841.5 Controls & safety
Drives, panels, devices (341–347). Controls often match crash rated bollard capex.
In automatic lanes, drives (341), panels/I/O (520–528), and safety devices & measures (353) can equal the bollard hardware budget. Include field devices (345)—photo-eyes, induction loops, traffic signals—and interlocks (352–355) sized to throughput and failure modes. Where authority interfaces apply (e.g., fire/BMS/SCADA at 346), add integration, testing (538), and witness time. The Opex side includes fault logging and KPIs (541–544) that reduce downtime and extend asset life.
841.6 Programme/time risk
Permits, inspections, dewatering (134, 614). Time risk inflates HVM bollard cost.
Time is money: permits/inspections (134), traffic management and utility shutdown windows add prelims and idle costs. Groundwater brings wellpoints and dewatering (614), while complex phasing (855) adds out-of-hours premiums. Build a risk register with duration bands and allocate a float for authority reviews; in the UAE, consider SIRA coordination early to avoid late hold points.
841.7 Market & sourcing
Lead times, local content, logistics (338, 361). Sourcing stabilizes crash rated bollard delivery.
Market conditions swing totals: currency, freight, and factory lead times. Plan alternates via 338 value engineering without downgrading rating or as-tested geometry. Materials choices (361–367) change price and durability; coastal sites may mandate 316 stainless or duplex coatings. Confirm vendor capacity and spares policy (854) to keep lifecycle costs predictable.
841.8 Contingency policy
Risk-weighted % tied to registers (351, 335). Transparent buffers for HVM bollard unknowns.
Use risk-weighted contingency, not a flat guess. Tie % bands to a hazards/controls register (start at 351 Hazard analysis) and to utilities uncertainty (335 Underground Utilities). Typical triggers: unproven services, groundwater variability, night working, authority changes, and witness scheduling. Keep the contingency visible in reports and adjust as information matures.
841.9 Cost reporting
Standard templates with 911 naming. Reporting aligns crash rated bollard stakeholders (131).
Stabilize expectations with a standard BOQ and a recurring report cadence: progress, risks, changes, and cash flow. Use file naming aligned to 911 File Index & Naming Rules so stakeholders can trace revisions. Map responsibilities to 131 Stakeholders, and keep a live TCO section that references 432 the selection guide and 443 low-speed vs HVM to justify scope decisions.
