The building's electrical-continuity rollup: the share of critical backup points that are both ready and have their redundancy available right now — a UPS on line with a healthy battery, a generator in AUTO with fuel and a good last test, the ATS armed to transfer. A point that is degraded, in a fault or bypass state, or has lost its redundancy drops out of posture. It answers the one question backup exists for: if the primary source fails this minute, does the backup take the load? Target 100% of critical points ready.
The share of a building's critical electrical-backup points that are ready to carry the load and still hold their designed redundancy, measured continuously. It is a readiness rollup — a posture signal about whether backup will work when called — not a "broken now" alarm. A backup point that has failed silently (a dead UPS string, a generator left in MANUAL, an ATS in a fault) shows here as not-ready long before the outage that would otherwise expose it.
Each critical backup point is classified ready, degraded, or not-ready from its own readiness signals — a UPS from battery health and mode, a generator from AUTO mode, start battery, fuel, and last test, an ATS from its armed / fault state.
A point is ready only when it is operable AND its designed redundancy is available. A UPS running on its last good string, or an N+1 set reduced to N, is reported degraded — operable but with no margin — rather than counted as ready.
continuity_posture = count(points ready) / count(critical points) × 100, with the degraded and not-ready points listed by name so the gap is actionable rather than a bare percentage.
Read-only. Keedian rolls up the state and surfaces the not-ready and degraded points; energizing, repairing, or servicing the assets stays with the customer's electrical / power vendor.
| Range | Classification | Interpretation |
|---|---|---|
| 100% of critical points ready, redundancy intact | Ready — full posture | Every critical backup point is operable with its designed redundancy available; the building is positioned to ride through a primary-source failure. |
| One or more points degraded (operable, no redundancy) or a non-critical point not-ready | Degraded — margin lost | Backup would still take the load, but a second fault would not be covered; scope the degraded point with the electrical / power vendor before the margin is needed. |
| A critical point not-ready | Not ready — exposed | A critical load has no working backup; the next primary-source failure is uncovered. Refer to the vendor out of cycle. |
Reference bands only. Which points are "critical" and what redundancy each is designed to hold is a per-building decision — confirm the critical-point list and the redundancy design with the customer before reporting posture against it.
The target is 100% of critical backup points ready with redundancy intact. Because backup only matters at the moment of failure, there is no acceptable steady-state count of not-ready critical points; a degraded (no-margin) point is tolerable only as a scoped, time-boxed item with the vendor.
The table below shows how moving Continuity Posture 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 Continuity Posture moves this lever |
|---|---|---|
| Operational continuity | Direct, primary | Posture is the single readiness number for whether the building rides through a primary-source failure. Every not-ready critical point it surfaces is an outage that would otherwise have been discovered during the event it was meant to cover. Per-building magnitude is expected (pending validation) — offices have no named Keedian reference deployment yet. |
| Asset lifespan | Indirect | A point that keeps dropping to degraded — a UPS repeatedly down to its last string, a generator that fails its test — is an asset aging toward failure in the open. Surfacing the pattern lets the vendor replace or service the asset on a plan rather than after it fails under load. |
The table below summarizes the alarms that fire directly from Continuity Posture. 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 redundancy lost | A critical backup point drops from ready — it loses the designed redundancy it was built to hold (N+1, a dual feed, or a backup unit). The severe end of the same alarm is the point going fully not-ready. Read-only: Keedian surfaces which point lost its margin and refers the correction to the customer's electrical / power vendor. | Urgent | Essential | Hybrid | Operational continuity · Asset lifespan | Open SOP → |
More alarms in development (single-metric): a posture-erosion watch that flags a building losing redundancy across several points before any goes not-ready. Composite alarms that combine posture with backup autonomy and the primary-source state — to separate a building that is merely degraded from one about to be exposed — 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.
Posture is rolled up from the backup points' readiness states; Keedian does not energize, repair, or service any asset. When a point drops to degraded or not-ready, Keedian surfaces which point, why, and since when, and hands it to the customer's electrical / power vendor with a recommended action. Do not report a building as exposed on a reading that traces to a stale or mis-mapped point before the point mapping is confirmed.
Which backup points are critical, and what redundancy each is designed to hold, differs per building. Confirm the critical-point list and the redundancy design at onboarding so a point that a building never had is not scored as a gap, and a single-corded load is not reported as having lost redundancy it never had.
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.