Short answer. Energization on a data center project is safest and most on schedule when it follows one approved, written procedure with hold points, named roles and a record of every step. This guide lists what to check before, during and after energization.
Definition. Energization is applying voltage to electrical equipment or a circuit for the first time, or again after work, under an approved, written procedure with hold points.
Why energization is a high-risk point on data center and AI projects
AI data center projects, and the legacy and enterprise builds alongside them, are adding more switchgear, more UPS systems and more energization events, on tighter schedules. Procedures are long and crews are under time pressure. A skip or out-of-order step can mean arc flash, injury/fatalities, equipment damage, or a failed test or outage.
How ICARUS Ops helps. The EES shows one step at a time, with warnings and cautions before critical steps.
Before energization: readiness checklist
- Drawings and one-lines are current.
- Acceptance testing is complete and documented (ANSI/NETA ATS). ICARUS Ops: data steps and photos record results.
- The energization plan is reviewed and approved. ICARUS Ops: HQ approves it in the ICARUS Ops web portal, with version control.
- Utility and authority having jurisdiction (AHJ) coordination is done where required.
- Roles are named: person in charge, operators, observers, QA. ICARUS Ops: assign procedures per person or site.
- A communication plan is in place.
- Arc flash labels and PPE requirements are reviewed (NFPA 70E-2024 Article 130). ICARUS Ops: a caution flags PPE before the step.
- The area is barricaded when required and access is controlled, with egress preserved.
- Lockout/tagout is removed only under your energy-control program or ICARUS Ops lockout/tagout system. ICARUS Ops: electronic lockout/tagout and the group lockbox record each lock. ICARUS Ops supports, and does not replace, your OSHA 1910.147 and NFPA 70E energy-control program.
During energization
- Step order. Follow the approved sequence, one step at a time.
- Hold points. Stop where the procedure says, until the named person checks and signs off. Sign-off gates hold the procedure until signed.
- Readings. Record the readings the procedure calls for, against expected values. Data steps capture each reading.
- Photo proof. Photograph device states, lockout/tagout (LOTO), and readings at critical steps. Photos or short video attach to the step, time-stamped.
- Stop-work rule. Anyone can stop the work if something is not as expected.
After energization
Keep the complete record (who did each step, when, readings, photos, sign-offs), update status tags on the equipment, and hand over to the next trade or to the owner with the record attached.
How ICARUS Ops helps. The completed procedure is the turnover record, synced when the device reconnects.
Common failure points
- A skipped step. Fixed step order flags it.
- Steps done in the wrong order.
- A signature without the work. Sign-offs sit with photos and readings.
- An out-of-date procedure version in the field. Only the approved version reaches the field.
Where ICARUS Ops fits
The ICARUS Ops Error Elimination System (EES) lets HQ write and approve the energization procedures once, then crews run it step by step in a native Android and iOS app with quality assurance holds, timestamps, photo proof, and QA sign-off where required, even with no signal. Deployed in the field for construction, energization, and operations for over twelve years of continuous improvement.
See a sample ICARUS Ops EES procedure
See a sample ICARUS Ops EES procedure
Demos are for teams actively evaluating software for deployment.