Emergency management needs resource-type counts by incident as columns on a command dashboard. What should they do?

Emergency-management command dashboards that need resource-type counts by incident as columns require a pivot (wide) transform. Each incident becomes a row with columns such as ambulances, engines, and mutual-aid units—the shape operators scan during an incident. Pivoting typed counts from long resource assignments into those columns matches how command UIs and situation reports consume readiness data.

Unpivoting resource-type counts by incident into columns for the command dashboard gets the transform backward because unpivot lengthens columns into rows and cannot produce the wide column layout the dashboard requires. Grouping resource-type counts by incident into columns for the command dashboard leaves results in grouped rows and does not widen resource types into separate columns the dashboard requires. Summarizing resource-type counts by incident into columns for the command dashboard collapses counts instead of widening resource types into separate columns and hides the typed breakdown operators need.

Exam caveat: Pivot widens categorized measures into columns; unpivot lengthens them. Choose pivot when the municipal consumer explicitly needs resource types as columns per incident. Keep a governed long table underneath if needed, and pivot in the serve layer.

Operational check: From a long assignment table, pivot resource_type counts by incident_id and confirm columns match the command dashboard contract. Inject a new resource type in a test feed and verify the pivot contract versioning policy (new column vs. mapped other). Refresh the dashboard dataset and confirm counts match dispatch system totals for a drill incident.