Rack UPS and PDU Commissioning Runbook
Installing a UPS does not prove protected runtime or manageable recovery. The outcome depends on input circuit, topology, battery state, connected load, PDU rating, redundancy, network management, alarm delivery and an approved response plan. TechRunz records each dependency and tests only scenarios that are safe for the live environment.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Power, load and runtime design validation
Reconcile exact UPS, battery pack, rail, PDU, network-card and cable models with the design. Verify rack depth, weight, airflow and service access. A qualified party must confirm branch circuit, receptacle, voltage and grounding where required.
Inventory every intended load and its power supplies, rated or measured demand, criticality, redundancy and shutdown behavior. Calculate usable capacity and runtime with the manufacturer tools and approved margin; nameplate totals alone can be misleading.
Power work adds a party the network team does not control, so the packet should say which qualified electrician confirmed the branch circuit and receptacle, and when the room can lose power. On delivery, check crate damage, battery date codes and receptacle type against the order before anything is lifted into the rack.
- Circuit and grounding
- Exact UPS/PDU/accessories
- Load and redundancy map
- Runtime and maintenance objective
Rack installation and protected outlet mapping
Install heavy UPS components low in the rack using the specified rails and handling guidance. Connect external batteries, network card and temperature sensors according to the model instructions. Allow batteries to charge before runtime acceptance when required.
Map every UPS and PDU outlet to the powered device and preserve A/B separation for dual-cord equipment. Avoid placing both supplies on the same failure domain unless that is the approved design. Label cords without blocking service or airflow.
Moving a running load onto new protected outlets is a one-cord-at-a-time job with a pause between each, and the picture of how the rack was corded beforehand is the record that lets a second technician put it back. Keep the original receptacle free until the outlet map has been verified against the devices.
- Rated rails and placement
- Battery/network accessories
- A/B outlet mapping
- Cord labels and airflow
| Layer | Acceptance | Evidence |
|---|---|---|
| Electrical | Correct source and ratings | Circuit record |
| Capacity | Load, margin and runtime | Load/runtime data |
| Distribution | Correct outlet and redundancy | Outlet map |
| Operations | Alerts, recovery and ownership | Scenario/handoff |
UPS, PDU, alarm and resilience tests
Verify normal state, input, output, battery, load, estimated runtime, self-test and alarms. Configure protected management addressing, time, users, certificates and notifications. Confirm alerts reach the people or systems expected to respond.
Test an approved input-loss or transfer scenario without risking production, and verify protected loads, event timing and recovery. Validate outlet control only on noncritical or authorized loads. Document bypass behavior and never operate unfamiliar maintenance bypass equipment as an improvised test.
Proof for this kind of commissioning lives in the event log and the notification inbox: the self-test result, the load reading at the time, and a test alert that someone confirms arriving. If a transfer test is declined or deferred, write that down as a known gap instead of leaving the record ambiguous.
- Status/self-test/runtime
- Management and alert delivery
- Approved transfer test
- Recovery and bypass boundaries
Closeout, maintenance and response ownership
Deliver model/serial, battery date, circuit, rack position, outlet map, load, runtime estimate, settings, firmware, tests and photographs. Store credentials and detailed power maps in the client-controlled repository.
Assign self-test review, battery health, environmental monitoring, firmware, alert escalation and replacement planning. Record safe shutdown and bypass contacts and use official manufacturer support for battery, firmware and lifecycle guidance.
The outlet map is what shows which loads are single-corded and therefore exposed when a circuit opens, which is why it sits in the client repository rather than a public page. Record the battery install date and the load at commissioning so a replacement can be planned from real numbers, and name whose inbox receives the alarms.
- Inventory/circuit/outlet map
- Battery and test record
- Maintenance schedule
- Named electrical/IT owners
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Verify the circuit
Confirm input circuit, breaker rating and available capacity with the electrician or facilities owner before equipment arrives.
Rack and map
Install the UPS and PDUs, then map each protected outlet to the equipment it actually feeds.
Test under load
Run transfer and battery tests only in scenarios the live environment can tolerate, with the owner present.
Route the alarms
Set network management, confirm alarms reach a monitored destination and name who responds to them.
Information to gather before design
Protected runtime depends on what the circuit can deliver, what the rack actually draws and who is allowed to respond when an alarm fires.
- Input circuit type and breaker rating
- Connected load per rack position
- Battery age and replacement history
- Redundant supplies needing separate feeds
- Alarm destination and after-hours responder
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Can a UPS be loaded to its full nameplate rating?
Design to the manufacturer limits and approved reserve, accounting for topology, runtime and load behavior.
Does a passed self-test prove required runtime?
No. Review battery state, actual load and an approved runtime method.
Should both server power supplies use one PDU?
Not when the design requires A/B redundancy across independent paths.
Who may work on fixed electrical circuits?
Only appropriately qualified and authorized personnel under applicable requirements.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Commissioning UPS and PDU capacity in your racks
A UPS is going in, or an old one is coming out, and someone has to say what stays up. Describe the racks, the circuits feeding them, the equipment on each and how alarms are monitored today.