UPS Runtime, Load Testing and Commissioning

1. Define the acceptance objective

Decide whether you are proving basic operation, estimated runtime, graceful shutdown, bypass operation or a full battery discharge. These are different tests with different risk.

2. Measure the connected load

Record watts/VA/load percentage from the UPS and compare to the design. Include PoE loads and redundant-PSU failure scenarios where relevant.

3. Confirm battery charge and health

Do not start a battery-dependent test with an unresolved battery alarm or incomplete charge unless the manufacturer procedure specifically calls for it.

4. Test alarms and monitoring

Verify mains-fail, battery, overload and other supported alarms through the network card/software where safe. Confirm time, SNMP/email destinations and event logging.

5. Test graceful shutdown separately

For servers/NAS, prove the shutdown agent can communicate with the UPS and that the shutdown timing matches the required runtime reserve.

6. Use runtime calibration only for a reason

Schneider states calibration deliberately discharges the battery and can reduce available protection until recharge. It should not be a casual commissioning ritual.

7. If a controlled battery test is required

Use non-critical load or an approved maintenance window, follow the model procedure and define abort conditions. Never create a surprise production outage to see how long it lasts.

8. Observe recharge

After battery operation, confirm the UPS returns online, begins charging, alarms clear as expected and the site understands reduced protection during recharge.

9. Record baseline

Capture load, battery charge, estimated runtime, firmware, battery date, test results and monitoring configuration. This baseline is valuable for later battery degradation analysis.

Worked field scenario

A new UPS shows 45 minutes estimated runtime at a light commissioning load, but production will add PoE switches and servers. Record the real design load and validate shutdown timing against that load rather than treating the initial display as guaranteed runtime.

Procurement questions before ordering

The ordering stage is where many field problems are created. Capture the following before selecting the exact product:

• Load in watts and VA where available
• UPS topology and rated output
• Battery type, age and external packs
• Input/output plug or hardwire arrangement
• Shutdown, monitoring and bypass requirements

Where a manufacturer compatibility list, rail matrix, supported-optics table or battery cartridge reference exists, record the exact source used for the decision. That gives the later installer evidence rather than a verbal assumption.

Fault-finding decision path

Start with the UPS event log and operating state. Separate utility/input problems, overload, battery health, charger faults, bypass conditions and downstream load issues. Compare current load and runtime to the commissioned baseline before deciding the battery or UPS is undersized.

Keep a simple change log while troubleshooting: observation, action, result. If a change does not alter the symptom, put the system back unless there is a documented reason to retain it. This prevents troubleshooting from becoming an uncontrolled configuration drift.

Common mistakes that create repeat faults

Do not pull utility power as an improvised battery test on critical equipment. Do not perform repeated runtime calibrations as routine maintenance. Do not operate hardwired bypass switching without the approved procedure and competent electrical personnel.

A technically successful installation can still be a poor operational result if the next technician cannot identify what was installed, why it was selected, or how it was tested. Serviceability is part of infrastructure quality.

Acceptance and handover evidence

Record UPS model/serial, firmware, battery date, load, estimated runtime, self-test state, monitoring addresses and shutdown configuration. Keep the one-line power path and bypass procedure with the handover documentation.

Use filenames, labels and port/bay identifiers that match the physical installation. Handover evidence should let someone who was not present at the installation verify the final state and repeat the important tests later.