NIMS Components Explained: Resource Management, Command & Coordination, and Communications

Quick Answers

The three NIMS components are: Resource Management; Command and Coordination; and Communications and Information Management. That is the full list under the current doctrine (NIMS Third Edition, October 2017).

Which NIMS component focuses on the coordination of resources? Resource Management — it standardizes how resources are identified, ordered, mobilized, tracked, and demobilized.

Which component contains ICS, EOCs, MAC Groups, and the JIS? Command and Coordination. Those four are structures inside it, not components of their own.

Is "modular organization" a component? No. Modular organization is a management characteristic of ICS that sits inside Command and Coordination. It describes how the org chart scales — not a fourth component.

If you came here from a study guide that lists five components, your guide is describing the retired 2008 version. Here is what actually changed, and what each of the three components does today.

NIMS Has Three Components — Not Five

The 2008 NIMS listed five components: Preparedness, Communications and Information Management, Resource Management, Command and Management, and Ongoing Management and Maintenance. A lot of training material — and a surprising number of exam prep sites — still teaches that list.

The 2017 rewrite collapsed it to three. The reasoning matters because it tells you where the old content went:

• Preparedness was removed as a standalone component because it duplicated the National Preparedness Goal. Its two operational pieces — Mutual Aid and Personnel Qualification and Certification — moved into Resource Management, where they functionally belong.
• Command and Management was renamed Command and Coordination and restructured around four coordination structures.
• Ongoing Management and Maintenance was reframed as a supporting function (the NIMS Integration Center work) rather than a component agencies operate.

What is left is three components that map to three questions every incident asks: What do we have and where is it? Who is in charge of what? How do we talk to each other and stay on the same page?

Component 1: Resource Management

Resource Management is the component that standardizes how agencies identify, order, mobilize, track, and demobilize the people, teams, equipment, and supplies an incident consumes. When a study question asks which NIMS component focuses on the coordination of resources, this is the answer.

It is organized around three activity sets:

• Resource management preparedness (before the incident): typing resources to a common standard, credentialing personnel, inventorying capability, and writing the mutual aid agreements that will actually move resources across jurisdictional lines.
• Resource management during an incident: the order-mobilize-track-recover-demobilize cycle, run against the incident's objectives for each Operational Period.
• Mutual aid: the agreements and the EMAC-style mechanisms that let one jurisdiction lend resources to another and get reimbursed for it.

The reason this component is also where FEMA reimbursement lives or dies: a resource you cannot prove you ordered, tracked, and demobilized is a resource you cannot defend at closeout. The full resource lifecycle — ICS 211 check-in, ICS 204 assignment, ICS 214 activity log, ICS 221 demobilization — is the documentary spine of a Public Assistance cost claim. Resource Management is not an administrative afterthought to the response; it is the part of the response a FEMA reviewer reads first.

Component 2: Command and Coordination

Command and Coordination is the component most people mean when they say "NIMS." It describes the systems and structures that provide a standard national framework for managing incidents, and it contains four structures:

These four are frequently confused with one another, and the confusion is expensive — it is the difference between an EOC coordinator authorizing a procurement that should have routed through the MAC Group, and a clean audit trail. We unpack the boundaries in MAC Group vs. EOC vs. Unified Command and the broader umbrella in the Multi-Agency Coordination Systems explainer.

Two more terms get miscategorized as components and belong here instead. ICS itself is not a NIMS component — it is one structure inside Command and Coordination, a point worth getting right before you write an RFP. (See NIMS and ICS Explained.) And modular organization — the principle that the incident org chart expands and contracts to fit the incident — is one of ICS's management characteristics, not a component. The fourteen management characteristics (common terminology, modular organization, management by objectives, incident action planning, manageable span of control, and the rest) all live within this component.

Component 3: Communications and Information Management

The third component is the one that keeps the other two honest. Communications and Information Management establishes the principles for interoperable, reliable, scalable, and portable communications — and for managing the information that flows across the incident.

Its job is to build and maintain two things:

• A common operating picture — a single, shared view of the incident that command and support entities all work from, so the EOC and the field are not running on different facts.
• Situational awareness — the continuously updated understanding of what is happening that decisions get made against.

This is where voice and data interoperability requirements, standardized communications planning (the ICS 205), and information-sharing protocols live. It is also the component that gets quietly violated most often: when the planning section's incident action plan is current but the field is working off yesterday's printout, that is a Communications and Information Management failure, not an operations failure. A common operating picture only counts if it is actually common.

Where the Components Meet

The three components are not silos. A single resource request touches all three: Resource Management defines and tracks the resource, Command and Coordination decides who authorizes and assigns it, and Communications and Information Management carries the request and updates the common operating picture when its status changes.

That intersection is also where documentation gets made — or lost. When operations run inside a system built on the ICS data model — organized by Operational Period, with resources tracked from check-in to demobilization — the records the three components require are produced as a byproduct of running the incident, not reconstructed afterward from memory and a stack of paper forms. Documentation that survives a FEMA audit is documentation that already existed before anyone asked for it.

The Bottom Line

NIMS has three components. Resource Management answers what do we have. Command and Coordination answers who decides what. Communications and Information Management answers how do we stay on the same page. Everything else you may have seen on the list — Preparedness, ICS as a component, modular organization as a component — is either retired 2008 doctrine or a structure or characteristic that lives inside one of the three.

Get the framework right and the rest follows: the right software, the right RFP language, and the right audit trail. Start with NIMS and ICS Explained for the foundation, then MAC Group vs. EOC vs. Unified Command for the structures inside Command and Coordination.