Role-based dashboards for ops, maintenance, and management.
Turn data into decisions for different audiences—operators, FM, and management. Combine live status with historical trends from SCADA/BMS feeds (533) and health pings (541). Highlight exceptions, enable drill-downs, and export evidence for SAT closeout and authorities (638, 717, 444). Align availability views to KPIs/SLAs (542, 738) and secure the dashboards with clear roles and access rules (535). For UAE projects, keep reviewer expectations in mind and see SIRA Bollards (UAE) for approvals context.
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.
544.1 Audience & views
Operators need live states; FM needs trends; leadership needs KPIs. Tailored views keep HVM bollard focus sharp (542).
Design three role-focused views and keep them minimal. Operators need lane-level tiles showing current state, alarm banners, inhibits, and a visible Safe Local Mode banner when active. Facilities/Maintenance (FM) need trend screens: ops/hour, cycle-time drift, and fault rates. Leadership wants roll-up KPIs—availability and SLA attainment—plus monthly deltas.
Back the views with named data sources from 533, using a stable tag naming convention so dashboards are templatized across sites and easier to audit during SAT (638). Add small sparklines beside headline numbers to reveal trend direction at a glance.
Link each tile to an action: acknowledge, suppress (shelve), or open the runbook (734, 547). That way, dashboards don’t just “inform”—they shorten time to recovery.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Uptime by lane/site; MTBF trend | KPIs & thresholds (542) |
| Operations | State machine health; alarm handling | Alarm Philosophy (536) |
| Data | Authoritative tag list; historian setup | SCADA/BMS signals (533) |
544.2 Live vs historical
Live tiles for alarms; trend pages for root-cause. Balance supports crash rated bollard decisions (533).
Use “live” pages for events that require immediate action: lane state, first-out alarms, inhibit reasons, and active interlocks. Keep latency below the agreed alarm latency target and show a time sync indicator sourced by NTP.
Use historical pages to explain “why”: trends for cycle time, restart frequency, oil temperature/pressure (512), and counters from remote logging (541). Pair each chart with a short narrative and cross-links to test evidence (638) or maintenance plans (734).
544.3 Exception highlighting
Surface lanes off-SLA or with rising faults. Exceptions guide HVM bollard attention (541).
Flag three exception types: (a) SLA breach risk based on forecast availability; (b) abnormal trend alarms (rate/persistence) on cycle time; (c) missed health pings indicating comms loss. Use a compact list at the top with severity, site, and lane identifiers.
Drive color purely from the alarm/priority matrix (536) to avoid “alarm floods.” Provide a one-click filter to “Exceptions only,” then let the operator jump straight to the lane detail or open the work-order form.
544.4 Drill-downs & filters
Filter by site/lane/fault class; click to evidence. Drill-downs speed crash rated bollard fixes (444).
Start with global → site → lane navigation, then add filters for fault class, time window, and mode of operation. A lane’s detail page should show a compact timeline (states, alarms, operator actions) with links to the ITP step or SAT script that proves the behavior. Include “open evidence” links to photos or extracts from the Handover Pack Index (736).
For recurring issues, show a small Pareto chart. Use runbooks to suggest next actions and reduce MTTR.
544.5 Export & sharing
PDF/CSV scheduled reports tied to 911 names. Exports document HVM bollard performance (938).
Offer one-click exports (CSV for data, PDF for snapshots) named per File Index & Naming Rules (911). PDFs should embed time range, site IDs, and report release ID. For monthly closeout, schedule the “SLA Attainment” and “Top 5 Fault Drivers” packs and attach them to the submission index (938).
544.6 Availability & SLAs
Compute per lane and site; show gaps (738). SLAs prove crash rated bollard value.
Track availability with explicit SLA gauges at site and lane levels. Define inclusion rules (e.g., planned maintenance windows) and make degradation visible (e.g., one lane down on a two-lane set). Attach evidence links to incidents that consumed allowance, and show projected risk to month-end target.
544.7 Mobile access
Responsive views for on-site teams. Mobility accelerates HVM bollard response.
Keep the mobile experience tile-first, large hit targets, and offline-tolerant where possible. Show a condensed alarm list with acknowledge/shelve, a lane picker, and a map pin view with Site IDs. Use push/email subscriptions sparingly to avoid alert fatigue; reserve them for SLA risks and safety-critical alarms.
544.8 Security & roles
RBAC, MFA, and read-only defaults (535). Security protects crash rated bollard data.
Apply RBAC with least-privilege defaults: Operators acknowledge; FM edits notes/schedules; Reviewers read-only. Enforce MFA, segment traffic via VLANs, and restrict paths with ACLs. Forward key events to a SIEM and log configuration changes to support audits and change control (537).
544.9 Sample layouts
Provide gallery with IDs and legends. Samples standardize HVM bollard reporting.
Document a small gallery of reference layouts with legend IDs (e.g., “D1 Lane Tile, D2 Alarm Banner, D3 SLA Gauge”). Pair each with the tag list it consumes (533) so integrators can build quickly. Include one “Operations wallboard,” one “FM trend suite,” and one “Monthly KPI pack” example, each mapped to the same data model for easy reuse across sites.
Related
External resources
- NPSA — Hostile Vehicle Mitigation (overview)
- ASIS — Security Risk Assessment Standard
- BSI — Vehicle Security Barriers (impact test specifications)
544 Operational Dashboards & Reporting — FAQ
What’s the minimum data set to build a useful HVM dashboard?
Start with lane state, alarm list (with priorities), ops/hour, cycle time, availability (per lane/site), and health pings. Add links to the tag list (533) and evidence (638) so every tile is traceable.
How do we prevent “alarm floods” on the operator view?
Use a clear Alarm Philosophy (536): priorities, latching, and first-out logic. Cap list length, allow shelving for nuisance alarms, and escalate only when persistence/rate thresholds are crossed.
What’s the best way to report SLA attainment each month?
Use a site-level SLA gauge plus a tabular breakdown by lane. Schedule a PDF/CSV export named per 911, attach it to the submission pack (938), and include explanations for any allowance consumed (738).
How should access be controlled for reviewers and authorities?
Apply RBAC with read-only roles for reviewers, enforce MFA, and segment networks via VLANs and ACLs. Log all configuration changes and forward security events to a SIEM (535, 537).