Estimated ride-through time for a building's critical load if the primary source fails now — the UPS bridges the transfer on battery, then the standby generator carries the load while fuel lasts. It answers "for how long?", the second half of the readiness question posture answers with "yes or no". A shrinking estimate — an aging battery bank, a low fuel tank — is a continuity risk building silently. Compared against the building's agreed minimum autonomy.
The estimated time a building's critical load can run on backup if the primary source fails right now — the UPS's battery bridge through the transfer, followed by the generator's run-time on its available fuel. It quantifies the depth of the building's cover, so a slowly shrinking autonomy (a battery bank losing capacity, a fuel tank drawn down and not refilled) is visible as a trend rather than discovered as a too-short ride-through during the outage.
The UPS bridge is estimated from battery state of charge and the bank's measured autonomy at the present load — the minutes the UPS can hold the load through the transfer to the generator.
The generator leg is estimated from usable fuel volume and the consumption rate at the present load — the hours the generator can carry the load once running.
Both legs move with load and asset health — a heavier load or an aged battery shortens the bridge; a lower tank shortens the generator leg. The estimate is recomputed as those inputs change.
Read-only estimate. Keedian surfaces autonomy below the agreed minimum and the reason (battery capacity vs fuel); refuelling, battery replacement, and load management stay with the customer and the electrical / power vendor.
| Range | Classification | Interpretation |
|---|---|---|
| Estimated autonomy at or above the building's agreed minimum, both legs healthy | Ready — cover adequate | The UPS bridge and generator leg together meet the building's continuity requirement at the present load. |
| Autonomy within margin of the minimum, or one leg degraded (battery capacity down, fuel low) | Degraded — cover thinning | Ride-through is shorter than designed; scope the failing leg (battery service or refuelling) before the margin is needed. |
| Estimated autonomy below the agreed minimum | Below minimum — exposed | The building cannot ride through for its required time; refer to the vendor out of cycle. |
Reference bands only. The minimum required autonomy — how long the building must ride through — is a per-building decision driven by the load and the expected restoration time. Set and agree the minimum per building before reporting against it.
The target is estimated autonomy at or above the building's agreed minimum ride-through time, at the present load, with neither leg (UPS battery, generator fuel) degraded. Agree the minimum per building; a below-minimum estimate is an exposure, not a tolerance band.
The table below shows how moving Backup Autonomy 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 Backup Autonomy moves this lever |
|---|---|---|
| Operational continuity | Direct, primary | Autonomy is the depth of the building's cover — how long it actually rides through, not just whether backup starts. Surfacing a shrinking estimate turns a too-short ride-through from something discovered mid-outage into a scoped battery-service or refuelling item done ahead of need. Per-building magnitude is expected (pending validation) — offices have no named Keedian reference deployment yet. |
The table below summarizes the alarms that fire directly from Backup Autonomy. 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 |
|---|---|---|---|---|---|---|
| Backup autonomy below minimum | Estimated ride-through — the UPS battery bridge plus the generator's run-time on available fuel — falls below the building's agreed minimum at the present load. If the grid fails now, backup does not cover the outage to restoration. Read-only: Keedian surfaces the shortfall and the leg responsible and refers it to the customer and the electrical / power vendor. | High | Managed | Hybrid | Operational continuity | Open SOP → |
| Generator fuel low | Usable fuel has been drawn down so the standby generator's run-time falls under the building's required autonomy — the generator leg of the ride-through is short even if the UPS bridge is intact. Read-only: Keedian surfaces the run-time shortfall and refers refuelling to the customer and the electrical / power vendor. | High | Managed | Hybrid | Operational continuity | Open SOP → |
More alarms in development (single-metric): a battery-capacity-fade trend that projects when a UPS bank will fall below the minimum bridge, and a fuel-burn-rate watch. Composite alarms combining autonomy with posture and the primary-source state — to prioritise the buildings both shortest on cover and most likely to need it — 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.
Autonomy is an estimate from battery and fuel state; Keedian does not refuel, replace batteries, or shed load. When the estimate drops below the agreed minimum, Keedian surfaces which leg is short and by how much, and hands it to the customer and the electrical / power vendor with a recommended action. Treat the number as a live estimate, not a guarantee — it moves with load and asset health.
The required ride-through time is per-building, driven by the critical load and the expected restoration time. Agree the minimum autonomy with the customer at onboarding so the estimate is reported against the building's real requirement, not a default, and a building with a deliberately short bridge is not flagged as exposed.
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.