Montana Disaster & Emergency Services — SECC Familiarization Series
Module 2: ICS vs. ISM
Same emergency management toolbox, two different jobs.
Module 1 established that the SECC coordinates and supports rather than commands. This module unpacks exactly how that plays out — comparing the Incident Command System (ICS) that most responders already know to the Incident Support Model (ISM) the SECC runs on.
This module takes about 5–7 minutes. It's especially useful if you're a local emergency manager comparing your own EOC's structure, since the ICS-vs-ISM distinction is often the single most useful thing to understand before deciding whether — and how — to adapt your own center.
The Incident Command System (ICS) is the standardized, NIMS-based structure used to manage on-scene, tactical response. It's built around a single Incident Commander who directs a General Staff — Operations, Planning, Logistics, and Finance/Administration — to execute an Incident Action Plan (IAP) from an Incident Command Post.
ICS is designed to answer one question well: who is directing people and resources at this specific incident, right now? That clear chain of command is exactly what makes it effective on the fireline, at a flood scene, or any other tactical response.
The Incident Support Model (ISM) is Montana DES's NIMS-aligned structure for organizing the SECC. Instead of a single commander directing tactics, ISM organizes around the functions a coordination center actually performs: managing information, supporting resource needs, and coordinating recovery.
Rather than Operations, Planning, Logistics, and Finance/Admin, the SECC organizes under the SECC Manager into three sections:
Module 3 covers this organization chart in full detail, position by position.
Same emergency management foundation — NIMS — applied to two different jobs.
ICS and ISM aren't competing systems — they operate side by side during the same incident. When both field incident command and the SECC are active, the SECC supports rather than directs on-scene tactics, providing coordinated resources, situational awareness, and planning support.
In practice: if you're working in the SECC and a field team sends over an ICS-201 or an IAP, you're not replacing it or overriding it — you're using it to inform the SECC's own situational awareness and the ISP, so state-level support lines up with what the field actually needs.
Tap each one to see a quick reality check.
Before the knowledge check, here's the core distinction:
Command structure for directing tactical operations at the incident scene.
Coordination structure for the SECC's statewide support role.
Via shared objectives, and the IAP/ISP relationship — not by one replacing the other.
Same as last time — no score, no pressure. Just a quick way to reinforce the key ideas.
1. What is the primary difference between ICS and ISM?
2. What planning product does the SECC produce under ISM?
3. When both field ICS and the SECC are active on the same incident, what's true?
4. What does CORE stand for?
Content in this module is drawn from the Montana DES SECC Operations Manual (2026) and related SECC tools. This is a familiarization course; it is not a substitute for position-specific training or the manual itself.