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.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- 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.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- 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.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- 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.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- 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.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
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.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.