SLAs that protect uptime.
After handover, availability is the product. Define scope, tiered response times, spare-parts strategy, and preventive maintenance aligned to counters and duty. Use remote health pings, KPIs, and clear reports to manage performance, with escalation paths for incidents and root-cause reviews. SLAs keep HVM bollard lanes and crash rated bollards reliable—measurably and contractually. 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.
738.1 KPI targets
Availability, cycle time, response windows (542). Targets define HVM bollard success.
Set a small, auditable KPI set that reflects real operations: lane KPI targets for availability (% of scheduled time in service), cycle time (raise/lower), and reliability metrics like MTBF. Pair each target with alert thresholds and a definition of what counts as “down”—for example, blocked lanes or inhibited safety devices & measures. Reference counters and health pings to avoid manual guesswork.
Make targets tier-aware: heavy-duty sites (airports, embassies) often demand higher availability and tighter cycle-time envelopes than low-duty sites. Document the measurement window (24/7 vs business hours) and exclusions (approved maintenance, utility outages) to keep reports fair and comparable.
| Aspect | What matters | Where to verify |
|---|---|---|
| Availability | Clear definition of “in service” and exclusions | Operational dashboards |
| Cycle time | Measured raise/lower time vs acceptance band | Global crash ratings |
| Reliability | MTBF, fault rate per 1,000 ops | KPI set & thresholds |
738.2 Priority matrix
P1 safety, P2 operation, P3 cosmetic. Matrix drives crash rated bollard response.
Classify tickets so the right engineer arrives at the right time. P1 = safety or security impact (bollard stuck in unsafe state, EFO fault); P2 = degraded operations (slow cycle, intermittent health ping); P3 = cosmetic/documentation items. Publish examples, link each priority to targets in Section 738.3, and align with the site’s incident scheme and Incident / Near-Miss Reporting.
738.3 Response & resolution
Clear times for attend/fix. Times keep HVM bollard lanes dependable.
Define two clocks: response (qualified engineer on site or remote session started) and resolution (restored to service or safe local mode). Use separate targets per priority and per location (on-site vs remote). If approvals/authority context applies, observe local expectations and—where relevant—Dubai’s SIRA policies for critical sites.
- P1: response ≤2h, resolution ≤6–8h (stocked spares);
- P2: response same business day, resolution ≤3 working days;
- P3: batch within the next review cycle.
Record every clock start/stop in the CMMS (dashboards & reporting), with root-cause notes for repeated faults so Section 738.6 can drive improvements.
738.4 Preventive maintenance SLAs
Planned visits, evidence packs (734, 716). PM prevents crash rated bollard failures.
Commit to a visit cadence matched to duty and climate. For high-duty/harsh sites, add mid-cycle “light PM” for cleaning, checks, and lubrication. Each visit produces an evidence pack (timestamped photos, checklists, counters) and updates the asset register & serials. Missed PM windows should trigger an SLA alert and a reschedule within the same month.
738.5 Spares & logistics
Min/max levels, courier terms (854). Logistics reduce HVM bollard downtime.
Establish min–max stock for common failures (seal kits, hoses, sensors, relays) and define courier cut-offs so P1 parts move same-day. Link parts to serialised assets in the register for traceability and warranty rules—see Warranty & Spares Policy. For critical locations, keep a local cache or event kit to meet tight resolution times.
738.6 Reporting & reviews
Monthly dashboards and actions (544). Reviews tune crash rated bollard performance.
Send a monthly pack: uptime %, operations per hour, cycle-time distribution, top faults (Pareto), ticket SLA compliance, and action status. Visuals like an SLA gauge keep decisions quick. Close the loop by assigning accountable owners for each improvement and re-baselining targets if duty changes.
738.7 Escalation paths
Who escalates and when (131). Paths unstick HVM bollard issues.
Publish a simple tree: on-site team → service coordinator → duty manager → engineering lead → vendor principal. Define timers (e.g., P1 not resolved within 4h escalates to duty manager) and channels (phone + ticket note). Map roles to Stakeholders & Responsibilities so everyone knows who owns what at each step.
738.8 Penalties & credits
Fair mechanisms tied to KPIs. Balance protects crash rated bollard value.
Use measured KPIs—not anecdotes—to trigger remedies. Where commercial terms allow, apply service credits for missed monthly availability targets beyond an agreed dead-band; likewise, offer credits back if the client misses site access windows or delays spares approval. Keep caps reasonable, link remedies to root-cause actions, and avoid perverse incentives that discourage preventive maintenance.
738.9 Change & exit
How SLAs evolve or end (537). Governance keeps HVM bollard service fit.
Lock a lightweight governance cycle: quarterly review of KPIs, faults, and duty changes; semi-annual revision of targets if throughput shifts; and a documented change control & versioning trail for service procedures and runbooks. For exit, specify handback data (CMMS history, as-maintained asset register), final spares reconciliation, and a rollover plan to protect uptime during transition.
Related
External resources
- ASIS Security Risk Assessment Standard
- NPSA — Hostile Vehicle Mitigation
- FEMA 426 — Reference Manual
738 Service Levels & Availability — FAQ
What is a realistic availability target for automatic HVM bollard lanes?
Most critical sites aim for 99.5–99.9% measured over 24/7, excluding agreed maintenance windows and utility outages. Define what counts as “down” and keep the rules consistent month to month.
How do response and resolution times differ in an SLA?
Response time is how quickly a qualified engineer engages (remote or on site). Resolution time is how quickly the lane returns to service or a safe local mode. Set separate targets per priority level.
Which spares should be stocked to meet tight SLA targets?
Start with fast-moving items: seal kits, hoses, photo-eyes, loop parts, relays/contactors, and enclosure consumables. Link each part to asset serials and courier cut-offs to minimise downtime.
How should monthly SLA reports be structured?
Include uptime %, operations per hour, cycle-time trends, top faults (Pareto), ticket SLA performance, and a short action list with owners and due dates. Visuals like an SLA gauge keep decisions quick.