Whether the UPS will actually bridge the transfer when the primary source fails: battery-bank health and capacity versus nominal, state of charge, estimated autonomy minutes, transfer-to-battery events, and the last discharge-test result. A UPS looks fine on its panel right up to the moment a tired battery bank collapses under load — this metric surfaces the fade, the on-battery and bypass events, and the failed self-test before the outage that would expose them.
Whether a UPS is ready to carry its load through a transfer — the readiness of the battery bank behind it, not just the "online" light on the front. It combines battery capacity versus nominal, state of charge, estimated autonomy at load, the record of transfer-to-battery and bypass events, and the last discharge-test result into a single readiness view, so a bank silently fading toward collapse is visible long before it fails under load.
Battery capacity vs nominal — the bank's present usable capacity as a percentage of its rated capacity, tracked over time so age- and cycling-driven fade is a trend, not a surprise.
State of charge and autonomy minutes — the present charge and the estimated minutes the bank can hold the load, recomputed at the current load.
Transfer and bypass events — each transfer to battery and each move to bypass is logged; frequent unexplained transfers or time on bypass are readiness faults even while the UPS reports online.
Last discharge-test result — the outcome and date of the most recent battery self-test / discharge test; a failed or overdue test drops the UPS out of ready.
Read-only. Keedian surfaces the fading bank, the bypass events, or the failed test; battery replacement and UPS service stay with the electrical / power vendor.
| Range | Classification | Interpretation |
|---|---|---|
| Capacity near nominal, SoC full, autonomy at target, last test passed, no unexplained bypass | Ready — bridge intact | The UPS is positioned to bridge the transfer to the generator for its designed time. |
| Capacity fading below band, autonomy short, an overdue test, or recurring on-battery / bypass events | Degraded — bridge thinning | The UPS still shows online, but the battery bridge is shorter or less certain than designed; scope a battery service or test with the vendor. |
| Capacity well below nominal, a failed discharge test, or the UPS stuck on bypass | Not ready — bridge at risk | The UPS may not carry the load through a transfer; refer to the vendor out of cycle. |
Reference bands only. Nominal capacity, the acceptable fade band, and the discharge-test regime differ by UPS make, battery chemistry, and age. Confirm them per UPS before reporting readiness, so a bank at expected end-of-warranty capacity is not scored the same as one failing early.
The target is every critical-load UPS ready — capacity within its agreed band, autonomy at or above the required bridge time, a passed and in-date discharge test, and no unexplained bypass. Agree the capacity band and test cadence per UPS; a failed test or a stuck-bypass state is a not-ready fault, not a tolerance.
The table below shows how moving UPS Battery Readiness impacts each customer value driver the product is designed to improve — the metric page explains the mechanism; the product pages express the magnitude.
| Value driver | Impact strength | How UPS Battery Readiness moves this lever |
|---|---|---|
| Operational continuity | Direct, primary | The UPS bridge is the first and most time-critical leg of the ride-through — if the battery bank collapses under load, the transfer to the generator never completes cleanly. Surfacing the fade, the failed test, and the bypass events turns a silent UPS failure into a scoped battery service done ahead of need. Per-building magnitude is expected (pending validation) — offices have no named Keedian reference deployment yet. |
| Asset lifespan | Direct | Battery banks fade predictably with age and cycling; tracking capacity as a trend lets the vendor replace a bank on a plan at end of usable life rather than after it fails, and catches an early-failing string before it takes the rest of the bank with it. |
The table below summarizes the alarms that fire directly from UPS Battery Readiness. Each row links to the full operational detail (trigger, preconditions, action plan, human role, escalation, prevention) in the SOPs catalog.
| Alarm | Description | Severity | Tier | AI executes? | Value drivers | SOP |
|---|---|---|---|---|---|---|
| UPS battery capacity low | A UPS battery bank's usable capacity has faded below its agreed band — an aging bank whose bridge is thinning, even while the UPS still shows online. Read-only: Keedian surfaces the fade against nominal and refers the battery service to the customer's electrical / power vendor. | High | Essential | Hybrid | Operational continuity · Asset lifespan | Open SOP → |
| UPS on bypass | A UPS has moved to bypass — the load is running unprotected on raw utility and the battery bridge is gone right now. Read-only: Keedian surfaces the bypass event and refers restoration to the customer's electrical / power vendor; the UPS is not commanded off bypass. | Urgent | Essential | Hybrid | Operational continuity | Open SOP → |
More alarms in development (single-metric): a capacity-fade projection that schedules a battery replacement ahead of the readiness threshold, and a discharge-test-due reminder tied to the agreed cadence. Composite alarms that combine UPS readiness with backup autonomy and continuity posture will appear in a future release.
The action plan for each alarm lives on its own SOP page in the SOPs catalog — with the diagnostic steps, human role, value drivers, escalation, and prevention specific to that alarm. The list below maps each alarm to its SOP.
Battery readiness is read from the UPS interface; Keedian does not replace batteries, run the discharge test, or take the UPS off bypass. When a readiness fault surfaces, Keedian reports which UPS, which signal (capacity, test, bypass), and since when, and hands it to the electrical / power vendor with a recommended action. Do not report a UPS as not-ready on a reading that traces to a stale or mis-mapped point before the mapping is confirmed.
Rated capacity, the acceptable fade band, and the discharge-test cadence depend on the UPS make, battery chemistry, and age. Confirm them per UPS at onboarding so a bank at expected end-of-warranty capacity is not alarmed like one failing early, and an in-warranty test schedule is reported against the right cadence.
Per-alarm escalation criteria live in the Escalation block of each SOP in the SOPs catalog. The patterns below are metric-level — read from the portfolio view, not from any single alarm firing.