Initial energization tests and protective checks.
First energization sets the tone. Follow a written plan, confirm voltages/phases and UPS/generator transfers (511, 514, 518), then verify PLC/HMI boot, time sync, and comms (521–524). Check default states and alarms (536), confirm drive/HPU readiness (341, 512–513), and test local/remote controls. Log initial status, use safe fault-isolation steps, and retain records for SAT evidence and dashboards (638, 544). 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.
632.1 Energization plan
Script steps, roles, and abort criteria. Planned energization keeps HVM bollard commissioning controlled (631).
Use a written runbook that names the RACI, pre-checks, and Go/No-Go criteria from 631 Pre-Commission Checklist. Ensure LOTO boundaries are defined and briefed. Capture hazards in the Risk Assessment and set clear abort criteria (e.g., wrong voltage, phase loss, nuisance alarms).
Confirm comms with witnesses when SAT/Witness is in scope. Keep the energization plan in the project’s ITP with a traceable checklist and photo evidence per 716 Evidence Capture Standards.
| Aspect | What matters | Where to verify |
|---|---|---|
| Performance | Tested system (bollard + footing) | Global crash ratings |
| Operations | Duty cycles, fail-state, safety | Installation Guide |
632.2 Supply voltages & phases
Verify supply, phase rotation, and earthing (511, 514). Clean power prevents crash rated bollard nuisance faults.
Before enabling controls, confirm incoming voltage, phase loss absence, and correct phase rotation. Check protection grading, SPD status, and earthing integrity. Reference 511 Supply & Sources and 514 Electrical Supply & Protection for acceptable limits and test points in 519 Power Test Points.
632.3 UPS/generator behavior
Prove transfer, ride-through, and alarms (518). Stable transfers keep HVM bollard logic intact.
Exercise ATS/STS transfers and verify ride-through on the 518 Power Failure Modes scenarios. Confirm UPS autonomy and low-battery alarms, and prove that critical signals (e.g., Safe Local Mode banner) persist through short outages and return to normal after power restoration.
632.4 PLC/HMI boot & comms
Check boots, time sync, and links (521–524). Healthy comms sustain crash rated bollard visibility (533).
Power up the PLC and HMI; verify firmware versions, license status, and NTP sync. Confirm SCADA/BMS reporting is alive (heartbeat/health ping) and I/O modules are enumerated correctly per the I/O list. Record scan time, network latency, and any latched alarms for the CRR pack.
632.5 Alarms & default states
Validate safe defaults and annunciation (536). Defaults avoid unsafe HVM bollard motion.
With bollards inhibited, verify the alarm philosophy: first-out, priorities, shelving, and clear text. Confirm default states (e.g., bollards down, gates locked, EFO unavailable) align with the state machine and site risk profile. Test annunciation to SCADA/BMS and the dashboard, including alarm banners and inhibit reasons.
632.6 Drive/HPU readiness
Enable/disable tests, temps, and currents (341, 512–513). Readiness indicates crash rated bollard performance potential.
Check automatic drive readiness without motion: for hydraulics, accumulator pre-charge, reservoir level/ISO 4406 cleanliness if applicable; for EM drives, standby current, motor thermal protection, and STO circuits. Verify 512 HPU, 513 Electromechanical Drives, and 341 Drive Systems acceptance points before any motion testing.
632.7 Local/remote controls
Confirm mode authority (525). Clear authority prevents HVM bollard conflicts.
Prove authority hierarchy and modes of operation (Local, Remote, Safe Local). Validate that remote commands are blocked when Local has authority and that emergency/Fire Master inputs override as designed. Check door-open tamper, key switches, and any deadman controls if fitted.
632.8 Fault isolation
Use safe isolation and stepwise enablement (519). Isolation protects crash rated bollard devices.
When faults appear, isolate by domain (power, controls, field device) using 519 Power Test Points and 529 Commissioning Tools. Use a loopback plug for inputs, test/isolate switches, and safe enables to narrow root cause. Maintain the hazard log and resume the energization script only after a controlled reset.
632.9 Record initial status
Snapshot counters, temps, voltages (541). Baselines anchor HVM bollard KPIs (542).
Capture zero-hour snapshots: ops/hour counters, cycle time, reservoir temperature, supply voltages, health pings, and alarm tallies. Store results in the commissioning record and seed the KPI thresholds. These baselines support the next steps: 633 Loop & Sensor Proving and 634 Interlock Matrix Verification.
Related
External resources
632 Power-On & Controls Health — FAQ
What should be in a bollard power-on script?
List pre-checks (LOTO cleared, correct voltage/phase, SPD status), roles and comms, stepwise enables (power→PLC/HMI→drives), Go/No-Go criteria, and evidence capture steps. Keep it in the ITP with sign-offs.
How do we confirm UPS/Generator transfers won’t trip controls?
Test ATS/STS transfers under load, verify UPS autonomy/alarms, and prove ride-through of PLC/HMI and core I/O. Confirm default states and Safe Local Mode banner persist and recover cleanly after the event.
What baseline data should we record at first energization?
Record supply voltages, PLC scan time, alarm counts, ops/hour counters, cycle time, reservoir temperature, and health ping status. File snapshots with photos in the commissioning record for KPI thresholds.
How do we isolate faults safely during power-on?
Use domain isolation: power, controls, or field. Apply test/isolate switches, loopback plugs, and dry-contact simulators. Resume the script only after the hazard log is updated and a controlled reset is agreed.