Chapter 3 · EV13

Emergency Management as CAM Governance Analogue

Date collected: 26 May 2026

Summary

Emergency management's ICS/NIMS frameworks offer tested multi-agency coordination templates; scalable, interoperable structures mirror CAM governance gaps

Headline Finding

Emergency management has solved the cross-silo coordination problem through formal hierarchical command structures (Gold/Silver/Bronze in UK; ICS in US) and multi-agency coordination protocols. These institutional architectures enable real-time decision-making across dozens of agencies with different legal authorities, operational cultures, and information systems. The analogy for CAM: emergency management proves that multi-agency, multi-domain governance at city scale is operationally feasible. The question for CAM governance is not whether integration is possible, but what institutional form it should take.

UK Civil Contingencies Act 2004 — Gold/Silver/Bronze Command Structure

Statutory Framework:

Legal basis: Civil Contingencies Act 2004
Scope: multi-agency emergency response coordination across all responders (public, private, nongovernmental)
Designated “category 1 & 2 responders” must participate in formal coordination

Hierarchical Command Structure:

Gold (Strategic Level):

Sets overall management framework and strategic objectives
Defines policies to guide response (short-term recovery, long-term restoration)
Operates remotely from incident scene (typically from Strategic Coordinating Centre)
Hosted and chaired by police (local Chief Constable or nominated deputy)
Participants: senior representatives from all responding agencies (health, fire, local government, utilities, etc.)
Decision cycle: hours to days

Silver (Tactical Level):

Implements strategic direction from Gold into operational tasks
Manages incident-specific tactical response (resource allocation, sequencing)
Located at command center (near but not at incident)
Participants: operational commanders from relevant agencies
Decision cycle: minutes to hours

Bronze (Operational Level):

Executes tactical directives from Silver at incident site
Manages real-time tactical decisions (on-scene resource deployment)
Located forward at incident or in close support position
Participants: operational personnel from responding agencies
Decision cycle: seconds to minutes

Multi-Agency Coordination Mechanisms:

Unified command: all agencies with incident responsibility participate in decision-making at their respective levels
Interoperability: communication standards enable cross-agency information flow
Formal liaison roles: each agency designates representative at each command level
Clear role definition: eliminates competing command authority

Key Operational Features:

Scalable structure: can expand/contract based on incident complexity and scale
Proven resilience: operates across conflicting agency cultures and legal frameworks
Real-time information flow: each level has information from levels above and below
Clear accountability: each commander has defined scope and reporting relationships

Governance Lesson for CAM: The UK’s Gold/Silver/Bronze model proves that formal hierarchical coordination works at city scale across dozens of agencies. The architecture succeeds because: (1) it defines decision-making authority clearly (who decides at what level), (2) it enables information flow upward and directives downward, (3) it requires agencies to put personnel at command posts (embodied coordination, not virtual), (4) it has legal backing (Civil Contingencies Act). CAM governance could adapt this model: CAM might need a hierarchical decision structure with clear escalation protocols for conflicts about Flows, Space, and Power allocation.

Source:

US NIMS (National Incident Management System) — ICS as Cross-Silo Solution

Statutory Framework:

Legal basis: Homeland Security Presidential Directive-5 (2003)
Implementation: National Incident Management System (NIMS), 2004
Scope: standardized approach to incident management across all hazards, all responders (federal, state, local, private, nonprofit)
Legal requirement: all agencies receiving federal emergency funding must adopt NIMS/ICS

Incident Command System (ICS) Structure:

The ICS is a modular, scalable command structure with four core functional sections:

Operations: on-scene incident response (fire suppression, rescue, medical, recovery)
Planning: situational assessment, intelligence, strategic planning
Logistics: resource acquisition, personnel support, equipment
Finance/Administration: cost tracking, procurement, contracts

Multi-Agency Coordination Mechanisms:

Unified Command: All agencies with incident responsibility participate in unified decisionmaking (not competing commands)
Multi-Agency Coordination System (MACS): Enables inter-agency resource sharing and prioritization across concurrent incidents
Area Command: Established when multiple ICS organizations must be overseen (complex/widespread incidents)
Incident Management Teams (IMTs): Standardized personnel rosters (cadres of trained commanders and staff)

Scalability and Cross-Silo Coordination:

Modular expansion: Each core section can expand by adding sub-units (functional specialization or geographic sectors called “divisions”)
Interoperability standards: Common vocabulary, communication protocols, information systems enable cross-agency data sharing
Resource typing: Standardized descriptions of equipment and personnel enable rapid mutual aid
Typing: Incident complexity and response size determine initial ICS organization

Key Operational Features:

Proven across wildfires, hurricanes, floods, terrorist attacks, pandemic response
Enables coordination between agencies with zero pre-existing relationships (e.g., rural county fire departments + federal resources)
Operates despite legal jurisdictional conflicts and competing agency interests
Standardized training ensures common command vocabulary across thousands of agencies

Governance Lesson for CAM: The US NIMS/ICS model proves that cross-silo coordination can be achieved through: (1) standardized command structure (not negotiated ad hoc), (2) modular expansion based on incident complexity, (3) legal requirement for adoption (federal funding leverage), (4) standardized training and interoperability standards. CAM governance could adopt equivalent principles: standardized decision structure, modular escalation based on conflict complexity, legal anchoring (e.g., through transportation code), and coordinated training for agency personnel.

Source:

NYC Office of Emergency Management (OEM) — Proof of Concept at City Scale

Institutional Framework:

Primary agency: NYC Office of Emergency Management (OEM)
Statutory basis: NYC Charter, Chapter 19-A; coordination mandates to all city agencies
Infrastructure: Emergency Operations Center (EOC) with physical workstations for 130 agencies

Citywide Incident Management System (CIMS):

Adapts federal ICS to NYC context
Defines agency roles and responsibilities during multi-incident emergencies
Specifies integration of regional, state, and federal agencies into city response
Establishes clear escalation protocols and decision authority at each level

Multi-Agency Coordination Infrastructure:

Emergency Operations Center (EOC):
- 130 dedicated workstations for city, state, federal, and nonprofit agency representatives
- Video conferencing, secure communications, GIS capabilities
- Operational during major incidents or sustained threats
- Enables real-time coordination across agencies
Coordination Mandate:
- All city agencies required to provide information to OEM for emergency planning
- OEM designated as lead agency for coordination and resource facilitation
- All agencies must provide personnel, equipment, and resources upon OEM request
- Information-sharing requirement: agencies must promptly report relevant incident data

Decision Authority:

OEM chairs multi-agency coordination
Each agency represents its domain expertise (NYPD for law enforcement, FDNY for fire/rescue, DOH for health, etc.)
Unified decision-making: OEM coordinates rather than commands (respects agency autonomy within coordination framework)

Key Operational Features:

Proven in: 9/11 response, Hurricane Sandy, COVID-19 pandemic, infrastructure emergencies
Enables coordination across 130+ agencies without pre-established bilateral agreements
Functions despite competing agency cultures and legal authorities
Operational readiness maintained through regular drills and staff training

Governance Lesson for CAM: NYC’s OEM/CIMS model provides proof of concept that multi-agency coordination works at major city scale. The key success factors are: (1) statutory mandate (Charter requirement, not optional), (2) dedicated infrastructure (EOC with agency representatives present), (3) information-sharing legal framework (agencies must report to OEM), (4) clear escalation (agency roles defined by incident type), (5) unified decision authority (OEM as coordinator, not competing commands). CAM governance should require equivalent statutory anchoring and infrastructure investment.

Source:

Thread