Modular vs monolithic UPS: compare growth, redundancy and service

Ask what is modular in the offered configuration

The word modular can refer to power conversion, batteries or replaceable assemblies. Ask the bidder to identify which parts are modular, what can be expanded and which components the modules share. A brochure label cannot answer those questions for the final bill of materials.

Manufacturer guidance distinguishes module-based arrangements from paralleling complete UPS units. Schneider Electric discusses both as ways of implementing N+1. This is why the comparison should be between proposed systems serving the same requirement, rather than between labels that hide different installed capacities.

Sources: Eaton: Modular UPS technology ↗ · Schneider Electric: Cost, speed, and reliability tradeoffs between N+1 UPS configurations ↗

Separate growth capacity from redundant capacity

Consider a hypothetical arrangement of four 25 kW power modules. The arithmetic total is 100 kW. If the design requirement is to remain within the remaining modules’ capacity after one module is unavailable, the remaining arithmetic capacity is 75 kW. Whether that arrangement meets an actual requirement also depends on kVA, derating, overload behavior and the complete system design.

At a 60 kW load, three such modules are needed by kW arithmetic, with the fourth providing one additional module. At a 90 kW load, all four are needed; the same installed hardware no longer has one extra module by that arithmetic. This explains why a growth plan should show the failure-state capacity as well as the normal-state total. It is not an engineering approval for a 60 kW installation.

Do not confuse space for future modules with installed capacity. Ask the vendor to distinguish frame limit, installed modules, commissioned capacity and the amount remaining in the specified failure or maintenance state. Put those values in separate columns of the proposal.

Examine what the modules share

An N+1 power-module arrangement does not by itself describe the whole electrical path. Eaton documents a modular architecture with a common static bypass, illustrating that a system can contain both repeated power modules and shared components. Architecture varies, so request the actual diagram rather than transferring an assumption between product families.

Use a failure-state review with the design team. For each component or path the team identifies as relevant, record the proposed operating outcome and the evidence behind it. Asking what happens during a module outage is useful; asking what happens during service of a shared component may expose a different requirement.

The purpose is not to reject every shared component. It is to make the resilience boundary explicit. Two offers should be compared against the same agreed events so that a broad availability claim does not substitute for a documented operating result.

Sources: Eaton 93PM UPS: Modularity and resiliency ↗

Compare architecture against the way the site will operate

Use this decision matrix to organize supplier discussions. Neither column is a universal winner. For each row, ask bidders to describe the exact system they propose and attach the documentation that supports it.

Translate serviceability claims into a documented outcome

Vertiv describes serviceability and expansion as potential benefits of modular designs. For purchasing, convert that broad benefit into questions: which component is being serviced, who is authorized to perform the procedure, what operating state is required, and what protection remains throughout?

A claim that a component is hot-swappable does not authorize an owner to remove it from a live installation. Request the manufacturer’s procedure and have the responsible service team assess the actual site. Keep this separate from an emergency response-time commitment; a replaceable module is not evidence that a technician and compatible replacement will be locally available.

Ask bidders to state spare-part arrangements, service coverage and what happens if a module is unavailable for longer than expected. Do not assign a repair time from a marketing headline to your financial model without a contractual basis and an explanation of its assumptions.

Sources: Vertiv: The power of modularity in UPS systems ↗

• Review UPS service contract questions ↗

Model the expansion decision instead of assuming modular wins

Build at least two purchasing scenarios: growth occurs as planned, and growth is delayed. Record initial equipment, installation, the next capacity addition, service and the assumptions behind each line. Ask the bidder to explain any dependencies on future hardware availability or compatibility.

For example, a business expecting an additional workload in year three can request a priced expansion scope and a clear validity period today. That quote is evidence of the current offer, not a guarantee that the same parts and prices will exist in three years. Give uncertain future costs their own sensitivity case.

Use the same delivered load and approved operating mode for the efficiency comparison. Finish by recording why the selected architecture best satisfies the agreed growth and service requirements, which assumptions remain open, and who owns the next review.

• Build a consistent efficiency cost comparison ↗

Common questions