Government & Public Sector

Emergency Coordination Copilot

Designed for Emergency coordinator

Give the emergency coordinator a single grounded common operating picture during an active incident: fuse field reports, sensor and GIS layers, and resource availability, then propose the next tasking against the governing emergency operations plan with human commitment of every resource.

Contract GOV-03 · primary aggregate IncidentOperationalPeriod · mode loading

Decision brief

Incident command resource commitment: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Incident commander

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

During a riverine flood activation at EOC level 2, sensor telemetry shows a gauge crossing moderate flood stage two hours ahead of forecast while three field units report water over the roadway on two arterials.

Decision to make

Give the emergency coordinator a single grounded common operating picture during an active incident: fuse field reports, sensor and GIS layers, and resource availability, then propose the next tasking against the governing emergency operations plan with human commitment of every resource.

Outcome to show

committedAssignment gives Incident commander the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Multi-source situation intake
  2. 2Impact and life-safety assessment
  3. 3Plan and mutual-aid grounding
  4. 4Tasking recommendation for next operational period
  5. 5Incident command resource commitment

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Incident commander verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved IncidentOperationalPeriod evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Give the emergency coordinator a single grounded common operating picture during an active incident: fuse field reports, sensor and GIS layers, and resource availability, then propose the next tasking against the governing emergency operations plan with human commitment of every resource.
Primary aggregate
IncidentOperationalPeriod
Primary container
incidentOperationalPeriods
Hierarchical key
/tenantId + /incidentId
Schema version
1

Sample scenario

During a riverine flood activation at EOC level 2, sensor telemetry shows a gauge crossing moderate flood stage two hours ahead of forecast while three field units report water over the roadway on two arterials. The copilot fuses the reports, cites the flood annex clause that triggers evacuation of the low-lying mobile-home park at that gauge reading, and proposes committing two high-water rescue teams plus one transit bus strike team for the next operational period. The incident commander commits the rescue teams, defers the buses pending a shelter capacity check, and both decisions are written to the incident record with their cited sitreps and annex clauses.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
incidentOperationalPeriods Primary /tenantId + /incidentId Incident, SituationReport, ResourceStatus, TaskingRecommendation
emergencyPlanLibrary Reference /tenantId + /hazardType PlanProcedureChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Incident incidentOperationalPeriods /tenantId + /incidentId incident::{incidentId} None
SituationReport incidentOperationalPeriods /tenantId + /incidentId incident::{incidentId}::sitrep::{reportTimestampUtc}::{reportingUnitCode} narrativeVector
ResourceStatus incidentOperationalPeriods /tenantId + /incidentId incident::{incidentId}::resource::{resourceId} None
PlanProcedureChunk emergencyPlanLibrary /tenantId + /hazardType hazard::{hazardType}::plan::{planDocId}::{chunkOrdinal} chunkVector
TaskingRecommendation incidentOperationalPeriods /tenantId + /incidentId incident::{incidentId}::tasking::{taskingId} rationaleVector

Query patterns