__MK__tabaqat · StrataEmergency Management
Lifelines — Community Lifelines, live

The status board
that reads the feeds.

All eight FEMA Community Lifelines on one board — colors suggested by live data, confirmed by your desk. Outage-to-asset fusion every 15 minutes. A cascade view for what fails next. And the Senior Leadership Brief writes itself.

Live demo on real California feeds · complements CLSS · no API keys
© 2026 Tabaqat · Built on Strata — sovereign geospatial applications.
You know this ritual

Every operational period, someone builds the SLB by hand.

Status arrives by phone call and email. Somebody types it into the slide. The colors reflect whatever the desk heard last — with no way to see how old any of it is. FEMA's own 2024 doctrine review asks the question out loud: what standard data should actually feed each lifeline's status?

Meanwhile the feeds already exist: statewide outage polygons refresh every 15 minutes, facility registries are public APIs, grid conditions are published — and none of it touches the board.

3capabilities missing from every tool we studied: feed-suggested colors · live outage-to-asset fusion · a cascade view

Reporting tools structure the workflow. Modeling firms left for insurance. The national asset portal retired in 2025. The intersection stayed empty.

The epistemic chip

Suggested by data. Confirmed by you.

  • Hollow chip = the feeds suggest it. Energy turns yellow when customer-out totals cross a documented threshold. Health turns yellow when facilities sit inside outage areas. Every rule is written down.
  • Solid chip = your desk confirmed it — attributed, timestamped, with the limiting factor. The command-authority workflow stays exactly where doctrine puts it: with people.
  • Honest gray: water-system and fuel status have no machine-readable feed anywhere — so those lifelines say "needs report" instead of faking green. The board never pretends.
THE LEDGER
⚡ Energy YELLOW
suggested: 61k customers out
✚ Health & Medical GREEN
confirmed by Lifelines Desk · 12m ago
▢ Water Systems GRAY
no feed — needs report
Outage × assets, every 15 minutes

Which hospitals are dark right now?

  • The statewide outage feed refreshes every 15 minutes; the board joins it against the real registries — power plants, healthcare facilities, shelters, fire stations.
  • Affected assets light up on the map with orange halos; the fusion strip counts them per lifeline; suggested colors recompute automatically.
  • Scope statewide, or to the view you're looking at — the numbers follow.
15mthe refresh cycle from utility outage polygon to a recomputed lifeline color on your board

The question your desk answers by phone today, answered by geometry — with the phone call reserved for confirming it.

What fails next

Click the outage. See the cascade.

Downstream, typed

Power → water systems de-energized → facilities on those systems → shelters. Dependency arcs draw on the map; the lens lists every impact.

Confidence-tagged

Every edge says what it is: "geographic — high" or "heuristic — medium." Until utility topology is connected, the lens says so — labeled inference, never fake certainty.

What-if mode

No outage yet? Sketch a hazard area — the same cascade computes for the earthquake or storm you're planning against.

The analysis that lives in consulting PDFs today, running live on the board — and honest about its limits.

The briefing writes itself

One click. The FEMA grid. Zero re-typing.

  • Generated SLB: the familiar lifeline grid — colors, suggested-vs-confirmed marked, limiting factors, fusion counts — rendered from live state, every cycle.
  • Feed vintages printed on the brief: leadership sees not just the colors but how fresh each underlying feed was. Accountability travels with the slide.
  • CLSS-compatible by design: this board feeds your reporting workflow, it doesn't fight it.
0minutes re-typing status into slides — the SLB is a projection of the board, not a parallel document

⚡ YELLOW (suggested) — 61k customers out
✚ GREEN (confirmed · Lifelines Desk)
▢ GRAY — needs report
Feed vintages: outages 4m · registries static · archive labeled

Proof, not promises

Running on live, verified California feeds.

Board elementLive source
Outage areas (the fusion feed)Cal OES statewide feed — 15-minute refresh
Power plants · transmissionCalifornia Energy Commission
3,319 healthcare facilitiesCA Dept. of Health Care Access & Information
Drinking-water system areasState Water Board (SABL)
Shelters · fire & rescueCal OES
National fallback registriesHIFLD archive mirror — vintage labeled

186 lifeline services classified from a 2,339-service state inventory — every endpoint verified before it entered the catalog. Re-pointing to your state is configuration, not development.

For EM directors & lifelines desks

Doctrine-native. Sovereign. Deployable now.

  • Speaks FEMA: the 8 lifelines, the colors, the SLB grid — your staff needs no retraining.
  • Complements CLSS and your existing WebEOC/alerting stack — this is the data layer under the reporting, not a replacement.
  • On your servers, behind your SSO; open basemaps, no per-seat map licences; bilingual-ready (EN/AR incl. RTL); wall-mode for the EOC floor.
  • Honest by construction: hollow vs solid chips, gray where no feed exists, confidence tags on every cascade edge, vintages on every brief.
8lifelines, one board — with the answer to FEMA's own question: this is the data that feeds the colors

Your desk confirms instead of collects. Your leadership reads freshness, not hope. Your after-action starts from evidence.

See it live

Click the outage.
Watch the cascade.

Open the demo, click a live outage polygon, and watch the dependency arcs draw — then press Generate SLB and hand leadership a brief nobody typed.

tabaqat.net → Solutions → Lifelines info@tabaqat.net
© 2026 Tabaqat · Demo: live Cal OES/CEC/HCAI/SWRCB feeds · confirm-writes and cascade labeled per scope · FEMA® terms used nominatively.
1 / 9