Topology
2N, N+1 and distributed redundancy — as statements you can test
Redundancy labels are shorthand for a promise about what the facility survives. The label is worth exactly as much as the drawing behind it, and the arithmetic that checks the label is not the arithmetic most people use.
The configurations, stated as what they survive
| Label | Capacity | What it survives | What it does not |
|---|---|---|---|
| N | Exactly the load | Nothing. Any component out is load lost. | Maintenance without a shutdown. |
| N+1 | One spare unit | One unit out — failed or on maintenance — with the load still carried. | A fault on the distribution path the units share. One bus, one failure. |
| 2N | Two complete systems | Loss of an entire system, including its distribution path. | Maintenance on one system while a component on the other fails, unless each side is itself N+1. |
| 2(N+1) | Two systems, each with a spare | A whole system lost and a unit out on the surviving side. | Little, electrically. The cost is the objection, not the topology. |
| 3N/2, 4N/3 (distributed) | Several systems sharing dual-corded load | One system out, with the remaining systems picking up its share — if the paths allow it. | Being checked by adding capacity up. See below. |
Two different promises, often confused
Redundancy labels answer one question; the design brief usually asks two.
- Concurrent maintainability — every capacity component and every element of the distribution path can be removed from service on a planned basis without touching the critical load. This is a statement about one component at a time, chosen by you, at a time of your choosing.
- Fault tolerance — the facility survives a single unplanned failure anywhere, including during maintenance, without touching the critical load. The event is not chosen by you and the timing is not either.
N+1 on its own buys the first and not the second: the spare unit covers the unit, but the bus they share is still one failure. This is the single most common gap between what a brief asks for and what a drawing delivers.
The arithmetic mistake in a distributed plant
Take four generator sets of 2,000 kW carrying 6,000 kW of load — a 4N/3 arrangement. The familiar check is pooled: total capacity 8,000 kW, lose one set, 6,000 kW remains, load is 6,000 kW, so it holds.
That check is only valid if every remaining set can actually reach every part of the load. In a distributed plant it usually cannot. The sets do not share one bus; each feeds a subset of the boards, and the dual-corded loads are split between them in a pattern the drawing fixes. When one set is lost, its share does not spread evenly across the other three — it lands on the specific sets that share its loads.
| Check | GEN-A lost | Verdict |
|---|---|---|
| Pooled capacity | 6,000 kW available vs 6,000 kW load | Passes, at 100 % of remaining capacity |
| On the drawn paths | GEN-B takes 2,310 kW, GEN-C 1,950 kW, GEN-D 1,740 kW | GEN-B is above its 2,000 kW rating — it trips, and the case cascades |
Both rows describe the same plant. The first is a sum; the second is the drawing. Only the second is a design check.
What to ask of any redundancy claim
- Which components are counted as N, and at what load? A claim without a load is not a claim.
- Is the spare on the same bus as the units it covers? If yes, the bus is the limit, not the spare.
- Does the claim hold during maintenance, or only when everything else is healthy?
- In a distributed plant: with each source lost in turn, what does every remaining source carry?
- Does cooling carry the same label as power? A 2N electrical plant in front of an N chilled-water plant is an N facility.
Where cooling usually breaks the claim
Power is drawn, reviewed and argued about; cooling is often labelled by unit count alone. The questions that decide it are the same ones: can a chiller, a pump and a room unit each be taken out on a planned basis with the load carried? And if continuous cooling is claimed, are the chilled-water pumps on uninterruptible power — or is there a thermal store sized for the chiller restart? Room units on a UPS while the pumps are on the generator is not continuous cooling.
Check the label against the drawing
Data Center Simulator reads the redundancy configuration from the single line you drew rather than from a field you filled in, and tests it by losing each source in turn and following the load along the paths that exist. Every source reports what it carries, in kW and as a percentage of its rating, and a source held above its rating trips — the same way it would on site.
Download the free trial How topology is assessed