RELIABILITY ENGINEERING

Data center power loss event tree

A data center power loss event tree explains how backup power barriers work together after the utility supply fails. The UPS must carry the critical load long enough for the generator to start, and the transfer switch must then connect the standby source. If every barrier succeeds, service continues. If a barrier fails, the tree shows the interruption or outage path clearly. Facilities managers and reliability engineers can use this form to communicate the logic of a power-continuity design before building a more detailed reliability model. The frequencies in this example are illustrative. Use outage records, maintenance data, tested transfer times and the actual topology of the site when calculating risk or availability.

UPDATED 2026-09-24
EXAMPLEData center power loss event tree
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

A facilities team needs to explain the continuity path following a utility outage.

Key decisions

  • Ride-through first: The UPS bridges the interval before standby power is available.
  • Standby source second: Generator start is evaluated only if the UPS holds the load.
  • Transfer last: The switch must complete the connection to preserve service.

When to reuse this

Use for a simple continuity discussion of one standby-power path; represent redundant paths separately when needed.

FAQ

Frequently asked questions

Why is the UPS the first barrier?01
It provides immediate ride-through while the generator starts and the transfer switch operates.
Does this replace an availability model?02
No. It is a clear consequence model that can inform, but does not replace, a detailed availability analysis.
Can an event tree show redundant generators?03
Yes. Add the generator paths as ordered barrier functions that reflect the actual switching design.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.