Operations status

Manager view

Synthetic: modeled for the demo, not response guidance Real public data, source named (NASA EONET)

Read-only status across every incident: what is blocked, who owns what, how threatening incidents are resourced in the model, and which decisions were recorded. Only the EONET incident records are real; simulated incidents and every other figure are modeled for the demo, not response guidance.

All incidents

Whole-picture totals. Filters never change them.

Incidents Real: EONET, retrieved 2026-10-25Definition: IncidentsEvery incident: the cached NASA EONET snapshot plus any simulated demo incidents. With EONET incidents only, the count is real; once a simulated incident is added, the count is marked modeled. Everything else on this view is modeled.: 20; EONET snapshot 2026-10-25
Incidents threatening modeled communities SyntheticDefinition: Incidents threatening modeled communitiesIncidents with at least one modeled community inside the threat radius for their modeled severity (low 8 km, moderate 12 km, high 16 km).: 2 of 20
Unaddressed threats SyntheticDefinition: Unaddressed threatsIncidents that threaten modeled communities and have no team assigned.: 1 of 2; listed under Blockers
Teams assigned SyntheticDefinition: Teams assignedTeams with an incident, of all teams. Every team is counted once.: 1 of 5
Personnel demand met SyntheticDefinition: Personnel demand metFor each fire that threatens a modeled community, assigned personnel capped at its modeled demand, summed, of total modeled demand (ceil(threatened population / 1000 x severity rate 1, 1.5 or 2), as the decision engine computes it).: 15 of 70
Communities with demand fully met SyntheticDefinition: Communities with demand fully metModeled communities where every threatening fire has assigned capacity at or above its modeled demand, of all modeled communities (threatened or not).: 0 of 6
Open tickets SyntheticDefinition: Open ticketsTickets not closed. This demo has no close action, so every ticket counts. A ticket is created, as accepted, when someone takes ownership of an incident; each incident has at most one.: 0; none accepted yet
Decisions logged SyntheticDefinition: Decisions loggedAudit records written by approvePlan and assignTeam since the last demo reset. Incident acceptances, simulated incidents and demo resets are counted separately and are not decisions.: 0; since the seed

Showing all 20 incidents.

Blockers

What stands between the modeled demand and the teams available, most direct first.

Wildfire NORTEUnaddressed
No team assigned; 15,500 people in the threat radius, modeled demand 16 personnel.

Personnel shortfall: at least 10Definition: Personnel shortfallTotal modeled demand minus the personnel on all teams, when positive: the minimum shortfall under any allocation, even with every team assigned (not the current unmet demand).

60 personnel on all teams against 70 modeled demand. No allocation closes this gap, so it stays listed after any approval.

Needs an owner

Definition: Needs an ownerIncidents with no ticket that threaten a modeled community, plus every simulated demo incident, in priority order. Other EONET incidents with no ticket are not listed.

Incidents in scope with no ticket, in priority order. A reviewer accepts one on the Overview.

Wildfire HENDERSON
Threatens 3 communities (26,700 people, modeled); No ticket
Wildfire NORTE
Threatens 2 communities (15,500 people, modeled); No ticket

Ticket ownership

Definition: Ticket ownershipTickets grouped by owner name as entered (trimmed, case-sensitive), most tickets first, then by name.

Who has accepted which incidents. Accepting assigns no team.

No tickets yet. A ticket is created when a reviewer accepts an incident.

Incidents by resource status

Definition: Incidents by resource statusUnaddressed: Threatens modeled communities and has no team assigned.Under-resourced (modeled): Threatens modeled communities and has at least one team, but assigned capacity is below its modeled personnel demand.Demand met (modeled): Threatens modeled communities and its modeled personnel demand is met: assigned capacity is at or above it. A modeled figure, not a statement that the incident is handled.No modeled threat: No modeled community is inside its threat radius, so it has no modeled demand. Listed so the buckets add up to all incidents.

All 20 incidents in four buckets that add up; only incidents that threaten a modeled community have a modeled demand.

1 unaddressed and 1 under-resourced of 2 threatening incidents

Incidents that threaten modeled communities

In priority order. The other 18 incidents have no modeled threat and are not listed.

Incidents that threaten modeled communities, in priority order
IncidentReal: EONET, retrieved 2026-10-25	StatusSynthetic	People threatenedSynthetic	Personnel of demandSynthetic
Wildfire HENDERSON	Under-resourced (modeled)	26,700	15 of 54
Wildfire NORTE	Unaddressed	15,500	0 of 16

Severity mix

EONET

Definition: Severity mixEvery incident (the EONET snapshot plus any simulated demo incidents), grouped by modeled severity (from reported acres and fire kind). Incidents are real; severity is modeled.

1 of 20 modeled high severity

Team utilization

Definition: Team utilizationAssigned: the team has an incident. Unassigned: it has none. Every team is counted once.

4 unassigned, holding 45 personnel

Decision activity

0 decisions · 0 acceptances · 0 simulated (demo)

Definition: Decision activityEvery audit record since the last demo reset, newest first: approvals with approver and rationale, direct assignments with the actor, incident acceptances with the owner, and simulated incidents and demo resets labeled as demo events.

Every audit record, newest first. Acceptances and simulated incidents are counted apart from decisions. Read-only; decisions are made on the Reviewer's Decisions page.

No decisions, acceptances or demo events recorded since the seed.