Skip to content

The platform

The platform, mapped to what you have to answer for.

Venue operators and risk managers don't buy features — they buy answers to four questions. Here is how Alpha Command answers each one, with capabilities that are live today.

Concern 01“Can I prove who did what, and how fast?”

Yes — accountability is the substrate, not a report you assemble after. Access is per-person and authenticated, every action is attributed, and the dispatch loop times itself.

Per-person authenticated access with full audit attribution on every action Per-person access authenticated named identity role-scoped access Audit trail every action · attributed 09:41:02 J. Rivera assigned case → Gate 3 09:41:14 M. Chen acknowledged 09:43:50 M. Chen on scene 09:52:11 M. Chen resolved 10:03:27 Command board note added 10:07:09 A. Patel care center staffed Immutable, timestamped, who-did-what — no anonymous actions. (Names illustrative.)

Product illustration — attribution trail. Names are illustrative.

Accountability & audit

Every action tied to a named person.

There are no anonymous actions in Alpha Command. Access is per-person and authenticated, and every assignment, acknowledgement, status change, and note is attributed and timestamped.

  • Per-person authenticated access with role-scoped permissions
  • Full audit attribution — who did what, when
  • The record is built as the event runs, not reconstructed later
The closed dispatch loop: assign, phone alert, acknowledge, en route, on scene, back to the live board Live Board assign phonealert acknowledge en route /on scene resolve /update Every status change is timestamped, attributed, and reflected on the board in real time.

Product illustration of the closed dispatch loop.

Measured response

A dispatch loop that closes and times itself.

Assign a case, the provider's phone alerts, and each step — acknowledge, en route, on scene — returns to the live board. Because the loop closes, response times are measured, not estimated.

  • Assign → phone alert → acknowledge → en route → on scene
  • Timestamps at each transition feed response-time reporting
  • Nothing is left as an open radio call
Concern 02“What happens to patient data?”

The operational layer everyone uses carries no PHI at all. Protected health information is handled by a separate, HIPAA-grade datastore architecture designed with a signed-BAA path.

Privacy-by-default architecture: no PHI on the operational layer, separate HIPAA-grade PHI datastore behind a signed-BAA path Operational layer no PHI PT-7Q2 · trackedpseudonymous token only Care center · time · statusoperational facts, not identity Board · dispatch · AVLruns entirely PHI-free what every operator sees signed-BAA path PHI datastore HIPAA-grade, by design separate · access-controlled designed for a signed BAA

Product illustration of the privacy-by-default architecture.

Privacy by default

No PHI on the layer everyone touches.

The live board, the map, dispatch, and scan-to-track run on pseudonymous tokens and operational facts — care center, time, status. Protected health information lives in a separate datastore architected to HIPAA-grade standards, with a signed-BAA path for clients who need it.

  • No PHI on the operational layer — privacy is the default, not a setting
  • HIPAA-grade PHI datastore architecture, separated by design
  • Designed with a signed-BAA path
Concern 03“Are you ready when the weather or the crowd turns?”

Weather and heat are part of the operating picture, and a configurable alert engine watches for the conditions that precede a bad day. The workflow is engineered and tested for mass-gathering surge.

Weather, WBGT heat index, radar, and NWS alerts integrated into the operating picture WBGT heat 84° flag: yellow activity guidance by threshold Radar ! NWS alert Heat advisory · zone active auto-surfaced to command Conditions Temp91°F Humidity63% Wind12 mph Lightningnone SourceNWS feeds the alert engine

Product illustration — weather, WBGT, radar & NWS. Values illustrative.

Weather & heat

Heat and weather, on the same screen as the medicine.

WBGT heat index, radar, and National Weather Service alerts are integrated into the operating picture — so a rising heat flag or an incoming cell is something command sees, not something someone remembers to check.

  • WBGT / heat index with threshold guidance
  • Radar and NWS alerts surfaced to command automatically
  • Conditions feed the alert engine directly
Configurable real-time alert engine watching for surge, heat, severe weather, and response timeouts Signals in Case surge rate WBGT / heat Severe weather Response timeout Rule engine thresholds you configure Actions out Notify roleson-shift, by scope Escalateto command Real-time, configurable — surge, heat, severe weather, and response timeouts. Thresholds are set per event; nothing is hard-coded.

Product illustration of the configurable alert engine.

Alert engine

Configurable alerts for the things that matter.

Set thresholds per event and the engine watches in real time — case surge, heat, severe weather, and response timeouts — routing alerts to the right roles and escalating to command. The whole workflow is engineered and tested for mass-gathering surge.

  • Real-time rules for surge, heat, severe weather, and response timeouts
  • Thresholds configured per event — nothing hard-coded
  • Engineered and tested for mass-gathering surge
Concern 04“What do I have to show for it afterward?”

After every event, an automatic, zero-PHI after-action report with response-time percentiles — the evidence a risk manager needs, generated without extra work.

Illustrative layout of the automated, zero-PHI after-action report with response-time percentiles After-Action Report Event ____ · Date ____ · generated automatically zero-PHI Total encounters Median response Transports Response-time percentiles p50 p75 p90 p95 Sections Executive summary Encounter overview Response times By care center Weather & alerts Timeline & audit Illustrative layout — not real event data.

Illustrative report layout — not real event data.

After-action evidence

The event, documented — automatically.

Close the event and the after-action report is generated for you: encounter overview, response-time percentiles, breakdowns by care center, and the weather and alert context — all zero-PHI, ready to share with stakeholders.

  • Automatic generation — no manual assembly
  • Response-time percentiles from the closed dispatch loop
  • Zero-PHI by construction, safe to distribute

Answer all four in one walkthrough.

We'll show accountability, privacy, readiness, and the after-action evidence on a live operating picture.