Emergency Coordination Copilot
Outcome
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.
| Portfolio attribute | Value |
|---|---|
| Primary persona | Emergency coordinator |
| Primary aggregate | IncidentOperationalPeriod |
| Cosmos DB containers | 2 |
| Grounding data | incidents, sensors, GIS, resources, procedures |
| Development estimate | USD 60-220 monthly dev estimate |
| Runtime options | Python FastAPI and C# ASP.NET Core |
Productivity hypothesis
These measures reflect the workflow, evidence, decision boundary, and industry risk for this use case.
| Impact type | Measure | Conservative internal assumption | Customer measurement |
|---|---|---|---|
| Productivity | Operational brief preparation time | 8-12% reduction | (baseline median operational-brief minutes - assisted median minutes) / baseline median minutes * 100 |
| Quality or risk | Corrected or reissued briefs | 2-5% reduction | (baseline corrected or reissued brief rate - assisted rate) / baseline rate * 100 |
Important: Conservative internal pilot assumptions only; not public benchmarks, commitments, or expected customer results. Validate against a comparable baseline or matched control cohort with mandatory human review.
Rationale: Incident, sensor, GIS, resource, and procedure evidence can accelerate situation reporting in a high-consequence workflow.
Pilot guardrail: Incident command exclusively owns warnings, prioritization, operational decisions, and resource commitments.
Customer validation plan
- Baseline the current workflow with representative users and tasks.
- Run the accelerator on the same task mix with human review retained.
- Measure operational brief preparation time and corrected or reissued briefs with the documented formulas.
- Replace internal assumptions with customer-observed results before a business case.
Why Azure Cosmos DB
This AI solution needs an operational data plane, not only a vector index:
- Hybrid vector and full-text retrieval combines semantic recall with exact identifiers, codes, names, and domain language.
- Hierarchical partition keys and metadata predicates keep tenant and domain boundaries in the normal query path.
- Operational JSON, source chunks, workflow and agent state, feedback, and audit records remain together for low-latency reads and governed writes.
- Change feed reacts to source and operational updates without polling.
- Autoscale throughput, configurable consistency, and multi-region distribution support variable demand and enterprise availability.
Domain workflow

| Stage | Actor | Input → output | Approval |
|---|---|---|---|
| 1. Multi-source situation intake | Field units, sensors and GIS connectors | SituationReport → commonOperatingPicture | Policy controlled |
| 2. Impact and life-safety assessment | Emergency coordination copilot | commonOperatingPicture → impactAssessment | Policy controlled |
| 3. Plan and mutual-aid grounding | Retrieval orchestrator | impactAssessment → PlanProcedureChunk | Policy controlled |
| 4. Tasking recommendation for next operational period | Emergency coordination copilot | PlanProcedureChunk → TaskingRecommendation | Policy controlled |
| 5. Incident command resource commitment | Incident commander | TaskingRecommendation → committedAssignment | Human required |
Technical architecture

Cosmos DB data model
| Container | Hierarchical partition key | Documents | Search paths |
|---|---|---|---|
incidentOperationalPeriods | /tenantId, /incidentId | Incident, SituationReport, ResourceStatus, TaskingRecommendation | /narrativeVectorEmbedding, /rationaleVectorEmbedding, /narrativeVector, /rationaleVector |
emergencyPlanLibrary | /tenantId, /hazardType | PlanProcedureChunk | /chunkVectorEmbedding, /chunkVector |
Query contract
| Query | Container | Scope | Purpose |
|---|---|---|---|
| CurrentOperationalPictureSitreps | incidentOperationalPeriods | single-partition | Return the latest situation reports for the active operational period to render the common operating picture. |
| AvailableResourcesByType | incidentOperationalPeriods | single-partition | Find uncommitted resources of a required type that can reach the affected area within the period. |
| HazardAnnexRetrieval | emergencyPlanLibrary | single-partition | Retrieve the plan annex and mutual-aid clauses that apply to the hazard and jurisdiction in play. |
| PendingTaskingQueue | incidentOperationalPeriods | single-partition | Show taskings awaiting incident commander commitment, life-safety items first. |
Python and C# services route each document type to its declared container and hierarchical partition key. ETag-based writes protect mutable aggregates, while append-only records and bounded cross-partition queries preserve scale.
Azure deployment

Clone the source repository, authenticate with Azure, and run:
Set-Location accelerators/government-public-sector/emergency-coordination-copilot
az login
./Deploy.ps1 -Runtime python -Location eastus2
Change python to csharp to deploy the .NET implementation.
Explore the implementation
- Launch signed-in demo
- Implementation article
- Domain data model
- Workflow and API contract
- Python application
- C# application
- Domain container Bicep
- Platform Bicep
- Cost and configuration
- Source repository