Applying NIMS Management Characteristics Across Roles and Disciplines
One system, many disciplines
NIMS requires the same ICS structure for fire, EMS, law enforcement, public health, public works, and NGOs. A law enforcement operation - a planned event or an active threat - uses the same five functions; tactical units may be strike teams and a security branch may sit under Operations.
Complexity and typing
Incidents are typed 1 through 5 by complexity: Type 5 is the smallest and locally managed, Type 1 is national-level. Incident Management Teams are typed to match, and a Type 3 all-hazards IMT typically has most command and general staff positions filled. Resource typing describes capability - a Type 1 engine versus a Type 3 engine - so resources are ordered by capability, not by local nickname.
Across roles
A Planning Section Chief applies management by objectives by running the Planning P; the IC, not Planning, sets the objectives. A Logistics Chief applies comprehensive resource management through ordering, tracking, and demobilization. A company officer applies unity of command and accountability by checking in, maintaining a personnel roster, and reporting to a single supervisor.
Worked example
A public health department runs a point of dispensing for mass vaccination: Operations covers screening, vaccination, and traffic flow; Planning tracks throughput and writes the IAP; Logistics manages supplies and cold chain; Finance tracks costs for reimbursement. The same structure shrinks to a single clinic with an IC and one or two positions.
Traps
NIMS does not demand every position be filled - it demands the structure be available and used. Unified Command is not automatic whenever two agencies respond; it applies where agencies have jurisdictional or functional responsibility. EOCs coordinate and support the on-scene organization; they do not command the incident.